- Timestamp:
- Jun 4, 2014, 9:10:24 AM (10 years ago)
- Branches:
- clfs-3.0.0-systemd, master, systemd
- Children:
- a7a05cf
- Parents:
- b766e6c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/chroot/common/kernfs.xml
rb766e6c r1d396c4 38 38 are mounted again before entering the chroot environment.</para> 39 39 40 <para>Two device nodes, /dev/console and /dev/null, are required to be 40 <para>Two device nodes, <filename class="devicefile">/dev/console</filename> 41 and <filename class="devicefile">/dev/null</filename>, are required to be 41 42 present on the filesystem. These are needed by the kernel even before 42 starting Eudev early in the boot process, so we create them here:</para>43 starting Udev early in the boot process, so we create them here:</para> 43 44 44 45 <screen><userinput>mknod -m 600 ${CLFS}/dev/console c 5 1 … … 46 47 47 48 <para>Once the system is complete and booting, the rest of our device 48 nodes are created by Udev, part of Systemd. Since this package is not 49 available to us right now, we must take other steps to provide device 50 nodes under on the CLFS filesystem. We will use the <quote>bind</quote> 51 option in the mount command to make our host system's /dev structure 52 appear in the new CLFS filesystem:</para> 49 nodes will be created by the kernel's 50 <systemitem class="filesystem">devtmpfs</systemitem> file system. For now 51 though, we will just use the <quote>bind</quote> option in the mount command 52 to make our host system's /dev structure appear in the new CLFS filesystem:</para> 53 53 54 54 <screen><userinput>mount -v -o bind /dev ${CLFS}/dev</userinput></screen>
Note:
See TracChangeset
for help on using the changeset viewer.