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