276
276
#: using-d-i.xml:259
284
msgid "Automatically partitions an entire disk according to preset user preferences."
290
278
msgid "partitioner"
296
284
msgid "Allows the user to partition disks attached to the system. A partitioning program appropriate to your computer's architecture is chosen."
308
296
msgid "Displays a list of partitions, and creates file systems on the selected partitions according to user instructions."
320
308
msgid "Helps the user with the configuration of the <firstterm>LVM</firstterm> (Logical Volume Manager)."
332
320
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
326
msgid "base-installer"
344
332
msgid "Installs the most basic set of packages which would allow the computer to operate under Linux when rebooted."
350
338
msgid "user-setup"
356
344
msgid "Sets up the root password, and adds a non-root user."
362
350
msgid "apt-setup"
368
356
msgid "Configures apt, mostly automatically, based on what media the installer is running from."
380
368
msgid "Uses <classname>tasksel</classname> to select and install additional software."
386
374
msgid "os-prober"
392
380
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."
398
386
msgid "bootloader-installer"
404
392
msgid "The various bootloader installers each install 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."
416
404
msgid "Allows the user to execute a shell from the menu, or in the second console."
422
410
msgid "save-logs"
428
416
msgid "Provides a way for the user to record information on a floppy disk, network, hard disk, or other media when trouble is encountered, in order to accurately report installer software problems to Debian developers later."
434
422
msgid "Using Individual Components"
440
428
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."
446
434
msgid "Setting up Debian Installer and Hardware Configuration"
452
440
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)."
458
446
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."
464
452
msgid "Check available memory / low memory mode"
470
458
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."
476
464
msgid "The first measure taken to reduce memory consumption by the installer is to disable translations, which means that the installation can only be done in English. Of course, you can still localize the installed system after the installation has completed."
470
msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
480
474
#: using-d-i.xml:449
482
msgid "If that is not sufficient, the installer will further reduce memory consumption by loading only those components essential to complete a basic installation. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail."
488
476
msgid "If the installer runs in low memory mode, it is recommended to create a relatively large swap partition (64–128MB). The swap partition will be used as virtual memory and thus increases the amount of memory available to the system. The installer will activate the swap partition as early as possible in the installation process. Note that heavy use of swap will reduce performance of your system and may lead to high disk activity."
494
482
msgid "Despite these measures, it is still possible that your system freezes, that unexpected errors occur or that processes are killed by the kernel because the system runs out of memory (which will result in <quote>Out of memory</quote> messages on VT4 and in the syslog)."
500
488
msgid "For example, it has been reported that creating a big ext3 file system fails in low memory mode when there is insufficient swap space. If a larger swap doesn't help, try creating the file system as ext2 (which is an essential component of the installer) instead. It is possible to change an ext2 partition to ext3 after the installation."
506
494
msgid "It is possible to force the installer to use a higher lowmem level than the one based on available memory by using the boot parameter <quote>lowmem</quote> as described in <xref linkend=\"installer-args\"/>."
512
500
msgid "Selecting Localization Options"
518
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."
524
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."
530
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."
536
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."
542
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."
548
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."
554
542
msgid "Choosing a Keyboard"
560
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."
564
558
#: using-d-i.xml:578
566
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."
572
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."
578
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."
584
572
msgid "Looking for the Debian Installer ISO Image"
590
578
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
584
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
590
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
596
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
602
msgid "Configuring the Network"
620
608
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
614
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 fourth console. In any case, you will be asked if you want to retry, or if you want to perform a manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again."
632
620
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
626
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. The default broadcast address is calculated as 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 offered defaults — if necessary, you can change them by editing <filename>/etc/network/interfaces</filename> once the system has been installed."
644
632
msgid "Configuring the Clock"
650
638
msgid "The installer will first attempt to connect to a time server on the Internet (using the <firstterm>NTP</firstterm> protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process."
656
644
msgid "Depending on the location selected earlier in the installation process, you may be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone."
662
650
msgid "If for some reason you wish to set a time zone for the installed system that does <emphasis>not</emphasis> match the selected location, there are two options."
668
656
msgid "The simplest option is to just select a different timezone after the installation has been completed and you've booted into the new system. The command to do this is:"
674
662
msgid "# dpkg-reconfigure tzdata"
680
668
msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter <userinput>time/zone=<replaceable>value</replaceable></userinput> when you boot the installation system. The value should of course be a valid time zone, for example <userinput>Europe/London</userinput> or <userinput>UTC</userinput>."
686
674
msgid "For automated installations the time zone can also be set using preseeding."
692
680
msgid "Partitioning and Mount Point Selection"
698
686
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 options like RAID, LVM or encrypted devices."
704
692
msgid "If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>."
711
699
"If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to <quote>zero</quote> the first few sectors of the drive: <informalexample><screen>\n"
719
707
msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu."
725
713
msgid "Guided Partitioning"
731
719
msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>."
737
725
msgid "The option to use (encrypted) LVM may not be available on all architectures."
731
msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
741
735
#: using-d-i.xml:910
743
msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data."
737
msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
747
741
#: using-d-i.xml:919
749
msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk."
755
743
msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk."
749
msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
759
753
#: using-d-i.xml:938
761
msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them."
767
755
msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible."
773
761
msgid "Next, 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 a 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."
779
767
msgid "Partitioning scheme"
785
773
msgid "Minimum space"
791
779
msgid "Created partitions"
797
785
msgid "All files in one partition"
809
797
msgid "<filename>/</filename>, swap"
815
803
msgid "Separate /home partition"
827
815
msgid "<filename>/</filename>, <filename>/home</filename>, swap"
833
821
msgid "Separate /home, /usr, /var and /tmp partitions"
839
827
msgid "<entry>1GB</entry>"
833
msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
843
837
#: using-d-i.xml:991
845
msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap"
849
#: using-d-i.xml:1000
851
839
msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, including the swap partition, will be created inside the LVM partition."
855
#: using-d-i.xml:1006
857
845
msgid "If you choose guided partitioning for your IA-64 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."
861
#: using-d-i.xml:1014
849
#: using-d-i.xml:1005
863
851
msgid "If you choose guided 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."
867
#: using-d-i.xml:1020
855
#: using-d-i.xml:1011
869
857
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."
873
#: using-d-i.xml:1026
861
#: using-d-i.xml:1017
876
864
"The list of partitions might look like this: <informalexample><screen>\n"
896
#: using-d-i.xml:1039
884
#: using-d-i.xml:1030
898
886
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> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning."
902
#: using-d-i.xml:1053
890
#: using-d-i.xml:1044
904
892
msgid "Manual Partitioning"
908
#: using-d-i.xml:1054
896
#: using-d-i.xml:1045
910
898
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."
914
#: using-d-i.xml:1062
902
#: using-d-i.xml:1053
916
904
msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk."
920
#: using-d-i.xml:1070
908
#: using-d-i.xml:1061
922
910
msgid "If you select some free space, you will have the opportunity to create a 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 a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. 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 a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen."
926
#: using-d-i.xml:1092
914
#: using-d-i.xml:1083
928
916
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. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may 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."
932
#: using-d-i.xml:1103
920
#: using-d-i.xml:1094
934
922
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."
938
#: using-d-i.xml:1111
926
#: using-d-i.xml:1102
940
928
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."
944
#: using-d-i.xml:1117
932
#: using-d-i.xml:1108
946
934
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>)."
950
#: using-d-i.xml:1125
938
#: using-d-i.xml:1116
952
940
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."
956
#: using-d-i.xml:1153
944
#: using-d-i.xml:1144
958
946
msgid "Configuring Multidisk Devices (Software RAID)"
962
#: using-d-i.xml:1154
950
#: using-d-i.xml:1145
964
952
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>)."
968
#: using-d-i.xml:1168
956
#: using-d-i.xml:1159
970
958
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.)."
974
#: using-d-i.xml:1176
962
#: using-d-i.xml:1167
976
964
msgid "What benefits this brings depends on the type of 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 lose <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 incoming data into stripes and distributes them equally on all but one disk (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 a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:"
980
#: using-d-i.xml:1254
968
#: using-d-i.xml:1245
986
#: using-d-i.xml:1255
974
#: using-d-i.xml:1246
988
976
msgid "Minimum Devices"
992
#: using-d-i.xml:1256
980
#: using-d-i.xml:1247
994
982
msgid "Spare Device"
998
#: using-d-i.xml:1257
986
#: using-d-i.xml:1248
1000
988
msgid "Survives disk failure?"
1004
#: using-d-i.xml:1258
992
#: using-d-i.xml:1249
1006
994
msgid "Available Space"
1010
#: using-d-i.xml:1264
998
#: using-d-i.xml:1255
1016
#: using-d-i.xml:1265 using-d-i.xml:1273
1004
#: using-d-i.xml:1256 using-d-i.xml:1264
1018
1006
msgid "<entry>2</entry>"
1022
#: using-d-i.xml:1266 using-d-i.xml:1267
1010
#: using-d-i.xml:1257 using-d-i.xml:1258
1024
1012
msgid "<entry>no</entry>"
1028
#: using-d-i.xml:1268
1016
#: using-d-i.xml:1259
1030
1018
msgid "Size of the smallest partition multiplied by number of devices in RAID"
1034
#: using-d-i.xml:1272
1022
#: using-d-i.xml:1263
1040
#: using-d-i.xml:1274 using-d-i.xml:1282
1028
#: using-d-i.xml:1265 using-d-i.xml:1273
1042
1030
msgid "optional"
1046
#: using-d-i.xml:1275 using-d-i.xml:1283
1034
#: using-d-i.xml:1266 using-d-i.xml:1274
1048
1036
msgid "<entry>yes</entry>"
1052
#: using-d-i.xml:1276
1040
#: using-d-i.xml:1267
1054
1042
msgid "Size of the smallest partition in RAID"
1058
#: using-d-i.xml:1280
1046
#: using-d-i.xml:1271
1064
#: using-d-i.xml:1281
1052
#: using-d-i.xml:1272
1066
1054
msgid "<entry>3</entry>"
1070
#: using-d-i.xml:1284
1058
#: using-d-i.xml:1275
1072
1060
msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)"
1076
#: using-d-i.xml:1292
1064
#: using-d-i.xml:1283
1078
1066
msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>."
1070
#: using-d-i.xml:1288
1072
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>.)"
1082
1076
#: using-d-i.xml:1297
1084
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>.)"
1078
msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for <filename>/boot</filename> when using RAID for the root (<filename>/</filename>) file system. Most boot loaders <phrase arch=\"x86\">(including lilo and grub)</phrase> do support mirrored (not striped!) RAID1, so using for example RAID5 for <filename>/</filename> and RAID1 for <filename>/boot</filename> can be an option."
1088
#: using-d-i.xml:1306
1082
#: using-d-i.xml:1309
1090
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."
1084
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>) file system. 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."
1094
#: using-d-i.xml:1315
1088
#: using-d-i.xml:1318
1096
1090
msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) 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."
1100
#: using-d-i.xml:1328
1094
#: using-d-i.xml:1331
1102
1096
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."
1106
#: using-d-i.xml:1335
1100
#: using-d-i.xml:1338
1108
1102
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."
1112
#: using-d-i.xml:1347
1106
#: using-d-i.xml:1350
1114
1108
msgid "RAID5 has a similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions."
1118
#: using-d-i.xml:1355
1112
#: using-d-i.xml:1358
1120
1114
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 the first partitions on all three disks 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>)."
1124
#: using-d-i.xml:1364
1118
#: using-d-i.xml:1367
1126
1120
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."
1130
#: using-d-i.xml:1379
1124
#: using-d-i.xml:1382
1132
1126
msgid "Configuring the Logical Volume Manager (LVM)"
1136
#: using-d-i.xml:1380
1130
#: using-d-i.xml:1383
1138
1132
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."
1142
#: using-d-i.xml:1388
1136
#: using-d-i.xml:1391
1144
1138
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 disk (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 disks."
1148
#: using-d-i.xml:1398
1142
#: using-d-i.xml:1401
1150
1144
msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk 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>."
1154
#: using-d-i.xml:1409
1148
#: using-d-i.xml:1412
1156
1150
msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>."
1160
#: using-d-i.xml:1418
1154
#: using-d-i.xml:1421
1162
1156
msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:"
1166
#: using-d-i.xml:1429
1160
#: using-d-i.xml:1432
1168
1162
msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more"
1171
1165
#. Tag: guimenuitem
1172
#: using-d-i.xml:1434
1166
#: using-d-i.xml:1437
1174
1168
msgid "Create volume group"
1177
1171
#. Tag: guimenuitem
1178
#: using-d-i.xml:1437
1172
#: using-d-i.xml:1440
1180
1174
msgid "Create logical volume"
1183
1177
#. Tag: guimenuitem
1184
#: using-d-i.xml:1440
1178
#: using-d-i.xml:1443
1186
1180
msgid "Delete volume group"
1189
1183
#. Tag: guimenuitem
1190
#: using-d-i.xml:1443
1184
#: using-d-i.xml:1446
1192
1186
msgid "Delete logical volume"
1195
1189
#. Tag: guimenuitem
1196
#: using-d-i.xml:1446
1190
#: using-d-i.xml:1449
1198
1192
msgid "Extend volume group"
1201
1195
#. Tag: guimenuitem
1202
#: using-d-i.xml:1449
1196
#: using-d-i.xml:1452
1204
1198
msgid "Reduce volume group"
1208
#: using-d-i.xml:1451
1202
#: using-d-i.xml:1454
1210
1204
msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen"
1214
#: using-d-i.xml:1457
1208
#: using-d-i.xml:1460
1216
1210
msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it."
1220
#: using-d-i.xml:1462
1214
#: using-d-i.xml:1465
1222
1216
msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)."
1226
#: using-d-i.xml:1476
1220
#: using-d-i.xml:1479
1228
1222
msgid "Configuring Encrypted Volumes"
1232
#: using-d-i.xml:1477
1226
#: using-d-i.xml:1480
1234
1228
msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters."
1238
#: using-d-i.xml:1489
1232
#: using-d-i.xml:1492
1240
1234
msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition."
1244
#: using-d-i.xml:1504
1238
#: using-d-i.xml:1507
1246
1240
msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length."
1250
#: using-d-i.xml:1511
1244
#: using-d-i.xml:1514
1252
1246
msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition."
1256
#: using-d-i.xml:1522
1250
#: using-d-i.xml:1525
1258
1252
msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default."
1262
#: using-d-i.xml:1534
1256
#: using-d-i.xml:1537
1264
1258
msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind."
1268
#: using-d-i.xml:1544
1262
#: using-d-i.xml:1547
1270
1264
msgid "Encryption: <userinput>aes</userinput>"
1274
#: using-d-i.xml:1546
1268
#: using-d-i.xml:1549
1276
1270
msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century."
1280
#: using-d-i.xml:1564
1274
#: using-d-i.xml:1567
1282
1276
msgid "Key size: <userinput>256</userinput>"
1286
#: using-d-i.xml:1566
1280
#: using-d-i.xml:1569
1288
1282
msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher."
1292
#: using-d-i.xml:1578
1286
#: using-d-i.xml:1581
1294
1288
msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>"
1298
#: using-d-i.xml:1580
1292
#: using-d-i.xml:1583
1300
1294
msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data."
1304
#: using-d-i.xml:1590
1298
#: using-d-i.xml:1593
1306
1300
msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms."
1310
#: using-d-i.xml:1602
1304
#: using-d-i.xml:1605
1312
1306
msgid "Encryption key: <userinput>Passphrase</userinput>"
1316
#: using-d-i.xml:1604
1310
#: using-d-i.xml:1607
1318
1312
msgid "Here you can choose the type of the encryption key for this partition."
1322
#: using-d-i.xml:1610
1316
#: using-d-i.xml:1613
1324
1318
msgid "Passphrase"
1328
#: using-d-i.xml:1611
1322
#: using-d-i.xml:1614
1330
1324
msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process."
1334
#: using-d-i.xml:1626 using-d-i.xml:1719
1328
#: using-d-i.xml:1629 using-d-i.xml:1722
1336
1330
msgid "Random key"
1340
#: using-d-i.xml:1627
1334
#: using-d-i.xml:1630
1342
1336
msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)"
1346
#: using-d-i.xml:1636
1340
#: using-d-i.xml:1639
1348
1342
msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition."
1352
#: using-d-i.xml:1655 using-d-i.xml:1732
1346
#: using-d-i.xml:1658 using-d-i.xml:1735
1354
1348
msgid "Erase data: <userinput>yes</userinput>"
1358
#: using-d-i.xml:1657
1352
#: using-d-i.xml:1660
1360
1354
msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>."
1364
#: using-d-i.xml:1677
1358
#: using-d-i.xml:1680
1366
1360
msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:"
1370
#: using-d-i.xml:1686
1364
#: using-d-i.xml:1689
1372
1366
msgid "Encryption: <userinput>AES256</userinput>"
1376
#: using-d-i.xml:1688
1370
#: using-d-i.xml:1691
1378
1372
msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information."
1382
#: using-d-i.xml:1698
1376
#: using-d-i.xml:1701
1384
1378
msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>"
1388
#: using-d-i.xml:1700
1382
#: using-d-i.xml:1703
1390
1384
msgid "Here you can select the type of the encryption key for this partition."
1394
#: using-d-i.xml:1706
1388
#: using-d-i.xml:1709
1396
1390
msgid "Keyfile (GnuPG)"
1400
#: using-d-i.xml:1707
1394
#: using-d-i.xml:1710
1402
1396
msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)."
1406
#: using-d-i.xml:1720
1400
#: using-d-i.xml:1723
1408
1402
msgid "Please see the section on random keys above."
1412
#: using-d-i.xml:1734
1406
#: using-d-i.xml:1737
1414
1408
msgid "Please see the the section on erasing data above."
1418
#: using-d-i.xml:1744
1420
msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using a <emphasis>passphrase</emphasis> as the encryption key."
1424
#: using-d-i.xml:1752
1412
#: using-d-i.xml:1746
1426
1414
msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time."
1430
#: using-d-i.xml:1762
1418
#: using-d-i.xml:1756
1432
1420
msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)."
1436
#: using-d-i.xml:1771
1424
#: using-d-i.xml:1765
1438
1426
msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system."
1442
#: using-d-i.xml:1784
1430
#: using-d-i.xml:1778
1444
1432
msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted."
1448
#: using-d-i.xml:1800
1436
#: using-d-i.xml:1794
1451
1439
"After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n"
1461
#: using-d-i.xml:1813
1449
#: using-d-i.xml:1807
1463
1451
msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>."
1467
#: using-d-i.xml:1823
1455
#: using-d-i.xml:1817
1469
1457
msgid "Once you are satisfied with the partitioning scheme, continue with the installation."
1473
#: using-d-i.xml:1834
1461
#: using-d-i.xml:1828
1475
1463
msgid "Installing the Base System"
1479
#: using-d-i.xml:1835
1467
#: using-d-i.xml:1829
1481
1469
msgid "Although this stage is the least problematic, it consumes a significant fraction 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."
1485
#: using-d-i.xml:1848
1473
#: using-d-i.xml:1842
1487
1475
msgid "During installation of the base system, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>."
1479
#: using-d-i.xml:1851
1481
msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
1491
1485
#: using-d-i.xml:1857
1493
msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console."
1497
#: using-d-i.xml:1863
1499
1487
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."
1503
#: using-d-i.xml:1875
1491
#: using-d-i.xml:1869
1505
1493
msgid "Setting Up Users And Passwords"
1509
#: using-d-i.xml:1876
1497
#: using-d-i.xml:1870
1511
1499
msgid "After the base system has been installed, the installer will allow you to set up the <quote>root</quote> account and/or an account for the first user. Other user accounts can be created after the installation has been completed."
1515
#: using-d-i.xml:1890
1503
#: using-d-i.xml:1884
1517
1505
msgid "Set the Root Password"
1521
#: using-d-i.xml:1894
1509
#: using-d-i.xml:1888
1523
1511
msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible."
1527
#: using-d-i.xml:1902
1515
#: using-d-i.xml:1896
1529
1517
msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed."
1533
#: using-d-i.xml:1910
1521
#: using-d-i.xml:1904
1535
1523
msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator."
1539
#: using-d-i.xml:1920
1527
#: using-d-i.xml:1914
1541
1529
msgid "Create an Ordinary User"
1545
#: using-d-i.xml:1922
1533
#: using-d-i.xml:1916
1547
1535
msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login."
1551
#: using-d-i.xml:1931
1539
#: using-d-i.xml:1925
1553
1541
msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you."
1557
#: using-d-i.xml:1941
1545
#: using-d-i.xml:1935
1559
1547
msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account."
1563
#: using-d-i.xml:1948
1551
#: using-d-i.xml:1942
1565
1553
msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command."
1569
#: using-d-i.xml:1959
1557
#: using-d-i.xml:1953
1571
1559
msgid "Installing Additional Software"
1575
#: using-d-i.xml:1960
1563
#: using-d-i.xml:1954
1577
1565
msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection."
1581
#: using-d-i.xml:1975
1569
#: using-d-i.xml:1969
1583
1571
msgid "Configuring apt"
1587
#: using-d-i.xml:1977
1575
#: using-d-i.xml:1971
1589
1577
msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management."
1593
#: using-d-i.xml:2001
1581
#: using-d-i.xml:1995
1595
1583
msgid "<command>apt</command> must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>. You can examine and edit this file to your liking after the installation is complete."
1599
#: using-d-i.xml:2008
1587
#: using-d-i.xml:2002
1601
1589
msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the <quote>volatile</quote> update service."
1605
#: using-d-i.xml:2017
1593
#: using-d-i.xml:2011
1607
1595
msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the <quote>contrib</quote> and <quote>non-free</quote> sections of the archive."
1611
#: using-d-i.xml:2028
1599
#: using-d-i.xml:2022
1601
msgid "Installing from more than one CD or DVD"
1605
#: using-d-i.xml:2024
1607
msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them."
1611
#: using-d-i.xml:2031
1613
msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed."
1617
#: using-d-i.xml:2039
1619
msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set."
1623
#: using-d-i.xml:2046
1625
msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs."
1629
#: using-d-i.xml:2055
1631
msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments."
1635
#: using-d-i.xml:2063
1637
msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes."
1641
#: using-d-i.xml:2076
1613
1643
msgid "Using a network mirror"
1617
#: using-d-i.xml:2030
1647
#: using-d-i.xml:2078
1619
msgid "One question that will be asked in most cases is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
1649
msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions."
1623
#: using-d-i.xml:2036
1653
#: using-d-i.xml:2084
1625
1655
msgid "If you are <emphasis>not</emphasis> installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best <emphasis>not</emphasis> to select the <literal>desktop</literal> task in the next step of the installation."
1629
#: using-d-i.xml:2045
1631
msgid "If you are installing from a full CD or using a CD image (not DVD), using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. The installer currently does not support using multiple CD or DVD images during the installation<footnote> <para> Adding that option is planned. </para> </footnote>. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and install additional packages after the installation (i.e. after you have rebooted into the new system)."
1635
#: using-d-i.xml:2063
1637
msgid "If you are installing from a DVD or using a DVD image, the need to use a network mirror is a lot smaller, but there is still a chance that some packages that are part of the tasks you select in the next step will not be included on the first DVD. This is especially true if you are installing in another language than English: a number of font and localization packages are known to be on the second DVD. So, if you have a reasonable Internet connection it is still advisable to use a network mirror."
1641
#: using-d-i.xml:2073
1643
msgid "To install additional packages after the installation you have two options: <orderedlist> <listitem><para> if you have additional CD/DVD images available (from same set as the installation CD/DVD you are using), you can add those to the <filename>sources.list</filename> using <command>apt-cdrom</command>; </para></listitem> <listitem><para> manually add a mirror to the <filename>sources.list</filename> using an editor. </para></listitem> </orderedlist> You can then use one of the package management front-ends to select and install additional packages<footnote> <para> It is possible to add both additional CDs or DVDs <emphasis>and</emphasis> a network mirror in <filename>/etc/apt/sources.list</filename>. Also adding a network mirror has the advantage that it will make updates of packages in point releases of the distribution available for installation. </para> </footnote>."
1647
#: using-d-i.xml:2107
1649
msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available on the CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on a) the tasks you select in the next step of the installation, b) which packages are needed for those tasks, and c) which of those packages are present on the CD/DVD."
1653
#: using-d-i.xml:2117
1655
msgid "Note that even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
1659
#: using-d-i.xml:2093
1661
msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to <emphasis>not</emphasis> select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)."
1665
#: using-d-i.xml:2104
1667
msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional."
1671
#: using-d-i.xml:2111
1673
msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system."
1677
#: using-d-i.xml:2118
1679
msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on"
1683
#: using-d-i.xml:2127
1685
msgid "the tasks you select in the next step of the installation,"
1659
1689
#: using-d-i.xml:2132
1691
msgid "which packages are needed for those tasks,"
1695
#: using-d-i.xml:2137
1697
msgid "which of those packages are present on the CDs or DVDs you have scanned, and"
1701
#: using-d-i.xml:2142
1703
msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)."
1707
#: using-d-i.xml:2151
1709
msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured."
1713
#: using-d-i.xml:2167
1661
1715
msgid "Selecting and Installing Software"
1665
#: using-d-i.xml:2134
1719
#: using-d-i.xml:2169
1667
1721
msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks."
1671
#: using-d-i.xml:2143
1725
#: using-d-i.xml:2178
1673
1727
msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks."
1677
#: using-d-i.xml:2170
1679
msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point."
1683
#: using-d-i.xml:2177
1685
msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE."
1689
#: using-d-i.xml:2185
1691
msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer<footnote> <para> A more lightweight Xfce desktop environment can be selected by using <literal>xfce-desktop</literal> instead of <literal>kde-desktop</literal>. If you are installing on a laptop, you could also add <literal>laptop</literal> to the tasks to be installed. </para> </footnote>. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method."
1695
1731
#: using-d-i.xml:2205
1733
msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point."
1737
#: using-d-i.xml:2212
1739
msgid "Unless you are using the special KDE or Xfce CDs, the <quote>Desktop environment</quote> task will install the GNOME desktop environment."
1743
#: using-d-i.xml:2219
1745
msgid "It is not possible to interactively select a different desktop during the installation. However, it <emphasis>is</emphasis> possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding the parameter <literal>desktop=kde</literal> at the boot prompt when starting the installer. Alternatively the more lightweight Xfce desktop environment can be selected by using <literal>desktop=xfce</literal>."
1749
#: using-d-i.xml:2229
1751
msgid "Note that this will only work if the packages needed for KDE or Xfce are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE or Xfce this way should work fine if you are using a DVD image or any other installation method."
1755
#: using-d-i.xml:2237
1697
1757
msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL database: <classname>postgresql</classname>; Web server: <classname>apache</classname>."
1701
#: using-d-i.xml:2217
1761
#: using-d-i.xml:2249
1703
1763
msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected."
1707
#: using-d-i.xml:2224
1767
#: using-d-i.xml:2256
1709
1769
msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task."
1713
#: using-d-i.xml:2230
1773
#: using-d-i.xml:2262
1715
1775
msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started."
1719
#: using-d-i.xml:2239
1779
#: using-d-i.xml:2271
1721
1781
msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image."
1725
#: using-d-i.xml:2248
1785
#: using-d-i.xml:2280
1727
1787
msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process."
1731
#: using-d-i.xml:2261
1791
#: using-d-i.xml:2293
1733
1793
msgid "Making Your System Bootable"
1737
#: using-d-i.xml:2263
1797
#: using-d-i.xml:2295
1739
1799
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 OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>"
1743
#: using-d-i.xml:2278
1803
#: using-d-i.xml:2310
1745
1805
msgid "Detecting other operating systems"
1749
#: using-d-i.xml:2280
1809
#: using-d-i.xml:2312
1751
1811
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."
1755
#: using-d-i.xml:2288
1815
#: using-d-i.xml:2320
1757
1817
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."
1761
#: using-d-i.xml:2306
1821
#: using-d-i.xml:2338
1763
1823
msgid "Install <command>aboot</command> on a Hard Disk"
1767
#: using-d-i.xml:2307
1827
#: using-d-i.xml:2339
1769
1829
msgid "If you have booted from SRM and 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."
1773
#: using-d-i.xml:2327
1833
#: using-d-i.xml:2359
1775
1835
msgid "<command>palo</command>-installer"
1779
#: using-d-i.xml:2328
1839
#: using-d-i.xml:2360
1781
1841
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."
1785
#: using-d-i.xml:2337
1845
#: using-d-i.xml:2369
1787
1847
msgid "hppa FIXME ( need more info )"
1791
#: using-d-i.xml:2349
1851
#: using-d-i.xml:2381
1793
1853
msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk"
1797
#: using-d-i.xml:2351
1857
#: using-d-i.xml:2383
1799
1859
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 new users and old hands alike."
1803
#: using-d-i.xml:2357
1863
#: using-d-i.xml:2389
1805
1865
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."
1809
#: using-d-i.xml:2363
1869
#: using-d-i.xml:2395
1811
1871
msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use."
1815
#: using-d-i.xml:2376
1875
#: using-d-i.xml:2408
1817
1877
msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk"
1821
#: using-d-i.xml:2378
1881
#: using-d-i.xml:2410
1823
1883
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>."
1827
#: using-d-i.xml:2388
1887
#: using-d-i.xml:2420
1829
1889
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."
1833
#: using-d-i.xml:2396
1893
#: using-d-i.xml:2428
1835
1895
msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:"
1839
#: using-d-i.xml:2403
1899
#: using-d-i.xml:2435
1841
1901
msgid "Master Boot Record (MBR)"
1845
#: using-d-i.xml:2403
1905
#: using-d-i.xml:2435
1847
1907
msgid "This way the <command>LILO</command> will take complete control of the boot process."
1851
#: using-d-i.xml:2410
1911
#: using-d-i.xml:2442
1853
1913
msgid "new Debian partition"
1857
#: using-d-i.xml:2410
1917
#: using-d-i.xml:2442
1859
1919
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."
1863
#: using-d-i.xml:2419
1923
#: using-d-i.xml:2451
1865
1925
msgid "Other choice"
1869
#: using-d-i.xml:2419
1929
#: using-d-i.xml:2451
1871
1931
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 traditional device names such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>."
1875
#: using-d-i.xml:2429
1935
#: using-d-i.xml:2461
1877
1937
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!"
1881
#: using-d-i.xml:2445
1941
#: using-d-i.xml:2477
1883
1943
msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk"
1887
#: using-d-i.xml:2447
1947
#: using-d-i.xml:2479
1889
1949
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 files 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 do the actual work of loading and starting the Linux kernel."
1893
#: using-d-i.xml:2463
1953
#: using-d-i.xml:2495
1895
1955
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."
1899
#: using-d-i.xml:2475
1959
#: using-d-i.xml:2507
1901
1961
msgid "Choose the correct partition!"
1905
#: using-d-i.xml:2477
1965
#: using-d-i.xml:2509
1907
1967
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, <command>elilo</command> may format the partition during the installation, erasing any previous contents!"
1911
#: using-d-i.xml:2492
1971
#: using-d-i.xml:2524
1913
1973
msgid "EFI Partition Contents"
1917
#: using-d-i.xml:2494
1977
#: using-d-i.xml:2526
1919
1979
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."
1922
1982
#. Tag: filename
1923
#: using-d-i.xml:2516
1983
#: using-d-i.xml:2548
1925
1985
msgid "elilo.conf"
1929
#: using-d-i.xml:2517
1989
#: using-d-i.xml:2549
1931
1991
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."
1934
1994
#. Tag: filename
1935
#: using-d-i.xml:2526
1995
#: using-d-i.xml:2558
1937
1997
msgid "elilo.efi"
1941
#: using-d-i.xml:2527
2001
#: using-d-i.xml:2559
1943
2003
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."
1946
2006
#. Tag: filename
1947
#: using-d-i.xml:2537
2007
#: using-d-i.xml:2569
1949
2009
msgid "initrd.img"
1953
#: using-d-i.xml:2538
2013
#: using-d-i.xml:2570
1955
2015
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>."
1958
2018
#. Tag: filename
1959
#: using-d-i.xml:2550
2019
#: using-d-i.xml:2582
1961
2021
msgid "readme.txt"
1965
#: using-d-i.xml:2551
2025
#: using-d-i.xml:2583
1967
2027
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."
1970
2030
#. Tag: filename
1971
#: using-d-i.xml:2561
2031
#: using-d-i.xml:2593
1973
2033
msgid "vmlinuz"
1977
#: using-d-i.xml:2562
2037
#: using-d-i.xml:2594
1979
2039
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>."
1983
#: using-d-i.xml:2582
2043
#: using-d-i.xml:2614
1985
2045
msgid "<command>arcboot</command>-installer"
1989
#: using-d-i.xml:2583
2049
#: using-d-i.xml:2615
1992
2052
"The boot loader on SGI machines 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"
2064
2124
#. Tag: replaceable
2065
#: using-d-i.xml:2671
2125
#: using-d-i.xml:2703
2067
2127
msgid "<replaceable>#</replaceable>"
2071
#: using-d-i.xml:2672
2131
#: using-d-i.xml:2704
2073
2133
msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers"
2076
2136
#. Tag: replaceable
2077
#: using-d-i.xml:2680
2137
#: using-d-i.xml:2712
2079
2139
msgid "<replaceable>id</replaceable>"
2083
#: using-d-i.xml:2681
2143
#: using-d-i.xml:2713
2085
2145
msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed"
2089
#: using-d-i.xml:2690
2149
#: using-d-i.xml:2722
2091
2151
msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides"
2094
2154
#. Tag: replaceable
2095
#: using-d-i.xml:2698
2155
#: using-d-i.xml:2730
2101
#: using-d-i.xml:2699
2161
#: using-d-i.xml:2731
2103
2163
msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default."
2107
#: using-d-i.xml:2709
2167
#: using-d-i.xml:2741
2109
2169
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"
2113
#: using-d-i.xml:2715
2173
#: using-d-i.xml:2747
2115
2175
msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>"
2119
#: using-d-i.xml:2725
2179
#: using-d-i.xml:2757
2121
2181
msgid "Install <command>Yaboot</command> on a Hard Disk"
2125
#: using-d-i.xml:2726
2185
#: using-d-i.xml:2758
2127
2187
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;."
2131
#: using-d-i.xml:2744
2191
#: using-d-i.xml:2776
2133
2193
msgid "Install <command>Quik</command> on a Hard Disk"
2137
#: using-d-i.xml:2745
2197
#: using-d-i.xml:2777
2139
2199
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."
2143
#: using-d-i.xml:2761
2203
#: using-d-i.xml:2793
2145
2205
msgid "<command>zipl</command>-installer"
2149
#: using-d-i.xml:2762
2209
#: using-d-i.xml:2794
2151
2211
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>."
2155
#: using-d-i.xml:2779
2215
#: using-d-i.xml:2811
2157
2217
msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk"
2161
#: using-d-i.xml:2781
2221
#: using-d-i.xml:2813
2163
2223
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."
2167
#: using-d-i.xml:2806
2227
#: using-d-i.xml:2838
2169
2229
msgid "Continue Without Boot Loader"
2173
#: using-d-i.xml:2808
2233
#: using-d-i.xml:2840
2175
2235
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>"
2179
#: using-d-i.xml:2817
2239
#: using-d-i.xml:2849
2181
2241
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."
2185
#: using-d-i.xml:2834
2245
#: using-d-i.xml:2866
2187
2247
msgid "Finishing the Installation"
2191
#: using-d-i.xml:2835
2251
#: using-d-i.xml:2867
2193
2253
msgid "This is the last step in the Debian installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;."
2197
#: using-d-i.xml:2848
2257
#: using-d-i.xml:2880
2199
2259
msgid "Setting the System Clock"
2203
#: using-d-i.xml:2850
2263
#: using-d-i.xml:2882
2205
2265
msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed."
2209
#: using-d-i.xml:2857
2269
#: using-d-i.xml:2889
2211
2271
msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase> <phrase arch=\"x86\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC.</phrase>"
2215
#: using-d-i.xml:2868
2275
#: using-d-i.xml:2900
2217
2277
msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made."
2221
#: using-d-i.xml:2883
2281
#: using-d-i.xml:2915
2223
2283
msgid "Reboot the System"
2227
#: using-d-i.xml:2885
2287
#: using-d-i.xml:2917
2229
2289
msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new Debian system."
2233
#: using-d-i.xml:2891
2293
#: using-d-i.xml:2923
2235
2295
msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian; from the DASD which you selected for the root filesystem during the first steps of the installation."
2239
#: using-d-i.xml:2904
2299
#: using-d-i.xml:2936
2241
2301
msgid "Miscellaneous"
2245
#: using-d-i.xml:2905
2305
#: using-d-i.xml:2937
2247
2307
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."
2251
#: using-d-i.xml:2918
2311
#: using-d-i.xml:2950
2253
2313
msgid "Saving the installation logs"
2257
#: using-d-i.xml:2920
2317
#: using-d-i.xml:2952
2259
2319
msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system."
2263
#: using-d-i.xml:2927
2323
#: using-d-i.xml:2959
2265
2325
msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> 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."
2269
#: using-d-i.xml:2947
2329
#: using-d-i.xml:2979
2271
2331
msgid "Using the Shell and Viewing the Logs"
2275
#: using-d-i.xml:2949
2335
#: using-d-i.xml:2981
2277
2337
msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press 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. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself."
2281
#: using-d-i.xml:2967
2341
#: using-d-i.xml:2999
2343
msgid "For the graphical installer see also <xref linkend=\"gtk-using\"/>."
2347
#: using-d-i.xml:3003
2283
2349
msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type <userinput>exit</userinput> to close the shell and return to the installer."
2287
#: using-d-i.xml:2975
2353
#: using-d-i.xml:3011
2289
2355
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 shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history."
2293
#: using-d-i.xml:2984
2359
#: using-d-i.xml:3020
2295
2361
msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory."
2299
#: using-d-i.xml:2991
2365
#: using-d-i.xml:3027
2301
2367
msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging."
2305
#: using-d-i.xml:2997
2371
#: using-d-i.xml:3033
2307
2373
msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell."
2311
#: using-d-i.xml:3012
2377
#: using-d-i.xml:3048
2313
2379
msgid "Installation Over the Network"
2317
#: using-d-i.xml:3014
2383
#: using-d-i.xml:3050
2319
2385
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\"/>.)"
2323
#: using-d-i.xml:3024
2389
#: using-d-i.xml:3060
2325
2391
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>."
2329
#: using-d-i.xml:3037
2395
#: using-d-i.xml:3073
2331
2397
msgid "For installations on &arch-title;, this is the default method after setting up the network."
2335
#: using-d-i.xml:3042
2401
#: using-d-i.xml:3078
2337
2403
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>."
2341
#: using-d-i.xml:3054
2407
#: using-d-i.xml:3090
2343
2409
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."
2347
#: using-d-i.xml:3060
2413
#: using-d-i.xml:3096
2350
2416
"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"