| [bf8c11f] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?> | 
|---|
|  | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" | 
|---|
|  | 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ | 
|---|
|  | 4 | <!ENTITY % general-entities SYSTEM "../../general.ent"> | 
|---|
|  | 5 | %general-entities; | 
|---|
|  | 6 | ]> | 
|---|
|  | 7 |  | 
|---|
|  | 8 | <sect1 id="ch-chroot-kernfs"> | 
|---|
|  | 9 | <?dbhtml filename="kernfs.html"?> | 
|---|
|  | 10 |  | 
|---|
|  | 11 | <title>Mounting Virtual Kernel File Systems</title> | 
|---|
|  | 12 |  | 
|---|
| [0d80be2] | 13 | <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" | 
|---|
|  | 14 | href="../../boot/common/devices.xml" | 
|---|
|  | 15 | xpointer="xpointer(//*[@os='a'])"/> | 
|---|
| [bf8c11f] | 16 |  | 
|---|
|  | 17 | <para>Various file systems exported by the kernel are used to communicate | 
|---|
|  | 18 | to and from the kernel itself. These file systems are virtual in that no | 
|---|
|  | 19 | disk space is used for them. The content of the file systems resides in | 
|---|
|  | 20 | memory.</para> | 
|---|
|  | 21 |  | 
|---|
|  | 22 | <para>Begin by creating directories onto which the file systems will | 
|---|
|  | 23 | be mounted:</para> | 
|---|
|  | 24 |  | 
|---|
| [8545aa19] | 25 | <screen><userinput>mkdir -pv $LFS/{dev,proc,sys}</userinput></screen> | 
|---|
| [bf8c11f] | 26 |  | 
|---|
|  | 27 | <para>Now mount the file systems:</para> | 
|---|
|  | 28 |  | 
|---|
| [dd9906e] | 29 | <screen><userinput>mount -vt proc proc $LFS/proc | 
|---|
| [dca40f5] | 30 | mount -vt sysfs sysfs $LFS/sys</userinput></screen> | 
|---|
| [bf8c11f] | 31 |  | 
|---|
|  | 32 | <para>Remember that if for any reason you stop working on the LFS system | 
|---|
|  | 33 | and start again later, it is important to check that these file systems | 
|---|
|  | 34 | are mounted again before entering the chroot environment.</para> | 
|---|
|  | 35 |  | 
|---|
| [ed3238a] | 36 | <para>Two device nodes, /dev/console and /dev/null, are required to be | 
|---|
|  | 37 | present on the filesystem.  These are needed by the kernel even before | 
|---|
|  | 38 | starting Udev early in the boot process, so we create them here:</para> | 
|---|
| [bf8c11f] | 39 |  | 
|---|
| [ed3238a] | 40 | <screen><userinput>mknod -m 600 $LFS/dev/console c 5 1 | 
|---|
|  | 41 | mknod -m 666 $LFS/dev/null c 1 3</userinput></screen> | 
|---|
|  | 42 |  | 
|---|
|  | 43 | <para>Once the system is complete and booting, the rest of our device | 
|---|
|  | 44 | nodes are created by the Udev package.  Since this package is not | 
|---|
|  | 45 | available to us right now, we must take other steps to provide device | 
|---|
|  | 46 | nodes under on the LFS filesystem.  We will use the <quote>bind</quote> | 
|---|
|  | 47 | option in the mount command to make our host system's /dev structure | 
|---|
|  | 48 | appear in the new LFS filesystem:</para> | 
|---|
|  | 49 |  | 
|---|
|  | 50 | <screen><userinput>/tools/bin/mount -o bind /dev $LFS/dev</userinput></screen> | 
|---|
|  | 51 |  | 
|---|
|  | 52 | <para>Additional file systems will soon be mounted from within the chroot | 
|---|
|  | 53 | environment. To keep the host up to date, perform a <quote>fake mount</quote> | 
|---|
|  | 54 | for each of these now:</para> | 
|---|
|  | 55 |  | 
|---|
|  | 56 | <screen><userinput>mount -f -vt tmpfs tmpfs $LFS/dev/shm | 
|---|
| [dd9906e] | 57 | mount -f -vt devpts -o gid=10,mode=620 devpts $LFS/dev/pts</userinput></screen> | 
|---|
| [bf8c11f] | 58 |  | 
|---|
|  | 59 | </sect1> | 
|---|