- Timestamp:
- 02/10/2004 10:06:21 PM (20 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- c91dd5b
- Parents:
- 418e6cc
- Location:
- chapter06
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/chapter06.xml
r418e6cc r5cd6caa 313 313 <para>The created groups aren't part of any standard -- they are some of the 314 314 groups that the <command>make_devices</command> script in the next section 315 uses. The LSB (<ulink url="http://www.linuxbase.org ">Linux Standard315 uses. The LSB (<ulink url="http://www.linuxbase.org/">Linux Standard 316 316 Base</ulink>) recommends only that, beside the group "root" with a GID of 0, a 317 317 group "bin" with a GID of 1 be present. All other group names and GIDs can -
chapter06/makedev.xml
r418e6cc r5cd6caa 28 28 29 29 <para>Device nodes are special files: things that can generate or receive data. 30 They usually correspond to physical pieces of hardware , and can be created by31 issuing commands of the form: <command>mknod -m mode name type major30 They usually correspond to physical pieces of hardware. Device nodes can be 31 created by issuing commands of the form: <command>mknod -m mode name type major 32 32 minor</command>. In such a command, <emphasis>mode</emphasis> is the usual 33 33 octal read/write/execute permissions triplet, and <emphasis>name</emphasis> is … … 35 35 device name is actually arbitrary, except that most programs rely on devices 36 36 such as <filename>/dev/null</filename> having their usual names. The remaining 37 three parameters tell the kernel what piece of hardware the device node37 three parameters tell the kernel what device the node 38 38 actually refers to. The <emphasis>type</emphasis> is a letter, either b or c, 39 39 indicating whether the device is accessed in blocks (such as a hard disk) or … … 45 45 kernel sources.</para> 46 46 47 <para>Note that the same major/minor combination areusually assigned to both a47 <para>Note that the same major/minor combination is usually assigned to both a 48 48 block and a character device. These are, however, completely unrelated devices 49 49 that cannot be interchanged. A device is identified by the type/major/minor … … 80 80 and ttyXX device nodes. To do this, open <filename>make_devices</filename> in 81 81 your editor, go to the section "Pseudo-TTY masters" and enable as many ptyXX 82 devices as you think you will need ( one for every active xterm, ssh connection,83 telnet connection, and so on). In the immediately following section "Pseudo-TTY 84 slaves", enable the corresponding ttyXX devices. When you are done, rerun 85 <command>./make_devices</command> from inside <filename>/dev</filename> to have 86 i t create the new devices.</para>82 devices as you think you will need (every xterm, ssh connection, telnet 83 connection, and the like, uses one of these pseudo terminals). In the 84 immediately following section "Pseudo-TTY slaves", enable the corresponding 85 ttyXX devices. When you are done, rerun <command>./make_devices</command> from 86 inside <filename>/dev</filename> to have it create the new devices.</para> 87 87 88 88 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.