Remove untranslated and obsolete files for the Basque translation

15 files changed, 1 insertions, 361 deletions

diff --git a/eu/using-d-i/modules/alpha/aboot-installer.xml b/eu/using-d-i/modules/alpha/aboot-installer.xml
deleted file mode 100644
index 60eb48ed6..000000000
--- a/eu/using-d-i/modules/alpha/aboot-installer.xml
+++ /dev/null
@@ -1,19 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
-
-  <sect3 arch="alpha">
-  <title>Install <command>aboot</command> on a Hard Disk</title>
-<para>
-
-If you have booted from SRM, if 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
-systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix
-a.k.a. Tru64 Unix, or OpenVMS) from the same disk.  If you also have a
-different operating system installed on the disk where you have
-installed Debian, you will have to boot GNU/Linux from a floppy
-instead.
-
-</para>
-  </sect3>
diff --git a/eu/using-d-i/modules/baseconfig.xml b/eu/using-d-i/modules/baseconfig.xml
deleted file mode 100644
index 89cbe1d2e..000000000
--- a/eu/using-d-i/modules/baseconfig.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version:  21579  -->
-
-   <sect3 id="baseconfig">
-   <title>Running <command>base-config</command> From Within &d-i;</title>
-
-<para>
-
-Posible da sistema oinarri konfiguratu instalatzailearen atalik gabe
-(disko gogorretik abiarazi eta gero), <firstterm>chroot</firstterm>
-ingurune batetan  <command>base-config</command> erabiliaz. Hau oso 
-erabilgarria da instalatzailea frogatzeko baino jende gehieneak ez 
-du behar.
-<!-- Feel free to prove me I'm wrong -->
-
-</para>
-   </sect3>
diff --git a/eu/using-d-i/modules/finish-install.xml b/eu/using-d-i/modules/finish-install.xml
index 16ffc3ef1..dfed33cb7 100644
--- a/eu/using-d-i/modules/finish-install.xml
+++ b/eu/using-d-i/modules/finish-install.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original vesion: 21672  -->
+<!-- original version: 21672  -->
 <!-- Piarres Beobidek egina 2004ko Azaroaren 23-an -->
    <sect3 id="finish-install">
    <title>Instalatzea amaitu eta berrabiarazi</title>
diff --git a/eu/using-d-i/modules/ia64/elilo-installer.xml b/eu/using-d-i/modules/ia64/elilo-installer.xml
deleted file mode 100644
index 5c156a8fa..000000000
--- a/eu/using-d-i/modules/ia64/elilo-installer.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
diff --git a/eu/using-d-i/modules/iso-scan.xml b/eu/using-d-i/modules/iso-scan.xml
deleted file mode 100644
index 3bbe2f5e8..000000000
--- a/eu/using-d-i/modules/iso-scan.xml
+++ /dev/null
@@ -1,47 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
-
-   <sect3 id="iso-scan">
-   <title>Looking for the Debian Installer ISO Image</title>
-<para>
-
-When installing via the <emphasis>hd-media</emphasis> method, there
-will be a moment where you need to find and mount the Debian Installer
-iso image in order to get the rest of the installation files. The
-component <command>iso-scan</command> does exactly this.
-
-</para><para>
-
-At first, <command>iso-scan</command> automatically mounts all block
-devices (e.g. partitions) which have some known filesystem on them and
-sequentially searches for filenames ending with
-<filename>.iso</filename> (or <filename>.ISO</filename> for that
-matter). Beware that the first attempt scans only files in the root
-directory and in the first level of subdirectories (i.e. it finds
-<filename>/<replaceable>whatever</replaceable>.iso</filename>,
-<filename>/data/<replaceable>whatever</replaceable>.iso</filename>,
-but not
-<filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>).
-After an iso image has been found, <command>iso-scan</command> checks
-its content to determine, if the image is valid Debian iso image or
-not. In the former case we are done, in the latter
-<command>iso-scan</command> seeks for another image.
-
-</para><para>
-
-In case the previous attempt to find an installer iso image fails,
-<command>iso-scan</command> will ask you whether you would like to
-perform more throughly search. This pass doesn't look only into the
-topmost directories, but really traverses whole filesystem.
-
-</para><para>
-
-If <command>iso-scan</command> does not discover your installer iso
-image, reboot back to your original operating system and check if the
-image has correct name (ending in <filename>.iso</filename>), if it is
-placed on a filesystem recognizable by &d-i;, and if it is not
-corrupted (verify the checksum). Experienced unix users could do this
-without rebooting on the second console.
-
-</para>
-   </sect3>
diff --git a/eu/using-d-i/modules/kernel-chooser.xml b/eu/using-d-i/modules/kernel-chooser.xml
deleted file mode 100644
index 0034327ce..000000000
--- a/eu/using-d-i/modules/kernel-chooser.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
-
-   <sect3 id="kernel-chooser"><title>Selecting Kernel</title>
-<para>
-
-If there are more suitable kernels in the APT sources, you will be
-presented a list of these. Select the most suitable one for your
-system; the selected kernel will be installed on a hard disk and will
-be used in your new system. (E.g. you may have different requirements
-for this kernel compared to the installation one).
-
-</para>
-   </sect3>
diff --git a/eu/using-d-i/modules/mdcfg.xml b/eu/using-d-i/modules/mdcfg.xml
deleted file mode 100644
index d4c2f588b..000000000
--- a/eu/using-d-i/modules/mdcfg.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14337 untranslated -->
diff --git a/eu/using-d-i/modules/mips/arcboot-installer.xml b/eu/using-d-i/modules/mips/arcboot-installer.xml
deleted file mode 100644
index 5c156a8fa..000000000
--- a/eu/using-d-i/modules/mips/arcboot-installer.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
diff --git a/eu/using-d-i/modules/mipsel/delo-installer.xml b/eu/using-d-i/modules/mipsel/delo-installer.xml
deleted file mode 100644
index d355f86b9..000000000
--- a/eu/using-d-i/modules/mipsel/delo-installer.xml
+++ /dev/null
@@ -1,80 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
-
-  <sect3 arch="mipsel">
-  <title><command>delo</command>-installer</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
-
-<informalexample><screen>
-
-<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput>
-
-</screen></informalexample>
-
-on the firmware prompt.
-
-</para>
-
-<variablelist>
-<varlistentry>
-<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
-
-</para></listitem>
-</varlistentry>
-<varlistentry>
-<term> <replaceable>id</replaceable> </term>
-<listitem><para>
-
-is the SCSI ID of the hard disk on which <command>DELO</command> is
-installed
-
-</para></listitem>
-</varlistentry>
-<varlistentry>
-<term> <replaceable>partnr</replaceable> </term>
-<listitem><para>
-
-is the number of the partition on which
-<filename>/etc/delo.conf</filename> resides
-
-</para></listitem>
-</varlistentry>
-<varlistentry>
-<term> <replaceable>name</replaceable> </term>
-<listitem><para>
-
-is the name of the configuration entry in
-<filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by
-default.
-
-</para></listitem>
-</varlistentry>
-</variablelist>
-
-<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
-
-<informalexample><screen>
-
-<userinput>boot #/rz<replaceable>id</replaceable></userinput>
-
-</screen></informalexample>
-
-</para>
-  </sect3>
diff --git a/eu/using-d-i/modules/os-prober.xml b/eu/using-d-i/modules/os-prober.xml
deleted file mode 100644
index d4c2f588b..000000000
--- a/eu/using-d-i/modules/os-prober.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14337 untranslated -->
diff --git a/eu/using-d-i/modules/partman-lvm.xml b/eu/using-d-i/modules/partman-lvm.xml
deleted file mode 100644
index d4c2f588b..000000000
--- a/eu/using-d-i/modules/partman-lvm.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14337 untranslated -->
diff --git a/eu/using-d-i/modules/partman.xml b/eu/using-d-i/modules/partman.xml
deleted file mode 100644
index 7fa060159..000000000
--- a/eu/using-d-i/modules/partman.xml
+++ /dev/null
@@ -1,106 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
-
-   <sect3 id="partman"><title>Partitioning Your Disks</title>
-<para>
-
-Now it is time to partition your disks. If you are uncomfortable with
-partitioning, or just want to know more details, see <xref
-linkend="partitioning"/>.
-
-</para><para>
-
-First you will be given the opportunity to automatically partition
-either an entire drive, or free space on a drive. This is also called
-<quote>guided</quote> partitioning. If you do not want to
-autopartition, choose <guimenuitem>Manually edit partition
-table</guimenuitem> from the menu and skip to the next
-paragraph. Otherwise you will be asked if you want <guimenuitem>All
-files in one partition</guimenuitem>, <guimenuitem>Separate partition
-for home directories</guimenuitem>, or if you rather plan to have
-a <guimenuitem>Multi-user system</guimenuitem>. All schemes have their
-pros and cons, some of which are discussed in <xref
-linkend="partitioning"/>. If you are unsure, choose the first
-one. Bear in mind, that guided partitioning needs certain minimal
-amount of free space to operate with. If you don't give it at least
-about 1GB of space (depends on chosen scheme), guided partitioning
-will fail.
-
-</para>
-
-<informaltable>
-<tgroup cols="3">
-<thead>
-<row>
-  <entry>Partitioning scheme</entry>
-  <entry>Minimum space</entry>
-  <entry>Created partitions</entry>
-</row>
-</thead>
-
-<tbody>
-<row>
-  <entry>All files in one partition</entry>
-  <entry>600MB</entry>
-  <entry><filename>/</filename>, swap</entry>
-</row><row>
-  <entry>Separate partition for home directories</entry>
-  <entry>500MB</entry>
-  <entry>
-    <filename>/</filename>, <filename>/home</filename>, swap
-  </entry>
-</row><row>
-  <entry>Multi-user system</entry>
-  <entry>1GB</entry>
-  <entry>
-    <filename>/</filename>, <filename>/home</filename>,
-    <filename>/usr</filename>, <filename>/var</filename>,
-    <filename>/tmp</filename>, swap
-  </entry>
-</row>
-
-</tbody></tgroup></informaltable>
-
-<para>
-
-On the next screen you will see your partition table, how the
-partitions will be formatted, and where they will be mounted.
-If you did automatic partitioning, you should just be able to choose
-<guimenuitem>Finished partitioning</guimenuitem> from the menu to use
-what it set up.
-
-</para><para>
-
-Select partititons from the list to modify or delete them. If you have
-free space it will also show up under a drive, and you can select it
-to create new partitions. When modifying a partition you will have the
-opportunity to choose how to use the partition, the file system to
-use, and where to mount it. The partitioning menu also has a choice at
-the bottom that can be used to automatically partition a drive or
-existing free space on a drive, if you'd rather go that route. Be sure
-to create at least two partitions, one for <emphasis>swap</emphasis>
-and one for the <emphasis>root</emphasis> filesystem (which must be
-mounted as <filename>/</filename>). If you forget to mount the root
-filesystem, <command>partman</command> won't let you continue until
-you correct this issue. However, this situation should not happen,
-because <command>partman</command> by default offers reasonable
-defaults.
-
-</para><para>
-
-Capabilities of <command>partman</command> can be extended with
-installer modules, so if you can't see all promised goodies, check if
-you have loaded all required modules
-(e.g. <filename>partman-ext3</filename>,
-<filename>partman-xfs</filename>, or
-<filename>partman-lvm</filename>).
-
-</para><para>
-
-After you are satisfied with partitioning, select <guimenuitem>Finished
-partitioning</guimenuitem> from the partitioning menu. You will be
-presented with a summary of changes made to the disks and asked to
-confirm that the filesystems should be created as requested.
-
-</para>
-   </sect3>
diff --git a/eu/using-d-i/modules/pcmcia.xml b/eu/using-d-i/modules/pcmcia.xml
deleted file mode 100644
index 5c156a8fa..000000000
--- a/eu/using-d-i/modules/pcmcia.xml
+++ /dev/null
@@ -1,2 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
diff --git a/eu/using-d-i/modules/shell.xml b/eu/using-d-i/modules/shell.xml
deleted file mode 100644
index 73ce8173e..000000000
--- a/eu/using-d-i/modules/shell.xml
+++ /dev/null
@@ -1,40 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 14602 untranslated -->
-
-   <sect3 id="shell">
-<title>Using the Shell and Viewing the Logs</title>
-
-<para>
-
-There is an Execute a Shell item on the menu. If the menu is not
-available when you need to use the shell, press <keycombo>
-<keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac
-keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap>
-</keycombo>) to get to the second <emphasis>virtual
-console</emphasis>. That's the <keycap>Alt</keycap> key on the
-left-hand side of the <keycap>space bar</keycap>, and the
-<keycap>F2</keycap> function key, at the same time. This is a separate
-window running a Bourne shell clone called <command>ash</command>.
-
-</para><para>
-
-At this point you are booted from the RAM disk, and there is a limited
-set of Unix utilities available for your use. You can see what
-programs are available with the command <userinput>ls /bin /sbin
-/usr/bin /usr/sbin</userinput>. The text editor is
-<command>nano</command>. The shell has some nice features like
-autocompletion and history.
-
-</para><para>
-
-Use the menus to perform any task that they are able to do &mdash; the
-shell and commands are only there in case something goes wrong.  In
-particular, you should always use the menus, not the shell, to
-activate your swap partition, because the menu software can't detect
-that you've done this from the shell. Press <keycombo><keycap>Left
-Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or
-type <userinput>exit</userinput> if you used a menu item to open the
-shell. 
-
-</para>
-  </sect3>
diff --git a/eu/using-d-i/modules/sparc/silo-installer.xml b/eu/using-d-i/modules/sparc/silo-installer.xml
deleted file mode 100644
index f459a8cb1..000000000
--- a/eu/using-d-i/modules/sparc/silo-installer.xml
+++ /dev/null
@@ -1,25 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 16467 untranslated -->
-
-  <sect3 arch="sparc">
-  <title>Install the <command>SILO</command> Boot Loader
-         on a Hard Disk</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
-along side an existing SunOS/Solaris install.
-
-</para>
-  </sect3>