On Sat, Sep 15, 2001 at 12:29:21PM -0700, 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 versione 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 No, if it is a file system it will have an entry in fstab.
2. Called out in lilo.conf as boot=/dev/hda No, you are confusing two things "boot" in lilo is telling lilo the device to boot from. /boot could be /anything if you like !
3. Doesn't show up with df command Does if it is a file system.
4. Can't unmount it Can if it is a file system and not in use.
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?
/dev/hda specifies where the boot sectors lie and what lilo will use. hda is not a file system ! Here is an excerpt from my lilo.conf boot = /dev/hda read-only lba32 menu-scheme = Wg:kw:Wg:Wg prompt timeout = 100 message = /boot/message image = /boot/vmlinuz label = linux root = /dev/hdb3 initrd = /boot/initrd image = /boot/vmlinuz.old label = linux.old root = /dev/hdb3 initrd = /boot/initrd optional # snip other = /dev/hda1 optional # automatically added by patch_lilo_conf label = windows Get it ? -- Regards Cliff