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/using-d-i/modules/alpha/aboot-installer.xml | 19 ----- eu/using-d-i/modules/baseconfig.xml | 17 ---- eu/using-d-i/modules/finish-install.xml | 2 +- eu/using-d-i/modules/ia64/elilo-installer.xml | 2 - eu/using-d-i/modules/iso-scan.xml | 47 ----------- eu/using-d-i/modules/kernel-chooser.xml | 14 ---- eu/using-d-i/modules/mdcfg.xml | 2 - eu/using-d-i/modules/mips/arcboot-installer.xml | 2 - eu/using-d-i/modules/mipsel/delo-installer.xml | 80 ------------------ eu/using-d-i/modules/os-prober.xml | 2 - eu/using-d-i/modules/partman-lvm.xml | 2 - eu/using-d-i/modules/partman.xml | 106 ------------------------ eu/using-d-i/modules/pcmcia.xml | 2 - eu/using-d-i/modules/shell.xml | 40 --------- eu/using-d-i/modules/sparc/silo-installer.xml | 25 ------ 15 files changed, 1 insertion(+), 361 deletions(-) delete mode 100644 eu/using-d-i/modules/alpha/aboot-installer.xml delete mode 100644 eu/using-d-i/modules/baseconfig.xml delete mode 100644 eu/using-d-i/modules/ia64/elilo-installer.xml delete mode 100644 eu/using-d-i/modules/iso-scan.xml delete mode 100644 eu/using-d-i/modules/kernel-chooser.xml delete mode 100644 eu/using-d-i/modules/mdcfg.xml delete mode 100644 eu/using-d-i/modules/mips/arcboot-installer.xml delete mode 100644 eu/using-d-i/modules/mipsel/delo-installer.xml delete mode 100644 eu/using-d-i/modules/os-prober.xml delete mode 100644 eu/using-d-i/modules/partman-lvm.xml delete mode 100644 eu/using-d-i/modules/partman.xml delete mode 100644 eu/using-d-i/modules/pcmcia.xml delete mode 100644 eu/using-d-i/modules/shell.xml delete mode 100644 eu/using-d-i/modules/sparc/silo-installer.xml (limited to 'eu/using-d-i/modules') 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 @@ - - - - - Install <command>aboot</command> on a Hard Disk - - -If you have booted from SRM, if you select this option, the installer -will write aboot to the first sector of the disk on -which you installed Debian. Be very careful - it -is not 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. - - - 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 @@ - - - - - Running <command>base-config</command> From Within &d-i; - - - -Posible da sistema oinarri konfiguratu instalatzailearen atalik gabe -(disko gogorretik abiarazi eta gero), chroot -ingurune batetan base-config erabiliaz. Hau oso -erabilgarria da instalatzailea frogatzeko baino jende gehieneak ez -du behar. - - - - 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 @@ - + Instalatzea amaitu eta berrabiarazi 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 @@ - - 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 @@ - - - - - Looking for the Debian Installer ISO Image - - -When installing via the hd-media 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 iso-scan does exactly this. - - - -At first, iso-scan automatically mounts all block -devices (e.g. partitions) which have some known filesystem on them and -sequentially searches for filenames ending with -.iso (or .ISO 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 -/whatever.iso, -/data/whatever.iso, -but not -/data/tmp/whatever.iso). -After an iso image has been found, iso-scan 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 -iso-scan seeks for another image. - - - -In case the previous attempt to find an installer iso image fails, -iso-scan 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. - - - -If iso-scan does not discover your installer iso -image, reboot back to your original operating system and check if the -image has correct name (ending in .iso), 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. - - - 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 @@ - - - - Selecting Kernel - - -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). - - - 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 @@ - - 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 @@ - - 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 @@ - - - - - <command>delo</command>-installer - - -The boot loader on DECstations is DELO. -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 /etc/delo.conf. Each -configuration has a unique name, -the default setup as created by the installer is linux. -After DELO has been installed, the system can be booted from hard disk -by entering - - - -boot #/rzid partnr/name - - - -on the firmware prompt. - - - - - - # - - -is the TurboChannel device to be booted from, on most DECstations this -is 3 for the onboard controllers - - - - - id - - -is the SCSI ID of the hard disk on which DELO is -installed - - - - - partnr - - -is the number of the partition on which -/etc/delo.conf resides - - - - - name - - -is the name of the configuration entry in -/etc/delo.conf, which is linux by -default. - - - - - - - -In case /etc/delo.conf is on the first partition -on the disk and the default configuration shall be booted, it is -sufficient to use - - - -boot #/rzid - - - - - 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 @@ - - 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 @@ - - 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 @@ - - - - Partitioning Your Disks - - -Now it is time to partition your disks. If you are uncomfortable with -partitioning, or just want to know more details, see . - - - -First you will be given the opportunity to automatically partition -either an entire drive, or free space on a drive. This is also called -guided partitioning. If you do not want to -autopartition, choose Manually edit partition -table from the menu and skip to the next -paragraph. Otherwise you will be asked if you want All -files in one partition, Separate partition -for home directories, or if you rather plan to have -a Multi-user system. All schemes have their -pros and cons, some of which are discussed in . 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. - - - - - - - - Partitioning scheme - Minimum space - Created partitions - - - - - - All files in one partition - 600MB - /, swap - - Separate partition for home directories - 500MB - - /, /home, swap - - - Multi-user system - 1GB - - /, /home, - /usr, /var, - /tmp, swap - - - - - - - -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 -Finished partitioning from the menu to use -what it set up. - - - -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 swap -and one for the root filesystem (which must be -mounted as /). If you forget to mount the root -filesystem, partman won't let you continue until -you correct this issue. However, this situation should not happen, -because partman by default offers reasonable -defaults. - - - -Capabilities of partman 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. partman-ext3, -partman-xfs, or -partman-lvm). - - - -After you are satisfied with partitioning, select Finished -partitioning 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. - - - 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 @@ - - 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 @@ - - - - -Using the Shell and Viewing the Logs - - - -There is an Execute a Shell item on the menu. If the menu is not -available when you need to use the shell, press -Left Alt F2 (on a Mac -keyboard, Option F2 -) to get to the second virtual -console. That's the Alt key on the -left-hand side of the space bar, and the -F2 function key, at the same time. This is a separate -window running a Bourne shell clone called ash. - - - -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 ls /bin /sbin -/usr/bin /usr/sbin. The text editor is -nano. The shell has some nice features like -autocompletion and history. - - - -Use the menus to perform any task that they are able to do — 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 Left -Alt F1 to get back to menus, or -type exit if you used a menu item to open the -shell. - - - 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 @@ - - - - - Install the <command>SILO</command> Boot Loader - on a Hard Disk - - -The standard &architecture; boot loader is called silo. -It is documented in -/usr/share/doc/silo/. SILO is -similar in configuration and usage to LILO, with -a few exceptions. First of all, SILO allows you to -boot any kernel image on your drive, even if it is not listed in -/etc/silo.conf. This is because -SILO can actually read Linux partitions. Also, -/etc/silo.conf is read at boot time, so there is -no need to rerun silo after installing a new kernel -like you would with LILO. SILO -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. - - - -- cgit v1.2.3