Translation status

513 Strings 100% Translate
19,814 Words 100%

Other components

Component Translated Untranslated Untranslated words Checks Suggestions Comments
00a_preface This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
04_installation This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0 2
70_conclusion This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
Revision_History This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
Author_Group This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
Book_Info This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
03_existing-setup This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
07_solving-problems This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
00b_foreword This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0
99_website This component is linked to the Debian Handbook/12_advanced-administration repository. Fix this component to clear its alerts. GPL-2.0

Translation Information

Project website debian-handbook.info
Mailing list for translators debian-handbook-translators@lists.alioth.debian.org
Instructions for translators

https://debian-handbook.info/contribute/

Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license GNU General Public License v2.0 or later
Source code repository https://salsa.debian.org/hertzog/debian-handbook.git
Repository branch buster/master
Last remote commit pt-BR: Translated using Weblate. 5d9e19d7
User avatar pere authored 4 weeks ago
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
Filemask */12_advanced-administration.po
Translation file es-ES/12_advanced-administration.po
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:
Antes de encender estas máquinas virtuales, necesitamos definir cómo accederemos a ellas. Por supuesto, podemos considerarlas máquinas aisladas a las que sólo podemos acceder a través de su consola de sistema, pero rara vez esto coincide con el patrón de uso. La mayoría de las veces, consideraremos un domU como un servidor remoto al que sólo podemos acceder a través de la red. Sin embargo, sería un gran inconveniente agregar una tarjeta de red para cada domU; es por esto que Xen permite crear interfaces virtuales que cada dominio puede ver y utilizar de la forma estándar. Sepa que estas tarjetas, aunque sean virtuales, sólo serán útiles cuando estén conectadas a una red, inclusive una virtual. Xen tiene varios modelos de red para esto:
2 months ago
<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=buster --role=udev</userinput>
<computeroutput>
[...]
General Information
--------------------
Hostname : testxen
Distribution : buster
Mirror : http://deb.debian.org/debian
Partitions : swap 512M (swap)
/ 2G (ext4)
Image type : sparse
Memory size : 256M
Kernel path : /boot/vmlinuz-4.19.0-5-amd64
Initrd path : /boot/initrd.img-4.19.0-5-amd64
[...]
Logfile produced at:
/var/log/xen-tools/testxen.log

Installation Summary
---------------------
Hostname : testxen
Distribution : buster
MAC Address : 00:16:3E:0C:74:2F
IP Address(es) : dynamic
SSH Fingerprint : SHA256:PuAGX4/4S07Xzh1u0Cl2tL04EL5udf9ajvvbufBrfvU (DSA)
SSH Fingerprint : SHA256:ajFTX54eakzolyzmZku/ihq/BK6KYsz5MewJ98BM5co (ECDSA)
SSH Fingerprint : SHA256:/sFov86b+rD/bRSJoHKbiMqzGFiwgZulEwpzsiw6aSc (ED25519)
SSH Fingerprint : SHA256:/NJg/CcoVj+OLE/cL3yyJINStnla7YkHKe3/xEdVGqc (RSA)
Root Password : EwmQMHtywY9zsRBpqQuxZTb
</computeroutput>
<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=buster --role=udev</userinput>
<computeroutput>
[...]
General Information
--------------------
Hostname : testxen
Distribution : buster
Mirror : http://deb.debian.org/debian
Partitions : swap 512M (swap)
/ 2G (ext4)
Image type : sparse
Memory size : 256M
Kernel path : /boot/vmlinuz-4.19.0-5-amd64
Initrd path : /boot/initrd.img-4.19.0-5-amd64
[...]
Logfile produced at:
/var/log/xen-tools/testxen.log

Installation Summary
---------------------
Hostname : testxen
Distribution : buster
MAC Address : 00:16:3E:0C:74:2F
IP Address(es) : dynamic
SSH Fingerprint : SHA256:PuAGX4/4S07Xzh1u0Cl2tL04EL5udf9ajvvbufBrfvU (DSA)
SSH Fingerprint : SHA256:ajFTX54eakzolyzmZku/ihq/BK6KYsz5MewJ98BM5co (ECDSA)
SSH Fingerprint : SHA256:/sFov86b+rD/bRSJoHKbiMqzGFiwgZulEwpzsiw6aSc (ED25519)
SSH Fingerprint : SHA256:/NJg/CcoVj+OLE/cL3yyJINStnla7YkHKe3/xEdVGqc (RSA)
Root Password : EwmQMHtywY9zsRBpqQuxZTb
</computeroutput>
2 months ago
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”.
Pasemos un poco de tiempo en los términos. El hypervisor es la capa más baja que ejecuta directamente en el hardware, inclusive debajo del núcleo. Este hypervisor puede dividir el resto del software entre varios <emphasis>dominios</emphasis> («domains»), pueden interpretarse como máquinas virtuales. Se conoce a uno de estos dominios (el primero en iniciar) como <emphasis>dom0</emphasis> y tiene un rol especial ya que sólo este dominio puede controlar al hypervisor y la ejecución de otros dominios. Se conocen a los otros dominios como <emphasis>domU</emphasis>. En otras palabras, desde el punto de vista del usuario, el <emphasis>dom0</emphasis> es el «anfitrión» de los demás sistemas de virtualización, mientras que los <emphasis>domU</emphasis> son sus «invitados».
2 months ago
New strings to translate 3 months ago
Resource update 3 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationSpanish

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:
3 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationSpanish

<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=buster --role=udev</userinput>
<computeroutput>
[...]
General Information
--------------------
Hostname : testxen
Distribution : buster
Mirror : http://deb.debian.org/debian
Partitions : swap 512M (swap)
/ 2G (ext4)
Image type : sparse
Memory size : 256M
Kernel path : /boot/vmlinuz-4.19.0-5-amd64
Initrd path : /boot/initrd.img-4.19.0-5-amd64
[...]
Logfile produced at:
/var/log/xen-tools/testxen.log

Installation Summary
---------------------
Hostname : testxen
Distribution : buster
MAC Address : 00:16:3E:0C:74:2F
IP Address(es) : dynamic
SSH Fingerprint : SHA256:PuAGX4/4S07Xzh1u0Cl2tL04EL5udf9ajvvbufBrfvU (DSA)
SSH Fingerprint : SHA256:ajFTX54eakzolyzmZku/ihq/BK6KYsz5MewJ98BM5co (ECDSA)
SSH Fingerprint : SHA256:/sFov86b+rD/bRSJoHKbiMqzGFiwgZulEwpzsiw6aSc (ED25519)
SSH Fingerprint : SHA256:/NJg/CcoVj+OLE/cL3yyJINStnla7YkHKe3/xEdVGqc (RSA)
Root Password : EwmQMHtywY9zsRBpqQuxZTb
</computeroutput>
3 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationSpanish

Let's spend some time on terms. The hypervisor is the lowest layer, thatwhich 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”.
3 months ago
<computeroutput># </computeroutput><userinput>df -h /srv/files/</userinput>
<computeroutput>Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_critical-lv_files 4.9G 4.2G 485M 90% /srv/files
# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>
<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_files vg_critical -wi-ao-- 5.00g
# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>
<computeroutput> VG #PV #LV #SN Attr VSize VFree
vg_critical 2 2 0 wz--n- 7.99g 1.99g
# </computeroutput><userinput>lvresize -L 6G vg_critical/lv_files</userinput>
<computeroutput> Size of logical volume vg_critical/lv_files changed from 5.00 GiB (1280 extents) to 6.00 GiB (1536 extents).
Logical volume vg_critical/lv_files successfully resized.
# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>
<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_files vg_critical -wi-ao---- 6.00g
# </computeroutput><userinput>resize2fs /dev/vg_critical/lv_files</userinput>
<computeroutput>resize2fs 1.44.5 (15-Dec-2018)
Filesystem at /dev/vg_critical/lv_files is mounted on /srv/files; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
The filesystem on /dev/vg_critical/lv_files is now 1572864 (4k) blocks long.

# </computeroutput><userinput>df -h /srv/files/</userinput>
<computeroutput>Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_critical-lv_files 5.9G 4.2G 1.5G 75% /srv/files</computeroutput>
<computeroutput># </computeroutput><userinput>df -h /srv/files/</userinput>
<computeroutput>Filesystem Size Used AvailS.ficheros Tamaño Usados Disp Useo% Mounted oado en
/dev/mapper/vg_critical-lv_files 4.9G 4.2G 485M 90% /srv/files
# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>
<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_files vg_critical -wi-ao-- 5.00g
# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>
<computeroutput> VG #PV #LV #SN Attr VSize VFree
vg_critical 2 2 0 wz--n- 7.99g 1.99g
# </computeroutput><userinput>lvresize -L 6G vg_critical/lv_files</userinput>
<computeroutput> Size of logical volume vg_critical/lv_files changed from 5.00 GiB (1280 extents) to 6.00 GiB (1536 extents).
Logical volume vg_critical/lv_files successfully resized.
# </computeroutput><userinput>lvdisplay -C vg_critical/lv_files</userinput>
<computeroutput> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lv_files vg_critical -wi-ao---- 6.00g
# </computeroutput><userinput>resize2fs /dev/vg_critical/lv_files</userinput>
<computeroutput>resize2fs 1.44.5 (15-Dec-2018)
Filesystem at /dev/vg_critical/lv_files is mounted on /srv/files; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
The filesystem on /dev/vg_critical/lv_files is now 1572864 (4k) blocks long.

# </computeroutput><userinput>df -h /srv/files/</userinput>
<computeroutput>Filesystem Size Used AvailS.ficheros Tamaño Usados Disp Useo% Mounted oado en
/dev/mapper/vg_critical-lv_files 5.9G 4.2G 1.5G 75% /srv/files</computeroutput>
3 months ago
<computeroutput># </computeroutput><userinput>df -h /srv/base/</userinput>
<computeroutput>Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_critical-lv_base 976M 882M 28M 97% /srv/base
# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>
<computeroutput> VG #PV #LV #SN Attr VSize VFree
vg_critical 2 2 0 wz--n- 7.99g 1016.00m</computeroutput>
<computeroutput># </computeroutput><userinput>df -h /srv/base/</userinput>
<computeroutput>Filesystem Size Used AvailS.ficheros Tamaño Usados Disp Useo% Mounted oado en
/dev/mapper/vg_critical-lv_base 976M 882M 28M 97% /srv/base
# </computeroutput><userinput>vgdisplay -C vg_critical</userinput>
<computeroutput> VG #PV #LV #SN Attr VSize VFree
vg_critical 2 2 0 wz--n- 7.99g 1016.00m</computeroutput>
3 months ago
Browse all translation changes

Statistics

Percent Strings Words Chars
Total 513 19,814 146,962
Translated 100% 513 19,814 146,962
Needs editing 0% 0 0 0
Failing checks 0% 0 0 0

Last activity

Last change Aug. 28, 2020, 3:09 p.m.
Last author Jorge Maldonado Ventura

Daily activity

Daily activity

Weekly activity

Weekly activity