diff options
author | Jeroen Schot <schot@a-eskwadraat.nl> | 2012-08-29 15:10:27 +0000 |
---|---|---|
committer | Jeroen Schot <schot@a-eskwadraat.nl> | 2012-08-29 15:10:27 +0000 |
commit | a292182f917a4104b223016e041410498f4d47a3 (patch) | |
tree | 31983bd3bb12e47ca30a949da0d472b93796a9ea | |
parent | f842e23756734b3ce4932695707bc416810e46cc (diff) | |
download | installation-guide-a292182f917a4104b223016e041410498f4d47a3.zip |
Restart Dutch translation of D-I manual in PO format.
157 files changed, 73 insertions, 18297 deletions
diff --git a/nl/administrivia/administrivia.xml b/nl/administrivia/administrivia.xml deleted file mode 100644 index a6a268923..000000000 --- a/nl/administrivia/administrivia.xml +++ /dev/null @@ -1,153 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43043 untranslated --> - -<appendix id="administrivia"> - <title>Administrivia</title> - - - <sect1 id="about"> - <title>About This Document</title> - -<para> - -This manual was created for Sarge's debian-installer, based on -the Woody installation manual for boot-floppies, which was based -on earlier Debian installation manuals, and on the Progeny -distribution manual which was released under GPL in 2003. - -</para><para> - -This document is written in DocBook XML. Output formats are generated -by various programs using information from the -<classname>docbook-xml</classname> and -<classname>docbook-xsl</classname> packages. - -</para><para> - -In order to increase the maintainability of this document, we use -a number of XML features, such as entities and profiling attributes. -These play a role akin to variables and conditionals in programming -languages. The XML source to this document contains information for -each different architecture — profiling attributes are used to -isolate certain bits of text as architecture-specific. - -</para><para condition="about-langteam"> - -Translators can use this paragraph to acknowledge the people responsible -for the translation of the manual. -Translation teams are advised to just mention the coordinator and maybe -major contributors and thank everybody else in a phrase like "all -translators and reviewers from the translation team for {your language} -at {your l10n mailinglist}". - -See build/lang-options/README on how to enable this paragraph. -Its condition is "about-langteam". - -</para> - </sect1> - - <sect1 id="contributing"> - <title>Contributing to This Document</title> - -<para> - -If you have problems or suggestions regarding this document, you -should probably submit them as a bug report against the package -<classname>installation-guide</classname>. See the -<classname>reportbug</classname> package or read the online -documentation of the <ulink url="&url-bts;">Debian Bug -Tracking System</ulink>. It would be nice if you could check the -<ulink url="&url-bts;installation-guide">open bugs against -installation-guide</ulink> to see whether your problem has -already been reported. If so, you can supply additional corroboration -or helpful information to -<email><replaceable>XXXX</replaceable>@bugs.debian.org</email>, -where <replaceable>XXXX</replaceable> is the number for the -already-reported bug. - -</para><para> - -Better yet, get a copy of the DocBook source for this document, and -produce patches against it. The DocBook source can be found at the -<ulink url="&url-d-i-websvn;">debian-installer WebSVN</ulink>. If -you're not familiar with DocBook, don't worry: -there is a simple cheatsheet in the manuals directory that will get -you started. It's like html, but oriented towards the meaning of -the text rather than the presentation. Patches submitted to the -debian-boot mailing list (see below) are welcomed. -For instructions on how to check out the sources via SVN, see -<ulink url="&url-d-i-readme;">README</ulink> -from the source root directory. - -</para><para> - -Please do <emphasis>not</emphasis> contact the authors of this -document directly. There is also a discussion list for &d-i;, which -includes discussions of this manual. The mailing list is -<email>debian-boot@lists.debian.org</email>. Instructions for -subscribing to this list can be found at the <ulink -url="&url-debian-lists-subscribe;">Debian Mailing -List Subscription</ulink> page; or you can browse the <ulink -url="&url-debian-list-archives;">Debian Mailing List Archives</ulink> -online. - -</para> - - </sect1> - - <sect1 id="contributors"> - <title>Major Contributions</title> - -<para> - -This document was originally written by Bruce Perens, Sven Rudolph, Igor -Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the -Installation Howto. -Many, many Debian users and developers contributed to this document. -Particular note must be made of Michael Schmitz (m68k support), Frank -Neumann (original author of the <ulink -url="&url-m68k-old-amiga-install;">Amiga install manual</ulink>), -Arto Astala, Eric Delaunay/Ben Collins (SPARC information), Tapio -Lehtonen, and Stéphane Bortzmeyer for numerous edits and text. -We have to thank Pascal Le Bail for useful information about booting -from USB memory sticks. Miroslav Kuře has documented a lot of the new -functionality in Sarge's debian-installer. - -</para><para> - -Extremely helpful text and information was found in Jim Mintha's HOWTO -for network booting (no URL available), the <ulink -url="&url-debian-faq;">Debian FAQ</ulink>, the <ulink -url="&url-m68k-faq;">Linux/m68k FAQ</ulink>, the <ulink -url="&url-sparc-linux-faq;">Linux for SPARC Processors -FAQ</ulink>, the <ulink -url="&url-alpha-faq;">Linux/Alpha -FAQ</ulink>, amongst others. The maintainers of these freely -available and rich sources of information must be recognized. - -</para><para> - -The section on chrooted installations in this manual -(<xref linkend="linux-upgrade"/>) was derived in part from -documents copyright Karsten M. Self. - -</para><para arch="x86"> - -The section on installations over plip in this manual -(<xref linkend="plip"/>) was based on the -<ulink url="&url-plip-install-howto;">PLIP-Install-HOWTO</ulink> -by Gilles Lamiral. - -</para> - </sect1> - - <sect1 id="trademarks"> - <title>Trademark Acknowledgement</title> -<para> - -All trademarks are property of their respective trademark owners. - -</para> - </sect1> -</appendix> - diff --git a/nl/appendix/chroot-install.xml b/nl/appendix/chroot-install.xml deleted file mode 100644 index 3198bf108..000000000 --- a/nl/appendix/chroot-install.xml +++ /dev/null @@ -1,675 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 63062 untranslated --> - - <sect1 id="linux-upgrade"> - <title>Installing &debian-gnu; from a Unix/Linux System</title> - -<para> - -This section explains how to install &debian-gnu; from an existing -Unix or Linux system, without using the menu-driven installer as -explained in the rest of the manual. This <quote>cross-install</quote> -HOWTO has been requested by users switching to &debian-gnu; from -Red Hat, Mandriva, and SUSE. In this section some familiarity with -entering *nix commands and navigating the file system is assumed. In -this section, <prompt>$</prompt> symbolizes a command to be entered in -the user's current system, while <prompt>#</prompt> refers to a -command entered in the &debian; chroot. - -</para><para> - -Once you've got the new &debian; system configured to your preference, -you can migrate your existing user data (if any) to it, and keep on -rolling. This is therefore a <quote>zero downtime</quote> &debian-gnu; -install. It's also a clever way for dealing with hardware that -otherwise doesn't play friendly with various boot or installation -media. - -</para> - -<note><para> - -As this is a mostly manual procedure, you should bear in mind that you -will need to do a lot of basic configuration of the system yourself, -which will also require more knowledge of &debian; and of &arch-kernel; in general -than performing a regular installation. You cannot expect this procedure -to result in a system that is identical to a system from a regular -installation. You should also keep in mind that this procedure only -gives the basic steps to set up a system. Additional installation and/or -configuration steps may be needed. - -</para></note> - - <sect2> - <title>Getting Started</title> -<para> - -With your current *nix partitioning tools, repartition the hard -drive as needed, creating at least one filesystem plus swap. You -need around &base-system-size;MB of space available for a console only install, -or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to -install desktop environments like GNOME or KDE). - -</para><para> - -Next, create file systems on the partitions. For example, to create an -ext3 file system on partition <filename>/dev/hda6</filename> (that's -our example root partition): - -<informalexample><screen> -# mke2fs -j /dev/<replaceable>hda6</replaceable> -</screen></informalexample> - -To create an ext2 file system instead, omit <userinput>-j</userinput>. - -</para><para> - -Initialize and activate swap (substitute the partition number for -your intended &debian; swap partition): - -<informalexample><screen> -# mkswap /dev/<replaceable>hda5</replaceable> -# sync; sync; sync -# swapon /dev/<replaceable>hda5</replaceable> -</screen></informalexample> - -Mount one partition as <filename>/mnt/debinst</filename> (the -installation point, to be the root (<filename>/</filename>) filesystem -on your new system). The mount point name is strictly arbitrary, it is -referenced later below. - -<informalexample><screen> -# mkdir /mnt/debinst -# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst -</screen></informalexample> - -</para> -<note><para> - -If you want to have parts of the filesystem (e.g. /usr) mounted on -separate partitions, you will need to create and mount these directories -manually before proceding with the next stage. - -</para></note> - </sect2> - - <sect2> - <title>Install <command>debootstrap</command></title> -<para> - -The utility used by the &debian; installer, and recognized as the -official way to install a &debian; base system, is -<command>debootstrap</command>. It uses <command>wget</command> and -<command>ar</command>, but otherwise depends only on -<classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> - -<para> - -These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. - -</para> - -</footnote>. Install <command>wget</command> and -<command>ar</command> if they aren't already on your current system, -then download and install <command>debootstrap</command>. - -</para> - -<!-- The files linked to here are from 2004 and thus currently not usable -<para> - -If you have an rpm-based system, you can use alien to convert the -.deb into .rpm, or download an rpm-ized version at -<ulink url="http://people.debian.org/~blade/install/debootstrap"></ulink> - -</para> ---> - -<para> - -Or, you can use the following procedure to install it -manually. Make a work folder for extracting the .deb into: - -<informalexample><screen> -# mkdir work -# cd work -</screen></informalexample> - -The <command>debootstrap</command> binary is located in the &debian; -archive (be sure to select the proper file for your -architecture). Download the <command>debootstrap</command> .deb from -the <ulink url="http://ftp.debian.org/debian/pool/main/d/debootstrap/"> -pool</ulink>, copy the package to the work folder, and extract the -files from it. You will need to have root privileges to install -the files. - -<informalexample><screen> -# ar -x debootstrap_0.X.X_all.deb -# cd / -# zcat /full-path-to-work/work/data.tar.gz | tar xv -</screen></informalexample> - -</para> - </sect2> - - <sect2> - <title>Run <command>debootstrap</command></title> -<para> - -<command>debootstrap</command> can download the needed files directly -from the archive when you run it. You can substitute any &debian; -archive mirror for <userinput>&archive-mirror;/debian</userinput> in -the command example below, preferably a mirror close to you -network-wise. Mirrors are listed at -<ulink url="http://www.debian.org/mirror/list"></ulink>. - -</para><para> - -If you have a &releasename; &debian-gnu; CD mounted at -<filename>/cdrom</filename>, you could substitute a file URL instead -of the http URL: <userinput>file:/cdrom/debian/</userinput> - -</para><para> - -Substitute one of the following for <replaceable>ARCH</replaceable> -in the <command>debootstrap</command> command: - -<userinput>alpha</userinput>, -<userinput>amd64</userinput>, -<userinput>arm</userinput>, -<userinput>armel</userinput>, -<userinput>hppa</userinput>, -<userinput>i386</userinput>, -<userinput>ia64</userinput>, -<userinput>m68k</userinput>, -<userinput>mips</userinput>, -<userinput>mipsel</userinput>, -<userinput>powerpc</userinput>, -<userinput>s390</userinput>, or -<userinput>sparc</userinput>. - -<informalexample><screen> -# /usr/sbin/debootstrap --arch ARCH &releasename; \ - /mnt/debinst http://ftp.us.debian.org/debian -</screen></informalexample> - -</para> - </sect2> - - <sect2> - <title>Configure The Base System</title> -<para> - -Now you've got a real &debian; system, though rather lean, on disk. -<command>chroot</command> into it: - -<informalexample><screen> -# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash -</screen></informalexample> - -After chrooting you may need to set the terminal definition to be -compatible with the &debian; base system, for example: - -<informalexample><screen> -# export TERM=<replaceable>xterm-color</replaceable> -</screen></informalexample> - -</para> - - <sect3> - <title>Create device files</title> -<para> - -At this point <filename>/dev/</filename> only contains very basic device -files. For the next steps of the installation additional device files may -be needed. There are different ways to go about this and which method you -should use depends on the host system you are using for the installation, -on whether you intend to use a modular kernel or not, and on whether you -intend to use dynamic (e.g. using <classname>udev</classname>) or static -device files for the new system. - -</para><para> - -A few of the available options are: - -<itemizedlist> -<listitem><para> - -create a default set of static device files using -<informalexample><screen> -# cd /dev -# MAKEDEV generic -</screen></informalexample> - -</para></listitem> -<listitem><para> - -manually create only specific device files using <command>MAKEDEV</command> - -</para></listitem> -<listitem><para> - -bind mount /dev from your host system on top of /dev in the target system; -note that the postinst scripts of some packages may try to create device -files, so this option should only be used with care - -</para></listitem> -</itemizedlist> - -</para> - </sect3> - - <sect3> - <title>Mount Partitions</title> -<para> - -You need to create <filename>/etc/fstab</filename>. - -<informalexample><screen> -# editor /etc/fstab -</screen></informalexample> - -Here is a sample you can modify to suit: - -<informalexample><screen> -# /etc/fstab: static file system information. -# -# file system mount point type options dump pass -/dev/XXX / ext3 defaults 0 1 -/dev/XXX /boot ext3 ro,nosuid,nodev 0 2 - -/dev/XXX none swap sw 0 0 -proc /proc proc defaults 0 0 - -/dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0 -/dev/cdrom /media/cdrom iso9660 noauto,ro,user,exec 0 0 - -/dev/XXX /tmp ext3 rw,nosuid,nodev 0 2 -/dev/XXX /var ext3 rw,nosuid,nodev 0 2 -/dev/XXX /usr ext3 rw,nodev 0 2 -/dev/XXX /home ext3 rw,nosuid,nodev 0 2 -</screen></informalexample> - -Use <userinput>mount -a</userinput> to mount all the file systems you -have specified in your <filename>/etc/fstab</filename>, or, to mount -file systems individually, use: - -<informalexample><screen> -# mount /path # e.g.: mount /usr -</screen></informalexample> - -Current &debian; systems have mountpoints for removable media under -<filename>/media</filename>, but keep compatibility symlinks in -<filename>/</filename>. Create these as as needed, for example: - -<informalexample><screen> -# cd /media -# mkdir cdrom0 -# ln -s cdrom0 cdrom -# cd / -# ln -s media/cdrom -</screen></informalexample> - -You can mount the proc file system multiple times and to arbitrary -locations, though <filename>/proc</filename> is customary. If you didn't use -<userinput>mount -a</userinput>, be sure to mount proc before continuing: - -<informalexample><screen> -# mount -t proc proc /proc -</screen></informalexample> - -</para><para> - -The command <userinput>ls /proc</userinput> should now show a non-empty -directory. Should this fail, you may be able to mount proc from outside -the chroot: - -<informalexample><screen> -# mount -t proc proc /mnt/debinst/proc -</screen></informalexample> - -</para> - </sect3> - - <sect3> - <title>Setting Timezone</title> -<para> - -An option in the file <filename>/etc/default/rcS</filename> determines -whether the system will interpret the hardware clock as being set to UTC -or local time. The following command allows you to set that and choose -your timezone. - -<informalexample><screen> -# editor /etc/default/rcS -# dpkg-reconfigure tzdata -</screen></informalexample> - -</para> - </sect3> - - <sect3> - <title>Configure Networking</title> -<para> - -To configure networking, edit -<filename>/etc/network/interfaces</filename>, -<filename>/etc/resolv.conf</filename>, -<filename>/etc/hostname</filename> and -<filename>/etc/hosts</filename>. - -<informalexample><screen> -# editor /etc/network/interfaces -</screen></informalexample> - -Here are some simple examples from -<filename>/usr/share/doc/ifupdown/examples</filename>: - -<informalexample><screen> -###################################################################### -# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) -# See the interfaces(5) manpage for information on what options are -# available. -###################################################################### - -# We always want the loopback interface. -# -auto lo -iface lo inet loopback - -# To use dhcp: -# -# auto eth0 -# iface eth0 inet dhcp - -# An example static IP setup: (broadcast and gateway are optional) -# -# auto eth0 -# iface eth0 inet static -# address 192.168.0.42 -# network 192.168.0.0 -# netmask 255.255.255.0 -# broadcast 192.168.0.255 -# gateway 192.168.0.1 -</screen></informalexample> - -Enter your nameserver(s) and search directives in -<filename>/etc/resolv.conf</filename>: - -<informalexample><screen> -# editor /etc/resolv.conf -</screen></informalexample> - -A simple example <filename>/etc/resolv.conf</filename>: - -<informalexample><screen> -search hqdom.local -nameserver 10.1.1.36 -nameserver 192.168.9.100 -</screen></informalexample> - -Enter your system's host name (2 to 63 characters): - -<informalexample><screen> -# echo DebianHostName > /etc/hostname -</screen></informalexample> - -And a basic <filename>/etc/hosts</filename> with IPv6 support: - -<informalexample><screen> -127.0.0.1 localhost -127.0.1.1 DebianHostName - -# The following lines are desirable for IPv6 capable hosts -::1 ip6-localhost ip6-loopback -fe00::0 ip6-localnet -ff00::0 ip6-mcastprefix -ff02::1 ip6-allnodes -ff02::2 ip6-allrouters -ff02::3 ip6-allhosts -</screen></informalexample> - -If you have multiple network cards, you should arrange the names of -driver modules in the <filename>/etc/modules</filename> file into the -desired order. Then during boot, each card will be associated with the -interface name (eth0, eth1, etc.) that you expect. - -</para> - </sect3> - - <sect3> - <title>Configure Apt</title> -<para> - -Debootstrap will have created a very basic -<filename>/etc/apt/sources.list</filename> that will allow installing -additional packages. However, you may want to add some additional sources, -for example for source packages and security updates: - -<informalexample><screen> -deb-src http://ftp.us.debian.org/debian &releasename; main - -deb http://security.debian.org/ &releasename;/updates main -deb-src http://security.debian.org/ &releasename;/updates main -</screen></informalexample> - -Make sure to run <userinput>aptitude update</userinput> after you have -made changes to the sources list. - -</para> - </sect3> - - <sect3> - <title>Configure Locales and Keyboard</title> -<para> - -To configure your locale settings to use a language other than -English, install the <classname>locales</classname> support package -and configure it. Currently the use of UTF-8 locales is recommended. - -<informalexample><screen> -# aptitude install locales -# dpkg-reconfigure locales -</screen></informalexample> - -To configure your keyboard (if needed): - -<informalexample><screen> -# aptitude install console-setup -# dpkg-reconfigure keyboard-configuration -</screen></informalexample> - -</para><para> - -Note that the keyboard cannot be set while in the chroot, but will be -configured for the next reboot. - -</para> - </sect3> - </sect2> - - <sect2> - <title>Install a Kernel</title> -<para> - -If you intend to boot this system, you probably want a &arch-kernel; kernel -and a boot loader. Identify available pre-packaged kernels with: - -<informalexample><screen> -# apt-cache search &kernelpackage; -</screen></informalexample> - -</para><para> - -If you intend to use a pre-packaged kernel, you may want to create the -configuration file <filename>/etc/kernel-img.conf</filename> before you -do so. Here's an example file: - -<informalexample><screen> -# Kernel image management overrides -# See kernel-img.conf(5) for details -do_symlinks = yes -relative_links = yes -do_bootloader = yes -do_bootfloppy = no -do_initrd = yes -link_in_boot = no -</screen></informalexample> - -</para><para> - -For detailed information about this file and the various options, consult -its man page which will be available after installing the -<classname>kernel-package</classname> package. We recommend that you check -that the values are appropriate for your system. - -</para><para> - -Then install the kernel package of your choice using its package name. - -<informalexample><screen> -# aptitude install &kernelpackage;-<replaceable>&kernelversion;-arch-etc</replaceable> -</screen></informalexample> - -If you did not create a <filename>/etc/kernel-img.conf</filename> before -installing a pre-packaged kernel, you may be asked some questions during -its installation that refer to it. - -</para> - </sect2> - - <sect2> -<title>Set up the Boot Loader</title> -<para> - -To make your &debian-gnu; system bootable, set up your boot loader to load -the installed kernel with your new root partition. Note that -<command>debootstrap</command> does not install a boot loader, though you -can use <command>aptitude</command> inside your &debian; chroot to do so. - -</para><para arch="any-x86"> - -Check <userinput>info grub</userinput> or <userinput>man -lilo.conf</userinput> for instructions on setting up the -bootloader. If you are keeping the system you used to install &debian;, just -add an entry for the &debian; install to your existing grub -<filename>menu.lst</filename> or <filename>lilo.conf</filename>. For -<filename>lilo.conf</filename>, you could also copy it to the new system and -edit it there. After you are done editing, call <command>lilo</command> -(remember it will use -<filename>lilo.conf</filename> relative to the system you call it from). - -</para><para arch="any-x86"> - -Installing and setting up <classname>grub</classname> is as easy as: - -<informalexample><screen> -# aptitude install grub -# grub-install /dev/<replaceable>hda</replaceable> -# update-grub -</screen></informalexample> - -The second command will install <command>grub</command> (in this case in -the MBR of <literal>hda</literal>). The last command will create a sane -and working <filename>/boot/grub/menu.lst</filename>. - -</para><para> - -Note that this assumes that a <filename>/dev/hda</filename> device file has -been created. There are alternative methods to install <command>grub</command>, -but those are outside the scope of this appendix. - -</para><para arch="x86"> - -Here is a basic <filename>/etc/lilo.conf</filename> as an example: - -<informalexample><screen> -boot=/dev/<replaceable>hda6</replaceable> -root=/dev/<replaceable>hda6</replaceable> -install=menu -delay=20 -lba32 -image=/vmlinuz -initrd=/initrd.img -label=Debian -</screen></informalexample> - -</para><para arch="any-x86"> - -Depending on which bootloader you selected, you can now make some -additional changes in <filename>/etc/kernel-img.conf</filename>. - -</para><para arch="any-x86"> - -For the <classname>grub</classname> bootloader, you should -set the <literal>do_bootloader</literal> option to <quote>no</quote>. -And to automatically update your <filename>/boot/grub/menu.lst</filename> -on installation or removal of &debian; kernels, add the following lines: - -<informalexample><screen> -postinst_hook = update-grub -postrm_hook = update-grub -</screen></informalexample> - -For the <classname>lilo</classname> bootloader, the value of -<literal>do_bootloader</literal> needs to remain <quote>yes</quote>. - -</para><para arch="powerpc"> - -Check <userinput>man yaboot.conf</userinput> for instructions on -setting up the bootloader. If you are keeping the system you used to -install &debian;, just add an entry for the &debian; install to your -existing <filename>yaboot.conf</filename>. You could also copy it to -the new system and -edit it there. After you are done editing, call ybin (remember it will -use <filename>yaboot.conf</filename> relative to the system you call it from). - -</para><para arch="powerpc"> - -Here is a basic <filename>/etc/yaboot.conf</filename> as an example: - -<informalexample><screen> -boot=/dev/hda2 -device=hd: -partition=6 -root=/dev/hda6 -magicboot=/usr/lib/yaboot/ofboot -timeout=50 -image=/vmlinux -label=Debian -</screen></informalexample> - -On some machines, you may need to use <userinput>ide0:</userinput> -instead of <userinput>hd:</userinput>. - -</para> - </sect2> - - <sect2> -<title>Finishing touches</title> -<para> - -As mentioned earlier, the installed system will be very basic. If you -would like to make the system a bit more mature, there is an easy method -to install all packages with <quote>standard</quote> priority: - -<informalexample><screen> -# tasksel install standard -</screen></informalexample> - -Of course, you can also just use <command>aptitude</command> to install -packages individually. - -</para><para> - -After the installation there will be a lot of downloaded packages in -<filename>/var/cache/apt/archives/</filename>. You can free up some -diskspace by running: - -<informalexample><screen> -# aptitude clean -</screen></informalexample> - -</para> - </sect2> - </sect1> diff --git a/nl/appendix/files.xml b/nl/appendix/files.xml deleted file mode 100644 index 9de7f07d9..000000000 --- a/nl/appendix/files.xml +++ /dev/null @@ -1,354 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 58142 untranslated --> - - - <sect1 arch="linux-any" id="linuxdevices"><title>Linux Devices</title> -<para> - -In Linux various special files can be found under the directory -<filename>/dev</filename>. These files are called device files and -behave unlike ordinary files. The most common types of device files -are for block devices and character devices. These files are an -interface to the actual driver (part of the Linux kernel) which in -turn accesses the hardware. Another, less common, type of device file -is the named <firstterm>pipe</firstterm>. -The most important device files are listed in the tables below. - -</para><para> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>fd0</filename></entry> - <entry>First Floppy Drive</entry> -</row><row> - <entry><filename>fd1</filename></entry> - <entry>Second Floppy Drive</entry> -</row> -</tbody></tgroup></informaltable> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>hda</filename></entry> - <entry>IDE Hard disk / CD-ROM on the first IDE port (Master)</entry> -</row><row> - <entry><filename>hdb</filename></entry> - <entry>IDE Hard disk / CD-ROM on the first IDE port (Slave)</entry> -</row><row> - <entry><filename>hdc</filename></entry> - <entry>IDE Hard disk / CD-ROM on the second IDE port (Master)</entry> -</row><row> - <entry><filename>hdd</filename></entry> - <entry>IDE Hard disk / CD-ROM on the second IDE port (Slave)</entry> -</row><row> - <entry><filename>hda1</filename></entry> - <entry>First partition of the first IDE hard disk</entry> -</row><row> - <entry><filename>hdd15</filename></entry> - <entry>Fifteenth partition of the fourth IDE hard disk</entry> -</row> -</tbody></tgroup></informaltable> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>sda</filename></entry> - <entry>SCSI Hard disk with lowest SCSI ID (e.g. 0)</entry> -</row><row> - <entry><filename>sdb</filename></entry> - <entry>SCSI Hard disk with next higher SCSI ID (e.g. 1)</entry> -</row><row> - <entry><filename>sdc</filename></entry> - <entry>SCSI Hard disk with next higher SCSI ID (e.g. 2)</entry> -</row><row> - <entry><filename>sda1</filename></entry> - <entry>First partition of the first SCSI hard disk</entry> -</row><row> - <entry><filename>sdd10</filename></entry> - <entry>Tenth partition of the fourth SCSI hard disk</entry> -</row> -</tbody></tgroup></informaltable> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>sr0</filename></entry> - <entry>SCSI CD-ROM with the lowest SCSI ID</entry> -</row><row> - <entry><filename>sr1</filename></entry> - <entry>SCSI CD-ROM with the next higher SCSI ID</entry> -</row> -</tbody></tgroup></informaltable> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>ttyS0</filename></entry> - <entry>Serial port 0, COM1 under MS-DOS</entry> -</row><row> - <entry><filename>ttyS1</filename></entry> - <entry>Serial port 1, COM2 under MS-DOS</entry> -</row><row> - <entry><filename>psaux</filename></entry> - <entry>PS/2 mouse device</entry> -</row><row> - <entry><filename>gpmdata</filename></entry> - <entry>Pseudo device, repeater data from GPM (mouse) daemon</entry> -</row> -</tbody></tgroup></informaltable> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>cdrom</filename></entry> - <entry>Symbolic link to the CD-ROM drive</entry> -</row><row> - <entry><filename>mouse</filename></entry> - <entry>Symbolic link to the mouse device file</entry> -</row> -</tbody></tgroup></informaltable> - -<informaltable><tgroup cols="2"><tbody> -<row> - <entry><filename>null</filename></entry> - <entry>Anything written to this device will disappear</entry> -</row><row> - <entry><filename>zero</filename></entry> - <entry>One can endlessly read zeros out of this device</entry> -</row> -</tbody></tgroup></informaltable> - -</para> - - <sect2 arch="not-s390" id="device-mouse"> - <title>Setting Up Your Mouse</title> -<para> - -The mouse can be used in both the Linux console (with gpm) and the X -window environment. Normally, this is a simple matter of installing -<filename>gpm</filename> and the X server itself. Both should be -configured to use <filename>/dev/input/mice</filename> as the mouse -device. The correct mouse protocol is named <userinput>exps2</userinput> -in gpm, and <userinput>ExplorerPS/2</userinput> in X. The respective -configuration files are <filename>/etc/gpm.conf</filename> and -<filename>/etc/X11/xorg.conf</filename>. - -</para><para> - -Certain kernel modules must be loaded in order for your mouse to work. -In most cases the correct modules are autodetected, but not always for -old-style serial and bus mice<footnote> - -<para> -Serial mice usually have a 9-hole D-shaped connector; bus mice have an -8-pin round connector, not to be confused with the 6-pin round connector -of a PS/2 mouse or the 4-pin round connector of an ADB mouse. -</para> - -</footnote>, which are quite rare except on very old computers. Summary -of Linux kernel modules needed for different mouse types: - -<informaltable><tgroup cols="2"><thead> -<row> - <entry>Module</entry> - <entry>Description</entry> -</row> -</thead><tbody> -<row> - <entry>psmouse</entry> - <entry>PS/2 mice (should be autodetected)</entry> -</row> -<row> - <entry>usbhid</entry> - <entry>USB mice (should be autodetected)</entry> -</row> -<row> - <entry>sermouse</entry> - <entry>Most serial mice</entry> -</row> -<row> - <entry>logibm</entry> - <entry>Bus mouse connected to Logitech adapter card</entry> -</row> -<row> - <entry>inport</entry> - <entry>Bus mouse connected to ATI or Microsoft InPort card</entry> -</row> -</tbody></tgroup></informaltable> - -To load a mouse driver module, you can use the <command>modconf</command> -command (from the package with the same name) and look in the category -<userinput>kernel/drivers/input/mouse</userinput>. - -</para><para arch="powerpc"> -<!-- FJP 20070122: Unsure if this is still valid --> - -Modern kernels give you the capability to emulate a three-button mouse -when your mouse only has one button. Just add the following lines to -<filename>/etc/sysctl.conf</filename> file. - -<informalexample><screen> -# 3-button mouse emulation -# turn on emulation -/dev/mac_hid/mouse_button_emulation = 1 -# Send middle mouse button signal with the F11 key -/dev/mac_hid/mouse_button2_keycode = 87 -# Send right mouse button signal with the F12 key -/dev/mac_hid/mouse_button3_keycode = 88 -# For different keys, use showkey to tell you what the code is. -</screen></informalexample> - -</para> - </sect2> - </sect1> - - <sect1 id="tasksel-size-list"> - <title>Disk Space Needed for Tasks</title> -<para> - -A standard installation for the amd64 architecture, including all standard -packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. -A minimal base installation, without the <quote>Standard system</quote> -task selected, will take &base-system-size;MB. - -</para> -<important><para> - -In both cases this is the actual disk space used <emphasis>after</emphasis> -the installation is finished and any temporary files deleted. It also does -not take into account overhead used by the file system, for example for -journal files. This means that significantly more disk space is needed both -<emphasis>during</emphasis> the installation and for normal system use. - -</para></important> -<para> - -The following table lists sizes reported by aptitude for the tasks listed -in tasksel. Note that some tasks have overlapping constituents, so the -total installed size for two tasks together may be less than the total -obtained by adding up the numbers. - -</para><para> - -By default the installer will install the GNOME desktop environment, but -alternative desktop environments can be selected either by using one -of the special CD images, or by specifying the desired desktop environment -when the installer is booted (see <xref linkend="pkgsel"/>). - -</para><para> - -Note that you will need to add the sizes listed in the table to the size -of the standard installation when determining the size of partitions. -Most of the size listed as <quote>Installed size</quote> will end up in -<filename>/usr</filename> and in <filename>/lib</filename>; -the size listed as <quote>Download size</quote> -is (temporarily) required in <filename>/var</filename>. - -</para><para> - -<informaltable><tgroup cols="4"> -<thead> -<row> - <entry>Task</entry> - <entry>Installed size (MB)</entry> - <entry>Download size (MB)</entry> - <entry>Space needed to install (MB)</entry> -</row> -</thead> - -<tbody> -<row> - <entry>Desktop environment</entry> - <entry> </entry> - <entry> </entry> - <entry> </entry> -</row> -<row> - <entry> • GNOME (default)</entry> - <entry>&task-desktop-gnome-inst;</entry> - <entry>&task-desktop-gnome-dl;</entry> - <entry>&task-desktop-gnome-tot;</entry> -</row> -<row> - <entry> • KDE</entry> - <entry>&task-desktop-kde-inst;</entry> - <entry>&task-desktop-kde-dl;</entry> - <entry>&task-desktop-kde-tot;</entry> -</row> -<row> - <entry> • Xfce</entry> - <entry>&task-desktop-xfce-inst;</entry> - <entry>&task-desktop-xfce-dl;</entry> - <entry>&task-desktop-xfce-tot;</entry> -</row> -<row> - <entry> • LXDE</entry> - <entry>&task-desktop-lxde-inst;</entry> - <entry>&task-desktop-lxde-dl;</entry> - <entry>&task-desktop-lxde-tot;</entry> -</row> - -<row> - <entry>Laptop<footnote> - - <para> - There is some overlap of the Laptop task with the Desktop environment task. - If you install both, the Laptop task will only require a few MB additional - disk space. - </para> - - </footnote></entry> - <entry>&task-laptop-inst;</entry> - <entry>&task-laptop-dl;</entry> - <entry>&task-laptop-tot;</entry> -</row> - -<row> - <entry>Web server</entry> - <entry>&task-web-inst;</entry> - <entry>&task-web-dl;</entry> - <entry>&task-web-tot;</entry> -</row> - -<row> - <entry>Print server</entry> - <entry>&task-print-inst;</entry> - <entry>&task-print-dl;</entry> - <entry>&task-print-tot;</entry> -</row> - -<row> - <entry>DNS server</entry> - <entry>&task-dns-inst;</entry> - <entry>&task-dns-dl;</entry> - <entry>&task-dns-tot;</entry> -</row> - -<row> - <entry>File server</entry> - <entry>&task-file-inst;</entry> - <entry>&task-file-dl;</entry> - <entry>&task-file-tot;</entry> -</row> - -<row> - <entry>Mail server</entry> - <entry>&task-mail-inst;</entry> - <entry>&task-mail-dl;</entry> - <entry>&task-mail-tot;</entry> -</row> - -<row> - <entry>SQL database</entry> - <entry>&task-sql-inst;</entry> - <entry>&task-sql-dl;</entry> - <entry>&task-sql-tot;</entry> -</row> - -</tbody> -</tgroup></informaltable> - -</para><para> - -If you install in a language other than English, <command>tasksel</command> -may automatically install a <firstterm>localization task</firstterm>, if one -is available for your language. Space requirements differ per language; -you should allow up to 350MB in total for download and installation. - -</para> - </sect1> diff --git a/nl/appendix/gpl.xml b/nl/appendix/gpl.xml deleted file mode 100644 index e93459139..000000000 --- a/nl/appendix/gpl.xml +++ /dev/null @@ -1,525 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 38979 untranslated --> - -<appendix id="appendix-gpl"><title>GNU General Public License</title> - -<note condition="gpl-unofficial"><para> - -[[This note, consisting of two paragraphs, should only be included in your -translation if you translate the GPL in this appendix. -See build/lang-options/README on how to enable this paragraph and for -additional information. Its condition is "gpl-unofficial".]] -[[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English -name of your language. Do not change the link to the GPL!]] - -This is an unofficial translation of the GNU General Public License into -{language}. It was not published by the Free Software Foundation, and does -not legally state the distribution terms for software that uses the GNU -GPL — only the original <ulink url="&url-gnu-copyleft;">English -text</ulink> of the GNU GPL does that. However, we hope that this translation -will help {language} speakers to better understand the GNU GPL. - -</para><para> - -[[See build/lang-options/README on how to enable this paragraph and for -additional information. Its condition is "gpl-unofficial".]] -[[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English -name of your language before translating. Do not change the link to the GPL!]] - -This is an unofficial translation of the GNU General Public License into -{language}. It was not published by the Free Software Foundation, and does -not legally state the distribution terms for software that uses the GNU -GPL — only the original <ulink url="&url-gnu-copyleft;">English -text</ulink> of the GNU GPL does that. However, we hope that this translation -will help {language} speakers to better understand the GNU GPL. - -</para></note> -<para> - -Version 2, June 1991 - -<informalexample><screen> -Copyright (C) 1989, 1991 Free Software Foundation, Inc. -51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. - -Everyone is permitted to copy and distribute verbatim copies -of this license document, but changing it is not allowed. -</screen></informalexample> - -</para> - - <simplesect><title>Preamble</title> -<para> - -The licenses for most software are designed to take away your freedom -to share and change it. By contrast, the gnu General Public License -is intended to guarantee your freedom to share and change free -software — to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit -to using it. (Some other Free Software Foundation software is covered -by the gnu Library General Public License instead.) You can apply it -to your programs, too. - -</para><para> - -When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge -for this service if you wish), that you receive source code or can -get it if you want it, that you can change the software or use pieces -of it in new free programs; and that you know you can do these -things. - -</para><para> - -To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the -rights. These restrictions translate to certain responsibilities for -you if you distribute copies of the software, or if you modify it. - -</para><para> - -For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - -</para><para> - -We protect your rights with two steps: (1) copyright the software, -and (2) offer you this license which gives you legal permission to -copy, distribute and/or modify the software. - -</para><para> - -Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, -we want its recipients to know that what they have is not the -original, so that any problems introduced by others will not reflect -on the original authors' reputations. - -</para><para> - -Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making -the program proprietary. To prevent this, we have made it clear that -any patent must be licensed for everyone's free use or not licensed -at all. - -</para><para> - -The precise terms and conditions for copying, distribution and -modification follow. - -</para> - </simplesect> - - <simplesect><title>GNU GENERAL PUBLIC LICENSE</title> -<para> - -<emphasis role="bold">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION -AND MODIFICATION</emphasis> - -</para><para> - -<emphasis role="bold">0.</emphasis> -This License applies to any program or other work which contains a -notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -</para><para> - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the -Program is covered only if its contents constitute a work based on -the Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - -</para><para> - -<emphasis role="bold">1.</emphasis> -You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any -warranty; and give any other recipients of the Program a copy of this -License along with the Program. - -</para><para> - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a -fee. - -</para><para> - -<emphasis role="bold">2.</emphasis> -You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - -</para> -<orderedlist numeration='loweralpha'><listitem><para> - -You must cause the modified files to carry prominent notices -stating that you changed the files and the date of any change. - -</para></listitem> -<listitem><para> - -You must cause any work that you distribute or publish, that in -whole or in part contains or is derived from the Program or any part -thereof, to be licensed as a whole at no charge to all third parties -under the terms of this License. - -</para></listitem> -<listitem><para> - -If the modified program normally reads commands interactively when -run, you must cause it, when started running for such interactive use -in the most ordinary way, to print or display an announcement -including an appropriate copyright notice and a notice that there is -no warranty (or else, saying that you provide a warranty) and that -users may redistribute the program under these conditions, and -telling the user how to view a copy of this License. (Exception: if -the Program itself is interactive but does not normally print such an -announcement, your work based on the Program is not required to print -an announcement.) - -</para></listitem></orderedlist> -<para> - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote -it. - -</para><para> - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -</para><para> - -In addition, mere aggregation of another work not based on the -Program with the Program (or with a work based on the Program) on a -volume of a storage or distribution medium does not bring the other -work under the scope of this License. - -</para><para> - -<emphasis role="bold">3.</emphasis> -You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the -following: - -</para> -<orderedlist numeration='loweralpha'><listitem><para> - -Accompany it with the complete corresponding machine-readable -source code, which must be distributed under the terms of Sections 1 -and 2 above on a medium customarily used for software interchange; -or, - -</para></listitem> -<listitem><para> - -Accompany it with a written offer, valid for at least three years, -to give any third party, for a charge no more than your cost of -physically performing source distribution, a complete -machine-readable copy of the corresponding source code, to be -distributed under the terms of Sections 1 and 2 above on a medium -customarily used for software interchange; or, - -</para></listitem> -<listitem><para> - -Accompany it with the information you received as to the offer to -distribute corresponding source code. (This alternative is allowed -only for noncommercial distribution and only if you received the -program in object code or executable form with such an offer, in -accord with Subsection b above.) - -</para></listitem></orderedlist> -<para> - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -</para><para> - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - -</para><para> - -<emphasis role="bold">4.</emphasis> -You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this -License. However, parties who have received copies, or rights, from -you under this License will not have their licenses terminated so -long as such parties remain in full compliance. - -</para><para> - -<emphasis role="bold">5.</emphasis> -You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - -</para><para> - -<emphasis role="bold">6.</emphasis> -Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject -to these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted -herein. You are not responsible for enforcing compliance by third -parties to this License. - -</para><para> - -<emphasis role="bold">7.</emphasis> -If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do -not excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under -this License and any other pertinent obligations, then as a -consequence you may not distribute the Program at all. For example, -if a patent license would not permit royalty-free redistribution of -the Program by all those who receive copies directly or indirectly -through you, then the only way you could satisfy both it and this -License would be to refrain entirely from distribution of the -Program. - -</para><para> - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended -to apply and the section as a whole is intended to apply in other -circumstances. - -</para><para> - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is -willing to distribute software through any other system and a -licensee cannot impose that choice. - -</para><para> - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - -</para><para> - -<emphasis role="bold">8.</emphasis> -If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - -</para><para> - -<emphasis role="bold">9.</emphasis> -The Free Software Foundation may publish revised and/or new -versions of the General Public License from time to time. Such new -versions will be similar in spirit to the present version, but may -differ in detail to address new problems or concerns. Each version is -given a distinguishing version number. If the Program specifies a -version number of this License which applies to it and "any later -version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number -of this License, you may choose any version ever published by the -Free Software Foundation. - -</para><para> - -<emphasis role="bold">10.</emphasis> -If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the -author to ask for permission. For software which is copyrighted by -the Free Software Foundation, write to the Free Software Foundation; -we sometimes make exceptions for this. Our decision will be guided by -the two goals of preserving the free status of all derivatives of our -free software and of promoting the sharing and reuse of software -generally. - -</para><para> - -<emphasis role="bold">NO WARRANTY</emphasis> - -</para><para> - -<emphasis role="bold">11.</emphasis> -BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO -WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. -EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR -OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY -KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE -PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME -THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - -</para><para> - -<emphasis role="bold">12.</emphasis> -IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN -WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY -AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU -FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR -CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE -PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING -RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A -FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF -SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - -</para><para> - -<emphasis role="bold">END OF TERMS AND CONDITIONS</emphasis> - -</para> - </simplesect> - - <simplesect><title>How to Apply These Terms to Your New Programs</title> -<para> - -If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make -it free software which everyone can redistribute and change under -these terms. - -</para><para> - -To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - -<informalexample><screen> -<replaceable>one line to give the program's name and a brief idea of what it does.</replaceable> -Copyright (C) <replaceable>year name of author</replaceable> - -This program is free software; you can redistribute it and/or -modify it under the terms of the GNU General Public License -as published by the Free Software Foundation; either version 2 -of the License, or (at your option) any later version. - -This program is distributed in the hope that it will be useful, -but WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the -GNU General Public License for more details. - -You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software -Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. -</screen></informalexample> - -</para><para> - -Also add information on how to contact you by electronic and paper -mail. - -</para><para> - -If the program is interactive, make it output a short notice like -this when it starts in an interactive mode: - -<informalexample><screen> -Gnomovision version 69, Copyright (C) <replaceable>year name of author</replaceable> -Gnomovision comes with absolutely no warranty; for details -type `show w'. This is free software, and you are welcome -to redistribute it under certain conditions; type `show c' -for details. -</screen></informalexample> - -</para><para> - -The hypothetical commands `show w' and `show c' should show the -appropriate parts of the General Public License. Of course, the -commands you use may be called something other than `show w' and -`show c'; they could even be mouse-clicks or menu items — whatever -suits your program. - -</para><para> - -You should also get your employer (if you work as a programmer) or -your school, if any, to sign a "copyright disclaimer" for the -program, if necessary. Here is a sample; alter the names: - -<informalexample><screen> -Yoyodyne, Inc., hereby disclaims all copyright interest in the -program `Gnomovision' (which makes passes at compilers) written -by James Hacker. - -<replaceable>signature of Ty Coon</replaceable>, 1 April 1989 -Ty Coon, President of Vice -</screen></informalexample> - -</para><para> - -This General Public License does not permit incorporating your -program into proprietary programs. If your program is a subroutine -library, you may consider it more useful to permit linking -proprietary applications with the library. If this is what you want -to do, use the GNU Lesser General Public License instead of this -License. - -</para> - </simplesect> -</appendix> diff --git a/nl/appendix/graphical.xml b/nl/appendix/graphical.xml deleted file mode 100644 index 1b875377e..000000000 --- a/nl/appendix/graphical.xml +++ /dev/null @@ -1,148 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61189 untranslated --> - - <sect1 condition="gtk" id="graphical"> - <title>The Graphical Installer</title> -<para> - -The graphical version of the installer is only available for a limited -number of architectures, including &arch-title;. The functionality of -the graphical installer is essentially the same as that of the regular -installer as it basically uses the same programs, but with a different -frontend. - -</para><para> - -Although the functionality is identical, the graphical installer still has -a few significant advantages. The main advantage is that it supports more -languages, namely those that use a character set that cannot be displayed -with the regular <quote>newt</quote> frontend. It also has a few usability -advantages such as the option to use a mouse, and in some cases several -questions can be displayed on a single screen. - -</para><para arch="any-x86"> - -The graphical installer is available with all CD images and with the -hd-media installation method. To boot the graphical installer simply select -the relevant option from the boot menu. Expert and rescue mode for the -graphical installer can be selected from the <quote>Advanced options</quote> -menu. The previously used boot methods <userinput>installgui</userinput>, -<userinput>expertgui</userinput> and <userinput>rescuegui</userinput> can -still be used from the boot prompt which is shown after selecting the -<quote>Help</quote> option in the boot menu. - -</para><para arch="any-x86"> - -There is also a graphical installer image that can be netbooted. And there -is a special <quote>mini</quote> ISO image<footnote id="gtk-miniiso"> - -<para> -The mini ISO image can be downloaded from a &debian; mirror as described -in <xref linkend="downloading-files"/>. -Look for <filename>netboot/gtk/mini.iso</filename>. -</para> - -</footnote>, which is mainly useful for testing. - -</para><para arch="powerpc"> - -For &arch-title;, currently only an experimental <quote>mini</quote> ISO -image is available<footnote id="gtk-miniiso"> - -<para> -The mini ISO image can be downloaded from a &debian; mirror as described -in <xref linkend="downloading-files"/>. -Look for <filename>netboot/gtk/mini.iso</filename>. -</para> - -</footnote>. It should work on almost all PowerPC systems that have -an ATI graphical card, but is unlikely to work on other systems. - -</para><para> - -Just as with the regular installer it is possible to add boot parameters -when starting the graphical installer. One of those parameters allows to -configure the mouse for left-handed use. Others allow to select the mouse -device (e.g. for a serial mouse) and the mouse protocol. See -<xref linkend="boot-parms"/> for valid parameters<phrase arch="x86"> and -<xref linkend="boot-screen"/> for information on how to pass them</phrase>. - -</para> -<note><para> - -The graphical installer requires significantly more memory to run than -the regular installer: &minimum-memory-gtk;. If insufficient memory is -available, it will automatically fall back to the regular -<quote>newt</quote> frontend. - -</para><para> - -If the amount of memory in your system is below &minimum-memory;, -the graphical installer may fail to boot at all while booting the -regular installer would still work. Using the regular installer is -recommended for systems with little available memory. - -</para></note> - - <sect2 id="gtk-using"> - <title>Using the graphical installer</title> -<para> - -As already mentioned, the graphical installer basically works the same as -the regular installer and thus the rest of this manual can be used to guide -you through the installation process. - -</para><para> - -If you prefer using the keyboard over the mouse, there are two things you -need to know. To expand a collapsed list (used for example for the selection -of countries within continents), you can use the <keycap>+</keycap> and -<keycap>-</keycap> keys. For questions where more than one item can be -selected (e.g. task selection), you first need to tab to the -&BTN-CONT; button after making your selections; hitting -enter will toggle a selection, not activate &BTN-CONT;. - -</para><para> - -If a dialog offers additional help information, a <guibutton>Help</guibutton> -button will be displayed. The help information can be accessed either by -activating the button or by pressing the <keycap>F1</keycap> key. - -</para><para> - -To switch to another console, you will also need to use the -<keycap>Ctrl</keycap> key, just as with the X Window System. For example, -to switch to VT2 (the first debug shell) you would use: <keycombo> -<keycap>Ctrl</keycap> <keycap>Left Alt</keycap> <keycap>F2</keycap> -</keycombo>. The graphical installer itself runs on VT5, so you can use -<keycombo> <keycap>Left Alt</keycap> <keycap>F5</keycap> </keycombo> -to switch back. - -</para> - </sect2> - - <sect2 id="gtk-issues"> - <title>Known issues</title> -<para> - -The graphical frontend to the installer is relatively new and because of -that there are some known issues. We continue to work on resolving these. - -</para> - -<itemizedlist> -<listitem><para> - -Information on some screens is not yet nicely formatted into columns as it -should be. - -</para></listitem> -<listitem><para> - -Support for touchpads is not yet optimal. - -</para></listitem> -</itemizedlist> - - </sect2> - </sect1> diff --git a/nl/appendix/plip.xml b/nl/appendix/plip.xml deleted file mode 100644 index 830d75232..000000000 --- a/nl/appendix/plip.xml +++ /dev/null @@ -1,187 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39644 untranslated --> - - <sect1 id="plip" arch="x86"> - <title>Installing &debian-gnu; over Parallel Line IP (PLIP)</title> - -<para> - -This section explains how to install &debian-gnu; on a computer without an -Ethernet card, but with just a remote gateway computer attached via -a Null-Modem cable (also called Null-Printer cable). The gateway -computer should be connected to a network that has a &debian; mirror -on it (e.g. to the Internet). - -</para><para> - -In the example in this appendix we will set up a PLIP connection using -a gateway connected to the Internet over a dial-up connection (ppp0). -We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP -interfaces on the target system and the source system respectively -(these addresses should be unused within your network address space). - -</para><para> - -The PLIP connection set up during the installation will also be available -after the reboot into the installed system (see <xref linkend="boot-new"/>). - -</para><para> - -Before you start, you will need to check the BIOS configuration (IO base -address and IRQ) for the parallel ports of both the source and target -systems. The most common values are <literal>io=0x378</literal>, -<literal>irq=7</literal>. - -</para> - - <sect2> - <title>Requirements</title> - -<itemizedlist> -<listitem><para> - -A target computer, called <emphasis>target</emphasis>, where &debian; will be -installed. - -</para></listitem> -<listitem><para> - -System installation media; see <xref linkend="installation-media"/>. - -</para></listitem> -<listitem><para> - -Another computer connected to the Internet, called <emphasis>source</emphasis>, -that will function as the gateway. - -</para></listitem> -<listitem><para> - -A DB-25 Null-Modem cable. See the -<ulink url="&url-plip-install-howto;">PLIP-Install-HOWTO</ulink> for more -information on this cable and instructions how to make your own. - -</para></listitem> -</itemizedlist> - - </sect2> - - <sect2> - <title>Setting up source</title> -<para> - -The following shell script is a simple example of how to configure the -source computer as a gateway to the Internet using ppp0. - -<informalexample><screen> -#!/bin/sh - -# We remove running modules from kernel to avoid conflicts and to -# reconfigure them manually. -modprobe -r lp parport_pc -modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</replaceable> -modprobe plip - -# Configure the plip interface (plip0 for me, see dmesg | grep plip) -ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint <replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up - -# Configure gateway -modprobe iptable_nat -iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j MASQUERADE -echo 1 > /proc/sys/net/ipv4/ip_forward -</screen></informalexample> - -</para> - </sect2> - - <sect2> - <title>Installing target</title> -<para> - -Boot the installation media. The installation needs to be run in -expert mode; enter <userinput>expert</userinput> at the boot prompt. -If you need to set parameters for kernel modules, you also need to -do this at the boot prompt. For example, to boot the installer and -set values for the <quote>io</quote> and <quote>irq</quote> options -for the parport_pc module, enter the following at the boot prompt: - -<informalexample><screen> -expert parport_pc.io=<replaceable>0x378</replaceable> parport_pc.irq=<replaceable>7</replaceable> -</screen></informalexample> - -Below are the answers that should be given during various stages of -the installation. - -</para> - -<orderedlist> -<listitem><para> - -<guimenuitem>Load installer components from CD</guimenuitem> - -</para><para> - -Select the <userinput>plip-modules</userinput> option from the list; this -will make the PLIP drivers available to the installation system. - -</para></listitem> -<listitem><para> - -<guimenuitem>Detect network hardware</guimenuitem> - -</para> - - <itemizedlist> - <listitem><para> - -If target <emphasis>does</emphasis> have a network card, a list of driver -modules for detected cards will be shown. If you want to force &d-i; to -use plip instead, you have to deselect all listed driver modules. -Obviously, if target doesn't have a network card, the installer will not -show this list. - - </para></listitem> - <listitem><para> - -Because no network card was detected/selected earlier, the installer will -ask you to select a network driver module from a list. -Select the <userinput>plip</userinput> module. - - </para></listitem> - </itemizedlist> - -</listitem> -<listitem><para> - -<guimenuitem>Configure the network</guimenuitem> - - <itemizedlist> - <listitem><para> - -Auto-configure network with DHCP: No - - </para></listitem> - <listitem><para> - -IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput> - - </para></listitem> - <listitem><para> - -Point-to-point address: -<userinput><replaceable>192.168.0.2</replaceable></userinput> - - </para></listitem> - <listitem><para> - -Name server addresses: you can enter the same addresses used on -source (see <filename>/etc/resolv.conf</filename>) - - </para></listitem> - </itemizedlist> - -</para></listitem> -</orderedlist> - - </sect2> - </sect1> diff --git a/nl/appendix/pppoe.xml b/nl/appendix/pppoe.xml deleted file mode 100644 index a48f2f976..000000000 --- a/nl/appendix/pppoe.xml +++ /dev/null @@ -1,109 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 57313 untranslated --> - - <sect1 id="pppoe" arch="not-s390"> - <title>Installing &debian-gnu; using PPP over Ethernet (PPPoE)</title> - -<para> - -In some countries PPP over Ethernet (PPPoE) is a common protocol for -broadband (ADSL or cable) connections to an Internet Service Provider. -Setting up a network connection using PPPoE is not supported by default -in the installer, but can be made to work very simply. This section -explains how. - -</para><para> - -The PPPoE connection set up during the installation will also be available -after the reboot into the installed system (see <xref linkend="boot-new"/>). - -</para><para> - -To have the option of setting up and using PPPoE during the installation, -you will need to install using one of the CD-ROM/DVD images that are -available. It is not supported for other installation methods (e.g. -netboot<phrase condition="supports-floppy-boot"> or floppy</phrase>). - -</para><para> - -Installing over PPPoE is mostly the same as any other installation. The -following steps explain the differences. - -</para> - -<itemizedlist> -<listitem><para> - -Boot the installer with the boot parameter -<userinput>modules=ppp-udeb</userinput><footnote arch="x86"> - -<para> -See <xref linkend="boot-screen"/> for information on -how to add a boot parameter. -</para> - -</footnote>. -This will ensure the component responsible for the setup of PPPoE -(<classname>ppp-udeb</classname>) will be loaded and run automatically. - -</para></listitem> -<listitem><para> - -Follow the regular initial steps of the installation (language, -country and keyboard selection; the loading of additional installer -components<footnote> - -<para> - -The <classname>ppp-udeb</classname> component is loaded as one of -the additional components in this step. If you want to install at -medium or low priority (expert mode), you can also manually select -the <classname>ppp-udeb</classname> instead of entering the -<quote>modules</quote> parameter at the boot prompt. - -</para> - -</footnote>). - -</para></listitem> -<listitem><para> - -The next step is the detection of network hardware, in order to identify -any Ethernet cards present in the system. - -</para></listitem> -<listitem><para> - -After this the actual setup of PPPoE is started. The installer will probe -all the detected Ethernet interfaces in an attempt to find a PPPoE -concentrator (a type of server which handles PPPoE connections). - -</para><para> - -It is possible that the concentrator will not to be found at the first -attempt. This can happen occasionally on slow or loaded networks or with -faulty servers. In most cases a second attempt to detect the concentrator -will be successful; to retry, select <guimenuitem>Configure and start a -PPPoE connection</guimenuitem> from the main menu of the installer. - -</para></listitem> -<listitem><para> - -After a concentrator is found, the user will be prompted to type the login -information (the PPPoE username and password). - -</para></listitem> -<listitem><para> - -At this point the installer will use the provided information to establish -the PPPoE connection. If the correct information was provided, the PPPoE -connection should be configured and the installer should be able to use it -to connect to the Internet and retrieve packages over it (if needed). If -the login information is not correct or some error appears, the installer -will stop, but the configuration can be attempted again by selecting the -menu entry <guimenuitem>Configure and start a PPPoE connection</guimenuitem>. - -</para></listitem> -</itemizedlist> - - </sect1> diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml deleted file mode 100644 index 90ce8a4f6..000000000 --- a/nl/appendix/preseed.xml +++ /dev/null @@ -1,1624 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62798 untranslated --> - -<!-- -Be careful with the format of this file as it is parsed to generate -the example preconfiguration file. -In that file all text between <informalexample> tags that have the -attribute 'role="example"' set is included, except if a 'condition' -attribute is in force that does not match the specified release or if an -'arch' attribute is in force that does not match the specified architecture. - -Currently only a single variant of the example file is generated (for i386). ---> - -<appendix id="appendix-preseed"> -<title>Automating the installation using preseeding</title> - -<para> - -This appendix explains how to preseed answers to questions in &d-i; to -automate your installation. - -</para><para> - -The configuration fragments used in this appendix are also available as an -example preconfiguration file from &urlset-example-preseed;. - -</para> - - <sect1 id="preseed-intro"> - <title>Introduction</title> -<para> - -Preseeding provides a way to set answers to questions asked during the -installation process, without having to manually enter the answers while -the installation is running. This makes it possible to fully automate most -types of installation and even offers some features not available during -normal installations. - -</para><para> - -Preseeding is not required. If you use an empty preseed file, the installer -will behave just the same way as in a normal manual installation. Each -question you preseed will (if you got it right!) modify the installation in -some way from that baseline. - -</para> - - <sect2 id="preseed-methods"> - <title>Preseeding methods</title> -<para> - -There are three methods that can be used for preseeding: -<firstterm>initrd</firstterm>, <firstterm>file</firstterm> and -<firstterm>network</firstterm>. Initrd preseeding will work with any -installation method and supports preseeding of more things, but it requires -the most preparation. File and network preseeding each can be used with -different installation methods. - -</para><para> - -The following table shows which preseeding methods can be used with which -installation methods. - -<informaltable> -<tgroup cols="4"> -<thead> -<row> - <entry>Installation method</entry><entry>initrd</entry> - <entry>file</entry><entry>network</entry> -</row> -</thead> - -<tbody> -<row> - <entry>CD/DVD</entry> - <entry>yes</entry> - <entry>yes</entry> - <entry>yes<footnote id='apx-ps-net'> - - <para> - but only if you have network access, and set <literal>preseed/url</literal> - appropriately - </para> - - </footnote></entry> -</row><row> - <entry>netboot</entry> - <entry>yes</entry> - <entry>no</entry> - <entry>yes</entry> -</row><row> - <entry>hd-media <phrase condition="bootable-usb">(including usb-stick)</phrase></entry> - <entry>yes</entry> - <entry>yes</entry> - <entry>yes<footnoteref linkend='apx-ps-net'/></entry> -</row><row condition="supports-floppy-boot"> - <entry>floppy based (cd-drivers)</entry> - <entry>yes</entry> - <entry>yes</entry> - <entry>yes<footnoteref linkend='apx-ps-net'/></entry> -</row><row condition="supports-floppy-boot"> - <entry>floppy based (net-drivers)</entry> - <entry>yes</entry> - <entry>no</entry> - <entry>yes</entry> -</row><row arch="s390"> - <entry>generic/tape</entry> - <entry>yes</entry> - <entry>no</entry> - <entry>yes</entry> -</row> -</tbody> - -</tgroup></informaltable> - -</para><para> - -An important difference between the preseeding methods is the point at which -the preconfiguration file is loaded and processed. For initrd preseeding -this is right at the start of the installation, before the first question is -even asked. For file preseeding this is after the CD or CD image has been -loaded. For network preseeding it is only after the network has been -configured. - -</para><para> - -Obviously, any questions that have been processed before the -preconfiguration file is loaded cannot be preseeded (this will include -questions that are only displayed at medium or low priority, like the -first hardware detection run). <xref linkend="preseed-bootparms"/> -offers a way to avoid these questions being asked. - -</para><para> - -In order to avoid the questions that would normally appear before the -preseeding occurs, you can start the installer in <quote>auto</quote> -mode. This delays questions that would normally be asked too early for -preseeding (i.e. language, country and keyboard selection) until after -the network comes up, thus allowing them to be preseeded. It also runs -the installation at critical priority, which avoids many unimportant -questions. See <xref linkend="preseed-auto"/> for details. - -</para> - </sect2> - - <sect2 id="preseed-limitations"> - <title>Limitations</title> -<para> - -Although most questions used by &d-i; can be preseeded using this method, -there are some notable exceptions. You must (re)partition an entire disk -or use available free space on a disk; it is not possible to use existing -partitions. - -</para> - </sect2> - -<!-- Joeyh feels this is too technical, so leave it out for now - <sect2 id="preseed-debconf"> - <title>Debconf basics</title> -<para> - -Preseeding makes use of the <classname>debconf</classname> framework. This -framework is the preferred mechanism used in &debian; to interact with the user -when configuring packages and also forms the heart of &d-i;. -In the <classname>debconf</classname> framework questions or dialogs are -based on <firstterm>templates</firstterm>. There are different types of -templates for different types of questions. The actual questions are -<quote>generated</quote> from templates at runtime; multiple questions can -use the same template. - -</para><para> - -The following types of templates are relevant for preseeding. - -</para> - -<itemizedlist spacing="compact"> -<listitem><para> - string: allows the user to type any value -</para></listitem> -<listitem><para> - password: similar to string but the value typed is not displayed -</para></listitem> -<listitem><para> - boolean: for yes/no or true/false type of questions -</para></listitem> -<listitem><para> - select: allows the user to select one option from a list -</para></listitem> -<listitem><para> - multiselect: allows the user to select zero, one or more options from a list -</para></listitem> -<listitem><para> - note: used to display a message -</para></listitem> -</itemizedlist> - -<para> - -In &d-i; templates are stored in a readable file -<filename>/var/cache/debconf/templates.dat</filename>. This file contains all fixed -text and all translations. It can also contain a default value for the -template. The fixed text can include variables that will be replaced at -runtime. - -</para><para> - -Another readable file <filename>/var/cache/debconf/questions.dat</filename> -is used to store the values for variables and the answers given to questions. -A question always refers to the template used to ask it. For obvious -security reasons the values for questions of type <quote>password</quote> -are stored in a separate, non-readable file in the same directory. - -</para> - </sect2> ---> - </sect1> - - - <sect1 id="preseed-using"> - <title>Using preseeding</title> -<para> - -You will first need to create a preconfiguration file and place it in -the location from where you want to use it. Creating the preconfiguration file -is covered later in this appendix. Putting it in the correct location is fairly -straightforward for network preseeding or if you want to read the file off -a floppy or usb-stick. If you want to include the file on a CD or DVD, you -will have to remaster the ISO image. How to get the preconfiguration file -included in the initrd is outside the scope of this document; please consult -the developers' documentation for &d-i;. - -</para><para> - -An example preconfiguration file that you can use as basis for your own -preconfiguration file is available from &urlset-example-preseed;. This file is -based on the configuration fragments included in this appendix. - -</para> - - <sect2 id="preseed-loading"> - <title>Loading the preconfiguration file</title> -<para> - -If you are using initrd preseeding, you only have to make sure a file named -<filename>preseed.cfg</filename> is included in the root directory of the -initrd. The installer will automatically check if this file is present and -load it. - -</para><para> - -For the other preseeding methods you need to tell the installer what file -to use when you boot it. This is normally done by passing the kernel a boot -parameter, either manually at boot time or by editing the bootloader -configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the -parameter to the end of the append line(s) for the kernel. - -</para><para> - -If you do specify the preconfiguration file in the bootloader configuration, -you might change the configuration so you don't need to hit enter to boot the -installer. For syslinux this means setting the timeout to <literal>1</literal> -in <filename>syslinux.cfg</filename>. - -</para><para> - -To make sure the installer gets the right preconfiguration file, you can -optionally specify a checksum for the file. Currently this needs to be a -md5sum, and if specified it must match the preconfiguration file or the -installer will refuse to use it. - -</para> - -<informalexample><screen> -Boot parameters to specify: -- if you're netbooting: - preseed/url=http://host/path/to/preseed.cfg - preseed/url/checksum=5da499872becccfeda2c4872f9171c3d - -- if you're booting a remastered CD: - preseed/file=/cdrom/preseed.cfg - preseed/file/checksum=5da499872becccfeda2c4872f9171c3d - -- if you're installing from USB media (put the preconfiguration file in the - toplevel directory of the USB stick): - preseed/file=/hd-media/preseed.cfg - preseed/file/checksum=5da499872becccfeda2c4872f9171c3d -</screen></informalexample> - -<para> - -Note that <filename>preseed/url</filename> can be shortened to just -<filename>url</filename> and <filename>preseed/file</filename> to just -<filename>file</filename> when they are passed as boot parameters. - -</para> - </sect2> - - <sect2 id="preseed-bootparms"> - <title>Using boot parameters to preseed questions</title> -<para> - -If a preconfiguration file cannot be used to preseed some steps, the -install can still be fully automated, since you can pass preseed values on -the command line when booting the installer. - -</para><para> - -Boot parameters can also be used if you do not really want to use preseeding, -but just want to provide an answer for a specific question. Some examples where -this can be useful are documented elsewhere in this manual. - -</para><para> - -To set a value to be used inside &d-i;, just pass -<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput> -for any of the preseed variables listed in the examples in this appendix. -If a value is to be used to configure packages for the target system, you -will need to prepend the <firstterm>owner</firstterm><footnote> - -<para> -The owner of a debconf variable (or template) is normally the name of the -package that contains the corresponding debconf template. For variables -used in the installer itself the owner is <quote>d-i</quote>. -Templates and variables can have more than one owner which helps to -determine whether they can be removed from the debconf database if the -package is purged. -</para> - -</footnote> of the variable as in -<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>. -If you don't specify the owner, the value for the variable will not be -copied to the debconf database in the target system and thus remain unused -during the configuration of the relevant package. - -</para><para> - -Normally, preseeding a question in this way will mean that the question will -not be asked. To set a specific default value for a question, but still have -the question asked, use <quote>?=</quote> instead of <quote>=</quote> as -operator. See also <xref linkend="preseed-seenflag"/>. - -</para><para> - -Note that some variables that are frequently set at the boot prompt -have a shorter alias. If an alias is available, it is used in the -examples in this appendix instead of the full variable. The -<literal>preseed/url</literal> variable for example has been aliased as -<literal>url</literal>. Another example is the <literal>tasks</literal> -alias, which translates to <literal>tasksel:tasksel/first</literal>. - -</para><para> - -A <quote>--</quote> in the boot options has special meaning. Kernel -parameters that appear after the last <quote>--</quote> may be copied -into the bootloader configuration for the installed system (if supported by -the installer for the bootloader). The installer will automatically filter -out any options (like preconfiguration options) that it recognizes. - -</para> -<note arch="linux-any"><para> - -Current linux kernels (2.6.9 and later) accept a maximum of 32 command line -options and 32 environment options, including any options added by default -for the installer. If these numbers are exceeded, the kernel will panic -(crash). (For earlier kernels, these numbers were lower.) - -</para></note> -<para> - -For most installations some of the default options in your bootloader -configuration file, like <literal>vga=normal</literal>, may be safely -removed which may allow you to add more options for preseeding. - -</para> -<note><para> - -It may not always be possible to specify values with spaces for boot -parameters, even if you delimit them with quotes. - -</para></note> - </sect2> - - <sect2 id="preseed-auto"> - <title>Auto mode</title> -<para> - -There are several features of &debian; Installer that combine to allow -fairly simple command lines at the boot prompt to result in -arbitrarily complex customized automatic installs. To illustrate -this, here are some examples that can be used at the boot prompt: - -<informalexample><screen> -auto url=autoserver -</screen></informalexample> - -This relies on there being a DHCP server that will get the machine to -the point where <literal>autoserver</literal> can be resolved by DNS, -perhaps after adding the local domain if that was provided by DHCP. -If this was done at a site where the domain is -<literal>example.com</literal>, and they have a reasonably sane DHCP -setup, it would result in the preseed file being retrieved from -<literal>http://autoserver.example.com/d-i/&releasename;/./preseed.cfg</literal>. - -</para><para> - -The last part of that url (<literal>d-i/&releasename;/./preseed.cfg</literal>) -is taken from <literal>auto-install/defaultroot</literal>. By default -this includes the directory <literal>&releasename;</literal> to allow future versions -to specify their own codename and let people migrate forwards in a -controlled manner. The <literal>/./</literal> bit is used to indicate -a root, relative to which subsequent paths can be anchored (for use in -preseed/include and preseed/run). This allows files to be specified -either as full URLs, paths starting with / that are thus anchored, or -even paths relative to the location where the last preseed file was -found. This can be used to construct more portable scripts where an -entire hierarchy of scripts can be moved to a new location without -breaking it, for example copying the files onto a USB stick when they -started out on a web server. In this example, if the preseed file -sets <literal>preseed/run</literal> to -<literal>/scripts/late_command.sh</literal> then the file will be -fetched from -<literal>http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh</literal>. - -</para><para> - -If there is no local DHCP or DNS infrastructure, or if you do not want to -use the default path to <filename>preseed.cfg</filename>, you can still -use an explicit url, and if you don't use the <literal>/./</literal> -element it will be anchored to the start of the path (i.e. the third -<literal>/</literal> in the URL). Here is an example that requires minimal -support from the local network infrastructure: - -<informalexample><screen> -auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable> -</screen></informalexample> - -The way this works is that: -<itemizedlist spacing="compact"> -<listitem><para> -if the URL is missing a protocol, http is assumed, -</para></listitem> -<listitem><para> -if the hostname section contains no periods, it has the domain derived -from DHCP appended to it, and -</para></listitem> -<listitem><para> -if there's no <literal>/</literal>'s after the hostname, then the default -path is added. -</para></listitem> -</itemizedlist> - -</para><para> - -In addition to specifying the url, you can also specify settings that -do not directly affect the behavior of &d-i; itself, but can be passed -through to scripts specified using <literal>preseed/run</literal> -in the loaded preseed file. At present, the only example of -this is <literal>auto-install/classes</literal>, which has an alias -<literal>classes</literal>. This can be used thus: - -<informalexample><screen> -auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable> -</screen></informalexample> - -The classes could for example denote the type of system to be installed, -or the localization to be used. - -</para><para> - -It is of course possible to extend this concept, and if you do, it is -reasonable to use the auto-install namespace for this. So one might have -something like <literal>auto-install/style</literal> which is then used -in your scripts. If you feel the need to do this, please mention it on -the <email>debian-boot@lists.debian.org</email> mailing list so that we -can avoid namespace conflicts, and perhaps add an alias for the parameter -for you. - -</para><para> - -The <literal>auto</literal> boot label is not yet defined everywhere. -The same effect may be achieved by simply adding the two -parameters <literal>auto=true priority=critical</literal> to the kernel -command line. The <literal>auto</literal> parameter is an alias for -<literal>auto-install/enable</literal> and setting it to -<literal>true</literal> delays the -locale and keyboard questions until after there has been a chance to -preseed them, while <literal>priority</literal> is an alias for -<literal>debconf/priority</literal> and setting it to -<literal>critical</literal> stops any questions with a lower priority -from being asked. - -</para><para> - -Additional options that may be of interest while attempting to -automate an install while using DHCP are: <literal>interface=auto -netcfg/dhcp_timeout=60</literal> which makes the machine choose the -first viable NIC and be more patient about getting a reply to its -DHCP query. - -</para> -<tip><para> - -An extensive example of how to use this framework, including example scripts -and classes, can be found on the <ulink url="http://hands.com/d-i/">website -of its developer</ulink>. The examples available there also show many other -nice effects that can be achieved by creative use of preconfiguration. - -</para></tip> - </sect2> - - <sect2 id="preseed-aliases"> - <title>Aliases useful with preseeding</title> -<para> - -The following aliases can be useful when using (auto mode) preseeding. -Note that these are simply short aliases for question names, and you -always need to specify a value as well: for example, -<literal>auto=true</literal> or <literal>interface=eth0</literal>. - -</para> - -<!-- Setting column width does not seem to work; use non-breaking spaces - to separate columns a bit --> -<informaltable frame="none"> -<tgroup cols="2"><tbody> -<row><entry>auto</entry><entry>auto-install/enable</entry></row> -<row><entry>classes</entry><entry>auto-install/classes</entry></row> -<row><entry>fb</entry><entry>debian-installer/framebuffer</entry></row> -<row><entry>language</entry><entry>debian-installer/language</entry></row> -<row><entry>country</entry><entry>debian-installer/country</entry></row> -<row><entry>locale</entry><entry>debian-installer/locale</entry></row> -<row><entry>priority</entry><entry>debconf/priority</entry></row> -<row><entry>file</entry><entry>preseed/file</entry></row> -<row><entry>url</entry><entry>preseed/url</entry></row> -<row><entry>interface</entry><entry>netcfg/choose_interface</entry></row> -<row><entry>hostname </entry><entry>netcfg/get_hostname</entry></row> -<row><entry>domain</entry><entry>netcfg/get_domain</entry></row> -<row><entry>protocol</entry><entry>mirror/protocol</entry></row> -<row><entry>suite</entry><entry>mirror/suite</entry></row> -</tbody></tgroup> -</informaltable> - - </sect2> - - <sect2 id="preseed-dhcp"> - <title>Using a DHCP server to specify preconfiguration files</title> -<para> - -It's also possible to use DHCP to specify a preconfiguration file to download -from the network. DHCP allows specifying a filename. Normally this is a file -to netboot, but if it appears to be an URL then installation media that -support network preseeding will download the file from the URL and use it as a -preconfiguration file. Here is an example of how to set it up in the dhcpd.conf -for version 3 of the ISC DHCP server (the dhcp3-server &debian; package). - -</para> - -<informalexample><screen> -if substring (option vendor-class-identifier, 0, 3) = "d-i" { - filename "http://host/preseed.cfg"; -} -</screen></informalexample> - -<para> - -Note that the above example limits this filename to DHCP clients that identify -themselves as "d-i", so it will not affect regular DHCP clients, but only -the installer. You can also put the text in a stanza for only one particular -host to avoid preseeding all installs on your network. - -</para><para> - -A good way to use the DHCP preseeding is to only preseed values specific to -your network, such as the &debian; mirror to use. This way installs on your -network will automatically get a good mirror selected, but the rest of the -installation can be performed interactively. Using DHCP preseeding to fully -automate &debian; installs should only be done with care. - -</para> - </sect2> - </sect1> - - - <sect1 id="preseed-creating"> - <title>Creating a preconfiguration file</title> -<para> - -The preconfiguration file is in the format used by the -<command>debconf-set-selections</command> command. The general format of -a line in a preconfiguration file is: - -<informalexample><screen> -<owner> <question name> <question type> <value> -</screen></informalexample> - -</para><para> - -There are a few rules to keep in mind when writing a preconfiguration file. - -</para> - -<itemizedlist> -<listitem><para> - Put only a single space or tab between type and value: any additional - whitespace will be interpreted as belonging to the value. -</para></listitem> -<listitem><para> - A line can be split into multiple lines by appending a backslash - (<quote><literal>\</literal></quote>) as the line continuation character. - A good place to split a line is after the question name; a bad place is - between type and value. Split lines will be joined into a single line - with all leading/trailing whitespace condensed to a single space. -</para></listitem> -<listitem><para> - For debconf variables (templates) used in the installer itself, the - owner should be set to <quote>d-i</quote>; to preseed variables used - in the installed system, the name of the package that contains the - corresponding debconf template should be used. Only variables that have - their owner set to something other than <quote>d-i</quote> will be - propagated to the debconf database for the installed system. -</para></listitem> -<listitem><para> - Most questions need to be preseeded using the values valid in English and - not the translated values. However, there are some questions (for example - in <classname>partman</classname>) where the translated values need to be - used. -</para></listitem> -<listitem><para> - Some questions take a code as value instead of the English text that is - shown during installation. -</para></listitem> -</itemizedlist> - -<para> - -The easiest way to create a preconfiguration file is to use the example file -linked in <xref linkend="preseed-contents"/> as basis and work from there. - -</para><para> - -An alternative method is to do a manual installation and then, after -rebooting, use the <command>debconf-get-selections</command> from the -<classname>debconf-utils</classname> package to dump both the debconf -database and the installer's cdebconf database to a single file: - -<informalexample><screen> -$ debconf-get-selections --installer > <replaceable>file</replaceable> -$ debconf-get-selections >> <replaceable>file</replaceable> -</screen></informalexample> - -</para><para> - -However, a file generated in this manner will have some items that should -not be preseeded, and the example file is a better starting place for most -users. - -</para> - -<note><para> - -This method relies on the fact that, at the end of the installation, the -installer's cdebconf database is saved to the installed system in -<filename>/var/log/installer/cdebconf</filename>. However, because the -database may contain sensitive information, by default the files are only -readable by root. - -</para><para> - -The directory <filename>/var/log/installer</filename> and all files in it -will be deleted from your system if you purge the package -<classname>installation-report</classname>. - -</para></note> - -<para> - -To check possible values for questions, you can use <command>nano</command> -to examine the files in <filename>/var/lib/cdebconf</filename> while an -installation is in progress. View <filename>templates.dat</filename> for -the raw templates and <filename>questions.dat</filename> for the current -values and for the values assigned to variables. - -</para><para> - -To check if the format of your preconfiguration file is valid before performing -an install, you can use the command <command>debconf-set-selections -c -<replaceable>preseed.cfg</replaceable></command>. - -</para> - </sect1> - - - <sect1 id="preseed-contents"> - <title>Contents of the preconfiguration file (for &releasename;)</title> -<para> - -The configuration fragments used in this appendix are also available as an -example preconfiguration file from &urlset-example-preseed;. - -</para><para> - -Note that this example is based on an installation for the Intel x86 -architecture. If you are installing a different architecture, some of the -examples (like keyboard selection and bootloader installation) may not be -relevant and will need to be replaced by debconf settings appropriate for -your architecture. - -</para> - - <sect2 id="preseed-l10n"> - <title>Localization</title> -<para> - -Setting localization values will only work if you are using initrd preseeding. -With all other methods the preconfiguration file will only be loaded after -these questions have been asked. - -</para><para> - -The locale can be used to specify both language and country and can be any -combination of a language supported by &d-i; and a recognized country. If -the combination does not form a valid locale, the installer will automatically -select a locale that is valid for the selected language. -To specify the locale as a boot parameter, use -<userinput>locale=<replaceable>en_US</replaceable></userinput>. - -</para><para> - -Although this method is very easy to use, it does not allow preseeding of -all possible combinations of language, country and locale<footnote> - -<para> -Preseeding <literal>locale</literal> to <userinput>en_NL</userinput> would -for example result in <literal>en_US.UTF-8</literal> as default locale for -the installed system. If e.g. <literal>en_GB.UTF-8</literal> is preferred -instead, the values will need to be preseeded individually. -</para> - -</footnote>. So alternatively the values can be preseeded individually. -Language and country can also be specified as boot parameters. - -<informalexample role="example"><screen> -# Preseeding only locale sets language, country and locale. -d-i debian-installer/locale string en_US - -# The values can also be preseeded individually for greater flexibility. -#d-i debian-installer/language string en -#d-i debian-installer/country string NL -#d-i debian-installer/locale string en_GB.UTF-8 -# Optionally specify additional locales to be generated. -#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8 -</screen></informalexample> - -</para><para> - -Keyboard configuration consists of selecting a keymap. - -<informalexample role="example"><screen> -# Keyboard selection. -# keymap is an alias for keyboard-configuration/xkb-keymap -d-i keymap select us -# d-i keyboard-configuration/toggle select No toggling -</screen></informalexample> - -</para><para> - -To skip keyboard configuration, preseed -<classname>keymap</classname> with -<userinput>skip-config</userinput>. -This will result in the kernel keymap remaining active. - -</para> - - </sect2> - - <sect2 id="preseed-network"> - <title>Network configuration</title> -<para> - -Of course, preseeding the network configuration won't work if you're -loading your preconfiguration file from the network. But it's great when -you're booting from CD or USB stick. If you are loading preconfiguration -files from the network, you can pass network config parameters by using -kernel boot parameters. - -</para><para> - -If you need to pick a particular interface when netbooting before loading -a preconfiguration file from the network, use a boot parameter such as -<userinput>interface=<replaceable>eth1</replaceable></userinput>. - -</para><para> - -Although preseeding the network configuration is normally not possible when -using network preseeding (using <quote>preseed/url</quote>), you can use -the following hack to work around that, for example if you'd like to set a -static address for the network interface. The hack is to force the network -configuration to run again after the preconfiguration file has been loaded -by creating a <quote>preseed/run</quote> script containing the following -commands: - -<informalexample><screen> -killall.sh; netcfg -</screen></informalexample> - -</para><para> - -The following debconf variables are relevant for network configuration. - -</para> - -<informalexample role="example"><screen> -# Disable network configuration entirely. This is useful for cdrom -# installations on non-networked devices where the network questions, -# warning and long timeouts are a nuisance. -#d-i netcfg/enable boolean false - -# netcfg will choose an interface that has link if possible. This makes it -# skip displaying a list if there is more than one interface. -d-i netcfg/choose_interface select auto - -# To pick a particular interface instead: -#d-i netcfg/choose_interface select eth1 - -# If you have a slow dhcp server and the installer times out waiting for -# it, this might be useful. -#d-i netcfg/dhcp_timeout string 60 - -# If you prefer to configure the network manually, uncomment this line and -# the static network configuration below. -#d-i netcfg/disable_dhcp boolean true - -# If you want the preconfiguration file to work on systems both with and -# without a dhcp server, uncomment these lines and the static network -# configuration below. -#d-i netcfg/dhcp_failed note -#d-i netcfg/dhcp_options select Configure network manually - -# Static network configuration. -#d-i netcfg/get_nameservers string 192.168.1.1 -#d-i netcfg/get_ipaddress string 192.168.1.42 -#d-i netcfg/get_netmask string 255.255.255.0 -#d-i netcfg/get_gateway string 192.168.1.1 -#d-i netcfg/confirm_static boolean true - -# Any hostname and domain names assigned from dhcp take precedence over -# values set here. However, setting the values still prevents the questions -# from being shown, even if values come from dhcp. -d-i netcfg/get_hostname string unassigned-hostname -d-i netcfg/get_domain string unassigned-domain - -# Disable that annoying WEP key dialog. -d-i netcfg/wireless_wep string -# The wacky dhcp hostname that some ISPs use as a password of sorts. -#d-i netcfg/dhcp_hostname string radish - -# If non-free firmware is needed for the network or other hardware, you can -# configure the installer to always try to load it, without prompting. Or -# change to false to disable asking. -#d-i hw-detect/load_firmware boolean true -</screen></informalexample> - -<para> - -Please note that <command>netcfg</command> will automatically determine the -netmask if <classname>netcfg/get_netmask</classname> is not preseeded. In -this case, the variable has to be marked as <literal>seen</literal> for -automatic installations. Similarly, <command>netcfg</command> will choose -an appropriate address if <classname>netcfg/get_gateway</classname> is not -set. As a special case, you can set -<classname>netcfg/get_gateway</classname> to <quote>none</quote> to specify -that no gateway should be used. - -</para> - - </sect2> - - <sect2 id="preseed-network-console"> - <title>Network console</title> - -<informalexample role="example"><screen> -# Use the following settings if you wish to make use of the network-console -# component for remote installation over SSH. This only makes sense if you -# intend to perform the remainder of the installation manually. -#d-i anna/choose_modules string network-console -#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key -#d-i network-console/password password r00tme -#d-i network-console/password-again password r00tme -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-mirror"> - <title>Mirror settings</title> -<para> - -Depending on the installation method you use, a mirror may be used to -download additional components of the installer, to install the base system, -and to set up the <filename>/etc/apt/sources.list</filename> for the installed -system. - -</para><para> - -The parameter <classname>mirror/suite</classname> determines the suite for -the installed system. - -</para><para> - -The parameter <classname>mirror/udeb/suite</classname> determines the suite -for additional components for the installer. It is only useful to set this -if components are actually downloaded over the network and should match the -suite that was used to build the initrd for the installation method used for -the installation. Normally the installer will automatically use the correct -value and there should be no need to set this. - -</para> - -<informalexample role="example"><screen> -# If you select ftp, the mirror/country string does not need to be set. -#d-i mirror/protocol string ftp -d-i mirror/country string manual -d-i mirror/http/hostname string &archive-mirror; -d-i mirror/http/directory string /debian -d-i mirror/http/proxy string - -# Suite to install. -#d-i mirror/suite string testing -# Suite to use for loading installer components (optional). -#d-i mirror/udeb/suite string testing -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-account"> - <title>Account setup</title> -<para> - -The password for the root account and name and password for a first regular -user's account can be preseeded. For the passwords you can use either clear -text values or MD5 <emphasis>hashes</emphasis>. - -</para> -<warning><para> - -Be aware that preseeding passwords is not completely secure as everyone -with access to the preconfiguration file will have the knowledge of these -passwords. Using MD5 hashes is considered slightly better in terms of -security but it might also give a false sense of security as access to a -MD5 hash allows for brute force attacks. - -</para></warning> - -<informalexample role="example"><screen> -# Skip creation of a root account (normal user account will be able to -# use sudo). -#d-i passwd/root-login boolean false -# Alternatively, to skip creation of a normal user account. -#d-i passwd/make-user boolean false - -# Root password, either in clear text -#d-i passwd/root-password password r00tme -#d-i passwd/root-password-again password r00tme -# or encrypted using an MD5 hash. -#d-i passwd/root-password-crypted password [MD5 hash] - -# To create a normal user account. -#d-i passwd/user-fullname string Debian User -#d-i passwd/username string debian -# Normal user's password, either in clear text -#d-i passwd/user-password password insecure -#d-i passwd/user-password-again password insecure -# or encrypted using an MD5 hash. -#d-i passwd/user-password-crypted password [MD5 hash] -# Create the first user with the specified UID instead of the default. -#d-i passwd/user-uid string 1010 - -# The user account will be added to some standard initial groups. To -# override that, use this. -#d-i passwd/user-default-groups string audio cdrom video -</screen></informalexample> - -<para> - -The <classname>passwd/root-password-crypted</classname> and -<classname>passwd/user-password-crypted</classname> variables can also -be preseeded with <quote>!</quote> as their value. In that case, the -corresponding account is disabled. This may be convenient for the root -account, provided of course that an alternative method is set up to allow -administrative activities or root login (for instance by using SSH key -authentication or <command>sudo</command>). - -</para><para> - -The following command can be used to generate an MD5 hash for a password: - -<informalexample><screen> -$ printf "r00tme" | mkpasswd -s -m md5 -</screen></informalexample> - -</para> - </sect2> - - <sect2 id="preseed-time"> - <title>Clock and time zone setup</title> - -<informalexample role="example"><screen> -# Controls whether or not the hardware clock is set to UTC. -d-i clock-setup/utc boolean true - -# You may set this to any valid setting for $TZ; see the contents of -# /usr/share/zoneinfo/ for valid values. -d-i time/zone string US/Eastern - -# Controls whether to use NTP to set the clock during the install -d-i clock-setup/ntp boolean true -# NTP server to use. The default is almost always fine here. -#d-i clock-setup/ntp-server string ntp.example.com -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-partman"> - <title>Partitioning</title> -<para> - -Using preseeding to partition the harddisk is limited to what is supported -by <classname>partman-auto</classname>. You can choose to partition -either existing free space on a disk or a whole disk. The layout of the -disk can be determined by using a predefined recipe, a custom recipe from -a recipe file or a recipe included in the preconfiguration file. - -</para><para> - -Preseeding of advanced partition setups using RAID, LVM and encryption is -supported, but not with the full flexibility possible when partitioning -during a non-preseeded install. - -</para><para> - -The examples below only provide basic information on the use of recipes. -For detailed information see the files -<filename>partman-auto-recipe.txt</filename> and -<filename>partman-auto-raid-recipe.txt</filename> included in the -<classname>debian-installer</classname> package. -Both files are also available from the -<ulink url="&url-d-i-websvn;/trunk/installer/doc/devel/">&d-i; source -repository</ulink>. Note that the supported functionality may change -between releases. - -</para> - -<warning><para> - -The identification of disks is dependent on the order in which their drivers -are loaded. If there are multiple disks in the system, make very sure the -correct one will be selected before using preseeding. - -</para></warning> - - <sect3 id="preseed-partman-example"> - <title>Partitioning example</title> - -<informalexample role="example"><screen> -# If the system has free space you can choose to only partition that space. -# This is only honoured if partman-auto/method (below) is not set. -#d-i partman-auto/init_automatically_partition select biggest_free - -# Alternatively, you may specify a disk to partition. If the system has only -# one disk the installer will default to using that, but otherwise the device -# name must be given in traditional, non-devfs format (so e.g. /dev/hda or -# /dev/sda, and not e.g. /dev/discs/disc0/disc). -# For example, to use the first SCSI/SATA hard disk: -#d-i partman-auto/disk string /dev/sda -# In addition, you'll need to specify the method to use. -# The presently available methods are: -# - regular: use the usual partition types for your architecture -# - lvm: use LVM to partition the disk -# - crypto: use LVM within an encrypted partition -d-i partman-auto/method string lvm - -# If one of the disks that are going to be automatically partitioned -# contains an old LVM configuration, the user will normally receive a -# warning. This can be preseeded away... -d-i partman-lvm/device_remove_lvm boolean true -# The same applies to pre-existing software RAID array: -d-i partman-md/device_remove_md boolean true -# And the same goes for the confirmation to write the lvm partitions. -d-i partman-lvm/confirm boolean true -d-i partman-lvm/confirm_nooverwrite boolean true - -# You can choose one of the three predefined partitioning recipes: -# - atomic: all files in one partition -# - home: separate /home partition -# - multi: separate /home, /usr, /var, and /tmp partitions -d-i partman-auto/choose_recipe select atomic - -# Or provide a recipe of your own... -# If you have a way to get a recipe file into the d-i environment, you can -# just point at it. -#d-i partman-auto/expert_recipe_file string /hd-media/recipe - -# If not, you can put an entire recipe into the preconfiguration file in one -# (logical) line. This example creates a small /boot partition, suitable -# swap, and uses the rest of the space for the root partition: -#d-i partman-auto/expert_recipe string \ -# boot-root :: \ -# 40 50 100 ext3 \ -# $primary{ } $bootable{ } \ -# method{ format } format{ } \ -# use_filesystem{ } filesystem{ ext3 } \ -# mountpoint{ /boot } \ -# . \ -# 500 10000 1000000000 ext3 \ -# method{ format } format{ } \ -# use_filesystem{ } filesystem{ ext3 } \ -# mountpoint{ / } \ -# . \ -# 64 512 300% linux-swap \ -# method{ swap } format{ } \ -# . - -# The full recipe format is documented in the file partman-auto-recipe.txt -# included in the 'debian-installer' package or available from D-I source -# repository. This also documents how to specify settings such as file -# system labels, volume group names and which physical devices to include -# in a volume group. - -# This makes partman automatically partition without confirmation, provided -# that you told it what to do using one of the methods above. -d-i partman-partitioning/confirm_write_new_label boolean true -d-i partman/choose_partition select finish -d-i partman/confirm boolean true -d-i partman/confirm_nooverwrite boolean true -</screen></informalexample> - - </sect3> - <sect3 id="preseed-partman-raid"> - <title>Partitioning using RAID</title> -<para> - -You can also use preseeding to set up partitions on software RAID arrays. -Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and -specifying spare devices. -If you are using RAID 1, you can preseed grub to install to all devices -used in the array; see <xref linkend="preseed-bootloader"/>. - -</para> - -<warning><para> - -This type of automated partitioning is easy to get wrong. It is also -functionality that receives relatively little testing from the developers -of &d-i;. The responsibility to get the various recipes right (so they -make sense and don't conflict) lies with the user. -Check <filename>/var/log/syslog</filename> if you run into problems. - -</para></warning> - -<informalexample role="example"><screen> -# The method should be set to "raid". -#d-i partman-auto/method string raid -# Specify the disks to be partitioned. They will all get the same layout, -# so this will only work if the disks are the same size. -#d-i partman-auto/disk string /dev/sda /dev/sdb - -# Next you need to specify the physical partitions that will be used. -#d-i partman-auto/expert_recipe string \ -# multiraid :: \ -# 1000 5000 4000 raid \ -# $primary{ } method{ raid } \ -# . \ -# 64 512 300% raid \ -# method{ raid } \ -# . \ -# 500 10000 1000000000 raid \ -# method{ raid } \ -# . - -# Last you need to specify how the previously defined partitions will be -# used in the RAID setup. Remember to use the correct partition numbers -# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported; -# devices are separated using "#". -# Parameters are: -# <raidtype> <devcount> <sparecount> <fstype> <mountpoint> \ -# <devices> <sparedevices> - -#d-i partman-auto-raid/recipe string \ -# 1 2 0 ext3 / \ -# /dev/sda1#/dev/sdb1 \ -# . \ -# 1 2 0 swap - \ -# /dev/sda5#/dev/sdb5 \ -# . \ -# 0 2 0 ext3 /home \ -# /dev/sda6#/dev/sdb6 \ -# . - -# For additional information see the file partman-auto-raid-recipe.txt -# included in the 'debian-installer' package or available from D-I source -# repository. - -# This makes partman automatically partition without confirmation. -d-i partman-md/confirm boolean true -d-i partman-partitioning/confirm_write_new_label boolean true -d-i partman/choose_partition select finish -d-i partman/confirm boolean true -d-i partman/confirm_nooverwrite boolean true -</screen></informalexample> - - </sect3> - - <sect3 id="preseed-partman-mount-styles"> - <title>Controlling how partitions are mounted</title> -<para> - -Normally, filesystems are mounted using a universally unique identifier -(UUID) as a key; this allows them to be mounted properly even if their -device name changes. UUIDs are long and difficult to read, so, if you -prefer, the installer can mount filesystems based on the traditional device -names, or based on a label you assign. If you ask the installer to mount by -label, any filesystems without a label will be mounted using a UUID instead. - -</para><para> - -Devices with stable names, such as LVM logical volumes, will continue to use -their traditional names rather than UUIDs. - -</para> - -<warning><para> - -Traditional device names may change based on the order in which the kernel -discovers devices at boot, which may cause the wrong filesystem to be -mounted. Similarly, labels are likely to clash if you plug in a new disk or -a USB drive, and if that happens your system's behaviour when started will -be random. - -</para></warning> - -<informalexample role="example"><screen> -# The default is to mount by UUID, but you can also choose "traditional" to -# use traditional device names, or "label" to try filesystem labels before -# falling back to UUIDs. -#d-i partman/mount_style select uuid -</screen></informalexample> - - </sect3> - </sect2> - - <sect2 id="preseed-base-installer"> - <title>Base system installation</title> -<para> - -There is actually not very much that can be preseeded for this stage of the -installation. The only questions asked concern the installation of the kernel. - -</para> - -<informalexample role="example"><screen> -# Configure APT to not install recommended packages by default. Use of this -# option can result in an incomplete system and should only be used by very -# experienced users. -#d-i base-installer/install-recommends boolean false - -# Select the initramfs generator used to generate the initrd for 2.6 kernels. -#d-i base-installer/kernel/linux/initramfs-generators string initramfs-tools - -# The kernel image (meta) package to be installed; "none" can be used if no -# kernel is to be installed. -#d-i base-installer/kernel/image string &kernelpackage;-2.6-486 -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-apt"> - <title>Apt setup</title> -<para> - -Setup of the <filename>/etc/apt/sources.list</filename> and basic configuration -options is fully automated based on your installation method and answers to -earlier questions. You can optionally add other (local) repositories. - -</para> - -<informalexample role="example"><screen> -# You can choose to install non-free and contrib software. -#d-i apt-setup/non-free boolean true -#d-i apt-setup/contrib boolean true -# Uncomment this if you don't want to use a network mirror. -#d-i apt-setup/use_mirror boolean false -# Select which update services to use; define the mirrors to be used. -# Values shown below are the normal defaults. -#d-i apt-setup/services-select multiselect security, volatile -#d-i apt-setup/security_host string security.debian.org -#d-i apt-setup/volatile_host string volatile.debian.org - -# Additional repositories, local[0-9] available -#d-i apt-setup/local0/repository string \ -# http://local.server/debian stable main -#d-i apt-setup/local0/comment string local server -# Enable deb-src lines -#d-i apt-setup/local0/source boolean true -# URL to the public key of the local repository; you must provide a key or -# apt will complain about the unauthenticated repository and so the -# sources.list line will be left commented out -#d-i apt-setup/local0/key string http://local.server/key - -# By default the installer requires that repositories be authenticated -# using a known gpg key. This setting can be used to disable that -# authentication. Warning: Insecure, not recommended. -#d-i debian-installer/allow_unauthenticated boolean true -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-pkgsel"> - <title>Package selection</title> -<para> - -You can choose to install any combination of tasks that are available. -Available tasks as of this writing include: - -</para> - -<itemizedlist> -<listitem><para> - <userinput>standard</userinput> -</para></listitem> -<listitem><para> - <userinput>desktop</userinput> -</para></listitem> -<listitem><para> - <userinput>gnome-desktop</userinput> -</para></listitem> -<listitem><para> - <userinput>kde-desktop</userinput> -</para></listitem> -<listitem><para> - <userinput>web-server</userinput> -</para></listitem> -<listitem><para> - <userinput>print-server</userinput> -</para></listitem> -<listitem><para> - <userinput>dns-server</userinput> -</para></listitem> -<listitem><para> - <userinput>file-server</userinput> -</para></listitem> -<listitem><para> - <userinput>mail-server</userinput> -</para></listitem> -<listitem><para> - <userinput>sql-database</userinput> -</para></listitem> -<listitem><para> - <userinput>laptop</userinput> -</para></listitem> -</itemizedlist> - -<para> - -You can also choose to install no tasks, and force the installation of a -set of packages in some other way. We recommend always including the -<userinput>standard</userinput> task. - -</para><para> - -If you want to install some individual packages in addition to packages -installed by tasks, you can use the parameter -<classname>pkgsel/include</classname>. The value of this parameter can be -a list of packages separated by either commas or spaces, which allows it -to be used easily on the kernel command line as well. - -</para> - -<informalexample role="example"><screen> -#tasksel tasksel/first multiselect standard, web-server -# If the desktop task is selected, install the kde and xfce desktops -# instead of the default gnome desktop. -#tasksel tasksel/desktop multiselect kde, xfce - -# Individual additional packages to install -#d-i pkgsel/include string openssh-server build-essential -# Whether to upgrade packages after debootstrap. -# Allowed values: none, safe-upgrade, full-upgrade -#d-i pkgsel/upgrade select none - -# Some versions of the installer can report back on what software you have -# installed, and what software you use. The default is not to report back, -# but sending reports helps the project determine what software is most -# popular and include it on CDs. -#popularity-contest popularity-contest/participate boolean false -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-bootloader"> - <title>Boot loader installation</title> - -<informalexample role="example"><screen> -# Grub is the default boot loader (for x86). If you want lilo installed -# instead, uncomment this: -#d-i grub-installer/skip boolean true -# To also skip installing lilo, and install no bootloader, uncomment this -# too: -#d-i lilo-installer/skip boolean true - -# With a few exceptions for unusual partitioning setups, GRUB 2 is now the -# default. If you need GRUB Legacy for some particular reason, then -# uncomment this: -#d-i grub-installer/grub2_instead_of_grub_legacy boolean false - -# This is fairly safe to set, it makes grub install automatically to the MBR -# if no other operating system is detected on the machine. -d-i grub-installer/only_debian boolean true - -# This one makes grub-installer install to the MBR if it also finds some other -# OS, which is less safe as it might not be able to boot that other OS. -d-i grub-installer/with_other_os boolean true - -# Alternatively, if you want to install to a location other than the mbr, -# uncomment and edit these lines: -#d-i grub-installer/only_debian boolean false -#d-i grub-installer/with_other_os boolean false -#d-i grub-installer/bootdev string (hd0,0) -# To install grub to multiple disks: -#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0) - -# Optional password for grub, either in clear text -#d-i grub-installer/password password r00tme -#d-i grub-installer/password-again password r00tme -# or encrypted using an MD5 hash, see grub-md5-crypt(8). -#d-i grub-installer/password-crypted password [MD5 hash] - -# Use the following option to add additional boot parameters for the -# installed system (if supported by the bootloader installer). -# Note: options passed to the installer will be added automatically. -#d-i debian-installer/add-kernel-opts string nousb -</screen></informalexample> - -<para> - -An MD5 hash for a password for <classname>grub</classname> can be generated -using <command>grub-md5-crypt</command>, or using the command from the -example in <xref linkend="preseed-account"/>. - -</para> - </sect2> - - <sect2 id="preseed-finish"> - <title>Finishing up the installation</title> - -<informalexample role="example"><screen> -# During installations from serial console, the regular virtual consoles -# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next -# line to prevent this. -#d-i finish-install/keep-consoles boolean true - -# Avoid that last message about the install being complete. -d-i finish-install/reboot_in_progress note - -# This will prevent the installer from ejecting the CD during the reboot, -# which is useful in some situations. -#d-i cdrom-detect/eject boolean false - -# This is how to make the installer shutdown when finished, but not -# reboot into the installed system. -#d-i debian-installer/exit/halt boolean true -# This will power off the machine instead of just halting it. -#d-i debian-installer/exit/poweroff boolean true -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-other"> - <title>Preseeding other packages</title> - -<informalexample role="example"><screen> -# Depending on what software you choose to install, or if things go wrong -# during the installation process, it's possible that other questions may -# be asked. You can preseed those too, of course. To get a list of every -# possible question that could be asked during an install, do an -# installation, and then run these commands: -# debconf-get-selections --installer > file -# debconf-get-selections >> file -</screen></informalexample> - - </sect2> - </sect1> - - - <sect1 id="preseed-advanced"> - <title>Advanced options</title> - - <sect2 id="preseed-hooks"> - <title>Running custom commands during the installation</title> -<para> - -A very powerful and flexible option offered by the preconfiguration tools -is the ability to run commands or scripts at certain points in the -installation. - -</para> - -<informalexample role="example"><screen> -# d-i preseeding is inherently not secure. Nothing in the installer checks -# for attempts at buffer overflows or other exploits of the values of a -# preconfiguration file like this one. Only use preconfiguration files from -# trusted locations! To drive that home, and because it's generally useful, -# here's a way to run any shell command you'd like inside the installer, -# automatically. - -# This first command is run as early as possible, just after -# preseeding is read. -#d-i preseed/early_command string anna-install some-udeb -# This command is run immediately before the partitioner starts. It may be -# useful to apply dynamic partitioner preseeding that depends on the state -# of the disks (which may not be visible when preseed/early_command runs). -#d-i partman/early_command \ -# string debconf-set partman-auto/disk "$(list-devices disk | head -n1)" -# This command is run just before the install finishes, but when there is -# still a usable /target directory. You can chroot to /target and use it -# directly, or use the apt-install and in-target commands to easily install -# packages and run commands in the target system. -#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh -</screen></informalexample> - - </sect2> - - <sect2 id="preseed-seenflag"> - <title>Using preseeding to change default values</title> -<para> - -It is possible to use preseeding to change the default answer for a -question, but still have the question asked. To do this the -<firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after -setting the value for a question. - -<informalexample><screen> -d-i foo/bar string value -d-i foo/bar seen false -</screen></informalexample> - -The same effect can be achieved for <emphasis>all</emphasis> questions by -setting the parameter <classname>preseed/interactive=true</classname> at -the boot prompt. This can also be useful for testing or debugging your -preconfiguration file. - -</para><para> - -Note that the <quote>d-i</quote> owner should only be used for variables -used in the installer itself. For variables belonging to packages installed -on the target system, you should use the name of that package instead. See -the footnote to <xref linkend="preseed-bootparms"/>. - -</para><para> - -If you are preseeding using boot parameters, you can make the installer ask -the corresponding question by using the <quote>?=</quote> operator, i.e. -<userinput><replaceable>foo</replaceable>/<replaceable>bar</replaceable>?=<replaceable>value</replaceable></userinput> -(or <userinput><replaceable>owner</replaceable>:<replaceable>foo/bar</replaceable>?=<replaceable>value</replaceable></userinput>). -This will of course only have effect for parameters that correspond to -questions that are actually displayed during an installation and not for -<quote>internal</quote> parameters. - -</para> - </sect2> - - <sect2 id="preseed-chainload"> - <title>Chainloading preconfiguration files</title> -<para> - -It is possible to include other preconfiguration files from a preconfiguration -file. Any settings in those files will override pre-existing settings from -files loaded earlier. This makes it possible to put, for example, general -networking settings for your location in one file and more specific -settings for certain configurations in other files. - -</para> - -<informalexample><screen> -# More than one file can be listed, separated by spaces; all will be -# loaded. The included files can have preseed/include directives of their -# own as well. Note that if the filenames are relative, they are taken from -# the same directory as the preconfiguration file that includes them. -#d-i preseed/include string x.cfg - -# The installer can optionally verify checksums of preconfiguration files -# before using them. Currently only md5sums are supported, list the md5sums -# in the same order as the list of files to include. -#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d - -# More flexibly, this runs a shell command and if it outputs the names of -# preconfiguration files, includes those files. -#d-i preseed/include_command \ -# string if [ "`hostname`" = bob ]; then echo bob.cfg; fi - -# Most flexibly of all, this downloads a program and runs it. The program -# can use commands such as debconf-set to manipulate the debconf database. -# More than one script can be listed, separated by spaces. -# Note that if the filenames are relative, they are taken from the same -# directory as the preconfiguration file that runs them. -#d-i preseed/run string foo.sh -</screen></informalexample> - -<para> - -It is also possible to chainload from the initrd or file preseeding phase, -into network preseeding by setting preseed/url in the earlier files. -This will cause network preseeding to be performed when the network comes -up. You need to be careful when doing this, since there will be two -distinct runs at preseeding, meaning for example that you get another -chance to run the preseed/early command, the second one happening after the -network comes up. - -</para> - - </sect2> - </sect1> -</appendix> diff --git a/nl/appendix/random-bits.xml b/nl/appendix/random-bits.xml deleted file mode 100644 index d78717e51..000000000 --- a/nl/appendix/random-bits.xml +++ /dev/null @@ -1,12 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 45239 untranslated --> - -<appendix id="random-bits"><title>Random Bits</title> - -&files.xml; -&chroot-install.xml; -&plip.xml; -&pppoe.xml; -&graphical.xml; - -</appendix> diff --git a/nl/bookinfo.xml b/nl/bookinfo.xml deleted file mode 100644 index bda199627..000000000 --- a/nl/bookinfo.xml +++ /dev/null @@ -1,62 +0,0 @@ -<!-- original version: 61133 --> - -<bookinfo id="debian_installation_guide"> -<title>&debian-gnu; Installatiehandleiding</title> - -<abstract> -<para> -Dit document bevat instructies voor de installatie van het &debian-gnu; -&release; systeem (codenaam <quote>&releasename;</quote>), -voor het &arch-title; (<quote>&architecture;</quote>) -platform. Verder bevat het verwijzingen naar aanvullende informatie en -informatie over hoe u het meeste uit uw nieuwe &debian; systeem kunt halen. -</para> - -<para> -<warning condition="not-checked"><para> -Deze installatiehandleiding is gebaseerd op een eerdere handleiding die -is geschreven voor het oude installatiesysteem van Debian (de -<quote>boot-floppies</quote>) en is bijgewerkt voor de nieuwe &d-i;. Voor -&architecture; is de handleiding echter nog niet volledig bijgewerkt en -gecontroleerd voor het nieuwe installatiesysteem. Het is mogelijk dat er -nog delen zijnvan de handleiding die onvolledig of verouderd zijn, of die -nog steeds de oude boot-floppies beschrijven. Nieuwere versies van deze -handleiding, die mogelijk dit platform beter beschrijven, kunt u vinden -op het Internet op de <ulink url="&url-d-i;">&d-i; website</ulink>. -Mogelijk kunt u daar ook aanvullende vertalingen vinden. -</para></warning> - -<note condition="checked"><para> -Hoewel deze installatiehandleiding voor &architecture; grotendeels is bijgewerkt, -zijn er plannen voor wijzigingen en een reorganisatie van delen van de handleiding -na de officiële vrijgave van &releasename;. Nieuwere versies van deze handleiding -kunt u vinden op het Internet op de <ulink url="&url-d-i;">&d-i; website</ulink>. -Mogelijk kunt u daar ook aanvullende vertalingen vinden. -</para></note> -</para> - -<para condition="translation-status"> -Deze handleiding is oorspronkelijk geschreven in het Engels en de -vertaling naar het Nederlands is nog niet volledig. Voor de delen die nog -niet zijn vertaald is de originele, Engelstalige tekst opgenomen. -Voor informatie over de vertaling naar het Nederlands kunt u een e-mail -sturen naar de <email>debian-l10n-dutch@lists.debian.org</email> -mailinglijst. Zie ook <xref linkend="getting-newest-doc"/>. -</para> -</abstract> - -<copyright> - <year>2004 – 2012</year> - <holder>het Debian Installatiesysteem team</holder> -</copyright> - -<legalnotice> -<para> - -Deze handleiding is vrije software; u mag deze verspreiden en/of wijzigen -onder de bepalingen van de GNU Algemene Publieke Licentie. U wordt verzocht -de licentie in <xref linkend="appendix-gpl"/> te raadplegen. - -</para> -</legalnotice> -</bookinfo> diff --git a/nl/boot-installer/accessibility.xml b/nl/boot-installer/accessibility.xml deleted file mode 100644 index 6ce4ca335..000000000 --- a/nl/boot-installer/accessibility.xml +++ /dev/null @@ -1,110 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62899 untranslated --> - - <sect1 id="boot-installer-accessibility" arch="not-s390"> - <title>Accessibility</title> -<para> - -Some users may need specific support because of e.g. some visual -impairment. -<phrase arch="ia64;powerpc;x86">USB braille displays are detected -automatically, but most other</phrase> -<phrase arch="arm;hppa;mips;mipsel;sparc">Most</phrase> -accessibility features have to be enabled manually. -<phrase arch="x86">On machines that support it, the boot menu emits a beep -when it is ready to receive keystrokes.</phrase> -Some boot parameters can <phrase arch="x86">then</phrase> be appended to -enable accessibility features. Note that on most architectures the boot -loader interprets your keyboard as a QWERTY keyboard. - -</para> - - <sect2 arch="ia64;powerpc;x86"> - <title>USB Braille Displays</title> -<para> - -USB braille displays should be automatically detected. A textual version -of the installer will then be automatically selected, and support for the -braille display will be automatically installed on the target system. -You can thus just press &enterkey; at the boot menu. -Once <classname>brltty</classname> is started, you can choose a braille -table by entering the preference menu. Documentation on key -bindings for braille devices is available on the <ulink -url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>. - -</para> - </sect2> - - <sect2 arch="ia64;powerpc;x86"> - <title>Serial Braille Displays</title> -<para> - -Serial braille displays cannot safely be automatically detected -(since that may damage some of them). You thus need to append the -<userinput>brltty=<replaceable>driver</replaceable>,<replaceable>port</replaceable>,<replaceable>table</replaceable></userinput> -boot parameter to tell <classname>brltty</classname> which driver it -should use. <replaceable>driver</replaceable> should be replaced by the -two-letter driver code for your terminal (see the -<ulink url="&url-brltty-manual;">driver code list</ulink>). -<replaceable>port</replaceable> should be replaced by the name of the -serial port the display is connected to, <userinput>ttyS0</userinput> is -the default. <replaceable>table</replaceable> is the name of the braille -table to be used (see the <ulink url="&url-brltty-manual;">table code -list</ulink>); the English table is the default. Note that the table can -be changed later by entering the preference menu. Documentation on key -bindings for braille devices is available on the <ulink -url="&url-brltty-driver-help;"><classname>brltty</classname> website</ulink>. - -</para> - </sect2> - - <sect2 arch="x86"> - <title>Hardware Speech Synthesis</title> -<para> - -Support for hardware speech synthesis devices is available only alongside -support for graphical installer. You thus need to select the -<quote>Graphical install</quote> entry in the boot menu. - -</para><para> - -Hardware speech synthesis devices cannot be automatically detected. You -thus need to append the -<userinput>speakup.synth=<replaceable>driver</replaceable></userinput> -boot parameter to tell <classname>speakup</classname> which driver it should -use. <replaceable>driver</replaceable> should be replaced by the driver code -for your device (see <ulink url="&url-speakup-driver-codes;">driver code -list</ulink>). The textual version of the installer will then be -automatically selected, and support for the speech synthesis device will be -automatically installed on the target system. - -</para> - </sect2> - - <sect2 arch="linux-any"><title>Board Devices</title> -<para> - -Some accessibility devices are actual boards that are plugged inside the -machine and that read text directly from the video memory. To get them -to work framebuffer support must be disabled by using the -<userinput arch="x86">vga=normal</userinput> <userinput>fb=false</userinput> -boot parameter. This will however reduce the number of available languages. - -</para><para arch="x86"> - -If desired a textual version of the bootloader can be activated before adding -the boot parameter by typing <userinput>h</userinput> &enterkey;. - -</para> - </sect2> - - <sect2><title>High-Contrast Theme</title> -<para> - -For users with low vision, the installer can use a high-contrast -theme that makes it more readable. To enable it, append the -<userinput>theme=dark</userinput> boot parameter. - -</para> - </sect2> - </sect1> diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml deleted file mode 100644 index d295d0894..000000000 --- a/nl/boot-installer/arm.xml +++ /dev/null @@ -1,236 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62875 untranslated --> - - <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title> - -&boot-installer-intro-net.xml; - - </sect2> - - - <sect2 arch="arm"><title>Booting from CD-ROM</title> - -&boot-installer-intro-cd.xml; - - </sect2> - - - <sect2 arch="arm" id="boot-firmware"><title>Booting from Firmware</title> - -&boot-installer-intro-firmware.xml; - - <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title> -<para> - -There are three ways how to put the installer firmware into flash: - -</para> - - <sect4 arch="arm"><title>Using the NSLU2 web interface</title> -<para> - -Go to the administration section and choose the menu item -<literal>Upgrade</literal>. You can then browse your disk for the -installer image you have previously downloaded. Then press the -<literal>Start Upgrade</literal> button, confirm, wait for a few minutes -and confirm again. The system will then boot straight into the installer. - -</para> - </sect4> - - <sect4 arch="arm"><title>Via the network using Linux/Unix</title> -<para> - -You can use <command>upslug2</command> from any Linux or Unix machine to -upgrade the machine via the network. This software is packaged for -&debian;. - -First, you have to put your NSLU2 in upgrade mode: - -<orderedlist> -<listitem><para> - -Disconnect any disks and/or devices from the USB ports. - -</para></listitem> -<listitem><para> - -Power off the NSLU2 - -</para></listitem> -<listitem><para> - -Press and hold the reset button (accessible through the small hole on the -back just above the power input). - -</para></listitem> -<listitem><para> - -Press and release the power button to power on the NSLU2. - -</para></listitem> -<listitem><para> - -Wait for 10 seconds watching the ready/status LED. After 10 seconds it -will change from amber to red. Immediately release the reset button. - -</para></listitem> -<listitem><para> - -The NSLU2 ready/status LED will flash alternately red/green (there is a 1 -second delay before the first green). The NSLU2 is now in upgrade mode. - -</para></listitem> -</orderedlist> - -See the <ulink -url="http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary">NSLU2-Linux -pages</ulink> if you have problems with this. - -Once your NSLU2 is in upgrade mode, you can flash the new image: - -<informalexample><screen> -sudo upslug2 -i di-nslu2.bin -</screen></informalexample> - -Note that the tool also shows the MAC address of your NSLU2, which may come -in handy to configure your DHCP server. After the whole image has been -written and verified, the system will automatically reboot. Make sure you -connect your USB disk again now, otherwise the installer won't be able to -find it. - -</para> - </sect4> - - <sect4 arch="arm"><title>Via the network using Windows</title> -<para> - -There is <ulink -url="http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip">a -tool</ulink> for Windows to upgrade the firmware via the network. - -</para> - </sect4> - </sect3> - - <sect3 arch="arm" id="boot-firmware-ss4000e"> - <title>Booting the SS4000-E</title> -<para> - -Due to limitations in the SS4000-E firmware, it unfortunately is not -possible to boot the installer without the use of a serial port at -this time. To boot the installer, you will need a serial nullmodem -cable; a computer with a serial port<footnote id="arm-s4ke-port"> - -<para> -A USB serial converter will also work. -</para> - -</footnote>; and a ribbon cable with a male DB9 connector at one end, -and a 10-pin .1" IDC header at the other<footnote id="arm-s4k-rib"> - -<para> -This cable is often found in older desktop machines with builtin 9-pin -serial ports. -</para> - -</footnote>. - -</para><para> - -To boot the SS4000-E, use your serial nullmodem cable and the ribbon -cable to connect to the serial port of the SS4000-E, and reboot the -machine. You need to use a serial terminal application to communicate -with the machine; a good option on a &debian; GNU/Linux is to use the -<command>cu</command> program, in the package of the same name. Assuming -the serial port on your computer is to be found on -<filename>/dev/ttyS0</filename>, use the following command line: - -</para> - -<informalexample><screen> -cu -lttyS0 -s115200 -</screen></informalexample> - -<para> - -If using Windows, you may want to consider using the program -<classname>hyperterminal</classname>. Use a baud rate of 115200, -8 bits word length, no stop bits, and one parity bit. - -</para><para> - -When the machine boots, you will see the following line of output: - -</para> - -<informalexample><screen> -No network interfaces found - -EM-7210 ver.T04 2005-12-12 (For ver.AA) -== Executing boot script in 1.000 seconds - enter ^C to abort -</screen></informalexample> - -<para> - -At this point, hit Control-C to interrupt the boot -loader<footnote id="arm-s4ke-sec"> - -<para> -Note that you have only one second to do so; if you miss this window, -just powercycle the machine and try again. -</para> - -</footnote>. This will give you the RedBoot prompt. Enter the -following commands: - -<informalexample><screen> -load -v -r -b 0x01800000 -m ymodem ramdisk.gz -load -v -r -b 0x01008000 -m ymodem zImage -exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000 -</screen></informalexample> - -</para><para> - -After every <command>load</command> command, the system will expect a -file to be transmitted using the YMODEM protocol. When using cu, make -sure you have the package <classname>lrzsz</classname> installed, then -hit enter, followed by the <quote>~<</quote> escape sequence to start -an external program, and run <command>sb initrd.gz</command> or -<command>sb vmlinuz</command>. - -</para><para> - -Alternatively, it is possible to load the kernel and ramdisk using -HTTP rather than YMODEM. This is faster, but requires a working HTTP -server on the network. To do so, first switch the bootloader to RAM mode: - -<informalexample><screen> -fis load rammode -g -</screen></informalexample> - -</para><para> - -This will seemingly restart the machine; but in reality, it loads -reboot to RAM and restarts it from there. Not doing this step will cause -the system to hang in the necessary ip_address step that comes next. - -</para><para> - -You will need to hit Ctrl-C again to interrupt the boot. Then: - -<informalexample><screen> -ip_address -l 192.168.2.249 -h 192.168.2.4 -load -v -r -b 0x01800000 -m http /initrd.gz -load -v -r -b 0x01008000 -m http /zImage -exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000 -</screen></informalexample> - -</para><para> - -The installer will now start as usual. - -</para> - </sect3> - </sect2> diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml deleted file mode 100644 index 7aaad3b0e..000000000 --- a/nl/boot-installer/boot-installer.xml +++ /dev/null @@ -1,49 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - -<chapter id="boot-installer"><title>Booting the Installation System</title> - -<!-- Include only archs that are documented to avoid build-errors --> -<!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="arm;any-x86;ia64;mips;mipsel;s390;powerpc;sparc"> - <title>Booting the Installer on &arch-title;</title> - -<!-- This info is so architecture dependent, that I have turned the --> -<!-- structure inside out for this chapter. Each arch has a document. --> -<!-- Note: arch hppa is currently missing --> - -<warning arch="any-x86;powerpc"><para> - -If you have any other operating systems on your system that you wish to -keep (dual boot setup), you should make sure that they have been properly -shut down <emphasis>before</emphasis> you boot the installer. -Installing an operating system while another operating system is in -hibernation (has been suspended to disk) could result in loss of, or damage -to the state of the suspended operating system which could cause problems -when it is rebooted. - -</para></warning> -<note condition="gtk"><para> - -For information on how to boot the graphical installer, see -<xref linkend="graphical"/>. - -</para></note> - -&boot-installer-arm.xml; -<!-- &boot-installer-hppa.xml; --> -&boot-installer-x86.xml; -&boot-installer-ia64.xml; -&boot-installer-mips.xml; -&boot-installer-mipsel.xml; -&boot-installer-s390.xml; -&boot-installer-powerpc.xml; -&boot-installer-sparc.xml; - - </sect1> - -&boot-installer-accessibility.xml; -&boot-installer-parameters.xml; -&boot-installer-trouble.xml; - -</chapter> diff --git a/nl/boot-installer/hppa.xml b/nl/boot-installer/hppa.xml deleted file mode 100644 index 619d3eaf1..000000000 --- a/nl/boot-installer/hppa.xml +++ /dev/null @@ -1,12 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> - - <sect2 arch="hppa"> - <title></title> -<para> - -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> - -</para> - </sect2> diff --git a/nl/boot-installer/ia64.xml b/nl/boot-installer/ia64.xml deleted file mode 100644 index 17104727e..000000000 --- a/nl/boot-installer/ia64.xml +++ /dev/null @@ -1,464 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43841 untranslated --> - - <sect2 arch="ia64"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - - <note> - <title>CD Contents</title> - -<para> - -There are three basic variations of &debian; Install CDs. -The <emphasis>Business Card</emphasis> CD has a minimal installation -that will fit on the small form factor CD media. -It requires a network connection in order to install the rest of the -base installation and make a usable system. -The <emphasis>Network Install</emphasis> CD has all of the packages -for a base install but requires a network connection to a &debian; -mirror site in order to install the -extra packages one would want for a complete system . -The set of &debian; CDs can install a complete system from the wide -range of packages without needing access to the network. -</para> - </note> - -<para> - -The IA-64 architecture uses the next generation Extensible Firmware Interface -(EFI) from Intel. -Unlike the traditional x86 BIOS which knows little about the boot -device other than the partition table and Master Boot Record (MBR), -EFI can read and write files from FAT16 or FAT32 formatted disk -partitions. -This simplifies the often arcane process of starting a system. -The system boot loader and the EFI firmware that supports it have -a full filesystem to store the files necessary for booting the -machine. -This means that the system disk on an IA-64 system has an additional -disk partition dedicated to EFI instead of the simple MBR or boot -block on more conventional systems. - -</para><para> - -The &debian; Installer CD contains a small EFI partition where the -<command>ELILO</command> bootloader, its configuration file, the installer's -kernel, and initial filesystem (initrd) are located. -The running system also contains an EFI partition where the necessary -files for booting the system reside. -These files are readable from the EFI Shell as described below. - -</para><para> - -Most of the details of how <command>ELILO</command> actually loads and -starts a system are transparent to the system installer. -However, the installer must set up an EFI partition prior to installing -the base system. Otherwise, the installation of <command>ELILO</command> -will fail, rendering the system un-bootable. -The EFI partition is allocated and formatted in the partitioning step -of the installation prior to loading any packages on the system disk. -The partitioning task also verifies that a suitable EFI partition is -present before allowing the installation to proceed. - -</para><para> - -The EFI Boot Manager is presented as the last step of the firmware -initialization. -It displays a menu list from which the user can select -an option. -Depending on the model of system and what other software has been -loaded on the system, this menu may be different from one system -to another. -There should be at least two menu items displayed, -<command>Boot Option Maintenance Menu</command> and -<command>EFI Shell (Built-in)</command>. -Using the first option is preferred, however, if that -option is not available or the CD for some reason does not -boot with it, use the second option. - -</para> - - <warning> - <title>IMPORTANT</title> -<para> -The EFI Boot Manager will select a default boot action, typically -the first menu choice, within a pre-set number of seconds. -This is indicated by a countdown at the bottom of the screen. -Once the timer expires and the systems starts the default action, -you may have to reboot the machine in order to continue the installation. -If the default action is the EFI Shell, you can return to the Boot Manager -by running <command>exit</command> at the shell prompt. -</para> - </warning> - - <sect3 arch="ia64" id="bootable-cd"> - <title>Option 1: Booting from the Boot Option Maintenance Menu</title> -<para> - -</para> - -<itemizedlist> - -<listitem><para> -Insert the CD in the DVD/CD drive and reboot the machine. -The firmware will display the EFI Boot Manager page and menu after -it completes its system initialization. -</para></listitem> - -<listitem><para> -Select <command>Boot Maintenance Menu</command> from the menu -with the arrow keys and press <command>ENTER</command>. -This will display a new menu. -</para></listitem> - -<listitem><para> -Select <command>Boot From a File</command> from the menu -with the arrow keys and press <command>ENTER</command>. -This will display a list of devices probed by the firmware. -You should see two menu lines containing either the label -<command>Debian Inst [Acpi ...</command> or -<command>Removable Media Boot</command>. -If you examine the rest of the menu line, you will notice that -the device and controller information should be the same. -</para></listitem> - -<listitem><para> -You can choose either of the entries that refer to the CD/DVD -drive. -Select your choice with the arrow keys and press <command>ENTER</command>. -If you choose <command>Removable Media Boot</command> the machine -will immediately start the boot load sequence. -If you choose <command>Debian Inst [Acpi ...</command> instead, it -will display a directory listing of the bootable portion of the -CD, requiring you to proceed to the next (additional) step. -</para></listitem> - -<listitem><para> -You will only need this step if you chose -<command>Debian Inst [Acpi ...</command>. -The directory listing will also show -<command>[Treat like Removable Media Boot]</command> on the next to -the last line. -Select this line with the arrow keys and press <command>ENTER</command>. -This will start the boot load sequence. -</para></listitem> - -</itemizedlist> - -<para> - -These steps start the &debian; boot loader which will display a -menu page for you to select a boot kernel and options. -Proceed to selecting the boot kernel and options. - -</para> - </sect3> - - <sect3 arch="ia64" id="boot-with-efi"> - <title>Option 2: Booting from the EFI Shell</title> -<para> - -If, for some reason, option 1 is not successful, reboot the machine -and when the EFI Boot Manager screen appears there should be -one option called <command>EFI Shell [Built-in]</command>. -Boot the &debian; Installer CD with the following steps: - -</para> - -<itemizedlist> - -<listitem><para> -Insert the CD in the DVD/CD drive and reboot the machine. -The firmware will display the EFI Boot Manager page and menu after -it completes system initialization. -</para></listitem> - -<listitem><para> -Select <command>EFI Shell</command> from the menu with the arrow keys -and press <command>ENTER</command>. -The EFI Shell will scan all of the bootable devices and display -them to the console before displaying its command prompt. -The recognized bootable partitions on devices will show a device name of -<filename>fs<replaceable>n</replaceable>:</filename>. -All other recognized partitions will be named -<filename>blk<replaceable>n</replaceable>:</filename>. -If you inserted the CD just before entering the shell, this may -take a few extra seconds as it initializes the CD drive. -</para> -</listitem> - -<listitem><para> -Examine the output from the shell looking for the CDROM drive. -It is most likely the <filename>fs0:</filename> device although -other devices with bootable partitions will also show up as -<filename>fs<replaceable>n</replaceable></filename>. -</para></listitem> - -<listitem><para> -Enter <command>fs<replaceable>n</replaceable>:</command> and press -<command>ENTER</command> to select that -device where <replaceable>n</replaceable> is the partition number for the -CDROM. The shell will now display the partition number as its prompt. -</para></listitem> - -<listitem><para> -Enter <command>elilo</command> and press <command>ENTER</command>. -This will start the boot load sequence. -</para></listitem> - -</itemizedlist> - -<para> - -As with option 1, these steps start the &debian; boot loader which will -display a menu page for you to select a boot kernel and options. -You can also enter the shorter -<command>fs<replaceable>n</replaceable>:elilo</command> command at -the shell prompt. -Proceed to selecting the boot kernel and options. - -</para> - - </sect3> - - <sect3 arch="ia64" id="serial-console"> - <title>Installing using a Serial Console</title> - -<para> - -You may choose to perform an install using a monitor and keyboard -or using a serial connection. To use a monitor/keyboard setup, -select an option containing the string [VGA console]. To install -over a serial connection, choose an option containing the string -[<replaceable>BAUD</replaceable> baud serial console], where -<replaceable>BAUD</replaceable> is the speed of your serial console. -Menu items for the most typical baud rate settings on the ttyS0 -device are preconfigured. - -</para><para> - -In most circumstances, you will want the installer to use the same -baud rate as your connection to the EFI console. If you aren't -sure what this setting is, you can obtain it using the command -<command>baud</command> at the EFI shell. - -</para><para> - -If there is not an option available that is configured for the serial -device or baud rate you would like to use, you may override the console setting -for one of the existing menu options. For example, to use a -57600 baud console over the ttyS1 device, enter -<command>console=ttyS1,57600n8</command> into -the <classname>Boot:</classname> text window. - -</para> - -<note><para> -Most IA-64 boxes ship with a default console setting of 9600 baud. -This setting is rather slow, and the normal installation process -will take a significant time to draw each screen. You should consider -either increasing the baud rate used for performing the installation, -or performing a Text Mode installation. See the <classname>Params</classname> -help menu for instructions on starting the installer in Text Mode. -</para></note> - -<warning><para> -If you select the wrong console type, you -will be able to select the kernel and enter parameters but both -the display and your input will go dead as soon as the kernel starts, -requiring you to reboot before you can begin the installation. -</para></warning> - </sect3> - - <sect3 arch="ia64" id="kernel-option-menu"> - <title>Selecting the Boot Kernel and Options</title> - -<para> - -The boot loader will display a form with a menu list and a text -window with a <classname>Boot:</classname> prompt. -The arrow keys select an item from the menu and any text typed -at the keyboard will appear in the text window. -There are also help screens which can be displayed by pressing -the appropriate function key. -The <classname>General</classname> help screen explains the menu -choices and the <classname>Params</classname> screen explains -the common command line options. - -</para><para> - -Consult the <classname>General</classname> help screen for the -description of the kernels and install modes most appropriate -for your installation. -You should also consult <xref linkend="boot-parms"/> below for any additional -parameters that you may want to set in the <classname>Boot:</classname> -text window. -The kernel version you choose selects the kernel version that will be -used for both the installation process and the installed system. -If you encounter kernel problems with the installation, you may also -have those same problems with the system you install. -The following two steps will select and start the install: - -</para> - -<itemizedlist> - -<listitem><para> -Select the kernel version and installation mode most -appropriate to your needs with the arrow keys. -</para></listitem> - -<listitem><para> -Enter any boot parameters by typing at the keyboard. -The text will be displayed directly in the text window. -This is where kernel parameters (such as serial console -settings) are specified. -</para></listitem> - -<listitem><para> -Press <command>ENTER</command>. This will load and start the -kernel. -The kernel will display its usual initialization messages followed -by the first screen of the &debian; Installer. -</para></listitem> - -</itemizedlist> - -<para> - -Proceed to the next chapter to continue the installation where you will -set up the language locale, network, and disk partitions. - -</para> - </sect3> - </sect2> - - <sect2 arch="ia64" id="boot-tftp"><title>Booting with TFTP</title> - -<para> -Booting an IA-64 system from the network is similar to a CD boot. -The only difference is how the installation kernel is loaded. -The EFI Boot Manager can load and start programs from a server on -the network. -Once the installation kernel is loaded and starts, the system install -will proceed through the same steps as the CD install with the exception -that the packages of the base install will be loaded from the network -rather than the CD drive. - -</para> - -&boot-installer-intro-net.xml; - -<para> - -Network booting an IA-64 system requires two architecture-specific actions. -On the boot server, DHCP and TFTP must be configured to deliver -<command>elilo</command>. -On the client a new boot option must be defined in the EFI boot manager -to enable loading over a network. - -</para> - - <sect3 arch="ia64" id="boot-tftp-server"> - <title>Configuring the Server</title> -<para> - -A suitable TFTP entry for network booting an IA-64 system looks something -like this: - -<informalexample><screen> -host mcmuffin { - hardware ethernet 00:30:6e:1e:0e:83; - fixed-address 10.0.0.21; - filename "debian-installer/ia64/elilo.efi"; -} -</screen></informalexample> - -Note that the goal is to get <command>elilo.efi</command> running on -the client. - -</para><para> - -Extract the <filename>netboot.tar.gz</filename> file into the directory used -as the root for your tftp server. Typical tftp root directories include -<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. -This will create a <filename>debian-installer</filename> directory -tree containing the boot files for an IA-64 system. - -</para><para> - -<informalexample><screen> -# cd /var/lib/tftp -# tar xvfz /home/user/netboot.tar.gz -./ -./debian-installer/ -./debian-installer/ia64/ -[...] -</screen></informalexample> - -The <filename>netboot.tar.gz</filename> contains an -<filename>elilo.conf</filename> file that should work for most configurations. -However, should you need to make changes to this file, you can find it in the -<filename>debian-installer/ia64/</filename> directory. - -It is possible to have different config files for different clients by naming -them using the client's IP address in hex with the suffix -<filename>.conf</filename> instead of <filename>elilo.conf</filename>. -See documentation provided in the <classname>elilo</classname> package -for details. - -</para> - </sect3> - - <sect3 arch="ia64" id="boot-tftp-client"> - <title>Configuring the Client</title> -<para> - -To configure the client to support TFTP booting, start by booting to -EFI and entering the <guimenu>Boot Option Maintenance Menu</guimenu>. - -<itemizedlist> -<listitem><para> - -Add a boot option. - -</para></listitem> -<listitem><para> - -You should see one or more lines with the text -<guimenuitem>Load File [Acpi()/.../Mac()]</guimenuitem>. If more -than one of these entries exist, choose the one containing the -MAC address of the interface from which you'll be booting. -Use the arrow keys to highlight your choice, then press enter. - -</para></listitem> -<listitem><para> - -Name the entry <userinput>Netboot</userinput> or something similar, -save, and exit back to the boot options menu. - -</para></listitem> -</itemizedlist> - -You should see the new boot option you just created, and selecting it -should initiate a DHCP query, leading to a TFTP load of -<filename>elilo.efi</filename> from the server. - -</para><para> - -The boot loader will display its prompt after it has downloaded and -processed its configuration file. -At this point, the installation proceeds with the same steps as a -CD install. Select a boot option as in above and when the kernel -has completed installing itself from the network, it will start the -&debian; Installer. - -</para><para> - -Proceed to the next chapter to continue the installation where -you will set up the language locale, network, and disk partitions. - -</para> - </sect3> - </sect2> diff --git a/nl/boot-installer/intro-cd.xml b/nl/boot-installer/intro-cd.xml deleted file mode 100644 index 4c00e2593..000000000 --- a/nl/boot-installer/intro-cd.xml +++ /dev/null @@ -1,35 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> - -<para> - -The easiest route for most people will be to use a set of &debian; CDs. -If you have a CD set, and if your machine supports booting directly off -the CD, great! Simply -<phrase arch="x86"> -configure your system for booting off a CD as described in -<xref linkend="boot-dev-select"/>, -</phrase> -insert your CD, reboot, and proceed to the next chapter. - -</para><para> - -Note that certain CD drives may require special drivers, and thus be -inaccessible in the early installation stages. If it turns out the -standard way of booting off a CD doesn't work for your hardware, -revisit this chapter and read about alternate kernels and installation -methods which may work for you. - -</para><para> - -Even if you cannot boot from CD-ROM, you can probably install the -&debian; system components and any packages you want from CD-ROM. -Simply boot using a different media, such as floppies. When it's -time to install the operating system, base system, and any additional -packages, point the installation system at the CD-ROM drive. - -</para><para> - -If you have problems booting, see <xref linkend="boot-troubleshooting"/>. - -</para> diff --git a/nl/boot-installer/intro-firmware.xml b/nl/boot-installer/intro-firmware.xml deleted file mode 100644 index fe869608e..000000000 --- a/nl/boot-installer/intro-firmware.xml +++ /dev/null @@ -1,18 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 35309 untranslated --> - -<para> - -There is an increasing number of consumer devices that directly boot from a -flash chip on the device. The installer can be written to flash so it will -automatically start when you reboot your machines. - -</para><note><para> - -In many cases, changing the firmware of an embedded device voids your -warranty. Sometimes you are also not able to recover your device if there -are problems during the flashing process. Therefore, please take care and -follow the steps precisely. - -</para></note> - diff --git a/nl/boot-installer/intro-hd.xml b/nl/boot-installer/intro-hd.xml deleted file mode 100644 index 4df9f39b8..000000000 --- a/nl/boot-installer/intro-hd.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61184 untranslated --> - -<para> - -Booting from an existing operating system is often a convenient -option; for some systems it is the only supported method of -installation. - -</para><para> - -To boot the installer from hard disk, you will have already completed -downloading and placing the needed files as described in -<xref linkend="boot-drive-files"/>. - -</para> diff --git a/nl/boot-installer/intro-net.xml b/nl/boot-installer/intro-net.xml deleted file mode 100644 index 79189195c..000000000 --- a/nl/boot-installer/intro-net.xml +++ /dev/null @@ -1,19 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - -<para> - -Booting from the network requires that you have a network -connection and a TFTP network boot server (DHCP, RARP, or BOOTP). - -</para><para arch="hppa"> - -Older systems such as the 715 might require the use of an RBOOT server -instead of a BOOTP server. - -</para><para> - -The installation method to support network booting is described in <xref -linkend="install-tftp"/>. - -</para>
\ No newline at end of file diff --git a/nl/boot-installer/mips.xml b/nl/boot-installer/mips.xml deleted file mode 100644 index d1ef4d252..000000000 --- a/nl/boot-installer/mips.xml +++ /dev/null @@ -1,61 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59840 untranslated --> - - - <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title> - - <sect3> - <title>SGI TFTP Booting</title> -<para> - -After entering the command monitor use - -<informalexample><screen> -bootp(): -</screen></informalexample> - -on SGI machines to boot linux and to begin installation of the &debian; -Software. In order to make this -work you may have to unset the <envar>netaddr</envar> environment -variable. Type - -<informalexample><screen> -unsetenv netaddr -</screen></informalexample> - -in the command monitor to do this. - -</para> - </sect3> - - </sect2> - - <sect2 arch="mips"><title>Boot Parameters</title> - - <sect3> - <title>SGI TFTP Booting</title> -<para> - -On SGI machines you can append boot parameters to the -<command>bootp():</command> command in the command monitor. - -</para><para> - -Following the <command>bootp():</command> command you can give the -path and name of the file to boot if you did not give an explicit name -via your bootp/dhcp server. Example: - -<informalexample><screen> -bootp():/boot/tftpboot.img -</screen></informalexample> - -Further kernel parameters can be passed via <command>append</command>: - -<informalexample><screen> -bootp(): append="root=/dev/sda1" -</screen></informalexample> - -</para> - </sect3> - - </sect2> diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml deleted file mode 100644 index 7680c9cdb..000000000 --- a/nl/boot-installer/mipsel.xml +++ /dev/null @@ -1,54 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59840 untranslated --> - - <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title> - - <sect3> - <title>Cobalt TFTP Booting</title> -<para> - -Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to -install an NFS server and put the installer files in -<filename>/nfsroot</filename>. When you boot your Cobalt, you have to -press the left and the right cursor buttons at the same time and the -machine will boot via the network from NFS. It will then display several -options on the display. There are the following two installation methods: - -<itemizedlist> -<listitem><para> - -Via SSH (default): In this case, the installer will configure the network -via DHCP and start an SSH server. It will then display a random password -and other login information (such as the IP address) on the Cobalt LCD. -When you connect to the machine with an SSH client you can start with -the installation. - -</para></listitem> -<listitem><para> - -Via serial console: Using a null modem cable, you can connect to the serial -port of your Cobalt machine (using 115200 bps) and perform the installation -this way. - -</para></listitem> -</itemizedlist> - -</para> - </sect3> - - </sect2> - - <sect2 arch="mipsel"><title>Boot Parameters</title> - - <sect3> - <title>Cobalt TFTP Booting</title> -<para> - -You cannot pass any boot parameters directly. Instead, you have to edit -the <filename>/nfsroot/default.colo</filename> file on the NFS server and -add your parameters to the <replaceable>args</replaceable> variable. - -</para> - </sect3> - - </sect2> diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml deleted file mode 100644 index 545d1a5f4..000000000 --- a/nl/boot-installer/parameters.xml +++ /dev/null @@ -1,678 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62899 untranslated --> - - <sect1 id="boot-parms"><title>Boot Parameters</title> -<para arch="linux-any"> - -Boot parameters are Linux kernel parameters which are generally used -to make sure that peripherals are dealt with properly. For the most -part, the kernel can auto-detect information about your peripherals. -However, in some cases you'll have to help the kernel a bit. - -</para><para> - -If this is the first time you're booting the system, try the default -boot parameters (i.e., don't try setting parameters) and see if it works -correctly. It probably will. If not, you can reboot later and look for -any special parameters that inform the system about your hardware. - -</para><para arch="linux-any"> - -Information on many boot parameters can be found in the -<ulink url="http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html"> Linux -BootPrompt HOWTO</ulink>, including tips for obscure hardware. This -section contains only a sketch of the most salient parameters. Some -common gotchas are included below in -<xref linkend="boot-troubleshooting"/>. - -</para><para arch="linux-any"> - -When the kernel boots, a message - -<informalexample><screen> -Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k available -</screen></informalexample> - -should be emitted early in the process. -<replaceable>total</replaceable> should match the total amount of RAM, -in kilobytes. If this doesn't match the actual amount of RAM you have -installed, you need to use the -<userinput>mem=<replaceable>ram</replaceable></userinput> parameter, -where <replaceable>ram</replaceable> is set to the amount of memory, -suffixed with <quote>k</quote> for kilobytes, or <quote>m</quote> for -megabytes. For example, both <userinput>mem=65536k</userinput> and -<userinput>mem=64m</userinput> mean 64MB of RAM. - -</para><para arch="linux-any" condition="supports-serial-console"> - -If you are booting with a serial console, generally the kernel will -autodetect this. -If you have a videocard (framebuffer) and a keyboard also attached to -the computer which you wish to boot via serial console, you may have -to pass the -<userinput>console=<replaceable>device</replaceable></userinput> -argument to the kernel, where <replaceable>device</replaceable> is -your serial device, which is usually something like -<filename>ttyS0</filename><footnote> - -<para> -In order to ensure the terminal type used by the installer matches your -terminal emulator, the parameter -<userinput>TERM=<replaceable>type</replaceable></userinput> can be added. -Note that the installer only supports the following terminal types: -<literal>linux</literal>, <literal>bterm</literal>, <literal>ansi</literal>, -<literal>vt102</literal> and <literal>dumb</literal>. The default for -serial console in &d-i; is <userinput>vt102</userinput>. -</para> - -</footnote>. - -</para><para arch="sparc"> - -For &arch-title; the serial devices are <filename>ttya</filename> or -<filename>ttyb</filename>. -Alternatively, set the <envar>input-device</envar> and -<envar>output-device</envar> OpenPROM variables to -<filename>ttya</filename>. - -</para> - - - <sect2 id="installer-args"><title>&debian; Installer Parameters</title> -<para> - -The installation system recognizes a few additional boot parameters<footnote> - -<para> - -With current kernels (2.6.9 or newer) you can use 32 command line options and -32 environment options. If these numbers are exceeded, the kernel will panic. - -</para> - -</footnote> which may be useful. - -</para><para> - -A number of parameters have a <quote>short form</quote> that helps avoid -the limitations of the kernel command line options and makes entering the -parameters easier. If a parameter has a short form, it will be listed in -brackets behind the (normal) long form. Examples in this manual will -normally use the short form too. - -</para> - -<variablelist> -<varlistentry> -<term>debconf/priority (priority)</term> -<listitem><para> - -This parameter sets the lowest priority of messages to be displayed. - -</para><para> - -The default installation uses <userinput>priority=high</userinput>. -This means that both high and critical priority messages are shown, but medium -and low priority messages are skipped. -If problems are encountered, the installer adjusts the priority as needed. - -</para><para> - -If you add <userinput>priority=medium</userinput> as boot parameter, you -will be shown the installation menu and gain more control over the installation. -When <userinput>priority=low</userinput> is used, all messages are shown -(this is equivalent to the <emphasis>expert</emphasis> boot method). -With <userinput>priority=critical</userinput>, the installation system -will display only critical messages and try to do the right thing without fuss. - -</para></listitem> -</varlistentry> - - -<varlistentry> -<term>DEBIAN_FRONTEND</term> -<listitem><para> - -This boot parameter controls the type of user interface used for the -installer. The current possible parameter settings are: - -<itemizedlist> -<listitem> -<para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></para> -</listitem><listitem> -<para><userinput>DEBIAN_FRONTEND=text</userinput></para> -</listitem><listitem> -<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> -</listitem><listitem> -<para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> -</listitem> -</itemizedlist> - -The default frontend is <userinput>DEBIAN_FRONTEND=newt</userinput>. -<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for -serial console installs. Generally, only the -<userinput>newt</userinput> frontend is available on default install -media. On architectures that support it, the graphical installer uses -the <userinput>gtk</userinput> frontend. - -</para></listitem> -</varlistentry> - - -<varlistentry> -<term>BOOT_DEBUG</term> -<listitem><para> - -Setting this boot parameter to 2 will cause the installer's boot process -to be verbosely logged. Setting it to 3 makes debug shells -available at strategic points in the boot process. (Exit the shells to -continue the boot process.) - -<variablelist> -<varlistentry> -<term><userinput>BOOT_DEBUG=0</userinput></term> -<listitem><para>This is the default.</para></listitem> -</varlistentry> - -<varlistentry> -<term><userinput>BOOT_DEBUG=1</userinput></term> -<listitem><para>More verbose than usual.</para></listitem> -</varlistentry> - -<varlistentry> -<term><userinput>BOOT_DEBUG=2</userinput></term> -<listitem><para>Lots of debugging information.</para></listitem> -</varlistentry> - -<varlistentry> -<term><userinput>BOOT_DEBUG=3</userinput></term> -<listitem><para> - -Shells are run at various points in the boot process to allow detailed -debugging. Exit the shell to continue the boot. - -</para></listitem> -</varlistentry> -</variablelist> - -</para></listitem> -</varlistentry> - - -<varlistentry> -<term>INSTALL_MEDIA_DEV</term> -<listitem><para> - -The value of the parameter is the path to the device to load the -&debian; installer from. For example, -<userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</userinput> - -</para><para> - -The boot floppy, which normally scans all floppies it can to find the -root floppy, can be overridden by this parameter to only look at the -one device. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>lowmem</term> -<listitem><para> - -Can be used to force the installer to a lowmem level higher than the one -the installer sets by default based on available memory. Possible values -are 1 and 2. See also <xref linkend="lowmem"/>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>noshell</term> -<listitem><para> - -Prevents the installer from offering interactive shells on tty2 and tty3. -Useful for unattended installations where physical security is limited. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>debian-installer/framebuffer (fb)</term> -<listitem><para> - -Some architectures use the kernel framebuffer to offer installation in -a number of languages. If framebuffer causes a problem on your system -you can disable the feature using the parameter -<userinput arch="x86">vga=normal</userinput> <userinput>fb=false</userinput>. -Problem symptoms are error messages about bterm or bogl, a blank screen, -or a freeze within a few minutes after starting the install. - -</para><para arch="hppa"> - -Such problems have been reported on hppa. - -</para><note arch="sparc"><para> - -Because of display problems on some systems, framebuffer support is -<emphasis>disabled by default</emphasis> for &arch-title;. This can result -in ugly display on systems that do properly support the framebuffer, like -those with ATI graphical cards. -If you see display problems in the installer, you can try booting with -parameter <userinput>debian-installer/framebuffer=true</userinput> or -<userinput>fb=true</userinput> for short. - -</para></note></listitem> -</varlistentry> - -<varlistentry arch="not-s390"> -<term>debian-installer/theme (theme)</term> -<listitem><para> - -A theme determines how the user interface of the installer looks (colors, -icons, etc.). What themes are available differs per frontend. Currently -both the newt and gtk frontends only have a <quote>dark</quote> theme that was -designed for visually impaired users. Set the theme by booting with -<userinput>theme=<replaceable>dark</replaceable></userinput>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>netcfg/disable_dhcp</term> -<listitem><para> - -By default, the &d-i; automatically probes for network configuration -via DHCP. If the probe succeeds, you won't have a chance to review and -change the obtained settings. You can get to the manual network setup -only in case the DHCP probe fails. - -</para><para> - -If you have a DHCP server on your local network, but want to avoid it -because e.g. it gives wrong answers, you can use the parameter -<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring -the network with DHCP and to enter the information manually. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>hw-detect/start_pcmcia</term> -<listitem><para> - -Set to <userinput>false</userinput> to prevent starting PCMCIA -services, if that causes problems. Some laptops are well known for -this misbehavior. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>disk-detect/dmraid/enable (dmraid)</term> -<listitem><para> - -Set to <userinput>true</userinput> to enable support for Serial ATA RAID -(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. -Note that this support is currently experimental. Additional information -can be found on the <ulink url="&url-d-i-wiki;">Debian Installer Wiki</ulink>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>preseed/url (url)</term> -<listitem><para> - -Specify the url to a preconfiguration file to download and use for -automating the install. See <xref linkend="automatic-install"/>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>preseed/file (file)</term> -<listitem><para> - -Specify the path to a preconfiguration file to load for -automating the install. See <xref linkend="automatic-install"/>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>preseed/interactive</term> -<listitem><para> - -Set to <userinput>true</userinput> to display questions even if they have -been preseeded. Can be useful for testing or debugging a preconfiguration -file. Note that this will have no effect on parameters that are passed as -boot parameters, but for those a special syntax can be used. -See <xref linkend="preseed-seenflag"/> for details. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>auto-install/enable (auto)</term> -<listitem><para> - -Delay questions that are normally asked before preseeding is possible until -after the network is configured. -See <xref linkend="preseed-auto"/> for details about using this to -automate installs. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>finish-install/keep-consoles</term> -<listitem><para> - -During installations from serial or management console, the regular -virtual consoles (VT1 to VT6) are normally disabled in -<filename>/etc/inittab</filename>. -Set to <userinput>true</userinput> to prevent this. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>cdrom-detect/eject</term> -<listitem><para> - -By default, before rebooting, &d-i; automatically ejects the optical -media used during the installation. This can be unnecessary if the system -does not automatically boot off the CD. In some cases it may even be -undesirable, for example if the optical drive cannot reinsert the media -itself and the user is not there to do it manually. Many slot loading, -slim-line, and caddy style drives cannot reload media automatically. - -</para><para> - -Set to <userinput>false</userinput> to disable automatic ejection, and -be aware that you may need to ensure that the system does not -automatically boot from the optical drive after the initial -installation. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>base-installer/install-recommends (recommends)</term> -<listitem><para> - -By setting this option to <userinput>false</userinput>, the package -management system will be configured to not automatically install -<quote>Recommends</quote>, both during the installation and for the -installed system. See also <xref linkend="di-install-base"/>. - -</para><para> - -Note that this option allows to have a leaner system, but can also result -in features being missing that you might normally expect to be available. -You may have to manually install some of the recommended packages to -obtain the full functionality you want. This option should therefore only -be used by very experienced users. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>debian-installer/allow_unauthenticated</term> -<listitem><para> - -By default the installer requires that repositories be authenticated -using a known gpg key. Set to <userinput>true</userinput> to -disable that authentication. -<emphasis role="bold">Warning: insecure, not recommended.</emphasis> - -</para></listitem> -</varlistentry> - -<varlistentry arch="mips;mipsel"> -<term>ramdisk_size</term> -<listitem><para> - -This parameter should already be set to a correct value where needed; -set it only it you see errors during the boot that indicate the ramdisk -could not be loaded completely. The value is in kB. - -</para></listitem> -</varlistentry> - -<varlistentry condition="gtk"> -<term>mouse/protocol</term> -<listitem><para> - -For the gtk frontend (graphical installer), users can set the mouse -protocol to be used by setting this parameter. -Supported values are<footnote> - -<para> -See the man page for -<citerefentry><refentrytitle>directfbrc</refentrytitle> -<manvolnum>5</manvolnum></citerefentry> for additional information. -</para> - -</footnote>: -<userinput>PS/2</userinput>, <userinput>IMPS/2</userinput>, -<userinput>MS</userinput>, <userinput>MS3</userinput>, -<userinput>MouseMan</userinput> and <userinput>MouseSystems</userinput>. -In most cases the default protocol should work correctly. - -</para></listitem> -</varlistentry> - -<varlistentry condition="gtk"> -<term>mouse/device</term> -<listitem><para> - -For the gtk frontend (graphical installer), users can specify the mouse -device to be used by setting this parameter. This is mostly useful if the -mouse is connected to a serial port (serial mouse). Example: -<userinput>mouse/device=<replaceable>/dev/ttyS1</replaceable></userinput>. - -</para></listitem> -</varlistentry> - -<varlistentry condition="gtk"> -<term>mouse/left</term> -<listitem><para> - -For the gtk frontend (graphical installer), users can switch the mouse to -left-handed operation by setting this parameter to <userinput>true</userinput>. - -</para></listitem> -</varlistentry> - -<varlistentry condition="gtk"> -<term>directfb/hw-accel</term> -<listitem><para> - -For the gtk frontend (graphical installer), hardware acceleration in directfb -is disabled by default. Set this parameter to <userinput>true</userinput> to -enable it. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>rescue/enable</term> -<listitem><para> - -Set to <userinput>true</userinput> to enter rescue mode rather than -performing a normal installation. See <xref linkend="rescue"/>. - -</para></listitem> -</varlistentry> - -</variablelist> - - </sect2> - - <sect2 id="preseed-args"> - <title>Using boot parameters to answer questions</title> -<para> - -With some exceptions, a value can be set at the boot prompt for any question -asked during the installation, though this is only really useful in specific -cases. General instructions how to do this can be found in -<xref linkend="preseed-bootparms"/>. Some specific examples are listed below. - -</para> - -<variablelist> - -<varlistentry> -<term>debian-installer/language (language)</term> -<term>debian-installer/country (country)</term> -<term>debian-installer/locale (locale)</term> -<listitem><para> - -There are two ways to specify the language, country and locale to use for -the installation and the installed system. - -</para><para> - -The first and easiest is to pass only the parameter <literal>locale</literal>. -Language and country will then be derived from its value. You can for example -use <userinput>locale=de_CH</userinput> to select German as language and -Switzerland as country (<literal>de_CH.UTF-8</literal> will be set as default -locale for the installed system). Limitation is that not all possible -combinations of language, country and locale can be achieved this way. - -</para><para> - -The second, more flexible option is to specify <literal>language</literal> -and <literal>country</literal> separately. In this case -<literal>locale</literal> can optionally be added to specify a specific -default locale for the installed system. Example: -<userinput>language=en country=DE locale=en_GB.UTF-8</userinput>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>anna/choose_modules (modules)</term> -<listitem><para> - -Can be used to automatically load installer components that are not loaded -by default. -Examples of optional components that may be useful are -<classname>openssh-client-udeb</classname> (so you can use -<command>scp</command> during the installation)<phrase arch="not-s390"> and -<classname>ppp-udeb</classname> (see <xref linkend="pppoe"/>)</phrase>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>netcfg/disable_dhcp</term> -<listitem><para> - -Set to <userinput>true</userinput> if you want to disable DHCP and instead -force static network configuration. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>mirror/protocol (protocol)</term> -<listitem><para> - -By default the installer will use the http protocol to download files from -&debian; mirrors and changing that to ftp is not possible during installations -at normal priority. By setting this parameter to <userinput>ftp</userinput>, -you can force the installer to use that protocol instead. Note that you -cannot select an ftp mirror from a list, you have to enter the hostname -manually. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>tasksel:tasksel/first (tasks)</term> -<listitem><para> - -Can be used to select tasks that are not available from the interactive task -list, such as the <literal>kde-desktop</literal> task. -See <xref linkend="pkgsel"/> for additional information. - -</para></listitem> -</varlistentry> - -</variablelist> - - </sect2> - - <sect2 id="module-parms"> - <title>Passing parameters to kernel modules</title> -<para> - -If drivers are compiled into the kernel, you can pass parameters to them -as described in the kernel documentation. However, if drivers are compiled -as modules and because kernel modules are loaded a bit differently during -an installation than when booting an installed system, it is not possible -to pass parameters to modules as you would normally do. Instead, you need -to use a special syntax recognized by the installer which will then make -sure that the parameters are saved in the proper configuration files and -will thus be used when the modules are actually loaded. The parameters -will also be propagated automatically to the configuration for the installed -system. - -</para><para> - -Note that it is now quite rare that parameters need to be passed to modules. -In most cases the kernel will be able to probe the hardware present in a -system and set good defaults that way. However, in some situations it may -still be needed to set parameters manually. - -</para><para> - -The syntax to use to set parameters for modules is: - -<informalexample><screen> -<replaceable>module_name</replaceable>.<replaceable>parameter_name</replaceable>=<replaceable>value</replaceable> -</screen></informalexample> - -If you need to pass multiple parameters to the same or different modules, -just repeat this. For example, to set an old 3Com network interface card -to use the BNC (coax) connector and IRQ 10, you would pass: - -<informalexample><screen> -3c509.xcvr=3 3c509.irq=10 -</screen></informalexample> - -</para> - </sect2> - - <sect2 id="module-blacklist"> - <title>Blacklisting kernel modules</title> -<para> - -Sometimes it may be necessary to blacklist a module to prevent it from -being loaded automatically by the kernel and udev. One reason could be that -a particular module causes problems with your hardware. The kernel also -sometimes lists two different drivers for the same device. This can cause -the device to not work correctly if the drivers conflict or if the wrong -driver is loaded first. - -</para><para> - -You can blacklist a module using the following syntax: -<userinput><replaceable>module_name</replaceable>.blacklist=yes</userinput>. -This will cause the module to be blacklisted in -<filename>/etc/modprobe.d/blacklist.local</filename> both during the -installation and for the installed system. - -</para><para> - -Note that a module may still be loaded by the installation system itself. -You can prevent that from happening by running the installation in expert -mode and unselecting the module from the list of modules displayed during -the hardware detection phases. - -</para> - </sect2> - </sect1> diff --git a/nl/boot-installer/powerpc.xml b/nl/boot-installer/powerpc.xml deleted file mode 100644 index c11cbc4ba..000000000 --- a/nl/boot-installer/powerpc.xml +++ /dev/null @@ -1,262 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56248 untranslated --> - - <sect2 arch="powerpc" id="boot-cd"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - -<para> - -Currently, the only &arch-title; subarchitectures that support CD-ROM -booting are PReP (though not all systems) and New World PowerMacs. -On PowerMacs, hold the <keycap>c</keycap> key, or else the combination of -<keycap>Command</keycap>, <keycap>Option</keycap>, -<keycap>Shift</keycap>, and <keycap>Delete</keycap> -keys together while booting to boot from the CD-ROM. - -</para><para> - -OldWorld PowerMacs will not boot a &debian; CD, because OldWorld -computers relied on a Mac OS ROM CD boot driver to be present on the CD, -and a free-software version of this driver is not available. All -OldWorld systems have floppy drives, so use the floppy drive to launch -the installer, and then point the installer to the CD for the needed -files. - -</para><para> - -If your system doesn't boot directly from CD-ROM, you can still use -the CD-ROM to install the system. On NewWorlds, you can also use an -OpenFirmware command to boot from the CD-ROM manually. Follow the -instructions in <xref linkend="boot-newworld"/> for booting from -the hard disk, except use the path to <command>yaboot</command> on the -CD at the OF prompt, such as - -<informalexample><screen> -0 > boot cd:,\install\yaboot -</screen></informalexample> - -</para> - </sect2> - - <sect2 arch="powerpc" id="install-drive"> - <title>Booting from Hard Disk</title> - -&boot-installer-intro-hd.xml; - -<!-- - <sect3><title>Booting CHRP from OpenFirmware</title> - -<para> - - <emphasis>Not yet written.</emphasis> - -</para> - </sect3> ---> - - <sect3><title>Booting OldWorld PowerMacs from MacOS</title> -<para> - -If you set up BootX in <xref linkend="files-oldworld"/>, you can -use it to boot into the installation system. Double click the -<guiicon>BootX</guiicon> application icon. Click on the -<guibutton>Options</guibutton> button and select <guilabel>Use -Specified RAM Disk</guilabel>. This will give you the -chance to select the <filename>ramdisk.image.gz</filename> file. You -may need to select the <guilabel>No Video Driver</guilabel> checkbox, -depending on your hardware. Then click the -<guibutton>Linux</guibutton> button to shut down MacOS and launch the -installer. - -</para> - </sect3> - - - <sect3 id="boot-newworld"> - <title>Booting NewWorld Macs from OpenFirmware</title> -<para> - -You will have already placed the <filename>vmlinux</filename>, -<filename>initrd.gz</filename>, <filename>yaboot</filename>, and -<filename>yaboot.conf</filename> files at the root level of your HFS -partition in <xref linkend="files-newworld"/>. -You will now have to boot into OpenFirmware (see <xref linkend="invoking-openfirmware"/>). -At the prompt, type - -<informalexample><screen> -0 > boot hd:<replaceable>x</replaceable>,yaboot -</screen></informalexample> - -replacing <replaceable>x</replaceable> with the partition number of -the HFS partition where the -kernel and yaboot files were placed, followed by a &enterkey;. On some -machines, you may need to use <userinput>ide0:</userinput> instead of -<userinput>hd:</userinput>. In a few more seconds you will see a -yaboot prompt - -<informalexample><screen> -boot: -</screen></informalexample> - -At yaboot's <prompt>boot:</prompt> prompt, type either -<userinput>install</userinput> or <userinput>install video=ofonly</userinput> -followed by a &enterkey;. The -<userinput>video=ofonly</userinput> argument is for maximum -compatibility; you can try it if <userinput>install</userinput> -doesn't work. The &debian; installation program should start. - -</para> - </sect3> - </sect2> - - <sect2 arch="powerpc" condition="bootable-usb" id="usb-boot"> - <title>Booting from USB memory stick</title> -<para> - -Currently, NewWorld PowerMac systems are known to support USB booting. - -</para> - -<para> - -Make sure you have prepared everything from <xref -linkend="boot-usb-files"/>. To boot a Macintosh system from a USB stick, -you will need to use the Open Firmware prompt, since Open Firmware does -not search USB storage devices by default. -<!-- TODO: although it could be made to; watch this space --> -See <xref linkend="invoking-openfirmware"/>. - -</para><para> - -You will need to work out where the USB storage device appears in the -device tree, since at the moment <command>ofpath</command> cannot work -that out automatically. Type <userinput>dev / ls</userinput> and -<userinput>devalias</userinput> at the Open Firmware prompt to get a -list of all known devices and device aliases. On the author's system -with various types of USB stick, paths such as -<filename>usb0/disk</filename>, <filename>usb0/hub/disk</filename>, -<filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and -<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work. - -</para><para> - -Having worked out the device path, use a command like this to boot the -installer: - -<informalexample><screen> -boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\:tbxi -</screen></informalexample> - -The <replaceable>2</replaceable> matches the Apple_HFS or -Apple_Bootstrap partition onto which you copied the boot image earlier, -and the <userinput>,\\:tbxi</userinput> part instructs Open Firmware to -boot from the file with an HFS file type of "tbxi" (i.e. -<command>yaboot</command>) in the directory previously blessed with -<command>hattrib -b</command>. - -</para><para> - -The system should now boot up, and you should be presented with the -<prompt>boot:</prompt> prompt. Here you can enter optional boot -arguments, or just hit &enterkey;. - -</para><warning><para> - -This boot method is new, and may be difficult to get to work on some -NewWorld systems. If you have problems, please file an installation -report, as explained in <xref linkend="submit-bug"/>. - -</para></warning> - </sect2> - - <sect2 arch="powerpc" id="boot-tftp"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - -<para> - -Currently, PReP and New World PowerMac systems support netbooting. - -</para><para> - -On machines with Open Firmware, such as NewWorld Power Macs, enter the -boot monitor (see <xref linkend="invoking-openfirmware"/>) and -use the command - -<informalexample><screen> -0 > boot enet:0 -</screen></informalexample> - -If this doesn't work, you might have to add the filename like this: - -<informalexample><screen> -0 > boot enet:0,yaboot -</screen></informalexample> - -PReP and CHRP boxes -may have different ways of addressing the network. On a PReP machine, -you should try - -<informalexample><screen> -boot net:<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable> -</screen></informalexample> - -On some PReP systems (e.g. Motorola PowerStack machines) the command -<userinput>help boot</userinput> may give a description of syntax and -available options. - -</para> - </sect2> - - - <sect2 arch="powerpc" condition="supports-floppy-boot"> - <title>Booting from Floppies</title> -<para> - -Booting from floppies is supported for &arch-title;, although it is -generally only applicable for OldWorld systems. NewWorld systems are -not equipped with floppy drives, and attached USB floppy drives are -not supported for booting. - -</para><para> - -You will have already downloaded the floppy images you needed and -created floppies from the images in <xref linkend="create-floppy"/>. - -</para><para> - -To boot from the <filename>boot-floppy-hfs.img</filename> floppy, -place it in floppy drive after shutting the system down, and before -pressing the power-on button. - -</para><note><para> -For those not familiar with Macintosh -floppy operations: a floppy placed in the machine prior to boot will -be the first priority for the system to boot from. A floppy without a -valid boot system will be ejected, and the machine will then check for -bootable hard disk partitions. - -</para></note><para> - -After booting, the <filename>root.bin</filename> floppy is -requested. Insert the root floppy and press &enterkey;. The installer -program is automatically launched after the root system has been -loaded into memory. - -</para> - </sect2> - - - <sect2 arch="powerpc"><title>PowerPC Boot Parameters</title> -<para> - -Many older Apple monitors used a 640x480 67Hz mode. If your video -appears skewed on an older Apple monitor, try appending the boot -argument <userinput>video=atyfb:vmode:6</userinput> , which will -select that mode for most Mach64 and Rage video hardware. For Rage 128 -hardware, this changes to -<userinput>video=aty128fb:vmode:6</userinput> . - -</para> - </sect2> diff --git a/nl/boot-installer/s390.xml b/nl/boot-installer/s390.xml deleted file mode 100644 index f7991b127..000000000 --- a/nl/boot-installer/s390.xml +++ /dev/null @@ -1,36 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43745 untranslated --> - - <sect2 arch="s390"><title>s390 Limitations</title> -<para> - -In order to run the installation system a working network setup and -ssh session is needed on S/390. - -</para><para> - -The booting process starts with a network setup that prompts you for -several network parameters. If the setup is successful, you will login -to the system by starting an ssh session which will launch the -standard installation system. - -</para> - </sect2> - - - <sect2 arch="s390"><title>s390 Boot Parameters</title> -<para> - -On S/390 you can append boot parameters in the parm file. This file can -either be in ASCII or EBCDIC format. -A sample parm file <filename>parmfile.debian</filename> is provided with -the installation images. - -<!-- Link is bad; commented out for now -Please read -<ulink url="&url-s390-devices;">Device Drivers and Installation Commands</ulink> -for more information about S/390-specific boot parameters. ---> - -</para> - </sect2> diff --git a/nl/boot-installer/sparc.xml b/nl/boot-installer/sparc.xml deleted file mode 100644 index faf39b310..000000000 --- a/nl/boot-installer/sparc.xml +++ /dev/null @@ -1,46 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 58021 untranslated --> - - <sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - -<para> - -On machines with OpenBoot, simply enter the boot monitor on the -machine which is being installed (see -<xref linkend="invoking-openboot"/>). -Use the command <userinput>boot net</userinput> to boot from a TFTP -and RARP server, or try <userinput>boot net:bootp</userinput> or -<userinput>boot net:dhcp</userinput> to boot from a TFTP and BOOTP -or DHCP server. You can pass extra boot parameters to &d-i; at the end -of the <userinput>boot</userinput> command. - -</para> - </sect2> - - - <sect2 arch="sparc"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - -<para> - -Most OpenBoot versions support the <userinput>boot cdrom</userinput> -command which is simply an alias to boot from the SCSI device on ID 6 -(or the secondary master for IDE based systems). - -</para> - </sect2> - - <sect2 arch="sparc"><title>IDPROM Messages</title> -<para> - -If you cannot boot because you get messages about a problem with -<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which -holds configuration information for you firmware, has run out. See the -<ulink url="&url-sun-nvram-faq;">Sun NVRAM FAQ</ulink> for more -information. - -</para> - </sect2> diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml deleted file mode 100644 index 392e7f1f0..000000000 --- a/nl/boot-installer/trouble.xml +++ /dev/null @@ -1,572 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56669 untranslated --> - - <sect1 id="boot-troubleshooting"> - <title>Troubleshooting the Installation Process</title> -<para> -</para> - - <sect2 arch="not-s390" id="unreliable-cd"> - <title>CD-ROM Reliability</title> -<para> - -Sometimes, especially with older CD-ROM drives, the installer may fail -to boot from a CD-ROM. The installer may also — even after booting -successfully from CD-ROM — fail to recognize the CD-ROM or return -errors while reading from it during the installation. - -</para><para> - -There are many different possible causes for these problems. We can -only list some common issues and provide general suggestions on how to -deal with them. The rest is up to you. - -</para><para> - -There are two very simple things that you should try first. - -<itemizedlist> -<listitem><para> - -If the CD-ROM does not boot, check that it was inserted correctly and that -it is not dirty. - -</para></listitem> -<listitem><para> - -If the installer fails to recognize a CD-ROM, try just running the option -<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice> -a second time. Some DMA related issues with older CD-ROM drives are known to -be resolved in this way. - -</para></listitem> -</itemizedlist> - -</para><para> - -If this does not work, then try the suggestions in the subsections below. -Most, but not all, suggestions discussed there are valid for both CD-ROM and -DVD, but we'll use the term CD-ROM for simplicity. - -</para><para> - -If you cannot get the installation working from CD-ROM, try one of the -other installation methods that are available. - -</para> - - <sect3> - <title>Common issues</title> - -<itemizedlist> - <listitem><para> - -Some older CD-ROM drives do not support reading from discs that were burned -at high speeds using a modern CD writer. - - </para></listitem> - <listitem><para> - -If your system boots correctly from the CD-ROM, it does not necessarily -mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller -that your CD-ROM drive is connected to). - - </para></listitem> - <listitem><para> - -Some older CD-ROM drives do not work correctly if <quote>direct memory -access</quote> (DMA) is enabled. - - </para></listitem> -</itemizedlist> - - </sect3> - - <sect3> - <title>How to investigate and maybe solve issues</title> -<para> - -If the CD-ROM fails to boot, try the suggestions listed below. - -<itemizedlist> - <listitem><para> - -Check that your BIOS actually supports booting from CD-ROM (older systems -possibly don't) and that your CD-ROM drive supports the media you are using. - - </para></listitem> - <listitem><para> - -If you downloaded an iso image, check that the md5sum of that image matches -the one listed for the image in the <filename>MD5SUMS</filename> file that -should be present in the same location as where you downloaded the image -from. - -<informalexample><screen> -$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable> -a20391b12f7ff22ef705cee4059c6b92 <replaceable>debian-testing-i386-netinst.iso</replaceable> -</screen></informalexample> - -Next, check that the md5sum of the burned CD-ROM matches as well. The -following command should work. It uses the size of the image to read the -correct number of bytes from the CD-ROM. - -<informalexample><screen> -$ dd if=/dev/cdrom | \ -> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \ -> md5sum -a20391b12f7ff22ef705cee4059c6b92 - -262668+0 records in -262668+0 records out -134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s -</screen></informalexample> - - </para></listitem> -</itemizedlist> - -</para><para> - -If, after the installer has been booted successfully, the CD-ROM is not -detected, sometimes simply trying again may solve the problem. If you have -more than one CD-ROM drive, try changing the CD-ROM to the other drive. -If that does not work or if the CD-ROM is recognized but there are errors -when reading from it, try the suggestions listed below. Some basic knowledge -of &arch-kernel; is required for this. -To execute any of the commands, you should first switch to the second -virtual console (VT2) and activate the shell there. - -<itemizedlist> - <listitem><para> - -Switch to VT4 or view the contents of <filename>/var/log/syslog</filename> -(use <command>nano</command> as editor) to check for any specific error -messages. After that, also check the output of <command>dmesg</command>. - - </para></listitem> - <listitem><para> - -Check in the output of <command>dmesg</command> if your CD-ROM drive was -recognized. You should see something like (the lines do not necessarily -have to be consecutive): - -<informalexample><screen> -Probing IDE interface ide1... -hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive -ide1 at 0x170-0x177,0x376 on irq 15 -hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) -Uniform CD-ROM driver Revision: 3.20 -</screen></informalexample> - -If you don't see something like that, chances are the controller your CD-ROM -is connected to was not recognized or may be not supported at all. If you -know what driver is needed for the controller, you can try loading it manually -using <command>modprobe</command>. - - </para></listitem> - <listitem><para> - -Check that there is a device node for your CD-ROM drive under -<filename>/dev/</filename>. In the example above, this would be -<filename>/dev/hdc</filename>. -There should also be a <filename>/dev/cdrom</filename>. - - </para></listitem> - <listitem><para> - -Use the <command>mount</command> command to check if the CD-ROM is already -mounted; if not, try mounting it manually: - -<informalexample><screen> -$ mount /dev/<replaceable>hdc</replaceable> /cdrom -</screen></informalexample> - -Check if there are any error messages after that command. - - </para></listitem> - <listitem><para> - -Check if DMA is currently enabled: - -<informalexample><screen> -$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable> -$ grep using_dma settings -using_dma 1 0 1 rw -</screen></informalexample> - -A <quote>1</quote> in the first column after <literal>using_dma</literal> -means it is enabled. If it is, try disabling it: - -<informalexample><screen> -$ echo -n "using_dma:0" >settings -</screen></informalexample> - -Make sure that you are in the directory for the device that corresponds -to your CD-ROM drive. - - </para></listitem> - <listitem><para> - -If there are any problems during the installation, try checking the integrity -of the CD-ROM using the option near the bottom of the installer's main menu. -This option can also be used as a general test if the CD-ROM can be read -reliably. - - </para></listitem> -</itemizedlist> - -</para> - </sect3> - </sect2> - - <sect2 condition="supports-floppy-boot" id="unreliable-floppies"> - <title>Floppy Disk Reliability</title> - -<para> - -The biggest problem for people using floppy disks to install &debian; -seems to be floppy disk reliability. - -</para><para> - -The boot floppy is the floppy with the worst problems, because it -is read by the hardware directly, before Linux boots. Often, the -hardware doesn't read as reliably as the Linux floppy disk driver, and -may just stop without printing an error message if it reads incorrect -data. There can also be failures in the driver floppies, most of which -indicate themselves with a flood of messages about disk I/O errors. - -</para><para> - -If you are having the installation stall at a particular floppy, the first -thing you should do is write the image to a <emphasis>different</emphasis> -floppy and see if that solves the problem. Simply reformatting the old -floppy may not be sufficient, even if it appears that the floppy was -reformatted and written with no errors. It is sometimes useful to try -writing the floppy on a different system. - -</para><para> - -One user reports he had to write the images to floppy -<emphasis>three</emphasis> times before one worked, and then -everything was fine with the third floppy. - -</para><para> - -Normally you should not have to download a floppy image again, but if you -are experiencing problems it is always useful to verify that the images -were downloaded correctly by verifying their md5sums. - -</para><para> - -Other users have reported that simply rebooting a few times with the -same floppy in the floppy drive can lead to a successful boot. This is -all due to buggy hardware or firmware floppy drivers. - -</para> - </sect2> - - <sect2><title>Boot Configuration</title> - -<para> - -If you have problems and the kernel hangs during the boot process, -doesn't recognize peripherals you actually have, or drives are not -recognized properly, the first thing to check is the boot parameters, -as discussed in <xref linkend="boot-parms"/>. - -</para><para> - -Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. <phrase arch="any-x86">Internal modems, sound -cards, and Plug-n-Play devices can be especially problematic.</phrase> - -</para><para> - -If you have a large amount of memory installed in your machine, more -than 512M, and the installer hangs when booting the kernel, you may -need to include a boot argument to limit the amount of memory the -kernel sees, such as <userinput>mem=512m</userinput>. - -</para> - </sect2> - - <sect2 arch="x86" id="i386-boot-problems"> - <title>Common &arch-title; Installation Problems</title> -<para> - -There are some common installation problems that can be solved or avoided by -passing certain boot parameters to the installer. - -</para><para> - -Some systems have floppies with <quote>inverted DCLs</quote>. If you receive -errors reading from the floppy, even when you know the floppy is good, -try the parameter <userinput>floppy=thinkpad</userinput>. - -</para><para> - -On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 -disk drivers), the IDE drive may not be properly recognized. Again, -try it first without the parameters and see if the IDE drive is -recognized properly. If not, determine your drive geometry -(cylinders, heads, and sectors), and use the parameter -<userinput>hd=<replaceable>cylinders</replaceable>,<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></userinput>. - -</para><para> - -If you have a very old machine, and the kernel hangs after saying -<computeroutput>Checking 'hlt' instruction...</computeroutput>, then -you should try the <userinput>no-hlt</userinput> boot argument, which -disables this test. - -</para><para> - -Some systems (especially laptops) that have a native resolution that is not -a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank -display after the installer has been booted. In that case adding the boot -parameter <userinput>vga=788</userinput><footnote> - -<para> -The parameter <userinput>vga=788</userinput> will activate the VESA -framebuffer with a resolution of 800x600. This will probably work, but may -not be the optimal resolution for your system. A list of supported -resolutions can be obtained by using <userinput>vga=ask</userinput>, but -you should be aware that list may not be complete. -</para> - -</footnote> may help. If that does not work, -try adding the boot parameter <userinput>fb=false</userinput>. - -</para><para> - -If your screen begins to show a weird picture while the kernel boots, -eg. pure white, pure black or colored pixel garbage, your system may -contain a problematic video card which does not switch to the -framebuffer mode properly. Then you can use the boot parameter -<userinput>fb=false</userinput> to disable the framebuffer -console. Only a reduced set of -languages will be available during the installation due to limited -console features. See <xref linkend="boot-parms"/> for details. - -</para> - - <sect3> - <title>System Freeze During the PCMCIA Configuration Phase</title> -<para> - -Some laptop models produced by Dell are known to crash when PCMCIA device -detection tries to access some hardware addresses. Other laptops may display -similar problems. If you experience such a problem and you don't need PCMCIA -support during the installation, you can disable PCMCIA using the -<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can -then configure PCMCIA after the installation is completed and exclude the -resource range causing the problems. - -</para><para> - -Alternatively, you can boot the installer in expert mode. You will -then be asked to enter the resource range options your hardware -needs. For example, if you have one of the Dell laptops mentioned -above, you should enter <userinput>exclude port -0x800-0x8ff</userinput> here. There is also a list of some common -resource range options in the <ulink -url="http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12">System -resource settings section of the PCMCIA HOWTO</ulink>. Note that you -have to omit the commas, if any, when you enter this value in the -installer. - -</para> - </sect3> - - <sect3> - <title>System Freeze while Loading USB Modules</title> -<para> - -The kernel normally tries to install USB modules and the USB keyboard driver -in order to support some non-standard USB keyboards. However, there are some -broken USB systems where the driver hangs on loading. A possible workaround -may be disabling the USB controller in your mainboard BIOS setup. Another option -is passing the <userinput>nousb</userinput> parameter at the boot prompt. - -</para> - </sect3> - </sect2> - - <sect2 arch="sparc" id="sparc-boot-problems"> - <title>Common &arch-title; Installation Problems</title> -<para> - -There are some common installation problems that are worth mentioning. - -</para> - <sect3> - <title>Misdirected video output</title> -<para> - -It is fairly common for &arch-title; to have two video cards in one machine, -for example an ATI card and a Sun Creator 3D. In some cases, this may result -in the video output getting misdirected soon after the system boots. In -typical cases, the display will only show: - -<informalexample><screen> -Remapping the kernel... done -Booting Linux... -</screen></informalexample> - -To work around this, you can either pull out one of the video cards, or -disable the one not used during the OpenProm boot phase using a kernel -parameter. For example, to disable an ATI card, you should boot the -installer with <userinput>video=atyfb:off</userinput>. - -</para><para> - -Note that you may also have to manually add this parameter to the silo -configuration (edit <filename>/target/etc/silo.conf</filename> before -rebooting) and, if you installed X11, modify the video driver in -<filename>/etc/X11/xorg.conf</filename>. - -</para> - </sect3> - - <sect3> - <title>Failure to Boot or Install from CD-ROM</title> -<para> - -Some Sparc systems are notoriously difficult to boot from CD-ROM and -even if they do boot, there may be inexplicable failures during the -installation. Most problems have been reported with SunBlade systems. - -</para><para> - -We recommend to install such systems by netbooting the installer. - -</para> - </sect3> - </sect2> - - <sect2 id="kernel-msgs"> - <title>Interpreting the Kernel Startup Messages</title> - -<para> - -During the boot sequence, you may see many messages in the form -<computeroutput>can't find <replaceable>something</replaceable></computeroutput>, -or <computeroutput><replaceable>something</replaceable> -not present</computeroutput>, <computeroutput>can't initialize -<replaceable>something</replaceable></computeroutput>, -or even <computeroutput>this driver release depends -on <replaceable>something</replaceable></computeroutput>. -Most of these messages are harmless. You -see them because the kernel for the installation system is built to -run on computers with many different peripheral devices. Obviously, no -one computer will have every possible peripheral device, so the -operating system may emit a few complaints while it looks for -peripherals you don't own. You may also see the system pause for a -while. This happens when it is waiting for a device to respond, and -that device is not present on your system. If you find the time it -takes to boot the system unacceptably long, you can create a -custom kernel later <phrase arch="linux-any">(see <xref linkend="kernel-baking"/>)</phrase>. - -</para> - </sect2> - - - <sect2 id="problem-report"> - <title>Reporting Installation Problems</title> -<para> - -If you get through the initial boot phase but cannot complete the install, -the menu option <guimenuitem>Save debug logs</guimenuitem> may be helpful. -It lets you store system error logs and configuration information from the -installer to a floppy, or download them using a web browser. - -This information may provide clues as to what went wrong and how to -fix it. If you are submitting a bug report, you may want to attach -this information to the bug report. - -</para><para> - -Other pertinent installation messages may be found in -<filename>/var/log/</filename> during the -installation, and <filename>/var/log/installer/</filename> -after the computer has been booted into the installed system. - -</para> - </sect2> - - <sect2 id="submit-bug"> - <title>Submitting Installation Reports</title> -<para> - -If you still have problems, please submit an installation report. We also -encourage installation reports to be sent even if the installation is -successful, so that we can get as much information as possible on the largest -number of hardware configurations. - -</para><para> - -Note that your installation report will be published in the &debian; Bug -Tracking System (BTS) and forwarded to a public mailing list. Make sure that -you use an e-mail address that you do not mind being made public. - -</para><para> - -If you have a working &debian; system, the easiest way to send an installation -report is to install the <classname>installation-report</classname> and -<classname>reportbug</classname> packages -(<command>aptitude install installation-report reportbug</command>), -configure <classname>reportbug</classname> as explained in -<xref linkend="mail-outgoing"/>, and run the command <command>reportbug -installation-reports</command>. - -</para><para> - -Alternatively you can use this template when filling out -installation reports, and file the report as a bug report against the -<classname>installation-reports</classname> pseudo package, by sending it to -<email>submit@bugs.debian.org</email>. - -<informalexample><screen> -Package: installation-reports - -Boot method: <How did you boot the installer? CD? floppy? network?> -Image version: <Full URL to image you downloaded is best> -Date: <Date and time of the install> - -Machine: <Description of machine (eg, IBM Thinkpad R32)> -Processor: -Memory: -Partitions: <df -Tl will do; the raw partition table is preferred> - -Output of lspci -knn (or lspci -nn): - -Base System Installation Checklist: -[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it - -Initial boot: [ ] -Detect network card: [ ] -Configure network: [ ] -Detect CD: [ ] -Load installer modules: [ ] -Detect hard drives: [ ] -Partition hard drives: [ ] -Install base system: [ ] -Clock/timezone setup: [ ] -User/password setup: [ ] -Install tasks: [ ] -Install boot loader: [ ] -Overall install: [ ] - -Comments/Problems: - -<Description of the install, in prose, and any thoughts, comments - and ideas you had during the initial install.> -</screen></informalexample> - -In the bug report, describe what the problem is, including the last -visible kernel messages in the event of a kernel hang. Describe the -steps that you did which brought the system into the problem state. - -</para> - </sect2> - </sect1> diff --git a/nl/boot-installer/x86.xml b/nl/boot-installer/x86.xml deleted file mode 100644 index e090058db..000000000 --- a/nl/boot-installer/x86.xml +++ /dev/null @@ -1,433 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62896 untranslated --> - - <sect2 arch="any-x86"><title>Booting from a CD-ROM</title> - -&boot-installer-intro-cd.xml; - -<!-- We'll comment the following section until we know exact layout --> -<!-- -CD #1 of official &debian; CD-ROM sets for &arch-title; will present a -<prompt>boot:</prompt> prompt on most hardware. Press -<keycap>F4</keycap> to see the list of kernel options available -from which to boot. Just type your chosen flavor name (idepci, -vanilla, compact, bf24) at the <prompt>boot:</prompt> prompt -followed by &enterkey;. - -</para><para> - -If your hardware doesn't support booting of multiple images, put one -of the other CDs in the drive. It appears that most SCSI CD-ROM drives -do not support <command>isolinux</command> multiple image booting, so users -with SCSI CD-ROMs should try either CD2 (vanilla) or CD3 (compact), -or CD5 (bf2.4). - -</para><para> - -CD's 2 through 5 will each boot a -different ``flavor'' depending on which CD-ROM is -inserted. See <xref linkend="kernel-choice"/> for a discussion of the -different flavors. Here's how the flavors are laid out on the -different CD-ROMs: - -<variablelist> -<varlistentry> -<term>CD 1</term><listitem><para> - -Allows a selection of kernel images to boot from (the idepci flavor is -the default if no selection is made). - -</para></listitem></varlistentry> -<varlistentry> -<term>CD 2</term><listitem><para> - -Boots the <quote>vanilla</quote> flavor. - -</para></listitem></varlistentry> -<varlistentry> -<term>CD 3</term><listitem><para> - -Boots the <quote>compact</quote> flavor. - -</para></listitem></varlistentry> -<varlistentry> -<term>CD 4</term><listitem><para> - -Boots the <quote>idepci</quote> flavor. - -</para></listitem></varlistentry> -<varlistentry> -<term>CD 5</term><listitem><para> - -Boots the <quote>bf2.4</quote> flavor. - -</para></listitem></varlistentry> - - </variablelist> - -</para><para> - ---> - - </sect2> - - <sect2 arch="any-x86" id="boot-win32"> - <title>Booting from Windows</title> -<para> - -To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM -or USB memory stick installation media as described in -<xref linkend="official-cdrom"/> and <xref linkend="boot-usb-files"/>. - -</para><para> - -If you use an installation CD or DVD, a pre-installation program should be -launched automatically when you insert the disc. -In case Windows does not start it automatically, or if you are using a USB -memory stick, you can run it manually by accessing the device and executing -<command>setup.exe</command>. - -</para><para> - -After the program has been started, a few preliminary questions will be -asked and the system will be prepared to start the &debian-gnu; installer. - -</para> - </sect2> - -<!-- FIXME the documented procedure does not exactly work, commented out - until fixes - - <sect2 arch="x86" id="install-from-dos"> - <title>Booting from a DOS partition</title> - -&boot-installer-intro-hd.xml; - -<para> - -Boot into DOS (not Windows) without any drivers being loaded. To do -this, you have to press <keycap>F8</keycap> at exactly the right -moment (and optionally select the <quote>safe mode command prompt only</quote> -option). Enter the subdirectory for the flavor you chose, e.g., - -<informalexample><screen> -cd c:\install -</screen></informalexample>. - -Next, execute <command>install.bat</command>. -The kernel will load and launch the installer system. - -</para><para> - -Please note, there is currently a loadlin problem (#142421) which -precludes <filename>install.bat</filename> from being used with the -bf2.4 flavor. The symptom of the problem is an -<computeroutput>invalid compressed format</computeroutput> error. - -</para> - </sect2> - -END FIXME --> - - <sect2 arch="x86" id="boot-initrd"> - <title>Booting from Linux Using <command>LILO</command> or - <command>GRUB</command></title> - -<para> -To boot the installer from hard disk, you must first download -and place the needed files as described in <xref linkend="boot-drive-files"/>. -</para> - -<para> -If you intend to use the hard drive only for booting and then -download everything over the network, you should download the -<filename>netboot/debian-installer/&architecture;/initrd.gz</filename> file and its -corresponding kernel -<filename>netboot/debian-installer/&architecture;/linux</filename>. This will allow you -to repartition the hard disk from which you boot the installer, although you -should do so with care. -</para> - -<para> -Alternatively, if you intend to keep an existing partition on the hard -drive unchanged during the install, you can download the -<filename>hd-media/initrd.gz</filename> file and its kernel, as well as -copy a CD (or DVD) iso to the drive (make sure the file is named ending in -<literal>.iso</literal>). The installer can then boot from the drive -and install from the CD/DVD image, without needing the network. -</para> - -<para> -For <command>LILO</command>, you will need to configure two -essential things in <filename>/etc/lilo.conf</filename>: -<itemizedlist> -<listitem><para> - -to load the <filename>initrd.gz</filename> installer at boot time; - -</para></listitem> -<listitem><para> - -have the <filename>vmlinuz</filename> kernel use a RAM disk as -its root partition. - -</para></listitem> -</itemizedlist> - -Here is a <filename>/etc/lilo.conf</filename> example: - -</para><para> - -<informalexample><screen> -image=/boot/newinstall/vmlinuz - label=newinstall - initrd=/boot/newinstall/initrd.gz -</screen></informalexample> - -For more details, refer to the -<citerefentry><refentrytitle>initrd</refentrytitle> -<manvolnum>4</manvolnum></citerefentry> and -<citerefentry><refentrytitle>lilo.conf</refentrytitle> -<manvolnum>5</manvolnum></citerefentry> man pages. Now run -<userinput>lilo</userinput> and reboot. - -</para><para> - -The procedure for <command>GRUB</command> is quite similar. Locate your -<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> -directory (or sometimes <filename>/boot/boot/grub/</filename>) and add an -entry for the installer, for example (assuming <filename>/boot</filename> -is on the first partition of the first disk in the system): - -<informalexample><screen> -title New Install -root (hd0,0) -kernel /boot/newinstall/vmlinuz -initrd /boot/newinstall/initrd.gz -</screen></informalexample> - -</para><para> - -From here on, there should be no difference between <command>GRUB</command> -or <command>LILO</command>. - -</para> - </sect2> - - <sect2 arch="any-x86" condition="bootable-usb" id="usb-boot"> - <title>Booting from USB Memory Stick</title> -<para> - -Let's assume you have prepared everything from <xref -linkend="boot-dev-select"/> and <xref linkend="boot-usb-files"/>. Now -just plug your USB stick into some free USB connector and reboot the -computer. The system should boot up, and you should be presented with -the <prompt>boot:</prompt> prompt. Here you can enter optional boot -arguments, or just hit &enterkey;. - -</para> - </sect2> - - <sect2 arch="x86" condition="supports-floppy-boot" id="floppy-boot"> - <title>Booting from Floppies</title> -<para> - -You will have already downloaded the floppy images you needed and -created floppies from the images in <xref linkend="create-floppy"/>. -<!-- missing-doc FIXME If you need to, you can also modify the boot floppy; see -<xref linkend="rescue-replace-kernel"/>. --> - -</para><para> - -To boot from the installer boot floppy, place it in the primary floppy -drive, shut down the system as you normally would, then turn it back -on. - -</para><para> - -For installing from an LS-120 drive (ATAPI version) with a set of -floppies, you need to specify the virtual location for the floppy -device. This is done with the <emphasis>root=</emphasis> boot -argument, giving the device that the ide-floppy driver maps the device -to. For example, if your LS-120 drive is connected as the first IDE -device (master) on the second cable, you enter -<userinput>install root=/dev/hdc</userinput> at the boot prompt. - -</para><para> - -Note that on some machines, <keycombo><keycap>Control</keycap> -<keycap>Alt</keycap> <keycap>Delete</keycap></keycombo> does not -properly reset the machine, so a <quote>hard</quote> reboot is recommended. If -you are installing from an existing operating system (e.g., from a DOS -box) you don't have a choice. Otherwise, please do a hard reboot when -booting. - -</para><para> - -The floppy disk will be accessed, and you should then see a screen -that introduces the boot floppy and ends with the <prompt>boot:</prompt> -prompt. - -</para><para> - -Once you press &enterkey;, you should see the message -<computeroutput>Loading...</computeroutput>, followed by -<computeroutput>Uncompressing Linux...</computeroutput>, and -then a screenfull or so of information about the hardware in your -system. More information on this phase of the boot process can be -found below in <xref linkend="kernel-msgs"/>. - -</para><para> - -After booting from the boot floppy, the root floppy is -requested. Insert the root floppy and press &enterkey;, and the -contents are loaded into memory. The installer program -<command>debian-installer</command> is automatically launched. - -</para> - </sect2> - - <sect2 arch="x86" id="boot-tftp"><title>Booting with TFTP</title> - -&boot-installer-intro-net.xml; - -<para> - -There are various ways to do a TFTP boot on i386. - -</para> - - <sect3><title>NIC or Motherboard that support PXE</title> -<para> - -It could be that your Network Interface Card or Motherboard provides -PXE boot functionality. -This is a <trademark class="trade">Intel</trademark> re-implementation -of TFTP boot. If so, you may be able to configure your BIOS to boot from the -network. - -</para> - </sect3> - - <sect3><title>NIC with Network BootROM</title> -<para> - -It could be that your Network Interface Card provides -TFTP boot functionality. - -</para><para condition="FIXME"> - -Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. -Please refer to this document. - -</para> - </sect3> - - <sect3><title>Etherboot</title> -<para> - -The <ulink url="http://www.etherboot.org">etherboot project</ulink> -provides bootdiskettes and even bootroms that do a TFTPboot. - -</para> - </sect3> - </sect2> - - <sect2 arch="x86" id="boot-screen"> - <title>The Boot Screen</title> -<para> - -When the installer boots, you should be presented with a friendly graphical -screen showing the &debian; logo and a menu: - -<informalexample><screen> -Installer boot menu - -Install -Graphical install -Advanced options > -Help - -Press ENTER to boot or TAB to edit a menu entry -</screen></informalexample> - -Depending on the installation method you are using, the <quote>Graphical -install</quote> option may not be available. - -</para><para> - -For a normal installation, select either the <quote>Install</quote> or -the <quote>Graphical install</quote> entry — using either the -arrow keys on your keyboard or by typing the first (highlighted) letter -— and press &enterkey; to boot the installer. - -</para><para> - -The <quote>Advanced options</quote> entry gives access to a second menu -that allows to boot the installer in expert mode, in rescue mode and for -automated installs. - -</para><para> - -If you wish or need to add any boot parameters for either the installer -or the kernel, press &tabkey;. This will display the default boot command -for the selected menu entry and allow to add additional options. The help -screens (see below) list some common possible options. Press &enterkey; to -boot the installer with your options; pressing &escapekey; will return you -to the boot menu and undo any changes you made. - -</para><para> - -Choosing the <quote>Help</quote> entry will result in the first help screen -being displayed which gives an overview of all available help screens. -Note that it is not possible to return to the boot menu after the help -screens have been displayed. However, the F3 and F4 help screens list -commands that are equivalent to the boot methods listed in the menu. All -help screens have a boot prompt at which the boot command can be typed: - -<informalexample><screen> -Press F1 for the help index, or ENTER to boot: -</screen></informalexample> - -At this boot prompt you can either just press &enterkey; to boot the -installer with default options or enter a specific boot command and, -optionally, boot parameters. A number of boot parameters which might be -useful can be found on the various help screens. If you do add any -parameters to the boot command line, be sure to first type the boot method -(the default is <userinput>install</userinput>) and a space before the -first parameter (e.g., <userinput>install fb=false</userinput>). - -<note><para> - -The keyboard is assumed to have a default American English layout at this -point. This means that if your keyboard has a different (language-specific) -layout, the characters that appear on the screen may be different from what -you'd expect when you type parameters. Wikipedia has a -<ulink url="&url-us-keymap;">schema of the US keyboard layout</ulink> which -can be used as a reference to find the correct keys to use. - -</para></note> -<note><para> - -If you are using a system that has the BIOS configured to use serial console, -you may not be able to see the initial graphical splash screen upon booting -the installer; you may even not see the boot menu. The same can happen if -you are installing the system via a remote management device that provides a -text interface to the VGA console. Examples of these devices include the text -console of Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's -<quote>Integrated Remote Assistant</quote> (IRA). - -</para><para> - -To bypass the graphical boot screen you can either blindly press &escapekey; -to get a text boot prompt, or (equally blindly) press <quote>H</quote> -followed by &enterkey; to select the <quote>Help</quote> option described -above. After that your keystrokes should be echoed at the prompt. -To prevent the installer from using the framebuffer for the rest of the -installation, you will also want to add <userinput>vga=normal fb=false</userinput> -to the boot prompt, as described in the help text. - -</para></note> -</para> - - </sect2> diff --git a/nl/boot-new/boot-new.xml b/nl/boot-new/boot-new.xml deleted file mode 100644 index 7338c558e..000000000 --- a/nl/boot-new/boot-new.xml +++ /dev/null @@ -1,224 +0,0 @@ -<!-- original version: 61133 --> - -<chapter id="boot-new"> - <title>De computer opstarten met uw nieuwe &debian; systeem</title> - - <sect1 id="base-boot"><title>Het moment van de waarheid</title> -<para> - -De eerste keer dat u uw computer opnieuw opstart met uw nieuwe &debian; -systeem is een soort <quote>vuurdoop</quote>. - -</para><para arch="any-x86"> - -Als u een standaard installatie heeft uitgevoerd, is het menu van de -<classname>grub</classname><phrase arch="x86">, of eventueel van de <classname>lilo</classname></phrase> -opstartlader, het eerste dat u behoort te zien nadat het systeem opnieuw -opstart. -De eerste keuzes in het menu zullen betrekking hebben op uw nieuwe &debian; -systeem. Als u ook andere besturingssystemen (zoals Windows) op de computer -had die door het installatiesysteem gedetecteerd zijn, dan zullen deze lager -in het menu zijn opgenomen. - -Als het systeem niet juist opstart, raak dan vooral niet in paniek. Als de -installatie successvol is afgerond, dan is de kans groot dat slechts een -relatief klein probleem het opstarten van het systeem met &debian; verhindert. -In de meeste gevallen kunnen zulke problemen worden opgelost zonder de -installatie the hoeven herhalen. Eén van de beschikbare opties om -opstartproblemen te verhelpen is het gebruik van de ingebouwde -reddingsmodus van het installatiesysteem (zie <xref linkend="rescue"/>). - -</para><para> - -Als &debian; en &arch-kernel; nieuw zijn voor u, dan kunt u hierbij mogelijk wat hulp -gebruiken van meer ervaren gebruikers. -<phrase arch="x86">Voor directe on-line hulp kunt u de IRC-kanalen #debian of -#debian-boot op het OFTC-netwerk proberen. Of anders kunt u een bericht sturen -naar de <ulink url="&url-list-subscribe;">mailinglijst debian-user</ulink>.</phrase> -<phrase arch="not-x86">Voor minder gangbare architecturen zoals &arch-title;, -is uw beste optie om hulp te vragen op de -<ulink url="&url-list-subscribe;">mailinglijst debian-&arch-listname;</ulink>.</phrase> -Ook kunt u ons (in het Engels!) een installatieverslag sturen, zoals -beschreven in <xref linkend="submit-bug"/>. Probeer daarbij uw probeem helder -te omschrijven en neem in het verslag op eventuele getoonde berichten die -anderen kunnen helpen het probleem te diagnosticeren. - -</para><para arch="any-x86"> - -Als er andere besturingssystemen op uw computer aanwezig waren die niet -gedetecteerd, of niet correct gedetecteerd werden, stuur ons dan een -installatieverslag. - -</para> - - - <sect2 arch="powerpc"><title>OldWorld PowerMacs</title> - -<para> - -Als de machine niet goed opstart na afronding van de installatie en stopt met -een <prompt>boot:</prompt> prompt, probeer dan <userinput>Linux</userinput> -gevolgd door &enterkey; in te geven. (De standaard opstartconfiguratie in -<filename>quik.conf</filename> is Linux genaamd.) De namen die in -<filename>quik.conf</filename> zijn gedefinieerd, worden getoond als u bij de -<prompt>boot:</prompt> prompt de <keycap>Tab</keycap>-toets indrukt. U kunt -ook proberen opnieuw het installatieprogramma op te starten en vervolgens het -bestand <filename>/target/etc/quik.conf</filename> te wijzigen dat daar is -weggeschreven door de stap <guimenuitem>Quik op een harde schijf -installeren</guimenuitem>. Informatie over het werken met -<command>quik</command> is beschikbaar op -<ulink url="&url-powerpc-quik-faq;"></ulink>. -<!-- FJP: Hoe is "Install Quick on a Hard Disk" vertaald? //--> - -</para><para> - -Geef, om MacOS op te starten zonder dat de nvram wordt ingesteld naar -de standaardwaarden, bij de OpenFirmware-prompt het commando -<userinput>bye</userinput> (ervan uitgaande dat MacOS niet van de machine -is verwijderd). Houd, om een OpenFirmware-prompt te verkrijgen, de toetsen -<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</keycap> -<keycap>f</keycap> </keycombo> ingedrukt terwijl u de machine inschakelt. -Houd, als u de de wijzigingen in de OpenFirmware nvram wilt herstellen, -de toetsen <keycombo> <keycap>command</keycap> <keycap>option</keycap> -<keycap>p</keycap> <keycap>r</keycap> </keycombo> ingedrukt terwijl u -de machine inschakelt. - -</para><para> - -Als u <command>BootX</command> gebruikt om het geïnstalleerde systeem op -te starten, kunt u gewoon de gewenste kernel selecteren in de map -<filename>Linux Kernels</filename>, de optie ramdisk deselecteren en het -root-apparaat (bijvoorbeeld <userinput>/dev/hda8</userinput>) toevoegen -dat overeenkomt met uw installatie. - -</para> - </sect2> - - <sect2 arch="powerpc"><title>NewWorld PowerMacs</title> - -<para> - -Op G4- en iBook-systemen, kunt u de toets <keycap>option</keycap> ingedrukt -houden. U krijgt dan een grafisch scherm met een knop voor elk besturingssysteem -dat kan worden opgestart: &debian-gnu; zal een knop met daarop een klein icoon van -een penguin zijn. - -</para><para> - -Als u MacOS heeft behouden en als dat op enig moment de OpenFirmware-variabele -<envar>boot-device</envar> zou wijzigen, dan dient u OpenFirmware te herstellen -naar zijn standaard configuratie. Hiervoor houdt u de toetsen <keycombo> -<keycap>command</keycap> <keycap>option</keycap> <keycap>p</keycap> -<keycap>r</keycap> </keycombo> ingedrukt terwijl u de machine inschakelt. - -</para><para> - -De namen die zijn gedefinieerd in <filename>yaboot.conf</filename> zullen -worden getoond als u bij de <prompt>boot:</prompt> prompt de toets -<keycap>Tab</keycap> indrukt. - -</para><para> - -Het herstellen van OpenFirmware op G3- of G4-systemen zal standaard resulteren -in het opstarten van &debian-gnu; (als u de schijf juist heeft ingedeeld en de -Apple_Bootstrap partitie als eerste heeft geplaatst). Als u &debian-gnu; op een -SCSI harde schijf en MacOS op een IDE harde schijf heeft, werkt dit mogelijk -niet en zal u in OpenFirmware de variabele <envar>boot-device</envar> moeten -instellen. Normaal gesproken doet <command>ybin</command> dit automatisch. - -</para><para> - -Nadat u &debian-gnu; voor de eerste keer heeft opgestart, kunt u aanvullende -opties die u wenst (zoals voor 'dual boot') toevoegen aan -<filename>/etc/yaboot.conf</filename> en <command>ybin</command> starten om uw -opstartpartitie bij te werken met de gewijzigde configuratie. Aanvullende -informatie is beschikbaar op -<ulink url="&url-powerpc-yaboot-faq;">yaboot HOWTO</ulink>. - -</para> - </sect2> - </sect1> - -&mount-encrypted.xml; - - <sect1 id="login"> - <title>Aanloggen</title> - -<para> - -Nadat het systeem is opgestart, wordt de aanlogprompt getoond. -Log aan met uw persoonlijke gebruikersaccount door de gebruikersnaam en -het wachtwoord die u tijdens de installatie heeft geselecteerd, in te -geven. Uw systeem is nu klaar voor gebruik. - -</para><para> - -Als u een nieuwe gebruiker bent, adviseren wij om, terwijl u begint uw systeem -te gebruiken, ook de documentatie te verkennen die al is geïnstalleerd tijdens -het installatieproces. - -</para><para> - -De documentatie bij programma's die u heeft geïnstalleerd, kunt u vinden in -submappen onder <filename>/usr/share/doc/</filename>. Merk op dat deze -submappen de naam hebben van de geïnstalleerde &debian; pakketten, niet van de -programma's zelf. -Meer uitgebreide documentatie is vaak opgenomen in afzonderlijke -documentatiepakketten die in het algemeen niet standaard geïnstalleerd -worden. Documentatie over het pakketbeheersysteem <command>apt</command> kan -bijvoorbeeld worden gevonden in de pakketten <classname>apt-doc</classname> -of <classname>apt-howto</classname>. - -</para><para> - -Daarnaast zijn er enkele bijzondere mappen onder -<filename>/usr/share/doc/</filename>. Linux HOWTO handleidingen worden -in <emphasis>.gz</emphasis>-formaat (gecomprimeerd) geïnstalleerd in -<filename>/usr/share/doc/HOWTO/en-txt/</filename>. Na installatie van -<classname>dhelp</classname> vindt u in -<filename>/usr/share/doc/HTML/index.html</filename> een inhoudsopgave -van documentatie die met een browser kan worden bekeken. - -</para><para> - -Een eenvoudige manier om deze documenten met een tekstuele browser te -bekijken, is met de volgende commando's: - -<informalexample><screen> -$ cd /usr/share/doc/ -$ w3m . -</screen></informalexample> - -De punt achter het commando <command>w3m</command> bepaalt dat de inhoud van -de huidige directory moet worden getoond. - -</para><para> - -If you have a graphical desktop environment installed, you can also use -its web browser. Start the web browser from the application menu and -enter <userinput>/usr/share/doc/</userinput> in the address bar. - -Als u een grafische desktopomgeving heeft geïnstalleerd, kunt u ook de -bijbehorende webbrowser gebruiken. Start de browser vanuit het -toepassingenmenu en type <userinput>/usr/share/doc/</userinput> in de -adresregel. - -</para><para> - -U kunt ook <userinput>info <replaceable>command</replaceable></userinput> of -<userinput>man <replaceable>command</replaceable></userinput> gebruiken om -documentatie te bekijken over de meeste opdrachten die vanaf de opdrachtregel -gegeven kunnen worden. Ook als u een opdracht ingeeft gevolgd door -<userinput>--help</userinput>, krijgt u over het algemeen een korte samenvatting -over het gebruik van de betreffende opdracht. Als de uitvoer van een -opdracht niet op één scherm past, probeer dan om <userinput>| more</userinput> -achter de opdracht in te geven; hierdoor zal de uitvoer pauzeren voordat deze -voorbij de bovenkant van het scherm schuift. U kunt een overzicht krijgen van -alle opdrachten die met (een) bepaalde letter(s) beginnen door direct achter de -letter(s) tweemaal op <keycap>tab</keycap> te drukken. -<!-- FJP: origineel: tab is <keycap> //--> - -</para> - - </sect1> -</chapter> diff --git a/nl/boot-new/mount-encrypted.xml b/nl/boot-new/mount-encrypted.xml deleted file mode 100644 index d88c83144..000000000 --- a/nl/boot-new/mount-encrypted.xml +++ /dev/null @@ -1,181 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56326 untranslated --> - - <sect1 id="mount-encrypted-volumes"> - <title>Mounting encrypted volumes</title> - -<para> - -If you created encrypted volumes during the installation and assigned -them mount points, you will be asked to enter the passphrase for each -of these volumes during the boot. The actual procedure differs -slightly between dm-crypt and loop-AES. - -</para> - - <sect2 id="mount-dm-crypt"> - <title>dm-crypt</title> - -<para> - -For partitions encrypted using dm-crypt you will be shown the following -prompt during the boot: - -<informalexample><screen> -Starting early crypto disks... <replaceable>part</replaceable>_crypt(starting) -Enter LUKS passphrase: -</screen></informalexample> - -In the first line of the prompt, <replaceable>part</replaceable> is the -name of the underlying partition, e.g. sda2 or md0. -You are now probably wondering -<emphasis>for which volume</emphasis> you are actually entering the -passphrase. Does it relate to your <filename>/home</filename>? Or to -<filename>/var</filename>? Of course, if you have just one encrypted -volume, this is easy and you can just enter the passphrase you used -when setting up this volume. If you set up more than one encrypted -volume during the installation, the notes you wrote down as the last -step in <xref linkend="partman-crypto"/> come in handy. If you did not -make a note of the mapping between -<filename><replaceable>part</replaceable>_crypt</filename> and the mount -points before, you can still find it -in <filename>/etc/crypttab</filename> -and <filename>/etc/fstab</filename> of your new system. - -</para><para> - -The prompt may look somewhat different when an encrypted root file system is -mounted. This depends on which initramfs generator was used to generate the -initrd used to boot the system. The example below is for an initrd generated -using <classname>initramfs-tools</classname>: - -<informalexample><screen> -Begin: Mounting <emphasis>root file system</emphasis>... ... -Begin: Running /scripts/local-top ... -Enter LUKS passphrase: -</screen></informalexample> - -</para><para> - -No characters (even asterisks) will be shown while entering the passphrase. -If you enter the wrong passphrase, you have two more tries to correct it. -After the third try the boot process will skip this volume and continue to -mount the next filesystem. Please see <xref linkend="crypto-troubleshooting"/> -for further information. - -</para><para> - -After entering all passphrases the boot should continue as usual. - -</para> - </sect2> - - <sect2 id="mount-loop-aes"> - <title>loop-AES</title> - -<para> - -For partitions encrypted using loop-AES you will be shown the following -prompt during the boot: - -<informalexample><screen> -Checking loop-encrypted file systems. -Setting up /dev/loop<replaceable>X</replaceable> (/<replaceable>mountpoint</replaceable>) -Password: -</screen></informalexample> - -</para><para> - -No characters (even asterisks) will be shown while entering the passphrase. -If you enter the wrong passphrase, you have two more tries to correct it. -After the third try the boot process will skip this volume and continue to -mount the next filesystem. Please see <xref linkend="crypto-troubleshooting"/> -for further information. - -</para><para> - -After entering all passphrases the boot should continue as usual. - -</para> - </sect2> - - <sect2 id="crypto-troubleshooting"> - <title>Troubleshooting</title> - -<para> - -If some of the encrypted volumes could not be mounted because a wrong -passphrase was entered, you will have to mount them manually after the -boot. There are several cases. - -</para> - -<itemizedlist> -<listitem><para> - -The first case concerns the root partition. When it is not mounted -correctly, the boot process will halt and you will have to reboot the -computer to try again. - -</para></listitem> -<listitem><para> - -The easiest case is for encrypted volumes holding data like -<filename>/home</filename> or <filename>/srv</filename>. You can -simply mount them manually after the boot. For loop-AES this is -a one-step operation: - -<informalexample><screen> -<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput> -<prompt>Password:</prompt> -</screen></informalexample> - -where <replaceable>/mount_point</replaceable> should be replaced by -the particular directory (e.g. <filename>/home</filename>). The only -difference from an ordinary mount is that you will be asked to enter -the passphrase for this volume. - -</para><para> - -For dm-crypt this is a bit trickier. First you need to register the -volumes with <application>device mapper</application> by running: - -<informalexample><screen> -<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput> -</screen></informalexample> - -This will scan all volumes mentioned -in <filename>/etc/crypttab</filename> and will create appropriate -devices under the <filename>/dev</filename> directory after entering -the correct passphrases. (Already registered volumes will be skipped, -so you can repeat this command several times without worrying.) After -successful registration you can simply mount the volumes the usual -way: - -<informalexample><screen> -<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput> -</screen></informalexample> - -</para></listitem> -<listitem><para> - -If any volume holding noncritical system files could not be mounted -(<filename>/usr</filename> or <filename>/var</filename>), the system -should still boot and you should be able to mount the volumes manually -like in the previous case. However, you will also need to (re)start -any services usually running in your default runlevel because it is -very likely that they were not started. The easiest way to achieve -this is by switching to the first runlevel and back by entering - -<informalexample><screen> -<prompt>#</prompt> <userinput>init 1</userinput> -</screen></informalexample> - -at the shell prompt and pressing <keycombo> <keycap>Control</keycap> -<keycap>D</keycap> </keycombo> when asked for the root password. - -</para></listitem> -</itemizedlist> - - </sect2> - </sect1> diff --git a/nl/hardware/accessibility.xml b/nl/hardware/accessibility.xml deleted file mode 100644 index 565f47ff8..000000000 --- a/nl/hardware/accessibility.xml +++ /dev/null @@ -1,34 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - - <sect2 id="braille-displays" arch="ia64;powerpc;x86"> - <title>Braille Displays</title> -<para> - -Support for braille displays is determined by the underlying support -found in <classname>brltty</classname>. Most displays work under -<classname>brltty</classname>, connected via either a serial port, USB -or bluetooth. Details on supported braille devices can be found on the -<ulink url="&url-brltty;"><classname>brltty</classname> website</ulink>. -&debian-gnu; &release; ships with <classname>brltty</classname> version -&brlttyver;. - -</para> - </sect2> - - <sect2 id="hardware-speech-synthesis" arch="x86"> - <title>Hardware Speech Synthesis</title> -<para> - -Support for hardware speech synthesis devices is determined by the -underlying support found in <classname>speakup</classname>. -<classname>speakup</classname> only supports integrated boards and -external devices connected to a serial port (no USB or serial-to-USB -adapters are supported). Details on supported hardware speech synthesis -devices can be found on the -<ulink url="&url-speakup;"><classname>speakup</classname> website</ulink>. -&debian-gnu; &release; ships with <classname>speakup</classname> version -&speakupver;. - -</para> - </sect2> diff --git a/nl/hardware/buying-hardware.xml b/nl/hardware/buying-hardware.xml deleted file mode 100644 index 367aac515..000000000 --- a/nl/hardware/buying-hardware.xml +++ /dev/null @@ -1,98 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - <sect1 arch="not-s390"><title>Purchasing Hardware Specifically for GNU/&arch-kernel;</title> - -<para arch="linux-any"> - -There are several vendors, who ship systems with &debian; or other -distributions of GNU/Linux -<ulink url="&url-pre-installed;">pre-installed</ulink>. You might pay more -for the privilege, but it does buy a level of peace of mind, since you can -be sure that the hardware is well-supported by GNU/Linux. - -</para><para arch="any-x86"> - -If you do have to buy a machine with Windows bundled, carefully read -the software license that comes with Windows; you may be able to -reject the license and obtain a rebate from your vendor. Searching -the Internet for <quote>windows refund</quote> may get you some useful -information to help with that. - -</para><para> - -Whether or not you are purchasing a system with &arch-kernel; bundled, or even -a used system, it is still important to check that your hardware is -supported by the &arch-kernel; kernel. Check if your hardware is listed in -the references found above. Let your salesperson (if any) know that -you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware -vendors. - -</para> - - <sect2><title>Avoid Proprietary or Closed Hardware</title> -<para> - -Some hardware manufacturers simply won't tell us how to write drivers -for their hardware. Others won't allow us access to the documentation -without a non-disclosure agreement that would prevent us from -releasing the &arch-kernel; source code. - -</para><para> - -Since we haven't been granted access to the documentation on these -devices, they simply won't work under &arch-kernel;. You can help by asking -the manufacturers of such hardware to release the documentation. If -enough people ask, they will realize that the free software community -is an important market. - -</para> -</sect2> - - - <sect2 arch="any-x86"><title>Windows-specific Hardware</title> -<para> - -A disturbing trend is the proliferation of Windows-specific modems and -printers. In some cases these are specially designed to be operated by -the Microsoft Windows operating system and bear the legend <quote>WinModem</quote> -or <quote>Made especially for Windows-based computers</quote>. This -is generally done by removing the embedded processors of the hardware -and shifting the work they do over to a Windows driver that is run by -your computer's main CPU. This strategy makes the hardware less -expensive, but the savings are often <emphasis>not</emphasis> passed on to the -user and this hardware may even be more expensive than equivalent -devices that retain their embedded intelligence. - -</para><para> - -You should avoid Windows-specific hardware for two reasons. The first -is that the manufacturers do not generally make the resources -available to write a &arch-kernel; driver. Generally, the hardware and -software interface to the device is proprietary, and documentation is -not available without a non-disclosure agreement, if it is available -at all. This precludes it being used for free software, since free -software writers disclose the source code of their programs. The -second reason is that when devices like these have had their embedded -processors removed, the operating system must perform the work of the -embedded processors, often at <emphasis>real-time</emphasis> priority, -and thus the CPU is not available to run your programs while it is -driving these devices. Since the typical Windows user does not -multi-process as intensively as a &arch-kernel; user, the manufacturers hope -that the Windows user simply won't notice the burden this hardware -places on their CPU. However, any multi-processing operating system, -even Windows 2000 or XP, suffers from degraded performance when -peripheral manufacturers skimp on the embedded processing power of -their hardware. - -</para><para> - -You can help improve this situation by encouraging these manufacturers -to release the documentation and other resources necessary for us to -program their hardware, but the best strategy is simply to avoid this -sort of hardware until it is listed as working in the -<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>. - -</para> -</sect2> - </sect1> diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml deleted file mode 100644 index 97b0a5d5f..000000000 --- a/nl/hardware/hardware-supported.xml +++ /dev/null @@ -1,383 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - - <sect1 id="hardware-supported"> - <title>Supported Hardware</title> -<para> - -&debian; does not impose hardware requirements beyond the requirements -of the Linux kernel and the GNU tool-sets. Therefore, any -architecture or platform to which the Linux kernel, libc, -<command>gcc</command>, etc. have been ported, and for which a &debian; -port exists, can run &debian;. Please refer to the Ports pages at -<ulink url="&url-ports;"></ulink> for -more details on &arch-title; architecture systems which have been -tested with &debian-gnu;. - -</para><para> - -Rather than attempting to describe all the different hardware -configurations which are supported for &arch-title;, this section -contains general information and pointers to where additional -information can be found. - -</para> - - <sect2><title>Supported Architectures</title> -<para> - -&debian; GNU/Linux &release; supports eleven major architectures and several -variations of each architecture known as <quote>flavors</quote>. - -</para><para> - -<informaltable> -<tgroup cols="4"> -<thead> -<row> - <entry>Architecture</entry><entry>&debian; Designation</entry> - <entry>Subarchitecture</entry><entry>Flavor</entry> -</row> -</thead> - -<tbody> -<row> - <entry>Intel x86-based</entry> - <entry>i386</entry> - <entry></entry> - <entry></entry> -</row> - -<row> - <entry>AMD64 & Intel EM64T</entry> - <entry>amd64</entry> - <entry></entry> - <entry></entry> -</row> - -<row> - <entry morerows="4">ARM</entry> - <entry morerows="4">armel</entry> - <entry>Intel IOP32x</entry> - <entry>iop32x</entry> -</row><row> - <entry>Intel IXP4xx</entry> - <entry>ixp4xx</entry> -</row><row> - <entry>Marvell Kirkwood</entry> - <entry>kirkwood</entry> -</row><row> - <entry>Marvell Orion</entry> - <entry>orion5x</entry> -</row><row> - <entry>Versatile</entry> - <entry>versatile</entry> -</row> - -<row> - <entry>Intel IA-64</entry> - <entry>ia64</entry> - <entry></entry> - <entry></entry> -</row> - -<row> - <entry morerows="3">MIPS (big endian)</entry> - <entry morerows="3">mips</entry> - <entry>SGI IP22 (Indy/Indigo 2)</entry> - <entry>r4k-ip22</entry> -</row><row> - <entry>SGI IP32 (O2)</entry> - <entry>r5k-ip32</entry> -</row><row> - <entry>MIPS Malta (32 bit)</entry> - <entry>4kc-malta</entry> -</row><row> - <entry>MIPS Malta (64 bit)</entry> - <entry>5kc-malta</entry> -</row> - -<row> - <entry morerows="2">MIPS (little endian)</entry> - <entry morerows="2">mipsel</entry> - <entry>Cobalt</entry> - <entry>cobalt</entry> -</row><row> - <entry>MIPS Malta (32 bit)</entry> - <entry>4kc-malta</entry> -</row><row> - <entry>MIPS Malta (64 bit)</entry> - <entry>5kc-malta</entry> -</row> - -<row> - <entry morerows="1">IBM/Motorola PowerPC</entry> - <entry morerows="1">powerpc</entry> - <entry>PowerMac</entry> - <entry>pmac</entry> -</row><row> - <entry>PReP</entry> - <entry>prep</entry> -</row> - -<row> - <entry morerows="1">Sun SPARC</entry> - <entry morerows="1">sparc</entry> - <entry>sun4u</entry> - <entry morerows="1">sparc64</entry> -</row><row> - <entry>sun4v</entry> -</row> - -<row> - <entry morerows="1">IBM S/390</entry> - <entry morerows="1">s390</entry> - <entry>IPL from VM-reader and DASD</entry> - <entry>generic</entry> -</row><row> - <entry>IPL from tape</entry> - <entry>tape</entry> -</row> - -</tbody></tgroup></informaltable> - -</para><para> - -This document covers installation for the -<emphasis>&arch-title;</emphasis> architecture. If you are looking -for information on any of the other &debian;-supported architectures -take a look at the -<ulink url="http://www.debian.org/ports/">Debian-Ports</ulink> pages. - -</para> -<caution arch="ia64"><para> - -The &arch-title; architecture only supports Intel Itanium processors -and not the much more common 64-bit processors from the EM64T family -(including e.g. the Pentium D and the Core2 Duo). Those -systems are supported by the <emphasis>amd64</emphasis> architecture -or, if you prefer a 32-bit userland, the <emphasis>i386</emphasis> -architecture. - -</para></caution> -<para condition="new-arch"> - -This is the first official release of &debian-gnu; for the &arch-title; -architecture. We feel that it has proven itself sufficiently to be -released. However, because it has not had the exposure (and hence -testing by users) that some other architectures have had, you may -encounter a few bugs. Use our -<ulink url="&url-bts;">Bug Tracking System</ulink> to report any -problems; make sure to mention the fact that the bug is on the -&arch-title; platform. It can be necessary to use the -<ulink url="&url-list-subscribe;">debian-&arch-listname; mailing list</ulink> -as well. - -</para> - </sect2> - -<!-- supported cpu docs --> -&supported-amd64.xml; -&supported-arm.xml; -&supported-hppa.xml; -&supported-i386.xml; -&supported-ia64.xml; <!-- FIXME: currently missing --> -&supported-mips.xml; -&supported-mipsel.xml; -&supported-powerpc.xml; -&supported-s390.xml; -&supported-sparc.xml; - - <sect2 arch="x86" id="laptops"><title>Laptops</title> -<para> - -Laptops are also supported and nowadays most laptops work out of the box. -In case a laptop contains specialized or proprietary hardware, some specific -functions may not be supported. To see if your particular laptop works well -with GNU/Linux, see for example the -<ulink url="&url-x86-laptop;">Linux Laptop pages</ulink>. - -</para> - </sect2> - - <sect2 condition="defaults-smp"> - <title>Multiple Processors</title> -<para> - -Multiprocessor support — also called <quote>symmetric multiprocessing</quote> -or SMP — is available for this architecture. The standard &debian; -&release; kernel image has been compiled with SMP support. The standard -kernel is also usable on non-SMP systems, but has a slight overhead which -will cause a small reduction in performance. For normal system use this -will hardly be noticable. - -</para><para> - -In order to optimize the kernel for single CPU systems, you'll have to -replace the standard &debian; kernel. <phrase arch="linux-any">You can find a discussion of how -to do this in <xref linkend="kernel-baking"/>. At this time -(kernel version &kernelversion;) the way you disable SMP is to deselect -<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> -section of the kernel config.</phrase> - -</para> - </sect2> - - <sect2 condition="smp-alternatives"> -<title>Multiple Processors</title> - -<para> - -Multiprocessor support — also called <quote>symmetric -multiprocessing</quote> or SMP — is available for this architecture. -The standard &debian; &release; kernel image has been compiled with -<firstterm>SMP-alternatives</firstterm> support. This means that the kernel -will detect the number of processors (or processor cores) and will -automatically deactivate SMP on uniprocessor systems. - -</para><para arch="i386"> - -The 486 flavour of the &debian; kernel image packages for &arch-title; -is not compiled with SMP support. - -</para> - </sect2> - - <sect2 condition="supports-smp"> - <title>Multiple Processors</title> -<para> - -Multiprocessor support — also called <quote>symmetric -multiprocessing</quote> or SMP — is available for this architecture. -However, the standard &debian; &release; kernel image does not support -SMP. This should not prevent installation, since the standard, -non-SMP kernel should boot on SMP systems; the kernel will simply use -the first CPU. - -</para><para> - -In order to take advantage of multiple processors, you'll have to -replace the standard &debian; kernel. <phrase arch="linux-any">You can find a discussion of how -to do this in <xref linkend="kernel-baking"/>. At this time -(kernel version &kernelversion;) the way you enable SMP is to select -<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> -section of the kernel config.</phrase> - -</para> - </sect2> - - <sect2 condition="supports-smp-sometimes"> - <title>Multiple Processors</title> -<para> - -Multiprocessor support — also called <quote>symmetric -multiprocessing</quote> or SMP — is available for this architecture, -and is supported by a precompiled &debian; kernel image. Depending on your -install media, this SMP-capable kernel may or may not be installed by -default. This should not prevent installation, since the standard, -non-SMP kernel should boot on SMP systems; the kernel will simply use -the first CPU. - -</para><para> - -In order to take advantage of multiple processors, you should check to see -if a kernel package that supports SMP is installed, and if not, choose an -appropriate kernel package. - -</para><para> - -You can also build your own customized kernel to support SMP. <phrase arch="linux-any">You can find -a discussion of how to do this in <xref linkend="kernel-baking"/>. At this -time (kernel version &kernelversion;) the way you enable SMP is to select -<quote>&smp-config-option;</quote> in the <quote>&smp-config-section;</quote> -section of the kernel config.</phrase> - -</para> - </sect2> - - <sect2 id="gfx" arch="not-s390"><title>Graphics Card Support</title> -<para arch="x86"> - -You should be using a VGA-compatible display interface for the console -terminal. Nearly every modern display card is compatible with -VGA. Ancient standards such CGA, MDA, or HGA should also work, -assuming you do not require X11 support. Note that X11 is not used -during the installation process described in this document. - -</para><para> - -&debian;'s support for graphical interfaces is determined by the -underlying support found in X.Org's X11 system. Most AGP, PCI, -PCIe, and PCI-X video cards work under X.Org. Details on supported graphics -buses, cards, monitors, and pointing devices can be found at -<ulink url="&url-xorg;"></ulink>. &debian; &release; ships -with X.Org version &x11ver;. - -</para><para arch="mips"> - -<!-- FIXME: mention explicit graphics chips and not system names --> -The X.Org X Window System is only supported on the SGI Indy and the O2. - -</para><para arch="sparc"> - -Most graphics options commonly found on Sparc-based machines are supported. -X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, -sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), -PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards -(glint driver). To use an Elite3D card with X.org you additionally need to -install the <classname>afbinit</classname> package, and read the documentation -included with it on how to activate the card. - -</para><para arch="sparc"> - -It is not uncommon for a Sparc machine to have two graphics cards in a -default configuration. In such a case there is a possibility that the -Linux kernel will not direct its output to the card initially used by the -firmware. The lack of output on the graphical console may then be mistaken -for a hang (usually the last message seen on console is 'Booting Linux...'). -One possible solution is to physically remove one of the video cards; -another option is to disable one of the cards using a kernel boot parameter. -Also, if graphical output is not required or desired, serial console may be -used as an alternative. On some systems use of serial console can be -activated automatically by disconnecting the keyboard before booting the -system. - -</para> - </sect2> - -&network-cards.xml; -&accessibility-hardware.xml; -&supported-peripherals.xml; - - </sect1> - - <sect1 arch="not-s390" id="hardware-firmware"> - <title>Devices Requiring Firmware</title> -<para> - -Besides the availability of a device driver, some hardware also requires -so-called <firstterm>firmware</firstterm> or <firstterm>microcode</firstterm> -to be loaded into the device before it can become operational. This is most -common for network interface cards (especially wireless NICs), but for example -some USB devices and even some hard disk controllers also require firmware. - -</para><para> - -In most cases firmware is non-free according to the criteria used by the -&debian-gnu; project and thus cannot be included in the main distribution -or in the installation system. If the device driver itself is included in -the distribution and if &debian-gnu; legally can distribute the firmware, -it will often be available as a separate package from the non-free section -of the archive. - -</para><para> - -However, this does not mean that such hardware cannot be used during an -installation. Starting with &debian-gnu; 5.0, &d-i; supports loading -firmware files or packages containing firmware from a removable medium, -such as a floppy disk or USB stick. -See <xref linkend="loading-firmware"/> for detailed information on how to -load firmware files or packages during the installation. - -</para> - </sect1> diff --git a/nl/hardware/hardware.xml b/nl/hardware/hardware.xml deleted file mode 100644 index 781baf139..000000000 --- a/nl/hardware/hardware.xml +++ /dev/null @@ -1,20 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56244 untranslated --> - -<chapter id="hardware-req"> - <title>System Requirements</title> - -<para> - -This section contains information about what hardware you need to get -started with &debian;. You will also find links to further information -about hardware supported by GNU and &arch-kernel;. - -</para> - -&hardware-supported.xml; -&buying-hardware.xml; -&installation-media.xml; -&memory-disk-requirements.xml; - -</chapter> diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml deleted file mode 100644 index d8d4f3c52..000000000 --- a/nl/hardware/installation-media.xml +++ /dev/null @@ -1,239 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - - <sect1 id="installation-media"> - <title>Installation Media</title> - -<para> - -This section will help you determine which different media types you can use to -install &debian;. For example, if you have a floppy disk drive on your machine, -it can be used to install &debian;. There is a whole chapter devoted to media, -<xref linkend="install-methods"/>, which lists the advantages and -disadvantages of each media type. You may want to refer back to this page once -you reach that section. - -</para> - - <sect2 condition="supports-floppy-boot"><title>Floppies</title> -<para> - -In some cases, you'll have to do your first boot from floppy disks. -Generally, all you will need is a -high-density (1440 kilobytes) 3.5 inch floppy drive. - -</para><para arch="powerpc"> - -For CHRP, floppy support is currently broken. - -</para> - </sect2> - - <sect2><title>CD-ROM/DVD-ROM</title> - -<note><para> - -Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both -CD-ROMs and DVD-ROMs, because both technologies are really -the same from the operating system's point of view, except for some very -old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI. - -</para></note><para> - -CD-ROM based installation is supported for some architectures. -On machines which support bootable CD-ROMs, you should be able to do a -completely -<phrase arch="not-s390">floppy-less</phrase> -<phrase arch="s390">tape-less</phrase> -installation. Even if your system doesn't -support booting from a CD-ROM, you can use the CD-ROM in conjunction -with the other techniques to install your system, once you've booted -up by other means; see <xref linkend="boot-installer"/>. - -</para><para arch="x86"> - -SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The <ulink -url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> contains in-depth information -on using CD-ROMs with Linux. - -</para><para arch="x86"> - -USB CD-ROM drives are also supported, as are FireWire devices that -are supported by the ohci1394 and sbp2 drivers. - -</para><para arch="arm"> - -IDE/ATAPI CD-ROMs are supported on all ARM machines. - -</para><para arch="mips"> - -On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive -capable of working with a logical blocksize of 512 bytes. Many of the -SCSI CD-ROM drives sold on the PC market do not have this -capability. If your CD-ROM drive has a jumper labeled -<quote>Unix/PC</quote> or <quote>512/2048</quote>, place it in the -<quote>Unix</quote> or <quote>512</quote> position. -To start the install, simply choose the <quote>System installation</quote> -entry in the firmware. - -</para> - </sect2> - - <sect2><title>Hard Disk</title> - -<para> - -Booting the installation system directly from a hard disk is another option -for many architectures. This will require some other operating system -to load the installer onto the hard disk. - -</para><para arch="sparc"> - -Although the &arch-title; does not allow booting from SunOS -(Solaris), you can install from a SunOS partition (UFS slices). - -</para> - </sect2> - - <sect2 condition="bootable-usb"><title>USB Memory Stick</title> - -<para> - -Many &debian; boxes need their floppy and/or CD-ROM drives only for -setting up the system and for rescue purposes. If you operate some -servers, you will probably already have thought about omitting those -drives and using an USB memory stick for installing and (when -necessary) for recovering the system. This is also useful for small -systems which have no room for unnecessary drives. - -</para> - </sect2> - - <sect2><title>Network</title> - -<para> - -The network can be used during the installation to retrieve files needed -for the installation. Whether the network is used or not depends on the -installation method you choose and your answers to certain questions that -will be asked during the installation. The installation system supports -most types of network connections (including PPPoE, but not ISDN or PPP), -via either HTTP or FTP. After the installation is completed, you can also -configure your system to use ISDN and PPP. - -</para><para condition="supports-tftp"> - -You can also <emphasis>boot</emphasis> the installation system over the -network. <phrase arch="mips;mipsel">This is the preferred installation technique -for &arch-title;.</phrase> - -</para><para condition="supports-nfsroot"> - -Diskless installation, using network booting from a local area network -and NFS-mounting of all local filesystems, is another option. - -</para> - </sect2> - - <sect2><title>Un*x or GNU system</title> - -<para> - -If you are running another Unix-like system, you could use it to install -&debian-gnu; without using the &d-i; described in the rest of this -manual. This kind of install may be useful for users with otherwise -unsupported hardware or on hosts which can't afford downtime. If you -are interested in this technique, skip to the <xref -linkend="linux-upgrade"/>. - -</para> - </sect2> - - <sect2><title>Supported Storage Systems</title> - -<para> - -The &debian; boot disks contain a kernel which is built to maximize the -number of systems it runs on. Unfortunately, this makes for a larger -kernel, which includes many drivers that won't be used for your -machine<phrase arch="linux-any"> (see <xref linkend="kernel-baking"/> to learn how to -build your own kernel)</phrase>. Support for the widest possible range of -devices is desirable in general, to ensure that &debian; can be -installed on the widest array of hardware. - -</para><para arch="x86"> - -Generally, the &debian; installation system includes support for floppies, -IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA -and SCSI controllers and drives, USB, and FireWire. The supported file systems -include FAT, Win-32 FAT extensions (VFAT) and NTFS. - -</para><para arch="i386"> - -Disk interfaces that emulate the <quote>AT</quote> hard disk interface -— often called MFM, RLL, IDE, or PATA — are supported. SATA and -SCSI disk controllers from many different manufacturers are supported. See the -<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> -for more details. - -</para><para arch="sparc"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. The following SCSI drivers are supported in the default -kernel: - -<itemizedlist> -<listitem><para> - -Sparc ESP - -</para></listitem> -<listitem><para> - -PTI Qlogic,ISP - -</para></listitem> -<listitem><para> - -Adaptec AIC7xxx - -</para></listitem> -<listitem><para> - -NCR and Symbios 53C8XX - -</para></listitem> -</itemizedlist> - -IDE systems (such as the UltraSPARC 5) are also supported. See -<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink> -for more information on SPARC hardware supported by the Linux kernel. - -</para><para arch="powerpc"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. Note that the current Linux kernel does not support -floppies on CHRP systems at all. - -</para><para arch="hppa"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. Note that the current Linux kernel does not support -the floppy drive. - -</para><para arch="mips;mipsel"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. - -</para><para arch="s390"> - -Any storage system supported by the Linux kernel is also supported by -the boot system. This means that FBA and ECKD DASDs are supported with -the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl). - -</para> - - </sect2> - - </sect1> diff --git a/nl/hardware/memory-disk-requirements.xml b/nl/hardware/memory-disk-requirements.xml deleted file mode 100644 index a862dc997..000000000 --- a/nl/hardware/memory-disk-requirements.xml +++ /dev/null @@ -1,33 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - <sect1 id="memory-disk-requirements"> - <title>Memory and Disk Space Requirements</title> - -<para> - -You must have at least &minimum-memory; of memory and &minimum-fs-size; -of hard disk space to perform a normal installation. Note that these are -fairly minimal numbers. For more realistic figures, see -<xref linkend="minimum-hardware-reqts"/>. - -</para><para> - -Installation on systems with less memory<footnote condition="gtk"> - -<para> - -Installation images that support the graphical installer require more -memory than images that support only the textual installer and should -not be used on systems with less than &minimum-memory; of memory. If -there is a choice between booting the regular and the graphical installer, -the former should be selected. - -</para> - -</footnote> or disk space available may be possible but is only advised for -experienced users. - -</para> - - </sect1> diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml deleted file mode 100644 index e03bcb7b8..000000000 --- a/nl/hardware/network-cards.xml +++ /dev/null @@ -1,184 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61626 untranslated --> - - <sect2 id="network-cards"> - <title>Network Connectivity Hardware</title> -<para> - -Almost any network interface card (NIC) supported by the &arch-kernel; kernel -should also be supported by the installation system; modular drivers -should normally be loaded automatically. - -<phrase arch="x86">This includes most PCI and PCMCIA cards.</phrase> -<phrase arch="i386">Many older ISA cards are supported as well.</phrase> - -</para><para arch="sparc"> - -This includes a lot of generic PCI cards (for systems that have PCI) and -the following NICs from Sun: - -<itemizedlist> -<listitem><para> - -Sun LANCE - -</para></listitem> -<listitem><para> - -Sun Happy Meal - -</para></listitem> -<listitem><para> - -Sun BigMAC - -</para></listitem> -<listitem><para> - -Sun QuadEthernet - -</para></listitem> -<listitem><para> - -MyriCOM Gigabit Ethernet - -</para></listitem> -</itemizedlist> - -</para><para arch="s390"> - -The list of supported network devices is: - -<itemizedlist> - <listitem><para> - -Channel to Channel (CTC) and ESCON connection (real or emulated) - -</para></listitem> - <listitem><para> - -OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO) - -</para></listitem> -<listitem><para> - -OSA-Express in QDIO mode, HiperSockets and Guest-LANs - -</para></listitem> -</itemizedlist> - -</para> - -<para arch="arm"> - -On &arch-title;, most built-in Ethernet devices are supported and modules -for additional PCI and USB devices are provided. The major exception is -the IXP4xx platform (featuring devices such as the Linksys NSLU2) which -needs a proprietary microcode for the operation of its built-in Ethernet -device. Unofficial images for Linksys NSLU2 with this proprietary -microcode can be obtained from the <ulink -url="&url-slug-firmware;">Slug-Firmware site</ulink>. - -</para><para arch="x86"> - -ISDN is supported, but not during the installation. - -</para> - - <sect3 condition="supports-wireless" id="nics-wireless"> - <title>Wireless Network Cards</title> -<para> - -Wireless networking is in general supported as well and a growing number of -wireless adapters are supported by the official &arch-kernel; kernel, although many -of them do require firmware to be loaded. If firmware is needed, the installer -will prompt you to load firmware. See <xref linkend="loading-firmware"/> -for detailed information on how to load firmware during the installation. - -</para><para> - -Wireless NICs that are not supported by the official &arch-kernel; kernel can generally -be made to work under &debian-gnu;, but are not supported during the installation. - -</para><para> - -Support for encrypted wireless during installation is currently limited to WEP. -If your access point uses stronger encryption, it cannot be used during the -installation process. - -</para><para> - -If there is a problem with wireless and there -is no other NIC you can use during the installation, it is still -possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the -option to not configure a network and install using only the packages -available from the CD/DVD. You can then install the driver and firmware you -need after the installation is completed (after the reboot) and configure -your network manually. - -</para><para> - -In some cases the driver you need may not be available as a &debian; package. -You will then have to look if there is source code available in the internet -and compile the driver yourself. How to do this is outside the scope of this -manual. -<phrase arch="x86">If no Linux driver is available, your last resort is to -use the <classname>ndiswrapper</classname> package, which allows you to use -a Windows driver.</phrase> - -</para> - </sect3> - - <sect3 arch="sparc" id="nics-sparc-trouble"> - <title>Known Issues for &arch-title;</title> -<para> - -There are a couple of issues with specific network cards that are worth -mentioning here. - -</para> - - <sect4><title>Conflict between tulip and dfme drivers</title> -<!-- BTS: #334104; may also affect other arches, but most common on sparc --> -<para> - -<!-- BTS: #334104; may also affect other arches, but most common on sparc --> -There are various PCI network cards that have the same PCI identification, -but are supported by related, but different drivers. Some cards work with -the <literal>tulip</literal> driver, others with the <literal>dfme</literal> -driver. Because they have the same identification, the kernel cannot -distinguish between them and it is not certain which driver will be loaded. -If this happens to be the wrong one, the NIC may not work, or work badly. - -</para><para> - -This is a common problem on Netra systems with a Davicom (DEC-Tulip -compatible) NIC. In that case the <literal>tulip</literal> driver is -probably the correct one. -You can prevent this issue by blacklisting the wrong driver module as -described in <xref linkend="module-blacklist"/>. - -</para><para> - -An alternative solution during the installation is to switch to a shell -and unload the wrong driver module using -<userinput>modprobe -r <replaceable>module</replaceable></userinput> (or -both, if they are both loaded). After that you can load the correct module -using <userinput>modprobe <replaceable>module</replaceable></userinput>. -Note that the wrong module may then still be loaded when the system is -rebooted. - -</para> - </sect4> - - <sect4><title>Sun B100 blade</title> -<!-- BTS: #384549; should be checked for kernels >2.6.18 --> -<para> - -The <literal>cassini</literal> network driver does not work with Sun B100 -blade systems. - -</para> - </sect4> - </sect3> - </sect2> diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml deleted file mode 100644 index 799e12666..000000000 --- a/nl/hardware/supported-peripherals.xml +++ /dev/null @@ -1,36 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59840 untranslated --> - - <sect2 id="supported-peripherals"> - <title>Peripherals and Other Hardware</title> -<para arch="not-s390"> - -&arch-kernel; supports a large variety of hardware devices such as mice, -printers, scanners, PCMCIA and USB devices. However, most of these -devices are not required while installing the system. - -</para><para arch="x86"> - -USB hardware generally works fine, only some -USB keyboards may require additional configuration -(see <xref linkend="hardware-issues"/>). - -</para><para arch="x86"> - -Again, see the -<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> -to determine whether your specific hardware is supported by Linux. - -</para><para arch="s390"> - -Package installations from XPRAM and tape are not supported by this -system. All packages that you want to install need to be available on a -DASD or over the network using NFS, HTTP or FTP. - -</para><para arch="mipsel"> - -The Cobalt RaQ has no support for additional devices but the Qube has one -PCI slot. - -</para> - </sect2> diff --git a/nl/hardware/supported/amd64.xml b/nl/hardware/supported/amd64.xml deleted file mode 100644 index 946ecaaeb..000000000 --- a/nl/hardware/supported/amd64.xml +++ /dev/null @@ -1,34 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> - - - <sect2 arch="amd64"><title>CPU, Main Boards, and Video Support</title> -<para> - -Complete information concerning supported peripherals can be found at -<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>. -This section merely outlines the basics. - -</para> - - <sect3><title>CPU</title> -<para> - -Both AMD64 and Intel EM64t processors are supported. - -</para> - </sect3> - -<!-- Not sure if this is relevant for AMD64; AFAIK only PCI supported - <sect3 id="bus"><title>I/O Bus</title> -<para> - -The system bus is the part of the motherboard which allows the CPU to -communicate with peripherals such as storage devices. Your computer -must use the PCI bus. - -</para> - </sect3> ---> - </sect2> - diff --git a/nl/hardware/supported/arm.xml b/nl/hardware/supported/arm.xml deleted file mode 100644 index eae55aa2d..000000000 --- a/nl/hardware/supported/arm.xml +++ /dev/null @@ -1,104 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61324 untranslated --> - - - <sect2 arch="arm"><title>CPU, Main Boards, and Video Support</title> - -<para> - -Each distinct ARM architecture requires its own kernel. Because of -this the standard &debian; distribution only supports installation on -a number of the most common platforms. The &debian; userland however may be -used by <emphasis>any</emphasis> ARM CPU. - -</para> - -<para> - -Most ARM CPUs may be run in either endian mode (big or little). However, -the majority of current system implementation uses little-endian mode. -&debian; currently only supports little-endian ARM systems. - -</para> - -<para> - -The supported platforms are: - -<variablelist> - -<varlistentry> -<term>IOP32x</term> -<listitem><para> - -Intel's I/O Processor (IOP) line is found in a number of products related -to data storage and processing. &debian; currently supports the IOP32x -platform, featuring the IOP 80219 and 32x chips commonly found in Network -Attached Storage (NAS) devices. &debian; explicitly supports two such -devices: the <ulink url="&url-arm-cyrius-glantank;">GLAN Tank</ulink> from -IO-Data and the <ulink url="&url-arm-cyrius-n2100;">Thecus N2100</ulink>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>IXP4xx</term> -<listitem><para> - -The IXP4xx platform is based on Intel's XScale ARM core. Currently, only -one IXP4xx based system is supported, the Linksys NSLU2. -The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small -device which allows you to easily provide storage via the network. It -comes with an Ethernet connection and two USB ports to which hard drives -can be connected. There is an external site with <ulink -url="&url-arm-cyrius-nslu2;">installation instructions</ulink>. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Kirkwood</term> -<listitem><para> - -Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM -CPU, Ethernet, SATA, USB, and other functionality in one chip. We -currently support the following Kirkwood based devices: OpenRD (OpenRD-Base -and OpenRD-Client), <ulink -url="&url-arm-cyrius-sheevaplug;">SheevaPlug</ulink> and <ulink -url="&url-arm-cyrius-qnap-kirkwood;">QNAP Turbo Station</ulink> (TS-110, -TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet -supported). - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Orion5x</term> -<listitem><para> - -Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, -Ethernet, SATA, USB, and other functionality in one chip. There are many -Network Attached Storage (NAS) devices on the market that are based on an -Orion chip. We currently support the following Orion based devices: <ulink -url="&url-arm-cyrius-kuroboxpro;">Buffalo Kurobox</ulink>, <ulink -url="&url-arm-cyrius-mv2120;">HP mv2120</ulink>, <ulink -url="&url-arm-cyrius-qnap;">QNAP Turbo Station</ulink> (TS-109, TS-209 and -TS-409). - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Versatile</term> -<listitem><para> - -The Versatile platform is emulated by QEMU and is therefore a nice way to -test and run &debian; on ARM if you don't have the hardware. - -</para></listitem> -</varlistentry> - -</variablelist> - -</para> - </sect2> diff --git a/nl/hardware/supported/hppa.xml b/nl/hardware/supported/hppa.xml deleted file mode 100644 index 47578abcb..000000000 --- a/nl/hardware/supported/hppa.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 41452 untranslated --> - - - <sect2 arch="hppa"><title>CPU, Main Boards, and Video Support</title> -<para> - -There are two major support <emphasis>&architecture;</emphasis> flavors: -PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted -at 32-bit processors whereas the 2.0 architecture is targeted to -the 64-bit processors. Some systems are able to run either kernel. -In both cases, the userland is 32-bit. There is the possibility of -a 64-bit userland in the future. - -</para> - </sect2> - diff --git a/nl/hardware/supported/i386.xml b/nl/hardware/supported/i386.xml deleted file mode 100644 index baa209b29..000000000 --- a/nl/hardware/supported/i386.xml +++ /dev/null @@ -1,76 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56248 untranslated --> - - - <sect2 arch="i386"><title>CPU, Main Boards, and Video Support</title> -<para> - -Complete information concerning supported peripherals can be found at -<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink>. -This section merely outlines the basics. - -</para> - - <sect3><title>CPU</title> -<para> - -Nearly all x86-based (IA-32) processors still in use in personal computers -are supported, including all varieties of Intel's "Pentium" series. -This also includes 32-bit AMD and VIA (former Cyrix) processors, and -processors like the Athlon XP and Intel P4 Xeon. - -</para><para> - -However, &debian; GNU/Linux &releasename; will <emphasis>not</emphasis> run -on 386 or earlier processors. Despite the architecture name "i386", support -for actual 80386 processors (and their clones) was dropped with the Sarge -(r3.1) release of &debian;<footnote> - -<para> -We have long tried to avoid this, but in the end it was necessary due a -unfortunate series of issues with the compiler and the kernel, starting -with an bug in the C++ ABI provided by GCC. You should still be able to -run &debian; GNU/Linux on actual 80386 processors if you compile your own -kernel and compile all packages from source, but that is beyond the -scope of this manual. -</para> - -</footnote>. (No version of Linux has ever supported the 286 or earlier -chips in the series.) All i486 and later processors are still -supported<footnote> - -<para> - -Many &debian; packages will actually run slightly faster on modern computers -as a positive side effect of dropping support for these old chips. The -i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) -which the i386, introduced in 1986, did not have. Previously, these could not -be easily used by most &debian; packages; now they can. - -</para> - -</footnote>. - -</para> -<note><para> - -If your system has a 64-bit processor from the AMD64 or Intel EM64T families, -you will probably want to use the installer for the amd64 architecture instead -of the installer for the (32-bit) i386 architecture. - -</para></note> - </sect3> - - <sect3 id="bus"><title>I/O Bus</title> -<para> - -The system bus is the part of the motherboard which allows the CPU to -communicate with peripherals such as storage devices. Your computer -must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL -bus). Essentially all personal computers sold in recent years use one -of these. - -</para> - </sect3> - </sect2> - diff --git a/nl/hardware/supported/ia64.xml b/nl/hardware/supported/ia64.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/nl/hardware/supported/ia64.xml +++ /dev/null @@ -1,3 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - diff --git a/nl/hardware/supported/mips.xml b/nl/hardware/supported/mips.xml deleted file mode 100644 index 91f95d973..000000000 --- a/nl/hardware/supported/mips.xml +++ /dev/null @@ -1,56 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59840 untranslated --> - - - <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title> -<para> - -&debian; on &arch-title; supports the following platforms: - -<itemizedlist> -<listitem><para> - -SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and -Challenge S. Since these machines are very similar, whenever this document -refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. - -</para></listitem> -<listitem><para> - -SGI IP32: this platform is generally known as SGI O2. - -</para></listitem> -<listitem><para> - -MIPS Malta: this platform is emulated by QEMU and is therefore a nice way -to test and run &debian; on MIPS if you don't have the hardware. - -</para></listitem> -</itemizedlist> - -Complete information regarding supported mips/mipsel machines can be found -at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the -following, only the systems supported by the &debian; installer will be -covered. If you are looking for support for other subarchitectures, please -contact the <ulink url="&url-list-subscribe;"> -debian-&arch-listname; mailing list</ulink>. - -</para> - - <sect3><title>CPU</title> -<para> - -On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 -processors are supported by the &debian; installation system on big endian -MIPS. On SGI IP32, currently only systems based on the R5000 are supported. - -</para><para> - -Some MIPS machines can be operated in both big and little endian mode. For -little endian MIPS, please read the documentation for the mipsel -architecture. - -</para> - </sect3> - </sect2> - diff --git a/nl/hardware/supported/mipsel.xml b/nl/hardware/supported/mipsel.xml deleted file mode 100644 index 4ba800a5c..000000000 --- a/nl/hardware/supported/mipsel.xml +++ /dev/null @@ -1,51 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59840 untranslated --> - - - <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title> -<para> - -&debian; on &arch-title; supports the following platforms: - -<itemizedlist> -<listitem><para> - -Cobalt Microserver: only MIPS based Cobalt machines are covered here. This -includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. - -</para></listitem> -<listitem><para> - -MIPS Malta: this platform is emulated by QEMU and is therefore a nice way -to test and run &debian; on MIPS if you don't have the hardware. - -</para></listitem> -</itemizedlist> - -Complete information regarding supported mips/mipsel machines can be found -at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the -following, only the systems supported by the &debian; installer will be -covered. If you are looking for support for other subarchitectures, please -contact the <ulink url="&url-list-subscribe;"> -debian-&arch-listname; mailing list</ulink>. - -</para> - - <sect3><title>CPU/Machine types</title> - -<para> - -All MIPS based Cobalt machines are supported with the exception of the -Qube 2700 (Qube 1). - -</para> - </sect3> - - <sect3><title>Supported console options</title> -<para> - -Cobalt machines use 115200 bps. - -</para> - </sect3> - </sect2> diff --git a/nl/hardware/supported/powerpc.xml b/nl/hardware/supported/powerpc.xml deleted file mode 100644 index bb146b54a..000000000 --- a/nl/hardware/supported/powerpc.xml +++ /dev/null @@ -1,428 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56248 untranslated --> - - - <sect2 arch="powerpc"><title>CPU, Main Boards, and Video Support</title> -<para> - -For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP -subarchitectures are supported. - -<!-- -There are four major supported <emphasis>&architecture;</emphasis> -subarchitectures: PMac (Power-Macintosh or PowerMac), PReP, APUS (Amiga -Power-UP System), and CHRP machines. Each subarchitecture has its own boot -methods. In addition, there are four different kernel flavours, -supporting different CPU variants. - -</para><para> - -Ports to other <emphasis>&architecture;</emphasis> architectures, such -as the Be-Box and MBX architecture, are underway but not yet supported -by &debian;. We may have a 64-bit port in the future. ---> - -</para> - - <sect3><title>Kernel Flavours</title> - -<para> - -There are two flavours of the powerpc kernel in &debian;, based on the -CPU type: - -<variablelist> -<varlistentry> -<term>powerpc</term> -<listitem><para> - -Most systems use this kernel flavour, which supports the PowerPC 601, -603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines -up to and including the one marketed as G4 use one of these processors. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>power64</term> -<listitem><para> - -The power64 kernel flavour supports the following CPUs: - -</para><para> - -The POWER3 processor is used in older IBM 64-bit server systems: known -models include the IntelliStation POWER Model 265, the pSeries 610 and -640, and the RS/6000 7044-170, 7043-260, and 7044-270. - -</para><para> - -The POWER4 processor is used in more recent IBM 64-bit server systems: -known models include the pSeries 615, 630, 650, 655, 670, and 690. - -</para><para> - -Systems using the Apple G5 (PPC970FX processor) are also based on the -POWER4 architecture, and use this kernel flavour. - -</para></listitem> -</varlistentry> - -<!-- -<varlistentry> -<term>prep</term> -<listitem><para> - -This kernel flavour supports the PReP subarchitecture. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>apus</term> -<listitem><para> - -This kernel flavour supports the Amiga Power-UP System, though it is -currently disabled. - -</para></listitem> -</varlistentry> ---> -</variablelist> - -</para> - - </sect3> - - <sect3><title>Power Macintosh (pmac) subarchitecture</title> - -<para> - -Apple (and briefly a few other manufacturers — Power Computing, for -example) made a series of Macintosh computers based on the PowerPC -processor. For purposes of architecture support, they are categorized -as NuBus (not supported by &debian;), OldWorld, and NewWorld. - -</para><para> - -OldWorld systems are most Power Macintoshes with a floppy drive and a -PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are -OldWorld machines. Those pre-iMac PowerPC models from Apple use a -four digit naming scheme, except for the beige colored G3 systems, which -are also OldWorld. - -</para><para> - -The so called NewWorld PowerMacs are any PowerMacs in translucent -colored plastic cases and later models. That includes all iMacs, iBooks, -G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and -after 1999. The NewWorld PowerMacs are also known for using the <quote>ROM in -RAM</quote> system for MacOS, and were manufactured from mid-1998 onwards. - -</para><para> - -Specifications for Apple hardware are available at -<ulink url="http://www.info.apple.com/support/applespec.html">AppleSpec</ulink>, -and, for older hardware, -<ulink url="http://www.info.apple.com/support/applespec.legacy/index.html">AppleSpec Legacy</ulink>. - -</para><para> - -<informaltable> -<tgroup cols="3"> -<colspec colname="c1"/> -<colspec colname="c2"/> -<colspec colname="c3"/> -<thead> -<row> - <entry namest="c1" nameend="c2">Model Name/Number</entry> - <entry>Generation</entry> -</row> -</thead> - -<tbody> -<row> - <entry morerows="27">Apple</entry> - <entry>iMac Bondi Blue, 5 Flavors, Slot Loading</entry> - <entry>NewWorld</entry> -</row><row> - <entry>iMac Summer 2000, Early 2001</entry> - <entry>NewWorld</entry> -</row><row> - <entry>iMac G5</entry> - <entry>NewWorld</entry> -</row><row> - <entry>iBook, iBook SE, iBook Dual USB</entry> - <entry>NewWorld</entry> -</row><row> - <entry>iBook2</entry> - <entry>NewWorld</entry> -</row><row> - <entry>iBook G4</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Power Macintosh Blue and White (B&W) G3</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Power Macintosh G4 PCI, AGP, Cube</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Power Macintosh G4 Gigabit Ethernet</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Power Macintosh G4 Digital Audio, Quicksilver</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Power Macintosh G5</entry> - <entry>NewWorld</entry> -</row><row> - <entry>PowerBook G3 FireWire Pismo (2000)</entry> - <entry>NewWorld</entry> -</row><row> - <entry>PowerBook G3 Lombard (1999)</entry> - <entry>NewWorld</entry> -</row><row> - <entry>PowerBook G4 Titanium</entry> - <entry>NewWorld</entry> -</row><row> - <entry>PowerBook G4 Aluminum</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Xserve G5</entry> - <entry>NewWorld</entry> -</row><row> - <entry>Performa 4400, 54xx, 5500</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Performa 6360, 6400, 6500</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Power Macintosh 4400, 5400</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Power Macintosh 7200, 7300, 7500, 7600</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Power Macintosh 8200, 8500, 8600</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Power Macintosh 9500, 9600</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Power Macintosh (Beige) G3 Minitower</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Power Macintosh (Beige) Desktop, All-in-One</entry> - <entry>OldWorld</entry> -</row><row> - <entry>PowerBook 2400, 3400, 3500</entry> - <entry>OldWorld</entry> -</row><row> - <entry>PowerBook G3 Wallstreet (1998)</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Twentieth Anniversary Macintosh</entry> - <entry>OldWorld</entry> -</row><row> - <entry>Workgroup Server 7250, 7350, 8550, 9650, G3</entry> - <entry>OldWorld</entry> -</row> - -<row> - <entry morerows="1">Power Computing</entry> - <entry>PowerBase, PowerTower / Pro, PowerWave</entry> - <entry>OldWorld</entry> -</row><row> - <entry>PowerCenter / Pro, PowerCurve</entry> - <entry>OldWorld</entry> -</row> - -<row> - <entry>UMAX</entry> - <entry>C500, C600, J700, S900</entry> - <entry>OldWorld</entry> -</row> - -<row> - <entry>APS</entry> - <entry>APS Tech M*Power 604e/2000</entry> - <entry>OldWorld</entry> -</row> - -<row> - <entry>Motorola</entry> - <entry>Starmax 3000, 4000, 5000, 5500</entry> - <entry>OldWorld</entry> -</row> -</tbody></tgroup></informaltable> - -</para> - - </sect3> - - <sect3><title>PReP subarchitecture</title> - -<para> - -<informaltable> -<tgroup cols="2"> -<colspec colname="c1"/> -<colspec colname="c2"/> -<thead> -<row> - <entry namest="c1" nameend="c2">Model Name/Number</entry> -</row> -</thead> - -<tbody> -<row> - <entry morerows="4">Motorola</entry> - <entry>Firepower, PowerStack Series E, PowerStack II</entry> -</row><row> - <entry>MPC 7xx, 8xx</entry> -</row><row> - <entry>MTX, MTX+</entry> -</row><row> - <entry>MVME2300(SC)/24xx/26xx/27xx/36xx/46xx</entry> -</row><row> - <entry>MCP(N)750</entry> -</row> - -<row> - <entry morerows="3">IBM RS/6000</entry> - <entry>40P, 43P</entry> -</row><row> - <entry>Power 830/850/860 (6070, 6050)</entry> -</row><row> - <entry>6030, 7025, 7043</entry> -</row><row> - <entry>p640</entry> -</row> -</tbody></tgroup></informaltable> - -</para> - - </sect3> - - <sect3><title>CHRP subarchitecture (unsupported)</title> - -<para> - -<informaltable> -<tgroup cols="2"> -<colspec colname="c1"/> -<colspec colname="c2"/> -<thead> -<row> - <entry namest="c1" nameend="c2">Model Name/Number</entry> -</row> -</thead> - -<tbody> -<row> - <entry>IBM RS/6000</entry> - <entry>B50, 43P-150, 44P</entry> -</row> -<row> - <entry>Genesi</entry> - <entry>Pegasos I, Pegasos II</entry> -</row> -</tbody></tgroup></informaltable> - -</para> - - </sect3> - - <sect3><title>APUS subarchitecture (unsupported)</title> - -<para> - -<informaltable> -<tgroup cols="2"> -<colspec colname="c1"/> -<colspec colname="c2"/> -<thead> -<row> - <entry namest="c1" nameend="c2">Model Name/Number</entry> -</row> -</thead> - -<tbody> -<row> - <entry>Amiga Power-UP Systems (APUS)</entry> - <entry>A1200, A3000, A4000</entry> -</row> -</tbody></tgroup></informaltable> - -</para> - - </sect3> - - <sect3><title>Nubus PowerMac subarchitecture (unsupported)</title> - -<para> - -NuBus systems are not currently supported by &debian;/powerpc. The -monolithic Linux/PPC kernel architecture does not have support for -these machines; instead, one must use the MkLinux Mach microkernel, -which &debian; does not yet support. These include the following: - -<itemizedlist> -<listitem><para> - -Power Macintosh 6100, 7100, 8100 - -</para></listitem> -<listitem><para> - -Performa 5200, 6200, 6300 - -</para></listitem> -<listitem><para> - -Powerbook 1400, 2300, and 5300 - -</para></listitem> -<listitem><para> - -Workgroup Server 6150, 8150, 9150 - -</para></listitem> -</itemizedlist> - -A linux kernel for these machines and limited support is available at -<ulink url="http://nubus-pmac.sourceforge.net/"></ulink>. - -</para> - - </sect3> - - <sect3><title>Non-PowerPC Macs</title> - -<para> - -Macintosh computers using the 680x0 series of processors are -<emphasis>not</emphasis> in the PowerPC family but are instead m68k -machines. Those models start with <quote>Mac II</quote> series, go on -to the <quote>LC</quote> family, then the Centris series, and culminate -in the Quadras and Performas. These models usually have a Roman numeral -or 3-digit model number such as Mac IIcx, LCIII or Quadra 950. - -</para><para> - -This model range started with the Mac II (Mac II, IIx, IIcx, IIci, -IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, -550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, -660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, -950), and finally the Performa 200-640CD. - -</para><para> - -In laptops, it started with the Mac Portable, then the PowerBook -100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 -which is Nubus, please see the section above). - -</para> - - </sect3> - </sect2> diff --git a/nl/hardware/supported/s390.xml b/nl/hardware/supported/s390.xml deleted file mode 100644 index 237674566..000000000 --- a/nl/hardware/supported/s390.xml +++ /dev/null @@ -1,21 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39895 untranslated --> - - - <sect2 arch="s390"><title>S/390 and zSeries machine types</title> -<para> - -Complete information regarding supported S/390 and zSeries machines can -be found in IBM's Redbook -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> -Linux for IBM eServer zSeries and S/390: Distributions</ulink> in -chapter 2.1 or at the -<ulink url="http://www-128.ibm.com/developerworks/linux/linux390/index.html">zSeries -page at the developerWorks</ulink>. -In short, G5, Multiprise 3000, G6 and all zSeries are fully supported; -Multiprise 2000, G3 and G4 machines are supported with IEEE floating -point emulation and thus degraded performance. - -</para> - </sect2> - diff --git a/nl/hardware/supported/sparc.xml b/nl/hardware/supported/sparc.xml deleted file mode 100644 index 5d02c340b..000000000 --- a/nl/hardware/supported/sparc.xml +++ /dev/null @@ -1,70 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 49849 untranslated --> - - <sect2 arch="sparc" id="sparc-cpus"> - <title>CPU and Main Boards Support</title> -<para> - -Sparc-based hardware is divided into a number of different subarchitectures, -identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u -or sun4v. The following list describes what machines they include and what -level of support may be expected for each of them. - -</para> - -<variablelist> -<varlistentry> -<term>sun4, sun4c, sun4d, sun4m</term> - -<listitem><para> - -None of these 32-bit sparc subarchitectures (sparc32) is supported. For a -complete list of machines belonging to these subarchitectures, please consult -the <ulink url="http://en.wikipedia.org/wiki/SPARCstation">Wikipedia -SPARCstation page</ulink>. - -</para><para> - -The last &debian; release to support sparc32 was Etch, but even then only -for sun4m systems. Support for the other 32-bits subarchitectures had -already been discontinued after earlier releases. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>sun4u</term> - -<listitem><para> - -This subarchitecture includes all 64-bit machines (sparc64) based on -the UltraSparc processor and its clones. Most of the machines are well -supported, even though for some you may experience problems booting from -CD due to firmware or bootloader bugs (this problem may be worked around -by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP -configurations respectively. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>sun4v</term> - -<listitem><para> - -This is the newest addition to the Sparc family, which includes machines -based on the Niagara multi-core CPUs. At the moment such CPUs are only -available in T1000 and T2000 servers by Sun, and are well supported. Use -the sparc64-smp kernel. - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not -supported due to lack of support in the Linux kernel. - -</para> - </sect2> diff --git a/nl/howto/installation-howto.xml b/nl/howto/installation-howto.xml deleted file mode 100644 index 9665efa82..000000000 --- a/nl/howto/installation-howto.xml +++ /dev/null @@ -1,357 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56151 untranslated --> - -<appendix id="installation-howto"> -<title>Installation Howto</title> - -<para> - -This document describes how to install &debian-gnu; &releasename; for -the &arch-title; (<quote>&architecture;</quote>) with the -new &d-i;. It is a quick walkthrough of the installation process -which should contain all the information you will need for most installs. -When more information can be useful, we will link to more detailed -explanations in other parts of this document. - -</para> - - <sect1 id="howto-preliminaries"> - <title>Preliminaries</title> -<para> - -<phrase condition="unofficial-build"> -The debian-installer is still in a beta state. -</phrase> -If you encounter bugs during your install, please refer to -<xref linkend="submit-bug" /> for instructions -on how to report them. If you have questions which cannot be -answered by this document, please direct them to the debian-boot -mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot -on the OFTC network). - -</para> - </sect1> - - <sect1 id="howto-getting-images"> - <title>Booting the installer</title> -<para> - -<phrase condition="unofficial-build"> -For some quick links to CD images, check out the <ulink url="&url-d-i;"> -&d-i; home page</ulink>. -</phrase> -The debian-cd team provides builds of CD images using &d-i; on the -<ulink url="&url-debian-cd;">Debian CD page</ulink>. -For more information on where to get CDs, see <xref linkend="official-cdrom" />. - -</para><para> - -Some installation methods require other images than CD images. -<phrase condition="unofficial-build"> -The <ulink url="&url-d-i;">&d-i; home page</ulink> has links to -other images. -</phrase> -<xref linkend="where-files" /> explains how to find images on &debian; -mirrors. - -</para><para> - -The subsections below will give the details about which images you should -get for each possible means of installation. - -</para> - - <sect2 id="howto-getting-images-cdrom"> - <title>CDROM</title> - -<para> - -There are two different netinst CD images which can be used to install -&releasename; with the &d-i;. These images are intended to boot from CD -and install additional packages over a network, hence the name 'netinst'. -The difference between the two images is that on the full netinst image -the base packages are included, whereas you have to download these from -the web if you are using the business card image. If you'd rather, you can -get a full size CD image which will not need the network to install. You -only need the first CD of the set. - -</para><para> - -Download whichever type you prefer and burn it to a CD. -<phrase arch="any-x86">To boot the CD, you may need to change your BIOS -configuration, as explained in <xref linkend="bios-setup" />.</phrase> -<phrase arch="powerpc"> -To boot a PowerMac from CD, press the <keycap>c</keycap> key while booting. See -<xref linkend="boot-cd" /> for other ways to boot from CD. -</phrase> - -</para> - </sect2> - - <sect2 condition="supports-floppy-boot" id="howto-getting-images-floppy"> - <title>Floppy</title> -<para> - -If you can't boot from CD, you can download floppy images to install -&debian;. You need the <filename>floppy/boot.img</filename>, the -<filename>floppy/root.img</filename> and one or more of the driver disks. - -</para><para> - -The boot floppy is the one with <filename>boot.img</filename> on it. -This floppy, when booted, will prompt you to insert a second floppy — -use the one with <filename>root.img</filename> on it. - -</para><para> - -If you're planning to install over the network, you will usually need -the <filename>floppy/net-drivers-1.img</filename>. For PCMCIA or USB -networking, and some less common network cards, you will also need a second -driver floppy, <filename>floppy/net-drivers-2.img</filename>. - -</para><para> - -If you have a CD, but cannot boot from it, then boot from floppies and use -<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the -install using the CD. - -</para><para> - -Floppy disks are one of the least reliable media around, so be prepared for -lots of bad disks (see <xref linkend="unreliable-floppies" />). Each -<filename>.img</filename> file you downloaded goes on a single floppy; -you can use the dd command to write it to /dev/fd0 or some other means -(see <xref linkend="create-floppy" /> for details). -Since you'll have more than one floppy, it's a good idea to label them. - -</para> - </sect2> - - <sect2 condition="bootable-usb" id="howto-getting-images-usb"> - <title>USB memory stick</title> -<para> - -It's also possible to install from removable USB storage devices. For -example a USB keychain can make a handy &debian; install medium that you -can take with you anywhere. - -</para><para> - -The easiest way to prepare your USB memory stick is to download -<filename>hd-media/boot.img.gz</filename>, and use gunzip to extract the 256 MB -image from that file. Write this image directly to your memory stick, which -must be at least 256 mb in size. Of course this will destroy anything already -on the memory stick. Then mount the memory stick, which will now have a FAT -filesystem on it. Next, download a &debian; netinst CD image, and copy that file -to the memory stick; any filename is ok as long as it ends in -<literal>.iso</literal>. - -</para><para> - -There are other, more flexible ways to set up a memory stick to use the -debian-installer, and it's possible to get it to work with smaller memory -sticks. For details, see <xref linkend="boot-usb-files" />. - -</para><para arch="any-x86"> - -Some BIOSes can boot USB storage directly, and some cannot. You may need to -configure your BIOS to boot from a <quote>removable drive</quote> or even a -<quote>USB-ZIP</quote> to get it to boot from the USB device. For helpful -hints and details, see <xref linkend="usb-boot" />. - -</para><para arch="powerpc"> - -Booting Macintosh systems from USB storage devices involves manual use -of Open Firmware. For directions, see <xref linkend="usb-boot" />. - -</para> - </sect2> - - <sect2 id="howto-getting-images-netboot"> - <title>Booting from network</title> -<para> - -It's also possible to boot &d-i; completely from the net. The -various methods to netboot depend on your architecture and netboot setup. -The files in <filename>netboot/</filename> can be used to netboot &d-i;. - -</para><para arch="x86"> - -The easiest thing to set up is probably PXE netbooting. Untar the -file <filename>netboot/pxeboot.tar.gz</filename> into -<filename>/srv/tftp</filename> or -wherever is appropriate for your tftp server. Set up your DHCP server to pass -filename <filename>pxelinux.0</filename> to clients, and with luck -everything will just work. -For detailed instructions, see <xref linkend="install-tftp" />. - -</para> - </sect2> - - <sect2 arch="linux-any" id="howto-getting-images-hard-disk"> - <title>Booting from hard disk</title> -<para> - -It's possible to boot the installer using no removable media, but just an -existing hard disk, which can have a different OS on it. Download -<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</filename>, -and a &debian; CD image to the top-level directory of the hard disk. Make sure -that the CD image has a filename ending in <literal>.iso</literal>. Now -it's just a matter of booting linux with the initrd. -<phrase arch="x86"> -<xref linkend="boot-initrd" /> explains one way to do it. -</phrase> - -</para> - </sect2> - </sect1> - - <sect1 id="howto-installation"> -<title>Installation</title> -<para> - -Once the installer starts, you will be greeted with an initial screen. Press -&enterkey; to boot, or read the instructions for other boot -methods and parameters (see <xref linkend="boot-parms" />). - -</para><para> - -After a while you will be asked to select your language. Use the arrow keys -to pick a language and press &enterkey; to continue. Next you'll be asked to -select your country, with the choices including countries where your -language is spoken. If it's not on the short list, a list of all the -countries in the world is available. - -</para><para> - -You may be asked to confirm your keyboard layout. Choose the default unless -you know better. - -</para><para> - -Now sit back while debian-installer detects some of your hardware, and -loads the rest of itself from CD, floppy, USB, etc. - -</para><para> - -Next the installer will try to detect your network hardware and set up -networking by DHCP. If you are not on a network or do not have DHCP, you -will be given the opportunity to configure the network manually. - -</para><para> - -The next step is setting up your clock and time zone. The installer will -try to contact a time server on the Internet to ensure the clock is set -correctly. The time zone is based on the country selected earlier and the -installer will only ask to select one if a country has multiple zones. - -</para><para> - -Now it is time to partition your disks. First you will be given the -opportunity to automatically partition either an entire drive, or available -free space on a drive (see <xref linkend="partman-auto" />). -This is recommended for new users or anyone in a hurry. If you do not want -to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu. - -</para><para arch="any-x86"> - -If you have an existing DOS or Windows partition that you want to preserve, -be very careful with automatic partitioning. If you choose manual partitioning, -you can use the installer to resize existing FAT or NTFS partitions to create -room for the &debian; install: simply select the partition and specify its new size. - -</para><para> - -On the next screen you will see your partition table, how the partitions will -be formatted, and where they will be mounted. Select a partition to modify or -delete it. If you did automatic partitioning, you should just be able to choose -<guimenuitem>Finish partitioning and write changes to disk</guimenuitem> -from the menu to use what it set up. Remember to assign at least one partition -for swap space and to mount a partition on <filename>/</filename>. -For more detailed information on how to use the partitioner, please refer -to <xref linkend="di-partition" />; the appendix <xref -linkend="partitioning" /> has more general information about -partitioning. - -</para><para> - -Now &d-i; formats your partitions and starts to install the base system, -which can take a while. That is followed by installing a kernel. - -</para><para> - -The base system that was installed earlier is a working, but very minimal -installation. To make the system more functional the next step allows you -to install additional packages by selecting tasks. Before packages can be -installed <classname>apt</classname> needs to be configured as that defines -from where the packages will be retrieved. -The <quote>Standard system</quote> task will be selected by default and -should normally be installed. Select the <quote>Desktop environment</quote> -task if you would like to have a graphical desktop after the installation. -See <xref linkend="pkgsel"/> for additional information about this step. - -</para><para> - -Installation of the base system is followed by setting up user accounts. By -default you will need to provide a password for the <quote>root</quote> -(administrator) account and information necessary to create one regular user -account. - -</para><para> - -The last step is to install a boot loader. If the installer detects -other operating systems on your computer, it will add them to the boot menu -and let you know. -<phrase arch="any-x86">By default GRUB will be installed to the master boot -record of the first harddrive, which is generally a good choice. You'll be -given the opportunity to override that choice and install it elsewhere. -</phrase> - -</para><para> - -&d-i; will now tell you that the installation has -finished. Remove the cdrom or other boot media and hit &enterkey; to reboot -your machine. It should boot up into the newly installed system and -allow you to log in. This is explained in <xref linkend="boot-new"/>. - -</para><para> - -If you need more information on the install process, see -<xref linkend="d-i-intro" />. - -</para> - </sect1> - - <sect1 id="howto-installation-report"> - <title>Send us an installation report</title> -<para> - -If you successfully managed an installation with &d-i;, -please take time to provide us with a report. -The simplest way to do so is to install the reportbug package -(<command>aptitude install reportbug</command>), configure -<classname>reportbug</classname> as explained in -<xref linkend="mail-outgoing"/>, and run -<command>reportbug installation-reports</command>. - -</para><para> - -If you did not complete the install, you probably found a bug in -debian-installer. To improve the installer it is necessary that we know -about them, so please take the time to report them. You can use an -installation report to report problems; if the install completely fails, -see <xref linkend="problem-report" />. - -</para> - </sect1> - - <sect1 id="howto-installation-finally"> - <title>And finally…</title> -<para> - -We hope that your &debian; installation is pleasant and that you find &debian; -useful. You might want to read <xref linkend="post-install" />. - -</para> - </sect1> -</appendix> diff --git a/nl/install-methods/automatic-install.xml b/nl/install-methods/automatic-install.xml deleted file mode 100644 index 6aaddea31..000000000 --- a/nl/install-methods/automatic-install.xml +++ /dev/null @@ -1,34 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 33725 untranslated --> - - <sect1 id="automatic-install"> - <title>Automatic Installation</title> -<para> - -For installing on multiple computers it's possible to do fully -automatic installations. &debian; packages intended for this include -<classname>fai</classname> (which uses an install server), -<classname>replicator</classname>, -<classname>systemimager</classname>, -<classname>autoinstall</classname>, and -the &debian; Installer itself. - -</para> - - <sect2 id="preseed"> - <title>Automatic Installation Using the &debian; Installer</title> -<para> - -The &debian; Installer supports automating installs via preconfiguration -files. A preconfiguration file can be loaded from the network or from -removable media, and used to fill in answers to questions asked during the -installation process. - -</para><para> - -Full documentation on preseeding including a working example that you can -edit is in <xref linkend="appendix-preseed"/>. - -</para> - </sect2> - </sect1> diff --git a/nl/install-methods/boot-drive-files.xml b/nl/install-methods/boot-drive-files.xml deleted file mode 100644 index 22205ddd1..000000000 --- a/nl/install-methods/boot-drive-files.xml +++ /dev/null @@ -1,176 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> - - <sect1 condition="bootable-disk" id="boot-drive-files"> - <title>Preparing Files for Hard Disk Booting</title> -<para> - -The installer may be booted using boot files placed on an -existing hard drive partition, either launched from another operating -system or by invoking a boot loader directly from the BIOS. - -</para><para> - -A full, <quote>pure network</quote> installation can be achieved using this -technique. This avoids all hassles of removable media, like finding -and burning CD images or struggling with too numerous and -unreliable floppy disks. - -</para><para arch="x86"> - -The installer cannot boot from files on an NTFS file system. - -</para><para arch="powerpc"> - -The installer cannot boot from files on an HFS+ file system. MacOS -System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all -use HFS+. To determine whether your existing file system is HFS+, -select <userinput>Get Info</userinput> for the volume in question. HFS -file systems appear as <userinput>Mac OS Standard</userinput>, while -HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must -have an HFS partition in order to exchange files between MacOS and -Linux, in particular the installation files you download. - -</para><para arch="powerpc"> - -Different programs are used for hard disk installation system booting, -depending on whether the system is a <quote>NewWorld</quote> or an -<quote>OldWorld</quote> model. - -</para> - - <sect2 arch="x86" id="files-lilo"> - <title>Hard disk installer booting using <command>LILO</command> or - <command>GRUB</command></title> -<para> - -This section explains how to add to or even replace an existing linux -installation using either <command>LILO</command> or -<command>GRUB</command>. - -</para><para> - -At boot time, both bootloaders support loading in memory not -only the kernel, but also a disk image. This RAM disk can be used as -the root file-system by the kernel. - -</para><para> - -Copy the following files from the &debian; archives to a -convenient location on your hard drive, for instance to -<filename>/boot/newinstall/</filename>. - -<itemizedlist> -<listitem><para> - -<filename>vmlinuz</filename> (kernel binary) - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> (ramdisk image) - -</para></listitem> -</itemizedlist> - -</para><para> - -Finally, to configure the bootloader proceed to -<xref linkend="boot-initrd"/>. - -</para> - </sect2> - - - <sect2 arch="powerpc" id="files-oldworld"> - <title>Hard Disk Installer Booting for OldWorld Macs</title> -<para> - -The <filename>boot-floppy-hfs</filename> floppy uses -<application>miBoot</application> to launch Linux installation, but -<application>miBoot</application> cannot easily be used for hard disk -booting. <application>BootX</application>, launched from MacOS, -supports booting from files placed on the hard -disk. <application>BootX</application> can also be used to dual-boot -MacOS and Linux after your &debian; installation is complete. For the -Performa 6360, it appears that <command>quik</command> cannot make the -hard disk bootable. So <application>BootX</application> is required -on that model. - -</para><para> - -Download and unstuff the <application>BootX</application> -distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>, -or in the -<filename>dists/woody/main/disks-powerpc/current/powermac</filename> -directory on &debian; http/ftp mirrors and official &debian; CDs. Use -<application>Stuffit Expander</application> to extract it from its -archive. Within the package, there is an empty folder called -<filename>Linux Kernels</filename>. Download -<filename>linux.bin</filename> and -<filename>ramdisk.image.gz</filename> from the -<filename>disks-powerpc/current/powermac</filename> folder, and place -them in the <filename>Linux Kernels</filename> folder. Then place the -<filename>Linux Kernels</filename> folder in the active System Folder. - -</para> - </sect2> - - <sect2 arch="powerpc" id="files-newworld"> - <title>Hard Disk Installer Booting for NewWorld Macs</title> -<para> - -NewWorld PowerMacs support booting from a network or an ISO9660 -CD-ROM, as well as loading ELF binaries directly from the hard -disk. These machines will boot Linux directly via -<command>yaboot</command>, which supports loading a kernel and RAMdisk -directly from an ext2 partition, as well as dual-booting with -MacOS. Hard disk booting of the installer is particularly appropriate -for newer machines without floppy drives. <command>BootX</command> is -not supported and must not be used on NewWorld PowerMacs. - -</para><para> - -<emphasis>Copy</emphasis> (not move) the following four files which -you downloaded earlier from the &debian; archives, onto the root level -of your hard drive (this can be accomplished by -<keycap>option</keycap>-dragging each file to the hard drive icon). - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> - -</para></listitem> -</itemizedlist> - -</para><para> - -Make a note of the partition number of the MacOS partition where you -place these files. If you have the MacOS <command>pdisk</command> -program, you can use the <command>L</command> command to check for the -partition number. You will need this partition number for the command -you type at the Open Firmware prompt when you boot the installer. - -</para><para> - -To boot the installer, proceed to <xref linkend="boot-newworld"/>. - -</para> - </sect2> - </sect1> diff --git a/nl/install-methods/boot-usb-files.xml b/nl/install-methods/boot-usb-files.xml deleted file mode 100644 index afffe991d..000000000 --- a/nl/install-methods/boot-usb-files.xml +++ /dev/null @@ -1,159 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 57590 untranslated --> - - <sect1 condition="bootable-usb" id="boot-usb-files"> - <title>Preparing Files for USB Memory Stick Booting</title> - -<para> - -There are two installation methods possible when booting from USB stick. -The first is to install completely from the network. The second is to -also copy a CD image onto the USB stick and use that as a source for -packages, possibly in combination with a mirror. This second method is -the more common. - -</para><para> - -For the first installation method you'll need to download an installer -image from the <filename>netboot</filename> directory (at the location -mentioned in <xref linkend="where-files"/>) and use the -<quote>flexible way</quote> explained below to copy the files to the USB -stick. - -</para><para> - -Installation images for the second installation method can be found in -the <filename>hd-media</filename> directory and either the <quote>easy -way</quote> or the <quote>flexible way</quote> can be used to copy the -image to the USB stick. For this installation method you will also need -to download a CD image. The installation image and the CD image must be -based on the same release of &d-i;. If they do not match you are likely -to get errors<footnote> - -<para> -The error message that is most likely to be displayed is that no kernel -modules can be found. This means that the version of the kernel module -udebs included on the CD image is different from the version of the -running kernel. -</para> - -</footnote> during the installation. - -</para><para> - -To prepare the USB stick, you will need a system where GNU/Linux is -already running and where USB is supported. With current GNU/Linux systems -the USB stick should be automatically recognized when you insert it. If -it is not you should check that the usb-storage kernel module is loaded. -When the USB stick is inserted, it will be mapped to a device named -<filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter -in the range a-z. You should be able to see to which device the USB -stick was mapped by running the command <command>dmesg</command> after -inserting it. To write to your stick, you may have to turn off its write -protection switch. - -</para> -<warning><para> - -The procedures described in this section will destroy anything already -on the device! Make very sure that you use the correct device name for -your USB stick. If you use the wrong device the result could be that all -information on for example a hard disk could be lost. - -</para></warning> -<para> - -Note that the USB stick should be at least 256 MB in size (smaller -setups are possible if you follow <xref linkend="usb-copy-flexible"/>). - -</para> - - <sect2 id="usb-copy-easy"> - <title>Copying the files — the easy way</title> -<para> - -There is an all-in-one file <filename>hd-media/boot.img.gz</filename> -which contains all the installer files (including the kernel) -<phrase arch="x86">as well as <classname>syslinux</classname> and its -configuration file.</phrase> -<phrase arch="powerpc">as well as <classname>yaboot</classname> and its -configuration file.</phrase> - -</para><para> - -Note that, although convenient, this method does have one major -disadvantage: the logical size of the device will be limited to 256 MB, -even if the capacity of the USB stick is larger. You will need to -repartition the USB stick and create new file systems to get its full -capacity back if you ever want to use it for some different purpose. -A second disadvantage is that you cannot copy a full CD image onto -the USB stick, but only the smaller businesscard or netinst CD images. - -</para><para arch="x86"> - -To use this image simply extract it directly to your USB stick: - -<informalexample><screen> -# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable> -</screen></informalexample> - -</para><para arch="powerpc"> - -Create a partition of type "Apple_Bootstrap" on your USB stick using -<command>mac-fdisk</command>'s <userinput>C</userinput> command and -extract the image directly to that: - -<informalexample><screen> -# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable> -</screen></informalexample> - -</para><para> - -After that, mount the USB memory stick -<phrase arch="x86">(<userinput>mount -/dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> -<phrase arch="powerpc">(<userinput>mount -/dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> -which will now have -<phrase arch="x86">a FAT filesystem</phrase> -<phrase arch="powerpc">an HFS filesystem</phrase> -on it, and copy a &debian; netinst or businesscard ISO image to it. -Unmount the stick (<userinput>umount /mnt</userinput>) and you are done. - -</para> - </sect2> - - <sect2 id="usb-copy-flexible"> - <title>Copying the files — the flexible way</title> -<para> - -If you like more flexibility or just want to know what's going on, you -should use the following method to put the files on your stick. One -advantage of using this method is that — if the capacity of your -USB stick is large enough — you have the option of copying a -full CD ISO image to it. - -</para> - -&usb-setup-x86.xml; -&usb-setup-powerpc.xml; - - </sect2> - - <!-- TODO: doesn't this section belong later? --> - <sect2 arch="x86"> - <title>Booting the USB stick</title> -<warning><para> - -If your system refuses to boot from the memory stick, the stick may -contain an invalid master boot record (MBR). To fix this, use the -<command>install-mbr</command> command from the package -<classname>mbr</classname>: - -<informalexample><screen> -# install-mbr /dev/<replaceable>sdX</replaceable> -</screen></informalexample> - -</para></warning> - </sect2> - </sect1> diff --git a/nl/install-methods/create-floppy.xml b/nl/install-methods/create-floppy.xml deleted file mode 100644 index 6722dcde4..000000000 --- a/nl/install-methods/create-floppy.xml +++ /dev/null @@ -1,108 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - <sect1 condition="supports-floppy-boot" id="create-floppy"> - <title>Creating Floppies from Disk Images</title> -<para> - -Bootable floppy disks are generally used as a last resort to boot the -installer on hardware that cannot boot from CD or by other means. - -</para><para arch="powerpc"> - -Booting the installer from floppy disk reportedly fails on Mac USB -floppy drives. - -</para><para> - -Disk images are files containing the complete contents of a floppy -disk in <emphasis>raw</emphasis> form. Disk images, such as -<filename>boot.img</filename>, cannot simply be copied to floppy -drives. A special program is used to write the image files to floppy -disk in <emphasis>raw</emphasis> mode. This is required because these -images are raw representations of the disk; it is required to do a -<emphasis>sector copy</emphasis> of the data from the file onto the -floppy. - -</para><para> - -There are different techniques for creating floppies from disk images. -This section describes how to create floppies from disk images on -different platforms. - -</para><para> - -Before you can create the floppies, you will first need to download them -from one of the &debian; mirrors, as explained in -<xref linkend="downloading-files"/>. <phrase arch="i386">If you already -have an installation CD-ROM or DVD, the floppy images may also be included -on the CD/DVD.</phrase> - -</para><para> - -No matter which method you use to create your floppies, you should -remember to flip the write-protect tab on the floppies once you have -written them, to ensure they are not damaged unintentionally. - -</para> - - <sect2><title>Writing Disk Images From a Linux or Unix System</title> -<para> - -To write the floppy disk image files to the floppy disks, you will -probably need root access to the system. Place a good, blank floppy -in the floppy drive. Next, use the command - -<informalexample><screen> -$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync -</screen></informalexample> - -where <replaceable>filename</replaceable> is one of the floppy disk image -files. -<filename>/dev/fd0</filename> is a commonly used name of the floppy -disk device, it may be different on your workstation<phrase arch="sparc"> -(on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. -The command may return to the -prompt before Unix has finished writing the floppy disk, so look for -the disk-in-use light on the floppy drive and be sure that the light -is out and the disk has stopped revolving before you remove it from -the drive. On some systems, you'll have to run a command to eject the -floppy from the drive <phrase arch="sparc"> (on Solaris, use -<command>eject</command>, see the manual page)</phrase>. - -</para><para> - -Some systems attempt to automatically mount a floppy disk when you -place it in the drive. You might have to disable this feature before -the workstation will allow you to write a floppy in <emphasis>raw -mode</emphasis>. Unfortunately, how to accomplish this will vary -based on your operating system. -<phrase arch="sparc"> -On Solaris, you can work around -volume management to get raw access to the floppy. First, make sure -that the floppy is auto-mounted (using <command>volcheck</command> or -the equivalent command in the file manager). Then use a -<command>dd</command> command of the form given above, just replace -<filename>/dev/fd0</filename> with -<filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, -where <replaceable>floppy_name</replaceable> is the name the floppy -disk was given when it was formatted (unnamed floppies default to the -name <filename>unnamed_floppy</filename>). On other systems, ask your -system administrator. -</phrase> - -</para><para arch="powerpc"> - -If writing a floppy on powerpc Linux, you will need to eject it. The -<command>eject</command> program handles this nicely; you might need -to install it. - -</para> - - </sect2> - -&floppy-i386.xml; <!-- can be used for other arches --> -&floppy-powerpc.xml; - - </sect1> - diff --git a/nl/install-methods/download/arm.xml b/nl/install-methods/download/arm.xml deleted file mode 100644 index d4f3650a3..000000000 --- a/nl/install-methods/download/arm.xml +++ /dev/null @@ -1,88 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61346 untranslated --> - - - <sect3 arch="arm" id="nslu2-install-files"> - <title>NSLU2 Installation Files</title> -<para> - -A firmware image is provided for the Linksys NSLU2 which will automatically -boot <classname>debian-installer</classname>. This image can be uploaded -via the Linksys web frontend or with upslug2. This firmware image can be -obtained from &nslu2-firmware-img;. - -</para> - </sect3> - - - <sect3 arch="arm" id="n2100-install-files"> - <title>Thecus N2100 Installation Files</title> -<para> - -A firmware image is provided for the Thecus N2100 which will automatically -boot <classname>debian-installer</classname>. This image can be installed -using the Thecus firmware upgrade process. This firmware image can be -obtained from &n2100-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="glantank-install-files"> - <title>GLAN Tank Installation Files</title> -<para> - -The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the -disk on which you intend to install &debian;. These images can be obtained -from &glantank-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="kuroboxpro-install-files"> - <title>Kurobox Pro Installation Files</title> -<para> - -The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the -disk on which you intend to install &debian;. These images can be obtained -from &kuroboxpro-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="mv2120-install-files"> - <title>HP mv2120 Installation Files</title> -<para> - -A firmware image is provided for the HP mv2120 which will automatically -boot <classname>debian-installer</classname>. This image can be installed -with uphpmvault on Linux and other systems and with the HP Media -Vault Firmware Recovery Utility on Windows. The firmware image can be -obtained from &mv2120-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="qnap-install-files"> - <title>QNAP Turbo Station Installation Files</title> -<para> - -The installation files for the QNAP Turbo Station consist of a kernel and -ramdisk as well as a script to write these images to flash. You can obtain -the installation files for QNAP TS-109 and TS-209 from -&qnap-orion-firmware-img; and for QNAP TS-110, TS-119, TS-210, TS-219, -TS-219P from &qnap-kirkwood-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="marvell-install-files"> - <title>SheevaPlug and OpenRD Installation Files</title> -<para> - -The installation files for the Marvell SheevaPlug and OpenRD devices -consist of a kernel and initrd for U-Boot. You can obtain these files -from &kirkwood-marvell-firmware-img;. - -</para> - </sect3> - diff --git a/nl/install-methods/download/powerpc.xml b/nl/install-methods/download/powerpc.xml deleted file mode 100644 index d1dd228f9..000000000 --- a/nl/install-methods/download/powerpc.xml +++ /dev/null @@ -1,28 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - -<!-- commented out as it seems out of date and the links are broken - - <sect3 arch="powerpc" id="newworld-install-files"> - <title>NewWorld MacOS Installation Files </title> -<para> - -For floppy-less installation on NewWorld Macs, it may be most -convenient to obtain all the necessary files packaged into one Stuffit -archive from -<ulink url="&url-powerpc-of;"></ulink> (separate instructions are -included in the archive). Otherwise, obtain the normal installation -files listed above. Retrieve the files to an HFS (not HFS+) partition -on your system. You will also need the <filename>yaboot</filename> and -<filename>yaboot.conf</filename> files from the -<ulink url="&downloadable-file;new-powermac/">new-powermac</ulink> or -<ulink url="&downloadable-file;powermac/">powermac</ulink> archive folder. -However, the newest G4 PowerMacs, and those that work without MacOS 9, -need the newest version of <command>yaboot</command>; the one in the -archive will not work. Obtain the newest version from -<ulink url="http://penguinppc.org/projects/yaboot/"></ulink>. - -</para> - </sect3> - ---> diff --git a/nl/install-methods/downloading-files.xml b/nl/install-methods/downloading-files.xml deleted file mode 100644 index e799e7354..000000000 --- a/nl/install-methods/downloading-files.xml +++ /dev/null @@ -1,34 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - - <sect1 id="downloading-files"> - <title>Downloading Files from &debian; Mirrors</title> - -<para> - -To find the nearest (and thus probably the fastest) mirror, see the -<ulink url="&url-debian-mirrors;">list of Debian mirrors</ulink>. - -</para><para> - -When downloading files from a &debian; mirror using FTP, be sure to download the -files in <emphasis>binary</emphasis> mode, not text or automatic mode. - -</para> - - <sect2 id="where-files"> - <title>Where to Find Installation Images</title> - -<para> -The installation images are located on each &debian; mirror in the directory -<ulink url="&url-debian-installer;images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> -— the <ulink url="&url-debian-installer;images/MANIFEST">MANIFEST</ulink> -lists each image and its purpose. -</para> - -&download-arm.xml; -&download-powerpc.xml; - - </sect2> - - </sect1> diff --git a/nl/install-methods/floppy/i386.xml b/nl/install-methods/floppy/i386.xml deleted file mode 100644 index dba3753e2..000000000 --- a/nl/install-methods/floppy/i386.xml +++ /dev/null @@ -1,35 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39870 untranslated --> - - -<!-- This is not set off for i386 only, because many people will have --> -<!-- access to a PC in order to make a floppy for other arches. --> - - <sect2><title>Writing Disk Images From DOS, Windows, or OS/2</title> - -<para> - -If you have access to an i386 or amd64 machine, you can use one of the -following programs to copy images to floppies. - -</para><para> - -The <command>rawrite1</command> and <command>rawrite2</command> programs -can be used under MS-DOS. To use these programs, first make sure that you -are booted into DOS. Trying to use these programs from within a DOS box in -Windows, or double-clicking on these programs from the Windows Explorer is -<emphasis>not</emphasis> expected to work. - -</para><para> - -The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, -ME, XP and probably later versions. To use it you will need to unpack -diskio.dll in the same directory. - -</para><para> - -These tools can be found on the Official &debian; CD-ROMs under the -<filename>/tools</filename> directory. - -</para> - </sect2> diff --git a/nl/install-methods/floppy/powerpc.xml b/nl/install-methods/floppy/powerpc.xml deleted file mode 100644 index ffaa8ab70..000000000 --- a/nl/install-methods/floppy/powerpc.xml +++ /dev/null @@ -1,122 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28997 untranslated --> - - - <sect2 arch="powerpc"><title>Writing Disk Images From MacOS</title> -<para> - -An AppleScript, <application>Make Debian Floppy</application>, is -available for burning floppies from the provided disk image files. It -can be downloaded from -<ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit"></ulink>. To -use it, just unstuff it on your desktop, and then drag any floppy -image file to it. You must have Applescript installed and enabled in -your extensions manager. Disk Copy will ask you to confirm that you -wish to erase the floppy and proceed to write the file image to it. - -</para><para> - -You can also use the MacOS utility <command>Disk Copy</command> -directly, or the freeware utility <command>suntar</command>. The -<filename>root.bin</filename> file is an example of a floppy -image. Use one of the following methods to create a floppy from the -floppy image with these utilities. - -</para> - - <sect3> - <title>Writing Disk Images with <command>Disk Copy</command></title> -<para> - -If you are creating the floppy image from files which were originally -on the official &debian-gnu; CD, then the Type and Creator are already set -correctly. The following <command>Creator-Changer</command> steps are -only necessary if you downloaded the image files from a &debian; mirror. - -</para> -<orderedlist> -<listitem><para> - -Obtain -<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink> -and use it to open the <filename>root.bin</filename> file. - -</para></listitem> -<listitem><para> - -Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the -Type to <userinput>DDim</userinput> (binary floppy image). The case is -sensitive for these fields. - -</para></listitem> -<listitem><para> - -<emphasis>Important:</emphasis> In the Finder, use <userinput>Get -Info</userinput> to display the Finder information about the floppy -image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so -that MacOS will be unable to remove the boot blocks if the image is -accidentally mounted. - -</para></listitem> - <listitem><para> - -Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it -will very likely be there already, otherwise try -<ulink url="&url-powerpc-diskcopy;"></ulink>. - -</para></listitem> -<listitem><para> - -Run <command>Disk Copy</command>, and select <menuchoice> -<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> -</menuchoice>, then select the -<emphasis>locked</emphasis> image file from the resulting dialog. It -will ask you to insert a floppy, then ask if you really want to erase -it. When done it should eject the floppy. - -</para></listitem> -</orderedlist> - - </sect3> - - <sect3> - <title>Writing Disk Images with <command>suntar</command></title> -<para> - -<orderedlist> -<listitem><para> - -Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;"> -</ulink>. Start the <command>suntar</command> program and select -<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> -menu. - -</para></listitem> -<listitem><para> - -Insert the floppy disk as requested, then hit &enterkey; (start at -sector 0). - -</para></listitem> -<listitem><para> - -Select the <filename>root.bin</filename> file in the file-opening dialog. - -</para></listitem> -<listitem><para> - -After the floppy has been created successfully, select <menuchoice> -<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. -If there are any errors writing the floppy, simply toss that floppy and -try another. - -</para></listitem> -</orderedlist> - -Before using the floppy you created, <emphasis>set the write protect -tab</emphasis>! Otherwise if you accidentally mount it in MacOS, -MacOS will helpfully ruin it. - -</para> - </sect3> - </sect2> diff --git a/nl/install-methods/install-methods.xml b/nl/install-methods/install-methods.xml deleted file mode 100644 index 0956b911b..000000000 --- a/nl/install-methods/install-methods.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - -<chapter id="install-methods"> - <title>Obtaining System Installation Media</title> - -&official-cdrom.xml; -&downloading-files.xml; -&ipl-tape.xml; -&create-floppy.xml; -&boot-usb-files.xml; -&boot-drive-files.xml; -&install-tftp.xml; -&automatic-install.xml; - -</chapter> diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml deleted file mode 100644 index 6c54a89c4..000000000 --- a/nl/install-methods/install-tftp.xml +++ /dev/null @@ -1,341 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62454 untranslated --> - - <sect1 condition="supports-tftp" id="install-tftp"> - <title>Preparing Files for TFTP Net Booting</title> -<para> - -If your machine is connected to a local area network, you may be able -to boot it over the network from another machine, using TFTP. If you -intend to boot the installation system from another machine, the -boot files will need to be placed in specific locations on that machine, -and the machine configured to support booting of your specific machine. - -</para><para> - -You need to set up a TFTP server, and for many machines a DHCP -server<phrase condition="supports-rarp">, or RARP -server</phrase><phrase condition="supports-bootp">, or BOOTP -server</phrase>. - -</para><para> - -<phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) is -one way to tell your client what IP address to use for itself. Another -way is to use the BOOTP protocol.</phrase> - -<phrase condition="supports-bootp">BOOTP is an IP protocol that -informs a computer of its IP address and where on the network to obtain -a boot image.</phrase> - -The DHCP (Dynamic Host Configuration Protocol) is a more flexible, -backwards-compatible extension of BOOTP. -Some systems can only be configured via DHCP. - -</para><para arch="powerpc"> - -For PowerPC, if you have a NewWorld Power Macintosh machine, it is a -good idea to use DHCP instead of BOOTP. Some of the latest machines -are unable to boot using BOOTP. - -</para><para arch="hppa"> - -Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. -There is an <classname>rbootd</classname> package available in &debian;. - -</para><para> - -The Trivial File Transfer Protocol (TFTP) is used to serve the boot -image to the client. Theoretically, any server, on any platform, -which implements these protocols, may be used. In the examples in -this section, we shall provide commands for SunOS 4.x, SunOS 5.x -(a.k.a. Solaris), and GNU/Linux. - -<note arch="x86"><para> - -For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. -It's written by the same author as the <classname>syslinux</classname> -bootloader and is therefore least likely to cause issues. -A good alternative is <classname>atftpd</classname>. - -</para></note> - -</para> - -&tftp-rarp.xml; -&tftp-dhcp.xml; -&tftp-bootp.xml; - - <sect2 id="tftpd"> - <title>Enabling the TFTP Server</title> -<para> - -To get the TFTP server ready to go, you should first make sure that -<command>tftpd</command> is enabled. - -</para><para> - -In the case of <classname>tftpd-hpa</classname> there are two ways the -service can be run. It can be started on demand by the system's -<classname>inetd</classname> daemon, or it can be set up to run as an -independent daemon. Which of these methods is used is selected when the -package is installed and can be changed by reconfiguring the package. - -</para> -<note><para> - -Historically, TFTP servers used <filename>/tftpboot</filename> as directory -to serve images from. However, &debian-gnu; packages may use other directories -to comply with the <ulink url="&url-fhs-home;">Filesystem Hierarchy -Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default -uses <filename>/srv/tftp</filename>. You may have to adjust the -configuration examples in this section accordingly. - -</para></note> -<para> - -All <command>in.tftpd</command> alternatives available in &debian; should -log TFTP requests to the system logs by default. Some of them support a -<userinput>-v</userinput> argument to increase verbosity. -It is recommended to check these log messages in case of boot problems -as they are a good starting point for diagnosing the cause of errors. - -</para><para arch="mips"> - -If you intend to install &debian; on an SGI machine and your TFTP server is a -GNU/Linux box running Linux 2.4, you'll need to set the following on your -server: - -<informalexample><screen> -# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc -</screen></informalexample> - -to turn off Path MTU discovery, otherwise the SGI's PROM can't -download the kernel. Furthermore, make sure TFTP packets are sent from -a source port no greater than 32767, or the download will stall after -the first packet. Again, it's Linux 2.4.X tripping this bug in the -PROM, and you can avoid it by setting - -<informalexample><screen> -# echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range -</screen></informalexample> - -to adjust the range of source ports the Linux TFTP server uses. - -</para> - </sect2> - - <sect2 id="tftp-images"> - <title>Move TFTP Images Into Place</title> -<para> - -Next, place the TFTP boot image you need, as found in -<xref linkend="where-files"/>, in the <command>tftpd</command> -boot image directory. You may have to make a link from that -file to the file which <command>tftpd</command> will use for booting a -particular client. Unfortunately, the file name is determined by the -TFTP client, and there are no strong standards. - -</para><para arch="powerpc"> - -On NewWorld Power Macintosh machines, you will need to set up the -<command>yaboot</command> boot loader as the TFTP boot image. -<command>Yaboot</command> will then retrieve the kernel and RAMdisk -images via TFTP itself. You will need to download the following files -from the <filename>netboot/</filename> directory: - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> - -</para></listitem> -<listitem><para> - -<filename>boot.msg</filename> - -</para></listitem> -</itemizedlist> - -</para><para arch="x86"> - -For PXE booting, everything you should need is set up in the -<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this -tarball into the <command>tftpd</command> boot image directory. Make sure -your dhcp server is configured to pass <filename>pxelinux.0</filename> -to <command>tftpd</command> as the filename to boot. - -</para><para arch="ia64"> - -For PXE booting, everything you should need is set up in the -<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this -tarball into the <command>tftpd</command> boot image directory. Make sure -your dhcp server is configured to pass -<filename>/debian-installer/ia64/elilo.efi</filename> -to <command>tftpd</command> as the filename to boot. - -</para> - - <sect3 arch="sparc"> - <title>SPARC TFTP Booting</title> -<para> - -Some SPARC architectures add the subarchitecture names, such as -<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, -if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, -the filename would be <filename>C0A80103.SUN4C</filename>. However, -there are also subarchitectures where the file the client looks for is -just <filename>client-ip-in-hex</filename>. An easy way to determine the -hexadecimal code for the IP address is to enter the following command -in a shell (assuming the machine's intended IP is 10.0.0.4). - -<informalexample><screen> -$ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 -</screen></informalexample> - -To get to the correct filename, you will need to change all letters to -uppercase and if necessary append the subarchitecture name. - -</para><para> - -If you've done all this correctly, giving the command <userinput>boot -net</userinput> from the OpenPROM should load the image. If the image -cannot be found, try checking the logs on your tftp server to see which -image name is being requested. - -</para><para> - -You can also force some sparc systems to look for a specific file name -by adding it to the end of the OpenPROM boot command, such as -<userinput>boot net my-sparc.image</userinput>. This must still reside -in the directory that the TFTP server looks in. - -</para> - </sect3> - - <sect3 arch="mips"> - <title>SGI TFTP Booting</title> -<para> - -On SGI machines you can rely on the <command>bootpd</command> to supply -the name of the TFTP file. It is given either as the -<userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as -the <userinput>filename=</userinput> option in -<filename>/etc/dhcpd.conf</filename>. - -</para> - </sect3> - - </sect2> - -<!-- FIXME: commented out since it seems too old to be usable and a current - way is not known - - <sect2 id="tftp-low-memory"> - <title>TFTP Installation for Low-Memory Systems</title> -<para> - -On some systems, the standard installation RAMdisk, combined with the -memory requirements of the TFTP boot image, cannot fit in memory. In -this case, you can still install using TFTP, you'll just have to go -through the additional step of NFS mounting your root directory over -the network as well. This type of setup is also appropriate for -diskless or dataless clients. - -</para><para> - -First, follow all the steps above in <xref linkend="install-tftp"/>. - -<orderedlist> -<listitem><para> - -Copy the Linux kernel image on your TFTP server using the -<userinput>a.out</userinput> image for the architecture you are -booting. - -</para></listitem> -<listitem><para> - -Untar the root archive on your NFS server (can be the same system as -your TFTP server): - -<informalexample><screen> -# cd /tftpboot -# tar xvzf root.tar.gz -</screen></informalexample> - -Be sure to use the GNU <command>tar</command> (other tar programs, like the -SunOS one, badly handle devices as plain files). - -</para></listitem> -<listitem><para> - -Export your <filename>/tftpboot/debian-sparc-root</filename> directory -with root access to your client. E.g., add the following line to -<filename>/etc/exports</filename> (GNU/Linux syntax, should be similar -for SunOS): - -<informalexample><screen> -/tftpboot/debian-sparc-root <replaceable>client</replaceable>(rw,no_root_squash) -</screen></informalexample> - -NOTE: <replaceable>client</replaceable> is the host name or IP address recognized -by the server for the system you are booting. - -</para></listitem> -<listitem><para> - -Create a symbolic link from your client IP address in dotted notation -to <filename>debian-sparc-root</filename> in the -<filename>/tftpboot</filename> directory. For example, if the client -IP address is 192.168.1.3, do - -<informalexample><screen> -# ln -s debian-sparc-root 192.168.1.3 -</screen></informalexample> - -</para></listitem> -</orderedlist> - -</para> - - </sect2> - - <sect2 condition="supports-nfsroot"> - <title>Installing with TFTP and NFS Root</title> -<para> - -Installing with TFTP and NFS Root is similar to -<xref linkend="tftp-low-memory"/> because you don't want to -load the RAMdisk anymore but boot from the newly created NFS-root file -system. You then need to replace the symlink to the tftpboot image by -a symlink to the kernel image (for example, -<filename>linux-a.out</filename>). - -</para><para> - -RARP/TFTP requires all daemons to be running on the same server (the -workstation is sending a TFTP request back to the server that replied -to its previous RARP request). - -</para> - - - </sect2> -END FIXME --> - </sect1> diff --git a/nl/install-methods/ipl-tape.xml b/nl/install-methods/ipl-tape.xml deleted file mode 100644 index c99ac8b98..000000000 --- a/nl/install-methods/ipl-tape.xml +++ /dev/null @@ -1,24 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 36841 untranslated --> - - <sect1 arch="s390" id="ipl-tape"> - <title>Creating an IPL tape</title> - -<para> - -If you can't boot (IPL) from the CD-ROM and you are not using VM -you need to create an IPL tape first. This is described in section -3.4.3 in the -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> -Linux for IBM eServer zSeries and S/390: Distributions</ulink> -Redbook. The files you -need to write to the tape are (in this order): -<filename>kernel.debian</filename>, -<filename>parmfile.debian</filename> and -<filename>initrd.debian</filename>. The files can be downloaded -from the <filename>tape</filename> sub-directory, see -<xref linkend="where-files"/>. - -</para> - </sect1> - diff --git a/nl/install-methods/official-cdrom.xml b/nl/install-methods/official-cdrom.xml deleted file mode 100644 index 0965582c3..000000000 --- a/nl/install-methods/official-cdrom.xml +++ /dev/null @@ -1,69 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - - <sect1 id="official-cdrom"> - <title>Official &debian-gnu; CD-ROM Sets</title> -<para> - -By far the easiest way to install &debian-gnu; is from an Official -&debian; CD-ROM Set. You can buy a set from a vendor (see the -<ulink url="&url-debian-cd-vendors;">CD vendors page</ulink>). -You may also download the CD-ROM images from a &debian; mirror and make -your own set, if you have a fast network connection and a CD burner -(see the <ulink url="&url-debian-cd;">Debian CD page</ulink> for -detailed instructions). If you have a &debian; CD set and CDs are -bootable on your machine, you can skip right to -<xref linkend="boot-installer"/>; much effort has been expended to ensure -the files most people need are there on the CD. Although a full set of -binary packages requires several CDs, it is unlikely you will need -packages on the third CD and above. You may also consider using the -DVD version, which saves a lot of space on your shelf and you avoid -the CD shuffling marathon. - -</para><para> - -If your machine doesn't support CD booting, but you do have a CD set, -you can use an alternative strategy such as - -<phrase condition="supports-floppy-boot">floppy disk,</phrase> - -<phrase arch="s390">tape, emulated tape,</phrase> - -<phrase condition="bootable-disk">hard disk,</phrase> - -<phrase condition="bootable-usb">usb stick,</phrase> - -<phrase condition="supports-tftp">net boot,</phrase> - -or manually loading the kernel from the CD to initially boot the -system installer. The files you need for booting by another means are -also on the CD; the &debian; network archive and CD folder organization -are identical. So when archive file paths are given below for -particular files you need for booting, look for those files in the -same directories and subdirectories on your CD. - -</para><para> - -Once the installer is booted, it will be able to obtain all the other -files it needs from the CD. - -</para><para> - -If you don't have a CD set, then you will need to download the -installer system files and place them on the - -<phrase arch="s390">installation tape</phrase> - -<phrase condition="supports-floppy-boot">floppy disk or</phrase> - -<phrase condition="bootable-disk">hard disk or</phrase> - -<phrase condition="bootable-usb">usb stick or</phrase> - -<phrase condition="supports-tftp">a connected computer</phrase> - -so they can be used to boot the installer. - -</para> - - </sect1> diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml deleted file mode 100644 index 86be45104..000000000 --- a/nl/install-methods/tftp/bootp.xml +++ /dev/null @@ -1,73 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59293 untranslated --> - - - <sect2 condition="supports-bootp" id="tftp-bootp"> - <title>Setting up a BOOTP server</title> -<para> - -There are two BOOTP servers available for GNU/Linux. The first is CMU -<command>bootpd</command>. The other is actually a DHCP server: ISC -<command>dhcpd</command>. In &debian-gnu; these are contained in the -<classname>bootp</classname> and <classname>dhcp3-server</classname> -packages respectively. - -</para><para> - -To use CMU <command>bootpd</command>, you must first uncomment (or -add) the relevant line in <filename>/etc/inetd.conf</filename>. On -&debian-gnu;, you can run <userinput>update-inetd --enable -bootps</userinput>, then <userinput>/etc/init.d/inetd -reload</userinput> to do so. Just in case your BOOTP server does not -run &debian;, the line in question should look like: - -<informalexample><screen> -bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120 -</screen></informalexample> - -Now, you must create an <filename>/etc/bootptab</filename> file. This -has the same sort of familiar and cryptic format as the good old BSD -<filename>printcap</filename>, <filename>termcap</filename>, and -<filename>disktab</filename> files. See the -<filename>bootptab</filename> manual page for more information. For -CMU <command>bootpd</command>, you will need to know the hardware -(MAC) address of the client. Here is an example -<filename>/etc/bootptab</filename>: - -<informalexample><screen> -client:\ - hd=/tftpboot:\ - bf=tftpboot.img:\ - ip=192.168.1.90:\ - sm=255.255.255.0:\ - sa=192.168.1.1:\ - ha=0123456789AB: -</screen></informalexample> - -You will need to change at least the <quote>ha</quote> option, which -specifies the hardware address of the client. The <quote>bf</quote> -option specifies the file a client should retrieve via TFTP; see -<xref linkend="tftp-images"/> for more details. - -<phrase arch="mips"> -On SGI machines you can just enter the command monitor and type -<userinput>printenv</userinput>. The value of the -<userinput>eaddr</userinput> variable is the machine's MAC address. -</phrase> - -</para><para> - -By contrast, setting up BOOTP with ISC <command>dhcpd</command> is -really easy, because it treats BOOTP clients as a moderately special -case of DHCP clients. Some architectures require a complex -configuration for booting clients via BOOTP. If yours is one of -those, read the section <xref linkend="dhcpd"/>. Otherwise you -will probably be able to get away with simply adding the -<userinput>allow bootp</userinput> directive to the configuration -block for the subnet containing the client in -<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart -<command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server -restart</userinput>. - -</para> - </sect2> diff --git a/nl/install-methods/tftp/dhcp.xml b/nl/install-methods/tftp/dhcp.xml deleted file mode 100644 index 6f1a89b81..000000000 --- a/nl/install-methods/tftp/dhcp.xml +++ /dev/null @@ -1,94 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62402 untranslated --> - - <sect2 id="dhcpd"> - <title>Setting up a DHCP server</title> -<para> - -One free software DHCP server is ISC <command>dhcpd</command>. -For &debian-gnu;, the <classname>dhcp3-server</classname> package is -recommended. Here is a sample configuration file for it (see -<filename>/etc/dhcp3/dhcpd.conf</filename>): - -<informalexample><screen> -option domain-name "example.com"; -option domain-name-servers ns1.example.com; -option subnet-mask 255.255.255.0; -default-lease-time 600; -max-lease-time 7200; -server-name "servername"; - -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option routers 192.168.1.1; -} - -host clientname { - filename "/tftpboot.img"; - server-name "servername"; - next-server servername; - hardware ethernet 01:23:45:67:89:AB; - fixed-address 192.168.1.90; -} -</screen></informalexample> - -</para><para> - -In this example, there is one server -<replaceable>servername</replaceable> which performs all of the work -of DHCP server, TFTP server, and network gateway. You will almost -certainly need to change the domain-name options, as well as the -server name and client hardware address. The -<replaceable>filename</replaceable> option should be the name of the -file which will be retrieved via TFTP. - -</para><para> - -After you have edited the <command>dhcpd</command> configuration file, -restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>. - -</para> - - <sect3 arch="x86"> - <title>Enabling PXE Booting in the DHCP configuration</title> -<para> -Here is another example for a <filename>dhcp.conf</filename> using the -Pre-boot Execution Environment (PXE) method of TFTP. - -<informalexample><screen> -option domain-name "example.com"; - -default-lease-time 600; -max-lease-time 7200; - -allow booting; -allow bootp; - -# The next paragraph needs to be modified to fit your case -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option broadcast-address 192.168.1.255; -# the gateway address which can be different -# (access to the internet for instance) - option routers 192.168.1.1; -# indicate the dns you want to use - option domain-name-servers 192.168.1.3; -} - -group { - next-server 192.168.1.3; - host tftpclient { -# tftp client hardware address - hardware ethernet 00:10:DC:27:6C:15; - filename "pxelinux.0"; - } -} -</screen></informalexample> - -Note that for PXE booting, the client filename <filename>pxelinux.0</filename> -is a boot loader, not a kernel image (see <xref linkend="tftp-images"/> -below). - -</para> - </sect3> - </sect2> diff --git a/nl/install-methods/tftp/rarp.xml b/nl/install-methods/tftp/rarp.xml deleted file mode 100644 index 47715f8db..000000000 --- a/nl/install-methods/tftp/rarp.xml +++ /dev/null @@ -1,32 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62401 untranslated --> - - <sect2 condition="supports-rarp" id="tftp-rarp"> - <title>Setting up RARP server</title> -<para> - -To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) -of the client computers to be installed. -If you don't know this information, you can - -<phrase arch="sparc"> pick it off the initial OpenPROM boot messages, use the -OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> - -boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the -command <userinput>ip addr show dev eth0</userinput>. - -</para><para> - -On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, -you use the <command>rarpd</command> program. -You need to ensure that the Ethernet hardware address for the client is -listed in the <quote>ethers</quote> database (either in the -<filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the -<quote>hosts</quote> database. Then you need to start the RARP daemon. -Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> -on most Linux systems and SunOS 5 (Solaris 2), -<userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, -or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1). - -</para> - </sect2> diff --git a/nl/install-methods/usb-setup/powerpc.xml b/nl/install-methods/usb-setup/powerpc.xml deleted file mode 100644 index 6eba27fb6..000000000 --- a/nl/install-methods/usb-setup/powerpc.xml +++ /dev/null @@ -1,119 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56442 untranslated --> - - <sect3 arch="powerpc"> - <title>Partitioning the USB stick</title> -<para> - -Most USB sticks do not come pre-configured in such a way that Open -Firmware can boot from them, so you will need to repartition the stick. -On Mac systems, run -<userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, -initialise a new partition map using the <userinput>i</userinput> -command, and create a new partition of type Apple_Bootstrap using the -<userinput>C</userinput> command. (Note that the first "partition" will -always be the partition map itself.) Then type - -<informalexample><screen> -$ hformat /dev/<replaceable>sdX2</replaceable> -</screen></informalexample> - -Take care that you use the correct device name for your USB stick. The -<command>hformat</command> command is contained in the -<classname>hfsutils</classname> &debian; package. - -</para><para> - -In order to start the kernel after booting from the USB stick, we will -put a boot loader on the stick. The <command>yaboot</command> boot -loader can be installed on an HFS filesystem and can be reconfigured by -just editing a text file. Any operating system which supports the HFS -file system can be used to make changes to the configuration of the boot -loader. - -</para><para> - -The normal <command>ybin</command> tool that comes with -<command>yaboot</command> does not yet understand USB storage devices, -so you will have to install <command>yaboot</command> by hand using the -<classname>hfsutils</classname> tools. Type - -<informalexample><screen> -$ hmount /dev/<replaceable>sdX2</replaceable> -$ hcopy -r /usr/lib/yaboot/yaboot : -$ hattrib -c UNIX -t tbxi :yaboot -$ hattrib -b : -$ humount -</screen></informalexample> - -Again, take care that you use the correct device name. The partition -must not be otherwise mounted during this procedure. This procedure -writes the boot loader to the partition, and uses the HFS utilities to -mark it in such a way that Open Firmware will boot it. Having done this, -the rest of the USB stick may be prepared using the normal Unix -utilities. - -</para> - </sect3> - - <sect3 arch="powerpc"> - <title>Adding the installer image</title> -<para> - -Mount the partition -(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) -and copy the following installer image files to the stick: - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> (kernel binary) - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> (initial ramdisk image) - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> (yaboot configuration file) - -</para></listitem> -<listitem><para> - -<filename>boot.msg</filename> (optional boot message) - -</para></listitem> -</itemizedlist> - -</para><para> - -The <filename>yaboot.conf</filename> configuration file should -contain the following lines: - -<informalexample><screen> -default=install -root=/dev/ram - -message=/boot.msg - -image=/vmlinux - label=install - initrd=/initrd.gz - initrd-size=10000 - read-only -</screen></informalexample> - -Please note that the <userinput>initrd-size</userinput> parameter -may need to be increased, depending on the image you are booting. - -</para><para> - -If you used an <filename>hd-media</filename> image, you should now copy a -&debian; ISO image (businesscard, netinst or full CD image; be sure to select -one that fits) onto the stick. When you are done, unmount the USB memory -stick (<userinput>umount /mnt</userinput>). - -</para> - </sect3> diff --git a/nl/install-methods/usb-setup/x86.xml b/nl/install-methods/usb-setup/x86.xml deleted file mode 100644 index 36a96af21..000000000 --- a/nl/install-methods/usb-setup/x86.xml +++ /dev/null @@ -1,117 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61286 untranslated --> - - <sect3 arch="x86"> - <title>Partitioning the USB stick</title> -<para> - -We will show how to set up the memory stick to use the first partition, -instead of the entire device. - -</para><note><para> - -Since most USB sticks come pre-configured with a single FAT16 -partition, you probably won't have to repartition or reformat the -stick. If you have to do that anyway, use <command>cfdisk</command> -or any other partitioning tool to create a FAT16 partition<footnote> - -<para> -Don't forget to set the <quote>bootable</quote> bootable flag. -</para> - -</footnote>, and then create the filesystem using: - -<informalexample><screen> -# mkdosfs /dev/<replaceable>sdX1</replaceable> -</screen></informalexample> - -Take care that you use the correct device name for your USB stick. The -<command>mkdosfs</command> command is contained in the -<classname>dosfstools</classname> &debian; package. - -</para></note><para> - -In order to start the kernel after booting from the USB stick, we will -put a boot loader on the stick. Although any boot loader -(e.g. <classname>lilo</classname>) should work, it's convenient to use -<classname>syslinux</classname>, since it uses a FAT16 partition and can -be reconfigured by just editing a text file. Any operating system -which supports the FAT file system can be used to make changes to the -configuration of the boot loader. - -</para><para> - -To put <classname>syslinux</classname> on the FAT16 partition on your USB -stick, install the <classname>syslinux</classname> and -<classname>mtools</classname> packages on your system, and do: - -<informalexample><screen> -# syslinux /dev/<replaceable>sdX1</replaceable> -</screen></informalexample> - -Again, take care that you use the correct device name. The partition -must not be mounted when starting <command>syslinux</command>. This -procedure writes a boot sector to the partition and creates the file -<filename>ldlinux.sys</filename> which contains the boot loader code. - -</para> - </sect3> - - <sect3 arch="x86"> - <title>Adding the installer image</title> -<para> - -Mount the partition -(<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) -and copy the following installer image files to the stick: - -<itemizedlist> -<listitem><para> - -<filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> (initial ramdisk image) - -</para></listitem> -</itemizedlist> - -You can choose between either the regular version or the graphical version -of the installer. The latter can be found in the <filename>gtk</filename> -subdirectory. If you want to rename the files, please note that -<classname>syslinux</classname> can only process DOS (8.3) file names. - -</para><para> - -Next you should create a <filename>syslinux.cfg</filename> configuration -file, which at a bare minimum should contain the following two lines (change -the name of the kernel binary to <quote><filename>linux</filename></quote> -if you used a <filename>netboot</filename> image): - -<informalexample><screen> -default vmlinuz -append initrd=initrd.gz -</screen></informalexample> - -For the graphical installer you should add -<userinput>vga=788</userinput> to the second line. - -</para><para> - -If you used an <filename>hd-media</filename> image, you should now copy a -&debian; ISO image<footnote> - -<para> -You can use either a businesscard, a netinst or a full CD image (see -<xref linkend="official-cdrom"/>). Be sure to select one that fits. -Note that the <quote>netboot <filename>mini.iso</filename></quote> image is -not usable for this purpose. -</para> - -</footnote> onto the stick. When you are done, unmount the USB memory stick -(<userinput>umount /mnt</userinput>). - -</para> - </sect3> diff --git a/nl/partitioning/device-names.xml b/nl/partitioning/device-names.xml deleted file mode 100644 index eb52b09ef..000000000 --- a/nl/partitioning/device-names.xml +++ /dev/null @@ -1,131 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - - <sect1 arch="linux-any" id="device-names"> - <title>Device Names in Linux</title> -<para> - -Linux disks and partition names may be different from other operating -systems. You need to know the names that Linux uses when you create -and mount partitions. Here's the basic naming scheme: - -</para> -<itemizedlist arch="not-s390"> -<listitem><para> - -The first floppy drive is named <filename>/dev/fd0</filename>. - -</para></listitem> -<listitem><para> - -The second floppy drive is named <filename>/dev/fd1</filename>. - -</para></listitem> -<listitem><para> - -The first SCSI disk (SCSI ID address-wise) is named -<filename>/dev/sda</filename>. - -</para></listitem> -<listitem><para> - -The second SCSI disk (address-wise) is named -<filename>/dev/sdb</filename>, and so on. - -</para></listitem> -<listitem><para> - -The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also -known as <filename>/dev/sr0</filename>. - -</para></listitem> -<listitem><para> - -The master disk on IDE primary controller is named -<filename>/dev/hda</filename>. - -</para></listitem> -<listitem><para> - -The slave disk on IDE primary controller is named -<filename>/dev/hdb</filename>. - -</para></listitem> -<listitem><para> - -The master and slave disks of the secondary controller can be called -<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, -respectively. Newer IDE controllers can actually have two channels, -effectively acting like two controllers. - -</para></listitem> -</itemizedlist> - -<itemizedlist arch="s390"> -<listitem><para> - -The first DASD device is named -<filename>/dev/dasda</filename>. - -</para></listitem> -<listitem><para> - -The second DASD device is named -<filename>/dev/dasdb</filename>, and so on. - -</para></listitem> -</itemizedlist> - -<para arch="not-s390"> - -The partitions on each disk are represented by appending a decimal -number to the disk name: <filename>sda1</filename> and -<filename>sda2</filename> represent the first and -second partitions of the first SCSI disk drive in your system. - -</para><para arch="not-s390"> - -Here is a real-life example. Let's assume you have a system with 2 -SCSI disks, one at SCSI address 2 and the other at SCSI address 4. -The first disk (at address 2) is then named <filename>sda</filename>, -and the second <filename>sdb</filename>. If the -<filename>sda</filename> drive has 3 partitions on it, these will be -named <filename>sda1</filename>, <filename>sda2</filename>, and -<filename>sda3</filename>. The same applies to the -<filename>sdb</filename> disk and its partitions. - -</para><para arch="not-s390"> - -Note that if you have two SCSI host bus adapters (i.e., controllers), -the order of the drives can get confusing. The best solution in this -case is to watch the boot messages, assuming you know the drive models -and/or capacities. - -</para><para arch="x86"> - -Linux represents the primary partitions as the drive name, plus the -numbers 1 through 4. For example, the first primary partition on the -first IDE drive is <filename>/dev/hda1</filename>. The logical partitions are -numbered starting at 5, so the first logical partition on that same -drive is <filename>/dev/hda5</filename>. Remember that the extended -partition, that is, the primary partition holding the logical -partitions, is not usable by itself. This applies to SCSI disks as -well as IDE disks. - -</para><para arch="sparc"> - -Sun disk partitions allow for 8 separate partitions (or slices). The -third partition is usually (and is preferred to have) the <quote>Whole -Disk</quote> partition. This partition references all of the sectors of the -disk, and is used by the boot loader (either SILO, or Sun's). - -</para><para arch="s390"> - -The partitions on each disk are represented by appending a decimal -number to the disk name: <filename>dasda1</filename> and -<filename>dasda2</filename> represent the first and -second partitions of the first DASD device in your system. - -</para> - </sect1> diff --git a/nl/partitioning/partition-programs.xml b/nl/partitioning/partition-programs.xml deleted file mode 100644 index eb3045891..000000000 --- a/nl/partitioning/partition-programs.xml +++ /dev/null @@ -1,138 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - - <sect1 id="partition-programs"> - <title>&debian; Partitioning Programs</title> -<para> - -Several varieties of partitioning programs have been adapted by &debian; -developers to work on various types of hard disks and computer -architectures. Following is a list of the program(s) applicable for -your architecture. - -</para> - -<variablelist> - -<varlistentry> -<term><command>partman</command></term> -<listitem><para> - -Recommended partitioning tool in &debian;. This Swiss army knife can -also resize partitions, create filesystems -<phrase arch="any-x86"> (<quote>format</quote> in Windows speak)</phrase> -and assign them to the mountpoints. - -</para></listitem> -</varlistentry> - -<varlistentry condition="fdisk.txt"> -<term><command>fdisk</command></term> -<listitem><para> - -The original Linux disk partitioner, good for gurus. - -</para><para> - -Be careful if you have existing FreeBSD partitions on your machine. -The installation kernels include support for these partitions, but the -way that <command>fdisk</command> represents them (or not) can make the -device names differ. See the -<ulink url="&url-linux-freebsd;">Linux+FreeBSD HOWTO</ulink>. - -</para></listitem> -</varlistentry> - -<varlistentry condition="cfdisk.txt"> -<term><command>cfdisk</command></term> -<listitem><para> - -A simple-to-use, full-screen disk partitioner for the rest of us. - -</para><para> - -Note that <command>cfdisk</command> doesn't understand FreeBSD -partitions at all, and, again, device names may differ as a result. - -</para></listitem> -</varlistentry> - -<varlistentry condition="atari-fdisk.txt"> -<term><command>atari-fdisk</command></term> -<listitem><para> - -Atari-aware version of <command>fdisk</command>. - -</para></listitem> -</varlistentry> - -<varlistentry condition="amiga-fdisk.txt"> -<term><command>amiga-fdisk</command></term> -<listitem><para> - -Amiga-aware version of <command>fdisk</command>. - -</para></listitem> -</varlistentry> - -<varlistentry condition="mac-fdisk.txt"> -<term><command>mac-fdisk</command></term> -<listitem><para> - -Mac-aware version of <command>fdisk</command>. - -</para></listitem> -</varlistentry> - -<varlistentry condition="pmac-fdisk.txt"> -<term><command>pmac-fdisk</command></term> -<listitem><para> - -PowerMac-aware version of <command>fdisk</command>, also used by BVM -and Motorola VMEbus systems. - -</para></listitem> -</varlistentry> - -<varlistentry condition="fdasd.txt"> -<term><command>fdasd</command></term> -<listitem><para> - -&arch-title; version of <command>fdisk</command>; Please read the -fdasd manual page or chapter 13 in -<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf"> -Device Drivers and Installation Commands</ulink> for details. - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -One of these programs will be run by default when you select -<guimenuitem>Partition disks</guimenuitem> (or similar). It may be possible -to use a different partitioning tool from the command line on VT2, but this -is not recommended. - -</para><para arch="x86">Remember to mark your boot partition as -<quote>Bootable</quote>. - -</para><para condition="mac-fdisk.txt"> - -One key point when partitioning for Mac type disks is that the -swap partition is identified by its name; it must be named <quote>swap</quote>. -All Mac linux partitions are the same partition type, -Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the -<ulink url="&url-mac-fdisk-tutorial;">mac-fdisk Tutorial</ulink>, which -includes steps you should take if you are sharing your disk with MacOS. - -</para> - -&partition-hppa.xml; -&partition-x86.xml; -&partition-ia64.xml; -&partition-mips.xml; -&partition-powerpc.xml; -&partition-sparc.xml; - - </sect1> diff --git a/nl/partitioning/partition/hppa.xml b/nl/partitioning/partition/hppa.xml deleted file mode 100644 index e93a8bb7f..000000000 --- a/nl/partitioning/partition/hppa.xml +++ /dev/null @@ -1,22 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 35595 untranslated --> - - - <sect2 arch="hppa"><title>Partitioning for &arch-title;</title> -<para> - -PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> somewhere -in the first 2GB. This is where the boot loader and an optional kernel -and RAMdisk will be stored, so make it big enough for that — at least -4Mb (I like 8–16MB). An additional requirement of the firmware is that -the Linux kernel must reside within the first 2GB of the disk. This -is typically achieved by making the root ext2 partition fit entirely -within the first 2GB of the disk. Alternatively you can create a small -ext2 partition near the start of the disk and mount that on -<filename>/boot</filename>, since that is the directory where the Linux -kernel(s) will be stored. <filename>/boot</filename> needs to be big enough -to hold whatever kernels (and backups) you might wish to load; 25–50MB -is generally sufficient. - -</para> - </sect2> diff --git a/nl/partitioning/partition/ia64.xml b/nl/partitioning/partition/ia64.xml deleted file mode 100644 index ecb7b66b3..000000000 --- a/nl/partitioning/partition/ia64.xml +++ /dev/null @@ -1,120 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43254 untranslated --> - - - <sect2 arch="ia64"><title>Partitioning for &arch-title;</title> -<para> - -The <command>partman</command> disk partitioner is the default -partitioning tool for the installer. -It manages the set of partitions and their mount points to ensure -that the disks and filesystems are properly configured for a successful -installation. It actually uses <command>parted</command> to do the -on-disk partitioning. - -</para> - - <note> - <title>EFI Recognized Formats</title> -<para> - -The IA-64 EFI firmware supports two partition table (or disk label) -formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 -PCs, is no longer recommended for IA-64 systems. Although -the installer also provides <command>cfdisk</command>, -you should only use <ulink url="parted.txt"> -<command>parted</command></ulink> because only it can manage both GPT -and MS-DOS tables correctly. - -</para></note> - -<para> - -The automatic partitioning recipes for <command>partman</command> -allocate an EFI partition as the first partition on the disk. -You can also set up the partition under the <guimenuitem>Guided -partitioning</guimenuitem> from the main menu in a manner similar to -setting up a <emphasis>swap</emphasis> partition. - -</para><para> - -The <command>partman</command> partitioner will handle most disk -layouts. -For those rare cases where it is necessary to manually set up a disk, -you can use the shell as described above and run the -<command>parted</command> utility directly using its command line interface. -Assuming that you want to erase your whole disk and create a GPT table -and some partitions, then something similar to the following command -sequence could be used: - -<informalexample><screen> - mklabel gpt - mkpartfs primary fat 0 50 - mkpartfs primary linux-swap 51 1000 - mkpartfs primary ext2 1001 3000 - set 1 boot on - print - quit -</screen></informalexample> - -This creates a new partition table, and three partitions to be used as -an EFI boot partition, swap space, and a root file system. Finally it -sets the boot flag on the EFI partition. Partitions are specified in -Megabytes, with start and end offsets from the beginning of the disk. -So, for example, above we created a 1999MB ext2 file system starting -at offset 1001MB from the start of the disk. Note that formatting swap -space with <command>parted</command> can take a few minutes to -complete, as it scans the partition for bad blocks. - -</para> - </sect2> - - <sect2 arch="ia64"><title>Boot Loader Partition Requirements</title> -<para> - -ELILO, the IA-64 boot loader, requires a partition containing a FAT -file system with the <userinput>boot</userinput> flag set. -The partition must be big enough to hold the boot loader and any -kernels or RAMdisks you may wish to boot. A minimum size would be -about 20MB, but if you expect to run with multiple kernels, then -128MB might be a better size. - -</para><para> - -The EFI Boot Manager and the EFI Shell fully support the GPT table -so the boot partition does not necessarily have to be the first -partition or even on the same disk. -This is convenient if you should forget to allocate the partition and -only find out after you have formatted the other partitions on your disk(s). -The <command>partman</command> partitioner checks for an EFI partition -at the same time it checks for a properly set up <emphasis>root</emphasis> -partition. -This gives you an opportunity to correct the disk layout before the -package install begins. -The easiest way to correct this omission is to shrink the last partition -of the disk to make enough free space for adding an EFI partition. - -</para><para> - -It is strongly recommended that you allocate the EFI boot partition -on the same disk as the <emphasis>root</emphasis> filesystem. - -</para> - </sect2> - - <sect2 arch="ia64"><title>EFI Diagnostic Partitions</title> -<para> - -The EFI firmware is significantly more sophisticated than the usual -BIOS seen on most x86 PCs. -Some system vendors take advantage of the ability of the EFI to -access files and run programs from a hard disk filesystem to store diagnostics -and EFI based system management utilities on the hard disk. -This is a separate FAT format filesystem on the system disk. -Consult the system documentation and accessories that come with the -system for details. -The easiest time to set up a diagnostics partition is at the same time you -set up the EFI boot partition. - -</para> - </sect2> diff --git a/nl/partitioning/partition/mips.xml b/nl/partitioning/partition/mips.xml deleted file mode 100644 index edd4d7176..000000000 --- a/nl/partitioning/partition/mips.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 35613 untranslated --> - - - <sect2 arch="mips"><title>Partitioning for &arch-title;</title> -<para> - -SGI machines require an SGI disk label in order to make the system bootable -from hard disk. It can be created in the fdisk expert menu. The thereby -created volume header (partition number 9) should be at least 3MB large. -If the volume header created is too small, you can simply delete -partition number 9 and re-add it with a different size. Note that the -volume header must start at sector 0. - -</para> - </sect2> diff --git a/nl/partitioning/partition/powerpc.xml b/nl/partitioning/partition/powerpc.xml deleted file mode 100644 index 6aadde151..000000000 --- a/nl/partitioning/partition/powerpc.xml +++ /dev/null @@ -1,57 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 48741 untranslated --> - - - <sect2 arch="powerpc"><title>Partitioning Newer PowerMacs</title> -<para> - -If you are installing onto a NewWorld PowerMac you must create a -special bootstrap partition to hold the boot loader. The size of this -partition must have at least 819200 bytes and its partition type must be -<emphasis>Apple_Bootstrap</emphasis>. If the bootstrap partition is -not created with the <emphasis>Apple_Bootstrap</emphasis> type your -machine cannot be made bootable from the hard disk. This partition -can easily be created by creating a new partition in -<command>partman</command> and telling it to use it as a <quote>NewWorld -boot partition</quote>, or in <command>mac-fdisk</command> using the -<userinput>b</userinput> command. - -</para><para> - -The special partition type Apple_Bootstrap is required to prevent -MacOS from mounting and damaging the bootstrap partition, as there are -special modifications made to it in order for OpenFirmware to boot it -automatically. - -</para><para> - -Note that the bootstrap partition is only meant to hold 3 very small -files: the <command>yaboot</command> binary, its configuration -<filename>yaboot.conf</filename>, and a first stage OpenFirmware -loader <command>ofboot.b</command>. It need not and must not be -mounted on your file system nor have kernels or anything else copied -to it. The <command>ybin</command> and <command>mkofboot</command> -utilities are used to manipulate this partition. - -</para><para> - -In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap -partition should appear before other boot partitions on the disk, -especially MacOS boot partitions. The bootstrap partition should be -the first one you create. However, if you add a bootstrap partition -later, you can use <command>mac-fdisk</command>'s -<userinput>r</userinput> command to reorder the partition map so the -bootstrap partition comes right after the map (which is always -partition 1). It's the logical map order, not the physical address -order, that counts. - -</para><para> - -Apple disks normally have several small driver partitions. If you -intend to dual boot your machine with MacOSX, you should retain these -partitions and a small HFS partition (800k is the minimum size). That -is because MacOSX, on every boot, offers to initialize any disks which do -not have active MacOS partitions and driver partitions. - -</para> - </sect2> diff --git a/nl/partitioning/partition/sparc.xml b/nl/partitioning/partition/sparc.xml deleted file mode 100644 index f4996a519..000000000 --- a/nl/partitioning/partition/sparc.xml +++ /dev/null @@ -1,33 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - - - <sect2 arch="sparc"><title>Partitioning for &arch-title;</title> -<para> - -Make sure you create a <quote>Sun disk label</quote> on your boot disk. This is -the only kind of partition scheme that the OpenBoot PROM understands, -and so it's the only scheme from which you can boot. The -<keycap>s</keycap> key is used in <command>fdisk</command> to -create Sun disk labels. - -</para><para> - -Furthermore, on &arch-title; disks, make sure your first partition on -your boot disk starts at cylinder 0. While this is required, it also -means that the first partition will contain the partition table and -the boot block, which are the first two sectors of the disk. You must -<emphasis>not</emphasis> put swap on the first partition of the boot -drive, since swap partitions do not preserve the first few sectors of -the partition. You can put Ext2 or UFS partitions there; these will -leave the partition table and the boot block alone. - -</para><para> - -It is also advised that the third partition should be of type <quote>Whole -disk</quote> (type 5), and contain the entire disk (from the first cylinder -to the last). This is simply a convention of Sun disk labels, and -helps the <command>SILO</command> boot loader keep its bearings. - -</para> - </sect2>
\ No newline at end of file diff --git a/nl/partitioning/partition/x86.xml b/nl/partitioning/partition/x86.xml deleted file mode 100644 index ff3ef812c..000000000 --- a/nl/partitioning/partition/x86.xml +++ /dev/null @@ -1,95 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 42250 untranslated --> - - - <sect2 arch="x86"><title>Partitioning for &arch-title;</title> -<para> - -If you have an existing other operating system such as DOS or Windows and -you want to preserve that operating system while installing &debian;, you may -need to resize its partition to free up space for the &debian; installation. -The installer supports resizing of both FAT and NTFS filesystems; when you -get to the installer's partitioning step, select the option -<guimenuitem>Manual</guimenuitem> and then simply select an existing -partition and change its size. - -</para><para> - -The PC BIOS generally adds additional constraints for disk -partitioning. There is a limit to how many <quote>primary</quote> and -<quote>logical</quote> partitions a drive can contain. Additionally, with pre -1994–98 BIOSes, there are limits to where on the drive the BIOS can boot -from. More information can be found in the -<ulink url="&url-partition-howto;">Linux Partition HOWTO</ulink> and the -<ulink url="&url-phoenix-bios-faq-large-disk;">Phoenix BIOS FAQ</ulink>, but -this section will include a brief overview to help you plan most situations. - -</para><para> - -<quote>Primary</quote> partitions are the original partitioning scheme for PC -disks. However, there can only be four of them. To get past this -limitation, <quote>extended</quote> and <quote>logical</quote> partitions were invented. By -setting one of your primary partitions as an extended partition, you -can subdivide all the space allocated to that partition into logical -partitions. You can create up to 60 logical partitions per extended -partition; however, you can only have one extended partition per -drive. - -</para><para arch="linux-any"> - -Linux limits the partitions per drive to 255 partitions for SCSI disks -(3 usable primary partitions, 252 logical partitions), and 63 -partitions on an IDE drive (3 usable primary partitions, 60 logical -partitions). However the normal &debian-gnu; system provides -only 20 devices for partitions, so you may not install on partitions -higher than 20 unless you first manually create devices for those -partitions. - -</para><para> - -If you have a large IDE disk, and are using neither LBA addressing, -nor overlay drivers (sometimes provided by hard disk manufacturers), -then the boot partition (the partition containing your kernel image) -must be placed within the first 1024 cylinders of your hard drive -(usually around 524 megabytes, without BIOS translation). - -</para><para> - -This restriction doesn't apply if you have a BIOS newer than around -1995–98 (depending on the manufacturer) that supports the <quote>Enhanced -Disk Drive Support Specification</quote>. Both Lilo, the Linux loader, and -&debian;'s alternative <command>mbr</command> must use the BIOS to read the -kernel from the disk into RAM. If the BIOS int 0x13 large disk access -extensions are found to be present, they will be utilized. Otherwise, -the legacy disk access interface is used as a fall-back, and it cannot -be used to address any location on the disk higher than the 1023rd -cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer -has, these restrictions no longer apply, since &arch-kernel; does not use the -BIOS for disk access. - -</para><para> - -If you have a large disk, you might have to use cylinder translation -techniques, which you can set from your BIOS setup program, such as -LBA (Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). -More information about issues with large disks can be found in the -<ulink url="&url-large-disk-howto;">Large Disk HOWTO</ulink>. If you -are using a cylinder translation scheme, and the BIOS does not support -the large disk access extensions, then your boot partition has to fit -within the <emphasis>translated</emphasis> representation of the -1024th cylinder. - -</para><para> - -The recommended way of accomplishing this is to create a small (25–50MB -should suffice) partition at the beginning of the disk to be used as -the boot partition, and then create whatever other partitions you wish -to have, in the remaining area. This boot partition -<emphasis>must</emphasis> be mounted on <filename>/boot</filename>, -since that is the directory where the &arch-kernel; kernel(s) will be stored. -This configuration will work on any system, regardless of whether LBA -or large disk CHS translation is used, and regardless of whether your -BIOS supports the large disk access extensions. - -</para> - </sect2> diff --git a/nl/partitioning/partitioning.xml b/nl/partitioning/partitioning.xml deleted file mode 100644 index 68cd5c88f..000000000 --- a/nl/partitioning/partitioning.xml +++ /dev/null @@ -1,13 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - -<appendix id="partitioning"> -<title>Partitioning for &debian;</title> - -&sizing.xml; -&tree.xml; -&schemes.xml; -&device-names.xml; -&partition-programs.xml; - -</appendix> diff --git a/nl/partitioning/schemes.xml b/nl/partitioning/schemes.xml deleted file mode 100644 index 373430f3d..000000000 --- a/nl/partitioning/schemes.xml +++ /dev/null @@ -1,79 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - - <sect1> - <title>Recommended Partitioning Scheme</title> -<para> - -For new users, personal &debian; boxes, home systems, and other -single-user setups, a single <filename>/</filename> partition (plus -swap) is probably the easiest, simplest way to go. However, if your -partition is larger than around 6GB, choose ext3 as your partition -type. Ext2 partitions need periodic file system integrity checking, -and this can cause delays during booting when the partition is large. - -</para><para> - -For multi-user systems or systems with lots of disk space, it's best -to put <filename>/usr</filename>, <filename>/var</filename>, -<filename>/tmp</filename>, and <filename>/home</filename> each on -their own partitions separate from the <filename>/</filename> -partition. - -</para><para> - -You might need a separate <filename>/usr/local</filename> partition if -you plan to install many programs that are not part of the &debian; -distribution. If your machine will be a mail server, you might need -to make <filename>/var/mail</filename> a separate partition. Often, -putting <filename>/tmp</filename> on its own partition, for instance -20–50MB, is a good idea. If you are setting up a server with lots -of user accounts, it's generally good to have a separate, large -<filename>/home</filename> partition. In general, the partitioning -situation varies from computer to computer depending on its uses. - -</para><para> - -For very complex systems, you should see the -<ulink url="&url-multidisk-howto;"> -Multi Disk HOWTO</ulink>. This contains in-depth information, mostly -of interest to ISPs and people setting up servers. - -</para><para> - -With respect to the issue of swap partition size, there are many -views. One rule of thumb which works well is to use as much swap as -you have system memory. It also shouldn't be smaller than 16MB, in -most cases. Of course, there are exceptions to these rules. If you -are trying to solve 10000 simultaneous equations on a machine with -256MB of memory, you may need a gigabyte (or more) of swap. - -</para><para> - -On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the -maximum size of a swap partition is 2GB. That should be enough for -nearly any installation. However, if your swap requirements are this -high, you should probably try to spread the swap across different -disks (also called <quote>spindles</quote>) and, if possible, different SCSI or -IDE channels. The kernel will balance swap usage between multiple -swap partitions, giving better performance. - -</para><para> - -As an example, an older home machine might have 32MB of RAM and a -1.7GB IDE drive on <filename>/dev/hda</filename>. There might be a -500MB partition for another operating system on -<filename>/dev/hda1</filename>, a 32MB swap partition on -<filename>/dev/hda3</filename> and about 1.2GB on -<filename>/dev/hda2</filename> as the Linux partition. - -</para><para> - -For an idea of the space taken by tasks -you might be interested in adding after your system installation is -complete, check <xref linkend="tasksel-size-list"/>. - -</para> - - </sect1> diff --git a/nl/partitioning/sizing.xml b/nl/partitioning/sizing.xml deleted file mode 100644 index 2f4556621..000000000 --- a/nl/partitioning/sizing.xml +++ /dev/null @@ -1,52 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - - - <sect1 id="partition-sizing"> - <title>Deciding on &debian; Partitions and Sizes</title> -<para> - -At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can -have a single partition containing the entire operating system, -applications, and your personal files. Most people feel that a -separate swap partition is also a necessity, although it's not -strictly true. <quote>Swap</quote> is scratch space for an operating system, -which allows the system to use disk storage as <quote>virtual -memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much -more efficient use of it. It is possible to force &arch-kernel; to use a -regular file as swap, but it is not recommended. - -</para><para> - -Most people choose to give GNU/&arch-kernel; more than the minimum number of -partitions, however. There are two reasons you might want to break up -the file system into a number of smaller partitions. The first is for -safety. If something happens to corrupt the file system, generally -only one partition is affected. Thus, you only have to replace (from -the backups you've been carefully keeping) a portion of your -system. At a bare minimum, you should consider creating what is -commonly called a <quote>root partition</quote>. This contains the most essential -components of the system. If any other partitions get corrupted, you -can still boot into GNU/&arch-kernel; to fix the system. This can save you the -trouble of having to reinstall the system from scratch. - -</para><para> - -The second reason is generally more important in a business setting, -but it really depends on your use of the machine. For example, a mail -server getting spammed with e-mail can easily fill a partition. If you -made <filename>/var/mail</filename> a separate partition on the mail -server, most of the system will remain working even if you get spammed. - -</para><para> - -The only real drawback to using more partitions is that it is often -difficult to know in advance what your needs will be. If you make a -partition too small then you will either have to reinstall the system -or you will be constantly moving things around to make room in the -undersized partition. On the other hand, if you make the partition too -big, you will be wasting space that could be used elsewhere. Disk -space is cheap nowadays, but why throw your money away? - -</para> - </sect1> diff --git a/nl/partitioning/tree.xml b/nl/partitioning/tree.xml deleted file mode 100644 index 7a4aec4bc..000000000 --- a/nl/partitioning/tree.xml +++ /dev/null @@ -1,153 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39465 untranslated --> - - - <sect1 id="directory-tree"> - <title>The Directory Tree</title> -<para> - -&debian-gnu; adheres to the -<ulink url="&url-fhs-home;">Filesystem Hierarchy Standard</ulink> -for directory and file naming. This standard allows users and software -programs to predict the location of files and directories. The root -level directory is represented simply by the slash -<filename>/</filename>. At the root level, all &debian; systems include -these directories: - -<informaltable> -<tgroup cols="2"> -<thead> -<row> - <entry>Directory</entry><entry>Content</entry> -</row> -</thead> - -<tbody> -<row> - <entry><filename>bin</filename></entry> - <entry>Essential command binaries</entry> -</row><row> - <entry><filename>boot</filename></entry> - <entry>Static files of the boot loader</entry> -</row><row> - <entry><filename>dev</filename></entry> - <entry>Device files</entry> -</row><row> - <entry><filename>etc</filename></entry> - <entry>Host-specific system configuration</entry> -</row><row> - <entry><filename>home</filename></entry> - <entry>User home directories</entry> -</row><row> - <entry><filename>lib</filename></entry> - <entry>Essential shared libraries and kernel modules</entry> -</row><row> - <entry><filename>media</filename></entry> - <entry>Contains mount points for replaceable media</entry> -</row><row> - <entry><filename>mnt</filename></entry> - <entry>Mount point for mounting a file system temporarily</entry> -</row><row> - <entry><filename>proc</filename></entry> - <entry>Virtual directory for system information (2.4 and 2.6 kernels)</entry> -</row><row> - <entry><filename>root</filename></entry> - <entry>Home directory for the root user</entry> -</row><row> - <entry><filename>sbin</filename></entry> - <entry>Essential system binaries</entry> -</row><row> - <entry><filename>sys</filename></entry> - <entry>Virtual directory for system information (2.6 kernels)</entry> -</row><row> - <entry><filename>tmp</filename></entry> - <entry>Temporary files</entry> -</row><row> - <entry><filename>usr</filename></entry> - <entry>Secondary hierarchy</entry> -</row><row> - <entry><filename>var</filename></entry> - <entry>Variable data</entry> -</row><row> - <entry><filename>srv</filename></entry> - <entry>Data for services provided by the system</entry> -</row><row> - <entry><filename>opt</filename></entry> - <entry>Add-on application software packages</entry> -</row> -</tbody></tgroup></informaltable> -</para> - -<para> - -The following is a list of important considerations regarding -directories and partitions. Note that disk usage varies widely given -system configuration and specific usage patterns. The recommendations -here are general guidelines and provide a starting point for -partitioning. - -</para> -<itemizedlist> -<listitem><para> - -The root partition <filename>/</filename> must always physically -contain <filename>/etc</filename>, <filename>/bin</filename>, -<filename>/sbin</filename>, <filename>/lib</filename> and -<filename>/dev</filename>, otherwise you won't be able to boot. -Typically 150–250MB is needed for the root partition. - -</para></listitem> -<listitem><para> - -<filename>/usr</filename>: contains all user programs -(<filename>/usr/bin</filename>), libraries -(<filename>/usr/lib</filename>), documentation -(<filename>/usr/share/doc</filename>), etc. -This is the part of the file system that generally takes up most space. -You should provide at least 500MB of disk space. This amount should -be increased depending on the number and type of packages you plan -to install. A generous workstation or server installation should allow -4–6GB. - -</para></listitem> -<listitem><para> - -<filename>/var</filename>: variable data like news articles, e-mails, -web sites, databases, the packaging system cache, etc. will be placed -under this directory. The size of this directory depends greatly on -the usage of your system, but for most people will be dictated by -the package management tool's overhead. If you are going to do a full -installation of just about everything &debian; has to offer, all in one -session, setting aside 2 or 3 GB of space for -<filename>/var</filename> should be sufficient. If you are going to -install in pieces (that is to say, install services and utilities, -followed by text stuff, then X, ...), you can get away with 300–500 -MB. If hard drive space is at a premium and you don't plan on doing -major system updates, you can get by with as little as 30 or 40 MB. - -</para></listitem> -<listitem><para> - -<filename>/tmp</filename>: temporary data created by programs will -most likely go in this directory. 40–100MB should usually -be enough. Some applications — including archive manipulators, -CD/DVD authoring tools, and multimedia software — may use -<filename>/tmp</filename> to temporarily store image files. If you -plan to use such applications, you should adjust the space available -in <filename>/tmp</filename> accordingly. - -</para></listitem> -<listitem><para> - -<filename>/home</filename>: every user will put his personal data -into a subdirectory of this directory. Its size depends on how many -users will be using the system and what files are to be stored in -their directories. Depending on your planned usage you should reserve -about 100MB for each user, but adapt this value to your needs. Reserve -a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) -in your home directory. - -</para></listitem> -</itemizedlist> - - </sect1> diff --git a/nl/post-install/further-reading.xml b/nl/post-install/further-reading.xml deleted file mode 100644 index 357e3dd7e..000000000 --- a/nl/post-install/further-reading.xml +++ /dev/null @@ -1,49 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 30719 untranslated --> - - <sect1 id="further-reading"><title>Further Reading and Information</title> -<para> - -If you need information about a particular program, you should first -try <userinput>man <replaceable>program</replaceable></userinput>, or -<userinput>info <replaceable>program</replaceable></userinput>. - -</para><para> - -There is lots of useful documentation in -<filename>/usr/share/doc</filename> as well. In particular, -<filename>/usr/share/doc/HOWTO</filename> and -<filename>/usr/share/doc/FAQ</filename> contain lots of interesting -information. To submit bugs, look at -<filename>/usr/share/doc/debian/bug*</filename>. To read about -&debian;-specific issues for particular programs, look at -<filename>/usr/share/doc/(package name)/README.Debian</filename>. - -</para><para> - -The -<ulink url="http://www.debian.org/">Debian web site</ulink> -contains a large quantity of documentation about Debian. In -particular, see the -<ulink url="http://www.debian.org/doc/FAQ/">Debian GNU/Linux FAQ</ulink> and the -<ulink url="http://www.debian.org/doc/user-manuals#quick-reference">Debian -Reference</ulink>. -An index of more Debian documentation is available from the -<ulink url="http://www.debian.org/doc/ddp">Debian Documentation Project</ulink>. -The Debian community is self-supporting; to subscribe to -one or more of the Debian mailing lists, see the -<ulink url="http://www.debian.org/MailingLists/subscribe"> -Mail List Subscription</ulink> page. -Last, but not least, the <ulink url="http://lists.debian.org/">Debian Mailing -List Archives</ulink> contain a wealth of information on Debian. - -</para><para arch="linux-any"> - -A general source of information on GNU/Linux is the -<ulink url="http://www.tldp.org/">Linux Documentation Project</ulink>. -There you will find the HOWTOs and pointers to other very valuable -information on parts of a GNU/Linux system. - -</para> - - </sect1> diff --git a/nl/post-install/kernel-baking.xml b/nl/post-install/kernel-baking.xml deleted file mode 100644 index 5420f102c..000000000 --- a/nl/post-install/kernel-baking.xml +++ /dev/null @@ -1,173 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 40980 untranslated --> - - <sect1 arch="linux-any" id="kernel-baking"><title>Compiling a New Kernel</title> -<para> - -Why would someone want to compile a new kernel? It is often not -necessary since the default kernel shipped with &debian; handles most -configurations. Also, &debian; often offers several alternative kernels. -So you may want to check first if there is an alternative kernel image -package that better corresponds to your hardware. However, it can be -useful to compile a new kernel in order to: - -<itemizedlist> -<listitem><para> - -handle special hardware needs, or hardware conflicts with the -pre-supplied kernels - -</para></listitem> -<listitem><para> - -use options of the kernel which are not supported in the pre-supplied -kernels (such as high memory support) - -</para></listitem> -<listitem><para> - -optimize the kernel by removing useless drivers to speed up boot time - -</para></listitem> -<listitem><para> - -create a monolithic instead of a modularized kernel - -</para></listitem> -<listitem><para> - -run an updated or development kernel - -</para></listitem> -<listitem><para> - -learn more about linux kernels - -</para></listitem> -</itemizedlist> - -</para> - - <sect2><title>Kernel Image Management</title> -<para> - -Don't be afraid to try compiling the kernel. It's fun and profitable. - -</para><para> - -To compile a kernel the &debian; way, you need some packages: -<classname>fakeroot</classname>, <classname>kernel-package</classname>, -<classname>linux-source-2.6</classname> -and a few others which are probably already installed (see -<filename>/usr/share/doc/kernel-package/README.gz</filename> for the -complete list). - -</para><para> - -This method will make a .deb of your kernel source, and, if you have -non-standard modules, make a synchronized dependent .deb of those -too. It's a better way to manage kernel images; -<filename>/boot</filename> will hold the kernel, the System.map, and a -log of the active config file for the build. - -</para><para> - -Note that you don't <emphasis>have</emphasis> to compile your kernel -the <quote>Debian way</quote>; but we find that using the packaging system -to manage your kernel is actually safer and easier. In fact, you can get -your kernel sources right from Linus instead of -<classname>linux-source-2.6</classname>, -yet still use the <classname>kernel-package</classname> compilation method. - -</para><para> - -Note that you'll find complete documentation on using -<classname>kernel-package</classname> under -<filename>/usr/share/doc/kernel-package</filename>. This section just -contains a brief tutorial. - -</para><para> - -Hereafter, we'll assume you have free rein over your machine and will -extract your kernel source to somewhere in your home directory<footnote> - -<para> - -There are other locations where you can extract kernel sources and build -your custom kernel, but this is easiest as it does not require special -permissions. - -</para> - -</footnote>. We'll also assume that your kernel version is -&kernelversion;. Make sure you are in the directory to where you want to -unpack the kernel sources, extract them using -<userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> -and change to the directory <filename>linux-source-&kernelversion;</filename> -that will have been created. - -</para><para> - -Now, you can configure your kernel. Run <userinput>make -xconfig</userinput> if X11 is installed, configured and being run; run -<userinput>make menuconfig</userinput> otherwise (you'll need -<classname>libncurses5-dev</classname> installed). Take the time to read -the online help and choose carefully. When in doubt, it is typically -better to include the device driver (the software which manages -hardware peripherals, such as Ethernet cards, SCSI controllers, and so -on) you are unsure about. Be careful: other options, not related to a -specific hardware, should be left at the default value if you do not -understand them. Do not forget to select <quote>Kernel module loader</quote> -in <quote>Loadable module support</quote> (it is not selected by default). -If not included, your &debian; installation will experience problems. - -</para><para> - -Clean the source tree and reset the <classname>kernel-package</classname> -parameters. To do that, do <userinput>make-kpkg clean</userinput>. - -</para><para> - -Now, compile the kernel: -<userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. -The version number of <quote>1.0</quote> can be changed at will; this is just -a version number that you will use to track your kernel builds. -Likewise, you can put any word you like in place of <quote>custom</quote> -(e.g., a host name). Kernel compilation may take quite a while, depending on -the power of your machine. - -</para><para> - -Once the compilation is complete, you can install your custom kernel -like any package. As root, do -<userinput>dpkg -i -../&kernelpackage;-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. -The <replaceable>subarchitecture</replaceable> part is an optional -sub-architecture, -<phrase arch="i386"> such as <quote>686</quote>, </phrase> -depending on what kernel options you set. -<userinput>dpkg -i</userinput> will install the -kernel, along with some other nice supporting files. For instance, -the <filename>System.map</filename> will be properly installed -(helpful for debugging kernel problems), and -<filename>/boot/config-&kernelversion;</filename> will be installed, -containing your current configuration set. Your new -kernel package is also clever enough to automatically update your boot -loader to use the new kernel. If you have created a modules package, -you'll need to install that package as well. - -</para><para> - -It is time to reboot the system: read carefully any warning that the -above step may have produced, then <userinput>shutdown -r now</userinput>. - -</para><para> - -For more information on &debian; kernels and kernel compilation, see the -<ulink url="&url-kernel-handbook;">Debian Linux Kernel Handbook</ulink>. -For more information on <classname>kernel-package</classname>, read -the fine documentation in <filename>/usr/share/doc/kernel-package</filename>. - -</para> - </sect2> - </sect1> diff --git a/nl/post-install/mail-setup.xml b/nl/post-install/mail-setup.xml deleted file mode 100644 index 103d06059..000000000 --- a/nl/post-install/mail-setup.xml +++ /dev/null @@ -1,263 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 48595 untranslated --> - - <sect1 id="mail-setup"> - <title>Setting Up Your System To Use E-Mail</title> -<para> - -Today, email is an important part of many people's life. As there are -many options as to how to set it up, and as having it set up correctly is -important for some &debian; utilities, we will try to cover the basics in -this section. - -</para><para> - -There are three main functions that make up an e-mail system. First there is -the <firstterm>Mail User Agent</firstterm> (MUA) which is the program a user -actually uses to compose and read mails. Then there is the <firstterm>Mail -Transfer Agent</firstterm> (MTA) that takes care of transferring messages -from one computer to another. And last there is the <firstterm>Mail -Delivery Agent</firstterm> (MDA) that takes care of delivering incoming mail -to the user's inbox. - -</para><para> - -These three functions can be performed by separate programs, but they can -also be combined in one or two programs. It is also possible to have -different programs handle these functions for different types of mail. - -</para><para> - -On Linux and Unix systems <command>mutt</command> is historically a very -popular MUA. Like most traditional Linux programs it is text based. It is -often used in combination with <command>exim</command> or -<command>sendmail</command> as MTA and <command>procmail</command> as MDA. - -</para><para> - -With the increasing popularity of graphical desktop systems, the use of -graphical e-mail programs like GNOME's <command>evolution</command>, -KDE's <command>kmail</command> or Mozilla's <command>thunderbird</command> -(in &debian; available as <command>icedove</command><footnote> - -<para> -The reason that <command>thunderbird</command> has been renamed to -<command>icedove</command> in &debian; has to do with licensing issues. -Details are outside the scope of this manual. -</para> - -</footnote>) is becoming more popular. These programs combine the function -of a MUA, MTA and MDA, but can — and often are — also be used -in combination with the traditional Linux tools. - -</para> - - <sect2 id="mail-default"> - <title>Default E-Mail Configuration</title> -<para> - -Even if you are planning to use a graphical mail program, it is important -that a traditional MTA/MDA is also installed and correctly set up on your -&debian-gnu; system. Reason is that various utilities running on the -system<footnote> - -<para> -Examples are: <command>cron</command>, <command>quota</command>, -<command>logcheck</command>, <command>aide</command>, … -</para> - -</footnote> can send important notices by e-mail to inform the system -administrator of (potential) problems or changes. - -</para><para> - -For this reason the packages <classname>exim4</classname> and -<classname>mutt</classname> will be installed by default (provided you -did not unselect the <quote>standard</quote> task during the installation). -<classname>exim4</classname> is a combination MTA/MDA that is relatively -small but very flexible. By default it will be configured to only handle -e-mail local to the system itself and e-mails addressed to the system -administrator (root account) will be delivered to the regular user account -created during the installation<footnote> - -<para> -The forwarding of mail for root to the regular user account is configured -in <filename>/etc/aliases</filename>. If no regular user account was created, -the mail will of course be delivered to the root account itself. -</para> - -</footnote>. - -</para><para> - -When system e-mails are delivered they are added to a file in -<filename>/var/mail/<replaceable>account_name</replaceable></filename>. -The e-mails can be read using <command>mutt</command>. - -</para> - </sect2> - - <sect2 id="mail-outgoing"> - <title>Sending E-Mails Outside The System</title> -<para> - -As mentioned earlier, the installed &debian; system is only set up to handle -e-mail local to the system, not for sending mail to others nor for -receiving mail from others. - -</para><para> - -If you would like <classname>exim4</classname> to handle external e-mail, -please refer to the next subsection for the basic available configuration -options. Make sure to test that mail can be sent and received correctly. - -</para><para> - -If you intend to use a graphical mail program and use a mail server of -your Internet Service Provider (ISP) or your company, there is not really -any need to configure <classname>exim4</classname> for handling external -e-mail. Just configure your favorite graphical mail program to use the -correct servers to send and receive e-mail (how is outside the scope of -this manual). - -</para><para> - -However, in that case you may need to configure individual utilities to -correctly send e-mails. One such utility is <command>reportbug</command>, -a program that facilitates submitting bug reports against &debian; packages. -By default it expects to be able to use <classname>exim4</classname> to -submit bug reports. - -</para><para> - -To correctly set up <command>reportbug</command> to use an external mail -server, please run the command <command>reportbug --configure</command> -and answer <quote>no</quote> to the question if an MTA is available. You -will then be asked for the SMTP server to be used for submitting bug reports. - -</para> - </sect2> - - <sect2 id="config-mta"> - <title>Configuring the Exim4 Mail Transport Agent</title> -<para> - -If you would like your system to also handle external e-mail, you will -need to reconfigure the <classname>exim4</classname> package<footnote> - -<para> -You can of course also remove <classname>exim4</classname> and replace -it with an alternative MTA/MDA. -</para> - -</footnote>: - -<informalexample><screen> -# dpkg-reconfigure exim4-config -</screen></informalexample> - -</para><para> - -After entering that command (as root), you will be asked if you want split -the configuration into small files. If you are unsure, select the default -option. - -</para><para> - -Next you will be presented with several common mail scenarios. Choose the -one that most closely resembles your needs. - -</para> - -<variablelist> -<varlistentry> -<term>internet site</term> -<listitem><para> - -Your system is connected to a network and your mail is sent and -received directly using SMTP. On the following screens you will be -asked a few basic questions, like your machine's mail name, or a list of -domains for which you accept or relay mail. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>mail sent by smarthost</term> -<listitem><para> - -In this scenario your outgoing mail is forwarded to another machine, -called a <quote>smarthost</quote>, which takes care of sending the message -on to its destination. -The smarthost also usually stores incoming mail addressed to your -computer, so you don't need to be permanently online. That also means -you have to download your mail from the smarthost via programs like -fetchmail. - -</para><para> - -In a lot of cases the smarthost will be your ISP's mail server, which -makes this option very suitable for dial-up users. It can also be a -company mail server, or even another system on your own network. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>mail sent by smarthost; no local mail</term> -<listitem><para> - -This option is basically the same as the previous one except that the -system will not be set up to handle mail for a local e-mail domain. Mail -on the system itself (e.g. for the system administrator) will still be -handled. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>local delivery only</term> -<listitem><para> - -This is the option your system is configured for by default. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>no configuration at this time</term> -<listitem><para> - -Choose this if you are absolutely convinced you know what you are -doing. This will leave you with an unconfigured mail system — -until you configure it, you won't be able to send or receive any mail -and you may miss some important messages from your system utilities. - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -If none of these scenarios suits your needs, or if you need a finer -grained setup, you will need to edit configuration files under the -<filename>/etc/exim4</filename> directory after the installation is -complete. More information about <classname>exim4</classname> may be -found under <filename>/usr/share/doc/exim4</filename>; the file -<filename>README.Debian.gz</filename> has further details about -configuring <classname>exim4</classname> and explains where to find -additional documentation. - -</para><para> - -Note that sending mail directly to the Internet when you don't have an -official domain name, can result in your mail being rejected because of -anti-spam measures on receiving servers. Using your ISP's mail server is -preferred. If you still do want to send out mail directly, you may want to -use a different e-mail address than is generated by default. If you use -<classname>exim4</classname> as your MTA, this is possible by adding an -entry in <filename>/etc/email-addresses</filename>. - -</para> - </sect2> - </sect1> diff --git a/nl/post-install/new-to-unix.xml b/nl/post-install/new-to-unix.xml deleted file mode 100644 index e235f3757..000000000 --- a/nl/post-install/new-to-unix.xml +++ /dev/null @@ -1,29 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - - - <sect1 id="unix-intro"> - <title>If You Are New to Unix</title> -<para> - -If you are new to Unix, you probably should go out and buy some books -and do some reading. A lot of valuable information can also be found -in the <ulink url="&url-debian-reference;">Debian Reference</ulink>. -This <ulink url="&url-unix-faq;">list of Unix FAQs</ulink> contains a -number of UseNet documents which provide a nice historical reference. - -</para><para arch="linux-any"> - -Linux is an implementation of Unix. The -<ulink url="&url-ldp;">Linux Documentation Project (LDP)</ulink> -collects a number of HOWTOs and online books -relating to Linux. Most of these documents can be installed locally; -just install the <classname>doc-linux-html</classname> package (HTML -versions) or the <classname>doc-linux-text</classname> package (ASCII -versions), then look in <filename>/usr/share/doc/HOWTO</filename>. -International versions of the LDP HOWTOs are also available as &debian; -packages. - -</para> - - </sect1> diff --git a/nl/post-install/orientation.xml b/nl/post-install/orientation.xml deleted file mode 100644 index 50283724b..000000000 --- a/nl/post-install/orientation.xml +++ /dev/null @@ -1,109 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43576 untranslated --> - - - <sect1 id="debian-orientation"><title>Orienting Yourself to &debian;</title> -<para> - -&debian; is a little different from other distributions. Even if you're -familiar with Linux in other distributions, there are things you -should know about &debian; to help you to keep your system in a good, -clean state. This chapter contains material to help you get oriented; -it is not intended to be a tutorial for how to use &debian;, but just a -very brief glimpse of the system for the very rushed. - -</para> - - <sect2><title>&debian; Packaging System</title> -<para> - -The most important concept to grasp is the &debian; packaging system. -In essence, large parts of your system should be considered under the -control of the packaging system. These include: - -<itemizedlist> -<listitem><para> - -<filename>/usr</filename> (excluding <filename>/usr/local</filename>) - -</para></listitem> -<listitem><para> - -<filename>/var</filename> (you could make -<filename>/var/local</filename> and be safe in there) - -</para></listitem> -<listitem><para> - -<filename>/bin</filename> - -</para></listitem> -<listitem><para> - -<filename>/sbin</filename> - -</para></listitem> -<listitem><para> - -<filename>/lib</filename> - -</para></listitem> -</itemizedlist> - -For instance, if you replace <filename>/usr/bin/perl</filename>, that -will work, but then if you upgrade your <classname>perl</classname> -package, the file you put there will be replaced. Experts can get -around this by putting packages on <quote>hold</quote> in -<command>aptitude</command>. - -</para><para> - -One of the best installation methods is apt. You can use the command -line version <command>apt-get</command> or full-screen text version -<application>aptitude</application>. Note apt will also let you merge -main, contrib, and non-free so you can have export-restricted packages -as well as standard versions. - -</para> - </sect2> - - <sect2><title>Application Version Management</title> -<para> - - -Alternative versions of applications are managed by update-alternatives. If -you are maintaining multiple versions of your applications, read the -update-alternatives man page. - -</para> - </sect2> - - <sect2><title>Cron Job Management</title> -<para> - -Any jobs under the purview of the system administrator should be in -<filename>/etc</filename>, since they are configuration files. If you -have a root cron job for daily, weekly, or monthly runs, put them in -<filename>/etc/cron.{daily,weekly,monthly}</filename>. These are -invoked from <filename>/etc/crontab</filename>, and will run in -alphabetic order, which serializes them. - -</para><para> - -On the other hand, if you have a cron job that (a) needs to run as a -special user, or (b) needs to run at a special time or frequency, you -can use either <filename>/etc/crontab</filename>, or, better yet, -<filename>/etc/cron.d/whatever</filename>. These particular files -also have an extra field that allows you to stipulate the user account -under which the cron job runs. - -</para><para> - -In either case, you just edit the files and cron will notice them -automatically. There is no need to run a special command. For more -information see cron(8), crontab(5), and -<filename>/usr/share/doc/cron/README.Debian</filename>. - -</para> - </sect2> - </sect1> diff --git a/nl/post-install/post-install.xml b/nl/post-install/post-install.xml deleted file mode 100644 index 95eca7933..000000000 --- a/nl/post-install/post-install.xml +++ /dev/null @@ -1,15 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43623 untranslated --> - -<chapter id="post-install"> - <title>Next Steps and Where to Go From Here</title> - -&shutdown.xml; -&new-to-unix.xml; -&orientation.xml; -&further-reading.xml; -&mail-setup.xml; -&kernel-baking.xml; -&rescue.xml; - -</chapter> diff --git a/nl/post-install/rescue.xml b/nl/post-install/rescue.xml deleted file mode 100644 index 5517b5e2d..000000000 --- a/nl/post-install/rescue.xml +++ /dev/null @@ -1,71 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> - - <sect1 id="rescue"> - <title>Recovering a Broken System</title> -<para> - -Sometimes, things go wrong, and the system you've carefully installed is no -longer bootable. Perhaps the boot loader configuration broke while trying -out a change, or perhaps a new kernel you installed won't boot, or perhaps -cosmic rays hit your disk and flipped a bit in -<filename>/sbin/init</filename>. Regardless of the cause, you'll need to -have a system to work from while you fix it, and rescue mode can be useful -for this. - -</para><para> - -<!-- TODO: describe what to do on arches where this isn't set up in the - bootloader --> - -To access rescue mode, type <userinput>rescue</userinput> at the -<prompt>boot:</prompt> prompt, or boot with the -<userinput>rescue/enable=true</userinput> boot parameter. You'll be shown -the first few screens of the installer, with a note in the corner of the -display to indicate that this is rescue mode, not a full installation. Don't -worry, your system is not about to be overwritten! Rescue mode simply takes -advantage of the hardware detection facilities available in the installer to -ensure that your disks, network devices, and so on are available to you -while repairing your system. - -</para><para> - -Instead of the partitioning tool, you should now be presented with a list of -the partitions on your system, and asked to select one of them. Normally, -you should select the partition containing the root file system that you -need to repair. You may select partitions on RAID and LVM devices as well as -those created directly on disks. - -</para><para> - -If possible, the installer will now present you with a shell prompt in the -file system you selected, which you can use to perform any necessary -repairs. - -<phrase arch="any-x86"> -For example, if you need to reinstall the GRUB boot loader into the master -boot record of the first hard disk, you could enter the command -<userinput>grub-install '(hd0)'</userinput> to do so. -</phrase> - -</para><para> - -If the installer cannot run a usable shell in the root file system you -selected, perhaps because the file system is corrupt, then it will issue a -warning and offer to give you a shell in the installer environment instead. -You may not have as many tools available in this environment, but they will -often be enough to repair your system anyway. The root file system you -selected will be mounted on the <filename>/target</filename> directory. - -</para><para> - -In either case, after you exit the shell, the system will reboot. - -</para><para> - -Finally, note that repairing broken systems can be difficult, and this -manual does not attempt to go into all the things that might have gone wrong -or how to fix them. If you have problems, consult an expert. - -</para> - </sect1> diff --git a/nl/post-install/shutdown.xml b/nl/post-install/shutdown.xml deleted file mode 100644 index e71db46d4..000000000 --- a/nl/post-install/shutdown.xml +++ /dev/null @@ -1,31 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - - <sect1 id="shutdown"> - <title>Shutting down the system</title> - -<para> - -To shut down a running &debian-gnu; system, you must not reboot with the -reset switch on the front or back of your computer, or just turn off -the computer. &debian-gnu; should be shut down in a controlled manner, -otherwise files might get lost and/or disk damage might occur. If you run a -desktop environment, there is usually an option to <quote>log out</quote> -available from the application menu that allows you to shutdown (or reboot) -the system. - -</para><para> - -Alternatively you can press the key combination <keycombo> -<keycap>Ctrl</keycap> <keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> -<phrase arch="powerpc"> or <keycombo> <keycap>Control</keycap> -<keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh -systems</phrase>. A last option is to log in as root and type one of the -commands <command>poweroff</command>, <command>halt</command> or -<command>shutdown -h now</command> if either of the key combinations do not -work or you prefer to type commands; use <command>reboot</command> to reboot -the system. - -</para> - </sect1> diff --git a/nl/preface.xml b/nl/preface.xml deleted file mode 100644 index bcd7d5d52..000000000 --- a/nl/preface.xml +++ /dev/null @@ -1,30 +0,0 @@ -<!-- original version: 24750 --> - -<preface> - <title>&debian-gnu; &release; installeren op &architecture;</title> -<para> - -Wij zijn verheugd dat u heeft besloten om &debian; te proberen en weten -zeker dat u zult ontdekken dat de GNU/&arch-kernel; distributie van &debian; uniek -is. &debian-gnu; brengt vrije software van over de hele wereld samen en integreert -deze tot een samenhangend geheel. Wij zijn ervan overtuigd dat u zult -ontdekken dat het resultaat werkelijk meer is dan de som der delen. - -</para><para> - -Wij begrijpen dat velen onder u &debian; zal willen installeren zonder deze -handleiding te lezen en het &debian; installatiesysteem is ontworpen om dit -mogelijk te maken. Als u op dit moment geen gelegenheid heeft om de gehele -installatiehandleiding door te nemen, adviseren wij om tenminste de "Installatie -Howto" te lezen, die u meeneemt door het basis installatie proces en verwijzingen -bevat naar de handleiding voor meer geavanceerde onderwerpen of als er dingen -fout gaan. U vindt de Installatie Howto in <xref linkend="installation-howto"/>. - -</para><para> - -Dat gezegd hebbend, hopen wij dat u de tijd wilt nemen om het merendeel van deze -handleiding door te lezen en dat dit zal leiden tot een beter geïnformeerde en -waarschijnlijk meer succesvolle installatie. - -</para> -</preface> diff --git a/nl/preparing/backup.xml b/nl/preparing/backup.xml deleted file mode 100644 index 24c163dd8..000000000 --- a/nl/preparing/backup.xml +++ /dev/null @@ -1,35 +0,0 @@ -<!-- original version: 61133 --> - - <sect1 id="backup"> - <title>Maak een reservekopie van uw bestaande gegevens!</title> -<para> - -Zorg ervoor dat u, voor u met de installatie start, een reservekopie -maakt van elk bestand dat zich op dit moment op uw systeem bevindt. -Als dit de eerste keer is dat u op uw computer een besturingssysteem -installeert dat van een ander type is dan het besturingssysteem dat bij -de computer is geleverd, dan is de kans groot dat u uw harde schijf -opnieuw zult moeten indelen om ruimte te maken voor &debian-gnu;. Altijd als -u de indeling van uw harde schijf wijzigt, moet u er rekening mee houden -dat alles wat op de harde schijf staat verloren kan gaan, ongeacht het -programma dat u hiervoor gebruikt. De programma's die tijdens de -installatie worden gebruikt zijn behoorlijk betrouwbaar en de meeste worden -al jaren gebruikt; maar ze zijn ook zeer krachtig en een foutieve handeling -kan u in de problemen brengen. Zelfs nadat u een reservekopie heeft gemaakt, -zult u zorgvuldig moeten nadenken over uw antwoorden en keuzen. Twee minuten -nadenken kan uren aan niet noodzakelijk herstelwerk voorkomen. - -</para><para> - -Als u een multi-boot systeem wilt maken, zorg er dan voor dat u de -distributiemedia van de andere aanwezige besturingssystemen bij de hand -heeft. Vooral als u de indeling van uw harde schijf gaat wijzigen, zou -u tot de ontdekking kunnen komen dat u de opstartlader van uw -besturingssysteem opnieuw moet installeren of in veel gevallen het -volledige besturingssysteem en alle bestanden op aangetaste partities. -<!-- FJP Verwijzen naar shareware voor bootsector reparatie? -http://www.winimage.com and http://www.winimage.com/bootpart.htm //--> - -</para> - - </sect1> diff --git a/nl/preparing/bios-setup/i386.xml b/nl/preparing/bios-setup/i386.xml deleted file mode 100644 index 29765d25f..000000000 --- a/nl/preparing/bios-setup/i386.xml +++ /dev/null @@ -1,337 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56425 untranslated --> - -<!-- This section is heavily outdated. It only really describes - older BIOSes and not the current situation. Most of it is not - really relevant for AMD64, but a general description would be. - File should be renamed to x86.xml if a more general text is - written. --> - - <sect2 arch="any-x86" id="bios-setup"><title>Invoking the BIOS Set-Up Menu</title> - -<para> - -BIOS provides the basic functions needed to boot your machine to allow -your operating system to access your hardware. Your system probably -provides a BIOS setup menu, which is used to configure the BIOS. -Before installing, you <emphasis>must</emphasis> ensure that your BIOS -is set up correctly; not doing so can lead to intermittent crashes or -an inability to install &debian;. - -</para><para> - -The rest of this section is lifted from the -<ulink url="&url-pc-hw-faq;"></ulink>, answering the question, <quote>How do I -enter the CMOS configuration menu?</quote>. How you access the BIOS (or -<quote>CMOS</quote>) configuration menu depends on who wrote your BIOS -software: - -</para> - -<!-- From: burnesa@cat.com (Shaun Burnet) --> -<variablelist> - -<varlistentry> - <term>AMI BIOS</term> - <listitem><para> - -<keycap>Delete</keycap> key during the POST (power on self test) - -</para></listitem> -</varlistentry> - -<varlistentry> - <term>Award BIOS</term> - <listitem><para> - -<keycombo> - <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> -</keycombo>, or <keycap>Delete</keycap> key during the POST - -</para></listitem> -</varlistentry> - -<varlistentry><term>DTK BIOS</term> - <listitem><para> - -<keycap>Esc</keycap> key during the POST - -</para></listitem> -</varlistentry> - -<varlistentry><term>IBM PS/2 BIOS</term> - <listitem><para> - -<keycombo> - <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> -</keycombo> -after -<keycombo> - <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> -</keycombo> - -</para></listitem> -</varlistentry> - -<varlistentry> - <term>Phoenix BIOS</term> - <listitem><para> - -<keycombo> - <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> -</keycombo> -or -<keycombo> - <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> -</keycombo> -or -<keycap>F1</keycap> - -</para></listitem> -</varlistentry> -</variablelist> - -<para> - -Information on invoking other BIOS routines can be found in -<ulink url="&url-invoking-bios-info;"></ulink>. - -</para><para> - -Some &arch-title; machines don't have a CMOS configuration menu in the -BIOS. They require a software CMOS setup program. If you don't have -the Installation and/or Diagnostics diskette for your machine, you can -try using a shareware/freeware program. Try looking in -<ulink url="&url-simtel;"></ulink>. - -</para> - </sect2> - - <sect2 arch="any-x86" id="boot-dev-select"><title>Boot Device Selection</title> - -<para> - -Many BIOS setup menus allow you to select the devices that will be -used to bootstrap the system. Set this to look for a bootable -operating system on <filename>A:</filename> (the first floppy disk), -then optionally the first CD-ROM device (possibly appearing as -<filename>D:</filename> or <filename>E:</filename>), and then from -<filename>C:</filename> (the first hard disk). This setting enables -you to boot from either a floppy disk or a CD-ROM, which are the two -most common boot devices used to install &debian;. - -</para><para> - -If you have a newer SCSI controller and you have a CD-ROM device -attached to it, you are usually able to boot from the CD-ROM. All you -have to do is enable booting from a CD-ROM in the SCSI-BIOS of your -controller. - -</para><para> - -Another popular option is to boot from a USB storage device (also called -a USB memory stick or USB key). Some BIOSes can boot directly from a USB -storage device, but some cannot. You may need to configure your BIOS to boot -from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to -get it to boot from the USB device. - -</para><para> - -Here are some details about how to set the boot order. Remember to -reset the boot order after &arch-kernel; is installed, so that you restart -your machine from the hard drive. - -</para> - - <sect3 id="ctbooi"> - <title>Changing the Boot Order on IDE Computers</title> - -<orderedlist> -<listitem><para> - -As your computer starts, press the keys to enter the BIOS -utility. Often, it is the <keycap>Delete</keycap> key. However, -consult the hardware documentation for the exact keystrokes. - -</para></listitem> -<listitem><para> - -Find the boot sequence in the setup utility. Its location depends on -your BIOS, but you are looking for a field that lists drives. - -</para><para> - - -Common entries on IDE machines are C, A, cdrom or A, C, cdrom. - -</para><para> - - -C is the hard drive, and A is the floppy drive. - -</para></listitem> -<listitem><para> - -Change the boot sequence setting so that the CD-ROM or the -floppy is first. Usually, the <keycap>Page Up</keycap> or -<keycap>Page Down</keycap> keys cycle -through the possible choices. - -</para></listitem> -<listitem><para> - -Save your changes. Instructions on the screen tell you how to -save the changes on your computer. - -</para></listitem> -</orderedlist> - </sect3> - - <sect3 id="ctboos"> - <title>Changing the Boot Order on SCSI Computers</title> -<para> - -<orderedlist> -<listitem><para> - -As your computer starts, press the keys to enter the SCSI setup -utility. - -</para><para> - -You can start the SCSI setup utility after the memory check and -the message about how to start the BIOS utility displays when you -start your computer. - -</para><para> - -The keystrokes you need depend on the utility. Often, it is -<keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. -However, consult your hardware documentation for the -exact keystrokes. - -</para></listitem> -<listitem><para> - -Find the utility for changing the boot order. - -</para></listitem> -<listitem><para> - -Set the utility so that the SCSI ID of the CD drive is first on -the list. - -</para></listitem> -<listitem><para> - -Save your changes. Instructions on the screen tell you how to -save the changes on your computer. Often, you must press -<keycap>F10</keycap>. - -</para></listitem> -</orderedlist> - -</para> - </sect3> - </sect2> - - <sect2 arch="any-x86"> - <title>Miscellaneous BIOS Settings</title> - - <sect3 id="cd-settings"><title>CD-ROM Settings</title> -<para> - -Some BIOS systems (such as Award BIOS) allow you to automatically set -the CD speed. You should avoid that, and instead set it to, say, the -lowest speed. If you get <userinput>seek failed</userinput> error -messages, this may be your problem. - -</para> - </sect3> - - <sect3><title>Extended vs. Expanded Memory</title> -<para> - -If your system provides both ex<emphasis>ten</emphasis>ded and -ex<emphasis>pan</emphasis>ded memory, set it so that there is as much -extended and as little expanded memory as possible. &arch-kernel; requires -extended memory and cannot use expanded memory. - -</para> - </sect3> - - <sect3><title>Virus Protection</title> -<para> - -Disable any virus-warning features your BIOS may provide. If you have -a virus-protection board or other special hardware, make sure it is -disabled or physically removed while running GNU/&arch-kernel;. These aren't -compatible with GNU/&arch-kernel;; moreover, due to the file system -permissions and protected memory of the &arch-kernel; kernel, viruses are -almost unheard of<footnote> -<para> - -After installation you can enable Boot Sector protection if you -want. This offers no additional security in &arch-kernel; but if you also run -Windows it may prevent a catastrophe. There is no need to tamper with -the Master Boot Record (MBR) after the boot manager has been set up. - -</para> -</footnote>. - -</para> - </sect3> - - <sect3><title>Shadow RAM</title> -<para> - -Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS -caching. You may see settings for <quote>Video BIOS Shadow</quote>, -<quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> -all shadow RAM. Shadow -RAM is used to accelerate access to the ROMs on your motherboard and -on some of the controller cards. &arch-kernel; does not use these ROMs once it -has booted because it provides its own faster 32-bit software in place -of the 16-bit programs in the ROMs. Disabling the shadow RAM may make -some of it available for programs to use as normal memory. Leaving -the shadow RAM enabled may interfere with &arch-kernel; access to hardware -devices. - -</para> - </sect3> - - <sect3><title>Memory Hole</title> -<para> - -If your BIOS offers something like <quote>15–16 MB Memory -Hole</quote>, please disable that. &arch-kernel; expects to find memory there if -you have that much RAM. - -</para><para> - -We have a report of an Intel Endeavor motherboard on which there is an -option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. -This had two settings: <quote>Disabled</quote> and <quote>1 -Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. -When disabled, the installation floppy was not read correctly, and the -system eventually crashed. At this writing we don't understand what's -going on with this particular device — it just worked with that -setting and not without it. - -</para> - </sect3> - -<!-- no other platforms other than x86 provide this sort of thing, AFAIK --> - - <sect3><title>Advanced Power Management</title> -<para> - -If your motherboard provides Advanced Power Management (APM), -configure it so that power management is controlled by APM. Disable -the doze, standby, suspend, nap, and sleep modes, and disable the hard -disk's power-down timer. &arch-kernel; can take over control of these modes, -and can do a better job of power-management than the BIOS. - -</para> - </sect3> - </sect2> diff --git a/nl/preparing/bios-setup/powerpc.xml b/nl/preparing/bios-setup/powerpc.xml deleted file mode 100644 index 2725ca64a..000000000 --- a/nl/preparing/bios-setup/powerpc.xml +++ /dev/null @@ -1,52 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 54285 untranslated --> - - - <sect2 arch="powerpc" id="invoking-openfirmware"> - <title>Invoking OpenFirmware</title> -<para> - -There is normally no need to set up the BIOS (called OpenFirmware) on -&arch-title; systems. PReP and CHRP are equipped with OpenFirmware, -but unfortunately, the means you use to invoke it vary from -manufacturer to manufacturer. You'll have to consult the hardware -documentation which came with your machine. - -</para><para> - -On &arch-title; Macintoshes, you invoke OpenFirmware with -<keycombo><keycap>Command (cloverleaf/Apple)</keycap><keycap>Option</keycap><keycap>o</keycap><keycap>f</keycap></keycombo> -while booting. Generally it will check for these keystrokes after the -chime, but the exact timing varies from model to model. See -<ulink url="&url-netbsd-powerpc-faq;"></ulink> for more hints. - -</para><para> - -The OpenFirmware prompt looks like this: - -<informalexample><screen> -ok -0 > -</screen></informalexample> - -Note that on older model &arch-title; Macs, the default and sometimes -hardwired I/O for OpenFirmware user interaction is through the serial -(modem) port. If you invoke OpenFirmware on one of these machines, you -will just see a black screen. In that case, a terminal program running -on another computer, connected to the modem port, is needed to -interact with OpenFirmware. - -</para><para> - -The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 -and 2.4, is broken. These machines will most likely not be able to -boot from the hard drive unless the firmware is patched. A firmware -patch is included in the <application>System Disk 2.3.1</application> -utility, available from Apple at -<ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>. -After unpacking the utility in MacOS, and launching it, select the -<guibutton>Save</guibutton> button to have the firmware patches -installed to nvram. - -</para> - </sect2> diff --git a/nl/preparing/bios-setup/s390.xml b/nl/preparing/bios-setup/s390.xml deleted file mode 100644 index 1538023f9..000000000 --- a/nl/preparing/bios-setup/s390.xml +++ /dev/null @@ -1,106 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43655 untranslated --> - - - <sect2 arch="s390"><title>BIOS Setup</title> -<para> - -In order to install &debian-gnu; on a &arch-title; or zSeries -machine you have first boot a kernel into the system. The boot -mechanism of this platform is inherently different to other ones, -especially from PC-like systems: there are no floppy devices available -at all. You will notice another big difference while you work with -this platform: most (if not all) of the time you will work remote, -with the help of some client session software like telnet, or a -browser. This is due to that special system architecture where the -3215/3270 console is line-based instead of character-based. - -</para><para> - -Linux on this platform runs either natively on the bare machine, in a -so-called LPAR (Logical Partition) or in a virtual machine supplied by -the VM system. You can use a boot tape on all of those systems; you -may use some other boot media, too, but those may not be generally -available. For example, you can use the virtual card reader of a -virtual machine, or boot from the HMC (Hardware Management Console) of -an LPAR if the HMC and this option is available for you. - -</para><para> - -Before you actually perform an installation, you have to go over some -design and preparation steps. IBM has made documentation available -about the whole process, e.g. how to prepare an installation medium -and how actually to boot from that medium. Duplicating that information -here is neither possible nor necessary. However, we will describe -here which kind of &debian;-specific data is needed and where to find it. -Using both sources of information, you have to prepare your machine -and the installation medium before you can perform a boot from it. -When you see the welcome message in your client session, return to this -document to go through the &debian;-specific installation steps. - -</para> - </sect2> - - <sect2 arch="s390"> - <title>Native and LPAR installations</title> -<para> - -Please refer to chapter 5 of the -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> -Linux for &arch-title;</ulink> -Redbook and chapter 3.2 of the -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> -Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> -Redbook on how to set up an LPAR for Linux. - -</para> - </sect2> - - <sect2 arch="s390"> - <title>Installation as a VM guest</title> - -<para> - -Please refer to chapter 6 of the -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> -Linux for &arch-title;</ulink> -Redbook and chapter 3.1 of the -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> -Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> -Redbook on how to set up a VM guest for running Linux. - -</para><para> - -You need to copy all the files from the <filename>generic</filename> -sub-directory to your CMS disk. Be sure to transfer -<filename>kernel.debian</filename> and -<filename>initrd.debian</filename> in binary mode with a fixed record -length of 80 characters. - -</para> - </sect2> - - <sect2 arch="s390"> - <title>Setting up an installation server</title> - -<para> - -If you don't have a connection to the Internet (either directly or via -a web proxy) you need to create a local installation server that can -be accessed from your S/390. This server keeps all the packages -you want to install and must make them available using NFS, HTTP or -FTP. - -</para><para> - -The installation server needs to copy the exact directory structure -from any &debian-gnu; mirror, but only the s390 and -architecture-independent files are required. You can also copy the -contents of all installation CDs into such a directory tree. - -</para><para condition="FIXME"> - -<emphasis>FIXME: more information needed — from a Redbook?</emphasis> - -</para> - </sect2> diff --git a/nl/preparing/bios-setup/sparc.xml b/nl/preparing/bios-setup/sparc.xml deleted file mode 100644 index 22b4c13f6..000000000 --- a/nl/preparing/bios-setup/sparc.xml +++ /dev/null @@ -1,103 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43641 untranslated --> - - - <sect2 arch="sparc" id="invoking-openboot"><title>Invoking OpenBoot</title> - -<para> - -OpenBoot provides the basic functions needed to boot the &arch-title; -architecture. This is rather similar in function to the BIOS in the -x86 architecture, although much nicer. The Sun boot PROMs have a -built-in forth interpreter which lets you do quite a number of things -with your machine, such as diagnostics and simple scripts. - -</para><para> - -To get to the boot prompt you need to hold down the -<keycap>Stop</keycap> key (on older type 4 keyboards, use the -<keycap>L1</keycap> key, if you have a PC keyboard adapter, use -the <keycap>Break</keycap> key) and press the -<keycap>A</keycap> key. The boot PROM will give you a prompt, -either <userinput>ok</userinput> or <userinput>></userinput>. It is -preferred to have the <userinput>ok</userinput> prompt. So if you get -the old style prompt, hit the <keycap>n</keycap> key to get the new -style prompt. - -</para><para> - -If you are using a serial console, send a break to the machine. With Minicom, -use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, then type -<userinput>%~break</userinput>. Consult the documentation of your terminal -emulator if you are using a different program. - -</para> - </sect2> - - <sect2 arch="sparc" id="boot-dev-select-sun"> - <title>Boot Device Selection</title> - -<para> - -You can use OpenBoot to boot from specific devices, and also to change -your default boot device. However, you need to know some details -about how OpenBoot names devices; it's considerably different from Linux -device naming, described in <xref linkend="device-names"/>. -Also, the command will vary a bit, depending on what version of -OpenBoot you have. More information about OpenBoot can be found in -the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. - -</para><para> - -Typically, with newer revisions, you can use OpenBoot devices such as -<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, -<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious -meanings; the <quote>net</quote> device is for booting from the network. -Additionally, the device name can specify a particular partition of a disk, -such as <quote>disk2:a</quote> to boot disk2, first partition. Full -OpenBoot device names have the form: - -<informalexample> -<screen> -<replaceable>driver-name</replaceable>@ -<replaceable>unit-address</replaceable>: -<replaceable>device-arguments</replaceable> -</screen></informalexample> - -In older revisions of OpenBoot, device naming is a bit different: the -floppy device is called <quote>/fd</quote>, and SCSI disk devices are of -the form <quote>sd(<replaceable>controller</replaceable>, -<replaceable>disk-target-id</replaceable>, -<replaceable>disk-lun</replaceable>)</quote>. The command -<userinput>show-devs</userinput> in newer OpenBoot revisions is useful -for viewing the currently configured devices. For full information, -whatever your revision, see the -<ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>. - -</para><para> - -To boot from a specific device, use the command <userinput>boot -<replaceable>device</replaceable></userinput>. You can set this -behavior as the default using the <userinput>setenv</userinput> -command. However, the name of the variable to set changed between -OpenBoot revisions. In OpenBoot 1.x, use the command -<userinput>setenv boot-from -<replaceable>device</replaceable></userinput>. In later revisions of -OpenBoot, use the command <userinput>setenv boot-device -<replaceable>device</replaceable></userinput>. Note, this is also -configurable using the <command>eeprom</command> command on Solaris, -or modifying the appropriate files in -<filename>/proc/openprom/options/</filename>, for example under Linux: - -<informalexample><screen> -# echo disk1:1 > /proc/openprom/options/boot-device -</screen></informalexample> - -and under Solaris: - -<informalexample><screen> -eeprom boot-device=disk1:1 -</screen></informalexample> - -</para> - </sect2> diff --git a/nl/preparing/install-overview.xml b/nl/preparing/install-overview.xml deleted file mode 100644 index bb23295a4..000000000 --- a/nl/preparing/install-overview.xml +++ /dev/null @@ -1,186 +0,0 @@ -<!-- original version: 56322 --> - - <sect1 id="install-overview"> - <title>Overzicht van het installatieproces</title> -<para> - -Allereerst een opmerking over herinstallaties. Bij &debian; zal zich -slechts zeer zelden een omstandigheid voordoen die een volledige -herinstallatie noodzakelijk maakt; waarschijnlijk is een storing in de -harde schijf nog de meest voorkomende situatie. - -</para><para> - -Veel gangbare besturingssystemen kunnen een volledige herinstallatie -noodzakelijk maken als zich ernstige fouten voordoen of bij opwaardering -naar een nieuwe versie van het besturingssysteem. Zelfs als geen volledig -nieuwe installatie nodig is, moeten programma's die u gebruikt veelal -opnieuw geïnstalleerd worden voordat zij fatsoenlijk werken onder het -nieuwe besturingssysteem. - -</para><para> - -Onder &debian-gnu; is het veel waarschijnlijker dat uw besturingssysteem -gerepareerd kan worden als er iets mis gaat. Bij een opwaardering zal nooit -een complete installatie nodig zijn: het is altijd mogelijk om het bestaande -systeem op te waarderen. En de programma's zijn vrijwel altijd compatibel -met opeenvolgende releases van het besturingssysteem. Als een nieuwe versie -van een programma ook nieuwe ondersteunende software vereist, zorgt de manier -waarop &debian; pakketten maakt ervoor dat alle software die benodigd is, -automatisch wordt geïdentificeerd en geïnstalleerd. Omdat zoveel aandacht -is besteed aan het voorkomen van de noodzaak om opnieuw te installeeren, -zou u dat als uw allerlaatste redmiddel moeten beschouwen. Het installatiesysteem -is <emphasis>niet</emphasis> ontworpen om een installatie over een bestaand -systeem heen uit te voeren. - -</para><para> - -Hierna volgt een routekaart voor de stappen die u zult volgen tijdens het -installatieproces. -<!-- 'Road map'? Ze lijken Bush wel ;-( //--> - -</para> - -<orderedlist> -<listitem><para> - -Maak een reservekopie van bestaande gegevens en documenten op de harde schijf -waarop u van plan bent &debian; te installeren. - -</para></listitem> -<listitem><para> - -Verzamel informatie over uw computer en benodigde documentatie voordat u -met de installatie begint. - -</para></listitem> -<listitem><para> - -Maak op uw harde schijf ruimte vrij waarin door &debian; partities kunnen worden -aangemaakt. - -</para></listitem> -<listitem><para> - -Pak of download de installatiesoftware en eventueel bestanden met specifieke -stuurbestanden die voor uw machine nodig zijn (dit geldt niet voor gebruikers -van de &debian; Installatie CD). - -</para></listitem> -<listitem><para> - -Prepareer magneetbanden/diskettes/USB-sticks voor het opstarten van uw systeem -of plaats opstartbestanden (de meeste gebruikers van &debian; Installatie CDs -kunnen opstarten vanaf één van de CDs). -<!-- FJP Wat wordt bedoeld met 'place boot files'? Bug in origineel. //--> - -</para></listitem> -<listitem><para> - -Start de computer op met het installatiesysteem. - -</para></listitem> -<listitem arch="not-s390"><para> - -Selecteer de taal voor het installatiesysteem. - -</para></listitem> -<listitem arch="not-s390"><para> - -Activeer de Ethernet netwerkverbinding (indien beschikbaar). - -</para></listitem> - -<listitem arch="s390"><para> - -Configureer één netwerkinterface. - -</para></listitem> -<listitem arch="s390"><para> - -Open een ssh-verbinding met het nieuwe systeem. - -</para></listitem> -<listitem arch="s390"><para> - -Maak verbinding met één of meerdere DASDs (Direct Access Storage Device). - -</para></listitem> - -<listitem><para> - -Maak en mount de partities waarop &debian; zal worden geïnstalleerd. - -</para></listitem> -<listitem><para> - -Volg de volledig automatische download/installatie/instelling van het -<firstterm>basissysteem</firstterm>. - -</para></listitem> -<listitem><para> - -Installeer een <firstterm>opstartlader</firstterm> die &debian-gnu; en/of uw -bestaande systeem kan opstarten. - -</para></listitem> -<listitem><para> - -Start de computer opnieuw op met het nieuw geïnstalleerde systeem. - -</para></listitem> -</orderedlist> - -<para condition="gtk"> - -Voor &arch-title; heeft u de optie om gebruik te maken van een -<phrase arch="powerpc">experimentele</phrase> -grafische versie van het installatiesysteem. Zie <xref linkend="graphical"/> -voor nadere informatie over deze grafische variant. - -</para><para> - -Voor het geval u problemen tegenkomt tijdens de installatie, kan het nuttig zijn -om een beeld te hebben van de pakketten die een rol spelen in de verschillende -stappen. Hieronder introduceren wij de belangrijkste acteurs in dit -installatietheater. - -</para><para> - -De installatiesoftware, <classname>debian-installer</classname>, is het -voornaamste onderwerp van deze handleiding. Zij verzorgt de herkenning van -hardware en laadt geschikte stuurprogramma's, gebruikt -<classname>dhclient</classname> voor het opzetten van de netwerkverbinding, -en start <classname>debootstrap</classname> voor de installatie van de pakketten -voor het basissysteem. -Er zijn nog veel meer actoren die elk een kleinere rol spelen in dit proces, maar -<classname>debian-installer</classname> heeft haar taak volbracht op het moment -dat u het nieuwe systeem voor het eerst opstart. - -</para><para> - -Om het systeem aan te passen aan uw behoeften, biedt <classname>tasksel</classname> -u de mogelijkheid om diverse voorgedefinieerde softwarebundels, zoals een -webserver of desktopomgeving, te installeren. - -</para><para> - -Een belangrijke optie tijdens de installatie is om al dan niet een grafische -desktopomgeving, bestaande uit het X Window System en één van de beschikbare -grafische desktopomgevingen, te installeren. Als u ervoor kiest om de taak -<quote>Desktopomgeving</quote> niet te selecteren, krijgt u slechts een -relatief basaal, opdrachtregel georienteerd systeem. -Installatie van de taak <quote>Desktopomgeving</quote> is optioneel omdat het -relatief veel schijfruimte vereist en omdat veel &debian-gnu; systemen in gebruik -zijn als server en voor het vervullen van hun taak eigenlijk helemaal geen -behoefte aan een grafische gebruikersinterface bestaat. - -</para><para arch="not-s390"> - -U dient zich ervan bewust te zijn dat het X Window System volledig los staat -van <classname>debian-installer</classname> en in feite veel complexer is. -De installatie van het X Window System en het oplossen van problemen tijdens -de installatie hiervan, vallen buiten de scope van deze handleiding. - -</para> - </sect1> diff --git a/nl/preparing/minimum-hardware-reqts.xml b/nl/preparing/minimum-hardware-reqts.xml deleted file mode 100644 index 8fd2cd028..000000000 --- a/nl/preparing/minimum-hardware-reqts.xml +++ /dev/null @@ -1,102 +0,0 @@ -<!-- original version: 61133 --> - - <sect1 id="minimum-hardware-reqts"> - <title>Voldoen aan de minimum hardware-eisen</title> -<para> - -Nadat u de informatie over de apparatuur in uw computer heeft verzameld, -moet nog worden gecontroleerd of u daarmee de installatie die u van plan -bent, kunt uitvoeren. - -</para><para arch="not-s390"> - -Afhankelijk van uw behoeften, zou u op sommige punten met minder kunnen -volstaan dan de in de tabel hieronder aanbevolen specificaties. - -</para><para arch="any-x86"> - -Voor een desktop systeem wordt tenminste een Pentium 4, 1GHz systeem -aanbevolen. - -</para><para arch="powerpc"> - -Een willekeurige 'OldWorld' of 'NewWorld' PowerPC kan goed dienst doen als -desktop systeem. - -</para> - -<table> -<title>Aanbevolen minimum systeemeisen</title> -<tgroup cols="4"> -<thead> -<row> - <entry>Type installatie</entry> - <entry>RAM (minimum)</entry> - <entry>RAM (aanbevolen)</entry> - <entry>Harde schijf</entry> -</row> -</thead> - -<tbody> -<row> - <entry>Geen desktop</entry> - <entry>64 megabytes</entry> - <entry>256 megabytes</entry> - <entry>1 gigabyte</entry> -</row><row> - <entry>Met desktop</entry> - <entry>128 megabytes</entry> - <entry>512 megabytes</entry> - <entry>5 gigabytes</entry> -</row> - -</tbody></tgroup></table> - -<para> - -De eigenlijke minimum vereisten voor beschikbaar geheugen zijn een stuk -kleiner dan de getallen in deze tabel. Afhankelijk van de architectuur -kan &debian; worden geïnstalleerd met slechts 20MB (voor s390) tot 60MB -(voor amd64). Hetzelfde geldt, zeker als u selectief bent in welke -applicaties u installeert, voor de harde schijf capaciteit. Zie -<xref linkend="tasksel-size-list"/> voor aanvullende informatie over -benodigde harde schijf capaciteit. - -</para><para arch="not-s390"> - -Ook op oudere systemen of systemen met beperkte capaciteiten is het mogelijk -om een grafische desktopomgeving te gebruiken. Het is dan echter we aan -te raden om een vensterbeheerder te kiezen die een kleinere aanslag op de -baschikbare capaciteit doet dan die van de GNOME en KDE desktopomgevingen. -Alternatieven zijn bijvoorbeeld <classname>xfce4</classname>, -<classname>icewm</classname> en <classname>wmaker</classname>, maar er zijn -ook andere beschikbaar. - -</para><para> - -Het is vrijwel onmogelijk om algemene richtlijnen te geven voor benodigde -geheugen en harde schijf capaciteit voor server installaties omdat deze -te zeer afhankelijk zijn van het beoogde gebruik van de server. - -</para><para> - -Bedenk dat deze groottes exclusief alle andere zaken zijn die gewoonlijk -op een machine aanwezig zijn, zoals gebruikersbestanden, e-mail en gegevens. -Het is altijd het beste om de benodigde ruimte voor uw eigen bestanden en -gegevens royaal in te schatten. - -</para><para> - -De schijfruimte nodig voor een soepele werking van het &debian-gnu; systeem -zelf is reeds in deze aanbevelingen verwerkt. -De partitie <filename>/var</filename> in het -bijzonder bevat veel &debian;-specifieke statusinformatie naast de reguliere -inhoud, zoals logbestanden. De bestanden van <command>dpkg</command> (met -informatie over alle geïnstalleerde pakketten) kan makkelijk 40MB gebruiken. -Verder worden hier door <command>apt-get</command> pakketten die gedownload -worden, opgeslagen voordat deze worden geïnstalleerd. Normaal gesproken dient -u tenminste 200MB te reserveren voor <filename>/var</filename>. - -</para> - - </sect1> diff --git a/nl/preparing/needed-info.xml b/nl/preparing/needed-info.xml deleted file mode 100644 index b4d2236f4..000000000 --- a/nl/preparing/needed-info.xml +++ /dev/null @@ -1,402 +0,0 @@ -<!-- original version: 61147 --> - - <sect1 id="needed-info"> - <title>Benodigde informatie</title> - - <sect2> - <title>Documentatie</title> - - <sect3> - <title>Installatiehandleiding</title> - -<para condition="for_cd"> - -Het document dat u nu aan het lezen bent, als gewoon ASCII tekstbestand -of in HTML- of PDF-formaat. - -</para> - -<itemizedlist condition="for_cd"> -&list-install-manual-files; -</itemizedlist> - -<para condition="for_wdo"> - -Het document dat u nu aan het lezen bent. Dit is de officiële versie van -de installatiehandleiding voor release &releasename; van &debian; en is -beschikbaar in <ulink url="&url-release-area;/installmanual">diverse -bestandsformaten en vertalingen</ulink>. - -</para> - -<para condition="for_alioth"> - -Het document dat u nu aan het lezen bent. Dit is de ontwikkelingsversie van -de installatiehandleiding voor de volgende release van &debian; en is -beschikbaar in <ulink url="&url-d-i-alioth-manual;">diverse -bestandsformaten en vertalingen</ulink>. - -</para> -</sect3> - - <sect3><title>Hardware documentatie</title> -<para> - -Bevat vaak bruikbare informatie over de configuratie of het gebruik -van uw hardware. -</para> - - <itemizedlist arch="x86;sparc;mips;mipsel"> -<listitem arch="x86"><para> - -<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> - -</para></listitem> - -<listitem arch="sparc"><para> - -<ulink url="&url-sparc-linux-faq;">Linux for SPARC Processors FAQ</ulink> - -</para></listitem> - -<listitem arch="mips;mipsel"><para> - -<ulink url="&url-linux-mips;">Linux/Mips website</ulink> - -</para></listitem> - -</itemizedlist> - </sect3> - - <sect3 arch="s390"> - <title>Naslag voor &arch-title;-hardware</title> -<para> - -Installatie-instructies en stuurprogramma's ((DASD, XPRAM, Console, -tape, z90 crypto, chandev, netwerk) voor Linux op &arch-title; gebruik -makend van kernel 2.4. - -</para> - -<itemizedlist> -<listitem><para> - -<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/docu/l390dd08.pdf">Device Drivers and Installation Commands</ulink> - -</para></listitem> -</itemizedlist> - -<para> - -Redbook van IBM waarin is beschreven hoe Linux kan worden gecombineerd -met z/VM op zSeries en &arch-title; hardware. - -</para> - -<itemizedlist> -<listitem><para> - -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf"> -Linux for &arch-title;</ulink> - -</para></listitem> -</itemizedlist> - -<para> - -Redbook van IBM waarin de Linux distributies die beschikbaar zijn voor -het mainframe zijn beschreven. - -</para> - -<itemizedlist> -<listitem><para> - -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> -Linux for IBM eServer zSeries and &arch-title;: Distributions</ulink> - -</para></listitem> -</itemizedlist> - </sect3> - </sect2> - - - <sect2 id="fsohi"> - <title>Bronnen voor informatie over apparatuur</title> -<para> - -In veel gevallen zal het installatiesysteem in staat zijn om uw hardware -automatisch te herkennen. Wij adviseren u echter, om voorbereid te zijn, -om uzelf voor de installatie vertrouwd te maken met uw apparatuur. - -</para><para> - -Informatie over apparatuur kan worden verzameld op basis van: - -</para> - -<itemizedlist> -<listitem><para> - -De handleidingen die bij uw hardware behoren. - -</para></listitem> -<listitem><para> - -De configurartieschermen voor het BIOS van uw computer. U kunt deze schermen -bekijken door bepaalde toetsen in te drukken tijdens het opstarten van uw -computer. Welke toets(en) u moet indrukken vindt u in uw handleiding. -Vaak is dit de <keycap>Delete</keycap> toets of één van de functietoetsen. -<!-- FJP: op al mijn computers is het één van de functietoetsen //--> - -</para></listitem> -<listitem><para> - -De verpakkingen van uw hardware. - -</para></listitem> - -<listitem arch="any-x86"><para> - -Het Systeem-venster in het Configuratiescherm (Control Panel) van Windows. - -</para></listitem> -<listitem><para> - -Systeemopdrachten of hulpprogramma's in andere besturingssystemen, waaronder -programma's voor bestandsbeheer. Deze bron is met name geschikt om informatie -over het interne geheugen en harde schijf capaciteit te verkrijgen. -<!-- FJP Bedoelen ze niet 'RAM memory and hard drive capacity'? //--> - -</para></listitem> -<listitem><para> - -Uw systeembeheerder of Internetprovider (ISP). Deze bronnen kunnen u -vertellen welke instellingen u nodig heeft voor de configuratie van -uw netwerk en e-mail. - -</para></listitem> -</itemizedlist> - -<para> - -<table> -<title>Voor een installatie benodigde informatie over hardware</title> -<tgroup cols="2"> -<thead> -<row> - <entry>Hardware</entry><entry>Mogelijk benodigde informatie</entry> -</row> -</thead> - -<tbody> -<row arch="not-s390"> - <entry morerows="5">Harde schijven</entry> - <entry>Hoeveel heeft u er.</entry> -</row> -<row arch="not-s390"><entry>Hun volgorde in het systeem.</entry></row> -<row arch="not-s390"> - <entry>Zijn ze IDE (ook wel aangeduid met PATA), SATA of SCSI.</entry> -</row> -<row arch="not-s390"><entry>Beschikbare vrije ruimte.</entry></row> -<row arch="not-s390"><entry>Partities.</entry></row> -<row arch="not-s390"> - <entry>Op welke partities andere besturingssystemen geïnstalleerd zijn.</entry> -</row> - -<row arch="not-s390"> - <entry morerows="5">Beeldscherm</entry> - <entry>Model en fabrikant.</entry> -</row> -<row arch="not-s390"><entry>Ondersteunde resoluties.</entry></row> -<row arch="not-s390"><entry>Horizontale frequentie.</entry></row> -<row arch="not-s390"><entry>Verticale frequentie.</entry></row> -<row arch="not-s390"> - <entry>Ondersteunde kleurdieptes (aantal kleuren).</entry> -</row> -<row arch="not-s390"><entry>Grootte van het scherm.</entry></row> - -<row arch="not-s390"> - <entry morerows="3">Muis</entry> - <entry>Type: serieel, PS/2 of USB.</entry> -</row> -<row arch="not-s390"><entry>Poort.</entry></row> -<row arch="not-s390"><entry>Fabrikant.</entry></row> -<row arch="not-s390"><entry>Aantal knoppen.</entry></row> - -<row arch="not-s390"> - <entry morerows="1">Netwerk</entry> - <entry>Model en fabrikant.</entry> -</row> -<row arch="not-s390"><entry>Type van de adapter.</entry></row> - -<row arch="not-s390"> - <entry morerows="1">Printer</entry> - <entry>Model en fabrikant.</entry> -</row> -<row arch="not-s390"><entry>Ondersteunde afdrukresolities.</entry></row> - -<row arch="not-s390"> - <entry morerows="2">Videokaart</entry> - <entry>Model en fabrikant.</entry> -</row> -<row arch="not-s390"><entry>Beschikbaar videogeheugen.</entry></row> -<row arch="not-s390"> - <entry>Ondersteunde resoluties en kleurdieptes (deze dient u te controleren - ten opzichte van de mogelijkheden van uw beeldscherm).</entry> -</row> - -<row arch="s390"> - <entry morerows="1">DASD</entry> - <entry>Apparaatnummers.</entry> -</row> -<row arch="s390"><entry>Beschikbare vrije ruimte.</entry></row> - -<row arch="s390"> - <entry morerows="2">Netwerk</entry> - <entry>Type van de adapter.</entry> -</row> -<row arch="s390"><entry>Apparaatnummers.</entry></row> -<row arch="s390"><entry>Het relatieve apparaatnummer voor OSA kaarten.</entry></row> - -</tbody></tgroup></table> - -</para> - </sect2> - - - <sect2> - <title>Hardware compatibiliteit</title> - -<para> - -Veel merkproducten werken zonder problemen onder &arch-kernel;. Sterker nog, -de ondersteuning van apparatuur binnen &arch-kernel; verbetert met de dag. -Toch ondersteunt &arch-kernel; nog niet dezelfde variëteit aan apparatuur als -sommige andere besturingssystemen. -<!-- s/hardware for/hardware support for/ ? //--> - -</para><para arch="any-x86"> - -In het bijzonder kan &arch-kernel; geen hardware aansturen die vereist dat -een versie van Microsoft Windows actief is. - -</para><para arch="x86"> - -Hoewel het mogelijk is om sommige Windows-specifieke apparatuur onder -Linux aan de praat te krijgen, vereist dit vaak extra inspanning. Daarnaast -horen de stuurprogramma's voor Windows-specifieke apparatuur vaak bij één -bepaalde versie van de Linux kernel waardoor ze snel verouderd kunnen raken. - -</para><para arch="any-x86"> - -De meest voorkomende apparatuur van dit type zijn de zogenaamde win-modems. -Maar ook printers en andere apparatuur kunnen Windows-specifiek zijn. - -</para><para> - -U kunt de compabibiliteit van apparatuur vaststellen door: - -<itemizedlist> -<listitem><para> - -De websites van fabrikanten te raadplegen voor nieuwe stuurprogramma's. - -</para></listitem> -<listitem><para> - -Op websites of in handleidingen te zoeken naar informatie over emulatie. -Minder bekende merken kunnen soms gebruik maken van de stuurprogramma's -of instellingen van merkapparatuur. - -</para></listitem> -<listitem><para> - -De overzichten van hardware compatibiliteit voor &arch-kernel; te raadplegen op -websites gericht op uw platform. - -</para></listitem> -<listitem><para> - -Op het Internet te zoeken naar de ervaringen van andere gebruikers. - -</para></listitem> -</itemizedlist> - -</para> - </sect2> - - - <sect2> - <title>Netwerkinstellingen</title> - -<para> - -Als uw computer 24 uur per dag is aangesloten op een netwerk (dus een -Ethernet- of vergelijkbare verbinding — niet een PPP-verbinding) -kunt u deze informatie opvragen bij uw netwerkbeheerder. - -<itemizedlist> -<listitem><para> - -Uw computernaam (mogelijk mag u die zelf bepalen). - -</para></listitem> -<listitem><para> - -De domeinnaam van uw netwerk. - -</para></listitem> -<listitem><para> - -Het IP-adres van uw computer. - -</para></listitem> -<listitem><para> - -Het voor uw netwerk te gebruiken netwerkmasker. - -</para></listitem> -<listitem><para> - -Het IP-adres van het systeem (de 'gateway') waarlangs u toegang kunt krijgen tot -andere netwerken, waaronder het Internet (uiteraard <emphasis>alleen</emphasis> -als uw netwerk over een dergelijke gateway beschikt). -<!-- FJP Vertaling 'gateway'? //--> - -</para></listitem> -<listitem><para> - -Het systeem op uw netwerk dat u als DNS-server (Domain Name Service) -kunt gebruiken. - -</para></listitem> -</itemizedlist> - -</para><para> - -Als uw netwerkbeheerder echter aangeeft dat er een DHCP-server beschikbaar -is en dat het gebruik daarvan de voorkeur verdient, dan heeft u deze -informatie niet nodig omdat de DHCP-server die tijdens het installatieproces -automatisch beschikbaar zal stellen. - -</para><para> - -Als u gebruik maakt van een draadloos netwerk, zou u ook moeten uitzoeken: - -<itemizedlist> -<listitem><para> - -ESSID van uw draadloze netwerk. -</para></listitem> -<listitem><para> - -WEP-beveiligingssleutel (indien van toepassing). - -</para></listitem> -</itemizedlist> - -</para> - </sect2> - - </sect1> diff --git a/nl/preparing/non-debian-partitioning.xml b/nl/preparing/non-debian-partitioning.xml deleted file mode 100644 index 82e1387ef..000000000 --- a/nl/preparing/non-debian-partitioning.xml +++ /dev/null @@ -1,195 +0,0 @@ -<!-- original version: 61147 --> - - <sect1 id="non-debian-partitioning"> - <title>Uw harde schijf vooraf indelen voor een multi-boot systeem</title> -<para> - -Met 'het indelen van uw harde schijf' wordt bedoeld het verdelen van de -totale capaciteit van uw schijf in parten. Elk part is vervolgens -onafhankelijk van de andere. Het is enigszins vergelijkbaar met het bouwen -van muren in een huis; als u daarna meubelen in één kamer plaatst, heeft -dit geen invloed op de andere kamers. - -</para><para arch="s390"> - -Waar in deze paragraaf wordt gesproken over <quote>harde schijven</quote>, -dient u dit voor de &arch-title;-wereld te lezen als DASDs of VM-minidisks. -Analoog dient u systeem of machine te lezen als LPAR of VM-guest. - -</para><para> - -Als er al een besturingssysteem op uw systeem aanwezig is - -<phrase arch="any-x86"> -(Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, FreeBSD, …) -</phrase> - -<phrase arch="s390"> -(VM, z/OS, OS/390, …) -</phrase> - -en u wilt &debian; op dezelfde harde schijf installeren, dan zult u de schijf -moeten herindelen. &debian; vereist eigen partities op de harde schijf. -Het kan niet worden geïnstalleerd op Windows- of MacOS-partities. Sommige -partities zouden kunnen worden gedeeld met andere Unix systemen, maar dit -valt buiten de scope van deze handleiding. U zult tenminste een afzonderlijke -partitie nodig hebben voor het root-bestandssysteem van &debian;. - -</para><para> - -U kunt informatie over uw huidige partitie-indeling vinden door gebruik te maken -van een schijfindelingsprogramma voor uw huidige besturingssysteem<phrase -arch="any-x86">, zoals fdisk of PartitionMagic</phrase><phrase -arch="powerpc">, zoals Drive Setup, HD Toolkit of MacTools</phrase><phrase -arch="s390">, zoals de VM diskmap</phrase>. Schijfindelingsprogramma's -beschikken altijd over een functie om bestaande partities te tonen zonder -wijzigingen aan te brengen. - -</para><para> - -Algemeen geldt dat het wijzigen van een partititie waarop reeds een bestandssysteem -aanwezig is, de daarop aanwezige informatie zal vernietigen. Het is daarom raadzaam -om altijd reservekopieën te maken voordat u een schijf gaat herindelen. Als we nogmaals -de analogie van het huis gebruiken: waarschijnlijk zou u eerst alle meubelen opzij -zetten voordat u een muur uitbreekt om het risico dat meubelen worden beschadigd uit te -sluiten. - -</para><para arch="hppa" condition="FIXME"> - -<emphasis>FIXME: write about HP-UX disks?</emphasis> - -</para><para> - -Als uw computer over meer dan één harde schijf beschikt, zou u één daarvan -volledig kunnen reserveren voor &debian;. Als dat het geval is, hoeft u deze -harde schijf niet in te delen voordat u het installatiesysteem opstart; het -schijfindelingsprogramma van het installatiesysteem kan dit zonder problemen -verzorgen. - -</para><para> - -Als uw machine over slechts één harde schijf beschikt en u het bestaande -besturingssysteem volledig wilt vervangen door &debian-gnu;, kunt u eveneens het -indelen van de schijf uitstellen tot tijdens de installatieprocedure -(<xref linkend="di-partition"/>), dus nadat u de computer heeft opgestart met het -installatiesysteem. Dit kan echter alleen als u van plan bent om het -installatiesysteem op te starten vanaf magneetband, CD of vanaf een andere met uw -computer verbonden machine. Bedenk het volgende: als u de computer opstart met -behulp van bestanden op de harde schijf en vervolgens deze harde schijf opnieuw -indeelt vanuit het installatiesysteem en daarmee de opstartbestanden verwijdert, -dan moet u maar hopen dat de installatie in één keer goed gaat. U zou in deze -situatie tenminste moeten beschikken over een alternatieve methode om uw -machine weer tot leven te wekken, zoals de originele installatietapes of -CDs -van het systeem. -<!-- FJP: naast tape, CD ook diskette als opstartbron noemen (2 maal). //--> - -</para><para> - -Als op uw machine reeds meerdere partities aanwezig zijn en er kan voldoende -ruimte worden vrijgemaakt door één of meerdere daarvan te verwijderen en -vervangen, dan kunt u eveneens gebruik maken van het schijfindelingsprogramma -van het &debian; installatiesysteem. U wordt echter aangeraden om toch de -informatie hieronder door te lezen omdat er bijzondere omstandigheden kunnen -zijn — zoals de volgorde van bestaande partities in de partitie-index -— waardoor u alsnog wordt gedwongen om te herindelen vóór de installatie. - -</para><para arch="any-x86"> - -Als uw machine een FAT of NTFS bestandssysteem heeft, zoals wordt gebruikt door -DOS en Windows, kunt u wachten en het schijfindelingsprogramma van het &debian; -installatiesysteem gebruiken om de grootte van het bestandssysteem te wijzigen. - -</para><para> - -Als geen van bovenstaande situaties van toepassing is, zult u, om ruimte te -creëren voor &debian;-partities, uw harde schijf moeten herindelen voordat u met -de installatie begint. Als sommige van de partities bestemd zijn voor andere -besturingssystemen, zou u deze moeten creëren met behulp van de eigen -schijfindelingsprogrammatuur van die besturingssystemen. Wij adviseren u -<emphasis>niet</emphasis> te proberen om partities voor &debian-gnu; te maken met -de programma's van een ander besturingssysteem. Beperkt u zich tot het maken van -de partities die u wilt behouden voor het oorspronkelijke besturingssysteem. - -</para><para> - -Als u meerdere besturingssystemen op dezelfde machine wilt installeren, wordt -aangeraden om eerst alle andere systemen te installeren voordat u verder gaat -met de installatie van &debian;. Windows en andere besturingssystemen kunnen de -mogelijkheid om &debian; op te starten verstoren, of kunnen u aanmoedigen om -'vreemde' partities opnieuw te fomateren. - -</para><para> - -Het is mogelijk om dergelijke problemen te herstellen of te voorkomen, maar u -bespaart uzelf moeite door het oorspronkelijke besturingssysteem eerst te -installeren. - -</para><para arch="powerpc"> - -Om &debian-gnu; automatisch te laten opstarten door OpenFirmware, dienen de -&arch-parttype; partities zich te bevinden vóór alle andere partities, in het -bijzonder MacOS opstartpartities. U dient hiermee rekening te houden -wanneer u de schijfindeling voorbereidt: u zou ten behoeve van &arch-parttype; een -dummy-partitie moeten maken die <emphasis>voor</emphasis> de andere -opstartpartities op de harde schijf komt. (De kleine partities die zijn -gereserveerd voor de besturingsprogramma's van de harde schijven van Apple -zijn geen opstartpartities.) U kunt deze dummy-partitie later, tijdens de -eigenlijke installatie, verwijderen en vervangen door de &arch-parttype; partities. - -</para><para> - -Als u op dit moment beschikt over een harde schijf met één partitie (een -gebruikelijke situatie voor desktop systemen) en u wilt kunnen opstarten met -zowel het huidige besturingssysteem als met &debian;, dan zult u de volgende -stappen moeten doorlopen. - - <orderedlist> -<listitem><para> - -Maak een reservekopie van alles op de computer. -</para></listitem> -<listitem><para> - -Start de computer op met behulp van het installatiemedium (zoals een CD of -magneetband) van het oorspronkelijke besturingssysteem. - -<phrase arch="powerpc">Als u de computer opstart vanaf een MacOS CD, houd dan -de <keycap>c</keycap> toets ingedrukt tijdens het opstarten om af te dwingen -dat de CD het actieve MacOS systeem wordt.</phrase> - -</para></listitem> -<listitem><para> - -Gebruik de schijfindelingsprogramma's behorend bij het oorspronkelijke -besturingssysteem om partities daarvoor te maken. Maak ten behoeve van &debian-gnu; -een dummy-partitie of laat ongebruikte ruimte vrij. - -</para></listitem> -<listitem><para> - -Installeer het oorspronkelijke besturingssysteem op haar nieuwe partitie. - -</para></listitem> -<listitem><para> - -Start het oorspronkelijke besturingssysteem opnieuw om te controleren dat -alles in orde is en om de opstartbestanden van &debian; te downloaden. -<!-- FJP: Waarom nu opeens downloaden? Is helemaal geen onderdeel van dit traject! -Het lijkt me logischer om eerst een restore te doen. //--> - -</para></listitem> -<listitem><para> - -Start het &debian; installatiesysteem op om te vervolgen met de installatie -van &debian;. - -</para></listitem> -</orderedlist> - -</para> - -&nondeb-part-x86.xml; -&nondeb-part-sparc.xml; -&nondeb-part-powerpc.xml; - - </sect1> diff --git a/nl/preparing/nondeb-part/powerpc.xml b/nl/preparing/nondeb-part/powerpc.xml deleted file mode 100644 index 9072908c7..000000000 --- a/nl/preparing/nondeb-part/powerpc.xml +++ /dev/null @@ -1,43 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - - - <sect2 arch="powerpc"><title>MacOS/OSX Partitioning</title> - -<para> - -The <application>Apple Drive Setup</application> application can be found in the -<filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing -partitions; it is limited to partitioning the entire disk at once. The -disk driver partitions don't show up in <application>Drive Setup</application>. - -</para><para> - -Remember to create a placeholder partition for GNU/Linux, preferably -positioned first in the disk layout. it doesn't matter what type it -is, it will be deleted and replaced later inside the &debian-gnu; installer. - -</para><para> - -If you are planning to install both MacOS 9 and OS X, it is best to -create separate partitions for OS 9 and OS X. If they are installed on -the same partition, <application>Startup Disk</application> (and reboot) must be used to select -between the two; the choice between the two systems can't be made at -boot time. With separate partitions, separate options for OS 9 and OS -X will appear when holding the <keycap>option</keycap> key at boot time, and separate -options can be installed in the <application>yaboot</application> boot menu as well. Also, -Startup Disk will de-bless all other mountable partitions, which can -affect GNU/Linux booting. Both OS 9 and OS X partitions will be -accessible from either OS 9 or OS X. - -</para><para> - -GNU/Linux is unable to access information on UFS partitions, but does -support HFS+ (aka MacOS Extended) partitions. OS X requires one of these -two types for its boot partition. MacOS 9 can be installed on either HFS -(aka MacOS Standard) or HFS+. To share information between the MacOS and -GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT -partitions are supported by both MacOS and Linux. - -</para> - </sect2> diff --git a/nl/preparing/nondeb-part/sparc.xml b/nl/preparing/nondeb-part/sparc.xml deleted file mode 100644 index 174fb26f2..000000000 --- a/nl/preparing/nondeb-part/sparc.xml +++ /dev/null @@ -1,41 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43732 untranslated --> - - - <sect2 arch="sparc"><title>Partitioning from SunOS</title> - -<para> - -It's perfectly fine to partition from SunOS; in fact, if you intend to -run both SunOS and &debian; on the same machine, it is recommended that -you partition using SunOS prior to installing &debian;. The Linux -kernel understands Sun disk labels, so there are no problems there. -SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS -(SunOS), romfs or iso9660 (CDROM) partitions. - -</para> - </sect2> - - <sect2 arch="sparc"><title>Partitioning from Linux or another OS</title> - -<para> - -Whatever system you are using to partition, make sure you create a -<quote>Sun disk label</quote> on your boot disk. This is the only kind of -partition scheme that the OpenBoot PROM understands, and so it's the -only scheme from which you can boot. In <command>fdisk</command>, the -<keycap>s</keycap> key is used to create Sun disk labels. You only need to do this -on drives that do not already have a Sun disk label. If you are using a -drive that was previously formatted using a PC (or other architecture) you -must create a new disk label, or problems with the disk geometry will most -likely occur. - -</para><para> - -You will probably be using <command>SILO</command> as your boot loader (the -small program which runs the operating system kernel). -<command>SILO</command> has certain requirements for partition sizes and -location; see <xref linkend="partitioning"/>. - -</para> - </sect2> diff --git a/nl/preparing/nondeb-part/x86.xml b/nl/preparing/nondeb-part/x86.xml deleted file mode 100644 index 60626ed6d..000000000 --- a/nl/preparing/nondeb-part/x86.xml +++ /dev/null @@ -1,121 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43576 untranslated --> - - - <sect2 arch="any-x86"><title>Partitioning From DOS or Windows</title> -<para> - -If you are manipulating existing FAT or NTFS partitions, it is -recommended that you either use the scheme below or native Windows or -DOS tools. Otherwise, it is not really necessary to partition from DOS -or Windows; the &debian; partitioning tools will generally do a better -job. - -</para><para> - -But if you have a large IDE disk, and are not using LBA addressing, -overlay drivers (sometimes provided by hard disk manufacturers), or a -new (post 1998) BIOS that supports large disk access extensions, then -you must locate your &debian; boot partition carefully. In this case, -you will have to put the boot partition into the first 1024 cylinders -of your hard disk (usually around 524 megabytes, without BIOS -translation). This may require that you move an existing FAT or NTFS -partition. - -</para> - - <sect3 id="lossless"> - <title>Lossless Repartitioning When Starting From DOS, Win-32 or OS/2 - </title> - -<para> - -One of the most common installations is onto a system that already -contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, -NT, 2000, XP, 2003, Vista, 7), or OS/2, and it is desired to put &debian; onto the same disk -without destroying the previous system. Note that the installer supports -resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply -start the installer and when you get to the partitioning step, select the -option for <menuchoice> <guimenuitem>Manual</guimenuitem> </menuchoice> -partitioning, select the partition to resize, and specify its new size. -So in most cases you should not need to use the method described below. - -</para><para> - -Before going any further, you should have decided how you will be -dividing up the disk. The method in this section will only split a -partition into two pieces. One will contain the original OS and the -other will be used for &debian;. During the installation of &debian;, you -will be given the opportunity to use the &debian; portion of the disk as you -see fit, i.e., as swap or as a file system. - -</para><para> - -The idea is to move all the data on the partition to the beginning, -before changing the partition information, so that nothing will be -lost. It is important that you do as little as possible between the -data movement and repartitioning to minimize the chance of a file -being written near the end of the partition as this will decrease the -amount of space you can take from the partition. - -</para><para> - -The first thing needed is a copy of <command>fips</command> which is -available in the <filename>tools/</filename> directory on your nearest &debian; -mirror. Unzip the archive and copy the files -<filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and -<filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can -be created using the command <filename>sys a:</filename> under DOS. -<command>fips</command> comes with very good documentation which you may -want to read. You will definitely need to read the documentation if -you use a disk compression driver or a disk manager. Create the disk -and read the documentation <emphasis>before</emphasis> you defragment the disk. - -</para><para> - -The next thing needed is to move all the data to the beginning of the -partition. <command>defrag</command>, which comes standard with DOS 6.0 and -later, can easily do the job. See the <command>fips</command> documentation -for a list of other software that may do the trick. Note that if you -have Windows 9x, you must run <command>defrag</command> from there, since -DOS doesn't understand VFAT, which is used to support for long -filenames, used in Windows 95 and higher. - -</para><para> - -After running the defragmenter (which can take a while on a large -disk), reboot with the <command>fips</command> disk you created in the -floppy drive. Simply type <filename>a:\fips</filename> and follow the directions. - -</para><para> - -Note that there are many other partition managers out there, in -case <command>fips</command> doesn't do the trick for you. - -</para> - </sect3> - - <sect3 id="partitioning-for-dos"><title>Partitioning for DOS</title> - -<para> - -If you are partitioning for DOS drives, or changing the size of DOS -partitions, using &debian; tools, many people experience problems working -with the resulting FAT partitions. For instance, some have reported -slow performance, consistent problems with <command>scandisk</command>, or -other weird errors in DOS or Windows. - -</para><para> - -Apparently, whenever you create or resize a partition for DOS use, -it's a good idea to fill the first few sectors with zeros. You should do -this prior to running DOS's <command>format</command> command by executing -the following command from &debian;: - -<informalexample><screen> -# dd if=/dev/zero of=/dev/hdXX bs=512 count=4 -</screen></informalexample> - -</para> - </sect3> - </sect2> diff --git a/nl/preparing/pre-install-bios-setup.xml b/nl/preparing/pre-install-bios-setup.xml deleted file mode 100644 index 396d58f5a..000000000 --- a/nl/preparing/pre-install-bios-setup.xml +++ /dev/null @@ -1,59 +0,0 @@ -<!-- original version: 61133 --> - - <sect1 id="pre-install-bios-setup"> - <title>Configuratie van apparatuur en besturingssysteem voor de installatie</title> -<para> - -In deze sectie wordt ingegaan op eventuele hardwareconfiguratie die u moet -uitvoeren voordat u &debian; installeert. In het algemeen betreft dit controle -en mogelijk aanpassing van 'firmware'-instellingen voor uw systeem. De -firmware is de basisprogrammatuur die door de apparatuur wordt gebruikt; -het meest kritieke moment waarop deze wordt gebruikt is tijdens het opstarten -van uw systeem. Ook wordt ingegaan op bekende problemen met apparatuur die -de betrouwbaarheid van &debian-gnu; op uw systeem kunnen beïnvloeden. - -</para> - -&bios-setup-i386.xml; -&bios-setup-powerpc.xml; -&bios-setup-sparc.xml; -&bios-setup-s390.xml; - - <sect2 arch="x86;powerpc" id="hardware-issues"> - <title>Aandachtspunten ten aanzien van apparatuur</title> - - <formalpara arch="x86"> - <title>USB BIOS instellingen en toetsenborden</title> -<para> - -Als u geen AT- maar alleen een USB-toetsenbord heeft, is het mogelijk dat u -in uw BIOS-configuratie 'legacy AT keyboard'-emulatie moet activeren. -Doe dit echter alleen als uw toetsenbord in het installatiesysteem niet werkt -in de USB-modus. Aan de andere kant zijn er ook systemen (met name laptops) -waarbij u mogelijk de 'legacy USB support' moet uitschakelen als uw toetsenbord -niet werkt. Raadpleeg de handleiding van uw moederbord en zoek in het BIOS -naar opties voor <quote>Legacy keyboard emulation</quote> of <quote>USB keyboard -support</quote>. - -</para> - </formalpara> - - <formalpara arch="powerpc"> - <title>Beeldschermweergave op OldWorld Powermacs</title> -<para> - -Sommige OldWorld Powermacs kunnen onder Linux, als de weergave is ingesteld -op meer dan 256 kleuren, mogelijk kleuren onjuist weergeven. Dit geldt in -het bijzonder voor systemen met het <quote>control</quote> stuurprogramma -voor video, maar mogelijk ook voor andere. -Als u na het opstarten van de computer dergelijke problemen ondervindt (u -kunt soms wel informatie op de monitor zien, maar soms ook helemaal niets) -of als het scherm zwart wordt na het opstarten van het installatiesysteem -in plaats van de gebruikersinterface te tonen, probeer dan onder MacOS de -beeldscherminstellingen te wijzigen naar 256 kleuren in plaats van -<quote>duizenden</quote> of <quote>millioenen</quote>. - -</para> - </formalpara> - </sect2> - </sect1> diff --git a/nl/preparing/preparing.xml b/nl/preparing/preparing.xml deleted file mode 100644 index f5518f5b1..000000000 --- a/nl/preparing/preparing.xml +++ /dev/null @@ -1,22 +0,0 @@ -<!-- original version: 16467 --> - -<chapter id="preparing"> - <title>Voordat u &debian-gnu; installeert</title> - -<para> - -Dit hoofdstuk behandelt de voorbereiding op de installatie van &debian; zelfs -voordat u het installatieprogramma start. Dit omvat het maken van een reservekopie -van uw gegevens, het verzamelen van gegevens over uw hardware en het bijeenzoeken -van eventueel benodigde informatie. - -</para> - -&install-overview.xml; -&backup.xml; -&needed-info.xml; -&minimum-hardware-reqts.xml; -&non-debian-partitioning.xml; -&pre-install-bios-setup.xml; - -</chapter> diff --git a/nl/using-d-i/components.xml b/nl/using-d-i/components.xml deleted file mode 100644 index 560ca939a..000000000 --- a/nl/using-d-i/components.xml +++ /dev/null @@ -1,192 +0,0 @@ -<!-- original version: 61147 --> - - <sect1 id="module-details"> - <title>Individuele modules gebruiken</title> -<para> - -In deze sectie beschrijven we elke module van het installatiesysteem -in detail. De modules zijn gegroepeerd in stadia die herkenbaar -zouden moeten zijn voor gebruikers. Ze worden gepresenteerd in de -volgorde waarin ze tijdens de installatie verschijnen. Merk op dat -mogelijk niet alle modules voor elke installatie worden gebruikt; welke -modules daadwerkelijk worden gebruikt is afhankelijk van de door u -gekozen installatiemethode en van uw apparatuur. - -</para> - - <sect2 id="di-setup"> - <title>Instelling van het installatiesysteem en hardware configuratie</title> -<para> - -Laten we er vanuit gaan dat uw systeem met het &debian; installatiesysteem is -opgestart en dat u het eerste scherm voor u heeft. Op dat moment is de -functionaliteit van &d-i; nog vrij beperkt. Het weet nog niet veel over uw -apparatuur, welke taal u prefereert en zelfs de taken die het moet uitvoeren. -Maak u geen zorgen. &d-i; is slim genoeg om uw apparatuur te scannen, de nog -ontbrekende modules te localiseren en zichzelf op te waarderen tot een -volwaardig installatiesysteem. - -U zult echter &d-i; nog altijd moeten helpen met enige informatie die het niet -automatisch kan bepalen (zoals de selectie van de taal en toetsenbordindeling -die u verkiest of van de gewenste spiegelserver). - -</para><para> - -U zult merken dat &d-i; verschillende keren tijdens dit stadium een -<firstterm>hardwareherkenning</firstterm> uitvoert. De eerste keer is dit -specifiek gericht op de apparatuur (bijvoorbeeld uw CD-speler of netwerkkaart) -die nodig is voor het laden van de benodigde modules van het installatiesysteem. -Omdat bij deze eerste keer mogelijk nog niet alle stuurprogramma's beschikbaar -zijn, moet de hardwareherkenning later in het proces worden herhaald. - -</para><para arch="not-s390"> -Tijdens de hardwareherkenning zal &d-i; nagaan of er onder de stuurprogramma's -benodigd voor uw hardware gevallen zijn waarvoor firmware geladen moet worden. -Als er stuurprogramma's zijn die firmware proberen te laden, maar waarbij deze -niet beschikbaar is, zal een dialoog getoond worden die de mogelijkheid biedt -de ontbrekende firmware vanaf een verwisselbaar medium te laden. -Zie <xref linkend="loading-firmware"/> voor nadere details. - -</para> - -&module-lowmem.xml; -&module-localechooser.xml; -&module-kbd-chooser.xml; -&module-s390-netdevice.xml; -&module-ddetect.xml; -&module-cdrom-detect.xml; -&module-iso-scan.xml; -&module-anna.xml; -&module-netcfg.xml; -&module-choose-mirror.xml; -<!-- tzsetup is included in clock-setup --> -&module-clock-setup.xml; - - </sect2> - - <sect2 id="di-partition"> - <title>Schijfindeling en selectie van aanhechtpunten</title> -<para> - -Op dit punt, nadat voor de laatste keer hardwareherkenning heeft plaatsgevonden, -heeft &d-i; zijn volledige sterkte bereikt: aangepast aan de behoeften van de -gebruiker en klaar voor het echte werk. - -Zoals de titel van deze sectie aangeeft, is de voornaamste taak van de volgende -modules het indelen van uw harde schijven, het creëren van bestandssystemen en -het toekennen van aanhechtpunten. Optioneel kunnen nauw gerelateerde zaken als -RAID, LVM of versleutelde partities worden geconfigureerd. - -</para> - -&module-s390-dasd.xml; -&module-partman.xml; -&module-autopartkit.xml; -&module-partitioner.xml; -&module-partconf.xml; -&module-mdcfg.xml; -&module-partman-lvm.xml; -&module-partman-crypto.xml; - </sect2> - - <sect2 id="di-install-base"> - <title>Installatie van het Basissysteem</title> -<para> - -Hoewel dit stadium het minst problematisch is, beslaat het wel een significant -deel van de tijd van de installatie omdat hier het volledige basissysteem wordt -opgehaald, geverifieerd en uitgepakt. Als u een langzame computer of -netwerkverbinding heeft, kan dit enige tijd in beslag nemen. - -</para> - -&module-base-installer.xml; - </sect2> - - <sect2 id="di-user-setup"> - <title>Gebruikers en wachtwoorden instellen</title> -<para> - -Nadat het basissysteem is geïnstalleerd, zal het installatiesysteem u in -staat stellen om het <quote>root</quote> account en/of een account voor de -eerste gebruiker in te stellen. Accounts voor andere gebruikers kunnen worden -aangemaakt nadat de installatie is afgerond. - -</para> - -&module-user-setup.xml; - </sect2> - - <sect2 id="di-install-software"> - <title>Aanvullende software installeren</title> -<para> - -Op dit punt beschikt u over een bruikbaar systeem, maar met beperkte -functionaliteit. De meeste gebruikers zullen aanvullende -programmatuur op het systeem willen installeren om het aan te passen aan hun -behoeften. Het installatiesysteem maakt dit mogelijk. Deze stap kan, zeker -indien u een langzame computer of netwerkverbinding heeft, nog meer tijd in -beslag nemen dan de installatie van het basissysteem. - -</para> - -&module-apt-setup.xml; -&module-pkgsel.xml; - </sect2> - - <sect2 id="di-make-bootable"> - <title>Zorgen dat uw systeem kan worden opgestart</title> -<para condition="supports-nfsroot"> - -Als u een werkstation zonder schijfeenheden installeert, is opstarten vanaf -een locale schijfeenheid uiteraard geen optie en zal deze stap worden -overgeslagen. <phrase arch="sparc">Desgewenst kunt u OpenBoot instellen om -standaard vanaf het netwerk op te starten; zie <xref -linkend="boot-dev-select-sun"/>.</phrase> - -</para> - -&module-os-prober.xml; -&module-hppa-palo-installer.xml; -&module-x86-grub-installer.xml; -&module-x86-lilo-installer.xml; -&module-ia64-elilo-installer.xml; -&module-mips-arcboot-installer.xml; -&module-mipsel-colo-installer.xml; -&module-powerpc-yaboot-installer.xml; -&module-powerpc-quik-installer.xml; -&module-s390-zipl-installer.xml; -&module-sparc-silo-installer.xml; -&module-nobootloader.xml; - </sect2> - - <sect2 id="di-finish"> - <title>De installatie afronden</title> -<para> - -Dit is de laatste stap van het installatieproces voor &debian; waarbij het -installatiesysteem nog enkele afrondende taken uitvoert. -Het bestaat voornamelijk uit het afwerken van losse eindjes van &d-i;. - -</para> - -&module-clock-setup-finish.xml; -&module-finish-install.xml; - </sect2> - - <sect2 id="di-miscellaneous"> - <title>Diverse modules</title> -<para> - -De modules in deze sectie zijn normaalgesproken niet betrokken in het -installatieproces, maar zijn beschikbaar op de achtergrond voor gebruik -als er iets mis gaat. - -</para> - -&module-save-logs.xml; -&module-cdrom-checker.xml; -&module-shell.xml; - </sect2> -&module-network-console.xml; - </sect1> diff --git a/nl/using-d-i/loading-firmware.xml b/nl/using-d-i/loading-firmware.xml deleted file mode 100644 index 1fa223cb1..000000000 --- a/nl/using-d-i/loading-firmware.xml +++ /dev/null @@ -1,134 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56290 untranslated --> - - <sect1 id="loading-firmware" arch="not-s390"> - <title>Loading Missing Firmware</title> -<para> - -As described in <xref linkend="hardware-firmware"/>, some devices require -firmware to be loaded. In most cases the device will not work at all -if the firmware is not available; sometimes basic functionality is not -impaired if it is missing and the firmware is only needed to enable -additional features. - -</para><para> - -If a device driver requests firmware that is not available, &d-i; will -display a dialog offering to load the missing firmware. If this option -is selected, &d-i; will scan available devices for either loose firmware -files or packages containing firmware. If found, the firmware will be -copied to the correct location (<filename>/lib/firmware</filename>) and -the driver module will be reloaded. - -</para> -<note><para> - -Which devices are scanned and which file systems are supported depends on -the architecture, the installation method and the stage of the installation. -Especially during the early stages of the installation, loading the firmware -is most likely to succeed from a FAT-formatted floppy disk or USB stick. -<phrase arch="x86">On i386 and amd64 firmware can also be loaded from an -MMC or SD card.</phrase> - -</para></note> -<para> - -Note that it is possible to skip loading the firmware if you know the -device will also function without it, or if the device is not needed during -the installation. - -</para> -<warning><para> - -Support for loading firmware is still relatively basic and is likely to -be improved in future releases of the installer. Currently &d-i; will -for example not display any warning if you choose to load missing firmware, -but the requested firmware is not found. -Please report any issues you encounter by filing an installation report -(see <xref linkend="submit-bug"/>). - -</para></warning> - - <sect2><title>Preparing a medium</title> -<para> - -Although in some cases the firmware can also be loaded from a partition on -a hard disk, the most common method to load firmware will be from some -removable medium such as a floppy disk or a USB stick. -The firmware files or packages must be placed in either the root directory -or a directory named <filename>/firmware</filename> of the file system on -the medium. The recommended file system to use is FAT as that is most -certain to be supported during the early stages of the installation. - -</para><para> - -Tarballs containing current packages for the most common firmware are -available from: - -<itemizedlist> -<listitem><para> -<ulink url="&url-firmware-tarballs;"/> -</para></listitem> -</itemizedlist> - -Just download the tarball for the correct release and unpack it to the file -system on the medium. - -</para><para> - -If the firmware you need is not included in the tarball, you can also -download specific firmware packages from the (non-free section of the) -archive. The following overview should list most available firmware -packages but is not guaranteed to be complete and may also contain -non-firmware packages: - -<itemizedlist> -<listitem><para> -<ulink url="&url-firmware-packages;"/> -</para></listitem> -</itemizedlist> - -</para><para> - -It is also possible to copy individual firmware files to the medium. Loose -firmware could be obtained for example from an already installed system or -from a hardware vendor. - -</para> - </sect2> - - <sect2><title>Firmware and the Installed System</title> -<para> - -Any firmware loaded during the installation will be copied automatically -to the installed system. In most cases this will ensure that the device -that requires the firmware will also work correctly after the system is -rebooted into the installed system. However, if the installed system runs -a different kernel version from the installer there is a slight chance that -the firmware cannot be loaded due to version skew. - -</para><para> - -If the firmware was loaded from a firmware package, &d-i; will also install -this package for the installed system and will automatically add the non-free -section of the package archive in APT's <filename>sources.list</filename>. -This has the advantage that the firmware should be updated automatically if -a new version becomes available. - -</para><para> - -If loading the firmware was skipped during the installation, the relevant -device will probably not work with the installed system until the firmware -(package) is installed manually. - -</para> -<note><para> - -If the firmware was loaded from loose firmware files, the firmware copied to -the installed system will <emphasis>not</emphasis> be automatically updated -unless the corresponding firmware package (if available) is installed after -the installation is completed. - -</para></note> - </sect2> - </sect1> diff --git a/nl/using-d-i/modules/anna.xml b/nl/using-d-i/modules/anna.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/apt-setup.xml b/nl/using-d-i/modules/apt-setup.xml deleted file mode 100644 index 13e77789d..000000000 --- a/nl/using-d-i/modules/apt-setup.xml +++ /dev/null @@ -1,41 +0,0 @@ -<!-- original version: 33820 --> - - <sect3 id="apt-setup"> - <title>Het configureren van APT</title> - -<para> - -Het belangrijkste middel dat mensen gebruiken om pakketten op hun systeem -te installeren is een programma genaamd <command>apt-get</command>, -uit het pakket <classname>apt</classname><footnote> - -<para> - -Merk op dat het programma dat de feitelijke installatie van pakketten -uitvoert, <command>dpkg</command> is. Dit programma is echter meer een -soort specialistisch gereedschap en wordt waar nodig door -<command>apt-get</command> aangeroepen. <command>apt-get</command> bevat echter -ook hogere functionaliteit: het is in staat om andere pakketten te -installeren die vereist zijn voor het pakket dat u probeert te installeren -en ook om pakketten op te halen vanaf CD, het netwerk en andere bronnen. - -</para> -</footnote>. -Ook andere hulpprogramma's voor pakketbeheer, zoals <command>aptitude</command>, -<command>synaptic</command> en het oudere <command>dselect</command> maken -gebruik en zijn afhankelijk van <command>apt-get</command>. Nieuwe gebruikers -wordt aangeraden gebruik te maken van deze hulpprogramma's omdat zij aanvullende -functionaliteit (het zoeken van pakketten en status controles) integreren in een -vriendelijke gebruikersinterface. - -</para><para> - -APT moet worden geconfigureerd zodat het weet waar pakketten vandaan kunnen -worden gehaald. Het installatiesysteem verzorgt dit grotendeels automatisch op -basis van de gebruike installatiemethode. Het resultaat van deze configuratie -wordt weggeschreven naar het bestand <filename>/etc/apt/sources.list</filename>. -U kunt dit bestand na afronding van de installatie bekijken en naar behoefte -aanpassen. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/autopartkit.xml b/nl/using-d-i/modules/autopartkit.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/base-installer.xml b/nl/using-d-i/modules/base-installer.xml deleted file mode 100644 index 215fe6974..000000000 --- a/nl/using-d-i/modules/base-installer.xml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- original version: 43573 --> - -<para> - -Tijdens de installatie van het basissysteem worden boodschappen met -betrekking tot het uitpakken en configureren van pakketten doorgestuurd -naar <userinput>tty4</userinput>. U kunt naar deze terminal schakelen door -op <keycombo><keycap>Linker Alt</keycap><keycap>F4</keycap></keycombo> te -drukken; u schakelt terug naar het hoofdscherm van de installatie met behulp -van <keycombo><keycap>Linker Alt</keycap><keycap>F1</keycap></keycombo>. - -</para><para> - -De boodschappen die tijdens deze fase worden gegenereerd worden ook -opgeslagen in <filename>/var/log/syslog</filename>. Als de installatie wordt -uitgevoerd vanaf een seriële console, kunt u ze daar raadplegen. - -</para><para> - -Als onderdeel van de installatie zal een &arch-kernel; kernel worden geïnstalleerd. -Tijdens een standaard installatie zal het installatiesysteem een kernel voor -u kiezen die het beste past bij uw apparatuur. Bij installaties op een -lagere prioriteit zal een lijst worden getoond met beschikbare kernels waaruit -u een keuze kunt maken. - -</para> diff --git a/nl/using-d-i/modules/cdrom-checker.xml b/nl/using-d-i/modules/cdrom-checker.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/nl/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/nl/using-d-i/modules/cdrom-detect.xml b/nl/using-d-i/modules/cdrom-detect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/choose-mirror.xml b/nl/using-d-i/modules/choose-mirror.xml deleted file mode 100644 index 01a36f47c..000000000 --- a/nl/using-d-i/modules/choose-mirror.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43658 untranslated --> - -<!-- -Hmm. This really does need documenting :-/ - -- 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. -- Mirror selection is delayed until apt-setup for CD-based installs (except - businesscard) -- A list of countries is displayed with the default based on the country you - selected earlier. -- 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. - (not for ftp) -- Forcing to ftp can be done using "protocol=ftp" -- Note that not all mirrors are equal (see http://www.nl.debian.org/mirror/list) - -- The selected mirror will be tested. -- How to handle problems with mirrors. ---> diff --git a/nl/using-d-i/modules/clock-setup-finish.xml b/nl/using-d-i/modules/clock-setup-finish.xml deleted file mode 100644 index 7689d0a81..000000000 --- a/nl/using-d-i/modules/clock-setup-finish.xml +++ /dev/null @@ -1,33 +0,0 @@ -<!-- original version: 61133 --> - - <sect3 arch="not-s390" id="system-clock"> - <title>De interne systeemklok instellen</title> - -<para> - -Het installatiesysteem kan u vragen of de interne klok van uw systeem staat -ingesteld op Greenwich Mean Time (GMT of UTC) of niet. Indien mogelijk wordt -deze vraag echter vermeden en zal het installatiesysteem op basis van -informatie als de aanwezigheid van andere besturingssystemen zelf proberen te -bepalen of de interne klok al dan niet is ingesteld op UTC. - -</para><para> - -Bij een installatie in "expert" modus zal u altijd kunnen kiezen of de interne -klok staat ingesteld op UTC of niet. -<phrase arch="powerpc">De interne klok van Macintosh computers staat -gewoonlijk ingesteld op de lokale tijd. Selecteer lokaal in plaats van -GMT als u meerdere besturingssystemen op uw computer wilt gebruiken.</phrase> -<phrase arch="any-x86">Systemen waarop (ook) Dos of Windows draait, staan -gewoonlijk ingesteld op de lokale tijd. Selecteer lokaal in plaats van -GMT als u meerdere besturingssystemen op uw computer wilt gebruiken.</phrase> - -</para><para> - -Het installatiesysteem zal op dit punt ook proberen om de huidige tijd vast -te leggen in de interne systeemklok. Dit zal worden gedaan ofwel in UTC -ofwel in de locale tijd, afhankelijk van de zojuist gedane selectie. -schrijven - -</para> - </sect3> diff --git a/nl/using-d-i/modules/clock-setup.xml b/nl/using-d-i/modules/clock-setup.xml deleted file mode 100644 index 43d9be7cb..000000000 --- a/nl/using-d-i/modules/clock-setup.xml +++ /dev/null @@ -1,24 +0,0 @@ -<!-- original version: 59889 --> - - <sect3 id="clock-setup"> - <title>De klok instellen</title> - -<para arch="not-s390"> - -Het installatiesysteem zal allereerst proberen om verbinding te maken met -een tijdserver op het Internet (gebruikmakend van het <firstterm>NTP</firstterm> -protocol) om op basis daarvan de systeemtijd juist in te stellen. -Als dit mislukt, zal het systeem ervan uitgaan dat de datum en tijd die -tijdens het opstarten van het installatiesysteem zijn bepaald op basis van -de interne systeemklok, juist zijn. Het is niet mogelijk om tijdens de -installatie de systeemtijd handmatig in te stellen. - -</para><para arch="s390"> - -Het installatiesysteem wijzigt de systeemtijd niet op het s390 platform. - -</para> - -&module-tzsetup.xml; - - </sect3> diff --git a/nl/using-d-i/modules/ddetect.xml b/nl/using-d-i/modules/ddetect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/finish-install.xml b/nl/using-d-i/modules/finish-install.xml deleted file mode 100644 index 9bc3190e3..000000000 --- a/nl/using-d-i/modules/finish-install.xml +++ /dev/null @@ -1,20 +0,0 @@ -<!-- original version: 50618 --> - - <sect3 id="finish-install"> - <title>Het systeem opnieuw opstarten</title> - -<para arch="not-s390"> - -U zal worden gevraagd om het installatiemedium (CD, diskette, enz.) -dat u heeft gebruikt om het installatiesysteem op te starten, te verwijderen. -Vervolgens zal uw systeem opnieuw opstarten met uw nieuwe &debian; systeem. - -</para><para arch="s390"> - -Na een laatste dialoog zal het systeem worden gestopt omdat herstarten op -&arch-title; niet wordt ondersteund. U moet vervolgens een IPL voor &debian-gnu; -uitvoeren vanaf de DASD die u tijdens de eerste stappen van de installatie -heeft geselecteerd voor het root bestandssysteem. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/hppa/palo-installer.xml b/nl/using-d-i/modules/hppa/palo-installer.xml deleted file mode 100644 index 84a3608e8..000000000 --- a/nl/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/nl/using-d-i/modules/ia64/elilo-installer.xml b/nl/using-d-i/modules/ia64/elilo-installer.xml deleted file mode 100644 index 0c8088cb8..000000000 --- a/nl/using-d-i/modules/ia64/elilo-installer.xml +++ /dev/null @@ -1,135 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 43573 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 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. - -</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, <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> 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. - -</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/nl/using-d-i/modules/iso-scan.xml b/nl/using-d-i/modules/iso-scan.xml deleted file mode 100644 index 47e3b193f..000000000 --- a/nl/using-d-i/modules/iso-scan.xml +++ /dev/null @@ -1,49 +0,0 @@ -<!-- original version: 23058 --> - - <sect3 id="iso-scan"> - <title>De ISO-installatie-image localiseren</title> -<para> - -Als u de <emphasis>hd-media</emphasis> installatiemethode gebruikt, komt -er een moment waarop u de ISO-image met het &debian; Installatiesysteem -zult moeten localiseren en koppelen om het restant van de -installatiebestanden te laden. Dit is de taak van de module -<command>iso-scan</command>. - -</para><para> - -Allereerst zal <command>iso-scan</command> automatisch alle blok-apparaten -(d.w.z. partities) die een bekend bestandssysteem hebben, koppelen en -deze achtereenvolgens doorzoeken op bestanden met een extensie -<filename>.iso</filename> (of <filename>.ISO</filename>). Merk op dat -tijdens de eerste poging alleen de hoogste twee niveau's van de -mapstructuur zullen worden doorzocht (d.w.z. dat -<filename>/<replaceable>willekeurig</replaceable>.iso</filename> en -bijvoorbeeld <filename>/data/<replaceable>willekeurig</replaceable>.iso</filename> -gevonden zullen worden, maar niet bijvoorbeeld -<filename>/data/tmp/<replaceable>willekeurig</replaceable>.iso</filename>). -Nadat een ISO-image is gevonden, controleert <command>iso-scan</command> of -het een geldig &debian; ISO-installatie-image betreft of niet. In het eerste -geval zijn we klaar, in het tweede geval wordt verder gezocht. - -</para><para> - -Als de eerste poging om een ISO-installatie-image te vinden faalt, -zal <command>iso-scan</command> u vragen of u een meer uitgebreide -zoektocht wilt laten uitvoeren. Tijdens deze poging zal niet alleen in -de hoogste mappen worden gezocht, maar wordt het volledige bestandssysteem -doorlopen. - - -</para><para> - -Als <command>iso-scan</command> uw ISO-installatie-image niet kan vinden, -start dan de computer opnieuw op met uw oorspronkelijke besturingssysteem -en controleer of de image een correcte naam heeft (dus eindigend op -<filename>.iso</filename>), of het staat op een bestandssysteem dat door -&d-i; wordt herkend en of het niet beschadigd is (verifieer de checksum). -Ervaren gebruikers van Unix kunnen deze handelingen eventueel uitvoeren -op de tweede console zonder het systeem opnieuw op te starten. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/kbd-chooser.xml b/nl/using-d-i/modules/kbd-chooser.xml deleted file mode 100644 index 01e360817..000000000 --- a/nl/using-d-i/modules/kbd-chooser.xml +++ /dev/null @@ -1,38 +0,0 @@ -<!-- original version: 60683 --> - - <sect3 id="kbd-chooser"> - <title>Een toetsenbord selecteren</title> - -<para> - -De indeling van toetsenborden is vaak aangepast aan de tekens die in -een taal worden gebruikt. Selecteer een indeling die overeenkomt met -het toetsenbord dat u gebruikt. Als uw toetsenbordindeling niet in de -lijst voorkomt, kies dan de indeling die het best in de buurt komt. -U kunt, nadat de installatie is voltooid, een toetsenbordindeling kiezen -uit een meer uitgebreide selectie (geef hiervoor, nadat u de installatie -heeft afgerond, als root het commando <command>dpkg-reconfigure keyboard-configuration</command>). -<!-- FJP: in laatste zin staat nu 2x dat installatie afgerond moet zijn--> - -</para><para> - -Maak uw keuze door met de cursortoetsen de selectie te verplaatsen en -druk vervolgens op &enterkey;. De cursortoetsen zitten op alle -toetsenbordindelingen op dezelfde plaats en zijn dus onafhankelijk van -de toetsenbordconfiguratie. Een 'extended' toetsenbord heeft -<keycap>F1</keycap> t/m <keycap>F10</keycap> toetsen als bovenste regel. -<!-- FJP: Tegenwoordig hebben we toch t/m F12? --> - -</para><para arch="powerpc"> - -Er zijn twee toetsenbordindelingen voor US toetsenborden: de -qwerty/mac-usb-us (Apple USB) indeling zal de Alt functie koppelen aan de -<keycap>Command/Apple</keycap>-toets (op het toetsenbord naast de -<keycap>spatiebalk</keycap>, dus analoog aan <keycap>Alt</keycap> op -PC-toetsenborden), terwijl de qwerty/us (Standard) indeling de Alt functie -zal koppelen aan de <keycap>Option</keycap>-toets (op de meeste Mac -toetsenborden is op deze toets 'alt' gegraveerd). Verder zijn deze twee -indelingen gelijk. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/localechooser.xml b/nl/using-d-i/modules/localechooser.xml deleted file mode 100644 index fa1a7737d..000000000 --- a/nl/using-d-i/modules/localechooser.xml +++ /dev/null @@ -1,76 +0,0 @@ -<!-- original version: 56423 --> - - - <sect3 id="localechooser"> - <title>Lokalisatie bepalen</title> - -<para> - -Over het algemeen zullen de eerste vragen die worden gesteld de bepaling van -de lokalisatie voor zowel de installatie als het geïnstalleerde systeem -betreffen. De lokalisatie-opties betreffen taal, land en -<quote>locale</quote>. - -</para><para> - -De taal die u kiest zal worden gebruikt tijdens het vervolg van de -installatie, tenminste als een vertaling van de verschillende dialogen -beschikbaar is. Als voor de geselecteerde taal geen geldige vertaling -beschikbaar is, zal het installatiesysteem terugvallen op Engels. - -</para><para> - -Het geselecteerde land zal later in het installatieproces worden gebruikt -bij de selectie van uw tijdzone en een voor uw locatie geschikte &debian; -spiegelserver. Taal en land tezamen zullen worden gebruikt om de standaard -<quote>locale</quote> voor uw systeem in te stellen en om u te helpen bij -de selectie van uw toetsenboord. - -</para><para> - -Allereerst zal worden gevraagd welke taal uw voorkeur heeft. De talen -worden genoemd zowel in het Engels (links) als in de taal zelf (rechts); -de namen aan de rechter zijde worden tevens getoond in het juiste script -voor de taal. De lijst is gesorteerd op de Engelse namen. -Bovenaan de lijst vindt u een extra optie waarmee u, in plaats van een taal, -de <quote>C</quote>-locale kunt selecteren. Het kiezen van de -<quote>C</quote>-locale heeft tot gevolg dat de installatie in het Engels -zal plaatsvinden; daarnaast zal het geïnstalleerde systeem geen ondersteuning -voor lokalisatie hebben aangezien het pakket <classname>locales</classname> -niet zal worden geïnstalleerd. - -</para><para> - -Als u een taal heeft geselecteerd die wordt herkend als officiële taal voor -meer dan één land<footnote> - -<para> - -In technische termen: indien voor die taal meer dan één <quote>locale</quote> -bestaat met verschillende landcodes. - -</para> - -</footnote>, zal een keuzelijst worden getoond met daarin alleen die landen. -Om een land te kiezen dat niet in de lijst voorkomt, kiest u de optie -<guimenuitem>Andere</guimenuitem> onderaan de lijst. Er zal dan een -keuzelijst met continenten worden getoond; na selectie van een continent -gevolgd door een keuzelijst met landen die behoren tot dat continent. - -</para><para> - -Als de taal slechts bij één land voorkomt, zal dat land automatisch worden -geselecteerd. In dat geval is het alleen mogelijk om een ander land te -selecteren door eerst de debconf-prioriteit te verlagen en vervolgens -vanuit het hoofdmenu opnieuw de optie voor taalselectie te kiezen. - -</para><para> - -Op basis van door u geselecteerde taal en land zal een standaardwaarde voor -locale worden bepaald. Als u de installatie uitvoert op een lagere dan de -standaard prioriteit, heeft u de mogelijkheid om een andere standaard locale te -kiezen en om aanvullende locales te kiezen die voor het geïnstalleerde systeem -moeten worden gegenereerd. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/lowmem.xml b/nl/using-d-i/modules/lowmem.xml deleted file mode 100644 index 01a5f4a11..000000000 --- a/nl/using-d-i/modules/lowmem.xml +++ /dev/null @@ -1,21 +0,0 @@ -<!-- original version: 16990 --> - - <sect3 id="lowmem"> - <title>Controle van beschikbaar geheugen</title> - -<para> - -Eén van de eerste dingen die &d-i; doet, is het controleren van het -beschikbare geheugen. Als de hoeveelheid beschikbaar geheugen beperkt -is, zal deze module een aantal wijzigingen aanbrengen in het -installatieproces waardoor u hopelijk in staat zal zijn om &debian-gnu; -op uw systeem te installeren. - -</para><para> - -Tijdens een installatie op een systeem met beperkt geheugen, zullen -niet alle modules beschikbaar zijn. Eén van de beperkingen is dat u -de voor de installatie te gebruiken taal niet zal kunnen kiezen. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/mdcfg.xml b/nl/using-d-i/modules/mdcfg.xml deleted file mode 100644 index 9a6e9bd76..000000000 --- a/nl/using-d-i/modules/mdcfg.xml +++ /dev/null @@ -1,233 +0,0 @@ -<!-- original version: 50619 --> - - <sect3 id="mdcfg"> - <title>Meervoudige schijfapparaten configureren (Software-RAID)</title> -<para> - -Als u in uw computer meer dan één harde schijf<footnote><para> - -U zou zelfs een Software-RAID kunnen samenstellen uit verschillende -partities op één fysieke harde schijf, maar daarmee bereikt u niets -zinvols. - -</para></footnote> heeft, kunt u <command>mdcfg</command> gebruiken -om uw schijfeenheden te configureren voor betere prestaties en/of -grotere betrouwbaarheid van uw gegevens. Het resultaat wordt een -<firstterm>Multidisk Device</firstterm> (MD) of, naar zijn meest -bekende variant, <firstterm>Software-RAID</firstterm>). - -</para><para> - -MD is in feite niets meer dan een verzameling partities op verschillende -harde schijven die worden gecombineerd om gezamelijk één -<emphasis>logisch</emphasis> apparaat te vormen. Dit apparaat kan vervolgens -worden gebruikt als een gewone partitie (dat wil zeggen dat u het in -<command>partman</command> kunt formatteren en een aanhechtpunt kunt toewijzen. - -</para><para> - -Het voordeel dat u behaalt, is afhankelijk van het soort MD-apparaat dat u -creëert. Op dit moment worden ondersteund: - -<variablelist> -<varlistentry> - -<term>RAID0</term><listitem><para> - -Levert hoofdzakelijk prestatieverbetering. RAID0 splitst alle binnenkomende -gegevens op in zogenaamde <firstterm>stripes</firstterm> en verdeelt deze -gelijkmatig over elke schijf in de reeks. Dit kan de snelheid van lees- en -schrijfoperaties verhogen, maar als één van de schijven defect raakt, -verliest u <emphasis>alle</emphasis> gegevens (een deel van de informatie -staat nog wel op de 'gezonde' schijf/schijven, maar een ander deel -<emphasis>stond</emphasis> op de defecte schijf). - -</para><para> - -RAID0 wordt bijvoorbeeld veel toegepast voor video editing. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>RAID1</term><listitem><para> - -Is geschikt voor situaties waar betrouwbaarheid de belangrijkste -overweging is. Het bestaat uit verschillende (gewoonlijk twee) partities -van gelijke grootte; beide partities bevatten exact dezelfde gegevens. -In essentie betekent dit drie dingen. Ten eerste heeft u, als één van de -schijven defect raakt, nog altijd de gegevens op de tweede schijf. Ten -tweede kunt u effectief slechts een deel van de beschikbare capaciteit -gebruiken (meer exact: de grootte van de kleinste partitie in de RAID). -Ten derde wordt de belasting bij het lezen van gegevens verdeeld over -de schijven; dit kan de prestaties verbeteren als op een server over het -algemeen meer lees- dan schrijfacties plaatsvinden, zoals bij een -bestandsserver. - -</para><para> - -Desgewenst kunt u een reserve harde schijf in de reeks opnemen die bij -een storing de plaats zal innemen van de defecte schijf. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>RAID5</term><listitem><para> - -Is een goed compromis tussen snelheid, betrouwbaarheid en redundantie van -gegevens. Bij RAID5 worden binnenkomende gegevens gesplitst in stripes en -gelijkmatig verdeeld over alle harde schijven op één na (vergelijkbaar met -RAID0). In afwijking van RAID0, wordt bij RAID5 ook -<firstterm>pariteits</firstterm>informatie berekend die op de overgebleven -schijf wordt weggeschreven. De harde schijf met de pariteitsinformatie is -niet statisch (dat zou RAID4 zijn), maar wordt periodiek gewijzigd zodat de -pariteitsinformatie gelijkelijk wordt verdeeld over de schijven. Als één van -de schijven defect raakt, kunnen de ontbrekende gegevens worden berekend op -basis van de resterende gegevens en hun pariteit. RAID5 dient te zijn -opgebouwd uit tenminste drie actieve partities. Desgewenst kunt u een reserve -harde schijf in de reeks opnemen die bij een storing de plaats zal innemen -van de defecte schijf. - -</para><para> - -Zoals u kunt zien, heeft RAID5 een vergelijkbare mate van betrouwbaarheid -als RAID1 terwijl de opslag minder redundant is. Aan de andere kant is het, -in verband met de berekening van de partiteitsinformatie, mogelijk iets -trager bij schrijfoperaties dan RAID0 . - -</para></listitem> -</varlistentry> -</variablelist> - -Samenvattend: - -<informaltable> -<tgroup cols="5"> -<thead> -<row> - <entry>Type</entry> - <entry>Minimum apparaten</entry> - <entry>Reserve schijf</entry> - <entry>Overleeft een storing?</entry> - <entry>Beschikbare ruimte</entry> -</row> -</thead> - -<tbody> -<row> - <entry>RAID0</entry> - <entry>2</entry> - <entry>nee</entry> - <entry>nee</entry> - <entry>Grootte van de kleinste partitie vermenigvuldigd met het aantal apparaten</entry> -</row> - -<row> - <entry>RAID1</entry> - <entry>2</entry> - <entry>optioneel</entry> - <entry>ja</entry> - <entry>Grootte van de kleinste partitie in de RAID</entry> -</row> - -<row> - <entry>RAID5</entry> - <entry>3</entry> - <entry>naar keuze</entry> - <entry>ja</entry> - <entry> - Grootte van de kleinste partitie vermenigvuldigd met - (het aantal apparaten in de RAID minus één) - </entry> -</row> - -</tbody></tgroup></informaltable> - -</para><para> - -Als u meer wilt weten over Software-RAID, raadpleeg dan de -<ulink url="&url-software-raid-howto;">Software RAID HOWTO</ulink>. - -</para><para> - -Om een MD-apparaat aan te maken, dient u de partities die u ervan onderdeel -wilt laten uitmaken, te markeren voor gebruik in een RAID. -U doet dit in <command>partman</command> in het menu met <guimenu>partitie -instellingen</guimenu>. Daar selecteert u <menuchoice><guimenu>Gebruiken -als:</guimenu> <guimenuitem>Fysiek volume voor RAID</guimenuitem></menuchoice>. - -</para><warning><para> - -Ondersteuning voor meervoudige schijfapparaten is relatief nieuwe -functionaliteit in het installatiesysteem. Het is mogelijk dat u daardoor -problemen ondervindt bij sommige RAID-varianten, of in de combinatie van MD -met sommige opstartladers als probeert een MD te gebruiken voor het -bestandssysteem root (<filename>/</filename>). Ervaren gebruikers kunnen -proberen om deze problemen op te lossen door bepaalde configuratie- of -installatiestappen handmatig uit te voeren vanuit een opdrachtschil. - -</para></warning><para> - -Vervolgens dient u in het hoofdmenu van <command>partman</command> -te kiezen voor <guimenuitem>Software-RAID instellen</guimenuitem>. -(N.B. Dit menu verschijnt pas nadat u tenminste één partitie heeft -gemarkeerd voor gebruik als <guimenuitem>Fysiek volume voor -RAID</guimenuitem>.) -Kies dan op het eerste scherm van <command>mdcfg</command> voor -<guimenuitem>MD-apparaat aanmaken</guimenuitem>. Er zal een lijst -met ondersteunde typen MD-apparaten worden getoond, waaruit u er één -kunt kiezen (bijvoorbeeld RAID1). Het vervolg is afhankelijk van het -geselecteerde type MD. - -</para> - -<itemizedlist> -<listitem><para> - -RAID0 is eenvoudig — er zal een overzicht met beschikbare -RAID-partities worden getoond en uw enige taak is het selecteren van de -partities die u voor het MD-apparaat wilt gebruiken. - -</para></listitem> -<listitem><para> - -RAID1 is iets lastiger. Allereerst zal u worden gevraagd om het aantal -actieve en het aantal reserve eenheden voor het MD-apparaat in te -geven. Vervolgens dient u uit de lijst met beschikbare RAID-partities -eerst de partities te kiezen die actief moeten zijn en vervolgens de -reserve partities. Het aantal partities dat u selecteert moet gelijk zijn -aan het aantal dat u zojuist heeft opgegeven. Maak u geen zorgen; als u -een fout maakt en een afwijkend aantal partities selecteert, zal &d-i; -u beletten verder te gaan totdat dit gecorrigeerd is. - -</para></listitem> -<listitem><para> - -De configuratieprocedure voor RAID5 is vergelijkbaar met die voor RAID1. -Het enige verschil is dat u tenminste <emphasis>3</emphasis> actieve -partities dient te gebruiken. - -</para></listitem> -</itemizedlist> - -<para> - -Het is zonder meer mogelijk om verschillende typen MD-apparaten naast -elkaar te hebben. Als u bijvoorbeeld drie 200GB harde schijven heeft -ten behoeve van MD, elk met twee 100 GB partities, kunt u de eerste -partities op alle drie de schijven samenvoegen tot één RAID0 (snelle -partitie van 300GB voor video editing) en de andere drie partities -(2 actief en 1 reserve) gebruiken voor RAID1 (als zeer betrouwbare -100GB partitie voor <filename>/home</filename>). - -</para><para> - -Nadat u de MD-apparaten naar uw tevredenheid heeft ingesteld, kunt u -<command>mdcfg</command> afsluiten om terug te keren naar -<command>partman</command> om op uw nieuwe MD-apparaten bestandssystemen -aan te maken en daaraan de gebruikelijke kenmerken, zoals aanhechtpunten, -toe te kennen. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/mips/arcboot-installer.xml b/nl/using-d-i/modules/mips/arcboot-installer.xml deleted file mode 100644 index 2e522562e..000000000 --- a/nl/using-d-i/modules/mips/arcboot-installer.xml +++ /dev/null @@ -1,69 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 35613 untranslated --> - - <sect3 arch="mips"> - <title><command>arcboot</command>-installer</title> -<para> - -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> -<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput> -<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</replaceable>)</userinput> -<userinput> setenv OSLoader arcboot</userinput> -<userinput> setenv OSLoadFilename <replaceable>config</replaceable></userinput> -<userinput> setenv AutoLoad yes</userinput> -</screen></informalexample> - -on the firmware prompt, and then typing <command>boot</command>. - -</para> - -<variablelist> -<varlistentry> -<term> <replaceable>scsi</replaceable> </term> -<listitem><para> - -is the SCSI bus to be booted from, this is <userinput>0</userinput> -for the onboard controllers - -</para></listitem> -</varlistentry> -<varlistentry> -<term> <replaceable>disk</replaceable> </term> -<listitem><para> - -is the SCSI ID of the hard disk on which <command>arcboot</command> is -installed - -</para></listitem> -</varlistentry> -<varlistentry> -<term> <replaceable>partnr</replaceable> </term> -<listitem><para> - -is the number of the partition on which -<filename>/etc/arcboot.conf</filename> resides - -</para></listitem> -</varlistentry> -<varlistentry> -<term> <replaceable>config</replaceable> </term> -<listitem><para> - -is the name of the configuration entry in -<filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by -default. - -</para></listitem> -</varlistentry> -</variablelist> - - </sect3> diff --git a/nl/using-d-i/modules/mipsel/colo-installer.xml b/nl/using-d-i/modules/mipsel/colo-installer.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/nl/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/nl/using-d-i/modules/netcfg.xml b/nl/using-d-i/modules/netcfg.xml deleted file mode 100644 index 4cf6211e7..000000000 --- a/nl/using-d-i/modules/netcfg.xml +++ /dev/null @@ -1,57 +0,0 @@ -<!-- original version: 50619 --> - - <sect3 id="netcfg"> - <title>Het netwerk configureren</title> - -<para> - -Als het systeem, wanneer u start met deze stap, detecteert dat u meer -dan één netwerkkaart heeft, zal u worden gevraagd welke van de apparaten -u wilt gebruiken voor uw primaire netwerkinterface, dat wil zeggen welke -u wilt gebruiken voor de installatie. U kunt de overige interfaces -configureren nadat de installatie is voltooid; zie hiervoor de man pagina -<citerefentry> <refentrytitle>interfaces</refentrytitle> -<manvolnum>5</manvolnum> </citerefentry>. - -</para><para> - -Tijdens een standaardinstallatie zal &d-i; proberen uw netwerkinterface -automatisch met behulp van DHCP in te stellen. Er zijn verschillende -redenen waarom dit zou kunnen falen, variërend van het niet aangesloten -zijn van de netwerkkabel tot een onjuiste DHCP-configuratie. Ook is het -mogelijk dat er helemaal geen DHCP-server in uw lokale netwerk aanwezig -is. Voor nadere diagnose kunt u de boodschappen op de vierde console -raadplegen. In elk geval zal u worden gevraagd of u een nieuwe poging wilt -wagen of dat u het netwerk handmatig wilt configureren. DHCP-servers -kunnen soms zeer traag zijn; probeer het dus nogmaals als u zeker weet dat -alles juist is ingesteld. - -</para><para> - -Bij handmatige configuratie van de netwerkinterface, zal u een aantal -vragen worden gesteld over uw netwerk, te weten: -<computeroutput>IP-adres</computeroutput>, -<computeroutput>Netwerkmasker</computeroutput>, -<computeroutput>Gateway</computeroutput>, -<computeroutput>Adressen van naamservers</computeroutput>, en -<computeroutput>Computernaam</computeroutput>. -Als u beschikt over een draadloos netwerkapparaat, zal u worden gevraagd -naar de <computeroutput>ESSID</computeroutput> van uw draadloos netwerk -en de <computeroutput>WEP sleutel</computeroutput>. Voer de waarden in -die u heeft verzameld bij <xref linkend="needed-info"/>. - -</para><note><para> - -De volgende technische details kunnen mogelijk van pas komen (of niet). -Het programma gaat ervan uit dat het IP-adres van uw netwerk het resultaat -is van een bit-gewijze AND-operatie van het IP-adres van uw systeem en het -netwerkmasker. Het standaard Broadcast-adres wordt berekend als het resultaat -van een bit-gewijze OR-operatie van het IP-adres van uw systeem en de -bitgewijze inverse van het netwerkmasker. Ook zal een default waarde voor een -standaard router (gateway) worden bepaald. Gebruik de staandaardwaarden van het -installatiesysteem als u de juiste waarden voor deze vragen niet kunt vinden; -u kunt ze, indien nodig, altijd nog wijzigen nadat de installatie is afgerond -door het bestand <filename>/etc/network/interfaces</filename> te wijzigen. - -</para></note> - </sect3> diff --git a/nl/using-d-i/modules/network-console.xml b/nl/using-d-i/modules/network-console.xml deleted file mode 100644 index edaee355f..000000000 --- a/nl/using-d-i/modules/network-console.xml +++ /dev/null @@ -1,110 +0,0 @@ -<!-- original version: 31173 --> - - <sect2 id="network-console"> - <title>Installeren over het netwerk</title> - -<para arch="not-s390"> - -Een van de meer interressante componenten is -<firstterm>network-console</firstterm>. Deze component maakt het mogelijk -om een groot deel van de installatie via SSH over het netwerk uit te voeren. -Het gebruik van het netwerk impliceert dat u de eerste stappen van de -installatie vanaf de console zult moeten uitvoeren: in ieder geval tot en -met de configuratie van het netwerk. (Het is echter mogelijk om dat deel van -de installatie te automatiseren; zie <xref linkend="automatic-install"/>.) - -</para><para arch="not-s390"> - -Deze component wordt niet automatisch getoond in het installatie menu en -dus moet u hem expliciet laden. - -Als u installeert vanaf CD-ROM, dient u de installatie te starten met -prioriteit <quote>medium</quote> of op een andere wijze het hoofdmenu -zichtbaar te maken. Bij de optie <guimenuitem>Installatiemodules van CD -laden</guimenuitem> selecteert u <guimenuitem>network-console: Continue -installation remotely using SSH</guimenuitem>. De component is succesvol -geladen als in het hoofdmenu een nieuwe optie <guimenuitem>Installatie -verder van op afstand doorlopen via SSH</guimenuitem> aanwezig is. - -</para><para arch="s390"> - -Voor installaties op &arch-title; is dit de standaard methode nadat -het netwerk is geconfigureerd. - -</para><para> - -<phrase arch="not-s390">Nadat u deze nieuwe optie heeft geselecteerd, -zal u</phrase><phrase arch="s390">U zal</phrase> worden gevraagd -naar een wachtwoord waarmee de verbinding met het installatiesysteem -zal worden gerealiseerd en een bevestiging daarvan. Dat is alles. -Vervolgens zal een melding worden getoond met instructies om vanaf een -ander systeem in te loggen als gebruiker <emphasis>installer</emphasis> -met het wachtwoord dat u daarnet heeft ingevoerd. Een ander belangrijk -detail op dit scherm is de <quote>vingerafdruk</quote> van dit systeem. -U dient deze op een veilige manier beschikbaar te stellen aan degene die -de installatie op afstand zal vervolgen. - -</para><para> - -Indien u besluit de installatie locaal te vervolgen, kunt u altijd met -behulp van de &enterkey; terugkeren naar het hoofdmenu, vanwaar u de -installatie kunt vervolgen. - -</para><para> - -Laten we ons nu verplaatsen naar het andere einde van de netwerkkabel. -Voordat u de verbinding kunt opzetten, dient u uw terminal te configureren -voor UTF-8 codering aangezien dat is wat het installatiesysteem gebruikt. -Als u dit niet doet is installatie nog wel mogelijk, maar kunt u vreemde -effecten op uw scherm tegenkomen als ontbrekende randen van dialogen of -onleesbare niet-ASCII karakters. U brengt de verbinding met het -installatiesysteem eenvoudig tot stand met: - -<informalexample><screen> -<prompt>$</prompt> <userinput>ssh -l installer <replaceable>nieuw_systeem</replaceable></userinput> -</screen></informalexample> - -Hierbij is <replaceable>nieuw_systeem</replaceable> ofwel de systeemnaam -ofwel het IP-adres van het systeem dat wordt geïnstalleerd. Voordat -daadwerkelijk wordt aangelogd zal de vingerafdruk van dat systeem worden -getoond en zult u moeten bevestigen dat dit correct is. - -</para><note><para> - -Als u meerdere systemen achter elkaar installeert en deze hetzelfde IP-adres -of dezelfde systeemnaam krijgen, zal <command>ssh</command> weigeren om de -verbinding te maken. De reden is dat opeenvolgende systemen een andere -vingerafdruk zullen hebben, wat meestal een indicatie is van een -<quote>spoofing</quote> aanval. Als u er zeker van bent dat dit niet het -geval is, dient u de betreffende regel te verwijderen uit -<filename>~/.ssh/known_hosts</filename> waarna u een nieuwe poging kunt doen. - -</para></note><para> - -Nadat u bent aangelogd zal een aanvangsscherm worden getoond met twee -opties genaamd <guimenuitem>Menu opstarten</guimenuitem> en -<guimenuitem>Shell opstarten</guimenuitem>. Eerstgenoemde optie biedt -toegang tot het hoofdmenu van het installatiesysteem vanwaar u de -installatie kunt vervolgen. Laatstgenoemde optie start een shell op het -nieuwe systeem die u kunt gebruiken om bijvoorbeeld logs te bekijken of -commando's uit te voeren. U dient maximaal één SSH-sessie te starten met -een installatiemenu, maar kunt desgewenst meerdere sessies starten met -een shell. - -</para><warning><para> - -Nadat u via SSH de installatie op afstand heeft gestart, kunt u de -installatiesessie op de locale console niet meer hervatten. Als u dat toch -doet, is de kans groot dat de gegevensbank met de configuratie van het -nieuwe systeem beschadigd raakt. Dit kan weer tot gevolg hebben dat de -installatie mislukt of resulteren in problemen met het nieuwe systeem. - -</para><para> - -Daarnaast wordt afgeraden om, als u de SSH-sessie uitvoert in een -X-terminal, de grootte van het venster te wijzigen aangezien het gevolg -zal zijn dat de verbinding wordt verbroken. - -</para></warning> - - </sect2> diff --git a/nl/using-d-i/modules/nobootloader.xml b/nl/using-d-i/modules/nobootloader.xml deleted file mode 100644 index ee85f4942..000000000 --- a/nl/using-d-i/modules/nobootloader.xml +++ /dev/null @@ -1,35 +0,0 @@ -<!-- original version: 61133 --> - - <sect3 id="nobootloader"> - <title>Verder gaan zonder opstartlader</title> - -<para> - -Deze optie kan gebruikt worden om de installatie te voltooien als er -geen opstartlader wordt geïnstalleerd, ofwel omdat er geen beschikbaar is -voor het (sub)platform, ofwel omdat u er geen wilt installeren (b.v. als -u de bestaande opstartlader wilt gebruiken). - -</para><para> - -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. -Als u van plan bent om uw opstartlader handmatig te configureren, -adviseren wij om in <filename>/target/boot</filename> de naam van de -geïnstalleerde kernel te controleren. Daarnaast dient u diezelfde map te -controleren op de aanwezigheid van een <firstterm>initrd</firstterm>. -Indien een initrd aanwezig is, zult u waarschijnlijk uw opstartlader -moeten configureren om deze te gebruiken. Andere gegevens die u nodig -heeft zijn de harde schijf en partitie die u heeft geselecteerd voor uw -<filename>/</filename> bestandssysteem en, als u ervoor heeft gekozen om -<filename>/boot</filename> op een afzonderlijke partitie te installeren, -ook die voor uw <filename>/boot</filename> bestandssysteem. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/os-prober.xml b/nl/using-d-i/modules/os-prober.xml deleted file mode 100644 index b51f8a16d..000000000 --- a/nl/using-d-i/modules/os-prober.xml +++ /dev/null @@ -1,24 +0,0 @@ -<!-- original version: 33725 --> - - <sect3 id="os-prober"> - <title>Andere besturingssystemen detecteren</title> - -<para> - -Voordat een opstartlader wordt geïnstalleerd, zal het installatiesysteem -eerst proberen om te ontdekken of er andere besturingsystemen op de machine -aanwezig zijn. Als het een besturingssysteem heeft gevonden dat wordt -ondersteund, zult u hierover worden geïnformeerd tijdens de installatie van -de opstartlader en zal de computer geconfigureerd worden om naast &debian; ook -dit andere besturingsysteem te kunnen opstarten. - -</para><para> - -Merk op dat het opstarten van meerdere besturingssystemen op één machine nog -altijd iets wegheeft van zwarte magie. De ondersteuning voor de detectie van -andere besturingssystemen en voor het instellen van opstartladers om deze te -laden, varieert per (sub)platform. Als het niet werkt dient u de documentatie -van uw opstartlader te raadplegen voor nadere informatie. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/partconf.xml b/nl/using-d-i/modules/partconf.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/partitioner.xml b/nl/using-d-i/modules/partitioner.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/nl/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/nl/using-d-i/modules/partman-crypto.xml b/nl/using-d-i/modules/partman-crypto.xml deleted file mode 100644 index 233f98693..000000000 --- a/nl/using-d-i/modules/partman-crypto.xml +++ /dev/null @@ -1,355 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56427 untranslated --> - - <sect3 id="partman-crypto"> - <title>Configuring Encrypted Volumes</title> -<para> - -&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. - -</para><para> - -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. - -</para><note><para> - -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. - -</para></note><para> - -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. - -</para><para> - -&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. - -<!-- TODO: link to the "Debian block device encryption guide" - once Max writes it :-) --> - -</para><para> - -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. - -<variablelist> - -<varlistentry> -<term>Encryption: <userinput>aes</userinput></term> - -<listitem><para> - -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. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Key size: <userinput>256</userinput></term> - -<listitem><para> - -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. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>IV algorithm: <userinput>cbc-essiv:sha256</userinput></term> - -<listitem><para> - -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. - -</para><para> - -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. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Encryption key: <userinput>Passphrase</userinput></term> - -<listitem><para> - -Here you can choose the type of the encryption key for this partition. - - <variablelist> - <varlistentry> - <term>Passphrase</term> - <listitem><para> - -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. - - </para></listitem> - </varlistentry> - - <varlistentry> - <term>Random key</term> - <listitem><para> - -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.) - - </para><para> - -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. - - </para></listitem> - </varlistentry> - </variablelist> - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Erase data: <userinput>yes</userinput></term> - -<listitem><para> - -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>. - -</para></listitem> -</varlistentry> - -</variablelist> - -</para><para> - -If you select <menuchoice> <guimenu>Encryption method:</guimenu> -<guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu -changes to provide the following options: - - -<variablelist> -<varlistentry> -<term>Encryption: <userinput>AES256</userinput></term> - -<listitem><para> - -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. - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Encryption key: <userinput>Keyfile (GnuPG)</userinput></term> - -<listitem><para> - -Here you can select the type of the encryption key for this partition. - - <variablelist> - <varlistentry> - <term>Keyfile (GnuPG)</term> - <listitem><para> - -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). - - </para></listitem> - </varlistentry> - - <varlistentry> - <term>Random key</term> - <listitem><para> - -Please see the section on random keys above. - - </para></listitem> - </varlistentry> - </variablelist> - -</para></listitem> -</varlistentry> - -<varlistentry> -<term>Erase data: <userinput>yes</userinput></term> - -<listitem><para> - -Please see the the section on erasing data above. - -</para></listitem> -</varlistentry> - -</variablelist> - -</para><para> - -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. - -</para><para> - -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.). - -</para><warning><para> - -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. - -</para></warning><para> - -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.). - -<!-- TODO: Mention hardware random generators when we will support - them --> - -This will be repeated for each partition to be encrypted. - -</para><para> - -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> -Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper - #1 115.1 GB F ext3 - -Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile - #1 515.2 MB F ext3 -</screen></informalexample> - -Now is the time to assign mount points to the volumes and optionally -change the file system types if the defaults do not suit you. - -</para><para> - -Pay attention to 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 -the ordinary boot process and the boot process with encryption involved will -be covered later in <xref linkend="mount-encrypted-volumes"/>. - -</para><para> - -Once you are satisfied with the partitioning scheme, continue with the -installation. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/partman-lvm.xml b/nl/using-d-i/modules/partman-lvm.xml deleted file mode 100644 index ca0c46716..000000000 --- a/nl/using-d-i/modules/partman-lvm.xml +++ /dev/null @@ -1,98 +0,0 @@ -<!-- original version: 56326 --> - - <sect3 id="partman-lvm"> - <title>Logisch volumebeheer (LVM) instellen</title> -<para> - -Als u met computers werkt op het niveau van systeembeheerder of -<quote>gevorderde</quote> gebruiker, heeft u vast de situatie meegemaakt -waar op een partitie (meestal de meest belangrijke) onvoldoende ruimte -beschikbaar was, terwijl een andere partitie grotendeels ongebruikt was. -Als oplossing heeft u mogelijk bestanden moeten verplaatsen met symbolische -verwijzingen vanaf de oude lokatie. - -</para><para> - -Om deze situatie te voorkomen, kunt u gebruik maken van Logisch volumebeheer -(Logical Volume Management — LVM). Met LVM kunt u uw partities (in de -terminologie van LVM <firstterm>fysieke volumes</firstterm>) combineren tot -een virtuele harde schijf (ofwel <firstterm>volumegroep</firstterm>); deze -kan op zijn beurt worden opgedeeld in virtuele partities (<firstterm>logische -volumes</firstterm>). Het nut hiervan is dat logische volumes (en natuurlijk -ook de onderliggende volumegroepen) verschillende fysieke harde schijven -kunnen omvatten. - -</para><para> - -Als u bijvoorbeeld vervolgens ontdekt dat u meer ruimte nodig heeft op uw -oude 160GB <filename>/home</filename> partitie, kunt u eenvoudig een extra -300GB harde schijf in de computer plaatsen, deze toevoegen in uw bestaande -volumegroep en vervolgens het logische volume vergroten waarop uw -<filename>/home</filename> bestandssysteem zich bevindt. En klaar is Kees: uw -gebruikers kunnen beschikken over de extra ruimte op een vernieuwde partitie -van 460GB. Dit voorbeeld is uiteraard enigszins gesimplificeerd. Wij raden u -aan om, voor zover u dat nog niet heeft gedaan, de -<ulink url="&url-lvm-howto;">LVM HOWTO</ulink> te raadplegen. - -</para><para> - -Het instellen van LVM in &d-i; is relatief eenvoudig en volledig ondersteund -in <command>partman</command>. Allereerst dient u de partitie(s) die u wilt -gebruiken als fysieke volumes voor LVM, te markeren. -Hiervoor selecteert u in <command>partman</command> -vanuit het menu <guimenu>Partitie-instellingen</guimenu> -de optie <menuchoice> <guimenu>Gebruiken als:</guimenu> -<guimenuitem>Fysiek volume voor LVM</guimenuitem> </menuchoice>. - -</para><para> - -Als u terugkeert op het hoofdscherm van <command>partman</command>, zult u -een nieuwe optie <guimenuitem>Logisch volumebeheer (LVM) instellen</guimenuitem>. -Als u deze selecteert, zal u eerst worden gevraagd om nog niet vastgelegde -wijzigingen in de partitietabel te bevestigen (als die er zijn) en vervolgens -zal het configuratiemenu voor LVM worden getoond. Het menu is contextgevoelig -en toont alleen toegestane acties. De mogelijke acties zijn: - -<itemizedlist> - <listitem><para> - <guimenuitem>Toon configuratiedetails</guimenuitem>: - toont onder andere de structuur van LVM-elementen en de namen en groottes - van logische volumes - </para></listitem> - <listitem><para> - <guimenuitem>Volumegroep aanmaken</guimenuitem> - </para></listitem> - <listitem><para> - <guimenuitem>Logisch volume aanmaken</guimenuitem> - </para></listitem> - <listitem><para> - <guimenuitem>Volumegroep verwijderen</guimenuitem> - </para></listitem> - <listitem><para> - <guimenuitem>Logisch volume verwijderen</guimenuitem> - </para></listitem> - <listitem><para> - <guimenuitem>Volumegroep uitbreiden</guimenuitem> - </para></listitem> - <listitem><para> - <guimenuitem>Volumegroep verkleinen</guimenuitem> - </para></listitem> - <listitem><para> - <guimenuitem>Einde</guimenuitem>: - keer terug naar het hoofdscherm van <command>partman</command> - </para></listitem> -</itemizedlist> - -</para><para> - -Gebruik de opties in dit menu om eerst een volume groep en vervolgens -daaronder de gewenste logische volumes. - -</para><para> - -Als u wederom terugkeert op het hoofdscherm van <command>partman</command>, -zult u de aangemaakte logische volumes als ware het gewone partities -terugvinden in het menu (en u kunt ze verder ook als zodanig behandelen). - -</para> - </sect3> diff --git a/nl/using-d-i/modules/partman.xml b/nl/using-d-i/modules/partman.xml deleted file mode 100644 index 76389e9ed..000000000 --- a/nl/using-d-i/modules/partman.xml +++ /dev/null @@ -1,240 +0,0 @@ -<!-- original version: 39529 --> - -<para> - -Als u weinig ervaring heeft met het indelen van schijven of gewoon meer -gedetailleerde informatie wenst, kunt u <xref linkend="partitioning"/> -raadplegen. - -</para><para> - -Allereerst zal u de gelegenheid worden geboden om een gehele harde schijf, -of (indien aanwezig) de beschikbare vrije ruimte op een schijf, automatisch -in te delen. -Dit wordt <quote>begeleide schijfindeling</quote> genoemd. Als u dit niet -wenst, kies dan de optie <guimenuitem>Schijfindeling handmatig -bepalen</guimenuitem> uit het menu. - -</para> - - <sect3 id="partman-auto"> - <title>Begeleide schijfindeling</title> -<para> - -Als u kiest voor begeleide schijfindeling, heeft u mogelijk twee opties: -de partities direct op de harde schijf aanmaken (de klassieke methode) of -gebruik maken van logisch volumebeheer (LVM). In het tweede geval zal het -installatiesysteem de meeste partities aanmaken binnen één grote overkoepelende -partitie; het voordeel van deze methode is dat de grootte van de partities -binnen die overkoepelende partitie relatief eenvoudig kan worden gewijzigd. -Merk op dat de optie om gebruik te maken van LVM niet op alle platforms -beschikbaar hoeft te zijn. - -</para> -<warning><para> - -Als u kiest voor begeleide schijfindeling met gebruik van LVM, zal het -niet mogelijk zijn om wijzigingen in de partitietabel ongedaan te maken. -Met deze keuze worden effectief alle gegevens verwijderd die zich nu op -de harde schijf bevinden - -</para></warning> -<para> - -Nadat u heeft gekozen voor begeleide schijfindeling (klassieke methode -danwel met gebruik van LVM), kunt u een keuze maken uit de schema's -weergegeven in onderstaande tabel. Elk van deze schema's -heeft zijn voor- en nadelen, waarvan een aantal wordt besproken in -<xref linkend="partitioning"/>. Als u twijfelt, kies dan de eerste optie. -Merk op dat begeleide schijfindeling een zekere minimale vrije schijfruimte -nodig heeft om te kunnen werken. Als u niet tenminste ongeveer 1GB ruimte -(afhankelijk van het gekozen schema) beschikbaar heeft, zal de begeleide -schijfindeling mislukken. - -</para> - -<informaltable> -<tgroup cols="3"> -<thead> -<row> - <entry>Schema voor schijfindeling</entry> - <entry>Minimale ruimte</entry> - <entry>Aangemaakte partities</entry> -</row> -</thead> - -<tbody> -<row> - <entry>Alles in één partitie</entry> - <entry>600MB</entry> - <entry><filename>/</filename>, swap</entry> -</row><row> - <entry>Afzonderlijke /home partitie</entry> - <entry>500MB</entry> - <entry> - <filename>/</filename>, <filename>/home</filename>, swap - </entry> -</row><row> - <entry>Afzonderlijke /home, /usr, /var en /tmp partities</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> - -Als u kiest voor begeleide schijfindeling met gebruik van LVM, dan zal het -installatiesysteem ook een afzonderlijke <filename>/boot</filename> partitie -aanmaken. Alle andere partities, met uitzondering van de wisselgeheugen (swap) -partitie, zullen worden aangemaakt in de LVM partitie. - -</para><para arch="ia64"> - -Als u voor uw IA64 systeem kiest voor begeleide schijfindeling, zal een -extra partitie, geformatteerd met een FAT16 opstartbaar bestandssysteem, -worden aangemaakt ten behoeve van de EFI-opstartlader. -Er is ook een aanvullende menuoptie in het keuzemenu met formateeropties -om handmatig een EFI-opstartpartitie te kunnen aanmaken. - -</para><para> - -Nadat u een schema heeft geselecteerd, zal op het volgende scherm de -nieuwe partitie-indeling worden getoond met daarbij indicaties of en -hoe deze geformatteerd zullen worden en op welke aanhechtpunten ze -gekoppeld zullen worden. - -</para><para> - -De partitie-indeling zou er als volgt uit kunnen zien: - -<informalexample><screen> - IDE1 master (hda) - 6.4 GB WDC AC36400L - #1 primair 16.4 MB B f ext2 /boot - #2 primair 551.0 MB swap swap - #3 primair 5.8 GB ntfs - pri/log 8.2 MB VRIJE RUIMTE - - IDE1 slave (hdb) - 80.0 GB ST380021A - #1 primair 15.9 MB ext3 - #2 primair 996.0 MB fat16 - #3 primair 3.9 GB xfs /home - #5 logisch 6.0 GB f ext3 / - #6 logisch 1.0 GB f ext3 /var - #7 logisch 498.8 MB ext3 - #8 logisch 551.5 MB swap swap - #9 logisch 65.8 GB ext2 -</screen></informalexample> - -Dit voorbeeld toont twee IDE harde schijven die zijn opgedeeld in -verschillende partities; de eerste schijf heeft nog vrije ruimte. Elke -regel voor een partitie bevat de volgende informatie: partitienummer, -type en grootte van de partitie, wijzigingindicatoren, het bestandssysteem -en het aanhechtpunt (indien aanwezig) voor de partitie. -Merk op dat de hier weergegeven indeling niet kan worden gerealiseerd met -behulp van begeleide schijfindeling; zij toont echter wel de flexibiliteit -die kan worden bereikt met handmatige schijfindeling. -<!-- FJP: De wijzigingindicatoren zijn de smileys die aangeven wat er - met een partitie gat gebeuren. Dit moet nog worden uitgewerkt.--> - -</para><para> - -Hiermee is de begeleide schijfindeling voltooid. Als u tevreden bent met de -voorgestelde indeling, kunt u de menuoptie <guimenuitem>Schijfindeling -afsluiten & veranderingen naar schijf schrijven</guimenuitem> kiezen om -de nieuwe partitie-indeling te implementeren (zoals beschreven aan het einde -van deze paragraaf). Als u nog niet tevreden bent, kunt u kiezen voor -<guimenuitem>Veranderingen aan partities ongedaan maken</guimenuitem> en de -begeleide schijfindeling nogmaals uit te voeren of om de voorgestelde indeling -te wijzigen zoals hieronder beschreven voor handmatige schijfindeling. - -</para> - </sect3> - - <sect3 id="partman-manual"> - <title>Handmatige schijfindeling</title> -<para> - -Als u kiest voor handmatige schijfindeling, zal een vergelijkbaar scherm -worden getoond als hiervoor weergegeven, maar dan met uw bestaande -partitie-indeling en nog zonder aanhechtpunten. Hoe u de schijfindeling -en het gebruik van partities voor uw nieuwe &debian; systeem handmatig kunt -instellen, wordt hieronder behandeld. - -</para><para> - -Als een een nog maagdelijke schijf (waarop nog geen partities of vrije -ruimte gedefinieerd is) selecteert, zal u de mogelijkheid krijgen om een -nieuwe partitietabel te creëren (deze is nodig om partities te kunnen -aanmaken). Daarna behoort onder de geselecteerde schijf een nieuwe regel -met <quote>VRIJE RUIMTE</quote> te verschijnen. - -</para><para> - -Als u een regel met vrije ruimte selecteert, kunt u een nieuwe partitie -creëren. U zult een korte serie vragen over grootte, type (primair of -logisch) en positie (aan het begin of einde van de vrije ruimte) moeten -beantwoorden. Daarna krijgt u een gedetailleerd overzicht van de nieuwe -partitie. Daarin vindt u als aanhechtpunt, aankoppelopties, de indicatie of -de partitie opstartbaar moet zijn, en typisch gebruik. Als de -standaardwaarden u niet bevallen, kunt u ze naar behoefte wijzigen. Door -bijvoorbeeld de optie <guimenuitem>Gebruiken als:</guimenuitem> te selecteren, -kunt u een ander bestandssysteem voor de partitie selecteren, inclusief de -mogelijkheid om de partitie te gebruiken voor wisselgeheugen ('swap'), als -onderdeel van software RAID of LVM, of om de partitie helemaal niet te -gebruiken. Een andere aardige optie is de mogelijkheid om gegevens vanaf -een andere partitie naar de nieuwe partitie te kopiëren. -Als u tevreden bent met de nieuwe partitie kiest u <guimenuitem>Klaar met -instellen van partitie</guimenuitem> waarna u terugkeert naar het hoofdmenu -van <command>partman</command>. - -</para><para> - -Als u een instelling van een partitie wilt wijzigen, selecteert u -deze gewoon waarna u in het configuratiemenu voor de partitie komt. -Dit is hetzelfde scherm als bij het aanmaken van een nieuwe partitie en -u kunt dus dezelfde serie instellingen wijzigen. Iets dat mogelijk niet -meteen duidelijk is, is dat u de grootte van een partitie kunt wijzigen -door de regel met de grootte van de partitie te selecteren. -Bestandssystemen waarvan bekend is dat dit werkt zijn in ieder geval -fat16, fat32, ext2, ext3 en swap. Dit menu stelt u ook in staat om een -partitie te verwijderen. - -</para><para> - -Zorg ervoor dat u tenminste twee partities aanmaakt: één voor het -<emphasis>root</emphasis>-bestandssysteem (dat gekoppeld moet worden -aan het aanhechtpunt <filename>/</filename>) en één voor -<emphasis>swap</emphasis>. Als u vergeet om het root-bestandssysteem -aan te koppelen, zal <command>partman</command> u niet verder laten gaan -tot dit probleem is verholpen. - -</para><para arch="ia64"> - -Als u vergeet om een EFI-opstartpartitie te selecteren en formatteren, zal -<command>partman</command> dit signaleren en u beletten verder te gaan tot -u er een heeft toegewezen. - -</para><para> - -De functionaliteit van <command>partman</command> kan worden vergroot -met behulp van installatiesysteemmodules, maar is afhankelijk van het -platform waartoe uw systeem behoort. Als u dus niet alle beschreven -mogelijkheden ziet, controleer dan of alle vereiste modules (zoals -<filename>partman-ext3</filename>, <filename>partman-xfs</filename>, -of <filename>partman-lvm</filename>) zijn geladen. - -</para><para> - -Als u tevreden bent met het eindresultaat van de schijfindeling, kiest u -de menuoptie <guimenuitem>Schijfindeling afsluiten & veranderingen naar -schijf schrijven</guimenuitem>. Daarna zal een overzicht worden getoond van -de wijzigingen in de schijfindeling en zal u worden gevraagd om deze te -bevestigen voordat de gewenste wijzigingen worden doorgevoerd. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/pkgsel.xml b/nl/using-d-i/modules/pkgsel.xml deleted file mode 100644 index 408377216..000000000 --- a/nl/using-d-i/modules/pkgsel.xml +++ /dev/null @@ -1,70 +0,0 @@ -<!-- original version: 35518 --> - - <sect3 id="pkgsel"> - <title>Software selecteren en installeren</title> - -<para> - -Tijdens de installatie wordt de mogelijkheid geboden om aanvullende -programmatuur te installeren. In plaats van het selecteren van individuele -softwarepakketten uit de &num-of-distrib-pkgs; beschikbare pakketten, ligt -de nadruk tijdens deze fase van de installatie op het selecteren en installeren -van vooraf gedefinieerde verzamelingen van programmatuur waarmee uw computer -snel kan worden ingericht voor het uitvoeren van diverse taken. - -</para><para> - -U heeft dus de mogelijkheid om allereerst <emphasis>taken</emphasis> te -selecteren en vervolgens daaraan individuele pakketten toe te voegen. -Globaal vertegenwoordigen deze taken verschillende doeleinden waarvoor u -uw computer zou kunnen gebruiken, zoals <quote>Desktopomgeving</quote>, -<quote>Webserver</quote> of <quote>Printserver</quote><footnote> - -<para> - -Door <command>base-config</command> wordt om deze lijst te tonen het programma <command>tasksel</command> aangeroepen. Voor handmatige pakketselectie wordt -het programma <command>aptitude</command> uitgevoerd. Elk van deze programma's -kunt u na de installatie op elk gewenst moment zelf uitvoeren om extra pakketten -te installeren (of te verwijderen). Als u, nadat de installatie voltooid is, op -zoek bent naar een specifiek pakket, kunt u eenvoudig <userinput>aptitude -install <replaceable>pakket</replaceable></userinput> uitvoeren, waarbij -<replaceable>pakket</replaceable> de naam is van het pakket dat u zoekt. - -</para> - -</footnote>. In <xref linkend="tasksel-size-list"/> is een overzicht opgenomen -van de voor de beschikbare taken benodigde ruimte. - -</para><para> - -Nadat u de gewenste taken heeft geselecteerd, selecteert u <guibutton>Ok</guibutton>. -Vervolgens zal de installatie van de pakketten die behoren bij de door u -geselecteerde taken, plaatsvinden met behulp van <command>aptitude</command>. - -<note><para> - -Bij de standaard gebruikersinterface van het installatiesysteem kunt u de -spatiebalk gebruiken een taak te (de)selecteren. - -</para></note> - -<note><para> - -Merk op dat sommige taken reeds automatisch geselecteerd kunnen zijn -(afhankelijk van eigenschappen van het systeem waarop de installatie wordt -uitgevoerd). Als u het met deze selectie niet eens bent, kunt u deze ongedaan -maken. U kunt er zelfs voor kiezen om geen enkele taak te installeren. - -</para></note> - -</para><para> - -Elk pakket dat u met behulp van <command>tasksel</command> heeft -geselecteerd, wordt gedownload, uitgepakt en vervolgens geïnstalleerd -door achtereenvolgens de programma's <command>apt-get</command> en -<command>dpkg</command>. Als een bepaald programma aanvullende informatie -van de gebruiker nodig heeft, zal hierom tijdens dit proces worden -gevraagd. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/powerpc/quik-installer.xml b/nl/using-d-i/modules/powerpc/quik-installer.xml deleted file mode 100644 index ed6aa6a60..000000000 --- a/nl/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/nl/using-d-i/modules/powerpc/yaboot-installer.xml b/nl/using-d-i/modules/powerpc/yaboot-installer.xml deleted file mode 100644 index fdbf1edcb..000000000 --- a/nl/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-gnu;. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/s390/dasd.xml b/nl/using-d-i/modules/s390/dasd.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/s390/netdevice.xml b/nl/using-d-i/modules/s390/netdevice.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/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/nl/using-d-i/modules/s390/zipl-installer.xml b/nl/using-d-i/modules/s390/zipl-installer.xml deleted file mode 100644 index 61aa6465c..000000000 --- a/nl/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/nl/using-d-i/modules/save-logs.xml b/nl/using-d-i/modules/save-logs.xml deleted file mode 100644 index 7c0c1fe1a..000000000 --- a/nl/using-d-i/modules/save-logs.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- original version: 33725 --> - - <sect3 id="save-logs"> - <title>De logbestanden van de installatie bewaren</title> - -<para> - -Als de installatie succesvol is, worden de logbestanden die tijdens -het installatieproces zijn aangemaakt, automatisch opgeslagen in de -map <filename>/var/log/debian-installer/</filename> op uw nieuwe -&debian; systeem. - -</para><para> - -De optie <guimenuitem>Debug-logbestanden opslaan</guimenuitem> in -het hoofdmenu biedt u de mogelijkheid om de logbestanden op een -diskette, via het netwerk, op harde schijf of op een ander medium te -bewaren. Dit kan nuttig zijn als u onoverkomelijke problemen tegenkomt -tijdens de installatie en u de logbestanden op een ander systeem wilt -bestuderen of u ze wilt meesturen met een installatierapport. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/shell.xml b/nl/using-d-i/modules/shell.xml deleted file mode 100644 index 356b3cfaa..000000000 --- a/nl/using-d-i/modules/shell.xml +++ /dev/null @@ -1,42 +0,0 @@ -<!-- original version: 21579 --> - - <sect3 id="shell"> - <title>Een shell gebruiken en de logs bekijken</title> - -<para> - -In het hoofdmenu is een optie <guimenuitem>Een shell openen</guimenuitem> -aanwezig. Als het menu niet beschikbaar is op het moment dat u gebruik -wilt maken van een shell, kunt u op <keycombo><keycap>Linker Alt</keycap> -<keycap>F2</keycap></keycombo> (op een Mac-toetsenbord: -<keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>) indrukken -om naar de tweede <emphasis>virtuele</emphasis> terminal te schakelen. Dat -wil zeggen de toets <keycap>Alt</keycap> (links van de -<keycap>spatiebalk</keycap>) en de functietoets <keycap>F2</keycap> -tegelijkertijd indrukken. Dit is een afzonderlijk scherm waarin de shell -<command>ash</command>, een kloon van de Bourne-shell, draait - -</para><para> - -Op dat punt is uw systeem opgestart vanaf een RAM-schijf en heeft u een -beperkte set van Unix hulpprogramma's beschikbaar. U kunt zien welke -programma's beschikbaar zijn door het commando <command>ls /bin /sbin -/usr/bin /usr/sbin</command> te geven en door <command>help</command> -te typen. De tekstverwerker is <command>nano</command>. De shell heeft een -aantal aardige functies zoals het automatisch voltooien van commando's en -bestandsnamen en een opdrachthistorie. -<!-- FJP: is er een kortere vertaling voor 'autocompletion'? --> - -</para><para> - -Gebruik echter de menu's om de taken van het installatiesysteem uit te -voeren — de shell en commando's zijn er uitsluitend voor het geval -er iets mis gaat. U dient in het bijzonder altijd het menu, en niet de -shell, te gebruiken om wisselgeheugen te activeren De reden hiervoor is -dat het installatiesysteem dit niet kan signaleren als u dit vanuit de -shell doet. Druk op <keycombo><keycap>Linker Alt</keycap> -<keycap>F1</keycap></keycombo> om terug te keren naar de menu's, of type -<command>exit</command>, als u de shell heeft gestart met de menuoptie. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/sparc/silo-installer.xml b/nl/using-d-i/modules/sparc/silo-installer.xml deleted file mode 100644 index 3ce2b6ac6..000000000 --- a/nl/using-d-i/modules/sparc/silo-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 24582 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 -alongside an existing SunOS/Solaris install. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/tzsetup.xml b/nl/using-d-i/modules/tzsetup.xml deleted file mode 100644 index d68fc5300..000000000 --- a/nl/using-d-i/modules/tzsetup.xml +++ /dev/null @@ -1,54 +0,0 @@ -<!-- original version: 50620 --> - -<para> - -Afhankelijk van de eerder geselecteerde locatie, kan een keuzelijst met -tijdzones relevant voor die lokatie worden getoond. Als voor uw locatie -slechts één tijdzone relevant is, zal niets worden gevraagd maar wordt -de betreffende tijdzone automatisch ingesteld. - -</para><para> - -Als u, om wat voor reden dan ook, een tijdzone wilt instellen die -<emphasis>niet</emphasis> past bij de geselecteerde locatie, dan zijn er -twee opties. - -</para> - -<orderedlist> -<listitem> - -<para> - -De meest eenvoudige optie is om gewoon een andere tijdzone in te stellen -nadat de installatie is afgerond en u uw nieuwe systeem heeft opgestart. -Het juiste commando hiervoor is: - -<informalexample><screen> -# dpkg-reconfigure tzdata -</screen></informalexample> - -</para> - -</listitem><listitem> - -<para> - -Een alternatieve mogelijkheid is om de tijdzone helemaal aan het begin van -de installatie op te geven door de parameter -<userinput>time/zone=<replaceable>waarde</replaceable></userinput> -mee te geven bij het opstarten van het installatiesysteem. -De waarde dient uiteraard een geldige tijdzone te zijn, zoals -<userinput>Europe/Amsterdam</userinput> of <userinput>UTC</userinput>. - -</para> - -</listitem> -</orderedlist> - -<para> - -Voor geautomatiseerde installaties kan de tijdzone ook worden ingesteld door -gebruikmaking van voorconfiguratie. - -</para> diff --git a/nl/using-d-i/modules/user-setup.xml b/nl/using-d-i/modules/user-setup.xml deleted file mode 100644 index b39dba31e..000000000 --- a/nl/using-d-i/modules/user-setup.xml +++ /dev/null @@ -1,70 +0,0 @@ -<!-- original version: 50618 --> - - <sect3 id="user-setup-root"> - <title>Het wachtwoord voor root instellen</title> - -<para> - -Het <emphasis>root</emphasis>-account wordt ook wel de -<emphasis>super-user</emphasis> genoemd; het is een login die alle -beveiligingen op uw systeem omzeilt. Het root-account dient alleen te -worden gebruikt voor systeemadministratie en altijd gedurende een zo -kort mogelijke tijd. - -</para><para> - -Elk wachtwoord dat u aanmaakt zou uit tenminste 6 tekens moeten bestaan en -zou zowel hoofd- als kleine letters als ook leestekens moeten bevatten. -Wees extra zorgvuldig als u het wachtwoord voor root instelt, aangezien -dit account zoveel rechten geeft. Vermijd woorden die voorkomen in -woordenboeken en het gebruik van persoonlijke gegevens die eenvoudig kunnen -worden geraden. -<!-- FJP: vermelden dat wachtwoorden tijdens invoer onleesbaar zijn en daarom -twee keer moeten worden ingevoerd? //--> - -</para><para> - -Wees zeer argwanend als iemand u ooit vertelt dat hij het wachtwoord -van uw root-account nodig heeft. Normaalgesproken zou u het wachtwoord voor -uw root-account nooit mogen uitgeven, tenzij u een machine beheert die meer -dan één systeembeheerder heeft. -<!-- FJP: noemen alternatieven: su, sudo //--> - -</para> - </sect3> - - <sect3 id="make-normal-user"> - <title>Een gewone gebruiker aanmaken</title> - -<para> - -Het systeem zal u op dit punt ook vragen of u een gewoon gebruikersaccount -wilt aanmaken. Dit account is voor u de normale manier om aan te loggen. -Het is <emphasis>niet</emphasis> de bedoeling dat u het root-account benut -voor dagelijks gebruik of als uw persoonlijke login. - -</para><para> - -Waarom niet? Wel, één reden om het gebruik van de privileges van root te -vermijden is dat het zeer eenvoudig is om als root onherstelbare schade -aan te richten. Een andere reden is dat u verleid zou kunnen worden om een -<emphasis>Trojaans-paard</emphasis> te draaien — een programma dat -misbruik maakt van uw rechten als super-user om achter uw rug de beveiliging -van uw systeem de doorbreken. In elk degelijk boek over systeembeheer voor -Unix wordt meer uitgebreid ingegaan op dit onderwerp — overweeg om er -één te lezen als dit nieuw voor u is. - -</para><para> - -U zult eerst worden gevraagd om de volledige naam van de gebruiker in te voeren. -Vervolgens wordt u gevraagd om de naam voor het gebruikersaccount; in het -algemeen is uw voornaam (de standaardwaarde) of iets dergelijks afdoende. -Tot slot zal een wachtwoord voor dit account worden gevraagd. - -</para><para> - -Als u op enig moment na de installatie nog een gebruikersaccount wilt -aanmaken, kunt u het commando <command>adduser</command> gebruiken. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/x86/grub-installer.xml b/nl/using-d-i/modules/x86/grub-installer.xml deleted file mode 100644 index 9c654d539..000000000 --- a/nl/using-d-i/modules/x86/grub-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 46722 untranslated --> - - <sect3 arch="any-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 -new users 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, use the &BTN-GOBACK; button to get to the -main menu, and from there select whatever bootloader you would like to use. - -</para> - </sect3> diff --git a/nl/using-d-i/modules/x86/lilo-installer.xml b/nl/using-d-i/modules/x86/lilo-installer.xml deleted file mode 100644 index 89cc7f37e..000000000 --- a/nl/using-d-i/modules/x86/lilo-installer.xml +++ /dev/null @@ -1,67 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 49849 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 GNU/Linux and GNU/Hurd after the installation. - -</para></note> -<para> - -&d-i; offers you three choices on 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 beginning -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 traditional device 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;! - -</para> - </sect3> diff --git a/nl/using-d-i/using-d-i.xml b/nl/using-d-i/using-d-i.xml deleted file mode 100644 index 0cb8ec429..000000000 --- a/nl/using-d-i/using-d-i.xml +++ /dev/null @@ -1,418 +0,0 @@ -<!-- original version: 56428 --> - - <chapter id="d-i-intro"><title>Het &debian; installatiesysteem gebruiken</title> - - <sect1><title>Hoe het installatiesysteem werkt</title> -<para> - -Het &debian; installatiesysteem bestaat uit een aantal modules die -zijn ontwikkeld om een specifieke taak uit te voeren tijdens de installatie. -Elke module voert zijn taak uit, waarbij vragen kunnen worden gesteld -aan de gebruiker als dat voor die taak nodig is. Aan de vragen zelf is -een prioriteit toegekend, en de prioriteit van de vragen die zullen worden -gesteld wordt ingesteld bij het opstarten van het installatiesysteem. - -</para><para> - -Als een standaard installatie wordt uitgevoerd, zullen alleen essentiële -vragen (met prioriteit HIGH) worden gesteld. Het resultaat is een in hoge -mate geautomatiseerd installatieproces met weinig interactie met de -gebruiker. Modules worden vanzelf in de juiste volgorde uitgevoerd; -welke modules worden uitgevoerd wordt hoofdzakelijk bepaald door de -gekozen installatiemethode en door uw apparatuur. Het installatiesysteem -zal standaard antwoorden gebruiken voor vragen die niet worden gesteld. - -</para><para> - -Als er een probleem optreedt, wordt een scherm met een foutboodschap getoond -en kan het menu van het installatiesysteem worden getoond zodat de gebruiker -een alternatieve actie kan selecteren. Als er geen problemen zijn, zal de -gebruiker het menu van het installatiesysteem nooit zien, maar eenvoudig de -vragen voor iedere opeenvolgende module kunnen beantwoorden. Meldingen van -kritische fouten hebben een prioriteit CRITICAL waardoor de gebruiker altijd -geïnformeerd zal worden. -<!-- FJP Prioriteiten in caps (gebeurt ook later in tekst) //--> - -</para><para> - -Enkele van de standaard waarden die het installatiesysteem gebruikt, kunnen -worden gestuurd door opstartparameters mee te geven bij het starten van &d-i;. -Als u bijvoorbeeld statische netwerkconfiguratie wilt forceren (standaard wordt -DHCP gebruikt indien dit beschikbaar is), kunt u de opstartparameter -<userinput>netcfg/disable_dhcp=true</userinput> toevoegen. Zie -<xref linkend="installer-args"/> voor een overzicht van beschikbare opties. - -</para><para> - -Het is mogelijk dat gevorderde gebruikers zich meer thuis voelen met een -menugestuurde interface, waarbij niet het installatiesysteem automatisch -elke stap in volgorde uitvoert maar elke stap door de gebruiker zelf -wordt bepaald. Om het installatiesysteem op een handmatige, menugestuurde -manier uit te voeren, moet de opstartparameter -<userinput>priority=medium</userinput> worden toegevoegd. - -</para><para> - -Als het voor uw apparatuur noodzakelijk is om parameters mee te geven bij de -installatie van kernelmodules, dan zal u het installatiesysteem moeten starten -in de <quote>expert</quote> modus. Dit is mogelijk door voor het opstarten -van het installatiesysteem ofwel het commando <command>expert</command> te -gebruiken ofwel de opstartparameter <userinput>priority=low</userinput> -toe te voegen. De expert modus geeft u volledige controle over &d-i;. - -</para><para condition="gtk"> - -Voor dit platform ondersteunt &d-i; twee verschillende gebruikersinterfaces: -een tekstuele en een graphische. Tenzij u in het initiële opstartmenu kiest -voor <quote>Graphical install</quote> zal de tekstuele interface worden -gebruikt. Zie <xref linkend="graphical"/> voor nadere informatie over de -grafische versie van het installatiesysteem. - -</para><para condition="not-gtk"> - -Voor dit platform gebruikt het installatiesysteem een tekstuele -gebruikersinterface. Een grafische gebruikersinterface is momenteel niet -beschikbaar. - -</para><para> - -Voor de tekstuele gebruikersinterface wordt gebruik van een muis niet -ondersteund. De volgende toetsen kunnen worden gebruikt om te navigeren binnen -de diverse configuratieschermen. Om <quote>vooruit</quote> of -<quote>terug</quote> te gaan tussen getoonde knoppen of selecties, gebruikt ui -de toetsen <keycap>Tab</keycap> of pijl <keycap>rechts</keycap>, respectievelijk -de <keycombo> <keycap>Shift</keycap> <keycap>Tab</keycap> </keycombo> of pijl -<keycap>links</keycap>. Met de pijlen -<keycap>omhoog</keycap> en <keycap>omlaag</keycap> selecteert u de verschillende -regels in een schuifbare lijst en verschuift u ook de lijst zelf. Daarnaast -kunt u, bij lange lijsten, een letter intoetsen waardoor meteen het deel van de -lijst zal worden getoond waarvan de regels met die letter beginnen. Ook kunt -u met <keycap>Pagina omhoog</keycap> en <keycap>Pagina omlaag</keycap> -de lijst per pagina verschuiven. Met de <keycap>spatiebalk</keycap> selecteert u -opties, bijvoorbeeld bij een keuzevak. Gebruik &enterkey; om keuzes te activeren. - -</para><para arch="s390"> - -S/390 ondersteunt geen virtuele consoles. U kunt echter een tweede en derde -ssh sessie openen om de hieronder beschreven logboeken te bekijken. - -</para><para> - -Foutmeldingen worden omgeleid naar de vierde console. -U kunt toegang krijgen tot deze console door -op <keycombo><keycap>linker Alt</keycap><keycap>F4</keycap></keycombo> -te drukken (houd de linker <keycap>Alt</keycap> toets vast terwijl u de -<keycap>F4</keycap> functietoets indrukt); u keert terug naar het hoofd -installatiescherm met -<keycombo><keycap>linker Alt</keycap><keycap>F1</keycap></keycombo>. - -</para><para> - -Deze meldingen kunnen ook worden teruggevonden in -<filename>/var/log/syslog</filename>. Na de installatie wordt dit logbestand -gekopieerd naar <filename>/var/log/installer/syslog</filename> op uw -nieuwe systeem. Andere installatiemeldingen kunnen tijdens de installatie worden -gevonden in <filename>/var/log/</filename> en, nadat de computer opnieuw is -opgestart met het nieuwe systeem, in <filename>/var/log/installer/</filename>. - -</para> - </sect1> - - - <sect1 id="modules-list"><title>Introductie van de modules</title> -<para> - -Hieronder vindt u een lijst van de modules van het installatiesysteem -met een korte beschrijving van het doel van elke module. Details over -het gebruik van een specifieke module staan in <xref linkend="module-details"/>. -<!-- FJP Toevoegen dat welke modules verplicht/optioneel zijn? //--> - -</para> - -<variablelist> -<varlistentry> - -<term>main-menu</term><listitem><para> -De module 'main-menu' (hoofdmenu) toont tijdens de installatie de -lijst met modules aan de gebruiker en start een module wanneer deze -geselecteerd wordt. De vragen van deze module hebben prioriteit MEDIUM; -dit betekent dat u het menu niet zult zien als u de prioriteit voor -de installatie heeft ingesteld op HIGH of CRITICAL (HIGH is de -standaardwaarde). Indien er echter een fout optreedt waarvoor uw -interventie nodig is, kan de prioriteit tijdelijk worden verlaagd om -u in de gelegenheid te stellen het probleem op te lossen en in dat -geval kan dus het menu alsnog verschijnen. - -</para><para> - -U kunt het hoofdmenu van het installatiesysteem bereiken door herhaaldelijk -de &BTN-GOBACK; knop te selecteren, waardoor u stapsgewijs teruggaat -uit de op dat moment actieve module. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>localechooser</term><listitem><para> - -Stelt de gebruiker in staat om de lokalisatie te bepalen voor zowel -de installatie als het geïnstalleerde systeem: taal, locatie en -<quote>locale</quote>. Tijdens de installatie zullen boodschappen in de -gekozen taal worden getoond, tenzij de vertaling voor die taal niet -compleet is. Als een vertaling niet compleet is, worden de boodschappen -in het Engels getoond. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>console-setup</term><listitem><para> - -De module 'kbd-chooser' (toetsenbordkiezer) toont een lijst van toetsenborden -waaruit de gebruiker het model kan kiezen dat overeenkomt met zijn toetsenbord. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>hw-detect</term><listitem><para> - -Detecteert automatisch de meeste hardware in het systeem, inclusief -netwerkkaarten, harde schijven en PCMCIA. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>cdrom-detect</term><listitem><para> - -Zoekt naar en koppelt een &debian; installatie-CD. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>netcfg</term><listitem><para> - -Configureert de netwerkverbindingen van de computer zodat deze verbinding kan maken -met het Internet. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>iso-scan</term><listitem><para> - -Zoekt op harde schijven naar ISO-images (<filename>.iso</filename> bestanden). - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>choose-mirror</term><listitem><para> - -Deze module toont een overzicht van spiegelservers met het &debian; Archief. -De gebruiker kan hiermee de bron voor de installatie van &debian; pakketten kiezen. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>cdrom-checker</term><listitem><para> - -Controleert de integriteit van een CD. Op die manier kan een gebruiker -zich ervan verzekeren dat de installatie-CD niet beschadigd is. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>lowmem</term><listitem><para> - -De module 'lowmem' probeert te signaleren wanneer een systeem slechts over -beperkt intern geheugen beschikt en doet vervolgens verschillende trucs om -niet strict noodzakelijke onderdelen van &d-i; te verwijderen (ten koste van -enige functionaliteit). - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>anna</term><listitem><para> - -Het acroniem 'anna' staat voor "Anna's Not Nearly APT". Deze module installeert -pakketten die zijn opgehaald vanaf de gekozen mirror of CD. -<!-- FJP Niet alle pakketten; alleen het installatiesysteem? //--> - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>user-setup</term><listitem><para> - -Stelt het wachtwoord voor het <quote>root</quote> account in en voegt een -account voor een normale gebruiker toe. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>clock-setup</term><listitem><para> - -Stelt de interne systeem clock in en bepaalt of de deze is ingesteld op -UTC of niet. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>tzsetup</term><listitem><para> - -Selecteert de tijdzone op basis van de eerder geselecteerde locatie. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>partman</term><listitem><para> - -De module 'partman' (partitie-manager) stelt de gebruiker in staat om -harde schijven die met het systeem verbonden zijn, in te delen, bestandssystemen -te creëren op geselecteerde partities en deze aan te sluiten op koppelpunten. -Daarnaast kent 'partman' interessante functies als het volledig geautomatiseerd -indelen van een harde schijf en ondersteuning van LVM. Voor &debian; geniet 'partman' -de voorkeur als hulpmiddel voor het indelen van harde schijven. -<!-- FJP Ook op andere media dan harde schijven (b.v. USB memory sticks)? //--> - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>partitioner</term><listitem><para> - -Maakt het mogelijk om harde schijven in te delen die zijn aangesloten op het -systeem. Er wordt een schijfindelingsprogramma gekozen dat past bij het platform -waartoe uw computer behoort. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>partconf</term><listitem><para> - -Toont een overzicht van partities en creëert bestandssystemen op de -geselecteerde partities volgens de instructies van de gebruiker. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>lvmcfg</term><listitem><para> - -Helpt de gebruiker met het configureren van de <firstterm>LVM</firstterm> -('Logical Volume Manager'). - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>mdcfg</term><listitem><para> - -Stelt de gebruiker in staat om een Software <firstterm>RAID</firstterm> -('Redundant Array of Inexpensive Disks') te configureren. Een softwarematige RAID -is veelal beter dan de goedkope (semi-hardwarematige) IDE-stuurapparaten voor RAID -die op sommige nieuwere moederborden voorkomen. -<!-- FJP: Origineel: superb is volgens mij niet juist in deze context //--> - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>base-installer</term><listitem><para> - -Installeert een basisset van pakketten die het mogelijk maken om de -computer, nadat deze is herstart, onder &debian-gnu; te laten functioneren. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>apt-setup</term><listitem><para> - -Verzorgt de configuratie van apt. Dit gebeurt grotendeels automatisch op -basis van de gebruikte installatiemethode. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>pkgsel</term><listitem><para> - -Maakt gebruik van <classname>tasksel</classname> voor de selecte en -installatie van aanvullende programmatuur. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>os-prober</term><listitem><para> - -Zoekt naar reeds op de computer aanwezige besturingssystemen en geeft -deze informatie door aan de module 'bootloader-installer'. Afhankelijk -van de gebruikte opstartlader, kan deze de gevonden besturingssystemen -vervolgens toevoegen aan het menu van de opstartlader. Op deze manier -kan de gebruiker tijdens het opstarten van de computer op een eenvoudige -manier kiezen welk besturingssysteem moet worden gestart. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>bootloader-installer</term><listitem><para> - -Installeert een opstartlader (boot loader) programma op de harde schijf. Dit -is noodzakelijk om de computer onder &arch-kernel; te laten opstarten zonder een -diskette of CD te gebruiken. Veel opstartladers kennen de mogelijkheid om -de gebruiker — elke keer dat de computer wordt opgestart — te -laten kiezen uit verschillende besturingssystemen. -De installatieprogramma's voor de diverse opstartladers installeren alle een -opstartlader op de harde schijf. Een opstartlader is noodzakelijk om de -computer onder Linux te laten opstarten zonder een diskette of CD te gebruiken. -Veel opstartladers kennen de mogelijkheid om de gebruiker — elke keer -dat de computer wordt opgestart — te laten kiezen uit alternatieve -besturingssystemen. - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>shell</term><listitem><para> - -Stelt de gebruiker in staat vanuit het menu of in de tweede console -een shell te starten. -<!-- FJP Vertaling 'shell'? Zie ook 'what-is-linux.xml' //--> -<!-- FJP Welke shell is beschikbaar? //--> - -</para></listitem> -</varlistentry> -<varlistentry> - -<term>save-logs</term><listitem><para> - -Stelt de gebruiker in staat om, wanneer problemen worden tegengekomen, -informatie op een diskette, via het netwerk, op harde schijf of op een -ander medium te bewaren. -Hiermee kan later een nauwkeurig verslag van problemen met het -installatiesysteem worden gestuurd aan de &debian; ontwikkelaars. - -</para></listitem> -</varlistentry> - -</variablelist> - - </sect1> - -&using-d-i-components.xml; -&loading-firmware.xml; - -</chapter> diff --git a/nl/welcome/about-copyright.xml b/nl/welcome/about-copyright.xml deleted file mode 100644 index b13e153dc..000000000 --- a/nl/welcome/about-copyright.xml +++ /dev/null @@ -1,96 +0,0 @@ -<!-- original version: 56422 --> - - <sect1> -<!--FJP -<title>About Copyrights and Software Licenses - </title>//--> -<title>Over auteursrechten en softwarelicenties</title> - -<para> - -We're sure that you've read some of the licenses that come with most -commercial software — they usually say that you can only use one -copy of the software on a single computer. This system's license isn't -like that at all. We encourage you to put a copy of &debian-gnu; on every -computer in your school or place of business. Lend your installation -media to your friends and help them install it on their computers! -You can even make thousands of copies and <emphasis>sell</emphasis> -them — albeit with a few restrictions. Your freedom to install -and use the system comes directly from &debian; being based on -<emphasis>free software</emphasis>. - -</para><para> - -Calling software <emphasis>free</emphasis> doesn't mean that the software isn't -copyrighted, and it doesn't mean that CDs containing that software -must be distributed at no charge. Free software, in part, means that -the licenses of individual programs do not require you to pay for the -privilege of distributing or using those programs. Free software also -means that not only may anyone extend, adapt, and modify the software, -but that they may distribute the results of their work as -well. - -<note> -<para> - -The Debian project, as a pragmatic concession to its users, -does make some packages available that do not meet our criteria for -being free. These packages are not part of the official distribution, -however, and are only available from the -<userinput>contrib</userinput> or <userinput>non-free</userinput> -areas of &debian; mirrors or on third-party CD-ROMs; see the -<ulink url="&url-debian-faq;">Debian FAQ</ulink>, under -<quote>The Debian FTP archives</quote>, for more information about the -layout and contents of the archives. - -</para> -</note> - -</para><para> - -Many of the programs in the system are licensed under the -<emphasis>GNU</emphasis> <emphasis>General Public License</emphasis>, -often simply referred to as <quote>the GPL</quote>. The GPL requires you to make -the <emphasis>source code</emphasis> of the programs available -whenever you distribute a binary copy of the program; that provision -of the license ensures that any user will be able to modify the -software. Because of this provision, the source code<footnote> - -<para> - -For information on how to locate, unpack, and build -binaries from &debian; source packages, see the -<ulink url="&url-debian-faq;">Debian FAQ</ulink>, -under <quote>Basics of the Debian Package Management System</quote>. - -</para> -</footnote> for all such programs is available in the &debian; system. - -</para><para> - -There are several other forms of copyright statements and software -licenses used on the programs in &debian;. You can find the copyrights -and licenses for every package installed on your system by looking in -the file -<filename>/usr/share/doc/<replaceable>package-name</replaceable>/copyright -</filename> -once you've installed a package on your system. - -</para><para> - -For more information about licenses and how &debian; determines whether -software is free enough to be included in the main distribution, see the -<ulink url="&url-dfsg;">Debian Free Software Guidelines</ulink>. - -</para><para> - -The most important legal notice is that this software comes with -<emphasis>no warranties</emphasis>. The programmers who have created this -software have done so for the benefit of the community. No guarantee -is made as to the suitability of the software for any given purpose. -However, since the software is free, you are empowered to modify that -software to suit your needs — and to enjoy the benefits of the -changes made by others who have extended the software in this way. - -</para> - </sect1> diff --git a/nl/welcome/doc-organization.xml b/nl/welcome/doc-organization.xml deleted file mode 100644 index 9baab8ec1..000000000 --- a/nl/welcome/doc-organization.xml +++ /dev/null @@ -1,117 +0,0 @@ -<!-- original version: 56322 --> - - <sect1 id="doc-organization"> - <title>Indeling van dit document</title> - -<para> - -Dit document is bedoeld als handleiding voor mensen die &debian; voor -het eerst gebruiken. Het probeert zo weinig mogelijk aannames te doen -over uw kennisniveau. We gaan er echter wel vanuit dat u een algemeen -beeld heeft van de werking van de hardware in uw computer. - -</para><para> - -Ook gevorderde gebruikers kunnen interessante referentie-informatie -vinden in dit document, waaronder de voor installatie minimaal benodigde -specificaties, details over hardware die door het installatiesysteem van -&debian; wordt ondersteund, en dergelijke. We moedigen gevorderde gebruikers -aan om heen en weer te bladeren in het document. - -</para><para> - -In het algemeen is deze handleiding lineair van opzet waardoor u van -begin tot einde door het installatieproces wordt geleid. Hieronder vindt -u de stappen voor de installatie van &debian-gnu;, en de secties van dit -document die met elke stap overeenkomen: - -<orderedlist> -<listitem><para> - -Bepaal of uw hardware voldoet aan de vereisten om het installatiesysteem -te kunnen gebruiken; zie <xref linkend="hardware-req"/>. - -</para></listitem> -<listitem><para> - -Maak een veiligheidskopie (backup) van uw systeem, zorg indien nodig voor -een plan van aanpak en voor de configuratie van hardware voorafgaand aan -de installatie van &debian;; zie <xref linkend="preparing"/>. Als u een -multi-boot systeem voorbereidt, kan het zijn dat u ruimte op uw harde schijf -moet creëren die kan worden gepartitioneerd voor gebruik door &debian;. - -</para></listitem> -<listitem><para> - -In <xref linkend="install-methods"/> verkrijgt u de installatiebestanden -die noodzakelijk zijn voor de door u gekozen installatiemethode. - -</para></listitem> -<listitem><para> - -<xref linkend="boot-installer"/> beschrijft het opstarten van de computer -in het installatiesysteem. Dit hoofdstuk beschrijft ook stappen die genomen -kunnen worden als u hierbij problemen ondervindt. - -</para></listitem> -<listitem><para> - -Voer de eigenlijke installatie uit zoals beschreven in <xref linkend="d-i-intro"/>. -Dit omvat de taalkeuze, het configureren van stuurmodules voor randapparaten, -het configureren van uw netwerkverbinding, het partitioneren van uw harde -schijf, de installatie van een basissysteem en vervolgens de selectie en -installatie van taken. Als u niet vanaf een CD installeert, wordt de -netwerkverbinding gebruikt om andere benodigde installatiebestanden direct -vanaf een &debian; server te downloaden. (Enige achtergrondinformatie over het -opzetten van de partities voor uw &debian; systeem is te vinden in -<xref linkend="partitioning"/>.) - -</para></listitem> -<listitem><para> - -Start de computer opnieuw op in uw zojuist geïnstalleerde basissysteem -met behulp van <xref linkend="boot-new"/>. - -</para></listitem> -</orderedlist> - -</para><para> - -Wanneer u de installatie van uw systeem heeft voltooid, kunt u -<xref linkend="post-install"/> lezen. Dat hoofdstuk legt uit waar u -aanvullende informatie over Unix en &debian; kunt vinden en hoe u uw kernel -kunt vervangen. - -<!-- XXX FIXME: Als u uw eigen installatiesysteem wilt maken op basis van -de broncode, moet u zeker <xref linkend="boot-floppy-techinfo"/> lezen. --> - -</para><para> - -Tot slot kunt u informatie over dit document en over hoe u hieraan kunt -bijdragen vinden in <xref linkend="administrivia"/>. - -</para> - </sect1> - - <sect1 condition="FIXME"> - <title>Uw hulp bij het opstellen van documentatie is welkom</title> - -<para> - -Alle hulp, suggesties en (vooral) patches worden bijzonder gewaardeerd. -Ontwikkelversies van dit document zijn beschikbaar op -<ulink url="&url-d-i-alioth-manual;"/>. Daar vindt u een overzicht van de -verschillende platformen en talen waarvoor dit document beschikbaar is. - -</para><para> - -Ook de bronbestanden zijn vrij beschikbaar; zie <xref linkend="administrivia"/> -voor nader informatie over hoe u een bijdrage kunt leveren. -Suggesties, commentaar, patches en probleemrapporten worden verwelkomd -(gebruik het pakket <classname>installation-guide</classname> voor -probleemrapporten, maar controleer eerst of het probleem niet reeds -gerapporteerd is). -<!--FJP De voorgaande twee para's lijken te overlappen //--> - -</para> - </sect1> diff --git a/nl/welcome/getting-newest-doc.xml b/nl/welcome/getting-newest-doc.xml deleted file mode 100644 index c1252d864..000000000 --- a/nl/welcome/getting-newest-doc.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- original version: 28672 --> - - <sect1 id="getting-newest-doc"> - <title>De meest recente versie van dit document verkrijgen</title> - -<para> - -Dit document wordt voortdurend gereviseerd. Wij adviseren om de -<ulink url="&url-release-area;">Debian &release; webpagina's</ulink> -te raadplegen voor de meest recente informatie over de &release; versie -van het &debian-gnu; systeem. Bijgewerkte versies van deze installatie -handleiding zijn ook beschikbaar op de officiële -<ulink url="&url-install-manual;">Installatiehandleiding webpagina's</ulink>. - -</para> - - </sect1> diff --git a/nl/welcome/getting-newest-inst.xml b/nl/welcome/getting-newest-inst.xml deleted file mode 100644 index e81217be6..000000000 --- a/nl/welcome/getting-newest-inst.xml +++ /dev/null @@ -1,23 +0,0 @@ -<!-- original version: 28672 --> - - <sect1 id="getting-newest-inst"> - <title>&debian; verkrijgen</title> - -<para> - -Voor informatie over hoe u &debian-gnu; kunt downloaden vanaf het Internet -of waar officiële &debian; CDs gekocht kunnen worden, verwijzen wij u naar de -<ulink url="&url-debian-distrib;">distributie webpagina</ulink>. -Op de <ulink url="&url-debian-mirrors;">lijst van Debian-mirrors</ulink> -vindt u het complete overzicht van officiële &debian;-mirrors, zodat u -eenvoudig de dichtstbijzijnde kunt vinden. - -</para><para> - -Na de installatie kan &debian; eenvoudig worden opgewaardeerd. De -installatieprocedure helpt u het systeem zodanig in te richten dat u, -indien nodig, kunt opwaarderen zodra de installatie is voltooid. - -</para> - - </sect1> diff --git a/nl/welcome/welcome.xml b/nl/welcome/welcome.xml deleted file mode 100644 index 07d8232af..000000000 --- a/nl/welcome/welcome.xml +++ /dev/null @@ -1,25 +0,0 @@ -<!-- original version: 28672 --> - -<chapter id="welcome"><title>Welkom bij &debian;</title> -<para> - -Dit hoofdstuk biedt een overzicht over het &debian; Project en -&debian-gnu;. Als u reeds bekend bent met de geschiedenis van het -&debian; Project en van de &debian-gnu; distributie kunt u dit -hoofdstuk desgewenst overslaan. - -</para> - -&what-is-debian.xml; -&what-is-linux.xml; -&what-is-debian-linux.xml; -&what-is-debian-kfreebsd.xml; -&what-is-debian-hurd.xml; -&getting-newest-inst.xml; -&getting-newest-doc.xml; -&doc-organization.xml; -&about-copyright.xml; - -<!-- FJP Volgens mij zouden doc-org en getting-newest-doc omgedraaid moeten worden //--> - -</chapter> diff --git a/nl/welcome/what-is-debian-hurd.xml b/nl/welcome/what-is-debian-hurd.xml deleted file mode 100644 index 7f1f3a3ef..000000000 --- a/nl/welcome/what-is-debian-hurd.xml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- original version: 28672 --> - -<!-- conditionalised because the hurd port is not yet an official debian -release --> - <sect1 id="what-is-debian-hurd" condition="unofficial-build"> - <title>Wat is &debian; GNU/Hurd?</title> - -<para> - -&debian; GNU/Hurd is een &debian; GNU systeem waarbij de monolitische Linux -kernel wordt vervangen door de GNU Hurd — een verzameling servers -die bovenop de GNU Mach microkernel draaien. Hurd is nog niet voltooid en -is niet geschikt voor dagelijks gekruik, maar er is voortgang. Hurd wordt -op dit moment alleen ontwikkeld voor het i386 platform; zodra het systeem -stabieler wordt, zal het ook geschikt worden gemaakt voor andere platformen. - -</para><para> - -Voor meer informatie verwijzen wij naar de -<ulink url="http://www.debian.org/ports/hurd/"> -Debian GNU/Hurd webpagina</ulink> -en de <email>debian-hurd@lists.debian.org</email> mailinglijst. - -</para> - - </sect1> diff --git a/nl/welcome/what-is-debian-kfreebsd.xml b/nl/welcome/what-is-debian-kfreebsd.xml deleted file mode 100644 index 82ab120e9..000000000 --- a/nl/welcome/what-is-debian-kfreebsd.xml +++ /dev/null @@ -1,26 +0,0 @@ -<!-- original version: 64660 untranslated --> - - <sect1 id="what-is-debian-kfreebsd"> - <title>What is &debian; GNU/kFreeBSD?</title> - -<para> - -&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel. - -This port of &debian; is currently only being developed for the i386 and amd64 -architectures, although ports to other architectures is possible. - -Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some -information on Linux system may not apply to it. - -</para><para> - -For more information, see the -<ulink url="http://www.debian.org/ports/kfreebsd-gnu/"> -Debian GNU/kFreeBSD ports page</ulink> -and the <email>debian-bsd@lists.debian.org</email> -mailing list. - -</para> - - </sect1> diff --git a/nl/welcome/what-is-debian-linux.xml b/nl/welcome/what-is-debian-linux.xml deleted file mode 100644 index 8e78bd0bb..000000000 --- a/nl/welcome/what-is-debian-linux.xml +++ /dev/null @@ -1,86 +0,0 @@ -<!-- original version: 25496 --> - - <sect1 id="what-is-debian-linux"> - <title>Wat is &debian; GNU/Linux?</title> - -<para> - -De combinatie van de filosofie en methodologie van &debian; met de hulpprogramma's -van GNU, de Linux kernel en andere belangrijke vrije software, vormt een -unieke softwaredistributie die &debian; GNU/Linux wordt genoemd. Deze -distributie is opgebouwd uit een groot aantal <emphasis>pakketten</emphasis>. -Elk pakket in de distributie bevat uitvoerbare programma's, scripts, -documentatie en configuratie-informatie. Ook heeft elk pakket een -<emphasis>pakketbeheerder</emphasis> die de eerstverantwoordelijke is om het -pakket up-to-date te houden, probleemrapporten (bug reports) op te volgen -en te communiceren met de 'upstream' ontwikkelaar(s) van de software in het -pakket. Onze extreem grote gebruikersgroep, tezamen met ons volgsysteem voor -probleemrapporten verzekert dat problemen snel worden gevonden en hersteld. - -</para><para> - -&debian;'s aandacht voor detail staat ons toe om een distributie -samen te stellen die van hoge kwaliteit, stabiel en schaalbaar is. -Installaties kunnen eenvoudig worden geconfigureerd om vele rollen -te vervullen: van een uitgeklede firewall via een wetenschappelijk -werkstation tot een zware netwerkserver. - -</para><para> - -&debian; is in het bijzonder populair bij gevorderde gebruikers vanwege -haar techinische kwaliteit en haar sterke betrokkenheid bij de behoeften -en verwachtingen van de Linux gemeenschap. &debian; heeft veel nieuwe -functionaliteit in Linux geïntroduceerd die nu gemeengoed is. - -</para><para> - -Zo was &debian; de eerste Linux distributie die een systeem voor -pakketbeheer bevatte met als doel eenvoudige installatie en verwijdering -van software. &debian; was ook de eerste Linux distributie die kon worden -opgewaardeerd zonder dat een geheel nieuwe installatie nodig was. - -</para><para> - -&debian; is nog altijd vooraanstaand in de ontwikkeling van Linux. Het -ontwikkelproces van &debian; is een voorbeeld van hoe goed het Open -Source ontwikkelmodel kan werken — zelfs voor zeer complexe -taken als het opbouwen en beheren van een compleet besturingssysteem. - -</para><para> - -De eigenschap die &debian; het meest onderscheidt van andere Linux -distributies is het systeem voor pakketbeheer. Deze hulpmiddelen geven -de beheerder van een &debian; systeem volledige controle over de pakketten -die op dat systeem geïnstalleerd zijn, waaronder het vermogen om een -individueel pakket te installeren of automatisch het volledige -besturingssysteem op te waarderen. Ook is het mogelijk individuele -pakketten uit te sluiten van opwaardering. U kunt zelfs software die -u zelf heeft gecompileerd bekend maken bij het systeem voor pakketbeheer -en opgeven aan welke afhankelijkheden daarmee wordt voldaan. - -</para><para> - -Om uw systeem te beschermen tegen <quote>Trojaanse paarden</quote> en -andere kwaadaardige software, controleren de servers van &debian; of een nieuw(e) -(versie van een) pakket wel afkomstig is van zijn geregistreerde &debian; -ontwikkelaar. Ook besteden de samenstellers van &debian; pakketten veel zorg -aan het veilig configureren van hun pakketten. Als in uitgegeven pakketten -beveiligingsproblemen naar voren komen, is een verbeterde versie meestal -zeer snel beschikbaar. Door de eenvoudige wijze waarop pakketten kunnen worden -bijgewerkt, kunnen beveiligingsupdates automatisch via Internet gedownload en -geïnstalleerd worden. - -</para><para> - -De voornaamste (en beste) methode om ondersteuning te krijgen voor uw -&debian; GNU/Linux systeem en om te communiceren met &debian; ontwikkelaars, is -via de vele mailinglijsten die door het &debian; Project worden beheerd -(op dit moment meer dan &num-of-debian-maillists;). De meest eenvoudige -manier om u aan te melden voor één of meerdere van deze mailinglijsten -is door gebruik te maken van het <ulink url="&url-debian-lists-subscribe;"> -aanmeldingsformulier</ulink> op onze website. -<!--FJP Aanvulling origineel: waarschuwing high trafic lists? //--> - -</para> - - </sect1> diff --git a/nl/welcome/what-is-debian.xml b/nl/welcome/what-is-debian.xml deleted file mode 100644 index ed0c14b26..000000000 --- a/nl/welcome/what-is-debian.xml +++ /dev/null @@ -1,116 +0,0 @@ -<!-- original version: 45347 --> - - <sect1 id="what-is-debian"> - <title>Wat is Debian?</title> -<para> -<!-- FJP Debian (D|d)evelopers door elkaar gebruikt; gekozen voor klein //--> - -Debian is een organisatie van uitsluitend vrijwilligers die toegewijd -is aan het ontwikkelen van vrije software en het bevorderen van -de idealen van de vrije software gemeenschap. -Het Debian Project is gestart in 1993 toen Ian Murdock een open uitnodiging -deed aan software ontwikkelaars om bij te dragen aan een complete en -samenhangende softwaredistributie, gebaseerd op de toen nog relatief nieuwe -Linux kernel. Die relatief kleine groep van toegewijde enthousiastelingen, -oorspronkelijk gefinancierd door de -<ulink url="&url-fsf;">Free Software Foundation</ulink>, is, onder -invloed van de filosofie van <ulink url="&url-gnu-intro;">GNU</ulink>, over de -jaren uitgegroeid tot een organisatie van rond de &num-of-debian-developers; -<firstterm>Debian ontwikkelaars</firstterm>. -<!-- FJP 800 vervangen door &num-of-debian-developers; //--> - -</para><para> - -Debian ontwikkelaars zijn betrokken bij een scala aan activiteiten, waaronder -het beheer van <ulink url="&url-debian-home;">Websites</ulink> -en <ulink url="&url-debian-ftp;">FTP-sites</ulink>, -grafisch ontwerp, juridische analyse van softwarelicenties, het schrijven van -documentatie en, natuurlijk, het onderhouden van softwarepakketten. - -</para><para> - -In het belang van het overbrengen van onze filosofie en het aantrekken van -ontwikkelaars die geloven in de principes waar Debian voor staat, heeft -het Debian Project een aantal documenten gepubliceerd die onze waarden -uiteenzetten en als gids dienen voor wat het betekent om een Debian -Ontwikkelaar te zijn: - -<itemizedlist> -<listitem><para> - -Het <ulink url="&url-social-contract;">Debian Sociaal Contract</ulink> is -een verklaring van de verbintenis van Debian met de Vrije Software Gemeenschap. -Eenieder die ermee instemt het Sociaal Contract na te leven, kan een -<ulink url="&url-new-maintainer;">ontwikkelaar</ulink> worden. -Elke Debian ontwikkelaar kan nieuwe software in Debian introduceren — -onder voorwaarde dat de software voldoet aan onze criteria om 'vrij' te zijn -en het pakket aan onze kwaliteitsstandaarden voldoet. -<!-- FJP In origineel maintainer vervangen door Debian developer; begrip -maintainer wordt pas in what-is-debian-linux geïntroduceerd. //--> - -</para></listitem> -<listitem><para> - -De <ulink url="&url-dfsg;">Debian Richtlijn voor Vrije Software</ulink><footnote> - -<para> -Engels: Debian Free Software Guidelines (DFSG) -</para> - -</footnote> zijn een heldere en beknopte verklaring van de voorwaarden -van Debian voor vrije software. De Richtlijn is een zeer invloedrijk -document in de Vrije Software Beweging en was de fundering van -<ulink url="&url-osd;">The Open Source Definition</ulink>. -<!-- FJP foutje in en: the The Open Source Definition //--> - -</para></listitem> -<listitem><para> - -De <ulink url="&url-debian-policy;">Debian Policy Manual</ulink> is een -uitgebreide specificatie van de kwaliteitsstandaarden van het Debian Project. - -</para></listitem> -</itemizedlist> -</para><para> - -Debian ontwikkelaars zijn ook betrokken bij een groot aantal andere -projecten; sommige Debian-specifiek, andere waarbij een deel of de -gehele Linux gemeenschap betrokken is. Enkele voorbeelden zijn: - -<itemizedlist> -<listitem><para> - -De <ulink url="&url-lsb-org;">Linux Standard Base</ulink> (LSB) is een -project dat zich richt op de standaardisatie van het basis GNU/Linux systeem -dat externe software en hardware ontwikkelaars in staat stelt om eenvoudig -programma's en besturingsprogramma's voor apparatuur te ontwikkelen voor Linux -in het algemeen (in tegenstelling tot een specifieke GNU/Linux distributie). - -</para></listitem> -<listitem><para> - -De <ulink url="&url-fhs-home;">Filesystem Hierarchy Standard</ulink> (FHS) is -een poging om de indeling van het Linux bestandssysteem te standaardiseren. -De FHS zal softwareontwikkelaars in staat stellen om zich te concentreren op -het ontwerpen van programma's, zonder dat zij zich zorgen hoeven te maken over -hoe het pakket geïnstalleerd zal worden in verschillende GNU/Linux distributies. - -</para></listitem> -<listitem><para> - -<ulink url="&url-debian-jr;">Debian Jr.</ulink> is een eigen project dat -tot doel heeft zeker te stellen dat Debian ook onze jongste gebruikers iets -te bieden heeft. -<!-- FJP Ook skolinux vermelden? //--> - -</para></listitem> -</itemizedlist> - -</para><para> - -Voor meer algemene informatie over Debian verwijzen wij u naar de -<ulink url="&url-debian-faq;">Debian FAQ</ulink> (veelgestelde vragen). - -</para> - - </sect1> diff --git a/nl/welcome/what-is-linux.xml b/nl/welcome/what-is-linux.xml deleted file mode 100644 index a6e444050..000000000 --- a/nl/welcome/what-is-linux.xml +++ /dev/null @@ -1,98 +0,0 @@ -<!-- original version: 45186 --> - - <sect1 id="what-is-linux"> - <title>Wat is GNU/Linux?</title> -<para> -<!--FJP In oorspr. tekst 'unix' en 'Unix' door elkaar gebruikt//--> - -GNU/Linux is een besturingssysteem: een serie programma's die interactie -met uw computer en het uitvoeren van andere programma's mogelijk maken. -<!-- FJP Linux vervangen door GNU/Linux //--> - -</para><para> - -Een besturingssysteem bestaat uit diverse fundamentele programma's die -uw computer nodig heeft om te communiceren met en instructies te ontvangen -van gebruikers; gegevens van/naar harde schijven, magneetbanden en printers -te lezen en schrijven; het gebruik van geheugen te sturen; en andere -software te draaien. Het meest belangrijke onderdeel van een besturingssysteem -is de kernel. In een GNU/Linux systeem is Linux de kernelcomponent. De rest -van het systeem bestaat uit andere programma's, waarvan er veel geschreven zijn -door of voor het GNU Project. Omdat de Linux kernel op zichzelf geen werkend -besturingssysteem is, geven we de voorkeur aan het begrip <quote>GNU/Linux</quote> -om te verwijzen naar systemen die door velen voor het gemak met <quote>Linux</quote> -worden aangeduid. - -</para><para> - -Linux is gemodelleerd op het besturingssysteem Unix. Linux is vanaf het -begin ontworpen om een 'multi-tasking', 'multi-user' systeem te zijn. -Alleen deze feiten al zijn voldoende om Linux anders te laten zijn dan -andere bekende besturingssystemen. -Echter, Linux is zelfs meer fundamenteel anders dan u misschien denkt. -In tegenstelling tot andere besturingssystemen is niemand eigenaar van -Linux. Veel van de ontwikkeling ervan wordt gedaan door onbetaalde -vrijwilligers. - -</para><para> - -De ontwikkeling van wat later GNU/Linux zou worden, begon in 1984 toen de -<ulink url="&url-fsf;">Free Software Foundation</ulink> startte met -de ontwikkeling van een vrij Unix-achtig besturingssysteem, GNU genaamd. - -</para><para> - -Het <ulink url="&url-gnu;">GNU project</ulink> heeft een uitgebreide set -van vrije hulpprogramma's -ontwikkeld voor gebruik onder Unix™ en Unix-achtige besturingssystemen -zoals Linux. Deze hulpprogramma's stellen gebruikers in staat om taken uit te -voeren, variërend van alledaags (zoals het kopiëren of verwijderen van bestanden -van het systeem) tot specifiek (zoals het schrijven en compileren van -programmatuur of het uitgekiend wijzigen van een groot aantal verschillende -soorten documenten). - -</para><para> - -Hoewel vele groepen en individuen hebben bijgedragen aan Linux, heeft -de Free Software Foundation nog altijd de grootste bijdrage geleverd. -Zij heeft niet alleen de meeste hulpprogramma's tot stand gebracht, maar -ook de filosofie en de gemeenschapszin die Linux mogelijk hebben gemaakt. - -</para><para> - -De <ulink url="&url-kernel-org;">Linux kernel</ulink> verscheen -voor het eerst in 1991 toen Linus Torvalds, een Finse student Infromatica, -op de Usenet nieuwsgroep <userinput>comp.os.minix</userinput> een vroege versie -van een vervanger voor de Minix kernel aankondigde. - -</para><para> - -Linus Torvalds coördineert, met de hulp van enkele vertrouwelingen, -nog altijd het werk van honderden ontwikkelaars. -<ulink url="&url-kernel-traffic;">Kernel Traffic</ulink> -is een uitstekende wekelijkse samenvatting van discussies op de -<userinput>linux-kernel</userinput> mailinglijst. Nadere informatie over -de <userinput>linux-kernel</userinput> mailinglijst kan worden gevonden in de -<ulink url="&url-linux-kernel-list-faq;">linux-kernel mailinglijst FAQ</ulink>. - -</para><para> - -Gebruikers van Linux hebben een ongekende keuzevrijheid in hun software. -Zij kunnen bijvoorbeeld kiezen uit een twaalftal verschillende 'command -line shells' en diverse grafische werkbladen. Deze selectie werkt vaak -verwarrend voor gebruikers van andere besturingsystemen die niet gewend -zijn om de opdrachtregel of hun werkblad te zien als iets dat ze kunnen -veranderen. -<!--FJP Nog vertaling zoeken voor 'command line shells' //--> - -</para><para> - -Linux is ook minder storingsgevoelig, beter in staat om meerdere programma's -tegelijkertijd uit te voeren en veiliger dan veel andere besturingssystemen. -Met deze voordelen is Linux het snelst groeiende besturingssysteem in de -markt voor servers. Meer recent is Linux ook populair aan het worden bij -particuliere en zakelijke gebruikers. - -</para> - - </sect1> diff --git a/po/nl/preface.po b/po/nl/preface.po new file mode 100644 index 000000000..0ceb41cd1 --- /dev/null +++ b/po/nl/preface.po @@ -0,0 +1,73 @@ +# Dutch translation of the Debian Installation Guide. +# Copyright (C) 2004-2006, 2012 The Debian Project. +# This file is distributed under the same license as the Debian Installation Guide. +# Frans Pop <elendil@planet.nl>, 2004-2006. +# Jeroen Schot <schot@a-eskwadraat.nl>, 2012. +# +msgid "" +msgstr "" +"Project-Id-Version: d-i-manual/preface\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2012-06-16 09:12+0000\n" +"PO-Revision-Date: 2012-08-29 17:05+0200\n" +"Last-Translator: Jeroen Schot <schot@a-eskwadraat.nl>\n" +"Language-Team: Debian l10n Dutch <debian-l10n-dutch@lists.debian.org>\n" +"Language: nl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: preface.xml:5 +#, no-c-format +msgid "Installing &debian-gnu; &release; For &architecture;" +msgstr "&debian-gnu; &release; installeren op &architecture;" + +#. Tag: para +#: preface.xml:6 +#, no-c-format +msgid "" +"We are delighted that you have decided to try &debian;, and are sure that " +"you will find that &debian;'s GNU/&arch-kernel; distribution is unique. " +"&debian-gnu; brings together high-quality free software from around the " +"world, integrating it into a coherent whole. We believe that you will find " +"that the result is truly more than the sum of the parts." +msgstr "" +"Wij zijn verheugd dat u heeft besloten om &debian; te proberen en weten " +"zeker dat u zult ontdekken dat de GNU/&arch-kernel; distributie van &debian; " +"uniekis. &debian-gnu; brengt vrije software van over de hele wereld samen en " +"integreert deze tot een samenhangend geheel. Wij zijn ervan overtuigd dat u " +"zult ontdekken dat het resultaat werkelijk meer is dan de som der delen." + +#. Tag: para +#: preface.xml:15 +#, no-c-format +msgid "" +"We understand that many of you want to install &debian; without reading this " +"manual, and the &debian; installer is designed to make this possible. If you " +"don't have time to read the whole Installation Guide right now, we recommend " +"that you read the Installation Howto, which will walk you through the basic " +"installation process, and links to the manual for more advanced topics or " +"for when things go wrong. The Installation Howto can be found in <xref " +"linkend=\"installation-howto\"/>." +msgstr "" +"Wij begrijpen dat velen onder u &debian; zal willen installeren zonder deze " +"handleiding te lezen en het &debian; installatiesysteem is ontworpen om dit " +"mogelijk te maken. Als u op dit moment geen gelegenheid heeft om de gehele " +"installatiehandleiding door te nemen, adviseren wij om tenminste de " +"\"Installatie Howto\" te lezen, die u meeneemt door het basis installatie " +"proces en verwijzingen bevat naar de handleiding voor meer geavanceerde " +"onderwerpen of als er dingen fout gaan. U vindt de Installatie Howto in " +"<xref linkend=\"installation-howto\"/>." + +#. Tag: para +#: preface.xml:25 +#, no-c-format +msgid "" +"With that said, we hope that you have the time to read most of this manual, " +"and doing so will lead to a more informed and likely more successful " +"installation experience." +msgstr "" +"Dat gezegd hebbend, hopen wij dat u de tijd wilt nemen om het merendeel van " +"deze handleiding door te lezen en dat dit zal leiden tot een beter " +"geïnformeerde en waarschijnlijk meer succesvolle installatie." |