diff options
Diffstat (limited to 'doc/gettext/ru/udev-guide.xml.po')
| -rw-r--r-- | doc/gettext/ru/udev-guide.xml.po | 318 |
1 files changed, 85 insertions, 233 deletions
diff --git a/doc/gettext/ru/udev-guide.xml.po b/doc/gettext/ru/udev-guide.xml.po index 96cd61b..165d8a9 100644 --- a/doc/gettext/ru/udev-guide.xml.po +++ b/doc/gettext/ru/udev-guide.xml.po @@ -2,7 +2,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"POT-Creation-Date: 2011-01-21 01:40+0500\n" +"POT-Creation-Date: 2011-03-18 11:31+0500\n" "PO-Revision-Date: 2010-02-09 01:09+0500\n" "Last-Translator: Azamat H. Hackimov <azamat.hackimov@gmail.com>\n" "Language-Team: Russian <gentoo-doc-ru@gentoo.org>\n" @@ -57,13 +57,12 @@ msgid "" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(version):26 -msgid "7" +msgid "8" msgstr "" #: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(date):27 -#, fuzzy -msgid "2010-12-26" -msgstr "2009-08-05" +msgid "2011-03-11" +msgstr "" #: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):30 msgid "What is udev?" @@ -127,228 +126,81 @@ msgstr "" #: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):73 msgid "" -"To provide these features, udev is developed in three separate projects: " -"<e>namedev</e>, <e>libsysfs</e> and, of course, <e>udev</e>." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):81 -msgid "namedev" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):84 -msgid "" -"Namedev allows you to define the device naming separately from the udev " -"program. This allows for flexible naming policies and naming schemes " -"developed by separate entities. This device naming subsystem provides a " -"standard interface that udev can use." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):91 -msgid "" -"Currently only a single naming scheme is provided by namedev; the one " -"provided by LANANA, used by the majority of Linux systems currently and " -"therefore very suitable for the majority of Linux users." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):97 -msgid "" -"Namedev uses a 5-step procedure to find out the name of a given device. If " -"the device name is found in one of the given steps, that name is used. The " -"steps are:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):104 -msgid "label or serial number" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):105 -msgid "bus device number" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):106 -msgid "bus topology" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):107 -msgid "statically given name" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):108 -msgid "kernel provided name" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):111 -msgid "" -"The <e>label or serial number</e> step checks if the device has a unique " -"identifier. For instance USB devices have a unique USB serial number; SCSI " -"devices have a unique UUID. If namedev finds a match between this unique " -"number and a given configuration file, the name provided in the " -"configuration file is used." +"Every time a change happens within the device structure, the kernel emits a " +"<e>uevent</e> which gets picked up by udev. udev then follows the rules as " +"declared in the <path>/etc/udev/rules.d</path> and <path>/lib/udev/rules.d</" +"path> directories. Based on the information contained within the uevent, it " +"finds the rule or rules it needs to trigger and performs the required " +"actions. These actions can be creating or deleting device files, but can " +"also trigger the loading of particular firmware files into the kernel memory." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):119 -msgid "" -"The <e>bus device number</e> step checks the device bus number. For non-hot-" -"swappable environments this procedure is sufficient to identify a hardware " -"device. For instance PCI bus numbers rarely change in the lifetime of a " -"system. Again, if namedev finds a match between this position and a given " -"configuration file, the name provided in that configuration file is used." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):128 -msgid "" -"Likewise the <e>bus topology</e> is a rather static way of defining devices " -"as long as the user doesn't switch devices. When the position of the device " -"matches a given setting provided by the user, the accompanying name is used." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):134 -msgid "" -"The fourth step, <e>statically given name</e>, is a simple string " -"replacement. When the kernel name (the default name) matches a given " -"replacement string, the substitute name will be used." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):140 -msgid "" -"The final step (<e>kernel provided name</e>) is a catch-all: this one takes " -"the default name provided by the kernel. In the majority of cases this is " -"sufficient as it matches the device naming used on current Linux systems." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):149 -msgid "libsysfs" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):152 -msgid "" -"udev interacts with the kernel through the sysfs pseudo filesystem. The " -"libsysfs project provides a common API to access the information given by " -"the sysfs filesystem in a generic way. This allows for querying all kinds of " -"hardware without having to make assumptions on the kind of hardware." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):162 -msgid "udev" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):165 -msgid "" -"Every time the kernel gets an event in the device structure, it asks udev to " -"take a look. udev follows the rules in the <path>/etc/udev/rules.d/</path> " -"directory. udev then uses the information given by the kernel to perform the " -"necessary actions on the <path>/dev</path> structure (creating or deleting " -"device files)." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):178 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):89 msgid "Using udev on Gentoo" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):180 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):91 msgid "Requirements" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):183 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):94 msgid "" "udev is meant to be used in combination with a 2.6 kernel (like <c>gentoo-" -"sources</c> with the default 2007.0 profile). If you're using such a kernel " -"then you just have to make sure that you have a recent <c>sys-apps/" -"baselayout</c> version. That's all you need." +"sources</c> with the default 10.0 profile). If you're using such a kernel " +"then you just should have no issues whatsoever with using udev as the " +"necessary support is built-in in all stable <c>sys-apps/baselayout</c> " +"versions. Normally, udev should already be installed on your system, but if " +"this is not the case, then it is easy to install:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):190 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):103 msgid "Installing udev" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):190 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):103 #, no-wrap msgid "" "\n" "# <i>emerge udev</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):194 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):107 msgid "Kernelwise, be sure to activate the following options:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):198 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):111 msgid "Required kernel options" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):198 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):111 #, no-wrap msgid "" "\n" -"File systems --->\n" -" [*] Inotify file change notification support\n" -" [*] Inotify support for userspace\n" +"General Setup --->\n" +" <comment>(Make sure the following item is *not* enabled)</comment>\n" +" [ ] enable deprecated sysfs features to support old userspace tools\n" +"\n" +"File Systems --->\n" +" [*] Inotify support for userspace\n" " Pseudo filesystems --->\n" -" [*] /proc file system support\n" " [*] Virtual memory file system support (former shm fs)\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):207 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):122 msgid "" "If you use <c>genkernel</c>, you don't need to do anything special. " "Genkernel sets up udev by default." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):215 -msgid "Configuration" -msgstr "Настройка" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):218 -msgid "" -"If you want to use the udev settings Gentoo provides to make your life " -"comfortable, then read no more. Gentoo will use udev but keep a static " -"<path>/dev</path> so that you will never have any missing device nodes. The " -"Gentoo init scripts won't run the devfsd daemon and will deactivate devfs " -"when you boot up." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):226 -msgid "" -"But if you are a die-hard and want to run a udev-only, unmodified system as " -"is intended by the udev development (including the difficulties of missing " -"device nodes because udev doesn't support them yet), by all means, read on :)" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):232 -msgid "" -"We'll deactivate the rules that save the device file nodes: edit the " -"<c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it " -"to <c>no</c>:" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):238 -msgid "/etc/conf.d/rc" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):238 -#, no-wrap -msgid "" -"\n" -"RC_DEVICE_TARBALL=\"no\"\n" -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):242 -msgid "" -"If you have included devfs support in your kernel, you can deactivate it in " -"the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel " -"parameter. If you want to use devfs and deactivate udev, add " -"<c>gentoo=noudev</c> as kernel parameter." -msgstr "" - -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):254 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):132 msgid "Known Issues" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):256 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):134 msgid "Missing device node files at boot" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):259 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):137 msgid "" "If you can't boot successfully because you get an error about <path>/dev/" "null</path> not found, or because the initial console is missing, the " @@ -357,7 +209,7 @@ msgid "" "machines installed from old media." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):267 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):145 msgid "" "If you run <c>sys-apps/baselayout-1.8.12</c> or later, this problem is " "alleviated since the boot process should still manage to complete. However, " @@ -365,17 +217,17 @@ msgid "" "nodes as described below." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):274 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):152 msgid "" "To see which devices nodes are present before the <path>/dev</path> " "filesystem is mounted, run the following commands:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):279 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):157 msgid "Listing device nodes available at boot" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):279 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):157 #, no-wrap msgid "" "\n" @@ -385,7 +237,7 @@ msgid "" "# <i>ls</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):286 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):164 msgid "" "The devices needed for a successful boot are <path>/dev/null</path> and " "<path>/dev/console</path>. If they didn't show up in the previous test, you " @@ -393,11 +245,11 @@ msgid "" "dev/</path> directory:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):293 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):171 msgid "Creating necessary device node files" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):293 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):171 #, no-wrap msgid "" "\n" @@ -405,17 +257,17 @@ msgid "" "# <i>mknod -m 660 null c 1 3</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):298 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):176 msgid "" "When you're finished, don't forget to unmount the <path>test/</path> " "directory:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):302 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):180 msgid "Unmounting the test/ directory" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):302 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):180 #, no-wrap msgid "" "\n" @@ -424,39 +276,39 @@ msgid "" "# <i>rmdir test</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):311 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):189 msgid "udev and nvidia" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):314 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):192 msgid "" "If you use the proprietary driver from nVidia and the X server fails to " "start on a udev-only system, then make sure you have:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):320 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):198 msgid "" "the <c>nvidia</c> module listed in <path>/etc/modules.autoload.d/kernel-2.6</" "path>" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):324 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(li):202 msgid "" "a version of baselayout equal to or greater than <c>sys-apps/" "baselayout-1.8.12</c>" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):333 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):211 msgid "No Consistent Naming between DevFS and udev" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):336 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):214 msgid "" "Even though our intention is to have a consistent naming scheme between both " "dynamical device management solutions, sometimes naming differences do occur." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):341 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):219 msgid "" "One reported clash is with a HP Smart Array 5i RAID controller (more " "precisely the <c>cciss</c> kernel module). With udev, the devices are named " @@ -465,13 +317,13 @@ msgid "" "<path>/dev/cciss/cXdY</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):349 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):227 msgid "" "If this is the case, don't forget to update your <path>/etc/fstab</path> and " "bootloader configuration files accordingly." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):354 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):232 msgid "" "The same happens with all-round symlinks that used to exist in <path>/dev</" "path>, such as <path>/dev/mouse</path>, which <c>udev</c> doesn't create " @@ -479,7 +331,7 @@ msgid "" "rule for your mouse points to an existing device file." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):361 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):239 msgid "" "Another issue is the difference in naming of terminals between devfs and " "udev. While devfs calls its terminals <c>tty</c>, udev calls them <c>vc</c> " @@ -489,11 +341,11 @@ msgid "" "securetty</path> to ensure that root can login using the console." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):373 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):251 msgid "Block device renaming" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):376 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):254 msgid "" "Recent versions of udev (104 and up) along with newer kernel versions " "(2.6.19 and up) may change your disc device names, due to a change in the " @@ -505,29 +357,29 @@ msgid "" "newer kernel and udev renames your device to <path>/dev/cdrom1</path>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):387 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):265 msgid "" "To work around these issues, you must edit <path>/etc/udev/rules.d/70-" "persistent-cd.rules</path> and assign the correct name to the device." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):393 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):271 msgid "" "For more information on writing udev rules, be sure to read Daniel Drake's " "<uri link=\"http://www.reactivated.net/udevrules.php\">guide</uri>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):401 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):279 msgid "Network device renaming" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):404 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):282 msgid "" "Sometimes unplugging and replugging a network device (like a USB WiFi card) " "can rename your net device each time, incrementing the number by one." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):409 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):287 msgid "" "When this happens, you'll see it become <c>wlan0</c>, <c>wlan1</c>, " "<c>wlan2</c>, etc. This is because udev is adding additional rules to its " @@ -535,11 +387,11 @@ msgid "" "rules directory via inotify, you need inotify support in your kernel config:" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):416 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):294 msgid "Enabling inotify support in the kernel" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):416 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):294 #, no-wrap msgid "" "\n" @@ -548,15 +400,15 @@ msgid "" " [*] Inotify support for userspace\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):422 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):300 msgid "Now udev will retain proper names for your network devices." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):429 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):307 msgid "udev loads modules in an unpredictable order" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):432 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):310 msgid "" "Sometimes udev loads modules in an undesired, unpredictable, or seemingly " "random order. This is especially common for systems that have multiple " @@ -565,7 +417,7 @@ msgid "" "numbers." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):439 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):317 msgid "" "There are a few solutions to fix device numbers and/or module load order. " "Ideally, you can just use module parameters to specify your desired device " @@ -576,11 +428,11 @@ msgid "" "must be updated." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):448 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):326 msgid "Specifying module parameters" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):448 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):326 #, no-wrap msgid "" "\n" @@ -589,7 +441,7 @@ msgid "" "# <i>update-modules</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):454 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):332 msgid "" "The above example is the preferred solution, but not all modules support " "parameters such as index. For these modules, you'll have to force the " @@ -600,11 +452,11 @@ msgid "" "package. The following example uses DVB modules." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):464 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):342 msgid "Blacklisting modules" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):464 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):342 #, no-wrap msgid "" "\n" @@ -613,17 +465,17 @@ msgid "" "# <i>update-modules</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):470 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):348 msgid "" "Next, load the modules in the correct order. Add them to <path>/etc/modules." "autoload.d/kernel-2.6</path><e>in the exact order you want them loaded</e>." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):476 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):354 msgid "Loading modules in the correct order" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):476 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):354 #, no-wrap msgid "" "\n" @@ -631,11 +483,11 @@ msgid "" "# <i>echo \"b2c2-flexcop-pci\" >> /etc/modules.autoload.d/kernel-2.6</i>\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):484 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):362 msgid "Other issues" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):487 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):365 msgid "" "If device nodes are not created when a module is loaded from <path>/etc/" "modules.autoload.d/kernel-2.6</path> but they appear when you load the " @@ -643,23 +495,23 @@ msgid "" "baselayout-1.8.12</c> or later." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):494 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):372 msgid "" "Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the " "kernel starting from version 2.6.6-rc2." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):499 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):377 msgid "" "For kernels older than 2.6.4 you have to explicitly include support for the " "<path>/dev/pts</path> filesystem." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):504 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre:caption):382 msgid "Enabling the /dev/pts filesystem" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):504 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(pre):382 #, no-wrap msgid "" "\n" @@ -668,25 +520,25 @@ msgid "" " [*] /dev/pts file system for Unix98 PTYs\n" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):515 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(title):393 msgid "Resources & Acknowledgements" msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):519 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):397 msgid "" "The udev talk on the Linux Symposium (Ottawa, Ontario Canada - 2003) given " "by Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on " "the udev application." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):525 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):403 msgid "" "<uri link=\"http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer." "html\">Decibel's UDEV Primer</uri> is an in-depth document about udev and " "Gentoo." msgstr "" -#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):530 +#: ../../gentoo/xml/htdocs/doc/en//udev-guide.xml(p):408 msgid "" "<uri link=\"http://www.reactivated.net/udevrules.php\">Writing udev rules</" "uri> by fellow Gentoo developer Daniel Drake is an excellent document to " |