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 60cda8c2b0376c008d93bbb64d8ccbbaccdcf0c0 1c94b17ae1
Julien Lepiller authored an hour ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask blfs/*/postlfs/config/skel.po
Translation file Download blfs/fr/postlfs/config/skel.po
Last change None
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 22 677 5,461
Translated 100% 22 100% 677 100% 5,461
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 22% 5 7% 48 10% 580
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 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 0 changes 0 changes 23 changes 0 changes 0 changes 0 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

677
Hosted words
22
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource update

Beyond Linux From Scratch / postlfs_config_skel — French

File blfs/fr/postlfs/config/skel.po was added. 3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

<userinput>groupadd -g <replaceable>&lt;GID&gt;</replaceable> <replaceable>&lt;username&gt;</replaceable> &amp;&amp;
useradd -u <replaceable>&lt;UID&gt;</replaceable> -g <replaceable>&lt;username&gt;</replaceable> <replaceable>&lt;username&gt;</replaceable></userinput>
<userinput>groupadd -g <replaceable>&lt;GID&gt;</replaceable> <replaceable>&lt;username&gt;</replaceable> &amp;&amp;
useradd -u <replaceable>&lt;UID&gt;</replaceable> -g <replaceable>&lt;username&gt;</replaceable> <replaceable>&lt;username&gt;</replaceable></userinput>
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

The command should output the UID and GID, separated by a colon. Now on the BLFS system, create the primary group and the user:
La commande devrait montrer l'UID et le GID, séparés par une virgule. Maintenant sur le système BLFS, créez le groupe principal et l'utilisateur&nbsp;…
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

<userinput>getent passwd <replaceable>&lt;username&gt;</replaceable> | cut -d ':' -f 3,4</userinput>
<userinput>getent passwd <replaceable>&lt;username&gt;</replaceable> | cut -d ':' -f 3,4</userinput>
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

If you are sharing a <filename class="directory">/home</filename> or <filename class="directory">/usr/src</filename> with another Linux distro (for example, the host distro used for building LFS), you can create a user with the same UID (and, same primary group GID) to keep the file ownership consistent across the systems. First, on <emphasis>the other distro</emphasis>, get the UID of the user and the GID of the user's primary group:
Si vous partagez votre <filename class="directory">/home</filename> ou votre <filename class="directory">/usr/src</filename> avec une autre distribution Linux (par exemple, la distribution hôte utilisée pour construire LFS), vous pouvez créer un utilisateur avec le même UID (et le même GID de groupe principal) pour garder des droits cohérents sur ces systèmes. Tout d'abord, sur <emphasis>l'autre distro</emphasis>, récupérez l'UID de l'utilisateur et le GID de son groupe principal&nbsp;:
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

<userinput>useradd -m <replaceable>&lt;newuser&gt;</replaceable></userinput>
<userinput>useradd -m <replaceable>&lt;newuser&gt;</replaceable></userinput>
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

When adding a new user with <command>useradd</command>, use the <option>-m</option> parameter, which tells <command>useradd</command> to create the user's home directory and copy files from <filename class="directory">/etc/skel</filename> (can be overridden) to the new user's home directory. For example (perform as the <systemitem class="username">root</systemitem> user):
Lors de l'ajout d'un nouvel utilisateur avec <command>useradd</command>, utilisez le paramètre <option>-m</option> qui dit à <command>useradd</command> de créer le répertoire home de l'utilisateur et de copier les fichiers de <filename class="directory">/etc/skel</filename> (il peut être écrasé) vers le répertoire home du nouvel utilisateur. Par exemple (effectuez ceci en tant qu'utilisateur <systemitem class="username">root</systemitem>)&nbsp;:
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

When Adding a User
Lors de l'ajout d'un utilisateur
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

You will run a slightly modified set of commands for files which are placed in <filename class="directory">/etc/skel</filename>. Each section will remind you of this. In brief, the book's commands have been written for files <emphasis>not</emphasis> added to <filename class="directory"> /etc/skel</filename> and instead just sends the results to the user's home directory. If the file is going to be in <filename class="directory"> /etc/skel</filename>, change the book's command(s) to send output there instead and then just copy the file from <filename class="directory"> /etc/skel</filename> to the appropriate directories, like <filename class="directory">/etc</filename>, <filename class="directory">~ </filename> or the home directory of any other user already in the system.
Vous lancerez un jeu de commandes légèrement différent pour les fichiers qui se trouvent dans <filename class="directory">/etc/skel</filename>. Chaque section vous le rappellera. En bref, les commandes du livre ont été écrites pour des fichiers <emphasis>non</emphasis> ajoutés à <filename class="directory">/etc/skel</filename> et elles envoient simplement les résultats dans le répertoire personnel de l'utilisateur. Si le fichier va être dans <filename class="directory">/etc/skel</filename>, modifiez la/les commande(s) du livre pour y envoyer la sortie au lieu de juste copier le fichier de <filename class="directory">/etc/skel</filename> vers les répertoires adéquats, comme <filename class="directory">/etc</filename>, <filename class="directory">~</filename> ou le répertoire home d'un autre utilisateur déjà sur le systéme.
3 months ago
User avatar None

String updated in the repository

Beyond Linux From Scratch / postlfs_config_skel — French

The files from those sections that you might want to place in <filename class="directory">/etc/skel</filename> include <filename>.inputrc</filename>, <filename>.bash_profile</filename>, <filename>.bashrc</filename>, <filename>.bash_logout</filename>, <filename>.dircolors</filename>, and <filename>.vimrc</filename>. If you are unsure which of these should be placed there, just continue to the following sections, read each section and any references provided, and then make your decision.
Les fichiers de ces sections que vous pourriez vouloir mettre dans <filename class="directory">/etc/skel</filename> comprennent <filename>.inputrc</filename>, <filename>.bash_profile</filename>, <filename>.bashrc</filename>, <filename>.bash_logout</filename>, <filename>.dircolors</filename> et <filename>.vimrc</filename>. Si vous n'êtes pas sûr qu'ils devraient être mis là, poursuivez simplement les sections suivantes, lisez chaque section et les références fournies, puis prenez votre décision.
3 months ago
Browse all translation changes