2. Beyond Linux From Scratch 12.2
3. postlfs_config_devices
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	About Devices	About Devices
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	About Devices	À propos des périphériques
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	About Devices	Acerca de Dispositivos
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	/etc/udev/rules.d	/etc/udev/rules.d
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	/etc/udev/rules.d	/etc/udev/rules.d
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	/etc/udev/rules.d	/etc/udev/rules.d
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Although most devices needed by packages in BLFS and beyond are set up properly by <application>udev</application> using the default rules installed by LFS in <filename class="directory">/etc/udev/rules.d</filename>, there are cases where the rules must be modified or augmented.	Although most devices needed by packages in BLFS and beyond are set up properly by <application>udev</application> using the default rules installed by LFS in <filename class="directory">/etc/udev/rules.d</filename>, there are cases where the rules must be modified or augmented.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Although most devices needed by packages in BLFS and beyond are set up properly by <application>udev</application> using the default rules installed by LFS in <filename class="directory">/etc/udev/rules.d</filename>, there are cases where the rules must be modified or augmented.	Bien que la plupart des périphériques dont ont besoin les paquets de BLFS ont été correctement paramétrés par <application>udev</application> en utilisant les règles par défaut installées par LFS dans <filename class="directory">/etc/udev/rules.d</filename>, il y a des cas où il faut modifier ou ajouter des règles.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Although most devices needed by packages in BLFS and beyond are set up properly by <application>udev</application> using the default rules installed by LFS in <filename class="directory">/etc/udev/rules.d</filename>, there are cases where the rules must be modified or augmented.	Apesar da maioria dos dispositivos necessitados pelos pacotes no BLFS e além serem configurados adequadamente pelo <application>udev</application> usando as regras padrão instaladas pelo LFS em <filename class="directory">/etc/udev/rules.d</filename>, existem casos onde as regras precisam ser modificadas ou estendidas.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Multiple Sound Cards	Multiple Sound Cards
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Multiple Sound Cards	Cartes sons multiples
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Multiple Sound Cards	Múltiplas Placas de Som
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	If there are multiple sound cards in a system, the "default" sound card becomes random. The method to establish sound card order depends on whether the drivers are modules or not. If the sound card drivers are compiled into the kernel, control is via kernel command line parameters in <filename>/boot/grub/grub.cfg</filename>. For example, if a system has both an FM801 card and a SoundBlaster PCI card, the following can be appended to the command line:	If there are multiple sound cards in a system, the "default" sound card becomes random. The method to establish sound card order depends on whether the drivers are modules or not. If the sound card drivers are compiled into the kernel, control is via kernel command line parameters in <filename>/boot/grub/grub.cfg</filename>. For example, if a system has both an FM801 card and a SoundBlaster PCI card, the following can be appended to the command line:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	If there are multiple sound cards in a system, the "default" sound card becomes random. The method to establish sound card order depends on whether the drivers are modules or not. If the sound card drivers are compiled into the kernel, control is via kernel command line parameters in <filename>/boot/grub/grub.cfg</filename>. For example, if a system has both an FM801 card and a SoundBlaster PCI card, the following can be appended to the command line:	S'il y a plusieurs cartes sons sur un système, la carte son «&nbsp;default&nbsp;» (par défaut) devient aléatoire. La méthode pour établir un ordre dans les cartes sons dépend du fait que les pilotes soient en modules ou pas. Si les pilotes de la carte son sont compilés dans le noyau, leur contrôle s'effectue via des paramètres de la ligne de commande du noyau dans <filename>/boot/grub/grub.cfg</filename>. Par exemple, si un système contient une carte FM801 et une carte PCI SoundBlaster, ce qui suit peut être ajouté à la ligne de commande&nbsp;:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	If there are multiple sound cards in a system, the "default" sound card becomes random. The method to establish sound card order depends on whether the drivers are modules or not. If the sound card drivers are compiled into the kernel, control is via kernel command line parameters in <filename>/boot/grub/grub.cfg</filename>. For example, if a system has both an FM801 card and a SoundBlaster PCI card, the following can be appended to the command line:	Se existirem múltiplas placas de som em um sistema, [então] a placa de som "padrão" se torna aleatória. O método para estabelecer a ordem da placa de som depende se os controladores são módulos ou não. Se os controladores da placa de som forem compilados internamente no núcleo, [então] o controle é via parâmetros de linha de comando do núcleo em <filename>/boot/grub/grub.cfg</filename>. Por exemplo, se um sistema tiver ambas, uma placa FM801 e uma placa PCI SoundBlaster, [então] o seguinte pode ser acrescentado à linha de comando:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	<literal>snd-fm801.index=0 snd-ens1371.index=1</literal>	<literal>snd-fm801.index=0 snd-ens1371.index=1</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	<literal>snd-fm801.index=0 snd-ens1371.index=1</literal>	<literal>snd-fm801.index=0 snd-ens1371.index=1</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	<literal>snd-fm801.index=0 snd-ens1371.index=1</literal>	<literal>snd-fm801.index=0 snd-ens1371.index=1</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	If the sound card drivers are built as modules, the order can be established in the <filename>/etc/modprobe.conf</filename> file with:	If the sound card drivers are built as modules, the order can be established in the <filename>/etc/modprobe.conf</filename> file with:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	If the sound card drivers are built as modules, the order can be established in the <filename>/etc/modprobe.conf</filename> file with:	Si les pilotes de la carte son sont construits en modules, on peut établir l'ordre dans le fichier <filename>/etc/modprobe.conf</filename> avec&nbsp;:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	If the sound card drivers are built as modules, the order can be established in the <filename>/etc/modprobe.conf</filename> file with:	Se os controladores da placa de som forem construídos como módulos, [então] a ordem pode ser estabelecida no arquivo <filename>/etc/modprobe.conf</filename> com:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	<literal>options snd-fm801 index=0 options snd-ens1371 index=1</literal>	<literal>options snd-fm801 index=0 options snd-ens1371 index=1</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	<literal>options snd-fm801 index=0 options snd-ens1371 index=1</literal>	<literal>options snd-fm801 index=0 options snd-ens1371 index=1</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	<literal>options snd-fm801 index=0 options snd-ens1371 index=1</literal>	<literal>options snd-fm801 index=0 options snd-ens1371 index=1</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	USB Device Issues	USB Device Issues
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	USB Device Issues	Problèmes sur les périphériques USB
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	USB Device Issues	Consequências do Dispositivo USB
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	USB devices usually have two kinds of device nodes associated with them.	USB devices usually have two kinds of device nodes associated with them.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	USB devices usually have two kinds of device nodes associated with them.	Les périphériques USB ont habituellement deux types de nœuds de périphériques associés avec eux.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	USB devices usually have two kinds of device nodes associated with them.	Os dispositivos USB geralmente tem dois tipos de nós de dispositivo associados com eles.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	The first kind is created by device-specific drivers (e.g., usb_storage/sd_mod or usblp) in the kernel. For example, a USB mass storage device would be /dev/sdb, and a USB printer would be /dev/usb/lp0. These device nodes exist only when the device-specific driver is loaded.	The first kind is created by device-specific drivers (e.g., usb_storage/sd_mod or usblp) in the kernel. For example, a USB mass storage device would be /dev/sdb, and a USB printer would be /dev/usb/lp0. These device nodes exist only when the device-specific driver is loaded.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	The first kind is created by device-specific drivers (e.g., usb_storage/sd_mod or usblp) in the kernel. For example, a USB mass storage device would be /dev/sdb, and a USB printer would be /dev/usb/lp0. These device nodes exist only when the device-specific driver is loaded.	Le premier type est créé par le pilote du périphérique spécifique (usb_storage/sd_mod ou usblp) dans le noyau. Par exemple, un périphérique de stockage USB peut être /dev/sdb, et une imprimante USB peut être /dev/usb/lp0. Ces nœuds de périphériques existent seulement quand le pilote du périphérique spécifique est chargé.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	The first kind is created by device-specific drivers (e.g., usb_storage/sd_mod or usblp) in the kernel. For example, a USB mass storage device would be /dev/sdb, and a USB printer would be /dev/usb/lp0. These device nodes exist only when the device-specific driver is loaded.	O primeiro tipo é criado pelos controladores específicos do dispositivo (por exemplo, usb_storage/sd_mod ou usblp) no núcleo. Por exemplo, um dispositivo USB de armazenamento em massa seria /dev/sdb; e uma impressora USB seria /dev/usb/lp0. Esses nós de dispositivo existem somente quando o controlador específico do dispositivo estiver carregado.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	The second kind of device nodes (/dev/bus/usb/BBB/DDD, where BBB is the bus number and DDD is the device number) are created even if the device doesn't have a kernel driver. By using these "raw" USB device nodes, an application can exchange arbitrary USB packets with the device, i.e., bypass the possibly-existing kernel driver.	The second kind of device nodes (/dev/bus/usb/BBB/DDD, where BBB is the bus number and DDD is the device number) are created even if the device doesn't have a kernel driver. By using these "raw" USB device nodes, an application can exchange arbitrary USB packets with the device, i.e., bypass the possibly-existing kernel driver.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	The second kind of device nodes (/dev/bus/usb/BBB/DDD, where BBB is the bus number and DDD is the device number) are created even if the device doesn't have a kernel driver. By using these "raw" USB device nodes, an application can exchange arbitrary USB packets with the device, i.e., bypass the possibly-existing kernel driver.	Le second type de nœud de périphériques (/dev/bus/usb/BBB/DDD, ou BBB est le numéro du bus et DDD est le numéro du périphérique) est créé chaque fois que le périphérique n'a pas de driver dans le noyau. En utilisant ces nœuds de périphérique USB "directs", une application peut échanger arbitrairement des paquets USB avec le périphérique, c'est-à-dire, court-circuiter le possible pilote existant du noyau.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	The second kind of device nodes (/dev/bus/usb/BBB/DDD, where BBB is the bus number and DDD is the device number) are created even if the device doesn't have a kernel driver. By using these "raw" USB device nodes, an application can exchange arbitrary USB packets with the device, i.e., bypass the possibly-existing kernel driver.	O segundo tipo de nós de dispositivo (/dev/bus/usb/BBB/DDD, onde BBB é o número do barramento e DDD é o número do dispositivo) é criado mesmo se o dispositivo não tiver um controlador de núcleo. Ao usar esses nós de dispositivo USB "crus", um aplicativo consegue trocar pacotes USB arbitrários com o dispositivo, isto é, contornar o possivelmente existente controlador de núcleo.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Access to raw USB device nodes is needed when a userspace program is acting as a device driver. However, for the program to open the device successfully, the permissions have to be set correctly. By default, due to security concerns, all raw USB devices are owned by user root and group root, and have 0664 permissions (the read access is needed, e.g., for lsusb to work and for programs to access USB hubs). Packages (such as SANE and libgphoto2) containing userspace USB device drivers also ship udev rules that change the permissions of the controlled raw USB devices. That is, rules installed by SANE change permissions for known scanners, but not printers. If a package maintainer forgot to write a rule for your device, report a bug to both BLFS (if the package is there) and upstream, and you will need to write your own rule.	Access to raw USB device nodes is needed when a userspace program is acting as a device driver. However, for the program to open the device successfully, the permissions have to be set correctly. By default, due to security concerns, all raw USB devices are owned by user root and group root, and have 0664 permissions (the read access is needed, e.g., for lsusb to work and for programs to access USB hubs). Packages (such as SANE and libgphoto2) containing userspace USB device drivers also ship udev rules that change the permissions of the controlled raw USB devices. That is, rules installed by SANE change permissions for known scanners, but not printers. If a package maintainer forgot to write a rule for your device, report a bug to both BLFS (if the package is there) and upstream, and you will need to write your own rule.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Access to raw USB device nodes is needed when a userspace program is acting as a device driver. However, for the program to open the device successfully, the permissions have to be set correctly. By default, due to security concerns, all raw USB devices are owned by user root and group root, and have 0664 permissions (the read access is needed, e.g., for lsusb to work and for programs to access USB hubs). Packages (such as SANE and libgphoto2) containing userspace USB device drivers also ship udev rules that change the permissions of the controlled raw USB devices. That is, rules installed by SANE change permissions for known scanners, but not printers. If a package maintainer forgot to write a rule for your device, report a bug to both BLFS (if the package is there) and upstream, and you will need to write your own rule.	Accéder aux nœuds périphériques USB directement est nécessaire quand un programme de l'espace utilisateur est considéré comme un pilote de périphérique. Cependant, pour que le programme ouvre avec succès le périphérique, les permissions doivent être initialisées correctement. Par défaut, pour des considérations de sécurité, tous les périphériques USB directs appartiennent à l'utilisateur root et au groupe root, et ont la permission 0664 (l'accès en lecture est nécessaire, par exemple pour que lsusb puisse travailler et pour les programmes d'accès aux concentrateurs USB). Des paquets (comme SANE et libgphoto2) contenant un pilote de périphérique USB dans l'espace utilisateur utilisent aussi les règles udev pour changer les permissions des périphériques USB contrôlés. Ce qui fait que les règles installées par SANE changent les permissions pour les scanners reconnus, mais pas pour les imprimantes. Si le mainteneur du paquet oublie d'écrire une règle pour votre périphérique, signalez le bogue à BLFS (si le paquet est ici) et en amont, et vous aurez besoin d'écrire votre propre règle.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Access to raw USB device nodes is needed when a userspace program is acting as a device driver. However, for the program to open the device successfully, the permissions have to be set correctly. By default, due to security concerns, all raw USB devices are owned by user root and group root, and have 0664 permissions (the read access is needed, e.g., for lsusb to work and for programs to access USB hubs). Packages (such as SANE and libgphoto2) containing userspace USB device drivers also ship udev rules that change the permissions of the controlled raw USB devices. That is, rules installed by SANE change permissions for known scanners, but not printers. If a package maintainer forgot to write a rule for your device, report a bug to both BLFS (if the package is there) and upstream, and you will need to write your own rule.	O acesso a nós de dispositivo USB brutos é necessário quando um aplicativo do espaço do(a) usuário(a) estiver atuando como um controlador de dispositivo. Entretanto, para o aplicativo abrir o dispositivo com sucesso, as permissões tem de ser configuradas corretamente. Por padrão, devido a motivos de segurança, todos os dispositivos USB brutos são de propriedade do(a) usuário(a) root e do grupo root, e tem permissões 0664 (o acesso de leitura é necessário, por exemplo, para o lsusb funcionar e para os aplicativos acessarem hubs USB). Os pacotes (tais como SANE e libgphoto2) contendo controladores de dispositivo USB do espaço do(a) usuário(a) também enviam regras do Udev que mudam as permissões dos dispositivos USB brutos controlados. Isto é, as regras instaladas pelo SANE mudam as permissões para escaneadores conhecidos, porém não para impressoras. Se um(a) mantenedor(a) de pacote se esqueceu de escrever uma regra para o teu dispositivo, informe um defeito para ambos, o BLFS (se o pacote estiver lá) e o(a) desenvolvedor(a), e você precisará escrever tua própria regra.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Before Linux-2.6.15, raw USB device access was performed not with /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD pseudofiles. Some applications still use only this deprecated technique and can't use the new device nodes. They cannot work with Linux kernel version 3.5 or newer. If you need to run such an application, contact the developer of it for a fix.	Before Linux-2.6.15, raw USB device access was performed not with /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD pseudofiles. Some applications still use only this deprecated technique and can't use the new device nodes. They cannot work with Linux kernel version 3.5 or newer. If you need to run such an application, contact the developer of it for a fix.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Before Linux-2.6.15, raw USB device access was performed not with /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD pseudofiles. Some applications still use only this deprecated technique and can't use the new device nodes. They cannot work with Linux kernel version 3.5 or newer. If you need to run such an application, contact the developer of it for a fix.	Avant Linux-2.6.15, l'accès direct aux périphériques USB n'était pas géré avec les nœuds de périphériques /dev/bus/usb/BBB/DDD, mais avec des pseudo-fichiers /proc/bus/usb/BBB/DDD. Quelques applications utilisent seulement cette technique obsolète et ne peuvent pas utiliser les nouveaux nœuds de périphériques. Elles ne peuvent pas fonctionner avec le noyau Linux version 3.5 ou supérieur. Si vous avez besoin de ces applications, contactez le développeur pour demander un correctif.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Before Linux-2.6.15, raw USB device access was performed not with /dev/bus/usb/BBB/DDD device nodes, but with /proc/bus/usb/BBB/DDD pseudofiles. Some applications still use only this deprecated technique and can't use the new device nodes. They cannot work with Linux kernel version 3.5 or newer. If you need to run such an application, contact the developer of it for a fix.	Antes do Linux-2.6.15, o acesso de dispositivo USB bruto era realizado não com nós de dispositivo /dev/bus/usb/BBB/DDD, mas com pseudo arquivos /proc/bus/usb/BBB/DDD. Alguns aplicativos ainda usam somente essa técnica obsoleta e não conseguem usar os novos nós de dispositivo. Eles não conseguem funcionar com a versão 3.5 ou mais recente do núcleo Linux. Se você precisar executar tal aplicativo, contacte o(a) desenvolvedor(a) dele para uma correção.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Udev Device Attributes	Udev Device Attributes
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Udev Device Attributes	Attributs de périphériques d'Udev
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Udev Device Attributes	Atributos de Dispositivo do Udev
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Fine-tuning of device attributes such as group name and permissions is possible by creating extra <application>udev</application> rules, matching on something like this. The vendor and product can be found by searching the <filename class='directory'>/sys/devices</filename> directory entries or using <command>udevadm info</command> after the device has been attached. See the documentation in the current <application>udev</application> directory of <filename class='directory'>/usr/share/doc</filename> for details.	Fine-tuning of device attributes such as group name and permissions is possible by creating extra <application>udev</application> rules, matching on something like this. The vendor and product can be found by searching the <filename class='directory'>/sys/devices</filename> directory entries or using <command>udevadm info</command> after the device has been attached. See the documentation in the current <application>udev</application> directory of <filename class='directory'>/usr/share/doc</filename> for details.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Fine-tuning of device attributes such as group name and permissions is possible by creating extra <application>udev</application> rules, matching on something like this. The vendor and product can be found by searching the <filename class='directory'>/sys/devices</filename> directory entries or using <command>udevadm info</command> after the device has been attached. See the documentation in the current <application>udev</application> directory of <filename class='directory'>/usr/share/doc</filename> for details.	Le peaufinage des attributs de périphériques tels que le nom du groupe et les droits est possible en créant des règles <application>udev</application> supplémentaires, correspondant à quelque chose de ce genre. On peut trouver le fabricant et le produit en cherchant les entrées du répertoire <filename class='directory'>/sys/devices</filename> ou en utilisant <command>udevinfo</command> après avoir attaché le périphérique. Voir la documentation dans le répertoire d'<application>udev</application> actuel <filename class='directory'>/usr/share/doc</filename> pour des détails.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Fine-tuning of device attributes such as group name and permissions is possible by creating extra <application>udev</application> rules, matching on something like this. The vendor and product can be found by searching the <filename class='directory'>/sys/devices</filename> directory entries or using <command>udevadm info</command> after the device has been attached. See the documentation in the current <application>udev</application> directory of <filename class='directory'>/usr/share/doc</filename> for details.	O ajuste fino dos atributos de dispositivo, tais como nome e permissões do grupo, é possível criando-se regras extras do <application>udev</application>, casando com algo como isto. O fornecedor e produto pode ser encontrado procurando-se nas entradas do diretório <filename class='directory'>/sys/devices</filename> ou usando-se o <command>udevadm info</command> depois que o dispositivo tenha sido anexado. Veja-se a documentação no diretório atual do <application>udev</application> do <filename class='directory'>/usr/share/doc</filename> para detalhes.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	<literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \ GROUP:="scanner", MODE:="0660"</literal>	<literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \ GROUP:="scanner", MODE:="0660"</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	<literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \ GROUP:="scanner", MODE:="0660"</literal>	<literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \ GROUP:="scanner", MODE:="0660"</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	<literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \ GROUP:="scanner", MODE:="0660"</literal>	<literal>SUBSYSTEM=="usb_device", SYSFS{idVendor}=="05d8", SYSFS{idProduct}=="4002", \ GROUP:="scanner", MODE:="0660"</literal>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	The above line is used for descriptive purposes only. The scanner <application>udev</application> rules are put into place when installing <xref linkend='sane'/>.	The above line is used for descriptive purposes only. The scanner <application>udev</application> rules are put into place when installing <xref linkend='sane'/>.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	The above line is used for descriptive purposes only. The scanner <application>udev</application> rules are put into place when installing <xref linkend='sane'/>.	On n'utilise la ligne ci-dessus qu'à des fins descriptives. Les règles d'analyse d'<application>udev</application> sont mises en place lors de l'installation de <xref linkend='sane'/>.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	The above line is used for descriptive purposes only. The scanner <application>udev</application> rules are put into place when installing <xref linkend='sane'/>.	A linha acima é usada somente para propósitos descritivos. As regras do <application>udev</application> da escaneadora são colocadas no lugar quando se instalar o <xref linkend='sane'/>.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Devices for Servers	Devices for Servers
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Devices for Servers	Périphériques pour les serveurs
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Devices for Servers	Dispositivos para Servidores
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	In some cases, it makes sense to disable <application>udev</application> completely and create static devices. Servers are one example of this situation. Does a server need the capability of handling dynamic devices? Only the system administrator can answer that question, but in many cases the answer will be no.	In some cases, it makes sense to disable <application>udev</application> completely and create static devices. Servers are one example of this situation. Does a server need the capability of handling dynamic devices? Only the system administrator can answer that question, but in many cases the answer will be no.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	In some cases, it makes sense to disable <application>udev</application> completely and create static devices. Servers are one example of this situation. Does a server need the capability of handling dynamic devices? Only the system administrator can answer that question, but in many cases the answer will be no.	Dans certains cas, il est utile de désactiver <application>udev</application> complètement et de créer des périphériques statiques. Les serveurs sont un exemple de cette situation. Est-ce qu'un serveur a besoin de la possibilité de gérer des périphériques dynamiques&nbsp;? Seul l'administrateur système peut répondre à cette question, mais dans de nombreux cas, la réponse est non.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	In some cases, it makes sense to disable <application>udev</application> completely and create static devices. Servers are one example of this situation. Does a server need the capability of handling dynamic devices? Only the system administrator can answer that question, but in many cases the answer will be no.	Em alguns casos, faz sentido desabilitar o <application>udev</application> completamente e criar dispositivos estáticos. Servidores são um exemplo dessa situação. Um servidor precisa da capacidade de manusear dispositivos dinâmicos? Somente o(a) administrador(a) do sistema pode responder a essa pergunta, porém, em muitos casos, a resposta será não.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	If dynamic devices are not desired, then static devices must be created on the system. In the default configuration, the <filename>/etc/rc.d/rcS.d/S10udev</filename> boot script mounts a <systemitem class="filesystem">tmpfs</systemitem> partition over the <filename class="directory">/dev</filename> directory. This problem can be overcome by mounting the root partition temporarily:	If dynamic devices are not desired, then static devices must be created on the system. In the default configuration, the <filename>/etc/rc.d/rcS.d/S10udev</filename> boot script mounts a <systemitem class="filesystem">tmpfs</systemitem> partition over the <filename class="directory">/dev</filename> directory. This problem can be overcome by mounting the root partition temporarily:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	If dynamic devices are not desired, then static devices must be created on the system. In the default configuration, the <filename>/etc/rc.d/rcS.d/S10udev</filename> boot script mounts a <systemitem class="filesystem">tmpfs</systemitem> partition over the <filename class="directory">/dev</filename> directory. This problem can be overcome by mounting the root partition temporarily:	Si vous ne désirez pas de périphériques dynamiques, vous devez créer des périphériques statiques sur le système. Dans la configuration par défaut, le script de démarrage <filename>/etc/rc.d/rcS.d/S10udev</filename> monte une partition <systemitem class="filesystem">tmpfs</systemitem> dans le répertoire <filename class="directory">/dev</filename>. Ce problème peut être résolu en montant temporairement la partition racine&nbsp;:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	If dynamic devices are not desired, then static devices must be created on the system. In the default configuration, the <filename>/etc/rc.d/rcS.d/S10udev</filename> boot script mounts a <systemitem class="filesystem">tmpfs</systemitem> partition over the <filename class="directory">/dev</filename> directory. This problem can be overcome by mounting the root partition temporarily:	Se dispositivos dinâmicos não forem desejados, então dispositivos estáticos precisam ser criados no sistema. Na configuração padrão, o script de inicialização <filename>/etc/rc.d/rcS.d/S10udev</filename> monta uma partição <systemitem class="filesystem">tmpfs</systemitem> sobre o diretório <filename class="directory">/dev</filename>. Esse problema pode ser ultrapassado montando-se a partição raiz temporariamente:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	If the instructions below are not followed carefully, your system could become unbootable.	If the instructions below are not followed carefully, your system could become unbootable.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	If the instructions below are not followed carefully, your system could become unbootable.	Si vous ne suivez pas rigoureusement les instructions ci-dessous, votre système pourrait ne plus pouvoir démarrer.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	If the instructions below are not followed carefully, your system could become unbootable.	Se as instruções abaixo não forem seguidas cuidadosamente, [então] o seu sistema poderia se tornar não inicializável.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	<userinput>mount --bind / /mnt cp -a /dev/* /mnt/dev rm /etc/rc.d/rcS.d/{S10udev,S50udev_retry} umount /mnt</userinput>	<userinput>mount --bind / /mnt cp -a /dev/* /mnt/dev rm /etc/rc.d/rcS.d/{S10udev,S50udev_retry} umount /mnt</userinput>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	<userinput>mount --bind / /mnt cp -a /dev/* /mnt/dev rm /etc/rc.d/rcS.d/{S10udev,S50udev_retry} umount /mnt</userinput>	<userinput>mount --bind / /mnt cp -a /dev/* /mnt/dev rm /etc/rc.d/rcS.d/{S10udev,S50udev_retry} umount /mnt</userinput>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	<userinput>mount --bind / /mnt cp -a /dev/* /mnt/dev rm /etc/rc.d/rcS.d/{S10udev,S50udev_retry} umount /mnt</userinput>	<userinput>mount --bind / /mnt cp -a /dev/* /mnt/dev rm /etc/rc.d/rcS.d/{S10udev,S50udev_retry} umount /mnt</userinput>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	At this point, the system will use static devices upon the next reboot. Create any desired additional devices using <command>mknod</command>.	At this point, the system will use static devices upon the next reboot. Create any desired additional devices using <command>mknod</command>.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	At this point, the system will use static devices upon the next reboot. Create any desired additional devices using <command>mknod</command>.	Dès lors, le système utilisera des périphériques statiques lors du prochain redémarrage. Créez les périphériques supplémentaires désirés en utilisant <command>mknod</command>.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	At this point, the system will use static devices upon the next reboot. Create any desired additional devices using <command>mknod</command>.	Neste ponto, o sistema usará dispositivos estáticos até a próxima reinicialização. Crie quaisquer dispositivos adicionais desejados usando o <command>mknod</command>.
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	If you want to restore the dynamic devices, recreate the <filename>/etc/rc.d/rcS.d/{S10udev,S50udev_retry}</filename> symbolic links and reboot again. Static devices do not need to be removed (console and null are always needed) because they are covered by the <systemitem class="filesystem">tmpfs</systemitem> partition. Disk usage for devices is negligible (about 20&ndash;30 bytes per entry).	If you want to restore the dynamic devices, recreate the <filename>/etc/rc.d/rcS.d/{S10udev,S50udev_retry}</filename> symbolic links and reboot again. Static devices do not need to be removed (console and null are always needed) because they are covered by the <systemitem class="filesystem">tmpfs</systemitem> partition. Disk usage for devices is negligible (about 20&ndash;30 bytes per entry).
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	If you want to restore the dynamic devices, recreate the <filename>/etc/rc.d/rcS.d/{S10udev,S50udev_retry}</filename> symbolic links and reboot again. Static devices do not need to be removed (console and null are always needed) because they are covered by the <systemitem class="filesystem">tmpfs</systemitem> partition. Disk usage for devices is negligible (about 20&ndash;30 bytes per entry).	Si vous voulez restaurer les périphériques dynamiques, recréez les liens symboliques <filename>/etc/rc.d/rcS.d/{S10udev,S50udev_retry}</filename> et redémarrez de nouveau. Il n'est pas nécessaire de supprimer les périphériques statiques (console et null sont toujours nécessaires) car ils sont recouverts par la partition <systemitem class="filesystem">tmpfs</systemitem>. L'utilisation du disque par des périphériques est négligeable (environ 20&ndash;30 octets par entrée).
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	If you want to restore the dynamic devices, recreate the <filename>/etc/rc.d/rcS.d/{S10udev,S50udev_retry}</filename> symbolic links and reboot again. Static devices do not need to be removed (console and null are always needed) because they are covered by the <systemitem class="filesystem">tmpfs</systemitem> partition. Disk usage for devices is negligible (about 20&ndash;30 bytes per entry).	Se você quiser restaurar os dispositivos dinâmicos, recrie os vínculos simbólicos <filename>/etc/rc.d/rcS.d/{S10udev,S50udev_retry}</filename> e reinicialize novamente. Dispositivos estáticos não precisam ser removidos (console e null sempre são necessários), pois eles são cobertos pela partição <systemitem class="filesystem">tmpfs</systemitem>. O uso do disco para dispositivos é desprezível (cerca de 20&ndash;30 bytes por entrada).
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	Devices for DVD Drives	Devices for DVD Drives
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	Devices for DVD Drives	Périphériques pour les lecteurs DVD
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	Devices for DVD Drives	Dispositivos para Unidades de DVD
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	If the initial boot process does not set up the <systemitem>/dev/dvd</systemitem> device properly, it can be installed using the following modification to the default udev rules. As the <systemitem class="username">root</systemitem> user, run:	If the initial boot process does not set up the <systemitem>/dev/dvd</systemitem> device properly, it can be installed using the following modification to the default udev rules. As the <systemitem class="username">root</systemitem> user, run:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	If the initial boot process does not set up the <systemitem>/dev/dvd</systemitem> device properly, it can be installed using the following modification to the default udev rules. As the <systemitem class="username">root</systemitem> user, run:	Si le processus de démarrage initial ne met pas en place le périphérique <systemitem>/dev/dvd</systemitem> correctement, cela peut être fait avec les modifications suivantes des règles udev par défaut. En tant qu'utilisateur <systemitem class="username">root</systemitem>, lancez&nbsp;:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	If the initial boot process does not set up the <systemitem>/dev/dvd</systemitem> device properly, it can be installed using the following modification to the default udev rules. As the <systemitem class="username">root</systemitem> user, run:	Se o processo inicial da inicialização não configurar o dispositivo <systemitem>/dev/dvd</systemitem> adequadamente, [então] ele pode ser instalado usando-se a seguinte modificação para as regras padrão do udev. Como o(a) usuário(a) <systemitem class="username">root</systemitem>, execute:
	Beyond Linux From Scratch 12.2/postlfs_config_devices — English	<userinput>sed '1d;/SYMLINK.*cdrom/ a\ KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \ /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules</userinput>	<userinput>sed '1d;/SYMLINK.*cdrom/ a\ KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \ /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules</userinput>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — French	<userinput>sed '1d;/SYMLINK.*cdrom/ a\ KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \ /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules</userinput>	<userinput>sed '1d;/SYMLINK.*cdrom/ a\ KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \ /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules</userinput>
	Beyond Linux From Scratch 12.2/postlfs_config_devices — Portuguese (Brazil)	<userinput>sed '1d;/SYMLINK.*cdrom/ a\ KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \ /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules</userinput>	<userinput>sed '1d;/SYMLINK.*cdrom/ a\ KERNEL=="sr0", ENV{ID_CDROM_DVD}=="1", SYMLINK+="dvd", OPTIONS+="link_priority=-100"' \ /lib/udev/rules.d/60-cdrom_id.rules > /etc/udev/rules.d/60-cdrom_id.rules</userinput>