Overview

Project website debian-handbook.info
Instructions for translators

https://debian-handbook.info/contribute/ Mailing list for translators: <debian-handbook-translators@lists.alioth.debian.org
Project maintainers User avatar rhertzog User avatar pere User avatar dleidert
Translation license GNU General Public License v2.0 or later
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 https://salsa.debian.org/hertzog/debian-handbook.git
Repository branch bullseye/main
Last remote commit Fix incorrect syntax in pt-BR translation. 02708025
Petter Reinholdtsen authored 4 months ago
Last commit in Weblate es-ES: Translated using Weblate. 84c9d84e
User avatar gallegonovato authored 23 hours ago
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
File mask */08_basic-configuration.po
Translation file Download fr-FR/08_basic-configuration.po
Last change July 5, 2024, 5:38 p.m.
Last change made by Petter Reinholdtsen
Language French
Language code fr
Text direction Left to right
Number of speakers 295,510,923
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,007 17,838 165,831
Translated 51% 521 63% 11,291 54% 89,676
Needs editing 41% 422 27% 4,825 35% 58,334
Read-only 0% 0 0% 0 0% 0
Failing checks 30% 308 29% 5,180 32% 53,281
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 6% 64 9% 1,722 10% 17,821
Last 12 months Previous

Activity in last 12 months

1 change 0 changes 2 changes 0 changes 4 changes 0 changes 0 changes 0 changes 20 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 17 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

17,838
Hosted words
1,007
Hosted strings
51%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+51%
—
Contributors
—
User avatar pere

Resource updated
Parsing of the “fr-FR/08_basic-configuration.po” file was enforced. 4 months ago
User avatar pere

Resource updated
Parsing of the “fr-FR/08_basic-configuration.po” file was enforced. a year ago
User avatar None

String updated in the repository

<computeroutput>$ </computeroutput><userinput>sudo apt install dahdi-dkms</userinput>
<computeroutput><![CDATA[[...]
Setting up dkms (2.8.4-3) ...
Setting up linux-headers-5.10.0-8-amd64 (5.10.46-4) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-8-amd64:.
Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-7.4) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-7.4 DKMS files...
Building for 5.10.0-8-amd64
Building initial module for 5.10.0-8-amd64
Done.

dahdi_dummy.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

dahdi_dynamic_eth.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

[...]
DKMS: install completed.]]>
$ </computeroutput><userinput>sudo dkms status</userinput>
<computeroutput>dahdi, 2.11.1.0.20170917~dfsg-7.4, 5.10.0-8-amd64, x86_64: installed
$ </computeroutput><userinput>sudo modinfo dahdi_dummy</userinput>
<computeroutput><![CDATA[filename: /lib/modules/5.10.0-8-amd64/updates/dkms/dahdi_dummy.ko
license: GPL v2
author: Robert Pleh <robert.pleh@hermes.si>
description: Timing-Only Driver
depends: dahdi
retpoline: Y
name: dahdi_dummy
vermagic: 5.10.0-8-amd64 SMP mod_unload modversions
parm: debug:int
]]></computeroutput>

<computeroutput>$ </computeroutput><userinput>sudo apt install dahdi-dkms</userinput>
<computeroutput><![CDATA[[...]
Setting up dkms (2.8.4-3) ...
Setting up linux-headers-5.10.0-8-amd64 (5.10.46-4) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 5.10.0-8-amd64:.
Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-7.4) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-7.4 DKMS files...
Building for 5.10.0-8-amd64
Building initial module for 5.10.0-8-amd64
Done.

dahdi_dummy.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

dahdi_dynamic_eth.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.10.0-8-amd64/updates/dkms/

[...]
DKMS: install completed.]]>
$ </computeroutput><userinput>sudo dkms status</userinput>
<computeroutput>dahdi, 2.11.1.0.20170917~dfsg-7.4, 5.10.0-8-amd64, x86_64: installed
$ </computeroutput><userinput>sudo modinfo dahdi_dummy</userinput>
<computeroutput><![CDATA[filename: /lib/modules/5.10.0-8-amd64/updates/dkms/dahdi_dummy.ko
license: GPL v2
author: Robert Pleh <robert.pleh@hermes.si>
description: Timing-Only Driver
depends: dahdi
retpoline: Y
name: dahdi_dummy
vermagic: 5.10.0-8-amd64 SMP mod_unload modversions
parm: debug:int
]]></computeroutput>
a year ago
User avatar None

String updated in the repository
<computeroutput>$ </computeroutput><userinput>make deb-pkg LOCALVERSION=-falcot KDEB_PKGVERSION=$(make kernelversion)-1
</userinput><computeroutput>[...]
$ </computeroutput><userinput>ls ../*.deb
</userinput><computeroutput>../linux-headers-5.10.46-falcot_5.10.46-1_amd64.deb
../linux-image-5.10.46-falcot_5.10.46-1_amd64.deb
../linux-image-5.10.46-falcot-dbg_5.10.46-1_amd64.deb
../linux-libc-dev_5.10.46-1_amd64.deb
</computeroutput>
<computeroutput>$ </computeroutput><userinput>make deb-pkg LOCALVERSION=-falcot KDEB_PKGVERSION=$(make kernelversion)-1
</userinput><computeroutput>[...]
$ </computeroutput><userinput>ls ../*.deb
</userinput><computeroutput>../linux-headers-5.10.46-falcot_5.10.46-1_amd64.deb
../linux-image-5.10.46-falcot_5.10.46-1_amd64.deb
../linux-image-5.10.46-falcot-dbg_5.10.46-1_amd64.deb
../linux-libc-dev_5.10.46-1_amd64.deb
</computeroutput>
a year ago
User avatar None

String updated in the repository
If you have already compiled once in the directory and wish to rebuild everything from scratch (for example, because you substantially changed the kernel configuration), you will have to run <command>make clean</command> to remove the compiled files. <command>make distclean</command> removes even more generated files, including your <filename>.config</filename> file too, so make sure to backup it first.
Si vous avez déjà construit un noyau dans le répertoire et si vous voulez tout reconstruire depuis zéro (par exemple après avoir changé la configuration du noyau de manière substantielle), il faudra lancer <command>make clean</command>, qui supprimera les fichiers compilés. <command>make distclean</command> fait un ménage encore plus poussé et supprime tous les fichiers générés, y compris votre <filename>.config</filename> ; faites-en une sauvegarde au préalable.
a year ago
User avatar None

String updated in the repository

<computeroutput>$ </computeroutput><userinput>mkdir ~/kernel; cd ~/kernel</userinput>
<computeroutput>$ </computeroutput><userinput>tar -xaf /usr/src/linux-source-5.10.tar.xz</userinput>

<computeroutput>$ </computeroutput><userinput>mkdir ~/kernel; cd ~/kernel</userinput>
<computeroutput>$ </computeroutput><userinput>tar -xaf /usr/src/linux-source-5.10.tar.xz</userinput>
a year ago
User avatar None

String updated in the repository
<![CDATA[
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=7a250fb8-c16d-4a4e-9808-ec08ae92b6c6 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=13f367ae-dbaf-40ed-85c0-4072a2ebe426 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy auto rw,user,noauto 0 0
arrakis:/shared /shared nfs defaults 0 0
]]>
<![CDATA[
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=7a250fb8-c16d-4a4e-9808-ec08ae92b6c6 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=13f367ae-dbaf-40ed-85c0-4072a2ebe426 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy auto rw,user,noauto 0 0
arrakis:/shared /shared nfs defaults 0 0
]]>
a year ago
User avatar None

String updated in the repository
A complete list of known filesystems is available in the <citerefentry><refentrytitle>mount</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page. The <literal>swap</literal> special value is for swap partitions; the <literal>auto</literal> special value tells the <command>mount</command> program to automatically detect the filesystem (which is especially useful for disk readers and USB keys, since each one might have a different filesystem);
La liste complète des systèmes de fichiers reconnus est disponible dans la page de manuel <citerefentry><refentrytitle>mount</refentrytitle><manvolnum>8</manvolnum></citerefentry>. La valeur spéciale <literal>swap</literal> sert aux partitions d'échange ; la valeur spéciale <literal>auto</literal> demande au programme <command>mount</command> de détecter automatiquement le système de fichiers (ce qui est surtout utile pour les lecteurs de disques et les clés USB, car chacun peut abriter un système de fichiers différent).
a year ago
User avatar None

String updated in the repository
The <filename>/etc/fstab</filename> file gives a list of all possible mounts that happen either automatically on boot or manually for removable storage devices. Each mount point is described by a line with several space-separated fields:
Le fichier <filename>/etc/fstab</filename> donne la liste de tous les montages possibles (effectués automatiquement au démarrage ou à exécuter manuellement pour les périphériques amovibles). Chaque point de montage y est détaillé sur une ligne par plusieurs champs séparés par des espaces, qui sont :
a year ago
User avatar None

String updated in the repository
<emphasis>GRUB</emphasis> (GRand Unified Bootloader) is more recent. It is not necessary to invoke it after each update of the kernel; <emphasis>GRUB</emphasis> knows how to read the filesystems and find the position of the kernel on the disk by itself. To install it on the MBR of the first disk, simply type <command>grub-install /dev/sda</command>. This will overwrite the MBR, so be careful not to overwrite the wrong location. While it is also possible to install <emphasis>GRUB</emphasis> into a partition boot record, beware that it is usually a mistake and doing <command>grub-install /dev/sda1</command> has not the same meaning as <command>grub-install /dev/sda</command>.
<emphasis>GRUB</emphasis> (<foreignphrase>GRand Unified Bootloader</foreignphrase>) est plus récent. Il n'est pas nécessaire de l'invoquer après chaque mise à jour du noyau. <emphasis>GRUB</emphasis> sait lire les systèmes de fichiers et trouver la position du noyau sur le disque par lui-même. Pour l'installer sur le MBR du premier disque, tapez simplement <command>grub-install /dev/sda</command>. Cette opération écrasera le MBR, il faut donc faire attention à ne pas écraser le mauvais emplacement. Bien qu'il soit également possible d'installer <emphasis>GRUB</emphasis> dans un enregistrement sur la partition d'amorçage, sachez qu'il s'agit généralement d'une erreur et que <command>grub-install /dev/sda1</command> n'a pas la même signification que <command>grub-install /dev/sda</command>.
a year ago
Browse all translation changes