> /mnt/boot/vmlinuz-2.6.10-5-386 /mnt/boot/vmlinuz-2.6.15-25-386
> /mnt/boot/vmlinuz-2.6.12-10-386 /mnt/boot/vmlinuz-2.6.15-26-386
> /mnt/boot/vmlinuz-2.6.12-9-386 /mnt/boot/vmlinuz-2.6.15-27-386
> /mnt/boot/vmlinuz-2.6.15-23-386 /mnt/boot/vmlinuz-2.6.17-10-386
>
> That collection can definitely be trimmed back to the latest few, but
> now it ought to be possible to build a new menu.lst that works.
The most resent is probably more than good enough.
> This AM it occurred to me that even if hda does refer to the CD drive -- when
> there's a disk in it -- that should almost never interfere with booting.
> Thanks for your patient help.
No, hda is no longer the cdrom drive, ever. Unless you recable your
IDE drives again. You'll have to look through dmesg and find out
where the cdrom drive is now and update fstab. Actually you should do
`eject -t /dev/cdrom'. If that works change your fstab line to read
/dev/cdrom instead. You can do `ls -l /dev/cdrom' to see where its
pointing at.
You know, maybe that should be reported as a bug... Ubuntu sets
/dev/cdrom up properly, but then doesn't use it in the fstab file. I
just checked a couple Ubuntu machines and they all do that. Can
someone with feisty confirm what it does?
Received on Mon Apr 16 09:46:18 2007
This archive was generated by hypermail 2.1.8 : Mon Apr 16 2007 - 09:46:28 CST