zsh-2.6beta13-1 uploaded
Date: 24 Dec 95 06:02 UT Source: zsh Binary: zsh Version: 2.6beta13-1 Description: zsh: A shell with lots of features. Priority: Low Changes: * New upstream version. * Recompiled with updated gcc-2.7.2 (avoiding potential -O2 bugs.) Files: -rw-rw-r-- 1 rob rob605672 Dec 24 00:29 zsh-2.6beta13-1.tar.gz -rw-rw-r-- 1 rob rob127620 Dec 24 00:30 zsh-2.6beta13-1.diff.gz -rw-r--r-- 1 root root 401644 Dec 24 00:39 zsh-2.6beta13-1.deb 862e151d8f02ed43becf6958a67fcb9e zsh-2.6beta13-1.tar.gz 3608a3de3bb7668471614738037701a5 zsh-2.6beta13-1.diff.gz 9318701243ba104a6a25e54baf5dbf09 zsh-2.6beta13-1.deb -- Robert Leslie [EMAIL PROTECTED]
Bug#2063: scsi driver sequence unreasonable
Package: source Version: 1.3.43 The file drivers/scsi/hosts.c defines the sequence in which different SCSI controller cards are identified. The AHA152X driver appears early in the list, which is unreasonable if there is another, smarter, SCSI controller in the system... since it will result in the 1510/1522/1522/etc card assuming the role of the 0th SCSI channel. It seems to me that the "smartest" or "fastest" cards should be listed first, since it seems obvious that if there are multiple cards in a system, that the fastest one should be the default for the first SCSI channel. In my case, I have systems with 1542B and 1740A cards which also sometimes get a 1510 card when I need a long cable run to an external box, or more devices, or something. I've just moved the AHA152X driver to near the end of the list, but it seems that a more general review of the sequencing of SCSI card discovery is in order. Bdale
Bug#2064: aha1740 driver only supports one card
Package: source Version: 1.3.43 The SCSI device driver for the AHA1740 only supports one card in a system at one time. This is annoying. Bdale
Bug#2065: single user isn't
Package: base Version: 0.93.6-13 It is utterly unreasonable for the system to try and do fsck's when the system is booted with 'linux single'. The whole point of a single user boot is that something is wrong that needs reasoned attention from a system adminitrator. A single-user boot should do absolutely *nothing* that isn't required to drop the system admin into a shell. This caused me considerable grief when one of the disks on my system was starting to fail, and I was desperately trying to extract a few critical files that had been updated since the last backup. The cycle was to boot, snag a few files before the disk warmed up and failed, then power down to let things cool off, then repeat. The insistence of the system on doing fsck's at every boot made this a much less productive process per unit time than it could/should have been. Bdale
