1
# SOME DESCRIPTIVE TITLE.
2
# Copyright (C) YEAR Free Software Foundation, Inc.
3
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
8
"Project-Id-Version: PACKAGE VERSION\n"
9
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
10
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
11
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
12
"Language-Team: LANGUAGE <LL@li.org>\n"
14
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
15
"Content-Transfer-Encoding: ENCODING\n"
20
msgid "Using the Debian Installer"
26
msgid "How the Installer Works"
32
msgid "The Debian Installer consists of a number of special-purpose components to perform each installation task. Each component performs its task, asking the user questions as necessary to do its job. The questions themselves are given priorities, and the priority of questions to be asked is set when the installer is started."
38
msgid "When a default installation is performed, only essential (high priority) questions will be asked. This results in a highly automated installation process with little user interaction. Components are automatically run in sequence; which components are run depends mainly on the installation method you use and on your hardware. The installer will use default values for questions that are not asked."
44
msgid "If there is a problem, the user will see an error screen, and the installer menu may be shown in order to select some alternative action. If there are no problems, the user will never see the installer menu, but will simply answer questions for each component in turn. Serious error notifications are set to priority <quote>critical</quote> so the user will always be notified."
50
msgid "Some of the defaults that the installer uses can be influenced by passing boot arguments when &d-i; is started. If, for example, you wish to force static network configuration (DHCP is used by default if available), you could add the boot parameter <userinput>netcfg/disable_dhcp=true</userinput>. See <xref linkend=\"installer-args\"/> for available options."
56
msgid "Power users may be more comfortable with a menu-driven interface, where each step is controlled by the user rather than the installer performing each step automatically in sequence. To use the installer in a manual, menu-driven way, add the boot argument <userinput>debconf/priority=medium</userinput>."
62
msgid "If your hardware requires you to pass options to kernel modules as they are installed, you will need to start the installer in <quote>expert</quote> mode. This can be done by either using the <command>expert</command> command to start the installer or by adding the boot argument <userinput>debconf/priority=low</userinput>. Expert mode gives you full control over &d-i;."
68
msgid "The normal installer display is character-based (as opposed to the now more familiar graphical interface). The mouse is not operational in this environment. Here are the keys you can use to navigate within the various dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move <quote>backward</quote> between displayed buttons and selections. The <keycap>up</keycap> and <keycap>down</keycap> arrow select different items within a scrollable list, and also scroll the list itself. In addition, in long lists, you can type a letter to cause the list to scroll directly to the section with items starting with the letter you typed and use <keycap>Pg-Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The <keycap>space bar</keycap> selects an item such as a checkbox. Use &enterkey; to activate choices."
74
msgid "S/390 does not support virtual consoles. You may open a second and third ssh session to view the logs described below."
80
msgid "Error messages are redirected to the third console. You can access this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F3</keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing the <keycap>F3</keycap> function key); get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
86
msgid "These messages can also be found in <filename>/var/log/messages</filename>. After installation, this log is copied to <filename>/var/log/debian-installer/messages</filename> on your new system. Other installation messages may be found in <filename>/var/log/</filename> during the installation, and <filename>/var/log/debian-installer/</filename> after the computer has been booted into the installed system."
92
msgid "Components Introduction"
98
msgid "Here is a list of installer components with a brief description of each component's purpose. Details you might need to know about using a particular component are in <xref linkend=\"module-details\"/>."
110
msgid "Shows the list of components to the user during installer operation, and starts a component when it is selected. Main-menu's questions are set to priority medium, so if your priority is set to high or critical (high is the default), you will not see the menu. On the other hand, if there is an error which requires your intervention, the question priority may be downgraded temporarily to allow you to resolve the problem, and in that case the menu may appear."
116
msgid "You can get to the main menu by selecting the <quote>Back</quote> button repeatedly to back all the way out of the currently running component."
122
msgid "languagechooser"
128
msgid "Shows a list of languages and language variants. The installer will display messages in the chosen language, unless the translation for that language is not complete. When a translation is not complete, English messages are shown."
134
msgid "countrychooser"
140
msgid "Shows a list of countries. The user may choose the country he lives in."
146
msgid "localechooser"
152
msgid "Allows the user to select localization options for the installation and the installed system: language, country and locales. The installer will display messages in the selected language, unless the translation for that language is not complete in which case some messages may be shown in English."
164
msgid "Shows a list of keyboards, from which the user chooses the model which matches his own."
176
msgid "Automatically detects most of the system's hardware, including network cards, disk drives, and PCMCIA."
188
msgid "Looks for and mounts a Debian installation CD."
200
msgid "Configures the computer's network connections so it can communicate over the internet."
212
msgid "Looks for ISO file systems, which may be on a CD-ROM or on the hard drive."
218
msgid "choose-mirror"
224
msgid "Presents a list of Debian archive mirrors. The user may choose the source of his installation packages."
230
msgid "cdrom-checker"
236
msgid "Checks integrity of a CD-ROM. This way the user may assure him/herself that the installation CD-ROM was not corrupted."
248
msgid "Lowmem tries to detect systems with low memory and then does various tricks to remove unnecessary parts of &d-i; from the memory (at the cost of some features)."
260
msgid "Anna's Not Nearly APT. Installs packages which have been retrieved from the chosen mirror or CD."
272
msgid "Allows the user to partition disks attached to the system, create file systems on the selected partitions, and attach them to the mountpoints. Included are also interesting features like a fully automatic mode or LVM support. This is the preferred partitioning tool in Debian."
284
msgid "Automatically partitions an entire disk according to preset user preferences."
296
msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
308
msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
320
msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
332
msgid "Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant Array of Inexpensive Disks). This Software RAID is usually superior to the cheap IDE (pseudo hardware) RAID controllers found on newer motherboards."
338
msgid "base-installer"
344
msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted."
356
msgid "Detects currently installed operating systems on the computer and passes this information to the bootloader-installer, which may offer you an ability to add discovered operating systems to the bootloader's start menu. This way the user could easily choose at the boot time which operating system to start."
362
msgid "bootloader-installer"
368
msgid "Installs a boot loader program on the hard disk, which is necessary for the computer to start up using Linux without using a floppy or CD-ROM. Many boot loaders allow the user to choose an alternate operating system each time the computer boots."
380
msgid "Provides dialogs for setting up the base system packages according to user preferences. This is normally done after rebooting the computer; it is the <quote>first run</quote> of the new Debian system."
392
msgid "Allows the user to execute a shell from the menu, or in the second console."
410
msgid "Provides a way for the user to record information on a floppy disk<phrase condition=\"etch\">, network, hard disk, or other media</phrase> when trouble is encountered, in order to accurately report installer software problems to Debian developers later."
416
msgid "Using Individual Components"
422
msgid "In this section we will describe each installer component in detail. The components have been grouped into stages that should be recognizable for users. They are presented in the order they appear during the install. Note that not all modules will be used for every installation; which modules are actually used depends on the installation method you use and on your hardware."
428
msgid "Setting up Debian Installer and Hardware Configuration"
434
msgid "Let's assume the Debian Installer has booted and you are facing its first screen. At this time, the capabilities of &d-i; are still quite limited. It doesn't know much about your hardware, preferred language, or even the task it should perform. Don't worry. Because &d-i; is quite clever, it can automatically probe your hardware, locate the rest of its components and upgrade itself to a capable installation system. However, you still need to help &d-i; with some information it can't determine automatically (like selecting your preferred language, keyboard layout or desired network mirror)."
440
msgid "You will notice that &d-i; performs <firstterm>hardware detection</firstterm> several times during this stage. The first time is targeted specifically at the hardware needed to load installer components (e.g. your CD-ROM or network card). As not all drivers may be available during this first run, hardware detection needs to be repeated later in the process."
446
msgid "Check available memory"
452
msgid "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."
458
msgid "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."
464
msgid "Language selection"
470
msgid "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."
476
msgid "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."
482
msgid "Country selection"
488
msgid "If you selected a language in <xref linkend=\"lang-chooser\"/> 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 <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent."
494
msgid "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."
500
msgid "Selecting Localization Options"
506
msgid "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."
512
msgid "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."
518
msgid "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."
524
msgid "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 <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed."
530
msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will next be asked to select a country. If you choose <guimenuitem>Other</guimenuitem> 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."
536
msgid "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."
542
msgid "Choosing a Keyboard"
548
msgid "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 <command>kbdconfig</command> as root after you have completed the installation)."
554
msgid "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 <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row."
560
msgid "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."
566
msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar."
572
msgid "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."
578
msgid "To get a working keyboard, you should boot the installer with parameter <userinput>debconf/priority=medium</userinput>. When you get to keyboard selection<footnote> <para> If you are installing at default priority you should use the <userinput>Go Back</userinput> button to return to the installer menu when you are shown the list of Sun type keymaps. </para> </footnote>, choose <quote>No keyboard to configure</quote> if you have a keyboard with an American (US) layout, or choose <quote>USB keyboard</quote> if you have a keyboard with a localized layout. Selecting <quote>No keyboard to configure</quote> will leave the kernel keymap in place, which is correct for US keyboards."
584
msgid "Looking for the Debian Installer ISO Image"
590
msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the Debian Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this."
596
msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image."
602
msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem."
608
msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console."
614
msgid "Configuring Network"
620
msgid "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 <emphasis>primary</emphasis> 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 <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page."
626
msgid "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."
632
msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>."
638
msgid "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 <filename>/etc/network/interfaces</filename>. Alternatively, you can install <classname>etherconf</classname>, which will step you through your network setup."
644
msgid "Partitioning and Mount Point Selection"
650
msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related issues like LVM or RAID devices."
656
msgid "Partitioning Your Disks"
662
msgid "Now it is time to partition your disks. If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
668
msgid "First you will be given the opportunity to automatically partition either an entire drive, or free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manually edit partition table</guimenuitem> from the menu."
674
msgid "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 <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind, that guided partitioning needs certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail."
680
msgid "Partitioning scheme"
686
msgid "Minimum space"
692
msgid "Created partitions"
698
msgid "All files in one partition"
710
msgid "<filename>/</filename>, swap"
716
msgid "Desktop machine"
728
msgid "<filename>/</filename>, <filename>/home</filename>, swap"
734
msgid "Multi-user workstation"
740
msgid "<entry>1GB</entry>"
746
msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
752
msgid "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."
758
msgid "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."
764
msgid "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."
771
"The list of partitions might look like this: <informalexample><screen>\n"
772
" IDE1 master (hda) - 6.4 GB WDC AC36400L\n"
773
" #1 primary 16.4 MB ext2 /boot\n"
774
" #2 primary 551.0 MB swap swap\n"
775
" #3 primary 5.8 GB ntfs\n"
776
" pri/log 8.2 MB FREE SPACE\n"
778
" IDE1 slave (hdb) - 80.0 GB ST380021A\n"
779
" #1 primary 15.9 MB ext3\n"
780
" #2 primary 996.0 MB fat16\n"
781
" #3 primary 3.9 GB xfs /home\n"
782
" #5 logical 6.0 GB ext3 /\n"
783
" #6 logical 1.0 GB ext3 /var\n"
784
" #7 logical 498.8 MB ext3\n"
785
" #8 logical 551.5 MB swap swap\n"
786
" #9 logical 65.8 GB ext2\n"
787
"</screen></informalexample> 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)."
793
msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> 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 <guimenuitem>Undo changes to partitions</guimenuitem>, to run guided partitioning again or modify the proposed changes as described below for manual partitioning."
799
msgid "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."
805
msgid "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 <quote>FREE SPACE</quote> should appear under the selected disk."
811
msgid "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 <guimenuitem>Use as:</guimenuitem>, 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 <guimenuitem>Done setting up the partition</guimenuitem> and you will be thrown back to the <command>partman</command>'s main screen."
817
msgid "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."
823
msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue."
829
msgid "If you forget to select and format an EFI boot partition <command>partman</command> will detect this and will not let you continue until you allocate one."
835
msgid "Capabilities of <command>partman</command> 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. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)."
841
msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested."
844
#: using-d-i.xml:1007
847
msgid "Configuring Logical Volume Manager (LVM)"
850
#: using-d-i.xml:1008
853
msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> 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."
856
#: using-d-i.xml:1016
859
msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disc (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical discs."
862
#: using-d-i.xml:1026
865
msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> 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 <filename>/home</filename> 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 <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>."
868
#: using-d-i.xml:1037
871
msgid "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 <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>.) Then start the <command>lvmcfg</command> module (either directly from <command>partman</command> or from the &d-i;'s main menu) and combine physical volumes to volume group(s) under the <guimenuitem>Modify volume groups (VG)</guimenuitem> menu. After that, you should create logical volumes on the top of volume groups from the menu <guimenuitem>Modify logical volumes (LV)</guimenuitem>."
874
#: using-d-i.xml:1052
877
msgid "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."
880
#: using-d-i.xml:1060
883
msgid "To install using logical volumes on Power Macintosh hardware you should create all the disk partitions for your logical volumes as usual. In the <guimenu>Partition settings</guimenu> menu you should choose <menuchoice><guimenu>Use as:</guimenu> <guimenuitem>Do Not Use</guimenuitem></menuchoice> 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 <xref linkend=\"shell\"/>) and create them manually."
886
#: using-d-i.xml:1074
889
msgid "Use the <command>pvcreate</command> command at the shell command prompt to create a physical volume on each of your chosen partitions. Then use the <command>vgcreate</command> 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 <command>lvmcfg</command> menu items for logical volume management. You will see your volume groups and you can create the logical volumes you need as usual."
892
#: using-d-i.xml:1089
895
msgid "After returning from <command>lvmcfg</command> back to <command>partman</command>, you will see any created logical volumes in the same way as ordinary partitions (and you should treat them like that)."
898
#: using-d-i.xml:1104
901
msgid "Configuring Multidisk Device (Software RAID)"
904
#: using-d-i.xml:1105
907
msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)."
910
#: using-d-i.xml:1119
913
msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)."
916
#: using-d-i.xml:1127
919
msgid "The benefit you gain depends on a type of a MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> 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 <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> 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. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> 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 <firstterm>parity</firstterm> 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. </para><para> 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. </para></listitem> </varlistentry> </variablelist> To sum it up:"
922
#: using-d-i.xml:1205
928
#: using-d-i.xml:1206
931
msgid "Minimum Devices"
934
#: using-d-i.xml:1207
940
#: using-d-i.xml:1208
943
msgid "Survives disk failure?"
946
#: using-d-i.xml:1209
949
msgid "Available Space"
952
#: using-d-i.xml:1215
958
#: using-d-i.xml:1216 using-d-i.xml:1224
961
msgid "<entry>2</entry>"
964
#: using-d-i.xml:1217 using-d-i.xml:1218
967
msgid "<entry>no</entry>"
970
#: using-d-i.xml:1219
973
msgid "Size of the smallest partition multiplied by number of devices in RAID"
976
#: using-d-i.xml:1223
982
#: using-d-i.xml:1225 using-d-i.xml:1233
988
#: using-d-i.xml:1226 using-d-i.xml:1234
991
msgid "<entry>yes</entry>"
994
#: using-d-i.xml:1227
997
msgid "Size of the smallest partition in RAID"
1000
#: using-d-i.xml:1231
1006
#: using-d-i.xml:1232
1009
msgid "<entry>3</entry>"
1012
#: using-d-i.xml:1235
1015
msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
1018
#: using-d-i.xml:1243
1021
msgid "If you want to know the whole truth about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
1024
#: using-d-i.xml:1248
1027
msgid "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."
1030
#: using-d-i.xml:1256
1033
msgid "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 <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)"
1036
#: using-d-i.xml:1265
1039
msgid "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 (<filename>/</filename>) 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."
1042
#: using-d-i.xml:1274
1045
msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. 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."
1048
#: using-d-i.xml:1285
1051
msgid "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."
1054
#: using-d-i.xml:1292
1057
msgid "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."
1060
#: using-d-i.xml:1304
1063
msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
1066
#: using-d-i.xml:1312
1069
msgid "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 <filename>/home</filename>)."
1072
#: using-d-i.xml:1321
1075
msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints."
1078
#: using-d-i.xml:1334
1081
msgid "Installing the Base System"
1084
#: using-d-i.xml:1335
1087
msgid "Although this stage is the least problematic, it consumes most time of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time."
1090
#: using-d-i.xml:1349
1093
msgid "Base System Installation"
1096
#: using-d-i.xml:1351
1099
msgid "During the Base installation, package unpacking and setup messages are redirected to <userinput>tty3</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F3</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
1102
#: using-d-i.xml:1361
1105
msgid "The unpack/setup messages generated by the base installation are saved in <filename>/var/log/messages</filename> when the installation is performed over a serial console."
1108
#: using-d-i.xml:1367
1111
msgid "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."
1114
#: using-d-i.xml:1380
1117
msgid "Making Your System Bootable"
1120
#: using-d-i.xml:1382
1123
msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set the OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
1126
#: using-d-i.xml:1390
1129
msgid "Note that multiple operating systems booting on a single machine is still something of a black art. This document does not even attempt to document the various boot managers, which vary by architecture and even by subarchitecture. You should see your boot manager's documentation for more information."
1132
#: using-d-i.xml:1405
1135
msgid "Detecting other operating systems"
1138
#: using-d-i.xml:1407
1141
msgid "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."
1144
#: using-d-i.xml:1415
1147
msgid "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."
1150
#: using-d-i.xml:1427
1153
msgid "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 <command>partman</command>, or if you have mounted partitions manually from a console."
1156
#: using-d-i.xml:1444
1159
msgid "Install <command>aboot</command> on a Hard Disk"
1162
#: using-d-i.xml:1445
1165
msgid "If you have booted from SRM, if you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead."
1168
#: using-d-i.xml:1465
1171
msgid "<command>palo</command>-installer"
1174
#: using-d-i.xml:1466
1177
msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions."
1180
#: using-d-i.xml:1475
1183
msgid "hppa FIXME ( need more info )"
1186
#: using-d-i.xml:1487
1189
msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
1192
#: using-d-i.xml:1489
1195
msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike."
1198
#: using-d-i.xml:1495
1201
msgid "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."
1204
#: using-d-i.xml:1501
1207
msgid "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."
1210
#: using-d-i.xml:1515
1213
msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
1216
#: using-d-i.xml:1517
1219
msgid "The second &architecture; boot loader is called <quote>LILO</quote>. 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 <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>."
1222
#: using-d-i.xml:1527
1225
msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation."
1228
#: using-d-i.xml:1535
1231
msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:"
1234
#: using-d-i.xml:1542
1237
msgid "Master Boot Record (MBR)"
1240
#: using-d-i.xml:1542
1243
msgid "This way the <command>LILO</command> will take complete control of the boot process."
1246
#: using-d-i.xml:1549
1249
msgid "new Debian partition"
1252
#: using-d-i.xml:1549
1255
msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader."
1258
#: using-d-i.xml:1558
1261
msgid "Other choice"
1264
#: using-d-i.xml:1558
1267
msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
1270
#: using-d-i.xml:1570
1273
msgid "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 <userinput>fdisk /mbr</userinput> 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 <xref linkend=\"reactivating-win\"/>."
1276
#: using-d-i.xml:1587
1279
msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
1282
#: using-d-i.xml:1589
1285
msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> 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 <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies file into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to actually do the work of loading and starting the Linux kernel."
1288
#: using-d-i.xml:1605
1291
msgid "The <quote>elilo</quote> 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 <emphasis>root</emphasis> filesystem."
1294
#: using-d-i.xml:1617
1297
msgid "Choose the correct partition!"
1300
#: using-d-i.xml:1619
1303
msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> 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 <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
1306
#: using-d-i.xml:1634
1309
msgid "EFI Partition Contents"
1312
#: using-d-i.xml:1636
1315
msgid "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 <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured."
1318
#: using-d-i.xml:1658
1324
#: using-d-i.xml:1659
1327
msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition."
1330
#: using-d-i.xml:1668
1336
#: using-d-i.xml:1669
1339
msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu."
1342
#: using-d-i.xml:1679
1348
#: using-d-i.xml:1680
1351
msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>."
1354
#: using-d-i.xml:1692
1360
#: using-d-i.xml:1693
1363
msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run."
1366
#: using-d-i.xml:1703
1372
#: using-d-i.xml:1704
1375
msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>."
1378
#: using-d-i.xml:1724
1381
msgid "<command>arcboot</command>-installer"
1384
#: using-d-i.xml:1725
1388
"The boot loader on SGI Indys is <command>arcboot</command>. 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 <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n"
1389
"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n"
1390
"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput>\n"
1391
"<userinput> setenv OSLoader arcboot</userinput>\n"
1392
"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput>\n"
1393
"<userinput> setenv AutoLoad yes</userinput>\n"
1394
"</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>."
1397
#: using-d-i.xml:1744
1403
#: using-d-i.xml:1745
1406
msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers"
1409
#: using-d-i.xml:1753
1415
#: using-d-i.xml:1754
1418
msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed"
1421
#: using-d-i.xml:1762 using-d-i.xml:1831
1427
#: using-d-i.xml:1763
1430
msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides"
1433
#: using-d-i.xml:1771
1439
#: using-d-i.xml:1772
1442
msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default."
1445
#: using-d-i.xml:1793
1448
msgid "<command>delo</command>-installer"
1451
#: using-d-i.xml:1794
1455
"The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n"
1456
"<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput>\n"
1457
"</screen></informalexample> on the firmware prompt."
1460
#: using-d-i.xml:1813
1463
msgid "<replaceable>#</replaceable>"
1466
#: using-d-i.xml:1814
1469
msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
1472
#: using-d-i.xml:1822
1475
msgid "<replaceable>id</replaceable>"
1478
#: using-d-i.xml:1823
1481
msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
1484
#: using-d-i.xml:1832
1487
msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
1490
#: using-d-i.xml:1840
1496
#: using-d-i.xml:1841
1499
msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
1502
#: using-d-i.xml:1851
1505
msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use"
1508
#: using-d-i.xml:1857
1511
msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
1514
#: using-d-i.xml:1867
1517
msgid "Install <command>Yaboot</command> on a Hard Disk"
1520
#: using-d-i.xml:1868
1523
msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> 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;."
1526
#: using-d-i.xml:1886
1529
msgid "Install <command>Quik</command> on a Hard Disk"
1532
#: using-d-i.xml:1887
1535
msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones."
1538
#: using-d-i.xml:1903
1541
msgid "<command>zipl</command>-installer"
1544
#: using-d-i.xml:1904
1547
msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>."
1550
#: using-d-i.xml:1921
1553
msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
1556
#: using-d-i.xml:1923
1559
msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install."
1562
#: using-d-i.xml:1948
1565
msgid "Continue Without Boot Loader"
1568
#: using-d-i.xml:1950
1571
msgid "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). <phrase arch=\"m68k\">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.</phrase>"
1574
#: using-d-i.xml:1959
1577
msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; 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 <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem."
1580
#: using-d-i.xml:1976
1583
msgid "Finishing the First Stage"
1586
#: using-d-i.xml:1977
1589
msgid "These are the last bits to do before rebooting to your new Debian. It mostly consists of tidying up after the &d-i;."
1592
#: using-d-i.xml:1989
1595
msgid "Finish the Installation and Reboot"
1598
#: using-d-i.xml:1991
1601
msgid "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."
1604
#: using-d-i.xml:1998
1607
msgid "Select the <guimenuitem>Finish the installation</guimenuitem> 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."
1610
#: using-d-i.xml:2012
1613
msgid "Miscellaneous"
1616
#: using-d-i.xml:2013
1619
msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong."
1622
#: using-d-i.xml:2026
1625
msgid "Saving the installation logs"
1628
#: using-d-i.xml:2028
1631
msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/debian-installer/</filename> on your new Debian system."
1634
#: using-d-i.xml:2035
1637
msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk<phrase condition=\"etch\">, network, hard disk, or other media</phrase>. 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."
1640
#: using-d-i.xml:2056
1643
msgid "Using the Shell and Viewing the Logs"
1646
#: using-d-i.xml:2059
1649
msgid "There is an <guimenuitem>Execute a Shell</guimenuitem> item on the menu. If the menu is not available when you need to use the shell, press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> </keycombo>) to switch to the second <emphasis>virtual console</emphasis>. That's the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap>, and the <keycap>F2</keycap> function key, at the same time. This is a separate window running a Bourne shell clone called <command>ash</command>."
1652
#: using-d-i.xml:2071
1655
msgid "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 <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The text editor is <command>nano</command>. The shell has some nice features like autocompletion and history."
1658
#: using-d-i.xml:2080
1661
msgid "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 <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or type <command>exit</command> if you used a menu item to open the shell."
1664
#: using-d-i.xml:2099
1667
msgid "Installation Over the Network"
1670
#: using-d-i.xml:2101
1673
msgid "One of the more interesting components is <firstterm>network-console</firstterm>. 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 <xref linkend=\"automatic-install\"/>.)"
1676
#: using-d-i.xml:2111
1679
msgid "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 <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>."
1682
#: using-d-i.xml:2124
1685
msgid "For installations on &arch-title;, this is the default method after setting up the network."
1688
#: using-d-i.xml:2129
1691
msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> 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 <emphasis>installer</emphasis> 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 <quote>person who will continue the installation remotely</quote>."
1694
#: using-d-i.xml:2141
1697
msgid "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."
1700
#: using-d-i.xml:2147
1704
"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: <informalexample><screen>\n"
1705
"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</replaceable></userinput>\n"
1706
"</screen></informalexample> Where <replaceable>install_host</replaceable> 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."
1709
#: using-d-i.xml:2164
1712
msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> 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 <filename>~/.ssh/known_hosts</filename> and try again."
1715
#: using-d-i.xml:2173
1718
msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. 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."
1721
#: using-d-i.xml:2183
1724
msgid "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."
1727
#: using-d-i.xml:2191
1730
msgid "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."
1733
#: using-d-i.xml:2206
1736
msgid "Running <command>base-config</command> From Within &d-i;"
1739
#: using-d-i.xml:2208
1742
msgid "It is possible to configure the base system within the first stage installer (before rebooting from the hard drive), by running <command>base-config</command> in a <firstterm>chroot</firstterm> environment. This is mainly useful for testing the installer and should normally be avoided."
added
removed
po/pot/using-d-i.pot
