kgess-mirror/debian-handbook
1
0
Fork 0
mirror of https://salsa.debian.org/hertzog/debian-handbook.git synced 2026-01-11 19:56:38 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update POT files

Browse source
This commit is contained in:
Daniel Leidert 2025-08-09 20:03:25 +02:00
parent 7c9498b521
commit 37c4e9d82c
25 changed files with 130 additions and 130 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
pot/00a_preface.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"

6
pot/00b_foreword.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -212,7 +212,7 @@ msgstr ""
msgid "This book would not be what it is without the contributions of several persons who each played an important role during the translation phase and beyond. We would like to thank Marilyne Brun, who helped us to translate the sample chapter and who worked with us to define some common translation rules. She also revised several chapters that were desperately in need of supplementary work. Thank you to Anthony Baldwin (of Baldwin Linguas) who translated several chapters for us."
msgstr ""
msgid "Since Roland and I were too busy to update the book for Debian 11, we used the modest income that we get through donations and sales to hire contributors to do the bulk of the work. Thank you very much to Jorge Maldonado Ventura and Daniel Leidert for the hard work they put into the updates since then."
msgid "Since Roland and I were too busy to update the book for Debian 12, we used the modest income that we get through donations and sales to hire contributors to do the bulk of the work. Thank you very much to Jorge Maldonado Ventura and Daniel Leidert for the hard work they put into the updates since then."
msgstr ""
msgid "We benefited from the generous help of proofreaders: Daniel Phillips, Gerold Rupprecht, Gordon Dey, Jacob Owens, and Tom Syroid. They each reviewed many chapters. Thank you very much!"

6
pot/01_the-debian-project.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -1745,7 +1745,7 @@ msgstr ""
msgid "This Long Term Support (LTS) of Debian releases is a recent initiative: individual contributors and companies joined forces to create the Debian LTS team. Older releases which are no longer supported by the Debian security team fall under the responsibility of this new team."
msgstr ""
msgid "The Debian security team handles security support in the current <emphasis role=\"distribution\">Stable</emphasis> release and also in the <emphasis role=\"distribution\">Oldstable</emphasis> release (but only for as long as is needed to ensure one year of overlap with the current stable release). This amounts roughly to three years of support for each release. The Debian LTS team handles the last (two) years of security support so that each release benefits from at least 5 years of support and so that users can upgrade from version N to N+2, for example, from Debian 9 <emphasis role=\"distribution\">Stretch</emphasis> to Debian 11 <emphasis role=\"distribution\">Bullseye</emphasis>. <ulink type=\"block\" url=\"https://wiki.debian.org/LTS\" />"
msgid "The Debian security team handles security support in the current <emphasis role=\"distribution\">Stable</emphasis> release and also in the <emphasis role=\"distribution\">Oldstable</emphasis> release (but only for as long as is needed to ensure one year of overlap with the current stable release). This amounts roughly to three years of support for each release. The Debian LTS team handles the last (two) years of security support so that each release benefits from at least 5 years of support and so that users can upgrade from version N to N+2, for example, from Debian 10 <emphasis role=\"distribution\">Buster</emphasis> to Debian 12 <emphasis role=\"distribution\">Bookworm</emphasis>. <ulink type=\"block\" url=\"https://wiki.debian.org/LTS\" />"
msgstr ""
msgid "<emphasis>COMMUNITY</emphasis> Companies sponsoring the LTS effort"

4
pot/02_case-study.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"

8
pot/03_existing-setup.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -74,7 +74,7 @@ msgstr ""
msgid "<primary>AppleShare</primary>"
msgstr ""
msgid "In the other direction, the Netatalk daemon can be used to provide file servers to macOS machines on the network. It implements the AFP protocol (Apple Filing Protocol, now AppleShare) as well as the required notifications so that the servers can be automatically discovered by the macOS clients."
msgid "In the other direction, the Netatalk daemon can be used to provide file servers to macOS machines on the network. It implements the AFP protocol (Apple Filing Protocol) as well as the required notifications so that the servers can be automatically discovered by the macOS clients."
msgstr ""
msgid "<primary>AppleTalk</primary>"
@ -320,7 +320,7 @@ msgstr ""
msgid "Be careful to not blindly delete everything that <command>cruft</command> and <command>cruft-ng</command> might list!"
msgstr ""
msgid "The <emphasis role=\"pkg\">debsums</emphasis> package allows to check the MD5 hashsum of each file installed by a package against a reference hashsum and can help to determine, which files might have been altered (see <xref linkend=\"sidebar.debsums\" />). Be aware that created files (files generated by Debian packages, or generated configuration files not managed by <command>dpkg</command>, etc.) are not subject to this check."
msgid "The <emphasis role=\"pkg\">debsums</emphasis> package verifies the MD5 hashsum of each file installed by a package against a reference hashsum, which can help to determine which files might have been altered (see <xref linkend=\"sidebar.debsums\" />). Be aware that created files (files generated by Debian packages, or generated configuration files not managed by <command>dpkg</command>, etc.) are not subject to this check."
msgstr ""
msgid "The <emphasis role=\"pkg\">apt-show-versions</emphasis> package provides a tool to check for installed packages without a package source and can help to determine third party packages (see <xref linkend=\"sect.apt-show-versions\" />)."

18
pot/04_installation.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -56,7 +56,7 @@ msgstr ""
msgid "<emphasis>BEWARE</emphasis> Upgrading from Bullseye"
msgstr ""
msgid "If you already have Debian <emphasis role=\"distribution\">Bookworm</emphasis> installed on your computer, this chapter is not for you! Unlike other distributions, Debian allows updating a system from one version to the next without having to reinstall the system. Reinstalling, in addition to being unnecessary, could even be dangerous, since it could remove already installed programs."
msgid "If you already have Debian <emphasis role=\"distribution\">Bullseye</emphasis> installed on your computer, this chapter is not for you! Unlike other distributions, Debian allows updating a system from one version to the next without having to reinstall the system. Reinstalling, in addition to being unnecessary, could even be dangerous, since it could remove already installed programs."
msgstr ""
msgid "The upgrade process will be described in <xref linkend=\"sect.dist-upgrade\" />."
@ -251,7 +251,7 @@ msgstr ""
msgid "<primary>bootloader</primary>"
msgstr ""
msgid "The bootloader is a low-level program that is responsible for booting the Linux kernel just after the BIOS passes off its control. To handle this task, it must be able to locate the Linux kernel to boot on the disk. On the i386 and amd64 architectures, the two most used programs to perform this task are <acronym>LILO</acronym>, the older of the two, and <acronym>GRUB</acronym>, its modern replacement. Isolinux and Syslinux are alternatives frequently used to boot from removable media."
msgid "The bootloader is a low-level program that is responsible for booting the Linux kernel just after the BIOS passes off its control. To handle this task, it must be able to locate the Linux kernel to boot on the disk. On the i386 and amd64 architectures, the most used program to perform this task is <acronym>GRUB</acronym>. Isolinux and Syslinux are alternatives frequently used to boot from removable media."
msgstr ""
msgid "Each menu entry hides a specific boot command line, which can be configured as needed by pressing the <keycap>TAB</keycap> key before validating the entry and booting. The “Help” menu entry displays the old command line interface, where the <keycap>F1</keycap> to <keycap>F10</keycap> keys display different help screens detailing the various options available at the prompt. You will rarely need to use this option except in very specific cases."
@ -260,13 +260,13 @@ msgstr ""
msgid "The “expert” mode (accessible in the “Advanced options” menu) details all possible options in the process of installation, and allows navigation between the various steps without them happening automatically in sequence. Be careful, this very verbose mode can be confusing due to the multitude of configuration choices that it offers."
msgstr ""
msgid "The \"rescue\" mode, also accessible in the “Advanced options” menu, allows to recover a broken system or fix the bootloader. After presenting the first few screens of the installer, it will allow to enter a shell prompt in the file system you selected to perform any necessary actions, or allow to re-install the bootloader. <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/amd64/ch08s06\" />"
msgid "The “rescue” mode, also accessible in the “Advanced options” menu, allows recovering a broken system or fixing the bootloader. After presenting the first few screens of the installer, it will allow you to enter a shell prompt in the file system you selected to perform any necessary actions, or to re-install the bootloader. <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/amd64/ch08s06\" />"
msgstr ""
msgid "Boot screen"
msgstr ""
msgid "Once booted, the installation program guides you step by step throughout the process. This section presents each of these steps in detail. Here we follow the process of an installation from an amd64 DVD-ROM (more specifically, the version 12.5.0 of the installer for <emphasis role=\"distribution\">Bookworm</emphasis>); <emphasis>netinst</emphasis> installations, as well as the final release of the installer, may look slightly different. We will also address installation in graphical mode, but the only difference from “classic” (text-mode) installation is in the visual appearance."
msgid "Once booted, the installation program guides you step by step throughout the process. This section presents each of these steps in detail. Here we follow the process of an installation from an amd64 DVD-ROM (more specifically, the version 12.5.0 of the installer for <emphasis role=\"distribution\">Bookworm</emphasis>); <emphasis>netinst</emphasis> installations, as well as later releases of the installer, may look slightly different. We will also address installation in graphical mode, but the only difference from “classic” (text-mode) installation is in the visual appearance."
msgstr ""
msgid "Selecting the language"
@ -740,7 +740,7 @@ msgstr ""
msgid "If the installer detects a Debian installation disk in the CD/DVD reader, it is not necessary to configure APT to go looking for packages on the network: APT is automatically configured to read packages from a removable media drive. If the disk is part of a set, the software will offer to “explore” other disks in order to reference all of the packages stored on them."
msgstr ""
msgid "If getting packages from the network is requested, the installer allows to choose a server from which to download these packages, by choosing first a country, then a mirror available in that country. A mirror is a public server hosting copies of all the files of the Debian master archive."
msgid "If getting packages from the network is requested, the installer allows choosing a server from which to download these packages, by choosing first a country, then a mirror available in that country. A mirror is a public server hosting copies of all the files of the Debian master archive."
msgstr ""
msgid "Selecting a Debian mirror"
@ -824,10 +824,10 @@ msgstr ""
msgid "By default, the menu proposed by GRUB contains all the installed Linux kernels, as well as any other operating systems that were detected. This is why you should accept the offer to install it in the Master Boot Record. Since keeping older kernel versions preserves the ability to boot the same system if the most recently installed kernel is defective or poorly adapted to the hardware, it often makes sense to keep a few older kernel versions installed."
msgstr ""
msgid "<primary>LILO</primary>"
msgid "GRUB is the default bootloader installed by Debian thanks to its technical superiority: it works with most filesystems and therefore doesn't require an update after each installation of a new kernel, since it reads its configuration during boot and finds the exact position of the new kernel. Version 1 of GRUB (now known as “Grub Legacy”) couldn't handle all combinations of LVM and software RAID; version 2, installed by default, is more complete. While there may still be situations where it is preferable to install LILO (another bootloader); the Debian installer does no longer support the installation of it and it has also been removed from the Debian archive."
msgstr ""
msgid "GRUB is the default bootloader installed by Debian thanks to its technical superiority: it works with most filesystems and therefore doesn't require an update after each installation of a new kernel, since it reads its configuration during boot and finds the exact position of the new kernel. Version 1 of GRUB (now known as “Grub Legacy”) couldn't handle all combinations of LVM and software RAID; version 2, installed by default, is more complete. While there may still be situations where it is preferable to install LILO (another bootloader); the Debian installer does no longer support the installation of it and it has also been removed from the Debian archive."
msgid "<primary>LILO</primary>"
msgstr ""
msgid "It is worth noting that GRUB is not a single bootloader, it is more like a collection of bootloaders suited for different cases. The numerous binary packages built out of the GRUB source package reflect that: <emphasis role=\"pkg\">grub-efi-amd64</emphasis> is for 64-bit PC booting in UEFI mode, <emphasis role=\"pkg\">grub-efi-ia32</emphasis> is for 32-bit PC booting in UEFI mode, <emphasis role=\"pkg\">grub-pc</emphasis> is for PC booting in BIOS mode, <emphasis>grub-uboot</emphasis> for ARM computers, etc."

26
pot/05_packaging-system.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -291,7 +291,7 @@ msgstr ""
msgid "<primary>Internet Engineering Task Force</primary>"
msgstr ""
msgid "<acronym>RFC</acronym> is the abbreviation of “Request For Comments”. A RFC is generally a technical document that describes what will become an Internet standard. Before becoming standardized and frozen, these standards are submitted for public review (hence their name). The <acronym>IETF</acronym> (Internet Engineering Task Force) decides on the evolution of the status of these documents (proposed standard, draft standard, or standard)."
msgid "<acronym>RFC</acronym> is the abbreviation of “Request For Comments”. An RFC is generally a technical document that describes what will become an Internet standard. Before becoming standardized and frozen, these standards are submitted for public review (hence their name). The <acronym>IETF</acronym> (Internet Engineering Task Force) decides on the evolution of the status of these documents (proposed standard, draft standard, or standard)."
msgstr ""
msgid "RFC 2026 defines the process for standardization of Internet protocols. <ulink type=\"block\" url=\"https://tools.ietf.org/html/rfc2026\" />"
@ -363,7 +363,7 @@ msgstr ""
msgid "<primary>APT</primary><secondary><literal>Aptitude::Recommends-Important</literal></secondary>"
msgstr ""
msgid "You should always install the “recommended” packages, unless you know exactly why you do not need them. This is now also the default for APT unless configured otherwise. Conversely, it is not necessary to install “suggested” packages unless you know why you need them (the package description or its documentation may contain information which extra functionality they will activate). The behavior of <command>apt</command> can be controlled by using the <literal>APT::Install-Recommends</literal> and <literal>APT::Install-Suggests</literal> configuration options or the corresponding command line options <literal>--[no-]install-recommends</literal> and <literal>--[no-]install-suggests</literal>."
msgid "You should always install the “recommended” packages, unless you know exactly why you do not need them. This is now also the default for <acronym>APT</acronym> unless configured otherwise. Conversely, it is not necessary to install “suggested” packages unless you know why you need them (the package description or its documentation may contain information which extra functionality they will activate). The behavior of <command>apt</command> can be controlled by using the <literal>APT::Install-Recommends</literal> and <literal>APT::Install-Suggests</literal> configuration options or the corresponding command line options <literal>--[no-]install-recommends</literal> and <literal>--[no-]install-suggests</literal>."
msgstr ""
msgid "<primary>package</primary><secondary>enhancements</secondary>"
@ -612,7 +612,7 @@ msgstr ""
msgid "During the initial installation and for each upgrade of a package, <command>dpkg</command> calls the so called <emphasis>maintainer scripts</emphasis> such as the <command>prerm</command> or <command>preinst</command> scripts. These scripts can perform additional actions during the different stages of a package's life-cycle. Script names preceded by <literal>new-</literal> are the scripts from the new version of a package being installed or upgraded to. Script names preceded by <literal>old-</literal> are the scripts from the old version of a package that is being upgraded from."
msgstr ""
msgid "During each invocation <command>dpkg</command> will pass certain arguments to each script such as <command>upgrade <replaceable>new-version</replaceable></command>. The invoked script can then either handle the arguments and perform a particular action, or ignore the arguments and return with an exit code of <literal>0</literal>, if nothing needs to be done during that step. In practice many packages will not need to perform an action during every step in the life cycle. Thus a typical configuration script will check for a particular argument and ignore all other ones, implicitly returning with exit code <literal>0</literal>."
msgid "During each invocation <command>dpkg</command> will pass certain arguments to each script such as <command>upgrade <replaceable>new-version</replaceable></command>. The invoked script can then either handle the arguments and perform a particular action, or ignore the arguments and return with an exit code of <literal>0</literal>, if nothing needs to be done during that step. In practice many packages will not need to perform an action during every step in the life cycle. Thus a typical maintainer script will check for a particular argument and ignore all other ones, implicitly returning with exit code <literal>0</literal>."
msgstr ""
msgid "Here is what happens during an installation (or an update). The <replaceable>old-version</replaceable>, <replaceable>new-version</replaceable> and <replaceable>last-version-configured</replaceable> arguments are placeholders for the actual (old and new) version numbers of the package:"
@ -738,7 +738,7 @@ msgstr ""
msgid "The <command>--force-confask</command> option requires <command>dpkg</command> to display the questions about the configuration files, even in cases where they would not normally be necessary. Thus, when reinstalling a package with this option, <command>dpkg</command> will ask the questions again for all of the configuration files modified or deleted by the administrator. This is very convenient, especially for reinstalling the original configuration file if it has been deleted and no other copy is available: a normal re-installation won't work, because <command>dpkg</command> considers removal as a form of legitimate modification, and, thus, doesn't install the desired configuration file."
msgstr ""
msgid "See the sidebar <xref linkend=\"sidebar.questions-conffiles\" /> for how to use these options with <literal>APT</literal>."
msgid "See the sidebar <xref linkend=\"sidebar.questions-conffiles\" /> for how to use these options with <acronym>APT</acronym>."
msgstr ""
msgid "<emphasis>GOING FURTHER</emphasis> Avoiding the configuration file questions"
@ -786,7 +786,7 @@ msgstr ""
msgid "Triggers were introduced to reduce the amount of duplicated events during package installation, such as file registration or catalog/database update tasks. Packages can define their own or activate defined triggers. A more comprehensive documentation can be found in <ulink url=\"https://git.dpkg.org/cgit/dpkg/dpkg.git/tree/doc/spec/triggers.txt\"><filename>/usr/share/doc/dpkg/triggers.txt.gz</filename></ulink>."
msgstr ""
msgid "The <filename>shlibs</filename> system is an older and simpler alternative to the <filename>symbols</filename> system for declaring dependencies for shared libraries. It defines the package name and version in which to find a specific SONAME-version of a shared library. The newer <filename>symbols</filename> system allows to define the dependency by tracking the symbols and when they have been introduced or changed in the library instead."
msgid "The <filename>shlibs</filename> system is an older and simpler alternative to the <filename>symbols</filename> system for declaring dependencies for shared libraries. It defines the package name and version in which to find a specific SONAME-version of a shared library. The newer <filename>symbols</filename> system allows the definition of a dependency by tracking the symbols and their introduction or modification in the library instead."
msgstr ""
msgid "Structure of a Source Package"
@ -1093,7 +1093,7 @@ msgstr ""
msgid "<primary>broken dependency</primary>"
msgstr ""
msgid "If you are not careful, the use of an option <literal>--force-*</literal> can lead to a system where the APT family of commands will refuse to function. In effect, some of these options allow installation of a package when a dependency is not met, or when there is a conflict. The result is an inconsistent system from the point of view of dependencies, and the APT commands will refuse to execute any action except those that will bring the system back to a consistent state (this often consists of installing the missing dependency or removing a problematic package). This often results in a message like this one, obtained after installing a new version of <emphasis role=\"pkg\">rdesktop</emphasis> while ignoring its dependency on a newer version of the <emphasis role=\"pkg\">libc6</emphasis>:"
msgid "If you are not careful, the use of an option <literal>--force-*</literal> can lead to a system where the <acronym>APT</acronym> family of commands will refuse to function. In effect, some of these options allow installation of a package when a dependency is not met, or when there is a conflict. The result is an inconsistent system from the point of view of dependencies, and the <acronym>APT</acronym> commands will refuse to execute any action except those that will bring the system back to a consistent state (this often consists of installing the missing dependency or removing a problematic package). This often results in a message like this one, obtained after installing a new version of <emphasis role=\"pkg\">rdesktop</emphasis> while ignoring its dependency on a newer version of the <emphasis role=\"pkg\">libc6</emphasis>:"
msgstr ""
msgid ""
@ -1172,7 +1172,7 @@ msgstr ""
msgid "Most options are available in a “long” version (one or more relevant words, preceded by a double dash) and a “short” version (a single letter, often the initial of one word from the long version, and preceded by a single dash). This convention is so common that it is a POSIX standard."
msgstr ""
msgid "Before concluding this section, we will study <command>dpkg</command> options that query the internal database in order to obtain information. Giving first the long options and then corresponding short options (that will evidently take the same possible arguments) we cite"
msgid "Before concluding this section, we will study <command>dpkg</command> options that query the internal database in order to obtain information. Giving first the long options and then corresponding short options (that will evidently take the same possible arguments), we cite:"
msgstr ""
msgid "<literal>--listfiles <replaceable>package</replaceable></literal> (or <literal>-L</literal>), which lists the files installed by this package;"
@ -1187,10 +1187,10 @@ msgstr ""
msgid "<literal>--list</literal> (or <literal>-l</literal>), which displays the list of packages known to the system and their installation status;"
msgstr ""
msgid "<literal>--contents <replaceable>file.deb</replaceable></literal> (or <literal>-c</literal>), which lists the files in the Debian package specified;"
msgid "<literal>--contents <replaceable>file.deb</replaceable></literal> (or <literal>-c</literal>), which lists the files in this Debian package package;"
msgstr ""
msgid "<literal>--info<replaceable> file.deb </replaceable></literal> (or <literal>-I</literal>), which displays the headers of this Debian package."
msgid "<literal>--info <replaceable>file.deb</replaceable></literal> (or <literal>-I</literal>), which displays the headers of this Debian package."
msgstr ""
msgid "<emphasis>CAUTION</emphasis> <command>dpkg --search</command> and merged <filename>/usr</filename>"
@ -1495,7 +1495,7 @@ msgstr ""
msgid "<primary>APT</primary><secondary>multi-arch support</secondary>"
msgstr ""
msgid "APT will automatically detect when dpkg has been configured to support foreign architectures and will start downloading the corresponding <filename>Packages</filename> files during its update process."
msgid "<acronym>APT</acronym> will automatically detect when dpkg has been configured to support foreign architectures and will start downloading the corresponding <filename>Packages</filename> files during its update process."
msgstr ""
msgid "Foreign packages can then be installed with <command>apt install <replaceable>package</replaceable>:<replaceable>architecture</replaceable></command>."
@ -1619,6 +1619,6 @@ msgstr ""
msgid "Looking at the man page for the <command>alien</command> command, you will also note that this program handles other packaging formats, especially the one used by the Slackware distribution (it is made of a simple <filename>tar.gz</filename> archive)."
msgstr ""
msgid "The stability of the software deployed using the <command>dpkg</command> tool contributes to Debian's fame. The APT suite of tools, described in the following chapter, preserves this advantage, while relieving the administrator from managing the status of packages, a necessary but difficult task."
msgid "The stability of the software deployed using the <command>dpkg</command> tool contributes to Debian's fame. The <acronym>APT</acronym> suite of tools, described in the following chapter, preserves this advantage, while relieving the administrator from managing the status of packages, a necessary but difficult task."
msgstr ""

24
pot/06_apt.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -35,7 +35,7 @@ msgstr ""
msgid "Maintenance and Updates: The APT Tools"
msgstr ""
msgid "What makes Debian so popular with administrators is how easily software can be installed and how easily the whole system can be updated. This unique advantage is largely due to the <emphasis>APT</emphasis> program, which Falcot Corp administrators studied with enthusiasm."
msgid "What makes Debian so popular with administrators is how easily software can be installed and how easily the whole system can be updated. This unique advantage is largely due to the <acronym>APT</acronym> program, which Falcot Corp administrators studied with enthusiasm."
msgstr ""
msgid "<primary>APT</primary>"
@ -146,10 +146,10 @@ msgstr ""
msgid "The second field gives the base URL of the source. Combined with the filenames listed in the <filename>Packages.xz</filename> files, it must give a full and valid URL. This can consist in a Debian mirror or in any other package archive set up by a third party. The URL can start with <literal>file://</literal> to indicate a local source installed in the system's file hierarchy, with <literal>http://</literal> or <literal>https://</literal> to indicate a source accessible from a web server, or with <literal>ftp://</literal> or <literal>ftps://</literal> for a source available on an FTP server. The URL can also start with <literal>cdrom:</literal> for CD-ROM/DVD/Blu-ray disc based installations, although this is less frequent, since network-based installation methods are eventually more common. More methods like <literal>ssh://</literal> or <literal>tor+http(s)://</literal> are supported and are either described in <citerefentry><refentrytitle>sources.list</refentrytitle><manvolnum>5</manvolnum></citerefentry> or their respective <emphasis role=\"pkg\">apt-transport-<replaceable>method</replaceable></emphasis> package documentation."
msgstr ""
msgid "The syntax of the last field depends on the structure of the repository. In the simplest case, you can simply indicate a subdirectory (with a required trailing slash) of the desired source. This is often a simple “<filename>./</filename>” which refers to the absence of a subdirectory. The packages are then directly at the specified URL. But in most common cases, the repositories will be structured like a Debian mirror, with multiple distributions, each having multiple components. In those cases, name the chosen distribution by its “codename” — see the list in sidebar <xref linkend=\"sidebar.bruce-perens\" /> — or by the corresponding “suite” (<literal>oldoldstable</literal>, <literal>oldstable</literal>, <literal>stable</literal>, <literal>testing</literal>, <literal>unstable</literal>) and then the components to enable. A typical Debian mirror provides the components <literal>main</literal>, <literal>contrib</literal>, and <literal>non-free</literal>."
msgid "The syntax of the last field depends on the structure of the repository. In the simplest case, you can simply indicate a subdirectory (with a required trailing slash) of the desired source. This is often a simple “<filename>./</filename>” which refers to the absence of a subdirectory. The packages are then directly at the specified URL. But in most common cases, the repositories will be structured like a Debian mirror, with multiple distributions, each having multiple components. In those cases, name the chosen distribution by its “codename” — see the list in sidebar <xref linkend=\"sidebar.bruce-perens\" /> — or by the corresponding “suite” (<literal>oldoldstable</literal>, <literal>oldstable</literal>, <literal>stable</literal>, <literal>testing</literal>, <literal>unstable</literal>) and then the components to enable. A typical Debian mirror provides the components <literal>main</literal>, <literal>contrib</literal>, <literal>non-free</literal>, and <literal>non-free-firmware</literal>."
msgstr ""
msgid "<emphasis>VOCABULARY</emphasis> The <literal>main</literal>, <literal>contrib</literal>, <literal>non-free</literal>, and <literal>non-free-firmware</literal> archives"
msgid "<emphasis>VOCABULARY</emphasis> The <literal>main</literal>, <literal>contrib</literal>, <literal>non-free</literal>, and <literal>non-free-firmware</literal> components"
msgstr ""
msgid "<primary>component</primary><secondary><literal>main</literal></secondary>"
@ -182,13 +182,13 @@ msgstr ""
msgid "Debian uses four components to differentiate packages according to the licenses chosen by the authors of each work. <literal>Main</literal> gathers all packages which fully comply with the <link linkend=\"sect.dfsg\">Debian Free Software Guidelines</link>."
msgstr ""
msgid "The <literal>non-free</literal> component is different because it contains software which does not (entirely) conform to these principles but which can, nevertheless, be distributed without restrictions. This archive, which is not officially part of Debian, is a service for users who could need some of those programs. Debian always recommends giving priority to free software. The existence of this component represents a considerable problem for Richard M. Stallman and keeps the Free Software Foundation from recommending Debian to users."
msgid "The <literal>non-free</literal> component is different because it contains software which does not (entirely) conform to these principles but which can, nevertheless, be distributed without restrictions. This component, which is not officially part of Debian, is a service for users who could need some of those programs. Debian always recommends giving priority to free software. The existence of this component represents a considerable problem for Richard M. Stallman and keeps the Free Software Foundation from recommending Debian to users."
msgstr ""
msgid "The <literal>non-free-firmware</literal> component is new in Debian <emphasis role=\"distribution\">Bookworm</emphasis>. Following a General resolution in 2022, a statement was added to the Debian Social Contract that <quote>[..] The Debian official media may include firmware that is otherwise not part of the Debian system to enable use of Debian with hardware that requires such firmware. [..]</quote>. To distinguish these firmware packages from other <literal>non-free</literal> packages, this new component was introduced."
msgstr ""
msgid "<literal>Contrib</literal> (contributions) is a set of open source software which cannot function without some non-free elements — these elements can be software from the <literal>non-free</literal> section, or non-free files such as game ROMs, BIOS of consoles, etc. — or some elements, not available from the Debian <literal>main</literal> archive at all. The <literal>contrib</literal> component also includes free software whose compilation requires proprietary elements. This was initially the case for the OpenOffice.org office suite, which used to require a proprietary Java environment."
msgid "<literal>Contrib</literal> (contributions) is a set of open source software which cannot function without some non-free elements — these elements can be software from the <literal>non-free</literal> component, or non-free files such as game ROMs, BIOS of consoles, etc. — or some elements, not available from the Debian <literal>main</literal> component at all. The <literal>contrib</literal> component also includes free software whose compilation requires proprietary elements. This was initially the case for the OpenOffice.org office suite, which used to require a proprietary Java environment."
msgstr ""
msgid "<emphasis>TIP</emphasis> Files in <filename>/etc/apt/sources.list.d/</filename>"
@ -197,7 +197,7 @@ msgstr ""
msgid "<primary>APT</primary><secondary><filename>/etc/apt/sources.list.d/</filename></secondary>"
msgstr ""
msgid "If many package sources are referenced, it can be useful to split them in multiple files. Each part is then stored in <filename>/etc/apt/sources.list.d/<replaceable>filename</replaceable>.list</filename> (see sidebar <xref linkend=\"sidebar.directory.d\" />). To disable a source, the related file can simply be renamed to e.g. <filename>/etc/apt/sources.list.d/<replaceable>filename</replaceable>.list</filename>.disabled"
msgid "If many package sources are referenced, it can be useful to split them in multiple files. Each part is then stored in <filename>/etc/apt/sources.list.d/<replaceable>filename</replaceable>.list</filename> (see sidebar <xref linkend=\"sidebar.directory.d\" />). To disable a source, the related file can simply be renamed to e.g. <filename>/etc/apt/sources.list.d/<replaceable>filename</replaceable>.list.disabled</filename>."
msgstr ""
msgid "<primary><command>apt-cdrom</command></primary>"
@ -439,7 +439,7 @@ msgstr ""
msgid "Backports from <literal>stable-backports</literal> are only created from packages available in <emphasis role=\"distribution\">Testing</emphasis>. This ensures that all installed backports will be upgradable to the corresponding stable version once the next stable release of Debian is available."
msgstr ""
msgid "Even though this repository provides newer versions of packages, <literal>APT</literal> will not install them unless you give explicit instructions to do so (or unless you have already done so with a former version of the given backport):"
msgid "Even though this repository provides newer versions of packages, <acronym>APT</acronym> will not install them unless you give explicit instructions to do so (or unless you have already done so with a former version of the given backport):"
msgstr ""
msgid ""
@ -1324,7 +1324,7 @@ msgstr ""
msgid "Let's suppose that <emphasis role=\"distribution\">Stable</emphasis> is your reference distribution but that <emphasis role=\"distribution\">Testing</emphasis> and <emphasis role=\"distribution\">Unstable</emphasis> are also listed in your <filename>sources.list</filename> file. In this case, you can use <command>apt install <replaceable>package</replaceable>/testing</command> to install a package from <emphasis role=\"distribution\">Testing</emphasis>. If the installation fails due to some unsatisfiable dependencies, let it solve those dependencies within <emphasis role=\"distribution\">Testing</emphasis> by adding the <literal>-t testing</literal> parameter. The same obviously applies to <emphasis role=\"distribution\">Unstable</emphasis>."
msgstr ""
msgid "In this situation, upgrades (<literal>upgrade</literal> and <literal>full-upgrade</literal>) are done within <emphasis role=\"distribution\">Stable</emphasis> except for packages already upgraded to another distribution: those will follow updates available in the other distributions. We will explain this behavior with the help of the default priorities set by APT below. Do not hesitate to use <command>apt-cache policy</command> (<xref linkend=\"sect.apt-cache-policy\" />) to verify the given priorities."
msgid "In this situation, upgrades (<literal>upgrade</literal> and <literal>full-upgrade</literal>) are done within <emphasis role=\"distribution\">Stable</emphasis> except for packages already upgraded to another distribution: those will follow updates available in the other distributions. We will explain this behavior with the help of the default priorities set by APT below. Do not hesitate to use <command>apt-cache policy</command> (see <xref linkend=\"sect.apt-cache-policy\" />) to verify the given priorities."
msgstr ""
msgid "Everything centers around the fact that APT only considers packages of higher or equal version than the installed one (assuming that <filename>/etc/apt/preferences</filename> has not been used to force priorities higher than 1000 for some packages)."
@ -2024,7 +2024,7 @@ msgstr ""
msgid "<primary>system</primary><secondary><foreignphrase>update</foreignphrase></secondary>"
msgstr ""
msgid "Now for the upgrading itself. First, you need to change the <filename>/etc/apt/sources.list</filename> file to tell APT to get its packages from <emphasis role=\"distribution\">Bookworm</emphasis> instead of <emphasis role=\"distribution\">Bullseye</emphasis>. If the file only contains references to <emphasis role=\"distribution\">Stable</emphasis> rather than explicit codenames, the change isn't even required, since <emphasis role=\"distribution\">Stable</emphasis> always refers to the latest released version of Debian. In both cases, the database of available packages must be refreshed with the <command>apt update</command> command or the refresh button in <command>synaptic</command> (<xref linkend=\"sect.apt-update\" />)."
msgid "Now for the upgrading itself. First, you need to change the <filename>/etc/apt/sources.list</filename> file to tell APT to get its packages from <emphasis role=\"distribution\">Bookworm</emphasis> instead of <emphasis role=\"distribution\">Bullseye</emphasis>. If the file only contains references to <emphasis role=\"distribution\">Stable</emphasis> rather than explicit codenames, the change isn't even required, since <emphasis role=\"distribution\">Stable</emphasis> always refers to the latest released version of Debian. In both cases, the database of available packages must be refreshed with the <command>apt update</command> command or the refresh button in <command>synaptic</command> (see <xref linkend=\"sect.apt-update\" />)."
msgstr ""
msgid "<emphasis>NOTE</emphasis> Repository information changes"
@ -2051,7 +2051,7 @@ msgstr ""
msgid "<primary>system</primary><secondary><foreignphrase>full-upgrade</foreignphrase></secondary>"
msgstr ""
msgid "Once this first upgrade is done, it is time to handle the upgrade itself, either with <command>apt full-upgrade</command>, <command>aptitude</command>, or <command>synaptic</command> (<xref linkend=\"sect.dist-upgrade\" />). You should carefully check the suggested actions before applying them: you might want to add suggested packages or deselect packages which are only recommended and known not to be useful. In any case, the frontend should come up with a scenario ending in a coherent and up-to-date <emphasis role=\"distribution\">Bookworm</emphasis> system. Then, all you need is to do is wait while the required packages are downloaded, answer the debconf questions and possibly those about locally modified configuration files, and sit back while APT does its magic."
msgid "Once this first upgrade is done, it is time to handle the upgrade itself, either with <command>apt full-upgrade</command>, <command>aptitude</command>, or <command>synaptic</command> (see <xref linkend=\"sect.dist-upgrade\" />). You should carefully check the suggested actions before applying them: you might want to add suggested packages or deselect packages which are only recommended and known not to be useful. In any case, the frontend should come up with a scenario ending in a coherent and up-to-date <emphasis role=\"distribution\">Bookworm</emphasis> system. Then, all you need is to do is wait while the required packages are downloaded, answer the debconf questions and possibly those about locally modified configuration files, and sit back while APT does its magic."
msgstr ""
msgid "Handling Problems after an Upgrade"

8
pot/07_solving-problems.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -122,7 +122,7 @@ msgstr ""
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/inputrc</filename></secondary>"
msgstr ""
msgid "Among other things, most shells offer help (type <command>help</command>) and assistance during input at the prompt, such as the completion of command or file names (which you can generally activate by pressing the <keycap>tab</keycap> key), or recalling previous commands (history management; i.e. check out the mappings for \"page up\" and \"page down\" in <filename>/etc/inputrc</filename>)."
msgid "Among other things, most shells offer help (type <command>help</command>) and assistance during input at the prompt, such as the completion of command or file names (which you can generally activate by pressing the <keycap>tab</keycap> key), or recalling previous commands (history management; i.e. check out the mappings for <keycap>page up</keycap> and <keycap>page down</keycap> in <filename>/etc/inputrc</filename>)."
msgstr ""
msgid "Man pages not only document commands and programs accessible from the command line, but also configuration files, system calls, library functions, and so forth. Sometimes names can collide. For example, the shell's <command>read</command> command has the same name as the <function>read</function> system call. This is why manual pages are organized in numbered sections:"
@ -640,7 +640,7 @@ msgstr ""
msgid "<primary><literal>bugs.debian.org</literal></primary>"
msgstr ""
msgid "Once those two conditions are met, you can think of describing your problem to the mailing list. Include as much relevant information as possible: various tests conducted, documentation consulted, how you attempted to diagnose the problem, the packages concerned or those that may be involved, etc. Check the Debian Bug Tracking System (BTS, described in sidebar <xref linkend=\"sect.bts\" />) for similar problems, and mention the results of that search, providing links to bugs found. BTS starts on: <ulink type=\"block\" url=\"https://bugs.debian.org/\" />"
msgid "Once those two conditions are met, you can think of describing your problem to the mailing list. Include as much relevant information as possible: various tests conducted, documentation consulted, how you attempted to diagnose the problem, the packages concerned or those that may be involved, etc. Check the Debian Bug Tracking System (BTS, described in <xref linkend=\"sect.bts\" />) for similar problems, and mention the results of that search, providing links to bugs found. BTS starts on: <ulink type=\"block\" url=\"https://bugs.debian.org/\" />"
msgstr ""
msgid "The more courteous and precise you have been, the greater your chances are of getting an answer, or, at least, some elements of response. If you receive relevant information by private e-mail, think of summarizing this information publicly so that others can benefit. This also allows the list's archives, searched through various search engines, to show the resolution for others who may have the same question."

21
pot/08_basic-configuration.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -662,7 +662,7 @@ msgstr ""
msgid "<primary><command>isenkram-autoinstall-firmware</command></primary>"
msgstr ""
msgid "First you have to enable the non-free-firmware repository in APT's sources.list file: see <xref linkend=\"sect.apt-sources.list\" /> for details about this file. Many firmware are proprietary and are thus located in this repository. You can try to skip this step if you want, but if the next step doesn't find the required firmware, retry after having enabled the non-free section."
msgid "First you have to enable the non-free-firmware repository in your sources.list file (see <xref linkend=\"sect.apt-sources.list\" />). Many firmware are proprietary and are thus located in this repository. You can try to skip this step if you want, but if the next step doesn't find the required firmware, retry after having enabled the non-free-firmware section."
msgstr ""
msgid "Then you have to install the appropriate <literal>firmware-*</literal> packages. If you don't know which package you need, you can install the <emphasis role=\"pkg\">isenkram</emphasis> package and run its <command>isenkram-autoinstall-firmware</command> command. The packages are often named after the hardware manufacturer or the corresponding kernel module: <emphasis role=\"pkg\">firmware-iwlwifi</emphasis> for Intel wireless cards, <emphasis role=\"pkg\">firmware-atheros</emphasis> for Qualcomm Atheros, <emphasis role=\"pkg\">firmware-realtek</emphasis> for Realtek, etc. A reboot is then recommended because the kernel driver usually looks for the firmware files when it is first loaded and no longer afterwards."
@ -1766,7 +1766,7 @@ msgstr ""
msgid "<primary>CUPS</primary><secondary>filters</secondary>"
msgstr ""
msgid "Modern printers manufactured and sold within the last ten years are nearly always AirPrint-capable, and CUPS and cups-filters on Debian <emphasis role=\"distribution\">Bookworm</emphasis> have everything which is needed to take advantage of this facility on the network. In essence, these printers are IPP printers and an excellent fit for a driverless printing system, reducing the system to CUPS plus <emphasis role=\"pkg\">cups-filters</emphasis>. A printer-driver package can be dispensed with, and non-free printing software from vendors like Canon and Brother is no longer required. A USB-connected printer can take advantage of a modern printer with the <emphasis role=\"pkg\">ipp-usb</emphasis> package."
msgid "Modern printers manufactured and sold within the last ten years are nearly always AirPrint-capable, and CUPS and cups-filters on Debian <emphasis role=\"distribution\">Bookworm</emphasis> have everything which is needed to take advantage of this facility on the network. In essence, these printers are IPP printers and an excellent fit for a driverless printing system, reducing the system to CUPS plus <emphasis role=\"pkg\">cups-filters</emphasis>. A printer-driver package can be dispensed with, and non-free printing software from vendors like Canon and Brother is no longer required. A modern USB-connected printer can take advantage of the <emphasis role=\"pkg\">ipp-usb</emphasis> package."
msgstr ""
msgid "<primary><emphasis role=\"pkg\">ipp-usb</emphasis></primary>"
@ -1996,7 +1996,7 @@ msgstr ""
msgid "The example configuration files given in the following sections are based on the same setup: a single SATA disk, where the first partition is an old Windows installation and the second contains Debian GNU/Linux."
msgstr ""
msgid "<emphasis>ALTERNATIVE</emphasis> The LILO bootloader"
msgid "<emphasis>HISTORY</emphasis> The LILO bootloader"
msgstr ""
msgid "<primary>LILO</primary><seealso><command>lilo</command></seealso>"
@ -2097,9 +2097,6 @@ msgstr ""
msgid "<primary>GRUB</primary><secondary><filename>/boot/grub/grub.cfg</filename></secondary>"
msgstr ""
msgid "<primary>GRUB</primary><secondary></secondary>"
msgstr ""
msgid "Partitions also have a specific name in GRUB. When you use “classical” partitions in MS-DOS format, the first partition on the first disk is labeled, <literal>(hd0,msdos1)</literal>, the second <literal>(hd0,msdos2)</literal>, etc."
msgstr ""
@ -2142,7 +2139,7 @@ msgstr ""
msgid "<primary>GRUB</primary><secondary><errortext>symbol not found</errortext></secondary>"
msgstr ""
msgid "One of the most often reported issues when using <emphasis>GRUB</emphasis> is that users get an error like <errortext>error symbol `grub_calloc' not found</errortext> and they are unable to boot the system anymore. Most of the time this error is caused by installing an updated version of GRUB that causes new modules in <filename>/boot/grub</filename> to be incompatible with old core images in the boot sector that your firmware jumps to when booting your machine. This happens on systems that are configured to run <command>grub-install</command> to a target device that is not actually the one that the firmware uses to boot your system (e.g. after replacing disks or moving them around - one can see the issue when running <command>dpkg-reconfigure grub-pc</command> showing the wrong target device). With the release of Debian 11 <emphasis>Bullseye</emphasis> (the change was also populated to <emphasis>Buster</emphasis>) the update process now checks for this issue and exits with an error in case it finds such a constellation. <ulink type=\"block\" url=\"https://bugs.debian.org/bug=966575#95\" />"
msgid "One of the most often reported issues when using <emphasis>GRUB</emphasis> is that users get an error like <errortext>error symbol `grub_calloc' not found</errortext> and they are unable to boot the system anymore. Most of the time this error is caused by installing an updated version of GRUB that causes new modules in <filename>/boot/grub</filename> to be incompatible with old core images in the boot sector that your firmware jumps to when booting your machine. This happens on systems that are configured to run <command>grub-install</command> to a target device that is not actually the one that the firmware uses to boot your system (e.g. after replacing disks or moving them around - one can see the issue when running <command>dpkg-reconfigure grub-pc</command> showing the wrong target device). With the release of Debian 11 <emphasis>Bullseye</emphasis> (the change was also populated to <emphasis>Buster</emphasis>) the update process now checks for this issue and exits with an error in case it finds such a constellation. <ulink type=\"block\" url=\"https://bugs.debian.org/966575#95\" />"
msgstr ""
msgid ""
@ -2181,13 +2178,13 @@ msgstr ""
msgid "<primary><emphasis role=\"pkg\">grub-efi-<replaceable>arch</replaceable>-signed</emphasis></primary>"
msgstr ""
msgid "Using <emphasis>GRUB</emphasis> to boot either a traditional BIOS system (legacy or UEFI-CSM) or a UEFI system is quite different. Fortunately the user doesn't need to know the differences because Debian provides different packages for each purpose and the installer automatically cares about which one(s) to choose. The <emphasis role=\"pkg\">grub-pc</emphasis> package is chosen for legacy systems, where <emphasis>GRUB</emphasis> is installed into the MBR, while UEFI systems require <emphasis role=\"pkg\">grub-efi-<replaceable>arch</replaceable></emphasis>, where <emphasis>GRUB</emphasis> is installed into the EFI System Partition (ESP). The latter requires a GTP partition table as well as an EFI partition. <ulink type=\"block\" url=\"https://wiki.debian.org/Grub2#UEFI_vs_BIOS_boot\" />"
msgid "Using <emphasis>GRUB</emphasis> to boot either a traditional BIOS system (legacy or UEFI-CSM) or a UEFI system is quite different. Fortunately the user doesn't need to know the differences because Debian provides different packages for each purpose and the installer automatically cares about which one(s) to choose. The <emphasis role=\"pkg\">grub-pc</emphasis> package is chosen for legacy systems, where <emphasis>GRUB</emphasis> is installed into the MBR, while UEFI systems require <emphasis role=\"pkg\">grub-efi-<replaceable>arch</replaceable></emphasis>, where <emphasis>GRUB</emphasis> is installed into the EFI System Partition (ESP). The latter requires a GUID Partition Table (<acronym>GPT</acronym>) as well as an EFI partition. <ulink type=\"block\" url=\"https://wiki.debian.org/Grub2#UEFI_vs_BIOS_boot\" />"
msgstr ""
msgid "To switch an existing system (supporting UEFI) from legacy to UEFI boot mode not only requires to switch the <emphasis>GRUB</emphasis> packages on the system, but also to adjust the partition table and the to create an EFI partition (probably including resizing existing partitions to create the necessary free space). It is therefore quite an elaborate process and we cannot cover it here. Fortunately, there are some manuals by bloggers describing the necessary procedures."
msgstr ""
msgid "If you are using a system with “Secure Boot“ enabled and have installed <emphasis role=\"pkg\">shim-signed</emphasis> (see sidebar <xref linkend=\"sidebar.secure-boot\" />), you must also install <emphasis role=\"pkg\">grub-efi-<replaceable>arch</replaceable>-signed</emphasis>. This package is not pulled in automatically, only if the installation of recommended package has been enabled."
msgid "If you are using a system with “Secure Boot“ enabled and have installed <emphasis role=\"pkg\">shim-signed</emphasis> (see sidebar <xref linkend=\"sidebar.secure-boot\" />), you must also install <emphasis role=\"pkg\">grub-efi-<replaceable>arch</replaceable>-signed</emphasis>. This package is not pulled in automatically, unless the installation of recommended packages has been enabled."
msgstr ""
msgid "Other Configurations: Time Synchronization, Logs, Sharing Access…"
@ -2802,7 +2799,7 @@ msgstr ""
msgid "<primary><filename>/usr</filename></primary><secondary><filename>/usr/src/linux-source-<replaceable>version</replaceable>.tar.xz</filename></secondary>"
msgstr ""
msgid "We assume the <emphasis role=\"pkg\">linux-source-5.10</emphasis> package has been installed. It contains <filename>/usr/src/linux-source-6.1.tar.xz</filename>, a compressed archive of the kernel sources. You must extract these files in a new directory (not directly under <filename>/usr/src/</filename>, since there is no need for special permissions to compile a Linux kernel): <filename>~/kernel/</filename> is appropriate."
msgid "We assume the <emphasis role=\"pkg\">linux-source-6.1</emphasis> package has been installed. It contains <filename>/usr/src/linux-source-6.1.tar.xz</filename>, a compressed archive of the kernel sources. You must extract these files in a new directory (not directly under <filename>/usr/src/</filename>, since there is no need for special permissions to compile a Linux kernel): <filename>~/kernel/</filename> is appropriate."
msgstr ""
msgid ""

6
pot/09_unix-services.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -1219,7 +1219,7 @@ msgstr ""
msgid "To represent special rights, you can prefix a fourth digit to this number according to the same principle, where the <literal>setuid</literal>, <literal>setgid</literal> and <literal>sticky</literal> bits are 4, 2 and 1, respectively. <command>chmod 4754</command> will associate the <literal>setuid</literal> bit with the previously described rights."
msgstr ""
msgid "Note that the use of octal notation only allows to set all the rights at once on a file; you cannot use it to simply add a new right, such as read access for the group owner, since you must take into account the existing rights and compute the new corresponding numerical value."
msgid "Note that the use of octal notation only permits setting all file permissions at once; it does not allow you to change a single permission in a simple way, such as adding read access for the group owner, since you must take into account the existing permissions and compute the new corresponding numerical value."
msgstr ""
msgid "<emphasis>TIP</emphasis> Recursive operation"

12
pot/10_network-infrastructure.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -554,7 +554,7 @@ msgstr ""
msgid "<primary><filename>dh.pem</filename></primary>"
msgstr ""
msgid "The certificate can now be created, as well as the Diffie-Hellman parameters required for the server side of an SSL/TLS connection. They want to use it for a VPN server (see section <xref linkend=\"sect.virtual-private-network\" />) that is identified by the DNS name <literal>vpn.falcot.com</literal>; this name is re-used for the generated key files (<filename>keys/vpn.falcot.com.crt</filename> for the public certificate, <filename>keys/vpn.falcot.com.key</filename> for the private key):"
msgid "The certificate can now be created, as well as the Diffie-Hellman parameters required for the server side of an SSL/TLS connection. They want to use it for a VPN server (see <xref linkend=\"sect.virtual-private-network\" />) that is identified by the DNS name <literal>vpn.falcot.com</literal>; this name is re-used for the generated key files (<filename>keys/vpn.falcot.com.crt</filename> for the public certificate, <filename>keys/vpn.falcot.com.key</filename> for the private key):"
msgstr ""
msgid ""
@ -785,7 +785,7 @@ msgstr ""
msgid "Both methods for creating a virtual private network over SSH are quite straightforward. However, the VPN they provide is not the most efficient available; in particular, it does not handle high levels of traffic very well."
msgstr ""
msgid "The explanation is that when a TCP/IP stack is encapsulated within a TCP/IP connection (for SSH), the TCP protocol is used twice, once for the SSH connection and once within the tunnel. This leads to problems, especially due to the way TCP adapts to network conditions by altering timeout delays. The following site describes the problem in more detail: <ulink type=\"block\" url=\"http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" />"
msgid "The explanation is that when a TCP/IP stack is encapsulated within a TCP/IP connection (for SSH), the TCP protocol is used twice, once for the SSH connection and once within the tunnel. This leads to problems, especially due to the way TCP adapts to network conditions by altering timeout delays. The following site describes the problem in more detail: <ulink type=\"block\" url=\"https://web.archive.org/web/20220321144426/http://sites.inka.de/sites/bigred/devel/tcp-tcp.html\" />"
msgstr ""
msgid "VPNs over SSH should therefore be restricted to one-off tunnels with no performance constraints."
@ -1180,7 +1180,7 @@ msgstr ""
msgid "<primary><command>tc</command></primary>"
msgstr ""
msgid "QoS parameters are set through the <command>tc</command> command (provided by the<emphasis role=\"pkg\">iproute</emphasis> or the <emphasis role=\"pkg\">iproute2</emphasis> package). Since its interface is quite complex, using higher-level tools is recommended."
msgid "QoS parameters are set through the <command>tc</command> command (provided by the <emphasis role=\"pkg\">iproute</emphasis> or the <emphasis role=\"pkg\">iproute2</emphasis> package). Since its interface is quite complex, using higher-level tools is recommended."
msgstr ""
msgid "Reducing Latencies: <command>wondershaper</command>"
@ -1320,7 +1320,7 @@ msgstr ""
msgid "Daemons are enabled by creating the <filename>/etc/frr/<replaceable>daemon</replaceable>.conf</filename> config file, <replaceable>daemon</replaceable> being the name of the daemon to use, and editing the <filename>/etc/frr/daemons</filename> configuration file. The daemon config file must belong to the <literal>frr</literal> user and group with permissions of <literal>0640</literal> in order for the <filename>/etc/init.d/frr</filename> script or the <filename>frr.service</filename> systemd service file to invoke the daemon. The package <emphasis role=\"pkg\">frr</emphasis> provides configuration examples under <filename>/usr/share/doc/frr/examples/</filename>."
msgstr ""
msgid "The configuration of each of these daemons requires knowledge of the routing protocol in question. These protocols cannot be described in detail here, but <emphasis role=\"pkg\">frr-doc</emphasis> provides ample explanation in the form of both <command>info</command> and HTML files. The same contents may be more browsed on the project's website: <ulink type=\"block\" url=\"http://docs.frrouting.org/en/latest/\" />"
msgid "The configuration of each of these daemons requires knowledge of the routing protocol in question. These protocols cannot be described in detail here, but <emphasis role=\"pkg\">frr-doc</emphasis> provides ample explanation in the form of both <command>info</command> and HTML files. The same contents may also be browsed on the project's website: <ulink type=\"block\" url=\"http://docs.frrouting.org/en/latest/\" />"
msgstr ""
msgid "In addition, the syntax is very close to a standard router's configuration interface, and network administrators will adapt quickly to <command>frr</command>."

16
pot/11_network-services.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -1410,7 +1410,7 @@ msgid ""
"[...]"
msgstr ""
msgid "It is usually a good idea to not send passwords over an unencrypted connection. <emphasis>Postfix</emphasis> allows to use different configurations for each port (service) it runs on. All these can be configured with different rules and directives in the <filename>/etc/postfix/master.cf</filename> file. To turn off authentication at all for port 25 (<literal>smtpd</literal> service) add the following directive:"
msgid "It is usually a good idea to not send passwords over an unencrypted connection. <emphasis>Postfix</emphasis> allows using different configurations for each port (service) it runs on. All these can be configured with different rules and directives in the <filename>/etc/postfix/master.cf</filename> file. To turn off authentication at all for port 25 (<literal>smtpd</literal> service) add the following directive:"
msgstr ""
msgid "<primary>Postfix</primary><secondary><filename>/etc/postfix/master.cf</filename></secondary>"
@ -1579,7 +1579,7 @@ msgstr ""
msgid "<primary>Apache</primary><secondary><literal>mod_info</literal>, module</secondary>"
msgstr ""
msgid "The <literal>mod_info</literal> module (<command>a2enmod info</command>) allows to access the comprehensive Apache server configuration and information via browser visiting <literal>http://localhost/server-info</literal>. Because it might contain sensitive information, access is only allowed from the local host by default. <ulink type=\"block\" url=\"https://httpd.apache.org/docs/2.4/mod/mod_info.html\" />"
msgid "The <literal>mod_info</literal> module (<command>a2enmod info</command>) provides access to the comprehensive Apache server configuration and information via a browser at <literal>http://localhost/server-info</literal>. Since it might contain sensitive information, access is only allowed from local host by default. <ulink type=\"block\" url=\"https://httpd.apache.org/docs/2.4/mod/mod_info.html\" />"
msgstr ""
msgid "With its default configuration, the web server listens on port 80 (as configured in <filename>/etc/apache2/ports.conf</filename>), and serves pages from the <filename>/var/www/html/</filename> directory (as configured in <filename>/etc/apache2/sites-enabled/000-default.conf</filename>)."
@ -1609,7 +1609,7 @@ msgstr ""
msgid "Apache 2.4 includes the SSL module (<literal>mod_ssl</literal>) required for secure HTTP (HTTPS) out of the box. It just needs to be enabled with <command>a2enmod ssl</command>, then the required directives have to be added to the configuration files. A configuration example is provided in <filename>/etc/apache2/sites-available/default-ssl.conf</filename>. <ulink type=\"block\" url=\"https://httpd.apache.org/docs/2.4/mod/mod_ssl.html\" />"
msgstr ""
msgid "If you want to generate trusted certificates, you can follow section <xref linkend=\"sect.trusted-certs\" /> and then adjust the following variables:"
msgid "If you want to generate trusted certificates, you can follow <xref linkend=\"sect.trusted-certs\" /> and then adjust the following variables:"
msgstr ""
msgid "<primary>Apache</primary><secondary><literal>SSLCertificateFile</literal>, directive</secondary>"
@ -1638,7 +1638,7 @@ msgstr ""
msgid "<primary><emphasis>Perfect Forward Secrecy</emphasis></primary>"
msgstr ""
msgid "As an alternative to the standard SSL module, there is an extension module called <literal>mod_gnutls</literal>, which is shipped with the <emphasis role=\"pkg\">libapache2-mod-gnutls</emphasis> package and enabled with the <command>a2enmod gnutls</command> command. Unfortunately the version packaged for Debian had serious issues and even security implications and is therefor not part of Debian Stable since the Bullseye release. <ulink type=\"block\" url=\"https://mod.gnutls.org/\" />"
msgid "As an alternative to the standard SSL module, there is an extension module called <literal>mod_gnutls</literal>, which is shipped with the <emphasis role=\"pkg\">libapache2-mod-gnutls</emphasis> package and enabled with the <command>a2enmod gnutls</command> command. Unfortunately the version packaged for Debian had serious issues and even security implications and is therefor not part of Debian Stable since the release of <emphasis role=\"distribution\">Bullseye</emphasis>. <ulink type=\"block\" url=\"https://mod.gnutls.org/\" />"
msgstr ""
msgid "<primary>Apache</primary><secondary><literal>mod_gnutls</literal>, module</secondary>"
@ -2043,7 +2043,7 @@ msgstr ""
msgid "<emphasis>SECURITY</emphasis> Access to statistics"
msgstr ""
msgid "AWStats makes its statistics available on the website with no restrictions by default, but restrictions can be set up so that only a few (probably internal) IP addresses can access them; the list of allowed IP addresses needs to be defined in the <varname>AllowAccessFromWebToFollowingIPAddresses</varname> parameter"
msgid "AWStats makes its statistics available on the website with no restrictions by default, but restrictions can be set up so that only a few (probably internal) IP addresses can access them; the list of allowed IP addresses needs to be defined in the <varname>AllowAccessFromWebToFollowingIPAddresses</varname> parameter."
msgstr ""
msgid "AWStats will also be enabled for other virtual hosts; each virtual host needs its own configuration file, such as <filename>/etc/awstats/awstats.www.falcot.org.conf</filename>."
@ -2796,7 +2796,7 @@ msgstr ""
msgid "<primary>service</primary><secondary><filename>squid.service</filename></secondary>"
msgstr ""
msgid "The working database must be regenerated with <command>update-squidguard</command> after each change of the <command>squidGuard</command> configuration file (or one of the lists of domains or URLs it mentions). The configuration file syntax is documented on the following website: <ulink type=\"block\" url=\"http://www.squidguard.org/Doc/configure.html\" />"
msgid "The working database must be regenerated with <command>update-squidguard</command> after each change of the <command>squidGuard</command> configuration file (or one of the lists of domains or URLs it mentions). The configuration file syntax is documented on the following website: <ulink type=\"block\" url=\"https://web.archive.org/web/20220813010658/http://www.squidguard.org/Doc/configure.html\" />"
msgstr ""
msgid "<primary><command>update-squidguard</command></primary>"

10
pot/12_advanced-administration.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -592,7 +592,7 @@ msgstr ""
msgid "Backing up the Configuration"
msgstr ""
msgid "Most of the meta-data concerning RAID volumes are saved directly on the disks that make up these arrays, so that the kernel can detect the arrays and their components and assemble them automatically when the system starts up. However, backing up this configuration is encouraged, because this detection isn't fail-proof, and it is only expected that it will fail precisely in sensitive circumstances. In our example, if the <filename>sde</filename> disk failure had been real (instead of simulated) and the system had been restarted without removing this <filename>sde</filename> disk, this disk could start working again due to having been probed during the reboot. The kernel would then have three physical elements, each claiming to contain half of the same RAID volume. In reality this leads to the RAID starting from the individual disks alternately - distributing the data also alternately, depending on which disk started the RAID in degraded mode Another source of confusion can come when RAID volumes from two servers are consolidated onto one server only. If these arrays were running normally before the disks were moved, the kernel would be able to detect and reassemble the pairs properly; but if the moved disks had been aggregated into an <filename>md1</filename> on the old server, and the new server already has an <filename>md1</filename>, one of the mirrors would be renamed."
msgid "Most of the meta-data concerning RAID volumes are saved directly on the disks that make up these arrays, so that the kernel can detect the arrays and their components and assemble them automatically when the system starts up. However, backing up this configuration is encouraged, because this detection isn't fail-proof, and it is only expected that it will fail precisely in sensitive circumstances. In our example, if the <filename>sde</filename> disk failure had been real (instead of simulated) and the system had been restarted without removing this <filename>sde</filename> disk, this disk could start working again due to having been probed during the reboot. The kernel would then have three physical elements, each claiming to contain half of the same RAID volume. In reality this leads to the RAID starting from the individual disks alternately - distributing the data also alternately, depending on which disk started the RAID in degraded mode. Another source of confusion can come when RAID volumes from two servers are consolidated onto one server only. If these arrays were running normally before the disks were moved, the kernel would be able to detect and reassemble the pairs properly; but if the moved disks had been aggregated into an <filename>md1</filename> on the old server, and the new server already has an <filename>md1</filename>, one of the mirrors would be renamed."
msgstr ""
msgid "Backing up the configuration is therefore important, if only for reference. The standard way to do it is by editing the <filename>/etc/mdadm/mdadm.conf</filename> file, an example of which is listed here:"
@ -1214,7 +1214,7 @@ msgstr ""
msgid "<emphasis>HARDWARE</emphasis> Virtualization support"
msgstr ""
msgid "Some computers might not have hardware virtualization support; when they do, it should be enabled in the BIOS."
msgid "Some computers might not have hardware virtualization support; when they do, it should be enabled in the UEFI (or BIOS)."
msgstr ""
msgid "To know if you have virtualization support enabled, you can check if the relevant flag is enabled with <command>grep</command>. If the following command for your processor returns some text, you already have virtualization support enabled:"
@ -2223,7 +2223,7 @@ msgstr ""
msgid "<primary><emphasis role=\"pkg\">debconf-doc</emphasis></primary>"
msgstr ""
msgid "Preseeding allows to provide a set of answers to Debconf questions at installation time, but these answers are static and do not evolve as time passes. Since already-installed machines may need upgrading, and new answers may become required, the <filename>/etc/debconf.conf</filename> configuration file can be set up so that Debconf uses external data sources (such as an LDAP directory server, or a remote file accessed via NFS or Samba). Several external data sources can be defined at the same time, and they complement one another. The local database is still used (for read-write access), but the remote databases are usually restricted to reading. The <citerefentry><refentrytitle>debconf.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page describes all the possibilities in detail (you need the <emphasis role=\"pkg\">debconf-doc</emphasis> package)."
msgid "Preseeding allows you to provide a set of answers to Debconf questions at installation time, but these answers are static and do not evolve as time passes. Since already-installed machines may need upgrading, and new answers may become required, the <filename>/etc/debconf.conf</filename> configuration file can be set up so that Debconf uses external data sources (such as an LDAP directory server, or a remote file accessed via NFS or Samba). Several external data sources can be defined at the same time, and they complement one another. The local database is still used (for read-write access), but the remote databases are usually restricted to reading. The <citerefentry><refentrytitle>debconf.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> manual page describes all the possibilities in detail (you need the <emphasis role=\"pkg\">debconf-doc</emphasis> package)."
msgstr ""
msgid "<primary><command>debconf</command></primary>"

21
pot/13_workstation.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -125,10 +125,13 @@ msgstr ""
msgid "Some video card makers (most notably NVIDIA) refuse to publish the hardware specifications that would be required to implement good free drivers. They do, however, provide proprietary drivers that allow using their hardware. This policy is nefarious, because even when the provided driver exists, it is usually not as polished as it should be; more importantly, it does not necessarily follow the X.org updates, which may prevent the latest available driver from loading correctly (or at all). We cannot condone this behavior, and we recommend you avoid these makers and favor more cooperative manufacturers."
msgstr ""
msgid "If you still end up with such a card, you will find the required packages in the <emphasis>non-free</emphasis> section: <emphasis role=\"pkg\">nvidia-driver</emphasis> for NVIDIA cards. It requires a matching kernel module. Building the module can be automated by installing the package <emphasis role=\"pkg\">nvidia-kernel-dkms</emphasis> (for NVIDIA)."
msgid "If you still end up with such a card, you will find the required packages in the <emphasis>non-free</emphasis> section: <emphasis role=\"pkg\">nvidia-driver</emphasis> for NVIDIA cards. It requires a matching kernel module. Building this module can be automated by installing the package <emphasis role=\"pkg\">nvidia-kernel-dkms</emphasis>."
msgstr ""
msgid "The <literal>nouveau</literal> project aims to develop a free software driver for NVIDIA cards and is the default driver that you get for those cards in Debian. In general, its feature set and performance do not match the proprietary driver. In the developers' defense, we should mention that the required information can only be gathered by reverse engineering, which makes things difficult. The free drivers for ATI video cards, called <literal>radeon</literal> and <literal>amdgpu</literal>, are much better in that regard although it often requires non-free firmware from the <emphasis role=\"pkg\">firmware-amd-graphics</emphasis> package."
msgid "The <literal>nouveau</literal> project aims to develop a free software driver for NVIDIA cards and is the default driver that you get for those cards in Debian. In general, its feature set and performance do not match the proprietary driver. In the developers' defense, we should mention that the required information can only be gathered by reverse engineering, which makes things difficult. The free drivers for AMD/ATI video cards, called <literal>radeon</literal> and <literal>amdgpu</literal>, are much better in that regard although it often requires non-free firmware from the <emphasis role=\"pkg\">firmware-amd-graphics</emphasis> package."
msgstr ""
msgid "<primary>AMD</primary>"
msgstr ""
msgid "<primary>ATI</primary>"
@ -185,7 +188,7 @@ msgstr ""
msgid "<primary>x-display-manager</primary>"
msgstr ""
msgid "The graphical interface only provides display space. Running the X server by itself only leads to an empty screen, which is why most installations use a <emphasis>display manager</emphasis> to display a user authentication screen and start the graphical desktop once the user has authenticated. The three most popular display managers in current use are <emphasis role=\"pkg\">gdm3</emphasis> (<foreignphrase>GNOME Display Manager</foreignphrase>), <emphasis role=\"pkg\">sddm</emphasis> (suggested for KDE Plasma) and <emphasis role=\"pkg\">lightdm</emphasis> (<foreignphrase>Light Display Manager</foreignphrase>). More alternatives exist and can be found by searching for the <emphasis role=\"pkg\">x-display-manager</emphasis> virtual package."
msgid "The graphical interface only provides display space. Running the X server by itself only leads to an empty screen, which is why most installations use a <emphasis>display manager</emphasis> to display a user authentication screen and start the graphical desktop once the user has authenticated. The three most popular display managers in current use are <emphasis role=\"pkg\">gdm3</emphasis> (<foreignphrase>GNOME Display Manager</foreignphrase>), <emphasis role=\"pkg\">sddm</emphasis> ( <foreignphrase>Simple Desktop Display Manager</foreignphrase>, suggested for KDE Plasma) and <emphasis role=\"pkg\">lightdm</emphasis> (<foreignphrase>Light Display Manager</foreignphrase>). More alternatives exist and can be found by searching for the <emphasis role=\"pkg\">x-display-manager</emphasis> virtual package."
msgstr ""
msgid "Since the Falcot Corp administrators have opted to use the GNOME desktop environment, they logically picked <command>gdm3</command> as a display manager too. The <filename>/etc/gdm3/daemon.conf</filename> configuration file has many options (the list can be found in the <filename>/usr/share/gdm/gdm.schemas</filename> schema file) to control its behavior while <filename>/etc/gdm3/greeter.dconf-defaults</filename> contains settings for the greeter “session” (more than just a login window, it is a limited desktop with power management and accessibility related tools). Note that some of the most useful settings for end-users can be tweaked with GNOME's control center."
@ -647,7 +650,7 @@ msgstr ""
msgid "Before Debian <emphasis role=\"distribution\">Stretch</emphasis>, Firefox and Thunderbird were missing. The <emphasis role=\"pkg\">iceweasel</emphasis> package contained Iceweasel, which was basically Firefox under another name."
msgstr ""
msgid "The rationale behind this renaming was a result of the usage rules imposed by the Mozilla Foundation on the <trademark>Firefox</trademark> registered trademark: any software named Firefox had to use the official Firefox logo and icons. However, since these elements are not released under a free license, Debian could not distribute them in its <emphasis>main</emphasis> section. Rather than moving the whole browser to <emphasis>non-free</emphasis>, the package maintainer choose to use a different name."
msgid "The rationale behind this renaming was a result of the usage rules imposed by the Mozilla Foundation on the <trademark>Firefox</trademark> registered trademark: any software named Firefox had to use the official Firefox logo and icons. However, since these elements were not released under a free license, Debian could not distribute them in its <emphasis>main</emphasis> section. Rather than moving the whole browser to <emphasis>non-free</emphasis>, the package maintainer chose to use a different name."
msgstr ""
msgid "For similar reasons, the <trademark>Thunderbird</trademark> email client was renamed to Icedove in a similar fashion."
@ -680,7 +683,7 @@ msgstr ""
msgid "Tools for GTK+ on GNOME"
msgstr ""
msgid "Anjuta (in the <emphasis role=\"pkg\">anjuta</emphasis> package) and GNOME Builder (in the <emphasis role=\"pkg\">gnome-builder</emphasis> package) are Integrated Development Environments (<acronym>IDE</acronym>) optimized for creating GTK+ applications for GNOME. Glade (in the <emphasis role=\"pkg\">glade</emphasis> package) is an application designed to create GTK+ graphical interfaces for GNOME and save them in an XML file. These XML files can then be loaded by the GTK+ shared library through its <literal>GtkBuilder</literal> component to recreate the saved interfaces; such a feature can be interesting, for instance for plugins that require dialogs. <ulink type=\"block\" url=\"https://wiki.gnome.org/Apps/Builder\" /> <ulink type=\"block\" url=\"http://anjuta.org/\" /> <ulink type=\"block\" url=\"https://glade.gnome.org/\" />"
msgid "Anjuta (in the <emphasis role=\"pkg\">anjuta</emphasis> package) and GNOME Builder (in the <emphasis role=\"pkg\">gnome-builder</emphasis> package) are Integrated Development Environments (<acronym>IDE</acronym>) optimized for creating GTK+ applications for GNOME. Glade (in the <emphasis role=\"pkg\">glade</emphasis> package) is an application designed to create GTK+ graphical interfaces for GNOME and save them in an XML file. These XML files can then be loaded by the GTK+ shared library through its <literal>GtkBuilder</literal> component to recreate the saved interfaces; such a feature can be interesting, for instance for plugins that require dialogs. <ulink type=\"block\" url=\"https://wiki.gnome.org/Apps/Builder\" /> <ulink type=\"block\" url=\"https://wiki.gnome.org/Apps(2f)Anjuta.html\" /> <ulink type=\"block\" url=\"https://glade.gnome.org/\" />"
msgstr ""
msgid "<primary>Anjuta</primary>"
@ -695,7 +698,7 @@ msgstr ""
msgid "Tools for Qt"
msgstr ""
msgid "The equivalent applications for Qt applications are KDevelop by KDE (in the <emphasis role=\"pkg\">kdevelop</emphasis> package) for the development environment, and Qt Designer (in the <emphasis role=\"pkg\">qttools5-dev-tools</emphasis> package) for the design of graphical interfaces for Qt applications."
msgid "The equivalent applications for Qt are KDevelop by KDE (in the <emphasis role=\"pkg\">kdevelop</emphasis> package) for the development environment, and Qt Designer (in the <emphasis role=\"pkg\">qttools5-dev-tools</emphasis> package) for the design of graphical interfaces for Qt applications."
msgstr ""
msgid "KDevelop is also a generic IDE and provides plugins for other languages like Python and PHP and different build systems."
@ -737,7 +740,7 @@ msgstr ""
msgid "<primary>Gnumeric</primary>"
msgstr ""
msgid "Another important feature for users is the ability to import Microsoft Office documents. Even though all office suites have this feature, only the ones in OpenOffice.org and LibreOffice are functional enough for daily use."
msgid "Another important feature for users is the ability to import Microsoft Office documents. Even though all office suites have this feature, only OpenOffice.org and LibreOffice are functional enough for daily use."
msgstr ""
msgid "<emphasis>THE BROADER VIEW</emphasis> LibreOffice replaces OpenOffice.org"

12
pot/14_security.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -233,7 +233,7 @@ msgstr ""
msgid "<primary>firewall</primary><secondary>chains</secondary>"
msgstr ""
msgid "The firewall is configured with <emphasis>tables</emphasis>, which hold <emphasis>rules</emphasis> contained in <emphasis>chains</emphasis>. Unlike iptables, <emphasis>nftables</emphasis> does not have any default table. The user decides which and how many tables to create. Every table must have only one of the following five families assigned: <literal>ip</literal>, <literal>ip6</literal>, <literal>inet</literal>, <literal>arp</literal> and <literal>bridge</literal>. <literal>ip</literal> is used if the family is not specified."
msgid "The firewall is configured with <emphasis>tables</emphasis>, which hold <emphasis>rules</emphasis> contained in <emphasis>chains</emphasis>. Unlike iptables, <emphasis>nftables</emphasis> does not have any default table. The user decides which and how many tables to create. Every table must have only one of the following five families assigned: <literal>ip</literal>, <literal>ip6</literal>, <literal>inet</literal>, <literal>arp</literal> or <literal>bridge</literal>. <literal>ip</literal> is used if the family is not specified."
msgstr ""
msgid "There are two types of chains: <emphasis>base chains</emphasis> and <emphasis>regular chains</emphasis>. A base chain is an entry point for packets from the networking stack. Base chains are registered into the Netfilter hooks, e.g. they see packets flowing through the TCP/IP stack. On the other hand, a regular chain is not attached to any hook so it does not see any traffic. But it may be used as a jump target for better organization of the rules."
@ -680,7 +680,7 @@ msgstr ""
msgid "To enable, disable, or configure “jails“, the main configuration file <filename>/etc/fail2ban/jail.conf</filename> is not supposed to be altered. Instead this is supposed to be done in <filename>/etc/fail2ban/jail.d/defaults-debian.conf</filename> or files within the same directory."
msgstr ""
msgid "If docker containers are involved, the rules injected into <command>iptables</command> by <command>fail2ban</command> to block traffic from specific IPs must be applied to the right chain by <command>chain = DOCKER-USER</command>. Otherwise, the ban will not work."
msgid "If Docker containers are involved, the rules injected into <command>iptables</command> by <command>fail2ban</command> to block traffic from specific IPs must be applied to the right chain by <command>chain = DOCKER-USER</command>. Otherwise, the ban will not work."
msgstr ""
msgid "Fail2Ban is a very simple and effective way to protect against the most common brute-force attacks, but it cannot protect against distributed brute-force attacks, which is when an attacker uses a large number of machines spread around the Internet."
@ -925,7 +925,7 @@ msgstr ""
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/suricata/suricata.yaml</filename></secondary>"
msgstr ""
msgid "On top of this, you should also edit to define the network <literal>interface</literal>. You might also want to set <literal>LISTENMODE=pcap</literal> in <filename>/etc/default/suricata</filename> because the default <literal>LISTENMODE=nfqueue</literal> requires further configuration to work properly (the netfilter firewall must be configured to pass packets to some user-space queue handled by suricata via the <literal>NFQUEUE</literal> target)."
msgid "On top of this, you should also define the network <literal>interface</literal>. You might also want to set <literal>LISTENMODE=pcap</literal> in <filename>/etc/default/suricata</filename> because the default <literal>LISTENMODE=nfqueue</literal> requires further configuration to work properly (the netfilter firewall must be configured to pass packets to some user-space queue handled by suricata via the <literal>NFQUEUE</literal> target)."
msgstr ""
msgid "To detect bad behavior, <command>suricata</command> needs a set of monitoring rules: you can find such rules in the <emphasis role=\"pkg\">snort-rules-default</emphasis> package. <command>snort</command> is the historical reference in the IDS ecosystem and <command>suricata</command> is able to reuse rules written for it."
@ -2162,7 +2162,7 @@ msgstr ""
msgid "<primary>forensics</primary>"
msgstr ""
msgid "Some of these operations can be made easier with specialized software. In particular, the <emphasis role=\"pkg\">sleuthkit</emphasis> package provides many tools to analyze a filesystem. Their use is made easier by the <emphasis>Autopsy Forensic Browser</emphasis> graphical interface (in the <emphasis role=\"pkg\">autopsy</emphasis> package). Some Linux distributions have a \"live install\" image and contain many programs for forensic analysis, such as Kali Linux (see <xref linkend=\"sect.kali\" />), with its <emphasis>forensic mode</emphasis>, BlackArchLinux, and the commercial Grml-Forensic, based on Grml (see <xref linkend=\"sect.grml\" />). <ulink type=\"block\" url=\"https://blackarch.org\" /> <ulink type=\"block\" url=\"https://grml-forensic.org/\" />"
msgid "Some of these operations can be made easier with specialized software. In particular, the <emphasis role=\"pkg\">sleuthkit</emphasis> package provides many tools to analyze a filesystem. Their use is made easier by the <emphasis>Autopsy Forensic Browser</emphasis> graphical interface (in the <emphasis role=\"pkg\">autopsy</emphasis> package). Some Linux distributions have a “live install” image and contain many programs for forensic analysis, such as Kali Linux (see <xref linkend=\"sect.kali\" />), with its <emphasis>forensic mode</emphasis>, BlackArchLinux, and the commercial Grml-Forensic, based on Grml (see <xref linkend=\"sect.grml\" />). <ulink type=\"block\" url=\"https://blackarch.org\" /> <ulink type=\"block\" url=\"https://grml-forensic.org/\" />"
msgstr ""
msgid "Reconstituting the Attack Scenario"

8
pot/15_debian-packaging.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -313,7 +313,7 @@ msgstr ""
msgid "<primary><command>chroot</command></primary>"
msgstr ""
msgid "These tools allow the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using <emphasis role=\"distribution\">Stable</emphasis> for its normal workload, and the chrooted environments can be running on the same machine using <emphasis role=\"distribution\">Unstable</emphasis> for package builds. Using these tools, it is also possible to build for a different distribution, like <emphasis role=\"distribution\">Ubuntu</emphasis>."
msgid "These tools allow the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). They also allow building a package for a Debian version that is not the one used by the system as a whole: the machine can be using <emphasis role=\"distribution\">Stable</emphasis> for its normal workload, and the chrooted environments can be running on the same machine using <emphasis role=\"distribution\">Unstable</emphasis> for package builds. Using these tools, it is also possible to build for a different distribution, like <emphasis role=\"distribution\">Ubuntu</emphasis>."
msgstr ""
msgid "<command>schroot</command>, <command>sbuild-shell</command>, or <command>pbuilder</command> allow running a command or a login shell in a <emphasis>chrooted</emphasis> environment."
@ -1036,7 +1036,7 @@ msgstr ""
msgid "One of the most famous packages is <emphasis role=\"pkg\">git-buildpackage</emphasis>. An alternative is <emphasis role=\"pkg\">dgit</emphasis>. Of course it is still possible to use neither of those."
msgstr ""
msgid "Below is an example for a <filename>~/.gbp.conf</filename> configuration file"
msgid "Below is an example for a <filename>~/.gbp.conf</filename> configuration file:"
msgstr ""
msgid ""

12
pot/70_conclusion.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -29,10 +29,10 @@ msgstr ""
msgid "Upcoming Developments"
msgstr ""
msgid "Now that Debian version 11 is out, the developers are already busy working on the next version, codenamed <emphasis role=\"distribution\">Bookworm</emphasis>…"
msgid "Now that Debian version 12 is out, the developers are already busy working on the next version, codenamed <emphasis role=\"distribution\">Trixie</emphasis>…"
msgstr ""
msgid "There is no official list of all planned changes, and Debian never makes promises relating to technical goals of the coming versions. However, a few development trends and discussion topics can already be noted, and we can try to guess what might happen (or not). Some of the expected changes are documented in the Debian 11 release notes: <ulink type=\"block\" url=\"https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#deprecated-components\" />"
msgid "There is no official list of all planned changes, and Debian never makes promises relating to technical goals of the coming versions. However, a few development trends and discussion topics can already be noted, and we can try to guess what might happen (or not). Some of the expected changes are documented in the Debian 12 release notes: <ulink type=\"block\" url=\"https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#deprecated-components\" />"
msgstr ""
msgid "Beyond usual deprecation of some software components, it is worth pointing out that Debian is in the process of switching to what is known as a <emphasis>merged-usr filesystem</emphasis>: in this scheme <literal>/bin</literal>, <literal>/sbin</literal> and <literal>/lib</literal> are symlinks pointing to the corresponding directories in <literal>/usr</literal>. This improves compatibility between all Unix systems, makes us closer of having all Debian-supplied files in a single top-level directory that can be easily protected, snapshotted or shared. You can learn more about the benefits here: <ulink type=\"block\" url=\"https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/\" />"
@ -59,7 +59,7 @@ msgstr ""
msgid "The default permission of home directories will be more restrictive, allowing only the user to access their files."
msgstr ""
msgid "Developments which already began will continue: Improve build reproducibility and security for example. With the widespread use of continuous integration and the growth of the archive (and of the biggest packages!), the constraints on release architectures will be harder to meet and architectures will be dropped."
msgid "Developments which already began will continue: Improve build reproducibility and security for example. With the widespread use of continuous integration and the growth of the archive (and of the biggest packages!), the constraints on release architectures will be harder to meet and some architectures will be dropped."
msgstr ""
msgid "Debian's Future"
@ -71,7 +71,7 @@ msgstr ""
msgid "The Debian user community will increase, and new contributors will join the project… including, maybe, you!"
msgstr ""
msgid "There are recurring discussions about how the software ecosystem is evolving, towards applications shipped within containers, where Debian packages have no added value, or with language-specific package managers (e.g. <command>pip</command> for Python, <command>npm</command> for JavaScript, etc.), which are rendering <command>dpkg</command> and <command>apt</command> obsolete. Facing those threats, I am convinced that Debian developers will find ways to embrace those changes and to continue to provide value to users."
msgid "There are recurring discussions about how the software ecosystem is evolving, towards applications shipped within containers, where Debian packages have no added value, or with language-specific package managers (e.g. <command>pip</command> for Python, <command>npm</command> for JavaScript, etc.), which are rendering <command>dpkg</command> and <command>apt</command> obsolete. Facing those threats, we are convinced that Debian developers will find ways to embrace those changes and to continue to provide value to users."
msgstr ""
msgid "In spite of its old age and its respectable size, Debian keeps on growing in all kinds of (sometimes unexpected) directions. Contributors are teeming with ideas, and discussions on development mailing lists, even when they look like bickerings, keep increasing the momentum. Debian is sometimes compared to a black hole, of such density that any new free software project is attracted."

4
pot/90_derivative-distributions.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"

8
pot/92_short-remedial-course.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -544,7 +544,7 @@ msgstr ""
msgid "<primary>Compatibility Support Mode</primary><see>CSM</see>"
msgstr ""
msgid "BIOS (which stands for Basic Input/Output System) is a software that is included in the motherboard - the electronic board connecting all peripherals - and executed when the computer is booted, in order to load an operating system (via an adapted bootloader). It stays in the background to provide an interface between the hardware and the software (in our case, the Linux kernel)."
msgid "BIOS (which stands for Basic Input/Output System) is a software that is included in the motherboard - the electronic board connecting all components - and executed when the computer is booted, in order to load an operating system (via an adapted bootloader). It stays in the background to provide an interface between the hardware and the software (in our case, the Linux kernel)."
msgstr ""
msgid "In 2005/2006 its successor, the UEFI (Unified Extensible Firmware Interface) specification, has been published. This specification defines an interface that has the same purpose as the BIOS, but tries to provide more usability, extensibility, and flexibility, a graphical user interface, and true 64bit support. And it got rid of some of the limitations of BIOS booting: with the usage of a dedicated partition, the bootloaders no longer need special tricks to fit in a tiny <emphasis>master boot record</emphasis> and then discover the kernel to boot. Even better, with a suitably built Linux kernel, UEFI can directly boot the kernel without any intermediary bootloader. UEFI is also the basic foundation used to deliver <emphasis>Secure Boot</emphasis>, a technology ensuring that you run only software validated by your operating system vendor."
@ -648,7 +648,7 @@ msgstr ""
msgid "<primary>device</primary><secondary>block</secondary>"
msgstr ""
msgid "Applications often access devices by way of special files created within <filename>/dev/</filename> (see sidebar <xref linkend=\"sidebar.special-files\" />). These are special files that represent disk drives (for instance, <filename>/dev/hda</filename> and <filename>/dev/sdc</filename>), <filename>/dev/nvme1n1</filename> partitions (<filename>/dev/hda1</filename> or <filename>/dev/sdc3</filename> or <filename>/dev/nvme1n1p2</filename>), mice (<filename>/dev/input/mouse0</filename>), keyboards (<filename>/dev/input/event0</filename>), soundcards (<filename>/dev/snd/*</filename>), serial ports (<filename>/dev/ttyS*</filename>), and so on."
msgid "Applications often access devices by way of special files created within <filename>/dev/</filename> (see sidebar <xref linkend=\"sidebar.special-files\" />). These are special files that represent disk drives (for instance, <filename>/dev/hda</filename>, <filename>/dev/sdc</filename>, or <filename>/dev/nvme1n1</filename>), partitions (<filename>/dev/hda1</filename>, <filename>/dev/sdc3</filename>, or <filename>/dev/nvme1n1p2</filename>), mice (<filename>/dev/input/mouse0</filename>), keyboards (<filename>/dev/input/event0</filename>), soundcards (<filename>/dev/snd/*</filename>), serial ports (<filename>/dev/ttyS*</filename>), and so on."
msgstr ""
msgid "Filesystems"

8
pot/99_backcover.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -14,13 +14,13 @@ msgstr ""
msgid "The Debian Administrator's Handbook"
msgstr ""
msgid "Debian Bullseye from Discovery to Mastery"
msgid "Debian Bookworm from Discovery to Mastery"
msgstr ""
msgid "Debian GNU/Linux, a very popular non-commercial Linux distribution, is known for its reliability and richness. Built and maintained by an impressive network of thousands of developers throughout the world, the Debian project is cemented by its social contract. This foundation text defines the project's objective: fulfilling the needs of users with a 100% free operating system. The success of Debian and of its ecosystem of derivative distributions (with Ubuntu at the forefront) means that an increasing number of administrators are exposed to Debian's technologies."
msgstr ""
msgid "This Debian Administrator's Handbook, which has been entirely updated for Debian 11 “Bullseye”, builds on the success of its 9 previous editions. Accessible to all, this book teaches the essentials to anyone who wants to become an effective and independent Debian GNU/Linux administrator. It covers all the topics that a competent Linux administrator should master, from installation to updating the system, creating packages and compiling the kernel, but also monitoring, backup and migration, without forgetting advanced topics such as setting up SELinux or AppArmor to secure services, automated installations, or virtualization with Xen, KVM or LXC."
msgid "This Debian Administrator's Handbook, which has been entirely updated for Debian 12 “Bookworm”, builds on the success of its 10 previous editions. Accessible to all, this book teaches the essentials to anyone who wants to become an effective and independent Debian GNU/Linux administrator. It covers all the topics that a competent Linux administrator should master, from installation to updating the system, creating packages and compiling the kernel, but also monitoring, backup and migration, without forgetting advanced topics such as setting up SELinux or AppArmor to secure services, automated installations, or virtualization with Xen, KVM or LXC."
msgstr ""
msgid "This book is not only designed for professional system administrators. Anyone who uses Debian or Ubuntu on their own computer is de facto an administrator and will find tremendous value in knowing more about how their system works. Being able to understand and resolve problems will save you invaluable time."

6
pot/99_website.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"
@ -23,7 +23,7 @@ msgstr ""
msgid "The paperback is available through Lulu's print-on-demand service at a price of €44.90 (without VAT and shipping). <ulink url=\"\">Click here to view the book details on Lulu.com</ulink> or order it from their shop."
msgstr ""
msgid "This paperback covers the latest version of Debian (Debian 11 Bullseye)."
msgid "This paperback covers the latest version of Debian (Debian 12 Bookworm)."
msgstr ""
msgid "Note that the paperback linked here has not yet been updated for the latest version of Debian. The electronic version might be more up-to-date."

4
pot/Author_Group.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"

4
pot/Book_Info.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"

4
pot/Revision_History.pot
View file

@ -1,8 +1,8 @@
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2025-04-22 01:11+0200\n"
"PO-Revision-Date: 2025-04-22 01:11+0200\n"
"POT-Creation-Date: 2025-08-09 20:03+0200\n"
"PO-Revision-Date: 2025-08-09 20:03+0200\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"Language: en-US \n"