boot=/dev/hda has nothing to do with /boot. It just means that lilo is installed on the master boot record of the first ide hard drive. What you have to do if you want to move /boot from the / partition to a partition of its own is mkdir /mnt/tmpmnt1 mount /dev/hda1 /mnt/tmpmnt1 cp /boot/* /mnt/tmpmnt1 umount /mnt/tmpmnt1 mount /dev/hda1 /boot /sbin/lilo umount /boot rm /boot/* edit the fstab file to have an entry for the /boot mount point reboot Anders On Saturday 15 September 2001 21.29, Patrick Nelson wrote:
Cliff Sarginson wrote: ----------------->>>> A mount point is just a directory. Conventionally people store kernel images and associated files in /boot .. if it isn't being used as a mount point for a seperate boot fs, then it is just used as an ordinary directory would be. One of the reasons is that until recently and only with recent versions of lilo and PC bios's the boot files had to be in the first physical sectors of the disk. So people installing linux would tend to create a file system for /boot as the first on the disk, making it about 12-15MB in size. ----------------->>>> Understand, but boot acts different so I want to make sure that I'm doing it right. Here is how boot acts different:
1. No entry in fstab 2. Called out in lilo.conf as boot=/dev/hda 3. Doesn't show up with df command 4. Can't unmount it
One thing I've noticed is that on the new drive where I've created and then copied the files of the boot partition (/dev/hda1 is new the new boot and /dev/hdb1 is old boot) it is mountable (mount /dev/hda1 /mnt/tmpmnt1) and the old boot isn't mountable (mount /dev/hdb1 /mnt/tmpmnt2) saying device is busy. To me this says that lilo isn't booting off the new mount point using the boot=/dev/hda. Yes I've run lilo and rebooted! Anyone have input on this?