Changes
Translation components API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/translations/debian-handbook/12_advanced-administration/de/changes/?format=api&page=14
{ "count": 772, "next": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/changes/?format=api&page=15", "previous": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/changes/?format=api&page=13", "results": [ { "unit": "https://hosted.weblate.org/api/units/16827949/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:55.710086+02:00", "action": 30, "target": "The Nagios web interface is rather nice, but it does not allow configuration, nor can it be used to add monitored hosts and services. The whole configuration is managed via files referenced in the central configuration file, <filename>/etc/nagios4/nagios.cfg</filename>.", "old": "The Nagios web interface is rather nice, but it does not allow configuration, nor can it be used to add monitored hosts and services. The whole configuration is managed via files referenced in the central configuration file, <filename>/etc/nagios3/nagios.cfg</filename>.", "details": {}, "id": 6194898, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194898/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827948/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:55.666707+02:00", "action": 30, "target": "<computeroutput># </computeroutput><userinput>systemctl stop nagios4\n</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios4/rw\n</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios4\n</userinput><computeroutput># </computeroutput><userinput>systemctl start nagios4\n</userinput>", "old": "<computeroutput># </computeroutput><userinput>service nagios3 stop</userinput>\n<computeroutput>[...]\n# </computeroutput><userinput>dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios3/rw\n</userinput><computeroutput># </computeroutput><userinput>dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios3\n</userinput><computeroutput># </computeroutput><userinput>service nagios3 start</userinput>\n<computeroutput>[...]</computeroutput>", "details": {}, "id": 6194897, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194897/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827947/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:55.622483+02:00", "action": 30, "target": "Enabling some features involves editing <filename>/etc/nagios4/nagios.cfg</filename>. We also need to set up write permissions for the directory used by Nagios, with commands such as the following:", "old": "As documented in <filename>/usr/share/doc/nagios3/README.Debian</filename>, enabling some features involves editing <filename>/etc/nagios3/nagios.cfg</filename> and setting its <literal>check_external_commands</literal> parameter to “1”. We also need to set up write permissions for the directory used by Nagios, with commands such as the following:", "details": {}, "id": 6194896, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194896/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827946/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:55.587352+02:00", "action": 30, "target": "Pointing a browser at <literal>http://<replaceable>server</replaceable>/nagios4/</literal> displays the web interface; in particular, note that Nagios already monitors some parameters of the machine where it runs. However, some interactive features such as adding comments to a host do not work. These features are disabled in the default configuration for Nagios, which is very restrictive for security reasons.", "old": "Pointing a browser at <literal>http://<replaceable>server</replaceable>/nagios3/</literal> displays the web interface; in particular, note that Nagios already monitors some parameters of the machine where it runs. However, some interactive features such as adding comments to a host do not work. These features are disabled in the default configuration for Nagios, which is very restrictive for security reasons.", "details": {}, "id": 6194895, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194895/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827942/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:55.385989+02:00", "action": 30, "target": "The various available fields are described by the “Plugin reference” available as part of the “Munin guide”. <ulink type=\"block\" url=\"https://munin.readthedocs.org/en/latest/reference/plugin.html\" />", "old": "The various available fields are described by the “Plugin reference” available as part of the “Munin guide”. <ulink type=\"block\" url=\"http://munin.readthedocs.org/en/latest/reference/plugin.html\" />", "details": {}, "id": 6194894, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194894/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827940/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:55.295435+02:00", "action": 30, "target": "Once all plugins are correctly set up, the daemon configuration must be updated to describe access control for the collected data. This involves <literal>allow</literal> directives in the <filename>/etc/munin/munin-node.conf</filename> file. The default configuration is <literal>allow ^127\\.0\\.0\\.1$</literal>, and only allows access to the local host. An administrator will usually add a similar line containing the IP address of the grapher host, then restart the daemon with <command>systemctl restart munin-node</command>.", "old": "Once all plugins are correctly set up, the daemon configuration must be updated to describe access control for the collected data. This involves <literal>allow</literal> directives in the <filename>/etc/munin/munin-node.conf</filename> file. The default configuration is <literal>allow ^127\\.0\\.0\\.1$</literal>, and only allows access to the local host. An administrator will usually add a similar line containing the IP address of the grapher host, then restart the daemon with <command>service munin-node restart</command>.", "details": {}, "id": 6194892, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194892/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827935/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:54.675018+02:00", "action": 30, "target": "When a computer is booted from the network, the server sending the initialization elements also defines the boot parameters. Thus, the change needs to be made in the PXE configuration for the boot server; more specifically, in its <filename>/tftpboot/pxelinux.cfg/default</filename> configuration file. Setting up network boot is a prerequisite; see the Installation Guide for details. <ulink type=\"block\" url=\"https://www.debian.org/releases/stable/amd64/ch04s05\" />", "old": "When a computer is booted from the network, the server sending the initialization elements also defines the boot parameters. Thus, the change needs to be made in the PXE configuration for the boot server; more specifically, in its <filename>/tftpboot/pxelinux.cfg/default</filename> configuration file. Setting up network boot is a prerequisite; see the Installation Guide for details. <ulink type=\"block\" url=\"https://www.debian.org/releases/jessie/amd64/ch04s05.html\" />", "details": {}, "id": 6194887, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194887/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827931/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:54.023495+02:00", "action": 30, "target": "<computeroutput># </computeroutput><userinput>virsh -c qemu:///system vncdisplay testkvm\n</userinput><computeroutput>127.0.0.1:0</computeroutput>", "old": "<computeroutput># </computeroutput><userinput>virsh -c qemu:///system vncdisplay testkvm\n</userinput><computeroutput>:0</computeroutput>", "details": {}, "id": 6194883, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194883/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827930/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.993690+02:00", "action": 30, "target": "<computeroutput># </computeroutput><userinput>virsh -c qemu:///system list --all\n Id Name State\n----------------------------------\n 8 testkvm shut off\n</userinput>", "old": "<computeroutput># </computeroutput><userinput>virsh -c qemu:///system list --all\n Id Name State\n----------------------------------\n - testkvm shut off\n</userinput>", "details": {}, "id": 6194882, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194882/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827929/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.865467+02:00", "action": 30, "target": "<literal>--graphics vnc</literal> states that the graphical console should be made available using VNC. The default behavior for the associated VNC server is to only listen on the local interface; if the VNC client is to be run on a different host, establishing the connection will require setting up an SSH tunnel (see <xref linkend=\"sect.ssh-port-forwarding\" />). Alternatively, <literal>--graphics vnc,listen=0.0.0.0</literal> can be used so that the VNC server is accessible from all interfaces; note that if you do that, you really should design your firewall accordingly.", "old": "<literal>--vnc</literal> states that the graphical console should be made available using VNC. The default behavior for the associated VNC server is to only listen on the local interface; if the VNC client is to be run on a different host, establishing the connection will require setting up an SSH tunnel (see <xref linkend=\"sect.ssh-port-forwarding\" />). Alternatively, the <literal>--vnclisten=0.0.0.0</literal> can be used so that the VNC server is accessible from all interfaces; note that if you do that, you really should design your firewall accordingly.", "details": {}, "id": 6194881, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194881/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827928/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.809972+02:00", "action": 30, "target": "The <literal>--disk</literal> specifies the location of the image file that is to represent our virtual machine's hard disk; that file is created, unless present, with a size (in GB) specified by the <literal>size</literal> parameter. The <literal>format</literal> parameter allows choosing among several ways of storing the image file. The default format (<literal>qcow2</literal>) allows starting with a small file that only grows when the virtual machine starts actually using space.", "old": "The <literal>--disk</literal> specifies the location of the image file that is to represent our virtual machine's hard disk; that file is created, unless present, with a size (in GB) specified by the <literal>size</literal> parameter. The <literal>format</literal> parameter allows choosing among several ways of storing the image file. The default format (<literal>raw</literal>) is a single file exactly matching the disk's size and contents. We picked a more advanced format here, that is specific to QEMU and allows starting with a small file that only grows when the virtual machine starts actually using space.", "details": {}, "id": 6194880, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194880/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827927/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.788637+02:00", "action": 30, "target": "The <literal>--memory</literal> option allows specifying the amount of RAM (in MB) to allocate for the virtual machine.", "old": "The <literal>--ram</literal> option allows specifying the amount of RAM (in MB) to allocate for the virtual machine.", "details": {}, "id": 6194879, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194879/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827925/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.715799+02:00", "action": 30, "target": "All samples in this section assume that you are running commands as root. Effectively, if you want to control a local libvirt daemon, you need either to be root or to be a member of the <literal>libvirt</literal> group (which is not the case by default). Thus if you want to avoid using root rights too often, you can add yourself to the <literal>libvirt</literal> group and run the various commands under your user identity.", "old": "All samples in this section assume that you are running commands as root. Effectively, if you want to control a local libvirt daemon, you need either to be root or to be a member of the <literal>libvirt</literal> group (which is not the case by default). Thus if you want to avoid using root rights too often, you can add yoursel to the <literal>libvirt</literal> group and run the various commands under your user identity.", "details": {}, "id": 6194877, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194877/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827924/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.601771+02:00", "action": 30, "target": "We first install the required packages, with <command>apt-get install libvirt-clients libvirt-daemon-system qemu-kvm virtinst virt-manager virt-viewer</command>. <emphasis role=\"pkg\">libvirt-daemon-system</emphasis> provides the <command>libvirtd</command> daemon, which allows (potentially remote) management of the virtual machines running of the host, and starts the required VMs when the host boots. <emphasis role=\"pkg\">libvirt-clients</emphasis> provides the <command>virsh</command> command-line tool, which allows controlling the <command>libvirtd</command>-managed machines.", "old": "We first install the required packages, with <command>apt-get install qemu-kvm libvirt-bin virtinst virt-manager virt-viewer</command>. <emphasis role=\"pkg\">libvirt-bin</emphasis> provides the <command>libvirtd</command> daemon, which allows (potentially remote) management of the virtual machines running of the host, and starts the required VMs when the host boots. In addition, this package provides the <command>virsh</command> command-line tool, which allows controlling the <command>libvirtd</command>-managed machines.", "details": {}, "id": 6194876, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194876/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827920/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.295220+02:00", "action": 30, "target": "lxc.uts.name = testlxc", "old": "lxc.utsname = testlxc", "details": {}, "id": 6194873, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194873/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827918/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.214349+02:00", "action": 30, "target": "Note that the Debian template creation script accepts an <option>--arch</option> option to specify the architecture of the system to be installed and a <option>--release</option> option if you want to install something else than the current stable release of Debian. You can also set the <literal>MIRROR</literal> environment variable to point to a local Debian mirror.", "old": "Note that the debian template creation script accepts an <option>--arch</option> option to specify the architecture of the system to be installed and a <option>--release</option> option if you want to install something else than the current stable release of Debian. You can also set the <literal>MIRROR</literal> environment variable to point to a local Debian mirror.", "details": {}, "id": 6194871, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194871/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827916/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.093319+02:00", "action": 30, "target": "In cases where this configuration cannot be used (for instance, if no public IP addresses can be assigned to the containers), a virtual <emphasis>tap</emphasis> interface will be created and connected to the bridge. The equivalent network topology then becomes that of a host with a second network card plugged into a separate switch, with the containers also plugged into that switch. The host must then act as a gateway for the containers if they are meant to communicate with the outside world.", "old": "In cases where this configuration cannot be used (for instance if no public IP addresses can be assigned to the containers), a virtual <emphasis>tap</emphasis> interface will be created and connected to the bridge. The equivalent network topology then becomes that of a host with a second network card plugged into a separate switch, with the containers also plugged into that switch. The host must then act as a gateway for the containers if they are meant to communicate with the outside world.", "details": {}, "id": 6194869, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194869/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827914/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:53.010918+02:00", "action": 30, "target": "The goal of installing LXC is to set up virtual machines; while we could, of course, keep them isolated from the network, and only communicate with them via the filesystem, most use cases involve giving at least minimal network access to the containers. In the typical case, each container will get a virtual network interface, connected to the real network through a bridge. This virtual interface can be plugged either directly onto the host's physical network interface (in which case the container is directly on the network), or onto another virtual interface defined on the host (and the host can then filter or route traffic). In both cases, the <emphasis role=\"pkg\">bridge-utils</emphasis> package will be required.", "old": "The goal of installing LXC is to set up virtual machines; while we could of course keep them isolated from the network, and only communicate with them via the filesystem, most use cases involve giving at least minimal network access to the containers. In the typical case, each container will get a virtual network interface, connected to the real network through a bridge. This virtual interface can be plugged either directly onto the host's physical network interface (in which case the container is directly on the network), or onto another virtual interface defined on the host (and the host can then filter or route traffic). In both cases, the <emphasis role=\"pkg\">bridge-utils</emphasis> package will be required.", "details": {}, "id": 6194867, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194867/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827913/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:52.869484+02:00", "action": 30, "target": "These features can be combined to isolate a whole process family starting from the <command>init</command> process, and the resulting set looks very much like a virtual machine. The official name for such a setup is a “container” (hence the LXC moniker: <emphasis>LinuX Containers</emphasis>), but a rather important difference with “real” virtual machines such as provided by Xen or KVM is that there is no second kernel; the container uses the very same kernel as the host system. This has both pros and cons: advantages include excellent performance due to the total lack of overhead, and the fact that the kernel has a global vision of all the processes running on the system, so the scheduling can be more efficient than it would be if two independent kernels were to schedule different task sets. Chief among the inconveniences is the impossibility to run a different kernel in a container (whether a different Linux version or a different operating system altogether).", "old": "These features can be combined to isolate a whole process family starting from the <command>init</command> process, and the resulting set looks very much like a virtual machine. The official name for such a setup is a “container” (hence the LXC moniker: <emphasis>LinuX Containers</emphasis>), but a rather important difference with “real” virtual machines such as provided by Xen or KVM is that there's no second kernel; the container uses the very same kernel as the host system. This has both pros and cons: advantages include excellent performance due to the total lack of overhead, and the fact that the kernel has a global vision of all the processes running on the system, so the scheduling can be more efficient than it would be if two independent kernels were to schedule different task sets. Chief among the inconveniences is the impossibility to run a different kernel in a container (whether a different Linux version or a different operating system altogether).", "details": {}, "id": 6194866, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194866/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827912/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:52.665036+02:00", "action": 30, "target": "Xen has many more features than we can describe in these few paragraphs. In particular, the system is very dynamic, and many parameters for one domain (such as the amount of allocated memory, the visible hard drives, the behavior of the task scheduler, and so on) can be adjusted even when that domain is running. A domU can even be migrated across servers without being shut down, and without losing its network connections! For all these advanced aspects, the primary source of information is the official Xen documentation. <ulink type=\"block\" url=\"https://xenproject.org/help/documentation/\" />", "old": "Xen has many more features than we can describe in these few paragraphs. In particular, the system is very dynamic, and many parameters for one domain (such as the amount of allocated memory, the visible hard drives, the behavior of the task scheduler, and so on) can be adjusted even when that domain is running. A domU can even be migrated across servers without being shut down, and without losing its network connections! For all these advanced aspects, the primary source of information is the official Xen documentation. <ulink type=\"block\" url=\"http://www.xen.org/support/documentation.html\" />", "details": {}, "id": 6194864, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194864/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827910/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:52.485627+02:00", "action": 30, "target": "While it is of course possible to have several domU systems running in parallel, they will all need to use their own image, since each domU is made to believe it runs on its own hardware (apart from the small slice of the kernel that talks to the hypervisor). In particular, it isn't possible for two domU systems running simultaneously to share storage space. If the domU systems are not run at the same time, it is, however, quite possible to reuse a single swap partition, or the partition hosting the <filename>/home</filename> filesystem.", "old": "While it is of course possible to have several domU systems running in parallel, they will all need to use their own image, since each domU is made to believe it runs on its own hardware (apart from the small slice of the kernel that talks to the hypervisor). In particular, it isn't possible for two domU systems running simultaneously to share storage space. If the domU systems are not run at the same time, it is however quite possible to reuse a single swap partition, or the partition hosting the <filename>/home</filename> filesystem.", "details": {}, "id": 6194862, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194862/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827908/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:52.372949+02:00", "action": 30, "target": "After rebooting to make sure the bridge is automatically created, we can now start the domU with the Xen control tools, in particular the <command>xl</command> command. This command allows different manipulations on the domains, including listing them and, starting/stopping them. You might need to increase the default memory by editing the variable memory from configuration file (in this case, <filename>/etc/xen/testxen.cfg</filename>). Here we have set it to 1024 (megabytes).", "old": "After rebooting to make sure the bridge is automatically created, we can now start the domU with the Xen control tools, in particular the <command>xl</command> command. This command allows different manipulations on the domains, including listing them and, starting/stopping them.", "details": {}, "id": 6194860, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194860/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827901/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.925935+02:00", "action": 30, "target": "Xen requires modifications to all the operating systems one wants to run on it; not all kernels have the same level of maturity in this regard. Many are fully-functional, both as dom0 and domU: Linux 3.0 and later, NetBSD 4.0 and later, and OpenSolaris. Others only work as a domU. You can check the status of each operating system in the Xen wiki: <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/Dom0_Kernels_for_Xen\" /> <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/DomU_Support_for_Xen\" />", "old": "Xen requires modifications to all the operating systems one wants to run on it; not all kernels have the same level of maturity in this regard. Many are fully-functional, both as dom0 and domU: Linux 3.0 and later, NetBSD 4.0 and later, and OpenSolaris. Others only work as a domU. You can check the status of each operating system in the Xen wiki: <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/Dom0_Kernels_for_Xen\" /> <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/DomU_Support_for_Xen\" />", "details": {}, "id": 6194853, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194853/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827900/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.881411+02:00", "action": 30, "target": "Since <emphasis role=\"distribution\">Jessie</emphasis> is based on version 3.16 of the Linux kernel, the standard <emphasis role=\"pkg\">linux-image-686-pae</emphasis> and <emphasis role=\"pkg\">linux-image-amd64</emphasis> packages include the necessary code, and the distribution-specific patching that was required for <emphasis role=\"distribution\">Squeeze</emphasis> and earlier versions of Debian is no more. <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/Xen_Kernel_Feature_Matrix\" />", "old": "Since <emphasis role=\"distribution\">Jessie</emphasis> is based on version 3.16 of the Linux kernel, the standard <emphasis role=\"pkg\">linux-image-686-pae</emphasis> and <emphasis role=\"pkg\">linux-image-amd64</emphasis> packages include the necessary code, and the distribution-specific patching that was required for <emphasis role=\"distribution\">Squeeze</emphasis> and earlier versions of Debian is no more. <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/Xen_Kernel_Feature_Matrix\" />", "details": {}, "id": 6194852, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194852/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827899/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.851311+02:00", "action": 30, "target": "Xensource, the company behind Xen, therefore had to port Xen to this new framework, so that the Xen patches could be merged into the official Linux kernel. That meant a lot of code rewrite, and although Xensource soon had a working version based on the paravirt_ops interface, the patches were only progressively merged into the official kernel. The merge was completed in Linux 3.0. <ulink type=\"block\" url=\"https://wiki.xenproject.org/wiki/XenParavirtOps\" />", "old": "Xensource, the company behind Xen, therefore had to port Xen to this new framework, so that the Xen patches could be merged into the official Linux kernel. That meant a lot of code rewrite, and although Xensource soon had a working version based on the paravirt_ops interface, the patches were only progressively merged into the official kernel. The merge was completed in Linux 3.0. <ulink type=\"block\" url=\"http://wiki.xenproject.org/wiki/XenParavirtOps\" />", "details": {}, "id": 6194851, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194851/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827894/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.721145+02:00", "action": 30, "target": "<emphasis>HARDWARE</emphasis> Virtualization support", "old": "<emphasis>GOING FURTHER</emphasis> Mass virtualization", "details": {}, "id": 6194850, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194850/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827890/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.459645+02:00", "action": 30, "target": "We now have both some redundancy for important data and much flexibility in how the available space is split across the applications.", "old": "We now have both some redundancy for important data and much flexibility in how the available space is split across the applications. Should new software be installed later on (for editing audio clips, for instance), the LV hosting <filename>/usr/</filename> can be grown painlessly.", "details": {}, "id": 6194846, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194846/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827889/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.419228+02:00", "action": 30, "target": "We will therefore create the <filename>lv_var</filename> and <filename>lv_home</filename> LVs on <filename>vg_raid</filename>, to host the matching filesystems; another large LV, <filename>lv_movies</filename>, will be used to host the definitive versions of movies after editing. The other VG will be split into a large <filename>lv_rushes</filename>, for data straight out of the digital video cameras, and a <filename>lv_tmp</filename> for temporary files. The location of the work area is a less straightforward choice to make: while good performance is needed for that volume, is it worth risking losing work if a disk fails during an editing session? Depending on the answer to that question, the relevant LV will be created on one VG or the other.", "old": "We will therefore create the <filename>lv_usr</filename>, <filename>lv_var</filename> and <filename>lv_home</filename> LVs on <filename>vg_raid</filename>, to host the matching filesystems; another large LV, <filename>lv_movies</filename>, will be used to host the definitive versions of movies after editing. The other VG will be split into a large <filename>lv_rushes</filename>, for data straight out of the digital video cameras, and a <filename>lv_tmp</filename> for temporary files. The location of the work area is a less straightforward choice to make: while good performance is needed for that volume, is it worth risking losing work if a disk fails during an editing session? Depending on the answer to that question, the relevant LV will be created on one VG or the other.", "details": {}, "id": 6194845, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194845/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827888/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.230677+02:00", "action": 30, "target": "LVM also caters for more advanced uses, where many details can be specified by hand. For instance, an administrator can tweak the size of the blocks that make up physical and logical volumes, as well as their physical layout. It is also possible to move blocks across PVs, for instance, to fine-tune performance or, in a more mundane way, to free a PV when one needs to extract the corresponding physical disk from the VG (whether to affect it to another VG or to remove it from LVM altogether). The manual pages describing the commands are generally clear and detailed. A good entry point is the <citerefentry><refentrytitle>lvm</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page.", "old": "LVM also caters for more advanced uses, where many details can be specified by hand. For instance, an administrator can tweak the size of the blocks that make up physical and logical volumes, as well as their physical layout. It is also possible to move blocks across PVs, for instance to fine-tune performance or, in a more mundane way, to free a PV when one needs to extract the corresponding physical disk from the VG (whether to affect it to another VG or to remove it from LVM altogether). The manual pages describing the commands are generally clear and detailed. A good entry point is the <citerefentry><refentrytitle>lvm</refentrytitle> <manvolnum>8</manvolnum></citerefentry> manual page.", "details": {}, "id": 6194843, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194843/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827885/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:51.088835+02:00", "action": 30, "target": "Not all filesystems can be resized online; resizing a volume can therefore require unmounting the filesystem first and remounting it afterwards. Of course, if one wants to shrink the space allocated to an LV, the filesystem must be shrunk first; the order is reversed when the resizing goes in the other direction: the logical volume must be grown before the filesystem on it. It is rather straightforward, since at no time must the filesystem size be larger than the block device where it resides (whether that device is a physical partition or a logical volume).", "old": "Not all filesystems can be resized online; resizing a volume can therefore require unmounting the filesystem first and remounting it afterwards. Of course, if one wants to shrink the space allocated to an LV, the filesystem must be shrunk first; the order is reversed when the resizing goes in the other direction: the logical volume must be grown before the filesystem on it. It's rather straightforward, since at no time must the filesystem size be larger than the block device where it resides (whether that device is a physical partition or a logical volume).", "details": {}, "id": 6194840, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194840/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827882/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:50.886130+02:00", "action": 30, "target": "<emphasis>NOTE</emphasis> Auto-detecting LVM volumes", "old": "<emphasis>NOTE</emphasis> Autodetecting LVM volumes", "details": {}, "id": 6194837, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194837/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827881/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:50.842053+02:00", "action": 30, "target": "It is also possible to hint at the physical location of an LV, so that its extents are stored on a particular PV (while staying within the ones assigned to the VG, of course). Since we know that <filename>sdb</filename> is faster than <filename>sdf</filename>, we may want to store the <filename>lv_base</filename> there if we want to give an advantage to the database server compared to the file server. The command line becomes: <command>lvcreate -n lv_base -L 1G vg_critical /dev/sdb2</command>. Note that this command can fail if the PV doesn't have enough free extents. In our example, we would probably have to create <filename>lv_base</filename> before <filename>lv_files</filename> to avoid this situation – or free up some space on <filename>sdb2</filename> with the <command>pvmove</command> command.", "old": "It's also possible to hint at the physical location of an LV, so that its extents are stored on a particular PV (while staying within the ones assigned to the VG, of course). Since we know that <filename>sdb</filename> is faster than <filename>sdf</filename>, we may want to store the <filename>lv_base</filename> there if we want to give an advantage to the database server compared to the file server. The command line becomes: <command>lvcreate -n lv_base -L 1G vg_critical /dev/sdb2</command>. Note that this command can fail if the PV doesn't have enough free extents. In our example, we would probably have to create <filename>lv_base</filename> before <filename>lv_files</filename> to avoid this situation – or free up some space on <filename>sdb2</filename> with the <command>pvmove</command> command.", "details": {}, "id": 6194836, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194836/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827879/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:50.717170+02:00", "action": 30, "target": "We now have two “virtual disks”, sized about 8 GB and 12 GB respectively. Let's now carve them up into “virtual partitions” (LVs). This involves the <command>lvcreate</command> command, and a slightly more complex syntax:", "old": "We now have two “virtual disks”, sized about 8 GB and 12 GB, respectively. Let's now carve them up into “virtual partitions” (LVs). This involves the <command>lvcreate</command> command, and a slightly more complex syntax:", "details": {}, "id": 6194834, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194834/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827876/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:50.451919+02:00", "action": 30, "target": "A number of PVs can be clustered in a VG (<emphasis>Volume Group</emphasis>), which can be compared to disks both virtual and extensible. VGs are abstract, and don't appear in a device file in the <filename>/dev</filename> hierarchy, so there is no risk of using them directly.", "old": "A number of PVs can be clustered in a VG (<emphasis>Volume Group</emphasis>), which can be compared to disks both virtual and extensible. VGs are abstract, and don't appear in a device file in the <filename>/dev</filename> hierarchy, so there's no risk of using them directly.", "details": {}, "id": 6194831, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194831/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827869/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.921974+02:00", "action": 30, "target": "The <command>mdadm --create</command> command requires several parameters: the name of the volume to create (<filename>/dev/md*</filename>, with MD standing for <foreignphrase>Multiple Device</foreignphrase>), the RAID level, the number of disks (which is compulsory despite being mostly meaningful only with RAID-1 and above), and the physical drives to use. Once the device is created, we can use it like we'd use a normal partition, create a filesystem on it, mount that filesystem, and so on. Note that our creation of a RAID-0 volume on <filename>md0</filename> is nothing but coincidence, and the numbering of the array doesn't need to be correlated to the chosen amount of redundancy. It is also possible to create named RAID arrays, by giving <command>mdadm</command> parameters such as <filename>/dev/md/linear</filename> instead of <filename>/dev/md0</filename>.", "old": "The <command>mdadm --create</command> command requires several parameters: the name of the volume to create (<filename>/dev/md*</filename>, with MD standing for <foreignphrase>Multiple Device</foreignphrase>), the RAID level, the number of disks (which is compulsory despite being mostly meaningful only with RAID-1 and above), and the physical drives to use. Once the device is created, we can use it like we'd use a normal partition, create a filesystem on it, mount that filesystem, and so on. Note that our creation of a RAID-0 volume on <filename>md0</filename> is nothing but coincidence, and the numbering of the array doesn't need to be correlated to the chosen amount of redundancy. It's also possible to create named RAID arrays, by giving <command>mdadm</command> parameters such as <filename>/dev/md/linear</filename> instead of <filename>/dev/md0</filename>.", "details": {}, "id": 6194824, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194824/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827867/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.706576+02:00", "action": 30, "target": "This isn't strictly speaking, a RAID level, but a stacking of two RAID groupings. Starting from 2×N disks, one first sets them up by pairs into N RAID-1 volumes; these N volumes are then aggregated into one, either by “linear RAID” or (increasingly) by LVM. This last case goes farther than pure RAID, but there is no problem with that.", "old": "This isn't strictly speaking, a RAID level, but a stacking of two RAID groupings. Starting from 2×N disks, one first sets them up by pairs into N RAID-1 volumes; these N volumes are then aggregated into one, either by “linear RAID” or (increasingly) by LVM. This last case goes farther than pure RAID, but there's no problem with that.", "details": {}, "id": 6194822, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194822/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827865/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.441763+02:00", "action": 30, "target": "This system doesn't aim at increasing reliability, since (as in the linear case) the availability of all the data is jeopardized as soon as one disk fails, but at increasing performance: during sequential access to large amounts of contiguous data, the kernel will be able to read from both disks (or write to them) in parallel, which increases the data transfer rate. The disks are utilized entirely by the RAID device, so they should have the same size not to lose performance.", "old": "This system doesn't aim at increasing reliability, since (as in the linear case) the availability of all the data is jeopardized as soon as one disk fails, but at increasing performance: during sequential access to large amounts of contiguous data, the kernel will be able to read from both disks (or write to them) in parallel, which increases the data transfer rate. However, RAID-0 use is shrinking, its niche being filled by LVM (see later).", "details": {}, "id": 6194821, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194821/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827864/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.400712+02:00", "action": 30, "target": "Even though the kernel's RAID subsystem allows creating “linear RAID”, this is not proper RAID, since this setup doesn't involve any redundancy. The kernel merely aggregates several disks end-to-end and provides the resulting aggregated volume as one virtual disk (one block device). That is about its only function. This setup is rarely used by itself (see later for the exceptions), especially since the lack of redundancy means that one disk failing makes the whole aggregate, and therefore all the data, unavailable.", "old": "Even though the kernel's RAID subsystem allows creating “linear RAID”, this is not proper RAID, since this setup doesn't involve any redundancy. The kernel merely aggregates several disks end-to-end and provides the resulting aggregated volume as one virtual disk (one block device). That's about its only function. This setup is rarely used by itself (see later for the exceptions), especially since the lack of redundancy means that one disk failing makes the whole aggregate, and therefore all the data, unavailable.", "details": {}, "id": 6194820, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194820/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827863/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.364234+02:00", "action": 30, "target": "The I in RAID initially stood for <emphasis>inexpensive</emphasis>, because RAID allowed a drastic increase in data safety without requiring investing in expensive high-end disks. Probably due to image concerns, however, it is now more customarily considered to stand for <emphasis>independent</emphasis>, which doesn't have the unsavory flavor of cheapness.", "old": "The I in RAID initially stood for <emphasis>inexpensive</emphasis>, because RAID allowed a drastic increase in data safety without requiring investing in expensive high-end disks. Probably due to image concerns, however, it is now more customarily considered to stand for <emphasis>independent</emphasis>, which doesn't have the unsavory flavour of cheapness.", "details": {}, "id": 6194819, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194819/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827862/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.341181+02:00", "action": 30, "target": "RAID means <emphasis>Redundant Array of Independent Disks</emphasis>. The goal of this system is to prevent data loss and ensure availability in case of hard disk failure. The general principle is quite simple: data are stored on several physical disks instead of only one, with a configurable level of redundancy. Depending on this amount of redundancy, and even in the event of an unexpected disk failure, data can be losslessly reconstructed from the remaining disks.", "old": "RAID means <emphasis>Redundant Array of Independent Disks</emphasis>. The goal of this system is to prevent data loss in case of hard disk failure. The general principle is quite simple: data are stored on several physical disks instead of only one, with a configurable level of redundancy. Depending on this amount of redundancy, and even in the event of an unexpected disk failure, data can be losslessly reconstructed from the remaining disks.", "details": {}, "id": 6194818, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194818/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827860/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:49.301142+02:00", "action": 30, "target": "RAID and LVM are both techniques to abstract the mounted volumes from their physical counterparts (actual hard-disk drives or partitions thereof); the former ensures the security and availability of the data in case of hardware failure by introducing redundancy, the latter makes volume management more flexible and independent of the actual size of the underlying disks. In both cases, the system ends up with new block devices, which can be used to create filesystems or swap space, without necessarily having them mapped to one physical disk. RAID and LVM come from quite different backgrounds, but their functionality can overlap somewhat, which is why they are often mentioned together.", "old": "RAID and LVM are both techniques to abstract the mounted volumes from their physical counterparts (actual hard-disk drives or partitions thereof); the former secures the data against hardware failure by introducing redundancy, the latter makes volume management more flexible and independent of the actual size of the underlying disks. In both cases, the system ends up with new block devices, which can be used to create filesystems or swap space, without necessarily having them mapped to one physical disk. RAID and LVM come from quite different backgrounds, but their functionality can overlap somewhat, which is why they are often mentioned together.", "details": {}, "id": 6194816, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194816/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371205/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": "https://hosted.weblate.org/api/users/anonymous/?format=api", "timestamp": "2018-04-22T00:29:11+02:00", "action": 29, "target": "<primary>RAID</primary>", "old": "", "details": {}, "id": 2712072, "action_name": "Suggestion removed during cleanup", "url": "https://hosted.weblate.org/api/changes/2712072/?format=api" }, { "unit": null, "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": "https://hosted.weblate.org/api/users/_caba/?format=api", "timestamp": "2018-04-21T08:49:31+02:00", "action": 1, "target": "", "old": "", "details": {}, "id": 2710144, "action_name": "Translation completed", "url": "https://hosted.weblate.org/api/changes/2710144/?format=api" }, { "unit": null, "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": null, "timestamp": "2018-04-21T08:49:31+02:00", "action": 17, "target": "", "old": "", "details": {}, "id": 2710145, "action_name": "Changes committed", "url": "https://hosted.weblate.org/api/changes/2710145/?format=api" }, { "unit": null, "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": null, "author": null, "timestamp": "2018-04-21T08:48:43+02:00", "action": 17, "target": "", "old": "", "details": {}, "id": 2710139, "action_name": "Changes committed", "url": "https://hosted.weblate.org/api/changes/2710139/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2454910/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": "https://hosted.weblate.org/api/users/_caba/?format=api", "timestamp": "2018-04-21T08:33:23+02:00", "action": 5, "target": "Im Gegensatz zu anderen Virtualisierungssystemen war KVM von Anfang an Teil des Linux-Kernels. Seine Entwickler entschieden sich, die für eine Virtualisierung vorgesehenen Prozessor-Befehlssätze (Intel-VT und AMD-V) zu nutzen, wodurch KVM leichtgewichtig, elegant und ressourcenschonend bleibt. Die Kehrseite ist natürlich, dass KVM nicht auf allen Rechnerarchitekturen läuft, sondern nur auf denen mit entsprechenden Prozessoren. Sie können überprüfen, ob Sie einen derartigen Prozessor haben wenn unter den CPU-Flags in der Datei <filename>/proc/cpuinfo</filename> „vmx“ oder „svm“ aufgeführt ist.", "old": "Im Gegensatz zu anderen Virtualisierungssystemen war KVM von Anfang an Teil des Linux-Kernels. Seine Entwickler entschieden sich, die für eine Virtualisierung vorgesehenen Prozessor-Befehlssätze (Intel-VT und AMD-V) zu nutzen, wodurch KVM leichtgewichtig, elegant und ressourcenschonend bleibt. Die Kehrseite ist natürlich, dass KVM hauptsächlich auf i386- und amd64-Prozessoren läuft und zwar nur auf denen, die so neu sind, dass sie über diese Befehlssätze verfügen. Sie können sicher sein, dass Sie einen derartigen Prozessor haben, wenn unter den CPU-Flags in der Datei <filename>/proc/cpuinfo</filename> „vmx“ oder „svm“ aufgeführt ist.", "details": {}, "id": 2710104, "action_name": "Translation added", "url": "https://hosted.weblate.org/api/changes/2710104/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371256/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": "https://hosted.weblate.org/api/users/_caba/?format=api", "timestamp": "2018-04-21T08:29:00+02:00", "action": 5, "target": "LXC benötigt außerdem das Konfigurationssystem für die <emphasis>Kontrollgruppen</emphasis>, das ein unter <filename>/sys/fs/cgroup</filename> einzuhängendes virtuelles Dateisystem ist. Weil Debian 8 auf systemd geschwenkt hat, das auch auf control groups setzt, wird es automatisch beim Starten ohne weitere Konfiguration ausgeführt.", "old": "LXC benötigt außerdem das Konfigurationssystem für die <emphasis>Kontrollgruppen</emphasis>, das ein unter <filename>/sys/fs/cgroup</filename> einzuhängendes virtuelles Dateisystem ist. Die Datei <filename>/etc/fstab</filename> sollte daher unter anderem folgenden Eintrag enthalten:", "details": {}, "id": 2710103, "action_name": "Translation added", "url": "https://hosted.weblate.org/api/changes/2710103/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371254/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": "https://hosted.weblate.org/api/users/_caba/?format=api", "timestamp": "2018-04-21T08:26:16+02:00", "action": 5, "target": "Obwohl es dazu benutzt wird, „virtuelle Rechner“ zu erstellen, ist LXC genaugenommen kein Virtualisierungssystem, sondern ein System, um Gruppen von Prozessen voneinander zu isolieren, obwohl sie alle auf demselben Host laufen. Es macht sich eine Reihe neuerer Entwicklungen im Linux-Kernel zunutze, die gemeinhin als <emphasis>Kontrollgruppen</emphasis> (control groups) bekannt sind, mit denen verschiedene Sätze von Prozessen, die „Gruppen“ genannt werden, bestimmte Aspekte des Gesamtsystems auf unterschiedliche Weise sehen. Dies gilt vor allem für Aspekte wie die Prozesskennungen, die Netzwerkonfiguration und die Einhängepunkte. Eine derartige Gruppe isolierter Prozesse hat keinerlei Zugriff auf die anderen Prozesse des Systems, und ihre Zugriffe auf das Dateisystem können auf einen bestimmten Teilbereich eingegrenzt werden. Sie kann auch ihre eigene Netzwerkschnittstelle und Routing-Tabelle haben, und möglicherweise ist sie so konfiguriert, dass sie nur einen Teil der auf dem System verfügbaren Geräte sieht.", "old": "Obwohl es dazu benutzt wird, „virtuelle Rechner“ zu erstellen, ist LXC <indexterm><primary>LXC</primary></indexterm> genaugenommen kein Virtualisierungssystem, sondern ein System, um Gruppen von Prozessen voneinander zu isolieren, obwohl sie alle auf demselben Host laufen. Es macht sich eine Reihe neuerer Entwicklungen im Linux-Kernel zunutze, die gemeinhin als <emphasis>Kontrollgruppen</emphasis> bekannt sind, mit denen verschiedene Sätze von Prozessen, die „Gruppen“ genannt werden, bestimmte Aspekte des Gesamtsystems auf unterschiedliche Weise sehen. Dies gilt vor allem für Aspekte wie die Prozesskennungen, die Netzwerkonfiguration und die Einhängepunkte. Eine derartige Gruppe isolierter Prozesse hat keinerlei Zugriff auf die anderen Prozesse des Systems, und ihre Zugriffe auf das Dateisystem können auf einen bestimmten Teilbereich eingegrenzt werden. Sie kann auch ihre eigene Netzwerkschnittstelle und Routing-Tabelle haben, und möglicherweise ist sie so konfiguriert, dass sie nur einen Teil der auf dem System verfügbaren Geräte sieht.", "details": {}, "id": 2710096, "action_name": "Translation added", "url": "https://hosted.weblate.org/api/changes/2710096/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371221/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": "https://hosted.weblate.org/api/users/_caba/?format=api", "timestamp": "2018-04-21T08:14:51+02:00", "action": 5, "target": "Wenn der Rechner hochfährt, ruft der systemd-Service <filename>Lvm2-activation</filename> den Befehl <command>vgchange -aay</command> auf um alle volume groups zu aktivieren: Diejenigen, die als physische Volumes für LVM initialisiert sind, werden im LVM-Untersystem registriert; diejenigen, die zu Volume-Gruppen gehören, werden zusammengefügt; und die entsprechenden logischen Volumes werden gestartet und bereitgestellt. Es ist daher nicht erforderlich, Konfigurationsdateien zu editieren, wenn LVM-Volumes erstellt oder verändert werden.", "old": "Wenn der Rechner hochfährt, überprüft das Skript <filename>/etc/init.d/lvm</filename> die verfügbaren Geräte. Diejenigen, die als physische Volumes für LVM initialisiert sind, werden im LVM-Untersystem registriert; diejenigen, die zu Volume-Gruppen gehören, werden zusammengefügt; und die entsprechenden logischen Volumes werden gestartet und bereitgestellt. Es ist daher nicht erforderlich, Konfigurationsdateien zu editieren, wenn LVM-Volumes erstellt oder verändert werden.", "details": {}, "id": 2710086, "action_name": "Translation added", "url": "https://hosted.weblate.org/api/changes/2710086/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371217/?format=api", "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api", "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/de/?format=api", "user": "https://hosted.weblate.org/api/users/_caba/?format=api", "author": "https://hosted.weblate.org/api/users/_caba/?format=api", "timestamp": "2018-04-21T08:10:35+02:00", "action": 5, "target": "LVM, der <emphasis>Logical Volume Manager</emphasis>, ist ein weiterer Ansatz zur Abstraktion logischer Volumes von ihren physischen Geräten, der sich auf die Erhöhung der Flexibilität und nicht auf die Erhöhung der Zuverlässigkeit konzentriert. LVM erlaubt es, ein logisches Volume transparent für die Anwendungen zu ändern; es ist beispielsweise möglich, neue Platten hinzuzufügen, die Daten darauf zu migrieren und die alten Platten zu entfernen, ohne das Volume zu deinstallieren.", "old": "LVM, der <emphasis>Logical Volume Manager</emphasis>, ist ein weiterer Ansatz zur Abstraktion logischer Volumes von ihren physischen Unterstützungen, der sich auf die Erhöhung der Flexibilität und nicht auf die Erhöhung der Zuverlässigkeit konzentriert. LVM erlaubt es, ein logisches Volume transparent für die Anwendungen zu ändern; es ist beispielsweise möglich, neue Platten hinzuzufügen, die Daten darauf zu migrieren und die alten Platten zu entfernen, ohne das Volume zu deinstallieren.", "details": {}, "id": 2710083, "action_name": "Translation added", "url": "https://hosted.weblate.org/api/changes/2710083/?format=api" } ] }