On Sat, Mar 20, 2010 at 11:13:50AM +0000, Brad Rogers wrote: > On Sat, 20 Mar 2010 03:05:56 -0700 > freeman <gen...@worldwidehtml.com> wrote: > > Hello freeman, > > > Finally installed grub legacy. (Long story. And no I don't want > > Grub2/Grub-PC, whatever. > > Currently, you may well be using grub2. Especially since you say > installing "grub" pulled in grub-pc. On testing, you need to install > "grub-legacy" to use grub1. The package "grub" is a transitional one to > move the machine over to using grub2. >
Thanks Brad. That is what confused me. But it looks like I did get legacy installed. |free...@europa:~$ apt-show-versions grub-legacy |grub-legacy/testing uptodate 0.97-59 |free...@europa:~$ | |i A grub-common - GRand Unified |Bootloader, version 2 (common files) |i grub-legacy - GRand Unified |Bootloader (Legacy version) |i grub-legacy-doc - Documentation for |GRUB Legacy grub-common is a listed as a dependency of legacy. And common installs, among others, these files: |/etc |/etc/grub.d |/etc/grub.d/00_header |/etc/grub.d/30_os-prober |/etc/grub.d/10_linux |/etc/grub.d/README |/etc/grub.d/40_custom I believe those files generate the /boot/grub/grub.cfg when "grup-update" 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? -- 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/20100320191926.gb10...@europa.office
