Remove untranslated and obsolete files for the Basque translation

6 files changed, 0 insertions, 323 deletions

diff --git a/eu/partitioning/partition/alpha.xml b/eu/partitioning/partition/alpha.xml
deleted file mode 100644
index a925db8ab..000000000
--- a/eu/partitioning/partition/alpha.xml
+++ /dev/null
@@ -1,56 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-
-  <sect2 arch="alpha"><title>Partitioning for &arch-title;</title>
-<para>
-
-If you have chosen to boot from the SRM console, you must use
-<command>fdisk</command> to partition your disk, as it is the only
-partitioning program that can manipulate the BSD disk labels required
-by <command>aboot</command> (remember, the SRM boot block is
-incompatible with MS-DOS partition tables - see 
-<xref linkend="alpha-firmware"/>).
-<command>debian-installer</command> will run <command>fdisk</command>
-by default if you have not booted from <command>MILO</command>.
-
-</para><para>
-
-If the disk that you have selected for partitioning already contains a
-BSD disk label, <command>fdisk</command> will default to BSD disk
-label mode.  Otherwise, you must use the `b' command to enter disk
-label mode.
-
-</para><para>
-
-Unless you wish to use the disk you are partitioning from Tru64 Unix
-or one of the free 4.4BSD-Lite derived operating systems (FreeBSD,
-OpenBSD, or NetBSD), it is suggested that you do
-<emphasis>not</emphasis> make the third partition contain the whole
-disk.  This is not required by <command>aboot</command>, and in fact,
-it may lead to confusion since the <command>swriteboot</command>
-utility used to install <command>aboot</command> in the boot sector
-will complain about a partition overlapping with the boot block.
-
-</para><para>
-
-Also, because <command>aboot</command> is written to the first few
-sectors of the disk (currently it occupies about 70 kilobytes, or 150
-sectors), you <emphasis>must</emphasis> leave enough empty space at
-the beginning of the disk for it.  In the past, it was suggested that
-you make a small partition at the beginning of the disk, to be left
-unformatted.  For the same reason mentioned above, we now suggest that
-you do not do this on disks that will only be used by GNU/Linux.
-
-</para><para>
-
-For ARC installations, you should make a small FAT partition at the
-beginning of the disk to contain <command>MILO</command> and
-<command>linload.exe</command> - 5 megabytes should be sufficient, see
-<xref linkend="non-debian-partitioning"/>. Unfortunately, making FAT
-file systems from the menu is not yet supported, so you'll have to do
-it manually from the shell using <command>mkdosfs</command> before
-attempting to install the boot loader.
-
-</para>
-  </sect2>
\ No newline at end of file
diff --git a/eu/partitioning/partition/hppa.xml b/eu/partitioning/partition/hppa.xml
deleted file mode 100644
index fdf510b2c..000000000
--- a/eu/partitioning/partition/hppa.xml
+++ /dev/null
@@ -1,22 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-
-  <sect2 arch="hppa"><title>&arch-title;(e)n partizioak sortzen</title>
-<para>
-
-PALOk, HPPAko sistema abiarazleak, <quote>F0</quote> erako partizio bat
-behar du diskaren lehen 2 GBen guneren batean. Gune honetan kokatuko dira
-sistema abiarazlea, hautazko nukleo bat eta RAM diska, beraz, behar besteko
-handia izan dadin ziurtatu: 4 Mb gutxienez (edo, hobeto, 8tik 16era bitartean).
-Firmwarearentzat beharrezko beste ezaugarri bat Linuxen nukleoa diskaren lehen
-2 GBetan egotea da. Hau lortzeko era erraz bat fitxategi sistemak diskaren
-lehen 2 GBak guztiz betez partizio bat sortzea da. Bestela, diskaren hasieran
-partizio bat sor dezakezu, <filename>/boot</filename>en muntatuz, hau baita
-Linuxen nukleoa(k) bilduko dituen helbidetegia. <filename>/boot</filename>
-behar besteko handia izan behar da, kargatu nahi dituzun nukleoak bertan kokatzeko;
-8tik 16ra MB nahikoa izaten da.
-
-</para>
-  </sect2>
-
diff --git a/eu/partitioning/partition/ia64.xml b/eu/partitioning/partition/ia64.xml
deleted file mode 100644
index 50620040d..000000000
--- a/eu/partitioning/partition/ia64.xml
+++ /dev/null
@@ -1,86 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-
-  <sect2 arch="ia64"><title>Partitioning for &arch-title;</title>
-<para>
-
-ia64 EFI firmware supports two partition table (or disk label)
-formats, GPT and MS-DOS.  MS-DOS is the format typically used on i386
-PCs, and is no longer recommended for ia64 systems.  The installer
-provides two partitioning programs, 
-<ulink url="cfdisk.txt"><command>cfdisk</command></ulink> and 
-<ulink url="parted.txt"><command>parted</command></ulink>.
-<command>parted</command> can manage both GPT and MS-DOS tables, while
-<command>cfdisk</command> can only manage MS-DOS tables.  It is very
-important to note that if your disk has previously been partitioned
-with a GPT table, and you now want to use MS-DOS tables, you must use
-<command>parted</command> to create the new partition table.  This is
-because the two tables use different areas of a disk, and
-<command>cfdisk</command> does not know how to remove a GPT table.
-
-</para><para>
-
-An important difference between <command>cfdisk</command> and
-<command>parted</command> is the way they identify a partition
-``type''.  <command>cfdisk</command> uses a byte in the partition
-table (for example, 83 for a linux ext2 partition), while
-<command>parted</command> identifies a partition ``type'' by examining
-the data on that partition.  This means that <command>parted</command>
-will not consider a partition to be a swap partition until you format
-it as such.  Similarly, it won't consider a partition a linux ext2
-partition until you create a file system on it.
-<command>parted</command> does allow you to create file systems and
-format swap space, and you should do that from within
-<command>parted</command>.
-
-</para><para>
-
-Unfortunately, <command>parted</command> is a command line driven
-program and so not as easy to use as <command>cfdisk</command>.
-Assuming that you want to erase your whole disk and create a GPT table
-and some partitions, then something similar to the following command
-sequence could be used:
-
-</para><para>
-<informalexample><screen>
-
-      mklabel gpt
-      mkpartfs primary fat 0 50
-      mkpartfs primary linux-swap 51 1000
-      mkpartfs primary ext2 1001 3000
-      set 1 boot on
-      print
-      quit
-
-</screen></informalexample>
-</para><para>
-
-That creates a new partition table, and three partitions to be used as
-an EFI boot partition, swap space, and a root file system.  Finally it
-sets the boot flag on the EFI partition.  Partitions are specified in
-Megabytes, with start and end offsets from the beginning of the disk.
-So, for example, above we created a 1999MB ext2 file system starting
-at offset 1001MB from the start of the disk.  Note that formatting swap
-space with <command>parted</command> can take a few minutes to
-complete, as it scans the partition for bad blocks.
-
-</para>
-  </sect2>
-
-  <sect2 arch="ia64"><title>Boot Loader Partition Requirements</title>
-
-<para>
-
-ELILO, the ia64 boot loader, requires a partition containing a FAT
-file system.  If you used GPT partition tables, then that partition
-should have the <userinput>boot</userinput> flag set; if you used
-MS-DOS partition tables, then that partition should be of type "EF".
-The partition must be big enough to hold the boot loader and any
-kernels or RAMdisks you may wish to boot.  A minimum size would be
-about 16MB, but if you are likely to be doing development, or
-experimenting with different kernels, then 128MB might be a better
-size.
-
-</para>
-  </sect2>
\ No newline at end of file
diff --git a/eu/partitioning/partition/mips.xml b/eu/partitioning/partition/mips.xml
deleted file mode 100644
index ff4751f81..000000000
--- a/eu/partitioning/partition/mips.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-
-  <sect2 arch="mips"><title>&arch-title;(e)n partizioak sortzen</title>
-<para>
-
-SGI Indysek SGI diskaren etiketa bat behar dute diska gogorretik sistema
-abiaraz ahal dadin. Hau fdisken adituen menutik sor daiteke. Honela, sorturiko
-bolumenak (9. partizioa) 3 MB baino gehiago izan behar ditu.
-Nukleo ezberdin ugari bildu nahi badituzu, neurria gutxienera ere 10 MBetakoa
-izan behar da. Sortutako bolumena txikiegia bada, 9. partizio hori besterik gabe
-ezaba dezakezu, eta gero neurri ezberdinarekin gehitu. Ohartu bolumen hori 0
-sektorean hasi behar dela.
-
-</para>
-  </sect2>
-
diff --git a/eu/partitioning/partition/powerpc.xml b/eu/partitioning/partition/powerpc.xml
deleted file mode 100644
index 729f1ba75..000000000
--- a/eu/partitioning/partition/powerpc.xml
+++ /dev/null
@@ -1,55 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-
-  <sect2 arch="powerpc"><title>Partitioning Newer PowerMacs</title>
-<para>
-
-If you are installing onto a NewWorld PowerMac you must create a
-special bootstrap partition to hold the boot loader. The size of this
-partition must be 800KB and its partition type must be
-<emphasis>Apple_Bootstrap</emphasis>.  If the bootstrap partition is
-not created with the <emphasis>Apple_Bootstrap</emphasis> type your
-machine cannot be made bootable from the hard disk.  This partition
-can easily be created in <command>mac-fdisk</command> using the
-<userinput>b</userinput> command.
-
-</para><para>
-
-The special partition type Apple_Bootstrap is required to prevent
-MacOS from mounting and damaging the bootstrap partition, as there are
-special modifications made to it in order for OpenFirmware to boot it
-automatically.
-
-</para><para>
-
-Note that the bootstrap partition is only meant to hold 3 very small
-files: the <command>yaboot</command> binary, its configuration
-<filename>yaboot.conf</filename>, and a first stage OpenFirmware
-loader <command>ofboot.b</command>.  It need not and must not be
-mounted on your file system nor have kernels or anything else copied
-to it. The <command>ybin</command> and <command>mkofboot</command>
-utilities are used to manipulate this partition.
-
-</para><para>
-
-In order for OpenFirmware to automatically boot &debian; the bootstrap
-partition should appear before other boot partitions on the disk,
-especially MacOS boot partitions.  The bootstrap partition should be
-the first one you create. However, if you add a bootstrap partition
-later, you can use <command>mac-fdisk</command>'s
-<userinput>r</userinput> command to reorder the partition map so the
-bootstrap partition comes right after the map (which is always
-partition 1). It's the logical map order, not the physical address
-order, that counts.
-
-</para><para>
-
-Apple disks normally have several small driver partitions. If you
-intend to dual boot your machine with MacOSX, you should retain these
-partitions and a small HFS partition (800k is the minimum size). That
-is because MacOSX, on every boot, offers to initialize any disks which do
-not have active MacOS partitions and driver partitions.
-
-</para>
-  </sect2>
\ No newline at end of file
diff --git a/eu/partitioning/partition/x86.xml b/eu/partitioning/partition/x86.xml
deleted file mode 100644
index 26c3e4296..000000000
--- a/eu/partitioning/partition/x86.xml
+++ /dev/null
@@ -1,86 +0,0 @@
-<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 untranslated -->
-
-
-  <sect2 arch="x86"><title>Partitioning for &arch-title;</title>
-<para>
-
-The PC BIOS generally adds additional constraints for disk
-partitioning.  There is a limit to how many <quote>primary</quote> and
-<quote>logical</quote> partitions a drive can contain.  Additionally, with pre
-1994-98 BIOS, there are limits to where on the drive the BIOS can boot
-from.  More information can be found in the
- <ulink url="&url-partition-howto;">Linux Partition HOWTO</ulink> and the 
-<ulink url="&url-phoenix-bios-faq-large-disk;">Phoenix BIOS FAQ</ulink>, but
-this section will include a brief overview to help you plan most
-situations.
-
-</para><para>
-
-<quote>Primary</quote> partitions are the original partitioning scheme for PC
-disks.  However, there can only be four of them.  To get past this
-limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented.  By
-setting one of your primary partitions as an extended partition, you
-can subdivide all the space allocated to that partition into logical
-partitions.  You can create up to 60 logical partitions per extended
-partition; however, you can only have one extended partition per
-drive.
-
-</para><para>
-
-Linux limits the partitions per drive to 15 partitions for SCSI disks
-(3 usable primary partitions, 12 logical partitions), and 63
-partitions on an IDE drive (3 usable primary partitions, 60 logical
-partitions). However the normal &debian; system provides 
-only 20 devices for partitions, so you may not install on partitions
-higher than 20 unless you first manually create devices for those
-partitions. 
-
-</para><para>
-
-If you have a large IDE disk, and are using neither LBA addressing,
-nor overlay drivers (sometimes provided by hard disk manufacturers),
-then the boot partition (the partition containing your kernel image)
-must be placed within the first 1024 cylinders of your hard drive
-(usually around 524 megabytes, without BIOS translation).
-
-</para><para>
-
-This restriction doesn't apply if you have a BIOS newer than around
-1995-98 (depending on the manufacturer) that supports the <quote>Enhanced
-Disk Drive Support Specification</quote>.  Both Lilo, the Linux loader, and
-Debian's alternative <command>mbr</command> must use the BIOS to read the
-kernel from the disk into RAM.  If the BIOS int 0x13 large disk access
-extensions are found to be present, they will be utilized. Otherwise,
-the legacy disk access interface is used as a fall-back, and it cannot
-be used to address any location on the disk higher than the 1023rd
-cylinder.  Once Linux is booted, no matter what BIOS your computer
-has, these restrictions no longer apply, since Linux does not use the
-BIOS for disk access.
-
-</para><para>
-
-If you have a large disk, you might have to use cylinder translation
-techniques, which you can set from your BIOS setup program, such as
-LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>).
-More information about issues with large disks can be found in the
-<ulink url="&url-large-disk-howto;">Large Disk HOWTO</ulink>.  If you
-are using a cylinder translation scheme, and the BIOS does not support
-the large disk access extensions, then your boot partition has to fit
-within the <emphasis>translated</emphasis> representation of the
-1024th cylinder.
-
-</para><para>
-
-The recommended way of accomplishing this is to create a small (5-10MB
-should suffice) partition at the beginning of the disk to be used as
-the boot partition, and then create whatever other partitions you wish
-to have, in the remaining area.  This boot partition
-<emphasis>must</emphasis> be mounted on <filename>/boot</filename>,
-since that is the directory where the Linux kernel(s) will be stored.
-This configuration will work on any system, regardless of whether LBA
-or large disk CHS translation is used, and regardless of whether your
-BIOS supports the large disk access extensions.
-
-</para>
-  </sect2>