Bug#243011: os-prober: installation report (beauty, but some issues)
Comments below.
One additional suggestion.
I don't really want the Windows 98 partition in my boot menu (removed it
manually now). It would be very nice if OS-prober would offer a list of
options based on the probe and allow the user to (de)select the ones (not) to
be included. However, this introduces a risk for newbies as well as they
might inadvertently deselect to much.
This is severity Wishlist-minus and needs further thought.
On Saturday 10 April 2004 20:25, Joey Hess wrote:
> Frans Pop wrote:
> It told grub the right boot partition (hd0,0), but then gage it a path
> to the kernel that is not relative to that partition (/boot/vmlinuz
> instead of /vmlinuz). Fixed.
Confirmed. After I remove '/boot' Woody boots fine :-)
> > I have some additional entries in my current lilo.conf for backup kernel
> > versions and for memtest. These were not included in the new GRUB menu.
> > This means, if I had installed GRUB on /dev/hda, I would have lost these
> > entries.
>
> Something went wrong, you should have gotten those entries.
<...>
> Can you send me your /etc/fstab for /dev/hda5? Also,
> grep for "linux-boot-prober" in the installed system's
> /var/log/debian-installer/syslog and send me that as well.
Great that the lilo.conf parser caches all!
Not much in the log:
linux-boot-prober: info: found boot partition /dev/discs/disc0/part1 for linux
system on /dev/discs/disc0/part5
(same message repeated because I ran GRUB twice)
/etc/fstab from Woody is attached.
> > Other observations
> > ==================
> > As you can see in my partition list, fdisk marks /dev/hda3 as the active
> > partition. I don't understand what's happening here because lilo is
> > installed on /dev/hda (master boot record) and I am certain it boots from
> > that! Lilo can't be installed on /dev/hda3 as the boot record of that
> > partition contains the win2k bootrecord. So it looks like lilo works
> > independent of the 'active partition'.
> >
> > I think a test should be run to see what happens if current lilo is on
> > for example /dev/hda5 and you install GRUB to /dev/hda. Will a new boot
> > use the old lilo or the new GRUB?
> > You might need to change the active partition during GRUB installation in
> > such situations (or something).
>
> This is beyond my knowledge and should probably be a bug on partman.
Perhaps Anton could shed some light on this?
The problem IMO is that when you run partman, you don't know yet how you're
going to install GRUB and that info is needed to set the correct partition
active.
I think I'll try installing GRUB to my /dev/hda after my next download (with
the fixes). Maybe I'll try to relocate lilo first (e.g. to /dev/hda5).
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/discs/disc0/part5 / ext3 errors=remount-ro 0 1
/dev/discs/disc0/part6 none swap sw 0 0
/dev/discs/disc0/part1 /boot ext3 defaults 0 2
proc /proc proc defaults 0 0
none /proc/bus/usb usbdevfs defaults 0 0
/dev/floppy/0 /floppy auto user,noauto 0 0
/dev/cdroms/cdrom0 /cdrom iso9660 ro,user,noauto 0 0
/dev/cdroms/cdrom1 /cdrw iso9660 ro,user,noauto 0 0
/dev/cdroms/cdrom1 /cdrw-udf udf ro,user,noauto 0 0
/dev/discs/disc0/part2 none ignore
/dev/discs/disc0/part3 /mnt vfat rw,gid=50,umask=5002,noexec,noauto 0 0
/dev/discs/disc0/part7 /mnt vfat rw,gid=50,umask=5002,noexec,noauto 0 0
/dev/discs/disc0/part8 /mnt vfat rw,gid=50,umask=5002,noexec,noauto 0 0
/dev/discs/disc0/part9 /mnt vfat rw,gid=50,umask=5002,noexec,noauto 0 0
# <file system> <mount point> <type> <options> <dump> <pass>
elrond.fjphome.nl:/exports/dists /usr/local/dists nfs rw,hard,intr 0 0
elrond.fjphome.nl:/exports/src /usr/src/downloads nfs rw,hard,intr 0 0
elrond.fjphome.nl:/exports/home /home nfs rw,hard,intr 0 0
elrond.fjphome.nl:/var/mail /var/rmail nfs rw,hard,intr 0 0
Reply to: