Paul Johnson wrote:
I have a Firewire external hard drive, and recently with the upgrade
to linux-image-2.6.22, my firewire block device has been detecting as
sda instead of sdc, causing my machine to hang at boot if it is turned
on. What can be done to resolve the detection order?
This is
I have a Firewire external hard drive, and recently with the upgrade
to linux-image-2.6.22, my firewire block device has been detecting as
sda instead of sdc, causing my machine to hang at boot if it is turned
on. What can be done to resolve the detection order?
--
To UNSUBSCRIBE, email to
fine in linux afterwards (and
beforewards). There are no error messages, just a lack of
device detection messages. /proc/bus/usb/devices won't
show the drives when this happens, but all USB ports are
detected.
ctl-alt-del as bios is scanning for a bootable floppy does
the trick
I wrote:
I'm not sure I see why checkpointing every test should be particularly
slow.
Michele Bini writes:
Because you have to wait after every test for the checkpoint to
be written to disk and the disk to be flushed
A few milliseconds, according to my measurements. How many tests do we
On Sun, Mar 21, 1999 at 08:38:56PM -0600, John Hasler wrote:
Rob Browning writes:
Presuming that most people won't have lockups, the overall inconvenience
might be less this way, particularly if it dramatically cuts the time to
run successful tests.
I'm not sure I see why checkpointing
I wrote:
I'm not sure I see why checkpointing every test should be particularly
slow.
Michele Bini writes:
Because you have to wait after every test for the checkpoint to
be written to disk and the disk to be flushed
I'm not convinced that has to all that slow.
and disk's builtin cache to
6 matches
Mail list logo
