Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 100% 0 0 0 0 4 0 0
French 100% 0 0 0 0 41 0 0
Portuguese (Brazil) 0 0 0 0 0 0 0
Please sign in to see the alerts.

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch 12.1
Last remote commit Add pt_BR translation e751a3b16e
Julien Lepiller authored 9 months ago
Last commit in Weblate Translated using Weblate (Portuguese (Brazil)) 75579e8588
User avatar jamenson authored 8 months ago
Weblate repository https://translate.linuxfromscratch.org/git/linux-from-scratch-12-1/index/
File mask blfs/*/introduction/important/building-notes.po
a week ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 549 20,760 146,082
Source 183 6,920 48,694
Translated 100% 549 100% 20,760 100% 146,082
Needs editing 0% 0 0% 0 0% 0
Read-only 33% 183 33% 6,920 33% 48,694
Failing checks 8% 45 6% 1,336 7% 10,255
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 368 changes 0 changes 0 changes 0 changes 193 changes 0 changes 30 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

20,760
Hosted words
549
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Changes committed
Changes committed 8 months ago
User avatar jamenson

Translation completed
Translation completed 8 months ago
User avatar jamenson

Translation changed
For hardening options which are reasonably cheap, there is some discussion in the 'tuning' link above (occasionally, one or more of these options might be inappropriate for a package). These options are <option>-D_FORTIFY_SOURCE=2</option> (or <option>-D_FORTIFY_SOURCE=3</option> which is more secure but with a larger performance overhead) and (for C++) <option>-D_GLIBCXX_ASSERTIONS</option>. On modern machines these should only have a little impact on how fast things run, and often they will not be noticeable.
Para opções de reforço que são razoavelmente baratas, existe alguma discussão no link "ajuste" acima (ocasionalmente, uma ou mais dessas opções podem ser inadequadas para um pacote). Essas opções são <option>-D_FORTIFY_SOURCE=2</option> (ou <option>-D_FORTIFY_SOURCE=3</option> que é mais seguro, mas com maior sobrecarga de desempenho) e (para "C++") <option>-D_GLIBCXX_ASSERTIONS</option>. Nas máquinas modernas, isso deveria ter somente um pequeno impacto na rapidez com que as coisas funcionexecutam e, muitas vezes, não serão perceptíveis.
8 months ago
User avatar jamenson

Translation changed
Like <command>ninja</command>, by default <command>cargo</command> uses all logical cores. This can often be worked around, either by exporting <envar>CARGO_BUILD_JOBS=<replaceable>&lt;N&gt;</replaceable></envar> or passing <option>--jobs <replaceable>&lt;N&gt;</replaceable></option> to <command>cargo</command>. For compiling rustc itself, specifying <option>--jobs <replaceable>&lt;N&gt;</replaceable></option> for invocations of <command>x.py</command> (together with the <envar>CARGO_BUILD_JOBS</envar> environment variable, which looks like a <quote>belt and braces</quote> approach but seems to be necessary) mostly works. The exception is running the tests when building rustc, some of them will nevertheless use all online CPUs, at least as of rustc-1.42.0.
Semelhante ao <command>ninja</command>, por padrão <command>cargo</command> usa todos os processadorenúcleos lógicos. Isso frequentemente pode ser contornado, seja exportando-se <envar>CARGO_BUILD_JOBS=<replaceable>&lt;N&gt;</replaceable></envar> seja passando-se <option>--jobs <replaceable>&lt;N&gt;</replaceable></option> para <command>cargo</command>. Para compilar o próprio rustc, especificar-se <option>--jobs <replaceable>&lt;N&gt;</replaceable></option> para invocações do <command>x.py</command> (juntamente com a variável de ambiente <envar>CARGO_BUILD_JOBS=</envar>, que se parece com uma abordagem <quote>cinto e suspensórios</quote>, porém parece ser necessária) funciona na maioria. A exceção é a de executar-se os testes quando construir-se o rustc; alguns deles, ainda assim, usarão todas as CPUs online, pelo menos desde o rustc-1.42.0.
8 months ago
User avatar jamenson

Translation added
Read the <filename>Documentation/admin-guide/cgroup-v2.rst</filename> file in the Linux kernel source tree for the detailed explanation of <systemitem class="filesystem">cgroup2</systemitem> pseudo file system entries referred in the command.
Leia-se o arquivo <filename>Documentation/admin-guide/cgroup-v2.rst</filename> na árvore do fonte do núcleo Linux para a explicação detalhada das entradas do pseudo sistema de arquivos <systemitem class="filesystem">cgroup2</systemitem> referidas no comando.
8 months ago
User avatar jamenson

Translation added
Read the man pages <ulink role='man' url='&man;systemd-run.1'>systemd-run(1)</ulink> and <ulink role='man' url='&man;systemd.resource-control.5'>systemd.resource-control(5)</ulink> for the detailed explanation of parameters in the command.
Leiam-se as páginas de manual <ulink role='man' url='&man;systemd-run.1'>systemd-run(1)</ulink> e <ulink role='man' url='&man;systemd.resource-control.5'>systemd.resource-control(5)</ulink> para a explicação detalhada dos parâmetros no comando.
8 months ago
User avatar jamenson

Translation added
When the <command>nproc</command> or <command>ninja</command> command runs in a cgroup, it will use the number of logical cores assigned to the cgroup as the <quote>system logical core count</quote>. For example, in a cgroup with logical cores 0-3 assigned, <command>nproc</command> will print <computeroutput>4</computeroutput>, and <command>ninja</command> will run 6 (4 + 2) jobs simultaneously if no <option>-j</option> setting is explicitly given.
Quando o comando <command>nproc</command> ou <command>ninja</command> executa em um cgroup, ele usará o número de núcleos lógicos atribuídos para o cgroup como a <quote>contagem de núcleos lógicos do sistema</quote>. Por exemplo, em um cgroup com núcleos lógicos 0-3 atribuídos, <command>nproc</command> imprimirá <computeroutput>4</computeroutput> e <command>ninja</command> executará 6 (4 + 2) tarefas simultaneamente se nenhuma configuração <option>-j</option> for fornecida explicitamente.
8 months ago
User avatar jamenson

Translation changed
<phrase revision='systemd'> <parameter>AllowedCPUs=0-3</parameter> </phrase> <phrase revision='sysv'> <literal>0-3</literal> in the <filename>cpuset.cpus</filename> entry </phrase> makes the kernel only run the processes in the cgroup on the logical cores with numbers 0, 1, 2, or 3. You may need to adjust this setting based the mapping between the logical cores and the physical cores. For example, with an Intel Core i9-13900K CPU, the logical cores 0, 2, 4, ..., 14 are mapped to the first threads of the eight physical P cores, the logical cores 1, 3, 5, ..., 15 are mapped to the second threads of the physical P cores, and the logical cores 16, 17, ..., 31 are mapped to the 16 physical E cores. So if we want to use four threads from four different P cores, we need to specify <literal>0,2,4,6</literal> instead of <literal>0-3</literal>. Note that the other CPU models may use a different mapping scheme. If you are not sure about the mapping between the logical cores and the physical cores, run <command>grep -E '^processor|^core' /proc/cpuinfo</command> which will output logical core IDs in the <computeroutput>processor</computeroutput> lines, and physical core IDs in the <computeroutput>core id</computeroutput> lines.
<phrase revision='systemd'> <parameter>AllowedCPUs=0-3</parameter> </phrase> <phrase revision='sysv'> <literal>0-3</literal> na entrada <filename>cpuset.cpus</filename> </phrase> faz com que o núcleo execute somente os processos no cgroup nos núcleos lógicos com números 0, 1, 2 ou 3. Você possivelmente precise ajustar essa configuração baseada no mapeamento entre os núcleos lógicos e os núcleos físicos. Por exemplo, com uma CPU Intel Core i9-13900K, os núcleos lógicos 0, 2, 4, ..., 14 são mapeados para as primeiras camadas dos oito núcleos P físicos; os núcleos lógicos 1, 3, 5, ..., 15 são mapeados para as segundas camadas dos núcleos P físicos; e os núcleos lógicos 16, 17, ..., 31 são mapeados para os 16 núcleos E físicos. Portanto, se quisermos usar quatro camadas de quatro núcleos P, precisamos especificar <literal>0,2,4,6</literal> em vez de <literal>0-3</literal>. Observe que os outros modelos de CPU podem usar um esquema de mapeamento diferente. Se você não tiver certeza acerca do mapeamento entre os núcleos lógicos e os núcleos físicos, execute <command>grep -E '^processor|^core' /proc/cpuinfo</command> que gerará IDs de núcleo lógico nas linhas <computeroutput>processor</computeroutput> e IDs de núcleo físico nas linhas <computeroutput>core id</computeroutput>.
8 months ago
User avatar jamenson

Translation added
<phrase revision='systemd'> <parameter>AllowedCPUs=0-3</parameter> </phrase> <phrase revision='sysv'> <literal>0-3</literal> in the <filename>cpuset.cpus</filename> entry </phrase> makes the kernel only run the processes in the cgroup on the logical cores with numbers 0, 1, 2, or 3. You may need to adjust this setting based the mapping between the logical cores and the physical cores. For example, with an Intel Core i9-13900K CPU, the logical cores 0, 2, 4, ..., 14 are mapped to the first threads of the eight physical P cores, the logical cores 1, 3, 5, ..., 15 are mapped to the second threads of the physical P cores, and the logical cores 16, 17, ..., 31 are mapped to the 16 physical E cores. So if we want to use four threads from four different P cores, we need to specify <literal>0,2,4,6</literal> instead of <literal>0-3</literal>. Note that the other CPU models may use a different mapping scheme. If you are not sure about the mapping between the logical cores and the physical cores, run <command>grep -E '^processor|^core' /proc/cpuinfo</command> which will output logical core IDs in the <computeroutput>processor</computeroutput> lines, and physical core IDs in the <computeroutput>core id</computeroutput> lines.
<phrase revision='systemd'> <parameter>AllowedCPUs=0-3</parameter> </phrase> <phrase revision='sysv'> <literal>0-3</literal> na entrada <filename>cpuset.cpus</filename> </phrase> faz com que o núcleo execute somente os processos no cgroup nos núcleos lógicos com números 0, 1, 2 ou 3. Você possivelmente precise ajustar essa configuração baseada no mapeamento entre os núcleos lógicos e o núcleos físicos. Por exemplo, com uma CPU Intel Core i9-13900K, os núcleos lógicos 0, 2, 4, ..., 14 são mapeados para as primeiras camadas dos oito núcleos P físicos; os núcleos lógicos 1, 3, 5, ..., 15 são mapeados para as segundas camadas dos núcleos P físicos; e os núcleos lógicos 16, 17, ..., 31 são mapeados para os 16 núcleos E físicos. Portanto, se quisermos usar quatro camadas de quatro núcleos P, precisamos especificar <literal>0,2,4,6</literal> em vez de <literal>0-3</literal>. Observe que os outros modelos de CPU podem usar um esquema de mapeamento diferente. Se você não tiver certeza acerca do mapeamento entre os núcleos lógicos e os núcleos físicos, execute <command>grep -E '^processor|^core' /proc/cpuinfo</command> que gerará IDs de núcleo lógico nas linhas <computeroutput>processor</computeroutput> e IDs de núcleo físico nas linhas <computeroutput>core id</computeroutput>.
8 months ago
User avatar jamenson

Translation added
With <phrase revision='systemd'> <parameter>MemoryHigh=8G</parameter> </phrase> <phrase revision='sysv'> <literal>8589934592</literal> (the output of <userinput>bc -e '8*2^30'</userinput>, 2^30 represents 2<superscript>30</superscript>, i.e. a Gigabyte) in the <filename>memory.high</filename> entry </phrase>, a soft limit of memory usage is set. If the processes in the cgroup (<command>make</command> and all the descendants of it) uses more than 8 GB of system memory in total, the kernel will throttle down the processes and try to reclaim the system memory from them. But they can still use more than 8 GB of system memory. If you want to make a hard limit instead, replace <phrase revision='systemd'> <parameter>MemoryHigh</parameter> with <parameter>MemoryMax</parameter>. </phrase> <phrase revision='sysv'> <filename>memory.high</filename> with <filename>memory.max</filename>. </phrase> But doing so will cause the processes killed if 8 GB is not enough for them.
Com <phrase revision='systemd'> <parameter>MemoryHigh=8G</parameter> </phrase> <phrase revision='sysv'> <literal>8589934592</literal> (a saída gerada de <userinput>bc -e '8*2^30'</userinput>, 2^30 representa 2<superscript>30</superscript>, ou seja, um Gigabyte) na entrada <filename>memory.high</filename> </phrase>, um limite flexível de uso de memória está configurado. Se os processos no cgroup (<command>make</command> e todos os descendentes dele) usarem mais de 8 GB de memória do sistema no total, o núcleo irá desacelerar os processos e tentará recuperar a memória do sistema proveniente deles. Mas eles ainda podem usar mais de 8 GB de memória do sistema. Se você quiser definir um limite rígido, substitua <phrase revision='systemd'> <parameter>MemoryHigh</parameter> por <parameter>MemoryMax</parameter>. </phrase> <phrase revision='sysv'> <filename>memory.high</filename> com <filename>memory.max</filename>. </phrase> Mas fazer isso causará a interrupção dos processos se 8 GB não forem suficientes para eles.
8 months ago
Browse all component changes