Yes I wondered about that. I also moved the /home/karl to another
partition and fstab connects it back on bootup. I see no change as a
user. But if you use $ df it shows you the now two partitions connected
to the main tree.
On Wed, 2007-10-10 at 06:09 -0600, Karl Larsen wrote:
I moved my /boot from the main directory tree to a new partition.
All of F7 was in the /dev/sda5 partition. I moved /boot to /dev/sda6 and
with lots of rebooting got it to work. Here is my grub.conf file.
title Fedora (188.8.131.52-85.fc7)
kernel /vmlinuz-184.108.40.206-85.fc7 ro root=/dev/sda5 quiet
title Fedora (220.127.116.11-76.fc7)
kernel /vmlinuz-18.104.22.168-76.fc7 ro root=/dev/sda5 quiet
Now the problem is, on the next kernel update it didn't work right.
Instead of putting the new kernel in /dev/sda6 it made a new /boot
directory in /dev/sda5. Here is what is in this directory:
[[email protected] boot]# ls
[[email protected] boot]#
I expect I can just copy these to /dev/sda6 but why did the kernel
update do this?
After you moved things around, did you change fstab entries to
make /boot get mounted in /dev/sda6? If not, the /boot directory in
root (/dev/sda5), will get used as a directory, rather than a mount
point for a /boot partition.
I think you should be right to just copy them over and change anything
that refers to their location to point to the right places.
Well now the partition that has /boot is attached so kernel updates will
see no change to the system. I hope this does it :-)
Karl F. Larsen, AKA K5DI