[e73e361] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[6732c094] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
[e73e361] | 4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
| 7 |
|
---|
| 8 | <sect1 id="postlfs-devices" xreflabel="About Devices">
|
---|
| 9 | <?dbhtml filename="devices.html"?>
|
---|
| 10 |
|
---|
| 11 | <sect1info>
|
---|
| 12 | <othername>$LastChangedBy$</othername>
|
---|
| 13 | <date>$Date$</date>
|
---|
| 14 | </sect1info>
|
---|
| 15 |
|
---|
| 16 | <title>About Devices</title>
|
---|
| 17 |
|
---|
| 18 | <indexterm zone="postlfs-devices">
|
---|
| 19 | <primary sortas="e-etc-udev-rules">/etc/udev/rules.d</primary>
|
---|
| 20 | </indexterm>
|
---|
| 21 |
|
---|
| 22 |
|
---|
| 23 | <para>Although most devices needed by packages in BLFS and beyond are set up
|
---|
| 24 | properly by <application>udev</application> using the default rules installed
|
---|
| 25 | by LFS in <filename class="directory">/etc/udev/rules.d</filename>, there are
|
---|
| 26 | cases where the rules must be modified or augmented.</para>
|
---|
| 27 |
|
---|
| 28 | <para condition="html" role="usernotes">User Notes:
|
---|
| 29 | <ulink url="&blfs-wiki;/aboutdevices"/></para>
|
---|
| 30 |
|
---|
| 31 | <sect2>
|
---|
| 32 | <title>Multiple Sound Cards</title>
|
---|
| 33 |
|
---|
[9f12e36] | 34 | <para>If there are multiple sound cards in a system, the "default"
|
---|
| 35 | sound card becomes random. The method to establish sound card order
|
---|
| 36 | depends on whether the drivers are modules or not. If the sound card
|
---|
[e73e361] | 37 | drivers are compiled into the kernel, control is via kernel command line
|
---|
[baf47952] | 38 | parameters in <filename>/boot/grub/menu.lst</filename>. For example,
|
---|
[9f12e36] | 39 | if a system has both an FM801 card and a SoundBlaster PCI card, the
|
---|
[e73e361] | 40 | following can be appended to the command line:</para>
|
---|
| 41 |
|
---|
| 42 | <screen><literal>snd-fm801.index=0 snd-ens1371.index=1</literal></screen>
|
---|
| 43 |
|
---|
| 44 | <para>If the sound card drivers are built as modules, the order can be
|
---|
| 45 | established in the <filename>/etc/modprobe.conf</filename> file
|
---|
| 46 | with:</para>
|
---|
| 47 |
|
---|
| 48 | <screen><literal>options snd-fm801 index=0
|
---|
| 49 | options snd-ens1371 index=1</literal></screen>
|
---|
| 50 |
|
---|
| 51 | </sect2>
|
---|
| 52 |
|
---|
[d20c871] | 53 | <sect2 id="usb-device-issues">
|
---|
| 54 | <title>USB Device Issues</title>
|
---|
| 55 |
|
---|
| 56 | <para>USB devices usually have two kinds of device nodes associated with
|
---|
| 57 | them.</para>
|
---|
| 58 |
|
---|
| 59 | <para>The first kind is created by device-specific drivers (e.g.,
|
---|
| 60 | usb_storage/sd_mod or usblp) in the kernel. For example, a USB mass storage
|
---|
| 61 | device would be /dev/sdb, and a USB printer would be /dev/usb/lp0. These
|
---|
| 62 | device nodes exist only when the device-specific driver is loaded.</para>
|
---|
| 63 |
|
---|
| 64 | <para>The second kind of device nodes (/dev/bus/usb/BBB/DDD, where BBB is
|
---|
| 65 | the bus number and DDD is the device number) is created even if the device
|
---|
| 66 | doesn't have a kernel driver. By using these "raw" USB device nodes, an
|
---|
| 67 | application can exchange arbitrary USB packets with the device, i.e.,
|
---|
| 68 | bypass the possibly-existing kernel driver.</para>
|
---|
| 69 |
|
---|
| 70 | <para>Access to raw USB device nodes is needed when a userspace program is
|
---|
| 71 | acting as a device driver. However, for the program to open the device
|
---|
| 72 | successfully, the permissions have to be set correctly. By default, due to
|
---|
| 73 | security concerns, all raw USB devices are owned by user root and group
|
---|
| 74 | usb, and have 0664 permissions (the read access is needed, e.g., for lsusb
|
---|
| 75 | to work and for programs to access USB hubs). Packages (such as SANE and
|
---|
| 76 | libgphoto2) containing userspace USB device drivers also ship udev rules
|
---|
| 77 | that change the permissions of the controlled raw USB devices. That is, rules
|
---|
[a41f643] | 78 | installed by SANE change permissions for known scanners, but not printers.
|
---|
[d20c871] | 79 | If a package maintainer forgot to write a rule for your device,
|
---|
[a41f643] | 80 | report a bug to both BLFS (if the package is there) and upstream, and
|
---|
[d40737d] | 81 | you will need to write your own rule.</para>
|
---|
[d20c871] | 82 |
|
---|
| 83 | <para>There is one situation when such fine-grained access control with
|
---|
| 84 | pre-generated udev rules doesn't work. Namely, PC emulators such as KVM,
|
---|
| 85 | QEMU and VirtualBox use raw USB device nodes to present arbitrary USB
|
---|
| 86 | devices to the guest operating system (note: patches are needed in order to
|
---|
| 87 | get this to work without the obsolete /proc/bus/usb mount point described
|
---|
| 88 | below). Obviously, maintainers of these packages cannot know which USB
|
---|
| 89 | devices are going to be connected to the guest operating system. You can
|
---|
| 90 | either write separate udev rules for all needed USB devices yourself, or
|
---|
[a41f643] | 91 | use the default catch-all "usb" group, members of which can send
|
---|
[d20c871] | 92 | arbitrary commands to all USB devices. </para>
|
---|
[a41f643] | 93 |
|
---|
[d20c871] | 94 | <para>Before Linux-2.6.15, raw USB device access was performed not with
|
---|
| 95 | /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD
|
---|
| 96 | pseudofiles. Some applications (e.g., VMware Workstation) still use only
|
---|
| 97 | this deprecated technique and can't use the new device nodes. For them to
|
---|
| 98 | work, use the "usb" group, but remember that members will have unrestricted
|
---|
| 99 | access to all USB devices. To create the fstab entry for the obsolete
|
---|
| 100 | usbfs filesystem:</para>
|
---|
| 101 |
|
---|
| 102 | <screen><literal>usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0</literal></screen>
|
---|
| 103 |
|
---|
| 104 | <note><para>Adding users to the "usb" group is inherently insecure, as they
|
---|
| 105 | can bypass access restrictions imposed through the driver-specific USB
|
---|
| 106 | device nodes. For instance, they can read sensitive data from USB hard drives
|
---|
[a41f643] | 107 | without being in the "disk" group. Avoid adding users to this group, if
|
---|
[d20c871] | 108 | you can.</para></note>
|
---|
| 109 |
|
---|
| 110 | </sect2>
|
---|
| 111 |
|
---|
[e73e361] | 112 | <sect2>
|
---|
[826bacb5] | 113 | <title>Udev Device Attributes</title>
|
---|
[9f12e36] | 114 |
|
---|
[e73e361] | 115 | <para>Fine-tuning of device attributes such as group name and permissions
|
---|
| 116 | is possible by creating extra <application>udev</application> rules,
|
---|
[5e9adc53] | 117 | matching on something like this. The vendor and product can be found by
|
---|
| 118 | searching the <filename class='directory'>/sys/devices</filename> directory
|
---|
| 119 | entries or using <command>udevadm info</command> after the device has been
|
---|
| 120 | attached. See the documentation in the current
|
---|
| 121 | <application>udev</application> directory of
|
---|
[e73e361] | 122 | <filename class='directory'>/usr/share/doc</filename> for details.</para>
|
---|
[9f12e36] | 123 |
|
---|
[fdf8b6d0] | 124 | <screen><literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \
|
---|
| 125 | GROUP:="scanner", MODE:="0660"</literal></screen>
|
---|
| 126 |
|
---|
| 127 | <note><para>The above line is used for descriptive purposes only. The
|
---|
| 128 | scanner <application>udev</application> rules are put into place when
|
---|
| 129 | installing <xref linkend='sane'/>.</para></note>
|
---|
[9f12e36] | 130 |
|
---|
[e73e361] | 131 | </sect2>
|
---|
| 132 |
|
---|
| 133 | <!--
|
---|
| 134 | <sect2>
|
---|
| 135 | <title>Multiple Network Interfaces</title>
|
---|
| 136 |
|
---|
| 137 |
|
---|
| 138 | </sect2>
|
---|
| 139 | -->
|
---|
| 140 |
|
---|
| 141 | <sect2>
|
---|
| 142 | <title>Devices for Servers</title>
|
---|
| 143 |
|
---|
| 144 | <para>In some cases, it makes sense to disable
|
---|
| 145 | <application>udev</application> completely and create static devices.
|
---|
| 146 | Servers are one example of this situation. Does a server need the
|
---|
| 147 | capability of handling dynamic devices? Only the system administrator can
|
---|
| 148 | answer that question, but in many cases the answer will be no.</para>
|
---|
| 149 |
|
---|
| 150 | <para>If dynamic devices are not desired, then static devices must be
|
---|
| 151 | created on the system. In the default configuration, the
|
---|
| 152 | <filename>/etc/rc.d/rcsysinit.d/S10udev</filename> boot script mounts a
|
---|
| 153 | <systemitem class="filesystem">tmpfs</systemitem> partition over the
|
---|
| 154 | <filename class="directory">/dev</filename> directory. This problem can be
|
---|
| 155 | overcome by mounting the root partition temporarily:</para>
|
---|
| 156 |
|
---|
| 157 | <warning><para>If the instructions below are not followed carefully, your
|
---|
| 158 | system could become unbootable.</para></warning>
|
---|
[9f12e36] | 159 |
|
---|
[e73e361] | 160 |
|
---|
| 161 | <screen><userinput>mount --bind / /mnt
|
---|
| 162 | cp -a /dev/* /mnt/dev
|
---|
| 163 | rm /etc/rc.d/rcsysinit.d/{S10udev,S45udev_retry}
|
---|
| 164 | umount /mnt</userinput></screen>
|
---|
| 165 |
|
---|
| 166 | <para>At this point, the system will use static devices upon the next
|
---|
| 167 | reboot. Create any desired additional devices using
|
---|
| 168 | <command>mknod</command>.</para>
|
---|
[9f12e36] | 169 |
|
---|
[e73e361] | 170 | <para>If you want to restore the dynamic devices, recreate the
|
---|
| 171 | <filename>/etc/rc.d/rcsysinit.d/{S10udev,S45udev_retry}</filename> symbolic
|
---|
| 172 | links and reboot again. Static devices do not need to be removed (console
|
---|
| 173 | and null are always needed) because they are covered by the <systemitem
|
---|
| 174 | class="filesystem">tmpfs</systemitem> partition. Disk usage for devices is
|
---|
| 175 | negligible (about 20–30 bytes per entry.)</para>
|
---|
| 176 |
|
---|
| 177 | </sect2>
|
---|
| 178 |
|
---|
| 179 | </sect1>
|
---|