summaryrefslogtreecommitdiff
path: root/ca/using-d-i
diff options
context:
space:
mode:
authorGuillem Jover <guillem@debian.org>2006-01-09 02:31:04 +0000
committerGuillem Jover <guillem@debian.org>2006-01-09 02:31:04 +0000
commita6cfdeb2abfb05749610a1db9aefb1f5110c9912 (patch)
treefe994fe5730426addd80af1bba497315984fdc13 /ca/using-d-i
parent18d7c0f80270fefd31a1fd729fb826305cd29b80 (diff)
downloadinstallation-guide-a6cfdeb2abfb05749610a1db9aefb1f5110c9912.zip
Merge change from sarge branch.
Add some missing files from etch english trunk.
Diffstat (limited to 'ca/using-d-i')
-rw-r--r--ca/using-d-i/modules/apt-setup.xml40
-rw-r--r--ca/using-d-i/modules/clock-setup.xml34
-rw-r--r--ca/using-d-i/modules/ia64/elilo-installer.xml134
-rw-r--r--ca/using-d-i/modules/mips/arcboot-installer.xml41
-rw-r--r--ca/using-d-i/modules/mipsel/delo-installer.xml51
-rw-r--r--ca/using-d-i/modules/network-console.xml128
-rw-r--r--ca/using-d-i/modules/pkgsel.xml161
-rw-r--r--ca/using-d-i/modules/sparc/silo-installer.xml33
-rw-r--r--ca/using-d-i/modules/tzsetup.xml16
-rw-r--r--ca/using-d-i/modules/user-setup.xml69
10 files changed, 508 insertions, 199 deletions
diff --git a/ca/using-d-i/modules/apt-setup.xml b/ca/using-d-i/modules/apt-setup.xml
new file mode 100644
index 000000000..c571e15f1
--- /dev/null
+++ b/ca/using-d-i/modules/apt-setup.xml
@@ -0,0 +1,40 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 33820 untranslated -->
+
+ <sect3 id="apt-setup">
+ <title>Configuring apt</title>
+
+<para>
+
+The main means that people use to install packages on their system is
+via a program called <command>apt-get</command>, from the
+<classname>apt</classname> package.<footnote>
+
+<para>
+
+Note that the actual program that installs packages is called
+<command>dpkg</command>. However, this program is more of a low-level
+tool. <command>apt-get</command> is a higher-level tool as it will
+invoke <command>dpkg</command> as appropriate and also because it knows
+to install other packages which are required for the package you're
+trying to install, as well as how to retrieve the package from your
+CD, the network, or wherever.
+
+</para>
+</footnote>
+Other front-ends for package management, like <command>aptitude</command>
+and <command>synaptic</command> are also in use and depend on
+<command>apt-get</command>. These front-ends are recommended for new users,
+since they integrate some additional features (package searching and status checks)
+in a nice user interface.
+
+</para><para>
+
+<command>apt</command> must be configured so that it knows where to retrieve
+packages from. The installer largely takes care of this automatically based on
+what it knows about your installation medium. The results of this configuration
+are written to the file <filename>/etc/apt/sources.list</filename>, and you can
+examine and edit it to your liking after the install is complete.
+
+</para>
+ </sect3>
diff --git a/ca/using-d-i/modules/clock-setup.xml b/ca/using-d-i/modules/clock-setup.xml
new file mode 100644
index 000000000..864b594a8
--- /dev/null
+++ b/ca/using-d-i/modules/clock-setup.xml
@@ -0,0 +1,34 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 33814 untranslated -->
+
+ <sect3 id="clock-setup">
+ <title>Configuring the Clock</title>
+
+<para>
+
+The installer might ask you if the computer's clock is set to UTC. Normally
+this question is avoided if possible and the installer tries to work out
+whether the clock is set to UTC based on things like what other operating
+systems are installed.
+
+</para><para>
+
+In expert mode you will always be able to choose
+whether or not the clock is set to UTC.
+<phrase arch="m68k;powerpc">Macintosh hardware clocks are normally
+set to local time. If you want to dual-boot, select local time instead of
+GMT.</phrase>
+<phrase arch="i386">Systems that (also) run Dos or Windows are normally
+set to local time. If you want to dual-boot, select local time
+instead of GMT.</phrase>
+
+</para><para>
+
+Note that the installer does not currently allow you to actually set the
+time in the computer's clock. You can set the clock to the current time
+after you have installed, if it is incorrect or if it was previously not
+set to UTC.
+
+</para>
+
+ </sect3>
diff --git a/ca/using-d-i/modules/ia64/elilo-installer.xml b/ca/using-d-i/modules/ia64/elilo-installer.xml
index 7953befe6..06a99d853 100644
--- a/ca/using-d-i/modules/ia64/elilo-installer.xml
+++ b/ca/using-d-i/modules/ia64/elilo-installer.xml
@@ -1,72 +1,70 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 24321 untranslated -->
+<!-- original version: 24321 -->
<sect3 arch="ia64">
- <title>Install the <command>ELILO</command> Boot Loader
- on a Hard Disk</title>
+ <title>Instal·lació del carregador <command>ELILO</command>
+ a un disc dur</title>
<para>
-The &architecture; boot loader is called <quote>elilo</quote>.
-It is modeled on the <quote>lilo</quote> boot loader for the
-x86 architecture and uses a similar configuration file.
-However, instead of writing an MBR or partition boot record to
-the disk, it copies the necessary files to a separate FAT formatted
-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.
-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.
+El carregador per a l'&architecture; s'anomena <quote>elilo</quote>.
+Està basat en el carregador <quote>lilo</quote>, de l'arquitectura x86,
+i fa servir un fitxer de configuració semblant. Tanmateix, en lloc
+d'escriure un MBR o un registre d'arrencada de partició al disc, copia
+els fitxers necessaris a una partició FAT separada i modifica el menú del
+<guimenuitem>gestor d'arrencada EFI</guimenuitem> del firmware perquè apunte
+als fitxers de la partició EFI. El carregador <command>elilo</command>
+té en realitat dues parts. L'ordre <filename>/usr/sbin/elilo</filename>
+gestiona la partició i hi copia els fitxers. El programa
+<filename>elilo.efi</filename> es copia a la partició EFI i després
+és executat pel <quote>gestor d'arrencada EFI</quote> a fi de dur a
+terme realment la feina de carregar i iniciar el nucli del Linux.
</para><para>
-The <quote>elilo</quote> configuration and installation is done as the
-last step of installing the packages of the base installation.
-&d-i; will present you with a list of potential disk partitions that it
-has found suitable for an EFI partition.
-Select the partition you set up earlier in the installation, typically
-a partition on the same disk that contains your
-<emphasis>root</emphasis> filesystem.
+La instal·lació i configuració de l'<quote>elilo</quote> constitueix el
+darrer pas de la instal·lació dels paquets de la instal·lació bàsica.
+El &d-i; us presentarà una llista de possibles particions del disc adients
+per a esdevenir una partició EFI. Seleccioneu la partició que heu
+configurat abans durant la instal·lació, que serà normalment una
+partició al mateix disc dur que conté el sistema de fitxers
+<emphasis>arrel</emphasis>.
</para>
- <warning><title>Choose the correct partition!</title>
+ <warning><title>Trieu la partició correcta!</title>
<para>
-The criteria for selecting a partition is that it is FAT format
-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
-the installation, erasing any previous contents!
+Els criteris per seleccionar una partició són: tenir el sistema de fitxers
+en format FAT amb el senyalador <emphasis>boot (arrencada)</emphasis>
+activat. El &d-i; pot mostrar nombroses opcions segons el que haja trobat
+en analitzar els discs del sistema, incloent-hi les particions EFI d'altres
+discs del sistema i les particions de diagnòstic EFI. Recordeu que
+l'<command>elilo</command> pot formatejar la partició durant la
+instal·lació i que això esborrarà qualsevol contingut que hi haja!
</para></warning>
</sect3>
<sect3 arch="ia64">
- <title>EFI Partition Contents</title>
+ <title>Continguts de la partició EFI</title>
<para>
-The EFI partition is a FAT filesystem format partition on one of the
-hard disks of the system, usually the same disk that contains the
-<emphasis>root</emphasis> filesystem.
-It is normally not mounted on a running system as it is only needed
-by the <quote>EFI Boot Manager</quote> to load the system and the
-installer part of the <command>elilo</command> writes to the filesystem
-directly.
-The <command>/usr/sbin/elilo</command> utility writes the following files
-into the <filename>efi/debian</filename> directory of the EFI
-partition during the installation.
-Note that the <quote>EFI Boot Manager</quote> would find these files
-using the path <filename>fs<replaceable>n</replaceable>:\efi\debian</filename>.
-There may be other files in this filesystem as well over time as
-the system is updated or re-configured.
+La partició EFI és una partició de format de sistema de fitxers FAT,
+situada a un dels discs durs del sistema, normalment el mateix que conté
+el sistema de fitxers <emphasis>arrel</emphasis>. No sol estar muntada a
+un sistema que estiga en execució, ja que solament la necessita el
+<quote>gestor d'arrencada EFI</quote> per carregar el sistema i la part
+de l'instal·lador que l'<command>elilo</command> escriu al sistema de
+fitxers directament. La utilitat <command>/usr/sbin/elilo</command> escriu
+els següents fitxers al directori <filename>efi/debian</filename> de la
+partició EFI durant la instal·lació. Tingueu en compte que el
+<quote>gestor de càrrega EFI</quote> trobarà aquests fitxers emprant el
+camí <filename>fs<replaceable>n</replaceable>:\efi\debian</filename>.
+Podrà haver-hi altres fitxers en aquest sistema de fitxers a mesura que,
+amb el temps, s'actualitze o es reconfigure el sistema.
</para>
@@ -76,9 +74,10 @@ the system is updated or re-configured.
<term><filename>elilo.conf</filename></term>
<listitem><para>
-This is the configuration file read by the boot loader when it starts.
-It is a copy of the <filename>/etc/elilo.conf</filename> with
-the filenames re-written to refer to files in the EFI partition.
+Aquest és el fitxer de configuració que llegeix el carregador quan
+s'inicia. És una còpia de l'<filename>/etc/elilo.conf</filename> amb
+els noms de fitxer reescrits per referir-se als fitxers de la partició
+EFI.
</para></listitem></varlistentry>
@@ -86,10 +85,10 @@ the filenames re-written to refer to files in the EFI partition.
<term><filename>elilo.efi</filename></term>
<listitem><para>
-This is the boot loader program that the <quote>EFI Boot Manager</quote>
-runs to boot the system.
-It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem>
-menu item of the <quote>EFI Boot Manager</quote> command menu.
+Aquest és el programa carregador que el <quote>gestor d'arrencada EFI</quote>
+executa per arrencar el sistema. És el programa que hi ha al darrere de
+l'ítem <guimenuitem>Debian GNU/Linux</guimenuitem> del menú d'ordres
+del <quote>gestor d'arrencada EFI</quote>.
</para></listitem></varlistentry>
@@ -97,12 +96,11 @@ menu item of the <quote>EFI Boot Manager</quote> command menu.
<term><filename>initrd.img</filename></term>
<listitem><para>
-This is the initial root filesystem used to boot the kernel.
-It is a copy of the file referenced in the
-<filename>/etc/elilo.conf</filename>.
-In a standard Debian installation it would be the file in
-<filename>/boot</filename> pointed to by the symbolic link
-<filename>/initrd.img</filename>.
+Aquest és el sistema de fitxers arrel inicial emprat per arrencar el
+nucli. És una còpia del fitxer referenciat a
+<filename>/etc/elilo.conf</filename>. En una instal·lació estàndard de
+Debian seria el fitxer de <filename>/boot</filename> al qual apunta
+l'enllaç simbòlic <filename>/initrd.img</filename>.
</para></listitem></varlistentry>
@@ -110,10 +108,10 @@ In a standard Debian installation it would be the file in
<term><filename>readme.txt</filename></term>
<listitem><para>
-This is a small text file warning you that the contents of the
-directory are managed by the <command>elilo</command> and that
-any local changes would be lost at the next time
-<filename>/usr/sbin/elilo</filename> is run.
+És un petit fitxer de text que us informa que els continguts del
+directori són gestionats per l'<command>elilo</command> i que
+qualsevol canvi local es perdrà la propera vegada que s'execute
+l'<filename>/usr/sbin/elilo</filename>.
</para></listitem></varlistentry>
@@ -121,12 +119,10 @@ any local changes would be lost at the next time
<term><filename>vmlinuz</filename></term>
<listitem><para>
-This is the compressed kernel itself.
-It is a copy of the file referenced in the
-<filename>/etc/elilo.conf</filename>.
-In a standard Debian installation it would be the file in
-<filename>/boot</filename> pointed to by the symbolic link
-<filename>/vmlinuz</filename>.
+És el nucli comprimit. És una còpia del fitxer referenciat a
+<filename>/etc/elilo.conf</filename>. En una instal·lació estàndard
+de Debian, seria el fitxer de <filename>/boot</filename> al qual
+apunta l'enllaç simbòlic <filename>/vmlinuz</filename>.
</para></listitem></varlistentry>
diff --git a/ca/using-d-i/modules/mips/arcboot-installer.xml b/ca/using-d-i/modules/mips/arcboot-installer.xml
index 13eba925e..c21f2b982 100644
--- a/ca/using-d-i/modules/mips/arcboot-installer.xml
+++ b/ca/using-d-i/modules/mips/arcboot-installer.xml
@@ -1,28 +1,27 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 24663 untranslated -->
+<!-- original version: 24663 -->
<sect3 arch="mips">
- <title><command>arcboot</command>-installer</title>
+ <title>Instal·lador <command>arcboot</command></title>
<para>
-The boot loader on SGI Indys is <command>arcboot</command>.
-It has to be installed on the same hard disk as the kernel (this is done
-automatically by the installer). Arcboot supports different configurations
-which are set up in <filename>/etc/arcboot.conf</filename>. Each
-configuration has a unique name,
-the default setup as created by the installer is <quote>linux</quote>.
-After arcboot has been installed, the system can be booted from hard disk
-by setting some firmware environment variables entering
+El carregador als Indy SGI és <command>arcboot</command>.
+Ha d'instal·lar-se al mateix disc dur que el nucli (açò ho fa automàticament
+l'instal·lador). L'arcboot suporta diferents configuracions que són ja al
+<filename>/etc/arcboot.conf</filename>. Aquesta configuració té un nom únic,
+la configuració predeterminada que crea l'instal·lador és <quote>linux</quote>.
+Desprès de tenir instal·lat l'arcboot, el sistema ja es pot arrencar des del
+disc dur donant valors a algunes variables d'entorn del firmware fent:
<informalexample><screen>
<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>
-<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>
+<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>nrpart</replaceable>)</userinput>
<userinput> setenv OSLoader arcboot</userinput>
<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>
<userinput> setenv AutoLoad yes</userinput>
</screen></informalexample>
-on the firmware prompt, and then typing <command>boot</command>.
+a l'indicador del firmware, i escrivint <command>boot</command>.
</para>
@@ -31,8 +30,8 @@ on the firmware prompt, and then typing <command>boot</command>.
<term> <replaceable>scsi</replaceable> </term>
<listitem><para>
-is the SCSI bus to be booted from, this is <userinput>0</userinput>
-for the onboard controllers
+és el bus SCSI des d'on arrencar, que és <userinput>0</userinput>
+per les controladores en placa base
</para></listitem>
</varlistentry>
@@ -40,17 +39,15 @@ for the onboard controllers
<term> <replaceable>disk</replaceable> </term>
<listitem><para>
-is the SCSI ID of the hard disk on which <command>arcboot</command> is
-installed
+és l'ID SCSI del disc dur on es té instal·lat l'<command>arcboot</command>
</para></listitem>
</varlistentry>
<varlistentry>
-<term> <replaceable>partnr</replaceable> </term>
+<term> <replaceable>nrpart</replaceable> </term>
<listitem><para>
-is the number of the partition on which
-<filename>/etc/arcboot.conf</filename> resides
+és el nombre de la partició on és l'<filename>/etc/arcboot.conf</filename>
</para></listitem>
</varlistentry>
@@ -58,9 +55,9 @@ is the number of the partition on which
<term> <replaceable>config</replaceable> </term>
<listitem><para>
-is the name of the configuration entry in
-<filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by
-default.
+és el nom de l'entrada a la configuració al
+<filename>/etc/arcboot.conf</filename>, on <quote>linux</quote> és
+l'opció predeterminada.
</para></listitem>
</varlistentry>
diff --git a/ca/using-d-i/modules/mipsel/delo-installer.xml b/ca/using-d-i/modules/mipsel/delo-installer.xml
index 7325398ac..d840bf718 100644
--- a/ca/using-d-i/modules/mipsel/delo-installer.xml
+++ b/ca/using-d-i/modules/mipsel/delo-installer.xml
@@ -1,24 +1,23 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 24663 untranslated -->
+<!-- original version: 24663 -->
<sect3 arch="mipsel">
- <title><command>delo</command>-installer</title>
+ <title>Instal·lador <command>delo</command></title>
<para>
-The boot loader on DECstations is <command>DELO</command>.
-It has to be installed on the same hard disk as the kernel (this is done
-automatically by the installer). DELO supports different configurations
-which are set up in <filename>/etc/delo.conf</filename>. Each
-configuration has a unique name,
-the default setup as created by the installer is <quote>linux</quote>.
-After DELO has been installed, the system can be booted from hard disk
-by entering
+El carregador en DECstations és <command>DELO</command>.
+Ha de ser instal·lat en el mateix disc dur que el nucli (això es fet
+per l'instal·lador automàticament). DELO suporta diferents configuracions
+les quals són definides a <filename>/etc/delo.conf</filename>. Cada
+configuració té un nom únic, la configuració predeterminada creada per
+l'instal·lador és <quote>linux</quote>. Després de que DELO hagi estat
+instal·lat, el sistema pot ser arrencat des de el disc dur teclejant
<informalexample><screen>
-<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput>
+<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>nrpart</replaceable>/<replaceable>nom</replaceable></userinput>
</screen></informalexample>
-on the firmware prompt.
+a l'indicador de firmware.
</para>
@@ -27,8 +26,8 @@ on the firmware prompt.
<term> <replaceable>#</replaceable> </term>
<listitem><para>
-is the TurboChannel device to be booted from, on most DECstations this
-is <userinput>3</userinput> for the onboard controllers
+és el dispositiu TurboChannel des d'on s'ha d'arrencar, en la majoria
+de DECstations és <userinput>3</userinput> per als controladors
</para></listitem>
</varlistentry>
@@ -36,27 +35,27 @@ is <userinput>3</userinput> for the onboard controllers
<term> <replaceable>id</replaceable> </term>
<listitem><para>
-is the SCSI ID of the hard disk on which <command>DELO</command> is
-installed
+és l'ID SCSI del disc dur on <command>DELO</command> és
+instal·lat
</para></listitem>
</varlistentry>
<varlistentry>
-<term> <replaceable>partnr</replaceable> </term>
+<term> <replaceable>nrpart</replaceable> </term>
<listitem><para>
-is the number of the partition on which
-<filename>/etc/delo.conf</filename> resides
+és el número de la partició a la qual
+<filename>/etc/delo.conf</filename> resideix
</para></listitem>
</varlistentry>
<varlistentry>
-<term> <replaceable>name</replaceable> </term>
+<term> <replaceable>nom</replaceable> </term>
<listitem><para>
-is the name of the configuration entry in
-<filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by
-default.
+és el nom de l'entrada de configuració a
+<filename>/etc/delo.conf</filename>, la qual és <quote>linux</quote>
+de manera predeterminada.
</para></listitem>
</varlistentry>
@@ -64,9 +63,9 @@ default.
<para>
-In case <filename>/etc/delo.conf</filename> is on the first partition
-on the disk and the default configuration shall be booted, it is
-sufficient to use
+En cas de que <filename>/etc/delo.conf</filename> sigui a la primera
+partició del disc i la configuració predeterminades sigui emprada per
+arrencar, n'hi ha prou usant
<informalexample><screen>
<userinput>boot #/rz<replaceable>id</replaceable></userinput>
diff --git a/ca/using-d-i/modules/network-console.xml b/ca/using-d-i/modules/network-console.xml
index 505280b55..d5f518e99 100644
--- a/ca/using-d-i/modules/network-console.xml
+++ b/ca/using-d-i/modules/network-console.xml
@@ -1,106 +1,104 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 31173 untranslated -->
+<!-- original version: 31173 -->
<sect3 id="network-console">
- <title>Installation Over the Network</title>
+ <title>Instal·lació a través de la xarxa</title>
<para arch="not-s390">
-One of the more interesting components is
-<firstterm>network-console</firstterm>. It allows you to do a large
-part of the installation over the network via SSH. The use of the
-network implies you will have to perform the first steps of the
-installation from the console, at least to the point of setting up
-the networking. (Although you can automate that part with
-<xref linkend="automatic-install"/>.)
+Un dels components més interessants és
+<firstterm>network-console</firstterm>. Permet realitzar una bona part
+de la instal·lació per xarxa, via SSH. L'ús de la xarxa implica
+que haureu de seguir els primers passos de la instal·lació des de la
+consola, almenys fins a tenir configurada la xarxa (tot i que podeu
+automatitzar també aquesta part, <xref linkend="automatic-install"/>).
</para><para arch="not-s390">
-This component is not loaded into the main installation menu by default,
-so you have to explicitly ask for it.
+Aquest component no es carrega al menú principal de la instal·lació
+predeterminada, s'ha de fer explícitament.
-If you are installing from CD, you need to boot with medium priority or
-otherwise invoke the main installation menu and choose <guimenuitem>Load
-installer components from CD</guimenuitem> and from the list of
-additional components select <guimenuitem>network-console: Continue
-installation remotely using SSH</guimenuitem>. Successful load is
-indicated by a new menu entry called <guimenuitem>Continue
-installation remotely using SSH</guimenuitem>.
+Si esteu instal·lant des de CD, haureu d'arrencar amb prioritat mitja o
+bé triar <guimenuitem>Carrega components de l'instal·lador des d'un
+CD</guimenuitem> al menú principal d'instal·lació, i seleccionar
+<guimenuitem>network-console: Continua la instal·lació remotament
+utilitzant SSH</guimenuitem> a la llista de components addicionals.
</para><para arch="s390">
-For installations on &arch-title;, this is the default method after
-setting up the network.
+Per a instal·lacions a &arch-title;, aquest és el mètode predeterminat
+després de configurar la xarxa.
</para><para>
-<phrase arch="not-s390">After selecting this new entry, you</phrase>
-<phrase arch="s390">You</phrase> will be asked for a new password
-to be used for connecting to the installation system and for its
-confirmation. That's all. Now you should see a screen which instructs
-you to login remotely as the user <emphasis>installer</emphasis> with
-the password you just provided. Another important detail to notice on
-this screen is the fingerprint of this system. You need to transfer
-the fingerprint securely to the <quote>person who will continue the
-installation remotely</quote>.
+<phrase arch="not-s390">Després de seleccionar aquesta nova entrada,
+haureu</phrase><phrase arch="s390">Haureu</phrase> d'introduir
+una contrasenya nova, que s'utilitzarà per connectar al sistema
+d'instal·lació i per a la seva confirmació. Això és tot. A
+continuació veureu una pantalla d'entrada que us instruirà a entrar
+remotament com a usuari <emphasis>installer</emphasis> i la contrasenya
+que acabeu de proporcionar. Un altre detall important que s'ha de tenir
+en compte en aquest punt és l'empremta digital del sistema. Caldrà
+transferir-la de manera segura a la <quote>persona encarregada de
+continuar amb la instal·lació remota</quote>.
</para><para>
-Should you decide to continue with the installation locally, you
-can always press &enterkey;, which will bring you back to
-the main menu, where you can select another component.
+Si decidiu continuar la instal·lació localment, sempre podeu prémer
+&enterkey;, que us tornarà al menú principal, on novament podreu
+seleccionar un altre component.
</para><para>
-Now let's switch to the other side of the wire. As a prerequisite, you
-need to configure your terminal for UTF-8 encoding, because that is
-what the installation system uses. If you do not, remote installation
-will be still possible, but you may encounter strange display
-artefacts like destroyed dialog borders or unreadable non-ascii
-characters. Establishing a connection with the installation system
-is as simple as typing:
+Tornem ara a l'altra banda del cable. En primer lloc, és necessari
+que configureu el vostre terminal per a UTF-8, ja que aquesta és la
+codificació que utilitza el sistema d'instal·lació. Si no ho feu,
+la instal·lació remota encara serà possible, però segurament certs
+diàlegs o caràcters no es visualitzaran correctament. Establir una
+connexió amb el sistema d'instal·lació és tan fàcil com teclejar:
<informalexample><screen>
-<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>
+<prompt>$</prompt> <userinput>ssh -l installer <replaceable>ordinador_a_instal·lar</replaceable></userinput>
</screen></informalexample>
-Where <replaceable>install_host</replaceable> is either the name
-or IP address of the computer being installed. Before the actual
-login the fingerprint of the remote system will be displayed and
-you will have to confirm that it is correct.
+On <replaceable>ordinador_a_instal·lar</replaceable> és el nom o
+l'adreça IP de l'ordinador que s'està instal·lant. Abans de fer
+l'entrada de debò, es mostrarà l'empremta digital del sistema remot,
+i haureu de confirmar que és correcta.
</para><note><para>
-If you install several computers in turn and they happen to have the
-same IP address or hostname, <command>ssh</command> will refuse to connect
-to such host. The reason is that it will have different fingerprint, which
-is usually a sign of a spoofing attack. If you are sure this is not the
-case, you will need to delete the relevant line from
-<filename>~/.ssh/known_hosts</filename> and try again.
+Si instal·leu molts ordinadors alhora i casualment tenen la mateixa
+adreça IP o el mateix nom, <command>ssh</command> rebutjarà la
+connexió. El problema és que hi haurà empremtes digitals diferents
+per a un mateix identificador, fet que normalment s'interpreta com un
+atac. Si esteu segurs que no és el cas, esborreu la línia corresponent
+del fitxer <filename>~/.ssh/known_hosts</filename> i torneu a intentar-ho.
</para></note><para>
-After the login you will be presented with an initial screen where you
-have two possibilities called <guimenuitem>Start menu</guimenuitem> and
-<guimenuitem>Start shell</guimenuitem>. The former brings you to the
-main installer menu, where you can continue with the installation as
-usual. The latter starts a shell from which you can examine and possibly
-fix the remote system. You should only start one SSH session for the
-installation menu, but may start multiple sessions for shells.
+Després d'entrar, veureu la pantalla inicial, des d'on teniu dos
+possibilitats anomenades <guimenuitem>Inicia el menú</guimenuitem>
+i <guimenuitem>Inicia un intèrpret d'ordres</guimenuitem>. La primera
+us durà al menú principal de l'instal·lador, on podreu continuar la
+instal·lació normalment. L'altra, iniciarà un intèrpret d'ordres des
+del que podreu examinar, i potser arreglar, el sistema remot. Només
+hauríeu de començar una sessió SSH per al menú d'instal·lació,
+però podeu iniciar més intèrprets d'ordres.
</para><warning><para>
-After you have started the installation remotely over SSH, you should
-not go back to the installation session running on the local console.
-Doing so may corrupt the database that holds the configuration of
-the new system. This in turn may result in a failed installation or
-problems with the installed system.
+Després d'iniciar la instal·lació remotament sobre SSH, no hauríeu
+de tornar a la sessió que hi ha a la consola local. Podria corrompre's
+la base de dades que manté la configuració del nou sistema. Això
+pot provocar alhora problemes al sistema instal·lat, o fins i tot que
+la instal·lació no finalitzi correctament.
</para><para>
-Also, if you are running the SSH session from an X terminal, you should
-not resize the window as that will result in the connection being
-terminated.
+També hauríeu de tenir en compte que si executeu la sessió SSH des
+d'un terminal X, no s'ha de redimensionar la finestra ja que això
+tallaria la connexió.
</para></warning>
diff --git a/ca/using-d-i/modules/pkgsel.xml b/ca/using-d-i/modules/pkgsel.xml
new file mode 100644
index 000000000..c1796aa44
--- /dev/null
+++ b/ca/using-d-i/modules/pkgsel.xml
@@ -0,0 +1,161 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 33814 untranslated -->
+
+ <sect3 id="pkgsel">
+ <title>Selecting and Installing Software</title>
+
+<para>
+
+During the installation process, you are given the opportunity to select
+additional software to install. Rather than picking individual software
+packages from the &num-of-distrib-pkgs; available packages, this stage of
+the installation process focuses on selecting and installing predefined
+collections of software to quickly set up your computer to perform various
+tasks.
+
+</para><para>
+
+So, you have the ability to choose <emphasis>tasks</emphasis> first,
+and then add on more individual packages later. These tasks loosely
+represent a number of different jobs or things you want to do with
+your computer, such as <quote>Desktop environment</quote>,
+<quote>Web server</quote>, or <quote>Print server</quote><footnote>
+
+<para>
+
+You should know that to present this list, the installer is merely
+invoking the <command>tasksel</command> program. It can be
+run at any time after installation to install (or remove) more
+packages, or you can use a more fine-grained tool such as <command>aptitude</command>.
+If you are looking for a specific single package, after
+installation is complete, simply run <userinput>aptitude install
+<replaceable>package</replaceable></userinput>, where
+<replaceable>package</replaceable> is the name of the package you are
+looking for.
+
+</para>
+
+</footnote>. <xref linkend="tasksel-size-list"/> lists the space
+requirements for the available tasks.
+
+</para><para>
+
+Once you've selected your tasks, select
+<guibutton>Ok</guibutton>. At this point,
+<command>aptitude</command> will install the packages you've
+selected.
+
+<note><para>
+
+In the standard user interface of the installer, you can use the space bar
+to toggle selection of a task.
+
+</para></note>
+
+<note><para>
+
+Note that some tasks may be pre-selected based on the characteristics of the
+computer you are installing. If you disagree with these selections you can
+un-select the tasks. You can even opt to install no tasks at all at this point.
+
+</para></note>
+
+</para><para>
+
+Each package you selected with <command>tasksel</command> is downloaded,
+unpacked and then installed in turn by the <command>apt-get</command> and
+<command>dpkg</command> programs. If a particular program needs more
+information from the user, it will prompt you during this process.
+
+</para>
+ <sect4 id="config-mta">
+ <title>Configuring Your Mail Transport Agent</title>
+
+<para>
+
+Today, email is a very important part of many people's life, so it's
+no surprise Debian lets you configure your mail system right as a part
+of the installation process. The standard mail transport agent in
+Debian is <command>exim4</command>, which is relatively small,
+flexible, and easy to learn.
+
+</para><para>
+
+You may ask if this is needed even if your computer is not connected
+to any network. The short answer is: Yes. The longer explanation: Some
+system utilities (like <command>cron</command>,
+<command>quota</command>, <command>aide</command>, &hellip;) may send
+you important notices via email.
+
+</para><para>
+
+So on the first screen you will be presented with several common mail
+scenarios. Choose the one that most closely resembles your needs:
+
+</para>
+
+<variablelist>
+<varlistentry>
+<term>internet site</term>
+<listitem><para>
+
+Your system is connected to a network and your mail is sent and
+received directly using SMTP. On the following screens you will be
+asked a few basic questions, like your machine's mail name, or a list of
+domains for which you accept or relay mail.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>mail sent by smarthost</term>
+<listitem><para>
+
+In this scenario is your outgoing mail forwarded to another machine,
+called a <quote>smarthost</quote>, which does the actual job for
+you. Smarthost also usually stores incoming mail addressed to your
+computer, so you don't need to be permanently online. That also means
+you have to download your mail from the smarthost via programs like
+fetchmail. This option is suitable for dial-up users.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>local delivery only</term>
+<listitem><para>
+
+Your system is not on a network and mail is sent or received only
+between local users. Even if you don't plan to send any messages, this
+option is highly recommended, because some system utilities may send
+you various alerts from time to time (e.g. beloved <quote>Disk quota
+exceeded</quote>). This option is also convenient for new users,
+because it doesn't ask any further questions.
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry>
+<term>no configuration at this time</term>
+<listitem><para>
+
+Choose this if you are absolutely convinced you know what you are
+doing. This will leave you with an unconfigured mail system &mdash;
+until you configure it, you won't be able to send or receive any mail
+and you may miss some important messages from your system utilities.
+
+</para></listitem>
+</varlistentry>
+</variablelist>
+
+<para>
+
+If none of these scenarios suits your needs, or if you need a finer
+setup, you will need to edit configuration files under the
+<filename>/etc/exim4</filename> directory after the installation is
+complete. More information about <command>exim4</command> may be found
+under <filename>/usr/share/doc/exim4</filename>.
+
+</para>
+ </sect4>
+ </sect3>
diff --git a/ca/using-d-i/modules/sparc/silo-installer.xml b/ca/using-d-i/modules/sparc/silo-installer.xml
index 3ce2b6ac6..a94aa1a9f 100644
--- a/ca/using-d-i/modules/sparc/silo-installer.xml
+++ b/ca/using-d-i/modules/sparc/silo-installer.xml
@@ -1,25 +1,24 @@
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 24582 untranslated -->
+<!-- original version: 24582 -->
<sect3 arch="sparc">
- <title>Install the <command>SILO</command> Boot Loader
- on a Hard Disk</title>
+ <title>Instal·lant el carregador <command>SILO</command> al disc dur</title>
<para>
-The standard &architecture; boot loader is called <quote>silo</quote>.
-It is documented in
-<filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is
-similar in configuration and usage to <command>LILO</command>, with
-a few exceptions. First of all, <command>SILO</command> allows you to
-boot any kernel image on your drive, even if it is not listed in
-<filename>/etc/silo.conf</filename>. This is because
-<command>SILO</command> can actually read Linux partitions. Also,
-<filename>/etc/silo.conf</filename> is read at boot time, so there is
-no need to rerun <command>silo</command> after installing a new kernel
-like you would with <command>LILO</command>. <command>SILO</command>
-can also read UFS partitions, which means it can boot SunOS/Solaris
-partitions as well. This is useful if you want to install GNU/Linux
-alongside an existing SunOS/Solaris install.
+El carregador estàndard a &architecture; es diu <quote>silo</quote>. La
+documentació és a <filename>/usr/share/doc/silo/</filename>. La
+configuració de <command>SILO</command> és semblant a la utilitzada al
+<command>LILO</command>, amb poques excepcions. Primer,
+<command>SILO</command> permet que arrenqueu qualsevol imatge del nucli
+al vostre disc, independentment si és o no a la llista que hi ha al
+<filename>/etc/silo.conf</filename>. Açò és perquè <command>SILO</command>
+pot llegir particions Linux. També llegeix el
+<filename>/etc/silo.conf</filename> quan s'arrenca, així que no necessiteu
+tornar a executar el <command>silo</command> desprès d'instal·lar un nou
+nucli com es faria amb el <command>LILO</command>. El
+<command>SILO</command> també pot llegir particions UFS, que vol dir que
+pot arrencar particions SunOS/Solaris. Açò és útil si voleu instal·lar
+GNU/Linux al costat d'una instal·lació existent de SunOS/Solaris.
</para>
</sect3>
diff --git a/ca/using-d-i/modules/tzsetup.xml b/ca/using-d-i/modules/tzsetup.xml
new file mode 100644
index 000000000..6dcba28b1
--- /dev/null
+++ b/ca/using-d-i/modules/tzsetup.xml
@@ -0,0 +1,16 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 33814 untranslated -->
+
+ <sect3 id="tzsetup">
+ <title>Configuring Your Time Zone</title>
+
+<para>
+
+Depending on the location selected at the beginning of the installation
+process, you might be shown a list of timezones relevant for that location.
+If your location has only one time zone, you will not be asked anything and
+the system will assume that time zone.
+
+</para>
+
+ </sect3>
diff --git a/ca/using-d-i/modules/user-setup.xml b/ca/using-d-i/modules/user-setup.xml
new file mode 100644
index 000000000..b2494caad
--- /dev/null
+++ b/ca/using-d-i/modules/user-setup.xml
@@ -0,0 +1,69 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 33814 untranslated -->
+
+ <sect3 id="user-setup">
+ <title>Setting Up Users And Passwords</title>
+
+ <sect4 id="user-setup-root">
+ <title>Set the Root Password</title>
+
+<para>
+
+The <emphasis>root</emphasis> account is also called the
+<emphasis>super-user</emphasis>; it is a login that bypasses all
+security protection on your system. The root account should only be
+used to perform system administration, and only used for as short
+a time as possible.
+
+</para><para>
+
+Any password you create should contain at least 6 characters, and
+should contain both upper- and lower-case characters, as well as
+punctuation characters. Take extra care when setting your root
+password, since it is such a powerful account. Avoid dictionary
+words or use of any personal information which could be guessed.
+
+</para><para>
+
+If anyone ever tells you they need your root password, be extremely
+wary. You should normally never give your root password out, unless you
+are administering a machine with more than one system administrator.
+
+</para>
+ </sect4>
+
+ <sect4 id="make-normal-user">
+ <title>Create an Ordinary User</title>
+
+<para>
+
+The system will ask you whether you wish to create an ordinary user
+account at this point. This account should be your main personal
+log-in. You should <emphasis>not</emphasis> use the root account for
+daily use or as your personal login.
+
+</para><para>
+
+Why not? Well, one reason to avoid using root's privileges is that it
+is very easy to do irreparable damage as root. Another reason is that
+you might be tricked into running a <emphasis>Trojan-horse</emphasis>
+program &mdash; that is a program that takes advantage of your
+super-user powers to compromise the security of your system behind
+your back. Any good book on Unix system administration will cover this
+topic in more detail &mdash; consider reading one if it is new to you.
+
+</para><para>
+
+You will first be prompted for the user's full name. Then you'll be asked
+for a name for the user account; generally your first name or something
+similar will suffice and indeed will be the default. Finally, you will be
+prompted for a password for this account.
+
+</para><para>
+
+If at any point after installation you would like to create another
+account, use the <command>adduser</command> command.
+
+</para>
+ </sect4>
+ </sect3>