I'm in the process of moving over to a new PC, with a fresh install of
Ubuntu (6.06).  I'm gradually learning the Debian way of things (as
opposed to the Red Hat way).

When I installed, I thought 10GB would be enough space for the root
partition.  And it was - by about 300MB.  (I selected a lot of
useful-sounding packages.)

The root partition for the install was hda6, and so I resized hda7 to
12GB, and copied all of hda6 to hda7, then booted up that.  (I then
fixed /etc/fstab to point / at hda7 and added all the hda7
kernels to menu.lst and copied that file to both drives and rebooted
again, because having grub and fstab disagree about where / was,
confused the system substantially.)

That worked well.

So I resized hda6 to 12GB too, but haven't rebooted.  (I've been working
from / being on hda7 since then.)

So now I have two partitions with /boot/grub directories, though the
hda6 one is old.

Which (finally) brings me to my questions:

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?

   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.

luke

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to