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" [
|
---|
3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
4 | %general-entities;
|
---|
5 | ]>
|
---|
6 | <sect1 id="ch-system-devices">
|
---|
7 | <title>Populating /dev</title>
|
---|
8 | <?dbhtml filename="devices.html"?>
|
---|
9 |
|
---|
10 | <indexterm zone="ch-system-devices"><primary sortas="e-/dev/">/dev/*</primary></indexterm>
|
---|
11 |
|
---|
12 | <sect2>
|
---|
13 | <title>Creating Initial Device Nodes</title>
|
---|
14 |
|
---|
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. Create these by
|
---|
18 | running the following commands:</para>
|
---|
19 |
|
---|
20 | <screen><userinput>mknod -m 600 /dev/console c 5 1
|
---|
21 | mknod -m 666 /dev/null c 1 3</userinput></screen>
|
---|
22 | </sect2>
|
---|
23 |
|
---|
24 | <sect2>
|
---|
25 | <title>Mounting tmpfs and Populating /dev</title>
|
---|
26 |
|
---|
27 | <para>The recommended method of populating the <filename
|
---|
28 | class="directory">/dev</filename> directory with devices is to mount a virtual
|
---|
29 | filesystem (such as <systemitem class="filesystem">tmpfs</systemitem>) on the
|
---|
30 | <filename class="directory">/dev</filename> directory, and allow the devices to
|
---|
31 | be created dynamically on that virtual filesystem as they are detected or
|
---|
32 | accessed. This is generally done during the boot process. Since this new system
|
---|
33 | has not been booted, it is necessary to do what the LFS-Bootscripts package would
|
---|
34 | otherwise do by mounting <filename class="directory">/dev</filename>:</para>
|
---|
35 |
|
---|
36 | <screen><userinput>mount -n -t tmpfs none /dev</userinput></screen>
|
---|
37 |
|
---|
38 | <para>The Udev package is what actually creates the devices in the <filename
|
---|
39 | class="directory">/dev</filename> directory. Since it will not be installed
|
---|
40 | until later on in the process, manually create the minimal set of device nodes
|
---|
41 | needed to complete the building of this system:</para>
|
---|
42 |
|
---|
43 | <screen><userinput>mknod -m 622 /dev/console c 5 1
|
---|
44 | mknod -m 666 /dev/null c 1 3
|
---|
45 | mknod -m 666 /dev/zero c 1 5
|
---|
46 | mknod -m 666 /dev/ptmx c 5 2
|
---|
47 | mknod -m 666 /dev/tty c 5 0
|
---|
48 | mknod -m 444 /dev/random c 1 8
|
---|
49 | mknod -m 444 /dev/urandom c 1 9
|
---|
50 | chown root:tty /dev/{console,ptmx,tty}</userinput></screen>
|
---|
51 | <!-- -->
|
---|
52 |
|
---|
53 | <para>There are some symlinks and directories required by LFS that are created
|
---|
54 | during system startup by the LFS-Bootscripts package. Since this is a chroot
|
---|
55 | environment and not a booted environment, those symlinks and directories need to
|
---|
56 | be created here:</para>
|
---|
57 |
|
---|
58 | <screen><userinput>ln -s /proc/self/fd /dev/fd
|
---|
59 | ln -s /proc/self/fd/0 /dev/stdin
|
---|
60 | ln -s /proc/self/fd/1 /dev/stdout
|
---|
61 | ln -s /proc/self/fd/2 /dev/stderr
|
---|
62 | ln -s /proc/kcore /dev/core
|
---|
63 | mkdir /dev/pts
|
---|
64 | mkdir /dev/shm</userinput></screen>
|
---|
65 |
|
---|
66 | <para>Finally, mount the proper virtual (kernel) file systems on the
|
---|
67 | newly-created directories:</para>
|
---|
68 |
|
---|
69 | <screen><userinput>mount -t devpts -o gid=4,mode=620 none /dev/pts
|
---|
70 | mount -t tmpfs none /dev/shm</userinput></screen>
|
---|
71 |
|
---|
72 | <para>The <command>mount</command> commands executed above may result
|
---|
73 | in the following warning message:</para>
|
---|
74 |
|
---|
75 | <screen><computeroutput>can't open /etc/fstab: No such file or directory.</computeroutput></screen>
|
---|
76 |
|
---|
77 | <para>This file—<filename>/etc/fstab</filename>—has not
|
---|
78 | been created yet but is also not required for the file systems to be
|
---|
79 | properly mounted. As such, the warning can be safely ignored.</para>
|
---|
80 | </sect2>
|
---|
81 |
|
---|
82 | </sect1>
|
---|
83 |
|
---|