| 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 | <screen><userinput>bzcat MAKEDEV-&makedev-version;.bz2 > /dev/MAKEDEV
|
|---|
| 13 | chmod 754 /dev/MAKEDEV</userinput></screen>
|
|---|
| 14 |
|
|---|
| 15 | <para>Run the script to create the device files:</para>
|
|---|
| 16 |
|
|---|
| 17 | <screen><userinput>cd /dev
|
|---|
| 18 | ./MAKEDEV -v generic-nopty</userinput></screen>
|
|---|
| 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>Additionally, if you were unable to mount the devpts filesystem earlier in
|
|---|
| 39 | the "Mounting the proc and devpts file systems" section, now is the time to
|
|---|
| 40 | try the alternatives. If your kernel supports the devfs file system, run the
|
|---|
| 41 | following command to mount devfs:</para>
|
|---|
| 42 |
|
|---|
| 43 | <screen><userinput>mount -t devfs devfs /dev</userinput></screen>
|
|---|
| 44 |
|
|---|
| 45 | <para>This will mount the devfs file system over the top of the new static
|
|---|
| 46 | <filename>/dev</filename> structure. This poses no problems, as the device nodes
|
|---|
| 47 | created are still present, they are just hidden by the new devfs
|
|---|
| 48 | filesystem.</para>
|
|---|
| 49 |
|
|---|
| 50 | <para>If this still doesn't work, the only option left is to use the MAKEDEV
|
|---|
| 51 | script to create the ptyXX and ttyXX range of files that would otherwise not be
|
|---|
| 52 | needed. Ensure you are still in the <filename>/dev</filename> directory then run
|
|---|
| 53 | <userinput>./MAKEDEV -v pty</userinput>. The downside of this is, we are
|
|---|
| 54 | creating an extra 512 device special files which will not be needed when we
|
|---|
| 55 | finally boot into the finished LFS system.</para>
|
|---|
| 56 |
|
|---|
| 57 | </sect2>
|
|---|
| 58 |
|
|---|
