Translation status
| 635 | Strings | 93% | Translate |
|---|---|---|---|
| 15,385 | Words | 83% |
Other components
Translation Information
| Project website | https://debian-handbook.info/ | |
|---|---|---|
| Mailing list for translators | debian-handbook-translators@lists.alioth.debian.org | |
| Instructions for translators | ||
| Translation process |
|
|
| Translation license | GNU General Public License v2.0 or later | |
| Repository |
https://salsa.debian.org/hertzog/debian-handbook.git
|
|
| Repository branch | buster/master | |
| Last remote commit |
Drop draft status
bd654cd4
Raphaël Hertzog authored 10 days ago |
|
| Repository containing Weblate translations |
https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
|
|
| Filemask | */08_basic-configuration.po |
|
| Translation file |
ja-JP/08_basic-configuration.po
|
|
None
Using <command>apt</command> is so convenient that it makes it easy to forget about the lower-level tools, but the easiest way of installing a compiled kernel is to use a command such as <command>dpkg -i <replaceable>package</replaceable>.deb</command>, where <literal><replaceable>package</replaceable>.deb</literal> is the name of a <emphasis role="pkg">linux-image</emphasis> package such as <filename>linux-image-4.19.30-ckt47-falcot_1_amd64.deb</filename>.
A Debian kernel package installs the kernel image (<filename>vmlinuz-<replaceable>version</replaceable></filename>), its configuration (<filename>config-<replaceable>version</replaceable></filename>) and its symbols table (<filename>System.map-<replaceable>version</replaceable></filename>) in <filename>/boot/</filename>. The symbols table helps developers understand the meaning of a kernel error message; without it, kernel “oopses” (an “oops” is the kernel equivalent of a segmentation fault for user-space programs, in other words messages generated following an invalid pointer dereference) only contain numeric memory addresses, which is useless information without the table mapping these addresses to symbols and function names. The modules are installed in the <filename>/lib/modules/<replaceable>version</replaceable>/</filename> directory.
Before DKMS, <emphasis role="pkg">module-assistant</emphasis> was the simplest solution to build and deploy kernel modules. It can still be used, in particular for packages lacking DKMS integration: with a simple command like <command>module-assistant auto-install xtables-addonsdadhi</command> (or <command>m-a a-i xtables-addonsdahdi</command> for short), the modules are compiled for the current kernel, put in a new Debian package, and that package gets installed on the fly.
<computeroutput>$ </computeroutput><userinput>sudo apt install
<computeroutput>
[...]
Setting up xtables-addons-dkms (2.12-0.1) ...
Loading new xtables-addons-2.12 DKMS files...
Building for 4.19.0-
Building initial module for 4.19.0-
Done.
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-
[...]
DKMS: install completed.
$ </computeroutput><userinput>sudo dkms status</userinput>
<computeroutput>
$ </computeroutput><userinput>sudo modinfo
<computeroutput>filename: /lib/modules/4.19.0-
license: GPL
alias: ipt_ACCOUNT
author: Intra2net AG <opensource@intra2net.com>
description: Xtables: per-IP accounting for large prefixes
author: Robert Pleh <robert.pleh@hermes.si>
description: Timing-Only Driver
[...]
</computeroutput>
For example, let's look at the <emphasis role="pkg">xtables-addonsdahdi-source</emphasis> package: after installation, a <filename>.tar.bz2</filename> of the module's sources is stored in <filename>/usr/src/</filename>. While we could manually extract the tarball and build the module, in practice we prefer to automate all this using DKMS. Most modules offer the required DKMS integration in a package ending with a <literal>-dkms</literal> suffix. In our case, installing <emphasis role="pkg">xtables-addonsdahdi-dkms</emphasis> is all that is needed to compile the kernel module for the current kernel provided that we have the <emphasis role="pkg">linux-headers-*</emphasis> package matching the installed kernel. For instance, if you use <emphasis role="pkg">linux-image-amd64</emphasis>, you would also install <emphasis role="pkg">linux-headers-amd64</emphasis>.
These external packages are many and varied and we won't list them all here; the <command>apt-cache search source$</command> command can narrow down the search field, <command>apt-cache rdepends module-assistant$</command> can show the list provided by Debian. However, a complete list isn't particularly useful since there is no particular reason for compiling external modules except when you know you need it. In such cases, the device's documentation will typically detail the specific module(s) it needs to function under Linux.
Statistics
| Percent | Strings | Words | Chars | ||
|---|---|---|---|---|---|
| Total | 635 | 15,385 | 122,992 | ||
| Translated | 93% | 591 | 12,873 | 102,829 | |
| Needs editing | 5% | 36 | 2,089 | 16,879 | |
| Failing check | 32% | 209 | 4,458 | 40,660 |
Last activity
| Last change | April 9, 2018, 10:52 a.m. | |||
|---|---|---|---|---|
| Last author | Galina Anikina | |||