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 a month ago
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
Filemask */12_advanced-administration.po
Translation file fr-FR/12_advanced-administration.po
New strings to translate 3 months ago
Resource update 3 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationFrench

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-administrationFrench

<computeroutput># </computeroutput><userinput>xen-create-image --hostname testxen --dhcp --dir /srv/testxen --size=2G --dist=jessiebuster --role=udev</userinput>
<computeroutput>
[...]
General Information
--------------------
Hostname : testxen
Distribution : jessiebuster
Mirror : http://ftpdeb.debian.org/debian/
Partitions : swap 5128MbM (swap)
/ 2G (ext34)
Image type : sparse
Memory size : 128Mb256M
Kernel path : /boot/vmlinuz-34.169.0-45-amd64
Initrd path : /boot/initrd.img-34.169.0-45-amd64
[...]
Logfile produced at:
/var/log/xen-tools/testxen.log

Installation Summary
---------------------
Hostname : testxen
Distribution : jessiebuster
MAC Address : 00:16:3E:8E:67:5C0C:74:2F
IP- Address(es) : dynamic
RSASSH Fingerprint : 0a:6e:71:98:95:46:64:ec:80:37:63:18:73:04:dd:2b
Root Password : adaX2jyRHNuWm8BDJS7PcEJ
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-administrationFrench

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
New strings to translate 5 months ago
Resource update 5 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationFrench

<computeroutput># </computeroutput><userinput>virt-install --connect qemu:///system <co id="virtinst.connect"></co>
--virt-type kvm <co id="virtinst.type"></co>
--name testkvm <co id="virtinst.name"></co>
--rammemory 1024 <co id="virtinst.ram"></co>
--disk /srv/kvm/testkvm.qcow,format=qcow2,size=10 <co id="virtinst.disk"></co>
--cdrom /srv/isos/debian-8.110.2.0-amd64-netinst.iso <co id="virtinst.cdrom"></co>
--network bridge=virbr0 <co id="virtinst.network"></co>
--vnc graphics vnc <co id="virtinst.vnc"></co>
--os-type linux <co id="virtinst.os"></co>
--os-variant debianwheezy10
</userinput><computeroutput>
Starting install...
Allocating 'testkvm.qcow' | 10 GB 00:00
Creating domain... | 0 B 00:00
Guest installation complete... restarting guest.
</computeroutput>
5 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationFrench

<computeroutput># </computeroutput><userinput>vgdisplay</userinput>
<computeroutput> No volume groups found
#
</computeroutput><userinput>vgcreate vg_critical /dev/sdb2 /dev/sdf1</userinput>
<computeroutput> Volume group "vg_critical" successfully created
# </computeroutput><userinput>vgdisplay</userinput>
<computeroutput> --- Volume group ---
VG Name vg_critical
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 1
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 0
Open LV 0
Max PV 0
Cur PV 2
Act PV 2
VG Size 8.07.99 GiB
PE Size 4.00 MiB
Total PE 207146
Alloc PE / Size 0 / 0
Free PE / Size 207146 / 8.07.99 GiB
VG UUID bpq7zO-PzPD-R7HW-V8eN-c10c-S32h-f6rKqpwAbBjx-d82B-q7St-0KFf-z40h-w5Mh-uAXkNZ

# </computeroutput><userinput>vgcreate vg_normal /dev/sdc3 /dev/sdd /dev/sdf2</userinput>
<computeroutput> Volume group "vg_normal" successfully created
# </computeroutput><userinput>vgdisplay -C</userinput>
<computeroutput> VG #PV #LV #SN Attr VSize VFree
vg_critical 2 0 0 wz--n- 8.09g 8.0 7.99g 7.99g
vg_normal 3 0 0 wz--n- 12.30g 12.30&lt;11.99g &lt;11.99g
</computeroutput>
5 months ago
User avatar None

Source string changed

Debian Handbook / 12_advanced-administrationFrench

<computeroutput># </computeroutput><userinput>pvdisplay</userinput>
<computeroutput># </computeroutput><userinput>pvcreate /dev/sdb2</userinput>
<computeroutput> Physical volume "/dev/sdb2" successfully created.
# </computeroutput><userinput>pvdisplay</userinput>
<computeroutput> "/dev/sdb2" is a new physical volume of "4.00 GiB"
--- NEW Physical volume ---
PV Name /dev/sdb2
VG Name
PV Size 4.00 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID 0zuiQQ-j1Oe-P593-4tsN-9FGy-TY0d-Quz31Iz4Clgk-T5a4-C27o-1P0E-lIAF-OeUM-e7EMwq

# </computeroutput><userinput>for i in sdc3 sdd sdf1 sdf2 ; do pvcreate /dev/$i ; done</userinput>
<computeroutput> Physical volume "/dev/sdc3" successfully created.
Physical volume "/dev/sdd" successfully created.
Physical volume "/dev/sdf1" successfully created.
Physical volume "/dev/sdf2" successfully created.
# </computeroutput><userinput>pvdisplay -C</userinput>
<computeroutput>
PV VG Fmt Attr PSize PFree
/dev/sdb2 lvm2 --- 4.00g 4.00g
/dev/sdc3 lvm2 --- 3.09g0g 3.090g
/dev/sdd lvm2 --- 4.00g 4.00g
/dev/sdf1 lvm2 --- 4.100g 4.100g
/dev/sdf2 lvm2 --- 5.22g 5.22&lt;5.00g &lt;5.00g
</computeroutput>
5 months ago
Browse all translation changes

Statistics

Percent Strings Words Chars
Total 513 19,814 146,962
Translated 81% 417 13,459 93,868
Needs editing 16% 87 6,134 51,222
Failing checks 25% 133 7,635 61,997

Last activity

Last change April 9, 2018, 10:12 a.m.
Last author Galina Anikina

Daily activity

Daily activity

Weekly activity

Weekly activity