153 strings / 5342 words

Translation Source string Target string
Linux From Scratch 12.3/chapter09_symlinks — English
Managing Devices
Managing Devices
Linux From Scratch 12.3/chapter09_symlinks — French
Managing Devices
Gérer les périphériques
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Managing Devices
Gerenciando Dispositivos
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
Managing Devices
管理设备
Linux From Scratch 12.3/chapter09_symlinks — English
Network Devices
Network Devices
Linux From Scratch 12.3/chapter09_symlinks — French
Network Devices
Périphériques réseaux
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Network Devices
Dispositivos da Rede de Comunicação
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
Network Devices
网络设备
Linux From Scratch 12.3/chapter09_symlinks — English
Udev, by default, names network devices according to Firmware/BIOS data or physical characteristics like the bus, slot, or MAC address. The purpose of this naming convention is to ensure that network devices are named consistently, not based on when the network card was discovered. In older versions of Linux—on a computer with two network cards made by Intel and Realtek, for instance—the network card manufactured by Intel might have become eth0 while the Realtek card became eth1. After a reboot, the cards would sometimes get renumbered the other way around.
Udev, by default, names network devices according to Firmware/BIOS data or physical characteristics like the bus, slot, or MAC address. The purpose of this naming convention is to ensure that network devices are named consistently, not based on when the network card was discovered. In older versions of Linux—on a computer with two network cards made by Intel and Realtek, for instance—the network card manufactured by Intel might have become eth0 while the Realtek card became eth1. After a reboot, the cards would sometimes get renumbered the other way around.
Linux From Scratch 12.3/chapter09_symlinks — French
Udev, by default, names network devices according to Firmware/BIOS data or physical characteristics like the bus, slot, or MAC address. The purpose of this naming convention is to ensure that network devices are named consistently, not based on when the network card was discovered. In older versions of Linux—on a computer with two network cards made by Intel and Realtek, for instance—the network card manufactured by Intel might have become eth0 while the Realtek card became eth1. After a reboot, the cards would sometimes get renumbered the other way around.
Udev, par défaut, nomme les périphériques réseaux à partir des données du logiciel embarqué/BIOS ou des caractéristiques physiques comme leur bus, leur slot ou leur adresse MAC. Le but de cette convention de nommage est de s'assurer que les périphériques réseaux sont nommés de façon cohérente et non en fonction du moment où la carte réseau a été trouvée. Sur des anciennes versions de Linux—sur des ordinateurs avec deux cartes réseaux Intel et Realtek, par exemple, il se peut que la carte réseau Intel soit nommée eth0 et la Realtek soit nommée eth1. Au redémarrage, les cartes sont parfois numérotées en sens inverse.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Udev, by default, names network devices according to Firmware/BIOS data or physical characteristics like the bus, slot, or MAC address. The purpose of this naming convention is to ensure that network devices are named consistently, not based on when the network card was discovered. In older versions of Linux—on a computer with two network cards made by Intel and Realtek, for instance—the network card manufactured by Intel might have become eth0 while the Realtek card became eth1. After a reboot, the cards would sometimes get renumbered the other way around.
O Udev, por padrão, nomeia dispositivos da rede de comunicação de acordo com dados de Firmware/BIOS ou características físicas, como o barramento, slot ou endereço MAC. O propósito dessa convenção de nomenclatura é o de garantir que dispositivos da rede de comunicação sejam nomeados consistentemente e não baseados em quando a placa de rede de comunicação foi descoberta. Em versões mais antigas do Linux—em um computador com duas placas de rede de comunicação feitas por Intel e Realtek, por exemplo—a placa de rede de comunicação fabricada pela Intel talvez se torne eth0, enquanto que e a placa Realtek se tornou eth1. Depois de uma reinicialização, as placas poderiam, às vezes, serem renumeradas da maneira inversa.
Linux From Scratch 12.3/chapter09_symlinks — English
In the new naming scheme, typical network device names are something like enp5s0 or wlp3s0. If this naming convention is not desired, the traditional naming scheme, or a custom scheme, can be implemented.
In the new naming scheme, typical network device names are something like enp5s0 or wlp3s0. If this naming convention is not desired, the traditional naming scheme, or a custom scheme, can be implemented.
Linux From Scratch 12.3/chapter09_symlinks — French
In the new naming scheme, typical network device names are something like enp5s0 or wlp3s0. If this naming convention is not desired, the traditional naming scheme, or a custom scheme, can be implemented.
Avec la nouvelle règle de nommage, les noms des cartes réseaux ressembleraient en général à quelque chose comme enp5s0 ou wlp3s0. Si cette convention de nommage ne vous convient pas, vous pouvez implémenter la convention de nommage traditionnelle ou une personnalisée.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
In the new naming scheme, typical network device names are something like enp5s0 or wlp3s0. If this naming convention is not desired, the traditional naming scheme, or a custom scheme, can be implemented.
No novo esquema de nomenclatura, nomes típicos de dispositivo da rede de comunicação são alguma coisa como enp5s0 ou wlp3s0. Se essa convenção de nomenclatura não for desejada, [então] o esquema de nomenclatura tradicional, ou um esquema personalizado, pode ser implementado.
Linux From Scratch 12.3/chapter09_symlinks — English
Disabling Persistent Naming on the Kernel Command Line
Disabling Persistent Naming on the Kernel Command Line
Linux From Scratch 12.3/chapter09_symlinks — French
Disabling Persistent Naming on the Kernel Command Line
Désactiver la conservation des noms en ligne de commandes du noyau
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Disabling Persistent Naming on the Kernel Command Line
Desabilitando Nomenclatura Persistente na Linha de Comando do Núcleo
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
Disabling Persistent Naming on the Kernel Command Line
在内核命令行中禁用一致性命名
Linux From Scratch 12.3/chapter09_symlinks — English
The traditional naming scheme using eth0, eth1, etc. can be restored by adding <userinput>net.ifnames=0</userinput> on the kernel command line. This is most appropriate for systems that have just one ethernet device of a particular type. Laptops often have two ethernet connections named eth0 and wlan0; such laptops can also use this method. The command line is in the GRUB configuration file. See <xref linkend="grub-cfg" role='.'/>
The traditional naming scheme using eth0, eth1, etc. can be restored by adding <userinput>net.ifnames=0</userinput> on the kernel command line. This is most appropriate for systems that have just one ethernet device of a particular type. Laptops often have two ethernet connections named eth0 and wlan0; such laptops can also use this method. The command line is in the GRUB configuration file. See <xref linkend="grub-cfg" role='.'/>
Linux From Scratch 12.3/chapter09_symlinks — French
The traditional naming scheme using eth0, eth1, etc. can be restored by adding <userinput>net.ifnames=0</userinput> on the kernel command line. This is most appropriate for systems that have just one ethernet device of a particular type. Laptops often have two ethernet connections named eth0 and wlan0; such laptops can also use this method. The command line is in the GRUB configuration file. See <xref linkend="grub-cfg" role='.'/>
Vous pouvez rétablir la règle de nommage traditionnelle qui utilise eth0, eth1, etc. en ajoutant <userinput>net.ifnames=0</userinput> à la ligne de commande du noyau. Ceci est surtout adapté aux systèmes n'ayant qu'un périphérique ethernet d'un type particulier. Les ordinateurs portables ont souvent plusieurs ports ethernet appelés eth0 et wlan0, ils sont donc éligibles à cette méthode. La ligne de commande se trouve dans le fichier de configuration de GRUB. Voir <xref linkend="grub-cfg" role='.'/>
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
The traditional naming scheme using eth0, eth1, etc. can be restored by adding <userinput>net.ifnames=0</userinput> on the kernel command line. This is most appropriate for systems that have just one ethernet device of a particular type. Laptops often have two ethernet connections named eth0 and wlan0; such laptops can also use this method. The command line is in the GRUB configuration file. See <xref linkend="grub-cfg" role='.'/>
O esquema tradicional de nomenclatura usando eth0, eth1, etc., pode ser restaurado adicionando-se <userinput>net.ifnames=0</userinput> na linha de comando do núcleo. Isso é mais apropriado para sistemas que tenham apenas um dispositivo ethernet de um tipo específico. Laptops frequentemente tem duas conexões ethernet nomeadas de eth0 e wlan0; tais laptops também conseguem usar esse método. A linha de comando está no arquivo de configuração do GRUB. Veja-se <xref linkend="grub-cfg" role='.'/>
Linux From Scratch 12.3/chapter09_symlinks — English
Creating Custom Udev Rules
Creating Custom Udev Rules
Linux From Scratch 12.3/chapter09_symlinks — French
Creating Custom Udev Rules
Créer des règles Udev personnalisées
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Creating Custom Udev Rules
Criando Regras Personalizadas do Udev
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
Creating Custom Udev Rules
创建自定义 Udev 规则
Linux From Scratch 12.3/chapter09_symlinks — English
The naming scheme can be customized by creating custom udev rules. A script has been included that generates the initial rules. Generate these rules by running:
The naming scheme can be customized by creating custom udev rules. A script has been included that generates the initial rules. Generate these rules by running:
Linux From Scratch 12.3/chapter09_symlinks — French
The naming scheme can be customized by creating custom udev rules. A script has been included that generates the initial rules. Generate these rules by running:
Vous pouvez personnaliser les règles de nommage en créant des règles udev personnalisées. Un script est inclus pour générer les règles initiales. Générez ces règles en lançant&nbsp;:
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
The naming scheme can be customized by creating custom udev rules. A script has been included that generates the initial rules. Generate these rules by running:
O esquema de nomenclatura pode ser personalizado criando-se regras personalizadas do Udev. Um script foi incluído que gera as regras iniciais. Gere essas regras executando:
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
The naming scheme can be customized by creating custom udev rules. A script has been included that generates the initial rules. Generate these rules by running:
可以创建自定义 Udev 规则，定制命名架构。系统中包含一个生成初始规则的脚本，执行以下命令生成初始规则：
Linux From Scratch 12.3/chapter09_symlinks — English
<userinput>bash /usr/lib/udev/init-net-rules.sh</userinput>
<userinput>bash /usr/lib/udev/init-net-rules.sh</userinput>
Linux From Scratch 12.3/chapter09_symlinks — French
<userinput>bash /usr/lib/udev/init-net-rules.sh</userinput>
<userinput>bash /usr/lib/udev/init-net-rules.sh</userinput>
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<userinput>bash /usr/lib/udev/init-net-rules.sh</userinput>
<userinput>bash /usr/lib/udev/init-net-rules.sh</userinput>
Linux From Scratch 12.3/chapter09_symlinks — English
Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file, to find out which name was assigned to which network device:
Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file, to find out which name was assigned to which network device:
Linux From Scratch 12.3/chapter09_symlinks — French
Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file, to find out which name was assigned to which network device:
Maintenant, lisez le fichier <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> pour trouver le nom affecté à une carte réseau&nbsp;:
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file, to find out which name was assigned to which network device:
Agora, inspecione o arquivo <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>, para descobrir qual nome foi atribuído a qual dispositivo da rede de comunicação:
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file, to find out which name was assigned to which network device:
现在检查文件 <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>，确认网络设备与命名的对应关系：
Linux From Scratch 12.3/chapter09_symlinks — English
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
Linux From Scratch 12.3/chapter09_symlinks — French
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
<userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput>
Linux From Scratch 12.3/chapter09_symlinks — English
In some cases, such as when MAC addresses have been assigned to a network card manually, or in a virtual environment such as Qemu or Xen, the network rules file may not be generated because addresses are not consistently assigned. In these cases, this method cannot be used.
In some cases, such as when MAC addresses have been assigned to a network card manually, or in a virtual environment such as Qemu or Xen, the network rules file may not be generated because addresses are not consistently assigned. In these cases, this method cannot be used.
Linux From Scratch 12.3/chapter09_symlinks — French
In some cases, such as when MAC addresses have been assigned to a network card manually, or in a virtual environment such as Qemu or Xen, the network rules file may not be generated because addresses are not consistently assigned. In these cases, this method cannot be used.
Dans certains cas, comme lorsqu'une adresse MAC est affectée manuellement à une carte réseau ou dans un environnement virtuel tel que Qemu ou Xen, il se peut que le fichier des règles du réseau ne se génère pas car les adresses ne sont pas affectées de façon cohérente. Dans ces cas-là, vous ne pouvez pas utiliser cette méthode.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
In some cases, such as when MAC addresses have been assigned to a network card manually, or in a virtual environment such as Qemu or Xen, the network rules file may not be generated because addresses are not consistently assigned. In these cases, this method cannot be used.
Em alguns casos, tais como quando endereços MAC tenham sido atribuídos para uma placa de rede de comunicação manualmente, ou em um ambiente virtual, como Qemu ou Xen, o arquivo das regras da rede de comunicação possivelmente não seja gerado, pois endereços não são atribuídos consistentemente. Nesses casos, esse método não pode ser usado.
Linux From Scratch 12.3/chapter09_symlinks — English
The file begins with a comment block, followed by two lines for each NIC. The first line for each NIC is a commented description showing its hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card), along with its driver (in parentheses, if the driver can be found). Neither the hardware ID nor the driver is used to determine which name to give an interface; this information is only for reference. The second line is the udev rule that matches this NIC and actually assigns it a name.
The file begins with a comment block, followed by two lines for each NIC. The first line for each NIC is a commented description showing its hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card), along with its driver (in parentheses, if the driver can be found). Neither the hardware ID nor the driver is used to determine which name to give an interface; this information is only for reference. The second line is the udev rule that matches this NIC and actually assigns it a name.
Linux From Scratch 12.3/chapter09_symlinks — French
The file begins with a comment block, followed by two lines for each NIC. The first line for each NIC is a commented description showing its hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card), along with its driver (in parentheses, if the driver can be found). Neither the hardware ID nor the driver is used to determine which name to give an interface; this information is only for reference. The second line is the udev rule that matches this NIC and actually assigns it a name.
Le fichier commence par un bloc en commentaire suivi de deux lignes pour chaque carte réseau. La première ligne d'une carte réseau est une description commentée indiquant les ID matériel (comme l'ID PCI du fabricant et du périphérique s'il s'agit d'une carte PCI), et le pilote (entre parenthèses, si le pilote n'est pas détecté). L'ID matériel et le pilote ne déterminent pas le nom à donner à une interface&nbsp;; ces informations ne sont présentes qu'à titre informatif. La deuxième ligne est la règle udev correspondant à la carte réseau. Cette deuxième règle affecte le nom à l'interface.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
The file begins with a comment block, followed by two lines for each NIC. The first line for each NIC is a commented description showing its hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card), along with its driver (in parentheses, if the driver can be found). Neither the hardware ID nor the driver is used to determine which name to give an interface; this information is only for reference. The second line is the udev rule that matches this NIC and actually assigns it a name.
O arquivo começa com um bloco de comentário seguido por duas linhas para cada NIC. A primeira linha para cada NIC é uma descrição comentada mostrando os IDs de hardware delas (por exemplo, fornecedor(a) de PCI delas e IDs de dispositivo, se ela for uma placa PCI), juntamente com o controlador delas (entre parênteses, se o controlador puder ser encontrado). Nem o ID de hardware, nem o controlador, é usado para determinar quais nomes dar para uma interface; essa informação é somente para referência. A segunda linha é a regra do Udev que corresponde a essa NIC e atualmente atribui a ela um nome.
Linux From Scratch 12.3/chapter09_symlinks — English
All udev rules are made up of several keywords, separated by commas and optional whitespace. Here are the keywords, and an explanation of each one:
All udev rules are made up of several keywords, separated by commas and optional whitespace. Here are the keywords, and an explanation of each one:
Linux From Scratch 12.3/chapter09_symlinks — French
All udev rules are made up of several keywords, separated by commas and optional whitespace. Here are the keywords, and an explanation of each one:
Toutes les règles udev se composent de mots-clefs séparées par des virgules et éventuellement des espaces. Voici les mots-clefs avec leurs explications&nbsp;:
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
All udev rules are made up of several keywords, separated by commas and optional whitespace. Here are the keywords, and an explanation of each one:
Todas as regras do Udev são compostas de várias palavras chave, separadas por vírgulas e espaços em branco opcionais. Aqui estão as palavras chave e uma explicação de cada uma:
Linux From Scratch 12.3/chapter09_symlinks — English
<literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore devices that are not network cards.
<literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore devices that are not network cards.
Linux From Scratch 12.3/chapter09_symlinks — French
<literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore devices that are not network cards.
<literal>SUBSYSTEM=="net"</literal> — Ceci dit à udev d'ignorer les périphériques n'étant pas des cartes réseaux.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore devices that are not network cards.
<literal>SUBSYSTEM=="net"</literal> - Isso diz ao Udev para ignorar dispositivos que não sejam placas da rede de comunicação.
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
<literal>SUBSYSTEM=="net"</literal> - This tells udev to ignore devices that are not network cards.
<literal>SUBSYSTEM=="net"</literal> - 告诉 udev 忽略除网卡以外的设备。
Linux From Scratch 12.3/chapter09_symlinks — English
<literal>ACTION=="add"</literal> - This tells udev to ignore this rule for a uevent that isn't an add ("remove" and "change" uevents also happen, but don't need to rename network interfaces).
<literal>ACTION=="add"</literal> - This tells udev to ignore this rule for a uevent that isn't an add ("remove" and "change" uevents also happen, but don't need to rename network interfaces).
Linux From Scratch 12.3/chapter09_symlinks — French
<literal>ACTION=="add"</literal> - This tells udev to ignore this rule for a uevent that isn't an add ("remove" and "change" uevents also happen, but don't need to rename network interfaces).
<literal>ACTION=="add"</literal> — Ceci dit à udev d'ignorer la règle pour un uevent autre qu'un ajout (les uevents «&nbsp;remove&nbsp;» et «&nbsp;change&nbsp;» se produisent aussi mais il n'est pas utile de renommer les interfaces réseaux).
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<literal>ACTION=="add"</literal> - This tells udev to ignore this rule for a uevent that isn't an add ("remove" and "change" uevents also happen, but don't need to rename network interfaces).
<literal>ACTION=="add"</literal> - Isso diz ao Udev para ignorar essa regra para um uevent que não seja um adicionar (uevents "remover" e "mudar" também acontecem, porém não precisam renomear interfaces da rede de comunicação).
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
<literal>ACTION=="add"</literal> - This tells udev to ignore this rule for a uevent that isn't an add ("remove" and "change" uevents also happen, but don't need to rename network interfaces).
<literal>ACTION=="add"</literal> - 告诉 udev 忽略除了“添加”外的所有 uevent (也存在“删除”或“修改”类型的 uevent，但在这种情况下不需要重命名网络接口)。
Linux From Scratch 12.3/chapter09_symlinks — English
<literal>DRIVERS=="?*"</literal> - This exists so that udev will ignore VLAN or bridge sub-interfaces (because these sub-interfaces do not have drivers). These sub-interfaces are skipped because the name that would be assigned would collide with the parent devices.
<literal>DRIVERS=="?*"</literal> - This exists so that udev will ignore VLAN or bridge sub-interfaces (because these sub-interfaces do not have drivers). These sub-interfaces are skipped because the name that would be assigned would collide with the parent devices.
Linux From Scratch 12.3/chapter09_symlinks — French
<literal>DRIVERS=="?*"</literal> - This exists so that udev will ignore VLAN or bridge sub-interfaces (because these sub-interfaces do not have drivers). These sub-interfaces are skipped because the name that would be assigned would collide with the parent devices.
<literal>DRIVERS=="?*"</literal> — Ceci permet à udev d'ignorer les sous-interfaces VLAN ou les ponts (ces interfaces n'ont pas de pilote). Ces sous-interfaces sont ignorées car le nom qui leur serait affecté entrerait en conflit avec les périphériques parents.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<literal>DRIVERS=="?*"</literal> - This exists so that udev will ignore VLAN or bridge sub-interfaces (because these sub-interfaces do not have drivers). These sub-interfaces are skipped because the name that would be assigned would collide with the parent devices.
<literal>DRIVERS=="?*"</literal> - Isso existe, de forma que o Udev ignorará sub-interfaces VLAN ou bridge (pois essas sub-interfaces não tem controladores). Essas sub-interfaces são puladas, pois o nome que seria atribuído conflitaria com os dispositivos ancestrais delas.
Linux From Scratch 12.3/chapter09_symlinks — English
<literal>ATTR{address}</literal> - The value of this keyword is the NIC's MAC address.
<literal>ATTR{address}</literal> - The value of this keyword is the NIC's MAC address.
Linux From Scratch 12.3/chapter09_symlinks — French
<literal>ATTR{address}</literal> - The value of this keyword is the NIC's MAC address.
<literal>ATTR{address}</literal> - La valeur de ce mot-clé est l'adresse MAC de la carte réseau.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<literal>ATTR{address}</literal> - The value of this keyword is the NIC's MAC address.
<literal>ATTR{address}</literal> - O valor dessa palavra chave é o endereço MAC da NIC.
Linux From Scratch 12.3/chapter09_symlinks — English
<literal>ATTR{type}=="1"</literal> - This ensures the rule only matches the primary interface in the case of certain wireless drivers which create multiple virtual interfaces. The secondary interfaces are skipped for the same reason that VLAN and bridge sub-interfaces are skipped: there would be a name collision otherwise.
<literal>ATTR{type}=="1"</literal> - This ensures the rule only matches the primary interface in the case of certain wireless drivers which create multiple virtual interfaces. The secondary interfaces are skipped for the same reason that VLAN and bridge sub-interfaces are skipped: there would be a name collision otherwise.
Linux From Scratch 12.3/chapter09_symlinks — French
<literal>ATTR{type}=="1"</literal> - This ensures the rule only matches the primary interface in the case of certain wireless drivers which create multiple virtual interfaces. The secondary interfaces are skipped for the same reason that VLAN and bridge sub-interfaces are skipped: there would be a name collision otherwise.
<literal>ATTR{type}=="1"</literal> — Ceci garantit que la règle ne corresponde qu'à l'interface primaire au cas où certains pilotes sans fil créent plusieurs interfaces virtuelles. Les interfaces secondaires sont ignorées pour la même raison que l'on évite les sous-interfaces VLAN et les ponts&nbsp;: il y aurait conflit de noms.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<literal>ATTR{type}=="1"</literal> - This ensures the rule only matches the primary interface in the case of certain wireless drivers which create multiple virtual interfaces. The secondary interfaces are skipped for the same reason that VLAN and bridge sub-interfaces are skipped: there would be a name collision otherwise.
<literal>ATTR{type}=="1"</literal> - Isso garante que a regra corresponda somente à interface primária no caso de certos controladores sem fios os quais criam múltiplas interfaces virtuais. As interfaces secundárias são puladas pela mesma razão que sub-interfaces VLAN e bridge são puladas: existiria um conflito de nome do contrário.
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
<literal>ATTR{type}=="1"</literal> - This ensures the rule only matches the primary interface in the case of certain wireless drivers which create multiple virtual interfaces. The secondary interfaces are skipped for the same reason that VLAN and bridge sub-interfaces are skipped: there would be a name collision otherwise.
<literal>ATTR{type}=="1"</literal> - 这保证在使用创建多个虚拟接口的无线驱动程序时，只匹配主要接口。跳过其他接口的原因和忽略 VLAN 与桥接子接口一样，是为了防止命名冲突。
Linux From Scratch 12.3/chapter09_symlinks — English
<literal>NAME</literal> - The value of this keyword is the name that udev will assign to this interface.
<literal>NAME</literal> - The value of this keyword is the name that udev will assign to this interface.
Linux From Scratch 12.3/chapter09_symlinks — French
<literal>NAME</literal> - The value of this keyword is the name that udev will assign to this interface.
<literal>NAME</literal> - La valeur de ce mot-clé est le nom donné par udev à cette interface.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<literal>NAME</literal> - The value of this keyword is the name that udev will assign to this interface.
<literal>NAME</literal> - O valor dessa palavra chave é o nome que o Udev atribuirá para essa interface.
Linux From Scratch 12.3/chapter09_symlinks — English
The value of <literal>NAME</literal> is the important part. Make sure you know which name has been assigned to each of your network cards before proceeding, and be sure to use that <literal>NAME</literal> value when creating your network configuration files.
The value of <literal>NAME</literal> is the important part. Make sure you know which name has been assigned to each of your network cards before proceeding, and be sure to use that <literal>NAME</literal> value when creating your network configuration files.
Linux From Scratch 12.3/chapter09_symlinks — French
The value of <literal>NAME</literal> is the important part. Make sure you know which name has been assigned to each of your network cards before proceeding, and be sure to use that <literal>NAME</literal> value when creating your network configuration files.
La valeur de <literal>NAME</literal> est une partie très importante. Assurez-vous de connaître le nom affecté à chacune de vos cartes réseaux avant de continuer, et utilisez cette valeur <literal>NAME</literal> au moment de créer les fichiers de configuration.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
The value of <literal>NAME</literal> is the important part. Make sure you know which name has been assigned to each of your network cards before proceeding, and be sure to use that <literal>NAME</literal> value when creating your network configuration files.
O valor de <literal>NAME</literal> é a parte importante. Assegure-se de que você sabe qual nome foi atribuído para cada uma das suas placas da rede de comunicação antes de prosseguir, e tenha certeza de usar esse valor <literal>NAME</literal> quando criar seus arquivos de configuração da rede de comunicação.
Linux From Scratch 12.3/chapter09_symlinks — English
Even if the custom udev rule file is created, udev may still assign one or more alternative names for a NIC based on physical characteristics. If a custom udev rule would rename some NIC using a name already assigned as an alternative name of another NIC, this udev rule will fail. If this issue happens, you may create the <filename>/etc/udev/network/99-default.link</filename> configuration file with an empty alternative assignment policy, overriding the default configuration file <filename>/usr/lib/udev/network/99-default.link</filename>:
Even if the custom udev rule file is created, udev may still assign one or more alternative names for a NIC based on physical characteristics. If a custom udev rule would rename some NIC using a name already assigned as an alternative name of another NIC, this udev rule will fail. If this issue happens, you may create the <filename>/etc/udev/network/99-default.link</filename> configuration file with an empty alternative assignment policy, overriding the default configuration file <filename>/usr/lib/udev/network/99-default.link</filename>:
Linux From Scratch 12.3/chapter09_symlinks — French
Even if the custom udev rule file is created, udev may still assign one or more alternative names for a NIC based on physical characteristics. If a custom udev rule would rename some NIC using a name already assigned as an alternative name of another NIC, this udev rule will fail. If this issue happens, you may create the <filename>/etc/udev/network/99-default.link</filename> configuration file with an empty alternative assignment policy, overriding the default configuration file <filename>/usr/lib/udev/network/99-default.link</filename>:
Même si vous créez le fichier de règles personnalisé, udev peut toujours assigner un ou plusieurs noms alternatifs à la carte réseau en fonction de ses caractéristiques physiques. Si une règle udev personnalisée renomme certaines cartes réseau avec un nom déjà assigné en tant que nom alternatif d'une autre carte, la règle udev échouera. Si ce problème arrive, vous pouvez créer le fichier de configuration <filename>/etc/udev/network/99-default.link</filename> avec une autre politique d'assignation, qui remplace le fichier de configuration par défaut <filename>/usr/lib/udev/network/99-default.link</filename>&nbsp;:
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Even if the custom udev rule file is created, udev may still assign one or more alternative names for a NIC based on physical characteristics. If a custom udev rule would rename some NIC using a name already assigned as an alternative name of another NIC, this udev rule will fail. If this issue happens, you may create the <filename>/etc/udev/network/99-default.link</filename> configuration file with an empty alternative assignment policy, overriding the default configuration file <filename>/usr/lib/udev/network/99-default.link</filename>:
Mesmo se o arquivo de regras personalizadas do &quot;udev&quot; for criado, o &quot;udev&quot; possivelmente ainda atribuirá um ou mais nomes alternativos para uma &quot;NIC&quot; baseados nas características físicas. Se uma regra personalizada do &quot;udev&quot; renomeasse alguma &quot;NIC&quot; usando um nome já atribuído como um nome alternativo de outra &quot;NIC&quot;, [então] essa regra do &quot;udev&quot; falharia. Se esse problema ocorrer, [então] você poderá criar o arquivo de configuração &quot;<filename>/etc/udev/network/99-default.link</filename>&quot; com uma política de atribuição alternativa vazia, substituindo o arquivo de configuração padrão &quot;<filename>/usr/lib/ udev/network/99-default.link</filename>&quot;:
Linux From Scratch 12.3/chapter09_symlinks — English
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
Linux From Scratch 12.3/chapter09_symlinks — French
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
Linux From Scratch 12.3/chapter09_symlinks — English
CD-ROM Symlinks
CD-ROM Symlinks
Linux From Scratch 12.3/chapter09_symlinks — French
CD-ROM Symlinks
Liens symboliques vers le CD-ROM
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
CD-ROM Symlinks
Links Simbólicos de CD-ROM
Linux From Scratch 12.3/chapter09_symlinks — English
Some software that you may want to install later (e.g., various media players) expects the <filename class="symlink">/dev/cdrom</filename> and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put references to those symlinks into <filename>/etc/fstab</filename>. Udev comes with a script that will generate rules files to create these symlinks for you, depending on the capabilities of each device, but you need to decide which of two modes of operation you wish to have the script use.
Some software that you may want to install later (e.g., various media players) expects the <filename class="symlink">/dev/cdrom</filename> and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put references to those symlinks into <filename>/etc/fstab</filename>. Udev comes with a script that will generate rules files to create these symlinks for you, depending on the capabilities of each device, but you need to decide which of two modes of operation you wish to have the script use.
Linux From Scratch 12.3/chapter09_symlinks — French
Some software that you may want to install later (e.g., various media players) expects the <filename class="symlink">/dev/cdrom</filename> and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put references to those symlinks into <filename>/etc/fstab</filename>. Udev comes with a script that will generate rules files to create these symlinks for you, depending on the capabilities of each device, but you need to decide which of two modes of operation you wish to have the script use.
Certains logiciels que vous pourriez vouloir installer ultérieurement (comme divers lecteurs multimédias) s'attendent à ce que les liens symboliques <filename class="symlink">/dev/cdrom</filename> et <filename class="symlink">/dev/dvd</filename> existent et pointent vers le lecteur CD-ROM ou DVD-ROM. De plus, il peut être pratique d'insérer des références à ces liens symboliques dans <filename>/etc/fstab</filename>. Udev est fourni avec un script qui génèrera des fichiers de règles pour créer ces liens symboliques à votre place, selon les possibilités de chaque périphérique, mais vous devez décider lequel des deux modes opératoires vous souhaitez que le script utilise.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
Some software that you may want to install later (e.g., various media players) expects the <filename class="symlink">/dev/cdrom</filename> and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put references to those symlinks into <filename>/etc/fstab</filename>. Udev comes with a script that will generate rules files to create these symlinks for you, depending on the capabilities of each device, but you need to decide which of two modes of operation you wish to have the script use.
Alguns aplicativos que você possivelmente queira instalar posteriormente (por exemplo, vários reprodutores de mídia) esperam que os links simbólicos <filename class="symlink">/dev/cdrom</filename> e <filename class="symlink">/dev/dvd</filename> existam, e apontem para um dispositivo de CD-ROM ou de DVD-ROM. Também, possivelmente seja conveniente colocar referências a esses links simbólicos em <filename>/etc/fstab</filename>. O Udev vem com um script que gerará arquivos de regras para criar esses links simbólicos para você, dependendo dos recursos de cada dispositivo, mas você precisa decidir qual dos dois modos de operação você deseja ter para o script usar.
Linux From Scratch 12.3/chapter09_symlinks — English
First, the script can operate in <quote>by-path</quote> mode (used by default for USB and FireWire devices), where the rules it creates depend on the physical path to the CD or DVD device. Second, it can operate in <quote>by-id</quote> mode (default for IDE and SCSI devices), where the rules it creates depend on identification strings stored on the CD or DVD device itself. The path is determined by udev's <command>path_id</command> script, and the identification strings are read from the hardware by its <command>ata_id</command> or <command>scsi_id</command> programs, depending on which type of device you have.
First, the script can operate in <quote>by-path</quote> mode (used by default for USB and FireWire devices), where the rules it creates depend on the physical path to the CD or DVD device. Second, it can operate in <quote>by-id</quote> mode (default for IDE and SCSI devices), where the rules it creates depend on identification strings stored on the CD or DVD device itself. The path is determined by udev's <command>path_id</command> script, and the identification strings are read from the hardware by its <command>ata_id</command> or <command>scsi_id</command> programs, depending on which type of device you have.
Linux From Scratch 12.3/chapter09_symlinks — French
First, the script can operate in <quote>by-path</quote> mode (used by default for USB and FireWire devices), where the rules it creates depend on the physical path to the CD or DVD device. Second, it can operate in <quote>by-id</quote> mode (default for IDE and SCSI devices), where the rules it creates depend on identification strings stored on the CD or DVD device itself. The path is determined by udev's <command>path_id</command> script, and the identification strings are read from the hardware by its <command>ata_id</command> or <command>scsi_id</command> programs, depending on which type of device you have.
Tout d'abord, le script peut opérer en mode <quote>chemin</quote> (utilisé par défaut pour les périphériques USB et FireWire), où les règles qu'il crée dépendent du chemin physique vers le lecteur CD ou DVD. Ensuite, il peut opérer en mode <quote>id</quote> (par défaut pour les périphériques IDE et SCSI), où les règles qu'il crée dépendent des chaînes d'identification contenues dans le lecteur CD ou DVD lui-même. Le chemin est déterminé par le script <command>path_id</command> d'Udev, et les chaînes d'identification sont lues à partir du matériel par ses programmes <command>ata_id</command> ou <command>scsi_id</command>, selon le type de périphérique que vous possédez.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
First, the script can operate in <quote>by-path</quote> mode (used by default for USB and FireWire devices), where the rules it creates depend on the physical path to the CD or DVD device. Second, it can operate in <quote>by-id</quote> mode (default for IDE and SCSI devices), where the rules it creates depend on identification strings stored on the CD or DVD device itself. The path is determined by udev's <command>path_id</command> script, and the identification strings are read from the hardware by its <command>ata_id</command> or <command>scsi_id</command> programs, depending on which type of device you have.
Primeiro, o script pode operar em modo <quote>por-caminho</quote> (usado por padrão para dispositivos USB e FireWire), onde as regras que ele cria dependem do caminho físico para o dispositivo de CD ou de DVD. Segundo, ele pode operar em modo <quote>por-id</quote> (padrão para dispositivos IDE e SCSI), onde as regras que ele cria dependem das sequências de caracteres de identificação armazenadas no próprio dispositivo de CD ou de DVD. O caminho é determinado pelo script <command>path_id</command> do Udev, e as sequências de caracteres de identificação são lidas a partir do hardware pelos aplicativos <command>ata_id</command> ou <command>scsi_id</command> dele, dependendo de qual tipo de dispositivo você tenha.
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
First, the script can operate in <quote>by-path</quote> mode (used by default for USB and FireWire devices), where the rules it creates depend on the physical path to the CD or DVD device. Second, it can operate in <quote>by-id</quote> mode (default for IDE and SCSI devices), where the rules it creates depend on identification strings stored on the CD or DVD device itself. The path is determined by udev's <command>path_id</command> script, and the identification strings are read from the hardware by its <command>ata_id</command> or <command>scsi_id</command> programs, depending on which type of device you have.
首先，该脚本可以在 <quote>by-path</quote> 模式下运行 (这是 USB 和 FireWire 设备的默认模式)，此时它创建的规则依赖于 CD 或 DVD 设备的物理路径。其次，它可以在 <quote>by-id</quote> 模式下运行，此时它创建的规则依赖于 CD 或 DVD 设备本身存储的识别字符串。物理路径由 udev 的 <command>path_id</command> 脚本确定，而识别字符串由 <command>ata_id</command> 或 <command>scsi_id</command> 程序 (根据设备类型选用其中一个) 从硬件中读取。
Linux From Scratch 12.3/chapter09_symlinks — English
There are advantages to each approach; the correct approach depends on what kinds of device changes may happen. If you expect the physical path to the device (that is, the ports and/or slots that it plugs into) to change, for example because you plan on moving the drive to a different IDE port or a different USB connector, then you should use the <quote>by-id</quote> mode. On the other hand, if you expect the device's identification to change, for example because it may die, and you intend to replace it with a different device that plugs into the same connectors, then you should use the <quote>by-path</quote> mode.
There are advantages to each approach; the correct approach depends on what kinds of device changes may happen. If you expect the physical path to the device (that is, the ports and/or slots that it plugs into) to change, for example because you plan on moving the drive to a different IDE port or a different USB connector, then you should use the <quote>by-id</quote> mode. On the other hand, if you expect the device's identification to change, for example because it may die, and you intend to replace it with a different device that plugs into the same connectors, then you should use the <quote>by-path</quote> mode.
Linux From Scratch 12.3/chapter09_symlinks — French
There are advantages to each approach; the correct approach depends on what kinds of device changes may happen. If you expect the physical path to the device (that is, the ports and/or slots that it plugs into) to change, for example because you plan on moving the drive to a different IDE port or a different USB connector, then you should use the <quote>by-id</quote> mode. On the other hand, if you expect the device's identification to change, for example because it may die, and you intend to replace it with a different device that plugs into the same connectors, then you should use the <quote>by-path</quote> mode.
Il existe des avantages pour chaque approche&nbsp;; la bonne approche à utiliser dépend des types de changements de périphérique qui peuvent se produire. Si vous vous attendez à ce que le chemin physique vers le périphérique (c'est-à-dire, les ports ou les fentes par lesquels ils sont branchés) change, par exemple parce que vous envisagez de déplacer le lecteur sur un port IDE différent ou un connecteur USB différent, alors vous devriez utiliser le mode <quote>by-id</quote>. D'un autre côté, si vous vous attendez à ce que l'identification du périphérique change, par exemple parce qu'il ne marche plus, et que vous le remplaciez par un périphérique différent avec les mêmes capacités et qui serait monté sur les mêmes connecteurs, vous devriez utiliser le mode <quote>by-path</quote>.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
There are advantages to each approach; the correct approach depends on what kinds of device changes may happen. If you expect the physical path to the device (that is, the ports and/or slots that it plugs into) to change, for example because you plan on moving the drive to a different IDE port or a different USB connector, then you should use the <quote>by-id</quote> mode. On the other hand, if you expect the device's identification to change, for example because it may die, and you intend to replace it with a different device that plugs into the same connectors, then you should use the <quote>by-path</quote> mode.
Existem vantagens para cada abordagem; a abordagem correta depende de que tipos de mudanças de dispositivo possivelmente aconteçam. Se você espera o caminho físico para o dispositivo (isto é, as portas e (ou) slots aos quais ele se pluga) mudar, por exemplo porque você planeja mover a unidade para uma porta IDE diferente ou um conector USB diferente, então você deveria usar o modo <quote>por-id</quote>. Por outro lado, se você espera que a identificação do dispositivo mude, por exemplo porque ele possivelmente morra, e você pretende substitui-lo por um dispositivo diferente que pluga nos mesmos conectores, então você deveria usar o modo <quote>por-caminho</quote>.
Linux From Scratch 12.3/chapter09_symlinks — English
If either type of change is possible with your drive, then choose a mode based on the type of change you expect to happen more often.
If either type of change is possible with your drive, then choose a mode based on the type of change you expect to happen more often.
Linux From Scratch 12.3/chapter09_symlinks — French
If either type of change is possible with your drive, then choose a mode based on the type of change you expect to happen more often.
Si les deux types de changement sont possibles avec votre lecteur, choisissez un mode basé sur le type de changement que vous pensez rencontrer le plus fréquemment.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
If either type of change is possible with your drive, then choose a mode based on the type of change you expect to happen more often.
Se ambos os tipos de mudanças são possíveis com a sua unidade, então escolha um modo baseado no tipo de mudança que você espera acontecer mais frequentemente.
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
If either type of change is possible with your drive, then choose a mode based on the type of change you expect to happen more often.
如果两种变化都可能发生，则根据您预期较常发生的变化选择模式。
Linux From Scratch 12.3/chapter09_symlinks — English
External devices (for example, a USB-connected CD drive) should not use by-path persistence, because each time the device is plugged into a new external port, its physical path will change. All externally-connected devices will have this problem if you write udev rules to recognize them by their physical path; the problem is not limited to CD and DVD drives.
External devices (for example, a USB-connected CD drive) should not use by-path persistence, because each time the device is plugged into a new external port, its physical path will change. All externally-connected devices will have this problem if you write udev rules to recognize them by their physical path; the problem is not limited to CD and DVD drives.
Linux From Scratch 12.3/chapter09_symlinks — French
External devices (for example, a USB-connected CD drive) should not use by-path persistence, because each time the device is plugged into a new external port, its physical path will change. All externally-connected devices will have this problem if you write udev rules to recognize them by their physical path; the problem is not limited to CD and DVD drives.
Les périphériques externes (par exemple un lecteur CD connecté en USB) ne devraient pas utiliser la méthode des chemins, car chaque fois que le périphérique est monté sur un nouveau port, son chemin physique change. Tous les périphériques connectés en externe auront ce problème si vous écrivez des règles udev pour les reconnaître par leur chemin physique&nbsp;; le problème ne concerne pas que les lecteurs CD et DVD.
Linux From Scratch 12.3/chapter09_symlinks — Portuguese (Brazil)
External devices (for example, a USB-connected CD drive) should not use by-path persistence, because each time the device is plugged into a new external port, its physical path will change. All externally-connected devices will have this problem if you write udev rules to recognize them by their physical path; the problem is not limited to CD and DVD drives.
Dispositivos externos (por exemplo, uma unidade de CD conectada via USB) não deveria usar persistência por caminho, porque cada vez que o dispositivo for plugado em uma nova porta externa, o caminho físico dele mudará. Todos os dispositivos conectados externamente terão esse problema se você escrever regras do Udev para reconhecê-los pelo caminho físico deles; o problema não está limitado a unidades de CD e de DVD.
Linux From Scratch 12.3/chapter09_symlinks — Chinese (Simplified Han script)
External devices (for example, a USB-connected CD drive) should not use by-path persistence, because each time the device is plugged into a new external port, its physical path will change. All externally-connected devices will have this problem if you write udev rules to recognize them by their physical path; the problem is not limited to CD and DVD drives.
外接设备 (例如 USB 接口的 CD 驱动器) 不应使用 by-path 模式，因为每次将该设备插入到新的外部接口时，其物理路径都可能变化。只要您使用了基于物理路径识别外接设备的 udev 规则，都会导致这个问题，并不仅限于 CD 或 DVD 设备。