2. Beyond Linux From Scratch 12.0
3. introduction_important_building-notes
4. Search

Filters

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

state:>=translated

Position and priority

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

	Translation	Source string	Target string
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Notes on Building Software	Notes on Building Software
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Notes on Building Software	Remarques sur la construction de logiciels
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Notes on Building Software	Observações Acerca de Construir Software
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Those people who have built an LFS system may be aware of the general principles of downloading and unpacking software. Some of that information is repeated here for those new to building their own software.	Those people who have built an LFS system may be aware of the general principles of downloading and unpacking software. Some of that information is repeated here for those new to building their own software.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Those people who have built an LFS system may be aware of the general principles of downloading and unpacking software. Some of that information is repeated here for those new to building their own software.	Celles et ceux qui ont construit un système LFS connaissent sans doute les principes généraux du téléchargement et de l'extraction de logiciel. Certaines de ces informations sont répétées ici pour les nouveaux qui construisent leurs propres logiciels.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Those people who have built an LFS system may be aware of the general principles of downloading and unpacking software. Some of that information is repeated here for those new to building their own software.	Aquelas pessoas que tenham construído um sistema LFS possivelmente estejam cientes dos princípios gerais da transferência e do desempacotamento de software. Alguma daquela informação está repetida aqui para aquelas novatas em construir o próprio software delas.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Each set of installation instructions contains a URL from which you can download the package. The patches; however, are stored on the LFS servers and are available via HTTP. These are referenced as needed in the installation instructions.	Each set of installation instructions contains a URL from which you can download the package. The patches; however, are stored on the LFS servers and are available via HTTP. These are referenced as needed in the installation instructions.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Each set of installation instructions contains a URL from which you can download the package. The patches; however, are stored on the LFS servers and are available via HTTP. These are referenced as needed in the installation instructions.	Chaque ensemble d'instructions d'installation contient une URL sur laquelle laquelle vous pouvez télécharger le paquet. Cependant, les correctifs sont enregistrés sur les serveurs LFS et disponibles via HTTP. Ces derniers sont référencés, si besoin, dans les instructions d'installation.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Each set of installation instructions contains a URL from which you can download the package. The patches; however, are stored on the LFS servers and are available via HTTP. These are referenced as needed in the installation instructions.	Cada conjunto de instruções de instalação contém um URL a partir do qual você pode transferir o pacote. Os remendos, no entanto, estão armazenados nos servidores do LFS e estão disponíveis via HTTP. Esses estão referenciados conforme necessários nas instruções de instalação.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	While you can keep the source files anywhere you like, we assume that you have unpacked the package and changed into the directory created by the unpacking process (the source directory). We also assume you have uncompressed any required patches and they are in the directory immediately above the source directory.	While you can keep the source files anywhere you like, we assume that you have unpacked the package and changed into the directory created by the unpacking process (the source directory). We also assume you have uncompressed any required patches and they are in the directory immediately above the source directory.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	While you can keep the source files anywhere you like, we assume that you have unpacked the package and changed into the directory created by the unpacking process (the source directory). We also assume you have uncompressed any required patches and they are in the directory immediately above the source directory.	Même si vous pouvez placer les fichiers sources où vous voulez, nous supposons que vous avez extrait le paquet et êtes allé dans le répertoire créé par le processus de décompression (le répertoire des sources). Nous supposons aussi que vous avez décompressé les correctifs requis et qu'ils sont dans le répertoire directement au-dessus du répertoire des sources.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	While you can keep the source files anywhere you like, we assume that you have unpacked the package and changed into the directory created by the unpacking process (the source directory). We also assume you have uncompressed any required patches and they are in the directory immediately above the source directory.	Embora possa manter os arquivos do fonte onde quiser, presumimos que você desempacotou o pacote e mudou para o diretório criado pelo processo de desempacotamento (o diretório do fonte). Também presumimos que você descomprimiu quaisquer remendos exigidos e que eles estão no diretório imediatamente acima do diretório do fonte.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	We can not emphasize strongly enough that you should start from a <emphasis>clean source tree</emphasis> each time. This means that if you have had an error during configuration or compilation, it's usually best to delete the source tree and re-unpack it <emphasis>before</emphasis> trying again. This obviously doesn't apply if you're an advanced user used to hacking <filename>Makefile</filename>s and C code, but if in doubt, start from a clean tree.	We can not emphasize strongly enough that you should start from a <emphasis>clean source tree</emphasis> each time. This means that if you have had an error during configuration or compilation, it's usually best to delete the source tree and re-unpack it <emphasis>before</emphasis> trying again. This obviously doesn't apply if you're an advanced user used to hacking <filename>Makefile</filename>s and C code, but if in doubt, start from a clean tree.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	We can not emphasize strongly enough that you should start from a <emphasis>clean source tree</emphasis> each time. This means that if you have had an error during configuration or compilation, it's usually best to delete the source tree and re-unpack it <emphasis>before</emphasis> trying again. This obviously doesn't apply if you're an advanced user used to hacking <filename>Makefile</filename>s and C code, but if in doubt, start from a clean tree.	Nous ne saurions que trop vous recommander de démarrer à partir d'une <emphasis>arborescence de sources propre</emphasis> à chaque fois. Cela veut dire que si vous avez eu une erreur lors de la configuration ou de la compilation, il est généralement préférable de supprimer l'arborescence des sources et de l'extraire de nouveau <emphasis>avant</emphasis> de réessayer. Cela ne s'applique évidemment pas si vous êtes un utilisateur avancé habitué à modifier les <filename>Makefile</filename>s et le code C. Si vous avez un doute cependant, commencez à partir d'une arborescence propre.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	We can not emphasize strongly enough that you should start from a <emphasis>clean source tree</emphasis> each time. This means that if you have had an error during configuration or compilation, it's usually best to delete the source tree and re-unpack it <emphasis>before</emphasis> trying again. This obviously doesn't apply if you're an advanced user used to hacking <filename>Makefile</filename>s and C code, but if in doubt, start from a clean tree.	Nós não podemos enfatizar fortemente o suficiente que você deveria iniciar a partir de uma <emphasis>árvore limpa do fonte</emphasis> a cada vez. Isso significa que, se você tiver tido um erro durante a configuração ou a compilação, [então] geralmente é melhor deletar a árvore do fonte e desempacotá-la outra vez <emphasis>antes de</emphasis> tentar novamente. Isso, obviamente, não se aplica se você for um(a) usuário(a) avançado(a) habituado(a) a hackear <filename>Makefile</filename>s e código C; porém, se em dúvida, [então] inicie a partir de uma árvore limpa.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Building Software as an Unprivileged (non-root) User	Building Software as an Unprivileged (non-root) User
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Building Software as an Unprivileged (non-root) User	Construction de logiciels en tant qu'utilisateur non privilégié (non root)
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Building Software as an Unprivileged (non-root) User	Construindo Software como um(a) Usuário(a) Não Privilegiado(a) (não root)
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	The golden rule of Unix System Administration is to use your superpowers only when necessary. Hence, BLFS recommends that you build software as an unprivileged user and only become the <systemitem class='username'>root</systemitem> user when installing the software. This philosophy is followed in all the packages in this book. Unless otherwise specified, all instructions should be executed as an unprivileged user. The book will advise you on instructions that need <systemitem class='username'>root</systemitem> privileges.	The golden rule of Unix System Administration is to use your superpowers only when necessary. Hence, BLFS recommends that you build software as an unprivileged user and only become the <systemitem class='username'>root</systemitem> user when installing the software. This philosophy is followed in all the packages in this book. Unless otherwise specified, all instructions should be executed as an unprivileged user. The book will advise you on instructions that need <systemitem class='username'>root</systemitem> privileges.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	The golden rule of Unix System Administration is to use your superpowers only when necessary. Hence, BLFS recommends that you build software as an unprivileged user and only become the <systemitem class='username'>root</systemitem> user when installing the software. This philosophy is followed in all the packages in this book. Unless otherwise specified, all instructions should be executed as an unprivileged user. The book will advise you on instructions that need <systemitem class='username'>root</systemitem> privileges.	La règle d'or de l'administration d'un système Unix est de n'utiliser vos super-pouvoirs que si nécessaire. D'où la recommandation de BLFS de construire les logiciels en tant qu'utilisateur non privilégié et de ne devenir l'utilisateur <systemitem class='username'>root</systemitem> que lors de l'installation du logiciel. On suit cette philosophie dans tous les paquets de ce livre. Sauf spécifications contraires, toutes les instructions devraient être exécutées en tant qu'utilisateur non privilégié. Le livre vous conseillera sur les instructions qui ont besoin des privilèges <systemitem class='username'>root</systemitem>.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	The golden rule of Unix System Administration is to use your superpowers only when necessary. Hence, BLFS recommends that you build software as an unprivileged user and only become the <systemitem class='username'>root</systemitem> user when installing the software. This philosophy is followed in all the packages in this book. Unless otherwise specified, all instructions should be executed as an unprivileged user. The book will advise you on instructions that need <systemitem class='username'>root</systemitem> privileges.	A regra de ouro da Administração do Sistema Unix é a de usar os seus super poderes somente quando necessário. Assim, o BLFS recomenda que você construa software como um(a) usuário(a) não privilegiado(a) e somente se torne o(a) usuário(a) <systemitem class='username'>root</systemitem> quando instalar o software. Essa filosofia é seguida em todos os pacotes neste livro. A menos que especificado de outra maneira, todas as instruções deveriam ser executadas como um(a) usuário(a) não privilegiado(a). O livro alertará você acerca de instruções que precisarem de privilégios do(a) <systemitem class='username'>root</systemitem>.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Unpacking the Software	Unpacking the Software
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Unpacking the Software	Décompresser le logiciel
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Unpacking the Software	Desempacotando o Software
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	If a file is in <filename class='extension'>.tar</filename> format and compressed, it is unpacked by running one of the following commands:	If a file is in <filename class='extension'>.tar</filename> format and compressed, it is unpacked by running one of the following commands:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	If a file is in <filename class='extension'>.tar</filename> format and compressed, it is unpacked by running one of the following commands:	S'il y a un fichier compressé au format <filename class='extension'>.tar</filename>, on le décompresse en utilisant une des commandes suivantes&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	If a file is in <filename class='extension'>.tar</filename> format and compressed, it is unpacked by running one of the following commands:	Se um arquivo estiver no formato <filename class='extension'>.tar</filename> e comprimido, [então] ele é desempacotado executando-se um dos seguintes comandos:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>tar -xvf filename.tar.gz tar -xvf filename.tgz tar -xvf filename.tar.Z tar -xvf filename.tar.bz2</userinput>	<userinput>tar -xvf filename.tar.gz tar -xvf filename.tgz tar -xvf filename.tar.Z tar -xvf filename.tar.bz2</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>tar -xvf filename.tar.gz tar -xvf filename.tgz tar -xvf filename.tar.Z tar -xvf filename.tar.bz2</userinput>	<userinput>tar -xvf filename.tar.gz tar -xvf filename.tgz tar -xvf filename.tar.Z tar -xvf filename.tar.bz2</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>tar -xvf filename.tar.gz tar -xvf filename.tgz tar -xvf filename.tar.Z tar -xvf filename.tar.bz2</userinput>	<userinput>tar -xvf nome_arquivo.tar.gz tar -xvf nome_arquivo.tgz tar -xvf nome_arquivo.tar.Z tar -xvf nome_arquivo.tar.bz2</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	You may omit using the <option>v</option> parameter in the commands shown above and below if you wish to suppress the verbose listing of all the files in the archive as they are extracted. This can help speed up the extraction as well as make any errors produced during the extraction more obvious to you.	You may omit using the <option>v</option> parameter in the commands shown above and below if you wish to suppress the verbose listing of all the files in the archive as they are extracted. This can help speed up the extraction as well as make any errors produced during the extraction more obvious to you.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	You may omit using the <option>v</option> parameter in the commands shown above and below if you wish to suppress the verbose listing of all the files in the archive as they are extracted. This can help speed up the extraction as well as make any errors produced during the extraction more obvious to you.	Vous pouvez ne pas utiliser le paramètre <option>v</option> dans les commandes décrites ci-dessus et ci-dessous si vous souhaitez supprimer le listage verbeux de tous les fichiers de l'archive au fur et à mesure qu'ils sont extraits. Cela peut aider à accélérer l'extraction mais aussi rendre plus évidentes les erreurs produites durant le processus.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	You may omit using the <option>v</option> parameter in the commands shown above and below if you wish to suppress the verbose listing of all the files in the archive as they are extracted. This can help speed up the extraction as well as make any errors produced during the extraction more obvious to you.	Você possivelmente omita o uso do parâmetro <option>v</option> nos comandos mostrados acima e abaixo se você desejar suprimir a listagem verbosa de todos os arquivos no arquivamento conforme eles forem extraídos. Isso pode ajudar a acelerar a extração, bem como torna quaisquer erros produzidos durante a extração mais óbvios para você.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	You can also use a slightly different method:	You can also use a slightly different method:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	You can also use a slightly different method:	Vous pouvez aussi utiliser une méthode légèrement différente&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	You can also use a slightly different method:	Você também pode usar um método ligeiramente diferente:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>	<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>	<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>bzcat filename.tar.bz2 | tar -xv</userinput>	<userinput>bzcat nome_arquivo.tar.bz2 | tar -xv</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Finally, sometimes we have a compressed patch file in <filename class='extension'>.patch.gz</filename> or <filename class='extension'>.patch.bz2</filename> format. The best way to apply the patch is piping the output of the decompressor to the <command>patch</command> utility. For example:	Finally, sometimes we have a compressed patch file in <filename class='extension'>.patch.gz</filename> or <filename class='extension'>.patch.bz2</filename> format. The best way to apply the patch is piping the output of the decompressor to the <command>patch</command> utility. For example:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Finally, sometimes we have a compressed patch file in <filename class='extension'>.patch.gz</filename> or <filename class='extension'>.patch.bz2</filename> format. The best way to apply the patch is piping the output of the decompressor to the <command>patch</command> utility. For example:	Enfin, nous avons parfois un fichier de correctif compressé au format <filename class='extension'>.patch.gz</filename> ou <filename class='extension'>.patch.bz2</filename>. La meilleure manière d'applique le correctif est de passer la sortie du décompresseur à l'utilitaire <command>patch</command> via un pipe. Par exemple&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Finally, sometimes we have a compressed patch file in <filename class='extension'>.patch.gz</filename> or <filename class='extension'>.patch.bz2</filename> format. The best way to apply the patch is piping the output of the decompressor to the <command>patch</command> utility. For example:	Finalmente, ocasionalmente, temos um arquivo de remendo comprimido no formato <filename class='extension'>.patch.gz</filename> ou <filename class='extension'>.patch.bz2</filename>. A melhor maneira de aplicar o remendo é a de canalizar a saída gerada do descompressor para o utilitário <command>patch</command>. Por exemplo:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput>	<userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput>	<userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput>	<userinput>gzip -cd ../patchname.patch.gz | patch -p1</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Or for a patch compressed with <command>bzip2</command>:	Or for a patch compressed with <command>bzip2</command>:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Or for a patch compressed with <command>bzip2</command>:	Ou pour un correctif compressé avec <command>bzip2</command>&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Or for a patch compressed with <command>bzip2</command>:	Ou para um remendo comprimido com <command>bzip2</command>:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>bzcat ../patchname.patch.bz2 | patch -p1</userinput>	<userinput>bzcat ../patchname.patch.bz2 | patch -p1</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>bzcat ../patchname.patch.bz2 | patch -p1</userinput>	<userinput>bzcat ../patchname.patch.bz2 | patch -p1</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>bzcat ../patchname.patch.bz2 | patch -p1</userinput>	<userinput>bzcat ../nome_remendo.patch.bz2 | patch -p1</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Verifying File Integrity	Verifying File Integrity
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Verifying File Integrity	Vérifier l'intégrité des fichiers
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Verifying File Integrity	Averiguando a Integridade do Arquivo
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Generally, to verify that the downloaded file is complete, many package maintainers also distribute md5sums of the files. To verify the md5sum of the downloaded files, download both the file and the corresponding md5sum file to the same directory (preferably from different on-line locations), and (assuming <filename>file.md5sum</filename> is the md5sum file downloaded) run the following command:	Generally, to verify that the downloaded file is complete, many package maintainers also distribute md5sums of the files. To verify the md5sum of the downloaded files, download both the file and the corresponding md5sum file to the same directory (preferably from different on-line locations), and (assuming <filename>file.md5sum</filename> is the md5sum file downloaded) run the following command:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Generally, to verify that the downloaded file is complete, many package maintainers also distribute md5sums of the files. To verify the md5sum of the downloaded files, download both the file and the corresponding md5sum file to the same directory (preferably from different on-line locations), and (assuming <filename>file.md5sum</filename> is the md5sum file downloaded) run the following command:	En général, pour vérifier que le fichier téléchargé est complet, de nombreux mainteneurs de paquets distribuent aussi les sommes md5 des fichiers. Pour vérifier la somme md5 des fichiers téléchargés, téléchargez à la fois le fichier et le fichier md5sum correspondant dans le même répertoire (de préférence à partir d'emplacements différents en ligne) et (en supposant que <filename>file.md5sum</filename> est le fichier md5sum téléchargé), lancez la commande suivante&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Generally, to verify that the downloaded file is complete, many package maintainers also distribute md5sums of the files. To verify the md5sum of the downloaded files, download both the file and the corresponding md5sum file to the same directory (preferably from different on-line locations), and (assuming <filename>file.md5sum</filename> is the md5sum file downloaded) run the following command:	Geralmente, para se averiguar se o arquivo transferido está completo, muitos(as) mantenedores(as) de pacote também distribuem somas de verificação md5 dos arquivos. Para averiguar a soma de verificação md5 dos arquivos transferidos, transfira ambos, o arquivo e o arquivo correspondente de soma de verificação md5, para o mesmo diretório (preferencialmente a partir de locais diferentes online) e (assumindo que <filename>arquivo.md5sum</filename> seja o arquivo de soma de verificação md5 transferido) execute o seguinte comando:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>md5sum -c file.md5sum</userinput>	<userinput>md5sum -c file.md5sum</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>md5sum -c file.md5sum</userinput>	<userinput>md5sum -c file.md5sum</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>md5sum -c file.md5sum</userinput>	<userinput>md5sum -c arquivo.md5sum</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	If there are any errors, they will be reported. Note that the BLFS book includes md5sums for all the source files also. To use the BLFS supplied md5sums, you can create a <filename>file.md5sum</filename> (place the md5sum data and the exact name of the downloaded file on the same line of a file, separated by white space) and run the command shown above. Alternately, simply run the command shown below and compare the output to the md5sum data shown in the BLFS book.	If there are any errors, they will be reported. Note that the BLFS book includes md5sums for all the source files also. To use the BLFS supplied md5sums, you can create a <filename>file.md5sum</filename> (place the md5sum data and the exact name of the downloaded file on the same line of a file, separated by white space) and run the command shown above. Alternately, simply run the command shown below and compare the output to the md5sum data shown in the BLFS book.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	If there are any errors, they will be reported. Note that the BLFS book includes md5sums for all the source files also. To use the BLFS supplied md5sums, you can create a <filename>file.md5sum</filename> (place the md5sum data and the exact name of the downloaded file on the same line of a file, separated by white space) and run the command shown above. Alternately, simply run the command shown below and compare the output to the md5sum data shown in the BLFS book.	S'il y a une erreur, elle sera signalée. Remarquez que le livre BLFS contient aussi les sommes md5 de tous les fichiers sources. Pour utiliser les sommes md5 fournies par BLFS, vous pouvez créer un <filename>file.md5sum</filename> (mettez les données md5sum et le nom exact du fichier téléchargé sur la même ligne d'un fichier, séparés par un espace blanc), et lancez la commande montrée ci-dessus. Sinon, lancez simplement la commande décrite ci-dessus et comparez la sortie avec les données de somme md5 inscrites dans le livre BLFS.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	If there are any errors, they will be reported. Note that the BLFS book includes md5sums for all the source files also. To use the BLFS supplied md5sums, you can create a <filename>file.md5sum</filename> (place the md5sum data and the exact name of the downloaded file on the same line of a file, separated by white space) and run the command shown above. Alternately, simply run the command shown below and compare the output to the md5sum data shown in the BLFS book.	Se existirem quaisquer erros, [então] eles serão informados. Observe que o livro BLFS inclui somas de verificação md5 para todos os arquivos de fonte também. Para usar as somas de verificação md5 fornecidas pelo BLFS, você pode criar um <filename>arquivo.md5sum</filename> (coloque os dados da soma de verificação md5 e o nome exato do arquivo transferido na mesma linha de um arquivo, separados por espaço em branco) e executar o comando mostrado acima. Alternativamente, simplesmente execute o comando mostrado abaixo e compare a saída gerada para os dados da soma de verificação md5 mostrada no livro BLFS.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>md5sum <replaceable>&lt;name_of_downloaded_file&gt;</replaceable></userinput>	<userinput>md5sum <replaceable>&lt;name_of_downloaded_file&gt;</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>md5sum <replaceable>&lt;name_of_downloaded_file&gt;</replaceable></userinput>	<userinput>md5sum <replaceable>&lt;name_of_downloaded_file&gt;</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>md5sum <replaceable>&lt;name_of_downloaded_file&gt;</replaceable></userinput>	<userinput>md5sum <replaceable>&lt;nome_do_arquivo_transferido&gt;</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	MD5 is not cryptographically secure, so the md5sums are only provided for detecting unmalicious changes to the file content. For example, an error or truncation introduced during network transfer, or a <quote>stealth</quote> update to the package from the upstream (updating the content of a released tarball instead of making a new release properly).	MD5 is not cryptographically secure, so the md5sums are only provided for detecting unmalicious changes to the file content. For example, an error or truncation introduced during network transfer, or a <quote>stealth</quote> update to the package from the upstream (updating the content of a released tarball instead of making a new release properly).
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	MD5 is not cryptographically secure, so the md5sums are only provided for detecting unmalicious changes to the file content. For example, an error or truncation introduced during network transfer, or a <quote>stealth</quote> update to the package from the upstream (updating the content of a released tarball instead of making a new release properly).	Le MD5 n'est pas cryptographiquement sûr, donc les sommes md5 ne sont fournies que pour détecter des changements non intentionnels au contenu du fichier. Par exemple, une erreur ou troncation introduite pendant le transfert réseau, ou une mise à jour <quote>furtive</quote> du paquet en amont (mise à jour du contenu d'une archive publiée au lieu de créer directement une nouvelle version).
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	MD5 is not cryptographically secure, so the md5sums are only provided for detecting unmalicious changes to the file content. For example, an error or truncation introduced during network transfer, or a <quote>stealth</quote> update to the package from the upstream (updating the content of a released tarball instead of making a new release properly).	MD5 não é seguro criptograficamente, de forma que as somas de verificação md5 são fornecidas somente para se detectar mudanças não maliciosas para o conteúdo do arquivo. Por exemplo, um erro ou truncamento introduzido durante a transferência de rede de comunicação; ou uma atualização <quote>furtiva</quote> para o pacote oriunda do(a) desenvolvedor(a) (atualizando o conteúdo de um tarball liberado em vez de fazer um lançamento novo adequadamente).
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	There is no <quote>100%</quote> secure way to make sure the genuity of the source files. Assuming the upstream is managing their website correctly (the private key is not leaked and the domain is not hijacked), and the trust anchors have been set up correctly using <xref linkend="make-ca"/> on the BLFS system, we can reasonably trust download URLs to the upstream official website <emphasis role="bold">with https protocol</emphasis>. Note that BLFS book itself is published on a website with https, so you should already have some confidence in https protocol or you wouldn't trust the book content.	There is no <quote>100%</quote> secure way to make sure the genuity of the source files. Assuming the upstream is managing their website correctly (the private key is not leaked and the domain is not hijacked), and the trust anchors have been set up correctly using <xref linkend="make-ca"/> on the BLFS system, we can reasonably trust download URLs to the upstream official website <emphasis role="bold">with https protocol</emphasis>. Note that BLFS book itself is published on a website with https, so you should already have some confidence in https protocol or you wouldn't trust the book content.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	There is no <quote>100%</quote> secure way to make sure the genuity of the source files. Assuming the upstream is managing their website correctly (the private key is not leaked and the domain is not hijacked), and the trust anchors have been set up correctly using <xref linkend="make-ca"/> on the BLFS system, we can reasonably trust download URLs to the upstream official website <emphasis role="bold">with https protocol</emphasis>. Note that BLFS book itself is published on a website with https, so you should already have some confidence in https protocol or you wouldn't trust the book content.	Il n'y a pas de manière sure à <quote>100 %</quote> pour s'assurer de l'authenticité des fichiers sources. En supposant que les développeurs en amont gèrent leur site correctement (la clé privée n'est pas communiquée et le domaine n'est pas usurpé), et que les ancres de confiance ont été correctement configurées avec <xref linkend="make-ca"/> sur le système BLFS, on peut raisonnablement faire confiance aux URL des site web officiels <emphasis role="bold">avec le protocole https</emphasis>. Remarquez que le livre BLFS lui-même est publié sur un site avec https, donc vous devez déjà avoir un peu confiance en le protocole https ou vous ne pourriez pas faire confiance au contenu de ce livre.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	There is no <quote>100%</quote> secure way to make sure the genuity of the source files. Assuming the upstream is managing their website correctly (the private key is not leaked and the domain is not hijacked), and the trust anchors have been set up correctly using <xref linkend="make-ca"/> on the BLFS system, we can reasonably trust download URLs to the upstream official website <emphasis role="bold">with https protocol</emphasis>. Note that BLFS book itself is published on a website with https, so you should already have some confidence in https protocol or you wouldn't trust the book content.	Não existe maneira <quote>100%</quote> segura de garantir a genuinidade dos arquivos do fonte. Assumindo que o(a) desenvolvedor(a) esteja gerenciando corretamente o sítio da web dele(a) (a chave privada não vazou e o domínio não esteja sequestrado); e que as âncoras de confiança tenham sido configuradas corretamente usando <xref linkend="make-ca"/> no sistema BLFS; nós podemos razoavelmente confiar nos URLs de transferência para o sítio oficial da web do(a) desenvolvedor(a) <emphasis role="bold">com protocolo https</emphasis>. Observe que o próprio livro BLFS está publicado em um sítio da web com https, de forma que você já deveria ter alguma confiança no protocolo https ou você não confiaria no conteúdo do livro.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	If the package is downloaded from an unofficial location (for example a local mirror), checksums generated by cryptographically secure digest algorithms (for example SHA256) can be used to verify the genuity of the package. Download the checksum file from the upstream <emphasis role="bold">official</emphasis> website (or somewhere <emphasis role="bold">you can trust</emphasis>) and compare the checksum of the package from unofficial location with it. For example, SHA256 checksum can be checked with the command:	If the package is downloaded from an unofficial location (for example a local mirror), checksums generated by cryptographically secure digest algorithms (for example SHA256) can be used to verify the genuity of the package. Download the checksum file from the upstream <emphasis role="bold">official</emphasis> website (or somewhere <emphasis role="bold">you can trust</emphasis>) and compare the checksum of the package from unofficial location with it. For example, SHA256 checksum can be checked with the command:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	If the package is downloaded from an unofficial location (for example a local mirror), checksums generated by cryptographically secure digest algorithms (for example SHA256) can be used to verify the genuity of the package. Download the checksum file from the upstream <emphasis role="bold">official</emphasis> website (or somewhere <emphasis role="bold">you can trust</emphasis>) and compare the checksum of the package from unofficial location with it. For example, SHA256 checksum can be checked with the command:	Si le paquet est téléchargé à partir d'un emplacement non officiel (par exemple un miroir local), vous pouvez utiliser des sommes de contrôles générées par un algorithme cryptographiquement sûr (par exemple SHA256) pour vérifier l'authenticité du paquet. Téléchargez le fichier de somme de contrôle depuis le site <emphasis role="bold">officiel</emphasis> des développeurs en amont (ou depuis un endroit <emphasis role="bold">auquel vous faites confiance</emphasis>) et comparez la somme de contrôle du paquet de l'emplacement non officiel. Par exemple, vous pouvez vérifier une somme de contrôle SHA256 avec la commande&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	If the package is downloaded from an unofficial location (for example a local mirror), checksums generated by cryptographically secure digest algorithms (for example SHA256) can be used to verify the genuity of the package. Download the checksum file from the upstream <emphasis role="bold">official</emphasis> website (or somewhere <emphasis role="bold">you can trust</emphasis>) and compare the checksum of the package from unofficial location with it. For example, SHA256 checksum can be checked with the command:	Se o pacote for transferido a partir de um local não oficial (por exemplo, um espelho local), [então] as somas de verificação geradas por algoritmos de resumo criptograficamente seguros (por exemplo, SHA256) podem ser usadas para averiguar a genuinidade do pacote. Transfira o arquivo da soma de verificação a partir do sítio da web <emphasis role="bold">oficial</emphasis> do(a) desenvolvedor(a) (ou algum lugar que <emphasis role="bold">você possa confiar</emphasis>) e compare a soma de verificação do pacote oriunda do local não oficial com ele. Por exemplo, a soma de verificação SHA256 pode ser verificada com o comando:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	If the checksum and the package are downloaded from the same untrusted location, you won't gain security enhancement by verifying the package with the checksum. The attacker can fake the checksum as well as compromising the package itself.	If the checksum and the package are downloaded from the same untrusted location, you won't gain security enhancement by verifying the package with the checksum. The attacker can fake the checksum as well as compromising the package itself.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	If the checksum and the package are downloaded from the same untrusted location, you won't gain security enhancement by verifying the package with the checksum. The attacker can fake the checksum as well as compromising the package itself.	Si la somme de contrôle et le paquet sont téléchargés à partir de la même source non fiable, vous ne gagnerez rien à vérifier le paquet avec la somme de contrôle. L'attaquant peut présenter une fausse somme de contrôle en plus de compromettre le paquet en lui-même.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	If the checksum and the package are downloaded from the same untrusted location, you won't gain security enhancement by verifying the package with the checksum. The attacker can fake the checksum as well as compromising the package itself.	Se a soma de verificação e o pacote forem transferidos a partir do mesmo local não confiável, [então] você não ganharia melhoramento de segurança averiguando o pacote com a soma de verificação. O(A) atacante pode falsear a soma de verificação assim como comprometer o próprio pacote.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>sha256sum -c <replaceable>file</replaceable>.sha256sum</userinput>	<userinput>sha256sum -c <replaceable>file</replaceable>.sha256sum</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>sha256sum -c <replaceable>file</replaceable>.sha256sum</userinput>	<userinput>sha256sum -c <replaceable>file</replaceable>.sha256sum</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>sha256sum -c <replaceable>file</replaceable>.sha256sum</userinput>	<userinput>sha256sum -c <replaceable>arquivo</replaceable>.sha256sum</userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	If <xref linkend="gnupg2"/> is installed, you can also verify the genuity of the package with a GPG signature. Import the upstream GPG public key with:	If <xref linkend="gnupg2"/> is installed, you can also verify the genuity of the package with a GPG signature. Import the upstream GPG public key with:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	If <xref linkend="gnupg2"/> is installed, you can also verify the genuity of the package with a GPG signature. Import the upstream GPG public key with:	Si <xref linkend="gnupg2"/> est installé, vous pouvez aussi vérifier l'authenticité du paquet avec une signature GPG. Importez la clé publique GPG amont avec&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	If <xref linkend="gnupg2"/> is installed, you can also verify the genuity of the package with a GPG signature. Import the upstream GPG public key with:	Se o <xref linkend="gnupg2"/> estiver instalado, [então] você também pode averiguar a genuinidade do pacote com uma assinatura GPG. Importe a chave pública GPG do(a) desenvolvedor(a) com:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>gpg --recv-key <replaceable>keyID</replaceable></userinput>	<userinput>gpg --recv-key <replaceable>keyID</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>gpg --recv-key <replaceable>keyID</replaceable></userinput>	<userinput>gpg --recv-key <replaceable>keyID</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>gpg --recv-key <replaceable>keyID</replaceable></userinput>	<userinput>gpg --recv-key <replaceable>ID_da_chave</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<replaceable>keyID</replaceable> should be replaced with the key ID from somewhere <emphasis role="bold">you can trust</emphasis> (for example, copy it from the upstream official website using https). Now you can verify the signature with:	<replaceable>keyID</replaceable> should be replaced with the key ID from somewhere <emphasis role="bold">you can trust</emphasis> (for example, copy it from the upstream official website using https). Now you can verify the signature with:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<replaceable>keyID</replaceable> should be replaced with the key ID from somewhere <emphasis role="bold">you can trust</emphasis> (for example, copy it from the upstream official website using https). Now you can verify the signature with:	<replaceable>keyID</replaceable> devrait être remplacée par l'identifiant de la clé fournie par un site <emphasis role="bold">fiable</emphasis> (par exemple, copiez-la depuis le site officiel en utilisant https). Maintenant vous pouvez vérifier la signature avec&nbsp;:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<replaceable>keyID</replaceable> should be replaced with the key ID from somewhere <emphasis role="bold">you can trust</emphasis> (for example, copy it from the upstream official website using https). Now you can verify the signature with:	<replaceable>ID_da_chave</replaceable> deveria ser substituído pelo ID da chave oriundo de algum lugar que <emphasis role="bold">você possa confiar</emphasis> (por exemplo, copie-o a partir do sítio da web oficial do(a) desenvolvedor(a) usando https). Agora, você consegue averiguar a assinatura com:
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	<userinput>gpg --recv-key <replaceable>file</replaceable>.sig <replaceable>file</replaceable></userinput>	<userinput>gpg --recv-key <replaceable>file</replaceable>.sig <replaceable>file</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	<userinput>gpg --recv-key <replaceable>file</replaceable>.sig <replaceable>file</replaceable></userinput>	<userinput>gpg --recv-key <replaceable>file</replaceable>.sig <replaceable>file</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	<userinput>gpg --recv-key <replaceable>file</replaceable>.sig <replaceable>file</replaceable></userinput>	<userinput>gpg --recv-key <replaceable>arquivo</replaceable>.sig <replaceable>arquivo</replaceable></userinput>
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	The advantage of <application>GnuPG</application> signature is, once you imported a public key which can be trusted, you can download both the package and its signature from the same unofficial location and verify them with the public key. So you won't need to connect to the official upstream website to retrieve a checksum for each new release. You only need to update the public key if it's expired or revoked.	The advantage of <application>GnuPG</application> signature is, once you imported a public key which can be trusted, you can download both the package and its signature from the same unofficial location and verify them with the public key. So you won't need to connect to the official upstream website to retrieve a checksum for each new release. You only need to update the public key if it's expired or revoked.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	The advantage of <application>GnuPG</application> signature is, once you imported a public key which can be trusted, you can download both the package and its signature from the same unofficial location and verify them with the public key. So you won't need to connect to the official upstream website to retrieve a checksum for each new release. You only need to update the public key if it's expired or revoked.	L'avantage de la signature <application>GnuPG</application> est que, une fois une clé publique de confiance importée, vous pouvez télécharger à la fois le paquet et sa signature à partir du même emplacement non officiel et les vérifier avec la clé publique. Donc vous n'avez pas besoin de vous connecter au site officiel en amont pour récupérer une somme de contrôle pour chaque nouvelle version. Vous n'aurez besoin de mettre à jour la clé publique que si elle est révoquée ou expirée.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	The advantage of <application>GnuPG</application> signature is, once you imported a public key which can be trusted, you can download both the package and its signature from the same unofficial location and verify them with the public key. So you won't need to connect to the official upstream website to retrieve a checksum for each new release. You only need to update the public key if it's expired or revoked.	A vantagem da assinatura <application>GnuPG</application> é, tão logo você importou uma chave pública que possa ser confiada, você pode transferir ambos, o pacote e a assinatura dele, a partir do mesmo local não oficial e averiguá-los com a chave pública. Assim, você não precisaria conectar com o sítio da web oficial do(a) desenvolvedor(a) para ir buscar uma soma de verificação para cada lançamento novo. Você somente precisa atualizar a chave pública se ela estiver expirada ou revogada.
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	Creating Log Files During Installation	Creating Log Files During Installation
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — French	Creating Log Files During Installation	Créer des fichiers journaux pendant l'installation
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — Portuguese (Brazil)	Creating Log Files During Installation	Criando Arquivos de Registro Durante a Instalação
	Beyond Linux From Scratch 12.0/introduction_important_building-notes — English	For larger packages, it is convenient to create log files instead of staring at the screen hoping to catch a particular error or warning. Log files are also useful for debugging and keeping records. The following command allows you to create an installation log. Replace <replaceable>&lt;command&gt;</replaceable> with the command you intend to execute.	For larger packages, it is convenient to create log files instead of staring at the screen hoping to catch a particular error or warning. Log files are also useful for debugging and keeping records. The following command allows you to create an installation log. Replace <replaceable>&lt;command&gt;</replaceable> with the command you intend to execute.

• 1 / 5
  / 5