2. Linux From Scratch
3. chapter09_udev
4. Portuguese (Brazil)

This is due to the fact that udev, by design, handles uevents and loads modules in parallel, and thus in an unpredictable order. This will never be <quote>fixed.</quote> You should not rely upon the kernel device names being stable. Instead, create your own rules that make symlinks with stable names based on some stable attributes of the device, such as a serial number or the output of various *_id utilities installed by udev. See <xref linkend="ch-config-symlinks"/> and <xref linkend="ch-config-network"/> for examples.

Isso é devido ao fato de o Udev&quot;Udev&quot;, pelo projeto, lidar com &quot;uevents&quot; e carregar módulos em paralelo e, assim, em uma ordem imprevisível. Isso nunca será <quote>corrigido</quote>. Você não deveria confiar nos nomes de dispositivos do núcleo sendo estáveis. Em vez disso, crie sas tuas próprias regras que fazem links simbólicos com nomes estáveis baseados em alguns atributos estáveis do dispositivo, tais como um número de série ou a saída gerada dos vários utilitários *_id&quot;*_id&quot; instalados pelo Udev&quot;Udev&quot;. Veja-se a &quot;<xref linkend="ch-config-symlinks"/> e &quot; e &quot;<xref linkend="ch-config-network"/>&quot; para exemplos.

Note that the <quote>softdep</quote> command also allows <literal>pre:</literal> dependencies, or a mixture of both <literal>pre:</literal> and <literal>post:</literal> dependencies. See the <ulink role='man' url='&man;modprobe.d.5'>modprobe.d(5)</ulink> manual page for more information on <quote>softdep</quote> syntax and capabilities.

Observe que o comando <quote>softdep</quote> também permite dependências &quot;<literal>pre:</literal>&quot;, ou uma mistura de ambas as dependências &quot;<literal>pre:</literal> e &quot; e &quot;<literal>post:</literal>&quot;. Veja-se a página de manual <filename&quot;<ulink role='man' url='&man;modprobe.d.5'>modprobe.d(5)</filename>ulink>&quot; para mais informação a respeito da sintaxe e recursos do <quote>softdep</quote>.

Device drivers compiled as modules may have aliases built into them. Aliases are visible in the output of the <command>modinfo</command> program and are usually related to the bus-specific identifiers of devices supported by a module. For example, the <emphasis>snd-fm801</emphasis> driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801, and has an alias of <literal>pci:v00001319d00000801sv*sd*bc04sc01i*</literal>. For most devices, the bus driver exports the alias of the driver that would handle the device via <systemitem class="filesystem">sysfs</systemitem>. E.g., the <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file might contain the string <literal>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</literal>. The default rules provided with udev will cause <command>udevd</command> to call out to <command>/sbin/modprobe</command> with the contents of the <envar>MODALIAS</envar> uevent environment variable (which should be the same as the contents of the <filename>modalias</filename> file in sysfs), thus loading all modules whose aliases match this string after wildcard expansion.

Controladores de dispositivo compilados como módulos possivelmente tenham apelidos construídos dentro deles. Apelidos são visíveis na saída gerada do aplicativo &quot;<command>modinfo</command>&quot; e geralmente estão relacionados aos identificadores específicos ao barramento dos dispositivos suportados por um módulo. Por exemplo, o controlador &quot;<emphasis>snd-fm801</emphasis>&quot; suporta dispositivos PCI com ID de fornecedor 0x1319 e ID de dispositivo 0x0801&quot;PCI&quot; com &quot;ID&quot; de fornecedor &quot;0x1319&quot; e &quot;ID&quot; de dispositivo &quot;0x0801&quot; e tem um apelido de <&quote;<literal>pci:v00001319d00000801sv*sd*bc04sc01i*</literal>&quote>;. Para a maioria dos dispositivos, o controlador de barramento exporta o apelido do controlador que lidaria com o dispositivo via &quot;<systemitem class="filesystem">sysfs</systemitem>&quot;. Por exemplo, o arquivo &quot;<filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename>&quot; pode conter a sequência de caracteres <&quote;<literal>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</literal>&quote>;. As regras padrão fornecidas com o Udev&quot;Udev&quot; causarão o &quot;<command>udevd</command>&quot; chamar &quot;<command>/sbin/modprobe</command>&quot; com o conteúdo da variável de ambiente do uevent &quot;uevent&quot; &quot;<envar>MODALIAS</envar>&quot; (o qual deveria ser o mesmo que o conteúdo do arquivo &quot;<filename>modalias</filename> em sysfs&quot; em &quot;sysfs&quot;), dessa forma carregando todos os módulos cujos apelidos correspondeam a essa sequência de caracteres depois da expansão de carácter curinga.

This is due to the fact that udev, by design, handles uevents and loads modules in parallel, and thus in an unpredictable order. This will never be <quote>fixed.</quote> You should not rely upon the kernel device names being stable. Instead, create your own rules that make symlinks with stable names based on some stable attributes of the device, such as a serial number or the output of various *_id utilities installed by udev. See <xref linkend="ch-config-symlinks"/> and <xref linkend="ch-config-network"/> for examples.

Isso é devido ao fato de o Udev, pelo projeto, lidar com uevents e carregar módulos em paralelo e, assim, em uma ordem imprevisível. Isso nunca será <quote>corrigido</quote>. Você não deveria confiar nos nomes de dispositivos do núcleo sendo estáveis. Em vez disso, crie suas próprias regras que fazem links simbólicos com nomes estáveis baseados em alguns atributos estáveis do dispositivo, tais como um número de série ou a saída gerada dos vários utilitários *_id instalados pelo Udev. Veja-se a <xref linkend="ch-config-symlinks"/> e <xref linkend="ch-config-network"/> para exemplos.

This is due to the fact that udev, by design, handles uevents and loads modules in parallel, and thus in an unpredictable order. This will never be <quote>fixed.</quote>. You should not rely upon the kernel device names being stable. Instead, create your own rules that make symlinks with stable names based on some stable attributes of the device, such as a serial number or the output of various *_id utilities installed by udev. See <xref linkend="ch-config-symlinks"/> and <xref linkend="ch-config-network"/> for examples.

Device drivers compiled as modules may have aliases built into them. Aliases are visible in the output of the <command>modinfo</command> program and are usually related to the bus-specific identifiers of devices supported by a module. For example, the <emphasis>snd-fm801</emphasis> driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801, and has an alias of <literal>pci:v00001319d00000801sv*sd*bc04sc01i*</literal>. For most devices, the bus driver exports the alias of the driver that would handle the device via <systemitem class="filesystem">sysfs</systemitem>. E.g., the <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file might contain the string <literal>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</literal>. The default rules provided with udev will cause <command>udevd</command> to call out to <command>/sbin/modprobe</command> with the contents of the <envar>MODALIAS</envar> uevent environment variable (which should be the same as the contents of the <filename>modalias</filename> file in sysfs), thus loading all modules whose aliases match this string after wildcard expansion.

Controladores de dispositivo compilados como módulos possivelmente tenham apelidos construídos dentro deles. Apelidos são visíveis na saída gerada do aplicativo <command>modinfo</command> e geralmente estão relacionados aos identificadores específicos ao barramento dos dispositivos suportados por um módulo. Por exemplo, o controlador <emphasis>snd-fm801</emphasis> suporta dispositivos PCI com ID de fornecedor 0x1319 e ID de dispositivo 0x0801 e tem um apelido de <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>. Para a maioria dos dispositivos, o controlador de barramento exporta o apelido do controlador que lidaria com o dispositivo via <systemitem class="filesystem">sysfs</systemitem>. Por exemplo, o arquivo <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> pode conter a sequência de caracteres <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>. As regras padrão fornecidas com o Udev causarão <command>udevd</command> chamar <command>/sbin/modprobe</command> com o conteúdo da variável de ambiente do uevent <envar>MODALIAS</envar> (o qual deveria ser o mesmo que o conteúdo do arquivo <filename>modalias</filename> em sysfs), dessa forma carregando todos os módulos cujos apelidos correspondem a essa sequência de caracteres depois da expansão de carácter curinga.

Device drivers compiled as modules may have aliases built into them. Aliases are visible in the output of the <command>modinfo</command> program and are usually related to the bus-specific identifiers of devices supported by a module. For example, the <emphasis>snd-fm801</emphasis> driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801, and has an alias of <quoteliteral>pci:v00001319d00000801sv*sd*bc04sc01i*</quoteliteral>. For most devices, the bus driver exports the alias of the driver that would handle the device via <systemitem class="filesystem">sysfs</systemitem>. E.g., the <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file might contain the string <quoteliteral>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quoteliteral>. The default rules provided with udev will cause <command>udevd</command> to call out to <command>/sbin/modprobe</command> with the contents of the <envar>MODALIAS</envar> uevent environment variable (which should be the same as the contents of the <filename>modalias</filename> file in sysfs), thus loading all modules whose aliases match this string after wildcard expansion.