diff options
| author | Joey Hess <joeyh@debian.org> | 2005-10-07 19:51:38 +0000 |
|---|---|---|
| committer | Joey Hess <joeyh@debian.org> | 2005-10-07 19:51:38 +0000 |
| commit | 1ea73eea5ecc6a8ed901316049259aee737ee554 (patch) | |
| tree | 03a077f0b1b1548f3c806bd1c5795964fba0fb52 /nl | |
| download | installation-guide-1ea73eea5ecc6a8ed901316049259aee737ee554.zip | |
move manual to top-level directory, split out of debian-installer package
Diffstat (limited to 'nl')
164 files changed, 17837 insertions, 0 deletions
diff --git a/nl/administrivia/administrivia.xml b/nl/administrivia/administrivia.xml new file mode 100644 index 000000000..611b58af0 --- /dev/null +++ b/nl/administrivia/administrivia.xml @@ -0,0 +1,155 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29689 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> + +Translators can uncomment this paragraph and add an acknowledgement +to 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>". + +(Note: support for this for translations using PO files will be added + soon.) +--> + +</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>debian-installer-manual</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;debian-installer-manual">open bugs against +debian-installer-manual</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="i386"> + +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 new file mode 100644 index 000000000..cdd173363 --- /dev/null +++ b/nl/appendix/chroot-install.xml @@ -0,0 +1,458 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 31190 untranslated --> + + <sect1 id="linux-upgrade"> + <title>Installing &debian; from a Unix/Linux System</title> + +<para> + +This section explains how to install &debian; 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; from +Red Hat, Mandrake, 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; +install. It's also a clever way for dealing with hardware that +otherwise doesn't play friendly with various boot or installation +media. + +</para> + + <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 at least 150MB of space available for a console only install, +or at least 300MB if you plan to install X. + +</para><para> + +To create file systems on your 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/hda6 +</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/hda5 +# sync; sync; sync +# swapon /dev/hda5 +</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/hda6 /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 tool that the Debian installer uses, which is 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>. 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><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 +binary files from it. You will need to have root privileges to install +the binaries. + +<informalexample><screen> +# ar -x debootstrap_0.X.X_arch.deb +# cd / +# zcat /full-path-to-work/work/data.tar.gz | tar xv +</screen></informalexample> + +</para><para> + +Note that running <command>debootstrap</command> may require you to have +a minimal version of <classname>glibc</classname> installed (currently +GLIBC_2.3). <command>debootstrap</command> itself is a shell script, but +it calls various utilities that require <classname>glibc</classname>. + +</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>http.us.debian.org/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/misc/README.mirrors"></ulink>. + +</para><para> + +If you have a &releasename; &debian; 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>arm</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://http.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= chroot /mnt/debinst /bin/bash +</screen></informalexample> + +</para> + + <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 /mnt/floppy auto noauto,rw,sync,user,exec 0 0 +/dev/cdrom /mnt/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> + +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>Configure Keyboard</title> +<para> + +To configure your keyboard: + +<informalexample><screen> +# dpkg-reconfigure console-data +</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> + + <sect3> + <title>Configure Networking</title> +<para> + +To configure networking, edit +<filename>/etc/network/interfaces</filename>, +<filename>/etc/resolv.conf</filename>, and +<filename>/etc/hostname</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 <filename>/etc/resolv.conf</filename>: + +<informalexample><screen> +search hqdom.local\000 +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> + +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 Timezone, Users, and APT</title> +<para> + +Set your timezone, add a normal user, and choose your <command>apt</command> +sources by running + +<informalexample><screen> +# /usr/sbin/base-config new +</screen></informalexample> + +</para> + </sect3> + + <sect3> + <title>Configure Locales</title> +<para> + +To configure your locale settings to use a language other than +English, install the locales support package and configure it: + +<informalexample><screen> +# apt-get install locales +# dpkg-reconfigure locales +</screen></informalexample> + +NOTE: Apt must be configured before, ie. during the base-config phase. +Before using locales with character sets other than ASCII or latin1, +please consult the appropriate localization HOWTO. + +</para> + </sect3> + </sect2> + + <sect2> + <title>Install a Kernel</title> +<para> + +If you intend to boot this system, you probably want a Linux kernel +and a boot loader. Identify available pre-packaged kernels with + +<informalexample><screen> +# apt-cache search kernel-image +</screen></informalexample> + +Then install your choice using its package name. + +<informalexample><screen> +# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable> +</screen></informalexample> + +</para> + </sect2> + + <sect2> +<title>Set up the Boot Loader</title> +<para> + +To make your &debian; system bootable, set up your boot loader to load +the installed kernel with your new root partition. Note that debootstrap +does not install a boot loader, though you can use apt-get inside your +Debian chroot to do so. + +</para><para arch="i386"> + +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 lilo (remember it will use +<filename>lilo.conf</filename> relative to the system you call it from). + +</para><para arch="i386"> + +Here is a basic <filename>/etc/lilo.conf</filename> as an example: + +<informalexample><screen> +boot=/dev/hda6 +root=/dev/hda6 +install=menu +delay=20 +lba32 +image=/vmlinuz +label=Debian +</screen></informalexample> + +</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> + </sect1> diff --git a/nl/appendix/example-preseed-etch.xml b/nl/appendix/example-preseed-etch.xml new file mode 100644 index 000000000..79d3e143f --- /dev/null +++ b/nl/appendix/example-preseed-etch.xml @@ -0,0 +1,372 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30373 untranslated --> + +<informalexample condition="etch"><screen> +#### Startup. + +# To use a preseed file, you'll first need to boot the installer, +# and tell it what preseed file to use. This is done by passing the +# kernel a boot parameter, either manually at boot or by editing the +# syslinux.cfg (or similar) file and adding the parameter to the end +# of the append line(s) for the kernel. +# +# If you're netbooting, use this: +# preseed/url=http://host/path/to/preseed +# If you're remastering a CD, you could use this: +# preseed/file=/cdrom/preseed +# If you're installing from USB media, use this, and put the preseed file +# in the toplevel directory of the USB stick. +# preseed/file=/hd-media/preseed +# +# If you feel comfortable modifying the installer's initrd image, +# you can also place a preseed file in the root directory of the initrd's +# filesystem, named "preseed.cfg" -- the installer will always use this +# file if it is present. Otherwise, be sure to copy this file to the location +# you specify. +# +# To make sure the installer gets the right preseed file, you can specify +# a checksum for the file. Currently this needs to be a md5sum, and if +# specified it must match the file or the installer will refuse to use the +# file. +# preseed/url/checksum=5da499872becccfeda2c4872f9171c3d +# preseed/file/checksum=5da499872becccfeda2c4872f9171c3d +# +# Some parts of the installation process cannot be automated using +# some forms of preseeding, because the questions are asked before +# the preseed file is loaded. For example, if the preseed file is +# downloaded over the network, the network setup must be done first. +# One reason to use initrd preseeding is that it allows preseeding +# of even these early steps of the installation process. +# +# If a preseed file cannot be used to preseed some steps, the install can +# still be fully automated, since you can pass preseed values to the kernel +# on the command line. Just pass path/to/var=value for any of the preseed +# variables listed below. +# +# While you're at it, you may want to throw a debconf/priority=critical in +# there, to avoid most questions even if the preseeding below misses some. +# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit +# enter to boot the installer. +# +# Note that the 2.4 kernel accepts a maximum of 8 command line options and +# 8 environment options (including any options added by default for the +# installer). If these numbers are exceeded, 2.4 kernels will drop any +# excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, +# you can use 32 command line options and 32 environment options. +# +# Some of the default options, like 'vga=normal' may be safely removed +# for most installations, which may allow you to add more options for +# preseeding. + +# To select your language and country, use this setting, but remember +# that this will only work for initrd based preseeding, for other forms of +# preseeding you must convert it into a kernel parameter, +# such as debian-installer/locale=en_US +d-i debian-installer/locale string en_US + +# To select your keyboard, use this setting. Again it will need to be +# passed as a kernel parameter for most preseed setups. +d-i console-keymaps-at/keymap select us + +#### Network configuration. + +# Of course, this won't work if you're loading your preseed file from the +# network! But it's great if you're booting from CD or USB stick. You can +# also pass network config parameters in on the kernel params if you are +# loading preseed files from the network. + +# 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 + +# 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, here's how: +#d-i netcfg/disable_dhcp boolean true +#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 + +# Note that 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 + +#### Mirror settings. + +d-i mirror/country string enter information manually +d-i mirror/http/hostname string http.us.debian.org +d-i mirror/http/directory string /debian +d-i mirror/http/proxy string + +# What suite of Debian to install. +#d-i mirror/suite string testing +# What suite of Debian to use for loading installer components. +# (Defaults to same as mirror/suite.) +#d-i mirror/udeb/suite string testing + +#### Partitioning. + +# If the system has free space you can choose to only partition that space. +#d-i partman-auto/init_automatically_partition \ +# select Use the largest continuous free space + +# Alternatively, you can specify a disk to partition. The device name can +# be given in either devfs or traditional non-devfs format. +# For example, to use the first disk devfs knows of: +d-i partman-auto/disk string /dev/discs/disc0/disc + +# You can choose from any of the predefined partitioning recipes: +d-i partman-auto/choose_recipe \ + select All files in one partition (recommended for new users) +#d-i partman-auto/choose_recipe select Desktop machine +#d-i partman-auto/choose_recipe select Multi-user workstation + +# Or provide a recipe of your own... +# The recipe format is documented in the file devel/partman-auto-recipe.txt. +# 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 the preseed 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{ } \ +# . + +# This makes partman automatically partition without confirmation. +d-i partman/confirm_write_new_label boolean true +d-i partman/choose_partition \ + select Finish partitioning and write changes to disk +d-i partman/confirm boolean true + +#### Boot loader installation. + +# Grub is the default boot loader (for x86). If you want lilo installed +# instead, uncomment this: +#d-i grub-installer/skip boolean true + +# 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 if finds some other OS +# too, 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/bootdev string (hd0,0) +#d-i grub-installer/only_debian boolean false +#d-i grub-installer/with_other_os boolean false + +#### Finishing up the first stage install. + +# Avoid that last message about the install being complete. +d-i prebaseconfig/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 + +#### Shell commands. + +# 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 +# preseed file like this one. Only use preseed 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 just before the install finishes, but when there is +# still a usable /target directory. +#d-i preseed/late_command string echo foo > /target/etc/bar + +# This command is run just as base-config is starting up. +#base-config base-config/early_command string echo hi mom + +# This command is run after base-config is done, just before the login: +# prompt. This is a good way to install a set of packages you want, or to +# tweak the configuration of the system. +#base-config base-config/late_command \ +# string apt-get install zsh; chsh -s /bin/zsh + +###### Preseeding the 2nd stage of the installation. + +#### Preseeding base-config. + +# Avoid the introductory message. +base-config base-config/intro note + +# Avoid the final message. +base-config base-config/login note + +# If you installed a display manager, but don't want to start it immediately +# after base-config finishes. +#base-config base-config/start-display-manager boolean false + +# Some versions of the installer can report back on what you've installed. +# 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 + +#### Clock and time zone setup. + +# 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 options. +d-i time/zone string US/Eastern + +#### Account setup. + +# To preseed the root password, you have to put it in the clear in this +# file. That is not a very good idea, use caution! +#passwd passwd/root-password password r00tme +#passwd passwd/root-password-again password r00tme + +# If you want to skip creation of a normal user account. +#passwd passwd/make-user boolean false + +# Alternatively, you can preseed the user's name and login. +#passwd passwd/user-fullname string Debian User +#passwd passwd/username string debian +# And their password, but use caution! +#passwd passwd/user-password password insecure +#passwd passwd/user-password-again password insecure + +#### Apt setup. + +# This question controls what source the second stage installation uses +# for packages. Choices are cdrom, http, ftp, filesystem, edit sources list +# by hand +base-config apt-setup/uri_type select http + +# If you choose ftp or http, you'll be asked for a country and a mirror. +base-config apt-setup/country select enter information manually +base-config apt-setup/hostname string http.us.debian.org +base-config apt-setup/directory string /debian +# Stop after choosing one mirror. +base-config apt-setup/another boolean false + +# You can choose to install non-free and contrib software. +#base-config apt-setup/non-free boolean true +#base-config apt-setup/contrib boolean true + +# Do enable security updates. +base-config apt-setup/security-updates boolean true + +#### Package selection. + +# You can choose to install any combination of tasks that are available. +# Available tasks as of this writing include: Desktop environment, +# Web server, Print server, DNS server, File server, Mail server, +# SQL database, Laptop, Standard system, manual package selection. The +# last of those will run aptitude. 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 Standard system task. +tasksel tasksel/first multiselect Desktop environment, Standard system +#tasksel tasksel/first multiselect Web server, Standard system + +#### Mailer configuration. + +# During a normal install, exim asks only a few questions. Here's how to +# avoid even those. More complicated preseeding is possible. +exim4-config exim4/dc_eximconfig_configtype \ + select no configuration at this time +exim4-config exim4/no_config boolean true +exim4-config exim4/no_config boolean true + +# It's a good idea to set this to whatever user account you choose to +# create. Leaving the value blank results in postmaster mail going to +# /var/mail/mail. +exim4-config exim4/dc_postmaster string + +#### X Configuration. + +# Preseeding Debian's X config is possible, but you probably need to know +# some details about the video hardware of the machine, since Debian's X +# configurator does not do fully automatic configuration of everything. + +# X can detect the right driver for some cards, but if you're preseeding, +# you override whatever it chooses. Still, vesa will work most places. +#xserver-xfree86 xserver-xfree86/config/device/driver select vesa + +# A caveat with mouse autodetection is that if it fails, X will retry it +# over and over. So if it's preseeded to be done, there is a possibility of +# an infinite loop if the mouse is not autodetected. +#xserver-xfree86 xserver-xfree86/autodetect_mouse boolean true + +# Monitor autodetection is recommended. +xserver-xfree86 xserver-xfree86/autodetect_monitor boolean true +# Uncomment if you have an LCD display. +#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true +# X has three configuration paths for the monitor. Here's how to preseed +# the "medium" path, which is always available. The "simple" path may not +# be available, and the "advanced" path asks too many questions. +xserver-xfree86 xserver-xfree86/config/monitor/selection-method \ + select medium +xserver-xfree86 xserver-xfree86/config/monitor/mode-list \ + select 1024x768 @ 60 Hz + +#### Everything else. + +# 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 + +# If you like, you can include other preseed files into this one. +# Any settings in those files will override pre-existing settings from this +# file. More that 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 preseed file that includes them. +#d-i preseed/include string x.cfg + +# The installer can optionally verify checksums of preseed 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 +# preseed files, includes those files. +#d-i preseed/include_command \ +# string echo if [ "`hostname`" = bob ]; then echo bob.cfg; fi + +# To check the format of your preseed file before performing an install, +# you can use debconf-set-selections: +# debconf-set-selections -c preseed.cfg +</screen></informalexample> diff --git a/nl/appendix/example-preseed-sarge.xml b/nl/appendix/example-preseed-sarge.xml new file mode 100644 index 000000000..3d79dda57 --- /dev/null +++ b/nl/appendix/example-preseed-sarge.xml @@ -0,0 +1,366 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30372 untranslated --> + +<informalexample condition="sarge"><screen> +#### Startup. + +# To use a preseed file, you'll first need to boot the installer, +# and tell it what preseed file to use. This is done by passing the +# kernel a boot parameter, either manually at boot or by editing the +# syslinux.cfg (or similar) file and adding the parameter to the end +# of the append line(s) for the kernel. +# +# If you're netbooting, use this: +# preseed/url=http://host/path/to/preseed +# If you're remastering a CD, you could use this: +# preseed/file=/cdrom/preseed +# If you're installing from USB media, use this, and put the preseed file +# in the toplevel directory of the USB stick. +# preseed/file=/hd-media/preseed +# Be sure to copy this file to the location you specify. +# +# Some parts of the installation process cannot be automated using +# some forms of preseeding, because the questions are asked before +# the preseed file is loaded. For example, if the preseed file is +# downloaded over the network, the network setup must be done first. +# One reason to use initrd preseeding is that it allows preseeding +# of even these early steps of the installation process. +# +# If a preseed file cannot be used to preseed some steps, the install can +# still be fully automated, since you can pass preseed values to the kernel +# on the command line. Just pass path/to/var=value for any of the preseed +# variables listed below. +# +# While you're at it, you may want to throw a debconf/priority=critical in +# there, to avoid most questions even if the preseeding below misses some. +# And you might set the timeout to 1 in syslinux.cfg to avoid needing to hit +# enter to boot the installer. +# +# Note that the kernel accepts a maximum of 8 command line options and +# 8 environment options (including any options added by default for the +# installer). If these numbers are exceeded, 2.4 kernels will drop any +# excess options and 2.6 kernels will panic. With kernel 2.6.9 or newer, +# you can use 32 command line options and 32 environment options. +# +# Some of the default options, like 'vga=normal' may be safely removed +# for most installations, which may allow you to add more options for +# preseeding. + +# It is not possible to use preseeding to set language, country, and +# keyboard. Instead you should use kernel parameters. Example: +# languagechooser/language-name=English +# countrychooser/shortlist=US +# console-keymaps-at/keymap=us + +#### Network configuration. + +# Of course, this won't work if you're loading your preseed file from the +# network! But it's great if you're booting from CD or USB stick. You can +# also pass network config parameters in on the kernel params if you are +# loading preseed files from the network. + +# 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 + +# 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, here's how: +#d-i netcfg/disable_dhcp boolean true +#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 + +# Note that 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 + +#### Mirror settings. + +d-i mirror/country string enter information manually +d-i mirror/http/hostname string http.us.debian.org +d-i mirror/http/directory string /debian +d-i mirror/suite string testing +d-i mirror/http/proxy string + +#### Partitioning. + +# If the system has free space you can choose to only partition that space. +#d-i partman-auto/init_automatically_partition \ +# select Use the largest continuous free space + +# Alternatively, you can specify a disk to partition. The device name can +# be given in either devfs or traditional non-devfs format. +# For example, to use the first disk devfs knows of: +d-i partman-auto/disk string /dev/discs/disc0/disc + +# You can choose from any of the predefined partitioning recipes: +d-i partman-auto/choose_recipe select \ + All files in one partition (recommended for new users) +#d-i partman-auto/choose_recipe select Desktop machine +#d-i partman-auto/choose_recipe select Multi-user workstation + +# Or provide a recipe of your own... +# The recipe format is documented in the file devel/partman-auto-recipe.txt. +# 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 in one 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 :: \ +# 20 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{ } . +# For reference, here is that same recipe in a more readable form: +# 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{ } +# . + +# This makes partman automatically partition without confirmation. +d-i partman/confirm_write_new_label boolean true +d-i partman/choose_partition select \ + Finish partitioning and write changes to disk +d-i partman/confirm boolean true + +#### Boot loader installation. + +# Grub is the default boot loader (for x86). If you want lilo installed +# instead, uncomment this: +#d-i grub-installer/skip boolean true + +# 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 if finds some other OS +# too, 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/bootdev string (hd0,0) +#d-i grub-installer/only_debian boolean false +#d-i grub-installer/with_other_os boolean false + +#### Finishing up the first stage install. + +# Avoid that last message about the install being complete. +d-i prebaseconfig/reboot_in_progress note + +#### Shell commands. + +# 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 +# preseed file like this one. Only use preseed 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 just before the install finishes, but when there is +# still a usable /target directory. +#d-i preseed/late_command string echo foo > /target/etc/bar + +# This command is run just as base-config is starting up. +#base-config base-config/early_command string echo hi mom + +# This command is run after base-config is done, just before the login: +# prompt. This is a good way to install a set of packages you want, or to +# tweak the configuration of the system. +#base-config base-config/late_command string \ +# apt-get install zsh; chsh -s /bin/zsh + +###### Preseeding the 2nd stage of the installation. + +#### Preseeding base-config. + +# Avoid the introductory message. +base-config base-config/intro note + +# Avoid the final message. +base-config base-config/login note + +# If you installed a display manager, but don't want to start it immediately +# after base-config finishes. +#base-config base-config/start-display-manager boolean false + +# Some versions of the installer can report back on what you've installed. +# 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 + +#### Clock and time zone setup. + +# Controls whether or not the hardware clock is set to UTC. +#base-config tzconfig/gmt boolean true +# If you told the installer that you're in the United States, then you +# can set the time zone using this variable. +# (Choices are: Eastern, Central, Mountain, Pacific, Alaska, Hawaii, +# Aleutian, Arizona East-Indiana, Indiana-Starke, Michigan, Samoa, other) +#base-config tzconfig/choose_country_zone/US select Eastern +# If you told it you're in Canada. +# (Choices are: Newfoundland, Atlantic, Eastern, Central, +# East-Saskatchewan, Saskatchewan, Mountain, Pacific, Yukon, other) +#base-config tzconfig/choose_country_zone/CA select Eastern +# If you told it you're in Brazil. (Choices are: East, West, Acre, +# DeNoronha, other) +#base-config tzconfig/choose_country_zone/BR select East +# Many countries have only one time zone. If you told the installer you're +# in one of those countries, you can choose its standard time zone via this +# question. +#base-config tzconfig/choose_country_zone_single boolean true +# This question is asked as a fallback for countries other than those +# listed above, which have more than one time zone. You can preseed one of +# the time zones, or "other". +#base-config tzconfig/choose_country_zone_multiple select + +#### Account setup. + +# To preseed the root password, you have to put it in the clear in this +# file. That is not a very good idea, use caution! +#passwd passwd/root-password password r00tme +#passwd passwd/root-password-again password r00tme + +# If you want to skip creation of a normal user account. +#passwd passwd/make-user boolean false + +# Alternatively, you can preseed the user's name and login. +#passwd passwd/user-fullname string Debian User +#passwd passwd/username string debian +# And their password, but use caution! +#passwd passwd/user-password password insecure +#passwd passwd/user-password-again password insecure + +#### Apt setup. + +# This question controls what source the second stage installation uses +# for packages. Choices are cdrom, http, ftp, filesystem, edit sources list +# by hand +base-config apt-setup/uri_type select http + +# If you choose ftp or http, you'll be asked for a country and a mirror. +base-config apt-setup/country select enter information manually +base-config apt-setup/hostname string http.us.debian.org +base-config apt-setup/directory string /debian +# Stop after choosing one mirror. +base-config apt-setup/another boolean false + +# You can choose to install non-free and contrib software. +#base-config apt-setup/non-free boolean true +#base-config apt-setup/contrib boolean true + +# Do enable security updates. +base-config apt-setup/security-updates boolean true + +#### Package selection. + +# You can choose to install any combination of tasks that are available. +# Available tasks as of this writing include: Desktop environment, +# Web server, Print server, DNS server, File server, Mail server, +# SQL database, Laptop, Standard system, manual package selection. The +# last of those will run aptitude. 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 Standard system task. +tasksel tasksel/first multiselect Desktop environment, Standard system +#tasksel tasksel/first multiselect Web server, Standard system + +#### Mailer configuration. + +# During a normal install, exim asks only a few questions. Here's how to +# avoid even those. More complicated preseeding is possible. +exim4-config exim4/dc_eximconfig_configtype \ + select no configuration at this time +exim4-config exim4/no_config boolean true +exim4-config exim4/no_config boolean true + +# It's a good idea to set this to whatever user account you choose to +# create. Leaving the value blank results in postmaster mail going to +# /var/mail/mail. +exim4-config exim4/dc_postmaster string + +#### X Configuration. + +# Preseeding Debian's X config is possible, but you probably need to know +# some details about the video hardware of the machine, since Debian's X +# configurator does not do fully automatic configuration of everything. + +# X can detect the right driver for some cards, but if you're preseeding, +# you override whatever it chooses. Still, vesa will work most places. +#xserver-xfree86 xserver-xfree86/config/device/driver select vesa + +# A caveat with mouse autodetection is that if it fails, X will retry it +# over and over. So if it's preseeded to be done, there is a possibility of +# an infinite loop if the mouse is not autodetected. +#xserver-xfree86 xserver-xfree86/autodetect_mouse boolean true + +# Monitor autodetection is recommended. +xserver-xfree86 xserver-xfree86/autodetect_monitor boolean true +# Uncomment if you have an LCD display. +#xserver-xfree86 xserver-xfree86/config/monitor/lcd boolean true +# X has three configuration paths for the monitor. Here's how to preseed +# the "medium" path, which is always available. The "simple" path may not +# be available, and the "advanced" path asks too many questions. +xserver-xfree86 xserver-xfree86/config/monitor/selection-method \ + select medium +xserver-xfree86 xserver-xfree86/config/monitor/mode-list \ + select 1024x768 @ 60 Hz + +#### Everything else. + +# 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 + +# If you like, you can include other preseed files into this one. +# Any settings in those files will override pre-existing settings from this +# file. More that 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 preseed file that includes them. +#d-i preseed/include string x.cfg + +# More flexibly, this runs a shell command and if it outputs the names of +# preseed files, includes those files. For example, to switch configs based +# on a particular usb storage device (in this case, a built-in card reader): +#d-i preseed/include_command string \ +# if $(grep -q "GUID: 0aec3050aec305000001a003" /proc/scsi/usb-storage-*/*); \ +# then echo kraken.cfg; else echo otherusb.cfg; fi + +# To check the format of your preseed file before performing an install, +# you can use debconf-set-selections: +# debconf-set-selections -c preseed.cfg +</screen></informalexample> diff --git a/nl/appendix/example-preseed.xml b/nl/appendix/example-preseed.xml new file mode 100644 index 000000000..58339363d --- /dev/null +++ b/nl/appendix/example-preseed.xml @@ -0,0 +1,39 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30379 untranslated --> + +<sect1 id="example-preseed"> +<title>Preconfiguration File Example</title> + +<para> + +This is a complete working example of a preconfiguration file for an automated +install. Its use is explained in <xref linkend="automatic-install"/>. You +may want to uncomment some of the lines before using the file. + +</para> + +<note condition="sarge"><para> + +In order to be able to properly present this example in the manual, we've had +to split some lines. This is indicated by the use of the line-continuation-character +<quote>\</quote> and extra indentation in the next line. In a real preconfiguration +file, these split lines have to be joined into <emphasis>one single line</emphasis>. +If you do not, preconfiguration will fail with unpredictable results. + +</para><para> + +A <quote>clean</quote> example file is available from &urlset-example-preseed;. + +</para></note> + +<para condition="etch"> + +The example file is also available from &urlset-example-preseed;. + +</para><para> + +&example-preseed-sarge.xml; +&example-preseed-etch.xml; + +</para> +</sect1> diff --git a/nl/appendix/files.xml b/nl/appendix/files.xml new file mode 100644 index 000000000..555a6395b --- /dev/null +++ b/nl/appendix/files.xml @@ -0,0 +1,298 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect1 id="linuxdevices"><title>Linux Devices</title> +<para> + +In Linux you have various special files in +<filename>/dev</filename>. These files are called device files. In +the Unix world accessing hardware is different. There you have a +special file which actually runs a driver which in turn accesses the +hardware. The device file is an interface to the actual system +component. Files under <filename>/dev</filename> also behave +differently than ordinary files. Below are the most important device +files listed. + +</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>Everything pointed 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> +<title>Setting Up Your Mouse</title> + +<para> + +The mouse can be used in both the Linux console (with gpm) and the X window +environment. The two uses can be made compatible if the gpm repeater is used +to allow the signal to flow to the X server as shown: + +<informalexample><screen> +mouse => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => X + /dev/ttyS0 (repeater) (symlink) + /dev/ttyS1 +</screen></informalexample> + +Set the repeater protocol to be raw (in <filename>/etc/gpm.conf</filename>) while +setting X to the original mouse protocol in <filename>/etc/X11/XF86Config</filename> +or <filename>/etc/X11/XF86Config-4</filename>. + +</para><para> + +This approach to use gpm even in X has advantages when the mouse is +unplugged inadvertently. Simply restarting gpm with + +<informalexample><screen> +# /etc/init.d/gpm restart +</screen></informalexample> + +will re-connect the mouse in software without restarting X. + +</para><para> + +If gpm is disabled or not installed with some reason, make sure to set X to +read directly from the mouse device such as /dev/psaux. For details, refer +to the 3-Button Mouse mini-Howto at +<filename>/usr/share/doc/HOWTO/en-txt/mini/3-Button-Mouse.gz</filename>, +<userinput>man gpm</userinput>, +<filename>/usr/share/doc/gpm/FAQ.gz</filename>, and +<ulink url="&url-xfree86;current/mouse.html">README.mouse</ulink>. + +</para><para arch="powerpc"> + +For PowerPC, in <filename>/etc/X11/XF86Config</filename> or +<filename>/etc/X11/XF86Config-4</filename>, set the mouse device to +<userinput>"/dev/input/mice"</userinput>. + +</para><para arch="powerpc"> + +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> + +<!-- Note for d-i and manual maintainers + Sizes of tasks should be determined by running "tasksel new" on a system + that been fully installed without selecting any tasks. By selecting a + task together with the "manual selection" option, aptitude will be started + and show the sizes for the task. After deselecting the packages to be + installed, quit aptitude and repeat for other tasks. + Space requirements need to be determined from tasksel as tasksel will not + install recommended packages while selecting a task from aptitude will. +--> + +<para> + +The base installation for i386 using the default 2.4 kernel, +including all standard packages, requires 573MB of disk space. + +</para><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> + +Note that you will need to add the sizes listed in the table to the size +of the base installation when determining the size of partitions. +Most of the size listed as <quote>Installed size</quote> will end up in +<filename>/usr</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</entry> + <entry>1392</entry> + <entry>460</entry> + <entry>1852</entry> +</row> + +<row> + <entry>Web server</entry> + <entry>36</entry> + <entry>12</entry> + <entry>48</entry> +</row> + +<row> + <entry>Print server</entry> + <entry>168</entry> + <entry>58</entry> + <entry>226</entry> +</row> + +<row> + <entry>DNS server</entry> + <entry>2</entry> + <entry>1</entry> + <entry>3</entry> +</row> + +<row> + <entry>File server</entry> + <entry>47</entry> + <entry>24</entry> + <entry>71</entry> +</row> + +<row> + <entry>Mail server</entry> + <entry>10</entry> + <entry>3</entry> + <entry>13</entry> +</row> + +<row> + <entry>SQL database</entry> + <entry>66</entry> + <entry>21</entry> + <entry>87</entry> +</row> + +</tbody> +</tgroup></informaltable> + +<note><para> + +The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE +desktop environments. + +</para></note> + +</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 200MB in total for download and installation. + +</para> + </sect1> diff --git a/nl/appendix/gpl.xml b/nl/appendix/gpl.xml new file mode 100644 index 000000000..ba5782af2 --- /dev/null +++ b/nl/appendix/gpl.xml @@ -0,0 +1,512 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29618 untranslated --> + +<appendix id="appendix-gpl"><title>GNU General Public License</title> + +<para> + +Version 2, June 1991 + +</para><para> + +Copyright (C) 1989, 1991 Free Software Foundation, Inc. +— +51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. +</para><para> + +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. + +</para> + + <sect1><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> + </sect1> + + <sect1><title>GNU GENERAL PUBLIC LICENSE</title> +<para> + +TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + +</para> + +<itemizedlist><listitem><para> + +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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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><para> + +a) You must cause the modified files to carry prominent notices +stating that you changed the files and the date of any change. + +</para><para> + +b) 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><para> + +c) 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><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></listitem> +<listitem><para> + +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><para> + +a) 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><para> + +b) 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><para> + +c) 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><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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +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> + +NO WARRANTY + +</para></listitem> +<listitem><para> + +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></listitem> +<listitem><para> + +in no event unless required by applicable law or agreed to in +writing will any 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></listitem> +</itemizedlist> +<para> + +END OF TERMS AND CONDITIONS + +</para> + </sect1> + + <sect1><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. + +</para><para> + +one line to give the program's name and a brief idea of what it +does. + +</para><para> + +Copyright (C) year name of author + +</para><para> + +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. + +</para><para> + +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. + +</para><para> + +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. + +</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: + +</para><para> + +Gnomovision version 69, Copyright (C) year name of author + +</para><para> + +Gnomovision comes with absolutely no warranty; for details type `show +w'. + +</para><para> + +This is free software, and you are welcome to redistribute it under +certain conditions; type `show c' for details. + +</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: + +</para><para> + +Yoyodyne, Inc., hereby disclaims all copyright interest in the +program `Gnomovision' (which makes passes at compilers) written by +James Hacker. + +</para><para> + +signature of Ty Coon, 1 April 1989 + +</para><para> + +Ty Coon, President of Vice + +</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 Library General Public License instead of this +License. + +</para> + </sect1> +</appendix> diff --git a/nl/appendix/plip.xml b/nl/appendix/plip.xml new file mode 100644 index 000000000..74913ab34 --- /dev/null +++ b/nl/appendix/plip.xml @@ -0,0 +1,194 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29687 untranslated --> + + <sect1 id="plip" arch="i386"> + <title>Installing &debian; over Parallel Line IP (PLIP)</title> + +<para> + +This section explains how to install &debian; on a computer without +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. +Below are the answers that should be given during various stages of +the installation. + +</para> + +<orderedlist> +<listitem><para> + +<guimenuitem>Load installer components</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> + +Prompt for module parameters: Yes + + </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> + <listitem><para> + +Additional parameters for module parport_pc: +<userinput><replaceable>io=0x378 irq=7</replaceable></userinput> + + </para></listitem> + <listitem><para> + +Additional parameters for module plip: leave empty + + </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/random-bits.xml b/nl/appendix/random-bits.xml new file mode 100644 index 000000000..4d39d21cd --- /dev/null +++ b/nl/appendix/random-bits.xml @@ -0,0 +1,11 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29687 untranslated --> + +<appendix id="random-bits"><title>Random Bits</title> + +&example-preseed.xml; +&files.xml; +&chroot-install.xml; +&plip.xml; + +</appendix> diff --git a/nl/bookinfo.xml b/nl/bookinfo.xml new file mode 100644 index 000000000..addb50cd6 --- /dev/null +++ b/nl/bookinfo.xml @@ -0,0 +1,65 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 29882 --> + +<bookinfo id="debian_installation_guide"> +<title>&debian; Installatiehandleiding</title> + +<abstract> +<para> +Dit document bevat instructies voor de installatie van het &debian; +&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> + +<!--FJP Nieuwe paragraaf specifiek voor nl //--> +<para> +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</year> + <year>2005</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/alpha.xml b/nl/boot-installer/alpha.xml new file mode 100644 index 000000000..d43770c8b --- /dev/null +++ b/nl/boot-installer/alpha.xml @@ -0,0 +1,441 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29334 untranslated --> + + <sect2 arch="alpha" id="alpha-firmware"> + <title>Alpha Console Firmware</title> +<para> + +Console firmware is stored in a flash ROM and started when an Alpha +system is powered up or reset. There are two different console +specifications used on Alpha systems, and hence two classes of console +firmware available: + +</para> + +<itemizedlist> +<listitem><para> + + <emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem + specification, which provides an operating environment for OpenVMS, Tru64 + UNIX, and Linux operating systems. + +</para></listitem> +<listitem><para> + + <emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the + Advanced RISC Computing (ARC) specification, which provides an operating + environment for Windows NT. + +</para></listitem> +</itemizedlist> + +<para> + +From the user's perspective, the most important difference between SRM +and ARC is that the choice of console constrains the possible +disk-partitioning scheme for the hard disk which you wish to boot off +of. + +</para><para> + +ARC requires that you use an MS-DOS partition table (as created by +<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition +tables are the <quote>native</quote> partition format when booting from +ARC. In fact, since AlphaBIOS contains a disk partitioning utility, you may +prefer to partition your disks from the firmware menus before +installing Linux. + +</para><para> + +Conversely, SRM is <emphasis>incompatible</emphasis><footnote> + +<para> +Specifically, the bootsector format required by the Console Subsystem +Specification conflicts with the placement of the DOS partition table. +</para> + +</footnote> with MS-DOS partition tables. Since Tru64 Unix uses the BSD +disklabel format, this is the <quote>native</quote> partition format for +SRM installations. + +</para><para> + +GNU/Linux is the only operating system on Alpha that can be booted from +both console types, but &debian; &release; only supports booting on +SRM-based systems. If you have an Alpha for which no version of SRM is +available, if you will be dual-booting the system with Windows NT, or if +your boot device requires ARC console support for BIOS initialization, +you will not be able to use the &debian; &release; installer. You can +still run &debian; &release; on such systems by using other install +media; for instance, you can install Debian woody with MILO and upgrade. + +</para><para> + +Because <command>MILO</command> is not available for any of the Alpha +systems currently in production (as of February 2000), and because it +is no longer necessary to buy an OpenVMS or Tru64 Unix license to have +SRM firmware on your older Alpha, it is recommended that you use SRM +when possible. + +</para><para> + +The following table summarizes available and supported system +type/console combinations (see <xref linkend="alpha-cpus"/> for the +system type names). The word <quote>ARC</quote> below denotes any of the +ARC-compliant consoles. + +</para><para> + +<informaltable><tgroup cols="2"> +<thead> +<row> + <entry>System Type</entry> + <entry>Console Type Supported</entry> +</row> +</thead> + +<tbody> +<row> + <entry>alcor</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>avanti</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>book1</entry> + <entry>SRM only</entry> +</row><row> + <entry>cabriolet</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>dp264</entry> + <entry>SRM only</entry> +</row><row> + <entry>eb164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb64p</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb66</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>eb66p</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>jensen</entry> + <entry>SRM only</entry> +</row><row> + <entry>lx164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>miata</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>mikasa</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>mikasa-p</entry> + <entry>SRM only</entry> +</row><row> + <entry>nautilus</entry> + <entry>ARC (see motherboard manual) or SRM</entry> +</row><row> + <entry>noname</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>noritake</entry> + <entry>SRM only</entry> +</row><row> + <entry>noritake-p</entry> + <entry>SRM only</entry> +</row><row> + <entry>pc164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>rawhide</entry> + <entry>SRM only</entry> +</row><row> + <entry>ruffian</entry> + <entry>ARC only</entry> +</row><row> + <entry>sable</entry> + <entry>SRM only</entry> +</row><row> + <entry>sable-g</entry> + <entry>SRM only</entry> +</row><row> + <entry>sx164</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>takara</entry> + <entry>ARC or SRM</entry> +</row><row> + <entry>xl</entry> + <entry>ARC only</entry> +</row><row> + <entry>xlt</entry> + <entry>ARC only</entry> +</row> + +</tbody> +</tgroup> +</informaltable> + +</para><para> + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. For the SRM +console, <command>aboot</command>, a small, platform-independent +bootloader, is used. See the (unfortunately outdated) <ulink +url="&url-srm-howto;">SRM HOWTO</ulink> for more information on +<command>aboot</command>. + +</para><para condition="FIXME"> + +The following paragraphs are from the woody install manual, and are +included here for reference; they may be useful to someone at a later +date when Debian supports MILO-based installs again. + +</para><para condition="FIXME"> + +Generally, none of these consoles can boot Linux directly, so the +assistance of an intermediary bootloader is required. There are two +mainstream Linux loaders: <command>MILO</command> and <command>aboot</command>. + +</para><para condition="FIXME"> + +<command>MILO</command> is itself a console, which replaces ARC or SRM in +memory. <command>MILO</command> can be booted from both ARC and SRM and is +the only way to bootstrap Linux from the ARC console. +<command>MILO</command> is platform-specific (a different <command>MILO</command> +is needed for each system type) and exist only for those systems, for +which ARC support is shown in the table above. See also the +(unfortunately outdated) <ulink url="&url-milo-howto;">MILO HOWTO</ulink>. + +</para><para condition="FIXME"> + +<command>aboot</command> is a small, platform-independent bootloader, which +runs from SRM only. See the (also unfortunately outdated) <ulink +url="&url-srm-howto;">SRM HOWTO</ulink> for more information on +<command>aboot</command>. + +</para><para condition="FIXME"> + +Thus, three scenarios are generally possible, depending on the +system's console firmware and whether or not <command>MILO</command> is +available: + +<informalexample><screen> +SRM -> aboot +SRM -> MILO +ARC -> MILO +</screen></informalexample> + +Because <command>MILO</command> is not available for any of the Alpha +systems currently in production (as of February 2000), and because it +is no longer necessary to buy an OpenVMS or Tru64 Unix license to have +SRM firmware on your older Alpha, it is recommended that you use SRM and +<command>aboot</command> on new installations of GNU/Linux, unless you wish +to dual-boot with Windows NT. + +</para><para> + +The majority of AlphaServers and all current server and workstation +products contain both SRM and AlphaBIOS in their firmware. For +<quote>half-flash</quote> machines such as the various evaluation boards, +it is possible to switch from one version to another by reflashing the +firmware. Also, once SRM is installed, it is possible to run +ARC/AlphaBIOS from a floppy disk (using the <command>arc</command> +command). For the reasons mentioned above, we recommend switching to +SRM before installing &debian;. + +</para><para> + +As on other architectures, you should install the newest available +revision of the firmware<footnote> + +<para> +Except on Jensen, where Linux is not supported on firmware versions +newer than 1.7 — see <ulink url="&url-jensen-howto;"></ulink> +for more information. +</para> + +</footnote> before installing &debian;. +For Alpha, firmware updates can be obtained from +<ulink url="&url-alpha-firmware;">Alpha Firmware Updates</ulink>. + +</para> + </sect2> + + + <sect2 arch="alpha"><title>Booting with TFTP</title> +<para> + +In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> +prefix, and will be listed in the output of the <userinput>show dev</userinput> command, +like this (edited slightly): + +<informalexample><screen> +>>> show dev +ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65 +ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54 +ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0 +</screen></informalexample> + +You first need to set the boot protocol: + +<informalexample><screen> +>>> set ewa0_protocol bootp +</screen></informalexample> + +Then check the medium type is correct: + +<informalexample><screen> +>>> set ewa0_mode <replaceable>mode</replaceable> +</screen></informalexample> + +You can get a listing of valid modes with <userinput>>>>set ewa0_mode</userinput>. + +</para><para> + +Then, to boot from the first Ethernet interface, you would type: + +<informalexample><screen> +>>> boot ewa0 -flags "" +</screen></informalexample> + +This will boot using the default kernel parameters as included in the +netboot image. + +</para><para> + +If you wish to use a serial console, you <emphasis>must</emphasis> +pass the <userinput>console=</userinput> parameter to the kernel. +This can be done using the <userinput>-flags</userinput> argument to +the SRM <userinput>boot</userinput> command. The serial ports are +named the same as their corresponding files in +<userinput>/dev</userinput>. Also, when specifying additional kernel +parameters, you must repeat certain default options that are needed by +the &d-i; images. For example, to boot from <userinput>ewa0</userinput> +and use a console on the first serial port, you would type: + +<informalexample><screen> +>>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 console=ttyS0" +</screen></informalexample> + +</para> + </sect2> + + <sect2 arch="alpha"><title>Booting from CD-ROM with the SRM Console</title> +<para> + +Type + +<informalexample><screen> +>>> boot xxxx -flags 0 +</screen></informalexample> + +where <replaceable>xxxx</replaceable> is your CD-ROM drive in SRM notation. + +</para> + </sect2> + + <sect2 arch="alpha" condition="FIXME"> + <title>Booting from CD-ROM with the ARC or AlphaBIOS Console</title> +<para> + +To boot a CD-ROM from the ARC console, find your sub-architecture code +name (see <xref linkend="alpha-cpus"/>), then enter +<filename>\milo\linload.exe</filename> as the boot loader and +<filename>\milo\<replaceable>subarch</replaceable></filename> (where +<replaceable>subarch</replaceable> is the proper subarchitecture name) +as the OS Path in the `OS Selection Setup' menu. Ruffians make an +exception: You need to use <filename>\milo\ldmilo.exe</filename> as +boot loader. + +</para> + </sect2> + + + <sect2 arch="alpha" condition="supports-floppy-boot"> + <title>Booting from Floppies with the SRM Console</title> +<para> + +At the SRM prompt (<prompt>>>></prompt>), issue the following +command: + +<informalexample><screen> +>>> boot dva0 -flags 0 +</screen></informalexample> + +possibly replacing <filename>dva0</filename> with the actual device +name. Usually, <filename>dva0</filename> is the floppy; type + +<informalexample><screen> +>>> show dev +</screen></informalexample> + +to see the list of devices (e.g., if you want to boot from a CD). +Note that if you are booting via MILO, <command>-flags</command> argument +is ignored, so you can just type <command>boot dva0</command>. +If everything works OK, you will eventually see the Linux kernel boot. + +</para><para> + +If you want to specify kernel parameters when booting via +<command>aboot</command>, use the following command: + +<informalexample><screen> +>>> boot dva0 -file linux.bin.gz -flags "root=/dev/fd0 load_ramdisk=1 arguments" +</screen></informalexample> + +(typed on one line), substituting, if necessary, the actual SRM boot +device name for <filename>dva0</filename>, the Linux boot device name for +<filename>fd0</filename>, and the desired kernel parameters for +<filename>arguments</filename>. + +</para><para> + +If you want to specify kernel parameters when booting via +<command>MILO</command>, you will have to interrupt bootstrap once you get +into MILO. See <xref linkend="booting-from-milo"/>. +</para> + </sect2> + + + <sect2 arch="alpha" condition="supports-floppy-boot"> + <title>Booting from Floppies with the ARC or AlphaBIOS Console</title> + +<para> + +In the OS Selection menu, set <command>linload.exe</command> as the boot +loader, and <command>milo</command> as the OS Path. Bootstrap using the +newly created entry. + +</para> + </sect2> + + <sect2 arch="alpha" condition="FIXME" id="booting-from-milo"><title>Booting with MILO</title> +<para> + +MILO contained on the bootstrap media is configured to proceed straight +to Linux automatically. Should you wish to intervene, all you need is to +press space during MILO countdown. + +</para><para> + +If you want to specify all the bits explicitly (for example, to supply +additional parameters), you can use a command like this: + +<informalexample><screen> +MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments --> +</screen></informalexample> + +If you are booting from something other than a floppy, substitute +<filename>fd0</filename> in the above example with the appropriate device name +in Linux notation. The <command>help</command> command would give you a brief +MILO command reference. + +</para> + </sect2> diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml new file mode 100644 index 000000000..505a05323 --- /dev/null +++ b/nl/boot-installer/arm.xml @@ -0,0 +1,113 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title> + +&boot-installer-intro-net.xml; + + <sect3 arch="arm"><title>Booting from TFTP on NetWinder</title> + +<para> + +NetWinders have two network interfaces: The 10Mbps NE2000-compatible +card is <filename>eth0</filename> and the 100Mbps Tulip card is +<filename>eth1</filename>. + +</para><note><para> + +You need NeTTrom 2.2.1 or later to boot the +installation system. NeTTrom 2.3.3 is recommended: get these files +from +<ulink url="ftp://ftp.netwinder.org/pub/netwinder/firmware/"></ulink>: +<itemizedlist> +<listitem><para> + +<filename>nettrom-2.3-3.armv4l.rpm</filename> + +</para></listitem> +<listitem><para> + +<filename>nettrom-2.3.3.bin</filename> + +</para></listitem> +<listitem><para> + +<filename>nettrom-2.3.3.bin.md5sum</filename> + +</para></listitem> +</itemizedlist> + +</para></note><para> + +After rebooting and interrupting the boot process during the countdown, you +must first configure the network either with a static address: + +<informalexample><screen> + NeTTrom command-> setenv eth0_ip 192.168.0.10/24 +</screen></informalexample> + +where 24 is the number of set bits in the netmask, or a dynamic address: + +<informalexample><screen> + NeTTrom command-> boot diskless +</screen></informalexample> + +You may also need to configure the <userinput>route1</userinput> +settings if the TFTP +server is not on the local subnet. The rest of the config is pretty +standard (the save-all step is optional): + +<informalexample><screen> + NeTTrom command-> setenv kerntftpserver 192.168.0.1 + NeTTrom command-> setenv kerntftpfile boot.img + NeTTrom command-> save-all + NeTTrom command-> setenv netconfig_eth0 flash + NeTTrom command-> setenv kernconfig tftp + NeTTrom command-> setenv rootdev /dev/ram + NeTTrom command-> setenv cmdappend root=/dev/ram +</screen></informalexample> + +Only the last four of these interfere with normal disk booting, so it is +safe to issue <command>save-all</command> right before them, which will +store the network settings in case you need to boot from the network +again. + +If you want to use the serial console to install your NetWinder, you also +need the following setting: + +<informalexample><screen> + NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 +</screen></informalexample> + +Use the <command>printenv</command> command to review your +environment settings. Finally, if your <envar>cmdappend</envar> +NeTTrom variable has the <option>noinitrd</option> option, you must +remove it so the downloaded kernel can boot with its attached ramdisk. + +</para> + </sect3> + + <sect3 arch="arm"><title>Booting from TFTP on CATS</title> + +<para> + +On CATS machines, use <command>boot de0:</command> or similar at the +Cyclone prompt. + +</para> + </sect3> + </sect2> + + + + <sect2 arch="arm"><title>Booting from CD-ROM</title> + +&boot-installer-intro-cd.xml; + +<para> + +To boot a CD-ROM from the Cyclone console prompt, use the command +<command>boot cd0:cats.bin</command> + +</para> + </sect2> diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml new file mode 100644 index 000000000..ab8ab9784 --- /dev/null +++ b/nl/boot-installer/boot-installer.xml @@ -0,0 +1,32 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 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="alpha;arm;i386;ia64;m68k;mips;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: archs hppa and mipsel are currently missing --> + +&boot-installer-alpha.xml; +&boot-installer-arm.xml; +<!-- &boot-installer-hppa.xml; --> +&boot-installer-i386.xml; +&boot-installer-ia64.xml; +&boot-installer-m68k.xml; +&boot-installer-mips.xml; +<!-- &boot-installer-mipsel.xml; --> +&boot-installer-s390.xml; +&boot-installer-powerpc.xml; +&boot-installer-sparc.xml; + + </sect1> + +&boot-installer-parameters.xml; +&boot-installer-trouble.xml; + +</chapter> diff --git a/nl/boot-installer/hppa.xml b/nl/boot-installer/hppa.xml new file mode 100644 index 000000000..619d3eaf1 --- /dev/null +++ b/nl/boot-installer/hppa.xml @@ -0,0 +1,12 @@ +<!-- 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/i386.xml b/nl/boot-installer/i386.xml new file mode 100644 index 000000000..1e05a3ee8 --- /dev/null +++ b/nl/boot-installer/i386.xml @@ -0,0 +1,379 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect2 arch="i386"><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>F3</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> + +<!-- FIXME the documented procedure does not exactly work, commented out + until fixes + + <sect2 arch="i386" 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="i386" 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/i386/initrd.gz</filename> file and its +corresponding kernel. 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 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 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 + root=/dev/ram0 + append="<phrase condition="sarge">devfs=mount,dall </phrase>ramdisk_size=12000" +</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 (sometimes in the <filename>/boot/boot/grub/</filename>), +add the following lines: + +<informalexample><screen> +title New Install +kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000 +initrd (hd0,0)/boot/newinstall/initrd.gz +</screen></informalexample> + +and reboot. <phrase condition="sarge">If the boot fails, you can try adding +<userinput>devfs=mount,dall</userinput> to the <quote>kernel</quote> line. +</phrase> + +</para><para> + +Note that the value of the <userinput>ramdisk_size</userinput> may need to be +adjusted for the size of the initrd image. +From here on, there should be no difference between <command>GRUB</command> +or <command>LILO</command>. + +</para> + </sect2> + + <sect2 arch="i386" 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><para> + +In case your computer doesn't support booting from USB memory devices, +you can still use a single floppy to do the initial boot and then +switch to USB. Boot your system as described in <xref linkend="floppy-boot"/>; +the kernel on the boot floppy should detect your USB stick automatically. +When it asks for the root floppy, simply press &enterkey;. You should see +&d-i; starting. + +</para> + </sect2> + + <sect2 arch="i386" 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>linux root=/dev/hdc</userinput> at the boot prompt. +Installation from LS-120 is only supported by 2.4 and later kernels. + +</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="i386" 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-implemention +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="i386"><title>The Boot Prompt</title> +<para> + +When the installer boots, you should be presented with a friendly graphical +screen showing the Debian logo and the boot prompt: + +<informalexample><screen> +Press F1 for help, or ENTER to boot: +</screen></informalexample> + +At the boot prompt +you can either just press &enterkey; to boot the installer with +default options or enter a specific boot method and, optionally, boot +parameters. + +</para><para> + +Information on available boot methods and on boot parameters which might +be useful can be found by pressing <keycap>F2</keycap> through +<phrase condition="sarge"><keycap>F7</keycap></phrase><phrase +condition="etch"><keycap>F8</keycap></phrase>. If you add any parameters to +the boot command line, be sure to type the boot method (the default is +<userinput>linux</userinput>) and a space before the first parameter (e.g., +<userinput>linux debconf/priority=medium</userinput>). + +<note><para> + +If you are installing the system via a remote management device that +provides a text interface to the VGA console, you may not be able to +see the initial graphical splash screen upon booting the installer; +you may even not see the boot prompt. 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). +You can blindly press F1<footnote> + +<para> + +In some cases these devices will require special escape sequences to +enact this keypress, for example the IRA uses <keycombo> <keycap>Ctrl</keycap> +<keycap>F</keycap> </keycombo>, <keycap>1</keycap>. + +</para> + +</footnote> to bypass this screen and view the help text. Once you are +past the splash screen and at the help text your keystrokes will be echoed +at the prompt as expected. To prevent the installer from using the +framebuffer for the rest of the installation, you will also want to add +<userinput>debian-installer/framebuffer=false</userinput> to the boot prompt, +as described in the help text. + +</para></note> +</para> + + </sect2> diff --git a/nl/boot-installer/ia64.xml b/nl/boot-installer/ia64.xml new file mode 100644 index 000000000..9afc8b61e --- /dev/null +++ b/nl/boot-installer/ia64.xml @@ -0,0 +1,464 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 IA64 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 thru 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 ia64 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 ia64 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 the disk partitions. + +</para> + </sect3> + </sect2> diff --git a/nl/boot-installer/intro-cd.xml b/nl/boot-installer/intro-cd.xml new file mode 100644 index 000000000..8a3e1b20a --- /dev/null +++ b/nl/boot-installer/intro-cd.xml @@ -0,0 +1,35 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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="i386"> +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-hd.xml b/nl/boot-installer/intro-hd.xml new file mode 100644 index 000000000..569a87fb0 --- /dev/null +++ b/nl/boot-installer/intro-hd.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 in +<xref linkend="boot-drive-files"/>. + +</para> diff --git a/nl/boot-installer/intro-net.xml b/nl/boot-installer/intro-net.xml new file mode 100644 index 000000000..79189195c --- /dev/null +++ b/nl/boot-installer/intro-net.xml @@ -0,0 +1,19 @@ +<!-- 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/m68k.xml b/nl/boot-installer/m68k.xml new file mode 100644 index 000000000..1dc18c6ec --- /dev/null +++ b/nl/boot-installer/m68k.xml @@ -0,0 +1,371 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30283 untranslated --> + + <sect2 arch="m68k"><title>Choosing an Installation Method</title> + +<para> + +Some &arch-title; subarchs have the option of booting using either a +2.4.x or 2.2.x linux kernel. When such a choice exists, try the 2.4.x +linux kernel. The installer should also require less memory when using +a 2.4.x linux kernel as 2.2.x support requires a fixed-sized ramdisk +and 2.4.x uses tmpfs. + +</para><para condition="etch"> + +If you are using a 2.2.x linux kernel, then you need to use the &ramdisksize; +kernel parameter. + +</para><para> + +</para><para condition="sarge"> + +Also, if you are using a 2.2.x linux kernel, then you must make sure you +are using a ramdisk built to accommodate it, see the +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>. +In general, this means you need to use the initrd22.gz ramdisk from the respective +directory. + +</para><para> + +Make sure <userinput>root=/dev/ram</userinput> is one of your kernel +parameters. + +</para><para> + +If you're having trouble, check +<ulink url="&url-m68k-cts-faq;">cts's &arch-title; debian-installer FAQ</ulink>. + +</para> + +<itemizedlist> + <listitem><para><xref linkend="m68k-boot-amiga"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-atari"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-bvme6000"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-mac"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-mvme"/></para></listitem> + <listitem><para><xref linkend="m68k-boot-q40"/></para></listitem> +</itemizedlist> + + + <sect3 id="m68k-boot-amiga"><title>Amiga</title> +<para> + +The only method of installation available to amiga is the hard drive +(see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para><para> + +Amiga does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +<userinput>debian-installer/framebuffer=false</userinput>. + +</para> + </sect3> + + <sect3 id="m68k-boot-atari"><title>Atari</title> +<para> + +The installer for atari may be started from either the hard +drive (see <xref linkend="m68k-boot-hd"/>) or from floppies +(see <xref linkend="boot-from-floppies"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para><para> + +Atari does not currently work with bogl, so if +you are seeing bogl errors, you need to include the kernel parameter +<userinput>debian-installer/framebuffer=false</userinput>. + +</para> + </sect3> + + <sect3 id="m68k-boot-bvme6000"><title>BVME6000</title> +<para> + +The installer for BVME6000 may be started from a cdrom +(see <xref linkend="m68k-boot-cdrom"/>), floppies +(see <xref linkend="boot-from-floppies"/>), or the net +(see <xref linkend="boot-tftp"/>). + +</para> + </sect3> + + <sect3 id="m68k-boot-mac"><title>Macintosh</title> +<para> + +The only method of installation available to mac is from +the hard drive (see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> +Macs do not have a working 2.4.x kernel. + +</para><para> + +If your hardware uses a 53c9x-based scsi bus, then you may need to +include the kernel parameter <userinput>mac53c9x=1,0</userinput>. +Hardware with two such scsi buses, such as the Quadra 950, will need +<userinput>mac53c9x=2,0</userinput> instead. Alternatively, the +parameter can be specified as <userinput>mac53c9x=-1,0</userinput> +which will leave autodetection on, but which will disable SCSI +disconnects. Note that specifying this parameter is only necessary +if you have more than one hard disk; otherwise, the system will run +faster if you do not specify it. + +</para> + </sect3> + + <sect3 id="m68k-boot-mvme"><title>MVME147 and MVME16x</title> +<para> + +The installer for MVME147 and MVME16x may be started from +either floppies (see <xref linkend="boot-from-floppies"/>) +or the net (see <xref linkend="boot-tftp"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para> + </sect3> + + <sect3 id="m68k-boot-q40"><title>Q40/Q60</title> +<para> + +The only method of installation available to Q40/Q60 is +from the hard drive (see <xref linkend="m68k-boot-hd"/>). +<emphasis>In other words the cdrom is not bootable.</emphasis> + +</para> + </sect3> + + </sect2> + + <sect2 arch="m68k" id="m68k-boot-hd"><title>Booting from a Hard Disk</title> + +&boot-installer-intro-hd.xml; + +<para> + +At least six different ramdisks may be used to boot from the hard +drive, three different types each with and without support for a +2.2.x linux kernel (see +<ulink url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink> +for details). + +</para><para> + +The three different types of ramdisks are <filename>cdrom</filename>, +<filename>hd-media</filename>, and <filename>nativehd</filename>. These +ramdisks differ only in their source for installation packages. +The <filename>cdrom</filename> ramdisk uses a cdrom to get +debian-installer packages. The <filename>hd-media</filename> ramdisk +uses an iso image file of a cdrom currently residing on a hard disk. +Finally, the <filename>nativehd</filename> ramdisk uses the net to +install packages. + +</para> + +<itemizedlist> + <listitem><para><xref linkend="m68k-boothd-amiga"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-atari"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-mac"/></para></listitem> + <listitem><para><xref linkend="m68k-boothd-q40"/></para></listitem> +</itemizedlist> + + + <sect3 id="m68k-boothd-amiga"><title>Booting from AmigaOS</title> +<para> + +In the <command>Workbench</command>, start the Linux installation +process by double-clicking on the <guiicon>StartInstall</guiicon> icon +in the <filename>debian</filename> directory. + +</para><para> + +You may have to press the &enterkey; key twice after the Amiga +installer program has output some debugging information into a window. +After this, the screen will go grey, there will be a few seconds' +delay. Next, a black screen with white text should come up, displaying +all kinds of kernel debugging information. These messages may scroll +by too fast for you to read, but that's OK. After a couple of +seconds, the installation program should start automatically, so you +can continue down at <xref linkend="d-i-intro"/>. + +</para> + </sect3> + + + <sect3 id="m68k-boothd-atari"><title>Booting from Atari TOS</title> +<para> + +At the GEM desktop, start the Linux installation process by +double-clicking on the <guiicon>bootstra.prg</guiicon> icon in the +<filename>debian</filename> directory and clicking +<guibutton>Ok</guibutton> at the program options dialog box. + +</para><para> + +You may have to press the &enterkey; key after the Atari +bootstrap program has output some debugging information into a +window. After this, the screen will go grey, there will be a few +seconds' delay. Next, a black screen with white text should come up, +displaying all kinds of kernel debugging information. These messages +may scroll by too fast for you to read, but that's OK. After a couple +of seconds, the installation program should start automatically, so +you can continue below at <xref linkend="d-i-intro"/>. + +</para> + </sect3> + + + <sect3 id="m68k-boothd-mac"><title>Booting from MacOS</title> +<para> + +You must retain the original Mac system and +boot from it. It is <emphasis>essential</emphasis> that, when booting +MacOS in preparation for booting the Penguin linux loader, you +hold the <keycap>shift</keycap> key down to prevent extensions from +loading. If you don't use MacOS except for loading linux, you can +accomplish the same thing by removing all extensions and control +panels from the Mac's System Folder. Otherwise extensions may be left +running and cause random problems with the running linux kernel. + +</para><para> + +Macs require the <command>Penguin</command> +bootloader. If you do not have the tools to handle +a <command>Stuffit</command> archive, &penguin19.hfs; is an +hfs disk image with <command>Penguin</command> unpacked. +<xref linkend="create-floppy"/> describes how to copy this +image to a floppy. + +</para><para> + +At the MacOS desktop, start the Linux installation process by +double-clicking on the <guiicon>Penguin Prefs</guiicon> icon in +the <filename>Penguin</filename> directory. The +<command>Penguin</command> booter will start up. Go to the +<guimenuitem>Settings</guimenuitem> item in the +<guimenu>File</guimenu> menu, click the +<guilabel>Kernel</guilabel> tab. Select the kernel +(<filename>vmlinuz</filename>) and ramdisk +(<filename>initrd.gz</filename>) images in the +<filename>install</filename> directory by clicking on the corresponding +buttons in the upper right corner, and navigating the file select +dialogs to locate the files. + +</para><para> + +To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> +<guimenuitem>Settings...</guimenuitem>, then switch to the +<guilabel>Options</guilabel> tab. Boot parameters may be typed in to +the text entry area. If you will always want to use these settings, +select <guimenu>File</guimenu> -> <guimenuitem>Save Settings as +Default</guimenuitem>. + +</para><para> + +Close the <guilabel>Settings</guilabel> +dialog, save the settings and start the bootstrap using the +<guimenuitem>Boot Now</guimenuitem> item in the +<guimenu>File</guimenu> menu. + +</para><para> + +The <command>Penguin</command> booter will output some debugging +information into a window. After this, the screen will go grey, there +will be a few seconds' delay. Next, a black screen with white text +should come up, displaying all kinds of kernel debugging +information. These messages may scroll by too fast for you to read, +but that's OK. After a couple of seconds, the installation program +should start automatically, so you can continue below at +<xref linkend="d-i-intro"/>. + +</para> + + </sect3> + + <sect3 id="m68k-boothd-q40"><title>Booting from Q40/Q60</title> + +<para> + +FIXME + +</para><para> + +The installation program should start automatically, so you can +continue below at <xref linkend="d-i-intro"/>. + +</para> + + </sect3> + </sect2> + + + <sect2 arch="m68k" id="m68k-boot-cdrom"><title>Booting from a CD-ROM</title> +<para> + +Currently, the only &arch-title; subarchitecture that +supports CD-ROM booting is the BVME6000. + +</para> + +&boot-installer-intro-cd.xml; + + </sect2> + + + <sect2 arch="m68k" id="boot-tftp"><title>Booting with TFTP</title> + +&boot-installer-intro-net.xml; + +<para> + +After booting the VMEbus systems you will be presented with the LILO +<prompt>Boot:</prompt> prompt. At that prompt enter one of the +following to boot Linux and begin installation proper of the Debian +software using vt102 terminal emulation: + +<!-- Because the &enterkey; definition uses <keycap>, --> +<!-- we use <screen> instead of <userinput> in this list --> + +<itemizedlist> +<listitem><para> + +type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000 + +</para></listitem> +<listitem><para> + +type <screen>i162 &enterkey;</screen> to install an MVME162 + +</para></listitem> +<listitem><para> + +type <screen>i167 &enterkey;</screen> to install an MVME166/167 + +</para></listitem> + </itemizedlist> + +</para><para> + +You may additionally append the string +<screen>TERM=vt100</screen> to use vt100 terminal emulation, +e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>. + +</para> + </sect2> + + + <sect2 arch="m68k" id="boot-from-floppies"> + <title>Booting from Floppies</title> +<para> + +For most &arch-title; architectures, booting from a local filesystem is the +recommended method. + +</para><para> + +Booting from the boot floppy is supported only for Atari and VME +(with a SCSI floppy drive on VME) at this time. + +</para> + </sect2> diff --git a/nl/boot-installer/mips.xml b/nl/boot-installer/mips.xml new file mode 100644 index 000000000..f237aa957 --- /dev/null +++ b/nl/boot-installer/mips.xml @@ -0,0 +1,100 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + + <sect2 arch="mips" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>SGI Indys TFTP Booting</title> +<para> + +After entering the command monitor use + +<informalexample><screen> +bootp(): +</screen></informalexample> + +on SGI Indys 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> + + <sect3> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + +<informalexample><screen> +ifconfig eth0 -auto +</screen></informalexample> + +Once you have obtained an IP address, you can load SiByl with the following +command: + +<informalexample><screen> +boot 192.168.1.1:/boot/sibyl +</screen></informalexample> + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + +</para> +</sect3> + </sect2> + + <sect2 arch="mips"><title>Boot Parameters</title> + + <sect3> + <title>SGI Indys TFTP Booting</title> +<para> + +On SGI Indys 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> + + <sect3> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP +server and add your parameters to the <replaceable>extra_args</replaceable> +variable. + +</para> + </sect3> + + </sect2> diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml new file mode 100644 index 000000000..270390c53 --- /dev/null +++ b/nl/boot-installer/mipsel.xml @@ -0,0 +1,12 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24701 untranslated --> + + <sect2 arch="mipsel"> + <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/parameters.xml b/nl/boot-installer/parameters.xml new file mode 100644 index 000000000..5cd71f381 --- /dev/null +++ b/nl/boot-installer/parameters.xml @@ -0,0 +1,351 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30084 untranslated --> + + <sect1 id="boot-parms"><title>Boot Parameters</title> +<para> + +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> + +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> + +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 condition="supports-serial-console"> + +If you are booting with a serial console, generally the kernel will +autodetect +this<phrase arch="mipsel"> (although not on DECstations)</phrase>. +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>. + +</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> + +Note that the kernel accepts a maximum of 8 command line options and +8 environment options (including any options added by default for the +installer). If these numbers are exceeded, 2.4 kernels will drop any +excess options and 2.6 kernels will panic. +<phrase condition="etch">With kernel 2.6.9 or newer, you can use 32 +command line options and 32 environment options.</phrase> + +</para> + +</footnote> which may be useful. + +</para> + +<variablelist> +<varlistentry> +<term>debconf/priority</term> +<listitem><para> + +This parameter sets the lowest priority of messages to be displayed. + +</para><para> + +The default installation uses <userinput>debconf/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>debconf/priority=medium</userinput> as boot parameter, you +will be shown the installation menu and gain more control over the installation. +When <userinput>debconf/priority=low</userinput> is used, all messages are shown +(this is equivalent to the <emphasis>expert</emphasis> boot method). +With <userinput>debconf/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=slang</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=ncurses</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> +</listitem><listitem> +<para><userinput>DEBIAN_FRONTEND=corba</userinput></para> +</listitem> +</itemizedlist> + +The default front end 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, so this is not very useful right now. + +</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 and USB storage +devices 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>debian-installer/framebuffer</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 by the parameter +<userinput>debian-installer/framebuffer=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="i386"> + +The <userinput>video=vga16:off</userinput> argument may also be used +to disable the framebuffer. Such problems have been reported on a Dell +Inspiron with Mobile Radeon card. + +</para><para arch="m68k"> + +Such problems have been reported on the Amiga 1200 and SE/30. + +</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>. + +</para></note></listitem> +</varlistentry> + +<varlistentry> +<term>debian-installer/probe/usb</term> +<listitem><para> + +Set to <userinput>false</userinput> to prevent probing for USB on +boot, if that causes problems. + +</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>preseed/url</term> +<listitem><para> + +Specify the url to a preconfiguration file to download and use in +automating the install. See <xref linkend="automatic-install"/>. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>preseed/file</term> +<listitem><para> + +Specify the path to a preconfiguration file to load to +automating the install. See <xref linkend="automatic-install"/>. + +</para></listitem> +</varlistentry> + +<varlistentry condition="etch"> +<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>ramdisk_size</term> +<listitem><para> + +If you are using a 2.2.x kernel, you may need to set &ramdisksize;. + +</para></listitem> +</varlistentry> + +<varlistentry condition="etch"> +<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> + </sect1> + diff --git a/nl/boot-installer/powerpc.xml b/nl/boot-installer/powerpc.xml new file mode 100644 index 000000000..214c176d4 --- /dev/null +++ b/nl/boot-installer/powerpc.xml @@ -0,0 +1,247 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 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"/>. +Restart the computer, and immediately (during the chime) hold down the +<keycap>Option</keycap>, <keycap>Command (cloverleaf/Apple)</keycap>, +<keycap>o</keycap>, and <keycap>f</keycap> keys all together. After +a few seconds you will be presented with the Open Firmware prompt. +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" 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 --> +To get to the prompt, hold down +<keycombo><keycap>Command</keycap> <keycap>Option</keycap> +<keycap>o</keycap> <keycap>f</keycap></keycombo> all together while +booting (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 <command>boot enet:0</command>. PReP and CHRP boxes +may have different ways of addressing the network. On a PReP machine, +you should try +<userinput>boot <replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>,<replaceable>client_ipaddr</replaceable></userinput>. + +</para> + </sect2> + + + <sect2 arch="powerpc"> + <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 new file mode 100644 index 000000000..1413f795c --- /dev/null +++ b/nl/boot-installer/s390.xml @@ -0,0 +1,30 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 a 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. 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 new file mode 100644 index 000000000..81cad25e7 --- /dev/null +++ b/nl/boot-installer/sparc.xml @@ -0,0 +1,89 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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. Some older OpenBoot revisions require using +the device name, such as <userinput>boot le()</userinput>; these +probably don't support BOOTP nor DHCP. + +</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). You may have to use +the actual device name for older OpenBoot versions that don't support +this special command. Note that some problems have been reported on Sun4m +(e.g., Sparc 10s and Sparc 20s) systems booting from CD-ROM. + +</para> + </sect2> + + + <sect2 arch="sparc" condition="supports-floppy-boot"> + <title>Booting from Floppies</title> +<para> + +To boot from floppy on a Sparc, use + +<informalexample><screen> +Stop-A -> OpenBoot: "boot floppy" +</screen></informalexample> + +Be warned that the newer Sun4u (ultra) architecture does not support +floppy booting. A typical error message is <computeroutput>Bad magic +number in disk label - Can't open disk label package</computeroutput>. +Furthermore, a number of Sun4c models (such as the IPX) do not support +the compressed images found on the disks, so also are not supported. + +</para><para> + +Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from +booting (instead of not supporting booting at all). The appropriate +OBP update can be downloaded as product ID 106121 from +<ulink url="http://sunsolve.sun.com"></ulink>. + +</para><para> + +If you are booting from the floppy, and you see messages such as + +<informalexample><screen> +Fatal error: Cannot read partition +Illegal or malformed device name +</screen></informalexample> + +then it is possible that floppy booting is simply not supported on +your machine. + +</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 new file mode 100644 index 000000000..831d6aab5 --- /dev/null +++ b/nl/boot-installer/trouble.xml @@ -0,0 +1,274 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect1 id="boot-troubleshooting"> + <title>Troubleshooting the Installation Process</title> +<para> +</para> + + <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 re-download the floppy disk image and +write it to a <emphasis>different</emphasis> floppy. 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> + +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> + +If you are booting with your own kernel instead of the one supplied +with the installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in +your kernel. The installer requires +<userinput>CONFIG_DEVFS</userinput>. + +</para><para> + +Often, problems can be solved by removing add-ons and peripherals, and +then trying booting again. <phrase arch="i386">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="i386" 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> + +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>debian-installer/framebuffer=false</userinput> or +<userinput>video=vga16:off</userinput> to disable the framebuffer +console. Only the English +language 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 the 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>debian-installer/probe/usb=false</userinput> parameter +at the boot prompt, which will prevent the modules from being loaded. + +</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 (see <xref linkend="kernel-baking"/>). + +</para> + </sect2> + + + <sect2 id="problem-report"> + <title>Bug Reporter</title> +<para> + +If you get through the initial boot phase but cannot complete the +install, the bug reporter menu choice may be helpful. It copies system +error logs and configuration information to a user-supplied floppy. +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/debian-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. Please 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 + +Debian-installer-version: <Fill in date and from where you got the image> +uname -a: <The result of running uname -a on a shell prompt> +Date: <Date and time of the install> +Method: <How did you install? What did you boot off? If network + install, from where? Proxied?> + +Machine: <Description of machine (eg, IBM Thinkpad R32)> +Processor: +Memory: +Root Device: <IDE? SCSI? Name of device?> +Root Size/partition table: <Feel free to paste the full partition + table, with notes on which partitions are mounted where.> +Output of lspci and lspci -n: + +Base System Installation Checklist: +[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it + +Initial boot worked: [ ] +Configure network HW: [ ] +Config network: [ ] +Detect CD: [ ] +Load installer modules: [ ] +Detect hard drives: [ ] +Partition hard drives: [ ] +Create file systems: [ ] +Mount partitions: [ ] +Install base system: [ ] +Install boot loader: [ ] +Reboot: [ ] + +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-new/boot-new.xml b/nl/boot-new/boot-new.xml new file mode 100644 index 000000000..40032d9b5 --- /dev/null +++ b/nl/boot-new/boot-new.xml @@ -0,0 +1,304 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28730 --> + +<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> + +Als uw nieuwe Debian systeem niet goed opstart, probeer dan op te starten +met uw originele installatie opstartmedium of gebruik, als u deze heeft, +een 'Custom boot floppy' en start uw systeem opnieuw op. Waarschijnlijk +zal u enkele opstartargumenten moeten opgeven, zoals +<userinput>root=<replaceable>root</replaceable></userinput>, waarbij +<replaceable>root</replaceable> staat voor uw root-partitie (bijvoorbeeld +<filename>/dev/hda1</filename> of <filename>/dev/sda1</filename>). +<phrase condition="etch"> +U kunt echter ook de instructies in <xref linkend="rescue"/> volgen voor +het gebruik van de herstelmodus van het installatiesysteem. +</phrase> + +<!-- FJP: Is opstartargumenten consistent met andere plaatsen? //--> +<!-- FJP: Custom boot floppy moet nader worden uitgewerkt in manual //--> + +</para> + + <sect2 arch="m68k"><title>Een BVME 6000 opstarten</title> + +<para> + +Als u zojuist een installatie zonder schijfeenheden heeft uitgevoerd +op een BVM of Motorola VMEbus machine: geef dan, nadat het systeem het +programma <command>tftplilo</command> vanaf de TFTP-server heeft geladen, +één van de volgende commando's bij de <prompt>LILO Boot:</prompt> prompt: + +<itemizedlist> +<listitem><para> + +<userinput>b6000</userinput> gevolgd door &enterkey; +om een BVME 4000/6000 op te starten + +</para></listitem><listitem><para> + +<userinput>b162</userinput> gevolgd door &enterkey; +om een MVME162 op te starten + +</para></listitem><listitem><para> + +<userinput>b167</userinput> gevolgd door &enterkey; +om een MVME166/167 op te starten + +</para></listitem> +</itemizedlist> + +</para> + </sect2> + + <sect2 arch="m68k"><title>Een Macintosh opstarten</title> + +<para> + +Ga naar de map die de installatiebestanden bevat en start de +<command>Penguin</command> opstartlader op, waarbij u de +<keycap>command</keycap>-toets ingedrukt houdt. Ga vervolgens naar de +<userinput>Settings</userinput>-dialoog +(<keycombo> <keycap>command</keycap> <keycap>T</keycap> </keycombo>), en zoek +de invoerregel voor opstartparameters voor de kernel, die er ongeveer als volgt +zou moeten uitzien: <userinput>root=/dev/ram video=font:VGA8x16</userinput>. + +</para><para> + +U dient deze regel aan te passen naar +<userinput>root=/dev/<replaceable>yyyy</replaceable></userinput>. +Vervang daarbij <replaceable>yyyy</replaceable> met de Linux-naam van de +partitie waarop u het systeem heeft geïnstalleerd (bijvoorbeeld +<filename>/dev/sda1</filename>), zoals u eerder heeft genoteerd. +De <userinput>video=font:VGA8x8</userinput> wordt vooral aangeraden voor +gebruikers met kleinere schermen. De kernel zou een mooier (6x11) +lettertype kiezen, maar de console driver voor dat lettertype kan het +systeem doen vastlopen, dus 8x16 of 8x8 kiezen is in dit stadium +veiliger. U kunt dit op elk moment wijzigen. + +</para><para> + +Als u GNU/Linux niet automatisch wilt laten opstarten bij elke systeemstart, +zorg er dan voor dat de optie <userinput>Auto Boot</userinput> niet +geselecteerd is. Sla uw instellingen op in het bestand +<filename>Prefs</filename> met de optie <userinput>Save Settings As +Default</userinput>. + +</para><para> + +Kies nu <userinput>Boot Now</userinput> (<keycombo> +<keycap>command</keycap> <keycap>B</keycap> </keycombo>) om het nieuw +geïnstalleerde GNU/Linux-systeem op te starten in plaats van het +RAMdisk-gebaseerde installatiesysteem. + +</para><para> + +Debian zou nu moeten opstarten, en u zou de zelfde meldingen moeten zien +als bij het opstarten van het installatiesysteem, gevolgd door een aantal +nieuwe berichten. + +</para> + </sect2> + + <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; 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; (als u de schijf juist heeft ingedeeld en de +Apple_Bootstrap partitie als eerste heeft geplaatst). Als u &debian; 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; 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> + + <sect1 id="base-config"> + <title>Basisconfiguratie van Debian (na de herstart)</title> + +<para> + +Nadat het systeem opnieuw is gestart, zal u worden gevraagd de configuratie +van uw basissysteem te voltooien en vervolgens om te selecteren welke +aanvullende pakketten u wilt installeren. Het programma dat u door dit proces +leidt is <classname>base-config</classname>. Het concept daarvan lijkt zeer +sterk op de &d-i; uit de eerste fase van de installatie. +<classname>base-config</classname> gebruikt hetzelfde navigatiesysteem en is +opgebouwd uit een <quote>verborgen menu</quote> dat het installatieproces op +de achtergrond stuurt en een aantal gespecialiceerde componenten die elk een +bepaalde configuratietaak uitvoeren. +<!-- FJP: Origineel kan worden verbeterd //--> + +</para><para> + +U kunt, nadat de installatie is voltooid, de basisconfiguratie desgewenst opnieuw +uitvoeren door <userinput>base-config</userinput> te starten (als root). +<!-- FJP: Ik betwijfel of dit erg veel zin heeft; veel vragen worden automatisch +overgeslagen omdat ze gemarkeerd zijn als 'seen' //--> + +</para> + +&module-bc-timezone.xml; +&module-bc-shadow.xml; +&module-bc-ppp.xml; +&module-bc-apt.xml; +&module-bc-packages.xml; +&module-bc-install.xml; +&module-bc-mta.xml; + + </sect1> + + <sect1 id="login"> + <title>Aanloggen</title> + +<para> + +Nadat u de pakketten heeft geïnstalleerd en het mailsysteem heeft +geconfigureerd, zal, als alles goed is gegaan, een boodschap worden getoond +dat de configuratie van het basissysteem voltooid is. Daarna wordt de +aanlogprompt getoond. Log aan met uw persoonlijke gebruikersaccount door +de gebruikersnaam en het wachtwoord die u eerder heeft geselecteerd in te +geven. Uw systeem is nu klaar voor gebruik. +<!-- FJP: origineel herzien! //--> + +</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>; deze submappen hebben +de naam van de geïnstalleerde pakketten. De APT User's Guide bijvoorbeeld voor +het gebruik van <command>apt</command> om andere programma's op uw systeem te +installeren, kunt u vinden in +<filename>/usr/share/doc/apt/guide.html/index.html</filename>. +<!-- FJP: Mappen hebben niet de naam van het programma, maar van het pakket! //--> +<!-- FJP: Is dit wel zo'n geschikt voorbeeld? //--> + +</para><para> + +Daarnaast zijn er enkele bijzondere mappen onder +<filename>/usr/share/doc/</filename>. Linux HOWTO handleidingen worden +in <emphasis>.gz</emphasis>-formaat geïnstalleerd in +<filename>/usr/share/doc/HOWTO/en-txt/</filename>. Na installatie van +<command>dhelp</command> 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 te bekijken, is met +<userinput>cd /usr/share/doc/</userinput>, gevolgd door +<userinput>lynx .</userinput> (de punt staat voor de huidige map). +<!-- FJP: wordt lynx nog steeds standaard geïnstalleerd? Nee! //--> + +</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><para> + +Voor een meer volledige introductie van Debian en GNU/Linux verwijzen wij naar +<filename>/usr/share/doc/debian-guide/html/noframes/index.html</filename>. + +</para> + + </sect1> +</chapter> diff --git a/nl/boot-new/modules/apt.xml b/nl/boot-new/modules/apt.xml new file mode 100644 index 000000000..3c69fe8c2 --- /dev/null +++ b/nl/boot-new/modules/apt.xml @@ -0,0 +1,120 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 23845 --> + + <sect2 id="configure-apt"> + <title>APT configureren</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 pakket 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. De toepassing die daarbij assisteert heet +<command>apt-setup</command>. + +</para><para> + +De volgende stap in het configuratieproces is dat u APT moet vertellen +waar andere Debian-pakketten gevonden kunnen worden. Merk op dat u op +elk moment na de installatie de te gebruiken bronnen voor pakketten kunt +wijzigen door <command>apt-setup</command> te starten of door handmatig +het bestand <filename>/etc/apt/sources.list</filename> te wijzigen. +<!-- FJP: origineel loopt niet 're-run this tool ... by manually editing //--> + +</para><para> + +Als op dit moment een officiële Debian CD aanwezig is in het station, dan +behoort deze CD automatisch (zonder dat u daarom wordt gevraagd) +te worden geconfigureerd als bron voor APT. U kunt dit nagaan doordat u +zal merken dat de CD wordt gescand. +<!-- FJP: 'official _Debian_ CD'! //--> + +</para><para> + +Gebruikers zonder een officiële CD zal een reeks van mogelijkheden voor het +ophalen van Debian pakketten worden geboden: FTP, HTTP, CD-ROM of vanaf een +lokaal bestandssysteem. + +</para><para> + +U dient te weten dat het zeer wel mogelijk is om een aantal verschillende +bronnen voor APT te hebben, zelfs voor hetzelfde Debian archief. +<command>apt-get</command> zal automatisch het pakket met de hoogste versie +selecteren vanuit de beschikbare versies. Een ander voorbeeld is dat +<command>apt-get</command>, als u zowel een HTTP-bron als een CD-bron heeft +gedefinieerd, automatisch de CD-bron zal kiezen en alleen zal terugvallen op +de HTTP-bron als daar een nieuwere versie beschikbaar is. Het is echter geen +goed idee om onnodig bronnen voor APT toe te voegen omdat dit het proces van +controle op nieuwe versies in netwerkarchieven zal vertragen. + +</para> + + <sect3 id="configure-apt-net"> + <title>Netwerkbronnen voor pakketten configureren</title> + +<para> + +Als u van plan bent om de rest van uw systeem te installeren vanaf het +netwerk, is de <userinput>http</userinput>-bron de meestgebruikte optie. +De <userinput>ftp</userinput>-bron is ook een mogelijkheid, maar is over +het algemeen iets trager bij het tot stand brengen van een verbinding. + +</para><para> + +De volgende stap bij de configuratie van netwerkbronnen voor pakketten is +dat u <command>apt-setup</command> moet vertellen in welk land u woont. +Hiermee wordt geconfigureerd welke van de officiële Debian spiegelservers op +het Internet wordt gebruikt. Afhankelijk van het land dat u selecteert, wordt +een lijst met mogelijke spiegelservers getoond. Over het algemeen is het +prima om de bovenste van de lijst te kiezen, maar alle opties behoren te +werken. Merk wel op dat de lijst met spiegelservers die het installatiesysteem +biedt, gegenereerd is op het moment dat deze release van Debian werd vrijgegeven +en dat sommige spiegelservers mogelijk niet meer beschikbaar zijn. + +</para><para> + +Nadat u een spiegelserver heeft geselecteerd, zal u worden gevraagd of gebruik +moet worden gemaakt van een proxy-server. Een proxy-server is een server die al +uw HTTP- en FTP-verzoeken zal doorsturen naar het Internet en wordt het meest +gebruikt in bedrijfsnetwerken om de toegang tot het Internet te reguleren en +optimaliseren. In sommige netwerken heeft alleen de proxy-server direct toegang +tot het Internet en in dat geval moet u dus wel de naam van de proxy-server +opgeven. Mogelijk moet u ook een gebruikersnaam en een wachtwoord opgeven. +De meeste gebruikers van een computer thuis zullen geen proxy-server te hoeven +opgeven, hoewel ISP's soms proxy-servers beschikbaar stellen voor gebruik door +hun klanten. + +</para><para> + +Nadat u een spiegelserver heeft geselecteerd, zal uw nieuwe netwerkbron worden +getest. Als alles goed gaat, zal u worden gevraagd of u eventueel nog een extra +bron voor pakketten wilt toevoegen. Als u problemen ondervindt met de geselecteerde +bron, probeer dan een andere spiegelserver te selecteren (ofwel uit de keuzelijst +voor uw land ofwel uit de algemene lijst), of probeer een andere netwerkbron. + +</para> + </sect3> + </sect2> diff --git a/nl/boot-new/modules/install.xml b/nl/boot-new/modules/install.xml new file mode 100644 index 000000000..58592d99b --- /dev/null +++ b/nl/boot-new/modules/install.xml @@ -0,0 +1,42 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28997 --> + + <sect2 id="debconf"> + <title>Vragen tijdens de installatie van software</title> + +<para> + +Elk pakket dat u met behulp van <command>tasksel</command> of +<command>aptitude</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. Ook is het zinvol om tijdens het proces de uitvoer in de gaten +te houden met het oog op eventuele installatiefouten (al zult u fouten +die de installatie van een pakket onmogelijk maken, in ieder geval moeten +bevestigen). + +</para> + + <sect3 arch="powerpc" id="xserver"> + <title>Instellingen voor de X Server</title> + +<para> + +Op iMacs, en ook op sommige oudere Macintoshes, worden door de programmatuur +van de X Server geen passende videoinstellingen berekend. U dient daarom +tijdens de configuratie van de videoinstellingen te kiezen voor +<quote>Advanced</quote>. Voer <userinput>59–63</userinput> in als het +toegelaten bereik voor de <quote>horizontale synchronizatie</quote> van de +monitor. Voor het toegelaten bereik voor de <quote>verticale verversing</quote> +kunt u de standaardwaarde accepteren. +<!-- FJP: Optie "Advanced" is niet vertaald in po-debconf van xfree86 //--> + +</para><para> + +De muispoort dient te worden ingesteld op <userinput>/dev/input/mice</userinput>. + +</para> + </sect3> + </sect2> diff --git a/nl/boot-new/modules/mta.xml b/nl/boot-new/modules/mta.xml new file mode 100644 index 000000000..e911d12d7 --- /dev/null +++ b/nl/boot-new/modules/mta.xml @@ -0,0 +1,97 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 22935 --> + + <sect2 id="base-config-mta"> + <title>Uw 'Mail Transfer Agent' (MTA) configureren</title> + +<para> + +E-mail is vandaag de dag een belangrijk onderdeel van het leven van veel +mensen. Het is daarom niet verwonderlijk dat Debian u uw mailsysteem laat +configureren als een integraal onderdeel van het installatieproces. De +standaard 'agent' voor het verzenden en ontvangen van e-mail in Debian is +<command>exim4</command>, dat relatief klein en flexibel is en daarnaast +makkelijk is aan te leren. + +</para><para> + +Mogelijk vraagt u zich af of dit ook nodig is als uw computer niet op een +netwerk is aangesloten. Het korte antwoord is: ja. De iets langere +verklaring: sommige systeemhulpprogramma's (zoals <command>cron</command>, +<command>quota</command>, <command>aide</command>, …) kunnen u via +e-mail belangrijke berichten zenden. +<!-- FJP: ook debconf! //--> + +</para><para> + +Op het eerste configuratiescherm zullen diverse gebruikelijke +mail-scenario's worden gepresenteerd. Kies daaruit degene die het meest +overeenstemt met uw behoeften. + +</para> + +<variablelist> +<varlistentry> +<term>Internet-site</term> +<listitem><para> + +Uw systeem is aangesloten op een netwerk en uw e-mail wordt direct verzonden +en ontvangen via SMTP. Op de volgende configuratieschermen zal een aantal +basisvragen worden gesteld, zoals de mailnaam van uw machine of een lijst +met domeinen waarvoor u e-mail accepteert of doorstuurt. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>E-mail met smarthost</term> +<listitem><para> + +In dit scenario wordt uw uitgaande e-mail doorgesuurd naar een andere machine, +de <quote>smarthost</quote> genaamd, die het eigenlijke werk voor u verricht. +De smarthost bewaart veelal ook binnenkomende e-mail geadresseerd aan uw computer +zodat u niet continu online hoeft te zijn. Dit betekent tevens dat u uw e-mail +met behulp van een programma als fetchmail vanaf de smarthost zult moeten ophalen. +Deze optie is geschikt voor gebruikers met een inbelverbinding. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Enkel lokale e-mail</term> +<listitem><para> + +Uw systeem is niet aangesloten op een netwerk en e-mail wordt alleen verzonden +of ontvangen tussen lokale gebruikers. Deze optie wordt sterk aangeraden, zelfs +als u van plan bent om helemaal geen berichten te versturen. Reden is dat +systeemhulpprogramma's van tijd tot tijd diverse meldingen aan u kunnen zenden +(zoals het geliefde <quote>Schijfruimte-quota overschreden</quote>). Deze optie +is ook makkelijk voor nieuwe gebruikers omdat hierbij geen verdere vragen worden +gesteld. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Nu niet configureren</term> +<listitem><para> + +Kies deze optie alleen als u heel zeker weet wat u aan het doen bent. Dit laat +het e-mailsysteem ongeconfigureerd — totdat u het configureert, zult u +niet in staat zijn om e-mail te verzenden of ontvangen en bestaat de kans dat +u belangrijke berichten van hulpprogramma's van uw systeem mist. + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +Als geen van deze scenario's aansluit op uw behoeften, of als u een meer +verfijnde configuratie wenst, zult u na afloop van de installatie de +configuratiebestanden onder de map <filename>/etc/exim4</filename> moeten +wijzigen. Meer informatie over <command>exim4</command> kan worden gevonden +onder <filename>/usr/share/doc/exim4</filename>. + +</para> + </sect2> diff --git a/nl/boot-new/modules/packages.xml b/nl/boot-new/modules/packages.xml new file mode 100644 index 000000000..808d11d72 --- /dev/null +++ b/nl/boot-new/modules/packages.xml @@ -0,0 +1,162 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <sect2 id="install-packages"> + <title>Installatie van pakketten</title> + +<!-- FJP: Ontbreekt hier niet een algemene inleiding met uitleg +van prioriteit, secties van pakketten? //--> + +<para> + +Vervolgens wordt u een keuze uit een aantal vooraf door Debian +samengestelde programmatuurconfiguraties geboden. +Het is natuurlijk ook mogelijk om pakket voor pakket te kiezen wat u op +uw nieuwe systeem wilt installeren. Dit is de functie van het programma +<command>aptitude</command> dat hieronder wordt beschreven. Dit zou echter, +met ongeveer &num-of-distrib-pkgs; pakketten beschikbaar in Debian, een +langdurige bezigheid kunnen worden. + +</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> + +Hadat 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>apt-get</command>. + +<note><para> + +Zelfs als u geen enkele taak heeft geselecteerd, worden toch pakketten met +prioriteiten 'standaard', 'belangrijk' of 'vereist' — voor zover die nog +niet op uw systeem aanwezig waren — geïnstalleerd. Deze functionaliteit +is hetzelfde als wanneer u <userinput>tasksel -ris</userinput> zou uitvoeren +vanaf de opdrachtregel, en houdt op dit moment in dat ongeveer 37MB aan +archieven zal worden gedownload. Het aantal te installeren pakketten zal +worden getoond alsmede, als er pakketten gedownload moeten worden, de totale +omvang daarvan (in kB). + +</para></note> + +</para><para> + +Als u individuele pakketten wilt kunnen selecteren voor installatie, +selecteer dan de optie <quote>handmatige selectie van pakketten</quote> +van <command>tasksel</command>. Als u naast deze optie ook één of meer taken +selecteert, zal <command>aptitude</command> worden aangeroepen met de optie +<command>--visual-preview</command>. Dit houdt in dat u de te installeren +pakketten kunt controleren<footnote> + +<para> + +Ook is het mogelijk om de standaard selecties wijzigen. Gebruik <menuchoice> +<guimenu>Views</guimenu> <guimenuitem>Nieuwe Pakket-View</guimenuitem> +</menuchoice> als u aanvullende pakketten wilt selecteren. + +</para> + +</footnote>. Als u <emphasis>geen</emphasis> taken selecteert, zal het normale +startscherm van <command>aptitude</command> worden getoond. Nadat u uw +selectie heeft gemaakt, toetst u <quote><userinput>g</userinput></quote> om het +ophalen en de installatie van de pakketten te starten. + +<note><para> + +Als u de optie <quote>handmatige selectie van pakketten</quote> selecteert +<emphasis>zonder</emphasis> daarnaast taken te selecteren, dan zal geen +standaardinstallatie van pakketten plaatsvinden. Dit betekent dat u deze +optie kunt gebruiken om een minimaal systeem te installeren, maar ook dat de +verantwoordelijkheid om pakketten te selecteren die noodzakelijk zijn voor uw +systeem maar nog niet zijn geïnstalleerd als onderdeel van het basissysteem, +geheel bij uzelf ligt. + +</para></note> + +</para><para> + +Van de &num-of-distrib-pkgs; pakketten die beschikbaar zijn in Debian, wordt +slechts een klein deel afgedekt door de taken uit het Taak-installatieprogamma. +Om de informatie over de overige pakketten te bekijken, kunt u ofwel gebruik maken +van <userinput>apt-cache search <replaceable>zoektekst</replaceable></userinput> +(zie de man pagina voor <citerefentry><refentrytitle>apt-cache</refentrytitle> +<manvolnum>8</manvolnum></citerefentry>), ofwel het hieronder beschreven programma +<command>aptitude</command> uitvoeren. + +</para> + + <sect3 id="aptitude"> + <title>Geavanceerde pakketselectie met <command>aptitude</command></title> + +<para> + +<command>Aptitude</command> is een modern programma voor het beheer van pakketten. +<command>aptitude</command> stelt u in staat om zowel +individuele pakketten, een verzameling pakketten die aan bepaalde criteria voldoen +(alleen voor gevorderde gebruikers) als complete taken te installeren. + +</para><para> + +De belangrijkste opdrachttoetsen zijn: + +<informaltable> +<tgroup cols="2"> +<thead> +<row> + <entry>Toets</entry><entry>Actie</entry> +</row> +</thead> + +<tbody> +<row> + <entry><keycap>Omhoog</keycap>, <keycap>Naar beneden</keycap></entry> + <entry>De selectie omhoog of naar beneden verplaatsen.</entry> +</row><row> + <entry>&enterkey;</entry> + <entry>Het item uitklappen, inklappen of activeren.</entry> +</row><row> + <entry><keycap>+</keycap></entry> + <entry>Het pakket markeren voor installatie.</entry> +</row><row> + <entry><keycap>-</keycap></entry> + <entry>Het pakket markeren voor verwijdering.</entry> +</row><row> + <entry><keycap>d</keycap></entry> + <entry>Afhankelijkheden (dependencies) met andere pakketten tonen.</entry> +</row><row> + <entry><keycap>g</keycap></entry> + <entry>Het daadwerkelijk downloaden, installeren en/of verwijderen van pakketten.</entry> +</row><row> + <entry><keycap>q</keycap></entry> + <entry>Het huidige venster sluiten.</entry> +</row><row> + <entry><keycap>F10</keycap></entry> + <entry>Het menu activeren.</entry> +</row> +</tbody></tgroup></informaltable> + +Zie de online helpfunctie onder de <keycap>?</keycap> toets voor andere opdrachten. + +</para> + </sect3> + </sect2> diff --git a/nl/boot-new/modules/ppp.xml b/nl/boot-new/modules/ppp.xml new file mode 100644 index 000000000..052b7cceb --- /dev/null +++ b/nl/boot-new/modules/ppp.xml @@ -0,0 +1,146 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 23660 --> + + <sect2 arch="not-s390" id="PPP"> + <title>PPP configureren</title> + +<para> + +Als u tijdens de eerste fase van de installatie geen netwerk heeft +geconfigureerd, zal u vervolgens worden gevraagd of u voor het vervolg +van de installatie gebruik wilt maken van een PPP-verbinding. PPP is een +protocol dat wordt gebruikt om met een modem een inbelverbinding te maken. +Als u nu een modem configureert, zal het installatiesysteem tijdens de +volgende stappen van de installatie aanvullende pakketten of +beveiligingsupdates kunnen ophalen vanaf het Internet. +Als er geen modem in uw computer aanwezig is, of als u er de voorkeur aan +geeft uw modem na de installatie te configureren, kunt u deze stap +overslaan. + +</para><para> + +Om uw PPP-verbinding te configureren, heeft u enkele gegevens van uw +Internet leverancier (Engelse term: Internet Service Provider, afgekort +ISP) nodig, waaronder het telefoonnummer, de gebruikersnaam, het wachtwoord +en de te gebruiken DNS-servers (optioneel). +Sommige ISP's bieden installatie-instructies voor Linux-distributies. +Aangezien de meeste configuratie-instellingen (en programmatuur) +weinig verschilt tussen verschillende distributies, kunt u deze informatie +gebruiken, zelfs als deze niet specifiek op Debian gericht is. + +</para><para> + +Als u ervoor kiest om op dit punt PPP te configureren, zal het programma +<command>pppconfig</command> worden gestart. Dit programma helpt u bij de +configuratie van uw PPP-verbinding. <emphasis>Het is essentieel dat u, +als het programma vraagt om een naam voor uw inbelverbinding, antwoord met +<userinput>provider</userinput>.</emphasis> + +</para><para> + +Hopelijk zal <command>pppconfig</command> een probleemloze configuratie van +uw PPP-vervinding verzorgen. Voor het geval dit voor u niet het geval is, +vindt u hieronder meer gedetailleerde instructies. + +</para><para> + +Om PPP te kunnen configureren, dient u bekend te zijn met de beginselen +van het bekijken en wijzigen van bestanden onder GNU/Linux. Om bestanden +te bekijken, kunt u gebruik maken van <command>more</command> of, voor +gecomprimeerde bestanden met de extensie <userinput>.gz</userinput>, +<command>zmore</command>. Als u bijvoorbeeld +<filename>README.debian.gz</filename> wil bekijken, typt u <userinput>zmore +README.debian.gz</userinput>. Het basissysteem is uitgerust met een editor +genaamd <command>nano</command> die eenvoudig te gebruiken is, maar niet +veel functionaliteit heeft. Waarschijnlijk zult u later programma's willen +installeren met meer functionaliteit voor het bekijken en wijzigen van +bestanden, zoals <command>jed</command>, <command>nvi</command>, +<command>less</command> en <command>emacs</command>. + +</para><para> + +Wijzig het bestand <filename>/etc/ppp/peers/provider</filename> en vervang +<userinput>/dev/modem</userinput> met +<userinput>/dev/ttyS<replaceable>#</replaceable></userinput> waarbij +<replaceable>#</replaceable> staat voor het nummer van uw seriële poort. +Onder Linux worden seriële poorten geteld vanaf 0; uw eerste seriële poort +<phrase arch="i386">(bijvoorbeeld <userinput>COM1</userinput>)</phrase> is +onder Linux: <filename>/dev/ttyS0</filename>. + +<phrase arch="powerpc;m68k">Op Macintoshes met seriële poorten is de +modempoort <filename>/dev/ttyS0</filename> en de printerpoort +<filename>/dev/ttyS1</filename>.</phrase> + +De volgende stap is het wijzigen van +<filename>/etc/chatscripts/provider</filename> en daarin het telefoonnummer, +en uw gebruikersnaam en -wachtwoord toe te voegen. Verwijder daarbij zeker +niet de <quote>\q</quote> die voorafgaat aan het wachtwoord; dit zorgt ervoor +dat uw wachtwoord niet in uw logboekbestanden wordt getoond. + +</para><para> + +Veel providers gebruiken PAP of CHAP in plaats van leesbare tekst als +autorisatiemethode. Anderen gebruiken beide. Als uw provider het gebruik van +PAP of CHAP vereist, zal u een andere procedure moeten volgen. Wijzig in +<filename>/etc/chatscripts/provider</filename> alle regels onder de inbelstring +(deze start met <quote>ATDT</quote>) in commentaarregels, wijzig +<filename>/etc/ppp/peers/provider</filename> zoals hiervoor beschreven en voeg +<userinput>user <replaceable>naam</replaceable></userinput> toe waarbij +<replaceable>naam</replaceable> staat voor uw gebruikersnaam bij de provider +waarmee u probeert een verbinding te maken. Voeg vervolgens uw wachtwoord toe +in <filename>/etc/ppp/pap-secrets</filename> of +<filename>/etc/ppp/chap-secrets</filename>. +<!-- FJP: instructie voor maken van een commentaarregel (voetnoot?) //--> +<!-- FJP: wijzigingen in /etc/ppp moeten als root! //--> + +</para><para> + +U zal ook in het bestand <filename>/etc/resolv.conf</filename> de IP-adressen +van de domeinnaamservers (DNS) van uw provider moeten toevoegen. De regels in +<filename>/etc/resolv.conf</filename> hebben het volgende formaat: +<userinput>nameserver <replaceable>xxx.xxx.xxx.xxx</replaceable></userinput> +waarbij de <replaceable>x</replaceable>'en staan voor de cijfers in het +IP-adres. Desgewenst kunt u de optie <userinput>usepeerdns</userinput> toevoegen +in het bestand <filename>/etc/ppp/peers/provider</filename> waarmee automatische +keuze van geschikte DNS-servers geactiveerd wordt; hierbij wordt gebruik gemaakt +van instellingen die de inbelserver van de provider normaalgesproken biedt. +<!-- FJP Fout in origineel: het is niet _uw_ IP-adres maar dat van de provider //--> +<!-- FJP Is usepeerdns 'optionally' or 'alternatively'? //--> + +</para><para> + +Tenzij uw provider een aanlogprocedure heeft die afwijkt van de meerderheid van +de ISP's, bent u klaar! Start de PPP-verbinding door als root <command>pon</command> +te typen en volg het proces met behulp van de opdracht <command>plog</command>. +Gebruik <command>poff</command> om de verbinding te verbreken, wederom als root. + +</para><para> + +Lees het bestand <filename>/usr/share/doc/ppp/README.Debian.gz</filename> voor +meer informatie over het gebruik van PPP in Debian. + +</para><para> + +Voor statische SLIP-verbindingen zal u de opdracht <userinput>slattach</userinput> +(uit het pakket <classname>net-tools</classname>) moeten toevoegen in +<filename>/etc/init.d/network</filename>. Dynamisch SLIP vereist het pakket +<classname>gnudip</classname>. + +</para> + + <sect3 id="PPPOE"> + <title>PPP over Ethernet (PPPOE) configureren</title> + +<para> + +PPPOE is een protocol dat verwant is aan PPP en wordt gebruikt voor +sommige (ADSL) breedbandverbindingen. +Op dit moment bevat de basisconfiguratie geen ondersteuning voor het +configureren van PPPOE. De noodzakelijke programmatuur is echter al +geïnstalleerd, waardoor u wel PPPOE handmatig kunt configureren door +naar VT2 te schakelen en daar <command>pppoeconf</command> te starten. + +</para> + + </sect3> + </sect2> diff --git a/nl/boot-new/modules/shadow.xml b/nl/boot-new/modules/shadow.xml new file mode 100644 index 000000000..8c062eff7 --- /dev/null +++ b/nl/boot-new/modules/shadow.xml @@ -0,0 +1,80 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 18642 --> + + <sect2 id="base-config-users"> + <title>Gebruikers en wachtwoorden instellen</title> + + <sect3 id="base-config-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 kunt uw gebruikersaccount een willekeurige naam geven. Als u Jan Jansen +heet, dan zou u <userinput>jansen</userinput>, <userinput>jan</userinput>, +<userinput>jjansen</userinput> of <userinput>jj</userinput> kunnen gebruiken. +U zal ook worden gevraagd naar de volledige naam voor de gebruiker en, net +als hiervoor, om een wachtwoord. +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> + </sect2> diff --git a/nl/boot-new/modules/timezone.xml b/nl/boot-new/modules/timezone.xml new file mode 100644 index 000000000..194879836 --- /dev/null +++ b/nl/boot-new/modules/timezone.xml @@ -0,0 +1,30 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 19108 --> + + <sect2 id="base-config-tz"> + <title>Uw tijdzone instellen</title> +<para> + +Na een welkomstscherm, zal u worden gevraagd om uw tijdzone in te stellen. +Selecteer eerst of the interne klok van uw systeem staat ingesteld op +lokale tijd of op Greenwich Mean Time (GMT of UTC). De tijd die in de dialoog +wordt getoond kan u daarbij helpen. +<phrase arch="m68k;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="i386">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> + +Afhankelijk van de aan het begin van de installatie geselecteerde locatie, wordt +vervolgens een enkele tijdzone of een keuzelijst met tijdzones relevant voor +die lokatie getoond. Als een enkele tijdzone wordt getoond, kiest u +<guibutton>Ja</guibutton> om deze te bevestigen of <guibutton>Nee</guibutton> om +een keuze te kunnen maken uit de volledige lijst van tijdzones. Als een lijst +wordt getoond, selecteert u de juiste tijdzone uit de lijst of Andere voor de +volledige lijst. + +</para> + </sect2> diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml new file mode 100644 index 000000000..43bae3a81 --- /dev/null +++ b/nl/hardware/hardware-supported.xml @@ -0,0 +1,341 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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. + +</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 &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 morerows="2">Intel x86-based</entry> + <entry morerows="2">i386</entry> + <entry morerows="2"></entry> + <entry>vanilla</entry> +</row><row> + <entry>speakup</entry> +</row><row> + <entry>linux26</entry> +</row> + +<row> + <entry morerows="5">Motorola 680x0</entry> + <entry morerows="5">m68k</entry> + <entry>Atari</entry> + <entry>atari</entry> +</row><row> + <entry>Amiga</entry> + <entry>amiga</entry> +</row><row> + <entry>68k Macintosh</entry> + <entry>mac</entry> +</row><row> + <entry morerows="2">VME</entry> + <entry>bvme6000</entry> +</row><row> + <entry>mvme147</entry> +</row><row> + <entry>mvme16x</entry> +</row> + +<row> + <entry>DEC Alpha</entry> + <entry>alpha</entry> + <entry></entry> + <entry></entry> +</row> + +<row> + <entry morerows="1">Sun SPARC</entry> + <entry morerows="1">sparc</entry> + <entry morerows="1"></entry> + <entry>sun4cdm</entry> +</row><row> + <entry>sun4u</entry> +</row> + +<row> + <entry morerows="3">ARM and StrongARM</entry> + <entry morerows="3">arm</entry> + <entry morerows="3"></entry> + <entry>netwinder</entry> +</row><row> + <entry>riscpc</entry> +</row><row> + <entry>shark</entry> +</row><row> + <entry>lart</entry> +</row> + +<row> + <entry morerows="3">IBM/Motorola PowerPC</entry> + <entry morerows="3">powerpc</entry> + <entry>CHRP</entry> + <entry>chrp</entry> +</row><row> + <entry>PowerMac</entry> + <entry>pmac</entry> +</row><row> + <entry>PReP</entry> + <entry>prep</entry> +</row><row> + <entry>APUS</entry> + <entry>apus</entry> +</row> + +<row> + <entry morerows="1">HP PA-RISC</entry> + <entry morerows="1">hppa</entry> + <entry>PA-RISC 1.1</entry> + <entry>32</entry> +</row><row> + <entry>PA-RISC 2.0</entry> + <entry>64</entry> +</row> + +<row> + <entry>Intel ia64-based</entry> + <entry>ia64</entry> + <entry></entry> + <entry></entry> +</row> + +<row> + <entry morerows="2">MIPS (big endian)</entry> + <entry morerows="2">mips</entry> + <entry morerows="1">SGI Indy/Indigo 2</entry> + <entry>r4k-ip22</entry> +</row><row> + <entry>r5k-ip22</entry> +</row><row> + <entry>Broadcom BCM91250A (SWARM)</entry> + <entry>sb1-swarm-bn</entry> +</row> + +<row> + <entry morerows="3">MIPS (little endian)</entry> + <entry morerows="3">mipsel</entry> + <entry>Cobalt</entry> + <entry>cobalt</entry> +</row><row> + <entry morerows="1">DECstation</entry> + <entry>r4k-kn04</entry> +</row><row> + <entry>r3k-kn02</entry> +</row><row> + <entry>Broadcom BCM91250A (SWARM)</entry> + <entry>sb1-swarm-bn</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><para condition="new-arch"> + +This is the first official release of &debian; 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-&architecture; mailing list</ulink> +as well. + +</para> + + </sect2> + +<!-- supported cpu docs --> +&supported-alpha.xml; +&supported-arm.xml; +&supported-hppa.xml; +&supported-i386.xml; +&supported-ia64.xml; <!-- FIXME: currently missing --> +&supported-m68k.xml; +&supported-mips.xml; +&supported-mipsel.xml; +&supported-powerpc.xml; +&supported-s390.xml; +&supported-sparc.xml; + + <sect2 id="gfx" arch="not-s390"><title>Graphics Card</title> + +<para arch="i386"> + +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 XFree86's X11 system. Most AGP, PCI and +PCIe video cards work under XFree86. Details on supported graphics +buses, cards, monitors, and pointing devices can be found at +<ulink url="&url-xfree86;"></ulink>. Debian &release; ships +with XFree86 version &x11ver;. + +</para><para arch="mips"> + +The XFree86 X11 window system is only supported on the SGI Indy. The +Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports +VGA emulation or Linux framebuffer on a selected range of graphics cards. +A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for +the BCM91250A is available. + +</para><para arch="mipsel"> + +The XFree86 X11 window system is supported on some DECstation models. The +Broadcom BCM91250A evaluation board has standard 3.3v PCI slots and supports +VGA emulation or Linux framebuffer on a selected range of graphics cards. +A <ulink url="&url-bcm91250a-hardware;">compatibility listing</ulink> for +the BCM91250A is available. + +</para> + + </sect2> + + <sect2 arch="i386" id="laptops"><title>Laptops</title> +<para> + +Laptops are also supported. Laptops are often specialized or contain +proprietary hardware. To see if your particular laptop works well +with GNU/Linux, see the +<ulink url="&url-x86-laptop;">Linux Laptop pages</ulink> + +</para> + </sect2> + + + <sect2 condition="defaults-smp"> +<title>Multiple Processors</title> + +<para> + +Multi-processor support — also called <quote>symmetric multi-processing</quote> +or SMP — is supported for this architecture. The standard Debian +&release; kernel image was compiled with SMP support. This should not +prevent installation, since the SMP kernel should boot on non-SMP systems; +the kernel will simply cause a bit more overhead. + +</para><para> + +In order to optimize the kernel for single CPU systems, you'll have to +replace the standard Debian kernel. 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. + +</para> + + </sect2> + + + <sect2 condition="supports-smp"> + <title>Multiple Processors</title> +<para> + +Multi-processor support — also called <quote>symmetric +multi-processing</quote> or SMP — is supported 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. 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. + +</para> + </sect2> + + <sect2 condition="supports-smp-sometimes"> + <title>Multiple Processors</title> +<para> + +Multi-processor support — also called <quote>symmetric +multi-processing</quote> or SMP — is supported 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. + +You can also build your own customized kernel to support SMP. 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. + +</para> + </sect2> + </sect1> diff --git a/nl/hardware/hardware.xml b/nl/hardware/hardware.xml new file mode 100644 index 000000000..166cb9ab1 --- /dev/null +++ b/nl/hardware/hardware.xml @@ -0,0 +1,21 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 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 Linux. + +</para> + +&hardware-supported.xml; +&installation-media.xml; +&supported-peripherals.xml; +&memory-disk-requirements.xml; +&network-cards.xml; + +</chapter> diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml new file mode 100644 index 000000000..d9b182897 --- /dev/null +++ b/nl/hardware/installation-media.xml @@ -0,0 +1,311 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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 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="i386"> + +Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all +non-standard CD interfaces supported by Linux are supported by the +boot disks (such as Mitsumi and Matsushita drives). However, these +models might require special boot parameters or other massaging to get +them to work, and booting off these non-standard interfaces is +unlikely. The <ulink url="&url-cd-howto;">Linux CD-ROM HOWTO</ulink> +contains in-depth information on using CD-ROMs with Linux. + +</para><para arch="i386"> + +USB CD-ROM drives are also supported, as are FireWire devices that +are supported by the ohci1394 and sbp2 drivers. + +</para><para arch="alpha"> + +Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long +as the controller is supported by the SRM console. This rules out many +add-on controller cards, but most integrated IDE and SCSI chips and +controller cards that were provided by the manufacturer can be expected +to work. To find out whether your device is supported from the SRM +console, see the <ulink url="&url-srm-howto;">SRM HOWTO</ulink>. + +</para><para arch="arm"> + +IDE/ATAPI CD-ROMs are supported on all ARM machines. +On RiscPCs, SCSI CD-ROMs are also supported. + +</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-DROM drives sold for 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. The Broadcom BCM91250A supports standard IDE devices, +including CD-ROM drives, but CD images for this platform are currently not +provided because the firmware doesn't recognize CD drives. + +</para><para arch="mipsel"> + +On DECstations, 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-DROM drives sold for 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. + +</para><para arch="mipsel"> + +CD 1 contains the installer for the r3k-kn02 subarchitecture +(the R3000-based DECstations 5000/1xx and 5000/240 as well as +the R3000-based Personal DECstation models), CD 2 the +installer for the r4k-kn04 subarchitecture (the R4x00-based +DECstations 5000/150 and 5000/260 as well as the Personal DECstation +5000/50). + +</para><para arch="mipsel"> + +To boot from CD, issue the command <userinput>boot +<replaceable>#</replaceable>/rz<replaceable>id</replaceable></userinput> +on the firmware prompt, where <replaceable>#</replaceable> is the +number of the TurboChannel device from which to boot (3 on most +DECstations) and <replaceable>id</replaceable> is the SCSI ID of the +CD-ROM drive. If you need to pass additional parameters, they can +optionally be appended with the following syntax: + +</para><para arch="mipsel"> + +<userinput>boot +<replaceable>#</replaceable>/rz<replaceable>id</replaceable> +param1=value1 param2=value2 ...</userinput> + +</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="m68k"> + +In fact, installation from your local disk is the preferred +installation technique for most &architecture; machines. + +</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 condition="supports-tftp"> + +You can also <emphasis>boot</emphasis> your system over the network. +<phrase arch="mips">This is the preferred installation technique for +Mips.</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><para> + +After the operating system kernel is installed, you can install the +rest of your system via any sort of network connection (including +PPP after installation of the base system), via FTP or HTTP. + +</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; without using the &d-i; described in the rest of the +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 (see <xref linkend="kernel-baking"/> to learn how to +build your own kernel). 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="i386"> + +Generally, the Debian installation system includes support for floppies, +IDE drives, IDE floppies, parallel port IDE devices, SCSI controllers and +drives, USB, and FireWire. The file systems supported include FAT, +Win-32 FAT extensions (VFAT), and NTFS, among others. + +</para><para arch="i386"> + +The disk interfaces that emulate the <quote>AT</quote> hard disk interface +which are often called MFM, RLL, IDE, or ATA are supported. Very old 8 bit +hard disk controllers used in the IBM XT computer are supported only +as a module. 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="m68k"> + +Pretty much all storage systems supported by the Linux kernel are +supported by the Debian installation system. Note that the current +Linux kernel does not support floppies on the Macintosh at all, and +the Debian installation system doesn't support floppies for Amigas. +Also supported on the Atari is the Macintosh HFS system, and AFFS as a +module. Macs support the Atari (FAT) file system. Amigas support the +FAT file system, and HFS as a module. + +</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="alpha"> + +Any storage system supported by the Linux kernel is also supported by +the boot system. This includes both SCSI and IDE disks. Note, however, +that on many systems, the SRM console is unable to boot from IDE drives, +and the Jensen is unable to boot from floppies. (see +<ulink url="&url-jensen-howto;"></ulink> +for more information on booting the Jensen) + +</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"> + +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 new file mode 100644 index 000000000..e048007b8 --- /dev/null +++ b/nl/hardware/memory-disk-requirements.xml @@ -0,0 +1,47 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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. For a minimal console-based system (all standard packages), +250MB is required. If you want to install a reasonable amount of +software, including the X Window System, and some development programs +and libraries, you'll need at least 400MB. For a more or less complete +desktop system, you'll need a few gigabytes. + +</para><para arch="m68k"> + +On the Amiga the size of FastRAM is relevant towards the total memory +requirements. Also, using Zorro cards with 16-bit RAM is not +supported; you'll need 32-bit RAM. The <command>amiboot</command> +program can be used to disable 16-bit RAM; see the +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink>. Recent kernels should +disable 16-bit RAM automatically. + +</para><para arch="m68k"> + +On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. +Many users have reported problems running the kernel itself in Fast +RAM, so the Atari bootstrap will place the kernel in ST-RAM. The +minimum requirement for ST-RAM is 2 MB. You will need an additional +12 MB or more of TT-RAM. + +</para><para arch="m68k"> + +On the Macintosh, care should be taken on machines with RAM-based +video (RBV). The RAM segment at physical address 0 is used as screen +memory, making the default load position for the kernel unavailable. +The alternate RAM segment used for kernel and RAMdisk must be at least +4 MB. + +</para><para arch="m68k"> + +<emphasis condition="FIXME">FIXME: is this still true?</emphasis> + +</para> + + </sect1> diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml new file mode 100644 index 000000000..d296a821e --- /dev/null +++ b/nl/hardware/network-cards.xml @@ -0,0 +1,214 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="network-cards"> + <title>Network Connectivity Hardware</title> + +<para arch="i386"> + +<!-- last updated for kernel-image_2.0.36-2 --> + +Most PCI and many older ISA network cards are supported. +Some network interface cards are not supported by most Debian +installation disks, such as AX.25 cards and protocols; +NI16510 EtherBlaster cards; Schneider & Koch G16 cards; +and the Zenith Z-Note built-in network card. Microchannel (MCA) network +cards are not supported by the standard installation system, but see +<ulink url="&url-linux-mca;">Linux on MCA</ulink> for some (old) +instructions. +FDDI networks are also not supported by the installation disks, both +cards and protocols. + +<!-- missing-doc FIXME You can create a custom kernel which supports an +otherwise unsupported card and then substitute in the installer (see +<xref linkend="rescue-replace-kernel"/>). --> + +</para><para arch="i386"> + +As for ISDN, the D-channel protocol for the (old) German 1TR6 is not +supported; Spellcaster BRI ISDN boards are also not supported by the +&d-i;. + +</para> + +<para arch="m68k"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. Again, see +<ulink url="&url-m68k-faq;"></ulink> for complete details. + +</para> + +<para arch="sparc"> + +The following network interface cards (NICs) are supported from the bootable +kernel directly: + +<itemizedlist> + <listitem><para> + +Sun LANCE + + +</para></listitem> + <listitem><para> + +Sun Happy Meal + + +</para></listitem> +</itemizedlist> + +</para><para arch="sparc"> + +The following network interface cards are supported as modules. They +can be enabled once the drivers are installed during the setup. +However, due to the magic of OpenPROM, you still should be able to +boot from these devices: + +<itemizedlist> + <listitem><para> + +Sun BigMAC + + +</para></listitem> + <listitem><para> + +Sun QuadEthernet + +</para></listitem> + <listitem><para> + +MyriCOM Gigabit Ethernet + +</para></listitem> +</itemizedlist> + +</para><para arch="alpha"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="powerpc"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="hppa"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="ia64"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="mips"> + +Any network interface card (NIC) supported by the Linux kernel should +also be supported by the boot disks. You may need to load your +network driver as a module. + +</para><para arch="mipsel"> + +Due to kernel limitations only the onboard network interfaces on +DECstations are supported, TurboChannel option network cards currently +do not work. + +</para><para arch="s390"> + +Any network interface card (NIC) supported by the Linux kernel are +also be supported by the boot disks. All network drivers are compiled +as modules so you need to load one first during the initial network +setup. 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> + +Inter-User Communication Vehicle (IUCV) — available for VM guests only + +</para></listitem> +<listitem><para> + +OSA-Express in QDIO mode, HiperSockets and Guest-LANs + +</para></listitem> +</itemizedlist> + +</para> + +<para arch="arm"> + +The following network interface cards are supported directly by the +boot disks on NetWinder and CATS machines: + +<itemizedlist> + <listitem><para> + + PCI-based NE2000 + + +</para></listitem> + <listitem><para> + + DECchip Tulip + +</para></listitem> +</itemizedlist> + +</para><para arch="arm"> + +The following network interface cards are supported directly by the +boot disks on RiscPCs: + +<itemizedlist> + <listitem><para> + + Ether1 + +</para></listitem> + <listitem><para> + + Ether3 + +</para></listitem> + <listitem><para> + + EtherH + +</para></listitem> +</itemizedlist> + +</para><para arch="arm"> + +If your card is mentioned in the lists above, the complete installation +can be carried out from the network with no need for CD-ROMs or floppy +disks. + +</para><para arch="arm"> + +Any other network interface card (NIC) supported by the Linux kernel +should also be supported by the boot disks. You may need to load your +network driver as a module; this means that you will have to install +the operating system kernel and modules using some other media. + +</para> + + </sect1> diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml new file mode 100644 index 000000000..f3ab5db99 --- /dev/null +++ b/nl/hardware/supported-peripherals.xml @@ -0,0 +1,187 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29467 untranslated --> + + <sect1 id="supported-peripherals"> + <title>Peripherals and Other Hardware</title> +<para arch="not-s390"> + +Linux 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="i386"> + +USB hardware generally works fine, only some +USB keyboards may require additional configuration +(see <xref linkend="usb-keyboard-config"/>). + +</para><para arch="i386"> + +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="mips"> + +The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 +bit PCI slots as well as USB connectors. + +</para><para arch="mipsel"> + +The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 +bit PCI slots as well as USB connectors. The Cobalt RaQ has no support for +additional devices but the Qube has one PCI slot. + +</para> +</sect1> + + <sect1 arch="not-s390"><title>Purchasing Hardware Specifically for GNU/Linux</title> + +<para> + +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="m68k"> + +Unfortunately, it's quite rare to find any vendor shipping +new &arch-title; machines at all. + +</para><para arch="i386"> + +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 Linux bundled, or even +a used system, it is still important to check that your hardware is +supported by the Linux kernel. Check if your hardware is listed in +the references found above. Let your salesperson (if any) know that +you're shopping for a Linux system. Support Linux-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 Linux source code. + +</para><para arch="m68k"> + +Another example is the proprietary hardware in the older +Macintosh line. In fact, no specifications or documentation have ever +been released for any Macintosh hardware, most notably the ADB +controller (used by the mouse and keyboard), the floppy controller, +and all acceleration and CLUT manipulation of the video hardware +(though we do now support CLUT manipulation on nearly all internal +video chips). In a nutshell, this explains why the Macintosh Linux +port lags behind other Linux ports. + +</para><para> + +Since we haven't been granted access to the documentation on these +devices, they simply won't work under Linux. 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="i386"><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 Linux 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 its 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 Linux 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 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> + + + <sect2 id="Parity-RAM"> + <title>Fake or <quote>Virtual</quote> Parity RAM</title> +<para> + +If you ask for Parity RAM in a computer store, you'll probably get +<emphasis>virtual parity</emphasis> memory modules instead of +<emphasis>true parity</emphasis> ones. Virtual parity SIMMs can often +(but not always) be distinguished because they only have one more chip +than an equivalent non-parity SIMM, and that one extra chip is smaller +than all the others. Virtual-parity SIMMs work exactly like non-parity +memory. They can't tell you when you have a single-bit RAM error the +way true-parity SIMMs do in a motherboard that implements +parity. Don't ever pay more for a virtual-parity SIMM than a +non-parity one. Do expect to pay a little more for true-parity SIMMs, +because you are actually buying one extra bit of memory for every 8 +bits. + +</para><para> + +If you want complete information on &arch-title; RAM issues, and what +is the best RAM to buy, see the +<ulink url="&url-pc-hw-faq;">PC Hardware FAQ</ulink>. + +</para><para arch="alpha"> + +Most, if not all, Alpha systems require true-parity RAM. + +</para> + + </sect2> + + </sect1> diff --git a/nl/hardware/supported/alpha.xml b/nl/hardware/supported/alpha.xml new file mode 100644 index 000000000..02e0ad4be --- /dev/null +++ b/nl/hardware/supported/alpha.xml @@ -0,0 +1,457 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="alpha" id="alpha-cpus"><title>CPU, Main Boards, and Video Support</title> +<para> + +Complete information regarding supported DEC Alphas can be found at +<ulink url="&url-alpha-howto;">Linux Alpha HOWTO</ulink>. The +purpose of this section is to describe the systems supported +by the boot disks. + +</para><para> + +Alpha machines are subdivided into different system types because there +are a number of generations of motherboard and supporting chipsets. +Different systems (<quote>sub-architectures</quote>) often have radically +different engineering and capabilities. Therefore, the process of +installing and, more to the point, booting, can vary from system to system. + +</para><para> + +The following table lists the system types supported by the Debian +installation system. The table also indicates the <emphasis>code +name</emphasis> for these system types. You'll need to know this code +name when you actually begin the installation process: + +</para> + +<informaltable> +<tgroup cols="4"> +<colspec colname="c1"/> +<colspec colname="c2"/> +<colspec colname="c3"/> +<colspec colname="c4"/> +<thead> +<row> + <entry namest="c1" nameend="c2">Hardware Type</entry> + <entry>Aliases</entry><entry>MILO image</entry> +</row> +</thead> + +<tbody> +<row> + <entry morerows="3">ALCOR</entry> + <entry>AlphaStation 500 5/266.300</entry> + <entry>Maverick</entry> + <entry>alcor</entry> +</row><row> + <entry>AlphaStation 500 5/333...500</entry> + <entry>Bret</entry> + <entry>alcor</entry> +</row><row> + <entry>AlphaStation 600/266...300</entry> + <entry>Alcor</entry> + <entry>alcor</entry> +</row><row> + <entry>AlphaStation 600/300...433</entry> + <entry>XLT</entry> + <entry>xlt</entry> +</row> + +<row> + <entry>BOOK1</entry> + <entry>AlphaBook1 (laptop)</entry> + <entry>Alphabook1/Burns</entry> + <entry>book1</entry> +</row> + +<row> + <entry morerows="7">AVANTI</entry> + <entry>AlphaStation 200 4/100...166</entry> + <entry>Mustang</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 200 4/233</entry> + <entry>Mustang+</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 205 4/133...333</entry> + <entry>LX3</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 250 4/300</entry> + <entry>M3+</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 255 4/133...333</entry> + <entry>LX3+</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 300 4/266</entry> + <entry>Melmac</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 400 4/166</entry> + <entry>Chinet</entry> + <entry>avanti</entry> +</row><row> + <entry>AlphaStation 400 4/233...300</entry> + <entry>Avanti</entry> + <entry>avanti</entry> +</row> + +<row> + <entry morerows="3">EB164</entry> + <entry>AlphaPC164</entry> + <entry>PC164</entry> + <entry>pc164</entry> +</row><row> + <entry>AlphaPC164-LX</entry> + <entry>LX164</entry> + <entry>lx164</entry> +</row><row> + <entry>AlphaPC164-SX</entry> + <entry>SX164</entry> + <entry>sx164</entry> +</row><row> + <entry>EB164</entry> + <entry>EB164</entry> + <entry>eb164</entry> +</row> + +<row> + <entry morerows="2">EB64+</entry> + <entry>AlphaPC64</entry> + <entry>Cabriolet</entry> + <entry>cabriolet</entry> +</row><row> + <entry>AlphaPCI64</entry> + <entry>Cabriolet</entry> + <entry>cabriolet</entry> +</row><row> + <entry>EB64+</entry> + <entry>EB64+</entry> + <entry>eb64p</entry> +</row> + +<row> + <entry morerows="1">EB66</entry> + <entry>EB66</entry> + <entry>EB66</entry> + <entry>eb66</entry> +</row><row> + <entry>EB66+</entry> + <entry>EB66+</entry> + <entry>eb66p</entry> +</row> + +<row> + <entry morerows="2">JENSEN</entry> + <entry>DEC 2000 Model 300(S)</entry> + <entry>Jensen</entry> + <entry>N/A</entry> +</row><row> + <entry>DEC 2000 Model 500</entry> + <entry>Culzen</entry> + <entry>N/A</entry> +</row><row> + <entry>DECpc 150</entry> + <entry>Jensen</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="7">MIATA</entry> + <entry>Personal WorkStation 433a</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 433au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 466au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 500a</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 500au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 550au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 600a</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row><row> + <entry>Personal WorkStation 600au</entry> + <entry>Miata</entry> + <entry>miata</entry> +</row> + +<row> + <entry morerows="3">MIKASA</entry> + <entry>AlphaServer 1000 4/200</entry> + <entry>Mikasa</entry> + <entry>mikasa</entry> +</row><row> + <entry>AlphaServer 1000 4/233..266</entry> + <entry>Mikasa+</entry> + <entry>mikasa</entry> +</row><row> + <entry>AlphaServer 1000 5/300</entry> + <entry>Mikasa-Pinnacle</entry> + <entry>mikasa</entry> +</row><row> + <entry>AlphaServer 1000 5/300</entry> + <entry>Mikasa-Primo</entry> + <entry>mikasa</entry> +</row> + +<row> + <entry morerows="1">NAUTILUS</entry> + <entry>UP1000</entry> + <entry>Nautilus</entry> + <entry>N/A</entry> +</row><row> + <entry>UP1100</entry> + <entry>Galaxy-Train/Nautilus Jr.</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="1">NONAME</entry> + <entry>AXPpci33</entry> + <entry>Noname</entry> + <entry>noname</entry> +</row><row> + <entry>UDB</entry> + <entry>Multia</entry> + <entry>noname</entry> +</row> + +<row> + <entry morerows="6">NORITAKE</entry> + <entry>AlphaServer 1000A 4/233...266</entry> + <entry>Noritake</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 1000A 5/300</entry> + <entry>Noritake-Pinnacle</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 1000A 5/333...500</entry> + <entry>Noritake-Primo</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 800 5/333...500</entry> + <entry>Corelle</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaStation 600 A</entry> + <entry>Alcor-Primo</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 3300</entry> + <entry>Corelle</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 3300R</entry> + <entry>Corelle</entry> + <entry>N/A</entry> +</row> + +<row> + <entry>PLATFORM 2000</entry> + <entry>P2K</entry> + <entry>P2K</entry> + <entry>p2k</entry> +</row> + +<row> + <entry morerows="4">RAWHIDE</entry> + <entry>AlphaServer 1200 5/xxx</entry> + <entry>Tincup/DaVinci</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 4000 5/xxx</entry> + <entry>Wrangler/Durango</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 4100 5/xxx</entry> + <entry>Dodge</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 5300</entry> + <entry>Tincup/DaVinci</entry> + <entry>N/A</entry> +</row><row> + <entry>Digital Server 7300</entry> + <entry>Dodge</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="5">RUFFIAN</entry> + <entry>DeskStation AlphaPC164-UX</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPL164-2</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPL164-4</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPX164-2</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>DeskStation RPX164-4</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row><row> + <entry>Samsung AlphaPC164-BX</entry> + <entry>Ruffian</entry> + <entry>ruffian</entry> +</row> + +<row> + <entry morerows="3">SABLE</entry> + <entry>AlphaServer 2000 4/xxx</entry> + <entry>Demi-Sable</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 2000 5/xxx</entry> + <entry>Demi-Gamma-Sable</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 2100 4/xxx</entry> + <entry>Sable</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer 2100 5/xxx</entry> + <entry>Gamma-Sable</entry> + <entry>N/A</entry> +</row> + +<row> + <entry>TAKARA</entry> + <entry>21164 PICMG SBC</entry> + <entry>Takara</entry> + <entry>takara</entry> +</row> + +<row> + <entry morerows="3">TITAN</entry> + <entry>AlphaServer DS15</entry> + <entry>HyperBrick2</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS25</entry> + <entry>Granite</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer ES45</entry> + <entry>Privateer</entry> + <entry>N/A</entry> +</row><row> + <entry>UNKNOWN</entry> + <entry>Yukon</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="12">TSUNAMI</entry> + <entry>AlphaServer DS10</entry> + <entry>Webbrick</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS10L</entry> + <entry>Slate</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS20</entry> + <entry>Catamaran/Goldrush</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS20E</entry> + <entry>Goldrack</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer DS20L</entry> + <entry>Shark</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer ES40</entry> + <entry>Clipper</entry> + <entry>N/A</entry> +</row><row> + <entry>DP264</entry> + <entry>DP264</entry> + <entry>N/A</entry> +</row><row> + <entry>SMARTengine 21264 PCI/ISA SBC</entry> + <entry>Eiger</entry> + <entry>N/A</entry> +</row><row> + <entry>UNKNOWN</entry> + <entry>Warhol</entry> + <entry>N/A</entry> +</row><row> + <entry>UNKNOWN</entry> + <entry>Windjammer</entry> + <entry>N/A</entry> +</row><row> + <entry>UP2000</entry> + <entry>Swordfish</entry> + <entry>N/A</entry> +</row><row> + <entry>XP1000</entry> + <entry>Monet/Brisbane</entry> + <entry>N/A</entry> +</row><row> + <entry>XP900</entry> + <entry>Webbrick</entry> + <entry>N/A</entry> +</row> + +<row> + <entry morerows="1">WILDFIRE</entry> + <entry>AlphaServer GS160</entry> + <entry>Wildfire</entry> + <entry>N/A</entry> +</row><row> + <entry>AlphaServer GS320</entry> + <entry>Wildfire</entry> + <entry>N/A</entry> +</row> + +<row> + <entry>XL</entry> + <entry>XL-233...266</entry> + <entry>XL</entry> + <entry>xl</entry> +</row> + +</tbody></tgroup></informaltable> + +<para> + +It is believed that Debian &releasename; supports installing on all +alpha sub-architectures with the exception of the ARC-only Ruffian and +XL sub-architectures and the Titan subarchitecture, which requires a +change to the kernel compile options. + +</para> + </sect2> diff --git a/nl/hardware/supported/arm.xml b/nl/hardware/supported/arm.xml new file mode 100644 index 000000000..9ae4bef4e --- /dev/null +++ b/nl/hardware/supported/arm.xml @@ -0,0 +1,95 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25809 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 systems. The Debian userland however may be used by <emphasis>any</emphasis> ARM CPU including xscale. + +</para> + +<para> + +Most ARM CPUs may be run in either endian mode (big or little). However, +almost every current system implementation uses little-endian mode. +Debian currently only supports little-endian ARM systems. + +</para> + +<para> + +The commonly supported systems are + +<variablelist> +<varlistentry> +<term>Netwinder</term> +<listitem><para> + +This is actually the name for the group of machines +based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It +comprises of machines like: Netwinder (possibly one of the most common ARM +boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq +personal server (cps, aka skiff). + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Bast</term> +<listitem><para> + +This is a modern ARM 920 board with a 266MHz Samsung +processor. It has integrated IDE, USB, Serial, Parallel, audio, video, +flash and two ethernet ports. This system has a good bootloader which +is also found on the CATS and Riscstation systems. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>RiscPC</term> +<listitem><para> + +This machine is the oldest supported hardware: it was released +in 1994. It has RISC OS in ROM, Linux can be booted from that OS using +linloader. The RiscPC has a modular CPU card and typically has a 30MHz +610, 40MHz 710 or 233MHz Strongarm 110 CPU fitted. The mainboard has +integrated IDE, SVGA video, parallel port, single serial port, PS/2 +keyboard and proprietary mouse port. The proprietary module expansion +bus allows for up to eight expansion cards to be fitted depending on +configuration, several of these modules have Linux drivers. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>Riscstation</term> +<listitem><para> + +This is an inexpensive 56MHz 7500FE based machine with +integrated video, IDE, PS/2 keyboard and mouse and two serial +ports. Its lack of processing power was made up for by its price. It +may be found in two configurations one with RISC OS and one with a +simple bootloader. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>LART</term> +<listitem><para> + +This is a modular open hardware platform intended to be built +by enthusiasts. To be useful to install Debian it requires its KSB +expansion board. + +</para></listitem> +</varlistentry> +</variablelist> + +</para> + </sect2> diff --git a/nl/hardware/supported/hppa.xml b/nl/hardware/supported/hppa.xml new file mode 100644 index 000000000..6f3c8c8ee --- /dev/null +++ b/nl/hardware/supported/hppa.xml @@ -0,0 +1,17 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> + + + <sect2 arch="hppa"><title>CPU, Main Boards, and Video Support</title> +<para> + +The 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 new file mode 100644 index 000000000..725a5169b --- /dev/null +++ b/nl/hardware/supported/i386.xml @@ -0,0 +1,37 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 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 processors are supported; this includes AMD and +VIA (former Cyrix) processors as well. Also the new processors like +Athlon XP and Intel P4 Xeon are supported. However, Linux will +<emphasis>not</emphasis> run on 286 or earlier processors. + +</para> + </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, the Microchannel Architecture (MCA, used +in IBM's PS/2 line), or VESA Local Bus (VLB, sometimes called the VL +bus). + +</para> + </sect3> + </sect2> + diff --git a/nl/hardware/supported/ia64.xml b/nl/hardware/supported/ia64.xml new file mode 100644 index 000000000..0dabd4a41 --- /dev/null +++ b/nl/hardware/supported/ia64.xml @@ -0,0 +1,3 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> + diff --git a/nl/hardware/supported/m68k.xml b/nl/hardware/supported/m68k.xml new file mode 100644 index 000000000..4de0bc0f8 --- /dev/null +++ b/nl/hardware/supported/m68k.xml @@ -0,0 +1,39 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + <sect2 arch="m68k"><title>CPU, Main Boards, and Video Support</title> +<para> + +Complete information concerning supported M68000 based +(<emphasis>&architecture;</emphasis>) systems can be found at the +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink>. This section merely +outlines the basics. + +</para><para> + +The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged +Memory Management Unit) and a FPU (floating-point unit). This +includes the 68020 with an external 68851 PMMU, the 68030, and better, +and excludes the <quote>EC</quote> line of 680x0 processors. See the +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink> for complete details. + +</para><para> + +There are four major flavors of supported +<emphasis>&architecture;</emphasis> flavors: Amiga, Atari, Macintosh +and VME machines. Amiga and Atari were the first two systems to which +Linux was ported; in keeping, they are also the two most +well-supported Debian ports. The Macintosh line is supported +incompletely, both by Debian and by the Linux kernel; see +<ulink url="&url-m68k-mac;">Linux m68k for Macintosh</ulink> for project +status and supported hardware. The BVM and Motorola single board +VMEbus computers are the most recent addition to the list of machines +supported by Debian. Ports to other &architecture; architectures, +such as the Sun3 architecture and NeXT black box, are underway but not +yet supported by Debian. + +</para> + </sect2> + + + diff --git a/nl/hardware/supported/mips.xml b/nl/hardware/supported/mips.xml new file mode 100644 index 000000000..7ea1a2bf7 --- /dev/null +++ b/nl/hardware/supported/mips.xml @@ -0,0 +1,52 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 22939 untranslated --> + + + <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title> +<para> + +Debian on &arch-title; currently supports two subarchitectures: + +<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> + +Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from +Broadcom based on their SiByte processor family. + +</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-&architecture; 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. The Broadcom BCM91250A evaluation board comes with an SB1250 chip with +two SB-1 cores which are supported in SMP mode by this installer. + +</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 new file mode 100644 index 000000000..63d5a5bc1 --- /dev/null +++ b/nl/hardware/supported/mipsel.xml @@ -0,0 +1,149 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title> +<para> + +Debian on &arch-title; currently supports three subarchitectures: + +<itemizedlist> +<listitem><para> + +DECstation: various models of the DECstation are supported. + +</para></listitem> +<listitem><para> + +Cobalt Microserver: only MIPS based Cobalt machines are covered here. +This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Microserver. + +</para></listitem> +<listitem><para> + +Broadcom BCM91250A (SWARM): this is an ATX form factor evaluation board from +Broadcom based on their SiByte processor family. + +</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-&architecture; mailing list</ulink>. + +</para> + + <sect3><title>CPU/Machine types</title> + +<para> + +Currently only DECstations with R3000 and R4000/R4400 CPUs are +supported by the Debian installation system on little endian MIPS. +The Debian installation system works on the following machines: + +</para><para> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> + <entry>System Type</entry><entry>CPU</entry><entry>Code-name</entry> + <entry>Debian subarchitecture</entry> +</row> +</thead> + +<tbody> +<row> + <entry>DECstation 5000/1xx</entry> + <entry>R3000</entry> + <entry>3MIN</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>DECstation 5000/150</entry> + <entry>R4000</entry> + <entry>3MIN</entry> + <entry>r4k-kn04</entry> +</row><row> + <entry>DECstation 5000/200</entry> + <entry>R3000</entry> + <entry>3MAX</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>DECstation 5000/240</entry> + <entry>R3000</entry> + <entry>3MAX+</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>DECstation 5000/260</entry> + <entry>R4400</entry> + <entry>3MAX+</entry> + <entry>r4k-kn04</entry> +</row><row> + <entry>Personal DECstation 5000/xx</entry> + <entry>R3000</entry> + <entry>Maxine</entry> + <entry>r3k-kn02</entry> +</row><row> + <entry>Personal DECstation 5000/50</entry> + <entry>R4000</entry> + <entry>Maxine</entry> + <entry>r4k-kn04</entry> +</row> +</tbody></tgroup></informaltable> + +</para><para> + +All Cobalt machines are supported which have a serial console (which is +needed for the installation). + +</para><para> + +The Broadcom BCM91250A evaluation board comes with an SB1250 chip with two +SB-1 cores which are supported in SMP mode by this installer. + +</para> + </sect3> + + <sect3><title>Supported console options</title> +<para> + +Serial console is available on all supported DECstations (9600 bps, +8N1). For using serial console, you have to boot the installer image +with the <literal>console=ttyS</literal><replaceable>x</replaceable> kernel +parameter (with <replaceable>x</replaceable> being the number +of the serial port you have your terminal connected to — usually +<literal>2</literal>, but <literal>0</literal> for the Personal DECstations). +On 3MIN and 3MAX+ (DECstation 5000/1xx, 5000/240 and 5000/260) local console +is available with the PMAG-BA and the PMAGB-B graphics options. + +</para><para> + +If you have a Linux system to use as serial terminal, an easy way +is to run <command>cu</command><footnote> + +<para> +In Woody this command was part of the <classname>uucp</classname> package, +but in later releases it is available as a separate package. +</para> + +</footnote> on it. Example: + +<informalexample><screen> +$ cu -l /dev/ttyS1 -s 9600 +</screen></informalexample> + +where the option <literal>-l</literal> (line) sets the serial port to use +and <literal>-s</literal> (speed) sets the speed for the connection (9600 +bits per second). + +</para><para> + +Both Cobalt and Broadcom BCM91250A use 115200 bps. + +</para> + </sect3> + </sect2> diff --git a/nl/hardware/supported/powerpc.xml b/nl/hardware/supported/powerpc.xml new file mode 100644 index 000000000..fbc4b2f8b --- /dev/null +++ b/nl/hardware/supported/powerpc.xml @@ -0,0 +1,381 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 30269 untranslated --> + + + <sect2 arch="powerpc"><title>CPU, Main Boards, and Video Support</title> +<para> + +There are four major supported <emphasis>&architecture;</emphasis> +subarchitectures: PMac (Power-Macintosh), 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 four 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 Power Macintosh +systems up to and including the G4 use one of these processors. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>power3</term> +<listitem><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></listitem> +</varlistentry> + +<varlistentry> +<term>power4</term> +<listitem><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> + +The Apple G5 is also based on the POWER4 architecture, and uses this +kernel flavour. + +</para></listitem> +</varlistentry> + +<varlistentry> +<term>apus</term> +<listitem><para> + +This kernel flavour supports the Amiga Power-UP System. + +</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) makes a series of Macintosh computers based on the PowerPC +processor. For purposes of architecture support, they are categorized +as NuBus, OldWorld PCI, and NewWorld. + +</para><para> + +Macintosh computers using the 680x0 series of processors are not in +the PowerPC family but are instead m68k machines. Those models start +with <quote>Mac II</quote> or have a 3-digit model number such as Centris 650 +or Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits. + +</para><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><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. The beige colored G3 systems are also OldWorld. + +</para><para> + +The so called NewWorld PowerMacs are any PowerMacs in translucent +colored plastic cases. 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="22">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</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</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> + </sect2> diff --git a/nl/hardware/supported/s390.xml b/nl/hardware/supported/s390.xml new file mode 100644 index 000000000..edda7217d --- /dev/null +++ b/nl/hardware/supported/s390.xml @@ -0,0 +1,21 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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://oss.software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml">technical details web page</ulink> at +<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml">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 new file mode 100644 index 000000000..d00c6b252 --- /dev/null +++ b/nl/hardware/supported/sparc.xml @@ -0,0 +1,82 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="sparc" id="sparc-cpus"><title>CPU, Main Boards, and Video Support</title> +<para> + +Currently the <emphasis>&architecture;</emphasis> port supports +several types of Sparc systems. The most common identifiers for Sparc +systems are sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not +support very old sun4 hardware. However, the other systems are +supported. Sun4d has been tested the least of these, so expect +possible problems with regard to the kernel stability. Sun4c and +Sun4m, the most common of the older Sparc hardware, includes such +systems as SparcStation 1, 1+, IPC, IPX and the SparcStation LX, 5, +10, and 20, respectively. The UltraSPARC class systems fall under the +sun4u identifier, and are supported using the sun4u set of install +images. Some systems that fall under these supported identifiers are +known to not be supported. Known unsupported systems are the AP1000 +multicomputer and the Tadpole Sparcbook 1. See the +<ulink url="&url-sparc-linux-faq;">Linux for SPARCProcessors FAQ</ulink> +for complete information. + +</para> + + <sect3><title>Memory Configuration</title> +<para> + +Some older Sun workstations, notably the Sun IPX and Sun IPC have +memory banks located at fixed locations in physical memory. Thus if +the banks are not filled gaps will exist in the physical memory space. +The Linux installation requires a contiguous memory block into which +to load the kernel and the initial RAMdisk. If this is not available a +<quote>Data Access Exception</quote> will result. + +</para><para> + +Thus you must configure the memory so that the lowest memory block is +contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks +are mapped in at 16Mb boundaries. In effect this means that you must have +a sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. +In this case 4Mb is <emphasis>not</emphasis> sufficient. + +</para><para> + +Example: +In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four +SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS +connectors]. You must therefore install the 16Mb SIMM in bank 0; it is +then recommended to install the 4Mb SIMM in bank 2. + +</para> + </sect3> + + <sect3><title>Graphics Configuration</title> +<para> + +Especially in the case of older Sun workstations, it is very common +for there to be an onboard framebuffer which has been superseded (for +example the bwtwo on a sun IPC), and an SBUS card containing a later +probably accelerated buffer is then plugged in to an SBUS slot. +Under Solaris/SunOS this causes no problems because both cards are +initialized. + +</para><para> + +However with Linux this can cause a problem, in that the boot PROM +monitor may display its output on this additional card; however the +linux kernel boot messages may then be directed to the original on +board framebuffer, leaving <emphasis>no</emphasis> error messages on +the screen, with the machine apparently stuck loading the RAMdisk. + +</para><para> + +To avoid this problem, connect the monitor (if required) to the video +card in the lowest numbered SBUS slot (on motherboard card counts +as below external slots). Alternatively it is possible to use a serial +console. + +</para> + </sect3> + </sect2> diff --git a/nl/howto/installation-howto.xml b/nl/howto/installation-howto.xml new file mode 100644 index 000000000..401558e07 --- /dev/null +++ b/nl/howto/installation-howto.xml @@ -0,0 +1,350 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 31137 untranslated --> + +<appendix id="installation-howto"> +<title>Installation Howto</title> + +<para> + +This document describes how to install &debian; &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 the <link linkend="debian_installation_guide">&debian; +Installation Guide</link>. + +</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 freenode 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="i386">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 possibly one 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.img</filename>, which contains additional +drivers for many ethernet cards, and support for PCMCIA. + +</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 128 MB +image from that file. Write this image directly to your memory stick, which +must be at least 128 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="i386"> + +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. If it +doesn't, you can boot from one floppy and use the USB stick for the rest of +the install. 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="i386"> + +The easiest thing to set up is probably PXE netbooting. Untar the +file <filename>netboot/pxeboot.tar.gz</filename> into +<filename>/var/lib/tftpboot</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 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="i386"> +<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" />). +<phrase arch="i386"> +<phrase condition="sarge"> +If you want a 2.6 kernel, type <userinput>linux26</userinput> at the +<prompt>boot:</prompt> prompt. +</phrase> +<phrase condition="etch"> +If you want a 2.4 kernel, type <userinput>install24</userinput> at the +<prompt>boot:</prompt> prompt. +</phrase> +<footnote><para> + +<phrase condition="sarge"> +The 2.6 kernel is available for most boot methods, but not when booting from +a floppy. +</phrase> +<phrase condition="etch"> +The 2.6 kernel is the default for most boot methods, but is not available +when booting from a floppy. +</phrase> + +</para></footnote> +</phrase> + +</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> + +Now it is time to partition your disks. First you will be given the +opportunity to automatically partition either an entire drive, or free +space on a drive. This is recommended for new users or anyone in a hurry, +but if you do not want to autopartition, choose manual from the menu. + +</para><para arch="i386"> + +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>Finished partitioning</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>. +<xref linkend="partitioning" /> has more 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 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="i386">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 next stage of the install +process, which 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. There is a template +named <filename>install-report.template</filename> in the +<filename>/root</filename> directory of a freshly +installed system. Please fill it out and file it as a bug against the +package <classname>installation-reports</classname>, as explained in +<xref linkend="submit-bug" />. + +</para><para> + +If you did not reach base-config or ran into other trouble, 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 new file mode 100644 index 000000000..09aaf4d8c --- /dev/null +++ b/nl/install-methods/automatic-install.xml @@ -0,0 +1,111 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 question asked during the +installation process. + +</para><para> + +Although most dialogs used by &d-i; can be preseeded using this method, +there are some notable exceptions. You can (re)partition an entire disk +or use available free space on a disk; it is not possible to use existing +partitions. You currently cannot use preseeding to set up RAID and LVM. +<phrase condition="sarge">Also, with the exception of network driver modules, +it is not possible to preconfigure kernel module parameters.</phrase> + +</para><para> + +The preconfiguration file is in the format used by the +debconf-set-selections command. A well documented and working example that +you can edit is in <xref linkend="example-preseed"/>. + +</para><para> + +Alternatively, one way to get a complete file listing +all the values that can be preseeded is to do a manual install, +and then use <filename>debconf-get-selections</filename>, +from the <classname>debconf-utils</classname> package, +to dump both the debconf database and the cdebconf +database in /var/log/debian-installer/cdebconf to a single file: + +<informalexample><screen> +$ debconf-get-selections --installer > <replaceable>file</replaceable> +$ debconf-get-selections >> <replaceable>file</replaceable> +</screen></informalexample> + +However, a file generated in this manner will have some items that should +not be preseeded, and the file in <xref linkend="example-preseed"/> is a +better starting place for most users. + +</para><para> + +Once you have a preconfiguration file, you can edit it if necessary, and +place it on a web server, or copy it onto the installer's boot media. Wherever +you place the file, you need to pass a parameter to the installer at boot +time to tell it to use the file. + +</para><para> + +To make the installer use a preconfiguration file downloaded from the +network, add preseed/url=http://url/to/preseed.cfg to the kernel boot +parameters. Of course the preconfiguration will not take effect until the +installer manages to set up the network to download the file, so this is +most useful if the installer can set up the network via DHCP without asking +any questions. You may want to set the installation priority to critical to +avoid any questions while the network is being configured. See +<xref linkend="installer-args"/>. + +</para><para> + +To place a preconfiguration file on a CD, you would need to remaster the +ISO image to include your preconfiguration file. See the manual page for +mkisofs for details. Alternatively, put the preseed file on a floppy, and +use preseed/file=/floppy/preseed.cfg + +</para><para arch="i386"> + +If you'll be booting from a USB memory stick, then you can simply copy your +preconfiguration file onto the memory stick's filesystem, and edit the +syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel boot +parameters. + +</para> + + <sect3 condition="etch"> + <title>Using Preseeding to Change Default Values</title> +<para> + +It is also 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 template. + +<informalexample><screen> +d-i foo/bar string value +d-i foo/bar seen false +</screen></informalexample> + +</para> + </sect3> + </sect2> + </sect1> diff --git a/nl/install-methods/boot-drive-files.xml b/nl/install-methods/boot-drive-files.xml new file mode 100644 index 000000000..e80cf406a --- /dev/null +++ b/nl/install-methods/boot-drive-files.xml @@ -0,0 +1,176 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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="i386"> + +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="i386" 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 L 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 new file mode 100644 index 000000000..dffc1c3e0 --- /dev/null +++ b/nl/install-methods/boot-usb-files.xml @@ -0,0 +1,125 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25496 untranslated --> + + <sect1 condition="bootable-usb" id="boot-usb-files"> + <title>Preparing Files for USB Memory Stick Booting</title> + +<para> + +For preparing the USB stick you will need a system where GNU/Linux is +already running and where USB is supported. You should ensure that the +usb-storage kernel module is loaded (<userinput>modprobe +usb-storage</userinput>) and try to find out which SCSI device the USB +stick has been mapped to (in this example +<filename>/dev/sda</filename> is used). To write to your stick, you +will probably have to turn off its write protection switch. + +</para><para> + +Note, that the USB stick should be at least 128 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 arch="i386"> + +There is an all-in-one file <filename>hd-media/boot.img.gz</filename> +which contains all the installer files (including the kernel) as well +as <command>SYSLINUX</command> and its configuration file. You only +have to extract it directly to your USB stick: + +<informalexample><screen> +# zcat boot.img.gz > /dev/<replaceable>sda</replaceable> +</screen></informalexample> + +Of course this will destroy anything already on the device, so take +care that you use the correct device name for your USB stick. + +</para><para arch="powerpc"> + +There is an all-in-one file <filename>hd-media/boot.img.gz</filename> +which contains all the installer files (including the kernel) as well +as <command>yaboot</command> and its configuration file. 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>sda2</replaceable> +</screen></informalexample> + +Of course this will destroy anything already on the device, so take +care that you use the correct device name for your USB stick. + +</para><para> + +After that, mount the USB memory stick (<userinput>mount +<replaceable arch="i386">/dev/sda</replaceable> +<replaceable arch="powerpc">/dev/sda2</replaceable> +/mnt</userinput>), which will now have +<phrase arch="i386">a FAT filesystem</phrase> +<phrase arch="powerpc">an HFS filesystem</phrase> +on it, and copy a Debian netinst or businesscard ISO image to it. +Please note that the file name must end in <filename>.iso</filename>. +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. + +</para> + +&usb-setup-i386.xml; +&usb-setup-powerpc.xml; + + <sect3> + <title>Adding an ISO image</title> +<para> + +Now you should put any Debian ISO image (businesscard, netinst or even +a full one) onto your stick (if it fits). The file name of such an +image must end in <filename>.iso</filename>. + +</para><para> + +If you want to install over the network, without using an ISO image, +you will of course skip the previous step. Moreover you will have to +use the initial ramdisk from the <filename>netboot</filename> +directory instead of the one from <filename>hd-media</filename>, +because <filename>hd-media/initrd.gz</filename> does not have network +support. + +</para><para> + +When you are done, unmount the USB memory stick (<userinput>umount +/mnt</userinput>) and activate its write protection switch. + +</para> + </sect3> + + <!-- TODO: doesn't this section belong later? --> + <sect3 arch="i386"> + <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>sda</replaceable> +</screen></informalexample> + +</para></warning> + </sect3> + </sect2> + </sect1> diff --git a/nl/install-methods/create-floppy.xml b/nl/install-methods/create-floppy.xml new file mode 100644 index 000000000..fbef8b01b --- /dev/null +++ b/nl/install-methods/create-floppy.xml @@ -0,0 +1,108 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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"> + +Floppy disk booting reportedly fails on Mac USB floppy drives. + +</para><para arch="m68k"> + +Floppy disk booting is not supported on Amigas or +68k Macs. + +</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, +which depend on your platform. This section describes how to create +floppies from disk images on different platforms. + +</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 (see <xref linkend="downloading-files"/> for what +<replaceable>filename</replaceable> should be). +<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-m68k.xml; +&floppy-powerpc.xml; + + </sect1> + diff --git a/nl/install-methods/download/alpha.xml b/nl/install-methods/download/alpha.xml new file mode 100644 index 000000000..ff0250415 --- /dev/null +++ b/nl/install-methods/download/alpha.xml @@ -0,0 +1,36 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect3 arch="alpha"><title>Alpha Installation Files</title> +<para> + +If you choose to boot from ARC console firmware using +<command>MILO</command>, you will also need to prepare a disk +containing <command>MILO</command> and <command>LINLOAD.EXE</command> +from the provided disk images. See <xref linkend="alpha-firmware"/> +for more information on Alpha +firmware and boot loaders. The floppy images can be found in the +<filename>MILO</filename> directory as +<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>. + +</para><para> + +Unfortunately, these <command>MILO</command> images could not be +tested and might not work for all subarchitectures. If you find it +doesn't work for you, try copying the appropriate +<command>MILO</command> binary onto the floppy +(<ulink url="&disturlftp;main/disks-alpha/current/MILO/"></ulink>). +Note that those <command>MILO</command>s don't support ext2 <quote>sparse +superblocks</quote>, so you can't use them to load kernels from newly +generated ext2 file systems. As a workaround, you can put your kernel +onto the FAT partition next to the <command>MILO</command>. + +</para><para> + +<command>MILO</command> binaries are platform-specific. See +<xref linkend="alpha-cpus"/> to determine the appropriate +<command>MILO</command> image for your Alpha platform. + +</para> + </sect3> diff --git a/nl/install-methods/download/arm.xml b/nl/install-methods/download/arm.xml new file mode 100644 index 000000000..b21ad3ef1 --- /dev/null +++ b/nl/install-methods/download/arm.xml @@ -0,0 +1,37 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect3 arch="arm" id="riscpc-install-files"> + <title>RiscPC Installation Files</title> +<para> + +The RiscPC installer is booted initially from RISC OS. All the +necessary files are provided in one Zip archive, &rpc-install-kit;. +Download this file onto the RISC OS machine, copy the +<filename>linloader.!Boot</filename> components into place, and run +<filename>!dInstall</filename>. + +</para> + </sect3> + + <sect3 arch="arm" id="netwinder-install-files"> + <title>NetWinder Installation Files</title> +<para> + +The easiest way to boot a NetWinder is over the network, using the +supplied TFTP image &netwinder-boot-img;. + +</para> + </sect3> + + <sect3 arch="arm" id="cats-install-files"> + <title>CATS Installation Files</title> +<para> + +The only supported boot method for CATS is to use the combined image +&cats-boot-img;. This can be loaded from any device accessible to the +Cyclone bootloader. + +</para> + </sect3> diff --git a/nl/install-methods/download/m68k.xml b/nl/install-methods/download/m68k.xml new file mode 100644 index 000000000..409e6a459 --- /dev/null +++ b/nl/install-methods/download/m68k.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect3 arch="m68k" id="kernel-22"> + <title>Choosing a Kernel</title> + +<para> + +Some m68k subarchs have a choice of kernels to install. In general we +recommend trying the most recent version first. If your subarch or +machine needs to use a 2.2.x kernel, make sure you choose one of the +images that supports 2.2.x kernels (see the <ulink +url="&disturl;/main/installer-&architecture;/current/images/MANIFEST">MANIFEST</ulink>). + +</para> +<para> + +All of the m68k images for use with 2.2.x kernels, require the kernel +parameter &ramdisksize;. + +</para> + </sect3> diff --git a/nl/install-methods/download/powerpc.xml b/nl/install-methods/download/powerpc.xml new file mode 100644 index 000000000..d1dd228f9 --- /dev/null +++ b/nl/install-methods/download/powerpc.xml @@ -0,0 +1,28 @@ +<!-- 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 new file mode 100644 index 000000000..0fb20e181 --- /dev/null +++ b/nl/install-methods/downloading-files.xml @@ -0,0 +1,37 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25148 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, 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-alpha.xml; +&download-arm.xml; +&download-powerpc.xml; +&download-m68k.xml; + + </sect2> + + </sect1> diff --git a/nl/install-methods/floppy/i386.xml b/nl/install-methods/floppy/i386.xml new file mode 100644 index 000000000..00a80a4df --- /dev/null +++ b/nl/install-methods/floppy/i386.xml @@ -0,0 +1,35 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 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/m68k.xml b/nl/install-methods/floppy/m68k.xml new file mode 100644 index 000000000..839eefcea --- /dev/null +++ b/nl/install-methods/floppy/m68k.xml @@ -0,0 +1,29 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18672 untranslated --> + + + <sect2 arch="m68k"><title>Writing Disk Images on Atari Systems</title> +<para> + +You'll find the &rawwrite.ttp; program in the same directory as the +floppy disk images. Start the program by double clicking on the +program icon, and type in the name of the floppy image file you want +written to the floppy at the TOS program command line dialog box. + +</para> + + </sect2> + + <sect2 arch="m68k"><title>Writing Disk Images on Macintosh Systems</title> +<para> + +There is no MacOS application to write images to floppy disks +(and there would be no point in doing this as you can't use these +floppies to boot the installation system or install kernel and modules +from on Macintosh). However, these files are needed for the +installation of the operating system and modules, later in the +process. + +</para> + + </sect2> diff --git a/nl/install-methods/floppy/powerpc.xml b/nl/install-methods/floppy/powerpc.xml new file mode 100644 index 000000000..6c05a2e49 --- /dev/null +++ b/nl/install-methods/floppy/powerpc.xml @@ -0,0 +1,122 @@ +<!-- 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; 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 new file mode 100644 index 000000000..0956b911b --- /dev/null +++ b/nl/install-methods/install-methods.xml @@ -0,0 +1,16 @@ +<!-- 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 new file mode 100644 index 000000000..b3f577937 --- /dev/null +++ b/nl/install-methods/install-tftp.xml @@ -0,0 +1,430 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 31138 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 setup a TFTP server, and for many machines, a BOOTP server +<phrase condition="supports-rarp">, or RARP server</phrase> +<phrase condition="supports-dhcp">, or DHCP 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> + +<phrase arch="m68k"> Yet another alternative exists on VMEbus +systems: the IP address can be manually configured in boot ROM. </phrase> + +<phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration +Protocol) is a more flexible, backwards-compatible extension of BOOTP. +Some systems can only be configured via DHCP. </phrase> + +</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="alpha"> + +Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM +console will <emphasis>not</emphasis> use RARP to obtain its IP +address, and therefore you must use BOOTP for net booting your +Alpha<footnote> + +<para> +Alpha systems can also be net-booted using the DECNet MOP (Maintenance +Operations Protocol), but this is not covered here. Presumably, your +local OpenVMS operator will be happy to assist you should you have +some burning need to use MOP to boot Linux on your Alpha. +</para> + +</footnote>. You can also enter the IP configuration for network +interfaces directly in the SRM console. + +</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="i386"><para> + +To use the Pre-boot Execution Environment (PXE) method of TFTP +booting, you will need a TFTP server with <userinput>tsize</userinput> +support. On a &debian; server, the <classname>atftpd</classname> and +<classname>tftpd-hpa</classname> packages qualify; we recommend +<classname>tftpd-hpa</classname>. + +</para></note> + +</para> + +&tftp-rarp.xml; +&tftp-bootp.xml; +&tftp-dhcp.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. This is usually enabled by having +something like the following line in <filename>/etc/inetd.conf</filename>: + +<informalexample><screen> +tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot +</screen></informalexample> + +Debian packages will in general set this up correctly by default when they +are installed. + +</para><para> + +Look in that file and remember the directory which is used as the +argument of <command>in.tftpd</command>; you'll need that below. The +<userinput>-l</userinput> argument enables some versions of +<command>in.tftpd</command> to log all requests to the system logs; +this is useful for diagnosing boot errors. If you've had to change +<filename>/etc/inetd.conf</filename>, you'll have to notify the +running <command>inetd</command> process that the file has changed. +On a Debian machine, run <userinput>/etc/init.d/inetd +reload</userinput>; on other machines, +find out the process ID for <command>inetd</command>, and run +<userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. + +</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 Indy'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. Generally, this directory will be +<filename>/tftpboot</filename>. You'll 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. For net booting, use the +<filename>yaboot-netboot.conf</filename>. Just rename this to +<filename>yaboot.conf</filename> in the TFTP directory. + +</para><para arch="i386"> + +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="mipsel"> + <title>DECstation TFTP Images</title> +<para> + +For DECstations, there are tftpimage files for each subarchitecture, +which contain both kernel and installer in one file. The naming +convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. +Copy the tftpimage file you would like to use to +<userinput>/tftpboot/tftpboot.img</userinput> if you work with the +example BOOTP/DHCP setups described above. + +</para><para> + +The DECstation firmware boots by TFTP with the command <userinput>boot +<replaceable>#</replaceable>/tftp</userinput>, where +<replaceable>#</replaceable> is the number of the TurboChannel device +from which to boot. On most DECstations this is <quote>3</quote>. If the +BOOTP/DHCP server does not supply the filename or you need to pass +additional parameters, they can optionally be appended with the +following syntax: + +</para><para> + +<userinput>boot #/tftp/filename param1=value1 param2=value2 ...</userinput> + +</para><para> + +Several DECstation firmware revisions show a problem with regard to +net booting: the transfer starts, but after some time it stops with +an <computeroutput>a.out err</computeroutput>. This can have several reasons: + +<orderedlist> +<listitem><para> + +The firmware does not respond to ARP requests during a TFTP +transfer. This leads to an ARP timeout and the transfer stops. The +solution is to add the MAC address of the Ethernet card in the +DECstation statically to the ARP table of the TFTP server. This is +done by running <userinput>arp -s +<replaceable>IP-address</replaceable> +<replaceable>MAC-address</replaceable></userinput> as root on the +machine acting as TFTP server. The MAC-address of the DECstation can +be read out by entering <command>cnfg</command> at the DECstation +firmware prompt. + +</para></listitem> +<listitem><para> + +The firmware has a size limit on the files that can be booted +by TFTP. + +</para></listitem> +</orderedlist> + +There are also firmware revisions that cannot boot via TFTP at all. An +overview about the different firmware revisions can be found at the +NetBSD web pages: +<ulink url="http://www.netbsd.org/Ports/pmax/board-list.html#proms"></ulink>. + +</para> + </sect3> + + <sect3 arch="alpha"> + <title>Alpha TFTP Booting</title> +<para> +On Alpha, you must specify the filename (as a relative path to the +boot image directory) using the <userinput>-file</userinput> argument +to the SRM <userinput>boot</userinput> command, or by setting the +<userinput>BOOT_FILE</userinput> environment variable. Alternatively, +the filename can be given via BOOTP (in ISC <command>dhcpd</command>, +use the <userinput>filename</userinput> directive). Unlike Open +Firmware, there is <emphasis>no default filename</emphasis> on SRM, so +you <emphasis>must</emphasis> specify a filename by either one of +these methods. + +</para> + </sect3> + + <sect3 arch="sparc"> + <title>SPARC TFTP Booting</title> +<para> + +SPARC architectures for instance use the subarchitecture names, such +as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the +architecture is left blank, so the file the client looks for is just +<filename>client-ip-in-hex</filename>. Thus, if your system +subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename +would be <filename>C0A80103.SUN4C</filename>. An easy way to determine +this 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> + +This will spit out the IP in hexadecimal; to get to the correct +filename, you will need to change all letters to uppercase and +if necessary append the subarchitecture name. + +</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="m68k"> + <title>BVM/Motorola TFTP Booting</title> +<para> + +For BVM and Motorola VMEbus systems copy the files +&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. + +</para><para> + +Next, configure your boot ROMs or BOOTP server to initially load the +<filename>tftplilo.bvme</filename> or +<filename>tftplilo.mvme</filename> files from the TFTP server. Refer +to the <filename>tftplilo.txt</filename> file for your subarchitecture +for additional system-specific configuration information. + +</para> + </sect3> + + <sect3 arch="mips"> + <title>SGI Indys TFTP Booting</title> +<para> + +On SGI Indys 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> + + <sect3 arch="mips"> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You don't have to configure DHCP in a special way because you'll pass the +full path of the file to the loaded to CFE. + +</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 new file mode 100644 index 000000000..246d831b8 --- /dev/null +++ b/nl/install-methods/ipl-tape.xml @@ -0,0 +1,24 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 new file mode 100644 index 000000000..a4269fed7 --- /dev/null +++ b/nl/install-methods/official-cdrom.xml @@ -0,0 +1,69 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 id="official-cdrom"> + <title>Official &debian; CD-ROM Sets</title> +<para> + +By far the easiest way to install &debian; 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 new file mode 100644 index 000000000..b6683f0ad --- /dev/null +++ b/nl/install-methods/tftp/bootp.xml @@ -0,0 +1,72 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 condition="supports-bootp" id="tftp-bootp"> + <title>Setting up BOOTP server</title> +<para> + +There are two BOOTP servers available for GNU/Linux, the CMU +<command>bootpd</command> and the other is actually a DHCP server, ISC +<command>dhcpd</command>, which are contained in the +<classname>bootp</classname> and <classname>dhcp</classname> packages +in &debian;. + +</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;, you can run <userinput>update-inetd --enable +bootps</userinput>, then <userinput>/etc/init.d/inetd +reload</userinput> to do so. Elsewhere, 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 Indys 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, and restart +<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd +restart</userinput>. + +</para> + </sect2> diff --git a/nl/install-methods/tftp/dhcp.xml b/nl/install-methods/tftp/dhcp.xml new file mode 100644 index 000000000..f51eb2622 --- /dev/null +++ b/nl/install-methods/tftp/dhcp.xml @@ -0,0 +1,97 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29400 untranslated --> + + <sect2 condition="supports-dhcp" id="dhcpd"> + <title>Setting up a DHCP server</title> +<para> + +One free software DHCP server is ISC <command>dhcpd</command>. +In &debian;, this is available in the <classname>dhcp</classname> package. +Here is a sample configuration file for it (usually +<filename>/etc/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/tftpboot.img"; + server-name "servername"; + next-server servername; + hardware ethernet 01:23:45:67:89:AB; + fixed-address 192.168.1.90; +} +</screen></informalexample> + +Note: the new (and preferred) <classname>dhcp3</classname> package uses +<filename>/etc/dhcp3/dhcpd.conf</filename>. + +</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/dhcpd restart</userinput>. + +</para> + + <sect3 arch="i386"> + <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 "/tftpboot/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 new file mode 100644 index 000000000..c6fd184d4 --- /dev/null +++ b/nl/install-methods/tftp/rarp.xml @@ -0,0 +1,64 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 condition="supports-rarp" id="tftp-rarp"> + <title>Setting up RARP server</title> +<para> + +To setup 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>/sbin/ifconfig eth0</userinput>. + +</para><para> + +On a RARP server system using a Linux 2.2.x kernel, +you need to populate the kernel's RARP table. +To do this, run the following commands: + +<informalexample><screen> +# <userinput>/sbin/rarp -s +<replaceable>client-hostname</replaceable> +<replaceable>client-enet-addr</replaceable></userinput> + +# <userinput>/usr/sbin/arp -s +<replaceable>client-ip</replaceable> +<replaceable>client-enet-addr</replaceable></userinput> +</screen></informalexample> + +If you get + +<informalexample><screen> +SIOCSRARP: Invalid argument +</screen></informalexample> + +you probably need to load the RARP kernel module or else recompile the +kernel to support RARP. Try <userinput>modprobe rarp</userinput> and +then try the <command>rarp</command> command again. + +</para><para> + +On a RARP server system using a Linux 2.4.x kernel, +there is no RARP module, and +you should instead use the <command>rarpd</command> program. The +procedure is similar to that used under SunOS in the following +paragraph. + +</para><para> + +Under SunOS, 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. +In SunOS 4, issue the command (as root): +<userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use +<userinput>/usr/sbin/rarpd -a</userinput>. + +</para> + </sect2> diff --git a/nl/install-methods/usb-setup/i386.xml b/nl/install-methods/usb-setup/i386.xml new file mode 100644 index 000000000..cbeab6250 --- /dev/null +++ b/nl/install-methods/usb-setup/i386.xml @@ -0,0 +1,101 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 27345 untranslated --> + + <sect3 arch="i386"> + <title>USB stick partitioning on &arch-title;</title> +<para> + +We will show how to setup 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 for creating a FAT16 partition and then +create the filesystem using: + +<informalexample><screen> +# mkdosfs /dev/<replaceable>sda1</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. <command>LILO</command>) should work, it's convenient to use +<command>SYSLINUX</command>, 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 <command>SYSLINUX</command> 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>sda1</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><para> + +Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and +copy the following files from the Debian archives to the stick: + +<itemizedlist> +<listitem><para> + +<filename>vmlinuz</filename> (kernel binary) + +</para></listitem> +<listitem><para> + +<filename>initrd.gz</filename> (initial ramdisk image) + +</para></listitem> +<listitem><para> + +<filename>syslinux.cfg</filename> (SYSLINUX configuration file) + +</para></listitem> +<listitem><para> + +Optional kernel modules + +</para></listitem> +</itemizedlist> + +If you want to rename the files, please note that +<command>SYSLINUX</command> can only process DOS (8.3) file names. + +</para><para> + +The <filename>syslinux.cfg</filename> configuration file should +contain the following two lines: + +<informalexample><screen> +default vmlinuz +append initrd=initrd.gz ramdisk_size=12000 root=/dev/rd/0 init=/linuxrc rw +</screen></informalexample> + +Please note that the <userinput>ramdisk_size</userinput> parameter +may need to be increased, depending on the image you are booting. +<phrase condition="sarge"> +If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> +to the <quote>append</quote> line. +</phrase> + +</para> + </sect3> diff --git a/nl/install-methods/usb-setup/powerpc.xml b/nl/install-methods/usb-setup/powerpc.xml new file mode 100644 index 000000000..36c572fa4 --- /dev/null +++ b/nl/install-methods/usb-setup/powerpc.xml @@ -0,0 +1,111 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 27345 untranslated --> + + <sect3 arch="powerpc"> + <title>USB stick partitioning on &arch-title;</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/sda</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>sda2</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/sda2 +$ 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><para> + +Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and +copy the following files from the Debian archives 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> +<listitem><para> + +Optional kernel modules + +</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<phrase condition="sarge"> + append="devfs=mount,dall --"</phrase> + 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> + </sect3> diff --git a/nl/partitioning/device-names.xml b/nl/partitioning/device-names.xml new file mode 100644 index 000000000..49effd568 --- /dev/null +++ b/nl/partitioning/device-names.xml @@ -0,0 +1,161 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect1 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. + +<phrase arch="m68k"> +The letters may differ from what shows in the mac program pdisk +(i.e. what shows up as <filename>/dev/hdc</filename> on pdisk may show +up as <filename>/dev/hda</filename> in Debian). +</phrase> + +</para></listitem> + +<listitem arch="i386"><para> + +The first XT disk is named <filename>/dev/xda</filename>. + +</para></listitem> +<listitem arch="i386"><para> + +The second XT disk is named <filename>/dev/xdb</filename>. + +</para></listitem> +<listitem arch="m68k"><para> + +The first ACSI device is named <filename>/dev/ada</filename>, the +second is named <filename>/dev/adb</filename>. + +</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="i386"> + +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="m68k"> + +VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal +SCSI disk. To make identification of the drive simpler the installation +software will create a symbolic link to the appropriate device and name +it <filename>/dev/sfd0</filename>. + +</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 new file mode 100644 index 000000000..c0b5bdaf7 --- /dev/null +++ b/nl/partitioning/partition-programs.xml @@ -0,0 +1,169 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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="i386"> (<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 a Hard Disk</guimenuitem>. If the one which is run +by default isn't the one you want, quit the partitioner, go to the shell +(<userinput>tty2</userinput>) by pressing <keycap>Alt</keycap> +and <keycap>F2</keycap> keys together, and manually type in the +name of the program you want to use (and arguments, if any). Then +skip the <guimenuitem>Partition a Hard Disk</guimenuitem> step in +<command>debian-installer</command> and continue to the next step. + +</para><para> + +If you will be working with more than 20 partitions on your ide disk, +you will need to create devices for partitions 21 and beyond. The next +step of initializing the partition will fail unless a proper device is +present. As an example, here are commands you can use in +<userinput>tty2</userinput> or under Execute A Shell to add a device +so the 21st partition can be initialized: + +<informalexample><screen> +# cd /dev +# mknod hda21 b 3 21 +# chgrp disk hda21 +# chmod 660 hda21 +</screen></informalexample> + +Booting into the new system will fail unless proper devices are present +on the target system. After installing the kernel and modules, execute: + +<informalexample><screen> +# cd /target/dev +# mknod hda21 b 3 21 +# chgrp disk hda21 +# chmod 660 hda21 +</screen></informalexample> + +<phrase arch="i386">Remember to mark your boot partition as +<quote>Bootable</quote>.</phrase> + +</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-alpha.xml; +&partition-hppa.xml; +&partition-i386.xml; +&partition-ia64.xml; +&partition-mips.xml; +&partition-powerpc.xml; +&partition-sparc.xml; + + </sect1> diff --git a/nl/partitioning/partition/alpha.xml b/nl/partitioning/partition/alpha.xml new file mode 100644 index 000000000..240e7bd3d --- /dev/null +++ b/nl/partitioning/partition/alpha.xml @@ -0,0 +1,58 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="alpha"><title>Partitioning for &arch-title;</title> +<para> + +Booting Debian from the SRM console (the only disk boot method supported +by &releasename;) requires you to have a BSD disk label, not a DOS +partition table, on your boot disk. (Remember, the SRM boot block is +incompatible with MS-DOS partition tables — see +<xref linkend="alpha-firmware"/>.) As a result, <command>partman</command> +creates BSD disk labels when running on &architecture;, but if your disk +has an existing DOS partition table the existing partitions will need to +be deleted before partman can convert it to use a disk label. + +</para><para> + +If you have chosen to use <command>fdisk</command> to partition your +disk, and the disk that you have selected for partitioning does not +already contain a BSD disk label, you must use the <quote>b</quote> +command to enter disk label mode. + +</para><para> + +Unless you wish to use the disk you are partitioning from Tru64 Unix +or one of the free 4.4BSD-Lite derived operating systems (FreeBSD, +OpenBSD, or NetBSD), it is suggested that you do +<emphasis>not</emphasis> make the third partition contain the whole +disk. This is not required by <command>aboot</command>, and in fact, +it may lead to confusion since the <command>swriteboot</command> +utility used to install <command>aboot</command> in the boot sector +will complain about a partition overlapping with the boot block. + +</para><para> + +Also, because <command>aboot</command> is written to the first few +sectors of the disk (currently it occupies about 70 kilobytes, or 150 +sectors), you <emphasis>must</emphasis> leave enough empty space at +the beginning of the disk for it. In the past, it was suggested that +you make a small partition at the beginning of the disk, to be left +unformatted. For the same reason mentioned above, we now suggest that +you do not do this on disks that will only be used by GNU/Linux. When +using <command>partman</command>, a small partition will still be +created for <command>aboot</command> for convenience reasons. + +</para><para condition="FIXME"> + +For ARC installations, you should make a small FAT partition at the +beginning of the disk to contain <command>MILO</command> and +<command>linload.exe</command> — 5 megabytes should be sufficient, see +<xref linkend="non-debian-partitioning"/>. Unfortunately, making FAT +file systems from the menu is not yet supported, so you'll have to do +it manually from the shell using <command>mkdosfs</command> before +attempting to install the boot loader. + +</para> + </sect2> diff --git a/nl/partitioning/partition/hppa.xml b/nl/partitioning/partition/hppa.xml new file mode 100644 index 000000000..521a5e848 --- /dev/null +++ b/nl/partitioning/partition/hppa.xml @@ -0,0 +1,22 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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 you might wish load; 8–16MB is generally +sufficient. + +</para> + </sect2> diff --git a/nl/partitioning/partition/i386.xml b/nl/partitioning/partition/i386.xml new file mode 100644 index 000000000..c4d621477 --- /dev/null +++ b/nl/partitioning/partition/i386.xml @@ -0,0 +1,94 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="i386"><title>Partitioning for &arch-title;</title> +<para> + +If you have an existing other operating system such as DOS or Windows and +you want to preseve 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 to partition +manually 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> + +Linux limits the partitions per drive to 15 partitions for SCSI disks +(3 usable primary partitions, 12 logical partitions), and 63 +partitions on an IDE drive (3 usable primary partitions, 60 logical +partitions). However the normal &debian; 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 Linux is booted, no matter what BIOS your computer +has, these restrictions no longer apply, since Linux 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 (5–10MB +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 Linux 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/partition/ia64.xml b/nl/partitioning/partition/ia64.xml new file mode 100644 index 000000000..1dc42db62 --- /dev/null +++ b/nl/partitioning/partition/ia64.xml @@ -0,0 +1,125 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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 is properly configured for a successful +installation. It actually uses the <command>parted</command> to +do the on-disk partitioning. + +</para> + + <note> + <title>EFI Recognized Formats</title> +<para> + +The IA64 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 IA64 systems. Although +the installer also provides the <command>cfdisk</command>, +you should only use the <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 ia64 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 new file mode 100644 index 000000000..fa135ab9b --- /dev/null +++ b/nl/partitioning/partition/mips.xml @@ -0,0 +1,16 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="mips"><title>Partitioning for &arch-title;</title> +<para> + +SGI Indys 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 new file mode 100644 index 000000000..99e8324ee --- /dev/null +++ b/nl/partitioning/partition/powerpc.xml @@ -0,0 +1,57 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 23146 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 be 800KB 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; 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 new file mode 100644 index 000000000..f4996a519 --- /dev/null +++ b/nl/partitioning/partition/sparc.xml @@ -0,0 +1,33 @@ +<!-- 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/partitioning.xml b/nl/partitioning/partitioning.xml new file mode 100644 index 000000000..1ac85cf9b --- /dev/null +++ b/nl/partitioning/partitioning.xml @@ -0,0 +1,13 @@ +<!-- 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 new file mode 100644 index 000000000..64f99c2db --- /dev/null +++ b/nl/partitioning/schemes.xml @@ -0,0 +1,84 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 31069 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 to 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 arch="m68k"> + +On the other hand, Atari Falcons and Macs feel pain when swapping, so +instead of making a large swap partition, get as much RAM as possible. + +</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 new file mode 100644 index 000000000..3a7441dc6 --- /dev/null +++ b/nl/partitioning/sizing.xml @@ -0,0 +1,52 @@ +<!-- 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/Linux 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, Linux can make much +more efficient use of it. It is possible to force Linux to use a +regular file as swap, but it is not recommended. + +</para><para> + +Most people choose to give GNU/Linux 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/Linux 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 new file mode 100644 index 000000000..8317cec8b --- /dev/null +++ b/nl/partitioning/tree.xml @@ -0,0 +1,150 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect1 id="directory-tree"> + <title>The Directory Tree</title> +<para> + +&debian; 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>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–250 MB 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 500 MB 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-6 GB. + +</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 gigabyte 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–100 MB 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 100 MB 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 (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 new file mode 100644 index 000000000..4c9ad4b8a --- /dev/null +++ b/nl/post-install/further-reading.xml @@ -0,0 +1,49 @@ +<!-- 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> + +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 new file mode 100644 index 000000000..cc4c7bed7 --- /dev/null +++ b/nl/post-install/kernel-baking.xml @@ -0,0 +1,182 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + <sect1 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. However, it is 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> + +handle hardware or options not included in the stock kernel, such as +APM or SMP + +</para></listitem> +<listitem><para> + +optimize the kernel by removing useless drivers to speed up boot +time + +</para></listitem> +<listitem><para> + +use options of the kernel which are not supported by the default +kernel (such as high memory support) + +</para></listitem> +<listitem><para> + +run an updated or development kernel + +</para></listitem> +<listitem><para> + +impress your friends, try new things + +</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>kernel-package</classname>, +<classname>kernel-source-&kernelversion;</classname> (the most recent version +at the time of this writing), <classname>fakeroot</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>kernel-source-&kernelversion;</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/kernel-source-&kernelversion;.tar.bz2</userinput> and change +to the directory <filename>kernel-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 --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 condition="supports-pcmcia"> + +If you require PCMCIA support, you'll also need to install the +<classname>pcmcia-source</classname> package. Unpack the gzipped tar file +as root in the directory <filename>/usr/src</filename> (it's important that +modules are found where they are expected to be found, namely, +<filename>/usr/src/modules</filename>). Then, as root, do <userinput>make-kpkg +modules_image</userinput>. + +</para><para> + +Once the compilation is complete, you can install your custom kernel +like any package. As root, do <userinput>dpkg -i +../kernel-image-&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>i586</quote>, </phrase> +depending on what kernel options you set. +<userinput>dpkg -i kernel-image...</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 +<classname>kernel-image-&kernelversion;</classname> package is also clever +enough to automatically use your platform's boot-loader to run an +update on the booting, allowing you to boot without re-running the +boot loader. If you have created a modules package, e.g., if you have +PCMCIA, 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 <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/new-to-unix.xml b/nl/post-install/new-to-unix.xml new file mode 100644 index 000000000..c918d4d2a --- /dev/null +++ b/nl/post-install/new-to-unix.xml @@ -0,0 +1,29 @@ +<!-- 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> + +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 new file mode 100644 index 000000000..7c9b75a78 --- /dev/null +++ b/nl/post-install/orientation.xml @@ -0,0 +1,109 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 31137 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 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 new file mode 100644 index 000000000..59c327813 --- /dev/null +++ b/nl/post-install/post-install.xml @@ -0,0 +1,14 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28715 untranslated --> + +<chapter id="post-install"> + <title>Next Steps and Where to Go From Here</title> + +&new-to-unix.xml; +&orientation.xml; +&reactivating-win.xml; +&further-reading.xml; +&kernel-baking.xml; +&rescue.xml; + +</chapter> diff --git a/nl/post-install/reactivating-win.xml b/nl/post-install/reactivating-win.xml new file mode 100644 index 000000000..e34f01d12 --- /dev/null +++ b/nl/post-install/reactivating-win.xml @@ -0,0 +1,72 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect1 arch="i386" id="reactivating-win"> + <title>Reactivating DOS and Windows</title> +<para> + +After installing the base system and writing to the <emphasis>Master Boot +Record</emphasis>, you will be able to boot Linux, but probably nothing else. +This depends what you have chosen during the installation. This chapter +will describe how you can reactivate your old systems so that you can also +boot your DOS or Windows again. + +</para><para> + +<command>LILO</command> is a boot manager with which you can also boot +other operating systems than Linux, which complies to PC +conventions. The boot manager is configured via +<filename>/etc/lilo.conf</filename> file. Whenever you edited this +file you have to run <command>lilo</command> afterwards. The reason +for this is that the changes will take place only when you call the +program. + +</para><para> + +Important parts of the <filename>lilo.conf</filename> file are the +lines containing the <userinput>image</userinput> and +<userinput>other</userinput> keywords, as well as the lines following +those. They can be used to describe a system which can be booted by +<command>LILO</command>. Such a system can include a kernel +(<userinput>image</userinput>), a root partition, additional kernel +parameters, etc. as well as a configuration to boot another, non-Linux +(<userinput>other</userinput>) operating system. These keywords can +also be used more than once. The ordering of these systems within the +configuration file is important because it determines which system +will be booted automatically after, for instance, a timeout +(<userinput>delay</userinput>) presuming <command>LILO</command> +wasn't stopped by pressing the <keycap>shift</keycap> key. + +</para><para> + +After a fresh install of Debian, just the current system is configured +for booting with <command>LILO</command>. If you want to boot another +Linux kernel, you have to edit the configuration file +<filename>/etc/lilo.conf</filename> to add the following lines: + +<informalexample><screen> +&additional-lilo-image; +</screen></informalexample> + +For a basic setup just the first two lines are necessary. If you want +to know more about the other two options please have a look at the +<command>LILO</command> documentation. This can be found in +<filename>/usr/share/doc/lilo/</filename>. The file which should be +read is <filename>Manual.txt</filename>. To have a quicker start into +the world of booting a system you can also look at the +<command>LILO</command> man pages <filename>lilo.conf</filename> for +an overview of configuration keywords and <filename>lilo</filename> +for description of the installation of the new configuration into the +boot sector. + +</para><para> + +Notice that there are other boot loaders available in &debian;, such as +GRUB (in <classname>grub</classname> package), +CHOS (in <classname>chos</classname> package), +Extended-IPL (in <classname>extipl</classname> package), +loadlin (in <classname>loadlin</classname> package) etc. + +</para> + </sect1> diff --git a/nl/post-install/rescue.xml b/nl/post-install/rescue.xml new file mode 100644 index 000000000..f785258fd --- /dev/null +++ b/nl/post-install/rescue.xml @@ -0,0 +1,71 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28732 untranslated --> + + <sect1 id="rescue" condition="etch"> + <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="i386"> +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 new file mode 100644 index 000000000..e326be12d --- /dev/null +++ b/nl/post-install/shutdown.xml @@ -0,0 +1,25 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 21690 untranslated --> + + + <sect1 id="shutdown"> + <title>Shutting Down the System</title> + +<para> + +To shut down a running Linux system, you must not reboot with the +reset switch on the front or back of your computer, or just turn off +the computer. Linux must be shut down in a controlled manner, +otherwise files may be lost and disk damage incurred. You can press +the key combination <keycombo> <keycap>Ctrl</keycap> +<keycap>Alt</keycap> <keycap>Del</keycap> </keycombo> +<phrase arch="powerpc;m68k"> or <keycombo> <keycap>Control</keycap> +<keycap>Shift</keycap> <keycap>Power</keycap> </keycombo> on Macintosh +systems</phrase>. You may also log in as +root and type <userinput>shutdown -h now</userinput>, +<userinput>reboot</userinput>, or <userinput>halt</userinput> if +either of the key combinations do not work or you prefer to type +commands. + +</para> + </sect1> diff --git a/nl/preface.xml b/nl/preface.xml new file mode 100644 index 000000000..36b832a6b --- /dev/null +++ b/nl/preface.xml @@ -0,0 +1,31 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 24750 --> + +<preface> + <title>&debian; &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/Linux distributie van Debian uniek +is. &debian; 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 new file mode 100644 index 000000000..55e7d2616 --- /dev/null +++ b/nl/preparing/backup.xml @@ -0,0 +1,48 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28997 --> + + <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;. 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> + +<para arch="m68k"> + +Met uitzondering van BVM en Motorola VMEbus computers, is de enige +installatiemethode die voor m68k-systemen wordt ondersteund, het opstarten +met een op AmigaOS/TOS/MacOS gebaseerde bootstrap vanaf een lokale harde +schijf of diskette. Voor deze systemen heeft u het originele besturingssysteem +nodig om Linux te kunnen opstarten. Om Linux te kunnen opstarten op de BVM and +Motorola VMEbus machines, heeft u de boot-ROMs <quote>BVMBug</quote> of +<quote>16xBug</quote> nodig. + +</para> + + </sect1> diff --git a/nl/preparing/bios-setup/i386.xml b/nl/preparing/bios-setup/i386.xml new file mode 100644 index 000000000..668d4ed20 --- /dev/null +++ b/nl/preparing/bios-setup/i386.xml @@ -0,0 +1,332 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="i386" 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 set-up menu, which is used to configure the BIOS. +Before installing, you <emphasis>must</emphasis> ensure that your BIOS +is setup 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="i386" id="boot-dev-select"><title>Boot Device Selection</title> + +<para> + +Many BIOS set-up 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> + +Other popular option is to boot from a USB storage (also called USB +memory stick or USB key). 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. + +</para><para> + +Here are some details about how to set the boot order. Remember to +reset the boot order after Linux 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="i386"> + <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. Linux 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/Linux. These aren't +compatible with GNU/Linux; moreover, due to the file system +permissions and protected memory of the Linux 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 Linux 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. Linux 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 Linux 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. Linux 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. Linux 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/m68k.xml b/nl/preparing/bios-setup/m68k.xml new file mode 100644 index 000000000..e68cb35d7 --- /dev/null +++ b/nl/preparing/bios-setup/m68k.xml @@ -0,0 +1,23 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="m68k" id="firmware-revs"> + <title>Firmware Revisions and Existing OS Setup</title> + +<para> + +&arch-title; machines are generally self-configuring and do not require +firmware configuration. However, you should make sure that you have +the appropriate ROM and system patches. On the Macintosh, MacOS +version >= 7.1 is recommended because version 7.0.1 contains a bug in +the video drivers preventing the boot loader from deactivating the +video interrupts, resulting in a boot hang. On the BVM VMEbus systems +you should make sure you are using BVMBug revision G or higher boot ROMs. +The BVMBug boot ROMs do not come as standard on the BVM systems but are +available from BVM on request free of charge. + +</para> + + </sect2> + diff --git a/nl/preparing/bios-setup/powerpc.xml b/nl/preparing/bios-setup/powerpc.xml new file mode 100644 index 000000000..2368a0853 --- /dev/null +++ b/nl/preparing/bios-setup/powerpc.xml @@ -0,0 +1,52 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 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</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 +Save 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 new file mode 100644 index 000000000..b2ed18855 --- /dev/null +++ b/nl/preparing/bios-setup/s390.xml @@ -0,0 +1,106 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28672 untranslated --> + + + <sect2 arch="s390"><title>BIOS Setup</title> +<para> + +In order to install &debian; 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 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 do you +find them. Based on both sources of information you have to prepare +your machine and the installation medium and to perform a boot from +it. When you see the welcome message in your client session join this +document again for 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; mirror but of 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 new file mode 100644 index 000000000..591ea1415 --- /dev/null +++ b/nl/preparing/bios-setup/sparc.xml @@ -0,0 +1,103 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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, simple scripts, etc. + +</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 much 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 device 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 new file mode 100644 index 000000000..9cc19450f --- /dev/null +++ b/nl/preparing/install-overview.xml @@ -0,0 +1,206 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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; 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; en/of uw +bestaande systeem kan opstarten. + +</para></listitem> +<listitem><para> + +Start de computer opnieuw op met het nieuw geïnstalleerde systeem en verzorg +enkele initiële systeeminstellingen. + +</para></listitem> +<listitem arch="s390"><para> + +Open een ssh-verbinding met het nieuwe systeem. + +</para></listitem> +<listitem><para> + +Installeer aanvullende software (<firstterm>taken</firstterm> +en/of <firstterm>pakketten</firstterm>), conform uw eigen wensen. + +</para></listitem> +</orderedlist> + +<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> + +Nadat uw nieuwe basissysteem is geladen, draagt +<classname>base-config</classname> zorg voor het aanmaken van gebruikers, +het instellen van de tijdzone (via <classname>tzsetup</classname>) en het +configureren van het installatiesysteem voor pakketten (gebruik makend van +<classname>apt-setup</classname>). Vervolgens wordt <classname>tasksel</classname> +gestart waarmee u grote groepen gerelateerde programma's kunt selecteren voor +installatie en waarbinnen u desgewenst <classname>aptitude</classname> kan startem +waarmee u individuele programma's kunt selecteren. + +<!-- FJP Ik mis hier een beschrijving (of afzonderlijke stap)van het daadwerkelijk +installeren van de geselecteerde pakketten. //--> + +</para><para> + +Als <classname>debian-installer</classname> klaar is, beschikt u slechts +over een zeer eenvoudig systeem dat opdrachtregel-gestuurd is. De grafische +gebruikersinterface die 'windows' op uw beeldscherm weergeeft (onder Linux het +'X Window System' genaamd), wordt niet geïnstalleerd tenzij u het selecteert +voor installatie. Dit kunt u doen tijdens de laatste stappen van het +installatieproces, dus ofwel met <classname>tasksel</classname> ofwel met +<classname>aptitude</classname>. Installatie van het X Window System is +optioneel omdat veel &debian; systemen in gebruik zijn als server die voor +het vervullen van hun taak eigenlijk geen behoefte hebben aan een grafische +gebruikersinterface. +<!-- FJP Origineel is voor verbeteringen vatbaar: +- wat is het doel van de tussenzin 'before the first system load'; +- X Window System kan beter geïntroduceerd worden (naamgeving consequent!). +Is mijn vrije vertaling een verbetering? +Zou dit hele onderwerp niet beter eerder in de handleiding behandeld kunnen worden? //--> + +</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 new file mode 100644 index 000000000..9866cec25 --- /dev/null +++ b/nl/preparing/minimum-hardware-reqts.xml @@ -0,0 +1,135 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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="i386"> + +Voor desktop systemen wordt tenminste een Pentium 100 aanbevolen; voor +een server tenminste een Pentium II-300. + +</para><para arch="m68k"> + +Voor m68k installaties wordt een 68030 of betere processor aanbevolen. +Het is mogelijk dat u met wat minder schijfruimte kunt volstaan dan aangegeven. + +</para><para arch="powerpc"> + +Een willekeurige 'OldWorld' of 'NewWorld' PowerPC kan goed dienst doen als +desktop systeem. Voor servers wordt tenminste een 132 Mhz machine aangeraden. + +</para> + +<table> +<title>Aanbevolen minimum systeemeisen</title> +<tgroup cols="3"> +<thead> +<row> + <entry>Type installatie</entry><entry>RAM</entry><entry>Harde schijf</entry> +</row> +</thead> + +<tbody> +<row> + <entry>Geen desktop</entry> + <entry>24 megabytes</entry> + <entry>450 megabytes</entry> +</row><row> + <entry>Met desktop</entry> + <entry>64 megabytes</entry> + <entry>1 gigabyte</entry> +</row><row> + <entry>Server</entry> + <entry>128 megabytes</entry> + <entry>4 gigabytes</entry> +</row> + +</tbody></tgroup></table> + +<para> + +Hieronder vindt u een selectie van gangbare Debian systeemconfiguraties. +U kunt ook een beeld krijgen van de schijfruimte die benodigd is voor +aan elkaar gerelateerde groepen programma's door +<xref linkend="tasksel-size-list"/> te raadplegen. + +</para> +<variablelist> + +<varlistentry> + <term>Standaard server</term> + <listitem><para> + +Dit is een profiel voor een kleine server. Het is bruikbaar voor een +uitgekleedde server die niet veel aardigheden heeft voor shell-gebruikers. +Het profiel omvat een FTP-server, een webserver, DNS, NIS en POP. Hiervoor +zou 100MB schijfruimte volstaan; daarbij dient u vervolgens de ruimte voor +de 'te serveren' gegevens op te tellen. +<!-- FJP Naar mijn mening zijn deze profielen niet meer van deze tijd. //--> + +</para></listitem> +</varlistentry> + +<varlistentry arch="not-s390"> + <term>Desktop</term> + <listitem><para> + +Een standaard desktop machine, inclusief het X Window System, complete desktop +omgevingen, geluid, tekstbewerkers, enzovoorts. Als U de standaard Desktop taak +gebruikt, zult u ongeveer 2GB nodig hebben; het is echter mogelijk om het met +veel minder te doen. + +</para></listitem> +</varlistentry> + +<varlistentry arch="not-s390"> + <term>Werkstation</term> + <listitem><para> + +Een meer uitgekleedde machine voor een gebruiker: zonder het X Window System +of X-toepassingen. Mogelijk toepasbaar voor een laptop of mobiele computer. +De grootte is ongeveer 140MB. + +</para></listitem> +</varlistentry> + +<varlistentry> + <term>Ontwikkelaar</term> + <listitem><para> + +Een inrichting voor een desktop met alle pakketten voor systeemontwikkeling, +zoals Perl, C, C++, enzovoorts. Grootte is ongeveer 475MB. Aangenomen dat u +ook X11 en aanvullende pakketten voor ander gebruik toevoegt, moet u rekening +houden met 800MB voor dit type machine. + +</para></listitem> +</varlistentry> + +</variablelist><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. 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 20MB gebruiken. +Verder worden hier door <command>apt-get</command> pakketten die gedownload +worden, opgeslagen voordat deze worden geïnstalleerd. Normaal gesproken dient +u tenminste 100MB te reserveren voor <filename>/var</filename>. +<!-- FJP 'var' hoeft toch niet een afzonderlijke partitie te zijn? //--> + +</para> + + </sect1> diff --git a/nl/preparing/needed-info.xml b/nl/preparing/needed-info.xml new file mode 100644 index 000000000..ed2574a07 --- /dev/null +++ b/nl/preparing/needed-info.xml @@ -0,0 +1,415 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 31136 --> + + <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="i386;m68k;alpha;sparc;mips;mipsel"> +<listitem arch="i386"><para> + +<ulink url="&url-hardware-howto;">Linux Hardware Compatibility HOWTO</ulink> + +</para></listitem> + +<listitem arch="m68k"><para> + +<ulink url="&url-m68k-faq;">Linux/m68k FAQ</ulink> + +</para></listitem> + +<listitem arch="alpha"><para> + +<ulink url="&url-alpha-faq;">Linux/Alpha FAQ</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-mips-howto;">Linux/Mips Howto</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="i386"><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 of SCSI (de meeste computers hebben IDE).</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 Linux. Sterker nog, +de ondersteuning van apparatuur binnen Linux verbetert met de dag. +Toch ondersteunt Linux nog niet dezelfde variëteit aan apparatuur als +sommige andere besturingssystemen. +<!-- s/hardware for/hardware support for/ ? //--> + +</para><para arch="i386"> + +In het bijzonder kan Linux geen hardware aansturen die vereist dat +een versie van Microsoft Windows actief is. + +</para><para arch="i386"> + +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="i386"> + +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 Linux 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 condition="supports-dhcp"> + +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 new file mode 100644 index 000000000..1cb00e460 --- /dev/null +++ b/nl/preparing/non-debian-partitioning.xml @@ -0,0 +1,207 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28997 --> + + <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="i386"> +(Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) +</phrase> + +<phrase arch="alpha"> +(Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) +</phrase> + +<phrase arch="s390"> +(VM, z/OS, OS/390, …) +</phrase> + +<phrase arch="m68k"> +(Amiga OS, Atari TOS, Mac OS, …) +</phrase> + +en u wilt Linux 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 Linux 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="i386">, zoals fdisk of PartitionMagic</phrase><phrase +arch="powerpc">, zoals Drive Setup, HD Toolkit of MacTools</phrase><phrase +arch="m68k">, zoals HD SC Setup, HDToolBox of SCSITool</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;, kunt u eveneens het +indelen van de schijf uitstellen tot tijdens de installatieprocedure +(<xref linkend="partman"/>), 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="i386"> + +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; 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 Linux. Windows en andere besturingssystemen kunnen de +mogelijkheid om Linux 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; automatisch te laten opstarten door OpenFirmware, dienen de +Linux 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 Linux 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 Linux 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; +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-alpha.xml; +&nondeb-part-i386.xml; +&nondeb-part-m68k.xml; +&nondeb-part-sparc.xml; +&nondeb-part-powerpc.xml; + + </sect1> diff --git a/nl/preparing/nondeb-part/alpha.xml b/nl/preparing/nondeb-part/alpha.xml new file mode 100644 index 000000000..de065da6d --- /dev/null +++ b/nl/preparing/nondeb-part/alpha.xml @@ -0,0 +1,83 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="alpha"><title>Partitioning in Tru64 UNIX</title> +<para> + +Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly +known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk +label</quote>, which allows for up to eight partitions per disk drive. The +partitions are numbered <quote>1</quote> through to <quote>8</quote> in +Linux and <quote>lettered</quote> <quote>a</quote> through to +<quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond +<quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> +and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most +likely be called <filename>sda5</filename> in Linux. + +</para><para> + +Partitions in a Tru64 disk label may overlap. Moreover, if this disk +will be used from Tru64, the <quote>c</quote> partition is required to span +the entire disk (thus overlapping all other non-empty partitions). Under +Linux this makes <filename>sda3</filename> identical to +<filename>sda</filename> (<filename>sdb3</filename> to +<filename>sdb</filename>, if present, and so on). However, the partman +partitioning tool used by &d-i; cannot handle overlapping partitions at +present. As a result, it is currently not recommended to share disks +between Tru64 and Debian. Partitions on Tru64 disks can be mounted +under Debian after installation has been completed. + +</para><para> + +Another conventional requirement is for the <quote>a</quote> partition to +start from the beginning of the disk, so that it always includes the boot +block with the disk label. If you intend to boot Debian from that disk, you +need to size it at least 2MB to fit aboot and perhaps a kernel. +Note that this partition is only required for compatibility; you must +not put a file system onto it, or you'll destroy data. + +</para><para> + +It is possible, and indeed quite reasonable, to share a swap partition +between UNIX and Linux. In this case it will be needed to do a +<command>mkswap</command> on that partition every time the system is rebooted +from UNIX into Linux, as UNIX will damage the swap signature. You may +want to run <command>mkswap</command> from the Linux start-up scripts before +adding swap space with <command>swapon -a</command>. + +</para><para> + +If you want to mount UNIX partitions under Linux, note that Digital UNIX +can use two different file system types, UFS and AdvFS, of which Linux +only understands the former. + +</para> + </sect2> + + <sect2 arch="alpha"><title>Partitioning in Windows NT</title> + +<para> + +Windows NT uses the PC-style partition table. If you are manipulating +existing FAT or NTFS partitions, it is recommended that you use the +native Windows NT tools (or, more conveniently, you can also +repartition your disk from the AlphaBIOS setup menu). Otherwise, it +is not really necessary to partition from Windows; the Linux +partitioning tools will generally do a better job. Note that when you +run NT, the Disk Administrator may offer you to write a <quote>harmless +signature</quote> on non-Windows disks if you have any. +<emphasis>Never</emphasis> let it do that, as this signature will destroy +the partition information. + +</para><para> + +If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you +will need a (small) FAT partition for MILO. 5 MB is quite +sufficient. If Windows NT is installed, its 6 MB bootstrap partition +can be employed for this purpose. Debian &releasename; does not support +installing MILO. If you already have MILO installed on your system, or +install MILO from other media, Debian can still be booted from ARC. + +</para> + </sect2> diff --git a/nl/preparing/nondeb-part/i386.xml b/nl/preparing/nondeb-part/i386.xml new file mode 100644 index 000000000..b89864d7e --- /dev/null +++ b/nl/preparing/nondeb-part/i386.xml @@ -0,0 +1,120 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 29561 untranslated --> + + + <sect2 arch="i386"><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 Linux partitioning tools will generally do a better +job. + +</para><para> + +But if you have a large IDE disk, and are using neither LBA addressing, +overlay drivers (sometimes provided by hard disk manufacturers), nor 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 drive (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), 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, select the option to <menuchoice> <guimenuitem>Manually +edit partition table</guimenuitem> </menuchoice>, 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 Linux 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. Do this +prior to running DOS's <command>format</command> command, from Linux: + +<informalexample><screen> +# dd if=/dev/zero of=/dev/hdXX bs=512 count=4 +</screen></informalexample> + +</para> + </sect3> + </sect2> diff --git a/nl/preparing/nondeb-part/m68k.xml b/nl/preparing/nondeb-part/m68k.xml new file mode 100644 index 000000000..dbea5b44e --- /dev/null +++ b/nl/preparing/nondeb-part/m68k.xml @@ -0,0 +1,127 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 untranslated --> + + + <sect2 arch="m68k"><title>Partitioning in AmigaOS</title> +<para> + +If you are running AmigaOS, you can use the <command>HDToolBox</command> +program to adjust your native partitions prior to installation. + +</para> + </sect2> + + <sect2 arch="m68k"><title>Partitioning in Atari TOS</title> +<para> + +Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for +data and <quote>SWP</quote> for swap partitions. If using the low memory +installation method, a small Minix partition is also needed (about 2 MB), +for which the partition ID is <quote>MNX</quote>. Failure to set the +appropriate partition IDs not only prevents the Debian installation process +from recognizing the partitions, but also results in TOS attempting to use +the Linux partitions, which confuses the hard disk driver and renders the +whole disk inaccessible. + +</para><para> + +There are a multitude of third party partitioning tools available (the +Atari <command>harddisk</command> utility doesn't permit changing the +partition ID); this manual cannot give detailed descriptions for all +of them. The following description covers <command>SCSITool</command> (from +Hard+Soft GmBH). + +<orderedlist> +<listitem><para> + +Start <command>SCSITool</command> and select the disk you want to partition +(<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>). + +</para></listitem> +<listitem><para> + +From the <guimenu>Partition</guimenu> menu, select either +<guimenuitem>New</guimenuitem> to add new partitions or change the +existing partition sizes, or <guimenuitem>Change</guimenuitem> to +change one specific partition. Unless you have already created +partitions with the right sizes and only want to change the partition +ID, <guimenuitem>New</guimenuitem> is probably the best choice. + +</para></listitem> +<listitem><para> + +For the <guimenuitem>New</guimenuitem> choice, select +<guilabel>existing</guilabel> in the dialog box +prompting the initial settings. The next window shows a list of +existing partitions which you can adjust using the scroll buttons, or +by clicking in the bar graphs. The first column in the partition list +is the partition type; just click on the text field to edit it. When +you are finished changing partition settings, save the changes by +leaving the window with the <guibutton>OK</guibutton> button. + +</para></listitem> +<listitem><para> + +For the <guimenuitem>Change</guimenuitem> option, select the partition +to change in the selection list, and select <guilabel>other +systems</guilabel> in the dialog box. The +next window lists detailed information about the location of this +partition, and lets you change the partition ID. Save changes by +leaving the window with the <guibutton>OK</guibutton> button. + +</para></listitem> +<listitem><para> + +Write down the Linux names for each of the partitions you created or +changed for use with Linux — see <xref linkend="device-names"/>. + +</para></listitem> +<listitem><para> + +Quit <command>SCSITool</command> using the +<guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> +menu. The computer will reboot to make sure the changed partition +table is used by TOS. If you changed any TOS/GEM partitions, they will +be invalidated and have to be reinitialized (we told you to back up +everything on the disk, didn't we?). + +</para></listitem> +</orderedlist> + +</para><para> + +There is a partitioning tool for Linux/m68k called +<command>atari-fdisk</command> in the installation system, but for now we +recommend you partition your disk using a TOS partition editor or some +disk tool. If your partition editor doesn't have an option to edit the +partition type, you can do this crucial step at a later stage (from +the booted temporary install RAMdisk). <command>SCSITool</command> is only +one of the partition editors we know of which supports selection of +arbitrary partition types. There may be others; select the tool that +suits your needs. + +</para> +</sect2> + + <sect2 arch="m68k"><title>Partitioning in MacOS</title> +<para> + +Partitioning tools for Macintosh tested include <command>pdisk</command>, +<command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), +<command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim +Endres, GPL). Full versions are required for <command>HDT</command> and +<command>SilverLining</command>. The Apple tool requires a patch in order +to recognize third-party disks (a description on how to patch <command>HD +SC Setup</command> using <command>ResEdit</command> can be found at +<ulink url="http://www.euronet.nl/users/ernstoud/patch.html"></ulink>). + +</para><para> + +For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create +empty space for the Linux partitions, and complete the partitioning under +Linux, or use the MacOS version of pdisk available from the MkLinux FTP +server. + +</para> +</sect2> + diff --git a/nl/preparing/nondeb-part/powerpc.xml b/nl/preparing/nondeb-part/powerpc.xml new file mode 100644 index 000000000..8b70dc6a3 --- /dev/null +++ b/nl/preparing/nondeb-part/powerpc.xml @@ -0,0 +1,43 @@ +<!-- 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; 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 new file mode 100644 index 000000000..9bcc1239b --- /dev/null +++ b/nl/preparing/nondeb-part/sparc.xml @@ -0,0 +1,44 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 28997 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. +Just make sure you leave room for the Debian root partition within the +first 1GB area of the boot disk. You can also place the kernel image on a +UFS partition if that is easier than putting the root partition there. +SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS +(SunOS), romfs and 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/pre-install-bios-setup.xml b/nl/preparing/pre-install-bios-setup.xml new file mode 100644 index 000000000..a727e1b08 --- /dev/null +++ b/nl/preparing/pre-install-bios-setup.xml @@ -0,0 +1,158 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28997 --> + + <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; op uw systeem kunnen beïnvloeden. + +</para> + +&bios-setup-i386.xml; +&bios-setup-m68k.xml; +&bios-setup-powerpc.xml; +&bios-setup-sparc.xml; +&bios-setup-s390.xml; + + <sect2><title>Aandachtspunten ten aanzien van apparatuur</title> +<para arch="not-s390"> + +Velen hebben geprobeerd om bijvoorbeeld hun 90 MHz CPU op 100 MHz te laten +werken. Soms werkt dit, maar het is gevoelig voor temperatuur en andere +factoren en kan uw systeem beschadigen. Eén van de auteurs van dit document +heeft zijn systeem een jaar lang op verhoogde snelheid laten draaien waarna +het systeem tijdens de compilatie van het besturingssysteem plotseling begon +het <command>gcc</command>-programma af te breken met een onverwachte fout. +Het probleem kon worden opgelost door de CPU weer op zijn normale snelheid te +laten werken. + +</para><para arch="not-s390"> + +De <command>gcc</command>-compiler vertoont vaak als eerste problemen door +slechte geheugenmodules (of andere hardwareproblemen die onvoorspelbare +veranderingen van gegevens veroorzaken) omdat het enorme gegevensstructuren +opbouwt die herhaaldelijk worden doorlopen. Een fout in deze gegevensstructuren +resulteert in een ongeldige instructie of het lezen van een onbestaand +geheugenadres. Het symptoom hiervan is dat <command>gcc</command> afbreekt met +een onverwachte fout. + +</para><para arch="m68k"> + +Atari TT RAM moederborden zijn berucht om hun problemen met RAM onder +Linux; probeer, als u vreemde problemen tegenkomt, om tenminste de kernel +in ST-RAM te laden. Gebruikers van een Amiga moeten mogelijk RAM uitsluiten +met behulp van een 'booter memfile'. +<!-- FJP Is moederborden juist of zijn dit (insteek)kaarten? //--> +<!-- FJP What the f*ck is een booter memfile? //--> + +<phrase condition="FIXME"><emphasis> + +FIXME: more description of this needed. + +</emphasis></phrase> + +</para><para arch="i386"> + +De betere moederborden ondersteunen RAM met pariteitscontrole en kunnen u +melden als uw systeem een fout van één bit in het geheugen heeft. Helaas +kunnen ze deze fout niet herstellen en zullen ze over het algemeen stuklopen +direct na de melding van de geheugenfout. Het is echter nog altijd beter +om verteld te worden dat er geheugenproblemen zijn dan dat er ongemerkt +fouten in uw gegevens ontstaan. Daarom beschikken de betere systemen over +moederborden die geheugenmodules met 'parity' en 'true-parity' ondersteunen; +zie ook <xref linkend="Parity-RAM"/>. + +</para><para arch="i386"> + +Als u 'true-parity' RAM heeft en als dit door uw moederbord wordt ondersteund, +activeer dan eventuele BIOS-instellingen die ervoor zorgen dat het moederbord +een interrupt genereert bij pariteitsfouten in het geheugen. + +</para> + + <sect3 arch="i386"><title>De turboschakelaar</title> +<para> + +Veel systemen hebben een <emphasis>turboschakelaar</emphasis> die de +snelheid van de CPU reguleert. Selecteer de hoogste snelheid. Als uw +BIOS de mogelijkheid biedt om softwarematige besturing van de +turboschakelaar (of CPU-snelheid) uit te schakelen, kunt u dit het beste +doen en het systeem vastzetten in de hoogste snelheid. Er is één melding +van een systeem waarbij Linux, tijdens het automatisch zoeken naar aanwezige +apparatuur, per ongeluk de softwarematige besturing van de turboschakelaar raakte. + +</para> + </sect3> + + <sect3 arch="i386"><title>Cyrix-CPU's en diskettefouten</title> +<para> + +Bij systemen met een Cyrix-CPU kan het noodzakelijk zijn om tijdens de +installatie het cache-geheugen uit te schakelen omdat anders +diskettefouten optreden. Vergeet niet om na de installatie de cache weer +te activeren omdat het systeem <emphasis>veel</emphasis> trager werkt als +de cache uitgeschakeld is. + +</para><para> + +We denken dat dit niet noodzakelijk een fout van de Cyrix-CPU is. Mogelijk +kan dit probleem binnen Linux worden opgelost; we blijven hieraan werken. +(Voor technisch geïnteresseerde lezers: we vermoeden dat het probleem is dat +de cache ongeldig wordt na een omschakeling van instructies van 16-bit +naar 32-bit.) + +</para> + </sect3> + + <sect3 arch="i386"><title>Instellingen van randapparatuur</title> +<para> + +Mogelijk moet u instellingen of jumpers op in uw computer aanwezige kaarten +van randapparatuur wijzigen. Sommige kaarten beschikken over +configuratiemenu's terwijl andere gebruik maken van jumpers. Het is helaas +niet mogelijk om in dit document volledige informatie te verschaffen over elk +apparaat; wel proberen we nuttige tips te geven. + +</para><para> + +Als u kaarten heeft die gebruik maken van 'mapped memory', dan dient dit +geconfigureerd te worden ergens tussen 0xA0000 en 0xFFFFF (van 640K tot net +onder 1 megabyte) of een adres tenminste 1 megabyte groter dan de totale +hoeveelheid RAM in uw systeem. + +</para> + </sect3> + + <sect3 arch="i386" id="usb-keyboard-config"> + <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> + </sect3> + + <sect3><title>Meer dan 64 MB RAM</title> +<para> + +De Linux kernel kan niet in alle gevallen bepalen over hoeveel RAM u beschikt. +Raadpleeg in dat geval <xref linkend="boot-parms"/>. + +</para> + </sect3> + </sect2> + </sect1> diff --git a/nl/preparing/preparing.xml b/nl/preparing/preparing.xml new file mode 100644 index 000000000..df9f149e7 --- /dev/null +++ b/nl/preparing/preparing.xml @@ -0,0 +1,23 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 16467 --> + +<chapter id="preparing"> + <title>Voordat u &debian; 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 new file mode 100644 index 000000000..d321d4d5b --- /dev/null +++ b/nl/using-d-i/components.xml @@ -0,0 +1,163 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 29895 --> + + <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> + +&module-lowmem.xml; +&module-languagechooser.xml; +&module-countrychooser.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; + + </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 +LVM of RAID worden geconfigureerd. + +</para> + +&module-s390-dasd.xml; +&module-partman.xml; +&module-autopartkit.xml; +&module-partitioner.xml; +&module-partconf.xml; +&module-lvmcfg.xml; +&module-mdcfg.xml; + </sect2> + + <sect2 id="di-install-base"> + <title>Installatie van het Basissysteem</title> +<para> + +Hoewel dit stadium het minst problematisch is, neemt het wel de meeste tijd in +beslag 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-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><para> + +Het werken met verschillende besturingssystemen op één machine is nog altijd +een lastig onderwerp. In dit document wordt geen poging gedaan om zelfs +maar de verschillende opstartladers, die per platform en zelfs +subplatform verschillen, te documenteren. Voor aanvullende informatie +dient u de documentatie van uw opstartlader te raadplegen. + +</para> + +&module-os-prober.xml; +&module-alpha-aboot-installer.xml; +&module-hppa-palo-installer.xml; +&module-i386-grub-installer.xml; +&module-i386-lilo-installer.xml; +&module-ia64-elilo-installer.xml; +&module-mips-arcboot-installer.xml; +&module-mipsel-colo-installer.xml; +&module-mipsel-delo-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 eerste fase van de installatie afronden</title> +<para> + +Dit zijn de laatste acties die moeten worden uitgevoerd voordat de +computer kan worden opgestart met uw nieuwe Debian systeem. Het bestaat +voornamelijk uit het afwerken van losse eindjes van &d-i;. + +</para> + +&module-prebaseconfig.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; +&module-network-console.xml; +&module-baseconfig.xml; + </sect2> + </sect1> diff --git a/nl/using-d-i/modules/alpha/aboot-installer.xml b/nl/using-d-i/modules/alpha/aboot-installer.xml new file mode 100644 index 000000000..2d58e0f74 --- /dev/null +++ b/nl/using-d-i/modules/alpha/aboot-installer.xml @@ -0,0 +1,19 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 25496 untranslated --> + + <sect3 arch="alpha"> + <title>Install <command>aboot</command> on a Hard Disk</title> +<para> + +If you have booted from SRM, if you select this option, the installer +will write <command>aboot</command> to the first sector of the disk on +which you installed Debian. Be <emphasis>very</emphasis> careful — it +is <emphasis>not</emphasis> possible to boot multiple operating +systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix +a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a +different operating system installed on the disk where you have +installed Debian, you will have to boot GNU/Linux from a floppy +instead. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/anna.xml b/nl/using-d-i/modules/anna.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/anna.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> diff --git a/nl/using-d-i/modules/autopartkit.xml b/nl/using-d-i/modules/autopartkit.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/autopartkit.xml @@ -0,0 +1,2 @@ +<!-- 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 new file mode 100644 index 000000000..5ff5ae47f --- /dev/null +++ b/nl/using-d-i/modules/base-installer.xml @@ -0,0 +1,31 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <sect3 id="base-installer"> + <title>Installatie van het basissysteem</title> + +<para> + +Tijdens de installatie van het basissysteem worden boodschappen met +betrekking tot het uitpakken en configureren van pakketten doorgestuurd +naar <userinput>tty3</userinput>. U kunt naar deze terminal schakelen door +op <keycombo><keycap>Linker Alt</keycap><keycap>F3</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> + +Als de installatie wordt uitgevoerd vanaf een seriële console, worden de +boodschappen die worden gegenereerd tijdens deze fase opgeslagen in +<filename>/var/log/messages</filename>. + +</para><para> + +Als onderdeel van de installatie zal een Linux 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> + </sect3> diff --git a/nl/using-d-i/modules/baseconfig.xml b/nl/using-d-i/modules/baseconfig.xml new file mode 100644 index 000000000..b59f4a9fc --- /dev/null +++ b/nl/using-d-i/modules/baseconfig.xml @@ -0,0 +1,17 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 29903 --> + + <sect3 id="baseconfig"> + <title><command>Base-config</command> uitvoeren vanuit &d-i;</title> + +<para> + +Het is mogelijk om het basissysteem te configureren tijdens de eerste fase +van de installatie (dus voordat u het systeem opnieuw opstartvanaf de harde +schijf) door in een <firstterm>chroot</firstterm>-omgeving het commando +<command>base-config</command> uit te voeren. Dit is voornamelijk zinvol +bij het testen van het installatiesysteem en dient normaalgesproken te +worden gemeden. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/cdrom-checker.xml b/nl/using-d-i/modules/cdrom-checker.xml new file mode 100644 index 000000000..d4c2f588b --- /dev/null +++ b/nl/using-d-i/modules/cdrom-checker.xml @@ -0,0 +1,2 @@ +<!-- 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 new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/cdrom-detect.xml @@ -0,0 +1,2 @@ +<!-- 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 new file mode 100644 index 000000000..746804ecd --- /dev/null +++ b/nl/using-d-i/modules/choose-mirror.xml @@ -0,0 +1,17 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 16990 untranslated --> + +<!-- +- Component is only selected and executed if the installer needs to load + installer components or the base system from the network + (either local or the internet). +- This means you first have to configure a network interface. +- A list of countries is displayed with the default based on the country you + selected earlier. +- Note that not all mirrors are equal (see http://www.nl.debian.org/mirror/list) +- Selection of a local mirror (at top of the list: manual selection). +- After selecting a country, a list of mirrors in the country will be shown. + +- The selected mirror will be tested. +- How to handle problems with mirrors. +-->
\ No newline at end of file diff --git a/nl/using-d-i/modules/countrychooser.xml b/nl/using-d-i/modules/countrychooser.xml new file mode 100644 index 000000000..b831ef355 --- /dev/null +++ b/nl/using-d-i/modules/countrychooser.xml @@ -0,0 +1,26 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28343 --> + + + <sect3 id="country-chooser" condition="sarge"> + <title>Uw locatie selecteren</title> + +<para> + +Als u in <xref linkend="lang-chooser"/> een taal heeft geselecteerd waarmee +meer dan één land is geassocieerd (zoals het geval is voor Engels, Chinees, +Nederlands en vele andere talen), kunt u hier aangeven in welk land u zich +bevindt. Als u kiest voor <guimenuitem>Andere</guimenuitem> onderaan de +lijst, wordt een lijst met alle landen getoond, gegroepeerd op continent. + +</para><para> + +De geselecteerde locatie zal later in het installatieproces worden gebruikt +om een passende standaard waarde te bepalen voor de tijdzone en voor de te +gebruiken Debian spiegelserver. Als de door het installatiesysteem voorgestelde +standaard niet juist is, kunt u een andere waarde kiezen. Het geselecteerde land +kan, samen met de geselecteerde taal, ook de instellingen voor localisatie voor +uw nieuwe Debian systeem beïnvloeden. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/ddetect.xml b/nl/using-d-i/modules/ddetect.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/ddetect.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> diff --git a/nl/using-d-i/modules/hppa/palo-installer.xml b/nl/using-d-i/modules/hppa/palo-installer.xml new file mode 100644 index 000000000..84a3608e8 --- /dev/null +++ b/nl/using-d-i/modules/hppa/palo-installer.xml @@ -0,0 +1,20 @@ +<!-- 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/i386/grub-installer.xml b/nl/using-d-i/modules/i386/grub-installer.xml new file mode 100644 index 000000000..64e1e7ffb --- /dev/null +++ b/nl/using-d-i/modules/i386/grub-installer.xml @@ -0,0 +1,26 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 18640 untranslated --> + + <sect3 arch="i386"> + <title>Install the <command>Grub</command> Boot Loader + on a Hard Disk</title> +<para> + +The main &architecture; boot loader is called <quote>grub</quote>. +Grub is a flexible and robust boot loader and a good default choice for +newbies and old hands alike. + +</para><para> + +By default, grub will be installed into the Master Boot Record (MBR), where +it will take over complete control of the boot process. If you prefer, you +can install it elsewhere. See the grub manual for complete information. + +</para><para> + +If you do not want to install grub at all, use the Back button to get to +the main menu, and from there select whatever bootloader you would like to +use. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/i386/lilo-installer.xml b/nl/using-d-i/modules/i386/lilo-installer.xml new file mode 100644 index 000000000..30726d83a --- /dev/null +++ b/nl/using-d-i/modules/i386/lilo-installer.xml @@ -0,0 +1,70 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 22935 untranslated --> + + <sect3 arch="i386"> + <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; presents you three choices where to install the +<command>LILO</command> boot loader: + +<variablelist> +<varlistentry> +<term>Master Boot Record (MBR)</term><listitem><para> + +This way the <command>LILO</command> will take complete control of the +boot process. + +</para></listitem></varlistentry> +<varlistentry> +<term>new Debian partition</term><listitem><para> + +Choose this if you want to use another boot +manager. <command>LILO</command> will install itself at the 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 devfs style names, such as those that start with +<filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and +<filename>/dev/discs</filename>, as well as traditional names, such as +<filename>/dev/hda</filename> or <filename>/dev/sda</filename>. + +</para></listitem></varlistentry> +</variablelist> + +</para><para> + +If you can no longer boot into Windows 9x (or DOS) after this step, +you'll need to use a Windows 9x (MS-DOS) boot disk and use the +<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS +master boot record — however, this means that you'll need to use +some other way to get back into Debian! For more information on this +please read <xref linkend="reactivating-win"/>. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/ia64/elilo-installer.xml b/nl/using-d-i/modules/ia64/elilo-installer.xml new file mode 100644 index 000000000..7953befe6 --- /dev/null +++ b/nl/using-d-i/modules/ia64/elilo-installer.xml @@ -0,0 +1,135 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24321 untranslated --> + + <sect3 arch="ia64"> + <title>Install the <command>ELILO</command> Boot Loader + on a Hard Disk</title> +<para> + +The &architecture; boot loader is called <quote>elilo</quote>. +It is modeled on the <quote>lilo</quote> boot loader for the +x86 architecture and uses a similar configuration file. +However, instead of writing an MBR or partition boot record to +the disk, it copies the necessary files to a separate FAT formatted +disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> +menu in the firmware to point to the files in the EFI partition. +The <command>elilo</command> boot loader is really in two parts. +The <filename>/usr/sbin/elilo</filename> command manages the partition and +copies file into it. +The <filename>elilo.efi</filename> program is copied into the EFI +partition and then run by the <quote>EFI Boot Manager</quote> to actually +do the work of loading and starting the Linux kernel. + +</para><para> + +The <quote>elilo</quote> configuration and installation is done as the +last step of installing the packages of the base installation. +&d-i; will present you with a list of potential disk partitions that it +has found suitable for an EFI partition. +Select the partition you set up earlier in the installation, typically +a partition on the same disk that contains your +<emphasis>root</emphasis> filesystem. + +</para> + + <warning><title>Choose the correct partition!</title> + +<para> + +The criteria for selecting a partition is that it is FAT format +filesystem with its <emphasis>boot</emphasis> flag set. +&d-i; may show multiple choices depending on what it finds from scanning +all of the disks of the system including EFI partitions of other system +disks and EFI diagnostic partitions. +Remember, the <command>elilo</command> may format the partition during +the installation, erasing any previous contents! + +</para></warning> + + </sect3> + + <sect3 arch="ia64"> + <title>EFI Partition Contents</title> + +<para> + +The EFI partition is a FAT filesystem format partition on one of the +hard disks of the system, usually the same disk that contains the +<emphasis>root</emphasis> 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 new file mode 100644 index 000000000..968d9e49e --- /dev/null +++ b/nl/using-d-i/modules/iso-scan.xml @@ -0,0 +1,50 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- 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 new file mode 100644 index 000000000..deec0b9a8 --- /dev/null +++ b/nl/using-d-i/modules/kbd-chooser.xml @@ -0,0 +1,78 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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>kbdconfig</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="mipsel"> + +Voor DECstations is op dit moment geen toetsenbordindeling beschikbaar +om te laden; u dient daarom de toetsenbordselectie over te slaan en de +standaard indeling van de kernel (LK201 US) te accepteren. Mogelijk zal +dit in de toekomst veranderen, afhankelijk van ontwikkeling van de +Linux/MIPS kernel. + +</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> + +<note arch="sparc"><para> + +Als u een installatie uitvoert op een systeem met een USB toetsenbord van Sun +en het installatiesysteem is gestart met de standaard 2.4 kernel, dan zal het +toetsenbord niet correct worden gedetecteerd. Het installatiesysteem zal een +keuzelijst met Sun-toetsenbordindelingen tonen. Als u er daaruit echter één +selecteert, zal dit resulteren in een niet werkend toetsenbord. Als u met de +2.6 kernel installeert, is er geen probleem. + +</para><para> + +Om een werkend toetsenbord te krijgen, kunt u het installatiesysteem het beste +starten met parameter <userinput>debconf/priority=medium</userinput>. Op het +moment dat u bij de toetsenbordselectie komt<footnote> + +<para> +Als u de installatie uitvoert met de default prioriteit kunt u de optie +<userinput>Terug</userinput> gebruiken om naar het hoofdmenu van het +installatiesysteem te gaan als de keuzelijst met Sun-toetsenbordindelingen +wordt getoond. +</para> + +</footnote>, selecteert u <quote>Geen toetsenbord configureren</quote> als u +een toetsenbord met een Amerikaanse (US) indeling heeft, of +<quote>USB-toetsenbord</quote> voor een toetsenbord met een gelokaliseerde +indeling. Het selecteren van <quote>Geen toetsenbord configureren</quote> +heeft tot gevolg dat het systeem de standaard toetsenbordindeling van de kernel +blijft gebruiken, wat correct is voor US toetsenborden. + +</para></note> + </sect3> diff --git a/nl/using-d-i/modules/languagechooser.xml b/nl/using-d-i/modules/languagechooser.xml new file mode 100644 index 000000000..65f789051 --- /dev/null +++ b/nl/using-d-i/modules/languagechooser.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28343 --> + + <sect3 id="lang-chooser" condition="sarge"> + <title>Taalkeuze</title> + +<para> + +Als eerste stap van de installatie kunt u de taal kiezen waarin de rest +van de installatie zal plaatsvinden. 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. + +</para><para> + +De taal die u kiest zal worden gebruikt voor de rest van het installatieproces, +voor zover voor de verschillende dialogen een vertaling beschikbaar is. Als +geen geldige vertaling beschikbaar is voor de geselecteerde taal, zal het +installatiesysteem terugvallen op Engels. De geselecteerde taal zal tevens +worden gebruikt om te helpen een geschikte toetsenbordindeling te selecteren. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/localechooser.xml b/nl/using-d-i/modules/localechooser.xml new file mode 100644 index 000000000..d0a081bca --- /dev/null +++ b/nl/using-d-i/modules/localechooser.xml @@ -0,0 +1,70 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28856 --> + + + <sect3 id="localechooser" condition="etch"> + <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 u vervolgens worden gevraagd een land te selecteren. Als u +kiest voor <guimenuitem>Andere</guimenuitem> onderaan de lijst, zal een +overzicht worden getoond van alle landen, gegroepeerd op continent. Als de +taal slechts bij één land voorkomt, zal dat land automatisch worden +geselecteerd. + +</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 new file mode 100644 index 000000000..bbcc95fcf --- /dev/null +++ b/nl/using-d-i/modules/lowmem.xml @@ -0,0 +1,22 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- 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; +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/lvmcfg.xml b/nl/using-d-i/modules/lvmcfg.xml new file mode 100644 index 000000000..9a53c8441 --- /dev/null +++ b/nl/using-d-i/modules/lvmcfg.xml @@ -0,0 +1,97 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 30207 --> + + <sect3 id="lvmcfg"> + <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. Allereerst dient u de +partities te markeren die u wilt gebruiken als fysieke volumes voor LVM. +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>. Vervolgens start u de module +<command>lvmcfg</command> (dit is mogelijk zowel direct vanuit +<command>partman</command> als vanuit het hoofdmenu van &d-i;) en voegt u +vanuit de menukeuze <guimenuitem>Volumegroepen (VG) aanpassen</guimenuitem> +de fysieke volumes samen tot één of meerdere volumegroepen. Vervolgens +dient u nog vanuit de menukeuze <guimenuitem>Logische volumes (LV) +aanpassen</guimenuitem> de logische volumes te creëren bovenop de +volumegroepen. + +<note arch="powerpc" condition="sarge"><para> + +Voor Apple Power Macintosh systemen bestaat geen algemeen geaccepteerde +standaard om partities te identificeren die LVM-gegevens bevatten. +Op deze apparatuur zal bovenstaande procedure daardoor niet werken. +Er is echter een werkbare oplossing voor deze beperking; deze vereist +wel dat u bekend bent met de onderliggende LVM hulpprogramma's. + +</para><para> + +Om logische volumes te installeren op Power Macintosh systemen, creëert +u eerst op de gebruikelijke wijze alle fysieke partities voor uw +logische volumes. Selecteer in het menu <guimenu>Partitie-instellingen</guimenu> +de optie <menuchoice><guimenu>Use as:</guimenu> <guimenuitem>Deze partitie +niet gebruiken</guimenuitem></menuchoice> voor deze partities (de optie +om de partitie te gebruiken als fysiek volume zal niet worden getoond). +Als u klaar bent met het creëren van alle partities, start u de logisch +volumebeheerder. Omdat echter nog geen fysieke volumes zijn aangemaakt, +dient u deze nu handmatig aan te maken in de shell die beschikbaar is op +de tweede virtuele terminal (zie <xref linkend="shell"/>). + +</para><para> + +Gebruik in de shell vanaf de prompt het commando <command>pvcreate</command> +om voor elk van de door u gekozen partities een fysiek volume te creëren. +Gebruik vervolgens het commando <command>vgcreate</command> om de gewenste +volumegroepen aan te maken. U kunt eventuele foutmeldingen over onjuiste +'metadata area header checksums' en 'fsync failures' veilig negeren. Als u +klaar bent met het creëren van de volumegroepen, schakelt u terug naar de +eerste virtuele terminal en kiest u in <command>lvmcfg</command> direct de +menuopties voor logisch volumebeheer. Uw volumegroepen zullen worden getoond +en u kunt op de gebruikelijke wijze de logische volumes aanmaken. + +</para></note> + +</para><para> + +Nadat u vanuit <command>lvmcfg</command> terugkeert in +<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/mdcfg.xml b/nl/using-d-i/modules/mdcfg.xml new file mode 100644 index 000000000..b4815ef49 --- /dev/null +++ b/nl/using-d-i/modules/mdcfg.xml @@ -0,0 +1,240 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 30377 --> + + <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 geïnteresseerd bent in de meer intieme details over Software-RAID, +raadpleeg dan de <ulink url="&url-software-raid-howto;">Software RAID HOWTO</ulink>. + +<note arch="powerpc" condition="sarge"><para> + +Er bestaat voor Apple power Macintosh geen breed geaccepteerde standaard +voor het identificeren van partities met RAID-gegevens. Dit heeft tot gevolg +dat &d-i; op dit moment het configureren van RAID voor dit platform niet +ondersteunt. + +</para></note> + +</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>. +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 new file mode 100644 index 000000000..13eba925e --- /dev/null +++ b/nl/using-d-i/modules/mips/arcboot-installer.xml @@ -0,0 +1,69 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + <sect3 arch="mips"> + <title><command>arcboot</command>-installer</title> +<para> + +The boot loader on SGI Indys is <command>arcboot</command>. +It has to be installed on the same hard disk as the kernel (this is done +automatically by the installer). Arcboot supports different configurations +which are set up in <filename>/etc/arcboot.conf</filename>. Each +configuration has a unique name, +the default setup as created by the installer is <quote>linux</quote>. +After arcboot has been installed, the system can be booted from hard disk +by setting some firmware environment variables entering + +<informalexample><screen> +<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 new file mode 100644 index 000000000..d4c2f588b --- /dev/null +++ b/nl/using-d-i/modules/mipsel/colo-installer.xml @@ -0,0 +1,2 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14337 untranslated --> diff --git a/nl/using-d-i/modules/mipsel/delo-installer.xml b/nl/using-d-i/modules/mipsel/delo-installer.xml new file mode 100644 index 000000000..7325398ac --- /dev/null +++ b/nl/using-d-i/modules/mipsel/delo-installer.xml @@ -0,0 +1,76 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 24663 untranslated --> + + <sect3 arch="mipsel"> + <title><command>delo</command>-installer</title> +<para> + +The boot loader on DECstations is <command>DELO</command>. +It has to be installed on the same hard disk as the kernel (this is done +automatically by the installer). DELO supports different configurations +which are set up in <filename>/etc/delo.conf</filename>. Each +configuration has a unique name, +the default setup as created by the installer is <quote>linux</quote>. +After DELO has been installed, the system can be booted from hard disk +by entering + +<informalexample><screen> +<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> <replaceable>partnr</replaceable>/<replaceable>name</replaceable></userinput> +</screen></informalexample> + +on the firmware prompt. + +</para> + +<variablelist> +<varlistentry> +<term> <replaceable>#</replaceable> </term> +<listitem><para> + +is the TurboChannel device to be booted from, on most DECstations this +is <userinput>3</userinput> for the onboard controllers + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>id</replaceable> </term> +<listitem><para> + +is the SCSI ID of the hard disk on which <command>DELO</command> is +installed + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>partnr</replaceable> </term> +<listitem><para> + +is the number of the partition on which +<filename>/etc/delo.conf</filename> resides + +</para></listitem> +</varlistentry> +<varlistentry> +<term> <replaceable>name</replaceable> </term> +<listitem><para> + +is the name of the configuration entry in +<filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by +default. + +</para></listitem> +</varlistentry> +</variablelist> + +<para> + +In case <filename>/etc/delo.conf</filename> is on the first partition +on the disk and the default configuration shall be booted, it is +sufficient to use + +<informalexample><screen> +<userinput>boot #/rz<replaceable>id</replaceable></userinput> +</screen></informalexample> + +</para> + </sect3> diff --git a/nl/using-d-i/modules/netcfg.xml b/nl/using-d-i/modules/netcfg.xml new file mode 100644 index 000000000..b10afb3c3 --- /dev/null +++ b/nl/using-d-i/modules/netcfg.xml @@ -0,0 +1,59 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 23058 --> + + <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 derde 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 zouden van pas kunnen 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 Broadcast-adres wordt ingesteld op het resultaat van een +bit-gewijze OR-operatie van het IP-adres van uw systeem en de bitgewijze +inverse van het netwerkmasker. 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. +Ook kunt u het pakket <classname>etherconf</classname> installeren dat u +stapsgewijs zal helpen bij de configuratie van uw netwerkinterface. + +</para></note> + </sect3> diff --git a/nl/using-d-i/modules/network-console.xml b/nl/using-d-i/modules/network-console.xml new file mode 100644 index 000000000..f92319273 --- /dev/null +++ b/nl/using-d-i/modules/network-console.xml @@ -0,0 +1,111 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 31173 --> + + <sect3 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> + + </sect3> diff --git a/nl/using-d-i/modules/nobootloader.xml b/nl/using-d-i/modules/nobootloader.xml new file mode 100644 index 000000000..7f4a13a5d --- /dev/null +++ b/nl/using-d-i/modules/nobootloader.xml @@ -0,0 +1,39 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 25513 --> + + <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). <phrase arch="m68k"> Deze +optie is met name nuttig voor Macintosh, Atari en Amiga systemen waarbij +het oorspronkelijke besturingssysteem op de machine behouden moet blijven +en gebruikt wordt om GNU/Linux op te starten.</phrase> + +</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 new file mode 100644 index 000000000..1cdb1cfaa --- /dev/null +++ b/nl/using-d-i/modules/os-prober.xml @@ -0,0 +1,36 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 27596 --> + + <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> + +<note condition="sarge"><para> + +Het is mogelijk dat het installatiesysteem andere besturingssystemen niet zal +detecteren als de partities waarop deze zich bevinden, zijn aangekoppeld +op het moment dat de detectie plaatsvindt. Dit kan zich voordoen als u in +<command>partman</command> een koppelpunt (zoals /win) heeft geselecteerd voor een +partitie met een ander besturingssysteem of als u vanaf een console handmatig +partities heeft aangekoppeld. + +</para></note> + </sect3> diff --git a/nl/using-d-i/modules/partconf.xml b/nl/using-d-i/modules/partconf.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/partconf.xml @@ -0,0 +1,2 @@ +<!-- 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 new file mode 100644 index 000000000..0dabd4a41 --- /dev/null +++ b/nl/using-d-i/modules/partitioner.xml @@ -0,0 +1,3 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 11648 untranslated --> + diff --git a/nl/using-d-i/modules/partman.xml b/nl/using-d-i/modules/partman.xml new file mode 100644 index 000000000..ae14929dc --- /dev/null +++ b/nl/using-d-i/modules/partman.xml @@ -0,0 +1,211 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 30158 --> + + <sect3 id="partman"> + <title>Uw harde schijven indelen</title> + +<para> + +Nu is het moment aangebroken om uw harde schijven in te delen. 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 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><para> + +Als u kiest voor begeleide schijfindeling, kunt u kiezen tussen de +schema's die zijn 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>Alle bestanden in 1 partitie</entry> + <entry>600MB</entry> + <entry><filename>/</filename>, swap</entry> +</row><row> + <entry>Desktopmachine</entry> + <entry>500MB</entry> + <entry> + <filename>/</filename>, <filename>/home</filename>, swap + </entry> +</row><row> + <entry>Werkstation met meerdere gebruikers</entry> + <entry>1GB</entry> + <entry> + <filename>/</filename>, <filename>/home</filename>, + <filename>/usr</filename>, <filename>/var</filename>, + <filename>/tmp</filename>, swap + </entry> +</row> + +</tbody></tgroup></informaltable> + +<para arch="ia64"> + +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 arch="alpha"> + +Als u voor uw Alpha systeem kiest voor begeleide schijfindeling, zal een +extra, niet-geformatteerde partitie worden aangemaakt aan het begin van +uw harde schijf om deze schijfruimte te reserveren voor de opstartlader +<command>aboot</command>. + +</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: + +<!-- TODO: show some flags here (lightning, skull, smiley) --> +<informalexample><screen> + IDE1 master (hda) - 6.4 GB WDC AC36400L + #1 primair 16.4 MB 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 ext3 / + #6 logisch 1.0 GB 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. +<!-- 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> of om +de begeleide schijfindeling nogmaals uit te voeren of om de voorgestelde +indeling te wijzigen zoals hieronder beschreven voor handmatige schijfindeling. + +</para><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/powerpc/quik-installer.xml b/nl/using-d-i/modules/powerpc/quik-installer.xml new file mode 100644 index 000000000..ed6aa6a60 --- /dev/null +++ b/nl/using-d-i/modules/powerpc/quik-installer.xml @@ -0,0 +1,15 @@ +<!-- 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 new file mode 100644 index 000000000..4bba348fb --- /dev/null +++ b/nl/using-d-i/modules/powerpc/yaboot-installer.xml @@ -0,0 +1,17 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 14975 untranslated --> + + <sect3 arch="powerpc"> + <title>Install <command>Yaboot</command> on a Hard Disk</title> +<para> + +Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as +their boot loader. The installer will set up <command>yaboot</command> +automatically, so all you need is a small 820k partition named +<quote>bootstrap</quote> with type +<emphasis>Apple_Bootstrap</emphasis> created back in the partitioning +component. If this step completes successfully then your disk should +now be bootable and OpenFirmware will be set to boot &debian;. + +</para> + </sect3> diff --git a/nl/using-d-i/modules/prebaseconfig.xml b/nl/using-d-i/modules/prebaseconfig.xml new file mode 100644 index 000000000..17581a48d --- /dev/null +++ b/nl/using-d-i/modules/prebaseconfig.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 21672 --> + + <sect3 id="prebaseconfig"> + <title>De installatie afronden en opnieuw opstarten</title> + +<para> + +Dit is de laatste stap van de eerste fase van het installatieproces voor +Debian. U zal worden gevraagd om het installatiemedium (CD, diskette, enz.) +dat u heeft gebruikt om het installatiesysteem op te starten, te verwijderen. +Het installatiesysteem zal vervolgens nog enkele afrondende taken uitvoeren +en vervolgens uw systeem opnieuw opstarten met uw nieuwe Debian systeem. + +</para><para arch="s390"> + +Selecteer de optie <guimenuitem>De installatie afronden</guimenuitem> uit het +menu; deze zal het systeem stoppen omdat herstarten op &arch-title; in dit geval +niet wordt ondersteund. U moet dan een IPL voor GNU/Linux uitvoeren vanuit 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/s390/dasd.xml b/nl/using-d-i/modules/s390/dasd.xml new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/s390/dasd.xml @@ -0,0 +1,2 @@ +<!-- 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 new file mode 100644 index 000000000..5c156a8fa --- /dev/null +++ b/nl/using-d-i/modules/s390/netdevice.xml @@ -0,0 +1,2 @@ +<!-- 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 new file mode 100644 index 000000000..61aa6465c --- /dev/null +++ b/nl/using-d-i/modules/s390/zipl-installer.xml @@ -0,0 +1,16 @@ +<!-- 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 new file mode 100644 index 000000000..41f8996ed --- /dev/null +++ b/nl/using-d-i/modules/save-logs.xml @@ -0,0 +1,25 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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<phrase condition="etch">, via het network, op harde schijf of op een ander +medium</phrase> 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 new file mode 100644 index 000000000..c04ac5567 --- /dev/null +++ b/nl/using-d-i/modules/shell.xml @@ -0,0 +1,43 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- 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 new file mode 100644 index 000000000..3ce2b6ac6 --- /dev/null +++ b/nl/using-d-i/modules/sparc/silo-installer.xml @@ -0,0 +1,25 @@ +<!-- 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/using-d-i.xml b/nl/using-d-i/using-d-i.xml new file mode 100644 index 000000000..0d47d07a9 --- /dev/null +++ b/nl/using-d-i/using-d-i.xml @@ -0,0 +1,398 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28997 --> + + <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>debconf/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>debconf/priority=low</userinput> +toe te voegen. De expert modus geeft u volledige controle over &d-i;. + +</para><para> + +De standaard schermweergave van het installatiesysteem is karakter georiënteerd +(dit in tegenstelling tot de tegenwoordig meer vertrouwde grafische interface). +De muis is in deze omgeving niet actief. Dit zijn de toetsen waarmee u kunt +navigeren binnen de diverse configuratieschermen. Om <quote>vooruit</quote> of +<quote>terug</quote> te gaan tussen getoonde knoppen of selecties, gebruikt u 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 derde console. +U kunt toegang krijgen tot deze console door +op <keycombo><keycap>linker Alt</keycap><keycap>F3</keycap></keycombo> +te drukken (houd de linker <keycap>Alt</keycap> toets vast terwijl u de +<keycap>F3</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/messages</filename>. Na de installatie wordt dit logbestand +gekopieerd naar <filename>/var/log/debian-installer/messages</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/debian-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 <quote>Terug</quote> knop te selecteren, waardoor u stapsgewijs teruggaat +uit de op dat moment actieve module. + +</para></listitem> +</varlistentry> +<varlistentry condition="sarge"> + +<term>languagechooser</term><listitem><para> + +De module 'languagechooser' (taalkiezer) toont een lijst van talen en +varianten daarvan. 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 condition="sarge"> + +<term>countrychooser</term><listitem><para> + +De module 'countrychooser' (landkiezer) toont een lijst van landen waaruit de +gebruiker het land waar hij woont kan kiezen. + +</para></listitem> +</varlistentry> +<varlistentry condition="etch"> + +<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>kbd-chooser</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 naar ISO-bestandssystemen die zich zowel op een CD als op de harde schijf +kunnen bevinden. +<!-- FJP Dit zegt nog niet erg veel. //--> + +</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>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>autopartkit</term><listitem><para> + +Voert een automatische schijfindeling uit van een hele harde schijf op basis van +vooraf gedefinieerde gebruikersvoorkeuren. +<!-- FJP Zijn dit voorkeuren van de gebruiker of van het d-i team? //--> +<!-- 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 Linux te laten functioneren. + +</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 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 verschillende besturingssystemen. + +</para></listitem> +</varlistentry> +<varlistentry> + +<term>base-config</term><listitem><para> + +Voorziet in configuratieschermen om de pakketten van het basissysteem te +configureren conform de voorkeuren van de gebruiker. Dit gebeurt normaal +gesproken nadat de computer voor de eerste keer opnieuw is opgestart. + +</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 condition="sarge">bugreporter</term><term condition="etch">save-logs</term><listitem><para> + +Stelt de gebruiker in staat om, wanneer problemen worden tegengekomen, +informatie op een diskette<phrase condition="etch">, via het network, +op harde schijf of op een ander medium</phrase> 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; + +</chapter> diff --git a/nl/welcome/about-copyright.xml b/nl/welcome/about-copyright.xml new file mode 100644 index 000000000..1b1c45e3b --- /dev/null +++ b/nl/welcome/about-copyright.xml @@ -0,0 +1,97 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 29000 --> + + <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 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 new file mode 100644 index 000000000..0f94b3e68 --- /dev/null +++ b/nl/welcome/doc-organization.xml @@ -0,0 +1,122 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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;, 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 en de installatie van een minimaal werkend systeem. 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 wordt uitgelegd in <xref linkend="partitioning"/>). + +</para></listitem> +<listitem><para> + +Start de computer opnieuw op in uw zojuist geïnstalleerde basissysteem +en doorloop een aantal aanvullende configuratietaken met behulp van +<xref linkend="boot-new"/>. + +</para></listitem> +<listitem><para> + +Installeer aanvullende software met <xref linkend="install-packages"/>. + +</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 &d-i-manual; 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 new file mode 100644 index 000000000..9a77446e7 --- /dev/null +++ b/nl/welcome/getting-newest-doc.xml @@ -0,0 +1,18 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- 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; 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 new file mode 100644 index 000000000..9f5b34dc2 --- /dev/null +++ b/nl/welcome/getting-newest-inst.xml @@ -0,0 +1,24 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <sect1 id="getting-newest-inst"> + <title>Debian verkrijgen</title> + +<para> + +Voor informatie over hoe u &debian; 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 new file mode 100644 index 000000000..2939b94a6 --- /dev/null +++ b/nl/welcome/welcome.xml @@ -0,0 +1,25 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + +<chapter id="welcome"><title>Welkom bij Debian</title> +<para> + +Dit hoofdstuk biedt een overzicht over het Debian Project en +&debian;. Als u reeds bekend bent met de geschiedenis van het +Debian Project en van de &debian; distributie kunt u dit +hoofdstuk desgewenst overslaan. + +</para> + +&what-is-debian.xml; +&what-is-linux.xml; +&what-is-debian-linux.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 new file mode 100644 index 000000000..939bbdaee --- /dev/null +++ b/nl/welcome/what-is-debian-hurd.xml @@ -0,0 +1,27 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- 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-linux.xml b/nl/welcome/what-is-debian-linux.xml new file mode 100644 index 000000000..edf024d6e --- /dev/null +++ b/nl/welcome/what-is-debian-linux.xml @@ -0,0 +1,87 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 25496 --> + + <sect1 id="what-is-debian-linux"> + <title>Wat is &debian;?</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; 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; 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 new file mode 100644 index 000000000..234edaa45 --- /dev/null +++ b/nl/welcome/what-is-debian.xml @@ -0,0 +1,117 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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 Free Software Foundation. +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-intro;">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 new file mode 100644 index 000000000..10ab8cbd1 --- /dev/null +++ b/nl/welcome/what-is-linux.xml @@ -0,0 +1,98 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!-- original version: 28672 --> + + <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="http://www.gnu.org/">Free Software Foundation</ulink> startte met +de ontwikkeling van een vrij Unix-achtig besturingssysteem, GNU genaamd. + +</para><para> + +Het GNU project 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> |