| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182 | <?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [  <!ENTITY % general-entities SYSTEM "../general.ent">  %general-entities;]><sect1 id="ch-system-devices"><title>Populating /dev</title><?dbhtml filename="devices.html"?><indexterm zone="ch-system-devices"><primary sortas="e-/dev/">/dev/*</primary></indexterm><sect2><title>Creating Initial Device Nodes</title><para>When the kernel boots the system, it requires the presence of a few devicenodes, in particular the <filename class="devicefile">console</filename> and<filename class="devicefile">null</filename> devices. Create these byrunning the following commands:</para><screen><userinput>mknod -m 600 /dev/console c 5 1mknod -m 666 /dev/null c 1 3</userinput></screen></sect2><sect2><title>Mounting ramfs and Populating /dev</title><para>The recommended method of populating the <filenameclass="directory">/dev</filename> directory with devices is to mount a virtualfilesystem (such as <systemitem class="filesystem">ramfs</systemitem> or<systemitem class="filesystem">tmpfs</systemitem>) on the <filenameclass="directory">/dev</filename> directory, and allow the devices to be createddynamically on that virtual filesystem as they are detected or accessed. This isgenerally done during the boot process. Since this new system has not beenbooted, it is necessary to do what the bootscripts would otherwise do bymounting <filename class="directory">/dev</filename>:</para><screen><userinput>mount -n -t ramfs none /dev</userinput></screen><para>The Udev package is what actually creates the devices in the <filenameclass="directory">/dev</filename> directory. Since it will not be installeduntil later on in the process, manually create the minimal set of device nodesneeded to complete the building of this system:</para><screen><userinput>mknod -m 622 /dev/console c 5 1mknod -m 666 /dev/null c 1 3mknod -m 666 /dev/zero c 1 5mknod -m 666 /dev/ptmx c 5 2mknod -m 666 /dev/tty c 5 0mknod -m 444 /dev/random c 1 8mknod -m 444 /dev/urandom c 1 9chown root:tty /dev/{console,ptmx,tty}</userinput></screen><!-- --><para>There are some symlinks and directories required by LFS that arenot created by Udev, so create those here:</para><screen><userinput>ln -s /proc/self/fd /dev/fdln -s /proc/self/fd/0 /dev/stdinln -s /proc/self/fd/1 /dev/stdoutln -s /proc/self/fd/2 /dev/stderrln -s /proc/kcore /dev/coremkdir /dev/ptsmkdir /dev/shm</userinput></screen><para>Finally, mount the proper virtual (kernel) file systems on thenewly-created directories:</para><screen><userinput>mount -t devpts -o gid=4,mode=620 none /dev/ptsmount -t tmpfs none /dev/shm</userinput></screen><para>The <command>mount</command> commands executed above may resultin the following warning message:</para><screen><computeroutput>can't open /etc/fstab: No such file or directory.</computeroutput></screen><para>This file—<filename>/etc/fstab</filename>—has notbeen created yet but is also not required for the file systems to beproperly mounted. As such, the warning can be safely ignored.</para></sect2></sect1>
 |