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/ar_MA/changes/?format=api&page=12
{ "count": 663, "next": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/ar_MA/changes/?format=api&page=13", "previous": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/ar_MA/changes/?format=api&page=11", "results": [ { "unit": "https://hosted.weblate.org/api/units/82696649/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408718+02:00", "action": 30, "target": "<primary>volume</primary><secondary>management</secondary>", "old": "<primary>installation</primary><secondary>automated installation</secondary>", "details": {}, "id": 34028632, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34028632/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696647/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408673+02:00", "action": 59, "target": "استعرض <xref linkend=\"installation\" /> هذه التقنيات من وجهة نظر برنامج التثبيت، والطريقة التي دمجت فيها هذه التقنيات حتى يكون إعدادها سهلاً منذ البداية. يجب على مدير النظام أن يستطيع معالجة الحاجات المتزايدة للمساحة التخزينية بعد التثبيت الأولي للنظام، دون اللجوء إلى عملية إعادة التثبيت المكلفة (من ناحية الوقت والجهد). أي أن مدير النظام يجب أن يستخدم الأدوات المطلوبة لتعديل نظامي LVM و RAID بمهارة.", "old": "", "details": { "state": 10, "source": "<xref linkend=\"installation\" /> presented these technologies from the point of view of the installer, and how it integrated them to make their deployment easy from the start. After the initial installation, an administrator must be able to handle evolving storage space needs without having to resort to an expensive re-installation. They must therefore understand the required tools for manipulating RAID and LVM volumes.", "old_state": -1 }, "id": 34028631, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34028631/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696647/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408634+02:00", "action": 30, "target": "<xref linkend=\"installation\" /> presented these technologies from the point of view of the installer, and how it integrated them to make their deployment easy from the start. After the initial installation, an administrator must be able to handle evolving storage space needs without having to resort to an expensive re-installation. They must therefore understand the required tools for manipulating RAID and LVM volumes.", "old": "<xref linkend=\"installation\" /> presented these technologies from the point of view of the installer, and how it integrated them to make their deployment easy from the start. After the initial installation, an administrator must be able to handle evolving storage space needs without having to resort to an expensive reinstallation. They must therefore understand the required tools for manipulating RAID and LVM volumes.", "details": {}, "id": 34028630, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34028630/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696645/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408593+02:00", "action": 59, "target": "<primary>تثبيت</primary><secondary>التثبيت المؤتمت</secondary>", "old": "", "details": { "state": 10, "source": "<primary>filesystem</primary><secondary>redundancy</secondary>", "old_state": -1 }, "id": 34028629, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34028629/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696645/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408554+02:00", "action": 30, "target": "<primary>filesystem</primary><secondary>redundancy</secondary>", "old": "<primary>installation</primary><secondary>automated installation</secondary>", "details": {}, "id": 34028628, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34028628/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696643/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408512+02:00", "action": 59, "target": "<primary>تثبيت</primary><secondary>التثبيت المؤتمت</secondary>", "old": "", "details": { "state": 10, "source": "<primary>volume</primary><secondary>raid volume</secondary>", "old_state": -1 }, "id": 34028627, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34028627/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696643/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408472+02:00", "action": 30, "target": "<primary>volume</primary><secondary>raid volume</secondary>", "old": "<primary>installation</primary><secondary>automated installation</secondary>", "details": {}, "id": 34028626, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34028626/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696641/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408429+02:00", "action": 59, "target": "<primary>تثبيت</primary><secondary>التثبيت المؤتمت</secondary>", "old": "", "details": { "state": 10, "source": "<primary>volume</primary><secondary>logical volume</secondary>", "old_state": -1 }, "id": 34028625, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34028625/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696641/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408387+02:00", "action": 30, "target": "<primary>volume</primary><secondary>logical volume</secondary>", "old": "<primary>installation</primary><secondary>automated installation</secondary>", "details": {}, "id": 34028624, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34028624/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696639/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408336+02:00", "action": 59, "target": "<primary>Logical Volume Manager</primary>", "old": "", "details": { "state": 10, "source": "<primary>Logical Volume Manager</primary><see>LVM</see>", "old_state": -1 }, "id": 34028623, "action_name": "String updated in the repository", "url": "https://hosted.weblate.org/api/changes/34028623/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/82696639/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2022-09-07T09:41:07.408248+02:00", "action": 30, "target": "<primary>Logical Volume Manager</primary><see>LVM</see>", "old": "<primary>Logical Volume Manager</primary>", "details": {}, "id": 34028622, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/34028622/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2022-07-20T17:43:26.381416+02:00", "action": 0, "target": "", "old": "", "details": { "reason": "check forced", "filename": "ar-MA/12_advanced-administration.po" }, "id": 29885315, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/29885315/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2021-12-26T23:06:15.966948+01:00", "action": 0, "target": "", "old": "", "details": { "reason": "check forced", "filename": "ar-MA/12_advanced-administration.po" }, "id": 15504905, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/15504905/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2021-12-25T15:37:10.965568+01:00", "action": 0, "target": "", "old": "", "details": { "reason": "check forced", "filename": "ar-MA/12_advanced-administration.po" }, "id": 15492502, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/15492502/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2021-10-03T09:23:18.006446+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 13040191, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/13040191/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2021-08-01T16:33:06.566136+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 12004980, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/12004980/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2021-06-27T13:02:00.686467+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 11253642, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/11253642/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/pere/?format=api", "author": "https://hosted.weblate.org/api/users/pere/?format=api", "timestamp": "2021-06-27T12:55:02.544364+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 11252679, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/11252679/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827066/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/jad/?format=api", "author": "https://hosted.weblate.org/api/users/jad/?format=api", "timestamp": "2021-01-13T06:27:44.826414+01:00", "action": 2, "target": "تستخدم تقنيتا LVM و RAID لعزل الحيز التخزيني المتاح لنظام الملفات عن الحيز التخزيني الفيزيائي (الأقراص الصلبة الفعلية أو الأقسام partitions)؛ تحمي تقنية RAID البيانات من خلال التخزين الفائض، بينما تجعل تقنية LVM إدارة البيانات أكثر مرونة واستقلالاً عن السَّعَة الحقيقية للأقراص التي تحميل تلك البيانات. في الحالتين، يعتمد النظام على أجهزة تخزينية جديدة، يمكن استخدامها لإنشاء نظم ملفات أو مساحات الإبدال Swap، دون أن ترتبط بقرص فيزيائي واحد. إن جذور التقنيتين مختلفة كثيرًا، لكن وظائفهما متشابهة نوعًا ما، ولهذا غالبًا ما تذكران معًا.", "old": "تستخدم تقنيتا LVM و RAID لعزل الحيز التخزيني المتاح لنظام الملفات عن الحيز التخزيني الفيزيائي (الأقراص الصلبة الفعلية أو الأقسام partitions)؛ تحمي تقنية RAID البيانات من خلال التخزين الفائض، بينما تجعل تقنية LVM إدارة البيانات أكثر مرونة واستقلالاً عن السعة الحقيقية للأقراص التي تحميل تلك البيانات. في الحالتين، يعتمد النظام على أجهزة تخزينية جديدة، يمكن استخدامها لإنشاء نظم ملفات أو مساحات swap، دون أن ترتبط بقرص فيزيائي واحد. إن جذور التقنيتين مختلفة كثيرًا، لكن وظائفهما متشابهة نوعًا ما، ولهذا غالبًا ما تذكران معًا.", "details": {}, "id": 8953029, "action_name": "Translation changed", "url": "https://hosted.weblate.org/api/changes/8953029/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827066/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/jad/?format=api", "author": "https://hosted.weblate.org/api/users/jad/?format=api", "timestamp": "2021-01-13T06:27:44.820287+01:00", "action": 45, "target": "", "old": "", "details": {}, "id": 8953028, "action_name": "Contributor joined", "url": "https://hosted.weblate.org/api/changes/8953028/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/rhertzog/?format=api", "author": "https://hosted.weblate.org/api/users/rhertzog/?format=api", "timestamp": "2020-08-28T10:55:09.421918+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 7293411, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/7293411/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/19836349/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-08-28T10:55:09.091218+02:00", "action": 30, "target": "Before turning these virtual machines on, we need to define how they'll be accessed. They can of course be considered as isolated machines, only accessed through their system console, but this rarely matches the usage pattern. Most of the time, a domU will be considered as a remote server, and accessed only through a network. However, it would be quite inconvenient to add a network card for each domU; which is why Xen allows creating virtual interfaces that each domain can see and use in a standard way. Note that these cards, even though they're virtual, will only be useful once connected to a network, even a virtual one. Xen has several network models for that:", "old": "Before turning these virtual machines on, we need to define how they'll be accessed. They can of course be considered as isolated machines, only accessed through their system console, but this rarely matches the usage pattern. Most of the time, a domU will be considered as a remote server, and accessed only through a network. However, it would be quite inconvenient to add a network card for each domU; which is why Xen allows creating virtual interfaces, that each domain can see and use in a standard way. Note that these cards, even though they're virtual, will only be useful once connected to a network, even a virtual one. Xen has several network models for that:", "details": {}, "id": 7293410, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/7293410/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/19836345/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-08-28T10:55:08.852364+02:00", "action": 30, "target": "Let's spend some time on terms. The hypervisor is the lowest layer, which runs directly on the hardware, even below the kernel. This hypervisor can split the rest of the software across several <emphasis>domains</emphasis>, which can be seen as so many virtual machines. One of these domains (the first one that gets started) is known as <emphasis>dom0</emphasis>, and has a special role, since only this domain can control the hypervisor and the execution of other domains. These other domains are known as <emphasis>domU</emphasis>. In other words, and from a user point of view, the <emphasis>dom0</emphasis> matches the “host” of other virtualization systems, while a <emphasis>domU</emphasis> can be seen as a “guest”.", "old": "Let's spend some time on terms. The hypervisor is the lowest layer, that runs directly on the hardware, even below the kernel. This hypervisor can split the rest of the software across several <emphasis>domains</emphasis>, which can be seen as so many virtual machines. One of these domains (the first one that gets started) is known as <emphasis>dom0</emphasis>, and has a special role, since only this domain can control the hypervisor and the execution of other domains. These other domains are known as <emphasis>domU</emphasis>. In other words, and from a user point of view, the <emphasis>dom0</emphasis> matches the “host” of other virtualization systems, while a <emphasis>domU</emphasis> can be seen as a “guest”.", "details": {}, "id": 7293406, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/7293406/?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/ar_MA/?format=api", "user": "https://hosted.weblate.org/api/users/rhertzog/?format=api", "author": "https://hosted.weblate.org/api/users/rhertzog/?format=api", "timestamp": "2020-06-19T11:50:53.909320+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 6473068, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/6473068/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:31.892862+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 6194813, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/6194813/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827250/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:29.601765+02:00", "action": 30, "target": "This configuration file describes two monitored hosts. The first one is the web server, and the checks are made on the HTTP (80) and secure-HTTP (443) ports. Nagios also checks that an SMTP server runs on port 25. The second host is the FTP server, and the check includes making sure that a reply comes within 20 seconds. Beyond this delay, a <emphasis>warning</emphasis> is emitted; beyond 30 seconds, the alert is deemed critical. The Nagios web interface also shows that the SSH service is monitored: this comes from the hosts belonging to the <literal>ssh-servers</literal> hostgroup. The matching standard service is defined in <filename>/etc/nagios4/conf.d/services_nagios2.cfg</filename>.", "old": "This configuration file describes two monitored hosts. The first one is the web server, and the checks are made on the HTTP (80) and secure-HTTP (443) ports. Nagios also checks that an SMTP server runs on port 25. The second host is the FTP server, and the check includes making sure that a reply comes within 20 seconds. Beyond this delay, a <emphasis>warning</emphasis> is emitted; beyond 30 seconds, the alert is deemed critical. The Nagios web interface also shows that the SSH service is monitored: this comes from the hosts belonging to the <literal>ssh-servers</literal> hostgroup. The matching standard service is defined in <filename>/etc/nagios3/conf.d/services_nagios2.cfg</filename>.", "details": {}, "id": 6194810, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194810/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827248/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:29.503932+02:00", "action": 30, "target": "<filename>/etc/nagios4/conf.d/falcot.cfg</filename> file", "old": "<filename>/etc/nagios3/conf.d/falcot.cfg</filename> file", "details": {}, "id": 6194808, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194808/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827246/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:29.413403+02:00", "action": 30, "target": "An inheritance system allows easy sharing of a set of properties across many objects without duplicating information. Moreover, the initial configuration includes a number of standard objects; in many cases, defining new hosts, services and contacts is a simple matter of deriving from the provided generic objects. The files in <filename>/etc/nagios4/conf.d/</filename> are a good source of information on how they work.", "old": "An inheritance system allows easy sharing of a set of properties across many objects without duplicating information. Moreover, the initial configuration includes a number of standard objects; in many cases, defining new hosts, services and contacts is a simple matter of deriving from the provided generic objects. The files in <filename>/etc/nagios3/conf.d/</filename> are a good source of information on how they work.", "details": {}, "id": 6194806, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194806/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827244/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:29.089485+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": 6194804, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194804/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827242/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:29.029537+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": 6194802, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194802/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827240/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:28.969102+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": 6194800, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194800/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827238/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:28.915317+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": 6194798, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194798/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827230/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:28.435244+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": 6194793, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194793/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827226/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:28.247292+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": 6194789, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194789/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827216/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:26.720052+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": 6194779, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194779/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827208/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:24.921731+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": 6194771, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194771/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827206/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:24.750762+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": 6194769, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194769/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827204/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:24.506098+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": 6194767, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194767/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827202/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:24.414526+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": 6194765, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194765/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827200/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:24.357305+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": 6194763, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194763/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827196/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:24.131075+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": 6194759, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194759/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827194/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:23.821077+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": 6194757, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194757/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827186/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:23.110226+02:00", "action": 30, "target": "lxc.uts.name = testlxc", "old": "lxc.utsname = testlxc", "details": {}, "id": 6194750, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194750/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827182/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:22.932610+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": 6194746, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194746/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827178/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:22.432919+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": 6194742, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194742/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827174/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:22.201011+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": 6194738, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194738/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827172/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:21.868420+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": 6194736, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194736/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827170/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:21.758495+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": 6194734, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194734/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827166/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:21.397694+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": 6194730, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194730/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827162/?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/ar_MA/?format=api", "user": null, "author": null, "timestamp": "2020-05-17T18:33:21.155307+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": 6194726, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194726/?format=api" } ] }