diff options
Diffstat (limited to 'da/using-d-i/modules')
36 files changed, 0 insertions, 1253 deletions
diff --git a/da/using-d-i/modules/alpha/aboot-installer.xml b/da/using-d-i/modules/alpha/aboot-installer.xml deleted file mode 100644 index 60eb48ed6..000000000 --- a/da/using-d-i/modules/alpha/aboot-installer.xml +++ /dev/null @@ -1,19 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14602 untranslated --> - - <sect3 arch="alpha"> - <title>Install <command>aboot</command> on a Hard Disk</title> -<para> - -If you have booted from SRM, if you select this option, the installer -will write <command>aboot</command> to the first sector of the disk on -which you installed Debian. Be <emphasis>very</emphasis> careful - it -is <emphasis>not</emphasis> possible to boot multiple operating -systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix -a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a -different operating system installed on the disk where you have -installed Debian, you will have to boot GNU/Linux from a floppy -instead. - -</para> - </sect3> diff --git a/da/using-d-i/modules/anna.xml b/da/using-d-i/modules/anna.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/anna.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/autopartkit.xml b/da/using-d-i/modules/autopartkit.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/autopartkit.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/base-installer.xml b/da/using-d-i/modules/base-installer.xml deleted file mode 100644 index c2efe72e9..000000000 --- a/da/using-d-i/modules/base-installer.xml +++ /dev/null @@ -1,31 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="base-installer"> - <title>Base System Installation</title> - -<para> - -During the Base installation, package unpacking and setup messages are -redirected to <userinput>tty3</userinput>. You can access this -terminal by pressing -<keycombo><keycap>Left Alt</keycap><keycap>F3</keycap></keycombo>; -get back to the main installer process with -<keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>. - - -</para><para> - -The unpack/setup messages generated by the base installation are saved in -<filename>/var/log/messages</filename> when the installation is -performed over a serial console. - -</para><para> - -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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/baseconfig.xml b/da/using-d-i/modules/baseconfig.xml deleted file mode 100644 index 8bbae29d6..000000000 --- a/da/using-d-i/modules/baseconfig.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="baseconfig"> - <title>Running <command>base-config</command> From Within &d-i;</title> - -<para> - -It is possible to configure the base system within the first stage -installer (before rebooting from the hard drive), by running -<command>base-config</command> in a <firstterm>chroot</firstterm> -environment. This is mainly useful for testing the installer and a -vast majority of people should avoid it. -<!-- Feel free to prove me I'm wrong --> - -</para> - </sect3> diff --git a/da/using-d-i/modules/cdrom-checker.xml b/da/using-d-i/modules/cdrom-checker.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/da/using-d-i/modules/cdrom-checker.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14337 untranslated --> diff --git a/da/using-d-i/modules/cdrom-detect.xml b/da/using-d-i/modules/cdrom-detect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/cdrom-detect.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/choose-mirror.xml b/da/using-d-i/modules/choose-mirror.xml deleted file mode 100644 index 746804ecd..000000000 --- a/da/using-d-i/modules/choose-mirror.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 16990 untranslated --> - -<!-- -- Component is only selected and executed if the installer needs to load - installer components or the base system from the network - (either local or the internet). -- This means you first have to configure a network interface. -- A list of countries is displayed with the default based on the country you - selected earlier. -- Note that not all mirrors are equal (see http://www.nl.debian.org/mirror/list) -- Selection of a local mirror (at top of the list: manual selection). -- After selecting a country, a list of mirrors in the country will be shown. - -- The selected mirror will be tested. -- How to handle problems with mirrors. --->
\ No newline at end of file diff --git a/da/using-d-i/modules/ddetect.xml b/da/using-d-i/modules/ddetect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/ddetect.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/finish-install.xml b/da/using-d-i/modules/finish-install.xml deleted file mode 100644 index 309739b75..000000000 --- a/da/using-d-i/modules/finish-install.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21672 untranslated --> - - <sect3 id="finish-install"> - <title>Finish the Installation and Reboot</title> - -<para> - -This is the last step in the initial Debian installation process. You will -be prompted to remove the boot media (CD, floppy, etc) that you used to -boot the installer. The installer will do any last minute tasks, and then -reboot into your new Debian system. - -</para><para arch="s390"> - -Select the <guimenuitem>Finish the installation</guimenuitem> -menu item which will halt the system -because rebooting is not supported on &arch-title; in this case. You -then need to IPL GNU/Linux from the DASD which you selected for the -root filesystem during the first steps of the installation. - -</para> - </sect3> diff --git a/da/using-d-i/modules/hppa/palo-installer.xml b/da/using-d-i/modules/hppa/palo-installer.xml deleted file mode 100644 index 84a3608e8..000000000 --- a/da/using-d-i/modules/hppa/palo-installer.xml +++ /dev/null @@ -1,20 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14602 untranslated --> - - <sect3 arch="hppa"> - <title><command>palo</command>-installer</title> -<para> - -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. - -</para><para condition="FIXME"> - -hppa FIXME ( need more info ) - -</para> - </sect3> diff --git a/da/using-d-i/modules/ia64/elilo-installer.xml b/da/using-d-i/modules/ia64/elilo-installer.xml deleted file mode 100644 index 9c9050d0b..000000000 --- a/da/using-d-i/modules/ia64/elilo-installer.xml +++ /dev/null @@ -1,135 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 18660 untranslated --> - - <sect3 arch="ia64"> - <title>Install the <command>ELILO</command> Boot Loader - on a Hard Disk</title> -<para> - -The &architecture; boot loader is called <quote>elilo</quote>. -It is modeled on the <quote>lilo</quote> boot loader for the -x86 architecture and uses a similar configuration file. -However, instead of writing an MBR or partition boot record to -the disk, it copies the necessary files to a separate FAT formatted -disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> -menu in the firmware to point to the files in the EFI partition. -The <command>elilo</command> boot loader is really in two parts. -The <filename>/usr/sbin/elilo</filename> command manages the partition and -copies file into it. -The <filename>elilo.efi</filename> program is copied into the EFI -partition and then run by the <quote>EFI Boot Manager</quote> to actually -do the work of loading and starting the Linux kernel. - -</para><para> - -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. - -</para> - - <warning><title>Choose the correct partition!</title> - -<para> - -The criteria for selecting a partition is that it is FAT format -filesystem with its <emphasis>boot</emphasis> flag set. -&d-i; may show multiple choices depending on what it finds from scanning -all of the disks of the system including EFI partitions of other system -disks and EFI diagnostic partitions. -Remember, the <command>elilo</command> may format the partition during -the installation, erasing any previous contents! - -</para></warning> - - </sect3> - - <sect3 arch="ia64"> - <title>EFI Partition Contents</title> - -<para> - -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> filesytem. -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<emphasis>n</emphasis>:\efi\debian</filename>. -There may be other files in this filesystem as well over time as -the system is updated or re-configured. - -</para> - -<variablelist> - -<varlistentry> -<term><filename>elilo.conf</filename></term> -<listitem><para> - -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. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>elilo.efi</filename></term> -<listitem><para> - -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. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>initrd.img</filename></term> -<listitem><para> - -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>. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>readme.txt</filename></term> -<listitem><para> - -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. - -</para></listitem></varlistentry> - -<varlistentry> -<term><filename>vmlinuz</filename></term> -<listitem><para> - -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>. - -</para></listitem></varlistentry> - -</variablelist> - - </sect3> diff --git a/da/using-d-i/modules/iso-scan.xml b/da/using-d-i/modules/iso-scan.xml deleted file mode 100644 index f86cb4954..000000000 --- a/da/using-d-i/modules/iso-scan.xml +++ /dev/null @@ -1,47 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 18640 untranslated --> - - <sect3 id="iso-scan"> - <title>Looking for the Debian Installer ISO Image</title> -<para> - -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. - -</para><para> - -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 valid Debian iso image or -not. In the former case we are done, in the latter -<command>iso-scan</command> seeks for another image. - -</para><para> - -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 more throughly search. This pass doesn't look only into the -topmost directories, but really traverses whole filesystem. - -</para><para> - -If <command>iso-scan</command> does not discover your installer iso -image, reboot back to your original operating system and check if the -image has correct name (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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/kbd-chooser.xml b/da/using-d-i/modules/kbd-chooser.xml deleted file mode 100644 index b108ca1e4..000000000 --- a/da/using-d-i/modules/kbd-chooser.xml +++ /dev/null @@ -1,44 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="kbd-chooser"> - <title>Choosing a Keyboard</title> - -<para> - -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). - -</para><para> - -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. - -</para><para arch="mipsel"> - -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. - -</para><para arch="powerpc"> - -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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/lowmem.xml b/da/using-d-i/modules/lowmem.xml deleted file mode 100644 index 15cb78f91..000000000 --- a/da/using-d-i/modules/lowmem.xml +++ /dev/null @@ -1,21 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 16990 untranslated --> - - <sect3 id="lowmem"> - <title>Check available memory</title> - -<para> - -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. - -</para><para> - -During a low memory install, not all components will be available. -One of the limitations is that you won't be able to choose a -language for the installation. - -</para> - </sect3>
\ No newline at end of file diff --git a/da/using-d-i/modules/mdcfg.xml b/da/using-d-i/modules/mdcfg.xml deleted file mode 100644 index bff80ee04..000000000 --- a/da/using-d-i/modules/mdcfg.xml +++ /dev/null @@ -1,180 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 22841 untranslated --> - - <sect3 id="mdcfg"> - <title>Configuring Multidisk Device (Software RAID)</title> -<para> - -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 set up 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>). - -</para><para> - -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.). - -</para><para> - -The benefit you gain depends on a type of a MD device you are -creating. Currently supported are: - -<variablelist> -<varlistentry> - -<term>RAID0</term><listitem><para> - -Is mainly aimed at performance. RAID0 splits all incomming data into -<firstterm>stripes</firstterm> and distributes them equally over each -disk in the array. This can increase the speed of read/write -operations, but when one of the disks fails, you will loose -<emphasis>everything</emphasis> (part of the information is still on -the healthy disk(s), the other part <emphasis>was</emphasis> on the -failed disk). - -</para><para> - -The typical use for RAID0 is a partition for video editing. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>RAID1</term><listitem><para> - -Is suitable for setups where reliability is the first concern. It -consists of several (usualy two) equaly sized partitions where every -partition contains exactly the same data. This essentialy 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> -</variablelist> - -To sum it up: - -<informaltable> -<tgroup cols="5"> -<thead> -<row> - <entry>Type</entry> - <entry>Minimum Devices</entry> - <entry>Spare Device</entry> - <entry>Survives disk failure?</entry> - <entry>Available Space</entry> -</row> -</thead> - -<tbody> -<row> - <entry>RAID0</entry> - <entry>2</entry> - <entry>no</entry> - <entry>no</entry> - <entry>Size of the smallest partition multiplied by number of devices in RAID</entry> -</row> - -<row> - <entry>RAID1</entry> - <entry>2</entry> - <entry>optional</entry> - <entry>yes</entry> - <entry>Size of the smallest partition in RAID</entry> -</row> - -</tbody></tgroup></informaltable> - -</para><para> - -If you want to know the whole truth about Software RAID, have a look -at <ulink url="&url-software-raid-howto;">Software RAID HOWTO</ulink>. - -</para><para> - -To create an 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>Use the partition as a RAID -device</guimenuitem> </menuchoice>.) - -</para><warning><para> - -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. - -</para></warning><para> - -Next, you should choose <guimenuitem>Configure software -RAID</guimenuitem> from the main <command>partman</command> menu. -On the first screen of <command>mdcfg</command> simply select -<guimenuitem>Create MD device</guimenuitem>. You will be presented with -a list of supported types of MD devices, from which you should choose -one (e.g. RAID1). What follows depends on the type of MD you selected. -</para> - -<itemizedlist> -<listitem><para> - -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. - -</para></listitem> -<listitem><para> - -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 a different number of partitions, the &d-i; won't let you -continue until you correct the issue. - -</para></listitem> -</itemizedlist> - -<para> - -It is perfectly possible to have several types of MD at once. For -example if you have three 200 GB hard drives dedicated to MD, each -containing two 100 GB partitions, you can combine first partitions on -all three disk into the RAID0 (fast 300 GB video editing partition) -and use the other three partitions (2 active and 1 spare) for RAID1 -(quite reliable 100 GB partition for <filename>/home</filename>). - -</para><para> - -After you set up 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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/mips/arcboot-installer.xml b/da/using-d-i/modules/mips/arcboot-installer.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/mips/arcboot-installer.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/mipsel/colo-installer.xml b/da/using-d-i/modules/mipsel/colo-installer.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/da/using-d-i/modules/mipsel/colo-installer.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14337 untranslated --> diff --git a/da/using-d-i/modules/mipsel/delo-installer.xml b/da/using-d-i/modules/mipsel/delo-installer.xml deleted file mode 100644 index d355f86b9..000000000 --- a/da/using-d-i/modules/mipsel/delo-installer.xml +++ /dev/null @@ -1,80 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14602 untranslated --> - - <sect3 arch="mipsel"> - <title><command>delo</command>-installer</title> -<para> - -The boot loader on DECstations is <command>DELO</command>. -It has to be installed on the same hard disk as the kernel (this is done -automatically by the installer). DELO supports different configurations -which are set up in <filename>/etc/delo.conf</filename>. Each -configuration has a unique name, -the default setup as created by the installer is <quote>linux</quote>. -After DELO has been installed, the system can be booted from hard disk -by entering - -<informalexample><screen> - -<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput> - -</screen></informalexample> - -on the firmware prompt. - -</para> - -<variablelist> -<varlistentry> -<term> <replaceable>#</replaceable> </term> -<listitem><para> - -is the TurboChannel device to be booted from, on most DECstations this -is <userinput>3</userinput> for the onboard controllers - -</para></listitem> -</varlistentry> -<varlistentry> -<term> <replaceable>id</replaceable> </term> -<listitem><para> - -is the SCSI ID of the hard disk on which <command>DELO</command> is -installed - -</para></listitem> -</varlistentry> -<varlistentry> -<term> <replaceable>partnr</replaceable> </term> -<listitem><para> - -is the number of the partition on which -<filename>/etc/delo.conf</filename> resides - -</para></listitem> -</varlistentry> -<varlistentry> -<term> <replaceable>name</replaceable> </term> -<listitem><para> - -is the name of the configuration entry in -<filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by -default. - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -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 - -<informalexample><screen> - -<userinput>boot #/rz<replaceable>id</replaceable></userinput> - -</screen></informalexample> - -</para> - </sect3> diff --git a/da/using-d-i/modules/netcfg.xml b/da/using-d-i/modules/netcfg.xml deleted file mode 100644 index 3880b0bf8..000000000 --- a/da/using-d-i/modules/netcfg.xml +++ /dev/null @@ -1,58 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="netcfg"> - <title>Configuring Network</title> - -<para> - -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. - -</para><para> - -By default, &d-i; tries to configure your computer's network -automatically via DHCP. If 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 -DHCP server in your local network at all. For further explanation -check the error messages on the third console. In any case, you will -be asked, if you want to retry, or if you want to perform manual -setup. DHCP servers are sometimes really slow in their responses, so -if you are sure everything is in place, try again. - -</para><para> - -The manual network setup in turn asks you 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"/>. - -</para><note><para> - -Some technical details you might, or might not, find handy: the -program assumes the network IP address is the bitwise-AND of your -system's IP address and your netmask. It will guess the broadcast -address is the bitwise OR of your system's IP address with the bitwise -negation of the netmask. It will also guess your gateway. If you -can't find any of these answers, use the system's guesses — you -can change them once the system has been installed, if necessary, by -editing <filename>/etc/network/interfaces</filename>. Alternatively, -you can install <classname>etherconf</classname>, which will step you -through your network setup. - -</para></note> - </sect3> diff --git a/da/using-d-i/modules/nobootloader.xml b/da/using-d-i/modules/nobootloader.xml deleted file mode 100644 index f19398003..000000000 --- a/da/using-d-i/modules/nobootloader.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="nobootloader"> - <title>Continue Without Boot Loader</title> - -<para> - -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> - -</para> - </sect3> diff --git a/da/using-d-i/modules/os-prober.xml b/da/using-d-i/modules/os-prober.xml deleted file mode 100644 index 840cd3d3b..000000000 --- a/da/using-d-i/modules/os-prober.xml +++ /dev/null @@ -1,37 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 22664 untranslated --> - - <sect3 id="os-prober"> - <title>Detecting other operating systems</title> - -<para> - -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. - -</para><para> - -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. - -<!-- TODO: Maybe include some arch-dependent tables with supported OS'es here --> - -</para> - -<note><para> - -The installer may fail to detect other operating systems if the partitions on -which they reside are mounted when the detection takes place. This may occur if -you select a mountpoint (e.g. /win) for a partition containing another operating -system in <command>partman</command>, or if you have mounted partitions manually -from a console. - -</para></note> - - </sect3> diff --git a/da/using-d-i/modules/partconf.xml b/da/using-d-i/modules/partconf.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/partconf.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/partitioner.xml b/da/using-d-i/modules/partitioner.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/da/using-d-i/modules/partitioner.xml +++ /dev/null @@ -1,3 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - diff --git a/da/using-d-i/modules/partman-lvm.xml b/da/using-d-i/modules/partman-lvm.xml deleted file mode 100644 index de753b72d..000000000 --- a/da/using-d-i/modules/partman-lvm.xml +++ /dev/null @@ -1,58 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 22469 untranslated --> - - <sect3 id="partman-lvm"> - <title>Configuring Logical Volume Manager (LVM)</title> -<para> - -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 (usualy the most important one) was short on -space, while some other partition was grossly underused and you had to -manage this situation by moving stuff around, symlinking, etc. - -</para><para> - -To avoid the described situation you can use Logical Volume Manager -(LVM). Simply said, with LVM you can combine your partitions -(<firstterm>physical volumes</firstterm> in LVM lingo) to form -a virtual disc (so called <firstterm>volume group</firstterm>), which -can then be divided into virtual partitions (<firstterm>logical -volumes</firstterm>). The point is that logical volumes (and of course -underlying volume groups) can span across several physical discs. - -</para><para> - -Now when you realize you need more space for your old 160GB -<filename>/home</filename> partition, you can simply add a new 300GB -disc to the computer, join it with your existing volume group and then -resize the logical volume which holds your <filename>/home</filename> -filesystem and voila - your users have some room again on their -renewed 460GB partition. This example is of course a bit -oversimplified. If you haven't read it yet, you should consult the -<ulink url="&url-lvm-howto;">LVM HOWTO</ulink>. - -</para><para> - -LVM setup in &d-i; is quite simple. At first, you have to mark your -partitions to be used as physical volumes for LVM. (This is done in -<command>partman</command> in the <guimenu>Partition -settings</guimenu> menu where you should select <menuchoice> -<guimenu>Use as:</guimenu> <guimenuitem>physical volume for -LVM</guimenuitem> </menuchoice>.) Then start the -<command>lvmcfg</command> module (either directly from -<command>partman</command> or from the &d-i;'s main menu) and combine -physical volumes to volume group(s) under the <guimenuitem>Modify -volume groups (VG)</guimenuitem> menu. After that, you should create -logical volumes on the top of volume groups from the menu -<guimenuitem>Modify logical volumes (LV)</guimenuitem>. - -</para><para> - -After returning from <command>lvmcfg</command> back to -<command>partman</command>, you will see any created logical volumes -in the same way as ordinary partitions (and you should treat them like -that). - -</para> - </sect3> diff --git a/da/using-d-i/modules/partman.xml b/da/using-d-i/modules/partman.xml deleted file mode 100644 index e7e472eb8..000000000 --- a/da/using-d-i/modules/partman.xml +++ /dev/null @@ -1,193 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="partman"> - <title>Partitioning Your Disks</title> - -<para> - -Now it is time to partition your disks. If you are uncomfortable with -partitioning, or just want to know more details, see <xref -linkend="partitioning"/>. - -</para><para> - -First you will be given the opportunity to automatically partition -either an entire drive, or free space on a drive. This is also called -<quote>guided</quote> partitioning. If you do not want to -autopartition, choose <guimenuitem>Manually edit partition -table</guimenuitem> from the menu. - -</para><para> - -If you choose guided partitioning, you will be able to choose from the -schemes listed in the table below. All schemes have their pros and cons, -some of which are discussed in <xref linkend="partitioning"/>. If you are -unsure, choose the first one. Bear in mind, that guided partitioning -needs certain minimal amount of free space to operate with. If you don't -give it at least about 1GB of space (depends on chosen scheme), guided -partitioning will fail. - -</para> - -<informaltable> -<tgroup cols="3"> -<thead> -<row> - <entry>Partitioning scheme</entry> - <entry>Minimum space</entry> - <entry>Created partitions</entry> -</row> -</thead> - -<tbody> -<row> - <entry>All files in one partition</entry> - <entry>600MB</entry> - <entry><filename>/</filename>, swap</entry> -</row><row> - <entry>Desktop machine</entry> - <entry>500MB</entry> - <entry> - <filename>/</filename>, <filename>/home</filename>, swap - </entry> -</row><row> - <entry>Multi-user workstation</entry> - <entry>1GB</entry> - <entry> - <filename>/</filename>, <filename>/home</filename>, - <filename>/usr</filename>, <filename>/var</filename>, - <filename>/tmp</filename>, swap - </entry> -</row> - -</tbody></tgroup></informaltable> - -<para arch="ia64"> - -If you chose an automatic partitioning for your IA64 system, there -will be an additional partition, formatted as a FAT16 bootable filesystem, -for the EFI boot loader. -There is also an additional menu item in the formatting menu to manually -set up a partition as an EFI boot partition. - -</para><para> - -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. - -</para><para> - -The list of partitions might look like this: - -<!-- TODO: show some flags here (lightning, skull, smiley) --> -<informalexample><screen> - IDE1 master (hda) - 6.4 GB WDC AC36400L - #1 primary 16.4 MB ext2 /boot - #2 primary 551.0 MB swap swap - #3 primary 5.8 GB ntfs - pri/log 8.2 MB FREE SPACE - - IDE1 slave (hdb) - 80.0 GB ST380021A - #1 primary 15.9 MB ext3 - #2 primary 996.0 MB fat16 - #3 primary 3.9 GB xfs /home - #5 logical 6.0 GB ext3 / - #6 logical 1.0 GB ext3 /var - #7 logical 498.8 GB ext3 - #8 logical 551.5 GB swap swap - #9 logical 65.8 GB ext2 -</screen></informalexample> - -This example shows two IDE harddrives divided into several partitions; -the first disk has some free space. Each partition line consists of the -partition number, its type, size, optional flags, file system, and -mountpoint (if any). - -</para><para> - -This concludes the guided partitioning. If you are satisfied with the -generated partition table, you can choose <guimenuitem>Finish -partitioning and write changes to disk</guimenuitem> from the menu to -implement the new partition table (as described at the end of this -section). If you are not happy, you can choose to <guimenuitem>Undo -changes to partitions</guimenuitem>, to run guided partitioning again -or modify the proposed changes as described below for manual partitioning. - -</para><para> - -A similar screen to the one shown just above will be displayed if you -choose manual partioning except that your existing partition table will -be shown and without the mount points. How to manually set up your partition -table and the usage of partitions by your new Debian system will be covered -in the remainder of this section. - -</para><para> - -If you select a pristine disk which doesn't have neither partitions -nor free space on it, you will be offered to create a new partition -table (this is needed so you can create new partitions). After this -a new line entitled <quote>FREE SPACE</quote> should appear under the -selected disk. - -</para><para> - -If you select some free space, you will be offered to create new -partition. You will have to answer a quick series of questions about -its size, type (primary or logical), and location (begining or end of -the free space). After this, you will be presented with detailed -overview of your new partition. There are options like mountpoint, -mount options, bootable flag, or way of usage. If you don't like the -preselected defaults, feel free to change them to your liking. E.g. by -selecting the option <guimenuitem>Use as:</guimenuitem>, you can -choose different filesystem for this partition including the -possibility to use the partition for swap, software RAID, LVM, or not -use it at all. Other nice feature is the possibility to copy data from -existing partition onto this one. -When you are satisfied with your new partition, select -<guimenuitem>Finished with partition</guimenuitem> and you will be -thrown back to the <command>partman</command>'s main screen. - -</para><para> - -If you decide you want to change something about your partition, -simply select the partition, which will bring you to the partition -configuration menu. Because this is the same screen like when creating -a new partition, you can change the same set of options. One thing -which might not be very obvious at a first glance is that you can -resize the partition by selecting the item displaying the size of the -partition. Filesystems known to work are at least fat16, fat32, ext2, -ext3 and swap. This menu also allows you to delete a partition. - -</para><para> - -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. - -</para><para arch="ia64"> - -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. - -</para><para> - -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>). - -</para><para> - -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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/powerpc/quik-installer.xml b/da/using-d-i/modules/powerpc/quik-installer.xml deleted file mode 100644 index ed6aa6a60..000000000 --- a/da/using-d-i/modules/powerpc/quik-installer.xml +++ /dev/null @@ -1,15 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14975 untranslated --> - - <sect3 arch="powerpc"> - <title>Install <command>Quik</command> on a Hard Disk</title> -<para> - -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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/powerpc/yaboot-installer.xml b/da/using-d-i/modules/powerpc/yaboot-installer.xml deleted file mode 100644 index 4bba348fb..000000000 --- a/da/using-d-i/modules/powerpc/yaboot-installer.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14975 untranslated --> - - <sect3 arch="powerpc"> - <title>Install <command>Yaboot</command> on a Hard Disk</title> -<para> - -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;. - -</para> - </sect3> diff --git a/da/using-d-i/modules/s390/dasd.xml b/da/using-d-i/modules/s390/dasd.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/s390/dasd.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/s390/netdevice.xml b/da/using-d-i/modules/s390/netdevice.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/s390/netdevice.xml +++ /dev/null @@ -1,2 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> diff --git a/da/using-d-i/modules/s390/zipl-installer.xml b/da/using-d-i/modules/s390/zipl-installer.xml deleted file mode 100644 index 61aa6465c..000000000 --- a/da/using-d-i/modules/s390/zipl-installer.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 14602 untranslated --> - - <sect3 arch="s390"> - <title><command>zipl</command>-installer</title> -<para> - -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>. - -</para> - </sect3> diff --git a/da/using-d-i/modules/save-logs.xml b/da/using-d-i/modules/save-logs.xml deleted file mode 100644 index d905024ba..000000000 --- a/da/using-d-i/modules/save-logs.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="bugreporter"> - <title>Saving the installation logs</title> - -<para> - -If the installation is successful, the logfiles created during -the installation process will be automatically saved to -<filename>/var/log/debian-installer/</filename> on your new -Debian system. - -</para><para> - -Choosing <guimenuitem>Save debug logs</guimenuitem> from the main -menu allows you to save the log files to a floppy disk. 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. - -</para> - </sect3> diff --git a/da/using-d-i/modules/shell.xml b/da/using-d-i/modules/shell.xml deleted file mode 100644 index 0e26048a0..000000000 --- a/da/using-d-i/modules/shell.xml +++ /dev/null @@ -1,41 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 21579 untranslated --> - - <sect3 id="shell"> - <title>Using the Shell and Viewing the Logs</title> - <!-- TODO: There is nothing about logs in this section! --> - -<para> - -There is an <guimenuitem>Execute a Shell</guimenuitem> item on the -menu. If the menu is not available when you need to use the shell, -press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> -(on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> -</keycombo>) to switch to the second <emphasis>virtual -console</emphasis>. That's the <keycap>Alt</keycap> key on the -left-hand side of the <keycap>space bar</keycap>, and the -<keycap>F2</keycap> function key, at the same time. This is a separate -window running a Bourne shell clone called <command>ash</command>. - -</para><para> - -At this point you are booted from the RAM disk, and there is a limited -set of Unix utilities available for your use. You can see what -programs are available with the command <command>ls /bin /sbin /usr/bin -/usr/sbin</command> and by typing <command>help</command>. The -text editor is <command>nano</command>. The shell has some nice features -like autocompletion and history. - -</para><para> - -Use the menus to perform any task that they are able to do — the -shell and commands are only there in case something goes wrong. In -particular, you should always use the menus, not the shell, to -activate your swap partition, because the menu software can't detect -that you've done this from the shell. Press <keycombo><keycap>Left -Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or -type <command>exit</command> if you used a menu item to open the -shell. - -</para> - </sect3> diff --git a/da/using-d-i/modules/sparc/silo-installer.xml b/da/using-d-i/modules/sparc/silo-installer.xml deleted file mode 100644 index f459a8cb1..000000000 --- a/da/using-d-i/modules/sparc/silo-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 16467 untranslated --> - - <sect3 arch="sparc"> - <title>Install the <command>SILO</command> Boot Loader - on a Hard Disk</title> -<para> - -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 -along side an existing SunOS/Solaris install. - -</para> - </sect3> diff --git a/da/using-d-i/modules/x86/grub-installer.xml b/da/using-d-i/modules/x86/grub-installer.xml deleted file mode 100644 index 5a0159b01..000000000 --- a/da/using-d-i/modules/x86/grub-installer.xml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39622 untranslated --> - - <sect3 arch="x86"> - <title>Install the <command>Grub</command> Boot Loader - on a Hard Disk</title> -<para> - -The main &architecture; boot loader is called <quote>grub</quote>. -Grub is a flexible and robust boot loader and a good default choice for -newbies and old hands alike. - -</para><para> - -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. - -</para><para> - -If you do not want to install grub at all, use the Back button to get to -the main menu, and from there select whatever bootloader you would like to -use. - -</para> - </sect3> diff --git a/da/using-d-i/modules/x86/lilo-installer.xml b/da/using-d-i/modules/x86/lilo-installer.xml deleted file mode 100644 index 0f38f727d..000000000 --- a/da/using-d-i/modules/x86/lilo-installer.xml +++ /dev/null @@ -1,70 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 22664 untranslated --> - - <sect3 arch="x86"> - <title>Install the <command>LILO</command> Boot Loader - on a Hard Disk</title> -<para> - -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>. - -</para> -<note><para> - -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 linux and the hurd after the installation. - -</para></note> -<para> - -&d-i; presents you three choices where to install the -<command>LILO</command> boot loader: - -<variablelist> -<varlistentry> -<term>Master Boot Record (MBR)</term><listitem><para> - -This way the <command>LILO</command> will take complete control of the -boot process. - -</para></listitem></varlistentry> -<varlistentry> -<term>new Debian partition</term><listitem><para> - -Choose this if you want to use another boot -manager. <command>LILO</command> will install itself at the begining -of the new Debian partition and it will serve as a secondary boot -loader. - -</para></listitem></varlistentry> -<varlistentry> -<term>Other choice</term><listitem><para> - -Useful for advanced users who want to install <command>LILO</command> -somewhere else. In this case you will be asked for desired -location. You can use devfs style names, such as those that start with -<filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and -<filename>/dev/discs</filename>, as well as traditional names, such as -<filename>/dev/hda</filename> or <filename>/dev/sda</filename>. - -</para></listitem></varlistentry> -</variablelist> - -</para><para> - -If you can no longer boot into Windows 9x (or DOS) after this step, -you'll need to use a Windows 9x (MS-DOS) boot disk and use the -<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS -master boot record — however, this means that you'll need to use -some other way to get back into Debian! For more information on this -please read <xref linkend="reactivating-win"/>. - -</para> - </sect3> |