Changeset fa994c9 for chapter06/devices.xml
- Timestamp:
- 02/03/2006 09:04:48 PM (19 years ago)
- Children:
- 73c180db
- Parents:
- e6ab4b5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/devices.xml
re6ab4b5 rfa994c9 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ 2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" 3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [ 3 4 <!ENTITY % general-entities SYSTEM "../general.ent"> 4 5 %general-entities; 5 6 ]> 7 6 8 <sect1 id="ch-system-devices"> 7 <title>Populating /dev</title> 8 <?dbhtml filename="devices.html"?> 9 <?dbhtml filename="devices.html"?> 9 10 10 <indexterm zone="ch-system-devices"><primary sortas="e-/dev/">/dev/*</primary></indexterm>11 <title>Populating /dev</title> 11 12 12 <sect2> 13 <title>Creating Initial Device Nodes</title> 13 <indexterm zone="ch-system-devices"> 14 <primary sortas="e-/dev/">/dev/*</primary> 15 </indexterm> 14 16 15 <para>When the kernel boots the system, it requires the presence of a few device 16 nodes, in particular the <filename class="devicefile">console</filename> and 17 <filename class="devicefile">null</filename> devices. The device nodes will 18 be created on the hard disk so that they are available before 19 <command>udev</command> has been started, and additionally when Linux is started 20 in single user mode (hence the restrictive permissions on 21 <filename class="devicefile">console</filename>). Create the devices by running 22 the following commands:</para> 17 <sect2> 18 <title>Creating Initial Device Nodes</title> 19 20 <para>When the kernel boots the system, it requires the presence of a few 21 device nodes, in particular the <filename class="devicefile">console</filename> 22 and <filename class="devicefile">null</filename> devices. The device nodes 23 will be created on the hard disk so that they are available before 24 <command>udev</command> has been started, and additionally when Linux is 25 started in single user mode (hence the restrictive permissions on 26 <filename class="devicefile">console</filename>). Create the devices by 27 running the following commands:</para> 23 28 24 29 <screen><userinput>mknod -m 600 /dev/console c 5 1 25 30 mknod -m 666 /dev/null c 1 3</userinput></screen> 26 </sect2>27 31 28 <sect2> 29 <title>Mounting tmpfs and Populating /dev</title> 32 </sect2> 30 33 31 <para>The recommended method of populating the <filename 32 class="directory">/dev</filename> directory with devices is to mount a virtual 33 filesystem (such as <systemitem class="filesystem">tmpfs</systemitem>) on the 34 <filename class="directory">/dev</filename> directory, and allow the devices to 35 be created dynamically on that virtual filesystem as they are detected or 36 accessed. This is generally done during the boot process. Since this new system 37 has not been booted, it is necessary to do what the LFS-Bootscripts package would 38 otherwise do by mounting <filename class="directory">/dev</filename>:</para> 34 <sect2> 35 <title>Mounting tmpfs and Populating /dev</title> 36 37 <para>The recommended method of populating the <filename 38 class="directory">/dev</filename> directory with devices is to mount a 39 virtual filesystem (such as <systemitem class="filesystem">tmpfs</systemitem>) 40 on the <filename class="directory">/dev</filename> directory, and allow the 41 devices to be created dynamically on that virtual filesystem as they are 42 detected or accessed. This is generally done during the boot process. Since 43 this new system has not been booted, it is necessary to do what the 44 LFS-Bootscripts package would otherwise do by mounting <filename 45 class="directory">/dev</filename>:</para> 39 46 40 47 <screen><userinput>mount -nvt tmpfs none /dev</userinput></screen> 41 48 42 <para>The Udev package is what actually creates the devices in the <filename43 class="directory">/dev</filename> directory. Since it will not be installed44 until later on in the process, manually create the minimal set of device nodes45 needed to complete the building of this system:</para>49 <para>The Udev package is what actually creates the devices in the <filename 50 class="directory">/dev</filename> directory. Since it will not be installed 51 until later on in the process, manually create the minimal set of device nodes 52 needed to complete the building of this system:</para> 46 53 47 54 <screen><userinput>mknod -m 622 /dev/console c 5 1 … … 54 61 chown -v root:tty /dev/{console,ptmx,tty}</userinput></screen> 55 62 56 <para>There are some symlinks and directories required by LFS that are created 57 during system startup by the LFS-Bootscripts package. Since this is a chroot 58 environment and not a booted environment, those symlinks and directories need to 59 be created here:</para>63 <para>There are some symlinks and directories required by LFS that are 64 created during system startup by the LFS-Bootscripts package. Since this 65 is a chroot environment and not a booted environment, those symlinks and 66 directories need to be created here:</para> 60 67 61 68 <screen><userinput>ln -sv /proc/self/fd /dev/fd … … 67 74 mkdir -v /dev/shm</userinput></screen> 68 75 69 <para>Finally, mount the proper virtual (kernel) file systems on the70 newly-created directories:</para>76 <para>Finally, mount the proper virtual (kernel) file systems on the 77 newly-created directories:</para> 71 78 72 79 <screen><userinput>mount -vt devpts -o gid=4,mode=620 none /dev/pts 73 80 mount -vt tmpfs none /dev/shm</userinput></screen> 74 81 75 <para>The <command>mount</command> commands executed above may result76 in the following warning message:</para>82 <para>The <command>mount</command> commands executed above may result 83 in the following warning message:</para> 77 84 78 85 <screen><computeroutput>can't open /etc/fstab: No such file or directory.</computeroutput></screen> 79 86 80 <para>This file—<filename>/etc/fstab</filename>—has not 81 been created yet but is also not required for the file systems to be 82 properly mounted. As such, the warning can be safely ignored.</para> 83 </sect2> 87 <para>This file—<filename>/etc/fstab</filename>—has not 88 been created yet but is also not required for the file systems to be 89 properly mounted. As such, the warning can be safely ignored.</para> 90 91 </sect2> 84 92 85 93 </sect1> 86
Note:
See TracChangeset
for help on using the changeset viewer.