Various file systems exported by the kernel are used to communicate to and from the kernel itself. These file systems are virtual in that no disk space is used for them. The content of the file systems resides in memory.
Begin by creating directories onto which the file systems will be mounted:
mkdir -v $LFS/{dev,proc,sys}
When the kernel boots the system, it requires the presence of a few
device nodes, in particular the console and null
devices. The device nodes must be created on the hard disk so that
they are available before udevd has been started, and
additionally when Linux is started with init=/bin/bash. Create the devices by
running the following commands:
mknod -m 600 $LFS/dev/console c 5 1 mknod -m 666 $LFS/dev/null c 1 3
The recommended method of populating the /dev directory with devices is to mount a virtual
filesystem (such as tmpfs) on the
/dev directory, and allow the devices
to be created dynamically on that virtual filesystem as they are
detected or accessed. Device creation is generally done during the
boot process by Udev. Since this new system does not yet have Udev
and has not yet been booted, it is necessary to mount and populate
/dev manually. This is accomplished
by bind mounting the host system's /dev directory. A bind mount is a special type of
mount that allows you to create a mirror of a directory or mount
point to some other location. Use the following command to achieve
this:
mount -v --bind /dev $LFS/dev
Now mount the remaining virtual kernel filesystems:
mount -vt devpts devpts $LFS/dev/pts mount -vt proc proc $LFS/proc mount -vt sysfs sysfs $LFS/sys
In some host systems, /dev/shm is a
symbolic link to /run/shm. Inside a
chroot environment, this temporary file system needs to be mounted
separate from the host file system:
if [ -h $LFS/dev/shm ]; then link=$(readlink $LFS/dev/shm) mkdir -p $LFS/$link mount -vt tmpfs shm $LFS/$link unset link else mount -vt tmpfs shm $LFS/dev/shm fi