1
0

udev.po 30 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554
  1. msgid ""
  2. msgstr ""
  3. "X-Pootle-Revision: 9999999\n"
  4. "X-Pootle-Path: /zh_CN/lfs/chapter09/udev.po\n"
  5. "Project-Id-Version: PACKAGE VERSION\n"
  6. "POT-Creation-Date: 2020-08-08 19:28+0800\n"
  7. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
  8. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
  9. "Language-Team: LANGUAGE <LL@li.org>\n"
  10. "Language: zh_CN\n"
  11. "MIME-Version: 1.0\n"
  12. "Content-Type: text/plain; charset=UTF-8\n"
  13. "Content-Transfer-Encoding: 8bit\n"
  14. "X-Generator: Translate Toolkit 2.2.5\n"
  15. #. type: Content of: <sect1><title>
  16. msgid "Overview of Device and Module Handling"
  17. msgstr "设备和模块管理概述"
  18. #. type: Content of: <sect1><indexterm><primary>
  19. msgid "Udev"
  20. msgstr "Udev"
  21. #. type: Content of: <sect1><indexterm><secondary>
  22. msgid "usage"
  23. msgstr "用法"
  24. #. type: Content of: <sect1><para>
  25. msgid ""
  26. "In <xref linkend=\"chapter-building-system\"/>, we installed the udev "
  27. "package when <phrase revision=\"sysv\">eudev</phrase> <phrase revision="
  28. "\"systemd\">systemd</phrase> was built. Before we go into the details "
  29. "regarding how this works, a brief history of previous methods of handling "
  30. "devices is in order."
  31. msgstr ""
  32. "在<xref linkend=\"chapter-building-system\"/>中,我们在构建 <phrase revision="
  33. "\"sysv\">eudev</phrase> <phrase revision=\"systemd\">systemd</phrase> 时安装"
  34. "了 Udev 软件包。在我们详细讨论它的工作原理之前,首先按时间顺序简要介绍历史上"
  35. "曾经使用过的设备管理方式。"
  36. #. type: Content of: <sect1><para>
  37. msgid ""
  38. "Linux systems in general traditionally used a static device creation method, "
  39. "whereby a great many device nodes were created under <filename class="
  40. "\"directory\">/dev</filename> (sometimes literally thousands of nodes), "
  41. "regardless of whether the corresponding hardware devices actually existed. "
  42. "This was typically done via a <command>MAKEDEV</command> script, which "
  43. "contains a number of calls to the <command>mknod</command> program with the "
  44. "relevant major and minor device numbers for every possible device that might "
  45. "exist in the world."
  46. msgstr ""
  47. "传统的 Linux 系统通常使用静态地创建设备,即在 <filename class=\"directory\">/"
  48. "dev</filename> 下创建大量设备节点 (有时有数千个节点),无论对应的硬件设备是否"
  49. "真的存在。一般通过 <command>MAKEDEV</command> 脚本完成这一工作,它包含以相关"
  50. "的主设备号和次设备号,为世界上可能存在的每个设备建立节点的大量 "
  51. "<command>mknod</command> 命令。"
  52. #. type: Content of: <sect1><para>
  53. msgid ""
  54. "Using the udev method, only those devices which are detected by the kernel "
  55. "get device nodes created for them. Because these device nodes will be "
  56. "created each time the system boots, they will be stored on a <systemitem "
  57. "class=\"filesystem\">devtmpfs</systemitem> file system (a virtual file "
  58. "system that resides entirely in system memory). Device nodes do not require "
  59. "much space, so the memory that is used is negligible."
  60. msgstr ""
  61. "使用 Udev,则只有那些被内核检测到的设备才会获得为它们创建的设备节点。由于这些"
  62. "设备节点在每次引导系统时都会重新创建,它们被储存在 <systemitem class="
  63. "\"filesystem\">devtmpfs</systemitem> 文件系统中 (一个虚拟文件系统,完全驻留在"
  64. "系统内存)。设备节点不需要太多空间,它们使用的系统内存可以忽略不计。"
  65. #. type: Content of: <sect1><sect2><title>
  66. msgid "History"
  67. msgstr "历史"
  68. #. type: Content of: <sect1><sect2><para>
  69. msgid ""
  70. "In February 2000, a new filesystem called <systemitem class=\"filesystem"
  71. "\">devfs</systemitem> was merged into the 2.3.46 kernel and was made "
  72. "available during the 2.4 series of stable kernels. Although it was present "
  73. "in the kernel source itself, this method of creating devices dynamically "
  74. "never received overwhelming support from the core kernel developers."
  75. msgstr ""
  76. "在 2000 年 2 月,一个称为 <systemitem class=\"filesystem\">devfs</"
  77. "systemitem> 的新文件系统被合并到 2.3.46 版内核中,并在 2.4 系列稳定内核中可"
  78. "用。尽管它本身曾经存在于内核源代码中,但这种设备节点动态创建方法从未得到内核"
  79. "核心开发者的大力支持。"
  80. #. type: Content of: <sect1><sect2><para>
  81. msgid ""
  82. "The main problem with the approach adopted by <systemitem class=\"filesystem"
  83. "\">devfs</systemitem> was the way it handled device detection, creation, and "
  84. "naming. The latter issue, that of device node naming, was perhaps the most "
  85. "critical. It is generally accepted that if device names are allowed to be "
  86. "configurable, then the device naming policy should be up to a system "
  87. "administrator, not imposed on them by any particular developer(s). The "
  88. "<systemitem class=\"filesystem\">devfs</systemitem> file system also "
  89. "suffered from race conditions that were inherent in its design and could not "
  90. "be fixed without a substantial revision to the kernel. It was marked as "
  91. "deprecated for a long period &ndash; due to a lack of maintenance &ndash; "
  92. "and was finally removed from the kernel in June, 2006."
  93. msgstr ""
  94. "<systemitem class=\"filesystem\">devfs</systemitem> 实现机制的主要问题是它处"
  95. "理设备的检测、创建和命名的方式,其中最致命的或许最后一项,即设备节点命名方"
  96. "式。通常认为,如果设备名称是可配置的,那么设备命名策略应该由系统管理员,而不"
  97. "是某个 (某些)特定开发者决定。<systemitem class=\"filesystem\">devfs</"
  98. "systemitem> 还受到其设计中固有的竞争条件的严重影响,在不对内核进行大量修改的"
  99. "前提下无法修复这一问题。由于缺乏维护,它早已被标记为过时特性,最终在 2006 年 "
  100. "6 月被从内核中移除。"
  101. #. type: Content of: <sect1><sect2><para>
  102. msgid ""
  103. "With the development of the unstable 2.5 kernel tree, later released as the "
  104. "2.6 series of stable kernels, a new virtual filesystem called <systemitem "
  105. "class=\"filesystem\">sysfs</systemitem> came to be. The job of <systemitem "
  106. "class=\"filesystem\">sysfs</systemitem> is to export a view of the system's "
  107. "hardware configuration to userspace processes. With this userspace-visible "
  108. "representation, the possibility of developing a userspace replacement for "
  109. "<systemitem class=\"filesystem\">devfs</systemitem> became much more "
  110. "realistic."
  111. msgstr ""
  112. "在不稳定的 2.5 系列内核开发过程中,加入了一个新的虚拟文件系统,称为 "
  113. "<systemitem class=\"filesystem\">sysfs</systemitem>,并在 2.6 系列稳定内核中"
  114. "发布。<systemitem class=\"filesystem\">sysfs</systemitem> 的工作是将系统硬件"
  115. "配置信息导出给用户空间进程,有了这个用户空间可见的配置描述,就可能开发一种 "
  116. "<systemitem class=\"filesystem\">devfs</systemitem> 的用户空间替代品。"
  117. #. type: Content of: <sect1><sect2><title>
  118. msgid "Udev Implementation"
  119. msgstr "Udev 实现"
  120. #. type: Content of: <sect1><sect2><sect3><title>
  121. msgid "Sysfs"
  122. msgstr "Sysfs"
  123. #. type: Content of: <sect1><sect2><sect3><para>
  124. msgid ""
  125. "The <systemitem class=\"filesystem\">sysfs</systemitem> filesystem was "
  126. "mentioned briefly above. One may wonder how <systemitem class=\"filesystem"
  127. "\">sysfs</systemitem> knows about the devices present on a system and what "
  128. "device numbers should be used for them. Drivers that have been compiled into "
  129. "the kernel directly register their objects with a <systemitem class="
  130. "\"filesystem\">sysfs</systemitem> (devtmpfs internally) as they are "
  131. "detected by the kernel. For drivers compiled as modules, this registration "
  132. "will happen when the module is loaded. Once the <systemitem class="
  133. "\"filesystem\">sysfs</systemitem> filesystem is mounted (on /sys), data "
  134. "which the drivers register with <systemitem class=\"filesystem\">sysfs</"
  135. "systemitem> are available to userspace processes and to udevd for processing "
  136. "(including modifications to device nodes)."
  137. msgstr ""
  138. "前面已经简要提到了 <systemitem class=\"filesystem\">sysfs</systemitem> 文件系"
  139. "统。有些读者可能好奇,<systemitem class=\"filesystem\">sysfs</systemitem> 是"
  140. "如何知道系统中存在哪些设备,以及应该为它们使用什么设备号的。答案是,那些编译"
  141. "到内核中的驱动程序在它们的对象被内核检测到时,直接将它们注册到 <systemitem "
  142. "class=\"filesystem\">sysfs</systemitem> (内部的 devtmpfs)。对于那些被编译为"
  143. "模块的驱动程序,注册过程在模块加载时进行。只要 <systemitem class=\"filesystem"
  144. "\">sysfs</systemitem> 文件系统被挂载好 (位于 /sys),用户空间程序即可使用驱动"
  145. "程序注册在 <systemitem class=\"filesystem\">sysfs</systemitem> 中的数据,"
  146. "Udev 就能够使用这些数据对设备进行处理 (包括修改设备节点)。"
  147. #. type: Content of: <sect1><sect2><sect3><title>
  148. msgid "Device Node Creation"
  149. msgstr "设备节点的创建"
  150. #. type: Content of: <sect1><sect2><sect3><para>
  151. msgid ""
  152. "Device files are created by the kernel by the <systemitem class=\"filesystem"
  153. "\">devtmpfs</systemitem> filesystem. Any driver that wishes to register a "
  154. "device node will go through the <systemitem class=\"filesystem\">devtmpfs</"
  155. "systemitem> (via the driver core) to do it. When a <systemitem class="
  156. "\"filesystem\">devtmpfs</systemitem> instance is mounted on <filename class="
  157. "\"directory\">/dev</filename>, the device node will initially be created "
  158. "with a fixed name, permissions, and owner."
  159. msgstr ""
  160. "内核通过 <systemitem class=\"filesystem\">devtmpfs</systemitem> 直接创建设备"
  161. "文件,任何希望注册设备节点的驱动程序都要通过 <systemitem class=\"filesystem"
  162. "\">devtmpfs</systemitem> (经过驱动程序核心) 实现。当一个 <systemitem class="
  163. "\"filesystem\">devtmpfs</systemitem> 实例被挂载到 <filename class=\"directory"
  164. "\">/dev</filename> 时,设备节点将被以固定的名称、访问权限和所有者首次创建。"
  165. #. type: Content of: <sect1><sect2><sect3><para>
  166. msgid ""
  167. "A short time later, the kernel will send a uevent to <command> udevd</"
  168. "command>. Based on the rules specified in the files within the <filename "
  169. "class=\"directory\">/etc/udev/rules.d</filename>, <filename class=\"directory"
  170. "\">/lib/udev/rules.d</filename>, and <filename class=\"directory\">/run/udev/"
  171. "rules.d</filename> directories, <command> udevd</command> will create "
  172. "additional symlinks to the device node, or change its permissions, owner, or "
  173. "group, or modify the internal <command>udevd</command> database entry (name) "
  174. "for that object."
  175. msgstr ""
  176. "很快,内核会向 <command>udevd</command> 发送一个 uevent。根据 <filename "
  177. "class=\"directory\">/etc/udev/rules.d</filename>,<filename class=\"directory"
  178. "\">/lib/udev/rules.d</filename>,以及 <filename class=\"directory\">/run/"
  179. "udev/rules.d</filename> 目录中文件指定的规则,<command>udevd</command> 将为设"
  180. "备节点创建额外的符号链接,修改其访问权限,所有者,或属组,或者修改该对象的 "
  181. "<command>udevd</command> 数据库条目 (名称)。"
  182. #. type: Content of: <sect1><sect2><sect3><para>
  183. msgid ""
  184. "The rules in these three directories are numbered and all three directories "
  185. "are merged together. If <command>udevd</command> can't find a rule for the "
  186. "device it is creating, it will leave the permissions and ownership at "
  187. "whatever <systemitem class=\"filesystem\">devtmpfs</systemitem> used "
  188. "initially."
  189. msgstr ""
  190. "以上三个目录中的规则都被编号,且这三个目录的内容将合并处理。如果 "
  191. "<command>udevd</command> 找不到它正在创建的设备对应的规则,它将会沿用 "
  192. "<systemitem class=\"filesystem\">devtmpfs</systemitem> 最早使用的配置。"
  193. #. type: Content of: <sect1><sect2><sect3><title>
  194. msgid "Module Loading"
  195. msgstr "模块加载"
  196. #. type: Content of: <sect1><sect2><sect3><para>
  197. msgid ""
  198. "Device drivers compiled as modules may have aliases built into them. "
  199. "Aliases are visible in the output of the <command>modinfo</command> program "
  200. "and are usually related to the bus-specific identifiers of devices supported "
  201. "by a module. For example, the <emphasis>snd-fm801</emphasis> driver supports "
  202. "PCI devices with vendor ID 0x1319 and device ID 0x0801, and has an alias of "
  203. "<quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>. For most devices, "
  204. "the bus driver exports the alias of the driver that would handle the device "
  205. "via <systemitem class=\"filesystem\">sysfs</systemitem>. E.g., the "
  206. "<filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file might "
  207. "contain the string <quote>pci:"
  208. "v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>. The default "
  209. "rules provided with udev will cause <command>udevd</command> to call out to "
  210. "<command>/sbin/modprobe</command> with the contents of the <envar>MODALIAS</"
  211. "envar> uevent environment variable (which should be the same as the contents "
  212. "of the <filename>modalias</filename> file in sysfs), thus loading all "
  213. "modules whose aliases match this string after wildcard expansion."
  214. msgstr ""
  215. "编译为内核模块的设备驱动程序可能有内建的别名。别名可以通过 <command>modinfo</"
  216. "command> 程序查询,它通常和该模块支持的设备的总线相关标识符有关。例如,"
  217. "<emphasis>snd-fm801</emphasis> 驱动程序支持厂商 ID 为 0x1319,设备 ID 为 "
  218. "0x0801 的 PCI 设备,其别名为<quote>pci:v00001319d00000801sv*sd*bc04sc01l*</"
  219. "quote>。对于多数设备,总线驱动程序会通过 <systemitem class=\"filesystem"
  220. "\">sysfs</systemitem> 导出应该处理该设备的驱动程序别名,例如 <filename>/sys/"
  221. "bus/pci/devices/0000:00:0d.0/modalias</filename> 文件应该包含字符串"
  222. "<quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>。Udev 附"
  223. "带的默认规则会导致 <command>udevd</command> 调用 <command>/sbin/modprobe</"
  224. "command> 时传递 <envar>MODALIAS</envar> uevent 环境变量 (它的值应该和 sysfs "
  225. "中<filename>modalias</filename> 文件的内容相同),从而加载那些在通配符扩展后别"
  226. "名与这个字符串匹配的模块。"
  227. #. type: Content of: <sect1><sect2><sect3><para>
  228. msgid ""
  229. "In this example, this means that, in addition to <emphasis>snd-fm801</"
  230. "emphasis>, the obsolete (and unwanted) <emphasis>forte</emphasis> driver "
  231. "will be loaded if it is available. See below for ways in which the loading "
  232. "of unwanted drivers can be prevented."
  233. msgstr ""
  234. "在本例中,这意味着除了 <emphasis>snd-fm801</emphasis> 外,过时 (且不希望) 的 "
  235. "<emphasis>forte</emphasis> 如果可用,也会被加载。之后将介绍防止加载不希望的驱"
  236. "动程序的方法。"
  237. #. type: Content of: <sect1><sect2><sect3><para>
  238. msgid ""
  239. "The kernel itself is also able to load modules for network protocols, "
  240. "filesystems, and NLS support on demand."
  241. msgstr "内核本身也能够在需要时为网络协议,文件系统,以及 NLS 支持加载模块。"
  242. #. type: Content of: <sect1><sect2><sect3><title>
  243. msgid "Handling Hotpluggable/Dynamic Devices"
  244. msgstr "处理热插拔/动态设备"
  245. #. type: Content of: <sect1><sect2><sect3><para>
  246. msgid ""
  247. "When you plug in a device, such as a Universal Serial Bus (USB) MP3 player, "
  248. "the kernel recognizes that the device is now connected and generates a "
  249. "uevent. This uevent is then handled by <command>udevd</command> as described "
  250. "above."
  251. msgstr ""
  252. "当您插入一个设备,例如通用串行总线 (USB) MP3 播放器时,内核能够发现该设备现在"
  253. "已经被连接到系统,并生成一个 uevent 事件。之后 <command>udevd</command> 像前"
  254. "面描述的一样,处理该 uevent 事件。"
  255. #. type: Content of: <sect1><sect2><title>
  256. msgid "Problems with Loading Modules and Creating Devices"
  257. msgstr "加载模块和创建设备时的问题"
  258. #. type: Content of: <sect1><sect2><para>
  259. msgid ""
  260. "There are a few possible problems when it comes to automatically creating "
  261. "device nodes."
  262. msgstr "在自动创建设备节点时,可能出现一些问题。"
  263. #. type: Content of: <sect1><sect2><sect3><title>
  264. msgid "A kernel module is not loaded automatically"
  265. msgstr "内核模块没有自动加载"
  266. #. type: Content of: <sect1><sect2><sect3><para>
  267. msgid ""
  268. "Udev will only load a module if it has a bus-specific alias and the bus "
  269. "driver properly exports the necessary aliases to <systemitem class="
  270. "\"filesystem\">sysfs</systemitem>. In other cases, one should arrange module "
  271. "loading by other means. With Linux-&linux-version;, udev is known to load "
  272. "properly-written drivers for INPUT, IDE, PCI, USB, SCSI, SERIO, and FireWire "
  273. "devices."
  274. msgstr ""
  275. "Udev 只加载拥有总线特定别名,且总线驱动程序正确地向 <systemitem class="
  276. "\"filesystem\">sysfs</systemitem> 导出了必要别名的模块。如果情况不是这样,您"
  277. "应该考虑用其他方法加载模块。在 Linux-&linux-version; 中,已知 Udev 可以加载编"
  278. "写正确的 INPUT,IDE,PCI,USB,SCSI,SERIO,以及 FireWire 驱动程序。"
  279. #. type: Content of: <sect1><sect2><sect3><para>
  280. msgid ""
  281. "To determine if the device driver you require has the necessary support for "
  282. "udev, run <command>modinfo</command> with the module name as the argument. "
  283. "Now try locating the device directory under <filename class=\"directory\">/"
  284. "sys/bus</filename> and check whether there is a <filename>modalias</"
  285. "filename> file there."
  286. msgstr ""
  287. "为了确定您需要的设备驱动程序是否包含 Udev 支持,以模块名为参数运行 "
  288. "<command>modinfo</command> 命令。然后试着在 <filename class=\"directory\">/"
  289. "sys/bus</filename> 中找到设备对应的目录,并检查其中是否有 "
  290. "<filename>modalias</filename> 文件。"
  291. #. type: Content of: <sect1><sect2><sect3><para>
  292. msgid ""
  293. "If the <filename>modalias</filename> file exists in <systemitem class="
  294. "\"filesystem\">sysfs</systemitem>, the driver supports the device and can "
  295. "talk to it directly, but doesn't have the alias, it is a bug in the driver. "
  296. "Load the driver without the help from udev and expect the issue to be fixed "
  297. "later."
  298. msgstr ""
  299. "如果 <filename>modalias</filename> 文件存在于 <systemitem class=\"filesystem"
  300. "\">sysfs</systemitem> 中,说明驱动程序支持该设备,并能够直接和设备交互,但却"
  301. "没有正确的别名。这是驱动程序的 bug,您需要不通过 Udev 直接加载驱动,并等待这"
  302. "个问题日后被解决。"
  303. #. type: Content of: <sect1><sect2><sect3><para>
  304. msgid ""
  305. "If there is no <filename>modalias</filename> file in the relevant directory "
  306. "under <filename class=\"directory\">/sys/bus</filename>, this means that the "
  307. "kernel developers have not yet added modalias support to this bus type. With "
  308. "Linux-&linux-version;, this is the case with ISA busses. Expect this issue "
  309. "to be fixed in later kernel versions."
  310. msgstr ""
  311. "如果 <filename>modalias</filename> 文件不存在于 <filename class=\"directory"
  312. "\">/sys/bus</filename> 下的对应目录中,说明内核开发者尚未对该总线类型增加 "
  313. "modalias 支持。在 Linux-&linux-version; 中,ISA 总线不受支持。只能等待这个问"
  314. "题在日后被解决。"
  315. #. type: Content of: <sect1><sect2><sect3><para>
  316. msgid ""
  317. "Udev is not intended to load <quote>wrapper</quote> drivers such as "
  318. "<emphasis>snd-pcm-oss</emphasis> and non-hardware drivers such as "
  319. "<emphasis>loop</emphasis> at all."
  320. msgstr ""
  321. "Udev 根本不会尝试加载<quote>包装器</quote> 驱动程序,比如 <emphasis>snd-pcm-"
  322. "oss</emphasis> 等,或 <emphasis>loop</emphasis> 等非硬件驱动程序。"
  323. #. type: Content of: <sect1><sect2><sect3><title>
  324. msgid ""
  325. "A kernel module is not loaded automatically, and udev is not intended to "
  326. "load it"
  327. msgstr "内核模块没有自动加载,且 Udev 不尝试加载它"
  328. #. type: Content of: <sect1><sect2><sect3><para>
  329. msgid ""
  330. "If the <quote>wrapper</quote> module only enhances the functionality "
  331. "provided by some other module (e.g., <emphasis>snd-pcm-oss</emphasis> "
  332. "enhances the functionality of <emphasis>snd-pcm</emphasis> by making the "
  333. "sound cards available to OSS applications), configure <command>modprobe</"
  334. "command> to load the wrapper after udev loads the wrapped module. To do "
  335. "this, add a <quote>softdep</quote> line to the corresponding <filename>/etc/"
  336. "modprobe.d/<replaceable>&lt;filename&gt;</replaceable>.conf</filename> file. "
  337. "For example:"
  338. msgstr ""
  339. "如果<quote>包装器</quote>仅仅用于增强其他模块的功能 (例如,<emphasis>snd-pcm-"
  340. "oss</emphasis> 增强 <emphasis>snd-pcm</emphasis> 的功能,使 OSS 应用程序能够"
  341. "使用声卡),需要配置 <command>modprobe</command>,使其在 Udev 加载被包装的模块"
  342. "时,自动加载包装器。为此,需要将<quote>softdep</quote>行添加到对应的 "
  343. "<filename>/etc/modprobe.d/<replaceable>&lt;filename&gt;</replaceable>.conf</"
  344. "filename> 中。例如:"
  345. #. type: Content of: <sect1><sect2><sect3><screen>
  346. #, no-wrap
  347. msgid "<literal>softdep snd-pcm post: snd-pcm-oss</literal>"
  348. msgstr "<literal>softdep snd-pcm post: snd-pcm-oss</literal>"
  349. #. type: Content of: <sect1><sect2><sect3><para>
  350. msgid ""
  351. "Note that the <quote>softdep</quote> command also allows <literal>pre:</"
  352. "literal> dependencies, or a mixture of both <literal>pre:</literal> and "
  353. "<literal>post:</literal> dependencies. See the <filename>modprobe.d(5)</"
  354. "filename> manual page for more information on <quote>softdep</quote> syntax "
  355. "and capabilities."
  356. msgstr ""
  357. "注意<quote>softdep</quote>命令也允许 <literal>pre:</literal> 依赖项,或混合使"
  358. "用 <literal>pre:</literal> 和 <literal>post:</literal> 依赖项。参阅 "
  359. "<filename>modprobe.d(5)</filename> man 手册页面,了解更多关于<quote>softdep</"
  360. "quote>语法和功能的信息。"
  361. #. type: Content of: <sect1><sect2><sect3><para>
  362. msgid ""
  363. "If the module in question is not a wrapper and is useful by itself, "
  364. "configure the <command>modules</command> bootscript to load this module on "
  365. "system boot. To do this, add the module name to the <filename>/etc/sysconfig/"
  366. "modules</filename> file on a separate line. This works for wrapper modules "
  367. "too, but is suboptimal in that case."
  368. msgstr ""
  369. "如果出现问题的模块不是包装器,而是本身就有特定功能的模块,需要配置 "
  370. "<command>modules</command> 引导脚本以在系统引导时加载它。为此,将模块名添加"
  371. "到 <filename>/etc/sysconfig/modules</filename> 中,作为单独的一行。包装器模块"
  372. "也可以被添加到这里,但对于包装器来说这不是最好的方案。"
  373. #. type: Content of: <sect1><sect2><sect3><title>
  374. msgid "Udev loads some unwanted module"
  375. msgstr "Udev 加载了不希望的模块"
  376. #. type: Content of: <sect1><sect2><sect3><para>
  377. msgid ""
  378. "Either don't build the module, or blacklist it in a <filename>/etc/modprobe."
  379. "d/blacklist.conf</filename> file as done with the <emphasis>forte</emphasis> "
  380. "module in the example below:"
  381. msgstr ""
  382. "不要构建该模块,或者在 <filename>/etc/modprobe.d/blacklist.conf</filename> 文"
  383. "件中禁用它。以 <emphasis>forte</emphasis> 为例,下面一行禁用了该模块:"
  384. #. type: Content of: <sect1><sect2><sect3><screen>
  385. #, no-wrap
  386. msgid "<literal>blacklist forte</literal>"
  387. msgstr "<literal>blacklist forte</literal>"
  388. #. type: Content of: <sect1><sect2><sect3><para>
  389. msgid ""
  390. "Blacklisted modules can still be loaded manually with the explicit "
  391. "<command>modprobe</command> command."
  392. msgstr ""
  393. "被禁用的模块仍然可以通过直接执行 <command>modprobe</command> 手动加载。"
  394. #. type: Content of: <sect1><sect2><sect3><title>
  395. msgid "Udev creates a device incorrectly, or makes a wrong symlink"
  396. msgstr "Udev 创建了错误的设备或错误的符号链接"
  397. #. type: Content of: <sect1><sect2><sect3><para>
  398. msgid ""
  399. "This usually happens if a rule unexpectedly matches a device. For example, a "
  400. "poorly-written rule can match both a SCSI disk (as desired) and the "
  401. "corresponding SCSI generic device (incorrectly) by vendor. Find the "
  402. "offending rule and make it more specific, with the help of the "
  403. "<command>udevadm info</command> command."
  404. msgstr ""
  405. "这一般是由于一条规则意外地匹配了某个设备。例如,一个写得不好的规则可能同时匹"
  406. "配到 SCSI 磁盘 (正确的) 和对应厂商的 SCSI 通用设备 (不正确的)。找到引起问题的"
  407. "规则,并通过 <command>udevadm info</command> 的帮助,将它进一步细化。"
  408. #. type: Content of: <sect1><sect2><sect3><title>
  409. msgid "Udev rule works unreliably"
  410. msgstr "Udev 规则工作不可靠"
  411. #. type: Content of: <sect1><sect2><sect3><para>
  412. msgid ""
  413. "This may be another manifestation of the previous problem. If not, and your "
  414. "rule uses <systemitem class=\"filesystem\">sysfs</systemitem> attributes, it "
  415. "may be a kernel timing issue, to be fixed in later kernels. For now, you "
  416. "can work around it by creating a rule that waits for the used <systemitem "
  417. "class=\"filesystem\">sysfs</systemitem> attribute and appending it to the "
  418. "<filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename> file (create "
  419. "this file if it does not exist). Please notify the LFS Development list if "
  420. "you do so and it helps."
  421. msgstr ""
  422. "这可能是前一个问题的另一个表现形式。如果不是,而且您的规则使用了 <systemitem "
  423. "class=\"filesystem\">sysfs</systemitem> 属性,这个问题可能由内核计时问题引"
  424. "发,这类问题需要在新的内核版本中修复。目前,您可以创建一条规则以等待被使用的 "
  425. "<systemitem class=\"filesystem\">sysfs</systemitem> 属性,并将它附加到 "
  426. "<filename>/etc/udev/rules.d/10-wait-for-sysfs.rules</filename> 文件中 (如果不"
  427. "存在就创建一个文件),绕过这个问题。如果您通过这种方法解决了问题,请通知 LFS "
  428. "开发邮件列表。"
  429. #. type: Content of: <sect1><sect2><sect3><title>
  430. msgid "Udev does not create a device"
  431. msgstr "Udev 没有创建设备"
  432. #. type: Content of: <sect1><sect2><sect3><para>
  433. msgid ""
  434. "Further text assumes that the driver is built statically into the kernel or "
  435. "already loaded as a module, and that you have already checked that udev "
  436. "doesn't create a misnamed device."
  437. msgstr ""
  438. "以下内容假设驱动程序已经被编译到内核中,或作为模块被加载,而且您已经检查过并"
  439. "确认 Udev 没有创建命名错误的设备。"
  440. #. type: Content of: <sect1><sect2><sect3><para>
  441. msgid ""
  442. "Udev has no information needed to create a device node if a kernel driver "
  443. "does not export its data to <systemitem class=\"filesystem\">sysfs</"
  444. "systemitem>. This is most common with third party drivers from outside the "
  445. "kernel tree. Create a static device node in <filename>/lib/udev/devices</"
  446. "filename> with the appropriate major/minor numbers (see the file "
  447. "<filename>devices.txt</filename> inside the kernel documentation or the "
  448. "documentation provided by the third party driver vendor). The static device "
  449. "node will be copied to <filename class=\"directory\">/dev</filename> by "
  450. "<command>udev</command>."
  451. msgstr ""
  452. "如果驱动程序没有将它的信息导出到 <systemitem class=\"filesystem\">sysfs</"
  453. "systemitem>,Udev 就无法获得创建设备节点必需的信息。这种问题往往出现在内核源"
  454. "代码树以外的第三方驱动程序中。这时,需要在 <filename>/lib/udev/devices</"
  455. "filename> 中使用正确的主设备号和次设备号,创建一个静态设备节点 (参考内核文档"
  456. "中的 <filename>devices.txt</filename> 或第三方驱动厂商提供的文档),该静态设备"
  457. "节点将被复制到 <filename class=\"directory\">/dev</filename>,<command>udev</"
  458. "command> 会自动完成复制。"
  459. #. type: Content of: <sect1><sect2><sect3><title>
  460. msgid "Device naming order changes randomly after rebooting"
  461. msgstr "重启后设备命名顺序随机变化"
  462. #. type: Content of: <sect1><sect2><sect3><para>
  463. msgid ""
  464. "This is due to the fact that udev, by design, handles uevents and loads "
  465. "modules in parallel, and thus in an unpredictable order. This will never be "
  466. "<quote>fixed</quote>. You should not rely upon the kernel device names being "
  467. "stable. Instead, create your own rules that make symlinks with stable names "
  468. "based on some stable attributes of the device, such as a serial number or "
  469. "the output of various *_id utilities installed by udev. See <xref linkend="
  470. "\"ch-config-symlinks\"/> and <xref linkend=\"ch-config-network\"/> for "
  471. "examples."
  472. msgstr ""
  473. "这是由于 Udev 从设计上就是并行加载模块的,因此无法预测加载顺序。这个问题永远"
  474. "也不会被 <quote>修复</quote>。您不应该指望内核提供稳定的设备命名,而是应该创"
  475. "建您自己的规则,以根据设备的一些稳定属性,例如设备序列号或 Udev 安装的一些 "
  476. "*_id 工具的输出,来创建具有稳定名称的符号链接。可以参考<xref linkend=\"ch-"
  477. "config-symlinks\"/>和<xref linkend=\"ch-config-network\"/>中的例子。"
  478. #. type: Content of: <sect1><sect2><title>
  479. msgid "Useful Reading"
  480. msgstr "扩展阅读"
  481. #. type: Content of: <sect1><sect2><para>
  482. msgid "Additional helpful documentation is available at the following sites:"
  483. msgstr "以下链接包含了一些额外的帮助文档:"
  484. #. type: Content of: <sect1><sect2><itemizedlist><listitem><para>
  485. msgid ""
  486. "A Userspace Implementation of <systemitem class=\"filesystem\">devfs</"
  487. "systemitem> <ulink url=\"http://www.kroah.com/linux/talks/"
  488. "ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf\"/>"
  489. msgstr ""
  490. "A Userspace Implementation of <systemitem class=\"filesystem\">devfs</"
  491. "systemitem> <ulink url=\"http://www.kroah.com/linux/talks/"
  492. "ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf\"/>"
  493. #. type: Content of: <sect1><sect2><itemizedlist><listitem><para>
  494. msgid ""
  495. "The <systemitem class=\"filesystem\">sysfs</systemitem> Filesystem <ulink "
  496. "url=\"http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/"
  497. "ols-2005/mochel.pdf\"/>"
  498. msgstr ""
  499. "The <systemitem class=\"filesystem\">sysfs</systemitem> Filesystem <ulink "
  500. "url=\"http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/"
  501. "ols-2005/mochel.pdf\"/>"