From a292182f917a4104b223016e041410498f4d47a3 Mon Sep 17 00:00:00 2001 From: Jeroen Schot Date: Wed, 29 Aug 2012 15:10:27 +0000 Subject: Restart Dutch translation of D-I manual in PO format. --- nl/administrivia/administrivia.xml | 153 -- nl/appendix/chroot-install.xml | 675 --------- nl/appendix/files.xml | 354 ----- nl/appendix/gpl.xml | 525 ------- nl/appendix/graphical.xml | 148 -- nl/appendix/plip.xml | 187 --- nl/appendix/pppoe.xml | 109 -- nl/appendix/preseed.xml | 1624 --------------------- nl/appendix/random-bits.xml | 12 - nl/bookinfo.xml | 62 - nl/boot-installer/accessibility.xml | 110 -- nl/boot-installer/arm.xml | 236 --- nl/boot-installer/boot-installer.xml | 49 - nl/boot-installer/hppa.xml | 12 - nl/boot-installer/ia64.xml | 464 ------ nl/boot-installer/intro-cd.xml | 35 - nl/boot-installer/intro-firmware.xml | 18 - nl/boot-installer/intro-hd.xml | 16 - nl/boot-installer/intro-net.xml | 19 - nl/boot-installer/mips.xml | 61 - nl/boot-installer/mipsel.xml | 54 - nl/boot-installer/parameters.xml | 678 --------- nl/boot-installer/powerpc.xml | 262 ---- nl/boot-installer/s390.xml | 36 - nl/boot-installer/sparc.xml | 46 - nl/boot-installer/trouble.xml | 572 -------- nl/boot-installer/x86.xml | 433 ------ nl/boot-new/boot-new.xml | 224 --- nl/boot-new/mount-encrypted.xml | 181 --- nl/hardware/accessibility.xml | 34 - nl/hardware/buying-hardware.xml | 98 -- nl/hardware/hardware-supported.xml | 383 ----- nl/hardware/hardware.xml | 20 - nl/hardware/installation-media.xml | 239 --- nl/hardware/memory-disk-requirements.xml | 33 - nl/hardware/network-cards.xml | 184 --- nl/hardware/supported-peripherals.xml | 36 - nl/hardware/supported/amd64.xml | 34 - nl/hardware/supported/arm.xml | 104 -- nl/hardware/supported/hppa.xml | 17 - nl/hardware/supported/i386.xml | 76 - nl/hardware/supported/ia64.xml | 3 - nl/hardware/supported/mips.xml | 56 - nl/hardware/supported/mipsel.xml | 51 - nl/hardware/supported/powerpc.xml | 428 ------ nl/hardware/supported/s390.xml | 21 - nl/hardware/supported/sparc.xml | 70 - nl/howto/installation-howto.xml | 357 ----- nl/install-methods/automatic-install.xml | 34 - nl/install-methods/boot-drive-files.xml | 176 --- nl/install-methods/boot-usb-files.xml | 159 -- nl/install-methods/create-floppy.xml | 108 -- nl/install-methods/download/arm.xml | 88 -- nl/install-methods/download/powerpc.xml | 28 - nl/install-methods/downloading-files.xml | 34 - nl/install-methods/floppy/i386.xml | 35 - nl/install-methods/floppy/powerpc.xml | 122 -- nl/install-methods/install-methods.xml | 16 - nl/install-methods/install-tftp.xml | 341 ----- nl/install-methods/ipl-tape.xml | 24 - nl/install-methods/official-cdrom.xml | 69 - nl/install-methods/tftp/bootp.xml | 73 - nl/install-methods/tftp/dhcp.xml | 94 -- nl/install-methods/tftp/rarp.xml | 32 - nl/install-methods/usb-setup/powerpc.xml | 119 -- nl/install-methods/usb-setup/x86.xml | 117 -- nl/partitioning/device-names.xml | 131 -- nl/partitioning/partition-programs.xml | 138 -- nl/partitioning/partition/hppa.xml | 22 - nl/partitioning/partition/ia64.xml | 120 -- nl/partitioning/partition/mips.xml | 16 - nl/partitioning/partition/powerpc.xml | 57 - nl/partitioning/partition/sparc.xml | 33 - nl/partitioning/partition/x86.xml | 95 -- nl/partitioning/partitioning.xml | 13 - nl/partitioning/schemes.xml | 79 - nl/partitioning/sizing.xml | 52 - nl/partitioning/tree.xml | 153 -- nl/post-install/further-reading.xml | 49 - nl/post-install/kernel-baking.xml | 173 --- nl/post-install/mail-setup.xml | 263 ---- nl/post-install/new-to-unix.xml | 29 - nl/post-install/orientation.xml | 109 -- nl/post-install/post-install.xml | 15 - nl/post-install/rescue.xml | 71 - nl/post-install/shutdown.xml | 31 - nl/preface.xml | 30 - nl/preparing/backup.xml | 35 - nl/preparing/bios-setup/i386.xml | 337 ----- nl/preparing/bios-setup/powerpc.xml | 52 - nl/preparing/bios-setup/s390.xml | 106 -- nl/preparing/bios-setup/sparc.xml | 103 -- nl/preparing/install-overview.xml | 186 --- nl/preparing/minimum-hardware-reqts.xml | 102 -- nl/preparing/needed-info.xml | 402 ----- nl/preparing/non-debian-partitioning.xml | 195 --- nl/preparing/nondeb-part/powerpc.xml | 43 - nl/preparing/nondeb-part/sparc.xml | 41 - nl/preparing/nondeb-part/x86.xml | 121 -- nl/preparing/pre-install-bios-setup.xml | 59 - nl/preparing/preparing.xml | 22 - nl/using-d-i/components.xml | 192 --- nl/using-d-i/loading-firmware.xml | 134 -- nl/using-d-i/modules/anna.xml | 2 - nl/using-d-i/modules/apt-setup.xml | 41 - nl/using-d-i/modules/autopartkit.xml | 2 - nl/using-d-i/modules/base-installer.xml | 26 - nl/using-d-i/modules/cdrom-checker.xml | 2 - nl/using-d-i/modules/cdrom-detect.xml | 2 - nl/using-d-i/modules/choose-mirror.xml | 23 - nl/using-d-i/modules/clock-setup-finish.xml | 33 - nl/using-d-i/modules/clock-setup.xml | 24 - nl/using-d-i/modules/ddetect.xml | 2 - nl/using-d-i/modules/finish-install.xml | 20 - nl/using-d-i/modules/hppa/palo-installer.xml | 20 - nl/using-d-i/modules/ia64/elilo-installer.xml | 135 -- nl/using-d-i/modules/iso-scan.xml | 49 - nl/using-d-i/modules/kbd-chooser.xml | 38 - nl/using-d-i/modules/localechooser.xml | 76 - nl/using-d-i/modules/lowmem.xml | 21 - nl/using-d-i/modules/mdcfg.xml | 233 --- nl/using-d-i/modules/mips/arcboot-installer.xml | 69 - nl/using-d-i/modules/mipsel/colo-installer.xml | 2 - nl/using-d-i/modules/netcfg.xml | 57 - nl/using-d-i/modules/network-console.xml | 110 -- nl/using-d-i/modules/nobootloader.xml | 35 - nl/using-d-i/modules/os-prober.xml | 24 - nl/using-d-i/modules/partconf.xml | 2 - nl/using-d-i/modules/partitioner.xml | 3 - nl/using-d-i/modules/partman-crypto.xml | 355 ----- nl/using-d-i/modules/partman-lvm.xml | 98 -- nl/using-d-i/modules/partman.xml | 240 --- nl/using-d-i/modules/pkgsel.xml | 70 - nl/using-d-i/modules/powerpc/quik-installer.xml | 15 - nl/using-d-i/modules/powerpc/yaboot-installer.xml | 17 - nl/using-d-i/modules/s390/dasd.xml | 2 - nl/using-d-i/modules/s390/netdevice.xml | 2 - nl/using-d-i/modules/s390/zipl-installer.xml | 16 - nl/using-d-i/modules/save-logs.xml | 23 - nl/using-d-i/modules/shell.xml | 42 - nl/using-d-i/modules/sparc/silo-installer.xml | 25 - nl/using-d-i/modules/tzsetup.xml | 54 - nl/using-d-i/modules/user-setup.xml | 70 - nl/using-d-i/modules/x86/grub-installer.xml | 25 - nl/using-d-i/modules/x86/lilo-installer.xml | 67 - nl/using-d-i/using-d-i.xml | 418 ------ nl/welcome/about-copyright.xml | 96 -- nl/welcome/doc-organization.xml | 117 -- nl/welcome/getting-newest-doc.xml | 17 - nl/welcome/getting-newest-inst.xml | 23 - nl/welcome/welcome.xml | 25 - nl/welcome/what-is-debian-hurd.xml | 26 - nl/welcome/what-is-debian-kfreebsd.xml | 26 - nl/welcome/what-is-debian-linux.xml | 86 -- nl/welcome/what-is-debian.xml | 116 -- nl/welcome/what-is-linux.xml | 98 -- po/nl/preface.po | 73 + 157 files changed, 73 insertions(+), 18297 deletions(-) delete mode 100644 nl/administrivia/administrivia.xml delete mode 100644 nl/appendix/chroot-install.xml delete mode 100644 nl/appendix/files.xml delete mode 100644 nl/appendix/gpl.xml delete mode 100644 nl/appendix/graphical.xml delete mode 100644 nl/appendix/plip.xml delete mode 100644 nl/appendix/pppoe.xml delete mode 100644 nl/appendix/preseed.xml delete mode 100644 nl/appendix/random-bits.xml delete mode 100644 nl/bookinfo.xml delete mode 100644 nl/boot-installer/accessibility.xml delete mode 100644 nl/boot-installer/arm.xml delete mode 100644 nl/boot-installer/boot-installer.xml delete mode 100644 nl/boot-installer/hppa.xml delete mode 100644 nl/boot-installer/ia64.xml delete mode 100644 nl/boot-installer/intro-cd.xml delete mode 100644 nl/boot-installer/intro-firmware.xml delete mode 100644 nl/boot-installer/intro-hd.xml delete mode 100644 nl/boot-installer/intro-net.xml delete mode 100644 nl/boot-installer/mips.xml delete mode 100644 nl/boot-installer/mipsel.xml delete mode 100644 nl/boot-installer/parameters.xml delete mode 100644 nl/boot-installer/powerpc.xml delete mode 100644 nl/boot-installer/s390.xml delete mode 100644 nl/boot-installer/sparc.xml delete mode 100644 nl/boot-installer/trouble.xml delete mode 100644 nl/boot-installer/x86.xml delete mode 100644 nl/boot-new/boot-new.xml delete mode 100644 nl/boot-new/mount-encrypted.xml delete mode 100644 nl/hardware/accessibility.xml delete mode 100644 nl/hardware/buying-hardware.xml delete mode 100644 nl/hardware/hardware-supported.xml delete mode 100644 nl/hardware/hardware.xml delete mode 100644 nl/hardware/installation-media.xml delete mode 100644 nl/hardware/memory-disk-requirements.xml delete mode 100644 nl/hardware/network-cards.xml delete mode 100644 nl/hardware/supported-peripherals.xml delete mode 100644 nl/hardware/supported/amd64.xml delete mode 100644 nl/hardware/supported/arm.xml delete mode 100644 nl/hardware/supported/hppa.xml delete mode 100644 nl/hardware/supported/i386.xml delete mode 100644 nl/hardware/supported/ia64.xml delete mode 100644 nl/hardware/supported/mips.xml delete mode 100644 nl/hardware/supported/mipsel.xml delete mode 100644 nl/hardware/supported/powerpc.xml delete mode 100644 nl/hardware/supported/s390.xml delete mode 100644 nl/hardware/supported/sparc.xml delete mode 100644 nl/howto/installation-howto.xml delete mode 100644 nl/install-methods/automatic-install.xml delete mode 100644 nl/install-methods/boot-drive-files.xml delete mode 100644 nl/install-methods/boot-usb-files.xml delete mode 100644 nl/install-methods/create-floppy.xml delete mode 100644 nl/install-methods/download/arm.xml delete mode 100644 nl/install-methods/download/powerpc.xml delete mode 100644 nl/install-methods/downloading-files.xml delete mode 100644 nl/install-methods/floppy/i386.xml delete mode 100644 nl/install-methods/floppy/powerpc.xml delete mode 100644 nl/install-methods/install-methods.xml delete mode 100644 nl/install-methods/install-tftp.xml delete mode 100644 nl/install-methods/ipl-tape.xml delete mode 100644 nl/install-methods/official-cdrom.xml delete mode 100644 nl/install-methods/tftp/bootp.xml delete mode 100644 nl/install-methods/tftp/dhcp.xml delete mode 100644 nl/install-methods/tftp/rarp.xml delete mode 100644 nl/install-methods/usb-setup/powerpc.xml delete mode 100644 nl/install-methods/usb-setup/x86.xml delete mode 100644 nl/partitioning/device-names.xml delete mode 100644 nl/partitioning/partition-programs.xml delete mode 100644 nl/partitioning/partition/hppa.xml delete mode 100644 nl/partitioning/partition/ia64.xml delete mode 100644 nl/partitioning/partition/mips.xml delete mode 100644 nl/partitioning/partition/powerpc.xml delete mode 100644 nl/partitioning/partition/sparc.xml delete mode 100644 nl/partitioning/partition/x86.xml delete mode 100644 nl/partitioning/partitioning.xml delete mode 100644 nl/partitioning/schemes.xml delete mode 100644 nl/partitioning/sizing.xml delete mode 100644 nl/partitioning/tree.xml delete mode 100644 nl/post-install/further-reading.xml delete mode 100644 nl/post-install/kernel-baking.xml delete mode 100644 nl/post-install/mail-setup.xml delete mode 100644 nl/post-install/new-to-unix.xml delete mode 100644 nl/post-install/orientation.xml delete mode 100644 nl/post-install/post-install.xml delete mode 100644 nl/post-install/rescue.xml delete mode 100644 nl/post-install/shutdown.xml delete mode 100644 nl/preface.xml delete mode 100644 nl/preparing/backup.xml delete mode 100644 nl/preparing/bios-setup/i386.xml delete mode 100644 nl/preparing/bios-setup/powerpc.xml delete mode 100644 nl/preparing/bios-setup/s390.xml delete mode 100644 nl/preparing/bios-setup/sparc.xml delete mode 100644 nl/preparing/install-overview.xml delete mode 100644 nl/preparing/minimum-hardware-reqts.xml delete mode 100644 nl/preparing/needed-info.xml delete mode 100644 nl/preparing/non-debian-partitioning.xml delete mode 100644 nl/preparing/nondeb-part/powerpc.xml delete mode 100644 nl/preparing/nondeb-part/sparc.xml delete mode 100644 nl/preparing/nondeb-part/x86.xml delete mode 100644 nl/preparing/pre-install-bios-setup.xml delete mode 100644 nl/preparing/preparing.xml delete mode 100644 nl/using-d-i/components.xml delete mode 100644 nl/using-d-i/loading-firmware.xml delete mode 100644 nl/using-d-i/modules/anna.xml delete mode 100644 nl/using-d-i/modules/apt-setup.xml delete mode 100644 nl/using-d-i/modules/autopartkit.xml delete mode 100644 nl/using-d-i/modules/base-installer.xml delete mode 100644 nl/using-d-i/modules/cdrom-checker.xml delete mode 100644 nl/using-d-i/modules/cdrom-detect.xml delete mode 100644 nl/using-d-i/modules/choose-mirror.xml delete mode 100644 nl/using-d-i/modules/clock-setup-finish.xml delete mode 100644 nl/using-d-i/modules/clock-setup.xml delete mode 100644 nl/using-d-i/modules/ddetect.xml delete mode 100644 nl/using-d-i/modules/finish-install.xml delete mode 100644 nl/using-d-i/modules/hppa/palo-installer.xml delete mode 100644 nl/using-d-i/modules/ia64/elilo-installer.xml delete mode 100644 nl/using-d-i/modules/iso-scan.xml delete mode 100644 nl/using-d-i/modules/kbd-chooser.xml delete mode 100644 nl/using-d-i/modules/localechooser.xml delete mode 100644 nl/using-d-i/modules/lowmem.xml delete mode 100644 nl/using-d-i/modules/mdcfg.xml delete mode 100644 nl/using-d-i/modules/mips/arcboot-installer.xml delete mode 100644 nl/using-d-i/modules/mipsel/colo-installer.xml delete mode 100644 nl/using-d-i/modules/netcfg.xml delete mode 100644 nl/using-d-i/modules/network-console.xml delete mode 100644 nl/using-d-i/modules/nobootloader.xml delete mode 100644 nl/using-d-i/modules/os-prober.xml delete mode 100644 nl/using-d-i/modules/partconf.xml delete mode 100644 nl/using-d-i/modules/partitioner.xml delete mode 100644 nl/using-d-i/modules/partman-crypto.xml delete mode 100644 nl/using-d-i/modules/partman-lvm.xml delete mode 100644 nl/using-d-i/modules/partman.xml delete mode 100644 nl/using-d-i/modules/pkgsel.xml delete mode 100644 nl/using-d-i/modules/powerpc/quik-installer.xml delete mode 100644 nl/using-d-i/modules/powerpc/yaboot-installer.xml delete mode 100644 nl/using-d-i/modules/s390/dasd.xml delete mode 100644 nl/using-d-i/modules/s390/netdevice.xml delete mode 100644 nl/using-d-i/modules/s390/zipl-installer.xml delete mode 100644 nl/using-d-i/modules/save-logs.xml delete mode 100644 nl/using-d-i/modules/shell.xml delete mode 100644 nl/using-d-i/modules/sparc/silo-installer.xml delete mode 100644 nl/using-d-i/modules/tzsetup.xml delete mode 100644 nl/using-d-i/modules/user-setup.xml delete mode 100644 nl/using-d-i/modules/x86/grub-installer.xml delete mode 100644 nl/using-d-i/modules/x86/lilo-installer.xml delete mode 100644 nl/using-d-i/using-d-i.xml delete mode 100644 nl/welcome/about-copyright.xml delete mode 100644 nl/welcome/doc-organization.xml delete mode 100644 nl/welcome/getting-newest-doc.xml delete mode 100644 nl/welcome/getting-newest-inst.xml delete mode 100644 nl/welcome/welcome.xml delete mode 100644 nl/welcome/what-is-debian-hurd.xml delete mode 100644 nl/welcome/what-is-debian-kfreebsd.xml delete mode 100644 nl/welcome/what-is-debian-linux.xml delete mode 100644 nl/welcome/what-is-debian.xml delete mode 100644 nl/welcome/what-is-linux.xml create mode 100644 po/nl/preface.po diff --git a/nl/administrivia/administrivia.xml b/nl/administrivia/administrivia.xml deleted file mode 100644 index a6a268923..000000000 --- a/nl/administrivia/administrivia.xml +++ /dev/null @@ -1,153 +0,0 @@ - - - - - Administrivia - - - - About This Document - - - -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. - - - -This document is written in DocBook XML. Output formats are generated -by various programs using information from the -docbook-xml and -docbook-xsl packages. - - - -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. - - - -Translators can use this paragraph to acknowledge the people responsible -for the translation of the manual. -Translation teams are advised to just mention the coordinator and maybe -major contributors and thank everybody else in a phrase like "all -translators and reviewers from the translation team for {your language} -at {your l10n mailinglist}". - -See build/lang-options/README on how to enable this paragraph. -Its condition is "about-langteam". - - - - - - Contributing to This Document - - - -If you have problems or suggestions regarding this document, you -should probably submit them as a bug report against the package -installation-guide. See the -reportbug package or read the online -documentation of the Debian Bug -Tracking System. It would be nice if you could check the -open bugs against -installation-guide to see whether your problem has -already been reported. If so, you can supply additional corroboration -or helpful information to -XXXX@bugs.debian.org, -where XXXX is the number for the -already-reported bug. - - - -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 -debian-installer WebSVN. 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 -README -from the source root directory. - - - -Please do not 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 -debian-boot@lists.debian.org. Instructions for -subscribing to this list can be found at the Debian Mailing -List Subscription page; or you can browse the Debian Mailing List Archives -online. - - - - - - - Major Contributions - - - -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 Amiga install manual), -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. - - - -Extremely helpful text and information was found in Jim Mintha's HOWTO -for network booting (no URL available), the Debian FAQ, the Linux/m68k FAQ, the Linux for SPARC Processors -FAQ, the Linux/Alpha -FAQ, amongst others. The maintainers of these freely -available and rich sources of information must be recognized. - - - -The section on chrooted installations in this manual -() was derived in part from -documents copyright Karsten M. Self. - - - -The section on installations over plip in this manual -() was based on the -PLIP-Install-HOWTO -by Gilles Lamiral. - - - - - - Trademark Acknowledgement - - -All trademarks are property of their respective trademark owners. - - - - - diff --git a/nl/appendix/chroot-install.xml b/nl/appendix/chroot-install.xml deleted file mode 100644 index 3198bf108..000000000 --- a/nl/appendix/chroot-install.xml +++ /dev/null @@ -1,675 +0,0 @@ - - - - - Installing &debian-gnu; from a Unix/Linux System - - - -This section explains how to install &debian-gnu; from an existing -Unix or Linux system, without using the menu-driven installer as -explained in the rest of the manual. This cross-install -HOWTO has been requested by users switching to &debian-gnu; from -Red Hat, Mandriva, and SUSE. In this section some familiarity with -entering *nix commands and navigating the file system is assumed. In -this section, $ symbolizes a command to be entered in -the user's current system, while # refers to a -command entered in the &debian; chroot. - - - -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 zero downtime &debian-gnu; -install. It's also a clever way for dealing with hardware that -otherwise doesn't play friendly with various boot or installation -media. - - - - - -As this is a mostly manual procedure, you should bear in mind that you -will need to do a lot of basic configuration of the system yourself, -which will also require more knowledge of &debian; and of &arch-kernel; in general -than performing a regular installation. You cannot expect this procedure -to result in a system that is identical to a system from a regular -installation. You should also keep in mind that this procedure only -gives the basic steps to set up a system. Additional installation and/or -configuration steps may be needed. - - - - - Getting Started - - -With your current *nix partitioning tools, repartition the hard -drive as needed, creating at least one filesystem plus swap. You -need around &base-system-size;MB of space available for a console only install, -or about &task-desktop-lxde-inst;MB if you plan to install X (more if you intend to -install desktop environments like GNOME or KDE). - - - -Next, create file systems on the partitions. For example, to create an -ext3 file system on partition /dev/hda6 (that's -our example root partition): - - -# mke2fs -j /dev/hda6 - - -To create an ext2 file system instead, omit -j. - - - -Initialize and activate swap (substitute the partition number for -your intended &debian; swap partition): - - -# mkswap /dev/hda5 -# sync; sync; sync -# swapon /dev/hda5 - - -Mount one partition as /mnt/debinst (the -installation point, to be the root (/) filesystem -on your new system). The mount point name is strictly arbitrary, it is -referenced later below. - - -# mkdir /mnt/debinst -# mount /dev/hda6 /mnt/debinst - - - - - -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. - - - - - - Install <command>debootstrap</command> - - -The utility used by the &debian; installer, and recognized as the -official way to install a &debian; base system, is -debootstrap. It uses wget and -ar, but otherwise depends only on -/bin/sh and basic Unix/Linux tools - - - -These include the GNU core utilities and commands like sed, grep, tar and gzip. - - - -. Install wget and -ar if they aren't already on your current system, -then download and install debootstrap. - - - - - - - -Or, you can use the following procedure to install it -manually. Make a work folder for extracting the .deb into: - - -# mkdir work -# cd work - - -The debootstrap binary is located in the &debian; -archive (be sure to select the proper file for your -architecture). Download the debootstrap .deb from -the -pool, copy the package to the work folder, and extract the -files from it. You will need to have root privileges to install -the files. - - -# ar -x debootstrap_0.X.X_all.deb -# cd / -# zcat /full-path-to-work/work/data.tar.gz | tar xv - - - - - - - Run <command>debootstrap</command> - - -debootstrap can download the needed files directly -from the archive when you run it. You can substitute any &debian; -archive mirror for &archive-mirror;/debian in -the command example below, preferably a mirror close to you -network-wise. Mirrors are listed at -. - - - -If you have a &releasename; &debian-gnu; CD mounted at -/cdrom, you could substitute a file URL instead -of the http URL: file:/cdrom/debian/ - - - -Substitute one of the following for ARCH -in the debootstrap command: - -alpha, -amd64, -arm, -armel, -hppa, -i386, -ia64, -m68k, -mips, -mipsel, -powerpc, -s390, or -sparc. - - -# /usr/sbin/debootstrap --arch ARCH &releasename; \ - /mnt/debinst http://ftp.us.debian.org/debian - - - - - - - Configure The Base System - - -Now you've got a real &debian; system, though rather lean, on disk. -chroot into it: - - -# LANG=C.UTF-8 chroot /mnt/debinst /bin/bash - - -After chrooting you may need to set the terminal definition to be -compatible with the &debian; base system, for example: - - -# export TERM=xterm-color - - - - - - Create device files - - -At this point /dev/ only contains very basic device -files. For the next steps of the installation additional device files may -be needed. There are different ways to go about this and which method you -should use depends on the host system you are using for the installation, -on whether you intend to use a modular kernel or not, and on whether you -intend to use dynamic (e.g. using udev) or static -device files for the new system. - - - -A few of the available options are: - - - - -create a default set of static device files using - -# cd /dev -# MAKEDEV generic - - - - - -manually create only specific device files using MAKEDEV - - - - -bind mount /dev from your host system on top of /dev in the target system; -note that the postinst scripts of some packages may try to create device -files, so this option should only be used with care - - - - - - - - - Mount Partitions - - -You need to create /etc/fstab. - - -# editor /etc/fstab - - -Here is a sample you can modify to suit: - - -# /etc/fstab: static file system information. -# -# file system mount point type options dump pass -/dev/XXX / ext3 defaults 0 1 -/dev/XXX /boot ext3 ro,nosuid,nodev 0 2 - -/dev/XXX none swap sw 0 0 -proc /proc proc defaults 0 0 - -/dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0 -/dev/cdrom /media/cdrom iso9660 noauto,ro,user,exec 0 0 - -/dev/XXX /tmp ext3 rw,nosuid,nodev 0 2 -/dev/XXX /var ext3 rw,nosuid,nodev 0 2 -/dev/XXX /usr ext3 rw,nodev 0 2 -/dev/XXX /home ext3 rw,nosuid,nodev 0 2 - - -Use mount -a to mount all the file systems you -have specified in your /etc/fstab, or, to mount -file systems individually, use: - - -# mount /path # e.g.: mount /usr - - -Current &debian; systems have mountpoints for removable media under -/media, but keep compatibility symlinks in -/. Create these as as needed, for example: - - -# cd /media -# mkdir cdrom0 -# ln -s cdrom0 cdrom -# cd / -# ln -s media/cdrom - - -You can mount the proc file system multiple times and to arbitrary -locations, though /proc is customary. If you didn't use -mount -a, be sure to mount proc before continuing: - - -# mount -t proc proc /proc - - - - -The command ls /proc should now show a non-empty -directory. Should this fail, you may be able to mount proc from outside -the chroot: - - -# mount -t proc proc /mnt/debinst/proc - - - - - - - Setting Timezone - - -An option in the file /etc/default/rcS determines -whether the system will interpret the hardware clock as being set to UTC -or local time. The following command allows you to set that and choose -your timezone. - - -# editor /etc/default/rcS -# dpkg-reconfigure tzdata - - - - - - - Configure Networking - - -To configure networking, edit -/etc/network/interfaces, -/etc/resolv.conf, -/etc/hostname and -/etc/hosts. - - -# editor /etc/network/interfaces - - -Here are some simple examples from -/usr/share/doc/ifupdown/examples: - - -###################################################################### -# /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 - - -Enter your nameserver(s) and search directives in -/etc/resolv.conf: - - -# editor /etc/resolv.conf - - -A simple example /etc/resolv.conf: - - -search hqdom.local -nameserver 10.1.1.36 -nameserver 192.168.9.100 - - -Enter your system's host name (2 to 63 characters): - - -# echo DebianHostName > /etc/hostname - - -And a basic /etc/hosts with IPv6 support: - - -127.0.0.1 localhost -127.0.1.1 DebianHostName - -# The following lines are desirable for IPv6 capable hosts -::1 ip6-localhost ip6-loopback -fe00::0 ip6-localnet -ff00::0 ip6-mcastprefix -ff02::1 ip6-allnodes -ff02::2 ip6-allrouters -ff02::3 ip6-allhosts - - -If you have multiple network cards, you should arrange the names of -driver modules in the /etc/modules file into the -desired order. Then during boot, each card will be associated with the -interface name (eth0, eth1, etc.) that you expect. - - - - - - Configure Apt - - -Debootstrap will have created a very basic -/etc/apt/sources.list that will allow installing -additional packages. However, you may want to add some additional sources, -for example for source packages and security updates: - - -deb-src http://ftp.us.debian.org/debian &releasename; main - -deb http://security.debian.org/ &releasename;/updates main -deb-src http://security.debian.org/ &releasename;/updates main - - -Make sure to run aptitude update after you have -made changes to the sources list. - - - - - - Configure Locales and Keyboard - - -To configure your locale settings to use a language other than -English, install the locales support package -and configure it. Currently the use of UTF-8 locales is recommended. - - -# aptitude install locales -# dpkg-reconfigure locales - - -To configure your keyboard (if needed): - - -# aptitude install console-setup -# dpkg-reconfigure keyboard-configuration - - - - -Note that the keyboard cannot be set while in the chroot, but will be -configured for the next reboot. - - - - - - - Install a Kernel - - -If you intend to boot this system, you probably want a &arch-kernel; kernel -and a boot loader. Identify available pre-packaged kernels with: - - -# apt-cache search &kernelpackage; - - - - -If you intend to use a pre-packaged kernel, you may want to create the -configuration file /etc/kernel-img.conf before you -do so. Here's an example file: - - -# Kernel image management overrides -# See kernel-img.conf(5) for details -do_symlinks = yes -relative_links = yes -do_bootloader = yes -do_bootfloppy = no -do_initrd = yes -link_in_boot = no - - - - -For detailed information about this file and the various options, consult -its man page which will be available after installing the -kernel-package package. We recommend that you check -that the values are appropriate for your system. - - - -Then install the kernel package of your choice using its package name. - - -# aptitude install &kernelpackage;-&kernelversion;-arch-etc - - -If you did not create a /etc/kernel-img.conf before -installing a pre-packaged kernel, you may be asked some questions during -its installation that refer to it. - - - - - -Set up the Boot Loader - - -To make your &debian-gnu; 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 aptitude inside your &debian; chroot to do so. - - - -Check info grub or man -lilo.conf 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 -menu.lst or lilo.conf. For -lilo.conf, you could also copy it to the new system and -edit it there. After you are done editing, call lilo -(remember it will use -lilo.conf relative to the system you call it from). - - - -Installing and setting up grub is as easy as: - - -# aptitude install grub -# grub-install /dev/hda -# update-grub - - -The second command will install grub (in this case in -the MBR of hda). The last command will create a sane -and working /boot/grub/menu.lst. - - - -Note that this assumes that a /dev/hda device file has -been created. There are alternative methods to install grub, -but those are outside the scope of this appendix. - - - -Here is a basic /etc/lilo.conf as an example: - - -boot=/dev/hda6 -root=/dev/hda6 -install=menu -delay=20 -lba32 -image=/vmlinuz -initrd=/initrd.img -label=Debian - - - - -Depending on which bootloader you selected, you can now make some -additional changes in /etc/kernel-img.conf. - - - -For the grub bootloader, you should -set the do_bootloader option to no. -And to automatically update your /boot/grub/menu.lst -on installation or removal of &debian; kernels, add the following lines: - - -postinst_hook = update-grub -postrm_hook = update-grub - - -For the lilo bootloader, the value of -do_bootloader needs to remain yes. - - - -Check man yaboot.conf 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 yaboot.conf. You could also copy it to -the new system and -edit it there. After you are done editing, call ybin (remember it will -use yaboot.conf relative to the system you call it from). - - - -Here is a basic /etc/yaboot.conf as an example: - - -boot=/dev/hda2 -device=hd: -partition=6 -root=/dev/hda6 -magicboot=/usr/lib/yaboot/ofboot -timeout=50 -image=/vmlinux -label=Debian - - -On some machines, you may need to use ide0: -instead of hd:. - - - - - -Finishing touches - - -As mentioned earlier, the installed system will be very basic. If you -would like to make the system a bit more mature, there is an easy method -to install all packages with standard priority: - - -# tasksel install standard - - -Of course, you can also just use aptitude to install -packages individually. - - - -After the installation there will be a lot of downloaded packages in -/var/cache/apt/archives/. You can free up some -diskspace by running: - - -# aptitude clean - - - - - diff --git a/nl/appendix/files.xml b/nl/appendix/files.xml deleted file mode 100644 index 9de7f07d9..000000000 --- a/nl/appendix/files.xml +++ /dev/null @@ -1,354 +0,0 @@ - - - - - Linux Devices - - -In Linux various special files can be found under the directory -/dev. These files are called device files and -behave unlike ordinary files. The most common types of device files -are for block devices and character devices. These files are an -interface to the actual driver (part of the Linux kernel) which in -turn accesses the hardware. Another, less common, type of device file -is the named pipe. -The most important device files are listed in the tables below. - - - - - - fd0 - First Floppy Drive - - fd1 - Second Floppy Drive - - - - - - hda - IDE Hard disk / CD-ROM on the first IDE port (Master) - - hdb - IDE Hard disk / CD-ROM on the first IDE port (Slave) - - hdc - IDE Hard disk / CD-ROM on the second IDE port (Master) - - hdd - IDE Hard disk / CD-ROM on the second IDE port (Slave) - - hda1 - First partition of the first IDE hard disk - - hdd15 - Fifteenth partition of the fourth IDE hard disk - - - - - - sda - SCSI Hard disk with lowest SCSI ID (e.g. 0) - - sdb - SCSI Hard disk with next higher SCSI ID (e.g. 1) - - sdc - SCSI Hard disk with next higher SCSI ID (e.g. 2) - - sda1 - First partition of the first SCSI hard disk - - sdd10 - Tenth partition of the fourth SCSI hard disk - - - - - - sr0 - SCSI CD-ROM with the lowest SCSI ID - - sr1 - SCSI CD-ROM with the next higher SCSI ID - - - - - - ttyS0 - Serial port 0, COM1 under MS-DOS - - ttyS1 - Serial port 1, COM2 under MS-DOS - - psaux - PS/2 mouse device - - gpmdata - Pseudo device, repeater data from GPM (mouse) daemon - - - - - - cdrom - Symbolic link to the CD-ROM drive - - mouse - Symbolic link to the mouse device file - - - - - - null - Anything written to this device will disappear - - zero - One can endlessly read zeros out of this device - - - - - - - Setting Up Your Mouse - - -The mouse can be used in both the Linux console (with gpm) and the X -window environment. Normally, this is a simple matter of installing -gpm and the X server itself. Both should be -configured to use /dev/input/mice as the mouse -device. The correct mouse protocol is named exps2 -in gpm, and ExplorerPS/2 in X. The respective -configuration files are /etc/gpm.conf and -/etc/X11/xorg.conf. - - - -Certain kernel modules must be loaded in order for your mouse to work. -In most cases the correct modules are autodetected, but not always for -old-style serial and bus mice - - -Serial mice usually have a 9-hole D-shaped connector; bus mice have an -8-pin round connector, not to be confused with the 6-pin round connector -of a PS/2 mouse or the 4-pin round connector of an ADB mouse. - - -, which are quite rare except on very old computers. Summary -of Linux kernel modules needed for different mouse types: - - - - Module - Description - - - - psmouse - PS/2 mice (should be autodetected) - - - usbhid - USB mice (should be autodetected) - - - sermouse - Most serial mice - - - logibm - Bus mouse connected to Logitech adapter card - - - inport - Bus mouse connected to ATI or Microsoft InPort card - - - -To load a mouse driver module, you can use the modconf -command (from the package with the same name) and look in the category -kernel/drivers/input/mouse. - - - - -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 -/etc/sysctl.conf file. - - -# 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. - - - - - - - - Disk Space Needed for Tasks - - -A standard installation for the amd64 architecture, including all standard -packages and using the default 2.6 kernel, takes up &std-system-size;MB of disk space. -A minimal base installation, without the Standard system -task selected, will take &base-system-size;MB. - - - - -In both cases this is the actual disk space used after -the installation is finished and any temporary files deleted. It also does -not take into account overhead used by the file system, for example for -journal files. This means that significantly more disk space is needed both -during the installation and for normal system use. - - - - -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. - - - -By default the installer will install the GNOME desktop environment, but -alternative desktop environments can be selected either by using one -of the special CD images, or by specifying the desired desktop environment -when the installer is booted (see ). - - - -Note that you will need to add the sizes listed in the table to the size -of the standard installation when determining the size of partitions. -Most of the size listed as Installed size will end up in -/usr and in /lib; -the size listed as Download size -is (temporarily) required in /var. - - - - - - - Task - Installed size (MB) - Download size (MB) - Space needed to install (MB) - - - - - - Desktop environment -   -   -   - - -   • GNOME (default) - &task-desktop-gnome-inst; - &task-desktop-gnome-dl; - &task-desktop-gnome-tot; - - -   • KDE - &task-desktop-kde-inst; - &task-desktop-kde-dl; - &task-desktop-kde-tot; - - -   • Xfce - &task-desktop-xfce-inst; - &task-desktop-xfce-dl; - &task-desktop-xfce-tot; - - -   • LXDE - &task-desktop-lxde-inst; - &task-desktop-lxde-dl; - &task-desktop-lxde-tot; - - - - Laptop - - - There is some overlap of the Laptop task with the Desktop environment task. - If you install both, the Laptop task will only require a few MB additional - disk space. - - - - &task-laptop-inst; - &task-laptop-dl; - &task-laptop-tot; - - - - Web server - &task-web-inst; - &task-web-dl; - &task-web-tot; - - - - Print server - &task-print-inst; - &task-print-dl; - &task-print-tot; - - - - DNS server - &task-dns-inst; - &task-dns-dl; - &task-dns-tot; - - - - File server - &task-file-inst; - &task-file-dl; - &task-file-tot; - - - - Mail server - &task-mail-inst; - &task-mail-dl; - &task-mail-tot; - - - - SQL database - &task-sql-inst; - &task-sql-dl; - &task-sql-tot; - - - - - - - -If you install in a language other than English, tasksel -may automatically install a localization task, if one -is available for your language. Space requirements differ per language; -you should allow up to 350MB in total for download and installation. - - - diff --git a/nl/appendix/gpl.xml b/nl/appendix/gpl.xml deleted file mode 100644 index e93459139..000000000 --- a/nl/appendix/gpl.xml +++ /dev/null @@ -1,525 +0,0 @@ - - - -GNU General Public License - - - -[[This note, consisting of two paragraphs, should only be included in your -translation if you translate the GPL in this appendix. -See build/lang-options/README on how to enable this paragraph and for -additional information. Its condition is "gpl-unofficial".]] -[[LEAVE THIS PARAGRAPH IN ENGLISH! Only replace {language} with the English -name of your language. Do not change the link to the GPL!]] - -This is an unofficial translation of the GNU General Public License into -{language}. It was not published by the Free Software Foundation, and does -not legally state the distribution terms for software that uses the GNU -GPL — only the original English -text of the GNU GPL does that. However, we hope that this translation -will help {language} speakers to better understand the GNU GPL. - - - -[[See build/lang-options/README on how to enable this paragraph and for -additional information. Its condition is "gpl-unofficial".]] -[[THIS PARAGRAPH SHOULD BE TRANSLATED. Replace {language} with the English -name of your language before translating. Do not change the link to the GPL!]] - -This is an unofficial translation of the GNU General Public License into -{language}. It was not published by the Free Software Foundation, and does -not legally state the distribution terms for software that uses the GNU -GPL — only the original English -text of the GNU GPL does that. However, we hope that this translation -will help {language} speakers to better understand the GNU GPL. - - - - -Version 2, June 1991 - - -Copyright (C) 1989, 1991 Free Software Foundation, Inc. -51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA. - -Everyone is permitted to copy and distribute verbatim copies -of this license document, but changing it is not allowed. - - - - - Preamble - - -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. - - - -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. - - - -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. - - - -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. - - - -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. - - - -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. - - - -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. - - - -The precise terms and conditions for copying, distribution and -modification follow. - - - - - GNU GENERAL PUBLIC LICENSE - - -TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION -AND MODIFICATION - - - -0. -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". - - - -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. - - - -1. -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. - - - -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. - - - -2. -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: - - - - -You must cause the modified files to carry prominent notices -stating that you changed the files and the date of any change. - - - - -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. - - - - -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.) - - - - -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. - - - -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. - - - -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. - - - -3. -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: - - - - -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, - - - - -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, - - - - -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.) - - - - -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. - - - -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. - - - -4. -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. - - - -5. -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. - - - -6. -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. - - - -7. -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. - - - -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. - - - -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. - - - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - - -8. -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. - - - -9. -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. - - - -10. -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. - - - -NO WARRANTY - - - -11. -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. - - - -12. -IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN -WRITING WILL AND COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY -AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU -FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR -CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE -PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING -RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A -FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF -SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF -SUCH DAMAGES. - - - -END OF TERMS AND CONDITIONS - - - - - How to Apply These Terms to Your New Programs - - -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. - - - -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. - - -one line to give the program's name and a brief idea of what it does. -Copyright (C) year name of author - -This program is free software; you can redistribute it and/or -modify it under the terms of the GNU General Public License -as published by the Free Software Foundation; either version 2 -of the License, or (at your option) any later version. - -This program is distributed in the hope that it will be useful, -but WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the -GNU General Public License for more details. - -You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software -Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. - - - - -Also add information on how to contact you by electronic and paper -mail. - - - -If the program is interactive, make it output a short notice like -this when it starts in an interactive mode: - - -Gnomovision version 69, Copyright (C) year name of author -Gnomovision comes with absolutely no warranty; for details -type `show w'. This is free software, and you are welcome -to redistribute it under certain conditions; type `show c' -for details. - - - - -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. - - - -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: - - -Yoyodyne, Inc., hereby disclaims all copyright interest in the -program `Gnomovision' (which makes passes at compilers) written -by James Hacker. - -signature of Ty Coon, 1 April 1989 -Ty Coon, President of Vice - - - - -This General Public License does not permit incorporating your -program into proprietary programs. If your program is a subroutine -library, you may consider it more useful to permit linking -proprietary applications with the library. If this is what you want -to do, use the GNU Lesser General Public License instead of this -License. - - - - diff --git a/nl/appendix/graphical.xml b/nl/appendix/graphical.xml deleted file mode 100644 index 1b875377e..000000000 --- a/nl/appendix/graphical.xml +++ /dev/null @@ -1,148 +0,0 @@ - - - - - The Graphical Installer - - -The graphical version of the installer is only available for a limited -number of architectures, including &arch-title;. The functionality of -the graphical installer is essentially the same as that of the regular -installer as it basically uses the same programs, but with a different -frontend. - - - -Although the functionality is identical, the graphical installer still has -a few significant advantages. The main advantage is that it supports more -languages, namely those that use a character set that cannot be displayed -with the regular newt frontend. It also has a few usability -advantages such as the option to use a mouse, and in some cases several -questions can be displayed on a single screen. - - - -The graphical installer is available with all CD images and with the -hd-media installation method. To boot the graphical installer simply select -the relevant option from the boot menu. Expert and rescue mode for the -graphical installer can be selected from the Advanced options -menu. The previously used boot methods installgui, -expertgui and rescuegui can -still be used from the boot prompt which is shown after selecting the -Help option in the boot menu. - - - -There is also a graphical installer image that can be netbooted. And there -is a special mini ISO image - - -The mini ISO image can be downloaded from a &debian; mirror as described -in . -Look for netboot/gtk/mini.iso. - - -, which is mainly useful for testing. - - - -For &arch-title;, currently only an experimental mini ISO -image is available - - -The mini ISO image can be downloaded from a &debian; mirror as described -in . -Look for netboot/gtk/mini.iso. - - -. It should work on almost all PowerPC systems that have -an ATI graphical card, but is unlikely to work on other systems. - - - -Just as with the regular installer it is possible to add boot parameters -when starting the graphical installer. One of those parameters allows to -configure the mouse for left-handed use. Others allow to select the mouse -device (e.g. for a serial mouse) and the mouse protocol. See - for valid parameters and - for information on how to pass them. - - - - -The graphical installer requires significantly more memory to run than -the regular installer: &minimum-memory-gtk;. If insufficient memory is -available, it will automatically fall back to the regular -newt frontend. - - - -If the amount of memory in your system is below &minimum-memory;, -the graphical installer may fail to boot at all while booting the -regular installer would still work. Using the regular installer is -recommended for systems with little available memory. - - - - - Using the graphical installer - - -As already mentioned, the graphical installer basically works the same as -the regular installer and thus the rest of this manual can be used to guide -you through the installation process. - - - -If you prefer using the keyboard over the mouse, there are two things you -need to know. To expand a collapsed list (used for example for the selection -of countries within continents), you can use the + and -- keys. For questions where more than one item can be -selected (e.g. task selection), you first need to tab to the -&BTN-CONT; button after making your selections; hitting -enter will toggle a selection, not activate &BTN-CONT;. - - - -If a dialog offers additional help information, a Help -button will be displayed. The help information can be accessed either by -activating the button or by pressing the F1 key. - - - -To switch to another console, you will also need to use the -Ctrl key, just as with the X Window System. For example, -to switch to VT2 (the first debug shell) you would use: -Ctrl Left Alt F2 -. The graphical installer itself runs on VT5, so you can use - Left Alt F5 -to switch back. - - - - - - Known issues - - -The graphical frontend to the installer is relatively new and because of -that there are some known issues. We continue to work on resolving these. - - - - - - -Information on some screens is not yet nicely formatted into columns as it -should be. - - - - -Support for touchpads is not yet optimal. - - - - - - diff --git a/nl/appendix/plip.xml b/nl/appendix/plip.xml deleted file mode 100644 index 830d75232..000000000 --- a/nl/appendix/plip.xml +++ /dev/null @@ -1,187 +0,0 @@ - - - - - Installing &debian-gnu; over Parallel Line IP (PLIP) - - - -This section explains how to install &debian-gnu; on a computer without an -Ethernet card, but with just a remote gateway computer attached via -a Null-Modem cable (also called Null-Printer cable). The gateway -computer should be connected to a network that has a &debian; mirror -on it (e.g. to the Internet). - - - -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). - - - -The PLIP connection set up during the installation will also be available -after the reboot into the installed system (see ). - - - -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 io=0x378, -irq=7. - - - - - Requirements - - - - -A target computer, called target, where &debian; will be -installed. - - - - -System installation media; see . - - - - -Another computer connected to the Internet, called source, -that will function as the gateway. - - - - -A DB-25 Null-Modem cable. See the -PLIP-Install-HOWTO for more -information on this cable and instructions how to make your own. - - - - - - - - Setting up source - - -The following shell script is a simple example of how to configure the -source computer as a gateway to the Internet using ppp0. - - -#!/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=0x378 irq=7 -modprobe plip - -# Configure the plip interface (plip0 for me, see dmesg | grep plip) -ifconfig plip0 192.168.0.2 pointopoint 192.168.0.1 netmask 255.255.255.255 up - -# Configure gateway -modprobe iptable_nat -iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE -echo 1 > /proc/sys/net/ipv4/ip_forward - - - - - - - Installing target - - -Boot the installation media. The installation needs to be run in -expert mode; enter expert at the boot prompt. -If you need to set parameters for kernel modules, you also need to -do this at the boot prompt. For example, to boot the installer and -set values for the io and irq options -for the parport_pc module, enter the following at the boot prompt: - - -expert parport_pc.io=0x378 parport_pc.irq=7 - - -Below are the answers that should be given during various stages of -the installation. - - - - - - -Load installer components from CD - - - -Select the plip-modules option from the list; this -will make the PLIP drivers available to the installation system. - - - - -Detect network hardware - - - - - - -If target does 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. - - - - -Because no network card was detected/selected earlier, the installer will -ask you to select a network driver module from a list. -Select the plip module. - - - - - - - -Configure the network - - - - -Auto-configure network with DHCP: No - - - - -IP address: 192.168.0.1 - - - - -Point-to-point address: -192.168.0.2 - - - - -Name server addresses: you can enter the same addresses used on -source (see /etc/resolv.conf) - - - - - - - - - diff --git a/nl/appendix/pppoe.xml b/nl/appendix/pppoe.xml deleted file mode 100644 index a48f2f976..000000000 --- a/nl/appendix/pppoe.xml +++ /dev/null @@ -1,109 +0,0 @@ - - - - - Installing &debian-gnu; using PPP over Ethernet (PPPoE) - - - -In some countries PPP over Ethernet (PPPoE) is a common protocol for -broadband (ADSL or cable) connections to an Internet Service Provider. -Setting up a network connection using PPPoE is not supported by default -in the installer, but can be made to work very simply. This section -explains how. - - - -The PPPoE connection set up during the installation will also be available -after the reboot into the installed system (see ). - - - -To have the option of setting up and using PPPoE during the installation, -you will need to install using one of the CD-ROM/DVD images that are -available. It is not supported for other installation methods (e.g. -netboot or floppy). - - - -Installing over PPPoE is mostly the same as any other installation. The -following steps explain the differences. - - - - - - -Boot the installer with the boot parameter -modules=ppp-udeb - - -See for information on -how to add a boot parameter. - - -. -This will ensure the component responsible for the setup of PPPoE -(ppp-udeb) will be loaded and run automatically. - - - - -Follow the regular initial steps of the installation (language, -country and keyboard selection; the loading of additional installer -components - - - -The ppp-udeb component is loaded as one of -the additional components in this step. If you want to install at -medium or low priority (expert mode), you can also manually select -the ppp-udeb instead of entering the -modules parameter at the boot prompt. - - - -). - - - - -The next step is the detection of network hardware, in order to identify -any Ethernet cards present in the system. - - - - -After this the actual setup of PPPoE is started. The installer will probe -all the detected Ethernet interfaces in an attempt to find a PPPoE -concentrator (a type of server which handles PPPoE connections). - - - -It is possible that the concentrator will not to be found at the first -attempt. This can happen occasionally on slow or loaded networks or with -faulty servers. In most cases a second attempt to detect the concentrator -will be successful; to retry, select Configure and start a -PPPoE connection from the main menu of the installer. - - - - -After a concentrator is found, the user will be prompted to type the login -information (the PPPoE username and password). - - - - -At this point the installer will use the provided information to establish -the PPPoE connection. If the correct information was provided, the PPPoE -connection should be configured and the installer should be able to use it -to connect to the Internet and retrieve packages over it (if needed). If -the login information is not correct or some error appears, the installer -will stop, but the configuration can be attempted again by selecting the -menu entry Configure and start a PPPoE connection. - - - - - diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml deleted file mode 100644 index 90ce8a4f6..000000000 --- a/nl/appendix/preseed.xml +++ /dev/null @@ -1,1624 +0,0 @@ - - - - - - -Automating the installation using preseeding - - - -This appendix explains how to preseed answers to questions in &d-i; to -automate your installation. - - - -The configuration fragments used in this appendix are also available as an -example preconfiguration file from &urlset-example-preseed;. - - - - - Introduction - - -Preseeding provides a way to set answers to questions asked during the -installation process, without having to manually enter the answers while -the installation is running. This makes it possible to fully automate most -types of installation and even offers some features not available during -normal installations. - - - -Preseeding is not required. If you use an empty preseed file, the installer -will behave just the same way as in a normal manual installation. Each -question you preseed will (if you got it right!) modify the installation in -some way from that baseline. - - - - - Preseeding methods - - -There are three methods that can be used for preseeding: -initrd, file and -network. Initrd preseeding will work with any -installation method and supports preseeding of more things, but it requires -the most preparation. File and network preseeding each can be used with -different installation methods. - - - -The following table shows which preseeding methods can be used with which -installation methods. - - - - - - Installation methodinitrd - filenetwork - - - - - - CD/DVD - yes - yes - yes - - - but only if you have network access, and set preseed/url - appropriately - - - - - netboot - yes - no - yes - - hd-media (including usb-stick) - yes - yes - yes - - floppy based (cd-drivers) - yes - yes - yes - - floppy based (net-drivers) - yes - no - yes - - generic/tape - yes - no - yes - - - - - - - -An important difference between the preseeding methods is the point at which -the preconfiguration file is loaded and processed. For initrd preseeding -this is right at the start of the installation, before the first question is -even asked. For file preseeding this is after the CD or CD image has been -loaded. For network preseeding it is only after the network has been -configured. - - - -Obviously, any questions that have been processed before the -preconfiguration file is loaded cannot be preseeded (this will include -questions that are only displayed at medium or low priority, like the -first hardware detection run). -offers a way to avoid these questions being asked. - - - -In order to avoid the questions that would normally appear before the -preseeding occurs, you can start the installer in auto -mode. This delays questions that would normally be asked too early for -preseeding (i.e. language, country and keyboard selection) until after -the network comes up, thus allowing them to be preseeded. It also runs -the installation at critical priority, which avoids many unimportant -questions. See for details. - - - - - - Limitations - - -Although most questions used by &d-i; can be preseeded using this method, -there are some notable exceptions. You must (re)partition an entire disk -or use available free space on a disk; it is not possible to use existing -partitions. - - - - - - - - - - Using preseeding - - -You will first need to create a preconfiguration file and place it in -the location from where you want to use it. Creating the preconfiguration file -is covered later in this appendix. Putting it in the correct location is fairly -straightforward for network preseeding or if you want to read the file off -a floppy or usb-stick. If you want to include the file on a CD or DVD, you -will have to remaster the ISO image. How to get the preconfiguration file -included in the initrd is outside the scope of this document; please consult -the developers' documentation for &d-i;. - - - -An example preconfiguration file that you can use as basis for your own -preconfiguration file is available from &urlset-example-preseed;. This file is -based on the configuration fragments included in this appendix. - - - - - Loading the preconfiguration file - - -If you are using initrd preseeding, you only have to make sure a file named -preseed.cfg is included in the root directory of the -initrd. The installer will automatically check if this file is present and -load it. - - - -For the other preseeding methods you need to tell the installer what file -to use when you boot it. This is normally done by passing the kernel a boot -parameter, either manually at boot time or by editing the bootloader -configuration file (e.g. syslinux.cfg) and adding the -parameter to the end of the append line(s) for the kernel. - - - -If you do specify the preconfiguration file in the bootloader configuration, -you might change the configuration so you don't need to hit enter to boot the -installer. For syslinux this means setting the timeout to 1 -in syslinux.cfg. - - - -To make sure the installer gets the right preconfiguration file, you can -optionally specify a checksum for the file. Currently this needs to be a -md5sum, and if specified it must match the preconfiguration file or the -installer will refuse to use it. - - - - -Boot parameters to specify: -- if you're netbooting: - preseed/url=http://host/path/to/preseed.cfg - preseed/url/checksum=5da499872becccfeda2c4872f9171c3d - -- if you're booting a remastered CD: - preseed/file=/cdrom/preseed.cfg - preseed/file/checksum=5da499872becccfeda2c4872f9171c3d - -- if you're installing from USB media (put the preconfiguration file in the - toplevel directory of the USB stick): - preseed/file=/hd-media/preseed.cfg - preseed/file/checksum=5da499872becccfeda2c4872f9171c3d - - - - -Note that preseed/url can be shortened to just -url and preseed/file to just -file when they are passed as boot parameters. - - - - - - Using boot parameters to preseed questions - - -If a preconfiguration file cannot be used to preseed some steps, the -install can still be fully automated, since you can pass preseed values on -the command line when booting the installer. - - - -Boot parameters can also be used if you do not really want to use preseeding, -but just want to provide an answer for a specific question. Some examples where -this can be useful are documented elsewhere in this manual. - - - -To set a value to be used inside &d-i;, just pass -path/to/variable=value -for any of the preseed variables listed in the examples in this appendix. -If a value is to be used to configure packages for the target system, you -will need to prepend the owner - - -The owner of a debconf variable (or template) is normally the name of the -package that contains the corresponding debconf template. For variables -used in the installer itself the owner is d-i. -Templates and variables can have more than one owner which helps to -determine whether they can be removed from the debconf database if the -package is purged. - - - of the variable as in -owner:path/to/variable=value. -If you don't specify the owner, the value for the variable will not be -copied to the debconf database in the target system and thus remain unused -during the configuration of the relevant package. - - - -Normally, preseeding a question in this way will mean that the question will -not be asked. To set a specific default value for a question, but still have -the question asked, use ?= instead of = as -operator. See also . - - - -Note that some variables that are frequently set at the boot prompt -have a shorter alias. If an alias is available, it is used in the -examples in this appendix instead of the full variable. The -preseed/url variable for example has been aliased as -url. Another example is the tasks -alias, which translates to tasksel:tasksel/first. - - - -A -- in the boot options has special meaning. Kernel -parameters that appear after the last -- may be copied -into the bootloader configuration for the installed system (if supported by -the installer for the bootloader). The installer will automatically filter -out any options (like preconfiguration options) that it recognizes. - - - - -Current linux kernels (2.6.9 and later) accept a maximum of 32 command line -options and 32 environment options, including any options added by default -for the installer. If these numbers are exceeded, the kernel will panic -(crash). (For earlier kernels, these numbers were lower.) - - - - -For most installations some of the default options in your bootloader -configuration file, like vga=normal, may be safely -removed which may allow you to add more options for preseeding. - - - - -It may not always be possible to specify values with spaces for boot -parameters, even if you delimit them with quotes. - - - - - - Auto mode - - -There are several features of &debian; Installer that combine to allow -fairly simple command lines at the boot prompt to result in -arbitrarily complex customized automatic installs. To illustrate -this, here are some examples that can be used at the boot prompt: - - -auto url=autoserver - - -This relies on there being a DHCP server that will get the machine to -the point where autoserver can be resolved by DNS, -perhaps after adding the local domain if that was provided by DHCP. -If this was done at a site where the domain is -example.com, and they have a reasonably sane DHCP -setup, it would result in the preseed file being retrieved from -http://autoserver.example.com/d-i/&releasename;/./preseed.cfg. - - - -The last part of that url (d-i/&releasename;/./preseed.cfg) -is taken from auto-install/defaultroot. By default -this includes the directory &releasename; to allow future versions -to specify their own codename and let people migrate forwards in a -controlled manner. The /./ bit is used to indicate -a root, relative to which subsequent paths can be anchored (for use in -preseed/include and preseed/run). This allows files to be specified -either as full URLs, paths starting with / that are thus anchored, or -even paths relative to the location where the last preseed file was -found. This can be used to construct more portable scripts where an -entire hierarchy of scripts can be moved to a new location without -breaking it, for example copying the files onto a USB stick when they -started out on a web server. In this example, if the preseed file -sets preseed/run to -/scripts/late_command.sh then the file will be -fetched from -http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh. - - - -If there is no local DHCP or DNS infrastructure, or if you do not want to -use the default path to preseed.cfg, you can still -use an explicit url, and if you don't use the /./ -element it will be anchored to the start of the path (i.e. the third -/ in the URL). Here is an example that requires minimal -support from the local network infrastructure: - - -auto url=http://192.168.1.2/path/to/mypreseed.file - - -The way this works is that: - - -if the URL is missing a protocol, http is assumed, - - -if the hostname section contains no periods, it has the domain derived -from DHCP appended to it, and - - -if there's no /'s after the hostname, then the default -path is added. - - - - - -In addition to specifying the url, you can also specify settings that -do not directly affect the behavior of &d-i; itself, but can be passed -through to scripts specified using preseed/run -in the loaded preseed file. At present, the only example of -this is auto-install/classes, which has an alias -classes. This can be used thus: - - -auto url=example.com classes=class_A;class_B - - -The classes could for example denote the type of system to be installed, -or the localization to be used. - - - -It is of course possible to extend this concept, and if you do, it is -reasonable to use the auto-install namespace for this. So one might have -something like auto-install/style which is then used -in your scripts. If you feel the need to do this, please mention it on -the debian-boot@lists.debian.org mailing list so that we -can avoid namespace conflicts, and perhaps add an alias for the parameter -for you. - - - -The auto boot label is not yet defined everywhere. -The same effect may be achieved by simply adding the two -parameters auto=true priority=critical to the kernel -command line. The auto parameter is an alias for -auto-install/enable and setting it to -true delays the -locale and keyboard questions until after there has been a chance to -preseed them, while priority is an alias for -debconf/priority and setting it to -critical stops any questions with a lower priority -from being asked. - - - -Additional options that may be of interest while attempting to -automate an install while using DHCP are: interface=auto -netcfg/dhcp_timeout=60 which makes the machine choose the -first viable NIC and be more patient about getting a reply to its -DHCP query. - - - - -An extensive example of how to use this framework, including example scripts -and classes, can be found on the website -of its developer. The examples available there also show many other -nice effects that can be achieved by creative use of preconfiguration. - - - - - - Aliases useful with preseeding - - -The following aliases can be useful when using (auto mode) preseeding. -Note that these are simply short aliases for question names, and you -always need to specify a value as well: for example, -auto=true or interface=eth0. - - - - - - -autoauto-install/enable -classesauto-install/classes -fbdebian-installer/framebuffer -languagedebian-installer/language -countrydebian-installer/country -localedebian-installer/locale -prioritydebconf/priority -filepreseed/file -urlpreseed/url -interfacenetcfg/choose_interface -hostname   netcfg/get_hostname -domainnetcfg/get_domain -protocolmirror/protocol -suitemirror/suite - - - - - - - Using a DHCP server to specify preconfiguration files - - -It's also possible to use DHCP to specify a preconfiguration file to download -from the network. DHCP allows specifying a filename. Normally this is a file -to netboot, but if it appears to be an URL then installation media that -support network preseeding will download the file from the URL and use it as a -preconfiguration file. Here is an example of how to set it up in the dhcpd.conf -for version 3 of the ISC DHCP server (the dhcp3-server &debian; package). - - - - -if substring (option vendor-class-identifier, 0, 3) = "d-i" { - filename "http://host/preseed.cfg"; -} - - - - -Note that the above example limits this filename to DHCP clients that identify -themselves as "d-i", so it will not affect regular DHCP clients, but only -the installer. You can also put the text in a stanza for only one particular -host to avoid preseeding all installs on your network. - - - -A good way to use the DHCP preseeding is to only preseed values specific to -your network, such as the &debian; mirror to use. This way installs on your -network will automatically get a good mirror selected, but the rest of the -installation can be performed interactively. Using DHCP preseeding to fully -automate &debian; installs should only be done with care. - - - - - - - - Creating a preconfiguration file - - -The preconfiguration file is in the format used by the -debconf-set-selections command. The general format of -a line in a preconfiguration file is: - - -<owner> <question name> <question type> <value> - - - - -There are a few rules to keep in mind when writing a preconfiguration file. - - - - - - Put only a single space or tab between type and value: any additional - whitespace will be interpreted as belonging to the value. - - - A line can be split into multiple lines by appending a backslash - (\) as the line continuation character. - A good place to split a line is after the question name; a bad place is - between type and value. Split lines will be joined into a single line - with all leading/trailing whitespace condensed to a single space. - - - For debconf variables (templates) used in the installer itself, the - owner should be set to d-i; to preseed variables used - in the installed system, the name of the package that contains the - corresponding debconf template should be used. Only variables that have - their owner set to something other than d-i will be - propagated to the debconf database for the installed system. - - - Most questions need to be preseeded using the values valid in English and - not the translated values. However, there are some questions (for example - in partman) where the translated values need to be - used. - - - Some questions take a code as value instead of the English text that is - shown during installation. - - - - - -The easiest way to create a preconfiguration file is to use the example file -linked in as basis and work from there. - - - -An alternative method is to do a manual installation and then, after -rebooting, use the debconf-get-selections from the -debconf-utils package to dump both the debconf -database and the installer's cdebconf database to a single file: - - -$ debconf-get-selections --installer > file -$ debconf-get-selections >> file - - - - -However, a file generated in this manner will have some items that should -not be preseeded, and the example file is a better starting place for most -users. - - - - - -This method relies on the fact that, at the end of the installation, the -installer's cdebconf database is saved to the installed system in -/var/log/installer/cdebconf. However, because the -database may contain sensitive information, by default the files are only -readable by root. - - - -The directory /var/log/installer and all files in it -will be deleted from your system if you purge the package -installation-report. - - - - - -To check possible values for questions, you can use nano -to examine the files in /var/lib/cdebconf while an -installation is in progress. View templates.dat for -the raw templates and questions.dat for the current -values and for the values assigned to variables. - - - -To check if the format of your preconfiguration file is valid before performing -an install, you can use the command debconf-set-selections -c -preseed.cfg. - - - - - - - Contents of the preconfiguration file (for &releasename;) - - -The configuration fragments used in this appendix are also available as an -example preconfiguration file from &urlset-example-preseed;. - - - -Note that this example is based on an installation for the Intel x86 -architecture. If you are installing a different architecture, some of the -examples (like keyboard selection and bootloader installation) may not be -relevant and will need to be replaced by debconf settings appropriate for -your architecture. - - - - - Localization - - -Setting localization values will only work if you are using initrd preseeding. -With all other methods the preconfiguration file will only be loaded after -these questions have been asked. - - - -The locale can be used to specify both language and country and can be any -combination of a language supported by &d-i; and a recognized country. If -the combination does not form a valid locale, the installer will automatically -select a locale that is valid for the selected language. -To specify the locale as a boot parameter, use -locale=en_US. - - - -Although this method is very easy to use, it does not allow preseeding of -all possible combinations of language, country and locale - - -Preseeding locale to en_NL would -for example result in en_US.UTF-8 as default locale for -the installed system. If e.g. en_GB.UTF-8 is preferred -instead, the values will need to be preseeded individually. - - -. So alternatively the values can be preseeded individually. -Language and country can also be specified as boot parameters. - - -# Preseeding only locale sets language, country and locale. -d-i debian-installer/locale string en_US - -# The values can also be preseeded individually for greater flexibility. -#d-i debian-installer/language string en -#d-i debian-installer/country string NL -#d-i debian-installer/locale string en_GB.UTF-8 -# Optionally specify additional locales to be generated. -#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8 - - - - -Keyboard configuration consists of selecting a keymap. - - -# Keyboard selection. -# keymap is an alias for keyboard-configuration/xkb-keymap -d-i keymap select us -# d-i keyboard-configuration/toggle select No toggling - - - - -To skip keyboard configuration, preseed -keymap with -skip-config. -This will result in the kernel keymap remaining active. - - - - - - - Network configuration - - -Of course, preseeding the network configuration won't work if you're -loading your preconfiguration file from the network. But it's great when -you're booting from CD or USB stick. If you are loading preconfiguration -files from the network, you can pass network config parameters by using -kernel boot parameters. - - - -If you need to pick a particular interface when netbooting before loading -a preconfiguration file from the network, use a boot parameter such as -interface=eth1. - - - -Although preseeding the network configuration is normally not possible when -using network preseeding (using preseed/url), you can use -the following hack to work around that, for example if you'd like to set a -static address for the network interface. The hack is to force the network -configuration to run again after the preconfiguration file has been loaded -by creating a preseed/run script containing the following -commands: - - -killall.sh; netcfg - - - - -The following debconf variables are relevant for network configuration. - - - - -# Disable network configuration entirely. This is useful for cdrom -# installations on non-networked devices where the network questions, -# warning and long timeouts are a nuisance. -#d-i netcfg/enable boolean false - -# netcfg will choose an interface that has link if possible. This makes it -# skip displaying a list if there is more than one interface. -d-i netcfg/choose_interface select auto - -# To pick a particular interface instead: -#d-i netcfg/choose_interface select eth1 - -# If you have a slow dhcp server and the installer times out waiting for -# it, this might be useful. -#d-i netcfg/dhcp_timeout string 60 - -# If you prefer to configure the network manually, uncomment this line and -# the static network configuration below. -#d-i netcfg/disable_dhcp boolean true - -# If you want the preconfiguration file to work on systems both with and -# without a dhcp server, uncomment these lines and the static network -# configuration below. -#d-i netcfg/dhcp_failed note -#d-i netcfg/dhcp_options select Configure network manually - -# Static network configuration. -#d-i netcfg/get_nameservers string 192.168.1.1 -#d-i netcfg/get_ipaddress string 192.168.1.42 -#d-i netcfg/get_netmask string 255.255.255.0 -#d-i netcfg/get_gateway string 192.168.1.1 -#d-i netcfg/confirm_static boolean true - -# Any hostname and domain names assigned from dhcp take precedence over -# values set here. However, setting the values still prevents the questions -# from being shown, even if values come from dhcp. -d-i netcfg/get_hostname string unassigned-hostname -d-i netcfg/get_domain string unassigned-domain - -# Disable that annoying WEP key dialog. -d-i netcfg/wireless_wep string -# The wacky dhcp hostname that some ISPs use as a password of sorts. -#d-i netcfg/dhcp_hostname string radish - -# If non-free firmware is needed for the network or other hardware, you can -# configure the installer to always try to load it, without prompting. Or -# change to false to disable asking. -#d-i hw-detect/load_firmware boolean true - - - - -Please note that netcfg will automatically determine the -netmask if netcfg/get_netmask is not preseeded. In -this case, the variable has to be marked as seen for -automatic installations. Similarly, netcfg will choose -an appropriate address if netcfg/get_gateway is not -set. As a special case, you can set -netcfg/get_gateway to none to specify -that no gateway should be used. - - - - - - - Network console - - -# Use the following settings if you wish to make use of the network-console -# component for remote installation over SSH. This only makes sense if you -# intend to perform the remainder of the installation manually. -#d-i anna/choose_modules string network-console -#d-i network-console/authorized_keys_url string http://10.0.0.1/openssh-key -#d-i network-console/password password r00tme -#d-i network-console/password-again password r00tme - - - - - - Mirror settings - - -Depending on the installation method you use, a mirror may be used to -download additional components of the installer, to install the base system, -and to set up the /etc/apt/sources.list for the installed -system. - - - -The parameter mirror/suite determines the suite for -the installed system. - - - -The parameter mirror/udeb/suite determines the suite -for additional components for the installer. It is only useful to set this -if components are actually downloaded over the network and should match the -suite that was used to build the initrd for the installation method used for -the installation. Normally the installer will automatically use the correct -value and there should be no need to set this. - - - - -# If you select ftp, the mirror/country string does not need to be set. -#d-i mirror/protocol string ftp -d-i mirror/country string manual -d-i mirror/http/hostname string &archive-mirror; -d-i mirror/http/directory string /debian -d-i mirror/http/proxy string - -# Suite to install. -#d-i mirror/suite string testing -# Suite to use for loading installer components (optional). -#d-i mirror/udeb/suite string testing - - - - - - Account setup - - -The password for the root account and name and password for a first regular -user's account can be preseeded. For the passwords you can use either clear -text values or MD5 hashes. - - - - -Be aware that preseeding passwords is not completely secure as everyone -with access to the preconfiguration file will have the knowledge of these -passwords. Using MD5 hashes is considered slightly better in terms of -security but it might also give a false sense of security as access to a -MD5 hash allows for brute force attacks. - - - - -# Skip creation of a root account (normal user account will be able to -# use sudo). -#d-i passwd/root-login boolean false -# Alternatively, to skip creation of a normal user account. -#d-i passwd/make-user boolean false - -# Root password, either in clear text -#d-i passwd/root-password password r00tme -#d-i passwd/root-password-again password r00tme -# or encrypted using an MD5 hash. -#d-i passwd/root-password-crypted password [MD5 hash] - -# To create a normal user account. -#d-i passwd/user-fullname string Debian User -#d-i passwd/username string debian -# Normal user's password, either in clear text -#d-i passwd/user-password password insecure -#d-i passwd/user-password-again password insecure -# or encrypted using an MD5 hash. -#d-i passwd/user-password-crypted password [MD5 hash] -# Create the first user with the specified UID instead of the default. -#d-i passwd/user-uid string 1010 - -# The user account will be added to some standard initial groups. To -# override that, use this. -#d-i passwd/user-default-groups string audio cdrom video - - - - -The passwd/root-password-crypted and -passwd/user-password-crypted variables can also -be preseeded with ! as their value. In that case, the -corresponding account is disabled. This may be convenient for the root -account, provided of course that an alternative method is set up to allow -administrative activities or root login (for instance by using SSH key -authentication or sudo). - - - -The following command can be used to generate an MD5 hash for a password: - - -$ printf "r00tme" | mkpasswd -s -m md5 - - - - - - - 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 valid values. -d-i time/zone string US/Eastern - -# Controls whether to use NTP to set the clock during the install -d-i clock-setup/ntp boolean true -# NTP server to use. The default is almost always fine here. -#d-i clock-setup/ntp-server string ntp.example.com - - - - - - Partitioning - - -Using preseeding to partition the harddisk is limited to what is supported -by partman-auto. You can choose to partition -either existing free space on a disk or a whole disk. The layout of the -disk can be determined by using a predefined recipe, a custom recipe from -a recipe file or a recipe included in the preconfiguration file. - - - -Preseeding of advanced partition setups using RAID, LVM and encryption is -supported, but not with the full flexibility possible when partitioning -during a non-preseeded install. - - - -The examples below only provide basic information on the use of recipes. -For detailed information see the files -partman-auto-recipe.txt and -partman-auto-raid-recipe.txt included in the -debian-installer package. -Both files are also available from the -&d-i; source -repository. Note that the supported functionality may change -between releases. - - - - - -The identification of disks is dependent on the order in which their drivers -are loaded. If there are multiple disks in the system, make very sure the -correct one will be selected before using preseeding. - - - - - Partitioning example - - -# If the system has free space you can choose to only partition that space. -# This is only honoured if partman-auto/method (below) is not set. -#d-i partman-auto/init_automatically_partition select biggest_free - -# Alternatively, you may specify a disk to partition. If the system has only -# one disk the installer will default to using that, but otherwise the device -# name must be given in traditional, non-devfs format (so e.g. /dev/hda or -# /dev/sda, and not e.g. /dev/discs/disc0/disc). -# For example, to use the first SCSI/SATA hard disk: -#d-i partman-auto/disk string /dev/sda -# In addition, you'll need to specify the method to use. -# The presently available methods are: -# - regular: use the usual partition types for your architecture -# - lvm: use LVM to partition the disk -# - crypto: use LVM within an encrypted partition -d-i partman-auto/method string lvm - -# If one of the disks that are going to be automatically partitioned -# contains an old LVM configuration, the user will normally receive a -# warning. This can be preseeded away... -d-i partman-lvm/device_remove_lvm boolean true -# The same applies to pre-existing software RAID array: -d-i partman-md/device_remove_md boolean true -# And the same goes for the confirmation to write the lvm partitions. -d-i partman-lvm/confirm boolean true -d-i partman-lvm/confirm_nooverwrite boolean true - -# You can choose one of the three predefined partitioning recipes: -# - atomic: all files in one partition -# - home: separate /home partition -# - multi: separate /home, /usr, /var, and /tmp partitions -d-i partman-auto/choose_recipe select atomic - -# Or provide a recipe of your own... -# If you have a way to get a recipe file into the d-i environment, you can -# just point at it. -#d-i partman-auto/expert_recipe_file string /hd-media/recipe - -# If not, you can put an entire recipe into the preconfiguration file in one -# (logical) line. This example creates a small /boot partition, suitable -# swap, and uses the rest of the space for the root partition: -#d-i partman-auto/expert_recipe string \ -# boot-root :: \ -# 40 50 100 ext3 \ -# $primary{ } $bootable{ } \ -# method{ format } format{ } \ -# use_filesystem{ } filesystem{ ext3 } \ -# mountpoint{ /boot } \ -# . \ -# 500 10000 1000000000 ext3 \ -# method{ format } format{ } \ -# use_filesystem{ } filesystem{ ext3 } \ -# mountpoint{ / } \ -# . \ -# 64 512 300% linux-swap \ -# method{ swap } format{ } \ -# . - -# The full recipe format is documented in the file partman-auto-recipe.txt -# included in the 'debian-installer' package or available from D-I source -# repository. This also documents how to specify settings such as file -# system labels, volume group names and which physical devices to include -# in a volume group. - -# This makes partman automatically partition without confirmation, provided -# that you told it what to do using one of the methods above. -d-i partman-partitioning/confirm_write_new_label boolean true -d-i partman/choose_partition select finish -d-i partman/confirm boolean true -d-i partman/confirm_nooverwrite boolean true - - - - - Partitioning using RAID - - -You can also use preseeding to set up partitions on software RAID arrays. -Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and -specifying spare devices. -If you are using RAID 1, you can preseed grub to install to all devices -used in the array; see . - - - - - -This type of automated partitioning is easy to get wrong. It is also -functionality that receives relatively little testing from the developers -of &d-i;. The responsibility to get the various recipes right (so they -make sense and don't conflict) lies with the user. -Check /var/log/syslog if you run into problems. - - - - -# The method should be set to "raid". -#d-i partman-auto/method string raid -# Specify the disks to be partitioned. They will all get the same layout, -# so this will only work if the disks are the same size. -#d-i partman-auto/disk string /dev/sda /dev/sdb - -# Next you need to specify the physical partitions that will be used. -#d-i partman-auto/expert_recipe string \ -# multiraid :: \ -# 1000 5000 4000 raid \ -# $primary{ } method{ raid } \ -# . \ -# 64 512 300% raid \ -# method{ raid } \ -# . \ -# 500 10000 1000000000 raid \ -# method{ raid } \ -# . - -# Last you need to specify how the previously defined partitions will be -# used in the RAID setup. Remember to use the correct partition numbers -# for logical partitions. RAID levels 0, 1, 5, 6 and 10 are supported; -# devices are separated using "#". -# Parameters are: -# <raidtype> <devcount> <sparecount> <fstype> <mountpoint> \ -# <devices> <sparedevices> - -#d-i partman-auto-raid/recipe string \ -# 1 2 0 ext3 / \ -# /dev/sda1#/dev/sdb1 \ -# . \ -# 1 2 0 swap - \ -# /dev/sda5#/dev/sdb5 \ -# . \ -# 0 2 0 ext3 /home \ -# /dev/sda6#/dev/sdb6 \ -# . - -# For additional information see the file partman-auto-raid-recipe.txt -# included in the 'debian-installer' package or available from D-I source -# repository. - -# This makes partman automatically partition without confirmation. -d-i partman-md/confirm boolean true -d-i partman-partitioning/confirm_write_new_label boolean true -d-i partman/choose_partition select finish -d-i partman/confirm boolean true -d-i partman/confirm_nooverwrite boolean true - - - - - - Controlling how partitions are mounted - - -Normally, filesystems are mounted using a universally unique identifier -(UUID) as a key; this allows them to be mounted properly even if their -device name changes. UUIDs are long and difficult to read, so, if you -prefer, the installer can mount filesystems based on the traditional device -names, or based on a label you assign. If you ask the installer to mount by -label, any filesystems without a label will be mounted using a UUID instead. - - - -Devices with stable names, such as LVM logical volumes, will continue to use -their traditional names rather than UUIDs. - - - - - -Traditional device names may change based on the order in which the kernel -discovers devices at boot, which may cause the wrong filesystem to be -mounted. Similarly, labels are likely to clash if you plug in a new disk or -a USB drive, and if that happens your system's behaviour when started will -be random. - - - - -# The default is to mount by UUID, but you can also choose "traditional" to -# use traditional device names, or "label" to try filesystem labels before -# falling back to UUIDs. -#d-i partman/mount_style select uuid - - - - - - - Base system installation - - -There is actually not very much that can be preseeded for this stage of the -installation. The only questions asked concern the installation of the kernel. - - - - -# Configure APT to not install recommended packages by default. Use of this -# option can result in an incomplete system and should only be used by very -# experienced users. -#d-i base-installer/install-recommends boolean false - -# Select the initramfs generator used to generate the initrd for 2.6 kernels. -#d-i base-installer/kernel/linux/initramfs-generators string initramfs-tools - -# The kernel image (meta) package to be installed; "none" can be used if no -# kernel is to be installed. -#d-i base-installer/kernel/image string &kernelpackage;-2.6-486 - - - - - - Apt setup - - -Setup of the /etc/apt/sources.list and basic configuration -options is fully automated based on your installation method and answers to -earlier questions. You can optionally add other (local) repositories. - - - - -# You can choose to install non-free and contrib software. -#d-i apt-setup/non-free boolean true -#d-i apt-setup/contrib boolean true -# Uncomment this if you don't want to use a network mirror. -#d-i apt-setup/use_mirror boolean false -# Select which update services to use; define the mirrors to be used. -# Values shown below are the normal defaults. -#d-i apt-setup/services-select multiselect security, volatile -#d-i apt-setup/security_host string security.debian.org -#d-i apt-setup/volatile_host string volatile.debian.org - -# Additional repositories, local[0-9] available -#d-i apt-setup/local0/repository string \ -# http://local.server/debian stable main -#d-i apt-setup/local0/comment string local server -# Enable deb-src lines -#d-i apt-setup/local0/source boolean true -# URL to the public key of the local repository; you must provide a key or -# apt will complain about the unauthenticated repository and so the -# sources.list line will be left commented out -#d-i apt-setup/local0/key string http://local.server/key - -# By default the installer requires that repositories be authenticated -# using a known gpg key. This setting can be used to disable that -# authentication. Warning: Insecure, not recommended. -#d-i debian-installer/allow_unauthenticated boolean true - - - - - - Package selection - - -You can choose to install any combination of tasks that are available. -Available tasks as of this writing include: - - - - - - standard - - - desktop - - - gnome-desktop - - - kde-desktop - - - web-server - - - print-server - - - dns-server - - - file-server - - - mail-server - - - sql-database - - - laptop - - - - - -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 task. - - - -If you want to install some individual packages in addition to packages -installed by tasks, you can use the parameter -pkgsel/include. The value of this parameter can be -a list of packages separated by either commas or spaces, which allows it -to be used easily on the kernel command line as well. - - - - -#tasksel tasksel/first multiselect standard, web-server -# If the desktop task is selected, install the kde and xfce desktops -# instead of the default gnome desktop. -#tasksel tasksel/desktop multiselect kde, xfce - -# Individual additional packages to install -#d-i pkgsel/include string openssh-server build-essential -# Whether to upgrade packages after debootstrap. -# Allowed values: none, safe-upgrade, full-upgrade -#d-i pkgsel/upgrade select none - -# Some versions of the installer can report back on what software you have -# installed, and what software you use. The default is not to report back, -# but sending reports helps the project determine what software is most -# popular and include it on CDs. -#popularity-contest popularity-contest/participate boolean false - - - - - - 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 -# To also skip installing lilo, and install no bootloader, uncomment this -# too: -#d-i lilo-installer/skip boolean true - -# With a few exceptions for unusual partitioning setups, GRUB 2 is now the -# default. If you need GRUB Legacy for some particular reason, then -# uncomment this: -#d-i grub-installer/grub2_instead_of_grub_legacy boolean false - -# This is fairly safe to set, it makes grub install automatically to the MBR -# if no other operating system is detected on the machine. -d-i grub-installer/only_debian boolean true - -# This one makes grub-installer install to the MBR if it also finds some other -# OS, which is less safe as it might not be able to boot that other OS. -d-i grub-installer/with_other_os boolean true - -# Alternatively, if you want to install to a location other than the mbr, -# uncomment and edit these lines: -#d-i grub-installer/only_debian boolean false -#d-i grub-installer/with_other_os boolean false -#d-i grub-installer/bootdev string (hd0,0) -# To install grub to multiple disks: -#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0) - -# Optional password for grub, either in clear text -#d-i grub-installer/password password r00tme -#d-i grub-installer/password-again password r00tme -# or encrypted using an MD5 hash, see grub-md5-crypt(8). -#d-i grub-installer/password-crypted password [MD5 hash] - -# Use the following option to add additional boot parameters for the -# installed system (if supported by the bootloader installer). -# Note: options passed to the installer will be added automatically. -#d-i debian-installer/add-kernel-opts string nousb - - - - -An MD5 hash for a password for grub can be generated -using grub-md5-crypt, or using the command from the -example in . - - - - - - Finishing up the installation - - -# During installations from serial console, the regular virtual consoles -# (VT1-VT6) are normally disabled in /etc/inittab. Uncomment the next -# line to prevent this. -#d-i finish-install/keep-consoles boolean true - -# Avoid that last message about the install being complete. -d-i finish-install/reboot_in_progress note - -# This will prevent the installer from ejecting the CD during the reboot, -# which is useful in some situations. -#d-i cdrom-detect/eject boolean false - -# This is how to make the installer shutdown when finished, but not -# reboot into the installed system. -#d-i debian-installer/exit/halt boolean true -# This will power off the machine instead of just halting it. -#d-i debian-installer/exit/poweroff boolean true - - - - - - Preseeding other packages - - -# 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 - - - - - - - - Advanced options - - - Running custom commands during the installation - - -A very powerful and flexible option offered by the preconfiguration tools -is the ability to run commands or scripts at certain points in the -installation. - - - - -# d-i preseeding is inherently not secure. Nothing in the installer checks -# for attempts at buffer overflows or other exploits of the values of a -# preconfiguration file like this one. Only use preconfiguration files from -# trusted locations! To drive that home, and because it's generally useful, -# here's a way to run any shell command you'd like inside the installer, -# automatically. - -# This first command is run as early as possible, just after -# preseeding is read. -#d-i preseed/early_command string anna-install some-udeb -# This command is run immediately before the partitioner starts. It may be -# useful to apply dynamic partitioner preseeding that depends on the state -# of the disks (which may not be visible when preseed/early_command runs). -#d-i partman/early_command \ -# string debconf-set partman-auto/disk "$(list-devices disk | head -n1)" -# This command is run just before the install finishes, but when there is -# still a usable /target directory. You can chroot to /target and use it -# directly, or use the apt-install and in-target commands to easily install -# packages and run commands in the target system. -#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh - - - - - - Using preseeding to change default values - - -It is possible to use preseeding to change the default answer for a -question, but still have the question asked. To do this the -seen flag must be reset to false after -setting the value for a question. - - -d-i foo/bar string value -d-i foo/bar seen false - - -The same effect can be achieved for all questions by -setting the parameter preseed/interactive=true at -the boot prompt. This can also be useful for testing or debugging your -preconfiguration file. - - - -Note that the d-i owner should only be used for variables -used in the installer itself. For variables belonging to packages installed -on the target system, you should use the name of that package instead. See -the footnote to . - - - -If you are preseeding using boot parameters, you can make the installer ask -the corresponding question by using the ?= operator, i.e. -foo/bar?=value -(or owner:foo/bar?=value). -This will of course only have effect for parameters that correspond to -questions that are actually displayed during an installation and not for -internal parameters. - - - - - - Chainloading preconfiguration files - - -It is possible to include other preconfiguration files from a preconfiguration -file. Any settings in those files will override pre-existing settings from -files loaded earlier. This makes it possible to put, for example, general -networking settings for your location in one file and more specific -settings for certain configurations in other files. - - - - -# More than one file can be listed, separated by spaces; all will be -# loaded. The included files can have preseed/include directives of their -# own as well. Note that if the filenames are relative, they are taken from -# the same directory as the preconfiguration file that includes them. -#d-i preseed/include string x.cfg - -# The installer can optionally verify checksums of preconfiguration files -# before using them. Currently only md5sums are supported, list the md5sums -# in the same order as the list of files to include. -#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d - -# More flexibly, this runs a shell command and if it outputs the names of -# preconfiguration files, includes those files. -#d-i preseed/include_command \ -# string if [ "`hostname`" = bob ]; then echo bob.cfg; fi - -# Most flexibly of all, this downloads a program and runs it. The program -# can use commands such as debconf-set to manipulate the debconf database. -# More than one script can be listed, separated by spaces. -# Note that if the filenames are relative, they are taken from the same -# directory as the preconfiguration file that runs them. -#d-i preseed/run string foo.sh - - - - -It is also possible to chainload from the initrd or file preseeding phase, -into network preseeding by setting preseed/url in the earlier files. -This will cause network preseeding to be performed when the network comes -up. You need to be careful when doing this, since there will be two -distinct runs at preseeding, meaning for example that you get another -chance to run the preseed/early command, the second one happening after the -network comes up. - - - - - - diff --git a/nl/appendix/random-bits.xml b/nl/appendix/random-bits.xml deleted file mode 100644 index d78717e51..000000000 --- a/nl/appendix/random-bits.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - -Random Bits - -&files.xml; -&chroot-install.xml; -&plip.xml; -&pppoe.xml; -&graphical.xml; - - diff --git a/nl/bookinfo.xml b/nl/bookinfo.xml deleted file mode 100644 index bda199627..000000000 --- a/nl/bookinfo.xml +++ /dev/null @@ -1,62 +0,0 @@ - - - -&debian-gnu; Installatiehandleiding - - - -Dit document bevat instructies voor de installatie van het &debian-gnu; -&release; systeem (codenaam &releasename;), -voor het &arch-title; (&architecture;) -platform. Verder bevat het verwijzingen naar aanvullende informatie en -informatie over hoe u het meeste uit uw nieuwe &debian; systeem kunt halen. - - - - -Deze installatiehandleiding is gebaseerd op een eerdere handleiding die -is geschreven voor het oude installatiesysteem van Debian (de -boot-floppies) 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 &d-i; website. -Mogelijk kunt u daar ook aanvullende vertalingen vinden. - - - -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 &d-i; website. -Mogelijk kunt u daar ook aanvullende vertalingen vinden. - - - - -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 debian-l10n-dutch@lists.debian.org -mailinglijst. Zie ook . - - - - - 2004 – 2012 - het Debian Installatiesysteem team - - - - - -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 te raadplegen. - - - - diff --git a/nl/boot-installer/accessibility.xml b/nl/boot-installer/accessibility.xml deleted file mode 100644 index 6ce4ca335..000000000 --- a/nl/boot-installer/accessibility.xml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - Accessibility - - -Some users may need specific support because of e.g. some visual -impairment. -USB braille displays are detected -automatically, but most other -Most -accessibility features have to be enabled manually. -On machines that support it, the boot menu emits a beep -when it is ready to receive keystrokes. -Some boot parameters can then be appended to -enable accessibility features. Note that on most architectures the boot -loader interprets your keyboard as a QWERTY keyboard. - - - - - USB Braille Displays - - -USB braille displays should be automatically detected. A textual version -of the installer will then be automatically selected, and support for the -braille display will be automatically installed on the target system. -You can thus just press &enterkey; at the boot menu. -Once brltty is started, you can choose a braille -table by entering the preference menu. Documentation on key -bindings for braille devices is available on the brltty website. - - - - - - Serial Braille Displays - - -Serial braille displays cannot safely be automatically detected -(since that may damage some of them). You thus need to append the -brltty=driver,port,table -boot parameter to tell brltty which driver it -should use. driver should be replaced by the -two-letter driver code for your terminal (see the -driver code list). -port should be replaced by the name of the -serial port the display is connected to, ttyS0 is -the default. table is the name of the braille -table to be used (see the table code -list); the English table is the default. Note that the table can -be changed later by entering the preference menu. Documentation on key -bindings for braille devices is available on the brltty website. - - - - - - Hardware Speech Synthesis - - -Support for hardware speech synthesis devices is available only alongside -support for graphical installer. You thus need to select the -Graphical install entry in the boot menu. - - - -Hardware speech synthesis devices cannot be automatically detected. You -thus need to append the -speakup.synth=driver -boot parameter to tell speakup which driver it should -use. driver should be replaced by the driver code -for your device (see driver code -list). The textual version of the installer will then be -automatically selected, and support for the speech synthesis device will be -automatically installed on the target system. - - - - - Board Devices - - -Some accessibility devices are actual boards that are plugged inside the -machine and that read text directly from the video memory. To get them -to work framebuffer support must be disabled by using the -vga=normal fb=false -boot parameter. This will however reduce the number of available languages. - - - -If desired a textual version of the bootloader can be activated before adding -the boot parameter by typing h &enterkey;. - - - - - High-Contrast Theme - - -For users with low vision, the installer can use a high-contrast -theme that makes it more readable. To enable it, append the -theme=dark boot parameter. - - - - diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml deleted file mode 100644 index d295d0894..000000000 --- a/nl/boot-installer/arm.xml +++ /dev/null @@ -1,236 +0,0 @@ - - - - Booting from TFTP - -&boot-installer-intro-net.xml; - - - - - Booting from CD-ROM - -&boot-installer-intro-cd.xml; - - - - - Booting from Firmware - -&boot-installer-intro-firmware.xml; - - Booting the NSLU2 - - -There are three ways how to put the installer firmware into flash: - - - - Using the NSLU2 web interface - - -Go to the administration section and choose the menu item -Upgrade. You can then browse your disk for the -installer image you have previously downloaded. Then press the -Start Upgrade button, confirm, wait for a few minutes -and confirm again. The system will then boot straight into the installer. - - - - - Via the network using Linux/Unix - - -You can use upslug2 from any Linux or Unix machine to -upgrade the machine via the network. This software is packaged for -&debian;. - -First, you have to put your NSLU2 in upgrade mode: - - - - -Disconnect any disks and/or devices from the USB ports. - - - - -Power off the NSLU2 - - - - -Press and hold the reset button (accessible through the small hole on the -back just above the power input). - - - - -Press and release the power button to power on the NSLU2. - - - - -Wait for 10 seconds watching the ready/status LED. After 10 seconds it -will change from amber to red. Immediately release the reset button. - - - - -The NSLU2 ready/status LED will flash alternately red/green (there is a 1 -second delay before the first green). The NSLU2 is now in upgrade mode. - - - - -See the NSLU2-Linux -pages if you have problems with this. - -Once your NSLU2 is in upgrade mode, you can flash the new image: - - -sudo upslug2 -i di-nslu2.bin - - -Note that the tool also shows the MAC address of your NSLU2, which may come -in handy to configure your DHCP server. After the whole image has been -written and verified, the system will automatically reboot. Make sure you -connect your USB disk again now, otherwise the installer won't be able to -find it. - - - - - Via the network using Windows - - -There is a -tool for Windows to upgrade the firmware via the network. - - - - - - - Booting the SS4000-E - - -Due to limitations in the SS4000-E firmware, it unfortunately is not -possible to boot the installer without the use of a serial port at -this time. To boot the installer, you will need a serial nullmodem -cable; a computer with a serial port - - -A USB serial converter will also work. - - -; and a ribbon cable with a male DB9 connector at one end, -and a 10-pin .1" IDC header at the other - - -This cable is often found in older desktop machines with builtin 9-pin -serial ports. - - -. - - - -To boot the SS4000-E, use your serial nullmodem cable and the ribbon -cable to connect to the serial port of the SS4000-E, and reboot the -machine. You need to use a serial terminal application to communicate -with the machine; a good option on a &debian; GNU/Linux is to use the -cu program, in the package of the same name. Assuming -the serial port on your computer is to be found on -/dev/ttyS0, use the following command line: - - - - -cu -lttyS0 -s115200 - - - - -If using Windows, you may want to consider using the program -hyperterminal. Use a baud rate of 115200, -8 bits word length, no stop bits, and one parity bit. - - - -When the machine boots, you will see the following line of output: - - - - -No network interfaces found - -EM-7210 ver.T04 2005-12-12 (For ver.AA) -== Executing boot script in 1.000 seconds - enter ^C to abort - - - - -At this point, hit Control-C to interrupt the boot -loader - - -Note that you have only one second to do so; if you miss this window, -just powercycle the machine and try again. - - -. This will give you the RedBoot prompt. Enter the -following commands: - - -load -v -r -b 0x01800000 -m ymodem ramdisk.gz -load -v -r -b 0x01008000 -m ymodem zImage -exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000 - - - - -After every load command, the system will expect a -file to be transmitted using the YMODEM protocol. When using cu, make -sure you have the package lrzsz installed, then -hit enter, followed by the ~< escape sequence to start -an external program, and run sb initrd.gz or -sb vmlinuz. - - - -Alternatively, it is possible to load the kernel and ramdisk using -HTTP rather than YMODEM. This is faster, but requires a working HTTP -server on the network. To do so, first switch the bootloader to RAM mode: - - -fis load rammode -g - - - - -This will seemingly restart the machine; but in reality, it loads -reboot to RAM and restarts it from there. Not doing this step will cause -the system to hang in the necessary ip_address step that comes next. - - - -You will need to hit Ctrl-C again to interrupt the boot. Then: - - -ip_address -l 192.168.2.249 -h 192.168.2.4 -load -v -r -b 0x01800000 -m http /initrd.gz -load -v -r -b 0x01008000 -m http /zImage -exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000 - - - - -The installer will now start as usual. - - - - diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml deleted file mode 100644 index 7aaad3b0e..000000000 --- a/nl/boot-installer/boot-installer.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - -Booting the Installation System - - - - - Booting the Installer on &arch-title; - - - - - - - -If you have any other operating systems on your system that you wish to -keep (dual boot setup), you should make sure that they have been properly -shut down before you boot the installer. -Installing an operating system while another operating system is in -hibernation (has been suspended to disk) could result in loss of, or damage -to the state of the suspended operating system which could cause problems -when it is rebooted. - - - - -For information on how to boot the graphical installer, see -. - - - -&boot-installer-arm.xml; - -&boot-installer-x86.xml; -&boot-installer-ia64.xml; -&boot-installer-mips.xml; -&boot-installer-mipsel.xml; -&boot-installer-s390.xml; -&boot-installer-powerpc.xml; -&boot-installer-sparc.xml; - - - -&boot-installer-accessibility.xml; -&boot-installer-parameters.xml; -&boot-installer-trouble.xml; - - diff --git a/nl/boot-installer/hppa.xml b/nl/boot-installer/hppa.xml deleted file mode 100644 index 619d3eaf1..000000000 --- a/nl/boot-installer/hppa.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - - - - - - - - - diff --git a/nl/boot-installer/ia64.xml b/nl/boot-installer/ia64.xml deleted file mode 100644 index 17104727e..000000000 --- a/nl/boot-installer/ia64.xml +++ /dev/null @@ -1,464 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - CD Contents - - - -There are three basic variations of &debian; Install CDs. -The Business Card 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 Network Install 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. - - - - - -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. - - - -The &debian; Installer CD contains a small EFI partition where the -ELILO 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. - - - -Most of the details of how ELILO 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 ELILO -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. - - - -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, -Boot Option Maintenance Menu and -EFI Shell (Built-in). -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. - - - - - IMPORTANT - -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 exit at the shell prompt. - - - - - Option 1: Booting from the Boot Option Maintenance Menu - - - - - - - -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. - - - -Select Boot Maintenance Menu from the menu -with the arrow keys and press ENTER. -This will display a new menu. - - - -Select Boot From a File from the menu -with the arrow keys and press ENTER. -This will display a list of devices probed by the firmware. -You should see two menu lines containing either the label -Debian Inst [Acpi ... or -Removable Media Boot. -If you examine the rest of the menu line, you will notice that -the device and controller information should be the same. - - - -You can choose either of the entries that refer to the CD/DVD -drive. -Select your choice with the arrow keys and press ENTER. -If you choose Removable Media Boot the machine -will immediately start the boot load sequence. -If you choose Debian Inst [Acpi ... instead, it -will display a directory listing of the bootable portion of the -CD, requiring you to proceed to the next (additional) step. - - - -You will only need this step if you chose -Debian Inst [Acpi .... -The directory listing will also show -[Treat like Removable Media Boot] on the next to -the last line. -Select this line with the arrow keys and press ENTER. -This will start the boot load sequence. - - - - - - -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. - - - - - - Option 2: Booting from the EFI Shell - - -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 EFI Shell [Built-in]. -Boot the &debian; Installer CD with the following steps: - - - - - - -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. - - - -Select EFI Shell from the menu with the arrow keys -and press ENTER. -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 -fsn:. -All other recognized partitions will be named -blkn:. -If you inserted the CD just before entering the shell, this may -take a few extra seconds as it initializes the CD drive. - - - - -Examine the output from the shell looking for the CDROM drive. -It is most likely the fs0: device although -other devices with bootable partitions will also show up as -fsn. - - - -Enter fsn: and press -ENTER to select that -device where n is the partition number for the -CDROM. The shell will now display the partition number as its prompt. - - - -Enter elilo and press ENTER. -This will start the boot load sequence. - - - - - - -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 -fsn:elilo command at -the shell prompt. -Proceed to selecting the boot kernel and options. - - - - - - - Installing using a Serial Console - - - -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 -[BAUD baud serial console], where -BAUD is the speed of your serial console. -Menu items for the most typical baud rate settings on the ttyS0 -device are preconfigured. - - - -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 -baud at the EFI shell. - - - -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 -console=ttyS1,57600n8 into -the Boot: text window. - - - - -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 Params -help menu for instructions on starting the installer in Text Mode. - - - -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. - - - - - Selecting the Boot Kernel and Options - - - -The boot loader will display a form with a menu list and a text -window with a Boot: 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 General help screen explains the menu -choices and the Params screen explains -the common command line options. - - - -Consult the General help screen for the -description of the kernels and install modes most appropriate -for your installation. -You should also consult below for any additional -parameters that you may want to set in the Boot: -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: - - - - - - -Select the kernel version and installation mode most -appropriate to your needs with the arrow keys. - - - -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. - - - -Press ENTER. This will load and start the -kernel. -The kernel will display its usual initialization messages followed -by the first screen of the &debian; Installer. - - - - - - -Proceed to the next chapter to continue the installation where you will -set up the language locale, network, and disk partitions. - - - - - - Booting with TFTP - - -Booting an IA-64 system from the network is similar to a CD boot. -The only difference is how the installation kernel is loaded. -The EFI Boot Manager can load and start programs from a server on -the network. -Once the installation kernel is loaded and starts, the system install -will proceed through the same steps as the CD install with the exception -that the packages of the base install will be loaded from the network -rather than the CD drive. - - - -&boot-installer-intro-net.xml; - - - -Network booting an IA-64 system requires two architecture-specific actions. -On the boot server, DHCP and TFTP must be configured to deliver -elilo. -On the client a new boot option must be defined in the EFI boot manager -to enable loading over a network. - - - - - Configuring the Server - - -A suitable TFTP entry for network booting an IA-64 system looks something -like this: - - -host mcmuffin { - hardware ethernet 00:30:6e:1e:0e:83; - fixed-address 10.0.0.21; - filename "debian-installer/ia64/elilo.efi"; -} - - -Note that the goal is to get elilo.efi running on -the client. - - - -Extract the netboot.tar.gz file into the directory used -as the root for your tftp server. Typical tftp root directories include -/var/lib/tftp and /tftpboot. -This will create a debian-installer directory -tree containing the boot files for an IA-64 system. - - - - -# cd /var/lib/tftp -# tar xvfz /home/user/netboot.tar.gz -./ -./debian-installer/ -./debian-installer/ia64/ -[...] - - -The netboot.tar.gz contains an -elilo.conf file that should work for most configurations. -However, should you need to make changes to this file, you can find it in the -debian-installer/ia64/ 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 -.conf instead of elilo.conf. -See documentation provided in the elilo package -for details. - - - - - - Configuring the Client - - -To configure the client to support TFTP booting, start by booting to -EFI and entering the Boot Option Maintenance Menu. - - - - -Add a boot option. - - - - -You should see one or more lines with the text -Load File [Acpi()/.../Mac()]. 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. - - - - -Name the entry Netboot or something similar, -save, and exit back to the boot options menu. - - - - -You should see the new boot option you just created, and selecting it -should initiate a DHCP query, leading to a TFTP load of -elilo.efi from the server. - - - -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. - - - -Proceed to the next chapter to continue the installation where -you will set up the language locale, network, and disk partitions. - - - - diff --git a/nl/boot-installer/intro-cd.xml b/nl/boot-installer/intro-cd.xml deleted file mode 100644 index 4c00e2593..000000000 --- a/nl/boot-installer/intro-cd.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - - -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 - -configure your system for booting off a CD as described in -, - -insert your CD, reboot, and proceed to the next chapter. - - - -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. - - - -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. - - - -If you have problems booting, see . - - diff --git a/nl/boot-installer/intro-firmware.xml b/nl/boot-installer/intro-firmware.xml deleted file mode 100644 index fe869608e..000000000 --- a/nl/boot-installer/intro-firmware.xml +++ /dev/null @@ -1,18 +0,0 @@ - - - - - -There is an increasing number of consumer devices that directly boot from a -flash chip on the device. The installer can be written to flash so it will -automatically start when you reboot your machines. - - - -In many cases, changing the firmware of an embedded device voids your -warranty. Sometimes you are also not able to recover your device if there -are problems during the flashing process. Therefore, please take care and -follow the steps precisely. - - - diff --git a/nl/boot-installer/intro-hd.xml b/nl/boot-installer/intro-hd.xml deleted file mode 100644 index 4df9f39b8..000000000 --- a/nl/boot-installer/intro-hd.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - -Booting from an existing operating system is often a convenient -option; for some systems it is the only supported method of -installation. - - - -To boot the installer from hard disk, you will have already completed -downloading and placing the needed files as described in -. - - diff --git a/nl/boot-installer/intro-net.xml b/nl/boot-installer/intro-net.xml deleted file mode 100644 index 79189195c..000000000 --- a/nl/boot-installer/intro-net.xml +++ /dev/null @@ -1,19 +0,0 @@ - - - - - -Booting from the network requires that you have a network -connection and a TFTP network boot server (DHCP, RARP, or BOOTP). - - - -Older systems such as the 715 might require the use of an RBOOT server -instead of a BOOTP server. - - - -The installation method to support network booting is described in . - - \ No newline at end of file diff --git a/nl/boot-installer/mips.xml b/nl/boot-installer/mips.xml deleted file mode 100644 index d1ef4d252..000000000 --- a/nl/boot-installer/mips.xml +++ /dev/null @@ -1,61 +0,0 @@ - - - - - Booting with TFTP - - - SGI TFTP Booting - - -After entering the command monitor use - - -bootp(): - - -on SGI machines to boot linux and to begin installation of the &debian; -Software. In order to make this -work you may have to unset the netaddr environment -variable. Type - - -unsetenv netaddr - - -in the command monitor to do this. - - - - - - - Boot Parameters - - - SGI TFTP Booting - - -On SGI machines you can append boot parameters to the -bootp(): command in the command monitor. - - - -Following the bootp(): 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: - - -bootp():/boot/tftpboot.img - - -Further kernel parameters can be passed via append: - - -bootp(): append="root=/dev/sda1" - - - - - - diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml deleted file mode 100644 index 7680c9cdb..000000000 --- a/nl/boot-installer/mipsel.xml +++ /dev/null @@ -1,54 +0,0 @@ - - - - Booting with TFTP - - - Cobalt TFTP Booting - - -Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to -install an NFS server and put the installer files in -/nfsroot. When you boot your Cobalt, you have to -press the left and the right cursor buttons at the same time and the -machine will boot via the network from NFS. It will then display several -options on the display. There are the following two installation methods: - - - - -Via SSH (default): In this case, the installer will configure the network -via DHCP and start an SSH server. It will then display a random password -and other login information (such as the IP address) on the Cobalt LCD. -When you connect to the machine with an SSH client you can start with -the installation. - - - - -Via serial console: Using a null modem cable, you can connect to the serial -port of your Cobalt machine (using 115200 bps) and perform the installation -this way. - - - - - - - - - - Boot Parameters - - - Cobalt TFTP Booting - - -You cannot pass any boot parameters directly. Instead, you have to edit -the /nfsroot/default.colo file on the NFS server and -add your parameters to the args variable. - - - - - diff --git a/nl/boot-installer/parameters.xml b/nl/boot-installer/parameters.xml deleted file mode 100644 index 545d1a5f4..000000000 --- a/nl/boot-installer/parameters.xml +++ /dev/null @@ -1,678 +0,0 @@ - - - - Boot Parameters - - -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. - - - -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. - - - -Information on many boot parameters can be found in the - Linux -BootPrompt HOWTO, including tips for obscure hardware. This -section contains only a sketch of the most salient parameters. Some -common gotchas are included below in -. - - - -When the kernel boots, a message - - -Memory:availk/totalk available - - -should be emitted early in the process. -total 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 -mem=ram parameter, -where ram is set to the amount of memory, -suffixed with k for kilobytes, or m for -megabytes. For example, both mem=65536k and -mem=64m mean 64MB of RAM. - - - -If you are booting with a serial console, generally the kernel will -autodetect this. -If you have a videocard (framebuffer) and a keyboard also attached to -the computer which you wish to boot via serial console, you may have -to pass the -console=device -argument to the kernel, where device is -your serial device, which is usually something like -ttyS0 - - -In order to ensure the terminal type used by the installer matches your -terminal emulator, the parameter -TERM=type can be added. -Note that the installer only supports the following terminal types: -linux, bterm, ansi, -vt102 and dumb. The default for -serial console in &d-i; is vt102. - - -. - - - -For &arch-title; the serial devices are ttya or -ttyb. -Alternatively, set the input-device and -output-device OpenPROM variables to -ttya. - - - - - &debian; Installer Parameters - - -The installation system recognizes a few additional boot parameters - - - -With current kernels (2.6.9 or newer) you can use 32 command line options and -32 environment options. If these numbers are exceeded, the kernel will panic. - - - - which may be useful. - - - -A number of parameters have a short form that helps avoid -the limitations of the kernel command line options and makes entering the -parameters easier. If a parameter has a short form, it will be listed in -brackets behind the (normal) long form. Examples in this manual will -normally use the short form too. - - - - - -debconf/priority (priority) - - -This parameter sets the lowest priority of messages to be displayed. - - - -The default installation uses priority=high. -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. - - - -If you add priority=medium as boot parameter, you -will be shown the installation menu and gain more control over the installation. -When priority=low is used, all messages are shown -(this is equivalent to the expert boot method). -With priority=critical, the installation system -will display only critical messages and try to do the right thing without fuss. - - - - - - -DEBIAN_FRONTEND - - -This boot parameter controls the type of user interface used for the -installer. The current possible parameter settings are: - - - -DEBIAN_FRONTEND=noninteractive - -DEBIAN_FRONTEND=text - -DEBIAN_FRONTEND=newt - -DEBIAN_FRONTEND=gtk - - - -The default frontend is DEBIAN_FRONTEND=newt. -DEBIAN_FRONTEND=text may be preferable for -serial console installs. Generally, only the -newt frontend is available on default install -media. On architectures that support it, the graphical installer uses -the gtk frontend. - - - - - - -BOOT_DEBUG - - -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.) - - - -BOOT_DEBUG=0 -This is the default. - - - -BOOT_DEBUG=1 -More verbose than usual. - - - -BOOT_DEBUG=2 -Lots of debugging information. - - - -BOOT_DEBUG=3 - - -Shells are run at various points in the boot process to allow detailed -debugging. Exit the shell to continue the boot. - - - - - - - - - - -INSTALL_MEDIA_DEV - - -The value of the parameter is the path to the device to load the -&debian; installer from. For example, -INSTALL_MEDIA_DEV=/dev/floppy/0 - - - -The boot floppy, which normally scans all floppies it can to find the -root floppy, can be overridden by this parameter to only look at the -one device. - - - - - -lowmem - - -Can be used to force the installer to a lowmem level higher than the one -the installer sets by default based on available memory. Possible values -are 1 and 2. See also . - - - - - -noshell - - -Prevents the installer from offering interactive shells on tty2 and tty3. -Useful for unattended installations where physical security is limited. - - - - - -debian-installer/framebuffer (fb) - - -Some architectures use the kernel framebuffer to offer installation in -a number of languages. If framebuffer causes a problem on your system -you can disable the feature using the parameter -vga=normal fb=false. -Problem symptoms are error messages about bterm or bogl, a blank screen, -or a freeze within a few minutes after starting the install. - - - -Such problems have been reported on hppa. - - - -Because of display problems on some systems, framebuffer support is -disabled by default 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 debian-installer/framebuffer=true or -fb=true for short. - - - - - -debian-installer/theme (theme) - - -A theme determines how the user interface of the installer looks (colors, -icons, etc.). What themes are available differs per frontend. Currently -both the newt and gtk frontends only have a dark theme that was -designed for visually impaired users. Set the theme by booting with -theme=dark. - - - - - -netcfg/disable_dhcp - - -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. - - - -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 -netcfg/disable_dhcp=true to prevent configuring -the network with DHCP and to enter the information manually. - - - - - -hw-detect/start_pcmcia - - -Set to false to prevent starting PCMCIA -services, if that causes problems. Some laptops are well known for -this misbehavior. - - - - - -disk-detect/dmraid/enable (dmraid) - - -Set to true to enable support for Serial ATA RAID -(also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. -Note that this support is currently experimental. Additional information -can be found on the Debian Installer Wiki. - - - - - -preseed/url (url) - - -Specify the url to a preconfiguration file to download and use for -automating the install. See . - - - - - -preseed/file (file) - - -Specify the path to a preconfiguration file to load for -automating the install. See . - - - - - -preseed/interactive - - -Set to true to display questions even if they have -been preseeded. Can be useful for testing or debugging a preconfiguration -file. Note that this will have no effect on parameters that are passed as -boot parameters, but for those a special syntax can be used. -See for details. - - - - - -auto-install/enable (auto) - - -Delay questions that are normally asked before preseeding is possible until -after the network is configured. -See for details about using this to -automate installs. - - - - - -finish-install/keep-consoles - - -During installations from serial or management console, the regular -virtual consoles (VT1 to VT6) are normally disabled in -/etc/inittab. -Set to true to prevent this. - - - - - -cdrom-detect/eject - - -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. - - - -Set to false 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. - - - - - -base-installer/install-recommends (recommends) - - -By setting this option to false, the package -management system will be configured to not automatically install -Recommends, both during the installation and for the -installed system. See also . - - - -Note that this option allows to have a leaner system, but can also result -in features being missing that you might normally expect to be available. -You may have to manually install some of the recommended packages to -obtain the full functionality you want. This option should therefore only -be used by very experienced users. - - - - - -debian-installer/allow_unauthenticated - - -By default the installer requires that repositories be authenticated -using a known gpg key. Set to true to -disable that authentication. -Warning: insecure, not recommended. - - - - - -ramdisk_size - - -This parameter should already be set to a correct value where needed; -set it only it you see errors during the boot that indicate the ramdisk -could not be loaded completely. The value is in kB. - - - - - -mouse/protocol - - -For the gtk frontend (graphical installer), users can set the mouse -protocol to be used by setting this parameter. -Supported values are - - -See the man page for -directfbrc -5 for additional information. - - -: -PS/2, IMPS/2, -MS, MS3, -MouseMan and MouseSystems. -In most cases the default protocol should work correctly. - - - - - -mouse/device - - -For the gtk frontend (graphical installer), users can specify the mouse -device to be used by setting this parameter. This is mostly useful if the -mouse is connected to a serial port (serial mouse). Example: -mouse/device=/dev/ttyS1. - - - - - -mouse/left - - -For the gtk frontend (graphical installer), users can switch the mouse to -left-handed operation by setting this parameter to true. - - - - - -directfb/hw-accel - - -For the gtk frontend (graphical installer), hardware acceleration in directfb -is disabled by default. Set this parameter to true to -enable it. - - - - - -rescue/enable - - -Set to true to enter rescue mode rather than -performing a normal installation. See . - - - - - - - - - - Using boot parameters to answer questions - - -With some exceptions, a value can be set at the boot prompt for any question -asked during the installation, though this is only really useful in specific -cases. General instructions how to do this can be found in -. Some specific examples are listed below. - - - - - - -debian-installer/language (language) -debian-installer/country (country) -debian-installer/locale (locale) - - -There are two ways to specify the language, country and locale to use for -the installation and the installed system. - - - -The first and easiest is to pass only the parameter locale. -Language and country will then be derived from its value. You can for example -use locale=de_CH to select German as language and -Switzerland as country (de_CH.UTF-8 will be set as default -locale for the installed system). Limitation is that not all possible -combinations of language, country and locale can be achieved this way. - - - -The second, more flexible option is to specify language -and country separately. In this case -locale can optionally be added to specify a specific -default locale for the installed system. Example: -language=en country=DE locale=en_GB.UTF-8. - - - - - -anna/choose_modules (modules) - - -Can be used to automatically load installer components that are not loaded -by default. -Examples of optional components that may be useful are -openssh-client-udeb (so you can use -scp during the installation) and -ppp-udeb (see ). - - - - - -netcfg/disable_dhcp - - -Set to true if you want to disable DHCP and instead -force static network configuration. - - - - - -mirror/protocol (protocol) - - -By default the installer will use the http protocol to download files from -&debian; mirrors and changing that to ftp is not possible during installations -at normal priority. By setting this parameter to ftp, -you can force the installer to use that protocol instead. Note that you -cannot select an ftp mirror from a list, you have to enter the hostname -manually. - - - - - -tasksel:tasksel/first (tasks) - - -Can be used to select tasks that are not available from the interactive task -list, such as the kde-desktop task. -See for additional information. - - - - - - - - - - Passing parameters to kernel modules - - -If drivers are compiled into the kernel, you can pass parameters to them -as described in the kernel documentation. However, if drivers are compiled -as modules and because kernel modules are loaded a bit differently during -an installation than when booting an installed system, it is not possible -to pass parameters to modules as you would normally do. Instead, you need -to use a special syntax recognized by the installer which will then make -sure that the parameters are saved in the proper configuration files and -will thus be used when the modules are actually loaded. The parameters -will also be propagated automatically to the configuration for the installed -system. - - - -Note that it is now quite rare that parameters need to be passed to modules. -In most cases the kernel will be able to probe the hardware present in a -system and set good defaults that way. However, in some situations it may -still be needed to set parameters manually. - - - -The syntax to use to set parameters for modules is: - - -module_name.parameter_name=value - - -If you need to pass multiple parameters to the same or different modules, -just repeat this. For example, to set an old 3Com network interface card -to use the BNC (coax) connector and IRQ 10, you would pass: - - -3c509.xcvr=3 3c509.irq=10 - - - - - - - Blacklisting kernel modules - - -Sometimes it may be necessary to blacklist a module to prevent it from -being loaded automatically by the kernel and udev. One reason could be that -a particular module causes problems with your hardware. The kernel also -sometimes lists two different drivers for the same device. This can cause -the device to not work correctly if the drivers conflict or if the wrong -driver is loaded first. - - - -You can blacklist a module using the following syntax: -module_name.blacklist=yes. -This will cause the module to be blacklisted in -/etc/modprobe.d/blacklist.local both during the -installation and for the installed system. - - - -Note that a module may still be loaded by the installation system itself. -You can prevent that from happening by running the installation in expert -mode and unselecting the module from the list of modules displayed during -the hardware detection phases. - - - - diff --git a/nl/boot-installer/powerpc.xml b/nl/boot-installer/powerpc.xml deleted file mode 100644 index c11cbc4ba..000000000 --- a/nl/boot-installer/powerpc.xml +++ /dev/null @@ -1,262 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - -Currently, the only &arch-title; subarchitectures that support CD-ROM -booting are PReP (though not all systems) and New World PowerMacs. -On PowerMacs, hold the c key, or else the combination of -Command, Option, -Shift, and Delete -keys together while booting to boot from the CD-ROM. - - - -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. - - - -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 for booting from -the hard disk, except use the path to yaboot on the -CD at the OF prompt, such as - - -0 > boot cd:,\install\yaboot - - - - - - - Booting from Hard Disk - -&boot-installer-intro-hd.xml; - - - - Booting OldWorld PowerMacs from MacOS - - -If you set up BootX in , you can -use it to boot into the installation system. Double click the -BootX application icon. Click on the -Options button and select Use -Specified RAM Disk. This will give you the -chance to select the ramdisk.image.gz file. You -may need to select the No Video Driver checkbox, -depending on your hardware. Then click the -Linux button to shut down MacOS and launch the -installer. - - - - - - - Booting NewWorld Macs from OpenFirmware - - -You will have already placed the vmlinux, -initrd.gz, yaboot, and -yaboot.conf files at the root level of your HFS -partition in . -You will now have to boot into OpenFirmware (see ). -At the prompt, type - - -0 > boot hd:x,yaboot - - -replacing x 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 ide0: instead of -hd:. In a few more seconds you will see a -yaboot prompt - - -boot: - - -At yaboot's boot: prompt, type either -install or install video=ofonly -followed by a &enterkey;. The -video=ofonly argument is for maximum -compatibility; you can try it if install -doesn't work. The &debian; installation program should start. - - - - - - - Booting from USB memory stick - - -Currently, NewWorld PowerMac systems are known to support USB booting. - - - - - -Make sure you have prepared everything from . 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. - -See . - - - -You will need to work out where the USB storage device appears in the -device tree, since at the moment ofpath cannot work -that out automatically. Type dev / ls and -devalias 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 -usb0/disk, usb0/hub/disk, -/pci@f2000000/usb@1b,1/disk@1, and -/pci@f2000000/usb@1b,1/hub@1/disk@1 work. - - - -Having worked out the device path, use a command like this to boot the -installer: - - -boot usb0/disk:2,\\:tbxi - - -The 2 matches the Apple_HFS or -Apple_Bootstrap partition onto which you copied the boot image earlier, -and the ,\\:tbxi part instructs Open Firmware to -boot from the file with an HFS file type of "tbxi" (i.e. -yaboot) in the directory previously blessed with -hattrib -b. - - - -The system should now boot up, and you should be presented with the -boot: prompt. Here you can enter optional boot -arguments, or just hit &enterkey;. - - - -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 . - - - - - Booting with TFTP - -&boot-installer-intro-net.xml; - - - -Currently, PReP and New World PowerMac systems support netbooting. - - - -On machines with Open Firmware, such as NewWorld Power Macs, enter the -boot monitor (see ) and -use the command - - -0 > boot enet:0 - - -If this doesn't work, you might have to add the filename like this: - - -0 > boot enet:0,yaboot - - -PReP and CHRP boxes -may have different ways of addressing the network. On a PReP machine, -you should try - - -boot net:server_ipaddr,file,client_ipaddr - - -On some PReP systems (e.g. Motorola PowerStack machines) the command -help boot may give a description of syntax and -available options. - - - - - - - Booting from Floppies - - -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. - - - -You will have already downloaded the floppy images you needed and -created floppies from the images in . - - - -To boot from the boot-floppy-hfs.img floppy, -place it in floppy drive after shutting the system down, and before -pressing the power-on button. - - -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. - - - -After booting, the root.bin 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. - - - - - - PowerPC Boot Parameters - - -Many older Apple monitors used a 640x480 67Hz mode. If your video -appears skewed on an older Apple monitor, try appending the boot -argument video=atyfb:vmode:6 , which will -select that mode for most Mach64 and Rage video hardware. For Rage 128 -hardware, this changes to -video=aty128fb:vmode:6 . - - - diff --git a/nl/boot-installer/s390.xml b/nl/boot-installer/s390.xml deleted file mode 100644 index f7991b127..000000000 --- a/nl/boot-installer/s390.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - - s390 Limitations - - -In order to run the installation system a working network setup and -ssh session is needed on S/390. - - - -The booting process starts with a network setup that prompts you for -several network parameters. If the setup is successful, you will login -to the system by starting an ssh session which will launch the -standard installation system. - - - - - - s390 Boot Parameters - - -On S/390 you can append boot parameters in the parm file. This file can -either be in ASCII or EBCDIC format. -A sample parm file parmfile.debian is provided with -the installation images. - - - - - diff --git a/nl/boot-installer/sparc.xml b/nl/boot-installer/sparc.xml deleted file mode 100644 index faf39b310..000000000 --- a/nl/boot-installer/sparc.xml +++ /dev/null @@ -1,46 +0,0 @@ - - - - Booting with TFTP - -&boot-installer-intro-net.xml; - - - -On machines with OpenBoot, simply enter the boot monitor on the -machine which is being installed (see -). -Use the command boot net to boot from a TFTP -and RARP server, or try boot net:bootp or -boot net:dhcp to boot from a TFTP and BOOTP -or DHCP server. You can pass extra boot parameters to &d-i; at the end -of the boot command. - - - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - -Most OpenBoot versions support the boot cdrom -command which is simply an alias to boot from the SCSI device on ID 6 -(or the secondary master for IDE based systems). - - - - - IDPROM Messages - - -If you cannot boot because you get messages about a problem with -IDPROM, then it's possible that your NVRAM battery, which -holds configuration information for you firmware, has run out. See the -Sun NVRAM FAQ for more -information. - - - diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml deleted file mode 100644 index 392e7f1f0..000000000 --- a/nl/boot-installer/trouble.xml +++ /dev/null @@ -1,572 +0,0 @@ - - - - - Troubleshooting the Installation Process - - - - - CD-ROM Reliability - - -Sometimes, especially with older CD-ROM drives, the installer may fail -to boot from a CD-ROM. The installer may also — even after booting -successfully from CD-ROM — fail to recognize the CD-ROM or return -errors while reading from it during the installation. - - - -There are many different possible causes for these problems. We can -only list some common issues and provide general suggestions on how to -deal with them. The rest is up to you. - - - -There are two very simple things that you should try first. - - - - -If the CD-ROM does not boot, check that it was inserted correctly and that -it is not dirty. - - - - -If the installer fails to recognize a CD-ROM, try just running the option - Detect and mount CD-ROM -a second time. Some DMA related issues with older CD-ROM drives are known to -be resolved in this way. - - - - - - -If this does not work, then try the suggestions in the subsections below. -Most, but not all, suggestions discussed there are valid for both CD-ROM and -DVD, but we'll use the term CD-ROM for simplicity. - - - -If you cannot get the installation working from CD-ROM, try one of the -other installation methods that are available. - - - - - Common issues - - - - -Some older CD-ROM drives do not support reading from discs that were burned -at high speeds using a modern CD writer. - - - - -If your system boots correctly from the CD-ROM, it does not necessarily -mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller -that your CD-ROM drive is connected to). - - - - -Some older CD-ROM drives do not work correctly if direct memory -access (DMA) is enabled. - - - - - - - - How to investigate and maybe solve issues - - -If the CD-ROM fails to boot, try the suggestions listed below. - - - - -Check that your BIOS actually supports booting from CD-ROM (older systems -possibly don't) and that your CD-ROM drive supports the media you are using. - - - - -If you downloaded an iso image, check that the md5sum of that image matches -the one listed for the image in the MD5SUMS file that -should be present in the same location as where you downloaded the image -from. - - -$ md5sum debian-testing-i386-netinst.iso -a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso - - -Next, check that the md5sum of the burned CD-ROM matches as well. The -following command should work. It uses the size of the image to read the -correct number of bytes from the CD-ROM. - - -$ dd if=/dev/cdrom | \ -> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \ -> md5sum -a20391b12f7ff22ef705cee4059c6b92 - -262668+0 records in -262668+0 records out -134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s - - - - - - - -If, after the installer has been booted successfully, the CD-ROM is not -detected, sometimes simply trying again may solve the problem. If you have -more than one CD-ROM drive, try changing the CD-ROM to the other drive. -If that does not work or if the CD-ROM is recognized but there are errors -when reading from it, try the suggestions listed below. Some basic knowledge -of &arch-kernel; is required for this. -To execute any of the commands, you should first switch to the second -virtual console (VT2) and activate the shell there. - - - - -Switch to VT4 or view the contents of /var/log/syslog -(use nano as editor) to check for any specific error -messages. After that, also check the output of dmesg. - - - - -Check in the output of dmesg if your CD-ROM drive was -recognized. You should see something like (the lines do not necessarily -have to be consecutive): - - -Probing IDE interface ide1... -hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive -ide1 at 0x170-0x177,0x376 on irq 15 -hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33) -Uniform CD-ROM driver Revision: 3.20 - - -If you don't see something like that, chances are the controller your CD-ROM -is connected to was not recognized or may be not supported at all. If you -know what driver is needed for the controller, you can try loading it manually -using modprobe. - - - - -Check that there is a device node for your CD-ROM drive under -/dev/. In the example above, this would be -/dev/hdc. -There should also be a /dev/cdrom. - - - - -Use the mount command to check if the CD-ROM is already -mounted; if not, try mounting it manually: - - -$ mount /dev/hdc /cdrom - - -Check if there are any error messages after that command. - - - - -Check if DMA is currently enabled: - - -$ cd /proc/ide/hdc -$ grep using_dma settings -using_dma 1 0 1 rw - - -A 1 in the first column after using_dma -means it is enabled. If it is, try disabling it: - - -$ echo -n "using_dma:0" >settings - - -Make sure that you are in the directory for the device that corresponds -to your CD-ROM drive. - - - - -If there are any problems during the installation, try checking the integrity -of the CD-ROM using the option near the bottom of the installer's main menu. -This option can also be used as a general test if the CD-ROM can be read -reliably. - - - - - - - - - - Floppy Disk Reliability - - - -The biggest problem for people using floppy disks to install &debian; -seems to be floppy disk reliability. - - - -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. - - - -If you are having the installation stall at a particular floppy, the first -thing you should do is write the image to a different -floppy and see if that solves the problem. Simply reformatting the old -floppy may not be sufficient, even if it appears that the floppy was -reformatted and written with no errors. It is sometimes useful to try -writing the floppy on a different system. - - - -One user reports he had to write the images to floppy -three times before one worked, and then -everything was fine with the third floppy. - - - -Normally you should not have to download a floppy image again, but if you -are experiencing problems it is always useful to verify that the images -were downloaded correctly by verifying their md5sums. - - - -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. - - - - - Boot Configuration - - - -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 . - - - -Often, problems can be solved by removing add-ons and peripherals, and -then trying booting again. Internal modems, sound -cards, and Plug-n-Play devices can be especially problematic. - - - -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 mem=512m. - - - - - - Common &arch-title; Installation Problems - - -There are some common installation problems that can be solved or avoided by -passing certain boot parameters to the installer. - - - -Some systems have floppies with inverted DCLs. If you receive -errors reading from the floppy, even when you know the floppy is good, -try the parameter floppy=thinkpad. - - - -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 -hd=cylinders,heads,sectors. - - - -If you have a very old machine, and the kernel hangs after saying -Checking 'hlt' instruction..., then -you should try the no-hlt boot argument, which -disables this test. - - - -Some systems (especially laptops) that have a native resolution that is not -a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank -display after the installer has been booted. In that case adding the boot -parameter vga=788 - - -The parameter vga=788 will activate the VESA -framebuffer with a resolution of 800x600. This will probably work, but may -not be the optimal resolution for your system. A list of supported -resolutions can be obtained by using vga=ask, but -you should be aware that list may not be complete. - - - may help. If that does not work, -try adding the boot parameter fb=false. - - - -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 -fb=false to disable the framebuffer -console. Only a reduced set of -languages will be available during the installation due to limited -console features. See for details. - - - - - System Freeze During the PCMCIA Configuration Phase - - -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 -hw-detect/start_pcmcia=false boot parameter. You can -then configure PCMCIA after the installation is completed and exclude the -resource range causing the problems. - - - -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 exclude port -0x800-0x8ff here. There is also a list of some common -resource range options in the System -resource settings section of the PCMCIA HOWTO. Note that you -have to omit the commas, if any, when you enter this value in the -installer. - - - - - - System Freeze while Loading USB Modules - - -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 nousb parameter at the boot prompt. - - - - - - - Common &arch-title; Installation Problems - - -There are some common installation problems that are worth mentioning. - - - - Misdirected video output - - -It is fairly common for &arch-title; to have two video cards in one machine, -for example an ATI card and a Sun Creator 3D. In some cases, this may result -in the video output getting misdirected soon after the system boots. In -typical cases, the display will only show: - - -Remapping the kernel... done -Booting Linux... - - -To work around this, you can either pull out one of the video cards, or -disable the one not used during the OpenProm boot phase using a kernel -parameter. For example, to disable an ATI card, you should boot the -installer with video=atyfb:off. - - - -Note that you may also have to manually add this parameter to the silo -configuration (edit /target/etc/silo.conf before -rebooting) and, if you installed X11, modify the video driver in -/etc/X11/xorg.conf. - - - - - - Failure to Boot or Install from CD-ROM - - -Some Sparc systems are notoriously difficult to boot from CD-ROM and -even if they do boot, there may be inexplicable failures during the -installation. Most problems have been reported with SunBlade systems. - - - -We recommend to install such systems by netbooting the installer. - - - - - - - Interpreting the Kernel Startup Messages - - - -During the boot sequence, you may see many messages in the form -can't find something, -or something -not present, can't initialize -something, -or even this driver release depends -on something. -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 ). - - - - - - - Reporting Installation Problems - - -If you get through the initial boot phase but cannot complete the install, -the menu option Save debug logs may be helpful. -It lets you store system error logs and configuration information from the -installer to a floppy, or download them using a web browser. - -This information may provide clues as to what went wrong and how to -fix it. If you are submitting a bug report, you may want to attach -this information to the bug report. - - - -Other pertinent installation messages may be found in -/var/log/ during the -installation, and /var/log/installer/ -after the computer has been booted into the installed system. - - - - - - Submitting Installation Reports - - -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. - - - -Note that your installation report will be published in the &debian; Bug -Tracking System (BTS) and forwarded to a public mailing list. Make sure that -you use an e-mail address that you do not mind being made public. - - - -If you have a working &debian; system, the easiest way to send an installation -report is to install the installation-report and -reportbug packages -(aptitude install installation-report reportbug), -configure reportbug as explained in -, and run the command reportbug -installation-reports. - - - -Alternatively you can use this template when filling out -installation reports, and file the report as a bug report against the -installation-reports pseudo package, by sending it to -submit@bugs.debian.org. - - -Package: installation-reports - -Boot method: <How did you boot the installer? CD? floppy? network?> -Image version: <Full URL to image you downloaded is best> -Date: <Date and time of the install> - -Machine: <Description of machine (eg, IBM Thinkpad R32)> -Processor: -Memory: -Partitions: <df -Tl will do; the raw partition table is preferred> - -Output of lspci -knn (or lspci -nn): - -Base System Installation Checklist: -[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it - -Initial boot: [ ] -Detect network card: [ ] -Configure network: [ ] -Detect CD: [ ] -Load installer modules: [ ] -Detect hard drives: [ ] -Partition hard drives: [ ] -Install base system: [ ] -Clock/timezone setup: [ ] -User/password setup: [ ] -Install tasks: [ ] -Install boot loader: [ ] -Overall install: [ ] - -Comments/Problems: - -<Description of the install, in prose, and any thoughts, comments - and ideas you had during the initial install.> - - -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. - - - - diff --git a/nl/boot-installer/x86.xml b/nl/boot-installer/x86.xml deleted file mode 100644 index e090058db..000000000 --- a/nl/boot-installer/x86.xml +++ /dev/null @@ -1,433 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - - - - - - Booting from Windows - - -To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM -or USB memory stick installation media as described in - and . - - - -If you use an installation CD or DVD, a pre-installation program should be -launched automatically when you insert the disc. -In case Windows does not start it automatically, or if you are using a USB -memory stick, you can run it manually by accessing the device and executing -setup.exe. - - - -After the program has been started, a few preliminary questions will be -asked and the system will be prepared to start the &debian-gnu; installer. - - - - - - - - Booting from Linux Using <command>LILO</command> or - <command>GRUB</command> - - -To boot the installer from hard disk, you must first download -and place the needed files as described in . - - - -If you intend to use the hard drive only for booting and then -download everything over the network, you should download the -netboot/debian-installer/&architecture;/initrd.gz file and its -corresponding kernel -netboot/debian-installer/&architecture;/linux. This will allow you -to repartition the hard disk from which you boot the installer, although you -should do so with care. - - - -Alternatively, if you intend to keep an existing partition on the hard -drive unchanged during the install, you can download the -hd-media/initrd.gz file and its kernel, as well as -copy a CD (or DVD) iso to the drive (make sure the file is named ending in -.iso). The installer can then boot from the drive -and install from the CD/DVD image, without needing the network. - - - -For LILO, you will need to configure two -essential things in /etc/lilo.conf: - - - -to load the initrd.gz installer at boot time; - - - - -have the vmlinuz kernel use a RAM disk as -its root partition. - - - - -Here is a /etc/lilo.conf example: - - - - -image=/boot/newinstall/vmlinuz - label=newinstall - initrd=/boot/newinstall/initrd.gz - - -For more details, refer to the -initrd -4 and -lilo.conf -5 man pages. Now run -lilo and reboot. - - - -The procedure for GRUB is quite similar. Locate your -menu.lst in the /boot/grub/ -directory (or sometimes /boot/boot/grub/) and add an -entry for the installer, for example (assuming /boot -is on the first partition of the first disk in the system): - - -title New Install -root (hd0,0) -kernel /boot/newinstall/vmlinuz -initrd /boot/newinstall/initrd.gz - - - - -From here on, there should be no difference between GRUB -or LILO. - - - - - - Booting from USB Memory Stick - - -Let's assume you have prepared everything from and . 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 boot: prompt. Here you can enter optional boot -arguments, or just hit &enterkey;. - - - - - - Booting from Floppies - - -You will have already downloaded the floppy images you needed and -created floppies from the images in . - - - - -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. - - - -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 root= 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 -install root=/dev/hdc at the boot prompt. - - - -Note that on some machines, Control -Alt Delete does not -properly reset the machine, so a hard 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. - - - -The floppy disk will be accessed, and you should then see a screen -that introduces the boot floppy and ends with the boot: -prompt. - - - -Once you press &enterkey;, you should see the message -Loading..., followed by -Uncompressing Linux..., 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 . - - - -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 -debian-installer is automatically launched. - - - - - Booting with TFTP - -&boot-installer-intro-net.xml; - - - -There are various ways to do a TFTP boot on i386. - - - - NIC or Motherboard that support PXE - - -It could be that your Network Interface Card or Motherboard provides -PXE boot functionality. -This is a Intel re-implementation -of TFTP boot. If so, you may be able to configure your BIOS to boot from the -network. - - - - - NIC with Network BootROM - - -It could be that your Network Interface Card provides -TFTP boot functionality. - - - -Let us (&email-debian-boot-list;) know how did you manage it. -Please refer to this document. - - - - - Etherboot - - -The etherboot project -provides bootdiskettes and even bootroms that do a TFTPboot. - - - - - - - The Boot Screen - - -When the installer boots, you should be presented with a friendly graphical -screen showing the &debian; logo and a menu: - - -Installer boot menu - -Install -Graphical install -Advanced options > -Help - -Press ENTER to boot or TAB to edit a menu entry - - -Depending on the installation method you are using, the Graphical -install option may not be available. - - - -For a normal installation, select either the Install or -the Graphical install entry — using either the -arrow keys on your keyboard or by typing the first (highlighted) letter -— and press &enterkey; to boot the installer. - - - -The Advanced options entry gives access to a second menu -that allows to boot the installer in expert mode, in rescue mode and for -automated installs. - - - -If you wish or need to add any boot parameters for either the installer -or the kernel, press &tabkey;. This will display the default boot command -for the selected menu entry and allow to add additional options. The help -screens (see below) list some common possible options. Press &enterkey; to -boot the installer with your options; pressing &escapekey; will return you -to the boot menu and undo any changes you made. - - - -Choosing the Help entry will result in the first help screen -being displayed which gives an overview of all available help screens. -Note that it is not possible to return to the boot menu after the help -screens have been displayed. However, the F3 and F4 help screens list -commands that are equivalent to the boot methods listed in the menu. All -help screens have a boot prompt at which the boot command can be typed: - - -Press F1 for the help index, or ENTER to boot: - - -At this boot prompt you can either just press &enterkey; to boot the -installer with default options or enter a specific boot command and, -optionally, boot parameters. A number of boot parameters which might be -useful can be found on the various help screens. If you do add any -parameters to the boot command line, be sure to first type the boot method -(the default is install) and a space before the -first parameter (e.g., install fb=false). - - - -The keyboard is assumed to have a default American English layout at this -point. This means that if your keyboard has a different (language-specific) -layout, the characters that appear on the screen may be different from what -you'd expect when you type parameters. Wikipedia has a -schema of the US keyboard layout which -can be used as a reference to find the correct keys to use. - - - - -If you are using a system that has the BIOS configured to use serial console, -you may not be able to see the initial graphical splash screen upon booting -the installer; you may even not see the boot menu. The same can happen if -you are installing the system via a remote management device that provides a -text interface to the VGA console. Examples of these devices include the text -console of Compaq's integrated Lights Out (iLO) and HP's -Integrated Remote Assistant (IRA). - - - -To bypass the graphical boot screen you can either blindly press &escapekey; -to get a text boot prompt, or (equally blindly) press H -followed by &enterkey; to select the Help option described -above. After that your keystrokes should be echoed at the prompt. -To prevent the installer from using the framebuffer for the rest of the -installation, you will also want to add vga=normal fb=false -to the boot prompt, as described in the help text. - - - - - diff --git a/nl/boot-new/boot-new.xml b/nl/boot-new/boot-new.xml deleted file mode 100644 index 7338c558e..000000000 --- a/nl/boot-new/boot-new.xml +++ /dev/null @@ -1,224 +0,0 @@ - - - - De computer opstarten met uw nieuwe &debian; systeem - - Het moment van de waarheid - - -De eerste keer dat u uw computer opnieuw opstart met uw nieuwe &debian; -systeem is een soort vuurdoop. - - - -Als u een standaard installatie heeft uitgevoerd, is het menu van de -grub, of eventueel van de lilo -opstartlader, het eerste dat u behoort te zien nadat het systeem opnieuw -opstart. -De eerste keuzes in het menu zullen betrekking hebben op uw nieuwe &debian; -systeem. Als u ook andere besturingssystemen (zoals Windows) op de computer -had die door het installatiesysteem gedetecteerd zijn, dan zullen deze lager -in het menu zijn opgenomen. - -Als het systeem niet juist opstart, raak dan vooral niet in paniek. Als de -installatie successvol is afgerond, dan is de kans groot dat slechts een -relatief klein probleem het opstarten van het systeem met &debian; verhindert. -In de meeste gevallen kunnen zulke problemen worden opgelost zonder de -installatie the hoeven herhalen. Eén van de beschikbare opties om -opstartproblemen te verhelpen is het gebruik van de ingebouwde -reddingsmodus van het installatiesysteem (zie ). - - - -Als &debian; en &arch-kernel; nieuw zijn voor u, dan kunt u hierbij mogelijk wat hulp -gebruiken van meer ervaren gebruikers. -Voor directe on-line hulp kunt u de IRC-kanalen #debian of -#debian-boot op het OFTC-netwerk proberen. Of anders kunt u een bericht sturen -naar de mailinglijst debian-user. -Voor minder gangbare architecturen zoals &arch-title;, -is uw beste optie om hulp te vragen op de -mailinglijst debian-&arch-listname;. -Ook kunt u ons (in het Engels!) een installatieverslag sturen, zoals -beschreven in . Probeer daarbij uw probeem helder -te omschrijven en neem in het verslag op eventuele getoonde berichten die -anderen kunnen helpen het probleem te diagnosticeren. - - - -Als er andere besturingssystemen op uw computer aanwezig waren die niet -gedetecteerd, of niet correct gedetecteerd werden, stuur ons dan een -installatieverslag. - - - - - OldWorld PowerMacs - - - -Als de machine niet goed opstart na afronding van de installatie en stopt met -een boot: prompt, probeer dan Linux -gevolgd door &enterkey; in te geven. (De standaard opstartconfiguratie in -quik.conf is Linux genaamd.) De namen die in -quik.conf zijn gedefinieerd, worden getoond als u bij de -boot: prompt de Tab-toets indrukt. U kunt -ook proberen opnieuw het installatieprogramma op te starten en vervolgens het -bestand /target/etc/quik.conf te wijzigen dat daar is -weggeschreven door de stap Quik op een harde schijf -installeren. Informatie over het werken met -quik is beschikbaar op -. - - - - -Geef, om MacOS op te starten zonder dat de nvram wordt ingesteld naar -de standaardwaarden, bij de OpenFirmware-prompt het commando -bye (ervan uitgaande dat MacOS niet van de machine -is verwijderd). Houd, om een OpenFirmware-prompt te verkrijgen, de toetsen - command option o -f ingedrukt terwijl u de machine inschakelt. -Houd, als u de de wijzigingen in de OpenFirmware nvram wilt herstellen, -de toetsen command option -p r ingedrukt terwijl u -de machine inschakelt. - - - -Als u BootX gebruikt om het geïnstalleerde systeem op -te starten, kunt u gewoon de gewenste kernel selecteren in de map -Linux Kernels, de optie ramdisk deselecteren en het -root-apparaat (bijvoorbeeld /dev/hda8) toevoegen -dat overeenkomt met uw installatie. - - - - - NewWorld PowerMacs - - - -Op G4- en iBook-systemen, kunt u de toets option ingedrukt -houden. U krijgt dan een grafisch scherm met een knop voor elk besturingssysteem -dat kan worden opgestart: &debian-gnu; zal een knop met daarop een klein icoon van -een penguin zijn. - - - -Als u MacOS heeft behouden en als dat op enig moment de OpenFirmware-variabele -boot-device zou wijzigen, dan dient u OpenFirmware te herstellen -naar zijn standaard configuratie. Hiervoor houdt u de toetsen -command option p -r ingedrukt terwijl u de machine inschakelt. - - - -De namen die zijn gedefinieerd in yaboot.conf zullen -worden getoond als u bij de boot: prompt de toets -Tab indrukt. - - - -Het herstellen van OpenFirmware op G3- of G4-systemen zal standaard resulteren -in het opstarten van &debian-gnu; (als u de schijf juist heeft ingedeeld en de -Apple_Bootstrap partitie als eerste heeft geplaatst). Als u &debian-gnu; op een -SCSI harde schijf en MacOS op een IDE harde schijf heeft, werkt dit mogelijk -niet en zal u in OpenFirmware de variabele boot-device moeten -instellen. Normaal gesproken doet ybin dit automatisch. - - - -Nadat u &debian-gnu; voor de eerste keer heeft opgestart, kunt u aanvullende -opties die u wenst (zoals voor 'dual boot') toevoegen aan -/etc/yaboot.conf en ybin starten om uw -opstartpartitie bij te werken met de gewijzigde configuratie. Aanvullende -informatie is beschikbaar op -yaboot HOWTO. - - - - - -&mount-encrypted.xml; - - - Aanloggen - - - -Nadat het systeem is opgestart, wordt de aanlogprompt getoond. -Log aan met uw persoonlijke gebruikersaccount door de gebruikersnaam en -het wachtwoord die u tijdens de installatie heeft geselecteerd, in te -geven. Uw systeem is nu klaar voor gebruik. - - - -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. - - - -De documentatie bij programma's die u heeft geïnstalleerd, kunt u vinden in -submappen onder /usr/share/doc/. Merk op dat deze -submappen de naam hebben van de geïnstalleerde &debian; pakketten, niet van de -programma's zelf. -Meer uitgebreide documentatie is vaak opgenomen in afzonderlijke -documentatiepakketten die in het algemeen niet standaard geïnstalleerd -worden. Documentatie over het pakketbeheersysteem apt kan -bijvoorbeeld worden gevonden in de pakketten apt-doc -of apt-howto. - - - -Daarnaast zijn er enkele bijzondere mappen onder -/usr/share/doc/. Linux HOWTO handleidingen worden -in .gz-formaat (gecomprimeerd) geïnstalleerd in -/usr/share/doc/HOWTO/en-txt/. Na installatie van -dhelp vindt u in -/usr/share/doc/HTML/index.html een inhoudsopgave -van documentatie die met een browser kan worden bekeken. - - - -Een eenvoudige manier om deze documenten met een tekstuele browser te -bekijken, is met de volgende commando's: - - -$ cd /usr/share/doc/ -$ w3m . - - -De punt achter het commando w3m bepaalt dat de inhoud van -de huidige directory moet worden getoond. - - - -If you have a graphical desktop environment installed, you can also use -its web browser. Start the web browser from the application menu and -enter /usr/share/doc/ in the address bar. - -Als u een grafische desktopomgeving heeft geïnstalleerd, kunt u ook de -bijbehorende webbrowser gebruiken. Start de browser vanuit het -toepassingenmenu en type /usr/share/doc/ in de -adresregel. - - - -U kunt ook info command of -man command gebruiken om -documentatie te bekijken over de meeste opdrachten die vanaf de opdrachtregel -gegeven kunnen worden. Ook als u een opdracht ingeeft gevolgd door ---help, 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 | more -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 tab te drukken. - - - - - - diff --git a/nl/boot-new/mount-encrypted.xml b/nl/boot-new/mount-encrypted.xml deleted file mode 100644 index d88c83144..000000000 --- a/nl/boot-new/mount-encrypted.xml +++ /dev/null @@ -1,181 +0,0 @@ - - - - - Mounting encrypted volumes - - - -If you created encrypted volumes during the installation and assigned -them mount points, you will be asked to enter the passphrase for each -of these volumes during the boot. The actual procedure differs -slightly between dm-crypt and loop-AES. - - - - - dm-crypt - - - -For partitions encrypted using dm-crypt you will be shown the following -prompt during the boot: - - -Starting early crypto disks... part_crypt(starting) -Enter LUKS passphrase: - - -In the first line of the prompt, part is the -name of the underlying partition, e.g. sda2 or md0. -You are now probably wondering -for which volume you are actually entering the -passphrase. Does it relate to your /home? Or to -/var? Of course, if you have just one encrypted -volume, this is easy and you can just enter the passphrase you used -when setting up this volume. If you set up more than one encrypted -volume during the installation, the notes you wrote down as the last -step in come in handy. If you did not -make a note of the mapping between -part_crypt and the mount -points before, you can still find it -in /etc/crypttab -and /etc/fstab of your new system. - - - -The prompt may look somewhat different when an encrypted root file system is -mounted. This depends on which initramfs generator was used to generate the -initrd used to boot the system. The example below is for an initrd generated -using initramfs-tools: - - -Begin: Mounting root file system... ... -Begin: Running /scripts/local-top ... -Enter LUKS passphrase: - - - - -No characters (even asterisks) will be shown while entering the passphrase. -If you enter the wrong passphrase, you have two more tries to correct it. -After the third try the boot process will skip this volume and continue to -mount the next filesystem. Please see -for further information. - - - -After entering all passphrases the boot should continue as usual. - - - - - - loop-AES - - - -For partitions encrypted using loop-AES you will be shown the following -prompt during the boot: - - -Checking loop-encrypted file systems. -Setting up /dev/loopX (/mountpoint) -Password: - - - - -No characters (even asterisks) will be shown while entering the passphrase. -If you enter the wrong passphrase, you have two more tries to correct it. -After the third try the boot process will skip this volume and continue to -mount the next filesystem. Please see -for further information. - - - -After entering all passphrases the boot should continue as usual. - - - - - - Troubleshooting - - - -If some of the encrypted volumes could not be mounted because a wrong -passphrase was entered, you will have to mount them manually after the -boot. There are several cases. - - - - - - -The first case concerns the root partition. When it is not mounted -correctly, the boot process will halt and you will have to reboot the -computer to try again. - - - - -The easiest case is for encrypted volumes holding data like -/home or /srv. You can -simply mount them manually after the boot. For loop-AES this is -a one-step operation: - - -# mount /mount_point -Password: - - -where /mount_point should be replaced by -the particular directory (e.g. /home). The only -difference from an ordinary mount is that you will be asked to enter -the passphrase for this volume. - - - -For dm-crypt this is a bit trickier. First you need to register the -volumes with device mapper by running: - - -# /etc/init.d/cryptdisks start - - -This will scan all volumes mentioned -in /etc/crypttab and will create appropriate -devices under the /dev directory after entering -the correct passphrases. (Already registered volumes will be skipped, -so you can repeat this command several times without worrying.) After -successful registration you can simply mount the volumes the usual -way: - - -# mount /mount_point - - - - - -If any volume holding noncritical system files could not be mounted -(/usr or /var), the system -should still boot and you should be able to mount the volumes manually -like in the previous case. However, you will also need to (re)start -any services usually running in your default runlevel because it is -very likely that they were not started. The easiest way to achieve -this is by switching to the first runlevel and back by entering - - -# init 1 - - -at the shell prompt and pressing Control -D when asked for the root password. - - - - - - diff --git a/nl/hardware/accessibility.xml b/nl/hardware/accessibility.xml deleted file mode 100644 index 565f47ff8..000000000 --- a/nl/hardware/accessibility.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - - Braille Displays - - -Support for braille displays is determined by the underlying support -found in brltty. Most displays work under -brltty, connected via either a serial port, USB -or bluetooth. Details on supported braille devices can be found on the -brltty website. -&debian-gnu; &release; ships with brltty version -&brlttyver;. - - - - - - Hardware Speech Synthesis - - -Support for hardware speech synthesis devices is determined by the -underlying support found in speakup. -speakup only supports integrated boards and -external devices connected to a serial port (no USB or serial-to-USB -adapters are supported). Details on supported hardware speech synthesis -devices can be found on the -speakup website. -&debian-gnu; &release; ships with speakup version -&speakupver;. - - - diff --git a/nl/hardware/buying-hardware.xml b/nl/hardware/buying-hardware.xml deleted file mode 100644 index 367aac515..000000000 --- a/nl/hardware/buying-hardware.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - Purchasing Hardware Specifically for GNU/&arch-kernel; - - - -There are several vendors, who ship systems with &debian; or other -distributions of GNU/Linux -pre-installed. 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. - - - -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 windows refund may get you some useful -information to help with that. - - - -Whether or not you are purchasing a system with &arch-kernel; bundled, or even -a used system, it is still important to check that your hardware is -supported by the &arch-kernel; kernel. Check if your hardware is listed in -the references found above. Let your salesperson (if any) know that -you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware -vendors. - - - - Avoid Proprietary or Closed Hardware - - -Some hardware manufacturers simply won't tell us how to write drivers -for their hardware. Others won't allow us access to the documentation -without a non-disclosure agreement that would prevent us from -releasing the &arch-kernel; source code. - - - -Since we haven't been granted access to the documentation on these -devices, they simply won't work under &arch-kernel;. You can help by asking -the manufacturers of such hardware to release the documentation. If -enough people ask, they will realize that the free software community -is an important market. - - - - - - Windows-specific Hardware - - -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 WinModem -or Made especially for Windows-based computers. 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 not passed on to the -user and this hardware may even be more expensive than equivalent -devices that retain their embedded intelligence. - - - -You should avoid Windows-specific hardware for two reasons. The first -is that the manufacturers do not generally make the resources -available to write a &arch-kernel; driver. Generally, the hardware and -software interface to the device is proprietary, and documentation is -not available without a non-disclosure agreement, if it is available -at all. This precludes it being used for free software, since free -software writers disclose the source code of their programs. The -second reason is that when devices like these have had their embedded -processors removed, the operating system must perform the work of the -embedded processors, often at real-time priority, -and thus the CPU is not available to run your programs while it is -driving these devices. Since the typical Windows user does not -multi-process as intensively as a &arch-kernel; user, the manufacturers hope -that the Windows user simply won't notice the burden this hardware -places on their CPU. However, any multi-processing operating system, -even Windows 2000 or XP, suffers from degraded performance when -peripheral manufacturers skimp on the embedded processing power of -their hardware. - - - -You can help improve this situation by encouraging these manufacturers -to release the documentation and other resources necessary for us to -program their hardware, but the best strategy is simply to avoid this -sort of hardware until it is listed as working in the -Linux Hardware Compatibility HOWTO. - - - - diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml deleted file mode 100644 index 97b0a5d5f..000000000 --- a/nl/hardware/hardware-supported.xml +++ /dev/null @@ -1,383 +0,0 @@ - - - - - Supported Hardware - - -&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, -gcc, etc. have been ported, and for which a &debian; -port exists, can run &debian;. Please refer to the Ports pages at - for -more details on &arch-title; architecture systems which have been -tested with &debian-gnu;. - - - -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. - - - - Supported Architectures - - -&debian; GNU/Linux &release; supports eleven major architectures and several -variations of each architecture known as flavors. - - - - - - - - Architecture&debian; Designation - SubarchitectureFlavor - - - - - - Intel x86-based - i386 - - - - - - AMD64 & Intel EM64T - amd64 - - - - - - ARM - armel - Intel IOP32x - iop32x - - Intel IXP4xx - ixp4xx - - Marvell Kirkwood - kirkwood - - Marvell Orion - orion5x - - Versatile - versatile - - - - Intel IA-64 - ia64 - - - - - - MIPS (big endian) - mips - SGI IP22 (Indy/Indigo 2) - r4k-ip22 - - SGI IP32 (O2) - r5k-ip32 - - MIPS Malta (32 bit) - 4kc-malta - - MIPS Malta (64 bit) - 5kc-malta - - - - MIPS (little endian) - mipsel - Cobalt - cobalt - - MIPS Malta (32 bit) - 4kc-malta - - MIPS Malta (64 bit) - 5kc-malta - - - - IBM/Motorola PowerPC - powerpc - PowerMac - pmac - - PReP - prep - - - - Sun SPARC - sparc - sun4u - sparc64 - - sun4v - - - - IBM S/390 - s390 - IPL from VM-reader and DASD - generic - - IPL from tape - tape - - - - - - -This document covers installation for the -&arch-title; architecture. If you are looking -for information on any of the other &debian;-supported architectures -take a look at the -Debian-Ports pages. - - - - -The &arch-title; architecture only supports Intel Itanium processors -and not the much more common 64-bit processors from the EM64T family -(including e.g. the Pentium D and the Core2 Duo). Those -systems are supported by the amd64 architecture -or, if you prefer a 32-bit userland, the i386 -architecture. - - - - -This is the first official release of &debian-gnu; for the &arch-title; -architecture. We feel that it has proven itself sufficiently to be -released. However, because it has not had the exposure (and hence -testing by users) that some other architectures have had, you may -encounter a few bugs. Use our -Bug Tracking System 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 -debian-&arch-listname; mailing list -as well. - - - - - -&supported-amd64.xml; -&supported-arm.xml; -&supported-hppa.xml; -&supported-i386.xml; -&supported-ia64.xml; -&supported-mips.xml; -&supported-mipsel.xml; -&supported-powerpc.xml; -&supported-s390.xml; -&supported-sparc.xml; - - Laptops - - -Laptops are also supported and nowadays most laptops work out of the box. -In case a laptop contains specialized or proprietary hardware, some specific -functions may not be supported. To see if your particular laptop works well -with GNU/Linux, see for example the -Linux Laptop pages. - - - - - - Multiple Processors - - -Multiprocessor support — also called symmetric multiprocessing -or SMP — is available for this architecture. The standard &debian; -&release; kernel image has been compiled with SMP support. The standard -kernel is also usable on non-SMP systems, but has a slight overhead which -will cause a small reduction in performance. For normal system use this -will hardly be noticable. - - - -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 . At this time -(kernel version &kernelversion;) the way you disable SMP is to deselect -&smp-config-option; in the &smp-config-section; -section of the kernel config. - - - - - -Multiple Processors - - - -Multiprocessor support — also called symmetric -multiprocessing or SMP — is available for this architecture. -The standard &debian; &release; kernel image has been compiled with -SMP-alternatives support. This means that the kernel -will detect the number of processors (or processor cores) and will -automatically deactivate SMP on uniprocessor systems. - - - -The 486 flavour of the &debian; kernel image packages for &arch-title; -is not compiled with SMP support. - - - - - - Multiple Processors - - -Multiprocessor support — also called symmetric -multiprocessing or SMP — is available for this architecture. -However, the standard &debian; &release; kernel image does not support -SMP. This should not prevent installation, since the standard, -non-SMP kernel should boot on SMP systems; the kernel will simply use -the first CPU. - - - -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 . At this time -(kernel version &kernelversion;) the way you enable SMP is to select -&smp-config-option; in the &smp-config-section; -section of the kernel config. - - - - - - Multiple Processors - - -Multiprocessor support — also called symmetric -multiprocessing or SMP — is available for this architecture, -and is supported by a precompiled &debian; kernel image. Depending on your -install media, this SMP-capable kernel may or may not be installed by -default. This should not prevent installation, since the standard, -non-SMP kernel should boot on SMP systems; the kernel will simply use -the first CPU. - - - -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 . At this -time (kernel version &kernelversion;) the way you enable SMP is to select -&smp-config-option; in the &smp-config-section; -section of the kernel config. - - - - - Graphics Card Support - - -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. - - - -&debian;'s support for graphical interfaces is determined by the -underlying support found in X.Org's X11 system. Most AGP, PCI, -PCIe, and PCI-X video cards work under X.Org. Details on supported graphics -buses, cards, monitors, and pointing devices can be found at -. &debian; &release; ships -with X.Org version &x11ver;. - - - - -The X.Org X Window System is only supported on the SGI Indy and the O2. - - - -Most graphics options commonly found on Sparc-based machines are supported. -X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, -sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), -PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards -(glint driver). To use an Elite3D card with X.org you additionally need to -install the afbinit package, and read the documentation -included with it on how to activate the card. - - - -It is not uncommon for a Sparc machine to have two graphics cards in a -default configuration. In such a case there is a possibility that the -Linux kernel will not direct its output to the card initially used by the -firmware. The lack of output on the graphical console may then be mistaken -for a hang (usually the last message seen on console is 'Booting Linux...'). -One possible solution is to physically remove one of the video cards; -another option is to disable one of the cards using a kernel boot parameter. -Also, if graphical output is not required or desired, serial console may be -used as an alternative. On some systems use of serial console can be -activated automatically by disconnecting the keyboard before booting the -system. - - - - -&network-cards.xml; -&accessibility-hardware.xml; -&supported-peripherals.xml; - - - - - Devices Requiring Firmware - - -Besides the availability of a device driver, some hardware also requires -so-called firmware or microcode -to be loaded into the device before it can become operational. This is most -common for network interface cards (especially wireless NICs), but for example -some USB devices and even some hard disk controllers also require firmware. - - - -In most cases firmware is non-free according to the criteria used by the -&debian-gnu; project and thus cannot be included in the main distribution -or in the installation system. If the device driver itself is included in -the distribution and if &debian-gnu; legally can distribute the firmware, -it will often be available as a separate package from the non-free section -of the archive. - - - -However, this does not mean that such hardware cannot be used during an -installation. Starting with &debian-gnu; 5.0, &d-i; supports loading -firmware files or packages containing firmware from a removable medium, -such as a floppy disk or USB stick. -See for detailed information on how to -load firmware files or packages during the installation. - - - diff --git a/nl/hardware/hardware.xml b/nl/hardware/hardware.xml deleted file mode 100644 index 781baf139..000000000 --- a/nl/hardware/hardware.xml +++ /dev/null @@ -1,20 +0,0 @@ - - - - - System Requirements - - - -This section contains information about what hardware you need to get -started with &debian;. You will also find links to further information -about hardware supported by GNU and &arch-kernel;. - - - -&hardware-supported.xml; -&buying-hardware.xml; -&installation-media.xml; -&memory-disk-requirements.xml; - - diff --git a/nl/hardware/installation-media.xml b/nl/hardware/installation-media.xml deleted file mode 100644 index d8d4f3c52..000000000 --- a/nl/hardware/installation-media.xml +++ /dev/null @@ -1,239 +0,0 @@ - - - - - Installation Media - - - -This section will help you determine which different media types you can use to -install &debian;. For example, if you have a floppy disk drive on your machine, -it can be used to install &debian;. There is a whole chapter devoted to media, -, which lists the advantages and -disadvantages of each media type. You may want to refer back to this page once -you reach that section. - - - - Floppies - - -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. - - - -For CHRP, floppy support is currently broken. - - - - - CD-ROM/DVD-ROM - - - -Whenever you see CD-ROM 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. - - - -CD-ROM based installation is supported for some architectures. -On machines which support bootable CD-ROMs, you should be able to do a -completely -floppy-less -tape-less -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 . - - - -SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The Linux CD-ROM HOWTO contains in-depth information -on using CD-ROMs with Linux. - - - -USB CD-ROM drives are also supported, as are FireWire devices that -are supported by the ohci1394 and sbp2 drivers. - - - -IDE/ATAPI CD-ROMs are supported on all ARM machines. - - - -On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive -capable of working with a logical blocksize of 512 bytes. Many of the -SCSI CD-ROM drives sold on the PC market do not have this -capability. If your CD-ROM drive has a jumper labeled -Unix/PC or 512/2048, place it in the -Unix or 512 position. -To start the install, simply choose the System installation -entry in the firmware. - - - - - Hard Disk - - - -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. - - - -Although the &arch-title; does not allow booting from SunOS -(Solaris), you can install from a SunOS partition (UFS slices). - - - - - USB Memory Stick - - - -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. - - - - - Network - - - -The network can be used during the installation to retrieve files needed -for the installation. Whether the network is used or not depends on the -installation method you choose and your answers to certain questions that -will be asked during the installation. The installation system supports -most types of network connections (including PPPoE, but not ISDN or PPP), -via either HTTP or FTP. After the installation is completed, you can also -configure your system to use ISDN and PPP. - - - -You can also boot the installation system over the -network. This is the preferred installation technique -for &arch-title;. - - - -Diskless installation, using network booting from a local area network -and NFS-mounting of all local filesystems, is another option. - - - - - Un*x or GNU system - - - -If you are running another Unix-like system, you could use it to install -&debian-gnu; without using the &d-i; described in the rest of this -manual. This kind of install may be useful for users with otherwise -unsupported hardware or on hosts which can't afford downtime. If you -are interested in this technique, skip to the . - - - - - Supported Storage Systems - - - -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 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. - - - -Generally, the &debian; installation system includes support for floppies, -IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA -and SCSI controllers and drives, USB, and FireWire. The supported file systems -include FAT, Win-32 FAT extensions (VFAT) and NTFS. - - - -Disk interfaces that emulate the AT hard disk interface -— often called MFM, RLL, IDE, or PATA — are supported. SATA and -SCSI disk controllers from many different manufacturers are supported. See the -Linux Hardware Compatibility HOWTO -for more details. - - - -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: - - - - -Sparc ESP - - - - -PTI Qlogic,ISP - - - - -Adaptec AIC7xxx - - - - -NCR and Symbios 53C8XX - - - - -IDE systems (such as the UltraSPARC 5) are also supported. See -Linux for SPARC Processors FAQ -for more information on SPARC hardware supported by the Linux kernel. - - - -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. - - - -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. - - - -Any storage system supported by the Linux kernel is also supported by -the boot system. - - - -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). - - - - - - diff --git a/nl/hardware/memory-disk-requirements.xml b/nl/hardware/memory-disk-requirements.xml deleted file mode 100644 index a862dc997..000000000 --- a/nl/hardware/memory-disk-requirements.xml +++ /dev/null @@ -1,33 +0,0 @@ - - - - - Memory and Disk Space Requirements - - - -You must have at least &minimum-memory; of memory and &minimum-fs-size; -of hard disk space to perform a normal installation. Note that these are -fairly minimal numbers. For more realistic figures, see -. - - - -Installation on systems with less memory - - - -Installation images that support the graphical installer require more -memory than images that support only the textual installer and should -not be used on systems with less than &minimum-memory; of memory. If -there is a choice between booting the regular and the graphical installer, -the former should be selected. - - - - or disk space available may be possible but is only advised for -experienced users. - - - - diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml deleted file mode 100644 index e03bcb7b8..000000000 --- a/nl/hardware/network-cards.xml +++ /dev/null @@ -1,184 +0,0 @@ - - - - - Network Connectivity Hardware - - -Almost any network interface card (NIC) supported by the &arch-kernel; kernel -should also be supported by the installation system; modular drivers -should normally be loaded automatically. - -This includes most PCI and PCMCIA cards. -Many older ISA cards are supported as well. - - - -This includes a lot of generic PCI cards (for systems that have PCI) and -the following NICs from Sun: - - - - -Sun LANCE - - - - -Sun Happy Meal - - - - -Sun BigMAC - - - - -Sun QuadEthernet - - - - -MyriCOM Gigabit Ethernet - - - - - - -The list of supported network devices is: - - - - -Channel to Channel (CTC) and ESCON connection (real or emulated) - - - - -OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO) - - - - -OSA-Express in QDIO mode, HiperSockets and Guest-LANs - - - - - - - - -On &arch-title;, most built-in Ethernet devices are supported and modules -for additional PCI and USB devices are provided. The major exception is -the IXP4xx platform (featuring devices such as the Linksys NSLU2) which -needs a proprietary microcode for the operation of its built-in Ethernet -device. Unofficial images for Linksys NSLU2 with this proprietary -microcode can be obtained from the Slug-Firmware site. - - - -ISDN is supported, but not during the installation. - - - - - Wireless Network Cards - - -Wireless networking is in general supported as well and a growing number of -wireless adapters are supported by the official &arch-kernel; kernel, although many -of them do require firmware to be loaded. If firmware is needed, the installer -will prompt you to load firmware. See -for detailed information on how to load firmware during the installation. - - - -Wireless NICs that are not supported by the official &arch-kernel; kernel can generally -be made to work under &debian-gnu;, but are not supported during the installation. - - - -Support for encrypted wireless during installation is currently limited to WEP. -If your access point uses stronger encryption, it cannot be used during the -installation process. - - - -If there is a problem with wireless and there -is no other NIC you can use during the installation, it is still -possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the -option to not configure a network and install using only the packages -available from the CD/DVD. You can then install the driver and firmware you -need after the installation is completed (after the reboot) and configure -your network manually. - - - -In some cases the driver you need may not be available as a &debian; package. -You will then have to look if there is source code available in the internet -and compile the driver yourself. How to do this is outside the scope of this -manual. -If no Linux driver is available, your last resort is to -use the ndiswrapper package, which allows you to use -a Windows driver. - - - - - - Known Issues for &arch-title; - - -There are a couple of issues with specific network cards that are worth -mentioning here. - - - - Conflict between tulip and dfme drivers - - - - -There are various PCI network cards that have the same PCI identification, -but are supported by related, but different drivers. Some cards work with -the tulip driver, others with the dfme -driver. Because they have the same identification, the kernel cannot -distinguish between them and it is not certain which driver will be loaded. -If this happens to be the wrong one, the NIC may not work, or work badly. - - - -This is a common problem on Netra systems with a Davicom (DEC-Tulip -compatible) NIC. In that case the tulip driver is -probably the correct one. -You can prevent this issue by blacklisting the wrong driver module as -described in . - - - -An alternative solution during the installation is to switch to a shell -and unload the wrong driver module using -modprobe -r module (or -both, if they are both loaded). After that you can load the correct module -using modprobe module. -Note that the wrong module may then still be loaded when the system is -rebooted. - - - - - Sun B100 blade - - - -The cassini network driver does not work with Sun B100 -blade systems. - - - - - diff --git a/nl/hardware/supported-peripherals.xml b/nl/hardware/supported-peripherals.xml deleted file mode 100644 index 799e12666..000000000 --- a/nl/hardware/supported-peripherals.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - - - Peripherals and Other Hardware - - -&arch-kernel; supports a large variety of hardware devices such as mice, -printers, scanners, PCMCIA and USB devices. However, most of these -devices are not required while installing the system. - - - -USB hardware generally works fine, only some -USB keyboards may require additional configuration -(see ). - - - -Again, see the -Linux Hardware Compatibility HOWTO -to determine whether your specific hardware is supported by Linux. - - - -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. - - - -The Cobalt RaQ has no support for additional devices but the Qube has one -PCI slot. - - - diff --git a/nl/hardware/supported/amd64.xml b/nl/hardware/supported/amd64.xml deleted file mode 100644 index 946ecaaeb..000000000 --- a/nl/hardware/supported/amd64.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -Complete information concerning supported peripherals can be found at -Linux Hardware Compatibility HOWTO. -This section merely outlines the basics. - - - - CPU - - -Both AMD64 and Intel EM64t processors are supported. - - - - - - - diff --git a/nl/hardware/supported/arm.xml b/nl/hardware/supported/arm.xml deleted file mode 100644 index eae55aa2d..000000000 --- a/nl/hardware/supported/arm.xml +++ /dev/null @@ -1,104 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - - -Each distinct ARM architecture requires its own kernel. Because of -this the standard &debian; distribution only supports installation on -a number of the most common platforms. The &debian; userland however may be -used by any ARM CPU. - - - - - -Most ARM CPUs may be run in either endian mode (big or little). However, -the majority of current system implementation uses little-endian mode. -&debian; currently only supports little-endian ARM systems. - - - - - -The supported platforms are: - - - - -IOP32x - - -Intel's I/O Processor (IOP) line is found in a number of products related -to data storage and processing. &debian; currently supports the IOP32x -platform, featuring the IOP 80219 and 32x chips commonly found in Network -Attached Storage (NAS) devices. &debian; explicitly supports two such -devices: the GLAN Tank from -IO-Data and the Thecus N2100. - - - - - -IXP4xx - - -The IXP4xx platform is based on Intel's XScale ARM core. Currently, only -one IXP4xx based system is supported, the Linksys NSLU2. -The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small -device which allows you to easily provide storage via the network. It -comes with an Ethernet connection and two USB ports to which hard drives -can be connected. There is an external site with installation instructions. - - - - - -Kirkwood - - -Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM -CPU, Ethernet, SATA, USB, and other functionality in one chip. We -currently support the following Kirkwood based devices: OpenRD (OpenRD-Base -and OpenRD-Client), SheevaPlug and QNAP Turbo Station (TS-110, -TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet -supported). - - - - - -Orion5x - - -Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, -Ethernet, SATA, USB, and other functionality in one chip. There are many -Network Attached Storage (NAS) devices on the market that are based on an -Orion chip. We currently support the following Orion based devices: Buffalo Kurobox, HP mv2120, QNAP Turbo Station (TS-109, TS-209 and -TS-409). - - - - - -Versatile - - -The Versatile platform is emulated by QEMU and is therefore a nice way to -test and run &debian; on ARM if you don't have the hardware. - - - - - - - - diff --git a/nl/hardware/supported/hppa.xml b/nl/hardware/supported/hppa.xml deleted file mode 100644 index 47578abcb..000000000 --- a/nl/hardware/supported/hppa.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -There are two major support &architecture; 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. - - - - diff --git a/nl/hardware/supported/i386.xml b/nl/hardware/supported/i386.xml deleted file mode 100644 index baa209b29..000000000 --- a/nl/hardware/supported/i386.xml +++ /dev/null @@ -1,76 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -Complete information concerning supported peripherals can be found at -Linux Hardware Compatibility HOWTO. -This section merely outlines the basics. - - - - CPU - - -Nearly all x86-based (IA-32) processors still in use in personal computers -are supported, including all varieties of Intel's "Pentium" series. -This also includes 32-bit AMD and VIA (former Cyrix) processors, and -processors like the Athlon XP and Intel P4 Xeon. - - - -However, &debian; GNU/Linux &releasename; will not run -on 386 or earlier processors. Despite the architecture name "i386", support -for actual 80386 processors (and their clones) was dropped with the Sarge -(r3.1) release of &debian; - - -We have long tried to avoid this, but in the end it was necessary due a -unfortunate series of issues with the compiler and the kernel, starting -with an bug in the C++ ABI provided by GCC. You should still be able to -run &debian; GNU/Linux on actual 80386 processors if you compile your own -kernel and compile all packages from source, but that is beyond the -scope of this manual. - - -. (No version of Linux has ever supported the 286 or earlier -chips in the series.) All i486 and later processors are still -supported - - - -Many &debian; packages will actually run slightly faster on modern computers -as a positive side effect of dropping support for these old chips. The -i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) -which the i386, introduced in 1986, did not have. Previously, these could not -be easily used by most &debian; packages; now they can. - - - -. - - - - -If your system has a 64-bit processor from the AMD64 or Intel EM64T families, -you will probably want to use the installer for the amd64 architecture instead -of the installer for the (32-bit) i386 architecture. - - - - - I/O Bus - - -The system bus is the part of the motherboard which allows the CPU to -communicate with peripherals such as storage devices. Your computer -must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL -bus). Essentially all personal computers sold in recent years use one -of these. - - - - - diff --git a/nl/hardware/supported/ia64.xml b/nl/hardware/supported/ia64.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/nl/hardware/supported/ia64.xml +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/nl/hardware/supported/mips.xml b/nl/hardware/supported/mips.xml deleted file mode 100644 index 91f95d973..000000000 --- a/nl/hardware/supported/mips.xml +++ /dev/null @@ -1,56 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -&debian; on &arch-title; supports the following platforms: - - - - -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. - - - - -SGI IP32: this platform is generally known as SGI O2. - - - - -MIPS Malta: this platform is emulated by QEMU and is therefore a nice way -to test and run &debian; on MIPS if you don't have the hardware. - - - - -Complete information regarding supported mips/mipsel machines can be found -at the Linux-MIPS homepage. 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 -debian-&arch-listname; mailing list. - - - - CPU - - -On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 -processors are supported by the &debian; installation system on big endian -MIPS. On SGI IP32, currently only systems based on the R5000 are supported. - - - -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. - - - - - diff --git a/nl/hardware/supported/mipsel.xml b/nl/hardware/supported/mipsel.xml deleted file mode 100644 index 4ba800a5c..000000000 --- a/nl/hardware/supported/mipsel.xml +++ /dev/null @@ -1,51 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -&debian; on &arch-title; supports the following platforms: - - - - -Cobalt Microserver: only MIPS based Cobalt machines are covered here. This -includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. - - - - -MIPS Malta: this platform is emulated by QEMU and is therefore a nice way -to test and run &debian; on MIPS if you don't have the hardware. - - - - -Complete information regarding supported mips/mipsel machines can be found -at the Linux-MIPS homepage. 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 -debian-&arch-listname; mailing list. - - - - CPU/Machine types - - - -All MIPS based Cobalt machines are supported with the exception of the -Qube 2700 (Qube 1). - - - - - Supported console options - - -Cobalt machines use 115200 bps. - - - - diff --git a/nl/hardware/supported/powerpc.xml b/nl/hardware/supported/powerpc.xml deleted file mode 100644 index bb146b54a..000000000 --- a/nl/hardware/supported/powerpc.xml +++ /dev/null @@ -1,428 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP -subarchitectures are supported. - - - - - - Kernel Flavours - - - -There are two flavours of the powerpc kernel in &debian;, based on the -CPU type: - - - -powerpc - - -Most systems use this kernel flavour, which supports the PowerPC 601, -603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines -up to and including the one marketed as G4 use one of these processors. - - - - - -power64 - - -The power64 kernel flavour supports the following CPUs: - - - -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. - - - -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. - - - -Systems using the Apple G5 (PPC970FX processor) are also based on the -POWER4 architecture, and use this kernel flavour. - - - - - - - - - - - - Power Macintosh (pmac) subarchitecture - - - -Apple (and briefly a few other manufacturers — Power Computing, for -example) made a series of Macintosh computers based on the PowerPC -processor. For purposes of architecture support, they are categorized -as NuBus (not supported by &debian;), OldWorld, and NewWorld. - - - -OldWorld systems are most Power Macintoshes with a floppy drive and a -PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are -OldWorld machines. Those pre-iMac PowerPC models from Apple use a -four digit naming scheme, except for the beige colored G3 systems, which -are also OldWorld. - - - -The so called NewWorld PowerMacs are any PowerMacs in translucent -colored plastic cases and later models. That includes all iMacs, iBooks, -G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and -after 1999. The NewWorld PowerMacs are also known for using the ROM in -RAM system for MacOS, and were manufactured from mid-1998 onwards. - - - -Specifications for Apple hardware are available at -AppleSpec, -and, for older hardware, -AppleSpec Legacy. - - - - - - - - - - - Model Name/Number - Generation - - - - - - Apple - iMac Bondi Blue, 5 Flavors, Slot Loading - NewWorld - - iMac Summer 2000, Early 2001 - NewWorld - - iMac G5 - NewWorld - - iBook, iBook SE, iBook Dual USB - NewWorld - - iBook2 - NewWorld - - iBook G4 - NewWorld - - Power Macintosh Blue and White (B&W) G3 - NewWorld - - Power Macintosh G4 PCI, AGP, Cube - NewWorld - - Power Macintosh G4 Gigabit Ethernet - NewWorld - - Power Macintosh G4 Digital Audio, Quicksilver - NewWorld - - Power Macintosh G5 - NewWorld - - PowerBook G3 FireWire Pismo (2000) - NewWorld - - PowerBook G3 Lombard (1999) - NewWorld - - PowerBook G4 Titanium - NewWorld - - PowerBook G4 Aluminum - NewWorld - - Xserve G5 - NewWorld - - Performa 4400, 54xx, 5500 - OldWorld - - Performa 6360, 6400, 6500 - OldWorld - - Power Macintosh 4400, 5400 - OldWorld - - Power Macintosh 7200, 7300, 7500, 7600 - OldWorld - - Power Macintosh 8200, 8500, 8600 - OldWorld - - Power Macintosh 9500, 9600 - OldWorld - - Power Macintosh (Beige) G3 Minitower - OldWorld - - Power Macintosh (Beige) Desktop, All-in-One - OldWorld - - PowerBook 2400, 3400, 3500 - OldWorld - - PowerBook G3 Wallstreet (1998) - OldWorld - - Twentieth Anniversary Macintosh - OldWorld - - Workgroup Server 7250, 7350, 8550, 9650, G3 - OldWorld - - - - Power Computing - PowerBase, PowerTower / Pro, PowerWave - OldWorld - - PowerCenter / Pro, PowerCurve - OldWorld - - - - UMAX - C500, C600, J700, S900 - OldWorld - - - - APS - APS Tech M*Power 604e/2000 - OldWorld - - - - Motorola - Starmax 3000, 4000, 5000, 5500 - OldWorld - - - - - - - - PReP subarchitecture - - - - - - - - - - Model Name/Number - - - - - - Motorola - Firepower, PowerStack Series E, PowerStack II - - MPC 7xx, 8xx - - MTX, MTX+ - - MVME2300(SC)/24xx/26xx/27xx/36xx/46xx - - MCP(N)750 - - - - IBM RS/6000 - 40P, 43P - - Power 830/850/860 (6070, 6050) - - 6030, 7025, 7043 - - p640 - - - - - - - - CHRP subarchitecture (unsupported) - - - - - - - - - - Model Name/Number - - - - - - IBM RS/6000 - B50, 43P-150, 44P - - - Genesi - Pegasos I, Pegasos II - - - - - - - - APUS subarchitecture (unsupported) - - - - - - - - - - Model Name/Number - - - - - - Amiga Power-UP Systems (APUS) - A1200, A3000, A4000 - - - - - - - - Nubus PowerMac subarchitecture (unsupported) - - - -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: - - - - -Power Macintosh 6100, 7100, 8100 - - - - -Performa 5200, 6200, 6300 - - - - -Powerbook 1400, 2300, and 5300 - - - - -Workgroup Server 6150, 8150, 9150 - - - - -A linux kernel for these machines and limited support is available at -. - - - - - - Non-PowerPC Macs - - - -Macintosh computers using the 680x0 series of processors are -not in the PowerPC family but are instead m68k -machines. Those models start with Mac II series, go on -to the LC family, then the Centris series, and culminate -in the Quadras and Performas. These models usually have a Roman numeral -or 3-digit model number such as Mac IIcx, LCIII or Quadra 950. - - - -This model range started with the Mac II (Mac II, IIx, IIcx, IIci, -IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, -550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, -660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, -950), and finally the Performa 200-640CD. - - - -In laptops, it started with the Mac Portable, then the PowerBook -100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 -which is Nubus, please see the section above). - - - - - diff --git a/nl/hardware/supported/s390.xml b/nl/hardware/supported/s390.xml deleted file mode 100644 index 237674566..000000000 --- a/nl/hardware/supported/s390.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - S/390 and zSeries machine types - - -Complete information regarding supported S/390 and zSeries machines can -be found in IBM's Redbook - -Linux for IBM eServer zSeries and S/390: Distributions in -chapter 2.1 or at the -zSeries -page at the developerWorks. -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. - - - - diff --git a/nl/hardware/supported/sparc.xml b/nl/hardware/supported/sparc.xml deleted file mode 100644 index 5d02c340b..000000000 --- a/nl/hardware/supported/sparc.xml +++ /dev/null @@ -1,70 +0,0 @@ - - - - - CPU and Main Boards Support - - -Sparc-based hardware is divided into a number of different subarchitectures, -identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u -or sun4v. The following list describes what machines they include and what -level of support may be expected for each of them. - - - - - -sun4, sun4c, sun4d, sun4m - - - -None of these 32-bit sparc subarchitectures (sparc32) is supported. For a -complete list of machines belonging to these subarchitectures, please consult -the Wikipedia -SPARCstation page. - - - -The last &debian; release to support sparc32 was Etch, but even then only -for sun4m systems. Support for the other 32-bits subarchitectures had -already been discontinued after earlier releases. - - - - - -sun4u - - - -This subarchitecture includes all 64-bit machines (sparc64) based on -the UltraSparc processor and its clones. Most of the machines are well -supported, even though for some you may experience problems booting from -CD due to firmware or bootloader bugs (this problem may be worked around -by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP -configurations respectively. - - - - - -sun4v - - - -This is the newest addition to the Sparc family, which includes machines -based on the Niagara multi-core CPUs. At the moment such CPUs are only -available in T1000 and T2000 servers by Sun, and are well supported. Use -the sparc64-smp kernel. - - - - - - - -Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not -supported due to lack of support in the Linux kernel. - - - diff --git a/nl/howto/installation-howto.xml b/nl/howto/installation-howto.xml deleted file mode 100644 index 9665efa82..000000000 --- a/nl/howto/installation-howto.xml +++ /dev/null @@ -1,357 +0,0 @@ - - - - -Installation Howto - - - -This document describes how to install &debian-gnu; &releasename; for -the &arch-title; (&architecture;) with the -new &d-i;. It is a quick walkthrough of the installation process -which should contain all the information you will need for most installs. -When more information can be useful, we will link to more detailed -explanations in other parts of this document. - - - - - Preliminaries - - - -The debian-installer is still in a beta state. - -If you encounter bugs during your install, please refer to - for instructions -on how to report them. If you have questions which cannot be -answered by this document, please direct them to the debian-boot -mailing list (&email-debian-boot-list;) or ask on IRC (#debian-boot -on the OFTC network). - - - - - - Booting the installer - - - -For some quick links to CD images, check out the -&d-i; home page. - -The debian-cd team provides builds of CD images using &d-i; on the -Debian CD page. -For more information on where to get CDs, see . - - - -Some installation methods require other images than CD images. - -The &d-i; home page has links to -other images. - - explains how to find images on &debian; -mirrors. - - - -The subsections below will give the details about which images you should -get for each possible means of installation. - - - - - CDROM - - - -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. - - - -Download whichever type you prefer and burn it to a CD. -To boot the CD, you may need to change your BIOS -configuration, as explained in . - -To boot a PowerMac from CD, press the c key while booting. See - for other ways to boot from CD. - - - - - - - Floppy - - -If you can't boot from CD, you can download floppy images to install -&debian;. You need the floppy/boot.img, the -floppy/root.img and one or more of the driver disks. - - - -The boot floppy is the one with boot.img on it. -This floppy, when booted, will prompt you to insert a second floppy — -use the one with root.img on it. - - - -If you're planning to install over the network, you will usually need -the floppy/net-drivers-1.img. For PCMCIA or USB -networking, and some less common network cards, you will also need a second -driver floppy, floppy/net-drivers-2.img. - - - -If you have a CD, but cannot boot from it, then boot from floppies and use -floppy/cd-drivers.img on a driver disk to complete the -install using the CD. - - - -Floppy disks are one of the least reliable media around, so be prepared for -lots of bad disks (see ). Each -.img 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 for details). -Since you'll have more than one floppy, it's a good idea to label them. - - - - - - USB memory stick - - -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. - - - -The easiest way to prepare your USB memory stick is to download -hd-media/boot.img.gz, and use gunzip to extract the 256 MB -image from that file. Write this image directly to your memory stick, which -must be at least 256 mb in size. Of course this will destroy anything already -on the memory stick. Then mount the memory stick, which will now have a FAT -filesystem on it. Next, download a &debian; netinst CD image, and copy that file -to the memory stick; any filename is ok as long as it ends in -.iso. - - - -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 . - - - -Some BIOSes can boot USB storage directly, and some cannot. You may need to -configure your BIOS to boot from a removable drive or even a -USB-ZIP to get it to boot from the USB device. For helpful -hints and details, see . - - - -Booting Macintosh systems from USB storage devices involves manual use -of Open Firmware. For directions, see . - - - - - - Booting from network - - -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 netboot/ can be used to netboot &d-i;. - - - -The easiest thing to set up is probably PXE netbooting. Untar the -file netboot/pxeboot.tar.gz into -/srv/tftp or -wherever is appropriate for your tftp server. Set up your DHCP server to pass -filename pxelinux.0 to clients, and with luck -everything will just work. -For detailed instructions, see . - - - - - - Booting from hard disk - - -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 -hd-media/initrd.gz, hd-media/vmlinuz, -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 .iso. Now -it's just a matter of booting linux with the initrd. - - explains one way to do it. - - - - - - - -Installation - - -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 ). - - - -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. - - - -You may be asked to confirm your keyboard layout. Choose the default unless -you know better. - - - -Now sit back while debian-installer detects some of your hardware, and -loads the rest of itself from CD, floppy, USB, etc. - - - -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. - - - -The next step is setting up your clock and time zone. The installer will -try to contact a time server on the Internet to ensure the clock is set -correctly. The time zone is based on the country selected earlier and the -installer will only ask to select one if a country has multiple zones. - - - -Now it is time to partition your disks. First you will be given the -opportunity to automatically partition either an entire drive, or available -free space on a drive (see ). -This is recommended for new users or anyone in a hurry. If you do not want -to autopartition, choose Manual from the menu. - - - -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. - - - -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 -Finish partitioning and write changes to disk -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 /. -For more detailed information on how to use the partitioner, please refer -to ; the appendix has more general information about -partitioning. - - - -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. - - - -The base system that was installed earlier is a working, but very minimal -installation. To make the system more functional the next step allows you -to install additional packages by selecting tasks. Before packages can be -installed apt needs to be configured as that defines -from where the packages will be retrieved. -The Standard system task will be selected by default and -should normally be installed. Select the Desktop environment -task if you would like to have a graphical desktop after the installation. -See for additional information about this step. - - - -Installation of the base system is followed by setting up user accounts. By -default you will need to provide a password for the root -(administrator) account and information necessary to create one regular user -account. - - - -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. -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. - - - - -&d-i; will now tell you that the installation has -finished. Remove the cdrom or other boot media and hit &enterkey; to reboot -your machine. It should boot up into the newly installed system and -allow you to log in. This is explained in . - - - -If you need more information on the install process, see -. - - - - - - Send us an installation report - - -If you successfully managed an installation with &d-i;, -please take time to provide us with a report. -The simplest way to do so is to install the reportbug package -(aptitude install reportbug), configure -reportbug as explained in -, and run -reportbug installation-reports. - - - -If you did not complete the install, you probably found a bug in -debian-installer. To improve the installer it is necessary that we know -about them, so please take the time to report them. You can use an -installation report to report problems; if the install completely fails, -see . - - - - - - And finally… - - -We hope that your &debian; installation is pleasant and that you find &debian; -useful. You might want to read . - - - - diff --git a/nl/install-methods/automatic-install.xml b/nl/install-methods/automatic-install.xml deleted file mode 100644 index 6aaddea31..000000000 --- a/nl/install-methods/automatic-install.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - - Automatic Installation - - -For installing on multiple computers it's possible to do fully -automatic installations. &debian; packages intended for this include -fai (which uses an install server), -replicator, -systemimager, -autoinstall, and -the &debian; Installer itself. - - - - - Automatic Installation Using the &debian; Installer - - -The &debian; Installer supports automating installs via preconfiguration -files. A preconfiguration file can be loaded from the network or from -removable media, and used to fill in answers to questions asked during the -installation process. - - - -Full documentation on preseeding including a working example that you can -edit is in . - - - - diff --git a/nl/install-methods/boot-drive-files.xml b/nl/install-methods/boot-drive-files.xml deleted file mode 100644 index 22205ddd1..000000000 --- a/nl/install-methods/boot-drive-files.xml +++ /dev/null @@ -1,176 +0,0 @@ - - - - - Preparing Files for Hard Disk Booting - - -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. - - - -A full, pure network 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. - - - -The installer cannot boot from files on an NTFS file system. - - - -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 Get Info for the volume in question. HFS -file systems appear as Mac OS Standard, while -HFS+ file systems say Mac OS Extended. You must -have an HFS partition in order to exchange files between MacOS and -Linux, in particular the installation files you download. - - - -Different programs are used for hard disk installation system booting, -depending on whether the system is a NewWorld or an -OldWorld model. - - - - - Hard disk installer booting using <command>LILO</command> or - <command>GRUB</command> - - -This section explains how to add to or even replace an existing linux -installation using either LILO or -GRUB. - - - -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. - - - -Copy the following files from the &debian; archives to a -convenient location on your hard drive, for instance to -/boot/newinstall/. - - - - -vmlinuz (kernel binary) - - - - -initrd.gz (ramdisk image) - - - - - - -Finally, to configure the bootloader proceed to -. - - - - - - - Hard Disk Installer Booting for OldWorld Macs - - -The boot-floppy-hfs floppy uses -miBoot to launch Linux installation, but -miBoot cannot easily be used for hard disk -booting. BootX, launched from MacOS, -supports booting from files placed on the hard -disk. BootX can also be used to dual-boot -MacOS and Linux after your &debian; installation is complete. For the -Performa 6360, it appears that quik cannot make the -hard disk bootable. So BootX is required -on that model. - - - -Download and unstuff the BootX -distribution, available from , -or in the -dists/woody/main/disks-powerpc/current/powermac -directory on &debian; http/ftp mirrors and official &debian; CDs. Use -Stuffit Expander to extract it from its -archive. Within the package, there is an empty folder called -Linux Kernels. Download -linux.bin and -ramdisk.image.gz from the -disks-powerpc/current/powermac folder, and place -them in the Linux Kernels folder. Then place the -Linux Kernels folder in the active System Folder. - - - - - - Hard Disk Installer Booting for NewWorld Macs - - -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 -yaboot, 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. BootX is -not supported and must not be used on NewWorld PowerMacs. - - - -Copy (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 -option-dragging each file to the hard drive icon). - - - - -vmlinux - - - - -initrd.gz - - - - -yaboot - - - - -yaboot.conf - - - - - - -Make a note of the partition number of the MacOS partition where you -place these files. If you have the MacOS pdisk -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. - - - -To boot the installer, proceed to . - - - - diff --git a/nl/install-methods/boot-usb-files.xml b/nl/install-methods/boot-usb-files.xml deleted file mode 100644 index afffe991d..000000000 --- a/nl/install-methods/boot-usb-files.xml +++ /dev/null @@ -1,159 +0,0 @@ - - - - - Preparing Files for USB Memory Stick Booting - - - -There are two installation methods possible when booting from USB stick. -The first is to install completely from the network. The second is to -also copy a CD image onto the USB stick and use that as a source for -packages, possibly in combination with a mirror. This second method is -the more common. - - - -For the first installation method you'll need to download an installer -image from the netboot directory (at the location -mentioned in ) and use the -flexible way explained below to copy the files to the USB -stick. - - - -Installation images for the second installation method can be found in -the hd-media directory and either the easy -way or the flexible way can be used to copy the -image to the USB stick. For this installation method you will also need -to download a CD image. The installation image and the CD image must be -based on the same release of &d-i;. If they do not match you are likely -to get errors - - -The error message that is most likely to be displayed is that no kernel -modules can be found. This means that the version of the kernel module -udebs included on the CD image is different from the version of the -running kernel. - - - during the installation. - - - -To prepare the USB stick, you will need a system where GNU/Linux is -already running and where USB is supported. With current GNU/Linux systems -the USB stick should be automatically recognized when you insert it. If -it is not you should check that the usb-storage kernel module is loaded. -When the USB stick is inserted, it will be mapped to a device named -/dev/sdX, where the X is a letter -in the range a-z. You should be able to see to which device the USB -stick was mapped by running the command dmesg after -inserting it. To write to your stick, you may have to turn off its write -protection switch. - - - - -The procedures described in this section will destroy anything already -on the device! Make very sure that you use the correct device name for -your USB stick. If you use the wrong device the result could be that all -information on for example a hard disk could be lost. - - - - -Note that the USB stick should be at least 256 MB in size (smaller -setups are possible if you follow ). - - - - - Copying the files — the easy way - - -There is an all-in-one file hd-media/boot.img.gz -which contains all the installer files (including the kernel) -as well as syslinux and its -configuration file. -as well as yaboot and its -configuration file. - - - -Note that, although convenient, this method does have one major -disadvantage: the logical size of the device will be limited to 256 MB, -even if the capacity of the USB stick is larger. You will need to -repartition the USB stick and create new file systems to get its full -capacity back if you ever want to use it for some different purpose. -A second disadvantage is that you cannot copy a full CD image onto -the USB stick, but only the smaller businesscard or netinst CD images. - - - -To use this image simply extract it directly to your USB stick: - - -# zcat boot.img.gz > /dev/sdX - - - - -Create a partition of type "Apple_Bootstrap" on your USB stick using -mac-fdisk's C command and -extract the image directly to that: - - -# zcat boot.img.gz > /dev/sdX2 - - - - -After that, mount the USB memory stick -(mount -/dev/sdX /mnt), -(mount -/dev/sdX2 /mnt), -which will now have -a FAT filesystem -an HFS filesystem -on it, and copy a &debian; netinst or businesscard ISO image to it. -Unmount the stick (umount /mnt) and you are done. - - - - - - Copying the files — the flexible way - - -If you like more flexibility or just want to know what's going on, you -should use the following method to put the files on your stick. One -advantage of using this method is that — if the capacity of your -USB stick is large enough — you have the option of copying a -full CD ISO image to it. - - - -&usb-setup-x86.xml; -&usb-setup-powerpc.xml; - - - - - - Booting the USB stick - - -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 -install-mbr command from the package -mbr: - - -# install-mbr /dev/sdX - - - - - diff --git a/nl/install-methods/create-floppy.xml b/nl/install-methods/create-floppy.xml deleted file mode 100644 index 6722dcde4..000000000 --- a/nl/install-methods/create-floppy.xml +++ /dev/null @@ -1,108 +0,0 @@ - - - - - Creating Floppies from Disk Images - - -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. - - - -Booting the installer from floppy disk reportedly fails on Mac USB -floppy drives. - - - -Disk images are files containing the complete contents of a floppy -disk in raw form. Disk images, such as -boot.img, cannot simply be copied to floppy -drives. A special program is used to write the image files to floppy -disk in raw mode. This is required because these -images are raw representations of the disk; it is required to do a -sector copy of the data from the file onto the -floppy. - - - -There are different techniques for creating floppies from disk images. -This section describes how to create floppies from disk images on -different platforms. - - - -Before you can create the floppies, you will first need to download them -from one of the &debian; mirrors, as explained in -. If you already -have an installation CD-ROM or DVD, the floppy images may also be included -on the CD/DVD. - - - -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. - - - - Writing Disk Images From a Linux or Unix System - - -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 - - -$ dd if=filename of=/dev/fd0 bs=1024 conv=sync ; sync - - -where filename is one of the floppy disk image -files. -/dev/fd0 is a commonly used name of the floppy -disk device, it may be different on your workstation -(on Solaris, it is /dev/fd/0). -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 (on Solaris, use -eject, see the manual page). - - - -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 raw -mode. Unfortunately, how to accomplish this will vary -based on your operating system. - -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 volcheck or -the equivalent command in the file manager). Then use a -dd command of the form given above, just replace -/dev/fd0 with -/vol/rdsk/floppy_name, -where floppy_name is the name the floppy -disk was given when it was formatted (unnamed floppies default to the -name unnamed_floppy). On other systems, ask your -system administrator. - - - - -If writing a floppy on powerpc Linux, you will need to eject it. The -eject program handles this nicely; you might need -to install it. - - - - - -&floppy-i386.xml; -&floppy-powerpc.xml; - - - diff --git a/nl/install-methods/download/arm.xml b/nl/install-methods/download/arm.xml deleted file mode 100644 index d4f3650a3..000000000 --- a/nl/install-methods/download/arm.xml +++ /dev/null @@ -1,88 +0,0 @@ - - - - - - NSLU2 Installation Files - - -A firmware image is provided for the Linksys NSLU2 which will automatically -boot debian-installer. This image can be uploaded -via the Linksys web frontend or with upslug2. This firmware image can be -obtained from &nslu2-firmware-img;. - - - - - - - Thecus N2100 Installation Files - - -A firmware image is provided for the Thecus N2100 which will automatically -boot debian-installer. This image can be installed -using the Thecus firmware upgrade process. This firmware image can be -obtained from &n2100-firmware-img;. - - - - - - GLAN Tank Installation Files - - -The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the -disk on which you intend to install &debian;. These images can be obtained -from &glantank-firmware-img;. - - - - - - Kurobox Pro Installation Files - - -The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the -disk on which you intend to install &debian;. These images can be obtained -from &kuroboxpro-firmware-img;. - - - - - - HP mv2120 Installation Files - - -A firmware image is provided for the HP mv2120 which will automatically -boot debian-installer. This image can be installed -with uphpmvault on Linux and other systems and with the HP Media -Vault Firmware Recovery Utility on Windows. The firmware image can be -obtained from &mv2120-firmware-img;. - - - - - - QNAP Turbo Station Installation Files - - -The installation files for the QNAP Turbo Station consist of a kernel and -ramdisk as well as a script to write these images to flash. You can obtain -the installation files for QNAP TS-109 and TS-209 from -&qnap-orion-firmware-img; and for QNAP TS-110, TS-119, TS-210, TS-219, -TS-219P from &qnap-kirkwood-firmware-img;. - - - - - - SheevaPlug and OpenRD Installation Files - - -The installation files for the Marvell SheevaPlug and OpenRD devices -consist of a kernel and initrd for U-Boot. You can obtain these files -from &kirkwood-marvell-firmware-img;. - - - - diff --git a/nl/install-methods/download/powerpc.xml b/nl/install-methods/download/powerpc.xml deleted file mode 100644 index d1dd228f9..000000000 --- a/nl/install-methods/download/powerpc.xml +++ /dev/null @@ -1,28 +0,0 @@ - - - - diff --git a/nl/install-methods/downloading-files.xml b/nl/install-methods/downloading-files.xml deleted file mode 100644 index e799e7354..000000000 --- a/nl/install-methods/downloading-files.xml +++ /dev/null @@ -1,34 +0,0 @@ - - - - - Downloading Files from &debian; Mirrors - - - -To find the nearest (and thus probably the fastest) mirror, see the -list of Debian mirrors. - - - -When downloading files from a &debian; mirror using FTP, be sure to download the -files in binary mode, not text or automatic mode. - - - - - Where to Find Installation Images - - -The installation images are located on each &debian; mirror in the directory -debian/dists/&releasename;/main/installer-&architecture;/current/images/ -— the MANIFEST -lists each image and its purpose. - - -&download-arm.xml; -&download-powerpc.xml; - - - - diff --git a/nl/install-methods/floppy/i386.xml b/nl/install-methods/floppy/i386.xml deleted file mode 100644 index dba3753e2..000000000 --- a/nl/install-methods/floppy/i386.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - - - Writing Disk Images From DOS, Windows, or OS/2 - - - -If you have access to an i386 or amd64 machine, you can use one of the -following programs to copy images to floppies. - - - -The rawrite1 and rawrite2 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 -not expected to work. - - - -The rwwrtwin 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. - - - -These tools can be found on the Official &debian; CD-ROMs under the -/tools directory. - - - diff --git a/nl/install-methods/floppy/powerpc.xml b/nl/install-methods/floppy/powerpc.xml deleted file mode 100644 index ffaa8ab70..000000000 --- a/nl/install-methods/floppy/powerpc.xml +++ /dev/null @@ -1,122 +0,0 @@ - - - - - Writing Disk Images From MacOS - - -An AppleScript, Make Debian Floppy, is -available for burning floppies from the provided disk image files. It -can be downloaded from -. 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. - - - -You can also use the MacOS utility Disk Copy -directly, or the freeware utility suntar. The -root.bin 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. - - - - - Writing Disk Images with <command>Disk Copy</command> - - -If you are creating the floppy image from files which were originally -on the official &debian-gnu; CD, then the Type and Creator are already set -correctly. The following Creator-Changer steps are -only necessary if you downloaded the image files from a &debian; mirror. - - - - - -Obtain -Creator-Changer -and use it to open the root.bin file. - - - - -Change the Creator to ddsk (Disk Copy), and the -Type to DDim (binary floppy image). The case is -sensitive for these fields. - - - - -Important: In the Finder, use Get -Info to display the Finder information about the floppy -image, and X the File Locked check box so -that MacOS will be unable to remove the boot blocks if the image is -accidentally mounted. - - - - -Obtain Disk Copy; if you have a MacOS system or CD it -will very likely be there already, otherwise try -. - - - - -Run Disk Copy, and select -Utilities Make a Floppy -, then select the -locked 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. - - - - - - - - Writing Disk Images with <command>suntar</command> - - - - - -Obtain suntar from -. Start the suntar program and select -Overwrite Sectors... from the Special -menu. - - - - -Insert the floppy disk as requested, then hit &enterkey; (start at -sector 0). - - - - -Select the root.bin file in the file-opening dialog. - - - - -After the floppy has been created successfully, select -File Eject . -If there are any errors writing the floppy, simply toss that floppy and -try another. - - - - -Before using the floppy you created, set the write protect -tab! Otherwise if you accidentally mount it in MacOS, -MacOS will helpfully ruin it. - - - - diff --git a/nl/install-methods/install-methods.xml b/nl/install-methods/install-methods.xml deleted file mode 100644 index 0956b911b..000000000 --- a/nl/install-methods/install-methods.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - Obtaining System Installation Media - -&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; - - diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml deleted file mode 100644 index 6c54a89c4..000000000 --- a/nl/install-methods/install-tftp.xml +++ /dev/null @@ -1,341 +0,0 @@ - - - - - Preparing Files for TFTP Net Booting - - -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. - - - -You need to set up a TFTP server, and for many machines a DHCP -server, or RARP -server, or BOOTP -server. - - - -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. - -BOOTP is an IP protocol that -informs a computer of its IP address and where on the network to obtain -a boot image. - -The DHCP (Dynamic Host Configuration Protocol) is a more flexible, -backwards-compatible extension of BOOTP. -Some systems can only be configured via DHCP. - - - -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. - - - -Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. -There is an rbootd package available in &debian;. - - - -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. - - - -For a &debian-gnu; server we recommend tftpd-hpa. -It's written by the same author as the syslinux -bootloader and is therefore least likely to cause issues. -A good alternative is atftpd. - - - - - -&tftp-rarp.xml; -&tftp-dhcp.xml; -&tftp-bootp.xml; - - - Enabling the TFTP Server - - -To get the TFTP server ready to go, you should first make sure that -tftpd is enabled. - - - -In the case of tftpd-hpa there are two ways the -service can be run. It can be started on demand by the system's -inetd daemon, or it can be set up to run as an -independent daemon. Which of these methods is used is selected when the -package is installed and can be changed by reconfiguring the package. - - - - -Historically, TFTP servers used /tftpboot as directory -to serve images from. However, &debian-gnu; packages may use other directories -to comply with the Filesystem Hierarchy -Standard. For example, tftpd-hpa by default -uses /srv/tftp. You may have to adjust the -configuration examples in this section accordingly. - - - - -All in.tftpd alternatives available in &debian; should -log TFTP requests to the system logs by default. Some of them support a --v argument to increase verbosity. -It is recommended to check these log messages in case of boot problems -as they are a good starting point for diagnosing the cause of errors. - - - -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: - - -# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc - - -to turn off Path MTU discovery, otherwise the SGI's PROM can't -download the kernel. Furthermore, make sure TFTP packets are sent from -a source port no greater than 32767, or the download will stall after -the first packet. Again, it's Linux 2.4.X tripping this bug in the -PROM, and you can avoid it by setting - - -# echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range - - -to adjust the range of source ports the Linux TFTP server uses. - - - - - - Move TFTP Images Into Place - - -Next, place the TFTP boot image you need, as found in -, in the tftpd -boot image directory. You may have to make a link from that -file to the file which tftpd will use for booting a -particular client. Unfortunately, the file name is determined by the -TFTP client, and there are no strong standards. - - - -On NewWorld Power Macintosh machines, you will need to set up the -yaboot boot loader as the TFTP boot image. -Yaboot will then retrieve the kernel and RAMdisk -images via TFTP itself. You will need to download the following files -from the netboot/ directory: - - - - -vmlinux - - - - -initrd.gz - - - - -yaboot - - - - -yaboot.conf - - - - -boot.msg - - - - - - -For PXE booting, everything you should need is set up in the -netboot/netboot.tar.gz tarball. Simply extract this -tarball into the tftpd boot image directory. Make sure -your dhcp server is configured to pass pxelinux.0 -to tftpd as the filename to boot. - - - -For PXE booting, everything you should need is set up in the -netboot/netboot.tar.gz tarball. Simply extract this -tarball into the tftpd boot image directory. Make sure -your dhcp server is configured to pass -/debian-installer/ia64/elilo.efi -to tftpd as the filename to boot. - - - - - SPARC TFTP Booting - - -Some SPARC architectures add the subarchitecture names, such as -SUN4M or SUN4C, to the filename. Thus, -if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, -the filename would be C0A80103.SUN4C. However, -there are also subarchitectures where the file the client looks for is -just client-ip-in-hex. An easy way to determine the -hexadecimal code for the IP address is to enter the following command -in a shell (assuming the machine's intended IP is 10.0.0.4). - - -$ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 - - -To get to the correct filename, you will need to change all letters to -uppercase and if necessary append the subarchitecture name. - - - -If you've done all this correctly, giving the command boot -net from the OpenPROM should load the image. If the image -cannot be found, try checking the logs on your tftp server to see which -image name is being requested. - - - -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 -boot net my-sparc.image. This must still reside -in the directory that the TFTP server looks in. - - - - - - SGI TFTP Booting - - -On SGI machines you can rely on the bootpd to supply -the name of the TFTP file. It is given either as the -bf= in /etc/bootptab or as -the filename= option in -/etc/dhcpd.conf. - - - - - - - - diff --git a/nl/install-methods/ipl-tape.xml b/nl/install-methods/ipl-tape.xml deleted file mode 100644 index c99ac8b98..000000000 --- a/nl/install-methods/ipl-tape.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - - - Creating an IPL tape - - - -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 - -Linux for IBM eServer zSeries and S/390: Distributions -Redbook. The files you -need to write to the tape are (in this order): -kernel.debian, -parmfile.debian and -initrd.debian. The files can be downloaded -from the tape sub-directory, see -. - - - - diff --git a/nl/install-methods/official-cdrom.xml b/nl/install-methods/official-cdrom.xml deleted file mode 100644 index 0965582c3..000000000 --- a/nl/install-methods/official-cdrom.xml +++ /dev/null @@ -1,69 +0,0 @@ - - - - - Official &debian-gnu; CD-ROM Sets - - -By far the easiest way to install &debian-gnu; is from an Official -&debian; CD-ROM Set. You can buy a set from a vendor (see the -CD vendors page). -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 Debian CD page for -detailed instructions). If you have a &debian; CD set and CDs are -bootable on your machine, you can skip right to -; 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. - - - -If your machine doesn't support CD booting, but you do have a CD set, -you can use an alternative strategy such as - -floppy disk, - -tape, emulated tape, - -hard disk, - -usb stick, - -net boot, - -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. - - - -Once the installer is booted, it will be able to obtain all the other -files it needs from the CD. - - - -If you don't have a CD set, then you will need to download the -installer system files and place them on the - -installation tape - -floppy disk or - -hard disk or - -usb stick or - -a connected computer - -so they can be used to boot the installer. - - - - diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml deleted file mode 100644 index 86be45104..000000000 --- a/nl/install-methods/tftp/bootp.xml +++ /dev/null @@ -1,73 +0,0 @@ - - - - - - Setting up a BOOTP server - - -There are two BOOTP servers available for GNU/Linux. The first is CMU -bootpd. The other is actually a DHCP server: ISC -dhcpd. In &debian-gnu; these are contained in the -bootp and dhcp3-server -packages respectively. - - - -To use CMU bootpd, you must first uncomment (or -add) the relevant line in /etc/inetd.conf. On -&debian-gnu;, you can run update-inetd --enable -bootps, then /etc/init.d/inetd -reload to do so. Just in case your BOOTP server does not -run &debian;, the line in question should look like: - - -bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120 - - -Now, you must create an /etc/bootptab file. This -has the same sort of familiar and cryptic format as the good old BSD -printcap, termcap, and -disktab files. See the -bootptab manual page for more information. For -CMU bootpd, you will need to know the hardware -(MAC) address of the client. Here is an example -/etc/bootptab: - - -client:\ - hd=/tftpboot:\ - bf=tftpboot.img:\ - ip=192.168.1.90:\ - sm=255.255.255.0:\ - sa=192.168.1.1:\ - ha=0123456789AB: - - -You will need to change at least the ha option, which -specifies the hardware address of the client. The bf -option specifies the file a client should retrieve via TFTP; see - for more details. - - -On SGI machines you can just enter the command monitor and type -printenv. The value of the -eaddr variable is the machine's MAC address. - - - - -By contrast, setting up BOOTP with ISC dhcpd 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 . Otherwise you -will probably be able to get away with simply adding the -allow bootp directive to the configuration -block for the subnet containing the client in -/etc/dhcp3/dhcpd.conf, and restart -dhcpd with /etc/init.d/dhcp3-server -restart. - - - diff --git a/nl/install-methods/tftp/dhcp.xml b/nl/install-methods/tftp/dhcp.xml deleted file mode 100644 index 6f1a89b81..000000000 --- a/nl/install-methods/tftp/dhcp.xml +++ /dev/null @@ -1,94 +0,0 @@ - - - - - Setting up a DHCP server - - -One free software DHCP server is ISC dhcpd. -For &debian-gnu;, the dhcp3-server package is -recommended. Here is a sample configuration file for it (see -/etc/dhcp3/dhcpd.conf): - - -option domain-name "example.com"; -option domain-name-servers ns1.example.com; -option subnet-mask 255.255.255.0; -default-lease-time 600; -max-lease-time 7200; -server-name "servername"; - -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option routers 192.168.1.1; -} - -host clientname { - filename "/tftpboot.img"; - server-name "servername"; - next-server servername; - hardware ethernet 01:23:45:67:89:AB; - fixed-address 192.168.1.90; -} - - - - -In this example, there is one server -servername 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 -filename option should be the name of the -file which will be retrieved via TFTP. - - - -After you have edited the dhcpd configuration file, -restart it with /etc/init.d/dhcp3-server restart. - - - - - Enabling PXE Booting in the DHCP configuration - -Here is another example for a dhcp.conf using the -Pre-boot Execution Environment (PXE) method of TFTP. - - -option domain-name "example.com"; - -default-lease-time 600; -max-lease-time 7200; - -allow booting; -allow bootp; - -# The next paragraph needs to be modified to fit your case -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option broadcast-address 192.168.1.255; -# the gateway address which can be different -# (access to the internet for instance) - option routers 192.168.1.1; -# indicate the dns you want to use - option domain-name-servers 192.168.1.3; -} - -group { - next-server 192.168.1.3; - host tftpclient { -# tftp client hardware address - hardware ethernet 00:10:DC:27:6C:15; - filename "pxelinux.0"; - } -} - - -Note that for PXE booting, the client filename pxelinux.0 -is a boot loader, not a kernel image (see -below). - - - - diff --git a/nl/install-methods/tftp/rarp.xml b/nl/install-methods/tftp/rarp.xml deleted file mode 100644 index 47715f8db..000000000 --- a/nl/install-methods/tftp/rarp.xml +++ /dev/null @@ -1,32 +0,0 @@ - - - - - Setting up RARP server - - -To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) -of the client computers to be installed. -If you don't know this information, you can - - pick it off the initial OpenPROM boot messages, use the -OpenBoot .enet-addr command, or - -boot into Rescue mode (e.g., from the rescue floppy) and use the -command ip addr show dev eth0. - - - -On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, -you use the rarpd program. -You need to ensure that the Ethernet hardware address for the client is -listed in the ethers database (either in the -/etc/ethers file, or via NIS/NIS+) and in the -hosts database. Then you need to start the RARP daemon. -Issue the command (as root): /usr/sbin/rarpd -a -on most Linux systems and SunOS 5 (Solaris 2), -/usr/sbin/in.rarpd -a on some other Linux systems, -or /usr/etc/rarpd -a in SunOS 4 (Solaris 1). - - - diff --git a/nl/install-methods/usb-setup/powerpc.xml b/nl/install-methods/usb-setup/powerpc.xml deleted file mode 100644 index 6eba27fb6..000000000 --- a/nl/install-methods/usb-setup/powerpc.xml +++ /dev/null @@ -1,119 +0,0 @@ - - - - - Partitioning the USB stick - - -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 -mac-fdisk /dev/sdX, -initialise a new partition map using the i -command, and create a new partition of type Apple_Bootstrap using the -C command. (Note that the first "partition" will -always be the partition map itself.) Then type - - -$ hformat /dev/sdX2 - - -Take care that you use the correct device name for your USB stick. The -hformat command is contained in the -hfsutils &debian; package. - - - -In order to start the kernel after booting from the USB stick, we will -put a boot loader on the stick. The yaboot 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. - - - -The normal ybin tool that comes with -yaboot does not yet understand USB storage devices, -so you will have to install yaboot by hand using the -hfsutils tools. Type - - -$ hmount /dev/sdX2 -$ hcopy -r /usr/lib/yaboot/yaboot : -$ hattrib -c UNIX -t tbxi :yaboot -$ hattrib -b : -$ humount - - -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. - - - - - - Adding the installer image - - -Mount the partition -(mount /dev/sdX2 /mnt) -and copy the following installer image files to the stick: - - - - -vmlinux (kernel binary) - - - - -initrd.gz (initial ramdisk image) - - - - -yaboot.conf (yaboot configuration file) - - - - -boot.msg (optional boot message) - - - - - - -The yaboot.conf configuration file should -contain the following lines: - - -default=install -root=/dev/ram - -message=/boot.msg - -image=/vmlinux - label=install - initrd=/initrd.gz - initrd-size=10000 - read-only - - -Please note that the initrd-size parameter -may need to be increased, depending on the image you are booting. - - - -If you used an hd-media image, you should now copy a -&debian; ISO image (businesscard, netinst or full CD image; be sure to select -one that fits) onto the stick. When you are done, unmount the USB memory -stick (umount /mnt). - - - diff --git a/nl/install-methods/usb-setup/x86.xml b/nl/install-methods/usb-setup/x86.xml deleted file mode 100644 index 36a96af21..000000000 --- a/nl/install-methods/usb-setup/x86.xml +++ /dev/null @@ -1,117 +0,0 @@ - - - - - Partitioning the USB stick - - -We will show how to set up the memory stick to use the first partition, -instead of the entire device. - - - -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 cfdisk -or any other partitioning tool to create a FAT16 partition - - -Don't forget to set the bootable bootable flag. - - -, and then create the filesystem using: - - -# mkdosfs /dev/sdX1 - - -Take care that you use the correct device name for your USB stick. The -mkdosfs command is contained in the -dosfstools &debian; package. - - - -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. lilo) should work, it's convenient to use -syslinux, 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. - - - -To put syslinux on the FAT16 partition on your USB -stick, install the syslinux and -mtools packages on your system, and do: - - -# syslinux /dev/sdX1 - - -Again, take care that you use the correct device name. The partition -must not be mounted when starting syslinux. This -procedure writes a boot sector to the partition and creates the file -ldlinux.sys which contains the boot loader code. - - - - - - Adding the installer image - - -Mount the partition -(mount /dev/sdX1 /mnt) -and copy the following installer image files to the stick: - - - - -vmlinuz or linux (kernel binary) - - - - -initrd.gz (initial ramdisk image) - - - - -You can choose between either the regular version or the graphical version -of the installer. The latter can be found in the gtk -subdirectory. If you want to rename the files, please note that -syslinux can only process DOS (8.3) file names. - - - -Next you should create a syslinux.cfg configuration -file, which at a bare minimum should contain the following two lines (change -the name of the kernel binary to linux -if you used a netboot image): - - -default vmlinuz -append initrd=initrd.gz - - -For the graphical installer you should add -vga=788 to the second line. - - - -If you used an hd-media image, you should now copy a -&debian; ISO image - - -You can use either a businesscard, a netinst or a full CD image (see -). Be sure to select one that fits. -Note that the netboot mini.iso image is -not usable for this purpose. - - - onto the stick. When you are done, unmount the USB memory stick -(umount /mnt). - - - diff --git a/nl/partitioning/device-names.xml b/nl/partitioning/device-names.xml deleted file mode 100644 index eb52b09ef..000000000 --- a/nl/partitioning/device-names.xml +++ /dev/null @@ -1,131 +0,0 @@ - - - - - - Device Names in Linux - - -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: - - - - - -The first floppy drive is named /dev/fd0. - - - - -The second floppy drive is named /dev/fd1. - - - - -The first SCSI disk (SCSI ID address-wise) is named -/dev/sda. - - - - -The second SCSI disk (address-wise) is named -/dev/sdb, and so on. - - - - -The first SCSI CD-ROM is named /dev/scd0, also -known as /dev/sr0. - - - - -The master disk on IDE primary controller is named -/dev/hda. - - - - -The slave disk on IDE primary controller is named -/dev/hdb. - - - - -The master and slave disks of the secondary controller can be called -/dev/hdc and /dev/hdd, -respectively. Newer IDE controllers can actually have two channels, -effectively acting like two controllers. - - - - - - - -The first DASD device is named -/dev/dasda. - - - - -The second DASD device is named -/dev/dasdb, and so on. - - - - - - -The partitions on each disk are represented by appending a decimal -number to the disk name: sda1 and -sda2 represent the first and -second partitions of the first SCSI disk drive in your system. - - - -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 sda, -and the second sdb. If the -sda drive has 3 partitions on it, these will be -named sda1, sda2, and -sda3. The same applies to the -sdb disk and its partitions. - - - -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. - - - -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 /dev/hda1. The logical partitions are -numbered starting at 5, so the first logical partition on that same -drive is /dev/hda5. 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. - - - -Sun disk partitions allow for 8 separate partitions (or slices). The -third partition is usually (and is preferred to have) the Whole -Disk partition. This partition references all of the sectors of the -disk, and is used by the boot loader (either SILO, or Sun's). - - - -The partitions on each disk are represented by appending a decimal -number to the disk name: dasda1 and -dasda2 represent the first and -second partitions of the first DASD device in your system. - - - diff --git a/nl/partitioning/partition-programs.xml b/nl/partitioning/partition-programs.xml deleted file mode 100644 index eb3045891..000000000 --- a/nl/partitioning/partition-programs.xml +++ /dev/null @@ -1,138 +0,0 @@ - - - - - &debian; Partitioning Programs - - -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. - - - - - - -partman - - -Recommended partitioning tool in &debian;. This Swiss army knife can -also resize partitions, create filesystems - (format in Windows speak) -and assign them to the mountpoints. - - - - - -fdisk - - -The original Linux disk partitioner, good for gurus. - - - -Be careful if you have existing FreeBSD partitions on your machine. -The installation kernels include support for these partitions, but the -way that fdisk represents them (or not) can make the -device names differ. See the -Linux+FreeBSD HOWTO. - - - - - -cfdisk - - -A simple-to-use, full-screen disk partitioner for the rest of us. - - - -Note that cfdisk doesn't understand FreeBSD -partitions at all, and, again, device names may differ as a result. - - - - - -atari-fdisk - - -Atari-aware version of fdisk. - - - - - -amiga-fdisk - - -Amiga-aware version of fdisk. - - - - - -mac-fdisk - - -Mac-aware version of fdisk. - - - - - -pmac-fdisk - - -PowerMac-aware version of fdisk, also used by BVM -and Motorola VMEbus systems. - - - - - -fdasd - - -&arch-title; version of fdisk; Please read the -fdasd manual page or chapter 13 in - -Device Drivers and Installation Commands for details. - - - - - - - -One of these programs will be run by default when you select -Partition disks (or similar). It may be possible -to use a different partitioning tool from the command line on VT2, but this -is not recommended. - -Remember to mark your boot partition as -Bootable. - - - -One key point when partitioning for Mac type disks is that the -swap partition is identified by its name; it must be named swap. -All Mac linux partitions are the same partition type, -Apple_UNIX_SRV2. Please read the fine manual. We also suggest reading the -mac-fdisk Tutorial, which -includes steps you should take if you are sharing your disk with MacOS. - - - -&partition-hppa.xml; -&partition-x86.xml; -&partition-ia64.xml; -&partition-mips.xml; -&partition-powerpc.xml; -&partition-sparc.xml; - - diff --git a/nl/partitioning/partition/hppa.xml b/nl/partitioning/partition/hppa.xml deleted file mode 100644 index e93a8bb7f..000000000 --- a/nl/partitioning/partition/hppa.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - - Partitioning for &arch-title; - - -PALO, the HPPA boot loader, requires a partition of type F0 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 -/boot, since that is the directory where the Linux -kernel(s) will be stored. /boot needs to be big enough -to hold whatever kernels (and backups) you might wish to load; 25–50MB -is generally sufficient. - - - diff --git a/nl/partitioning/partition/ia64.xml b/nl/partitioning/partition/ia64.xml deleted file mode 100644 index ecb7b66b3..000000000 --- a/nl/partitioning/partition/ia64.xml +++ /dev/null @@ -1,120 +0,0 @@ - - - - - Partitioning for &arch-title; - - -The partman disk partitioner is the default -partitioning tool for the installer. -It manages the set of partitions and their mount points to ensure -that the disks and filesystems are properly configured for a successful -installation. It actually uses parted to do the -on-disk partitioning. - - - - - EFI Recognized Formats - - -The IA-64 EFI firmware supports two partition table (or disk label) -formats, GPT and MS-DOS. MS-DOS, the format typically used on i386 -PCs, is no longer recommended for IA-64 systems. Although -the installer also provides cfdisk, -you should only use -parted because only it can manage both GPT -and MS-DOS tables correctly. - - - - - -The automatic partitioning recipes for partman -allocate an EFI partition as the first partition on the disk. -You can also set up the partition under the Guided -partitioning from the main menu in a manner similar to -setting up a swap partition. - - - -The partman 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 -parted 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: - - - mklabel gpt - mkpartfs primary fat 0 50 - mkpartfs primary linux-swap 51 1000 - mkpartfs primary ext2 1001 3000 - set 1 boot on - print - quit - - -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 parted can take a few minutes to -complete, as it scans the partition for bad blocks. - - - - - Boot Loader Partition Requirements - - -ELILO, the IA-64 boot loader, requires a partition containing a FAT -file system with the boot 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. - - - -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 partman partitioner checks for an EFI partition -at the same time it checks for a properly set up root -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. - - - -It is strongly recommended that you allocate the EFI boot partition -on the same disk as the root filesystem. - - - - - EFI Diagnostic Partitions - - -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. - - - diff --git a/nl/partitioning/partition/mips.xml b/nl/partitioning/partition/mips.xml deleted file mode 100644 index edd4d7176..000000000 --- a/nl/partitioning/partition/mips.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - Partitioning for &arch-title; - - -SGI machines require an SGI disk label in order to make the system bootable -from hard disk. It can be created in the fdisk expert menu. The thereby -created volume header (partition number 9) should be at least 3MB large. -If the volume header created is too small, you can simply delete -partition number 9 and re-add it with a different size. Note that the -volume header must start at sector 0. - - - diff --git a/nl/partitioning/partition/powerpc.xml b/nl/partitioning/partition/powerpc.xml deleted file mode 100644 index 6aadde151..000000000 --- a/nl/partitioning/partition/powerpc.xml +++ /dev/null @@ -1,57 +0,0 @@ - - - - - Partitioning Newer PowerMacs - - -If you are installing onto a NewWorld PowerMac you must create a -special bootstrap partition to hold the boot loader. The size of this -partition must have at least 819200 bytes and its partition type must be -Apple_Bootstrap. If the bootstrap partition is -not created with the Apple_Bootstrap type your -machine cannot be made bootable from the hard disk. This partition -can easily be created by creating a new partition in -partman and telling it to use it as a NewWorld -boot partition, or in mac-fdisk using the -b command. - - - -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. - - - -Note that the bootstrap partition is only meant to hold 3 very small -files: the yaboot binary, its configuration -yaboot.conf, and a first stage OpenFirmware -loader ofboot.b. It need not and must not be -mounted on your file system nor have kernels or anything else copied -to it. The ybin and mkofboot -utilities are used to manipulate this partition. - - - -In order for OpenFirmware to automatically boot &debian-gnu; the bootstrap -partition should appear before other boot partitions on the disk, -especially MacOS boot partitions. The bootstrap partition should be -the first one you create. However, if you add a bootstrap partition -later, you can use mac-fdisk's -r 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. - - - -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. - - - diff --git a/nl/partitioning/partition/sparc.xml b/nl/partitioning/partition/sparc.xml deleted file mode 100644 index f4996a519..000000000 --- a/nl/partitioning/partition/sparc.xml +++ /dev/null @@ -1,33 +0,0 @@ - - - - - Partitioning for &arch-title; - - -Make sure you create a Sun disk label 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 -s key is used in fdisk to -create Sun disk labels. - - - -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 -not 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. - - - -It is also advised that the third partition should be of type Whole -disk (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 SILO boot loader keep its bearings. - - - \ No newline at end of file diff --git a/nl/partitioning/partition/x86.xml b/nl/partitioning/partition/x86.xml deleted file mode 100644 index ff3ef812c..000000000 --- a/nl/partitioning/partition/x86.xml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - Partitioning for &arch-title; - - -If you have an existing other operating system such as DOS or Windows and -you want to preserve that operating system while installing &debian;, you may -need to resize its partition to free up space for the &debian; installation. -The installer supports resizing of both FAT and NTFS filesystems; when you -get to the installer's partitioning step, select the option -Manual and then simply select an existing -partition and change its size. - - - -The PC BIOS generally adds additional constraints for disk -partitioning. There is a limit to how many primary and -logical 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 -Linux Partition HOWTO and the -Phoenix BIOS FAQ, but -this section will include a brief overview to help you plan most situations. - - - -Primary partitions are the original partitioning scheme for PC -disks. However, there can only be four of them. To get past this -limitation, extended and logical 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. - - - -Linux limits the partitions per drive to 255 partitions for SCSI disks -(3 usable primary partitions, 252 logical partitions), and 63 -partitions on an IDE drive (3 usable primary partitions, 60 logical -partitions). However the normal &debian-gnu; system provides -only 20 devices for partitions, so you may not install on partitions -higher than 20 unless you first manually create devices for those -partitions. - - - -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). - - - -This restriction doesn't apply if you have a BIOS newer than around -1995–98 (depending on the manufacturer) that supports the Enhanced -Disk Drive Support Specification. Both Lilo, the Linux loader, and -&debian;'s alternative mbr must use the BIOS to read the -kernel from the disk into RAM. If the BIOS int 0x13 large disk access -extensions are found to be present, they will be utilized. Otherwise, -the legacy disk access interface is used as a fall-back, and it cannot -be used to address any location on the disk higher than the 1023rd -cylinder. Once &arch-kernel; is booted, no matter what BIOS your computer -has, these restrictions no longer apply, since &arch-kernel; does not use the -BIOS for disk access. - - - -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 (Large). -More information about issues with large disks can be found in the -Large Disk HOWTO. 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 translated representation of the -1024th cylinder. - - - -The recommended way of accomplishing this is to create a small (25–50MB -should suffice) partition at the beginning of the disk to be used as -the boot partition, and then create whatever other partitions you wish -to have, in the remaining area. This boot partition -must be mounted on /boot, -since that is the directory where the &arch-kernel; kernel(s) will be stored. -This configuration will work on any system, regardless of whether LBA -or large disk CHS translation is used, and regardless of whether your -BIOS supports the large disk access extensions. - - - diff --git a/nl/partitioning/partitioning.xml b/nl/partitioning/partitioning.xml deleted file mode 100644 index 68cd5c88f..000000000 --- a/nl/partitioning/partitioning.xml +++ /dev/null @@ -1,13 +0,0 @@ - - - - -Partitioning for &debian; - -&sizing.xml; -&tree.xml; -&schemes.xml; -&device-names.xml; -&partition-programs.xml; - - diff --git a/nl/partitioning/schemes.xml b/nl/partitioning/schemes.xml deleted file mode 100644 index 373430f3d..000000000 --- a/nl/partitioning/schemes.xml +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - Recommended Partitioning Scheme - - -For new users, personal &debian; boxes, home systems, and other -single-user setups, a single / 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. - - - -For multi-user systems or systems with lots of disk space, it's best -to put /usr, /var, -/tmp, and /home each on -their own partitions separate from the / -partition. - - - -You might need a separate /usr/local 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 /var/mail a separate partition. Often, -putting /tmp on its own partition, for instance -20–50MB, is a good idea. If you are setting up a server with lots -of user accounts, it's generally good to have a separate, large -/home partition. In general, the partitioning -situation varies from computer to computer depending on its uses. - - - -For very complex systems, you should see the - -Multi Disk HOWTO. This contains in-depth information, mostly -of interest to ISPs and people setting up servers. - - - -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. - - - -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 spindles) and, if possible, different SCSI or -IDE channels. The kernel will balance swap usage between multiple -swap partitions, giving better performance. - - - -As an example, an older home machine might have 32MB of RAM and a -1.7GB IDE drive on /dev/hda. There might be a -500MB partition for another operating system on -/dev/hda1, a 32MB swap partition on -/dev/hda3 and about 1.2GB on -/dev/hda2 as the Linux partition. - - - -For an idea of the space taken by tasks -you might be interested in adding after your system installation is -complete, check . - - - - diff --git a/nl/partitioning/sizing.xml b/nl/partitioning/sizing.xml deleted file mode 100644 index 2f4556621..000000000 --- a/nl/partitioning/sizing.xml +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - Deciding on &debian; Partitions and Sizes - - -At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can -have a single partition containing the entire operating system, -applications, and your personal files. Most people feel that a -separate swap partition is also a necessity, although it's not -strictly true. Swap is scratch space for an operating system, -which allows the system to use disk storage as virtual -memory. By putting swap on a separate partition, &arch-kernel; can make much -more efficient use of it. It is possible to force &arch-kernel; to use a -regular file as swap, but it is not recommended. - - - -Most people choose to give GNU/&arch-kernel; more than the minimum number of -partitions, however. There are two reasons you might want to break up -the file system into a number of smaller partitions. The first is for -safety. If something happens to corrupt the file system, generally -only one partition is affected. Thus, you only have to replace (from -the backups you've been carefully keeping) a portion of your -system. At a bare minimum, you should consider creating what is -commonly called a root partition. This contains the most essential -components of the system. If any other partitions get corrupted, you -can still boot into GNU/&arch-kernel; to fix the system. This can save you the -trouble of having to reinstall the system from scratch. - - - -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 /var/mail a separate partition on the mail -server, most of the system will remain working even if you get spammed. - - - -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? - - - diff --git a/nl/partitioning/tree.xml b/nl/partitioning/tree.xml deleted file mode 100644 index 7a4aec4bc..000000000 --- a/nl/partitioning/tree.xml +++ /dev/null @@ -1,153 +0,0 @@ - - - - - - The Directory Tree - - -&debian-gnu; adheres to the -Filesystem Hierarchy Standard -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 -/. At the root level, all &debian; systems include -these directories: - - - - - - DirectoryContent - - - - - - bin - Essential command binaries - - boot - Static files of the boot loader - - dev - Device files - - etc - Host-specific system configuration - - home - User home directories - - lib - Essential shared libraries and kernel modules - - media - Contains mount points for replaceable media - - mnt - Mount point for mounting a file system temporarily - - proc - Virtual directory for system information (2.4 and 2.6 kernels) - - root - Home directory for the root user - - sbin - Essential system binaries - - sys - Virtual directory for system information (2.6 kernels) - - tmp - Temporary files - - usr - Secondary hierarchy - - var - Variable data - - srv - Data for services provided by the system - - opt - Add-on application software packages - - - - - - -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. - - - - - -The root partition / must always physically -contain /etc, /bin, -/sbin, /lib and -/dev, otherwise you won't be able to boot. -Typically 150–250MB is needed for the root partition. - - - - -/usr: contains all user programs -(/usr/bin), libraries -(/usr/lib), documentation -(/usr/share/doc), etc. -This is the part of the file system that generally takes up most space. -You should provide at least 500MB of disk space. This amount should -be increased depending on the number and type of packages you plan -to install. A generous workstation or server installation should allow -4–6GB. - - - - -/var: variable data like news articles, e-mails, -web sites, databases, the packaging system cache, etc. will be placed -under this directory. The size of this directory depends greatly on -the usage of your system, but for most people will be dictated by -the package management tool's overhead. If you are going to do a full -installation of just about everything &debian; has to offer, all in one -session, setting aside 2 or 3 GB of space for -/var 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. - - - - -/tmp: temporary data created by programs will -most likely go in this directory. 40–100MB should usually -be enough. Some applications — including archive manipulators, -CD/DVD authoring tools, and multimedia software — may use -/tmp to temporarily store image files. If you -plan to use such applications, you should adjust the space available -in /tmp accordingly. - - - - -/home: every user will put his personal data -into a subdirectory of this directory. Its size depends on how many -users will be using the system and what files are to be stored in -their directories. Depending on your planned usage you should reserve -about 100MB for each user, but adapt this value to your needs. Reserve -a lot more space if you plan to save a lot of multimedia files (pictures, MP3, movies) -in your home directory. - - - - - diff --git a/nl/post-install/further-reading.xml b/nl/post-install/further-reading.xml deleted file mode 100644 index 357e3dd7e..000000000 --- a/nl/post-install/further-reading.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - - Further Reading and Information - - -If you need information about a particular program, you should first -try man program, or -info program. - - - -There is lots of useful documentation in -/usr/share/doc as well. In particular, -/usr/share/doc/HOWTO and -/usr/share/doc/FAQ contain lots of interesting -information. To submit bugs, look at -/usr/share/doc/debian/bug*. To read about -&debian;-specific issues for particular programs, look at -/usr/share/doc/(package name)/README.Debian. - - - -The -Debian web site -contains a large quantity of documentation about Debian. In -particular, see the -Debian GNU/Linux FAQ and the -Debian -Reference. -An index of more Debian documentation is available from the -Debian Documentation Project. -The Debian community is self-supporting; to subscribe to -one or more of the Debian mailing lists, see the - -Mail List Subscription page. -Last, but not least, the Debian Mailing -List Archives contain a wealth of information on Debian. - - - -A general source of information on GNU/Linux is the -Linux Documentation Project. -There you will find the HOWTOs and pointers to other very valuable -information on parts of a GNU/Linux system. - - - - diff --git a/nl/post-install/kernel-baking.xml b/nl/post-install/kernel-baking.xml deleted file mode 100644 index 5420f102c..000000000 --- a/nl/post-install/kernel-baking.xml +++ /dev/null @@ -1,173 +0,0 @@ - - - - Compiling a New Kernel - - -Why would someone want to compile a new kernel? It is often not -necessary since the default kernel shipped with &debian; handles most -configurations. Also, &debian; often offers several alternative kernels. -So you may want to check first if there is an alternative kernel image -package that better corresponds to your hardware. However, it can be -useful to compile a new kernel in order to: - - - - -handle special hardware needs, or hardware conflicts with the -pre-supplied kernels - - - - -use options of the kernel which are not supported in the pre-supplied -kernels (such as high memory support) - - - - -optimize the kernel by removing useless drivers to speed up boot time - - - - -create a monolithic instead of a modularized kernel - - - - -run an updated or development kernel - - - - -learn more about linux kernels - - - - - - - Kernel Image Management - - -Don't be afraid to try compiling the kernel. It's fun and profitable. - - - -To compile a kernel the &debian; way, you need some packages: -fakeroot, kernel-package, -linux-source-2.6 -and a few others which are probably already installed (see -/usr/share/doc/kernel-package/README.gz for the -complete list). - - - -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; -/boot will hold the kernel, the System.map, and a -log of the active config file for the build. - - - -Note that you don't have to compile your kernel -the Debian way; 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 -linux-source-2.6, -yet still use the kernel-package compilation method. - - - -Note that you'll find complete documentation on using -kernel-package under -/usr/share/doc/kernel-package. This section just -contains a brief tutorial. - - - -Hereafter, we'll assume you have free rein over your machine and will -extract your kernel source to somewhere in your home directory - - - -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. - - - -. 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 -tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2 -and change to the directory linux-source-&kernelversion; -that will have been created. - - - -Now, you can configure your kernel. Run make -xconfig if X11 is installed, configured and being run; run -make menuconfig otherwise (you'll need -libncurses5-dev 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 Kernel module loader -in Loadable module support (it is not selected by default). -If not included, your &debian; installation will experience problems. - - - -Clean the source tree and reset the kernel-package -parameters. To do that, do make-kpkg clean. - - - -Now, compile the kernel: -fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image. -The version number of 1.0 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 custom -(e.g., a host name). Kernel compilation may take quite a while, depending on -the power of your machine. - - - -Once the compilation is complete, you can install your custom kernel -like any package. As root, do -dpkg -i -../&kernelpackage;-&kernelversion;-subarchitecture_custom.1.0_&architecture;.deb. -The subarchitecture part is an optional -sub-architecture, - such as 686, -depending on what kernel options you set. -dpkg -i will install the -kernel, along with some other nice supporting files. For instance, -the System.map will be properly installed -(helpful for debugging kernel problems), and -/boot/config-&kernelversion; will be installed, -containing your current configuration set. Your new -kernel package is also clever enough to automatically update your boot -loader to use the new kernel. If you have created a modules package, -you'll need to install that package as well. - - - -It is time to reboot the system: read carefully any warning that the -above step may have produced, then shutdown -r now. - - - -For more information on &debian; kernels and kernel compilation, see the -Debian Linux Kernel Handbook. -For more information on kernel-package, read -the fine documentation in /usr/share/doc/kernel-package. - - - - diff --git a/nl/post-install/mail-setup.xml b/nl/post-install/mail-setup.xml deleted file mode 100644 index 103d06059..000000000 --- a/nl/post-install/mail-setup.xml +++ /dev/null @@ -1,263 +0,0 @@ - - - - - Setting Up Your System To Use E-Mail - - -Today, email is an important part of many people's life. As there are -many options as to how to set it up, and as having it set up correctly is -important for some &debian; utilities, we will try to cover the basics in -this section. - - - -There are three main functions that make up an e-mail system. First there is -the Mail User Agent (MUA) which is the program a user -actually uses to compose and read mails. Then there is the Mail -Transfer Agent (MTA) that takes care of transferring messages -from one computer to another. And last there is the Mail -Delivery Agent (MDA) that takes care of delivering incoming mail -to the user's inbox. - - - -These three functions can be performed by separate programs, but they can -also be combined in one or two programs. It is also possible to have -different programs handle these functions for different types of mail. - - - -On Linux and Unix systems mutt is historically a very -popular MUA. Like most traditional Linux programs it is text based. It is -often used in combination with exim or -sendmail as MTA and procmail as MDA. - - - -With the increasing popularity of graphical desktop systems, the use of -graphical e-mail programs like GNOME's evolution, -KDE's kmail or Mozilla's thunderbird -(in &debian; available as icedove - - -The reason that thunderbird has been renamed to -icedove in &debian; has to do with licensing issues. -Details are outside the scope of this manual. - - -) is becoming more popular. These programs combine the function -of a MUA, MTA and MDA, but can — and often are — also be used -in combination with the traditional Linux tools. - - - - - Default E-Mail Configuration - - -Even if you are planning to use a graphical mail program, it is important -that a traditional MTA/MDA is also installed and correctly set up on your -&debian-gnu; system. Reason is that various utilities running on the -system - - -Examples are: cron, quota, -logcheck, aide, … - - - can send important notices by e-mail to inform the system -administrator of (potential) problems or changes. - - - -For this reason the packages exim4 and -mutt will be installed by default (provided you -did not unselect the standard task during the installation). -exim4 is a combination MTA/MDA that is relatively -small but very flexible. By default it will be configured to only handle -e-mail local to the system itself and e-mails addressed to the system -administrator (root account) will be delivered to the regular user account -created during the installation - - -The forwarding of mail for root to the regular user account is configured -in /etc/aliases. If no regular user account was created, -the mail will of course be delivered to the root account itself. - - -. - - - -When system e-mails are delivered they are added to a file in -/var/mail/account_name. -The e-mails can be read using mutt. - - - - - - Sending E-Mails Outside The System - - -As mentioned earlier, the installed &debian; system is only set up to handle -e-mail local to the system, not for sending mail to others nor for -receiving mail from others. - - - -If you would like exim4 to handle external e-mail, -please refer to the next subsection for the basic available configuration -options. Make sure to test that mail can be sent and received correctly. - - - -If you intend to use a graphical mail program and use a mail server of -your Internet Service Provider (ISP) or your company, there is not really -any need to configure exim4 for handling external -e-mail. Just configure your favorite graphical mail program to use the -correct servers to send and receive e-mail (how is outside the scope of -this manual). - - - -However, in that case you may need to configure individual utilities to -correctly send e-mails. One such utility is reportbug, -a program that facilitates submitting bug reports against &debian; packages. -By default it expects to be able to use exim4 to -submit bug reports. - - - -To correctly set up reportbug to use an external mail -server, please run the command reportbug --configure -and answer no to the question if an MTA is available. You -will then be asked for the SMTP server to be used for submitting bug reports. - - - - - - Configuring the Exim4 Mail Transport Agent - - -If you would like your system to also handle external e-mail, you will -need to reconfigure the exim4 package - - -You can of course also remove exim4 and replace -it with an alternative MTA/MDA. - - -: - - -# dpkg-reconfigure exim4-config - - - - -After entering that command (as root), you will be asked if you want split -the configuration into small files. If you are unsure, select the default -option. - - - -Next you will be presented with several common mail scenarios. Choose the -one that most closely resembles your needs. - - - - - -internet site - - -Your system is connected to a network and your mail is sent and -received directly using SMTP. On the following screens you will be -asked a few basic questions, like your machine's mail name, or a list of -domains for which you accept or relay mail. - - - - - -mail sent by smarthost - - -In this scenario your outgoing mail is forwarded to another machine, -called a smarthost, which takes care of sending the message -on to its destination. -The smarthost also usually stores incoming mail addressed to your -computer, so you don't need to be permanently online. That also means -you have to download your mail from the smarthost via programs like -fetchmail. - - - -In a lot of cases the smarthost will be your ISP's mail server, which -makes this option very suitable for dial-up users. It can also be a -company mail server, or even another system on your own network. - - - - - -mail sent by smarthost; no local mail - - -This option is basically the same as the previous one except that the -system will not be set up to handle mail for a local e-mail domain. Mail -on the system itself (e.g. for the system administrator) will still be -handled. - - - - - -local delivery only - - -This is the option your system is configured for by default. - - - - - -no configuration at this time - - -Choose this if you are absolutely convinced you know what you are -doing. This will leave you with an unconfigured mail system — -until you configure it, you won't be able to send or receive any mail -and you may miss some important messages from your system utilities. - - - - - - - -If none of these scenarios suits your needs, or if you need a finer -grained setup, you will need to edit configuration files under the -/etc/exim4 directory after the installation is -complete. More information about exim4 may be -found under /usr/share/doc/exim4; the file -README.Debian.gz has further details about -configuring exim4 and explains where to find -additional documentation. - - - -Note that sending mail directly to the Internet when you don't have an -official domain name, can result in your mail being rejected because of -anti-spam measures on receiving servers. Using your ISP's mail server is -preferred. If you still do want to send out mail directly, you may want to -use a different e-mail address than is generated by default. If you use -exim4 as your MTA, this is possible by adding an -entry in /etc/email-addresses. - - - - diff --git a/nl/post-install/new-to-unix.xml b/nl/post-install/new-to-unix.xml deleted file mode 100644 index e235f3757..000000000 --- a/nl/post-install/new-to-unix.xml +++ /dev/null @@ -1,29 +0,0 @@ - - - - - - If You Are New to Unix - - -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 Debian Reference. -This list of Unix FAQs contains a -number of UseNet documents which provide a nice historical reference. - - - -Linux is an implementation of Unix. The -Linux Documentation Project (LDP) -collects a number of HOWTOs and online books -relating to Linux. Most of these documents can be installed locally; -just install the doc-linux-html package (HTML -versions) or the doc-linux-text package (ASCII -versions), then look in /usr/share/doc/HOWTO. -International versions of the LDP HOWTOs are also available as &debian; -packages. - - - - diff --git a/nl/post-install/orientation.xml b/nl/post-install/orientation.xml deleted file mode 100644 index 50283724b..000000000 --- a/nl/post-install/orientation.xml +++ /dev/null @@ -1,109 +0,0 @@ - - - - - Orienting Yourself to &debian; - - -&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. - - - - &debian; Packaging System - - -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: - - - - -/usr (excluding /usr/local) - - - - -/var (you could make -/var/local and be safe in there) - - - - -/bin - - - - -/sbin - - - - -/lib - - - - -For instance, if you replace /usr/bin/perl, that -will work, but then if you upgrade your perl -package, the file you put there will be replaced. Experts can get -around this by putting packages on hold in -aptitude. - - - -One of the best installation methods is apt. You can use the command -line version apt-get or full-screen text version -aptitude. Note apt will also let you merge -main, contrib, and non-free so you can have export-restricted packages -as well as standard versions. - - - - - Application Version Management - - - -Alternative versions of applications are managed by update-alternatives. If -you are maintaining multiple versions of your applications, read the -update-alternatives man page. - - - - - Cron Job Management - - -Any jobs under the purview of the system administrator should be in -/etc, since they are configuration files. If you -have a root cron job for daily, weekly, or monthly runs, put them in -/etc/cron.{daily,weekly,monthly}. These are -invoked from /etc/crontab, and will run in -alphabetic order, which serializes them. - - - -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 /etc/crontab, or, better yet, -/etc/cron.d/whatever. These particular files -also have an extra field that allows you to stipulate the user account -under which the cron job runs. - - - -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 -/usr/share/doc/cron/README.Debian. - - - - diff --git a/nl/post-install/post-install.xml b/nl/post-install/post-install.xml deleted file mode 100644 index 95eca7933..000000000 --- a/nl/post-install/post-install.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - - Next Steps and Where to Go From Here - -&shutdown.xml; -&new-to-unix.xml; -&orientation.xml; -&further-reading.xml; -&mail-setup.xml; -&kernel-baking.xml; -&rescue.xml; - - diff --git a/nl/post-install/rescue.xml b/nl/post-install/rescue.xml deleted file mode 100644 index 5517b5e2d..000000000 --- a/nl/post-install/rescue.xml +++ /dev/null @@ -1,71 +0,0 @@ - - - - - Recovering a Broken System - - -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 -/sbin/init. 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. - - - - - -To access rescue mode, type rescue at the -boot: prompt, or boot with the -rescue/enable=true 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. - - - -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. - - - -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. - - -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 -grub-install '(hd0)' to do so. - - - - -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 /target directory. - - - -In either case, after you exit the shell, the system will reboot. - - - -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. - - - diff --git a/nl/post-install/shutdown.xml b/nl/post-install/shutdown.xml deleted file mode 100644 index e71db46d4..000000000 --- a/nl/post-install/shutdown.xml +++ /dev/null @@ -1,31 +0,0 @@ - - - - - - Shutting down the system - - - -To shut down a running &debian-gnu; system, you must not reboot with the -reset switch on the front or back of your computer, or just turn off -the computer. &debian-gnu; should be shut down in a controlled manner, -otherwise files might get lost and/or disk damage might occur. If you run a -desktop environment, there is usually an option to log out -available from the application menu that allows you to shutdown (or reboot) -the system. - - - -Alternatively you can press the key combination -Ctrl Alt Del - or Control -Shift Power on Macintosh -systems. A last option is to log in as root and type one of the -commands poweroff, halt or -shutdown -h now if either of the key combinations do not -work or you prefer to type commands; use reboot to reboot -the system. - - - diff --git a/nl/preface.xml b/nl/preface.xml deleted file mode 100644 index bcd7d5d52..000000000 --- a/nl/preface.xml +++ /dev/null @@ -1,30 +0,0 @@ - - - - &debian-gnu; &release; installeren op &architecture; - - -Wij zijn verheugd dat u heeft besloten om &debian; te proberen en weten -zeker dat u zult ontdekken dat de GNU/&arch-kernel; distributie van &debian; uniek -is. &debian-gnu; brengt vrije software van over de hele wereld samen en integreert -deze tot een samenhangend geheel. Wij zijn ervan overtuigd dat u zult -ontdekken dat het resultaat werkelijk meer is dan de som der delen. - - - -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 . - - - -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. - - - diff --git a/nl/preparing/backup.xml b/nl/preparing/backup.xml deleted file mode 100644 index 24c163dd8..000000000 --- a/nl/preparing/backup.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - Maak een reservekopie van uw bestaande gegevens! - - -Zorg ervoor dat u, voor u met de installatie start, een reservekopie -maakt van elk bestand dat zich op dit moment op uw systeem bevindt. -Als dit de eerste keer is dat u op uw computer een besturingssysteem -installeert dat van een ander type is dan het besturingssysteem dat bij -de computer is geleverd, dan is de kans groot dat u uw harde schijf -opnieuw zult moeten indelen om ruimte te maken voor &debian-gnu;. Altijd als -u de indeling van uw harde schijf wijzigt, moet u er rekening mee houden -dat alles wat op de harde schijf staat verloren kan gaan, ongeacht het -programma dat u hiervoor gebruikt. De programma's die tijdens de -installatie worden gebruikt zijn behoorlijk betrouwbaar en de meeste worden -al jaren gebruikt; maar ze zijn ook zeer krachtig en een foutieve handeling -kan u in de problemen brengen. Zelfs nadat u een reservekopie heeft gemaakt, -zult u zorgvuldig moeten nadenken over uw antwoorden en keuzen. Twee minuten -nadenken kan uren aan niet noodzakelijk herstelwerk voorkomen. - - - -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. - - - - - diff --git a/nl/preparing/bios-setup/i386.xml b/nl/preparing/bios-setup/i386.xml deleted file mode 100644 index 29765d25f..000000000 --- a/nl/preparing/bios-setup/i386.xml +++ /dev/null @@ -1,337 +0,0 @@ - - - - - - Invoking the BIOS Set-Up Menu - - - -BIOS provides the basic functions needed to boot your machine to allow -your operating system to access your hardware. Your system probably -provides a BIOS setup menu, which is used to configure the BIOS. -Before installing, you must ensure that your BIOS -is set up correctly; not doing so can lead to intermittent crashes or -an inability to install &debian;. - - - -The rest of this section is lifted from the -, answering the question, How do I -enter the CMOS configuration menu?. How you access the BIOS (or -CMOS) configuration menu depends on who wrote your BIOS -software: - - - - - - - - AMI BIOS - - -Delete key during the POST (power on self test) - - - - - - Award BIOS - - - - CtrlAltEsc -, or Delete key during the POST - - - - -DTK BIOS - - -Esc key during the POST - - - - -IBM PS/2 BIOS - - - - CtrlAltInsert - -after - - CtrlAltDelete - - - - - - - Phoenix BIOS - - - - CtrlAltEsc - -or - - CtrlAltS - -or -F1 - - - - - - - -Information on invoking other BIOS routines can be found in -. - - - -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 -. - - - - - Boot Device Selection - - - -Many BIOS setup menus allow you to select the devices that will be -used to bootstrap the system. Set this to look for a bootable -operating system on A: (the first floppy disk), -then optionally the first CD-ROM device (possibly appearing as -D: or E:), and then from -C: (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;. - - - -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. - - - -Another popular option is to boot from a USB storage device (also called -a USB memory stick or USB key). Some BIOSes can boot directly from a USB -storage device, but some cannot. You may need to configure your BIOS to boot -from a Removable drive or even from USB-ZIP to -get it to boot from the USB device. - - - -Here are some details about how to set the boot order. Remember to -reset the boot order after &arch-kernel; is installed, so that you restart -your machine from the hard drive. - - - - - Changing the Boot Order on IDE Computers - - - - -As your computer starts, press the keys to enter the BIOS -utility. Often, it is the Delete key. However, -consult the hardware documentation for the exact keystrokes. - - - - -Find the boot sequence in the setup utility. Its location depends on -your BIOS, but you are looking for a field that lists drives. - - - - -Common entries on IDE machines are C, A, cdrom or A, C, cdrom. - - - - -C is the hard drive, and A is the floppy drive. - - - - -Change the boot sequence setting so that the CD-ROM or the -floppy is first. Usually, the Page Up or -Page Down keys cycle -through the possible choices. - - - - -Save your changes. Instructions on the screen tell you how to -save the changes on your computer. - - - - - - - Changing the Boot Order on SCSI Computers - - - - - -As your computer starts, press the keys to enter the SCSI setup -utility. - - - -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. - - - -The keystrokes you need depend on the utility. Often, it is -CtrlF2. -However, consult your hardware documentation for the -exact keystrokes. - - - - -Find the utility for changing the boot order. - - - - -Set the utility so that the SCSI ID of the CD drive is first on -the list. - - - - -Save your changes. Instructions on the screen tell you how to -save the changes on your computer. Often, you must press -F10. - - - - - - - - - - Miscellaneous BIOS Settings - - CD-ROM Settings - - -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 seek failed error -messages, this may be your problem. - - - - - Extended vs. Expanded Memory - - -If your system provides both extended and -expanded memory, set it so that there is as much -extended and as little expanded memory as possible. &arch-kernel; requires -extended memory and cannot use expanded memory. - - - - - Virus Protection - - -Disable any virus-warning features your BIOS may provide. If you have -a virus-protection board or other special hardware, make sure it is -disabled or physically removed while running GNU/&arch-kernel;. These aren't -compatible with GNU/&arch-kernel;; moreover, due to the file system -permissions and protected memory of the &arch-kernel; kernel, viruses are -almost unheard of - - -After installation you can enable Boot Sector protection if you -want. This offers no additional security in &arch-kernel; but if you also run -Windows it may prevent a catastrophe. There is no need to tamper with -the Master Boot Record (MBR) after the boot manager has been set up. - - -. - - - - - Shadow RAM - - -Your motherboard may provide shadow RAM or BIOS -caching. You may see settings for Video BIOS Shadow, -C800-CBFF Shadow, etc. Disable -all shadow RAM. Shadow -RAM is used to accelerate access to the ROMs on your motherboard and -on some of the controller cards. &arch-kernel; does not use these ROMs once it -has booted because it provides its own faster 32-bit software in place -of the 16-bit programs in the ROMs. Disabling the shadow RAM may make -some of it available for programs to use as normal memory. Leaving -the shadow RAM enabled may interfere with &arch-kernel; access to hardware -devices. - - - - - Memory Hole - - -If your BIOS offers something like 15–16 MB Memory -Hole, please disable that. &arch-kernel; expects to find memory there if -you have that much RAM. - - - -We have a report of an Intel Endeavor motherboard on which there is an -option called LFB or Linear Frame Buffer. -This had two settings: Disabled and 1 -Megabyte. Set it to 1 Megabyte. -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. - - - - - - - Advanced Power Management - - -If your motherboard provides Advanced Power Management (APM), -configure it so that power management is controlled by APM. Disable -the doze, standby, suspend, nap, and sleep modes, and disable the hard -disk's power-down timer. &arch-kernel; can take over control of these modes, -and can do a better job of power-management than the BIOS. - - - - diff --git a/nl/preparing/bios-setup/powerpc.xml b/nl/preparing/bios-setup/powerpc.xml deleted file mode 100644 index 2725ca64a..000000000 --- a/nl/preparing/bios-setup/powerpc.xml +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - Invoking OpenFirmware - - -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. - - - -On &arch-title; Macintoshes, you invoke OpenFirmware with -Command (cloverleaf/Apple)Optionof -while booting. Generally it will check for these keystrokes after the -chime, but the exact timing varies from model to model. See - for more hints. - - - -The OpenFirmware prompt looks like this: - - -ok -0 > - - -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. - - - -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 System Disk 2.3.1 -utility, available from Apple at -. -After unpacking the utility in MacOS, and launching it, select the -Save button to have the firmware patches -installed to nvram. - - - diff --git a/nl/preparing/bios-setup/s390.xml b/nl/preparing/bios-setup/s390.xml deleted file mode 100644 index 1538023f9..000000000 --- a/nl/preparing/bios-setup/s390.xml +++ /dev/null @@ -1,106 +0,0 @@ - - - - - BIOS Setup - - -In order to install &debian-gnu; on a &arch-title; or zSeries -machine you have first boot a kernel into the system. The boot -mechanism of this platform is inherently different to other ones, -especially from PC-like systems: there are no floppy devices available -at all. You will notice another big difference while you work with -this platform: most (if not all) of the time you will work remote, -with the help of some client session software like telnet, or a -browser. This is due to that special system architecture where the -3215/3270 console is line-based instead of character-based. - - - -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. - - - -Before you actually perform an installation, you have to go over some -design and preparation steps. IBM has made documentation available -about the whole process, e.g. how to prepare an installation medium -and how actually to boot from that medium. Duplicating that information -here is neither possible nor necessary. However, we will describe -here which kind of &debian;-specific data is needed and where to find it. -Using both sources of information, you have to prepare your machine -and the installation medium before you can perform a boot from it. -When you see the welcome message in your client session, return to this -document to go through the &debian;-specific installation steps. - - - - - - Native and LPAR installations - - -Please refer to chapter 5 of the - -Linux for &arch-title; -Redbook and chapter 3.2 of the - -Linux for IBM eServer zSeries and &arch-title;: Distributions -Redbook on how to set up an LPAR for Linux. - - - - - - Installation as a VM guest - - - -Please refer to chapter 6 of the - -Linux for &arch-title; -Redbook and chapter 3.1 of the - -Linux for IBM eServer zSeries and &arch-title;: Distributions -Redbook on how to set up a VM guest for running Linux. - - - -You need to copy all the files from the generic -sub-directory to your CMS disk. Be sure to transfer -kernel.debian and -initrd.debian in binary mode with a fixed record -length of 80 characters. - - - - - - Setting up an installation server - - - -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. - - - -The installation server needs to copy the exact directory structure -from any &debian-gnu; mirror, but only the s390 and -architecture-independent files are required. You can also copy the -contents of all installation CDs into such a directory tree. - - - -FIXME: more information needed — from a Redbook? - - - diff --git a/nl/preparing/bios-setup/sparc.xml b/nl/preparing/bios-setup/sparc.xml deleted file mode 100644 index 22b4c13f6..000000000 --- a/nl/preparing/bios-setup/sparc.xml +++ /dev/null @@ -1,103 +0,0 @@ - - - - - Invoking OpenBoot - - - -OpenBoot provides the basic functions needed to boot the &arch-title; -architecture. This is rather similar in function to the BIOS in the -x86 architecture, although much nicer. The Sun boot PROMs have a -built-in forth interpreter which lets you do quite a number of things -with your machine, such as diagnostics and simple scripts. - - - -To get to the boot prompt you need to hold down the -Stop key (on older type 4 keyboards, use the -L1 key, if you have a PC keyboard adapter, use -the Break key) and press the -A key. The boot PROM will give you a prompt, -either ok or >. It is -preferred to have the ok prompt. So if you get -the old style prompt, hit the n key to get the new -style prompt. - - - -If you are using a serial console, send a break to the machine. With Minicom, -use Ctrl-A F, with cu, hit Enter, then type -%~break. Consult the documentation of your terminal -emulator if you are using a different program. - - - - - - Boot Device Selection - - - -You can use OpenBoot to boot from specific devices, and also to change -your default boot device. However, you need to know some details -about how OpenBoot names devices; it's considerably different from Linux -device naming, described in . -Also, the command will vary a bit, depending on what version of -OpenBoot you have. More information about OpenBoot can be found in -the Sun OpenBoot Reference. - - - -Typically, with newer revisions, you can use OpenBoot devices such as -floppy, cdrom, net, -disk, or disk2. These have the obvious -meanings; the net device is for booting from the network. -Additionally, the device name can specify a particular partition of a disk, -such as disk2:a to boot disk2, first partition. Full -OpenBoot device names have the form: - - - -driver-name@ -unit-address: -device-arguments - - -In older revisions of OpenBoot, device naming is a bit different: the -floppy device is called /fd, and SCSI disk devices are of -the form sd(controller, -disk-target-id, -disk-lun). The command -show-devs in newer OpenBoot revisions is useful -for viewing the currently configured devices. For full information, -whatever your revision, see the -Sun OpenBoot Reference. - - - -To boot from a specific device, use the command boot -device. You can set this -behavior as the default using the setenv -command. However, the name of the variable to set changed between -OpenBoot revisions. In OpenBoot 1.x, use the command -setenv boot-from -device. In later revisions of -OpenBoot, use the command setenv boot-device -device. Note, this is also -configurable using the eeprom command on Solaris, -or modifying the appropriate files in -/proc/openprom/options/, for example under Linux: - - -# echo disk1:1 > /proc/openprom/options/boot-device - - -and under Solaris: - - -eeprom boot-device=disk1:1 - - - - diff --git a/nl/preparing/install-overview.xml b/nl/preparing/install-overview.xml deleted file mode 100644 index bb23295a4..000000000 --- a/nl/preparing/install-overview.xml +++ /dev/null @@ -1,186 +0,0 @@ - - - - Overzicht van het installatieproces - - -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. - - - -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. - - - -Onder &debian-gnu; is het veel waarschijnlijker dat uw besturingssysteem -gerepareerd kan worden als er iets mis gaat. Bij een opwaardering zal nooit -een complete installatie nodig zijn: het is altijd mogelijk om het bestaande -systeem op te waarderen. En de programma's zijn vrijwel altijd compatibel -met opeenvolgende releases van het besturingssysteem. Als een nieuwe versie -van een programma ook nieuwe ondersteunende software vereist, zorgt de manier -waarop &debian; pakketten maakt ervoor dat alle software die benodigd is, -automatisch wordt geïdentificeerd en geïnstalleerd. Omdat zoveel aandacht -is besteed aan het voorkomen van de noodzaak om opnieuw te installeeren, -zou u dat als uw allerlaatste redmiddel moeten beschouwen. Het installatiesysteem -is niet ontworpen om een installatie over een bestaand -systeem heen uit te voeren. - - - -Hierna volgt een routekaart voor de stappen die u zult volgen tijdens het -installatieproces. - - - - - - - -Maak een reservekopie van bestaande gegevens en documenten op de harde schijf -waarop u van plan bent &debian; te installeren. - - - - -Verzamel informatie over uw computer en benodigde documentatie voordat u -met de installatie begint. - - - - -Maak op uw harde schijf ruimte vrij waarin door &debian; partities kunnen worden -aangemaakt. - - - - -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). - - - - -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). - - - - - -Start de computer op met het installatiesysteem. - - - - -Selecteer de taal voor het installatiesysteem. - - - - -Activeer de Ethernet netwerkverbinding (indien beschikbaar). - - - - - -Configureer één netwerkinterface. - - - - -Open een ssh-verbinding met het nieuwe systeem. - - - - -Maak verbinding met één of meerdere DASDs (Direct Access Storage Device). - - - - - -Maak en mount de partities waarop &debian; zal worden geïnstalleerd. - - - - -Volg de volledig automatische download/installatie/instelling van het -basissysteem. - - - - -Installeer een opstartlader die &debian-gnu; en/of uw -bestaande systeem kan opstarten. - - - - -Start de computer opnieuw op met het nieuw geïnstalleerde systeem. - - - - - - -Voor &arch-title; heeft u de optie om gebruik te maken van een -experimentele -grafische versie van het installatiesysteem. Zie -voor nadere informatie over deze grafische variant. - - - -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. - - - -De installatiesoftware, debian-installer, is het -voornaamste onderwerp van deze handleiding. Zij verzorgt de herkenning van -hardware en laadt geschikte stuurprogramma's, gebruikt -dhclient voor het opzetten van de netwerkverbinding, -en start debootstrap 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 -debian-installer heeft haar taak volbracht op het moment -dat u het nieuwe systeem voor het eerst opstart. - - - -Om het systeem aan te passen aan uw behoeften, biedt tasksel -u de mogelijkheid om diverse voorgedefinieerde softwarebundels, zoals een -webserver of desktopomgeving, te installeren. - - - -Een belangrijke optie tijdens de installatie is om al dan niet een grafische -desktopomgeving, bestaande uit het X Window System en één van de beschikbare -grafische desktopomgevingen, te installeren. Als u ervoor kiest om de taak -Desktopomgeving niet te selecteren, krijgt u slechts een -relatief basaal, opdrachtregel georienteerd systeem. -Installatie van de taak Desktopomgeving is optioneel omdat het -relatief veel schijfruimte vereist en omdat veel &debian-gnu; systemen in gebruik -zijn als server en voor het vervullen van hun taak eigenlijk helemaal geen -behoefte aan een grafische gebruikersinterface bestaat. - - - -U dient zich ervan bewust te zijn dat het X Window System volledig los staat -van debian-installer 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. - - - diff --git a/nl/preparing/minimum-hardware-reqts.xml b/nl/preparing/minimum-hardware-reqts.xml deleted file mode 100644 index 8fd2cd028..000000000 --- a/nl/preparing/minimum-hardware-reqts.xml +++ /dev/null @@ -1,102 +0,0 @@ - - - - Voldoen aan de minimum hardware-eisen - - -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. - - - -Afhankelijk van uw behoeften, zou u op sommige punten met minder kunnen -volstaan dan de in de tabel hieronder aanbevolen specificaties. - - - -Voor een desktop systeem wordt tenminste een Pentium 4, 1GHz systeem -aanbevolen. - - - -Een willekeurige 'OldWorld' of 'NewWorld' PowerPC kan goed dienst doen als -desktop systeem. - - - - -Aanbevolen minimum systeemeisen - - - - Type installatie - RAM (minimum) - RAM (aanbevolen) - Harde schijf - - - - - - Geen desktop - 64 megabytes - 256 megabytes - 1 gigabyte - - Met desktop - 128 megabytes - 512 megabytes - 5 gigabytes - - -
- - - -De eigenlijke minimum vereisten voor beschikbaar geheugen zijn een stuk -kleiner dan de getallen in deze tabel. Afhankelijk van de architectuur -kan &debian; worden geïnstalleerd met slechts 20MB (voor s390) tot 60MB -(voor amd64). Hetzelfde geldt, zeker als u selectief bent in welke -applicaties u installeert, voor de harde schijf capaciteit. Zie - voor aanvullende informatie over -benodigde harde schijf capaciteit. - - - -Ook op oudere systemen of systemen met beperkte capaciteiten is het mogelijk -om een grafische desktopomgeving te gebruiken. Het is dan echter we aan -te raden om een vensterbeheerder te kiezen die een kleinere aanslag op de -baschikbare capaciteit doet dan die van de GNOME en KDE desktopomgevingen. -Alternatieven zijn bijvoorbeeld xfce4, -icewm en wmaker, maar er zijn -ook andere beschikbaar. - - - -Het is vrijwel onmogelijk om algemene richtlijnen te geven voor benodigde -geheugen en harde schijf capaciteit voor server installaties omdat deze -te zeer afhankelijk zijn van het beoogde gebruik van de server. - - - -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 schijfruimte nodig voor een soepele werking van het &debian-gnu; systeem -zelf is reeds in deze aanbevelingen verwerkt. -De partitie /var in het -bijzonder bevat veel &debian;-specifieke statusinformatie naast de reguliere -inhoud, zoals logbestanden. De bestanden van dpkg (met -informatie over alle geïnstalleerde pakketten) kan makkelijk 40MB gebruiken. -Verder worden hier door apt-get pakketten die gedownload -worden, opgeslagen voordat deze worden geïnstalleerd. Normaal gesproken dient -u tenminste 200MB te reserveren voor /var. - - - - diff --git a/nl/preparing/needed-info.xml b/nl/preparing/needed-info.xml deleted file mode 100644 index b4d2236f4..000000000 --- a/nl/preparing/needed-info.xml +++ /dev/null @@ -1,402 +0,0 @@ - - - - Benodigde informatie - - - Documentatie - - - Installatiehandleiding - - - -Het document dat u nu aan het lezen bent, als gewoon ASCII tekstbestand -of in HTML- of PDF-formaat. - - - - -&list-install-manual-files; - - - - -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 diverse -bestandsformaten en vertalingen. - - - - - -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 diverse -bestandsformaten en vertalingen. - - - - - Hardware documentatie - - -Bevat vaak bruikbare informatie over de configuratie of het gebruik -van uw hardware. - - - - - -Linux Hardware Compatibility HOWTO - - - - - -Linux for SPARC Processors FAQ - - - - - -Linux/Mips website - - - - - - - - Naslag voor &arch-title;-hardware - - -Installatie-instructies en stuurprogramma's ((DASD, XPRAM, Console, -tape, z90 crypto, chandev, netwerk) voor Linux op &arch-title; gebruik -makend van kernel 2.4. - - - - - - -Device Drivers and Installation Commands - - - - - - -Redbook van IBM waarin is beschreven hoe Linux kan worden gecombineerd -met z/VM op zSeries en &arch-title; hardware. - - - - - - - -Linux for &arch-title; - - - - - - -Redbook van IBM waarin de Linux distributies die beschikbaar zijn voor -het mainframe zijn beschreven. - - - - - - - -Linux for IBM eServer zSeries and &arch-title;: Distributions - - - - - - - - - Bronnen voor informatie over apparatuur - - -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. - - - -Informatie over apparatuur kan worden verzameld op basis van: - - - - - - -De handleidingen die bij uw hardware behoren. - - - - -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 Delete toets of één van de functietoetsen. - - - - - -De verpakkingen van uw hardware. - - - - - -Het Systeem-venster in het Configuratiescherm (Control Panel) van Windows. - - - - -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. - - - - - -Uw systeembeheerder of Internetprovider (ISP). Deze bronnen kunnen u -vertellen welke instellingen u nodig heeft voor de configuratie van -uw netwerk en e-mail. - - - - - - - -Voor een installatie benodigde informatie over hardware - - - - HardwareMogelijk benodigde informatie - - - - - - Harde schijven - Hoeveel heeft u er. - -Hun volgorde in het systeem. - - Zijn ze IDE (ook wel aangeduid met PATA), SATA of SCSI. - -Beschikbare vrije ruimte. -Partities. - - Op welke partities andere besturingssystemen geïnstalleerd zijn. - - - - Beeldscherm - Model en fabrikant. - -Ondersteunde resoluties. -Horizontale frequentie. -Verticale frequentie. - - Ondersteunde kleurdieptes (aantal kleuren). - -Grootte van het scherm. - - - Muis - Type: serieel, PS/2 of USB. - -Poort. -Fabrikant. -Aantal knoppen. - - - Netwerk - Model en fabrikant. - -Type van de adapter. - - - Printer - Model en fabrikant. - -Ondersteunde afdrukresolities. - - - Videokaart - Model en fabrikant. - -Beschikbaar videogeheugen. - - Ondersteunde resoluties en kleurdieptes (deze dient u te controleren - ten opzichte van de mogelijkheden van uw beeldscherm). - - - - DASD - Apparaatnummers. - -Beschikbare vrije ruimte. - - - Netwerk - Type van de adapter. - -Apparaatnummers. -Het relatieve apparaatnummer voor OSA kaarten. - -
- - - - - - - Hardware compatibiliteit - - - -Veel merkproducten werken zonder problemen onder &arch-kernel;. Sterker nog, -de ondersteuning van apparatuur binnen &arch-kernel; verbetert met de dag. -Toch ondersteunt &arch-kernel; nog niet dezelfde variëteit aan apparatuur als -sommige andere besturingssystemen. - - - - -In het bijzonder kan &arch-kernel; geen hardware aansturen die vereist dat -een versie van Microsoft Windows actief is. - - - -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. - - - -De meest voorkomende apparatuur van dit type zijn de zogenaamde win-modems. -Maar ook printers en andere apparatuur kunnen Windows-specifiek zijn. - - - -U kunt de compabibiliteit van apparatuur vaststellen door: - - - - -De websites van fabrikanten te raadplegen voor nieuwe stuurprogramma's. - - - - -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. - - - - -De overzichten van hardware compatibiliteit voor &arch-kernel; te raadplegen op -websites gericht op uw platform. - - - - -Op het Internet te zoeken naar de ervaringen van andere gebruikers. - - - - - - - - - - Netwerkinstellingen - - - -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. - - - - -Uw computernaam (mogelijk mag u die zelf bepalen). - - - - -De domeinnaam van uw netwerk. - - - - -Het IP-adres van uw computer. - - - - -Het voor uw netwerk te gebruiken netwerkmasker. - - - - -Het IP-adres van het systeem (de 'gateway') waarlangs u toegang kunt krijgen tot -andere netwerken, waaronder het Internet (uiteraard alleen -als uw netwerk over een dergelijke gateway beschikt). - - - - - -Het systeem op uw netwerk dat u als DNS-server (Domain Name Service) -kunt gebruiken. - - - - - - -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. - - - -Als u gebruik maakt van een draadloos netwerk, zou u ook moeten uitzoeken: - - - - -ESSID van uw draadloze netwerk. - - - -WEP-beveiligingssleutel (indien van toepassing). - - - - - - - - diff --git a/nl/preparing/non-debian-partitioning.xml b/nl/preparing/non-debian-partitioning.xml deleted file mode 100644 index 82e1387ef..000000000 --- a/nl/preparing/non-debian-partitioning.xml +++ /dev/null @@ -1,195 +0,0 @@ - - - - Uw harde schijf vooraf indelen voor een multi-boot systeem - - -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. - - - -Waar in deze paragraaf wordt gesproken over harde schijven, -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. - - - -Als er al een besturingssysteem op uw systeem aanwezig is - - -(Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, FreeBSD, …) - - - -(VM, z/OS, OS/390, …) - - -en u wilt &debian; op dezelfde harde schijf installeren, dan zult u de schijf -moeten herindelen. &debian; vereist eigen partities op de harde schijf. -Het kan niet worden geïnstalleerd op Windows- of MacOS-partities. Sommige -partities zouden kunnen worden gedeeld met andere Unix systemen, maar dit -valt buiten de scope van deze handleiding. U zult tenminste een afzonderlijke -partitie nodig hebben voor het root-bestandssysteem van &debian;. - - - -U kunt informatie over uw huidige partitie-indeling vinden door gebruik te maken -van een schijfindelingsprogramma voor uw huidige besturingssysteem, zoals fdisk of PartitionMagic, zoals Drive Setup, HD Toolkit of MacTools, zoals de VM diskmap. Schijfindelingsprogramma's -beschikken altijd over een functie om bestaande partities te tonen zonder -wijzigingen aan te brengen. - - - -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. - - - -FIXME: write about HP-UX disks? - - - -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. - - - -Als uw machine over slechts één harde schijf beschikt en u het bestaande -besturingssysteem volledig wilt vervangen door &debian-gnu;, kunt u eveneens het -indelen van de schijf uitstellen tot tijdens de installatieprocedure -(), 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. - - - - -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. - - - -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. - - - -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 -niet te proberen om partities voor &debian-gnu; te maken met -de programma's van een ander besturingssysteem. Beperkt u zich tot het maken van -de partities die u wilt behouden voor het oorspronkelijke besturingssysteem. - - - -Als u meerdere besturingssystemen op dezelfde machine wilt installeren, wordt -aangeraden om eerst alle andere systemen te installeren voordat u verder gaat -met de installatie van &debian;. Windows en andere besturingssystemen kunnen de -mogelijkheid om &debian; op te starten verstoren, of kunnen u aanmoedigen om -'vreemde' partities opnieuw te fomateren. - - - -Het is mogelijk om dergelijke problemen te herstellen of te voorkomen, maar u -bespaart uzelf moeite door het oorspronkelijke besturingssysteem eerst te -installeren. - - - -Om &debian-gnu; automatisch te laten opstarten door OpenFirmware, dienen de -&arch-parttype; partities zich te bevinden vóór alle andere partities, in het -bijzonder MacOS opstartpartities. U dient hiermee rekening te houden -wanneer u de schijfindeling voorbereidt: u zou ten behoeve van &arch-parttype; een -dummy-partitie moeten maken die voor de andere -opstartpartities op de harde schijf komt. (De kleine partities die zijn -gereserveerd voor de besturingsprogramma's van de harde schijven van Apple -zijn geen opstartpartities.) U kunt deze dummy-partitie later, tijdens de -eigenlijke installatie, verwijderen en vervangen door de &arch-parttype; partities. - - - -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. - - - - -Maak een reservekopie van alles op de computer. - - - -Start de computer op met behulp van het installatiemedium (zoals een CD of -magneetband) van het oorspronkelijke besturingssysteem. - -Als u de computer opstart vanaf een MacOS CD, houd dan -de c toets ingedrukt tijdens het opstarten om af te dwingen -dat de CD het actieve MacOS systeem wordt. - - - - -Gebruik de schijfindelingsprogramma's behorend bij het oorspronkelijke -besturingssysteem om partities daarvoor te maken. Maak ten behoeve van &debian-gnu; -een dummy-partitie of laat ongebruikte ruimte vrij. - - - - -Installeer het oorspronkelijke besturingssysteem op haar nieuwe partitie. - - - - -Start het oorspronkelijke besturingssysteem opnieuw om te controleren dat -alles in orde is en om de opstartbestanden van &debian; te downloaden. - - - - - -Start het &debian; installatiesysteem op om te vervolgen met de installatie -van &debian;. - - - - - - -&nondeb-part-x86.xml; -&nondeb-part-sparc.xml; -&nondeb-part-powerpc.xml; - - diff --git a/nl/preparing/nondeb-part/powerpc.xml b/nl/preparing/nondeb-part/powerpc.xml deleted file mode 100644 index 9072908c7..000000000 --- a/nl/preparing/nondeb-part/powerpc.xml +++ /dev/null @@ -1,43 +0,0 @@ - - - - - MacOS/OSX Partitioning - - - -The Apple Drive Setup application can be found in the -Utilities 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 Drive Setup. - - - -Remember to create a placeholder partition for GNU/Linux, preferably -positioned first in the disk layout. it doesn't matter what type it -is, it will be deleted and replaced later inside the &debian-gnu; installer. - - - -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, Startup Disk (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 option key at boot time, and separate -options can be installed in the yaboot 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. - - - -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. - - - diff --git a/nl/preparing/nondeb-part/sparc.xml b/nl/preparing/nondeb-part/sparc.xml deleted file mode 100644 index 174fb26f2..000000000 --- a/nl/preparing/nondeb-part/sparc.xml +++ /dev/null @@ -1,41 +0,0 @@ - - - - - Partitioning from SunOS - - - -It's perfectly fine to partition from SunOS; in fact, if you intend to -run both SunOS and &debian; on the same machine, it is recommended that -you partition using SunOS prior to installing &debian;. The Linux -kernel understands Sun disk labels, so there are no problems there. -SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS -(SunOS), romfs or iso9660 (CDROM) partitions. - - - - - Partitioning from Linux or another OS - - - -Whatever system you are using to partition, make sure you create a -Sun disk label 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 fdisk, the -s 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. - - - -You will probably be using SILO as your boot loader (the -small program which runs the operating system kernel). -SILO has certain requirements for partition sizes and -location; see . - - - diff --git a/nl/preparing/nondeb-part/x86.xml b/nl/preparing/nondeb-part/x86.xml deleted file mode 100644 index 60626ed6d..000000000 --- a/nl/preparing/nondeb-part/x86.xml +++ /dev/null @@ -1,121 +0,0 @@ - - - - - Partitioning From DOS or Windows - - -If you are manipulating existing FAT or NTFS partitions, it is -recommended that you either use the scheme below or native Windows or -DOS tools. Otherwise, it is not really necessary to partition from DOS -or Windows; the &debian; partitioning tools will generally do a better -job. - - - -But if you have a large IDE disk, and are not using LBA addressing, -overlay drivers (sometimes provided by hard disk manufacturers), or a -new (post 1998) BIOS that supports large disk access extensions, then -you must locate your &debian; boot partition carefully. In this case, -you will have to put the boot partition into the first 1024 cylinders -of your hard disk (usually around 524 megabytes, without BIOS -translation). This may require that you move an existing FAT or NTFS -partition. - - - - - Lossless Repartitioning When Starting From DOS, Win-32 or OS/2 - - - - -One of the most common installations is onto a system that already -contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, -NT, 2000, XP, 2003, Vista, 7), or OS/2, and it is desired to put &debian; onto the same disk -without destroying the previous system. Note that the installer supports -resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply -start the installer and when you get to the partitioning step, select the -option for Manual -partitioning, select the partition to resize, and specify its new size. -So in most cases you should not need to use the method described below. - - - -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. - - - -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. - - - -The first thing needed is a copy of fips which is -available in the tools/ directory on your nearest &debian; -mirror. Unzip the archive and copy the files -RESTORRB.EXE, FIPS.EXE and -ERRORS.TXT to a bootable floppy. A bootable floppy can -be created using the command sys a: under DOS. -fips 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 before you defragment the disk. - - - -The next thing needed is to move all the data to the beginning of the -partition. defrag, which comes standard with DOS 6.0 and -later, can easily do the job. See the fips documentation -for a list of other software that may do the trick. Note that if you -have Windows 9x, you must run defrag from there, since -DOS doesn't understand VFAT, which is used to support for long -filenames, used in Windows 95 and higher. - - - -After running the defragmenter (which can take a while on a large -disk), reboot with the fips disk you created in the -floppy drive. Simply type a:\fips and follow the directions. - - - -Note that there are many other partition managers out there, in -case fips doesn't do the trick for you. - - - - - Partitioning for DOS - - - -If you are partitioning for DOS drives, or changing the size of DOS -partitions, using &debian; tools, many people experience problems working -with the resulting FAT partitions. For instance, some have reported -slow performance, consistent problems with scandisk, or -other weird errors in DOS or Windows. - - - -Apparently, whenever you create or resize a partition for DOS use, -it's a good idea to fill the first few sectors with zeros. You should do -this prior to running DOS's format command by executing -the following command from &debian;: - - -# dd if=/dev/zero of=/dev/hdXX bs=512 count=4 - - - - - diff --git a/nl/preparing/pre-install-bios-setup.xml b/nl/preparing/pre-install-bios-setup.xml deleted file mode 100644 index 396d58f5a..000000000 --- a/nl/preparing/pre-install-bios-setup.xml +++ /dev/null @@ -1,59 +0,0 @@ - - - - Configuratie van apparatuur en besturingssysteem voor de installatie - - -In deze sectie wordt ingegaan op eventuele hardwareconfiguratie die u moet -uitvoeren voordat u &debian; installeert. In het algemeen betreft dit controle -en mogelijk aanpassing van 'firmware'-instellingen voor uw systeem. De -firmware is de basisprogrammatuur die door de apparatuur wordt gebruikt; -het meest kritieke moment waarop deze wordt gebruikt is tijdens het opstarten -van uw systeem. Ook wordt ingegaan op bekende problemen met apparatuur die -de betrouwbaarheid van &debian-gnu; op uw systeem kunnen beïnvloeden. - - - -&bios-setup-i386.xml; -&bios-setup-powerpc.xml; -&bios-setup-sparc.xml; -&bios-setup-s390.xml; - - - Aandachtspunten ten aanzien van apparatuur - - - USB BIOS instellingen en toetsenborden - - -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 Legacy keyboard emulation of USB keyboard -support. - - - - - - Beeldschermweergave op OldWorld Powermacs - - -Sommige OldWorld Powermacs kunnen onder Linux, als de weergave is ingesteld -op meer dan 256 kleuren, mogelijk kleuren onjuist weergeven. Dit geldt in -het bijzonder voor systemen met het control stuurprogramma -voor video, maar mogelijk ook voor andere. -Als u na het opstarten van de computer dergelijke problemen ondervindt (u -kunt soms wel informatie op de monitor zien, maar soms ook helemaal niets) -of als het scherm zwart wordt na het opstarten van het installatiesysteem -in plaats van de gebruikersinterface te tonen, probeer dan onder MacOS de -beeldscherminstellingen te wijzigen naar 256 kleuren in plaats van -duizenden of millioenen. - - - - - diff --git a/nl/preparing/preparing.xml b/nl/preparing/preparing.xml deleted file mode 100644 index f5518f5b1..000000000 --- a/nl/preparing/preparing.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - Voordat u &debian-gnu; installeert - - - -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. - - - -&install-overview.xml; -&backup.xml; -&needed-info.xml; -&minimum-hardware-reqts.xml; -&non-debian-partitioning.xml; -&pre-install-bios-setup.xml; - - diff --git a/nl/using-d-i/components.xml b/nl/using-d-i/components.xml deleted file mode 100644 index 560ca939a..000000000 --- a/nl/using-d-i/components.xml +++ /dev/null @@ -1,192 +0,0 @@ - - - - Individuele modules gebruiken - - -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. - - - - - Instelling van het installatiesysteem en hardware configuratie - - -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). - - - -U zult merken dat &d-i; verschillende keren tijdens dit stadium een -hardwareherkenning 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. - - -Tijdens de hardwareherkenning zal &d-i; nagaan of er onder de stuurprogramma's -benodigd voor uw hardware gevallen zijn waarvoor firmware geladen moet worden. -Als er stuurprogramma's zijn die firmware proberen te laden, maar waarbij deze -niet beschikbaar is, zal een dialoog getoond worden die de mogelijkheid biedt -de ontbrekende firmware vanaf een verwisselbaar medium te laden. -Zie voor nadere details. - - - -&module-lowmem.xml; -&module-localechooser.xml; -&module-kbd-chooser.xml; -&module-s390-netdevice.xml; -&module-ddetect.xml; -&module-cdrom-detect.xml; -&module-iso-scan.xml; -&module-anna.xml; -&module-netcfg.xml; -&module-choose-mirror.xml; - -&module-clock-setup.xml; - - - - - Schijfindeling en selectie van aanhechtpunten - - -Op dit punt, nadat voor de laatste keer hardwareherkenning heeft plaatsgevonden, -heeft &d-i; zijn volledige sterkte bereikt: aangepast aan de behoeften van de -gebruiker en klaar voor het echte werk. - -Zoals de titel van deze sectie aangeeft, is de voornaamste taak van de volgende -modules het indelen van uw harde schijven, het creëren van bestandssystemen en -het toekennen van aanhechtpunten. Optioneel kunnen nauw gerelateerde zaken als -RAID, LVM of versleutelde partities worden geconfigureerd. - - - -&module-s390-dasd.xml; -&module-partman.xml; -&module-autopartkit.xml; -&module-partitioner.xml; -&module-partconf.xml; -&module-mdcfg.xml; -&module-partman-lvm.xml; -&module-partman-crypto.xml; - - - - Installatie van het Basissysteem - - -Hoewel dit stadium het minst problematisch is, beslaat het wel een significant -deel van de tijd van de installatie omdat hier het volledige basissysteem wordt -opgehaald, geverifieerd en uitgepakt. Als u een langzame computer of -netwerkverbinding heeft, kan dit enige tijd in beslag nemen. - - - -&module-base-installer.xml; - - - - Gebruikers en wachtwoorden instellen - - -Nadat het basissysteem is geïnstalleerd, zal het installatiesysteem u in -staat stellen om het root account en/of een account voor de -eerste gebruiker in te stellen. Accounts voor andere gebruikers kunnen worden -aangemaakt nadat de installatie is afgerond. - - - -&module-user-setup.xml; - - - - Aanvullende software installeren - - -Op dit punt beschikt u over een bruikbaar systeem, maar met beperkte -functionaliteit. De meeste gebruikers zullen aanvullende -programmatuur op het systeem willen installeren om het aan te passen aan hun -behoeften. Het installatiesysteem maakt dit mogelijk. Deze stap kan, zeker -indien u een langzame computer of netwerkverbinding heeft, nog meer tijd in -beslag nemen dan de installatie van het basissysteem. - - - -&module-apt-setup.xml; -&module-pkgsel.xml; - - - - Zorgen dat uw systeem kan worden opgestart - - -Als u een werkstation zonder schijfeenheden installeert, is opstarten vanaf -een locale schijfeenheid uiteraard geen optie en zal deze stap worden -overgeslagen. Desgewenst kunt u OpenBoot instellen om -standaard vanaf het netwerk op te starten; zie . - - - -&module-os-prober.xml; -&module-hppa-palo-installer.xml; -&module-x86-grub-installer.xml; -&module-x86-lilo-installer.xml; -&module-ia64-elilo-installer.xml; -&module-mips-arcboot-installer.xml; -&module-mipsel-colo-installer.xml; -&module-powerpc-yaboot-installer.xml; -&module-powerpc-quik-installer.xml; -&module-s390-zipl-installer.xml; -&module-sparc-silo-installer.xml; -&module-nobootloader.xml; - - - - De installatie afronden - - -Dit is de laatste stap van het installatieproces voor &debian; waarbij het -installatiesysteem nog enkele afrondende taken uitvoert. -Het bestaat voornamelijk uit het afwerken van losse eindjes van &d-i;. - - - -&module-clock-setup-finish.xml; -&module-finish-install.xml; - - - - Diverse modules - - -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. - - - -&module-save-logs.xml; -&module-cdrom-checker.xml; -&module-shell.xml; - -&module-network-console.xml; - diff --git a/nl/using-d-i/loading-firmware.xml b/nl/using-d-i/loading-firmware.xml deleted file mode 100644 index 1fa223cb1..000000000 --- a/nl/using-d-i/loading-firmware.xml +++ /dev/null @@ -1,134 +0,0 @@ - - - - - Loading Missing Firmware - - -As described in , some devices require -firmware to be loaded. In most cases the device will not work at all -if the firmware is not available; sometimes basic functionality is not -impaired if it is missing and the firmware is only needed to enable -additional features. - - - -If a device driver requests firmware that is not available, &d-i; will -display a dialog offering to load the missing firmware. If this option -is selected, &d-i; will scan available devices for either loose firmware -files or packages containing firmware. If found, the firmware will be -copied to the correct location (/lib/firmware) and -the driver module will be reloaded. - - - - -Which devices are scanned and which file systems are supported depends on -the architecture, the installation method and the stage of the installation. -Especially during the early stages of the installation, loading the firmware -is most likely to succeed from a FAT-formatted floppy disk or USB stick. -On i386 and amd64 firmware can also be loaded from an -MMC or SD card. - - - - -Note that it is possible to skip loading the firmware if you know the -device will also function without it, or if the device is not needed during -the installation. - - - - -Support for loading firmware is still relatively basic and is likely to -be improved in future releases of the installer. Currently &d-i; will -for example not display any warning if you choose to load missing firmware, -but the requested firmware is not found. -Please report any issues you encounter by filing an installation report -(see ). - - - - Preparing a medium - - -Although in some cases the firmware can also be loaded from a partition on -a hard disk, the most common method to load firmware will be from some -removable medium such as a floppy disk or a USB stick. -The firmware files or packages must be placed in either the root directory -or a directory named /firmware of the file system on -the medium. The recommended file system to use is FAT as that is most -certain to be supported during the early stages of the installation. - - - -Tarballs containing current packages for the most common firmware are -available from: - - - - - - - -Just download the tarball for the correct release and unpack it to the file -system on the medium. - - - -If the firmware you need is not included in the tarball, you can also -download specific firmware packages from the (non-free section of the) -archive. The following overview should list most available firmware -packages but is not guaranteed to be complete and may also contain -non-firmware packages: - - - - - - - - - -It is also possible to copy individual firmware files to the medium. Loose -firmware could be obtained for example from an already installed system or -from a hardware vendor. - - - - - Firmware and the Installed System - - -Any firmware loaded during the installation will be copied automatically -to the installed system. In most cases this will ensure that the device -that requires the firmware will also work correctly after the system is -rebooted into the installed system. However, if the installed system runs -a different kernel version from the installer there is a slight chance that -the firmware cannot be loaded due to version skew. - - - -If the firmware was loaded from a firmware package, &d-i; will also install -this package for the installed system and will automatically add the non-free -section of the package archive in APT's sources.list. -This has the advantage that the firmware should be updated automatically if -a new version becomes available. - - - -If loading the firmware was skipped during the installation, the relevant -device will probably not work with the installed system until the firmware -(package) is installed manually. - - - - -If the firmware was loaded from loose firmware files, the firmware copied to -the installed system will not be automatically updated -unless the corresponding firmware package (if available) is installed after -the installation is completed. - - - - diff --git a/nl/using-d-i/modules/anna.xml b/nl/using-d-i/modules/anna.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/anna.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/apt-setup.xml b/nl/using-d-i/modules/apt-setup.xml deleted file mode 100644 index 13e77789d..000000000 --- a/nl/using-d-i/modules/apt-setup.xml +++ /dev/null @@ -1,41 +0,0 @@ - - - - Het configureren van APT - - - -Het belangrijkste middel dat mensen gebruiken om pakketten op hun systeem -te installeren is een programma genaamd apt-get, -uit het pakket apt - - - -Merk op dat het programma dat de feitelijke installatie van pakketten -uitvoert, dpkg is. Dit programma is echter meer een -soort specialistisch gereedschap en wordt waar nodig door -apt-get aangeroepen. apt-get 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. - - -. -Ook andere hulpprogramma's voor pakketbeheer, zoals aptitude, -synaptic en het oudere dselect maken -gebruik en zijn afhankelijk van apt-get. 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. - - - -APT moet worden geconfigureerd zodat het weet waar pakketten vandaan kunnen -worden gehaald. Het installatiesysteem verzorgt dit grotendeels automatisch op -basis van de gebruike installatiemethode. Het resultaat van deze configuratie -wordt weggeschreven naar het bestand /etc/apt/sources.list. -U kunt dit bestand na afronding van de installatie bekijken en naar behoefte -aanpassen. - - - diff --git a/nl/using-d-i/modules/autopartkit.xml b/nl/using-d-i/modules/autopartkit.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/autopartkit.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/base-installer.xml b/nl/using-d-i/modules/base-installer.xml deleted file mode 100644 index 215fe6974..000000000 --- a/nl/using-d-i/modules/base-installer.xml +++ /dev/null @@ -1,26 +0,0 @@ - - - - -Tijdens de installatie van het basissysteem worden boodschappen met -betrekking tot het uitpakken en configureren van pakketten doorgestuurd -naar tty4. U kunt naar deze terminal schakelen door -op Linker AltF4 te -drukken; u schakelt terug naar het hoofdscherm van de installatie met behulp -van Linker AltF1. - - - -De boodschappen die tijdens deze fase worden gegenereerd worden ook -opgeslagen in /var/log/syslog. Als de installatie wordt -uitgevoerd vanaf een seriële console, kunt u ze daar raadplegen. - - - -Als onderdeel van de installatie zal een &arch-kernel; kernel worden geïnstalleerd. -Tijdens een standaard installatie zal het installatiesysteem een kernel voor -u kiezen die het beste past bij uw apparatuur. Bij installaties op een -lagere prioriteit zal een lijst worden getoond met beschikbare kernels waaruit -u een keuze kunt maken. - - diff --git a/nl/using-d-i/modules/cdrom-checker.xml b/nl/using-d-i/modules/cdrom-checker.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/nl/using-d-i/modules/cdrom-checker.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/cdrom-detect.xml b/nl/using-d-i/modules/cdrom-detect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/cdrom-detect.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/choose-mirror.xml b/nl/using-d-i/modules/choose-mirror.xml deleted file mode 100644 index 01a36f47c..000000000 --- a/nl/using-d-i/modules/choose-mirror.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - diff --git a/nl/using-d-i/modules/clock-setup-finish.xml b/nl/using-d-i/modules/clock-setup-finish.xml deleted file mode 100644 index 7689d0a81..000000000 --- a/nl/using-d-i/modules/clock-setup-finish.xml +++ /dev/null @@ -1,33 +0,0 @@ - - - - De interne systeemklok instellen - - - -Het installatiesysteem kan u vragen of de interne klok van uw systeem staat -ingesteld op Greenwich Mean Time (GMT of UTC) of niet. Indien mogelijk wordt -deze vraag echter vermeden en zal het installatiesysteem op basis van -informatie als de aanwezigheid van andere besturingssystemen zelf proberen te -bepalen of de interne klok al dan niet is ingesteld op UTC. - - - -Bij een installatie in "expert" modus zal u altijd kunnen kiezen of de interne -klok staat ingesteld op UTC of niet. -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. -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. - - - -Het installatiesysteem zal op dit punt ook proberen om de huidige tijd vast -te leggen in de interne systeemklok. Dit zal worden gedaan ofwel in UTC -ofwel in de locale tijd, afhankelijk van de zojuist gedane selectie. -schrijven - - - diff --git a/nl/using-d-i/modules/clock-setup.xml b/nl/using-d-i/modules/clock-setup.xml deleted file mode 100644 index 43d9be7cb..000000000 --- a/nl/using-d-i/modules/clock-setup.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - - De klok instellen - - - -Het installatiesysteem zal allereerst proberen om verbinding te maken met -een tijdserver op het Internet (gebruikmakend van het NTP -protocol) om op basis daarvan de systeemtijd juist in te stellen. -Als dit mislukt, zal het systeem ervan uitgaan dat de datum en tijd die -tijdens het opstarten van het installatiesysteem zijn bepaald op basis van -de interne systeemklok, juist zijn. Het is niet mogelijk om tijdens de -installatie de systeemtijd handmatig in te stellen. - - - -Het installatiesysteem wijzigt de systeemtijd niet op het s390 platform. - - - -&module-tzsetup.xml; - - diff --git a/nl/using-d-i/modules/ddetect.xml b/nl/using-d-i/modules/ddetect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/ddetect.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/finish-install.xml b/nl/using-d-i/modules/finish-install.xml deleted file mode 100644 index 9bc3190e3..000000000 --- a/nl/using-d-i/modules/finish-install.xml +++ /dev/null @@ -1,20 +0,0 @@ - - - - Het systeem opnieuw opstarten - - - -U zal worden gevraagd om het installatiemedium (CD, diskette, enz.) -dat u heeft gebruikt om het installatiesysteem op te starten, te verwijderen. -Vervolgens zal uw systeem opnieuw opstarten met uw nieuwe &debian; systeem. - - - -Na een laatste dialoog zal het systeem worden gestopt omdat herstarten op -&arch-title; niet wordt ondersteund. U moet vervolgens een IPL voor &debian-gnu; -uitvoeren vanaf de DASD die u tijdens de eerste stappen van de installatie -heeft geselecteerd voor het root bestandssysteem. - - - diff --git a/nl/using-d-i/modules/hppa/palo-installer.xml b/nl/using-d-i/modules/hppa/palo-installer.xml deleted file mode 100644 index 84a3608e8..000000000 --- a/nl/using-d-i/modules/hppa/palo-installer.xml +++ /dev/null @@ -1,20 +0,0 @@ - - - - - <command>palo</command>-installer - - -The bootloader on PA-RISC is palo. -PALO is similar in configuration and usage to -LILO, with a few exceptions. First of all, -PALO allows you to boot any kernel image on your -boot partition. This is because PALO can actually -read Linux partitions. - - - -hppa FIXME ( need more info ) - - - diff --git a/nl/using-d-i/modules/ia64/elilo-installer.xml b/nl/using-d-i/modules/ia64/elilo-installer.xml deleted file mode 100644 index 0c8088cb8..000000000 --- a/nl/using-d-i/modules/ia64/elilo-installer.xml +++ /dev/null @@ -1,135 +0,0 @@ - - - - - Install the <command>ELILO</command> Boot Loader - on a Hard Disk - - -The &architecture; boot loader is called elilo. -It is modeled on the lilo 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 EFI Boot Manager -menu in the firmware to point to the files in the EFI partition. -The elilo boot loader is really in two parts. -The /usr/sbin/elilo command manages the partition and -copies files into it. -The elilo.efi program is copied into the EFI -partition and then run by the EFI Boot Manager to -do the actual work of loading and starting the Linux kernel. - - - -The elilo 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 -root filesystem. - - - - Choose the correct partition! - - - -The criteria for selecting a partition is that it is FAT format -filesystem with its boot 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, elilo may format the partition during -the installation, erasing any previous contents! - - - - - - - EFI Partition Contents - - - -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 -root filesystem. -It is normally not mounted on a running system as it is only needed -by the EFI Boot Manager to load the system and the -installer part of the elilo writes to the filesystem -directly. -The /usr/sbin/elilo utility writes the following files -into the efi/debian directory of the EFI -partition during the installation. -Note that the EFI Boot Manager would find these files -using the path fsn:\efi\debian. -There may be other files in this filesystem as well over time as -the system is updated or re-configured. - - - - - - -elilo.conf - - -This is the configuration file read by the boot loader when it starts. -It is a copy of the /etc/elilo.conf with -the filenames re-written to refer to files in the EFI partition. - - - - -elilo.efi - - -This is the boot loader program that the EFI Boot Manager -runs to boot the system. -It is the program behind the &debian; GNU/Linux -menu item of the EFI Boot Manager command menu. - - - - -initrd.img - - -This is the initial root filesystem used to boot the kernel. -It is a copy of the file referenced in the -/etc/elilo.conf. -In a standard &debian; installation it would be the file in -/boot pointed to by the symbolic link -/initrd.img. - - - - -readme.txt - - -This is a small text file warning you that the contents of the -directory are managed by the elilo and that -any local changes would be lost at the next time -/usr/sbin/elilo is run. - - - - -vmlinuz - - -This is the compressed kernel itself. -It is a copy of the file referenced in the -/etc/elilo.conf. -In a standard &debian; installation it would be the file in -/boot pointed to by the symbolic link -/vmlinuz. - - - - - - diff --git a/nl/using-d-i/modules/iso-scan.xml b/nl/using-d-i/modules/iso-scan.xml deleted file mode 100644 index 47e3b193f..000000000 --- a/nl/using-d-i/modules/iso-scan.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - - De ISO-installatie-image localiseren - - -Als u de hd-media 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 -iso-scan. - - - -Allereerst zal iso-scan automatisch alle blok-apparaten -(d.w.z. partities) die een bekend bestandssysteem hebben, koppelen en -deze achtereenvolgens doorzoeken op bestanden met een extensie -.iso (of .ISO). Merk op dat -tijdens de eerste poging alleen de hoogste twee niveau's van de -mapstructuur zullen worden doorzocht (d.w.z. dat -/willekeurig.iso en -bijvoorbeeld /data/willekeurig.iso -gevonden zullen worden, maar niet bijvoorbeeld -/data/tmp/willekeurig.iso). -Nadat een ISO-image is gevonden, controleert iso-scan 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. - - - -Als de eerste poging om een ISO-installatie-image te vinden faalt, -zal iso-scan 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. - - - - -Als iso-scan 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 -.iso), 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. - - - diff --git a/nl/using-d-i/modules/kbd-chooser.xml b/nl/using-d-i/modules/kbd-chooser.xml deleted file mode 100644 index 01e360817..000000000 --- a/nl/using-d-i/modules/kbd-chooser.xml +++ /dev/null @@ -1,38 +0,0 @@ - - - - Een toetsenbord selecteren - - - -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 dpkg-reconfigure keyboard-configuration). - - - - -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 -F1 t/m F10 toetsen als bovenste regel. - - - - -Er zijn twee toetsenbordindelingen voor US toetsenborden: de -qwerty/mac-usb-us (Apple USB) indeling zal de Alt functie koppelen aan de -Command/Apple-toets (op het toetsenbord naast de -spatiebalk, dus analoog aan Alt op -PC-toetsenborden), terwijl de qwerty/us (Standard) indeling de Alt functie -zal koppelen aan de Option-toets (op de meeste Mac -toetsenborden is op deze toets 'alt' gegraveerd). Verder zijn deze twee -indelingen gelijk. - - - diff --git a/nl/using-d-i/modules/localechooser.xml b/nl/using-d-i/modules/localechooser.xml deleted file mode 100644 index fa1a7737d..000000000 --- a/nl/using-d-i/modules/localechooser.xml +++ /dev/null @@ -1,76 +0,0 @@ - - - - - Lokalisatie bepalen - - - -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 -locale. - - - -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. - - - -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 -locale voor uw systeem in te stellen en om u te helpen bij -de selectie van uw toetsenboord. - - - -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 C-locale kunt selecteren. Het kiezen van de -C-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 locales -niet zal worden geïnstalleerd. - - - -Als u een taal heeft geselecteerd die wordt herkend als officiële taal voor -meer dan één land - - - -In technische termen: indien voor die taal meer dan één locale -bestaat met verschillende landcodes. - - - -, zal een keuzelijst worden getoond met daarin alleen die landen. -Om een land te kiezen dat niet in de lijst voorkomt, kiest u de optie -Andere onderaan de lijst. Er zal dan een -keuzelijst met continenten worden getoond; na selectie van een continent -gevolgd door een keuzelijst met landen die behoren tot dat continent. - - - -Als de taal slechts bij één land voorkomt, zal dat land automatisch worden -geselecteerd. In dat geval is het alleen mogelijk om een ander land te -selecteren door eerst de debconf-prioriteit te verlagen en vervolgens -vanuit het hoofdmenu opnieuw de optie voor taalselectie te kiezen. - - - -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. - - - diff --git a/nl/using-d-i/modules/lowmem.xml b/nl/using-d-i/modules/lowmem.xml deleted file mode 100644 index 01a5f4a11..000000000 --- a/nl/using-d-i/modules/lowmem.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - Controle van beschikbaar geheugen - - - -Eén van de eerste dingen die &d-i; doet, is het controleren van het -beschikbare geheugen. Als de hoeveelheid beschikbaar geheugen beperkt -is, zal deze module een aantal wijzigingen aanbrengen in het -installatieproces waardoor u hopelijk in staat zal zijn om &debian-gnu; -op uw systeem te installeren. - - - -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. - - - diff --git a/nl/using-d-i/modules/mdcfg.xml b/nl/using-d-i/modules/mdcfg.xml deleted file mode 100644 index 9a6e9bd76..000000000 --- a/nl/using-d-i/modules/mdcfg.xml +++ /dev/null @@ -1,233 +0,0 @@ - - - - Meervoudige schijfapparaten configureren (Software-RAID) - - -Als u in uw computer meer dan één harde schijf - -U zou zelfs een Software-RAID kunnen samenstellen uit verschillende -partities op één fysieke harde schijf, maar daarmee bereikt u niets -zinvols. - - heeft, kunt u mdcfg gebruiken -om uw schijfeenheden te configureren voor betere prestaties en/of -grotere betrouwbaarheid van uw gegevens. Het resultaat wordt een -Multidisk Device (MD) of, naar zijn meest -bekende variant, Software-RAID). - - - -MD is in feite niets meer dan een verzameling partities op verschillende -harde schijven die worden gecombineerd om gezamelijk één -logisch apparaat te vormen. Dit apparaat kan vervolgens -worden gebruikt als een gewone partitie (dat wil zeggen dat u het in -partman kunt formatteren en een aanhechtpunt kunt toewijzen. - - - -Het voordeel dat u behaalt, is afhankelijk van het soort MD-apparaat dat u -creëert. Op dit moment worden ondersteund: - - - - -RAID0 - -Levert hoofdzakelijk prestatieverbetering. RAID0 splitst alle binnenkomende -gegevens op in zogenaamde stripes 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 alle gegevens (een deel van de informatie -staat nog wel op de 'gezonde' schijf/schijven, maar een ander deel -stond op de defecte schijf). - - - -RAID0 wordt bijvoorbeeld veel toegepast voor video editing. - - - - - -RAID1 - -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. - - - -Desgewenst kunt u een reserve harde schijf in de reeks opnemen die bij -een storing de plaats zal innemen van de defecte schijf. - - - - - -RAID5 - -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 -pariteitsinformatie 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. - - - -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 . - - - - - -Samenvattend: - - - - - - Type - Minimum apparaten - Reserve schijf - Overleeft een storing? - Beschikbare ruimte - - - - - - RAID0 - 2 - nee - nee - Grootte van de kleinste partitie vermenigvuldigd met het aantal apparaten - - - - RAID1 - 2 - optioneel - ja - Grootte van de kleinste partitie in de RAID - - - - RAID5 - 3 - naar keuze - ja - - Grootte van de kleinste partitie vermenigvuldigd met - (het aantal apparaten in de RAID minus één) - - - - - - - -Als u meer wilt weten over Software-RAID, raadpleeg dan de -Software RAID HOWTO. - - - -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 partman in het menu met partitie -instellingen. Daar selecteert u Gebruiken -als: Fysiek volume voor RAID. - - - -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 (/). Ervaren gebruikers kunnen -proberen om deze problemen op te lossen door bepaalde configuratie- of -installatiestappen handmatig uit te voeren vanuit een opdrachtschil. - - - -Vervolgens dient u in het hoofdmenu van partman -te kiezen voor Software-RAID instellen. -(N.B. Dit menu verschijnt pas nadat u tenminste één partitie heeft -gemarkeerd voor gebruik als Fysiek volume voor -RAID.) -Kies dan op het eerste scherm van mdcfg voor -MD-apparaat aanmaken. 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. - - - - - - -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. - - - - -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. - - - - -De configuratieprocedure voor RAID5 is vergelijkbaar met die voor RAID1. -Het enige verschil is dat u tenminste 3 actieve -partities dient te gebruiken. - - - - - - -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 /home). - - - -Nadat u de MD-apparaten naar uw tevredenheid heeft ingesteld, kunt u -mdcfg afsluiten om terug te keren naar -partman om op uw nieuwe MD-apparaten bestandssystemen -aan te maken en daaraan de gebruikelijke kenmerken, zoals aanhechtpunten, -toe te kennen. - - - diff --git a/nl/using-d-i/modules/mips/arcboot-installer.xml b/nl/using-d-i/modules/mips/arcboot-installer.xml deleted file mode 100644 index 2e522562e..000000000 --- a/nl/using-d-i/modules/mips/arcboot-installer.xml +++ /dev/null @@ -1,69 +0,0 @@ - - - - - <command>arcboot</command>-installer - - -The boot loader on SGI machines is arcboot. -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 /etc/arcboot.conf. Each -configuration has a unique name, -the default setup as created by the installer is linux. -After arcboot has been installed, the system can be booted from hard disk -by setting some firmware environment variables entering - - - setenv SystemPartition scsi(scsi)disk(disk)rdisk(0)partition(0) - setenv OSLoadPartition scsi(scsi)disk(disk)rdisk(0)partition(partnr) - setenv OSLoader arcboot - setenv OSLoadFilename config - setenv AutoLoad yes - - -on the firmware prompt, and then typing boot. - - - - - - scsi - - -is the SCSI bus to be booted from, this is 0 -for the onboard controllers - - - - - disk - - -is the SCSI ID of the hard disk on which arcboot is -installed - - - - - partnr - - -is the number of the partition on which -/etc/arcboot.conf resides - - - - - config - - -is the name of the configuration entry in -/etc/arcboot.conf, which is linux by -default. - - - - - - diff --git a/nl/using-d-i/modules/mipsel/colo-installer.xml b/nl/using-d-i/modules/mipsel/colo-installer.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/nl/using-d-i/modules/mipsel/colo-installer.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/netcfg.xml b/nl/using-d-i/modules/netcfg.xml deleted file mode 100644 index 4cf6211e7..000000000 --- a/nl/using-d-i/modules/netcfg.xml +++ /dev/null @@ -1,57 +0,0 @@ - - - - Het netwerk configureren - - - -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 - interfaces -5 . - - - -Tijdens een standaardinstallatie zal &d-i; proberen uw netwerkinterface -automatisch met behulp van DHCP in te stellen. Er zijn verschillende -redenen waarom dit zou kunnen falen, variërend van het niet aangesloten -zijn van de netwerkkabel tot een onjuiste DHCP-configuratie. Ook is het -mogelijk dat er helemaal geen DHCP-server in uw lokale netwerk aanwezig -is. Voor nadere diagnose kunt u de boodschappen op de vierde console -raadplegen. In elk geval zal u worden gevraagd of u een nieuwe poging wilt -wagen of dat u het netwerk handmatig wilt configureren. DHCP-servers -kunnen soms zeer traag zijn; probeer het dus nogmaals als u zeker weet dat -alles juist is ingesteld. - - - -Bij handmatige configuratie van de netwerkinterface, zal u een aantal -vragen worden gesteld over uw netwerk, te weten: -IP-adres, -Netwerkmasker, -Gateway, -Adressen van naamservers, en -Computernaam. -Als u beschikt over een draadloos netwerkapparaat, zal u worden gevraagd -naar de ESSID van uw draadloos netwerk -en de WEP sleutel. Voer de waarden in -die u heeft verzameld bij . - - - -De volgende technische details kunnen mogelijk van pas komen (of niet). -Het programma gaat ervan uit dat het IP-adres van uw netwerk het resultaat -is van een bit-gewijze AND-operatie van het IP-adres van uw systeem en het -netwerkmasker. Het standaard Broadcast-adres wordt berekend als het resultaat -van een bit-gewijze OR-operatie van het IP-adres van uw systeem en de -bitgewijze inverse van het netwerkmasker. Ook zal een default waarde voor een -standaard router (gateway) worden bepaald. Gebruik de staandaardwaarden van het -installatiesysteem als u de juiste waarden voor deze vragen niet kunt vinden; -u kunt ze, indien nodig, altijd nog wijzigen nadat de installatie is afgerond -door het bestand /etc/network/interfaces te wijzigen. - - - diff --git a/nl/using-d-i/modules/network-console.xml b/nl/using-d-i/modules/network-console.xml deleted file mode 100644 index edaee355f..000000000 --- a/nl/using-d-i/modules/network-console.xml +++ /dev/null @@ -1,110 +0,0 @@ - - - - Installeren over het netwerk - - - -Een van de meer interressante componenten is -network-console. 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 .) - - - -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 medium of op een andere wijze het hoofdmenu -zichtbaar te maken. Bij de optie Installatiemodules van CD -laden selecteert u network-console: Continue -installation remotely using SSH. De component is succesvol -geladen als in het hoofdmenu een nieuwe optie Installatie -verder van op afstand doorlopen via SSH aanwezig is. - - - -Voor installaties op &arch-title; is dit de standaard methode nadat -het netwerk is geconfigureerd. - - - -Nadat u deze nieuwe optie heeft geselecteerd, -zal uU zal 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 installer -met het wachtwoord dat u daarnet heeft ingevoerd. Een ander belangrijk -detail op dit scherm is de vingerafdruk van dit systeem. -U dient deze op een veilige manier beschikbaar te stellen aan degene die -de installatie op afstand zal vervolgen. - - - -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. - - - -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: - - -$ ssh -l installer nieuw_systeem - - -Hierbij is nieuw_systeem 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. - - - -Als u meerdere systemen achter elkaar installeert en deze hetzelfde IP-adres -of dezelfde systeemnaam krijgen, zal ssh weigeren om de -verbinding te maken. De reden is dat opeenvolgende systemen een andere -vingerafdruk zullen hebben, wat meestal een indicatie is van een -spoofing aanval. Als u er zeker van bent dat dit niet het -geval is, dient u de betreffende regel te verwijderen uit -~/.ssh/known_hosts waarna u een nieuwe poging kunt doen. - - - -Nadat u bent aangelogd zal een aanvangsscherm worden getoond met twee -opties genaamd Menu opstarten en -Shell opstarten. 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. - - - -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. - - - -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. - - - - diff --git a/nl/using-d-i/modules/nobootloader.xml b/nl/using-d-i/modules/nobootloader.xml deleted file mode 100644 index ee85f4942..000000000 --- a/nl/using-d-i/modules/nobootloader.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - Verder gaan zonder opstartlader - - - -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). - - - -If you plan to manually configure your bootloader, you should check the -name of the installed kernel in /target/boot. -You should also check that directory for the presence of an -initrd; 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 / -filesystem and, if you chose to install /boot on a -separate partition, also your /boot filesystem. -Als u van plan bent om uw opstartlader handmatig te configureren, -adviseren wij om in /target/boot de naam van de -geïnstalleerde kernel te controleren. Daarnaast dient u diezelfde map te -controleren op de aanwezigheid van een initrd. -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 -/ bestandssysteem en, als u ervoor heeft gekozen om -/boot op een afzonderlijke partitie te installeren, -ook die voor uw /boot bestandssysteem. - - - diff --git a/nl/using-d-i/modules/os-prober.xml b/nl/using-d-i/modules/os-prober.xml deleted file mode 100644 index b51f8a16d..000000000 --- a/nl/using-d-i/modules/os-prober.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - - Andere besturingssystemen detecteren - - - -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. - - - -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. - - - diff --git a/nl/using-d-i/modules/partconf.xml b/nl/using-d-i/modules/partconf.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/partconf.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/partitioner.xml b/nl/using-d-i/modules/partitioner.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/nl/using-d-i/modules/partitioner.xml +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/nl/using-d-i/modules/partman-crypto.xml b/nl/using-d-i/modules/partman-crypto.xml deleted file mode 100644 index 233f98693..000000000 --- a/nl/using-d-i/modules/partman-crypto.xml +++ /dev/null @@ -1,355 +0,0 @@ - - - - - Configuring Encrypted Volumes - - -&d-i; allows you to set up encrypted partitions. Every file you write -to such a partition is immediately saved to the device in encrypted -form. Access to the encrypted data is granted only after entering -the passphrase used when the encrypted -partition was originally created. This feature is useful to protect -sensitive data in case your laptop or hard drive gets stolen. The -thief might get physical access to the hard drive, but without knowing -the right passphrase, the data on the hard drive will look like random -characters. - - - -The two most important partitions to encrypt are: the home partition, -where your private data resides, and the swap partition, where -sensitive data might be stored temporarily during operation. Of -course, nothing prevents you from encrypting any other partitions that might -be of interest. For example /var where database -servers, mail servers or print servers store their data, or -/tmp which is used by various programs to store -potentially interesting temporary files. Some people may even want to -encrypt their whole system. The only exception is -the /boot partition which must remain -unencrypted, because currently there is no way to load the kernel from -an encrypted partition. - - - -Please note that the performance of encrypted partitions will be -less than that of unencrypted ones because the data needs to be -decrypted or encrypted for every read or write. The performance impact -depends on your CPU speed, chosen cipher and a key length. - - - -To use encryption, you have to create a new partition by selecting -some free space in the main partitioning menu. Another option is to -choose an existing partition (e.g. a regular partition, an LVM logical -volume or a RAID volume). In the Partition settings -menu, you need to select physical volume for -encryption at the Use -as: option. The menu will then change to -include several cryptographic options for the partition. - - - -&d-i; supports several encryption methods. The default method -is dm-crypt (included in newer Linux kernels, -able to host LVM physical volumes), the other -is loop-AES (older, maintained separately from -the Linux kernel tree). Unless you have compelling reasons to do -otherwise, it is recommended to use the default. - - - - - -First, let's have a look at the options available when you select -Device-mapper (dm-crypt) as the encryption -method. As always: when in doubt, use the defaults, because -they have been carefully chosen with security in mind. - - - - -Encryption: aes - - - -This option lets you select the encryption algorithm -(cipher) which will be used to encrypt the data -on the partition. &d-i; currently supports the following block -ciphers: aes, blowfish, -serpent, and twofish. -It is beyond the scope of this document to discuss the qualities of -these different algorithms, however, it might help your decision to -know that in 2000, AES was chosen by the American -National Institute of Standards and Technology as the standard -encryption algorithm for protecting sensitive information in the 21st -century. - - - - - -Key size: 256 - - - -Here you can specify the length of the encryption key. With a larger -key size, the strength of the encryption is generally improved. On the -other hand, increasing the length of the key usually has a negative -impact on performance. Available key sizes vary depending on the -cipher. - - - - - -IV algorithm: cbc-essiv:sha256 - - - -The Initialization Vector or -IV algorithm is used in cryptography to ensure -that applying the cipher on the same clear text -data with the same key always produces a unique -cipher text. The idea is to prevent the -attacker from deducing information from repeated patterns in the encrypted -data. - - - -From the provided alternatives, the default -cbc-essiv:sha256 is currently the least -vulnerable to known attacks. Use the other alternatives only when you -need to ensure compatibility with some previously installed system -that is not able to use newer algorithms. - - - - - -Encryption key: Passphrase - - - -Here you can choose the type of the encryption key for this partition. - - - - Passphrase - - -The encryption key will be computed - - -Using a passphrase as the key currently means that the partition will -be set up using LUKS. - - on the basis of a passphrase which you will be able -to enter later in the process. - - - - - - Random key - - -A new encryption key will be generated from random data each time you -try to bring up the encrypted partition. In other words: on every -shutdown the content of the partition will be lost as the key is -deleted from memory. (Of course, you could try to guess the key with a -brute force attack, but unless there is an unknown weakness in the -cipher algorithm, it is not achievable in our lifetime.) - - - -Random keys are useful for swap partitions because you do not need to -bother yourself with remembering the passphrase or wiping sensitive -information from the swap partition before shutting down your -computer. However, it also means that you -will not be able to use -the suspend-to-disk functionality offered by newer -Linux kernels as it will be impossible (during a subsequent boot) to -recover the suspended data written to the swap partition. - - - - - - - - - -Erase data: yes - - - -Determines whether the content of this partition should be overwritten -with random data before setting up the encryption. This is recommended -because it might otherwise be possible for an attacker to discern -which parts of the partition are in use and which are not. In -addition, this will make it harder to recover any leftover data from -previous installations - -It is believed that the guys from three-letter agencies can restore -the data even after several rewrites of the magnetooptical media, -though. - -. - - - - - - - - -If you select Encryption method: -Loopback (loop-AES) , the menu -changes to provide the following options: - - - - -Encryption: AES256 - - - -For loop-AES, unlike dm-crypt, the options for cipher and key size are -combined, so you can select both at the same time. Please see the -above sections on ciphers and key sizes for further information. - - - - - -Encryption key: Keyfile (GnuPG) - - - -Here you can select the type of the encryption key for this partition. - - - - Keyfile (GnuPG) - - -The encryption key will be generated from random data during the -installation. Moreover this key will be encrypted -with GnuPG, so to use it, you will need to -enter the proper passphrase (you will be asked to provide one later in -the process). - - - - - - Random key - - -Please see the section on random keys above. - - - - - - - - - -Erase data: yes - - - -Please see the the section on erasing data above. - - - - - - - - -After you have selected the desired parameters for your encrypted -partitions, return back to the main partitioning menu. There should -now be a new menu item called Configure encrypted -volumes. After you select it, you will be asked to confirm -the deletion of data on partitions marked to be erased and possibly -other actions such as writing a new partition table. For large -partitions this might take some time. - - - -Next you will be asked to enter a passphrase for partitions configured -to use one. Good passphrases should be longer than 8 characters, -should be a mixture of letters, numbers and other characters and -should not contain common dictionary words or information easily -associable with you (such as birthdates, hobbies, pet names, names of -family members or relatives, etc.). - - - -Before you input any passphrases, you should have made sure that your -keyboard is configured correctly and generates the expected -characters. If you are unsure, you can switch to the second virtual -console and type some text at the prompt. This ensures that you won't be -surprised later, e.g. by trying to input a passphrase using a qwerty -keyboard layout when you used an azerty layout during the installation. -This situation can have several causes. Maybe you switched to another -keyboard layout during the installation, or the selected keyboard layout -might not have been set up yet when entering the passphrase for the -root file system. - - - -If you selected to use methods other than a passphrase to create -encryption keys, they will be generated now. Because the kernel may -not have gathered a sufficient amount of entropy at this early stage -of the installation, the process may take a long time. You can help -speed up the process by generating entropy: e.g. by pressing random -keys, or by switching to the shell on the second virtual console and -generating some network and disk traffic (downloading some files, -feeding big files into /dev/null, etc.). - - - -This will be repeated for each partition to be encrypted. - - - -After returning to the main partitioning menu, you will see all -encrypted volumes as additional partitions which can be configured in -the same way as ordinary partitions. The following example shows two -different volumes. The first one is encrypted via dm-crypt, the second -one via loop-AES. - - -Encrypted volume (sda2_crypt) - 115.1 GB Linux device-mapper - #1 115.1 GB F ext3 - -Loopback (loop0) - 515.2 MB AES256 keyfile - #1 515.2 MB F ext3 - - -Now is the time to assign mount points to the volumes and optionally -change the file system types if the defaults do not suit you. - - - -Pay attention to the identifiers in parentheses -(sda2_crypt -and loop0 in this case) and the mount -points you assigned to each encrypted volume. You will need this -information later when booting the new system. The differences between -the ordinary boot process and the boot process with encryption involved will -be covered later in . - - - -Once you are satisfied with the partitioning scheme, continue with the -installation. - - - diff --git a/nl/using-d-i/modules/partman-lvm.xml b/nl/using-d-i/modules/partman-lvm.xml deleted file mode 100644 index ca0c46716..000000000 --- a/nl/using-d-i/modules/partman-lvm.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - Logisch volumebeheer (LVM) instellen - - -Als u met computers werkt op het niveau van systeembeheerder of -gevorderde 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. - - - -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 fysieke volumes) combineren tot -een virtuele harde schijf (ofwel volumegroep); deze -kan op zijn beurt worden opgedeeld in virtuele partities (logische -volumes). Het nut hiervan is dat logische volumes (en natuurlijk -ook de onderliggende volumegroepen) verschillende fysieke harde schijven -kunnen omvatten. - - - -Als u bijvoorbeeld vervolgens ontdekt dat u meer ruimte nodig heeft op uw -oude 160GB /home 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 -/home 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 -LVM HOWTO te raadplegen. - - - -Het instellen van LVM in &d-i; is relatief eenvoudig en volledig ondersteund -in partman. Allereerst dient u de partitie(s) die u wilt -gebruiken als fysieke volumes voor LVM, te markeren. -Hiervoor selecteert u in partman -vanuit het menu Partitie-instellingen -de optie Gebruiken als: -Fysiek volume voor LVM . - - - -Als u terugkeert op het hoofdscherm van partman, zult u -een nieuwe optie Logisch volumebeheer (LVM) instellen. -Als u deze selecteert, zal u eerst worden gevraagd om nog niet vastgelegde -wijzigingen in de partitietabel te bevestigen (als die er zijn) en vervolgens -zal het configuratiemenu voor LVM worden getoond. Het menu is contextgevoelig -en toont alleen toegestane acties. De mogelijke acties zijn: - - - - Toon configuratiedetails: - toont onder andere de structuur van LVM-elementen en de namen en groottes - van logische volumes - - - Volumegroep aanmaken - - - Logisch volume aanmaken - - - Volumegroep verwijderen - - - Logisch volume verwijderen - - - Volumegroep uitbreiden - - - Volumegroep verkleinen - - - Einde: - keer terug naar het hoofdscherm van partman - - - - - -Gebruik de opties in dit menu om eerst een volume groep en vervolgens -daaronder de gewenste logische volumes. - - - -Als u wederom terugkeert op het hoofdscherm van partman, -zult u de aangemaakte logische volumes als ware het gewone partities -terugvinden in het menu (en u kunt ze verder ook als zodanig behandelen). - - - diff --git a/nl/using-d-i/modules/partman.xml b/nl/using-d-i/modules/partman.xml deleted file mode 100644 index 76389e9ed..000000000 --- a/nl/using-d-i/modules/partman.xml +++ /dev/null @@ -1,240 +0,0 @@ - - - - -Als u weinig ervaring heeft met het indelen van schijven of gewoon meer -gedetailleerde informatie wenst, kunt u -raadplegen. - - - -Allereerst zal u de gelegenheid worden geboden om een gehele harde schijf, -of (indien aanwezig) de beschikbare vrije ruimte op een schijf, automatisch -in te delen. -Dit wordt begeleide schijfindeling genoemd. Als u dit niet -wenst, kies dan de optie Schijfindeling handmatig -bepalen uit het menu. - - - - - Begeleide schijfindeling - - -Als u kiest voor begeleide schijfindeling, heeft u mogelijk twee opties: -de partities direct op de harde schijf aanmaken (de klassieke methode) of -gebruik maken van logisch volumebeheer (LVM). In het tweede geval zal het -installatiesysteem de meeste partities aanmaken binnen één grote overkoepelende -partitie; het voordeel van deze methode is dat de grootte van de partities -binnen die overkoepelende partitie relatief eenvoudig kan worden gewijzigd. -Merk op dat de optie om gebruik te maken van LVM niet op alle platforms -beschikbaar hoeft te zijn. - - - - -Als u kiest voor begeleide schijfindeling met gebruik van LVM, zal het -niet mogelijk zijn om wijzigingen in de partitietabel ongedaan te maken. -Met deze keuze worden effectief alle gegevens verwijderd die zich nu op -de harde schijf bevinden - - - - -Nadat u heeft gekozen voor begeleide schijfindeling (klassieke methode -danwel met gebruik van LVM), kunt u een keuze maken uit de schema's -weergegeven in onderstaande tabel. Elk van deze schema's -heeft zijn voor- en nadelen, waarvan een aantal wordt besproken in -. 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. - - - - - - - - Schema voor schijfindeling - Minimale ruimte - Aangemaakte partities - - - - - - Alles in één partitie - 600MB - /, swap - - Afzonderlijke /home partitie - 500MB - - /, /home, swap - - - Afzonderlijke /home, /usr, /var en /tmp partities - 1GB - - /, /home, - /usr, /var, - /tmp, swap - - - - - - - -Als u kiest voor begeleide schijfindeling met gebruik van LVM, dan zal het -installatiesysteem ook een afzonderlijke /boot partitie -aanmaken. Alle andere partities, met uitzondering van de wisselgeheugen (swap) -partitie, zullen worden aangemaakt in de LVM partitie. - - - -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. - - - -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. - - - -De partitie-indeling zou er als volgt uit kunnen zien: - - - IDE1 master (hda) - 6.4 GB WDC AC36400L - #1 primair 16.4 MB B f ext2 /boot - #2 primair 551.0 MB swap swap - #3 primair 5.8 GB ntfs - pri/log 8.2 MB VRIJE RUIMTE - - IDE1 slave (hdb) - 80.0 GB ST380021A - #1 primair 15.9 MB ext3 - #2 primair 996.0 MB fat16 - #3 primair 3.9 GB xfs /home - #5 logisch 6.0 GB f ext3 / - #6 logisch 1.0 GB f ext3 /var - #7 logisch 498.8 MB ext3 - #8 logisch 551.5 MB swap swap - #9 logisch 65.8 GB ext2 - - -Dit voorbeeld toont twee IDE harde schijven die zijn opgedeeld in -verschillende partities; de eerste schijf heeft nog vrije ruimte. Elke -regel voor een partitie bevat de volgende informatie: partitienummer, -type en grootte van de partitie, wijzigingindicatoren, het bestandssysteem -en het aanhechtpunt (indien aanwezig) voor de partitie. -Merk op dat de hier weergegeven indeling niet kan worden gerealiseerd met -behulp van begeleide schijfindeling; zij toont echter wel de flexibiliteit -die kan worden bereikt met handmatige schijfindeling. - - - - -Hiermee is de begeleide schijfindeling voltooid. Als u tevreden bent met de -voorgestelde indeling, kunt u de menuoptie Schijfindeling -afsluiten & veranderingen naar schijf schrijven 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 -Veranderingen aan partities ongedaan maken en de -begeleide schijfindeling nogmaals uit te voeren of om de voorgestelde indeling -te wijzigen zoals hieronder beschreven voor handmatige schijfindeling. - - - - - - Handmatige schijfindeling - - -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. - - - -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 VRIJE RUIMTE te verschijnen. - - - -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 Gebruiken als: 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 Klaar met -instellen van partitie waarna u terugkeert naar het hoofdmenu -van partman. - - - -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. - - - -Zorg ervoor dat u tenminste twee partities aanmaakt: één voor het -root-bestandssysteem (dat gekoppeld moet worden -aan het aanhechtpunt /) en één voor -swap. Als u vergeet om het root-bestandssysteem -aan te koppelen, zal partman u niet verder laten gaan -tot dit probleem is verholpen. - - - -Als u vergeet om een EFI-opstartpartitie te selecteren en formatteren, zal -partman dit signaleren en u beletten verder te gaan tot -u er een heeft toegewezen. - - - -De functionaliteit van partman 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 -partman-ext3, partman-xfs, -of partman-lvm) zijn geladen. - - - -Als u tevreden bent met het eindresultaat van de schijfindeling, kiest u -de menuoptie Schijfindeling afsluiten & veranderingen naar -schijf schrijven. 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. - - - diff --git a/nl/using-d-i/modules/pkgsel.xml b/nl/using-d-i/modules/pkgsel.xml deleted file mode 100644 index 408377216..000000000 --- a/nl/using-d-i/modules/pkgsel.xml +++ /dev/null @@ -1,70 +0,0 @@ - - - - Software selecteren en installeren - - - -Tijdens de installatie wordt de mogelijkheid geboden om aanvullende -programmatuur te installeren. In plaats van het selecteren van individuele -softwarepakketten uit de &num-of-distrib-pkgs; beschikbare pakketten, ligt -de nadruk tijdens deze fase van de installatie op het selecteren en installeren -van vooraf gedefinieerde verzamelingen van programmatuur waarmee uw computer -snel kan worden ingericht voor het uitvoeren van diverse taken. - - - -U heeft dus de mogelijkheid om allereerst taken te -selecteren en vervolgens daaraan individuele pakketten toe te voegen. -Globaal vertegenwoordigen deze taken verschillende doeleinden waarvoor u -uw computer zou kunnen gebruiken, zoals Desktopomgeving, -Webserver of Printserver - - - -Door base-config wordt om deze lijst te tonen het programma tasksel aangeroepen. Voor handmatige pakketselectie wordt -het programma aptitude 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 aptitude -install pakket uitvoeren, waarbij -pakket de naam is van het pakket dat u zoekt. - - - -. In is een overzicht opgenomen -van de voor de beschikbare taken benodigde ruimte. - - - -Nadat u de gewenste taken heeft geselecteerd, selecteert u Ok. -Vervolgens zal de installatie van de pakketten die behoren bij de door u -geselecteerde taken, plaatsvinden met behulp van aptitude. - - - -Bij de standaard gebruikersinterface van het installatiesysteem kunt u de -spatiebalk gebruiken een taak te (de)selecteren. - - - - - -Merk op dat sommige taken reeds automatisch geselecteerd kunnen zijn -(afhankelijk van eigenschappen van het systeem waarop de installatie wordt -uitgevoerd). Als u het met deze selectie niet eens bent, kunt u deze ongedaan -maken. U kunt er zelfs voor kiezen om geen enkele taak te installeren. - - - - - -Elk pakket dat u met behulp van tasksel heeft -geselecteerd, wordt gedownload, uitgepakt en vervolgens geïnstalleerd -door achtereenvolgens de programma's apt-get en -dpkg. Als een bepaald programma aanvullende informatie -van de gebruiker nodig heeft, zal hierom tijdens dit proces worden -gevraagd. - - - diff --git a/nl/using-d-i/modules/powerpc/quik-installer.xml b/nl/using-d-i/modules/powerpc/quik-installer.xml deleted file mode 100644 index ed6aa6a60..000000000 --- a/nl/using-d-i/modules/powerpc/quik-installer.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - - Install <command>Quik</command> on a Hard Disk - - -The boot loader for OldWorld Power Macintosh machines is -quik. You can also use it on CHRP. The installer -will attempt to set up quik automatically. The -setup has been known to work on 7200, 7300, and 7600 Powermacs, and on -some Power Computing clones. - - - diff --git a/nl/using-d-i/modules/powerpc/yaboot-installer.xml b/nl/using-d-i/modules/powerpc/yaboot-installer.xml deleted file mode 100644 index fdbf1edcb..000000000 --- a/nl/using-d-i/modules/powerpc/yaboot-installer.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - Install <command>Yaboot</command> on a Hard Disk - - -Newer (mid 1998 and on) PowerMacs use yaboot as -their boot loader. The installer will set up yaboot -automatically, so all you need is a small 820k partition named -bootstrap with type -Apple_Bootstrap created back in the partitioning -component. If this step completes successfully then your disk should -now be bootable and OpenFirmware will be set to boot &debian-gnu;. - - - diff --git a/nl/using-d-i/modules/s390/dasd.xml b/nl/using-d-i/modules/s390/dasd.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/s390/dasd.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/s390/netdevice.xml b/nl/using-d-i/modules/s390/netdevice.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/nl/using-d-i/modules/s390/netdevice.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/nl/using-d-i/modules/s390/zipl-installer.xml b/nl/using-d-i/modules/s390/zipl-installer.xml deleted file mode 100644 index 61aa6465c..000000000 --- a/nl/using-d-i/modules/s390/zipl-installer.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - <command>zipl</command>-installer - - -The boot loader on &arch-title; is zipl. -ZIPL is similar in configuration and usage to -LILO, with a few exceptions. Please take a look at -LINUX for &arch-title; Device Drivers and Installation -Commands from IBM's developerWorks web site if you want to -know more about ZIPL. - - - diff --git a/nl/using-d-i/modules/save-logs.xml b/nl/using-d-i/modules/save-logs.xml deleted file mode 100644 index 7c0c1fe1a..000000000 --- a/nl/using-d-i/modules/save-logs.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - De logbestanden van de installatie bewaren - - - -Als de installatie succesvol is, worden de logbestanden die tijdens -het installatieproces zijn aangemaakt, automatisch opgeslagen in de -map /var/log/debian-installer/ op uw nieuwe -&debian; systeem. - - - -De optie Debug-logbestanden opslaan in -het hoofdmenu biedt u de mogelijkheid om de logbestanden op een -diskette, via het netwerk, op harde schijf of op een ander medium te -bewaren. Dit kan nuttig zijn als u onoverkomelijke problemen tegenkomt -tijdens de installatie en u de logbestanden op een ander systeem wilt -bestuderen of u ze wilt meesturen met een installatierapport. - - - diff --git a/nl/using-d-i/modules/shell.xml b/nl/using-d-i/modules/shell.xml deleted file mode 100644 index 356b3cfaa..000000000 --- a/nl/using-d-i/modules/shell.xml +++ /dev/null @@ -1,42 +0,0 @@ - - - - Een shell gebruiken en de logs bekijken - - - -In het hoofdmenu is een optie Een shell openen -aanwezig. Als het menu niet beschikbaar is op het moment dat u gebruik -wilt maken van een shell, kunt u op Linker Alt -F2 (op een Mac-toetsenbord: -Option F2) indrukken -om naar de tweede virtuele terminal te schakelen. Dat -wil zeggen de toets Alt (links van de -spatiebalk) en de functietoets F2 -tegelijkertijd indrukken. Dit is een afzonderlijk scherm waarin de shell -ash, een kloon van de Bourne-shell, draait - - - -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 ls /bin /sbin -/usr/bin /usr/sbin te geven en door help -te typen. De tekstverwerker is nano. De shell heeft een -aantal aardige functies zoals het automatisch voltooien van commando's en -bestandsnamen en een opdrachthistorie. - - - - -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 Linker Alt -F1 om terug te keren naar de menu's, of type -exit, als u de shell heeft gestart met de menuoptie. - - - diff --git a/nl/using-d-i/modules/sparc/silo-installer.xml b/nl/using-d-i/modules/sparc/silo-installer.xml deleted file mode 100644 index 3ce2b6ac6..000000000 --- a/nl/using-d-i/modules/sparc/silo-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - Install the <command>SILO</command> Boot Loader - on a Hard Disk - - -The standard &architecture; boot loader is called silo. -It is documented in -/usr/share/doc/silo/. SILO is -similar in configuration and usage to LILO, with -a few exceptions. First of all, SILO allows you to -boot any kernel image on your drive, even if it is not listed in -/etc/silo.conf. This is because -SILO can actually read Linux partitions. Also, -/etc/silo.conf is read at boot time, so there is -no need to rerun silo after installing a new kernel -like you would with LILO. SILO -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. - - - diff --git a/nl/using-d-i/modules/tzsetup.xml b/nl/using-d-i/modules/tzsetup.xml deleted file mode 100644 index d68fc5300..000000000 --- a/nl/using-d-i/modules/tzsetup.xml +++ /dev/null @@ -1,54 +0,0 @@ - - - - -Afhankelijk van de eerder geselecteerde locatie, kan een keuzelijst met -tijdzones relevant voor die lokatie worden getoond. Als voor uw locatie -slechts één tijdzone relevant is, zal niets worden gevraagd maar wordt -de betreffende tijdzone automatisch ingesteld. - - - -Als u, om wat voor reden dan ook, een tijdzone wilt instellen die -niet past bij de geselecteerde locatie, dan zijn er -twee opties. - - - - - - - - -De meest eenvoudige optie is om gewoon een andere tijdzone in te stellen -nadat de installatie is afgerond en u uw nieuwe systeem heeft opgestart. -Het juiste commando hiervoor is: - - -# dpkg-reconfigure tzdata - - - - - - - - -Een alternatieve mogelijkheid is om de tijdzone helemaal aan het begin van -de installatie op te geven door de parameter -time/zone=waarde -mee te geven bij het opstarten van het installatiesysteem. -De waarde dient uiteraard een geldige tijdzone te zijn, zoals -Europe/Amsterdam of UTC. - - - - - - - - -Voor geautomatiseerde installaties kan de tijdzone ook worden ingesteld door -gebruikmaking van voorconfiguratie. - - diff --git a/nl/using-d-i/modules/user-setup.xml b/nl/using-d-i/modules/user-setup.xml deleted file mode 100644 index b39dba31e..000000000 --- a/nl/using-d-i/modules/user-setup.xml +++ /dev/null @@ -1,70 +0,0 @@ - - - - Het wachtwoord voor root instellen - - - -Het root-account wordt ook wel de -super-user 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. - - - -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. - - - - -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. - - - - - - - Een gewone gebruiker aanmaken - - - -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 niet de bedoeling dat u het root-account benut -voor dagelijks gebruik of als uw persoonlijke login. - - - -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 -Trojaans-paard 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. - - - -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. - - - -Als u op enig moment na de installatie nog een gebruikersaccount wilt -aanmaken, kunt u het commando adduser gebruiken. - - - diff --git a/nl/using-d-i/modules/x86/grub-installer.xml b/nl/using-d-i/modules/x86/grub-installer.xml deleted file mode 100644 index 9c654d539..000000000 --- a/nl/using-d-i/modules/x86/grub-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - Install the <command>Grub</command> Boot Loader - on a Hard Disk - - -The main &architecture; boot loader is called grub. -Grub is a flexible and robust boot loader and a good default choice for -new users and old hands alike. - - - -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. - - - -If you do not want to install grub, use the &BTN-GOBACK; button to get to the -main menu, and from there select whatever bootloader you would like to use. - - - diff --git a/nl/using-d-i/modules/x86/lilo-installer.xml b/nl/using-d-i/modules/x86/lilo-installer.xml deleted file mode 100644 index 89cc7f37e..000000000 --- a/nl/using-d-i/modules/x86/lilo-installer.xml +++ /dev/null @@ -1,67 +0,0 @@ - - - - - Install the <command>LILO</command> Boot Loader - on a Hard Disk - - -The second &architecture; boot loader is called LILO. -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 -/usr/share/doc/lilo/ if you have special needs; -also see the LILO mini-HOWTO. - - - - -Currently the LILO installation will only create menu entries for other -operating systems if these can be chainloaded. -This means you may have to manually add a menu entry for operating -systems like GNU/Linux and GNU/Hurd after the installation. - - - - -&d-i; offers you three choices on where to install the -LILO boot loader: - - - -Master Boot Record (MBR) - -This way the LILO will take complete control of the -boot process. - - - -new &debian; partition - -Choose this if you want to use another boot -manager. LILO will install itself at the beginning -of the new &debian; partition and it will serve as a secondary boot -loader. - - - -Other choice - -Useful for advanced users who want to install LILO -somewhere else. In this case you will be asked for desired -location. You can use traditional device names such as -/dev/hda or /dev/sda. - - - - - - -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 -fdisk /mbr 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;! - - - diff --git a/nl/using-d-i/using-d-i.xml b/nl/using-d-i/using-d-i.xml deleted file mode 100644 index 0cb8ec429..000000000 --- a/nl/using-d-i/using-d-i.xml +++ /dev/null @@ -1,418 +0,0 @@ - - - Het &debian; installatiesysteem gebruiken - - Hoe het installatiesysteem werkt - - -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. - - - -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. - - - -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. - - - - -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 -netcfg/disable_dhcp=true toevoegen. Zie - voor een overzicht van beschikbare opties. - - - -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 -priority=medium worden toegevoegd. - - - -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 expert modus. Dit is mogelijk door voor het opstarten -van het installatiesysteem ofwel het commando expert te -gebruiken ofwel de opstartparameter priority=low -toe te voegen. De expert modus geeft u volledige controle over &d-i;. - - - -Voor dit platform ondersteunt &d-i; twee verschillende gebruikersinterfaces: -een tekstuele en een graphische. Tenzij u in het initiële opstartmenu kiest -voor Graphical install zal de tekstuele interface worden -gebruikt. Zie voor nadere informatie over de -grafische versie van het installatiesysteem. - - - -Voor dit platform gebruikt het installatiesysteem een tekstuele -gebruikersinterface. Een grafische gebruikersinterface is momenteel niet -beschikbaar. - - - -Voor de tekstuele gebruikersinterface wordt gebruik van een muis niet -ondersteund. De volgende toetsen kunnen worden gebruikt om te navigeren binnen -de diverse configuratieschermen. Om vooruit of -terug te gaan tussen getoonde knoppen of selecties, gebruikt ui -de toetsen Tab of pijl rechts, respectievelijk -de Shift Tab of pijl -links. Met de pijlen -omhoog en omlaag 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 Pagina omhoog en Pagina omlaag -de lijst per pagina verschuiven. Met de spatiebalk selecteert u -opties, bijvoorbeeld bij een keuzevak. Gebruik &enterkey; om keuzes te activeren. - - - -S/390 ondersteunt geen virtuele consoles. U kunt echter een tweede en derde -ssh sessie openen om de hieronder beschreven logboeken te bekijken. - - - -Foutmeldingen worden omgeleid naar de vierde console. -U kunt toegang krijgen tot deze console door -op linker AltF4 -te drukken (houd de linker Alt toets vast terwijl u de -F4 functietoets indrukt); u keert terug naar het hoofd -installatiescherm met -linker AltF1. - - - -Deze meldingen kunnen ook worden teruggevonden in -/var/log/syslog. Na de installatie wordt dit logbestand -gekopieerd naar /var/log/installer/syslog op uw -nieuwe systeem. Andere installatiemeldingen kunnen tijdens de installatie worden -gevonden in /var/log/ en, nadat de computer opnieuw is -opgestart met het nieuwe systeem, in /var/log/installer/. - - - - - - Introductie van de modules - - -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 . - - - - - - - -main-menu -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. - - - -U kunt het hoofdmenu van het installatiesysteem bereiken door herhaaldelijk -de &BTN-GOBACK; knop te selecteren, waardoor u stapsgewijs teruggaat -uit de op dat moment actieve module. - - - - - -localechooser - -Stelt de gebruiker in staat om de lokalisatie te bepalen voor zowel -de installatie als het geïnstalleerde systeem: taal, locatie en -locale. 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. - - - - - -console-setup - -De module 'kbd-chooser' (toetsenbordkiezer) toont een lijst van toetsenborden -waaruit de gebruiker het model kan kiezen dat overeenkomt met zijn toetsenbord. - - - - - -hw-detect - -Detecteert automatisch de meeste hardware in het systeem, inclusief -netwerkkaarten, harde schijven en PCMCIA. - - - - - -cdrom-detect - -Zoekt naar en koppelt een &debian; installatie-CD. - - - - - -netcfg - -Configureert de netwerkverbindingen van de computer zodat deze verbinding kan maken -met het Internet. - - - - - -iso-scan - -Zoekt op harde schijven naar ISO-images (.iso bestanden). - - - - - -choose-mirror - -Deze module toont een overzicht van spiegelservers met het &debian; Archief. -De gebruiker kan hiermee de bron voor de installatie van &debian; pakketten kiezen. - - - - - -cdrom-checker - -Controleert de integriteit van een CD. Op die manier kan een gebruiker -zich ervan verzekeren dat de installatie-CD niet beschadigd is. - - - - - -lowmem - -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). - - - - - -anna - -Het acroniem 'anna' staat voor "Anna's Not Nearly APT". Deze module installeert -pakketten die zijn opgehaald vanaf de gekozen mirror of CD. - - - - - - -user-setup - -Stelt het wachtwoord voor het root account in en voegt een -account voor een normale gebruiker toe. - - - - - -clock-setup - -Stelt de interne systeem clock in en bepaalt of de deze is ingesteld op -UTC of niet. - - - - - -tzsetup - -Selecteert de tijdzone op basis van de eerder geselecteerde locatie. - - - - - -partman - -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. - - - - - - -partitioner - -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. - - - - - -partconf - -Toont een overzicht van partities en creëert bestandssystemen op de -geselecteerde partities volgens de instructies van de gebruiker. - - - - - -lvmcfg - -Helpt de gebruiker met het configureren van de LVM -('Logical Volume Manager'). - - - - - -mdcfg - -Stelt de gebruiker in staat om een Software RAID -('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. - - - - - - -base-installer - -Installeert een basisset van pakketten die het mogelijk maken om de -computer, nadat deze is herstart, onder &debian-gnu; te laten functioneren. - - - - - -apt-setup - -Verzorgt de configuratie van apt. Dit gebeurt grotendeels automatisch op -basis van de gebruikte installatiemethode. - - - - - -pkgsel - -Maakt gebruik van tasksel voor de selecte en -installatie van aanvullende programmatuur. - - - - - -os-prober - -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. - - - - - -bootloader-installer - -Installeert een opstartlader (boot loader) programma op de harde schijf. Dit -is noodzakelijk om de computer onder &arch-kernel; te laten opstarten zonder een -diskette of CD te gebruiken. Veel opstartladers kennen de mogelijkheid om -de gebruiker — elke keer dat de computer wordt opgestart — te -laten kiezen uit verschillende besturingssystemen. -De installatieprogramma's voor de diverse opstartladers installeren alle een -opstartlader op de harde schijf. Een opstartlader is noodzakelijk om de -computer onder Linux te laten opstarten zonder een diskette of CD te gebruiken. -Veel opstartladers kennen de mogelijkheid om de gebruiker — elke keer -dat de computer wordt opgestart — te laten kiezen uit alternatieve -besturingssystemen. - - - - - -shell - -Stelt de gebruiker in staat vanuit het menu of in de tweede console -een shell te starten. - - - - - - - -save-logs - -Stelt de gebruiker in staat om, wanneer problemen worden tegengekomen, -informatie op een diskette, via het netwerk, op harde schijf of op een -ander medium te bewaren. -Hiermee kan later een nauwkeurig verslag van problemen met het -installatiesysteem worden gestuurd aan de &debian; ontwikkelaars. - - - - - - - - -&using-d-i-components.xml; -&loading-firmware.xml; - - diff --git a/nl/welcome/about-copyright.xml b/nl/welcome/about-copyright.xml deleted file mode 100644 index b13e153dc..000000000 --- a/nl/welcome/about-copyright.xml +++ /dev/null @@ -1,96 +0,0 @@ - - - - -Over auteursrechten en softwarelicenties - - - -We're sure that you've read some of the licenses that come with most -commercial software — they usually say that you can only use one -copy of the software on a single computer. This system's license isn't -like that at all. We encourage you to put a copy of &debian-gnu; on every -computer in your school or place of business. Lend your installation -media to your friends and help them install it on their computers! -You can even make thousands of copies and sell -them — albeit with a few restrictions. Your freedom to install -and use the system comes directly from &debian; being based on -free software. - - - -Calling software free 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. - - - - -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 -contrib or non-free -areas of &debian; mirrors or on third-party CD-ROMs; see the -Debian FAQ, under -The Debian FTP archives, for more information about the -layout and contents of the archives. - - - - - - -Many of the programs in the system are licensed under the -GNU General Public License, -often simply referred to as the GPL. The GPL requires you to make -the source code 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 - - - -For information on how to locate, unpack, and build -binaries from &debian; source packages, see the -Debian FAQ, -under Basics of the Debian Package Management System. - - - for all such programs is available in the &debian; system. - - - -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 -/usr/share/doc/package-name/copyright - -once you've installed a package on your system. - - - -For more information about licenses and how &debian; determines whether -software is free enough to be included in the main distribution, see the -Debian Free Software Guidelines. - - - -The most important legal notice is that this software comes with -no warranties. 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. - - - diff --git a/nl/welcome/doc-organization.xml b/nl/welcome/doc-organization.xml deleted file mode 100644 index 9baab8ec1..000000000 --- a/nl/welcome/doc-organization.xml +++ /dev/null @@ -1,117 +0,0 @@ - - - - Indeling van dit document - - - -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. - - - -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. - - - -In het algemeen is deze handleiding lineair van opzet waardoor u van -begin tot einde door het installatieproces wordt geleid. Hieronder vindt -u de stappen voor de installatie van &debian-gnu;, en de secties van dit -document die met elke stap overeenkomen: - - - - -Bepaal of uw hardware voldoet aan de vereisten om het installatiesysteem -te kunnen gebruiken; zie . - - - - -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 . 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;. - - - - -In verkrijgt u de installatiebestanden -die noodzakelijk zijn voor de door u gekozen installatiemethode. - - - - - beschrijft het opstarten van de computer -in het installatiesysteem. Dit hoofdstuk beschrijft ook stappen die genomen -kunnen worden als u hierbij problemen ondervindt. - - - - -Voer de eigenlijke installatie uit zoals beschreven in . -Dit omvat de taalkeuze, het configureren van stuurmodules voor randapparaten, -het configureren van uw netwerkverbinding, het partitioneren van uw harde -schijf, de installatie van een basissysteem en vervolgens de selectie en -installatie van taken. Als u niet vanaf een CD installeert, wordt de -netwerkverbinding gebruikt om andere benodigde installatiebestanden direct -vanaf een &debian; server te downloaden. (Enige achtergrondinformatie over het -opzetten van de partities voor uw &debian; systeem is te vinden in -.) - - - - -Start de computer opnieuw op in uw zojuist geïnstalleerde basissysteem -met behulp van . - - - - - - -Wanneer u de installatie van uw systeem heeft voltooid, kunt u - lezen. Dat hoofdstuk legt uit waar u -aanvullende informatie over Unix en &debian; kunt vinden en hoe u uw kernel -kunt vervangen. - - - - - -Tot slot kunt u informatie over dit document en over hoe u hieraan kunt -bijdragen vinden in . - - - - - - Uw hulp bij het opstellen van documentatie is welkom - - - -Alle hulp, suggesties en (vooral) patches worden bijzonder gewaardeerd. -Ontwikkelversies van dit document zijn beschikbaar op -. Daar vindt u een overzicht van de -verschillende platformen en talen waarvoor dit document beschikbaar is. - - - -Ook de bronbestanden zijn vrij beschikbaar; zie -voor nader informatie over hoe u een bijdrage kunt leveren. -Suggesties, commentaar, patches en probleemrapporten worden verwelkomd -(gebruik het pakket installation-guide voor -probleemrapporten, maar controleer eerst of het probleem niet reeds -gerapporteerd is). - - - - diff --git a/nl/welcome/getting-newest-doc.xml b/nl/welcome/getting-newest-doc.xml deleted file mode 100644 index c1252d864..000000000 --- a/nl/welcome/getting-newest-doc.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - De meest recente versie van dit document verkrijgen - - - -Dit document wordt voortdurend gereviseerd. Wij adviseren om de -Debian &release; webpagina's -te raadplegen voor de meest recente informatie over de &release; versie -van het &debian-gnu; systeem. Bijgewerkte versies van deze installatie -handleiding zijn ook beschikbaar op de officiële -Installatiehandleiding webpagina's. - - - - diff --git a/nl/welcome/getting-newest-inst.xml b/nl/welcome/getting-newest-inst.xml deleted file mode 100644 index e81217be6..000000000 --- a/nl/welcome/getting-newest-inst.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - &debian; verkrijgen - - - -Voor informatie over hoe u &debian-gnu; kunt downloaden vanaf het Internet -of waar officiële &debian; CDs gekocht kunnen worden, verwijzen wij u naar de -distributie webpagina. -Op de lijst van Debian-mirrors -vindt u het complete overzicht van officiële &debian;-mirrors, zodat u -eenvoudig de dichtstbijzijnde kunt vinden. - - - -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. - - - - diff --git a/nl/welcome/welcome.xml b/nl/welcome/welcome.xml deleted file mode 100644 index 07d8232af..000000000 --- a/nl/welcome/welcome.xml +++ /dev/null @@ -1,25 +0,0 @@ - - -Welkom bij &debian; - - -Dit hoofdstuk biedt een overzicht over het &debian; Project en -&debian-gnu;. Als u reeds bekend bent met de geschiedenis van het -&debian; Project en van de &debian-gnu; distributie kunt u dit -hoofdstuk desgewenst overslaan. - - - -&what-is-debian.xml; -&what-is-linux.xml; -&what-is-debian-linux.xml; -&what-is-debian-kfreebsd.xml; -&what-is-debian-hurd.xml; -&getting-newest-inst.xml; -&getting-newest-doc.xml; -&doc-organization.xml; -&about-copyright.xml; - - - - diff --git a/nl/welcome/what-is-debian-hurd.xml b/nl/welcome/what-is-debian-hurd.xml deleted file mode 100644 index 7f1f3a3ef..000000000 --- a/nl/welcome/what-is-debian-hurd.xml +++ /dev/null @@ -1,26 +0,0 @@ - - - - - Wat is &debian; GNU/Hurd? - - - -&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. - - - -Voor meer informatie verwijzen wij naar de - -Debian GNU/Hurd webpagina -en de debian-hurd@lists.debian.org mailinglijst. - - - - diff --git a/nl/welcome/what-is-debian-kfreebsd.xml b/nl/welcome/what-is-debian-kfreebsd.xml deleted file mode 100644 index 82ab120e9..000000000 --- a/nl/welcome/what-is-debian-kfreebsd.xml +++ /dev/null @@ -1,26 +0,0 @@ - - - - What is &debian; GNU/kFreeBSD? - - - -&debian; GNU/kFreeBSD is a &debian; GNU system with the kFreeBSD kernel. - -This port of &debian; is currently only being developed for the i386 and amd64 -architectures, although ports to other architectures is possible. - -Please note that &debian; GNU/kFreeBSD is not a Linux system, and thus some -information on Linux system may not apply to it. - - - -For more information, see the - -Debian GNU/kFreeBSD ports page -and the debian-bsd@lists.debian.org -mailing list. - - - - diff --git a/nl/welcome/what-is-debian-linux.xml b/nl/welcome/what-is-debian-linux.xml deleted file mode 100644 index 8e78bd0bb..000000000 --- a/nl/welcome/what-is-debian-linux.xml +++ /dev/null @@ -1,86 +0,0 @@ - - - - Wat is &debian; GNU/Linux? - - - -De combinatie van de filosofie en methodologie van &debian; met de hulpprogramma's -van GNU, de Linux kernel en andere belangrijke vrije software, vormt een -unieke softwaredistributie die &debian; GNU/Linux wordt genoemd. Deze -distributie is opgebouwd uit een groot aantal pakketten. -Elk pakket in de distributie bevat uitvoerbare programma's, scripts, -documentatie en configuratie-informatie. Ook heeft elk pakket een -pakketbeheerder 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. - - - -&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. - - - -&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. - - - -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. - - - -&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. - - - -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. - - - -Om uw systeem te beschermen tegen Trojaanse paarden 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. - - - -De voornaamste (en beste) methode om ondersteuning te krijgen voor uw -&debian; GNU/Linux systeem en om te communiceren met &debian; ontwikkelaars, is -via de vele mailinglijsten die door het &debian; Project worden beheerd -(op dit moment meer dan &num-of-debian-maillists;). De meest eenvoudige -manier om u aan te melden voor één of meerdere van deze mailinglijsten -is door gebruik te maken van het -aanmeldingsformulier op onze website. - - - - - diff --git a/nl/welcome/what-is-debian.xml b/nl/welcome/what-is-debian.xml deleted file mode 100644 index ed0c14b26..000000000 --- a/nl/welcome/what-is-debian.xml +++ /dev/null @@ -1,116 +0,0 @@ - - - - Wat is Debian? - - - -Debian is een organisatie van uitsluitend vrijwilligers die toegewijd -is aan het ontwikkelen van vrije software en het bevorderen van -de idealen van de vrije software gemeenschap. -Het Debian Project is gestart in 1993 toen Ian Murdock een open uitnodiging -deed aan software ontwikkelaars om bij te dragen aan een complete en -samenhangende softwaredistributie, gebaseerd op de toen nog relatief nieuwe -Linux kernel. Die relatief kleine groep van toegewijde enthousiastelingen, -oorspronkelijk gefinancierd door de -Free Software Foundation, is, onder -invloed van de filosofie van GNU, over de -jaren uitgegroeid tot een organisatie van rond de &num-of-debian-developers; -Debian ontwikkelaars. - - - - -Debian ontwikkelaars zijn betrokken bij een scala aan activiteiten, waaronder -het beheer van Websites -en FTP-sites, -grafisch ontwerp, juridische analyse van softwarelicenties, het schrijven van -documentatie en, natuurlijk, het onderhouden van softwarepakketten. - - - -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: - - - - -Het Debian Sociaal Contract 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 -ontwikkelaar 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. - - - - - -De Debian Richtlijn voor Vrije Software - - -Engels: Debian Free Software Guidelines (DFSG) - - - 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 -The Open Source Definition. - - - - - -De Debian Policy Manual is een -uitgebreide specificatie van de kwaliteitsstandaarden van het Debian Project. - - - - - -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: - - - - -De Linux Standard Base (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). - - - - -De Filesystem Hierarchy Standard (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. - - - - -Debian Jr. is een eigen project dat -tot doel heeft zeker te stellen dat Debian ook onze jongste gebruikers iets -te bieden heeft. - - - - - - - -Voor meer algemene informatie over Debian verwijzen wij u naar de -Debian FAQ (veelgestelde vragen). - - - - diff --git a/nl/welcome/what-is-linux.xml b/nl/welcome/what-is-linux.xml deleted file mode 100644 index a6e444050..000000000 --- a/nl/welcome/what-is-linux.xml +++ /dev/null @@ -1,98 +0,0 @@ - - - - Wat is GNU/Linux? - - - -GNU/Linux is een besturingssysteem: een serie programma's die interactie -met uw computer en het uitvoeren van andere programma's mogelijk maken. - - - - -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 GNU/Linux -om te verwijzen naar systemen die door velen voor het gemak met Linux -worden aangeduid. - - - -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. - - - -De ontwikkeling van wat later GNU/Linux zou worden, begon in 1984 toen de -Free Software Foundation startte met -de ontwikkeling van een vrij Unix-achtig besturingssysteem, GNU genaamd. - - - -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). - - - -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. - - - -De Linux kernel verscheen -voor het eerst in 1991 toen Linus Torvalds, een Finse student Infromatica, -op de Usenet nieuwsgroep comp.os.minix een vroege versie -van een vervanger voor de Minix kernel aankondigde. - - - -Linus Torvalds coördineert, met de hulp van enkele vertrouwelingen, -nog altijd het werk van honderden ontwikkelaars. -Kernel Traffic -is een uitstekende wekelijkse samenvatting van discussies op de -linux-kernel mailinglijst. Nadere informatie over -de linux-kernel mailinglijst kan worden gevonden in de -linux-kernel mailinglijst FAQ. - - - -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. - - - - -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. - - - - diff --git a/po/nl/preface.po b/po/nl/preface.po new file mode 100644 index 000000000..0ceb41cd1 --- /dev/null +++ b/po/nl/preface.po @@ -0,0 +1,73 @@ +# Dutch translation of the Debian Installation Guide. +# Copyright (C) 2004-2006, 2012 The Debian Project. +# This file is distributed under the same license as the Debian Installation Guide. +# Frans Pop , 2004-2006. +# Jeroen Schot , 2012. +# +msgid "" +msgstr "" +"Project-Id-Version: d-i-manual/preface\n" +"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" +"POT-Creation-Date: 2012-06-16 09:12+0000\n" +"PO-Revision-Date: 2012-08-29 17:05+0200\n" +"Last-Translator: Jeroen Schot \n" +"Language-Team: Debian l10n Dutch \n" +"Language: nl\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: preface.xml:5 +#, no-c-format +msgid "Installing &debian-gnu; &release; For &architecture;" +msgstr "&debian-gnu; &release; installeren op &architecture;" + +#. Tag: para +#: preface.xml:6 +#, no-c-format +msgid "" +"We are delighted that you have decided to try &debian;, and are sure that " +"you will find that &debian;'s GNU/&arch-kernel; distribution is unique. " +"&debian-gnu; brings together high-quality free software from around the " +"world, integrating it into a coherent whole. We believe that you will find " +"that the result is truly more than the sum of the parts." +msgstr "" +"Wij zijn verheugd dat u heeft besloten om &debian; te proberen en weten " +"zeker dat u zult ontdekken dat de GNU/&arch-kernel; distributie van &debian; " +"uniekis. &debian-gnu; brengt vrije software van over de hele wereld samen en " +"integreert deze tot een samenhangend geheel. Wij zijn ervan overtuigd dat u " +"zult ontdekken dat het resultaat werkelijk meer is dan de som der delen." + +#. Tag: para +#: preface.xml:15 +#, no-c-format +msgid "" +"We understand that many of you want to install &debian; without reading this " +"manual, and the &debian; installer is designed to make this possible. If you " +"don't have time to read the whole Installation Guide right now, we recommend " +"that you read the Installation Howto, which will walk you through the basic " +"installation process, and links to the manual for more advanced topics or " +"for when things go wrong. The Installation Howto can be found in ." +msgstr "" +"Wij begrijpen dat velen onder u &debian; zal willen installeren zonder deze " +"handleiding te lezen en het &debian; installatiesysteem is ontworpen om dit " +"mogelijk te maken. Als u op dit moment geen gelegenheid heeft om de gehele " +"installatiehandleiding door te nemen, adviseren wij om tenminste de " +"\"Installatie Howto\" te lezen, die u meeneemt door het basis installatie " +"proces en verwijzingen bevat naar de handleiding voor meer geavanceerde " +"onderwerpen of als er dingen fout gaan. U vindt de Installatie Howto in " +"." + +#. Tag: para +#: preface.xml:25 +#, no-c-format +msgid "" +"With that said, we hope that you have the time to read most of this manual, " +"and doing so will lead to a more informed and likely more successful " +"installation experience." +msgstr "" +"Dat gezegd hebbend, hopen wij dat u de tijd wilt nemen om het merendeel van " +"deze handleiding door te lezen en dat dit zal leiden tot een beter " +"geïnformeerde en waarschijnlijk meer succesvolle installatie." -- cgit v1.2.3