1
0

udev.po 30 KB

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