From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 7 Oct 2005 19:51:38 +0000 Subject: move manual to top-level directory, split out of debian-installer package --- fi/using-d-i/modules/alpha/aboot-installer.xml | 19 ++ fi/using-d-i/modules/anna.xml | 2 + fi/using-d-i/modules/autopartkit.xml | 2 + fi/using-d-i/modules/base-installer.xml | 31 +++ fi/using-d-i/modules/baseconfig.xml | 17 ++ fi/using-d-i/modules/cdrom-checker.xml | 2 + fi/using-d-i/modules/cdrom-detect.xml | 2 + fi/using-d-i/modules/choose-mirror.xml | 17 ++ fi/using-d-i/modules/countrychooser.xml | 25 +++ fi/using-d-i/modules/ddetect.xml | 2 + fi/using-d-i/modules/hppa/palo-installer.xml | 20 ++ fi/using-d-i/modules/i386/grub-installer.xml | 26 +++ fi/using-d-i/modules/i386/lilo-installer.xml | 70 +++++++ fi/using-d-i/modules/ia64/elilo-installer.xml | 135 +++++++++++++ fi/using-d-i/modules/iso-scan.xml | 47 +++++ fi/using-d-i/modules/kbd-chooser.xml | 73 +++++++ fi/using-d-i/modules/languagechooser.xml | 25 +++ fi/using-d-i/modules/localechooser.xml | 67 +++++++ fi/using-d-i/modules/lowmem.xml | 21 ++ fi/using-d-i/modules/lvmcfg.xml | 95 +++++++++ fi/using-d-i/modules/mdcfg.xml | 230 ++++++++++++++++++++++ fi/using-d-i/modules/mips/arcboot-installer.xml | 69 +++++++ fi/using-d-i/modules/mipsel/colo-installer.xml | 2 + fi/using-d-i/modules/mipsel/delo-installer.xml | 76 +++++++ fi/using-d-i/modules/netcfg.xml | 58 ++++++ fi/using-d-i/modules/network-console.xml | 107 ++++++++++ fi/using-d-i/modules/nobootloader.xml | 28 +++ fi/using-d-i/modules/os-prober.xml | 37 ++++ fi/using-d-i/modules/partconf.xml | 2 + fi/using-d-i/modules/partitioner.xml | 3 + fi/using-d-i/modules/partman.xml | 199 +++++++++++++++++++ fi/using-d-i/modules/powerpc/quik-installer.xml | 15 ++ fi/using-d-i/modules/powerpc/yaboot-installer.xml | 17 ++ fi/using-d-i/modules/prebaseconfig.xml | 23 +++ fi/using-d-i/modules/s390/dasd.xml | 2 + fi/using-d-i/modules/s390/netdevice.xml | 2 + fi/using-d-i/modules/s390/zipl-installer.xml | 16 ++ fi/using-d-i/modules/save-logs.xml | 24 +++ fi/using-d-i/modules/shell.xml | 41 ++++ fi/using-d-i/modules/sparc/silo-installer.xml | 25 +++ 40 files changed, 1674 insertions(+) create mode 100644 fi/using-d-i/modules/alpha/aboot-installer.xml create mode 100644 fi/using-d-i/modules/anna.xml create mode 100644 fi/using-d-i/modules/autopartkit.xml create mode 100644 fi/using-d-i/modules/base-installer.xml create mode 100644 fi/using-d-i/modules/baseconfig.xml create mode 100644 fi/using-d-i/modules/cdrom-checker.xml create mode 100644 fi/using-d-i/modules/cdrom-detect.xml create mode 100644 fi/using-d-i/modules/choose-mirror.xml create mode 100644 fi/using-d-i/modules/countrychooser.xml create mode 100644 fi/using-d-i/modules/ddetect.xml create mode 100644 fi/using-d-i/modules/hppa/palo-installer.xml create mode 100644 fi/using-d-i/modules/i386/grub-installer.xml create mode 100644 fi/using-d-i/modules/i386/lilo-installer.xml create mode 100644 fi/using-d-i/modules/ia64/elilo-installer.xml create mode 100644 fi/using-d-i/modules/iso-scan.xml create mode 100644 fi/using-d-i/modules/kbd-chooser.xml create mode 100644 fi/using-d-i/modules/languagechooser.xml create mode 100644 fi/using-d-i/modules/localechooser.xml create mode 100644 fi/using-d-i/modules/lowmem.xml create mode 100644 fi/using-d-i/modules/lvmcfg.xml create mode 100644 fi/using-d-i/modules/mdcfg.xml create mode 100644 fi/using-d-i/modules/mips/arcboot-installer.xml create mode 100644 fi/using-d-i/modules/mipsel/colo-installer.xml create mode 100644 fi/using-d-i/modules/mipsel/delo-installer.xml create mode 100644 fi/using-d-i/modules/netcfg.xml create mode 100644 fi/using-d-i/modules/network-console.xml create mode 100644 fi/using-d-i/modules/nobootloader.xml create mode 100644 fi/using-d-i/modules/os-prober.xml create mode 100644 fi/using-d-i/modules/partconf.xml create mode 100644 fi/using-d-i/modules/partitioner.xml create mode 100644 fi/using-d-i/modules/partman.xml create mode 100644 fi/using-d-i/modules/powerpc/quik-installer.xml create mode 100644 fi/using-d-i/modules/powerpc/yaboot-installer.xml create mode 100644 fi/using-d-i/modules/prebaseconfig.xml create mode 100644 fi/using-d-i/modules/s390/dasd.xml create mode 100644 fi/using-d-i/modules/s390/netdevice.xml create mode 100644 fi/using-d-i/modules/s390/zipl-installer.xml create mode 100644 fi/using-d-i/modules/save-logs.xml create mode 100644 fi/using-d-i/modules/shell.xml create mode 100644 fi/using-d-i/modules/sparc/silo-installer.xml (limited to 'fi/using-d-i/modules') diff --git a/fi/using-d-i/modules/alpha/aboot-installer.xml b/fi/using-d-i/modules/alpha/aboot-installer.xml new file mode 100644 index 000000000..2d58e0f74 --- /dev/null +++ b/fi/using-d-i/modules/alpha/aboot-installer.xml @@ -0,0 +1,19 @@ + + + + + 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/fi/using-d-i/modules/anna.xml b/fi/using-d-i/modules/anna.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/anna.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/autopartkit.xml b/fi/using-d-i/modules/autopartkit.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/autopartkit.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/base-installer.xml b/fi/using-d-i/modules/base-installer.xml new file mode 100644 index 000000000..a6dbfe615 --- /dev/null +++ b/fi/using-d-i/modules/base-installer.xml @@ -0,0 +1,31 @@ + + + + + Base System Installation + + + +During the Base installation, package unpacking and setup messages are +redirected to tty3. You can access this +terminal by pressing +Left AltF3; +get back to the main installer process with +Left AltF1. + + + + +The unpack/setup messages generated by the base installation are saved in +/var/log/messages when the installation is +performed over a serial console. + + + +As part of the installation, a Linux kernel will be installed. At the default +priority, the installer will choose one for you that best matches your +hardware. In lower priority modes, you will be able to choose from a list +of available kernels. + + + diff --git a/fi/using-d-i/modules/baseconfig.xml b/fi/using-d-i/modules/baseconfig.xml new file mode 100644 index 000000000..a189aa11d --- /dev/null +++ b/fi/using-d-i/modules/baseconfig.xml @@ -0,0 +1,17 @@ + + + + + Running <command>base-config</command> From Within &d-i; + + + +It is possible to configure the base system within the first stage +installer (before rebooting from the hard drive), by running +base-config in a chroot +environment. This is mainly useful for testing the installer and +should normally be avoided. + + + + diff --git a/fi/using-d-i/modules/cdrom-checker.xml b/fi/using-d-i/modules/cdrom-checker.xml new file mode 100644 index 000000000..d4c2f588b --- /dev/null +++ b/fi/using-d-i/modules/cdrom-checker.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/cdrom-detect.xml b/fi/using-d-i/modules/cdrom-detect.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/cdrom-detect.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/choose-mirror.xml b/fi/using-d-i/modules/choose-mirror.xml new file mode 100644 index 000000000..746804ecd --- /dev/null +++ b/fi/using-d-i/modules/choose-mirror.xml @@ -0,0 +1,17 @@ + + + + \ No newline at end of file diff --git a/fi/using-d-i/modules/countrychooser.xml b/fi/using-d-i/modules/countrychooser.xml new file mode 100644 index 000000000..4fd8dc907 --- /dev/null +++ b/fi/using-d-i/modules/countrychooser.xml @@ -0,0 +1,25 @@ + + + + + + Country selection + + + +If you selected a language in which has +more than one country associated with it (true for Chinese, English, +French, and many other languages), you can specify the country here. +If you choose Other at the bottom of the list, +you will be presented with a list of all countries, grouped by continent. + + + +This selection will be used later in the installation process to pick the +default timezone and a Debian mirror appropriate for your geographic +location. If the defaults proposed by the installer are not suitable, you +can make a different choice. The selected country, together with the selected +language, may also affect locale settings for your new Debian system. + + + diff --git a/fi/using-d-i/modules/ddetect.xml b/fi/using-d-i/modules/ddetect.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/ddetect.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/hppa/palo-installer.xml b/fi/using-d-i/modules/hppa/palo-installer.xml new file mode 100644 index 000000000..84a3608e8 --- /dev/null +++ b/fi/using-d-i/modules/hppa/palo-installer.xml @@ -0,0 +1,20 @@ + + + + + <command>palo</command>-installer + + +The bootloader on PA-RISC is palo. +PALO is similar in configuration and usage to +LILO, with a few exceptions. First of all, +PALO allows you to boot any kernel image on your +boot partition. This is because PALO can actually +read Linux partitions. + + + +hppa FIXME ( need more info ) + + + diff --git a/fi/using-d-i/modules/i386/grub-installer.xml b/fi/using-d-i/modules/i386/grub-installer.xml new file mode 100644 index 000000000..64e1e7ffb --- /dev/null +++ b/fi/using-d-i/modules/i386/grub-installer.xml @@ -0,0 +1,26 @@ + + + + + Install the <command>Grub</command> Boot Loader + on a Hard Disk + + +The main &architecture; boot loader is called grub. +Grub is a flexible and robust boot loader and a good default choice for +newbies and old hands alike. + + + +By default, grub will be installed into the Master Boot Record (MBR), where +it will take over complete control of the boot process. If you prefer, you +can install it elsewhere. See the grub manual for complete information. + + + +If you do not want to install grub at all, use the Back button to get to +the main menu, and from there select whatever bootloader you would like to +use. + + + diff --git a/fi/using-d-i/modules/i386/lilo-installer.xml b/fi/using-d-i/modules/i386/lilo-installer.xml new file mode 100644 index 000000000..30726d83a --- /dev/null +++ b/fi/using-d-i/modules/i386/lilo-installer.xml @@ -0,0 +1,70 @@ + + + + + Install the <command>LILO</command> Boot Loader + on a Hard Disk + + +The second &architecture; boot loader is called LILO. +It is an old complex program which offers lots of functionality, +including DOS, Windows, and OS/2 boot management. Please carefully +read the instructions in the directory +/usr/share/doc/lilo/ if you have special needs; +also see the LILO mini-HOWTO. + + + + +Currently the LILO installation will only create menu entries for other +operating systems if these can be chainloaded. +This means you may have to manually add a menu entry for operating +systems like GNU/Linux and GNU/Hurd after the installation. + + + + +&d-i; presents you three choices where to install the +LILO boot loader: + + + +Master Boot Record (MBR) + +This way the LILO will take complete control of the +boot process. + + + +new Debian partition + +Choose this if you want to use another boot +manager. LILO will install itself at the beginning +of the new Debian partition and it will serve as a secondary boot +loader. + + + +Other choice + +Useful for advanced users who want to install LILO +somewhere else. In this case you will be asked for desired +location. You can use devfs style names, such as those that start with +/dev/ide, /dev/scsi, and +/dev/discs, as well as traditional names, such as +/dev/hda or /dev/sda. + + + + + + +If you can no longer boot into Windows 9x (or DOS) after this step, +you'll need to use a Windows 9x (MS-DOS) boot disk and use the +fdisk /mbr command to reinstall the MS-DOS +master boot record — however, this means that you'll need to use +some other way to get back into Debian! For more information on this +please read . + + + diff --git a/fi/using-d-i/modules/ia64/elilo-installer.xml b/fi/using-d-i/modules/ia64/elilo-installer.xml new file mode 100644 index 000000000..7953befe6 --- /dev/null +++ b/fi/using-d-i/modules/ia64/elilo-installer.xml @@ -0,0 +1,135 @@ + + + + + Install the <command>ELILO</command> Boot Loader + on a Hard Disk + + +The &architecture; boot loader is called elilo. +It is modeled on the lilo 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 EFI Boot Manager +menu in the firmware to point to the files in the EFI partition. +The elilo boot loader is really in two parts. +The /usr/sbin/elilo command manages the partition and +copies file into it. +The elilo.efi program is copied into the EFI +partition and then run by the EFI Boot Manager to actually +do the work of loading and starting the Linux kernel. + + + +The elilo 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 +root filesystem. + + + + Choose the correct partition! + + + +The criteria for selecting a partition is that it is FAT format +filesystem with its boot 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 elilo may format the partition during +the installation, erasing any previous contents! + + + + + + + EFI Partition Contents + + + +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 +root filesystem. +It is normally not mounted on a running system as it is only needed +by the EFI Boot Manager to load the system and the +installer part of the elilo writes to the filesystem +directly. +The /usr/sbin/elilo utility writes the following files +into the efi/debian directory of the EFI +partition during the installation. +Note that the EFI Boot Manager would find these files +using the path fsn:\efi\debian. +There may be other files in this filesystem as well over time as +the system is updated or re-configured. + + + + + + +elilo.conf + + +This is the configuration file read by the boot loader when it starts. +It is a copy of the /etc/elilo.conf with +the filenames re-written to refer to files in the EFI partition. + + + + +elilo.efi + + +This is the boot loader program that the EFI Boot Manager +runs to boot the system. +It is the program behind the Debian GNU/Linux +menu item of the EFI Boot Manager command menu. + + + + +initrd.img + + +This is the initial root filesystem used to boot the kernel. +It is a copy of the file referenced in the +/etc/elilo.conf. +In a standard Debian installation it would be the file in +/boot pointed to by the symbolic link +/initrd.img. + + + + +readme.txt + + +This is a small text file warning you that the contents of the +directory are managed by the elilo and that +any local changes would be lost at the next time +/usr/sbin/elilo is run. + + + + +vmlinuz + + +This is the compressed kernel itself. +It is a copy of the file referenced in the +/etc/elilo.conf. +In a standard Debian installation it would be the file in +/boot pointed to by the symbolic link +/vmlinuz. + + + + + + diff --git a/fi/using-d-i/modules/iso-scan.xml b/fi/using-d-i/modules/iso-scan.xml new file mode 100644 index 000000000..5d5a055d4 --- /dev/null +++ b/fi/using-d-i/modules/iso-scan.xml @@ -0,0 +1,47 @@ + + + + + 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 a 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 a more thorough search. This pass doesn't just look 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 is named correctly (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/fi/using-d-i/modules/kbd-chooser.xml b/fi/using-d-i/modules/kbd-chooser.xml new file mode 100644 index 000000000..6024762ee --- /dev/null +++ b/fi/using-d-i/modules/kbd-chooser.xml @@ -0,0 +1,73 @@ + + + + + Choosing a Keyboard + + + +Keyboards are often tailored to the characters used in a language. +Select a layout that conforms to the keyboard you are using, or +select something close if the keyboard layout you want +isn't represented. Once the system installation is complete, you'll be +able to select a keyboard layout from a wider range of choices (run +kbdconfig as root after you have completed the +installation). + + + +Move the highlight to the keyboard selection you desire and press +&enterkey;. Use the arrow keys to move the highlight — they are +in the same place in all national language keyboard layouts, so they +are independent of the keyboard configuration. An 'extended' keyboard +is one with F1 through F10 keys +along the top row. + + + +On DECstations there is currently no loadable keymap available, +so you have to skip the keyboard selection and keep the default +kernel keymap (LK201 US). This may change in the future as it +depends on further Linux/MIPS kernel development. + + + +There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us +(Apple USB) layout will place the Alt function on the +Command/Apple key (in the keyboard position next to +the space key similar to Alt on +PC keyboards), while the qwerty/us (Standard) layout will place the +Alt function on the Option key (engraved with 'alt' +on most Mac keyboards). In other respects the two layouts are similar. + + + + + +If you are installing on a system that has a Sun USB keyboard and have +booted the installer with the default 2.4 kernel, the keyboard will not +be identified correctly by the installation system. The installer will show +you a list of Sun type keymaps to choose from, but selecting one of these +will result in a non-working keyboard. If you are installing with the 2.6 +kernel, there is no problem. + + + +To get a working keyboard, you should boot the installer with parameter +debconf/priority=medium. When you get to keyboard +selection + + +If you are installing at default priority you should use the Go +Back button to return to the installer menu when you are shown +the list of Sun type keymaps. + + +, choose No keyboard to configure if you have a +keyboard with an American (US) layout, or choose USB keyboard +if you have a keyboard with a localized layout. Selecting No keyboard +to configure will leave the kernel keymap in place, which is correct +for US keyboards. + + + diff --git a/fi/using-d-i/modules/languagechooser.xml b/fi/using-d-i/modules/languagechooser.xml new file mode 100644 index 000000000..fd64d9b31 --- /dev/null +++ b/fi/using-d-i/modules/languagechooser.xml @@ -0,0 +1,25 @@ + + + + + + Language selection + + + +As the first step of the installation, select the language in which +you want the installation process to proceed. The language names +are listed in both English (left side) and in the language itself +(right side); the names on the right side are also shown in the proper +script for the language. The list is sorted on the English names. + + + +The language you choose will be used for the rest of the installation +process, provided a translation of the different dialogs is available. +If no valid translation is available for the selected language, the +installer will default to English. The selected language will also be +used to help select a suitable keyboard layout. + + + diff --git a/fi/using-d-i/modules/localechooser.xml b/fi/using-d-i/modules/localechooser.xml new file mode 100644 index 000000000..6886acd83 --- /dev/null +++ b/fi/using-d-i/modules/localechooser.xml @@ -0,0 +1,67 @@ + + + + + + Selecting Localization Options + + + +In most cases the first questions you will be asked concern the selection +of localization options to be used both for the installation and for the +installed system. The localization options consist of language, country +and locales. + + + +The language you choose will be used for the rest of the installation +process, provided a translation of the different dialogs is available. +If no valid translation is available for the selected language, the +installer will default to English. + + + +The selected country will be used later in the installation process to +pick the default timezone and a Debian mirror appropriate for your +geographic location. Language and country together will be used to set +the default locale for your system and to help select your keyboard. + + + +You will first be asked to select your preferred language. The language +names are listed in both English (left side) and in the language itself +(right side); the names on the right side are also shown in the proper +script for the language. The list is sorted on the English names. +At the top of the list is an extra option that allows you to select the +C locale instead of a language. Choosing the C +locale will result in the installation proceding in English; the installed +system will have no localization support as the locales +package will not be installed. + + + +If you selected a language that is recognized as an official language for +more than one country + + + +In technical terms: where multiple locales exist for that language with +differing country codes. + + + +, you will next be asked to select a country. +If you choose Other at the bottom of the list, +you will be presented with a list of all countries, grouped by continent. +If the language has only one country associated with it, that country +will be selected automatically. + + + +A default locale will be selected based on the selected language and country. +If you are installing at medium or low priority, you will have the option +of selecting a different default locale and of selecting additional locales to +be generated for the installed system. + + + diff --git a/fi/using-d-i/modules/lowmem.xml b/fi/using-d-i/modules/lowmem.xml new file mode 100644 index 000000000..15cb78f91 --- /dev/null +++ b/fi/using-d-i/modules/lowmem.xml @@ -0,0 +1,21 @@ + + + + + Check available memory + + + +One of the first things &d-i; does, is to check available memory. +If the available memory is limited, this component will make some +changes in the installation process which hopefully will allow +you to install &debian; on your system. + + + +During a low memory install, not all components will be available. +One of the limitations is that you won't be able to choose a +language for the installation. + + + \ No newline at end of file diff --git a/fi/using-d-i/modules/lvmcfg.xml b/fi/using-d-i/modules/lvmcfg.xml new file mode 100644 index 000000000..f5ea056bb --- /dev/null +++ b/fi/using-d-i/modules/lvmcfg.xml @@ -0,0 +1,95 @@ + + + + + Configuring Logical Volume Manager (LVM) + + +If you are working with computers at the level of system administrator +or advanced user, you have surely seen the situation +where some disk partition (usually the most important one) was short on +space, while some other partition was grossly underused and you had to +manage this situation with moving stuff around, symlinking, etc. + + + +To avoid the described situation you can use Logical Volume Manager +(LVM). Simply said, with LVM you can combine your partitions +(physical volumes in LVM lingo) to form +a virtual disc (so called volume group), which +can then be divided into virtual partitions (logical +volumes). The point is that logical volumes (and of course +underlying volume groups) can span across several physical discs. + + + +Now when you realize you need more space for your old 160GB +/home partition, you can simply add a new 300GB +disc to the computer, join it with your existing volume group and then +resize the logical volume which holds your /home +filesystem and voila — your users have some room again on their +renewed 460GB partition. This example is of course a bit +oversimplified. If you haven't read it yet, you should consult the +LVM HOWTO. + + + +LVM setup in &d-i; is quite simple. At first, you have to mark your +partitions to be used as physical volumes for LVM. (This is done in +partman in the Partition +settings menu where you should select +Use as: physical volume for +LVM .) Then start the +lvmcfg module (either directly from +partman or from the &d-i;'s main menu) and combine +physical volumes to volume group(s) under the Modify +volume groups (VG) menu. After that, you should create +logical volumes on the top of volume groups from the menu +Modify logical volumes (LV). + + + +There is no widely accepted standard to identify partitions containing +LVM data on Apple Power Macintosh hardware. On this particular +hardware, the above procedure for creating physical volumes and volume +groups will not work. There is a good workaround for this limitation, +provided you are familiar with the underlying LVM tools. + + + +To install using logical volumes on Power Macintosh hardware you +should create all the disk partitions for your logical volumes as +usual. In the Partition settings menu you should +choose Use as: Do Not +Use for these partitions (you will not be +offered the option to use the partition as a physical volume). When +you are done with creating all your partitions, you should start the +logical volume manager as usual. However, since no physical volumes +have been created you must now access the command shell available on +the second virtual terminal (see ) and create +them manually. + + + +Use the pvcreate command at the shell command prompt +to create a physical volume on each of your chosen partitions. Then use +the vgcreate command to create each volume group +you want. You can safely ignore any errors about incorrect metadata +area header checksums and fsync failures while doing this. When you +have finished creating all your volume groups, you should go back to +the first virtual terminal and skip directly to the +lvmcfg menu items for logical volume +management. You will see your volume groups and you can create the +logical volumes you need as usual. + + + + + +After returning from lvmcfg back to +partman, you will see any created logical volumes +in the same way as ordinary partitions (and you should treat them like +that). + + + diff --git a/fi/using-d-i/modules/mdcfg.xml b/fi/using-d-i/modules/mdcfg.xml new file mode 100644 index 000000000..049fb21ea --- /dev/null +++ b/fi/using-d-i/modules/mdcfg.xml @@ -0,0 +1,230 @@ + + + + + Configuring Multidisk Device (Software RAID) + + +If you have more than one harddrive + +To be honest, you can construct MD device even from partitions +residing on single physical drive, but that won't bring you anything +useful. + + in your computer, you can use +mdcfg to setup your drives for increased +performance and/or better reliability of your data. The result is +called Multidisk Device (or after its most +famous variant software RAID). + + + +MD is basically a bunch of partitions located on different disks and +combined together to form a logical device. This +device can then be used like an ordinary partition (i.e. in +partman you can format it, assign a mountpoint, +etc.). + + + +The benefit you gain depends on a type of a MD device you are +creating. Currently supported are: + + + + +RAID0 + +Is mainly aimed at performance. RAID0 splits all incoming data into +stripes and distributes them equally over each +disk in the array. This can increase the speed of read/write +operations, but when one of the disks fails, you will loose +everything (part of the information is still on +the healthy disk(s), the other part was on the +failed disk). + + + +The typical use for RAID0 is a partition for video editing. + + + + + +RAID1 + +Is suitable for setups where reliability is the first concern. It +consists of several (usually two) equally sized partitions where every +partition contains exactly the same data. This essentially means three +things. First, if one of your disks fails, you still have the data +mirrored on the remaining disks. Second, you can use only a fraction +of the available capacity (more precisely, it is the size of the +smallest partition in the RAID). Third, file reads are load balanced among +the disks, which can improve performance on a server, such as a file +server, that tends to be loaded with more disk reads than writes. + + + +Optionally you can have a spare disk in the array which will take the +place of the failed disk in the case of failure. + + + + + +RAID5 + +Is a good compromise between speed, reliability and data redundancy. +RAID5 splits all incomming data into stripes and distributes them +equally on all but one disks (similar to RAID0). Unlike RAID0, RAID5 +also computes parity information, which gets +written on the remaining disk. The parity disk is not static (that +would be called RAID4), but is changing periodically, so the parity +information is distributed equally on all disks. When one of the +disks fails, the missing part of information can be computed from +remaining data and its parity. RAID5 must consist of at least three +active partitions. Optionally you can have a spare disk in the array +which will take the place of the failed disk in the case of failure. + + + +As you can see, RAID5 has similar degree of reliability like RAID1 +while achieving less redundancy. On the other hand it might be a bit +slower on write operation than RAID0 due to computation of parity +information. + + + + + +To sum it up: + + + + + + Type + Minimum Devices + Spare Device + Survives disk failure? + Available Space + + + + + + RAID0 + 2 + no + no + Size of the smallest partition multiplied by number of devices in RAID + + + + RAID1 + 2 + optional + yes + Size of the smallest partition in RAID + + + + RAID5 + 3 + optional + yes + + Size of the smallest partition multiplied by (number of devices in + RAID minus one) + + + + + + + +If you want to know the whole truth about Software RAID, have a look +at Software RAID HOWTO. + + + +There is no widely accepted standard to identify partitions containing +RAID data on Apple Power Macintosh hardware. This means that &d-i; +currently does not support setting up RAID on this platform. + + + + + +To create a MD device, you need to have the desired partitions it +should consist of marked for use in a RAID. (This is done in +partman in the Partition +settings menu where you should select +Use as: physical volume for +RAID .) + + + +Support for MD is a relatively new addition to the installer. +You may experience problems for some RAID levels and in combination +with some bootloaders if you try to use MD for the root +(/) filesystem. For experienced users, it may be +possible to work around some of these problems by executing some +configuration or installation steps manually from a shell. + + + +Next, you should choose Configure software +RAID from the main partman menu. +On the first screen of mdcfg simply select +Create MD device. You will be presented with +a list of supported types of MD devices, from which you should choose +one (e.g. RAID1). What follows depends on the type of MD you selected. + + + + + +RAID0 is simple — you will be issued with the list of available +RAID partitions and your only task is to select the partitions which +will form the MD. + + + + +RAID1 is a bit more tricky. First, you will be asked to enter the +number of active devices and the number of spare devices which will +form the MD. Next, you need to select from the list of available RAID +partitions those that will be active and then those that will be +spare. The count of selected partitions must be equal to the number +provided few seconds ago. Don't worry. If you make a mistake and +select different number of partitions, the &d-i; won't let you +continue until you correct the issue. + + + + +RAID5 has similar setup procedure as RAID1 with the exception that you +need to use at least three active partitions. + + + + + + +It is perfectly possible to have several types of MD at once. For +example if you have three 200 GB hard drives dedicated to MD, each +containing two 100 GB partitions, you can combine first partitions on +all three disk into the RAID0 (fast 300 GB video editing partition) +and use the other three partitions (2 active and 1 spare) for RAID1 +(quite reliable 100 GB partition for /home). + + + +After you setup MD devices to your liking, you can +Finish mdcfg to return +back to the partman to create filesystems on your +new MD devices and assign them the usual attributes like mountpoints. + + + diff --git a/fi/using-d-i/modules/mips/arcboot-installer.xml b/fi/using-d-i/modules/mips/arcboot-installer.xml new file mode 100644 index 000000000..13eba925e --- /dev/null +++ b/fi/using-d-i/modules/mips/arcboot-installer.xml @@ -0,0 +1,69 @@ + + + + + <command>arcboot</command>-installer + + +The boot loader on SGI Indys is arcboot. +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 /etc/arcboot.conf. Each +configuration has a unique name, +the default setup as created by the installer is linux. +After arcboot has been installed, the system can be booted from hard disk +by setting some firmware environment variables entering + + + setenv SystemPartition scsi(scsi)disk(disk)rdisk(0)partition(0) + setenv OSLoadPartition scsi(scsi)disk(disk)rdisk(0)partition(partnr) + setenv OSLoader arcboot + setenv OSLoadFilename config + setenv AutoLoad yes + + +on the firmware prompt, and then typing boot. + + + + + + scsi + + +is the SCSI bus to be booted from, this is 0 +for the onboard controllers + + + + + disk + + +is the SCSI ID of the hard disk on which arcboot is +installed + + + + + partnr + + +is the number of the partition on which +/etc/arcboot.conf resides + + + + + config + + +is the name of the configuration entry in +/etc/arcboot.conf, which is linux by +default. + + + + + + diff --git a/fi/using-d-i/modules/mipsel/colo-installer.xml b/fi/using-d-i/modules/mipsel/colo-installer.xml new file mode 100644 index 000000000..d4c2f588b --- /dev/null +++ b/fi/using-d-i/modules/mipsel/colo-installer.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/mipsel/delo-installer.xml b/fi/using-d-i/modules/mipsel/delo-installer.xml new file mode 100644 index 000000000..7325398ac --- /dev/null +++ b/fi/using-d-i/modules/mipsel/delo-installer.xml @@ -0,0 +1,76 @@ + + + + + <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/fi/using-d-i/modules/netcfg.xml b/fi/using-d-i/modules/netcfg.xml new file mode 100644 index 000000000..3584b8041 --- /dev/null +++ b/fi/using-d-i/modules/netcfg.xml @@ -0,0 +1,58 @@ + + + + + Configuring Network + + + +As you enter this step, if the system detects that you have more than +one network device, you'll be asked to choose which device will be +your primary network interface, i.e. the one +which you want to use for installation. The other interfaces won't be +configured at this time. You may configure additional interfaces after +installation is complete; see the +interfaces 5 + man page. + + + +By default, &d-i; tries to configure your computer's network +automatically via DHCP. If the DHCP probe succeeds, you are done. If the +probe fails, it may be caused by many factors ranging from unplugged +network cable, to a misconfigured DHCP setup. Or maybe you don't have +a DHCP server in your local network at all. For further explanation +check the error messages on the third console. In any case, you will +be asked if you want to retry, or if you want to perform manual +setup. DHCP servers are sometimes really slow in their responses, so +if you are sure everything is in place, try again. + + + +The manual network setup in turn asks you a number of questions about +your network, notably +IP address, +Netmask, +Gateway, +Name server addresses, and a +Hostname. +Moreover, if you have a wireless network interface, you will be asked +to provide your Wireless ESSID and +a WEP key. Fill in the answers from +. + + + +Some technical details you might, or might not, find handy: the +program assumes the network IP address is the bitwise-AND of your +system's IP address and your netmask. It will guess the broadcast +address is the bitwise OR of your system's IP address with the bitwise +negation of the netmask. It will also guess your gateway. If you +can't find any of these answers, use the system's guesses — you +can change them once the system has been installed, if necessary, by +editing /etc/network/interfaces. Alternatively, +you can install etherconf, which will step you +through your network setup. + + + diff --git a/fi/using-d-i/modules/network-console.xml b/fi/using-d-i/modules/network-console.xml new file mode 100644 index 000000000..505280b55 --- /dev/null +++ b/fi/using-d-i/modules/network-console.xml @@ -0,0 +1,107 @@ + + + + + Installation Over the Network + + + +One of the more interesting components is +network-console. 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 +.) + + + +This component is not loaded into the main installation menu by default, +so you have to explicitly ask for it. + +If you are installing from CD, you need to boot with medium priority or +otherwise invoke the main installation menu and choose Load +installer components from CD and from the list of +additional components select network-console: Continue +installation remotely using SSH. Successful load is +indicated by a new menu entry called Continue +installation remotely using SSH. + + + +For installations on &arch-title;, this is the default method after +setting up the network. + + + +After selecting this new entry, you +You 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 installer 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 person who will continue the +installation remotely. + + + +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. + + + +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: + + +$ ssh -l installer install_host + + +Where install_host 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. + + + +If you install several computers in turn and they happen to have the +same IP address or hostname, ssh 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 +~/.ssh/known_hosts and try again. + + + +After the login you will be presented with an initial screen where you +have two possibilities called Start menu and +Start shell. 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. + + + +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. + + + +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. + + + + diff --git a/fi/using-d-i/modules/nobootloader.xml b/fi/using-d-i/modules/nobootloader.xml new file mode 100644 index 000000000..439792b35 --- /dev/null +++ b/fi/using-d-i/modules/nobootloader.xml @@ -0,0 +1,28 @@ + + + + + Continue Without Boot Loader + + + +This option can be used to complete the installation even when no boot +loader is to be installed, either because the arch/subarch doesn't +provide one, or because none is desired (e.g. you will use existing +boot loader). This option is especially useful for +Macintosh, Atari, and Amiga systems, where the original operating system +must be maintained on the box and used to boot GNU/Linux. + + + +If you plan to manually configure your bootloader, you should check the +name of the installed kernel in /target/boot. +You should also check that directory for the presence of an +initrd; if one is present, you will probably have +to instruct your bootloader to use it. Other information you will need +are the disk and partition you selected for your / +filesystem and, if you chose to install /boot on a +separate partition, also your /boot filesystem. + + + diff --git a/fi/using-d-i/modules/os-prober.xml b/fi/using-d-i/modules/os-prober.xml new file mode 100644 index 000000000..4928d5769 --- /dev/null +++ b/fi/using-d-i/modules/os-prober.xml @@ -0,0 +1,37 @@ + + + + + Detecting other operating systems + + + +Before a boot loader is installed, the installer will attempt to probe for +other operating systems which are installed on the machine. If it finds a +supported operating system, you will be informed of this during the boot +loader installation step, and the computer will be configured to boot this +other operating system in addition to Debian. + + + +Note that multiple operating systems booting on a single machine is still +something of a black art. The automatic support for detecting and setting +up boot loaders to boot other operating systems varies by architecture and +even by subarchitecture. If it does not work you should consult your +boot manager's documentation for more information. + + + + + + + +The installer may fail to detect other operating systems if the partitions on +which they reside are mounted when the detection takes place. This may occur if +you select a mountpoint (e.g. /win) for a partition containing another operating +system in partman, or if you have mounted partitions manually +from a console. + + + + diff --git a/fi/using-d-i/modules/partconf.xml b/fi/using-d-i/modules/partconf.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/partconf.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/partitioner.xml b/fi/using-d-i/modules/partitioner.xml new file mode 100644 index 000000000..0dabd4a41 --- /dev/null +++ b/fi/using-d-i/modules/partitioner.xml @@ -0,0 +1,3 @@ + + + diff --git a/fi/using-d-i/modules/partman.xml b/fi/using-d-i/modules/partman.xml new file mode 100644 index 000000000..78fe131bb --- /dev/null +++ b/fi/using-d-i/modules/partman.xml @@ -0,0 +1,199 @@ + + + + + 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. + + + +If you choose guided partitioning, you will be able to choose from the +schemes listed in the table below. 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 + + Desktop machine + 500MB + + /, /home, swap + + + Multi-user workstation + 1GB + + /, /home, + /usr, /var, + /tmp, swap + + + + + + + +If you chose an automatic partitioning for your IA64 system, there +will be an additional partition, formatted as a FAT16 bootable filesystem, +for the EFI boot loader. +There is also an additional menu item in the formatting menu to manually +set up a partition as an EFI boot partition. + + + +If you chose an automatic partitioning for your Alpha system, an +additional, unformatted partition will be allocated at the beginning of +your disk to reserve this space for the aboot boot loader. + + + +After selecting a scheme, the next screen will show your new partition +table, including information on whether and how partitions will be +formatted and where they will be mounted. + + + +The list of partitions might look like this: + + + + IDE1 master (hda) - 6.4 GB WDC AC36400L + #1 primary 16.4 MB ext2 /boot + #2 primary 551.0 MB swap swap + #3 primary 5.8 GB ntfs + pri/log 8.2 MB FREE SPACE + + IDE1 slave (hdb) - 80.0 GB ST380021A + #1 primary 15.9 MB ext3 + #2 primary 996.0 MB fat16 + #3 primary 3.9 GB xfs /home + #5 logical 6.0 GB ext3 / + #6 logical 1.0 GB ext3 /var + #7 logical 498.8 MB ext3 + #8 logical 551.5 MB swap swap + #9 logical 65.8 GB ext2 + + +This example shows two IDE harddrives divided into several partitions; +the first disk has some free space. Each partition line consists of the +partition number, its type, size, optional flags, file system, and +mountpoint (if any). + + + +This concludes the guided partitioning. If you are satisfied with the +generated partition table, you can choose Finish +partitioning and write changes to disk from the menu to +implement the new partition table (as described at the end of this +section). If you are not happy, you can choose to Undo +changes to partitions, to run guided partitioning again +or modify the proposed changes as described below for manual partitioning. + + + +A similar screen to the one shown just above will be displayed if you +choose manual partitioning except that your existing partition table will +be shown and without the mount points. How to manually setup your partition +table and the usage of partitions by your new Debian system will be covered +in the remainder of this section. + + + +If you select a pristine disk which doesn't have neither partitions +nor free space on it, you will be offered to create a new partition +table (this is needed so you can create new partitions). After this +a new line entitled FREE SPACE should appear under the +selected disk. + + + +If you select some free space, you will be offered to create new +partition. You will have to answer a quick series of questions about +its size, type (primary or logical), and location (beginning or end of +the free space). After this, you will be presented with detailed +overview of your new partition. There are options like mountpoint, +mount options, bootable flag, or way of usage. If you don't like the +preselected defaults, feel free to change them to your liking. E.g. by +selecting the option Use as:, you can +choose different filesystem for this partition including the +possibility to use the partition for swap, software RAID, LVM, or not +use it at all. Other nice feature is the possibility to copy data from +existing partition onto this one. +When you are satisfied with your new partition, select +Done setting up the partition and you will be +thrown back to the partman's main screen. + + + +If you decide you want to change something about your partition, +simply select the partition, which will bring you to the partition +configuration menu. Because this is the same screen like when creating +a new partition, you can change the same set of options. One thing +which might not be very obvious at a first glance is that you can +resize the partition by selecting the item displaying the size of the +partition. Filesystems known to work are at least fat16, fat32, ext2, +ext3 and swap. This menu also allows you to delete a partition. + + + +Be sure to create at least two partitions: one for the +root filesystem (which must be mounted as +/) and one for swap. If you +forget to mount the root filesystem, partman won't +let you continue until you correct this issue. + + + +If you forget to select and format an EFI boot partition +partman will detect this and will not let you continue +until you allocate one. + + + +Capabilities of partman can be extended with installer +modules, but are dependent on your system's architecture. 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 Finish +partitioning and write changes to disk 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/fi/using-d-i/modules/powerpc/quik-installer.xml b/fi/using-d-i/modules/powerpc/quik-installer.xml new file mode 100644 index 000000000..ed6aa6a60 --- /dev/null +++ b/fi/using-d-i/modules/powerpc/quik-installer.xml @@ -0,0 +1,15 @@ + + + + + Install <command>Quik</command> on a Hard Disk + + +The boot loader for OldWorld Power Macintosh machines is +quik. You can also use it on CHRP. The installer +will attempt to set up quik automatically. The +setup has been known to work on 7200, 7300, and 7600 Powermacs, and on +some Power Computing clones. + + + diff --git a/fi/using-d-i/modules/powerpc/yaboot-installer.xml b/fi/using-d-i/modules/powerpc/yaboot-installer.xml new file mode 100644 index 000000000..4bba348fb --- /dev/null +++ b/fi/using-d-i/modules/powerpc/yaboot-installer.xml @@ -0,0 +1,17 @@ + + + + + Install <command>Yaboot</command> on a Hard Disk + + +Newer (mid 1998 and on) PowerMacs use yaboot as +their boot loader. The installer will set up yaboot +automatically, so all you need is a small 820k partition named +bootstrap with type +Apple_Bootstrap created back in the partitioning +component. If this step completes successfully then your disk should +now be bootable and OpenFirmware will be set to boot &debian;. + + + diff --git a/fi/using-d-i/modules/prebaseconfig.xml b/fi/using-d-i/modules/prebaseconfig.xml new file mode 100644 index 000000000..8ddd0905f --- /dev/null +++ b/fi/using-d-i/modules/prebaseconfig.xml @@ -0,0 +1,23 @@ + + + + + Finish the Installation and Reboot + + + +This is the last step in the initial Debian installation process. You will +be prompted to remove the boot media (CD, floppy, etc) that you used to +boot the installer. The installer will do any last minute tasks, and then +reboot into your new Debian system. + + + +Select the Finish the installation +menu item which will halt the system +because rebooting is not supported on &arch-title; in this case. You +then need to IPL GNU/Linux from the DASD which you selected for the +root filesystem during the first steps of the installation. + + + diff --git a/fi/using-d-i/modules/s390/dasd.xml b/fi/using-d-i/modules/s390/dasd.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/s390/dasd.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/s390/netdevice.xml b/fi/using-d-i/modules/s390/netdevice.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/fi/using-d-i/modules/s390/netdevice.xml @@ -0,0 +1,2 @@ + + diff --git a/fi/using-d-i/modules/s390/zipl-installer.xml b/fi/using-d-i/modules/s390/zipl-installer.xml new file mode 100644 index 000000000..61aa6465c --- /dev/null +++ b/fi/using-d-i/modules/s390/zipl-installer.xml @@ -0,0 +1,16 @@ + + + + + <command>zipl</command>-installer + + +The boot loader on &arch-title; is zipl. +ZIPL is similar in configuration and usage to +LILO, with a few exceptions. Please take a look at +LINUX for &arch-title; Device Drivers and Installation +Commands from IBM's developerWorks web site if you want to +know more about ZIPL. + + + diff --git a/fi/using-d-i/modules/save-logs.xml b/fi/using-d-i/modules/save-logs.xml new file mode 100644 index 000000000..497a4628b --- /dev/null +++ b/fi/using-d-i/modules/save-logs.xml @@ -0,0 +1,24 @@ + + + + + Saving the installation logs + + + +If the installation is successful, the logfiles created during +the installation process will be automatically saved to +/var/log/debian-installer/ on your new +Debian system. + + + +Choosing Save debug logs from the main +menu allows you to save the log files to a floppy +disk, network, hard disk, or other +media. This can be useful if you encounter fatal problems +during the installation and wish to study the logs on another system +or attach them to an installation report. + + + diff --git a/fi/using-d-i/modules/shell.xml b/fi/using-d-i/modules/shell.xml new file mode 100644 index 000000000..0e26048a0 --- /dev/null +++ b/fi/using-d-i/modules/shell.xml @@ -0,0 +1,41 @@ + + + + + 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 switch 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 and by typing help. 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/fi/using-d-i/modules/sparc/silo-installer.xml b/fi/using-d-i/modules/sparc/silo-installer.xml new file mode 100644 index 000000000..3ce2b6ac6 --- /dev/null +++ b/fi/using-d-i/modules/sparc/silo-installer.xml @@ -0,0 +1,25 @@ + + + + + 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 +alongside an existing SunOS/Solaris install. + + + -- cgit v1.2.3