Tony Lissner wrote: > [EMAIL PROTECTED] wrote: > >> 1) How will grub work out where to find menu.lst? How will it 'know' >> to use the updated /dev/hda7/boot/grub/menu.lst rather than the out >> of date /dev/hda6/boot/grub/menu.lst version? >> >> 2) I used apt to update the kernel image, and it thought I was still >> using the / mounted on hda6 (it clobbered all the extra hda7 entries >> I'd made and used to boot from). How do I tell apt that I'm running >> on hda7, not the hda6 which I was using when I first installed?
Check where the kernel is looking for root with rdev If it is hda6 it should change to hda7 after a reboot >> What made apt decide that hda6 is / - that disagrees with both >> menu.lst and fstab? Is that information stored in a 3rd place, too? >> >> I've manually fixed up the hda7 menu.lst file, but before I went any >> further I thought I'd ask about this, in case. >> >> I should and could copy the menu.lst file to both drives again, but >> thought I'd ask which one grub is really using, and how it picks it. >> >> I still wish grub had a mode that let you check the config before you >> rebooted. >> > > The easiest way to set where grub looks for the stage* images might be > to just re-install grub from the new partition. > try unmounting /dev/hda6 and commenting it out in fstab, then from the > new partition do: > # sudo grub-install /dev/hda > # sudo update-grub > and it should find the new menu.lst > > > or checkout the '--root-directory=' option > install grub-doc > info grub > > -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
