1 | <sect2><title> </title><para> </para></sect2>
|
---|
2 |
|
---|
3 | <sect2>
|
---|
4 | <title>Creating devices</title>
|
---|
5 |
|
---|
6 | <para>Please note that unpacking the MAKEDEV-&makedev-version;.bz2 file
|
---|
7 | doesn't create a directory for you to <userinput>cd</userinput> into, as
|
---|
8 | the file only contains a single shell script.</para>
|
---|
9 |
|
---|
10 | <para>Install the MAKEDEV script:</para>
|
---|
11 |
|
---|
12 | <para><screen><userinput>bzcat MAKEDEV-&makedev-version;.bz2 > /dev/MAKEDEV
|
---|
13 | chmod 754 /dev/MAKEDEV</userinput></screen></para>
|
---|
14 |
|
---|
15 | <para>Run the script to create the device files:</para>
|
---|
16 |
|
---|
17 | <para><screen><userinput>cd /dev
|
---|
18 | ./MAKEDEV -v generic-nopty</userinput></screen></para>
|
---|
19 |
|
---|
20 | <para>The meaning of the option:</para>
|
---|
21 |
|
---|
22 | <itemizedlist>
|
---|
23 | <listitem><para><userinput>-v generic-nopty</userinput>: The
|
---|
24 | <userinput>-v</userinput> parameter tells the MAKEDEV script to run in verbose
|
---|
25 | mode. The <userinput>generic-nopty</userinput> parameter instructs MAKEDEV to
|
---|
26 | create a generic selection of commonly used device special files, except for the
|
---|
27 | ptyXX and ttyXX range of files. We don't need those files because we are going
|
---|
28 | to use Unix98 PTYs via the <emphasis>devpts</emphasis> file
|
---|
29 | system.</para></listitem>
|
---|
30 | </itemizedlist>
|
---|
31 |
|
---|
32 | <para>If a device you need is missing, try running
|
---|
33 | <userinput>./MAKEDEV -v <device></userinput>. Alternatively, you may
|
---|
34 | create devices via the <emphasis>mknod</emphasis> program. Please refer to
|
---|
35 | the man and info pages of <emphasis>mknod</emphasis> if you need more
|
---|
36 | information.</para>
|
---|
37 |
|
---|
38 | <para>Also, if earlier in Chapter 6 you were unable to mount the devpts
|
---|
39 | filesystem because your host uses devfs, we will now mount that devfs
|
---|
40 | system over top of this new static /dev structure. This poses no problems,
|
---|
41 | as the device nodes created are still present, they are just hidden by the
|
---|
42 | new devfs filesystem. Run the following command to mount devfs, if necessary:
|
---|
43 | </para>
|
---|
44 |
|
---|
45 | <para><screen><userinput>mount -t devfs devfs /dev</userinput></screen></para>
|
---|
46 |
|
---|
47 | </sect2>
|
---|
48 |
|
---|