On Sat, Mar 20, 2010 at 04:55:19PM -0400, Stephen Powell wrote: > On Sat, 20 Mar 2010 15:19:26 -0400 (EDT), Freeman wrote: > > > > I believe those files generate the /boot/grub/grub.cfg when "grup-update" > > [sic] is run. > > > > However, the system still boots off menu.lst. It had to be edited to boot > > the system correctly. grub-update writes a non-existent UUID to menu.lst, > > which will mean manual editing after every kernel upgrade. > > > > But I am burying my question. > > > > My real question, where could grub-update be getting that wrong UUID from? > > > > I'm not quite as ignorant of grub1 as I am of grub2, as I still use grub1 on > some of my machines. (I haven't gotten around to converting them > to lilo yet.) But anyway, I believe that with grub-legacy the correct > command is > > update-grub > > not > > grub-update >
Most correct. (Shoddy posting skills no doubt.) > As to incorrect UUIDs, could this be due to the different naming convention > for partition numbers between grub1 and grub2? If I recall correctly, grub1 > numbers them starting with 0, while grub2 numbers them starting with 1. > It's just a guess, I don't claim to know the answer. > That explains the (H0,2) notation rather than the old style (H0,1) for //dev/hda2 in in the boot/grub/grub.cfg . Thanks. I reversed my edit on /that. -- Kind Regards, Freeman http://bugs.debian.org/release-critical/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100320235633.ga14...@europa.office
