From aae019d71a095b4bf234a1204e9508ee82167899 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Tue, 1 Sep 2009 17:22:27 +0000 Subject: Remove untranslated and obsolete files for the Basque translation --- eu/partitioning/partition/alpha.xml | 56 ----------------------- eu/partitioning/partition/hppa.xml | 22 --------- eu/partitioning/partition/ia64.xml | 86 ----------------------------------- eu/partitioning/partition/mips.xml | 18 -------- eu/partitioning/partition/powerpc.xml | 55 ---------------------- eu/partitioning/partition/x86.xml | 86 ----------------------------------- 6 files changed, 323 deletions(-) delete mode 100644 eu/partitioning/partition/alpha.xml delete mode 100644 eu/partitioning/partition/hppa.xml delete mode 100644 eu/partitioning/partition/ia64.xml delete mode 100644 eu/partitioning/partition/mips.xml delete mode 100644 eu/partitioning/partition/powerpc.xml delete mode 100644 eu/partitioning/partition/x86.xml (limited to 'eu/partitioning') 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 @@ - - - - - Partitioning for &arch-title; - - -If you have chosen to boot from the SRM console, you must use -fdisk to partition your disk, as it is the only -partitioning program that can manipulate the BSD disk labels required -by aboot (remember, the SRM boot block is -incompatible with MS-DOS partition tables - see -). -debian-installer will run fdisk -by default if you have not booted from MILO. - - - -If the disk that you have selected for partitioning already contains a -BSD disk label, fdisk will default to BSD disk -label mode. Otherwise, you must use the `b' command to enter disk -label mode. - - - -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 -not make the third partition contain the whole -disk. This is not required by aboot, and in fact, -it may lead to confusion since the swriteboot -utility used to install aboot in the boot sector -will complain about a partition overlapping with the boot block. - - - -Also, because aboot is written to the first few -sectors of the disk (currently it occupies about 70 kilobytes, or 150 -sectors), you must 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. - - - -For ARC installations, you should make a small FAT partition at the -beginning of the disk to contain MILO and -linload.exe - 5 megabytes should be sufficient, see -. Unfortunately, making FAT -file systems from the menu is not yet supported, so you'll have to do -it manually from the shell using mkdosfs before -attempting to install the boot loader. - - - \ 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 @@ - - - - - &arch-title;(e)n partizioak sortzen - - -PALOk, HPPAko sistema abiarazleak, F0 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, /booten muntatuz, hau baita -Linuxen nukleoa(k) bilduko dituen helbidetegia. /boot -behar besteko handia izan behar da, kargatu nahi dituzun nukleoak bertan kokatzeko; -8tik 16ra MB nahikoa izaten da. - - - - 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 @@ - - - - - Partitioning for &arch-title; - - -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, -cfdisk and -parted. -parted can manage both GPT and MS-DOS tables, while -cfdisk 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 -parted to create the new partition table. This is -because the two tables use different areas of a disk, and -cfdisk does not know how to remove a GPT table. - - - -An important difference between cfdisk and -parted is the way they identify a partition -``type''. cfdisk uses a byte in the partition -table (for example, 83 for a linux ext2 partition), while -parted identifies a partition ``type'' by examining -the data on that partition. This means that parted -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. -parted does allow you to create file systems and -format swap space, and you should do that from within -parted. - - - -Unfortunately, parted is a command line driven -program and so not as easy to use as cfdisk. -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: - - - - - mklabel gpt - mkpartfs primary fat 0 50 - mkpartfs primary linux-swap 51 1000 - mkpartfs primary ext2 1001 3000 - set 1 boot on - print - quit - - - - -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 parted can take a few minutes to -complete, as it scans the partition for bad blocks. - - - - - Boot Loader Partition Requirements - - - -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 boot 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. - - - \ 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 @@ - - - - - &arch-title;(e)n partizioak sortzen - - -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. - - - - 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 @@ - - - - - Partitioning Newer PowerMacs - - -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 -Apple_Bootstrap. If the bootstrap partition is -not created with the Apple_Bootstrap type your -machine cannot be made bootable from the hard disk. This partition -can easily be created in mac-fdisk using the -b command. - - - -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. - - - -Note that the bootstrap partition is only meant to hold 3 very small -files: the yaboot binary, its configuration -yaboot.conf, and a first stage OpenFirmware -loader ofboot.b. It need not and must not be -mounted on your file system nor have kernels or anything else copied -to it. The ybin and mkofboot -utilities are used to manipulate this partition. - - - -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 mac-fdisk's -r 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. - - - -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. - - - \ 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 @@ - - - - - Partitioning for &arch-title; - - -The PC BIOS generally adds additional constraints for disk -partitioning. There is a limit to how many primary and -logical 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 - Linux Partition HOWTO and the -Phoenix BIOS FAQ, but -this section will include a brief overview to help you plan most -situations. - - - -Primary partitions are the original partitioning scheme for PC -disks. However, there can only be four of them. To get past this -limitation, extended and logical 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. - - - -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. - - - -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). - - - -This restriction doesn't apply if you have a BIOS newer than around -1995-98 (depending on the manufacturer) that supports the Enhanced -Disk Drive Support Specification. Both Lilo, the Linux loader, and -Debian's alternative mbr 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. - - - -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 (Large). -More information about issues with large disks can be found in the -Large Disk HOWTO. 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 translated representation of the -1024th cylinder. - - - -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 -must be mounted on /boot, -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. - - - -- cgit v1.2.3