I just finished building LFS 6.3 and everything is well. It starts up
fine if all directories are on one parition. However, I plan to use
several partitions for some directories due to security reasons. Some
time ago, I tried the following scheme with LFS 6.1, and it worked fine:

 /dev/hda1      /boot
 /dev/hda6      /{etc,bin,sbin,lib,dev,opt,srv,root,media,mnt}
 /dev/hda7      /usr
 /dev/hda8      /home
 /dev/hda9      /var
 /dev/hda10     /var/mail
 /dev/hda11     /tmp

Unfortunately, as soon as /usr is in a separate partition, the LFS 6.3
bootscripts halt the system with the following error:

 Setting the console log level to 7... [  OK  ]
 /etc/rc.d/rcsysinit.d/S05modules: line 27: egrep: command not found
 Populating /dev with device nodes...
 /etc/rc.d/rcsysinit.d/S10udev: line 21: grep: command not found [ FAIL
]
 FAILURE:
 Unable to create devices without a SysFS filesystem

The /etc/fstab, of course, reflects the structure above (works for LFS
6.1 but fails for LFS 6.3):

/dev/hda6       /               ext3            defaults
1       1
/dev/hda2       swap            swap            pri=1
0       0
/dev/hda1       /boot           ext3            defaults
1       1
/dev/hda7       /usr            ext3            defaults
1       1
/dev/hda8       /home           ext3            defaults
1       1
/dev/hda9       /var            ext3            defaults
1       1
/dev/hda10      /var/mail       ext3            defaults
1       1
/dev/hda11      /tmp            ext3            defaults
1       1
proc            /proc           proc            defaults
0       0
sysfs           /sys            sysfs           defaults
0       0
devpts  /dev/pts        devpts  gid=4,mode=620  0       0
shm             /dev/shm        etmpfs  defaults                0
0

Any ideas? Thanks for your help!

p.s. How can I reply to an answer without starting a new thread?


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to