Translation Source string Target string
Linux From Scratch/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/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/chapter04_aboutsbus — English
On some newer systems, the motherboard is capable of controlling the system clock speed. This can be controlled with a command such as <command>powerprofilesctl</command>. This is not available in LFS, but may be available on the host distro. After LFS is complete, it can be added to a system with the procedures at the <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'> BLFS power-profiles-daemon</ulink> page. Before measuring the build time of any package it is advisable to use a system power profile set for maximum performance (and maximum power consumption). Otherwise the measured SBU value may be inaccurate because the system may react differently when building <xref linkend='ch-tools-binutils-pass1'/> or other packages. Be aware that a significant inaccuracy can still show up even if the same profile is used for both packages because the system may respond slower if the system is idle when starting the build procedure. Setting the power profile to <quote>performance</quote> will minimize this problem. And obviously doing so will also make the system build LFS faster.
On some newer systems, the motherboard is capable of controlling the system clock speed. This can be controlled with a command such as <command>powerprofilesctl</command>. This is not available in LFS, but may be available on the host distro. After LFS is complete, it can be added to a system with the procedures at the <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'> BLFS power-profiles-daemon</ulink> page. Before measuring the build time of any package it is advisable to use a system power profile set for maximum performance (and maximum power consumption). Otherwise the measured SBU value may be inaccurate because the system may react differently when building <xref linkend='ch-tools-binutils-pass1'/> or other packages. Be aware that a significant inaccuracy can still show up even if the same profile is used for both packages because the system may respond slower if the system is idle when starting the build procedure. Setting the power profile to <quote>performance</quote> will minimize this problem. And obviously doing so will also make the system build LFS faster.
Linux From Scratch/chapter04_aboutsbus — French
On some newer systems, the motherboard is capable of controlling the system clock speed. This can be controlled with a command such as <command>powerprofilesctl</command>. This is not available in LFS, but may be available on the host distro. After LFS is complete, it can be added to a system with the procedures at the <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'> BLFS power-profiles-daemon</ulink> page. Before measuring the build time of any package it is advisable to use a system power profile set for maximum performance (and maximum power consumption). Otherwise the measured SBU value may be inaccurate because the system may react differently when building <xref linkend='ch-tools-binutils-pass1'/> or other packages. Be aware that a significant inaccuracy can still show up even if the same profile is used for both packages because the system may respond slower if the system is idle when starting the build procedure. Setting the power profile to <quote>performance</quote> will minimize this problem. And obviously doing so will also make the system build LFS faster.
Sur certains systèmes récents, la carte mère peut contrôler la vitesse de l'horloge système. Cela peut être contrôlé avec une commande comme <command>powerprofilesctl</command>. Elle n'est pas disponible dans LFS, mais peut être disponible sur la distribution hôte. Après la complétion de LFS, elle peut être ajoutée au système avec les procédures de la page <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'>BLFS sur power-profiles-daemon</ulink>. Avant de mesurer le temps de construction d'un paquet il est recommandé d'utiliser un profil d'énergie système configuré pour les performances maximum (et la consommation d'énergie maximum). Sinon les SBU mesurés peuvent être imprécis car le système peut réagir différemment lors de la construction de <xref linkend='ch-tools-binutils-pass1'/> ou d'autres paquets. Soyez conscient qu'un grand nombre d'imprécisions peut toujours apparaître même si le même profil est utilisé pour les deux paquets car le système peut répondre plus lentement si le système est en attente lorsque la procédure de construction démarre. Utiliser le profil d'énergie <quote>performance</quote> minimisera ce problème. Évidemment, cela accélérera également la construction de LFS.
Linux From Scratch/chapter04_aboutsbus — Portuguese (Brazil)
On some newer systems, the motherboard is capable of controlling the system clock speed. This can be controlled with a command such as <command>powerprofilesctl</command>. This is not available in LFS, but may be available on the host distro. After LFS is complete, it can be added to a system with the procedures at the <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'> BLFS power-profiles-daemon</ulink> page. Before measuring the build time of any package it is advisable to use a system power profile set for maximum performance (and maximum power consumption). Otherwise the measured SBU value may be inaccurate because the system may react differently when building <xref linkend='ch-tools-binutils-pass1'/> or other packages. Be aware that a significant inaccuracy can still show up even if the same profile is used for both packages because the system may respond slower if the system is idle when starting the build procedure. Setting the power profile to <quote>performance</quote> will minimize this problem. And obviously doing so will also make the system build LFS faster.
Em alguns sistemas mais novos, a placa-mãe é capaz de controlar a velocidade do clock do sistema. Isso pode ser controlado com um comando como <command>powerprofilesctl</command>. Isso não está disponível no LFS, mas pode estar disponível na distribuição anfitriã. Depois que o LFS estiver completo, ele pode ser adicionado a um sistema com os procedimentos na página <ulink url='&blfs-book;sysutils/power-profiles-daemon.html'>power-profiles-daemon do BLFS</ulink>. Antes de mensurar o tempo de construção de qualquer pacote, é aconselhável usar um perfil de eletricidade do sistema configurado para desempenho máximo (e consumo máximo de eletricidade). Caso contrário, o valor da UPC mensurado pode ser impreciso porque o sistema pode reagir diferentemente ao construir <xref linkend='ch-tools-binutils-pass1'/> ou outros pacotes. Esteja ciente de que uma imprecisão significativa ainda pode aparecer mesmo se o mesmo perfil for usado para ambos os pacotes, porque o sistema pode responder mais lentamente se estiver ocioso ao iniciar o procedimento de construção. Configurar o perfil de eletricidade para <quote>performance</quote> minimizará esse problema. E, obviamente, fazer isso também fará com que o sistema construa o LFS mais rápido.
Linux From Scratch/chapter01_whatsnew — English
Expat-&expat-version;
Expat-&expat-version;
Linux From Scratch/chapter01_whatsnew — French
Expat-&expat-version;
Expat-&expat-version;
Linux From Scratch/chapter01_whatsnew — Portuguese (Brazil)
Expat-&expat-version;
Expat-&expat-version;
Linux From Scratch/prologue_standards — English
The LSB has four separate specifications: Core, Desktop, Languages, and Imaging. Some parts of Core and Desktop specifications are architecture specific. There are also two trial specifications: Gtk3 and Graphics. LFS attempts to conform to the LSB specifications for the IA32 (32-bit x86) or AMD64 (x86_64) architectures discussed in the previous section.
The LSB has four separate specifications: Core, Desktop, Languages, and Imaging. Some parts of Core and Desktop specifications are architecture specific. There are also two trial specifications: Gtk3 and Graphics. LFS attempts to conform to the LSB specifications for the IA32 (32-bit x86) or AMD64 (x86_64) architectures discussed in the previous section.
Linux From Scratch/prologue_standards — French
The LSB has four separate specifications: Core, Desktop, Languages, and Imaging. Some parts of Core and Desktop specifications are architecture specific. There are also two trial specifications: Gtk3 and Graphics. LFS attempts to conform to the LSB specifications for the IA32 (32-bit x86) or AMD64 (x86_64) architectures discussed in the previous section.
La LSB comporte quatre spécifications distinctes&nbsp;: le cœur, le bureau, les langages et l'impression. Certaines parties des spécifications du cœur et du bureau comportent des exigences qui s'appliquent à la construction. Il y a aussi deux spécifications pour l'évaluation&nbsp;: Gtk3 et les graphismes. LFS s'applique à respecter les constructions IA32 (32-bit x86) ou AMD64 (x86_64) qui ont été évoquées dans la section précédente.
Linux From Scratch/prologue_standards — Portuguese (Brazil)
The LSB has four separate specifications: Core, Desktop, Languages, and Imaging. Some parts of Core and Desktop specifications are architecture specific. There are also two trial specifications: Gtk3 and Graphics. LFS attempts to conform to the LSB specifications for the IA32 (32-bit x86) or AMD64 (x86_64) architectures discussed in the previous section.
O LSB tem quatro especificações separadas: Core, Desktop, Languages e Imaging. Algumas partes das especificações Core e Desktop são específicas de arquitetura. Existem também duas especificações experimentais: Gtk3 e Graphics. O LFS tenta obedecer às especificações da LSB para as arquiteturas IA32 (x86 de 32 bits) ou AMD64 (x86_64) discutidas na sessão anterior.
Linux From Scratch/chapter01_changelog — English
[bdubbs] - Update to vim-9.1.0866. Addresses <ulink url='&lfs-ticket-root;4500'>#4500</ulink>.
[bdubbs] - Update to vim-9.1.0866. Addresses <ulink url='&lfs-ticket-root;4500'>#4500</ulink>.
Linux From Scratch/chapter01_changelog — French
[bdubbs] - Update to vim-9.1.0866. Addresses <ulink url='&lfs-ticket-root;4500'>#4500</ulink>.
[bdubbs] — Mise à jour vers vim-9.01.0866. Corrige <ulink url='&lfs-ticket-root;4500'>#4500</ulink>.
Linux From Scratch/chapter01_changelog — Portuguese (Brazil)
[bdubbs] - Update to vim-9.1.0866. Addresses <ulink url='&lfs-ticket-root;4500'>#4500</ulink>.
[bdubbs] - Atualização para vim-9.1.0866. Endereça <ulink url='&lfs-ticket-root;4500'>#4500</ulink>.
Linux From Scratch/chapter02_stages — English
The /mnt/lfs partition must be mounted.
The /mnt/lfs partition must be mounted.
Linux From Scratch/chapter02_stages — French
The /mnt/lfs partition must be mounted.
La partition /mnt/lfs doit être montée.
Linux From Scratch/chapter02_stages — Chinese (Simplified Han script)
The /mnt/lfs partition must be mounted.
/mnt/lfs 分区需要重新挂载。
Linux From Scratch/chapter02_hostreqs — English
<emphasis role="strong">Bash-3.2</emphasis> (/bin/sh should be a symbolic or hard link to bash)
<emphasis role="strong">Bash-3.2</emphasis> (/bin/sh should be a symbolic or hard link to bash)
Linux From Scratch/chapter02_hostreqs — French
<emphasis role="strong">Bash-3.2</emphasis> (/bin/sh should be a symbolic or hard link to bash)
<emphasis role="strong">Bash-3.2</emphasis> (/bin/sh doit être un lien symbolique ou matériel vers bash)
Linux From Scratch/chapter02_hostreqs — Chinese (Simplified Han script)
<emphasis role="strong">Bash-3.2</emphasis> (/bin/sh should be a symbolic or hard link to bash)
<emphasis role="strong">Bash-3.2</emphasis> (/bin/sh 必须是到 bash 的符号链接或硬连接)
Linux From Scratch/chapter02_mounting — English
If you are using multiple partitions for LFS (e.g., one for <filename class="directory">/</filename> and another for <filename class="directory">/home</filename>), mount them like this:
If you are using multiple partitions for LFS (e.g., one for <filename class="directory">/</filename> and another for <filename class="directory">/home</filename>), mount them like this:
Linux From Scratch/chapter02_mounting — French
If you are using multiple partitions for LFS (e.g., one for <filename class="directory">/</filename> and another for <filename class="directory">/home</filename>), mount them like this:
Si vous utilisez plusieurs partitions pour LFS (par exemple une pour <filename class="directory">/</filename> et une autre pour <filename class="directory">/home</filename>), montez-les en utilisant&nbsp;:
Linux From Scratch/chapter02_creatingpartition — English
Remember the designation of the new partition (e.g., <filename class="devicefile">sda5</filename>). This book will refer to this as the LFS partition. Also remember the designation of the <systemitem class="filesystem">swap</systemitem> partition. These names will be needed later for the <filename>/etc/fstab</filename> file.
Remember the designation of the new partition (e.g., <filename class="devicefile">sda5</filename>). This book will refer to this as the LFS partition. Also remember the designation of the <systemitem class="filesystem">swap</systemitem> partition. These names will be needed later for the <filename>/etc/fstab</filename> file.
Linux From Scratch/chapter02_creatingpartition — French
Remember the designation of the new partition (e.g., <filename class="devicefile">sda5</filename>). This book will refer to this as the LFS partition. Also remember the designation of the <systemitem class="filesystem">swap</systemitem> partition. These names will be needed later for the <filename>/etc/fstab</filename> file.
Retenez bien la désignation de la nouvelle partition (par exemple <filename class="devicefile">sda5</filename>). Elle sera référencée dans ce livre comme partition LFS. Gardez également en mémoire la désignation de la partition <systemitem class="filesystem">swap</systemitem>. Ces noms vous seront utiles pour le fichier <filename>/etc/fstab</filename>.
Linux From Scratch/chapter02_creatingpartition — Chinese (Simplified Han script)
Remember the designation of the new partition (e.g., <filename class="devicefile">sda5</filename>). This book will refer to this as the LFS partition. Also remember the designation of the <systemitem class="filesystem">swap</systemitem> partition. These names will be needed later for the <filename>/etc/fstab</filename> file.
牢记新分区的代号 (例如 <filename class="devicefile">sda5</filename> )。本书将这个分区称为 LFS 分区。还需要记住 <systemitem class="filesystem">swap</systemitem> 分区的代号。之后在设置 <filename>/etc/fstab</filename> 文件时要用到这些代号。
Linux From Scratch/chapter02_creatingfilesystem — English
is an upgrade to ext2 that includes a journal to help recover the partition's status in the case of an unclean shutdown. It is commonly used as a general purpose file system.
is an upgrade to ext2 that includes a journal to help recover the partition's status in the case of an unclean shutdown. It is commonly used as a general purpose file system.
Linux From Scratch/chapter02_creatingfilesystem — French
is an upgrade to ext2 that includes a journal to help recover the partition's status in the case of an unclean shutdown. It is commonly used as a general purpose file system.
est une mise à jour d’ext2 qui comprend un journal aidant à récupérer l'état de la partition en cas d'arrêt brutal. Ce type est communément employé dans une perspective généraliste.
Linux From Scratch/chapter02_creatingfilesystem — Chinese (Simplified Han script)
is an upgrade to ext2 that includes a journal to help recover the partition's status in the case of an unclean shutdown. It is commonly used as a general purpose file system.
是 ext2 的升级版本，拥有日志系统，能够在非正常关机的情况下恢复分区的正常状态。它被广泛用于一般场合。
Linux From Scratch/chapter02_aboutlfs — English
Make sure the output shows the path to your LFS system's build location, which is <filename class="directory">/mnt/lfs</filename> if the provided example was followed. If the output is incorrect, use the command given earlier on this page to set <envar>$LFS</envar> to the correct directory name.
Make sure the output shows the path to your LFS system's build location, which is <filename class="directory">/mnt/lfs</filename> if the provided example was followed. If the output is incorrect, use the command given earlier on this page to set <envar>$LFS</envar> to the correct directory name.
Linux From Scratch/chapter02_aboutlfs — French
Make sure the output shows the path to your LFS system's build location, which is <filename class="directory">/mnt/lfs</filename> if the provided example was followed. If the output is incorrect, use the command given earlier on this page to set <envar>$LFS</envar> to the correct directory name.
Assurez-vous que la sortie affiche le chemin du répertoire dans lequel vous construisez votre système LFS, qui est <filename class="directory">/mnt/lfs</filename> si vous avez suivi l'exemple fourni. Si la sortie indique le mauvais répertoire, utilisez la commande précédemment indiquée dans cette page pour associer la variable <envar>$LFS</envar> au bon répertoire.
Linux From Scratch/chapter02_aboutlfs — Chinese (Simplified Han script)
Make sure the output shows the path to your LFS system's build location, which is <filename class="directory">/mnt/lfs</filename> if the provided example was followed. If the output is incorrect, use the command given earlier on this page to set <envar>$LFS</envar> to the correct directory name.
确认该命令的输出是您构建 LFS 的位置，如果您使用本书提供的例子，那么输出应该是 <filename class="directory">/mnt/lfs</filename>。如果输出不正确，使用前文给出的命令，将 <envar>$LFS</envar> 设置成正确的目录名。
Linux From Scratch/chapter07_createfiles — English
/var/log/wtmp
/var/log/wtmp
Linux From Scratch/chapter07_createfiles — French
/var/log/wtmp
/var/log/wtmp
Linux From Scratch/chapter07_createfiles — Chinese (Simplified Han script)
/var/log/wtmp
/var/log/wtmp
Linux From Scratch/chapter07_texinfo — English
&diskspace;
&diskspace;
Linux From Scratch/chapter07_texinfo — French
&diskspace;
&diskspace;
Linux From Scratch/chapter07_texinfo — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter07_kernfs — English
During a normal boot of an LFS system, the kernel automatically mounts the <systemitem class="filesystem">devtmpfs</systemitem> file system on the <filename class="directory">/dev</filename> directory; the kernel creates device nodes on that virtual file system during the boot process, or when a device is first detected or accessed. The udev daemon may change the ownership or permissions of the device nodes created by the kernel, and create new device nodes or symlinks, to ease the work of distro maintainers and system administrators. (See <xref linkend='ch-config-udev-device-node-creation'/> for details.) If the host kernel supports &devtmpfs;, we can simply mount a &devtmpfs; at <filename class='directory'>$LFS/dev</filename> and rely on the kernel to populate it.
During a normal boot of an LFS system, the kernel automatically mounts the <systemitem class="filesystem">devtmpfs</systemitem> file system on the <filename class="directory">/dev</filename> directory; the kernel creates device nodes on that virtual file system during the boot process, or when a device is first detected or accessed. The udev daemon may change the ownership or permissions of the device nodes created by the kernel, and create new device nodes or symlinks, to ease the work of distro maintainers and system administrators. (See <xref linkend='ch-config-udev-device-node-creation'/> for details.) If the host kernel supports &devtmpfs;, we can simply mount a &devtmpfs; at <filename class='directory'>$LFS/dev</filename> and rely on the kernel to populate it.
Linux From Scratch/chapter07_kernfs — French
During a normal boot of an LFS system, the kernel automatically mounts the <systemitem class="filesystem">devtmpfs</systemitem> file system on the <filename class="directory">/dev</filename> directory; the kernel creates device nodes on that virtual file system during the boot process, or when a device is first detected or accessed. The udev daemon may change the ownership or permissions of the device nodes created by the kernel, and create new device nodes or symlinks, to ease the work of distro maintainers and system administrators. (See <xref linkend='ch-config-udev-device-node-creation'/> for details.) If the host kernel supports &devtmpfs;, we can simply mount a &devtmpfs; at <filename class='directory'>$LFS/dev</filename> and rely on the kernel to populate it.
Lors d'un démarrage normal d'un système LFS, le noyau monte automatiquement le système de fichiers <systemitem class="filesystem">devtmpfs</systemitem> dans le répertoire <filename class="directory">/dev</filename> et crée des nœuds de périphériques sur ce système de fichiers virtuel pendant le processus de démarrage ou lorsqu’un périphérique est détecté ou qu'on tente d'y pour la première fois. Le démon udev permet de modifier le propriétaire, de gérer les permissions des nœuds de périphériques créés par le noyau, d’en créer de nouveaux ou de créer des liens symboliques afin de faciliter la tâche de maintenance de distribution ou d'administration système (voir le <xref linkend='ch-config-udev-device-node-creation'/> pour plus de détails). Si le noyau hôte prend en charge &devtmpfs;, il est possible de monter un &devtmpfs; sous <filename class='directory'>$LFS/dev</filename> et ainsi laisser le noyau le remplir.
Linux From Scratch/chapter07_util-linux — English
&buildtime;
&buildtime;
Linux From Scratch/chapter07_util-linux — French
&buildtime;
&buildtime;
Linux From Scratch/chapter07_util-linux — Chinese (Simplified Han script)
&buildtime;
&buildtime;
Linux From Scratch/chapter07_cleanup — English
The current system size is now about 3 GB, however the /tools directory is no longer needed. It uses about 1 GB of disk space. Delete it now:
The current system size is now about 3 GB, however the /tools directory is no longer needed. It uses about 1 GB of disk space. Delete it now:
Linux From Scratch/chapter07_cleanup — French
The current system size is now about 3 GB, however the /tools directory is no longer needed. It uses about 1 GB of disk space. Delete it now:
La taille du système est maintenant d'environ 3&nbsp;Go, mais le répertoire /tools n'est plus requis. Il utilise environ 1&nbsp;Go d'espace disque. Supprimez-le maintenant&nbsp;:
Linux From Scratch/chapter07_perl — English
&diskspace;
&diskspace;
Linux From Scratch/chapter07_perl — French
&diskspace;
&diskspace;
Linux From Scratch/chapter07_perl — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter07_chroot — English
Notice that <filename class="directory">/tools/bin</filename> is not in the <envar>PATH</envar>. This means that the cross toolchain will no longer be used.
Notice that <filename class="directory">/tools/bin</filename> is not in the <envar>PATH</envar>. This means that the cross toolchain will no longer be used.
Linux From Scratch/chapter07_chroot — French
Notice that <filename class="directory">/tools/bin</filename> is not in the <envar>PATH</envar>. This means that the cross toolchain will no longer be used.
Remarquez que <filename class="directory">/tools/bin</filename> n'est pas dans le <envar>PATH</envar>. Ceci signifie que la chaîne d'outils croisée ne sera plus utilisée.
Linux From Scratch/chapter07_gettext — English
&diskspace;
&diskspace;
Linux From Scratch/chapter07_gettext — French
&diskspace;
&diskspace;
Linux From Scratch/chapter07_gettext — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter07_python — English
&diskspace;
&diskspace;
Linux From Scratch/chapter07_python — French
&diskspace;
&diskspace;
Linux From Scratch/chapter07_python — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter07_bison — English
&diskspace;
&diskspace;
Linux From Scratch/chapter07_bison — French
&diskspace;
&diskspace;
Linux From Scratch/chapter07_bison — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter10_grub — English
Ensure that an emergency boot disk is ready to <quote>rescue</quote> the computer if the computer becomes unusable (un-bootable). If you do not already have a boot device, you can create one. In order for the procedure below to work, you need to jump ahead to BLFS and install <userinput>xorriso</userinput> from the <ulink url="&blfs-book;multimedia/libisoburn.html"> libisoburn</ulink> package.
Ensure that an emergency boot disk is ready to <quote>rescue</quote> the computer if the computer becomes unusable (un-bootable). If you do not already have a boot device, you can create one. In order for the procedure below to work, you need to jump ahead to BLFS and install <userinput>xorriso</userinput> from the <ulink url="&blfs-book;multimedia/libisoburn.html"> libisoburn</ulink> package.
Linux From Scratch/chapter10_grub — French
Ensure that an emergency boot disk is ready to <quote>rescue</quote> the computer if the computer becomes unusable (un-bootable). If you do not already have a boot device, you can create one. In order for the procedure below to work, you need to jump ahead to BLFS and install <userinput>xorriso</userinput> from the <ulink url="&blfs-book;multimedia/libisoburn.html"> libisoburn</ulink> package.
Assurez-vous d'avoir un disque de démarrage de façon à pouvoir <quote>dépanner</quote> l'ordinateur si celui-ci devenait inutilisable (non amorçable). Si vous n'avez pas déjà de périphérique de démarrage, vous pouvez en créer un. Afin que la procédure ci-dessous fonctionne, vous devez faire un tour du côté de BLFS et installer <userinput>xorriso</userinput> qui est dans le paquet <ulink url="&blfs-book;multimedia/libisoburn.html">libisoburn</ulink>.
Linux From Scratch/chapter10_grub — Chinese (Simplified Han script)
Ensure that an emergency boot disk is ready to <quote>rescue</quote> the computer if the computer becomes unusable (un-bootable). If you do not already have a boot device, you can create one. In order for the procedure below to work, you need to jump ahead to BLFS and install <userinput>xorriso</userinput> from the <ulink url="&blfs-book;multimedia/libisoburn.html"> libisoburn</ulink> package.
您务必保证自己拥有一个紧急引导磁盘，它在计算机不可用 (无法引导) 时能够 <quote>抢修</quote> 计算机。如果您现在还没有引导设备，您可以执行以下命令创建一个。在运行下列命令前，您需要跳到 BLFS，安装包含 <userinput>xorriso</userinput> 的 <ulink url="&blfs-book;multimedia/libisoburn.html">libisoburn</ulink> 软件包：
Linux From Scratch/chapter10_kernel — English
&diskspace;
&diskspace;
Linux From Scratch/chapter10_kernel — French
&diskspace;
&diskspace;
Linux From Scratch/chapter10_kernel — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter10_fstab — English
Filesystems with MS-DOS or Windows origin (i.e. vfat, ntfs, smbfs, cifs, iso9660, udf) need a special option, utf8, in order for non-ASCII characters in file names to be interpreted properly. For non-UTF-8 locales, the value of <option>iocharset</option> should be set to be the same as the character set of the locale, adjusted in such a way that the kernel understands it. This works if the relevant character set definition (found under File systems -&gt; Native Language Support when configuring the kernel) has been compiled into the kernel or built as a module. However, if the character set of the locale is UTF-8, the corresponding option <option>iocharset=utf8</option> would make the file system case sensitive. To fix this, use the special option <option>utf8</option> instead of <option>iocharset=utf8</option>, for UTF-8 locales. The <quote>codepage</quote> option is also needed for vfat and smbfs filesystems. It should be set to the codepage number used under MS-DOS in your country. For example, in order to mount USB flash drives, a ru_RU.KOI8-R user would need the following in the options portion of its mount line in <filename>/etc/fstab</filename>:
Filesystems with MS-DOS or Windows origin (i.e. vfat, ntfs, smbfs, cifs, iso9660, udf) need a special option, utf8, in order for non-ASCII characters in file names to be interpreted properly. For non-UTF-8 locales, the value of <option>iocharset</option> should be set to be the same as the character set of the locale, adjusted in such a way that the kernel understands it. This works if the relevant character set definition (found under File systems -&gt; Native Language Support when configuring the kernel) has been compiled into the kernel or built as a module. However, if the character set of the locale is UTF-8, the corresponding option <option>iocharset=utf8</option> would make the file system case sensitive. To fix this, use the special option <option>utf8</option> instead of <option>iocharset=utf8</option>, for UTF-8 locales. The <quote>codepage</quote> option is also needed for vfat and smbfs filesystems. It should be set to the codepage number used under MS-DOS in your country. For example, in order to mount USB flash drives, a ru_RU.KOI8-R user would need the following in the options portion of its mount line in <filename>/etc/fstab</filename>:
Linux From Scratch/chapter10_fstab — French
Filesystems with MS-DOS or Windows origin (i.e. vfat, ntfs, smbfs, cifs, iso9660, udf) need a special option, utf8, in order for non-ASCII characters in file names to be interpreted properly. For non-UTF-8 locales, the value of <option>iocharset</option> should be set to be the same as the character set of the locale, adjusted in such a way that the kernel understands it. This works if the relevant character set definition (found under File systems -&gt; Native Language Support when configuring the kernel) has been compiled into the kernel or built as a module. However, if the character set of the locale is UTF-8, the corresponding option <option>iocharset=utf8</option> would make the file system case sensitive. To fix this, use the special option <option>utf8</option> instead of <option>iocharset=utf8</option>, for UTF-8 locales. The <quote>codepage</quote> option is also needed for vfat and smbfs filesystems. It should be set to the codepage number used under MS-DOS in your country. For example, in order to mount USB flash drives, a ru_RU.KOI8-R user would need the following in the options portion of its mount line in <filename>/etc/fstab</filename>:
Les systèmes de fichiers ayant pour origine MS-DOS ou Windows (c-à-d. vfat, ntfs, smbfs, cifs, iso9660, udf) ont besoin d'une option spéciale, utf8, pour que les caractères non-ascii dans les noms de fichiers soient interprétés correctement. Pour les paramètres linguistiques non-utf-8, la valeur de <option>iocharset</option> devrait être la même que le jeu de caractères de votre locale, ajustée de telle sorte que le noyau la comprenne. Cela fonctionne si la définition du codage adéquat (que vous trouverez sous File systems -&gt; Native Language Support lors de la configuration du noyau) a été compilée en dur dans le noyau ou en module. Cependant, si le jeu de caractères des paramètres linguistiques est UTF-8, l'option correspondante <option>iocharset=utf8</option> rendrait le système de fichier sensible à la casse. Pour corriger cela, utilisez l'option spéciale <option>utf8</option> au lieu de <option>iocharset=utf8</option> pour les paramètres linguistiques UTF-8. L'option <quote>codepage</quote> est aussi nécessaire aux systèmes de fichiers vfat et smbfs. Elle devrait être paramétrée pour correspondre à la page de code utilisée sous MS-DOS dans votre pays. Par exemple, pour monter des lecteurs flash USB, un utilisateur ru_RU.KOI8-R aurait besoin de ce qui suit dans la partie des options de sa ligne de montage dans <filename>/etc/fstab</filename>&nbsp;:
Linux From Scratch/chapter10_fstab — Chinese (Simplified Han script)
Filesystems with MS-DOS or Windows origin (i.e. vfat, ntfs, smbfs, cifs, iso9660, udf) need a special option, utf8, in order for non-ASCII characters in file names to be interpreted properly. For non-UTF-8 locales, the value of <option>iocharset</option> should be set to be the same as the character set of the locale, adjusted in such a way that the kernel understands it. This works if the relevant character set definition (found under File systems -&gt; Native Language Support when configuring the kernel) has been compiled into the kernel or built as a module. However, if the character set of the locale is UTF-8, the corresponding option <option>iocharset=utf8</option> would make the file system case sensitive. To fix this, use the special option <option>utf8</option> instead of <option>iocharset=utf8</option>, for UTF-8 locales. The <quote>codepage</quote> option is also needed for vfat and smbfs filesystems. It should be set to the codepage number used under MS-DOS in your country. For example, in order to mount USB flash drives, a ru_RU.KOI8-R user would need the following in the options portion of its mount line in <filename>/etc/fstab</filename>:
在挂载来源于 MS-DOS 或 Windows 的文件系统 (如 vfat、ntfs、smbfs、cifs、iso9660、udf) 时，需要一个特殊的挂载选项 —— utf8，才能正常解析文件名中的非 ASCII 字符。对于非 UTF-8 locale，选项 <option>iocharset</option> 的值应该和您的 locale 字符集设定一致，但改写成内核可以识别的写法。该选项能够正常工作的前提是，将相关的字符集定义 (在内核配置选项的 File Systems -&gt; Native Language Support 子菜单中) 编译到内核中，或构建为内核模块。然而，如果使用了 UTF-8 locale，对应的 <option>iocharset=utf8</option> 会导致文件系统变得大小写敏感。为了避免这个问题，在使用 UTF-8 locale 时，需要用特殊选项 <option>utf8</option> 代替 <option>iocharset=utf8</option>。另外，vfat 和 smbfs 文件系统还需要<quote>codepage</quote>选项，它应该被设定为您的语言在 MS-DOS 下的代码页编号。例如，为了挂载一个 USB 闪存盘，一个 ru_RU.KOI8-R 用户应该在 <filename>/etc/fstab</filename> 中对应于闪存盘的行添加下列挂载选项：
Linux From Scratch/appendices_dependencies — English
The last list of dependencies are optional packages that are not addressed in LFS, but could be useful to the user. These packages may have additional mandatory or optional dependencies of their own. For these dependencies, the recommended practice is to install them after completion of the LFS book and then go back and rebuild the LFS package. In several cases, re-installation is addressed in BLFS.
The last list of dependencies are optional packages that are not addressed in LFS, but could be useful to the user. These packages may have additional mandatory or optional dependencies of their own. For these dependencies, the recommended practice is to install them after completion of the LFS book and then go back and rebuild the LFS package. In several cases, re-installation is addressed in BLFS.
Linux From Scratch/appendices_dependencies — French
The last list of dependencies are optional packages that are not addressed in LFS, but could be useful to the user. These packages may have additional mandatory or optional dependencies of their own. For these dependencies, the recommended practice is to install them after completion of the LFS book and then go back and rebuild the LFS package. In several cases, re-installation is addressed in BLFS.
La dernière liste de dépendances répertorie les paquets facultatifs qui ne sont pas destinées à LFS mais qui pourraient vous être utiles. Ces paquets peuvent avoir eux-mêmes des dépendances supplémentaires obligatoires ou facultatives. Pour ces dépendances, la pratique recommandée consiste à les installer après avoir terminé le livre LFS puis à revenir en arrière pour reconstruire le paquet LFS. Dans certains cas, la réinstallation est traitée dans BLFS.
Linux From Scratch/appendices_creat-comm — English
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
Linux From Scratch/appendices_creat-comm — French
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
Linux From Scratch/appendices_creat-comm — Chinese (Simplified Han script)
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HERE, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE LICENSOR GRANTS YOU THE RIGHTS CONTAINED HERE IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS.
Linux From Scratch/appendices_acronymlist — English
Automated Linux From Scratch
Automated Linux From Scratch
Linux From Scratch/appendices_acronymlist — French
Automated Linux From Scratch
<foreignphrase>Automated Linux From Scratch</foreignphrase>
Linux From Scratch/appendices_acronymlist — Chinese (Simplified Han script)
Automated Linux From Scratch
Automated Linux From Scratch
Linux From Scratch/appendices_scripts — English
/lib/lsb/init-functions
/lib/lsb/init-functions
Linux From Scratch/appendices_scripts — French
/lib/lsb/init-functions
/lib/lsb/init-functions
Linux From Scratch/appendices_scripts — Chinese (Simplified Han script)
/lib/lsb/init-functions
/lib/lsb/init-functions
Linux From Scratch/appendices_acknowledgments — English
<ulink url="mailto:pierre@linuxfromscratch.org">Pierre Labastie</ulink> &lt;pierre@linuxfromscratch.org&gt; &ndash; BLFS Editor and ALFS Lead
<ulink url="mailto:pierre@linuxfromscratch.org">Pierre Labastie</ulink> &lt;pierre@linuxfromscratch.org&gt; &ndash; BLFS Editor and ALFS Lead
Linux From Scratch/appendices_acknowledgments — French
<ulink url="mailto:pierre@linuxfromscratch.org">Pierre Labastie</ulink> &lt;pierre@linuxfromscratch.org&gt; &ndash; BLFS Editor and ALFS Lead
<ulink url="mailto:pierre@linuxfromscratch.org">Pierre Labastie</ulink> &lt;pierre@linuxfromscratch.org&gt; &ndash; Rédacteur de BLFS et meneur de ALFS
Linux From Scratch/appendices_acknowledgments — Chinese (Simplified Han script)
<ulink url="mailto:pierre@linuxfromscratch.org">Pierre Labastie</ulink> &lt;pierre@linuxfromscratch.org&gt; &ndash; BLFS Editor and ALFS Lead
<ulink url="mailto:pierre@linuxfromscratch.org">Pierre Labastie</ulink> &lt;pierre@linuxfromscratch.org&gt; &ndash; BLFS 编辑及 ALFS 负责人
Linux From Scratch/chapter04_creatingminlayout — English
The LFS editors have deliberately decided not to use a <filename class="directory">/usr/lib64</filename> directory. Several steps are taken to be sure the toolchain will not use it. If for any reason this directory appears (either because you made an error in following the instructions, or because you installed a binary package that created it after finishing LFS), it may break your system. You should always be sure this directory does not exist.
The LFS editors have deliberately decided not to use a <filename class="directory">/usr/lib64</filename> directory. Several steps are taken to be sure the toolchain will not use it. If for any reason this directory appears (either because you made an error in following the instructions, or because you installed a binary package that created it after finishing LFS), it may break your system. You should always be sure this directory does not exist.
Linux From Scratch/chapter04_creatingminlayout — French
The LFS editors have deliberately decided not to use a <filename class="directory">/usr/lib64</filename> directory. Several steps are taken to be sure the toolchain will not use it. If for any reason this directory appears (either because you made an error in following the instructions, or because you installed a binary package that created it after finishing LFS), it may break your system. You should always be sure this directory does not exist.
Les éditeurs de LFS ont choisi délibérément de ne pas utiliser de répertoire <filename class="directory">/usr/lib64</filename>. Plusieurs mesures sont prises pour s'assurer que la chaine d'outils ne l'utilisera pas. Si pour une quelconque raison ce répertoire apparaît (soit parce que vous avez fait une erreur en suivant les instructions, soit parce que vous avez installé un paquet binaire qui l'a créé après avoir fini LFS), cela pourrait casser votre système. Vous devriez toujours vous assurer que ce répertoire n'existe pas.
Linux From Scratch/chapter04_settingenviron — English
The meaning of the settings in <filename>.bashrc</filename>
The meaning of the settings in <filename>.bashrc</filename>
Linux From Scratch/chapter04_settingenviron — French
The meaning of the settings in <filename>.bashrc</filename>
Voici la signification des paramètres du fichier <filename>.bashrc</filename>
Linux From Scratch/chapter04_settingenviron — Chinese (Simplified Han script)
The meaning of the settings in <filename>.bashrc</filename>
<filename>.bashrc</filename> 中设定的含义：
Linux From Scratch/chapter04_addinguser — English
<parameter>-g lfs</parameter>
<parameter>-g lfs</parameter>
Linux From Scratch/chapter04_addinguser — French
<parameter>-g lfs</parameter>
<parameter>-g lfs</parameter>
Linux From Scratch/chapter04_addinguser — Chinese (Simplified Han script)
<parameter>-g lfs</parameter>
<parameter>-g lfs</parameter>
Linux From Scratch/chapter08_intltool — English
&diskspace;
&diskspace;
Linux From Scratch/chapter08_intltool — French
&diskspace;
&diskspace;
Linux From Scratch/chapter08_intltool — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter08_autoconf — English
&diskspace;
&diskspace;
Linux From Scratch/chapter08_autoconf — French
&diskspace;
&diskspace;
Linux From Scratch/chapter08_autoconf — Chinese (Simplified Han script)
&diskspace;
&diskspace;
Linux From Scratch/chapter08_wheel — English
&diskspace;
&diskspace;
Linux From Scratch/chapter08_wheel — French
&diskspace;
&diskspace;
Linux From Scratch/chapter08_gmp — English
&diskspace;
&diskspace;
Linux From Scratch/chapter08_gmp — French
&diskspace;
&diskspace;
Linux From Scratch/chapter08_gmp — Chinese (Simplified Han script)
&diskspace;
&diskspace;