2. Linux From Scratch 12.0
3. 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
	Linux From Scratch 12.0/chapter05_gcc-pass1 — French	<productname>gcc-pass1</productname> <productnumber>&gcc-version;</productnumber> <placeholder type="address" id="0"/>	<productname>gcc-pass1</productname> <productnumber>&gcc-version;</productnumber> <placeholder type="address" id="0"/>
	Linux From Scratch 12.0/chapter05_gcc-pass1 — Portuguese (Brazil)	<productname>gcc-pass1</productname> <productnumber>&gcc-version;</productnumber> <placeholder type="address" id="0"/>	<productname>gcc-pass1</productname> <productnumber>&gcc-version;</productnumber> <placeholder type="address" id="0"/>
	Linux From Scratch 12.0/chapter05_gcc-pass1 — Chinese (Simplified Han script)	<productname>gcc-pass1</productname> <productnumber>&gcc-version;</productnumber> <placeholder type="address" id="0"/>	<productname>gcc-pass1</productname> <productnumber>&gcc-version;</productnumber> <placeholder type="address" id="0"/>
	Linux From Scratch 12.0/chapter05_libstdc__ — English	Libstdc++ from GCC-&gcc-version;	Libstdc++ from GCC-&gcc-version;
	Linux From Scratch 12.0/chapter05_libstdc__ — French	Libstdc++ from GCC-&gcc-version;	Libstdc++ de GCC-&gcc-version;
	Linux From Scratch 12.0/chapter05_libstdc__ — Portuguese (Brazil)	Libstdc++ from GCC-&gcc-version;	Libstdc++ oriundo de GCC-&gcc-version;
	Linux From Scratch 12.0/chapter05_binutils-pass1 — English	Binutils-&binutils-version; - Pass 1	Binutils-&binutils-version; - Pass 1
	Linux From Scratch 12.0/chapter05_binutils-pass1 — French	Binutils-&binutils-version; - Pass 1	Binutils-&binutils-version; — Passe&nbsp;1
	Linux From Scratch 12.0/chapter05_binutils-pass1 — Portuguese (Brazil)	Binutils-&binutils-version; - Pass 1	Binutils-&binutils-version; - Passagem 1
	Linux From Scratch 12.0/chapter05_binutils-pass1 — Chinese (Simplified Han script)	Binutils-&binutils-version; - Pass 1	Binutils-&binutils-version; - 第一遍
	Linux From Scratch 12.0/chapter03_packages — English	The upstream sources may remove old releases, especially when those releases contain a security vulnerability. If one URL below is not reachable, you should read the security advisories first to figure out if a newer version (with the vulnerability fixed) should be used. If not, try to download the removed package from a mirror. Although it's possible to download an old release from a mirror even if this release has been removed because of a vulnerability, it's not a good idea to use a release known to be vulnerable when building your system.	The upstream sources may remove old releases, especially when those releases contain a security vulnerability. If one URL below is not reachable, you should read the security advisories first to figure out if a newer version (with the vulnerability fixed) should be used. If not, try to download the removed package from a mirror. Although it's possible to download an old release from a mirror even if this release has been removed because of a vulnerability, it's not a good idea to use a release known to be vulnerable when building your system.
	Linux From Scratch 12.0/chapter03_packages — French	The upstream sources may remove old releases, especially when those releases contain a security vulnerability. If one URL below is not reachable, you should read the security advisories first to figure out if a newer version (with the vulnerability fixed) should be used. If not, try to download the removed package from a mirror. Although it's possible to download an old release from a mirror even if this release has been removed because of a vulnerability, it's not a good idea to use a release known to be vulnerable when building your system.	Les développeurs en amont peuvent supprimer les anciennes versions surtout si elles contiennent des vulnérabilités. Si une URL ci-dessous est injoignable, vous pouvez lire les annonces de sécurité avant pour savoir si vous devriez utiliser une version plus récente (avec la vulnérabilité corrigée). Sinon, essayez de télécharger le paquets supprimé depuis un miroir. Bien qu'il soit possible de télécharger une ancienne version à partir d'un miroir même si la version a été supprimée à cause d'une vulnérabilité, nous ne vous recommandons pas d'utiliser une version connue pour être vulnérable pour construire votre système.
	Linux From Scratch 12.0/chapter03_packages — Portuguese (Brazil)	The upstream sources may remove old releases, especially when those releases contain a security vulnerability. If one URL below is not reachable, you should read the security advisories first to figure out if a newer version (with the vulnerability fixed) should be used. If not, try to download the removed package from a mirror. Although it's possible to download an old release from a mirror even if this release has been removed because of a vulnerability, it's not a good idea to use a release known to be vulnerable when building your system.	Os fontes do(a) desenvolvedor(a) possivelmente removam lançamentos antigos, especialmente quando esses lançamentos contenham uma vulnerabilidade de segurança. Se um URL abaixo não estiver alcançável, [então] você deveria ler os avisos de segurança primeiro para descobrir se uma versão mais nova (com a vulnerabilidade consertada) deveria ser usada. Se não, [então] tente transferir o pacote removido a partir de um espelho. Apesar de ser possível transferir um lançamento antigo a partir de um espelho, mesmo se esse lançamento tiver sido removido por causa de uma vulnerabilidade, não é uma boa ideia usar um lançamento conhecido por ser vulnerável quando da construção do seu sistema.
	Linux From Scratch 12.0/chapter03_introduction — English	For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar file names. A release tarball contains generated files (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.	For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar file names. A release tarball contains generated files (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.
	Linux From Scratch 12.0/chapter03_introduction — French	For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar file names. A release tarball contains generated files (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.	Pour certains paquets, l'archive de version et l'instantané du dépôt (Git ou SVN) pour cette version peuvent être publiés avec des noms similaires. Une archive de version contient des fichiers générés (par exemple, un script <command>configure</command> généré par <command>autoconf</command>) en plus du contenu de l'instantané du dépôt. Le livre utilise les archives de version chaque fois que cela est possible. Utiliser des instantanés de dépôt au lieu des archives de version spécifiées dans le livre causera des problèmes.
	Linux From Scratch 12.0/chapter03_introduction — Portuguese (Brazil)	For some packages, the release tarball and the (Git or SVN) repository snapshot tarball for that release may be published with similar file names. A release tarball contains generated files (for example, a <command>configure</command> script generated by <command>autoconf</command>), in addition to the contents of the corresponding repository snapshot. The book uses release tarballs whenever possible. Using a repository snapshot instead of a release tarball specified by the book will cause problems.	Para alguns pacotes, o tarball de lançamento e o tarball instantâneo de repositório (Git ou SVN) para aquele lançamento possivelmente seja publicado com nomes de arquivo semelhantes. Um tarball de lançamento contém arquivos generalizados (por exemplo, um script <command>configure</command> gerado pelo <command>autoconf</command>), em adição ao conteúdo do correspondente instantâneo de repositório. O livro usa tarballs de lançamento sempre que possível. Usar um instantâneo de repositório em vez de um tarball de lançamento especificado pelo livro causará problemas.
	Linux From Scratch 12.0/chapter03_patches — English	Bzip2 Documentation Patch - <token>&bzip2-docs-patch-size;</token>:	Bzip2 Documentation Patch - <token>&bzip2-docs-patch-size;</token>:
	Linux From Scratch 12.0/chapter03_patches — French	Bzip2 Documentation Patch - <token>&bzip2-docs-patch-size;</token>:	Bzip2 Correctif documentation — <token>&bzip2-docs-patch-size;</token>&nbsp;:
	Linux From Scratch 12.0/chapter03_patches — Portuguese (Brazil)	Bzip2 Documentation Patch - <token>&bzip2-docs-patch-size;</token>:	Remendo da Documentação do Bzip2 - <token>&bzip2-docs-patch-size;</token>:
	Linux From Scratch 12.0/chapter03_patches — Chinese (Simplified Han script)	Bzip2 Documentation Patch - <token>&bzip2-docs-patch-size;</token>:	Bzip2 文档补丁 - <token>&bzip2-docs-patch-size;</token>:
	Linux From Scratch 12.0/chapter01_how — English	There are many ways to install a Linux distribution and the defaults are usually not optimal for building an LFS system. For suggestions on setting up a commercial distribution see: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.	There are many ways to install a Linux distribution and the defaults are usually not optimal for building an LFS system. For suggestions on setting up a commercial distribution see: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.
	Linux From Scratch 12.0/chapter01_how — French	There are many ways to install a Linux distribution and the defaults are usually not optimal for building an LFS system. For suggestions on setting up a commercial distribution see: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.	On peut installer une distribution Linux de nombreuses manières et les paramètres par défaut ne sont en général pas optimisés pour construire un système LFS. Consultez <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/> pour trouver des suggestions de configuration pour des distributions commerciales.
	Linux From Scratch 12.0/chapter01_how — Portuguese (Brazil)	There are many ways to install a Linux distribution and the defaults are usually not optimal for building an LFS system. For suggestions on setting up a commercial distribution see: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.	Existem muitas maneiras de se instalar uma distribuição Linux e os padrões geralmente não são ideais para construir um sistema LFS. Para sugestões a respeito de configurar uma distribuição comercial, veja-se: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.
	Linux From Scratch 12.0/chapter01_changelog — English	Below is a list of changes made since the previous release of the book.	Below is a list of changes made since the previous release of the book.
	Linux From Scratch 12.0/chapter01_changelog — French	Below is a list of changes made since the previous release of the book.	Ci-dessous se trouve une liste des modifications apportées depuis la version précédente du livre.
	Linux From Scratch 12.0/chapter01_changelog — Portuguese (Brazil)	Below is a list of changes made since the previous release of the book.	Abaixo está uma lista das mudanças feitas desde o lançamento anterior do livro.
	Linux From Scratch 12.0/chapter01_changelog — Chinese (Simplified Han script)	Below is a list of changes made since the previous release of the book.	下面是本书自上一版本发布以来的更新日志。
	Linux From Scratch 12.0/chapter01_whatsnew — English	Upgraded to:	Upgraded to:
	Linux From Scratch 12.0/chapter01_whatsnew — French	Upgraded to:	Mis à jour vers&nbsp;:
	Linux From Scratch 12.0/chapter01_whatsnew — Portuguese (Brazil)	Upgraded to:	Atualizado para:
	Linux From Scratch 12.0/chapter01_whatsnew — Chinese (Simplified Han script)	Upgraded to:	已升级：
	Linux From Scratch 12.0/chapter01_askforhelp — English	If you must ask a question directly via an upstream support channel, you shall at least note that many upstream projects have the support channels separated from the bug tracker. The <quote>bug</quote> reports for asking questions are considered invalid and may annoy upstream developers for these projects.	If you must ask a question directly via an upstream support channel, you shall at least note that many upstream projects have the support channels separated from the bug tracker. The <quote>bug</quote> reports for asking questions are considered invalid and may annoy upstream developers for these projects.
	Linux From Scratch 12.0/chapter01_askforhelp — French	If you must ask a question directly via an upstream support channel, you shall at least note that many upstream projects have the support channels separated from the bug tracker. The <quote>bug</quote> reports for asking questions are considered invalid and may annoy upstream developers for these projects.	Si vous devez poser une question directement via un canal de support en amont, vous devez au moins prendre en compte que la plupart des projets ont un canal de support séparé du gestionnaire de bogues. Les rapports de <quote>boque</quote> qui posent des questions sont considérés comme invalides et peuvent embêter les développeurs amont de ces projets.
	Linux From Scratch 12.0/chapter01_askforhelp — Portuguese (Brazil)	If you must ask a question directly via an upstream support channel, you shall at least note that many upstream projects have the support channels separated from the bug tracker. The <quote>bug</quote> reports for asking questions are considered invalid and may annoy upstream developers for these projects.	Se precisar fazer uma pergunta diretamente por meio de um canal de suporte do(a) desenvolvedor(a), [então] você deveria observar, pelo menos, que muitos projetos de desenvolvedor(a) tem os canais de suporte separados do rastreador de defeitos. Os informes de <quote>defeito</quote> para fazer perguntas são considerados inválidos e podem incomodar os(as) desenvolvedores(as) upstream para esses projetos.
	Linux From Scratch 12.0/chapter01_resources — English	If during the building of the LFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the list of Frequently Asked Questions (FAQ), located at <ulink url="&faq-root;"/>.	If during the building of the LFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the list of Frequently Asked Questions (FAQ), located at <ulink url="&faq-root;"/>.
	Linux From Scratch 12.0/chapter01_resources — French	If during the building of the LFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the list of Frequently Asked Questions (FAQ), located at <ulink url="&faq-root;"/>.	Si vous rencontrez des erreurs lors de la construction du système LFS, si vous avez des questions ou si vous pensez qu'il y a une coquille dans ce livre, merci de commencer par consulter la <acronym>FAQ</acronym> (Foire aux Questions) sur <ulink url="&faq-root;"/>.
	Linux From Scratch 12.0/chapter01_resources — Portuguese (Brazil)	If during the building of the LFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the list of Frequently Asked Questions (FAQ), located at <ulink url="&faq-root;"/>.	Se durante a construção do sistema LFS você encontrar quaisquer erros, tiver quaisquer perguntas, ou entender que há um erro de digitação no livro, [então], por favor, comece consultando as Perguntas Feitas Frequentemente (FAQ) que estão localizadas em <ulink url="&faq-root;"/>.
	Linux From Scratch 12.0/part3intro_introduction — English	This is where the real work of building a new system begins. Be very careful to follow the instructions exactly as the book shows them. You should try to understand what each command does, and no matter how eager you are to finish your build, you should refrain from blindly typing the commands as shown. Read the documentation when there is something you do not understand. Also, keep track of your typing and of the output of commands, by using the <command>tee</command> utility to send the terminal output to a file. This makes debugging easier if something goes wrong.	This is where the real work of building a new system begins. Be very careful to follow the instructions exactly as the book shows them. You should try to understand what each command does, and no matter how eager you are to finish your build, you should refrain from blindly typing the commands as shown. Read the documentation when there is something you do not understand. Also, keep track of your typing and of the output of commands, by using the <command>tee</command> utility to send the terminal output to a file. This makes debugging easier if something goes wrong.
	Linux From Scratch 12.0/part3intro_introduction — French	This is where the real work of building a new system begins. Be very careful to follow the instructions exactly as the book shows them. You should try to understand what each command does, and no matter how eager you are to finish your build, you should refrain from blindly typing the commands as shown. Read the documentation when there is something you do not understand. Also, keep track of your typing and of the output of commands, by using the <command>tee</command> utility to send the terminal output to a file. This makes debugging easier if something goes wrong.	C’est dans cette partie qu’un vrai travail de construction d'un nouveau système peut commencer. Il est recommande d’être attentif et de suivre avec précision les instructions du livre. Mettez de côté toute envie de finir votre construction rapidement. Vous devez essayer de comprendre ce que les commandes font et éviter de les taper à l’aveugle. Lisez la documentation quand vous ne comprenez pas quelque chose. Gardez aussi une trace de ce que vous tapez et des sorties des commandes, en les envoyant dans un fichier, avec l'outil <command>tee</command>, qui permet de mieux diagnostiquer les problèmes qui pourraient survenir.
	Linux From Scratch 12.0/part3intro_introduction — Portuguese (Brazil)	This is where the real work of building a new system begins. Be very careful to follow the instructions exactly as the book shows them. You should try to understand what each command does, and no matter how eager you are to finish your build, you should refrain from blindly typing the commands as shown. Read the documentation when there is something you do not understand. Also, keep track of your typing and of the output of commands, by using the <command>tee</command> utility to send the terminal output to a file. This makes debugging easier if something goes wrong.	Essa é onde o trabalho real de construir um novo sistema inicia. Seja muito cuidadoso(a) em seguir as instruções exatamente conforme o livro as mostra. Você deveria tentar entender o que cada comando faz e, não importa o quão ansioso(a) você estiver para finalizar sua construção, você deveria evitar digitar cegamente os comandos como mostrado. Leia a documentação quando houver algo que você não entenda. Além disso, mantenha um rastreio da sua digitação e da saída gerada de comandos, usando o utilitário <command>tee</command> para enviar a saída gerada pelo terminal para um arquivo. Isso torna a depuração mais fácil se algo der errado.
	Linux From Scratch 12.0/part3intro_generalinstructions — English	Several packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both the current and the following chapters, but sometimes, when the same package is built more than once, the patch is not needed right away. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do not worry about these warnings; the patch was still successfully applied.	Several packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both the current and the following chapters, but sometimes, when the same package is built more than once, the patch is not needed right away. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do not worry about these warnings; the patch was still successfully applied.
	Linux From Scratch 12.0/part3intro_generalinstructions — French	Several packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both the current and the following chapters, but sometimes, when the same package is built more than once, the patch is not needed right away. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do not worry about these warnings; the patch was still successfully applied.	Plusieurs paquets sont corrigés avant d'être compilés, mais seulement dans le cas où la correction est nécessaire pour résoudre un problème. Souvent, le correctif est nécessaire à la fois dans ce chapitre et dans les suivants, mais quelques fois lorsque le même paquet est construit plus d'une fois, le correctif n'est pas immédiatement nécessaire. Donc, ne vous inquiétez pas lorsque des instructions pour un correctif téléchargé semblent manquer. Des messages d'avertissements sur un décalage (<emphasis>offset</emphasis>) ou sur autre chose (<emphasis>fuzz</emphasis>) peuvent apparaître lors de l'application d'un correctif. Ne vous inquiétez pas pour ces messages, le correctif a bien été appliqué.
	Linux From Scratch 12.0/part3intro_generalinstructions — Portuguese (Brazil)	Several packages are patched before compilation, but only when the patch is needed to circumvent a problem. A patch is often needed in both the current and the following chapters, but sometimes, when the same package is built more than once, the patch is not needed right away. Therefore, do not be concerned if instructions for a downloaded patch seem to be missing. Warning messages about <emphasis>offset</emphasis> or <emphasis>fuzz</emphasis> may also be encountered when applying a patch. Do not worry about these warnings; the patch was still successfully applied.	Vários pacotes são remendados antes da compilação, porém somente quando o remendo for necessário para contornar um problema. Um remendo frequentemente é necessário tanto neste quanto nos capítulos seguintes, porém às vezes, quando o mesmo pacote é construído mais que uma vez. o remendo não é necessário imediatamente. Portanto, não se preocupe se as instruções para um remendo baixado pareçam estar ausentes. Mensagens de aviso acerca de <emphasis>offset</emphasis> ou <emphasis>fuzz</emphasis> também possivelmente sejam encontradas quando da aplicação de um remendo. Não se preocupe com esses alertas; o remendo ainda foi aplicado com sucesso.
	Linux From Scratch 12.0/part3intro_toolchaintechnotes — English	The overall goal of <xref linkend="chapter-cross-tools"/> and <xref linkend="chapter-temporary-tools"/> is to produce a temporary area containing a set of tools that are known to be good, and that are isolated from the host system. By using the <command>chroot</command> command, the compilations in the remaining chapters will be isolated within that environment, ensuring a clean, trouble-free build of the target LFS system. The build process has been designed to minimize the risks for new readers, and to provide the most educational value at the same time.	The overall goal of <xref linkend="chapter-cross-tools"/> and <xref linkend="chapter-temporary-tools"/> is to produce a temporary area containing a set of tools that are known to be good, and that are isolated from the host system. By using the <command>chroot</command> command, the compilations in the remaining chapters will be isolated within that environment, ensuring a clean, trouble-free build of the target LFS system. The build process has been designed to minimize the risks for new readers, and to provide the most educational value at the same time.
	Linux From Scratch 12.0/part3intro_toolchaintechnotes — French	The overall goal of <xref linkend="chapter-cross-tools"/> and <xref linkend="chapter-temporary-tools"/> is to produce a temporary area containing a set of tools that are known to be good, and that are isolated from the host system. By using the <command>chroot</command> command, the compilations in the remaining chapters will be isolated within that environment, ensuring a clean, trouble-free build of the target LFS system. The build process has been designed to minimize the risks for new readers, and to provide the most educational value at the same time.	Le but global du <xref linkend="chapter-cross-tools"/> et du <xref linkend="chapter-temporary-tools"/> est de générer un espace temporaire comportant un ensemble d'outils connus et approuvés, qui sont isolés du système hôte. En utilisant la commande <command>chroot</command>, les compilations réalisées dans le reste des chapitres se cantonneront à cet environnement, en assurant une construction du système LFS cible propre et sans faille. Le processus de construction a été conçu pour minimiser les risques auprès des nouveaux lecteurs et pour fournir une valeur éducative maximale.
	Linux From Scratch 12.0/part3intro_toolchaintechnotes — Portuguese (Brazil)	The overall goal of <xref linkend="chapter-cross-tools"/> and <xref linkend="chapter-temporary-tools"/> is to produce a temporary area containing a set of tools that are known to be good, and that are isolated from the host system. By using the <command>chroot</command> command, the compilations in the remaining chapters will be isolated within that environment, ensuring a clean, trouble-free build of the target LFS system. The build process has been designed to minimize the risks for new readers, and to provide the most educational value at the same time.	O objetivo geral do <xref linkend="chapter-cross-tools"/> e do <xref linkend="chapter-temporary-tools"/> é o de produzir uma área temporária que contendo um conjunto de ferramentas que são conhecidas por serem boas e que estão isoladas do sistema anfitrião. Usando-se o comando <command>chroot</command>, as compilações nos capítulos subsequentes estarão isolados naquele ambiente, assegurando uma construção limpa e livre de problemas do sistema LFS alvo. O processo de construção foi projetado para minimizar os riscos para leitores(as) novatos(as) e para prover o maior valor educacional ao mesmo tempo.
	Linux From Scratch 12.0/index — Greek	Building the LFS Cross Toolchain and Temporary Tools	Κατασκευή του LFS Cross Toolchain και των προσωρινών εργαλείων
	Linux From Scratch 12.0/chapter08_grep — Greek	Grep-&grep-version;	Grep-&grep-version;
	Linux From Scratch 12.0/prologue_prerequisites — Greek	Because the LFS book assumes <emphasis>at least</emphasis> this basic level of skill, the various LFS support forums are unlikely to provide you with much assistance in these areas. You will find that your questions regarding such basic knowledge will likely go unanswered (or you will simply be referred to the LFS essential pre-reading list).	Επειδή το βιβλίο LFS υποθέτει <emphasis>τουλάχιστον</emphasis> αυτό το βασικό επίπεδο δεξιοτήτων, είναι απίθανο να λάβετε αρκετή βοήθεια από τα διάφορα φόρουμ υποστήριξης του LFS σε αυτούς τους τομείς. Θα διαπιστώσετε ότι οι ερωτήσεις σας σχετικά με τέτοιες βασικές γνώσεις πιθανότατα θα μείνουν αναπάντητες (ή απλώς θα σας ανατεθεί στην αναγκαία λίστα προαπαιτούμενης ανάγνωσης του LFS).
	Linux From Scratch 12.0/prologue_errata — Greek	In addition, the Linux From Scratch editors maintain a list of security vulnerabilities discovered <emphasis>after</emphasis> a book has been released. To read the list, please visit <ulink url="&secadv;"/> before proceeding with your build. You should apply the changes suggested by the advisories to the relevant sections of the book as you build the LFS system. And, if you will use the LFS system as a real desktop or server system, you should continue to consult the advisories and fix any security vulnerabilities, even when the LFS system has been completely constructed.	Επιπλέον, οι επεξεργαστές του Linux From Scratch διατηρούν μια λίστα με προβλήματα ασφαλείας που ανακαλύπτονται <emphasis>μετά την</emphasis> έκδοση ενός βιβλίου. Για να διαβάσετε τη λίστα αυτή, παρακαλούμε επισκεφθείτε το <ulink url="&secadv;"/> πριν συνεχίσετε με τη δημιουργία σας. Θα πρέπει να εφαρμόσετε τις αλλαγές που προτείνονται από τις ειδοποιήσεις στις αντίστοιχες ενότητες του βιβλίου καθώς δημιουργείτε το σύστημα LFS. Επιπλέον, εάν πρόκειται να χρησιμοποιήσετε το σύστημα LFS ως πραγματική επιφάνεια εργασίας ή εξυπηρετητή, θα πρέπει να συνεχίσετε να συμβουλεύεστε τις ειδοποιήσεις και να διορθώνετε οποιαδήποτε προβλήματα ασφαλείας, ακόμα και όταν το σύστημα LFS έχει κατασκευαστεί πλήρως.
	Linux From Scratch 12.0/chapter11_getcounted — Greek	Let's reboot into LFS now.	Ας επανεκκινήσουμε τώρα στο LFS.
	Linux From Scratch 12.0/chapter01_how — Greek	There are many ways to install a Linux distribution and the defaults are usually not optimal for building an LFS system. For suggestions on setting up a commercial distribution see: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.	Υπάρχουν πολλοί τρόποι για την εγκατάσταση μιας διανομής Linux, και οι προεπιλεγμένες ρυθμίσεις συνήθως δεν είναι βέλτιστες για τη δημιουργία ενός συστήματος LFS. Για προτάσεις σχετικά με τη διαμόρφωση μιας εμπορικής διανομής, δείτε: <ulink url="&lfs-root;hints/downloads/files/partitioning-for-lfs.txt"/>.
	Linux From Scratch 12.0/chapter01_whatsnew — Greek	Upgraded to:	Ενημερώθηκαν σε:
	Linux From Scratch 12.0/chapter01_askforhelp — Greek	If you must ask a question directly via an upstream support channel, you shall at least note that many upstream projects have the support channels separated from the bug tracker. The <quote>bug</quote> reports for asking questions are considered invalid and may annoy upstream developers for these projects.	Εάν πρέπει να κάνετε μια ερώτηση απευθείας μέσω ενός υποστηρικτικού καναλιού του δημιουργού πακέτου, πρέπει τουλάχιστον να σημειώσετε ότι πολλά έργα διαχωρίζουν τα κανάλια υποστήριξης από τον ανιχνευτή σφαλμάτων. Οι αναφορές <quote>σφαλμάτων</quote> για ερωτήσεις θεωρούνται μη έγκυρες και ενδέχεται να ενοχλήσουν τους δημιουργούς του πρότζεκτ αυτών των έργων.
	Linux From Scratch 12.0/chapter01_resources — Greek	If during the building of the LFS system you encounter any errors, have any questions, or think there is a typo in the book, please start by consulting the list of Frequently Asked Questions (FAQ), located at <ulink url="&faq-root;"/>.	Εάν κατά τη διάρκεια της κατασκευής του συστήματος LFS αντιμετωπίσετε οποιοδήποτε σφάλμα, έχετε κάποια ερώτηση ή πιστεύετε ότι υπάρχει κάποιο τυπογραφικό στο βιβλίο, παρακαλούμε ξεκινήστε ανατρέχοντας στη λίστα των Συχνών Ερωτήσεων (FAQ), που βρίσκεται στη διεύθυνση <ulink url="&faq-root;"/>.
	Linux From Scratch 12.0/chapter02_creatingpartition — Greek	A minimal system requires a partition of around 10 gigabytes (GB). This is enough to store all the source tarballs and compile the packages. However, if the LFS system is intended to be the primary Linux system, additional software will probably be installed which will require additional space. A 30 GB partition is a reasonable size to provide for growth. The LFS system itself will not take up this much room. A large portion of this requirement is to provide sufficient free temporary storage as well as for adding additional capabilities after LFS is complete. Additionally, compiling packages can require a lot of disk space which will be reclaimed after the package is installed.	Για ένα μινιμαλιστικό σύστημα LFS, θα χρειαστείτε ένα διαμέρισμα περίπου 10 gigabytes (GB). Αυτό είναι αρκετό για να αποθηκεύσετε όλα τα αρχεία tarballs με τον πηγαίο κώδικα και να μεταγλωττίσετε τα πακέτα. Ωστόσο, εάν το σύστημα LFS προορίζεται να είναι το κύριο σας σύστημα Linux, πιθανόν να εγκαταστήσετε επιπλέον λογισμικό που θα απαιτήσει πρόσθετο χώρο. Ένα διαμέρισμα 30 GB είναι μια λογική μέγεθος για μελλοντική ανάπτυξη. Το ίδιο το σύστημα LFS δεν θα καταλάβει τόσο χώρο. Ένα μεγάλο μέρος αυτής της απαίτησης είναι για να παρέχετε επαρκή ελεύθερο χώρο για προσωρινή αποθήκευση, καθώς και για προσθήκη επιπλέον δυνατοτήτων μετά την ολοκλήρωση του LFS. Επιπλέον, η μεταγλώττιση πακέτων μπορεί να απαιτήσει πολύ χώρο στον δίσκο, ο οποίος θα αποκατασταθεί μετά την εγκατάσταση του πακέτου.
	Linux From Scratch 12.0/chapter02_creatingfilesystem — Greek	LFS can use any file system recognized by the Linux kernel, but the most common types are ext3 and ext4. The choice of the right file system can be complex; it depends on the characteristics of the files and the size of the partition. For example:	Το LFS μπορεί να χρησιμοποιήσει οποιοδήποτε σύστημα αρχείων που αναγνωρίζεται από τον πυρήνα Linux, αλλά οι πιο κοινοί τύποι είναι το ext3 και το ext4. Η επιλογή του σωστού συστήματος αρχείων μπορεί να είναι πολύπλοκη και εξαρτάται από τα χαρακτηριστικά των αρχείων και το μέγεθος του διαμερίσματος. Για παράδειγμα:
	Linux From Scratch 12.0/chapter02_aboutlfs — Greek	<userinput>export LFS=<replaceable>/mnt/lfs</replaceable></userinput>	<userinput>export LFS=<replaceable>/mnt/lfs</replaceable></userinput>
	Linux From Scratch 12.0/appendices_creat-comm — Greek	Attribution-NonCommercial-ShareAlike 2.0	Αναφορά-Μη-Εμπορική-Κοινή Διανομή 2.0
	Linux From Scratch 12.0/appendices_udev-rules — Greek	The rules in this appendix are listed for convenience. Installation is normally done via instructions in <xref linkend='ch-system-udev'/>.	Οι κανόνες σε αυτό το παράρτημα παρατίθενται για την ευκολία σας. Η εγκατάσταση πραγματοποιείται συνήθως μέσω των οδηγιών που παρέχονται στην ενότητα <xref linkend='ch-system-udev'/>.
	Linux From Scratch 12.0/appendices_license — Greek	This book is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 2.0 License.	Αυτό το βιβλίο έχει άδεια χρήσης υπό την Άδεια Creative Commons Αναφορά Δημιουργού - Μη Εμπορική Χρήση - Παρόμοια Διανομή 2.0.
	Linux From Scratch 12.0/appendices_acronymlist — Greek	<?dbfo list-presentation="list"?> <?dbhtml list-presentation="table"?>	<?dbfo list-presentation="list"?> <?dbhtml list-presentation="table"?>
	Linux From Scratch 12.0/appendices_scripts — Greek	The scripts in this appendix are listed by the directory where they normally reside. The order is <filename class='directory'>/etc/rc.d/init.d</filename>, <filename class='directory'>/etc/sysconfig</filename>, <filename class='directory'>/etc/sysconfig/network-devices</filename>, and <filename class='directory'>/etc/sysconfig/network-devices/services</filename>. Within each section, the files are listed in the order they are normally called.	Τα σενάρια σε αυτό το παράρτημα καταχωρίζονται ανά κατάλογο όπου συνήθως διαμένουν. Η σειρά είναι <filename class='directory'>/etc/rc.d/init.d</filename>, <filename class='directory'>/etc/sysconfig</filename>, <filename class='directory'>/etc/sysconfig/network-devices</filename>, and <filename class='directory'>/etc/sysconfig/network-devices/services</filename>. Εντός κάθε ενότητας, τα αρχεία καταχωρίζονται με τη σειρά που συνήθως καλούνται.
	Linux From Scratch 12.0/appendices_mit-lic — Greek	Copyright &copy; &copyrightdate; Gerard Beekmans	Πνευματικά δικαιώματα &copy; &copyrightdate; Gerard Beekmans
	Linux From Scratch 12.0/appendices_acknowledgments — Greek	We would like to thank the following people and organizations for their contributions to the Linux From Scratch Project.	Θα θέλαμε να ευχαριστήσουμε τα παρακάτω άτομα και οργανισμούς για τις συνεισφορές τους στο έργο του Linux From Scratch.
	Linux From Scratch 12.0/appendices_dependencies — Greek	Every package built in LFS relies on one or more other packages in order to build and install properly. Some packages even participate in circular dependencies, that is, the first package depends on the second which in turn depends on the first. Because of these dependencies, the order in which packages are built in LFS is very important. The purpose of this page is to document the dependencies of each package built in LFS.	Κάθε πακέτο που δημιουργείται στο LFS βασίζεται σε ένα ή περισσότερα άλλα πακέτα προκειμένου να δημιουργηθεί και να εγκατασταθεί σωστά. Κάποια πακέτα συμμετέχουν ακόμη και σε κυκλικές εξαρτήσεις, δηλαδή το πρώτο πακέτο εξαρτάται από το δεύτερο, το οποίο, αντίστροφα, εξαρτάται από το πρώτο. Λόγω αυτών των εξαρτήσεων, η σειρά με την οποία δημιουργούνται τα πακέτα στο LFS είναι πολύ σημαντική. Ο σκοπός αυτής της σελίδας είναι να καταγράψει τις εξαρτήσεις κάθε πακέτου που δημιουργείται στο LFS.
	Linux From Scratch 12.0/chapter01_changelog — Greek	Below is a list of changes made since the previous release of the book.	Παρακάτω υπάρχει μια λίστα αλλαγών που έχουν γίνει από την προηγούμενη έκδοση του βιβλίου.
	Linux From Scratch 12.0/index — English	Building the LFS System	Building the LFS System
	Linux From Scratch 12.0/index — French	Building the LFS System	Construction du système LFS
	Linux From Scratch 12.0/index — Portuguese (Brazil)	Building the LFS System	Construindo o Sistema LFS
	Linux From Scratch 12.0/index — Chinese (Simplified Han script)	Building the LFS System	构建 LFS 系统
	Linux From Scratch 12.0/chapter02_mounting — English	Create the mount point and mount the LFS file system with these commands:	Create the mount point and mount the LFS file system with these commands:
	Linux From Scratch 12.0/chapter02_mounting — French	Create the mount point and mount the LFS file system with these commands:	Créez le point de montage et montez le système de fichiers LFS en exécutant la commande suivante&nbsp;:
	Linux From Scratch 12.0/chapter02_mounting — Portuguese (Brazil)	Create the mount point and mount the LFS file system with these commands:	Crie o ponto de montagem e monte o sistema de arquivos do LFS com estes comandos:
	Linux From Scratch 12.0/chapter02_stages — English	These chapters run commands on the host system. When restarting, be certain of one thing:	These chapters run commands on the host system. When restarting, be certain of one thing:
	Linux From Scratch 12.0/chapter02_stages — French	These chapters run commands on the host system. When restarting, be certain of one thing:	Ces chapitres exécutent des commandes sur le système hôte. En cas de redémarrage, vérifiez une chose&nbsp;:
	Linux From Scratch 12.0/chapter02_stages — Portuguese (Brazil)	These chapters run commands on the host system. When restarting, be certain of one thing:	Esses capítulos executam comandos no sistema anfitrião. Quando da reinicialização, esteja certo(a) de uma coisa:
	Linux From Scratch 12.0/chapter02_creatingpartition — English	Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as <systemitem class="filesystem">swap</systemitem> space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The <systemitem class="filesystem">swap</systemitem> partition for an LFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.	Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as <systemitem class="filesystem">swap</systemitem> space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The <systemitem class="filesystem">swap</systemitem> partition for an LFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.
	Linux From Scratch 12.0/chapter02_creatingpartition — French	Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as <systemitem class="filesystem">swap</systemitem> space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The <systemitem class="filesystem">swap</systemitem> partition for an LFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.	Parce qu'il n'y a pas toujours assez de mémoire vive (RAM) disponible pour les processus de compilation, il est conseillé d'utiliser une petite partition comme espace d'échange <systemitem class="filesystem">swap</systemitem>. Le noyau utilise cet espace pour stocker des données rarement utilisées et pour laisser plus de mémoire aux processus actifs. Il se peut que la partition <systemitem class="filesystem">swap</systemitem> pour un système LFS soit la même que celle utilisée par le système hôte, auquel cas il n'est pas nécessaire de créer une autre partition si votre système hôte possède déjà cette configuration.
	Linux From Scratch 12.0/chapter02_creatingpartition — Portuguese (Brazil)	Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as <systemitem class="filesystem">swap</systemitem> space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The <systemitem class="filesystem">swap</systemitem> partition for an LFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.	Como nem sempre existe Memória de Acesso Aleatório (RAM) suficiente disponível para processos de compilação, é uma boa ideia usar uma pequena partição de disco como espaço de <systemitem class="filesystem">swap</systemitem>. Ele é usado pelo kernel para armazenar dados raramente usados e deixa mais memória disponível para processos ativos. A partição de <systemitem class="filesystem">swap</systemitem> para um sistema LFS pode ser a mesma que aquela usada pelo sistema anfitrião, caso no qual não é necessário criar outra.
	Linux From Scratch 12.0/chapter02_creatingpartition — Chinese (Simplified Han script)	Because there is not always enough Random Access Memory (RAM) available for compilation processes, it is a good idea to use a small disk partition as <systemitem class="filesystem">swap</systemitem> space. This is used by the kernel to store seldom-used data and leave more memory available for active processes. The <systemitem class="filesystem">swap</systemitem> partition for an LFS system can be the same as the one used by the host system, in which case it is not necessary to create another one.	计算机未必有足够满足编译过程要求的内存 (RAM) 空间，因此可以使用一个小的磁盘分区作为 <systemitem class="filesystem">swap</systemitem> 空间。内核使用此分区存储很少使用的数据，从而为活动进程留出更多内存。LFS 的 <systemitem class="filesystem">swap</systemitem> 分区可以和宿主系统共用，这样就不用专门为 LFS 创建一个。
	Linux From Scratch 12.0/chapter07_util-linux — English	Util-linux	Util-linux
	Linux From Scratch 12.0/chapter07_util-linux — French	Util-linux	Util-linux
	Linux From Scratch 12.0/chapter07_util-linux — Portuguese (Brazil)	Util-linux	Util-linux
	Linux From Scratch 12.0/chapter07_util-linux — Chinese (Simplified Han script)	Util-linux	Util-linux
	Linux From Scratch 12.0/chapter07_introduction — English	Until <xref linkend="ch-tools-chroot"/>, the commands must be run as <systemitem class="username">root</systemitem>, with the <envar>LFS</envar> variable set. After entering chroot, all commands are run as &root;, fortunately without access to the OS of the computer you built LFS on. Be careful anyway, as it is easy to destroy the whole LFS system with bad commands.	Until <xref linkend="ch-tools-chroot"/>, the commands must be run as <systemitem class="username">root</systemitem>, with the <envar>LFS</envar> variable set. After entering chroot, all commands are run as &root;, fortunately without access to the OS of the computer you built LFS on. Be careful anyway, as it is easy to destroy the whole LFS system with bad commands.
	Linux From Scratch 12.0/chapter07_introduction — French	Until <xref linkend="ch-tools-chroot"/>, the commands must be run as <systemitem class="username">root</systemitem>, with the <envar>LFS</envar> variable set. After entering chroot, all commands are run as &root;, fortunately without access to the OS of the computer you built LFS on. Be careful anyway, as it is easy to destroy the whole LFS system with bad commands.	Jusqu'à la <xref linkend="ch-tools-chroot"/>, les commandes doivent être exécutées en tant qu’utilisateur <systemitem class="username">root</systemitem> avec la variable d'environnement <envar>LFS</envar>. Une fois entrées dans le chroot, toutes les commandes sont exécutées en tant qu’utilisateur &root;, heureusement sans avoir accès à l'OS de l'ordinateur sur lequel vous construisez LFS. Restez prudent malgré tout, car il est facile d’altérer l’entièreté du système LFS en exécutant de mauvaises commandes.
	Linux From Scratch 12.0/chapter07_introduction — Portuguese (Brazil)	Until <xref linkend="ch-tools-chroot"/>, the commands must be run as <systemitem class="username">root</systemitem>, with the <envar>LFS</envar> variable set. After entering chroot, all commands are run as &root;, fortunately without access to the OS of the computer you built LFS on. Be careful anyway, as it is easy to destroy the whole LFS system with bad commands.	Até a <xref linkend="ch-tools-chroot"/>, os comandos precisam ser executados como <systemitem class="username">root</systemitem>, com a variável <envar>LFS</envar> configurada. Após a entrada no chroot, todos os comandos são executados como &root;, por sorte sem acesso ao SO do computador no qual que você construiu o LFS. Seja cuidadoso(a) de qualquer maneira, dado que é fácil destruir o sistema LFS inteiro com comandos mau formados.
	Linux From Scratch 12.0/chapter02_hostreqs — English	Software	Software
	Linux From Scratch 12.0/chapter02_hostreqs — French	Software	Logiciel
	Linux From Scratch 12.0/chapter02_hostreqs — Portuguese (Brazil)	Software	Software
	Linux From Scratch 12.0/chapter07_cleanup — English	<userinput>rm -rf /usr/share/{info,man,doc}/*</userinput>	<userinput>rm -rf /usr/share/{info,man,doc}/*</userinput>
	Linux From Scratch 12.0/chapter07_cleanup — French	<userinput>rm -rf /usr/share/{info,man,doc}/*</userinput>	<userinput>rm -rf /usr/share/{info,man,doc}/*</userinput>
	Linux From Scratch 12.0/chapter07_cleanup — Portuguese (Brazil)	<userinput>rm -rf /usr/share/{info,man,doc}/*</userinput>	<userinput>rm -rf /usr/share/{info,man,doc}/*</userinput>
	Linux From Scratch 12.0/chapter02_creatingfilesystem — English	ext2	ext2
	Linux From Scratch 12.0/chapter02_creatingfilesystem — French	ext2	ext2
	Linux From Scratch 12.0/chapter02_creatingfilesystem — Portuguese (Brazil)	ext2	ext2
	Linux From Scratch 12.0/chapter02_creatingfilesystem — Chinese (Simplified Han script)	ext2	ext2
	Linux From Scratch 12.0/chapter07_perl — English	Perl	Perl
	Linux From Scratch 12.0/chapter07_perl — French	Perl	Perl

• 24 / 349
  / 349