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=13
{ "count": 663, "next": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/ar_MA/changes/?format=api&page=14", "previous": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/ar_MA/changes/?format=api&page=12", "results": [ { "unit": "https://hosted.weblate.org/api/units/16827148/?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:18.170443+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": 6194712, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194712/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827146/?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:18.048487+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": 6194710, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194710/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827144/?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:17.976738+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": 6194708, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194708/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827134/?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:17.639815+02:00", "action": 30, "target": "<emphasis>HARDWARE</emphasis> Virtualization support", "old": "<emphasis>GOING FURTHER</emphasis> Mass virtualization", "details": {}, "id": 6194702, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194702/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827126/?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:17.056160+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": 6194694, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194694/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827124/?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:16.975967+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": 6194692, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194692/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827122/?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:16.540653+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": 6194690, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194690/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827116/?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:16.280863+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": 6194684, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194684/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827110/?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:15.878236+02:00", "action": 30, "target": "<emphasis>NOTE</emphasis> Auto-detecting LVM volumes", "old": "<emphasis>NOTE</emphasis> Autodetecting LVM volumes", "details": {}, "id": 6194678, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194678/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827108/?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:15.761496+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": 6194676, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194676/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827104/?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:15.535702+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": 6194672, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194672/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827098/?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:14.939886+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": 6194666, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194666/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827084/?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:13.480103+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": 6194652, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194652/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827080/?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:12.994864+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": 6194648, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194648/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827076/?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:12.478469+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": 6194645, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194645/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827074/?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:12.435681+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": 6194643, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194643/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827072/?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:12.396027+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": 6194641, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194641/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/16827070/?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:12.334830+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": 6194639, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194639/?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": null, "author": null, "timestamp": "2020-05-17T18:33:12.223358+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": 6194635, "action_name": "Source string changed", "url": "https://hosted.weblate.org/api/changes/6194635/?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": "2018-04-18T11:50:34+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 2697247, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/2697247/?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": "2018-04-09T11:47:26+02:00", "action": 17, "target": "", "old": "", "details": {}, "id": 2657096, "action_name": "Changes committed", "url": "https://hosted.weblate.org/api/changes/2657096/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/1102896/?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/Mari3/?format=api", "author": "https://hosted.weblate.org/api/users/Mari3/?format=api", "timestamp": "2018-04-09T10:12:25+02:00", "action": 32, "target": "<primary><command>debconf</command></primary>", "old": "<primary><command>debconf</command></primary>", "details": {}, "id": 2653175, "action_name": "Bulk status changed", "url": "https://hosted.weblate.org/api/changes/2653175/?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": "2016-05-19T23:05:01+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 996262, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/996262/?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": "2016-03-25T10:50:22+01:00", "action": 0, "target": "", "old": "", "details": {}, "id": 822275, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/822275/?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": "2016-03-02T12:10:01+01:00", "action": 0, "target": "", "old": "", "details": {}, "id": 778817, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/778817/?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": "2015-10-19T15:13:17+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 545510, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/545510/?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": "2015-10-01T18:13:15+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 511507, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/511507/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2539505/?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": "2015-10-01T18:13:14+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 511503, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/511503/?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": "2015-09-09T18:59:02+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 458014, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/458014/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2454882/?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": "2015-09-09T18:59:01+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 458005, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/458005/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2454879/?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": "2015-09-09T18:59:00+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 458002, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/458002/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2454875/?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": "2015-09-09T18:59:00+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 457998, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/457998/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2454874/?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": "2015-09-09T18:59:00+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 457997, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/457997/?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": "2015-08-31T09:36:15+02:00", "action": 0, "target": "", "old": "", "details": {}, "id": 433973, "action_name": "Resource updated", "url": "https://hosted.weblate.org/api/changes/433973/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371132/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433961, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433961/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371134/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433963, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433963/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371127/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433956, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433956/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371140/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433969, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433969/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371139/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433968, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433968/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371129/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433958, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433958/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371131/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433960, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433960/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371130/?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": "2015-08-31T09:36:13+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433959, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433959/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371119/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433948, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433948/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371109/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433938, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433938/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371107/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433936, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433936/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371106/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433935, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433935/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371120/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433949, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433949/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371121/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433950, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433950/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371123/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433952, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433952/?format=api" }, { "unit": "https://hosted.weblate.org/api/units/2371125/?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": "2015-08-31T09:36:12+02:00", "action": 13, "target": "", "old": "", "details": {}, "id": 433954, "action_name": "Source string added", "url": "https://hosted.weblate.org/api/changes/433954/?format=api" } ] }