Source strings

43 Strings 100%
Browse Translate
1,568 Words 100%
11,086 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
43 1,568 11,086
All strings Browse Translate Zen
43 1,568 11,086
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 7ef1db772f3ce108a14d196d2f8faed9ae5607ad 621f4aa8f9
Julien Lepiller authored an hour ago
Last commit in Weblate Automatic BLFS commit based on 7ef1db772f3ce108a14d196d2f8faed9ae5607ad 621f4aa8f9
Julien Lepiller authored an hour ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter09/symlinks.po
Translation file Not available
Last change June 22, 2024, 5:19 a.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,900,209
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 43 1,568 11,086
Translated 100% 43 100% 1,568 100% 11,086
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 43 100% 1,568 100% 11,086
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

41 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

1,568
Hosted words
43
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

Source string added
As explained in <xref linkend="ch-config-udev" role=','/> the order in which devices with the same function appear in <filename class="directory">/dev</filename> is essentially random. E.g., if you have a USB web camera and a TV tuner, sometimes <filename>/dev/video0</filename> refers to the camera and <filename>/dev/video1</filename> refers to the tuner, and sometimes after a reboot the order changes. For all classes of hardware except sound cards and network cards, this is fixable by creating udev rules to create persistent symlinks. The case of network cards is covered separately in <xref linkend="ch-config-network" role=','/> and sound card configuration can be found in <ulink url="&blfs-book;postlfs/devices.html">BLFS</ulink>.
8 months ago
User avatar None

Source string added
The traditional naming scheme using eth0, eth1, etc. can be restored by adding <userinput>net.ifnames=0</userinput> on the kernel command line. This is most appropriate for systems that have just one ethernet device of a particular type. Laptops often have two ethernet connections named eth0 and wlan0; such laptops can also use this method. The command line is in the GRUB configuration file. See <xref linkend="grub-cfg" role='.'/>
8 months ago
User avatar None

Source string added
<userinput>sed -e '/^AlternativeNamesPolicy/s/=.*$/=/' \
/usr/lib/udev/network/99-default.link \
> /etc/udev/network/99-default.link</userinput>
9 months ago
User avatar None

Source string added
Even if the custom udev rule file is created, udev may still assign one or more alternative names for a NIC based on physical characteristics. If a custom udev rule would rename some NIC using a name already assigned as an alternative name of another NIC, this udev rule will fail. If this issue happens, you may create the <filename>/etc/udev/network/99-default.link</filename> configuration file with an empty alternative assignment policy, overriding the default configuration file <filename>/usr/lib/udev/network/99-default.link</filename>:
a year ago
User avatar None

Source string added
The result is that <filename>/dev/video0</filename> and <filename>/dev/video1</filename> devices still refer randomly to the tuner and the web camera (and thus should never be used directly), but there are symlinks <filename>/dev/tvtuner</filename> and <filename>/dev/webcam</filename> that always point to the correct device.
2 years ago
User avatar None

Source string added
<userinput>cat &gt; /etc/udev/rules.d/83-duplicate_devs.rules &lt;&lt; "EOF"
<literal>
# Persistent symlinks for webcam and tuner
KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", SYMLINK+="webcam"
KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", SYMLINK+="tvtuner"
</literal>
EOF</userinput>
2 years ago
User avatar None

Source string added
Then write rules that create the symlinks, e.g.:
2 years ago
User avatar None

Source string added
<userinput>udevadm info -a -p /sys/class/video4linux/video0</userinput>
2 years ago
User avatar None

Source string added
For each of your devices that is likely to have this problem (even if the problem doesn't exist in your current Linux distribution), find the corresponding directory under <filename class="directory">/sys/class</filename> or <filename class="directory">/sys/block</filename>. For video devices, this may be <filename class="directory">/sys/class/video4linux/video<replaceable>X</replaceable></filename>. Figure out the attributes that identify the device uniquely (usually, vendor and product IDs and/or serial numbers work):
2 years ago
User avatar None

Source string added
Dealing with Duplicate Devices
2 years ago
Browse all translation changes