| 1 | <sect2><title> </title><para> </para></sect2>
|
|---|
| 2 |
|
|---|
| 3 | <sect2>
|
|---|
| 4 | <title>Creating devices</title>
|
|---|
| 5 |
|
|---|
| 6 | <para>Note that unpacking the <filename>MAKEDEV-&makedev-version;.bz2</filename>
|
|---|
| 7 | file doesn't create a directory for you to <userinput>cd</userinput> into, as
|
|---|
| 8 | the file contains only a shell script.</para>
|
|---|
| 9 |
|
|---|
| 10 | <para>Install the <userinput>MAKEDEV</userinput> 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 arguments:</para>
|
|---|
| 21 |
|
|---|
| 22 | <itemizedlist>
|
|---|
| 23 | <listitem><para><userinput>-v</userinput>: This tells the script to run in
|
|---|
| 24 | verbose mode.</para></listitem>
|
|---|
| 25 |
|
|---|
| 26 | <listitem><para><userinput>generic-nopty</userinput>: This instructs
|
|---|
| 27 | <userinput>MAKEDEV</userinput> to create a generic selection of commonly used
|
|---|
| 28 | device special files, except for the ptyXX and ttyXX range of files. We don't
|
|---|
| 29 | need those files because we are going to use Unix98 PTYs via the
|
|---|
| 30 | <emphasis>devpts</emphasis> file system.</para></listitem>
|
|---|
| 31 | </itemizedlist>
|
|---|
| 32 |
|
|---|
| 33 | <para>If it turns out that some special device <filename>zzz</filename> that
|
|---|
| 34 | you need is missing, try running <userinput>./MAKEDEV -v zzz</userinput>.
|
|---|
| 35 | Alternatively, you may create devices via the <userinput>mknod</userinput>
|
|---|
| 36 | program. Please refer to its man and info pages if you need more
|
|---|
| 37 | information.</para>
|
|---|
| 38 |
|
|---|
| 39 | <para>Additionally, if you were unable to mount the devpts filesystem earlier in
|
|---|
| 40 | the "Mounting the proc and devpts file systems" section, now is the time to
|
|---|
| 41 | try the alternatives. If your kernel supports the devfs file system, run the
|
|---|
| 42 | following command to mount devfs:</para>
|
|---|
| 43 |
|
|---|
| 44 | <screen><userinput>mount -t devfs devfs /dev</userinput></screen>
|
|---|
| 45 |
|
|---|
| 46 | <para>This will mount the devfs file system over the top of the new static
|
|---|
| 47 | <filename>/dev</filename> structure. This poses no problems, as the device nodes
|
|---|
| 48 | created are still present, they are just hidden by the new devfs
|
|---|
| 49 | filesystem.</para>
|
|---|
| 50 |
|
|---|
| 51 | <para>If this still doesn't work, the only option left is to use the MAKEDEV
|
|---|
| 52 | script to create the ptyXX and ttyXX range of files that would otherwise not be
|
|---|
| 53 | needed. Ensure you are still in the <filename>/dev</filename> directory then run
|
|---|
| 54 | <userinput>./MAKEDEV -v pty</userinput>. The downside of this is, we are
|
|---|
| 55 | creating an extra 512 device special files which will not be needed when we
|
|---|
| 56 | finally boot into the finished LFS system.</para>
|
|---|
| 57 |
|
|---|
| 58 | </sect2>
|
|---|
| 59 |
|
|---|
