diff options
Diffstat (limited to 'it/using-d-i/modules')
| -rw-r--r-- | it/using-d-i/modules/alpha/aboot-installer.xml | 5 | ||||
| -rw-r--r-- | it/using-d-i/modules/base-installer.xml | 33 | ||||
| -rw-r--r-- | it/using-d-i/modules/choose-mirror.xml | 11 | ||||
| -rw-r--r-- | it/using-d-i/modules/ia64/elilo-installer.xml | 11 | ||||
| -rw-r--r-- | it/using-d-i/modules/mdcfg.xml | 22 | ||||
| -rw-r--r-- | it/using-d-i/modules/partman-crypto.xml | 5 | ||||
| -rw-r--r-- | it/using-d-i/modules/partman-lvm.xml | 21 | ||||
| -rw-r--r-- | it/using-d-i/modules/x86/lilo-installer.xml | 7 |
8 files changed, 54 insertions, 61 deletions
diff --git a/it/using-d-i/modules/alpha/aboot-installer.xml b/it/using-d-i/modules/alpha/aboot-installer.xml index 02c781a1d..d72fe931b 100644 --- a/it/using-d-i/modules/alpha/aboot-installer.xml +++ b/it/using-d-i/modules/alpha/aboot-installer.xml @@ -1,5 +1,6 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 25496 --> +<!-- original version: 43573 --> + <sect3 arch="alpha"> <!-- <title>Install <command>aboot</command> on a Hard Disk</title> --> @@ -7,7 +8,7 @@ <para> <!-- -If you have booted from SRM, if you select this option, the installer +If you have booted from SRM and you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating diff --git a/it/using-d-i/modules/base-installer.xml b/it/using-d-i/modules/base-installer.xml index 0616dde09..7db644f79 100644 --- a/it/using-d-i/modules/base-installer.xml +++ b/it/using-d-i/modules/base-installer.xml @@ -1,23 +1,21 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 33720 --> +<!-- original version: 43573 --> + - <sect3 id="base-installer"> - <!-- <title>Base System Installation</title> --> - <title>Installazione del sistema di base</title> <para> <!-- -During the Base installation, package unpacking and setup messages are -redirected to <userinput>tty4</userinput>. You can access this -terminal by pressing +During installation of the base system, package unpacking and setup +messages are redirected to <userinput>tty4</userinput>. +You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>. --> -Durante l'installazione di base i messaggi relativi all'estrazione e alla -configurazione dei pacchetti sono rediretti su <userinput>tty4</userinput>. -È possibile accedere a questo terminale premendo +Durante l'installazione del sistema di base i messaggi relativi +all'estrazione e alla configurazione dei pacchetti sono rediretti su +<userinput>tty4</userinput>. È possibile accedere a questo terminale premendo <keycombo><keycap>Alt</keycap><keycap>F4</keycap></keycombo>; per tornare al terminale con il processo d'installazione principale premere <keycombo><keycap>Alt</keycap><keycap>F1</keycap></keycombo>. @@ -25,14 +23,16 @@ al terminale con il processo d'installazione principale premere </para><para> <!-- -The unpack/setup messages generated by the base installation are saved in -<filename>/var/log/syslog</filename> when the installation is -performed over a serial console. +The unpack/setup messages generated during this phase are also saved in +<filename>/var/log/syslog</filename>. You can check them there if the +installation is performed over a serial console. --> -Se l'installazione avviene tramite una console seriale i messaggi relativi -all'estrazione e alla configurazione dei pacchetti sono salvati in -<filename>/var/log/syslog</filename>. +I messaggi relativi all'estrazione e alla configurazione dei pacchetti +generati durante questa fase sono salvati anche in +<filename>/var/log/syslog</filename>. Quando l'installazione avviene +tramite una console seriale questo è l'unico posto in cui è possibile +vederli. </para><para> @@ -49,4 +49,3 @@ meglio si adatta al proprio hardware. Nelle modalità con priorità più bassa è possibile scegliere uno dei kernel fra quelli disponibili. </para> - </sect3> diff --git a/it/using-d-i/modules/choose-mirror.xml b/it/using-d-i/modules/choose-mirror.xml index 2f09b3633..2b96ea2cf 100644 --- a/it/using-d-i/modules/choose-mirror.xml +++ b/it/using-d-i/modules/choose-mirror.xml @@ -1,5 +1,6 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 16990 --> +<!-- original version: 43658 --> + <!-- This comment is a workaround for translation-stats script: @@ -7,15 +8,21 @@ this file is translated now! --> <!-- +Hmm. This really does need documenting :-/ + - Component is only selected and executed if the installer needs to load installer components or the base system from the network (either local or the internet). - This means you first have to configure a network interface. +- Mirror selection is delayed until apt-setup for CD-based installs (except + businesscard) - A list of countries is displayed with the default based on the country you selected earlier. -- Note that not all mirrors are equal (see http://www.nl.debian.org/mirror/list) - Selection of a local mirror (at top of the list: manual selection). - After selecting a country, a list of mirrors in the country will be shown. + (not for ftp) +- Forcing to ftp can be done using "protocol=ftp" +- Note that not all mirrors are equal (see http://www.nl.debian.org/mirror/list) - The selected mirror will be tested. - How to handle problems with mirrors. diff --git a/it/using-d-i/modules/ia64/elilo-installer.xml b/it/using-d-i/modules/ia64/elilo-installer.xml index ec10b57b2..463dfb801 100644 --- a/it/using-d-i/modules/ia64/elilo-installer.xml +++ b/it/using-d-i/modules/ia64/elilo-installer.xml @@ -1,5 +1,6 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24321 --> +<!-- original version: 43573 --> + <sect3 arch="ia64"> <!-- <title>Install the <command>ELILO</command> Boot Loader @@ -18,10 +19,10 @@ disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and -copies file into it. +copies files into it. The <filename>elilo.efi</filename> program is copied into the EFI -partition and then run by the <quote>EFI Boot Manager</quote> to actually -do the work of loading and starting the Linux kernel. +partition and then run by the <quote>EFI Boot Manager</quote> to +do the actual work of loading and starting the Linux kernel. --> Il boot loader per &arch-title; è <quote>elilo</quote>. È modellato sul @@ -71,7 +72,7 @@ filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. -Remember, the <command>elilo</command> may format the partition during +Remember, <command>elilo</command> may format the partition during the installation, erasing any previous contents! --> diff --git a/it/using-d-i/modules/mdcfg.xml b/it/using-d-i/modules/mdcfg.xml index 12cc69b16..df8ce78f1 100644 --- a/it/using-d-i/modules/mdcfg.xml +++ b/it/using-d-i/modules/mdcfg.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 42251 --> +<!-- original version: 43573 --> <sect3 id="mdcfg"> @@ -59,7 +59,7 @@ point, ecc.). </para><para> <!-- -The benefit you gain depends on a type of a MD device you are +What benefit you gain depends on a type of a MD device you are creating. Currently supported are: --> @@ -75,7 +75,7 @@ che si intende creare. Attualmente quelli supportati sono: Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write -operations, but when one of the disks fails, you will loose +operations, but when one of the disks fails, you will lose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). @@ -105,12 +105,12 @@ Un uso tipico di RAID0 è una partizione per l'editing video. <!-- Is suitable for setups where reliability is the first concern. It -consists of several (usually two) equally sized partitions where every +consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the -smallest partition in the RAID). Third, file reads are load balanced among +smallest partition in the RAID). Third, file-reads are load balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. --> @@ -143,8 +143,8 @@ rottura di uno degli altri dischi lo rimpiazza. <!-- Is a good compromise between speed, reliability and data redundancy. -RAID5 splits all incomming data into stripes and distributes them -equally on all but one disks (similar to RAID0). Unlike RAID0, RAID5 +RAID5 splits all incoming data into stripes and distributes them +equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity @@ -171,9 +171,9 @@ caso di rottura di un disco rimpiazza il disco rotto. </para><para> <!-- -As you can see, RAID5 has similar degree of reliability like RAID1 -while achieving less redundancy. On the other hand it might be a bit -slower on write operation than RAID0 due to computation of parity +As you can see, RAID5 has a similar degree of reliability to RAID1 +while achieving less redundancy. On the other hand, it might be a bit +slower on write operations than RAID0 due to computation of parity information. --> @@ -253,7 +253,7 @@ Riassumendo: </para><para> <!-- -If you want to know the whole truth about Software RAID, have a look +If you want to know more about Software RAID, have a look at <ulink url="&url-software-raid-howto;">Software RAID HOWTO</ulink>. --> diff --git a/it/using-d-i/modules/partman-crypto.xml b/it/using-d-i/modules/partman-crypto.xml index f3177308f..a6af8cc9f 100644 --- a/it/using-d-i/modules/partman-crypto.xml +++ b/it/using-d-i/modules/partman-crypto.xml @@ -1,5 +1,6 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 41817 --> +<!-- original version: 43576 --> + <sect3 id="partman-crypto"> <!-- <title>Configuring Encrypted Volumes</title> --> @@ -77,7 +78,7 @@ chiave. To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical -volume or a RAID volume). In the <guimenu>Partition setting</guimenu> +volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to diff --git a/it/using-d-i/modules/partman-lvm.xml b/it/using-d-i/modules/partman-lvm.xml index 16d9738e2..ed81f76fb 100644 --- a/it/using-d-i/modules/partman-lvm.xml +++ b/it/using-d-i/modules/partman-lvm.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 39531 --> +<!-- original version: 43577 --> <sect3 id="partman-lvm"> @@ -168,24 +168,7 @@ your logical volumes inside it. Usare le voci nel menu per creare un gruppo di volumi e poi per creare dei volumi logici al suo interno. -</para> -<note><para> - -<!-- -You can also use this menu to delete an existing LVM configuration from -your hard disk before choosing <quote>Guided partitioning using LVM</quote>. -Guided partitioning using LVM is not possible if there already are volume -groups defined, but by removing them you can get a clean start. ---> - -Questo menu può essere usato anche per cancellare la configurazione del LVM -esistente sul proprio disco fisso prima di scegliere il <quote>partizionamento -guidato con LVM</quote>. Infatti questa operazione è impossibile se esistono -dei gruppi di volumi già definiti, però rimuovendoli si ottiene una situazione -pulita. - -</para></note> -<para> +</para><para> <!-- After you return to the main <command>partman</command> screen, any created diff --git a/it/using-d-i/modules/x86/lilo-installer.xml b/it/using-d-i/modules/x86/lilo-installer.xml index 2dfdf8eb2..f2baed388 100644 --- a/it/using-d-i/modules/x86/lilo-installer.xml +++ b/it/using-d-i/modules/x86/lilo-installer.xml @@ -1,6 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- original version: 43573 --> + <sect3 arch="x86"> <!-- <title>Install the <command>LILO</command> Boot Loader on a Hard Disk</title> --> @@ -44,7 +45,7 @@ come GNU/Linux e GNU/Hurd dopo l'installazione. <para> <!-- -&d-i; presents you three choices where to install the +&d-i; offers you three choices where to install the <command>LILO</command> boot loader: --> @@ -114,8 +115,8 @@ some other way to get back into Debian! Se dopo l'esecuzione di questo passo non è più possibile avviare Windows 9x (o DOS), è necessario usare un dischetto d'avvio per Windows 9x (MS-DOS) ed eseguire il comando <userinput>fdisk /mbr</userinput> per reinstallare -il master boot record di MS-DOS; purtroppo questo vuol anche dire usare un -metodo alternativo per poter avviare Debian! +il master boot record di MS-DOS; purtroppo dopo questa operazione è necessario +usare un metodo alternativo per avviare Debian. </para> </sect3> |