Source strings

107 Strings 100%
Browse Translate
2,420 Words 100%
17,682 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
107 2,420 17,682
All strings Browse Translate Zen
107 2,420 17,682
Read-only strings Browse Translate Zen

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 trunk
Last remote commit Automatic BLFS commit based on 3ff7a891478c883722a2f0de6c83d6b02310454a a23a67f42f
Julien Lepiller authored 7 hours ago
Last commit in Weblate Automatic BLFS commit based on 3ff7a891478c883722a2f0de6c83d6b02310454a a23a67f42f
Julien Lepiller authored 7 hours ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter10/kernel.po
Translation file Not available
Last change Dec. 13, 2024, 4:19 p.m.
Last author None
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 107 2,420 17,682
Translated 100% 107 100% 2,420 100% 17,682
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 107 100% 2,420 100% 17,682
Failing checks 0% 0 0% 0 0% 0
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 2 changes 0 changes 1 change 0 changes 1 change 113 changes 0 changes 1 change 0 changes 0 changes 0 changes 1 change 1 change 9 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 1 change 0 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

2,420
Hosted words
107
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Source string added
On the other hand, if you've upgraded GCC, you should run <command>make clean</command> to purge all the <filename class='extension'>.o</filename> files from the previous build, or the new build may fail.
8 days ago
User avatar None

Source string added
If you are updating the configuration and rebuilding the kernel from a retained kernel source tree, normally you should <emphasis role='bold'>not</emphasis> run the <command>make mrproper</command> command. The command would purge the <filename>.config</filename> file and all the <filename class='extension'>.o</filename> files from the previous build. Despite it's easy to restore <filename>.config</filename> from the copy in <filename class='directory'>/boot</filename>, purging all the <filename class='extension'>.o</filename> files is still a waste: for a simple configuration change, often only a few <filename class='extension'>.o</filename> files need to be (re)built and the kernel build system will correctly skip other <filename class='extension'>.o</filename> files if they are not purged.
8 days ago
User avatar None

Source string added
This will make the kernel correctly display the message in case a kernel panic happens and a running DRM driver supports to do so. Without this, it would be more difficult to diagnose a panic: if no DRM driver is running, we'd be on the VGA console which can only hold 24 lines and the relevant kernel message is often flushed away; if a DRM driver is running, the display is often completely messed up on panic. As of Linux-6.12, none of the dedicated drivers for mainstream GPU models really supports this, but it's supported by the <quote>Simple framebuffer driver</quote> which runs on the VESA (or EFI) framebuffer before the dedicated GPU driver is loaded. If the dedicated GPU driver is built as a module (instead of a part of the kernel image) and no initramfs is used, this functionality will work just fine before the root file system is mounted and it's already enough for providing information about most LFS configuration errors causing a panic (for example, an incorrect <parameter>root=</parameter> setting in <xref linkend='ch-bootable-grub'/>).
2 weeks ago
User avatar None

Source string added
These are needed to display the Linux console on a GPU driven by a DRI (Direct Rendering Infrastructure) driver. As <option>CONFIG_DRM</option> (Direct Rendering Manager) is enabled, we should enable these two options as well or we'll see a blank screen once the DRI driver is loaded.
2 weeks ago
User avatar None

Source string added
These allow to use the VESA framebuffer (or the EFI framebuffer if booting the LFS system via UEFI) as a DRM device. The VESA framebuffer will be set up by GRUB (or the EFI framebuffer will be set up by the UEFI firmware), so the DRM panic handler can function before the GPU-specific DRM driver is loaded.
2 weeks ago
User avatar None

Source string added
<parameter> Mark VGA/VBE/EFI FB as generic system framebuffer </parameter> and <parameter>Simple framebuffer driver</parameter>
2 weeks ago
User avatar None

Source string added
Set this <literal>kmsg</literal> to make sure the last kernel messages lines are displayed when a kernel panic happens. The default, <literal>user</literal>, would make the kernel show only a <quote>user friendly</quote> panic message which is not helpful on diagnostic. The third choice, <literal>qr_code</literal>, would make the kernel to compress the last kernel message lines into a QR code and display it. The QR code can hold more message lines than plain text and it can be decoded with an external device (like a smart phone). But it requires a Rust compiler that LFS does not provide.
2 weeks ago
User avatar None

Source string added
<parameter> Panic screen formatter </parameter>
2 weeks ago
User avatar None

Source string added
<parameter> Display a user-friendly message when a kernel panic occurs </parameter>
2 weeks ago
User avatar None

Source string added
If you've decided to use a separate &boot-dir; partition for the LFS system (maybe sharing a &boot-dir; partition with the host distro), the files copied below should go there. The easiest way to do that is to create the entry for &boot-dir; in &fstab; first (read the previous section for details), then issue the following command as the &root; user in the <emphasis>chroot environment</emphasis>:
a month ago
Browse all translation changes