From 325e7229b079ce8367df7a7571aad8bfc8e1e5a9 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Sat, 22 Aug 2009 15:52:14 +0000 Subject: Remove all untranslated documents for Danish --- da/administrivia/administrivia.xml | 125 ------ da/administrivia/contributors.xml | 183 -------- da/appendix/chroot-install.xml | 498 --------------------- da/appendix/example-preseed.xml | 321 -------------- da/appendix/files.xml | 214 --------- da/appendix/gpl.xml | 513 ---------------------- da/appendix/random-bits.xml | 10 - da/boot-installer/alpha.xml | 456 ------------------- da/boot-installer/arm.xml | 109 ----- da/boot-installer/boot-installer.xml | 28 -- da/boot-installer/ia64.xml | 462 ------------------- da/boot-installer/intro-cd.xml | 35 -- da/boot-installer/intro-hd.xml | 16 - da/boot-installer/intro-net.xml | 19 - da/boot-installer/m68k.xml | 349 --------------- da/boot-installer/mips.xml | 95 ---- da/boot-installer/parameters.xml | 300 ------------- da/boot-installer/powerpc.xml | 188 -------- da/boot-installer/s390.xml | 30 -- da/boot-installer/sparc.xml | 103 ----- da/boot-installer/trouble.xml | 194 -------- da/boot-installer/x86.xml | 426 ------------------ da/boot-new/boot-new.xml | 290 ------------ da/boot-new/modules/apt.xml | 97 ---- da/boot-new/modules/install.xml | 39 -- da/boot-new/modules/mta.xml | 93 ---- da/boot-new/modules/packages.xml | 128 ------ da/boot-new/modules/ppp.xml | 112 ----- da/boot-new/modules/shadow.xml | 69 --- da/boot-new/modules/timezone.xml | 30 -- da/hardware/hardware-supported.xml | 345 --------------- da/hardware/hardware.xml | 21 - da/hardware/installation-media.xml | 317 ------------- da/hardware/memory-disk-requirements.xml | 47 -- da/hardware/network-cards.xml | 214 --------- da/hardware/supported-peripherals.xml | 186 -------- da/hardware/supported/alpha.xml | 432 ------------------ da/hardware/supported/arm.xml | 96 ---- da/hardware/supported/hppa.xml | 17 - da/hardware/supported/i386.xml | 37 -- da/hardware/supported/ia64.xml | 3 - da/hardware/supported/m68k.xml | 39 -- da/hardware/supported/mips.xml | 52 --- da/hardware/supported/mipsel.xml | 146 ------ da/hardware/supported/powerpc.xml | 248 ----------- da/hardware/supported/s390.xml | 21 - da/hardware/supported/sparc.xml | 82 ---- da/howto/installation-howto.xml | 325 -------------- da/install-methods/automatic-install.xml | 88 ---- da/install-methods/boot-drive-files.xml | 176 -------- da/install-methods/boot-usb-files.xml | 188 -------- da/install-methods/create-floppy.xml | 108 ----- da/install-methods/download/alpha.xml | 36 -- da/install-methods/download/arm.xml | 37 -- da/install-methods/download/m68k.xml | 22 - da/install-methods/download/powerpc.xml | 28 -- da/install-methods/downloading-files.xml | 37 -- da/install-methods/floppy/i386.xml | 35 -- da/install-methods/floppy/m68k.xml | 29 -- da/install-methods/floppy/powerpc.xml | 119 ----- da/install-methods/install-methods.xml | 16 - da/install-methods/install-tftp.xml | 435 ------------------ da/install-methods/ipl-tape.xml | 24 - da/install-methods/official-cdrom.xml | 69 --- da/install-methods/tftp/bootp.xml | 78 ---- da/install-methods/tftp/dhcp.xml | 110 ----- da/install-methods/tftp/rarp.xml | 73 --- da/partitioning/device-names.xml | 161 ------- da/partitioning/partition-programs.xml | 182 -------- da/partitioning/partition/alpha.xml | 56 --- da/partitioning/partition/hppa.xml | 22 - da/partitioning/partition/ia64.xml | 129 ------ da/partitioning/partition/mips.xml | 17 - da/partitioning/partition/powerpc.xml | 55 --- da/partitioning/partition/sparc.xml | 33 -- da/partitioning/partition/x86.xml | 86 ---- da/partitioning/partitioning.xml | 13 - da/partitioning/schemes.xml | 84 ---- da/partitioning/sizing.xml | 52 --- da/partitioning/tree.xml | 135 ------ da/post-install/further-reading.xml | 44 -- da/post-install/kernel-baking.xml | 203 --------- da/post-install/new-to-unix.xml | 32 -- da/post-install/orientation.xml | 109 ----- da/post-install/post-install.xml | 12 - da/post-install/shutdown.xml | 25 -- da/preparing/backup.xml | 41 -- da/preparing/bios-setup/i386.xml | 331 -------------- da/preparing/bios-setup/m68k.xml | 23 - da/preparing/bios-setup/powerpc.xml | 56 --- da/preparing/bios-setup/s390.xml | 106 ----- da/preparing/bios-setup/sparc.xml | 99 ----- da/preparing/install-overview.xml | 185 -------- da/preparing/minimum-hardware-reqts.xml | 135 ------ da/preparing/needed-info.xml | 407 ----------------- da/preparing/non-debian-partitioning.xml | 204 --------- da/preparing/nondeb-part/alpha.xml | 92 ---- da/preparing/nondeb-part/m68k.xml | 127 ------ da/preparing/nondeb-part/powerpc.xml | 43 -- da/preparing/nondeb-part/sparc.xml | 44 -- da/preparing/nondeb-part/x86.xml | 119 ----- da/preparing/pre-install-bios-setup.xml | 148 ------- da/preparing/preparing.xml | 21 - da/using-d-i/components.xml | 158 ------- da/using-d-i/modules/alpha/aboot-installer.xml | 19 - da/using-d-i/modules/anna.xml | 2 - da/using-d-i/modules/autopartkit.xml | 2 - da/using-d-i/modules/base-installer.xml | 31 -- da/using-d-i/modules/baseconfig.xml | 17 - da/using-d-i/modules/cdrom-checker.xml | 2 - da/using-d-i/modules/cdrom-detect.xml | 2 - da/using-d-i/modules/choose-mirror.xml | 17 - da/using-d-i/modules/ddetect.xml | 2 - da/using-d-i/modules/finish-install.xml | 23 - da/using-d-i/modules/hppa/palo-installer.xml | 20 - da/using-d-i/modules/ia64/elilo-installer.xml | 135 ------ da/using-d-i/modules/iso-scan.xml | 47 -- da/using-d-i/modules/kbd-chooser.xml | 44 -- da/using-d-i/modules/lowmem.xml | 21 - da/using-d-i/modules/mdcfg.xml | 180 -------- da/using-d-i/modules/mips/arcboot-installer.xml | 2 - da/using-d-i/modules/mipsel/colo-installer.xml | 2 - da/using-d-i/modules/mipsel/delo-installer.xml | 80 ---- da/using-d-i/modules/netcfg.xml | 58 --- da/using-d-i/modules/nobootloader.xml | 17 - da/using-d-i/modules/os-prober.xml | 37 -- da/using-d-i/modules/partconf.xml | 2 - da/using-d-i/modules/partitioner.xml | 3 - da/using-d-i/modules/partman-lvm.xml | 58 --- da/using-d-i/modules/partman.xml | 193 -------- da/using-d-i/modules/powerpc/quik-installer.xml | 15 - da/using-d-i/modules/powerpc/yaboot-installer.xml | 17 - da/using-d-i/modules/s390/dasd.xml | 2 - da/using-d-i/modules/s390/netdevice.xml | 2 - da/using-d-i/modules/s390/zipl-installer.xml | 16 - da/using-d-i/modules/save-logs.xml | 23 - da/using-d-i/modules/shell.xml | 41 -- da/using-d-i/modules/sparc/silo-installer.xml | 25 -- da/using-d-i/modules/x86/grub-installer.xml | 26 -- da/using-d-i/modules/x86/lilo-installer.xml | 70 --- da/using-d-i/using-d-i.xml | 365 --------------- da/welcome/what-is-debian.xml | 113 ----- 142 files changed, 15388 deletions(-) delete mode 100644 da/administrivia/administrivia.xml delete mode 100644 da/administrivia/contributors.xml delete mode 100644 da/appendix/chroot-install.xml delete mode 100644 da/appendix/example-preseed.xml delete mode 100644 da/appendix/files.xml delete mode 100644 da/appendix/gpl.xml delete mode 100644 da/appendix/random-bits.xml delete mode 100644 da/boot-installer/alpha.xml delete mode 100644 da/boot-installer/arm.xml delete mode 100644 da/boot-installer/boot-installer.xml delete mode 100644 da/boot-installer/ia64.xml delete mode 100644 da/boot-installer/intro-cd.xml delete mode 100644 da/boot-installer/intro-hd.xml delete mode 100644 da/boot-installer/intro-net.xml delete mode 100644 da/boot-installer/m68k.xml delete mode 100644 da/boot-installer/mips.xml delete mode 100644 da/boot-installer/parameters.xml delete mode 100644 da/boot-installer/powerpc.xml delete mode 100644 da/boot-installer/s390.xml delete mode 100644 da/boot-installer/sparc.xml delete mode 100644 da/boot-installer/trouble.xml delete mode 100644 da/boot-installer/x86.xml delete mode 100644 da/boot-new/boot-new.xml delete mode 100644 da/boot-new/modules/apt.xml delete mode 100644 da/boot-new/modules/install.xml delete mode 100644 da/boot-new/modules/mta.xml delete mode 100644 da/boot-new/modules/packages.xml delete mode 100644 da/boot-new/modules/ppp.xml delete mode 100644 da/boot-new/modules/shadow.xml delete mode 100644 da/boot-new/modules/timezone.xml delete mode 100644 da/hardware/hardware-supported.xml delete mode 100644 da/hardware/hardware.xml delete mode 100644 da/hardware/installation-media.xml delete mode 100644 da/hardware/memory-disk-requirements.xml delete mode 100644 da/hardware/network-cards.xml delete mode 100644 da/hardware/supported-peripherals.xml delete mode 100644 da/hardware/supported/alpha.xml delete mode 100644 da/hardware/supported/arm.xml delete mode 100644 da/hardware/supported/hppa.xml delete mode 100644 da/hardware/supported/i386.xml delete mode 100644 da/hardware/supported/ia64.xml delete mode 100644 da/hardware/supported/m68k.xml delete mode 100644 da/hardware/supported/mips.xml delete mode 100644 da/hardware/supported/mipsel.xml delete mode 100644 da/hardware/supported/powerpc.xml delete mode 100644 da/hardware/supported/s390.xml delete mode 100644 da/hardware/supported/sparc.xml delete mode 100644 da/howto/installation-howto.xml delete mode 100644 da/install-methods/automatic-install.xml delete mode 100644 da/install-methods/boot-drive-files.xml delete mode 100644 da/install-methods/boot-usb-files.xml delete mode 100644 da/install-methods/create-floppy.xml delete mode 100644 da/install-methods/download/alpha.xml delete mode 100644 da/install-methods/download/arm.xml delete mode 100644 da/install-methods/download/m68k.xml delete mode 100644 da/install-methods/download/powerpc.xml delete mode 100644 da/install-methods/downloading-files.xml delete mode 100644 da/install-methods/floppy/i386.xml delete mode 100644 da/install-methods/floppy/m68k.xml delete mode 100644 da/install-methods/floppy/powerpc.xml delete mode 100644 da/install-methods/install-methods.xml delete mode 100644 da/install-methods/install-tftp.xml delete mode 100644 da/install-methods/ipl-tape.xml delete mode 100644 da/install-methods/official-cdrom.xml delete mode 100644 da/install-methods/tftp/bootp.xml delete mode 100644 da/install-methods/tftp/dhcp.xml delete mode 100644 da/install-methods/tftp/rarp.xml delete mode 100644 da/partitioning/device-names.xml delete mode 100644 da/partitioning/partition-programs.xml delete mode 100644 da/partitioning/partition/alpha.xml delete mode 100644 da/partitioning/partition/hppa.xml delete mode 100644 da/partitioning/partition/ia64.xml delete mode 100644 da/partitioning/partition/mips.xml delete mode 100644 da/partitioning/partition/powerpc.xml delete mode 100644 da/partitioning/partition/sparc.xml delete mode 100644 da/partitioning/partition/x86.xml delete mode 100644 da/partitioning/partitioning.xml delete mode 100644 da/partitioning/schemes.xml delete mode 100644 da/partitioning/sizing.xml delete mode 100644 da/partitioning/tree.xml delete mode 100644 da/post-install/further-reading.xml delete mode 100644 da/post-install/kernel-baking.xml delete mode 100644 da/post-install/new-to-unix.xml delete mode 100644 da/post-install/orientation.xml delete mode 100644 da/post-install/post-install.xml delete mode 100644 da/post-install/shutdown.xml delete mode 100644 da/preparing/backup.xml delete mode 100644 da/preparing/bios-setup/i386.xml delete mode 100644 da/preparing/bios-setup/m68k.xml delete mode 100644 da/preparing/bios-setup/powerpc.xml delete mode 100644 da/preparing/bios-setup/s390.xml delete mode 100644 da/preparing/bios-setup/sparc.xml delete mode 100644 da/preparing/install-overview.xml delete mode 100644 da/preparing/minimum-hardware-reqts.xml delete mode 100644 da/preparing/needed-info.xml delete mode 100644 da/preparing/non-debian-partitioning.xml delete mode 100644 da/preparing/nondeb-part/alpha.xml delete mode 100644 da/preparing/nondeb-part/m68k.xml delete mode 100644 da/preparing/nondeb-part/powerpc.xml delete mode 100644 da/preparing/nondeb-part/sparc.xml delete mode 100644 da/preparing/nondeb-part/x86.xml delete mode 100644 da/preparing/pre-install-bios-setup.xml delete mode 100644 da/preparing/preparing.xml delete mode 100644 da/using-d-i/components.xml delete mode 100644 da/using-d-i/modules/alpha/aboot-installer.xml delete mode 100644 da/using-d-i/modules/anna.xml delete mode 100644 da/using-d-i/modules/autopartkit.xml delete mode 100644 da/using-d-i/modules/base-installer.xml delete mode 100644 da/using-d-i/modules/baseconfig.xml delete mode 100644 da/using-d-i/modules/cdrom-checker.xml delete mode 100644 da/using-d-i/modules/cdrom-detect.xml delete mode 100644 da/using-d-i/modules/choose-mirror.xml delete mode 100644 da/using-d-i/modules/ddetect.xml delete mode 100644 da/using-d-i/modules/finish-install.xml delete mode 100644 da/using-d-i/modules/hppa/palo-installer.xml delete mode 100644 da/using-d-i/modules/ia64/elilo-installer.xml delete mode 100644 da/using-d-i/modules/iso-scan.xml delete mode 100644 da/using-d-i/modules/kbd-chooser.xml delete mode 100644 da/using-d-i/modules/lowmem.xml delete mode 100644 da/using-d-i/modules/mdcfg.xml delete mode 100644 da/using-d-i/modules/mips/arcboot-installer.xml delete mode 100644 da/using-d-i/modules/mipsel/colo-installer.xml delete mode 100644 da/using-d-i/modules/mipsel/delo-installer.xml delete mode 100644 da/using-d-i/modules/netcfg.xml delete mode 100644 da/using-d-i/modules/nobootloader.xml delete mode 100644 da/using-d-i/modules/os-prober.xml delete mode 100644 da/using-d-i/modules/partconf.xml delete mode 100644 da/using-d-i/modules/partitioner.xml delete mode 100644 da/using-d-i/modules/partman-lvm.xml delete mode 100644 da/using-d-i/modules/partman.xml delete mode 100644 da/using-d-i/modules/powerpc/quik-installer.xml delete mode 100644 da/using-d-i/modules/powerpc/yaboot-installer.xml delete mode 100644 da/using-d-i/modules/s390/dasd.xml delete mode 100644 da/using-d-i/modules/s390/netdevice.xml delete mode 100644 da/using-d-i/modules/s390/zipl-installer.xml delete mode 100644 da/using-d-i/modules/save-logs.xml delete mode 100644 da/using-d-i/modules/shell.xml delete mode 100644 da/using-d-i/modules/sparc/silo-installer.xml delete mode 100644 da/using-d-i/modules/x86/grub-installer.xml delete mode 100644 da/using-d-i/modules/x86/lilo-installer.xml delete mode 100644 da/using-d-i/using-d-i.xml delete mode 100644 da/welcome/what-is-debian.xml diff --git a/da/administrivia/administrivia.xml b/da/administrivia/administrivia.xml deleted file mode 100644 index 73f2a0b11..000000000 --- a/da/administrivia/administrivia.xml +++ /dev/null @@ -1,125 +0,0 @@ - - - - - Administrivia - - - - About This Document - - - -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 CVSWeb. 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 CVS, 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. - - - - - - - -&contributors.xml; - - - - 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 for 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. - - - -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. - - - - - - Trademark Acknowledgement - - -All trademarks are property of their respective trademark owners. - - - - - diff --git a/da/administrivia/contributors.xml b/da/administrivia/contributors.xml deleted file mode 100644 index a2cda7413..000000000 --- a/da/administrivia/contributors.xml +++ /dev/null @@ -1,183 +0,0 @@ - - - - Acknowledgements and Thanks - - -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. - - - -Listed below are contributors to both parent manuals, and the current -manual. If you've been left out somehow, please let us know. - - - -Debian-installer Documentation - - -Chris Tillman -Miroslav Kuře -Joey Hess -Sebastian Ley - -
- -Boot-floppies Documentation - - -Bruce Perens -Sven Rudolph -Igor Grobman -James Treacy -Adam Di Carlo -Chris Tillman -Denis Barbier -Marc Herbert -Richard Hirst -Karl M. Hegbloom - -
- -Progeny Documentation - - -Ian Murdock -Bruce Byfield -C. Stephen Gunn -Pat Ouellette -John Daily -John Hartman -Doug Porter -Dean Esmay -Keith Hartman -Branden Robinson -Bern Galvin -Steve Hunger -Steve Schafer -Aaron Stenhoff -Eric Gillespie -Andrew J. Korty -John Goerzen -Jeff Licquia -Michael Schultheiss -Adam Lazur -Kevin Mathews - -
- -Translators - - -Bulgarian:George Tchavdarov -Catalan:Jordi Mallach -Antoni Bella Pérez -Ingrid C. Peiró -Lluis Vilanova -Pau (aka pdl) -Xavi Drudis Ferran -Ivan Vilata i Balaguer -Chinese:malix -Chuan-kai Lin -Croatian:Matej Vela -Josip Rodin -Czech:Pavel Makovec -Jiří Mašík -Vilém Vychodil -Miroslav Kuře -Petr Vaněk -Danish:Claus Hindsgaul -Dutch:Luk Claes -Bart Cornelis -Frans Pop -Wouter Verhelst -Bas Zoetekouw -Esperanto:Edmund Grimley Evans -Finnish:Tapio Lehtonen -Antti-Juhani Kaijanaho -French:Christophe Le Bars -Vincent Renardias -Eric Van Buggenhaut -Martin Quinson -Pierre Machard -Galician:Jacobo Tarrio -German:Hartmut Koptein -Martin Schulze -Philipp Stratmann -Joerg Friedrich -Gerd Bavendiek -Peter Ganten -Michael Bramer -Torsten Landschoff -Greek:Konstantinos Margaritis -George Papamichelakis -Hungarian:Gergely Risko -Italian:Michele Dalla Silvestra -Paolo Didonè -Riccardo Fabris -Giuseppe Sacco -Japanese:Yoshizumi Endo -Atsushi Kamoshida -Junichi Uekawa -Tsutomu Saito -NAKANO, Takeo -KISE Hiroshi -Mitsuru Oka -NABETANI Hidenobu -Masayuki Hatta -Guangcheng Wen -Nobuhiro IMAI -Tomohiro KUBOTA -KURASAWA Nozomu -SUGIYAMA Tomoaki -TAKEI Nobumitsu -Polish:Piotr Pogorzelski -Marcin Owsiany -Portuguese:Gleydson Mazioli da Silva -Paulo Henrique B. Oliveira -André Luís Lopes -Luis Alberto Garcia Cipriano -Paulo Rogério Ormenese -Marcio Roberto Teixeira -Rafael Laboissiere -Russian:Mikhail Sobolev -Alexey Vyskubov -Aleksey Novodvorsky -Peter Novodvorsky -Paul Romanchenko -Ilgiz Kalmetev -Max V. Kosmach -Slovak:Miroslav Vaško -Spanish:Enrique Zanardi -Fernando Herrera -Sergio Gómez Bachiller -Gonzalo G. Agulló -Ignacio J. Alonso -Tinguaro Barreno -Pedro Gracia -Angel David Rancel Mendoza -Javier Fernández-Sanguino -David Martinez -Ricardo J. Cárdenes -Jose Carlos García -Javier Carranza -Miguel A. Arévalo -Fermín García-Herreros -Javier Linares -Manolo Romero -Gabriel Rodríguez -Santiago Vila -Ricardo Cárdenes -David Moreno Garza -Rudy Godoy -Bruno Barrera -Rubén Porras Campo -Swedish:Nils-Erik Svangård -Peter Karlsson - -
- - diff --git a/da/appendix/chroot-install.xml b/da/appendix/chroot-install.xml deleted file mode 100644 index 104e156ec..000000000 --- a/da/appendix/chroot-install.xml +++ /dev/null @@ -1,498 +0,0 @@ - - - - - Installing &debian; from a Unix/Linux System - - - -This section explains how to install &debian; from an existing -Unix or Linux system, without using the ncurses-based, menu-driven -installer as explained in the rest of the manual. This "cross-install" -HOWTO has been requested by users switching to &debian; from -Redhat, 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 - - - - - - - - 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, but -otherwise depends only on /bin/sh. Install -wget if it isn'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 -xf debootstrap_0.X.X_arch.deb - $ cd / - $ zcat < /full-path-to-work/work/data.tar.gz | tar xv - - - - - - - - Run <command>debootstrap</command> - - -debootstrap can download the needed files directly -from the archive when you run it. You can substitute any Debian -archive mirror for 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 sarge \ - /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: - - - - $ 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 / ext2 defaults 0 0 -/dev/XXX /boot ext2 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 ext2 rw,nosuid,nodev 0 2 -/dev/XXX /var ext2 rw,nosuid,nodev 0 2 -/dev/XXX /usr ext2 rw,nodev 0 2 -/dev/XXX /home ext2 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 - - - - - - - - - Configure Keyboard - - - -To configure your keyboard: - - - - # dpkg-reconfigure console-data - - - - - - - - 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 localisation 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=/boot/boot-menu.b -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/da/appendix/example-preseed.xml b/da/appendix/example-preseed.xml deleted file mode 100644 index 0773c6829..000000000 --- a/da/appendix/example-preseed.xml +++ /dev/null @@ -1,321 +0,0 @@ - - - - -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. - - - - -#### Modifying syslinux.cfg. - -# Edit the syslinux.cfg (or similar) file, and add parameters to the end -# of the append line(s) for the kernel. -# -# You'll at least want to add a parameter telling the installer where to -# get its preseed file from. -# 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're netbooting, use this instead: -# preseed/url=http://host/path/to/preseed -# If you're remastering a CD, you could use this: -# preseed/file=/cdrom/preseed -# Be sure to copy this file to the location you specify. -# -# 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. -# -# Language, country, and keyboard selection cannot be preseeded from a file, -# because the questions are asked before the preseed file can be loaded. -# Instead, to avoid these questions, pass some more parameters to the kernel: -# -# languagechooser/language-name=English -# countrychooser/shortlist=US -# console-keymaps-at/keymap=us - -#### 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 wget http://url/to/my.udeb -O /tmp/my.udeb ; udpkg -i /tmp/my.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 for deb in /hd-media/*.deb; do cp $deb /target/tmp; chroot /target dpkg -i /tmp/$(basename $deb); done -# 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 - -#### 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 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 -# precidence 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/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 finish-install/reboot_in_progress note - - -##### Preseeding base-config. -# XXX: Note that most of this will not work right until base-config 2.40.4 -# is available. - -# Avoid the intorductory 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 - -###### Time zone setup. - -# Controls whether or not the hardware clock is set to GMT. -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. Note that the username -# will be derived from this; it cannot be overridden currently. The -# username will be the (lowercase) first name of the full name. -#passwd passwd/user-fullname string Debian User -#passwd passwd/username string -# 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, 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. -# XXX: this will not work until tasksel 2.12 is available -tasksel tasksel/first multiselect Desktop environment -#tasksel tasksel/first multiselect Web server, Mail server, DNS server - -###### Mailer configuration. - -# During a normal install, exim asks only two 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 -# 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 a 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 flexably, 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 - - - diff --git a/da/appendix/files.xml b/da/appendix/files.xml deleted file mode 100644 index 7637513a3..000000000 --- a/da/appendix/files.xml +++ /dev/null @@ -1,214 +0,0 @@ - - - - - Linux Devices - - -In Linux you have various special files in -/dev. These files are called devices 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 - -user@debian:# /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 sarge installation for i386, including all standard packages, -requires 178MB 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 the numbers up. - - - - -Task Installed Download Space Needed - Size (MB) Size (MB) To Install (MB) - -Desktop 1537 521 2058 -Web server 71 21 92 -Print server 240 83 323 -Mail server 41 12 53 -File server 85 34 119 -SQL database 108 33 141 - - - - diff --git a/da/appendix/gpl.xml b/da/appendix/gpl.xml deleted file mode 100644 index 66dc64386..000000000 --- a/da/appendix/gpl.xml +++ /dev/null @@ -1,513 +0,0 @@ - - - -GNU General Public License - - - -Version 2, June 1991 - - - -Copyright (C) 1989, 1991 Free Software Foundation, Inc. -— -59 Temple Place - Suite 330, Boston, MA 02111-1307, 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., 59 Temple Place, Suite 330, Boston, MA 02111-1307 -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/da/appendix/random-bits.xml b/da/appendix/random-bits.xml deleted file mode 100644 index 5dc521dc9..000000000 --- a/da/appendix/random-bits.xml +++ /dev/null @@ -1,10 +0,0 @@ - - - -Random Bits - -&example-preseed.xml; -&files.xml; -&chroot-install.xml; - - diff --git a/da/boot-installer/alpha.xml b/da/boot-installer/alpha.xml deleted file mode 100644 index 76efb0f86..000000000 --- a/da/boot-installer/alpha.xml +++ /dev/null @@ -1,456 +0,0 @@ - - - - - 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 with MS-DOS partition tables. -Specifically, the bootsector format required by the Console -Subsystem Specification conflicts with the placement of the DOS -partition table. Since Tru64 Unix uses the BSD disklabel format, -this is the ``native'' partition format for SRM installations. - - - -Because GNU/Linux is the only operating system on Alpha that can be -booted from both console types, the choice will also depend on what -other operating systems you wish to run on the same machine. All -other Unix-like operating systems (Tru64 Unix, FreeBSD, OpenBSD, and -NetBSD) and OpenVMS can only boot from SRM, whereas Windows NT can -only boot from ARC. - - - -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 only (see motherboard manual) - - 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 or SRM - - - - - - - - -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 - - - - - -The UP1000 motherboard (subarchitecture name `nautilus') from Alpha -Processor, Inc. is different from all the others, in that it uses an -API-specific bootloader that runs under AlphaBIOS firmware. - - - -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. For example, to boot from -ewa0 and use a console on the first serial -port, you would type: - - - ->>> boot ewa0 -flags 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 from Floppies with the APB Boot Loader (UP1000) - - - -To boot on this platform, run \apb\apb.exe from the -`Utility/Run Maintenance Program' menu, and type - - -boot debian_install - - - at the APB prompt. - - - - - 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/da/boot-installer/arm.xml b/da/boot-installer/arm.xml deleted file mode 100644 index fadc600e3..000000000 --- a/da/boot-installer/arm.xml +++ /dev/null @@ -1,109 +0,0 @@ - - - - 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 tftpboot.img - NeTTrom command-> save-all - NeTTrom command-> setenv netconfig_eth0 flash - NeTTrom command-> setenv kernconfig tftp - - - - - -Only the last two of these interfere with normal disk booting, so it is -safe to save-all right before it, which will -store the network settings in case you need to boot from the network -again. Use the printenv command to review your -environment settings. Finally, if your cmdappend -NeTTrom variable has the option (which is -necessary to boot 2.4 kernels), 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/da/boot-installer/boot-installer.xml b/da/boot-installer/boot-installer.xml deleted file mode 100644 index b98b4c6dd..000000000 --- a/da/boot-installer/boot-installer.xml +++ /dev/null @@ -1,28 +0,0 @@ - - - -Booting the Installation System - - Booting the Installer on &arch-title; - - - - -&boot-installer-alpha.xml; -&boot-installer-arm.xml; -&boot-installer-x86.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/da/boot-installer/ia64.xml b/da/boot-installer/ia64.xml deleted file mode 100644 index 37c14f59c..000000000 --- a/da/boot-installer/ia64.xml +++ /dev/null @@ -1,462 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - CD Contents - - - -There are three basic variations of Debian Install CDs. -The Business Card CD has a minimal installation -that will fit on the small form factor CD media. -It requires a network connection in order to install the rest of the -base installation and make a usable system. -The Network Install CD has all of the packages -for a base install but requires a network connection to a Debian -mirror site in order to install the -extra packages one would want for a complete system . -The set of Debian CDs can install a complete system from the wide -range of packages without needing access to the network. - - - - - -The IA-64 architecture uses the next generation Extensible Firmware Interface -(EFI) from Intel. -Unlike the traditional x86 BIOS which knows little about the boot -device other than the partition table and Master Boot Record (MBR), -EFI can read and write files from FAT16 or FAT32 formatted disk -partitions. -This simplifies the often arcane process of starting a system. -The system boot loader and the EFI firmware that supports it have -a full filesystem to store the files necessary for booting the -machine. -This means that the system disk on an IA-64 system has an additional -disk partition dedicated to EFI instead of the simple MBR or boot -block on more conventional systems. - - - -The Debian Installer CD contains a small EFI partition where the -ELILO bootloader, its configuration file, the installer's -kernel, and initial filesystem (initrd) are located. -The running system also contains an EFI partition where the necessary -files for booting the system reside. -These files are readable from the EFI Shell as described below. - - - -Most of the details of how ELILO actually loads and -starts a system are transparent to the system installer. -However, the installer must set up an EFI partition prior to installing -the base system. Otherwise, the installation of ELILO -will fail, rendering the system un-bootable. -The EFI partition is allocated and formatted in the partitioning step -of the installation prior to loading any packages on the system disk. -The partitioning task also verifies that a suitable EFI partition is -present before allowing the installation to proceed. - - - -The EFI Boot Manager is presented as the last step of the firmware -initialization. -It displays a menu list from which the user can select -an option. -Depending on the model of system and what other software has been -loaded on the system, this menu may be different from one system -to another. -There should be at least two menu items displayed, -Boot Option Maintenance Menu and -EFI Shell (Built-in). -Using the first option is preferred, however, if that -option is not available or the CD for some reason does not -boot with it, use the second option. - - - - - IMPORTANT - -The EFI Boot Manager will select a default boot action, typically -the first menu choice, within a pre-set number of seconds. -This is indicated by a countdown at the bottom of the screen. -Once the timer expires and the systems starts the default action, -you may have to reboot the machine in order to continue the installation. -If the default action is th 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. - - - - - - - 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. - - - - 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. - - - - -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/da/boot-installer/intro-cd.xml b/da/boot-installer/intro-cd.xml deleted file mode 100644 index 9f603991c..000000000 --- a/da/boot-installer/intro-cd.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - - -The easiest route for most people will be to use a set of Debian CDs. -If you have a CD set, and if your machine supports booting directly off -the CD, great! Simply - -configure your system for booting off a CD as described in -, - -insert your CD, reboot, and proceed to the next chapter. - - - -Note that certain CD drives may require special drivers, and thus be -inaccessible in the early installation stages. If it turns out the -standard way of booting off a CD doesn't work for your hardware, -revisit this chapter and read about alternate kernels and installation -methods which may work for you. - - - -Even if you cannot boot from CD-ROM, you can probably install the -Debian system components and any packages you want from CD-ROM. -Simply boot using a different media, such as floppies. When it's -time to install the operating system, base system, and any additional -packages, point the installation system at the CD-ROM drive. - - - -If you have problems booting, see . - - \ No newline at end of file diff --git a/da/boot-installer/intro-hd.xml b/da/boot-installer/intro-hd.xml deleted file mode 100644 index be5f65be3..000000000 --- a/da/boot-installer/intro-hd.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - -Booting from an existing operating system is often a convenient -option; for some systems it is the only supported method of -installation. - - - -To boot the installer from hard disk, you will have already completed -downloading and placing the needed files in -. - - \ No newline at end of file diff --git a/da/boot-installer/intro-net.xml b/da/boot-installer/intro-net.xml deleted file mode 100644 index 79189195c..000000000 --- a/da/boot-installer/intro-net.xml +++ /dev/null @@ -1,19 +0,0 @@ - - - - - -Booting from the network requires that you have a network -connection and a TFTP network boot server (DHCP, RARP, or BOOTP). - - - -Older systems such as the 715 might require the use of an RBOOT server -instead of a BOOTP server. - - - -The installation method to support network booting is described in . - - \ No newline at end of file diff --git a/da/boot-installer/m68k.xml b/da/boot-installer/m68k.xml deleted file mode 100644 index 2a75270a4..000000000 --- a/da/boot-installer/m68k.xml +++ /dev/null @@ -1,349 +0,0 @@ - - - - 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 must make sure you -are using a ramdisk built to accomodate it, see the MANIFEST. You will -also need to use the &ramdisksize; kernel parameter. - - - -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. - - - - - MVME147 and MVME16x - - -The installer for MVEM147 and MVEM16x 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/da/boot-installer/mips.xml b/da/boot-installer/mips.xml deleted file mode 100644 index 1b69e86ac..000000000 --- a/da/boot-installer/mips.xml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - Booting with TFTP - - - SGI Indys TFTP Booting - - -After entering the command monitor use - - -bootp(): root=/dev/ram0 - - -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 - - - - - - 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/da/boot-installer/parameters.xml b/da/boot-installer/parameters.xml deleted file mode 100644 index ba48ef64c..000000000 --- a/da/boot-installer/parameters.xml +++ /dev/null @@ -1,300 +0,0 @@ - - - - Boot Parameters - - -Boot parameters are Linux kernel parameters which are generally used -to make sure that peripherals are dealt with properly. For the most -part, the kernel can auto-detect information about your peripherals. -However, in some cases you'll have to help the kernel a bit. - - - -If this is the first time you're booting the system, try the default -boot parameters (i.e., don't try setting parameters) and see if it works -correctly. It probably will. If not, you can reboot later and look for -any special parameters that inform the system about your hardware. - - - -Information on many boot parameters can be found in the - Linux -BootPrompt HOWTO, including tips for obscure hardware. This -section contains only a sketch of the most salient parameters. Some -common gotchas are included below in -. - - - -When the kernel boots, a message - - - -Memory:availk/totalk available - - - -should be emitted early in the process. -total should match the total amount of RAM, -in kilobytes. If this doesn't match the actual amount of RAM you have -installed, you need to use the -mem=ram parameter, -where ram is set to the amount of memory, -suffixed with ``k'' for kilobytes, or ``m'' for megabytes. For -example, both mem=65536k and -mem=64m mean 64MB of RAM. - - - -If you are booting with a serial console, generally the kernel will -autodetect this -(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 which may -be useful. - - - - - -debconf/priority - - -This parameter settings will set the highest 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 - - -Passing this boot parameter will cause the boot to be more verbosely -logged. - - - -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 floppys 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. - - - - - -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 -chage 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 misbehaviour. - - - - - -preseed/url - - -Specify the url to a preconfiguration file to download and use in -automating the install. See . - - - - - -preseed/file - - -Specify the url to a preconfiguration file to load to -automating the install. See . - - - - - -ramdisk_size - - -If you are using a 2.2.x kernel, you may need to set &ramdisksize;. - - - - - - - - diff --git a/da/boot-installer/powerpc.xml b/da/boot-installer/powerpc.xml deleted file mode 100644 index f7de30364..000000000 --- a/da/boot-installer/powerpc.xml +++ /dev/null @@ -1,188 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - -Currently, the only &arch-title; subarchitectures that support CD-ROM -booting are PReP 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 MacOSROM 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 linux.bin, yaboot, -yaboot.conf, and root.bin 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 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/da/boot-installer/s390.xml b/da/boot-installer/s390.xml deleted file mode 100644 index 530bb2db0..000000000 --- a/da/boot-installer/s390.xml +++ /dev/null @@ -1,30 +0,0 @@ - - - - s390 Limitations - - -In order to run the installation system a working network setup and -ssh session is needed on S/390. - - - -The booting process starts with a network setup that prompts you for -several network parameters. If the setup is successful, you will login -to the system by starting 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/da/boot-installer/sparc.xml b/da/boot-installer/sparc.xml deleted file mode 100644 index a12f25cf3..000000000 --- a/da/boot-installer/sparc.xml +++ /dev/null @@ -1,103 +0,0 @@ - - - - Booting from NFS - - -To install the system via NFS, simply select -NFS for the location of the images and files -and follow the instructions provided. You will be prompted for the -server:/directory where the images are located. - - - - - - 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/da/boot-installer/trouble.xml b/da/boot-installer/trouble.xml deleted file mode 100644 index 18067e318..000000000 --- a/da/boot-installer/trouble.xml +++ /dev/null @@ -1,194 +0,0 @@ - - - - - Troubleshooting the Install Process - - - - - Floppy Disk Reliability - - - -The biggest problem for people installing Debian for the first time -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. - - - - - - 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/da/boot-installer/x86.xml b/da/boot-installer/x86.xml deleted file mode 100644 index 4aafec5c2..000000000 --- a/da/boot-installer/x86.xml +++ /dev/null @@ -1,426 +0,0 @@ - - - - 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/ram - append="devfs=mount,dall ramdisk_size=17000 - - - -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/ram devfs=mount,dall ramdisk_size=17000 -initrd (hd0,0)/boot/newinstall/initrd.gz - - - -and reboot. Note that the value of the ramdisksize -may need to be adjusted for the size of the initrd image. -From now on, there should be no difference between GRUB -or LILO. - - - - - - Booting from USB memory stick - - -Lets 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 a 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 screenful 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. - - - - - - i386 Boot Parameters - - -When the installer boots, you will be presented with the boot prompt, -boot:. You can do two things at the boot: -prompt. You can press the function keys F1 through -F10 to view a few pages of helpful information, or -you can press Enter to boot the system. - - - -Information on boot parameters which might be useful can be found by -pressing F3 through F7. 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 floppy=thinkpad). If you simply press &enterkey;, -that's the same as typing linux without any special -parameters. - - - -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. - - - diff --git a/da/boot-new/boot-new.xml b/da/boot-new/boot-new.xml deleted file mode 100644 index fb8a108df..000000000 --- a/da/boot-new/boot-new.xml +++ /dev/null @@ -1,290 +0,0 @@ - - - - - Booting Into Your New Debian System - - The Moment of Truth - - -Your system's first boot on its own power is what electrical engineers -call the smoke test. - - - -If you are booting directly into Debian, and the system doesn't start -up, either use your original installation boot media, or insert the -custom boot floppy if you have one, and reset your system. This way, -you will probably need to add some boot arguments like -root=root, where -root is your root partition, such as -/dev/sda1. - - - - BVME 6000 Booting - - -If you have just performed a diskless install on a BVM or Motorola -VMEbus machine: once the system has loaded the -tftplilo program from the TFTP server, from the -LILO Boot: prompt enter one of: - - - - -b6000 followed by &enterkey; -to boot a BVME 4000/6000 - - - -b162 followed by &enterkey; -to boot an MVME162 - - - -b167 followed by &enterkey; -to boot an MVME166/167 - - - - - - - - - Macintosh Booting - - - -Go to the directory containing the installation files and start up the -Penguin booter, holding down the -command key. Go to the -Settings dialogue ( -command T ), and locate -the kernel options line which should look like -root=/dev/ram video=font:VGA8x16 or similar. - - - -You need to change the entry to -root=/dev/yyyy. -Replace the yyyy with the Linux name of the -partition onto which you installed the system -(e.g. /dev/sda1); you wrote this down earlier. -The video=font:VGA8x8 is recommended especially -for users with tiny screens. The kernel would pick a prettier (6x11) -font but the console driver for this font can hang the machine, so -using 8x16 or 8x8 is safer at this stage. You can change this at any -time. - - - -If you don't want to start GNU/Linux immediately each time you start, -uncheck the Auto Boot option. Save your -settings in the Prefs file using the -Save Settings As Default option. - - - -Now select Boot Now ( -command B ) to start your -freshly installed GNU/Linux instead of the RAMdisk installer system. - - - -Debian should boot, and you should see the same messages as -when you first booted the installation system, followed by some new -messages. - - - - - - OldWorld PowerMacs - - -If the machine fails to boot after completing the installation, and -stops with a boot: prompt, try typing -Linux followed by &enterkey;. (The default boot -configuration in quik.conf is labeled Linux). The -labels defined in quik.conf will be displayed if -you press the Tab key at the boot: -prompt. You can also try booting back into the installer, and editing -the /target/etc/quik.conf placed there by the -Install Quik on a Hard -Disk step. Clues for dealing with -quik are available at . - - - -To boot back into MacOS without resetting the nvram, type -bye at the OpenFirmware prompt (assuming MacOS -has not been removed from the machine). To obtain an OpenFirmware -prompt, hold down the command -option o f - keys while cold booting the machine. If you need to reset -the OpenFirmware nvram changes to the MacOS default in order to boot -back to MacOS, hold down the command -option p r - keys while cold booting the machine. - - - -If you use BootX to boot into the installed system, -just select your desired kernel in the Linux -Kernels folder, un-choose the ramdisk option, and add -a root device corresponding to your installation; -e.g. /dev/hda8. - - - - - - NewWorld PowerMacs - - -On G4 machines and iBooks, you can hold down the -option key and get a graphical screen with a button -for each bootable OS, &debian; will be a button with a small penguin -icon. - - - -If you kept MacOS and at some point it changes the OpenFirmware -boot-device variable you should reset OpenFirmware to -its default configuration. To do this hold down the -command option p -r keys while cold booting the machine. - - - -The labels defined in yaboot.conf will be -displayed if you press the Tab key at the -boot: prompt. - - - -Resetting OpenFirmware on G3 or G4 hardware will cause it to boot -&debian; by default (if you correctly partitioned and placed the -Apple_Bootstrap partition first). If you have &debian; on a SCSI disk -and MacOS on an IDE disk this may not work and you will have to enter -OpenFirmware and set the boot-device variable, -ybin normally does this automatically. - - - -After you boot &debian; for the first time you can add any additional -options you desire (such as dual boot options) to -/etc/yaboot.conf and run ybin -to update your boot partition with the changed configuration. Please -read the yaboot HOWTO -for more information. - - - - - - - Debian Post-Boot (Base) Configuration - - - -After booting, you will be prompted to complete the configuration of -your basic system, and then to select what additional packages you -wish to install. The application which guides you through this -process is called base-config. Its concept is -very similar to the &d-i; from the first stage. Indeed, -base-config consists of a number of specialized -components, where each component handles one configuration task, -contains hidden menu in the background and also uses -the same navigation system. - - - -If you wish to re-run the base-config at any -point after installation is complete, as root run -base-config. - - - -&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; - - - - - Log In - - - -After you've installed packages, you'll be presented with the login -prompt. Log in using the personal login and password you -selected. Your system is now ready to use. - - - -If you are a new user, you may want to explore the documentation which -is already installed on your system as you start to use it. There are -currently several documentation systems, work is proceeding on -integrating the different types of documentation. Here are a few -starting points. - - - -Documentation accompanying programs you have installed is in -/usr/share/doc/, under a subdirectory named after -the program. For example, the APT User's Guide for using -apt to install other programs on your system, is -located in -/usr/share/doc/apt/guide.html/index.html. - - - - -In addition, there are some special folders within the -/usr/share/doc/ hierarchy. Linux HOWTOs are -installed in .gz format, in -/usr/share/doc/HOWTO/en-txt/ and -/usr/share/doc/HOWTO/en-txt/mini/. The -/usr/share/doc/HTML/index.html contains -browsable indexes of documentation installed by -dhelp. - - - -One easy way to view these documents is to cd -/usr/share/doc/, and type lynx -followed by a space and a dot (the dot stands for the current -directory). - - - -You can also type info -command or man -command to see documentation on -most commands available at the command prompt. Typing -help will display help on shell commands. And -typing a command followed by --help will -usually display a short summary of the command's usage. If a command's -results scroll past the top of the screen, type | -more after the command to cause the results to pause -before scrolling past the top of the screen. To see a list of all -commands available which begin with a certain letter, type the letter -and then two tabs. - - - -For a more complete introduction to Debian and GNU/Linux, see -/usr/share/doc/debian-guide/html/noframes/index.html. - - - - - diff --git a/da/boot-new/modules/apt.xml b/da/boot-new/modules/apt.xml deleted file mode 100644 index 12d2a208b..000000000 --- a/da/boot-new/modules/apt.xml +++ /dev/null @@ -1,97 +0,0 @@ - - - - - Configuring APT - - - -The main means that people use to install packages on their system is -via a program called apt-get, from the -apt package. - - - -Note that the actual program that installs packages is called -dpkg. However, this package is more of a low-level -tool. apt-get will invoke dpkg -as appropriate; it is a higher-level too, however, because it knows to -install other packages which are required for the package you're -trying to install, as well as how to retrieve the package from your -CD, the network, or wherever. - - - - -APT must be configured, however, so that it knows where to retrieve -packages from. The helper application which assists in this task is -called apt-setup. - - - -The next step in your configuration process is to tell APT where other -Debian packages can be found. Note that you can re-run this tool at -any point after installation by running apt-setup, -or by manually editing /etc/apt/sources.list. - - - -If an official CD-ROM is in the drive at this point, then that CD-ROM -should automatically be configured as an apt source without prompting. -You will notice this because you will see the CD-ROM being scanned. - - - -For users without an official CD-ROM, you will be offered an array of -choices for how Debian packages are accessed: FTP, HTTP, CD-ROM, or -a local file system. - - - -You should know that it's perfectly acceptable to have a number of -different APT sources, even for the same Debian archive. -apt-get will automatically pick the package with -the highest version number given all the available versions. Or, for -instance, if you have both an HTTP and a CD-ROM APT source, -apt-get should automatically use the local CD-ROM -when possible, and only resort to HTTP if a newer version is available -there. However, it is not a good idea to add unnecessary APT sources, -since this will tend to slow down the process of checking the network -archives for new versions. - - - - - Configuring Network Package Sources - - - -If you plan on installing the rest of your system via the network, the -most common option is to select the http -source. The ftp source is also acceptable, but -tends to be a little slower making connections. - - - -The next step during the configuration of network packages sources is -to tell apt-setup which country you live in. This -configures which of the official Debian Internet mirror network you -connect to. Depending on which country you select, you will be given -a list of possible machines. Its generally fine to pick the one on -the top of the list, but any of them should work. - - - -If you are installing via HTTP, you will be asked to configure your -proxy server. This is sometimes required by people behind firewalls, -on corporate networks, etc. - - - -Finally, your new network package source will be tested. If all goes -well, you will be prompted whether you want to do it all over again -with another network source. - - - - diff --git a/da/boot-new/modules/install.xml b/da/boot-new/modules/install.xml deleted file mode 100644 index d0998127e..000000000 --- a/da/boot-new/modules/install.xml +++ /dev/null @@ -1,39 +0,0 @@ - - - - - Prompts During Software Installation - - - -Each package you selected with tasksel or -aptitude is -downloaded, unpacked and then installed in turn by the -apt-get and dpkg programs. If -a particular program needs more information from the user, it will -prompt you during this process. You might also want to keep an eye on -the output during the process, to watch for any installation errors -(although you will be asked to acknowledge errors which prevented -a package's installation). - - - - - Settings for the X Server - - - -On iMacs, and some older Macintoshes as well, the X Server software -doesn't calculate appropriate video settings. You will need to choose -the 'Advanced' option during configuration of the video settings. For -the monitor's horizontal sync range, enter 59-63. You can leave the -default for vertical refresh range. - - - -The mouse device should be set to -/dev/input/mice. - - - - diff --git a/da/boot-new/modules/mta.xml b/da/boot-new/modules/mta.xml deleted file mode 100644 index 5290c4254..000000000 --- a/da/boot-new/modules/mta.xml +++ /dev/null @@ -1,93 +0,0 @@ - - - - - Configuring Your Mail Transport Agent - - - -Today, email is a very important part of many people's life, so it's -no surprise Debian lets you configure your mail system right as a part -of the installation process. The standard mail transport agent in -Debian is exim4, which is relatively small, -flexible, and easy to learn. - - - -You may ask if this is needed even if your computer is not connected -to any network. The short answer is: Yes. The longer explanation: Some -system utilities (like cron, -quota, aide, …) may send -you important notices via email. - - - -So on the first screen you will be presented with several common mail -scenarios. Choose the one that most closely resembles your needs: - - - - - -internet site - - -Your system is connected to a network and your mail is sent and -received directly using SMTP. On the following screens you will be -asked a few basic questions, like your machine's mail name, or a list of -domains for which you accept or relay mail. - - - - - -mail sent by smarthost - - -In this scenario is your outgoing mail forwarded to another machine, -called a smarthost, which does the actual job for -you. Smarthost also usually stores incoming mail addresed to your -computer, so you don't need to be permanently online. That also means -you have to download your mail from the smarthost via programs like -fetchmail. This option is suitable for dial-up users. - - - - - -local delivery only - - -Your system is not on a network and mail is sent or received only -between local users. Even if you don't plan to send any messages, this -option is highly recommended, because some system utilities may send -you various alerts from time to time (e.g. beloved Disk quota -exceeded). This option is also convenient for new users, -because it doesn't ask any further questions. - - - - - -no configuration at this time - - -Choose this if you are absolutely convinced you know what you are -doing. This will leave you with an unconfigured mail system — -until you configure it, you won't be able to send or receive any mail -and you may miss some important messages from your system utilities. - - - - - - - -If none of these scenarios suits your needs, or if you need a finer -setup, you will need to edit configuration files under the -/etc/exim4 directory after the installation is -complete. More information about exim4 may be found -under /usr/share/doc/exim4. - - - diff --git a/da/boot-new/modules/packages.xml b/da/boot-new/modules/packages.xml deleted file mode 100644 index ccfed03d9..000000000 --- a/da/boot-new/modules/packages.xml +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Package Installation - - - -Next you will be offered a number of pre-rolled software -configurations offered by Debian. You could always choose, package by -package, what you want to install on your new machine. This is the -purpose of the aptitude program, described below. -But this can be a long task with around &num-of-distrib-pkgs; packages -available in Debian! - - - -So, you have the ability to choose tasks first, -and then add on more individual packages later. These tasks loosely -represent a number of different jobs or things you want to do with -your computer, such as desktop environment, -web server, or print server. - - - - -You should know that to present this list, -base-config is merely invoking the -tasksel program. For manual package -selection, the -aptitude program is being run. Any of these can be -run at any time after installation to install (or remove) more -packages. If you are looking for a specific single package, after -installation is complete, simply run apt-get install -package, where -package is the name of the package you are -looking for. - - - - - -If you do want to choose what to install on a package by package basis, -select the manual package selection in -tasksel. - - - -Once you've selected your tasks, select -Ok. At this point, -aptitude will install the packages you've -selected. Note, even if you did not select any tasks at all, any standard, -important, or required priority packages that are not yet present on -your system will be installed. This functionality is the same as -running tasksel -s at the command line, and -currently involves -a download of about 37M of archives. You will be shown the number of -packages to be installed, and how many kilobytes of packages, if any, -need to be downloaded. - - - -Of the &num-of-distrib-pkgs; packages available in Debian, only -a small minority are covered by tasks offered in the Task Installer. -To see information on more packages, either use apt-cache -search search-string for some -given search string (see the -apt-cache 8 - man page), or run -aptitude as described below. - - - - - Advanced Package Selection with <command>aptitude</command> - - - -Aptitude is a modern program for managing -packages. aptitude allows you to -select individual packages, set of packages matching given criteria -(for advanced users), or whole tasks. - - - -The most basic keybindings are: - - - - - - KeyAction - - - - - - Up, Down - Move selection up or down. - - &enterkey; - Open/collapse/activate item. - - + - Mark package for installation. - - - - Mark package for removal. - - d - Show package dependencies. - - g - Actually download/install/remove packages. - - q - Quit current view. - - F10 - Activate menu. - - - -For more commands see the online help under the ? key. - - - - diff --git a/da/boot-new/modules/ppp.xml b/da/boot-new/modules/ppp.xml deleted file mode 100644 index 868963085..000000000 --- a/da/boot-new/modules/ppp.xml +++ /dev/null @@ -1,112 +0,0 @@ - - - - - Setting Up PPP - - - -If your computer is not connected to a network, you will next be asked -whether you wish to install the rest of the system using PPP. - - - -If you do choose to configure PPP at this point, a program named -pppconfig will be run. This program helps you -configure your PPP connection. Make sure, when it asks you -for the name of your dialup connection, that you name it -provider. - - - -Hopefully, the pppconfig program will walk you -through a pain-free PPP connection setup. However, if it does not -work for you, see below for detailed instructions. - - - -In order to setup PPP, you'll need to know the basics of file viewing -and editing in GNU/Linux. To view files, you should use -more, and zmore for compressed -files with a .gz extension. For example, to -view README.debian.gz, type zmore -README.debian.gz. The base system comes with an editor -named nano, which is very simple to use, but does -not have a lot of features. You will probably want to install more -full-featured editors and viewers later, such as -jed, nvi, -less, and emacs. - - - -Edit /etc/ppp/peers/provider and replace -/dev/modem with -/dev/ttyS# where -# stands for the number of your serial -port. In Linux, serial ports are counted from 0; your first serial -port (i.e., COM1) -is /dev/ttyS0 under Linux. - -On Macintoshes with serial ports, the -modem port is /dev/ttyS0 and the printer port is -/dev/ttyS1. - -The next step is to edit -/etc/chatscripts/provider and insert your -provider's phone number, your user-name and password. Please do not -delete the \q that precedes the password. It hides the -password from appearing in your log files. - - - -Many providers use PAP or CHAP for login sequence instead of text mode -authentication. Others use both. If your provider requires PAP or -CHAP, you'll need to follow a different procedure. Comment out -everything below the dialing string (the one that starts with -ATDT) in -/etc/chatscripts/provider, modify -/etc/ppp/peers/provider as described above, and -add user name where -name stands for your user-name for the -provider you are trying to connect to. Next, edit -/etc/ppp/pap-secrets or -/etc/ppp/chap-secrets and enter your password -there. - - - -You will also need to edit /etc/resolv.conf and -add your provider's name server (DNS) IP addresses. The lines in -/etc/resolv.conf are in the following format: -nameserver -xxx.xxx.xxx.xxx where the -xs stand for numbers in your IP -address. Optionally, you could add the -usepeerdns option to the -/etc/ppp/peers/provider file, which will enable -automatic choosing of appropriate DNS servers, using settings the -remote host usually provides. - - - -Unless your provider has a login sequence different from the majority -of ISPs, you are done! Start the PPP connection by typing -pon as root, and monitor the process using -plog command. To disconnect, use -poff, again, as root. - - - -Read /usr/share/doc/ppp/README.Debian.gz file for -more information on using PPP on Debian. - - - -For static SLIP connections, you will need to add the -slattach command (from the -net-tools package) into -/etc/init.d/network. Dynamic SLIP will require -the gnudip package. - - - diff --git a/da/boot-new/modules/shadow.xml b/da/boot-new/modules/shadow.xml deleted file mode 100644 index e4ac0ce1e..000000000 --- a/da/boot-new/modules/shadow.xml +++ /dev/null @@ -1,69 +0,0 @@ - - - - - Setting Up Users And Passwords - - - Set the Root Password - - - -The root account is also called the -super-user; it is a login that bypasses all -security protection on your system. The root account should only be -used to perform system administration, and only used for as short -a time as possible. - - - -Any password you create should contain at least 6 characters, and -should contain both upper- and lower-case characters, as well as -punctuation characters. Take extra care when setting your root -password, since it is such a powerful account. Avoid dictionary -words or use of any personal information which could be guessed. - - - -If anyone ever tells you they need your root password, be extremely -wary. You should normally never give your root password out, unless you -are administering a machine with more than one system administrator. - - - - - - Create an Ordinary User - - - -The system will ask you whether you wish to create an ordinary user -account at this point. This account should be your main personal -log-in. You should not use the root account for -daily use or as your personal login. - - - -Why not? Well, one reason to avoid using root's privileges is that it -is very easy to do irreparable damage as root. Another reason is that -you might be tricked into running a Trojan-horse -program — that is a program that takes advantage of your -super-user powers to compromise the security of your system behind -your back. Any good book on Unix system administration will cover this -topic in more detail — consider reading one if it is new to you. - - - -You will first be prompted for the user's full name. Then you'll be asked -for a name for the user account; generally your first name or something -similar will suffice and indeed will be the default. Finally, you will be -prompted for a password for this account. - - - -If at any point after installation you would like to create another -account, use the adduser command. - - - - diff --git a/da/boot-new/modules/timezone.xml b/da/boot-new/modules/timezone.xml deleted file mode 100644 index e0c8ee4e7..000000000 --- a/da/boot-new/modules/timezone.xml +++ /dev/null @@ -1,30 +0,0 @@ - - - - - Configuring Your Time Zone - - - -After a welcome screen, you will be prompted to configure your time zone. -First select whether the hardware clock of your system is set to local -time or Greenwich Mean Time (GMT or UTC). The time displayed in the dialog -may help you decide on the correct option. -Macintosh hardware clocks are normally -set to local time. If you want to dual-boot, select local time instead of -GMT. -Systems that (also) run Dos or Windows are normally -set to local time. If you want to dual-boot, select local time instead of -GMT. - - - -Depending on the location selected at the beginning of the installation -process, you will next be shown either a single timezone or a list of -timezones relevant for that location. If a single timezone is shown, choose -Yes to confirm or choose No -to select from the full list of timezones. If a list is shown, select your -timezone from the list, or select Other for the full list. - - - diff --git a/da/hardware/hardware-supported.xml b/da/hardware/hardware-supported.xml deleted file mode 100644 index 6c3602fc5..000000000 --- a/da/hardware/hardware-supported.xml +++ /dev/null @@ -1,345 +0,0 @@ - - - - - Supported Hardware - - - -Debian does not impose hardware requirements beyond the requirements -of the Linux kernel and the GNU tool-sets. Therefore, any -architecture or platform to which the Linux kernel, libc, -gcc, etc. have been ported, and for which a Debian -port exists, can run Debian. Please refer to the Ports pages at - for -more details on &arch-title; architecture systems which have been -tested with Debian. - - - -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 - - generic - - jensen - - nautilus - - - - Sun SPARC - sparc - - sun4cdm - - sun4u - - - - ARM and StrongARM - arm - - netwinder - - riscpc - - shark - - lart - - - - IBM/Motorola PowerPC - powerpc - CHRP - chrp - - PowerMac - powermac, new-powermac - - 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 BCM1250 (SWARM) - sb1-bcm91250a - - - - MIPS (little endian) - mipsel - Cobalt - cobalt - - DECstation - r4k-kn04 - - r3k-kn02 - - Broadcom BCM1250 (SWARM) - sb1-bcm91250a - - - - IBM S/390 - s390 - - tape - - vmrdr - - - - - - -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. The newer AGP video -slots are actually a modification on the PCI specification, and most -AGP 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 BCM1250 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 BCM1250 is available. - - - -The XFree86 X11 window system is supported on some DECstation models. The -Broadcom BCM1250 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 BCM1250 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 -``symmetric multi-processing'' in the ``General'' 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 -``symmetric multi-processing'' in the ``General'' 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 customised 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 -``symmetric multi-processing'' in the ``General'' section of the -kernel config. - - - - diff --git a/da/hardware/hardware.xml b/da/hardware/hardware.xml deleted file mode 100644 index 798fe2cad..000000000 --- a/da/hardware/hardware.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - System Requirements - - - -This section contains information about what hardware you need to get -started with Debian. You will also find links to further information -about hardware supported by GNU and Linux. - - - -&hardware-supported.xml; -&installation-media.xml; -&supported-peripherals.xml; -&memory-disk-requirements.xml; -&network-cards.xml; - - diff --git a/da/hardware/installation-media.xml b/da/hardware/installation-media.xml deleted file mode 100644 index 05aca1ccd..000000000 --- a/da/hardware/installation-media.xml +++ /dev/null @@ -1,317 +0,0 @@ - - - - - Installation Media - - - -This section will help you determine which different media types you can use to -install Debian. For example, if you have a floppy disk drive on your machine, -it can be used to install Debian. There is a whole chapter devoted 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. - - - -IDE/ATAPI CD-ROMs are supported on all ARM machines. -On RiscPCs, SCSI CD-ROMs are also supported. - - - -On SGI machines, it is possible to boot from CD and images are provided. -To start the install, simply choose the System installation -entry in the firmware. The Broadcom BCM1250 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 partiton (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 other 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 downtimes. 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. The following SCSI drivers are supported in the default -kernel: - - - - -Qlogic ISP - - - - -NCR and Symbios 53c8xx - - - - -Adaptec AIC7xxx - - - - -IDE disks are also supported. 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/da/hardware/memory-disk-requirements.xml b/da/hardware/memory-disk-requirements.xml deleted file mode 100644 index 6bb18618e..000000000 --- a/da/hardware/memory-disk-requirements.xml +++ /dev/null @@ -1,47 +0,0 @@ - - - - - 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/da/hardware/network-cards.xml b/da/hardware/network-cards.xml deleted file mode 100644 index c98b29234..000000000 --- a/da/hardware/network-cards.xml +++ /dev/null @@ -1,214 +0,0 @@ - - - - - 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, and the -Linux MCA discussion archives. -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. Support for the built-in DECChip -(Tulip) Ethernet on many Alpha models is compiled directly into the -kernel. For other cards, 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) or ESCON connection (real or emulated) - - - - - -lcs: OSA-2 Token Ring/Ethernet or OSA-Express Fast Ethernet - (non-QDIO) - - - - -Inter-User Communication Vehicle (IUCV) - available for VM - guests only - - - - -qeth: OSA-Express in QDIO mode / HiperSockets - - - - - - - - -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/da/hardware/supported-peripherals.xml b/da/hardware/supported-peripherals.xml deleted file mode 100644 index 35fe2ccb6..000000000 --- a/da/hardware/supported-peripherals.xml +++ /dev/null @@ -1,186 +0,0 @@ - - - - - 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 BCM1250 evaluation board offers standard 3.3v 32 bit and 64 -bit PCI slots as well as USB connectors. - - - -The Broadcom BCM1250 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. See - for complete details. - - - -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/da/hardware/supported/alpha.xml b/da/hardware/supported/alpha.xml deleted file mode 100644 index 816c89c8b..000000000 --- a/da/hardware/supported/alpha.xml +++ /dev/null @@ -1,432 +0,0 @@ - - - - - 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 chip-sets. -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 ES45 - Privateer - N/A - - UNKNOWN - Yukon - N/A - - - - TSUNAMI - AlphaServer DS10 - Webbrick - N/A - - AlphaServer DS20 - Catamaran/Goldrush - N/A - - AlphaServer DS20E - Goldrack - 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 - - - - diff --git a/da/hardware/supported/arm.xml b/da/hardware/supported/arm.xml deleted file mode 100644 index 2c330b5bc..000000000 --- a/da/hardware/supported/arm.xml +++ /dev/null @@ -1,96 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - - -Each distinct ARM architecture requires its own kernel, because of -this the standard Debian distribution only supports installation on -a number of the most common systems. The Debian userland however may be used by any ARM CPU including xscale. - - - - - -Most ARM CPUs may be run in either endian mode, however almost every -current system implementation uses little-endian mode. Debian -currently only supports little-endian ARM systems. - - - - - -The common supported systems are - - - -Netwinder - - -This is actually the name for the group of machines -based upon the StrongARM 110 CPU and Intel 21285 Nothbridge it -comprises machines are: 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 typicaly 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 proprietay 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, PS2 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 -be enthusiasts. To be useful to install Debian it requires its KSB -expansion board. - - - - - - - - diff --git a/da/hardware/supported/hppa.xml b/da/hardware/supported/hppa.xml deleted file mode 100644 index 6f3c8c8ee..000000000 --- a/da/hardware/supported/hppa.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - 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/da/hardware/supported/i386.xml b/da/hardware/supported/i386.xml deleted file mode 100644 index 4b1e4a2ca..000000000 --- a/da/hardware/supported/i386.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -Complete information concerning supported peripherals can be found at -Linux Hardware Compatibility HOWTO. -This section merely outlines the basics. - - - - CPU - - -Nearly all x86-based 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/da/hardware/supported/ia64.xml b/da/hardware/supported/ia64.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/da/hardware/supported/ia64.xml +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/da/hardware/supported/m68k.xml b/da/hardware/supported/m68k.xml deleted file mode 100644 index 6e165f6e7..000000000 --- a/da/hardware/supported/m68k.xml +++ /dev/null @@ -1,39 +0,0 @@ - - - - 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/da/hardware/supported/mips.xml b/da/hardware/supported/mips.xml deleted file mode 100644 index 5b4c53f27..000000000 --- a/da/hardware/supported/mips.xml +++ /dev/null @@ -1,52 +0,0 @@ - - - - - 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 BCM1250 (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 and R5000 -processors are supported by the Debian installation system on big endian -MIPS. The Broadcom BCM1250 evaluation board comes with an SB1250 chip with -two 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/da/hardware/supported/mipsel.xml b/da/hardware/supported/mipsel.xml deleted file mode 100644 index a0d355211..000000000 --- a/da/hardware/supported/mipsel.xml +++ /dev/null @@ -1,146 +0,0 @@ - - - - - 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 BCM1250 (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 BCM1250 evaluation board comes with an SB1250 chip with two -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 (part of the uucp 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 BCM1250 use 115200 bps. - - - - - diff --git a/da/hardware/supported/powerpc.xml b/da/hardware/supported/powerpc.xml deleted file mode 100644 index 7373a693d..000000000 --- a/da/hardware/supported/powerpc.xml +++ /dev/null @@ -1,248 +0,0 @@ - - - - - CPU, Main Boards, and Video Support - - -There are four major supported &architecture; -flavors: PMac (Power-Macintosh) PReP, Apus, and CHRP machines. 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 64bit port (Power3) in the future. - - - -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. - - - -Recently introduced Macintosh systems have hardware which is more well -supported by the 2.4 Linux kernel. For some, the 2.2 kernel just -doesn't work. The new-powermac flavor, which uses the 2.4 kernel, has -been added to keep up with the hardware. The new-powermac flavor may -also be installed on other OldWorld and NewWorld machines. Machines -for which new-powermac is highly recommended are flagged with an -asterisk below. - - - -Specifications for Apple hardware are available at -AppleSpec, -and, for older hardware, -AppleSpec Legacy. - - - - - - - - - - - Model Name/Number - Architecture - - - - - - Apple - iMac Bondi Blue, 5 Flavors, Slot Loading - powermac-NewWorld - - iMac Summer 2000, Early 2001 - powermac-NewWorld - - * iBook, iBook SE, iBook Dual USB - powermac-NewWorld - - * iBook2 - powermac-NewWorld - - Power Macintosh Blue and White (B&W) G3 - powermac-NewWorld - - * Power Macintosh G4 PCI, AGP, Cube - powermac-NewWorld - - * Power Macintosh G4 Gigabit Ethernet - powermac-NewWorld - - * Power Macintosh G4 Digital Audio, Quicksilver - powermac-NewWorld - - PowerBook G3 FireWire Pismo (2000) - powermac-NewWorld - - PowerBook G3 Lombard (1999) - powermac-NewWorld - - * PowerBook G4 Titanium - powermac-NewWorld - - Performa 4400, 54xx, 5500 - powermac-OldWorld - - Performa 6360, 6400, 6500 - powermac-OldWorld - - Power Macintosh 4400, 5400 - powermac-OldWorld - - Power Macintosh 7200, 7300, 7500, 7600 - powermac-OldWorld - - Power Macintosh 8200, 8500, 8600 - powermac-OldWorld - - Power Macintosh 9500, 9600 - powermac-OldWorld - - Power Macintosh (Beige) G3 Minitower - powermac-OldWorld - - Power Macintosh (Beige) Desktop, All-in-One - powermac-OldWorld - - PowerBook 2400, 3400, 3500 - powermac-OldWorld - - PowerBook G3 Wallstreet (1998) - powermac-OldWorld - - Twentieth Anniversary Macintosh - powermac-OldWorld - - Workgroup Server 7250, 7350, 8550, 9650, G3 - powermac-OldWorld - - - - Power Computing - PowerBase, PowerTower / Pro, PowerWave - powermac-OldWorld - - PowerCenter / Pro, PowerCurve - powermac-OldWorld - - - - UMAX - C500, C600, J700, S900 - powermac-OldWorld - - - - APS - APS Tech M*Power 604e/2000 - powermac-OldWorld - - - - Motorola - Starmax 3000, 4000, 5000, 5500 - powermac-OldWorld - - Firepower, PowerStack Series E, PowerStack II - prep - - MPC 7xx, 8xx - prep - - MTX, MTX+ - prep - - MVME2300(SC)/24xx/26xx/27xx/36xx/46xx - prep - - MCP(N)750 - prep - - - - IBM RS/6000 - 40P, 43P - prep - - Power 830/850/860 (6070, 6050) - prep - - 6030, 7025, 7043 - prep - - p640 - prep - - B50, 43P-150, 44P - chrp - - - - Amiga Power-UP Systems (APUS) - A1200, A3000, A4000 - apus - - - - - - diff --git a/da/hardware/supported/s390.xml b/da/hardware/supported/s390.xml deleted file mode 100644 index 3de7074d1..000000000 --- a/da/hardware/supported/s390.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - S/390 and zSeries machine types - - -Complete information regarding supported S/390 and zSeries machines can -be found in IBM's Redbook - -Linux for IBM eServer zSeries and S/390: Distributions in -chapter 2.1 or at the -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/da/hardware/supported/sparc.xml b/da/hardware/supported/sparc.xml deleted file mode 100644 index 4ee2352eb..000000000 --- a/da/hardware/supported/sparc.xml +++ /dev/null @@ -1,82 +0,0 @@ - - - - - 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 -initialised. - - - -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/da/howto/installation-howto.xml b/da/howto/installation-howto.xml deleted file mode 100644 index fc7612447..000000000 --- a/da/howto/installation-howto.xml +++ /dev/null @@ -1,325 +0,0 @@ - - - - -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 media 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 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 it 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. - - -The 2.6 kernel is available for most boot methods, but not 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. - - - -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/da/install-methods/automatic-install.xml b/da/install-methods/automatic-install.xml deleted file mode 100644 index 6ec9c2dfc..000000000 --- a/da/install-methods/automatic-install.xml +++ /dev/null @@ -1,88 +0,0 @@ - - - - - Automatic Installation - - -For installing on multiple computers it's possible to do fully -automatic installations. Debian packages intended for this include -fai (which uses an install server), -replicator, -systemimager, -autoinstall, and -the Debian Installer itself. - - - - -Automatic installation using the Debian Installer - - -The Debian Installer supports automating installs via preconfiguration -files. A preconfiguration file can be loaded from the network or from -removable media, and used to fill in answers to question asked during the -installation process. - - - -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 . - - - -The preconfiguration file is in the format used by the -debconf-set-selections command, and 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 preconfiguation 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 preconfiguraton 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. - - - - diff --git a/da/install-methods/boot-drive-files.xml b/da/install-methods/boot-drive-files.xml deleted file mode 100644 index 2aba36d30..000000000 --- a/da/install-methods/boot-drive-files.xml +++ /dev/null @@ -1,176 +0,0 @@ - - - - - Preparing Files for Hard Disk Booting - - -The installer may be booted using boot files placed on an -existing hard drive partition, either launched from another operating -system or by invoking a boot loader directly from the BIOS. - - - -A full, "pure network" installation can be achieved using this -technique. This avoids all hassles of removable media, like finding -and burning CD images or struggling with too numerous and -unreliable floppy disks. - - - -The installer cannot boot from files on an NTFS file system. - - - -The installer cannot boot from files on an HFS+ file system. MacOS -System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all -use HFS+. To determine whether your existing file system is HFS+, -select Get Info for the volume in question. HFS -file systems appear as Mac OS Standard, while -HFS+ file systems say Mac OS Extended. You must -have an HFS partition in order to exchange files between MacOS and -Linux, in particular the installation files you download. - - - -Different programs are used for hard disk installation system booting, -depending on whether the system is a ``NewWorld'' or an ``OldWorld'' -model. - - - - - Hard disk installer booting using <command>LILO</command> or - <command>GRUB</command> - - -This section explains how to add to or even replace an existing linux -installation using either LILO or -GRUB. - - - -At boot time, both bootloaders support loading in memory not -only the kernel, but also a disk image. This RAM disk can be used as -the root file-system by the kernel. - - - -Copy the following files from the Debian archives to a -convenient location on your hard drive, for instance to -/boot/newinstall/. - - - - -vmlinuz (kernel binary) - - - - -initrd.gz (ramdisk image) - - - - - - -Finally, to configure the bootloader proceed to -. - - - - - - - Hard Disk Installer Booting for OldWorld Macs - - -The boot-floppy-hfs floppy uses -miBoot to launch Linux installation, but -miBoot cannot easily be used for hard disk -booting. BootX, launched from MacOS, -supports booting from files placed on the hard -disk. BootX can also be used to dual-boot -MacOS and Linux after your Debian installation is complete. For the -Performa 6360, it appears that quik cannot make the -hard disk bootable. So BootX is required -on that model. - - - -Download and unstuff the BootX -distribution, available from , -or in the -dists/woody/main/disks-powerpc/current/powermac -directory on Debian http/ftp mirrors and official Debian CDs. Use -Stuffit Expander to extract it from its -archive. Within the package, there is an empty folder called -Linux Kernels. Download -linux.bin and -ramdisk.image.gz from the -disks-powerpc/current/powermac folder, and place -them in the Linux Kernels folder. Then place the -Linux Kernels folder in the active System Folder. - - - - - - Hard Disk Installer Booting for NewWorld Macs - - -NewWorld PowerMacs support booting from a network or an ISO9660 -CD-ROM, as well as loading ELF binaries directly from the hard -disk. These machines will boot Linux directly via -yaboot, which supports loading a kernel and RAMdisk -directly from an ext2 partition, as well as dual-booting with -MacOS. Hard disk booting of the installer is particularly appropriate -for newer machines without floppy drives. BootX is -not supported and must not be used on NewWorld PowerMacs. - - - -Copy (not move) the following four files which -you downloaded earlier from the Debian archives, onto the root level -of your hard drive (this can be accomplished by -option-dragging each file to the hard drive icon). - - - - -linux.bin - - - - -root.bin (from inside the images-1.44 folder) - - - - -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/da/install-methods/boot-usb-files.xml b/da/install-methods/boot-usb-files.xml deleted file mode 100644 index 52b765c3e..000000000 --- a/da/install-methods/boot-usb-files.xml +++ /dev/null @@ -1,188 +0,0 @@ - - - - - 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 to your USB stick: - - - -gzip -dc 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. - - - -After that, mount the USB memory stick (mount /dev/sda -/mnt), which will now have a FAT 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. We -will show how to setup the memory stick to use the first partition, -instead of 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 -type - - - -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 type - - - -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 parition (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=10000 root=/dev/rd/0 init=/linuxrc devfs=mount,dall rw - - - -Please note, that the ramdisk_size parameter -may need to be increased, depending on the image you are booting. - - - -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. - - - -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/da/install-methods/create-floppy.xml b/da/install-methods/create-floppy.xml deleted file mode 100644 index 546d5c273..000000000 --- a/da/install-methods/create-floppy.xml +++ /dev/null @@ -1,108 +0,0 @@ - - - - - Creating Floppies from Disk Images - - -Bootable floppy disks are generally used as a last resort to boot the -installer on hardware that cannot boot from CD or by other means. - - - -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=file of=/dev/fd0 bs=1024 conv=sync ; sync - - -where file is one of the floppy disk image -files (see for what -file 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/da/install-methods/download/alpha.xml b/da/install-methods/download/alpha.xml deleted file mode 100644 index 6aec375c3..000000000 --- a/da/install-methods/download/alpha.xml +++ /dev/null @@ -1,36 +0,0 @@ - - - - - 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/da/install-methods/download/arm.xml b/da/install-methods/download/arm.xml deleted file mode 100644 index f0bc838b0..000000000 --- a/da/install-methods/download/arm.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - - 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/da/install-methods/download/m68k.xml b/da/install-methods/download/m68k.xml deleted file mode 100644 index a0dfd011c..000000000 --- a/da/install-methods/download/m68k.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - - - 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/da/install-methods/download/powerpc.xml b/da/install-methods/download/powerpc.xml deleted file mode 100644 index f8902926d..000000000 --- a/da/install-methods/download/powerpc.xml +++ /dev/null @@ -1,28 +0,0 @@ - - - - diff --git a/da/install-methods/downloading-files.xml b/da/install-methods/downloading-files.xml deleted file mode 100644 index 491fccfc6..000000000 --- a/da/install-methods/downloading-files.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - Downloading Files from Debian Mirrors - - - -To find the nearest (and thus probably the fastest) mirror, see the -list of Debian mirrors. - - - -When downloading files from a Debian mirror, 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/da/install-methods/floppy/i386.xml b/da/install-methods/floppy/i386.xml deleted file mode 100644 index 84b2957b7..000000000 --- a/da/install-methods/floppy/i386.xml +++ /dev/null @@ -1,35 +0,0 @@ - - - - - - - - Writing Disk Images From DOS, Windows, or OS/2 - - - -If you have access to an i386 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/da/install-methods/floppy/m68k.xml b/da/install-methods/floppy/m68k.xml deleted file mode 100644 index 839eefcea..000000000 --- a/da/install-methods/floppy/m68k.xml +++ /dev/null @@ -1,29 +0,0 @@ - - - - - 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/da/install-methods/floppy/powerpc.xml b/da/install-methods/floppy/powerpc.xml deleted file mode 100644 index adc4055da..000000000 --- a/da/install-methods/floppy/powerpc.xml +++ /dev/null @@ -1,119 +0,0 @@ - - - - - Writing Disk Images From MacOS - - -An AppleScript, Make Debian Floppy, is -available for burning floppies from the provided disk image files. It -can be downloaded from -. To -use it, just unstuff it on your desktop, and then drag any floppy -image file to it. You must have Applescript installed and enabled in -your extensions manager. Disk Copy will ask you to confirm that you -wish to erase the floppy and proceed to write the file image to it. - - - -You can also use the MacOS utility Disk Copy -directly, or the freeware utility suntar. The -root.bin file is an example of a floppy -image. Use one of the following methods to create a floppy from the -floppy image with these utilities. - - - - - Writing Disk Images with <command>Disk Copy</command> - - -If you are creating the floppy image from files which were originally -on the official &debian; 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 `Make a Floppy' from the -Utilities menu, 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 `Eject' from -the File menu. 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/da/install-methods/install-methods.xml b/da/install-methods/install-methods.xml deleted file mode 100644 index 0956b911b..000000000 --- a/da/install-methods/install-methods.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - Obtaining System Installation Media - -&official-cdrom.xml; -&downloading-files.xml; -&ipl-tape.xml; -&create-floppy.xml; -&boot-usb-files.xml; -&boot-drive-files.xml; -&install-tftp.xml; -&automatic-install.xml; - - diff --git a/da/install-methods/install-tftp.xml b/da/install-methods/install-tftp.xml deleted file mode 100644 index 3c8281fb8..000000000 --- a/da/install-methods/install-tftp.xml +++ /dev/null @@ -1,435 +0,0 @@ - - - - - Preparing Files for TFTP Net Booting - - -If your machine is connected to a local area network, you may be able -to boot it over the network from another machine, using TFTP. If you -intend to boot the installation system from another machine, the -boot files will need to be placed in specific locations on that machine, -and the machine configured to support booting of your specific machine. - - - -You need to set up a TFTP server, and for many machines, a 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. -You can also enter the IP configuration for network interfaces -directly in the SRM console. - - - - -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. - - - - -Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. -An RBOOTD package is available on the parisc-linux web site. - - - -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. - - - -&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. - - - -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. - - - -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 tftpimage-subarchitecture or -tftpimage-subarchitecture.gz. If the -tftpimage is gzipped (the name ends with .gz), you need to unpack it -first with gunzip -tftpimage-subarchitecture.gz, -as DECstations cannot boot compressed files by TFTP. 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. - - - -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/da/install-methods/ipl-tape.xml b/da/install-methods/ipl-tape.xml deleted file mode 100644 index a2ede6a88..000000000 --- a/da/install-methods/ipl-tape.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - - - Creating an IPL tape - - - -If you can't boot (IPL) from the CD-ROM and you are not using VM -you need to create an IPL tape first. This is described in section -3.4.3 in the - -Linux for IBM eServer zSeries and S/390: Distributions -Redbook. The files you -need to write to the tape are (in this order): -kernel.debian, -parmfile.debian and -initrd.debian. The files can be downloaded -from the tape sub-directory, see -, - - - - diff --git a/da/install-methods/official-cdrom.xml b/da/install-methods/official-cdrom.xml deleted file mode 100644 index 508d11e0a..000000000 --- a/da/install-methods/official-cdrom.xml +++ /dev/null @@ -1,69 +0,0 @@ - - - - - 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/da/install-methods/tftp/bootp.xml b/da/install-methods/tftp/bootp.xml deleted file mode 100644 index 1b0df1d95..000000000 --- a/da/install-methods/tftp/bootp.xml +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - 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/da/install-methods/tftp/dhcp.xml b/da/install-methods/tftp/dhcp.xml deleted file mode 100644 index 6132f3ef7..000000000 --- a/da/install-methods/tftp/dhcp.xml +++ /dev/null @@ -1,110 +0,0 @@ - - - - - - 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 6048; -max-lease-time 604800; - -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 subnet-mask 255.255.255.0; - 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; -} - -host tftpserver { -# tftp server ip address - fixed-address 192.168.1.90; -# tftp server hardware address - hardware ethernet 01:23:45:67:89:AB; -} - -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/da/install-methods/tftp/rarp.xml b/da/install-methods/tftp/rarp.xml deleted file mode 100644 index 26f2b681a..000000000 --- a/da/install-methods/tftp/rarp.xml +++ /dev/null @@ -1,73 +0,0 @@ - - - - - - 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/da/partitioning/device-names.xml b/da/partitioning/device-names.xml deleted file mode 100644 index 94206995a..000000000 --- a/da/partitioning/device-names.xml +++ /dev/null @@ -1,161 +0,0 @@ - - - - - - Device Names in Linux - - -Linux disks and partition names may be different from other operating -systems. You need to know the names that Linux uses when you create -and mount partitions. Here's the basic naming scheme: - - - - - -The first floppy drive is named /dev/fd0. - - - - -The second floppy drive is named /dev/fd1. - - - - -The first SCSI disk (SCSI ID address-wise) is named -/dev/sda. - - - - -The second SCSI disk (address-wise) is named -/dev/sdb, and so on. - - - - -The first SCSI CD-ROM is named /dev/scd0, also -known as /dev/sr0. - - - - -The master disk on IDE primary controller is named -/dev/hda. - - - - -The slave disk on IDE primary controller is named -/dev/hdb. - - - - -The master and slave disks of the secondary controller can be called -/dev/hdc and /dev/hdd, -respectively. Newer IDE controllers can actually have two channels, -effectively acting like two controllers. - - -The 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/da/partitioning/partition-programs.xml b/da/partitioning/partition-programs.xml deleted file mode 100644 index 468cc7cef..000000000 --- a/da/partitioning/partition-programs.xml +++ /dev/null @@ -1,182 +0,0 @@ - - - - - Debian Partitioning Programs - - -Several varieties of partitioning programs have been adapted by Debian -developers to work on various types of hard disks and computer -architectures. Following is a list of the program(s) applicable for -your architecture. - - - - - - -partman - - -Recommended partitioning tool in Debian. This swiss army knife can -also create filesystems (format in -Windows speak) and assign them to the mountpoints. - - - - - -fdisk - - - The original Linux disk partitioner, good for gurus; read the -fdisk manual page . - - - -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; read -the cfdisk manual page. - - - -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; read the -atari-fdisk manual page. - - - - - -amiga-fdisk - - -Amiga-aware version of fdisk; read the -amiga-fdisk manual page. - - - - - -mac-fdisk - - -Mac-aware version of fdisk; read the -mac-fdisk manual page. - - - - - -pmac-fdisk - - -PowerMac-aware version of fdisk, also used by BVM -and Motorola VMEbus systems; read the -pmac-fdisk manual page. - - - - - -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''. - - - -See the -mac-fdisk manual page for -information on how to create partitions. One key point, is that the -swap partition is identified on Mac type disks 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-x86.xml; -&partition-ia64.xml; -&partition-mips.xml; -&partition-powerpc.xml; -&partition-sparc.xml; - - - - - - diff --git a/da/partitioning/partition/alpha.xml b/da/partitioning/partition/alpha.xml deleted file mode 100644 index a925db8ab..000000000 --- a/da/partitioning/partition/alpha.xml +++ /dev/null @@ -1,56 +0,0 @@ - - - - - Partitioning for &arch-title; - - -If you have chosen to boot from the SRM console, you must use -fdisk to partition your disk, as it is the only -partitioning program that can manipulate the BSD disk labels required -by aboot (remember, the SRM boot block is -incompatible with MS-DOS partition tables - see -). -debian-installer will run fdisk -by default if you have not booted from MILO. - - - -If the disk that you have selected for partitioning already contains a -BSD disk label, fdisk will default to BSD disk -label mode. Otherwise, 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. - - - -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. - - - \ No newline at end of file diff --git a/da/partitioning/partition/hppa.xml b/da/partitioning/partition/hppa.xml deleted file mode 100644 index c9c1c7ff4..000000000 --- a/da/partitioning/partition/hppa.xml +++ /dev/null @@ -1,22 +0,0 @@ - - - - - Partitioning for &arch-title; - - -PALO, the HPPA boot loader, requires a partition of type F0 somewhere -in the first 2GB. This is where the boot loader and an optional kernel -and RAMdisk will be stored, so make it big enough for that -- at least -4Mb (I like 8-16Mb). An additional requirement of the firmware is that -the Linux kernel must reside within the first 2GB of the disk. This -is typically achieved by making the root ext2 partition fit entirely -within the first 2GB of the disk. Alternatively you can create a small -ext2 partition near the start of the disk and mount that on -/boot, since that is the directory where the Linux -kernel(s) will be stored. /boot needs to be big enough -to hold whatever kernels you might wish load; 8-16MB is generally -sufficient. - - - diff --git a/da/partitioning/partition/ia64.xml b/da/partitioning/partition/ia64.xml deleted file mode 100644 index aa0742356..000000000 --- a/da/partitioning/partition/ia64.xml +++ /dev/null @@ -1,129 +0,0 @@ - - - - - Partitioning for &arch-title; - - - -The partman disk partitioner is the default -partitioning tool for the installer. -It manages the set of partitions and their mount points to ensure -that the disks and filesystems 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/da/partitioning/partition/mips.xml b/da/partitioning/partition/mips.xml deleted file mode 100644 index 760156368..000000000 --- a/da/partitioning/partition/mips.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - 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. -In order to be able to store several different kernels in it a size of -10MB is recommended. 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. - - - \ No newline at end of file diff --git a/da/partitioning/partition/powerpc.xml b/da/partitioning/partition/powerpc.xml deleted file mode 100644 index 729f1ba75..000000000 --- a/da/partitioning/partition/powerpc.xml +++ /dev/null @@ -1,55 +0,0 @@ - - - - - Partitioning Newer PowerMacs - - -If you are installing onto a NewWorld PowerMac you must create a -special bootstrap partition to hold the boot loader. The size of this -partition must 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 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. - - - \ No newline at end of file diff --git a/da/partitioning/partition/sparc.xml b/da/partitioning/partition/sparc.xml deleted file mode 100644 index f4996a519..000000000 --- a/da/partitioning/partition/sparc.xml +++ /dev/null @@ -1,33 +0,0 @@ - - - - - Partitioning for &arch-title; - - -Make sure you create a Sun disk label on your boot disk. This is -the only kind of partition scheme that the OpenBoot PROM understands, -and so it's the only scheme from which you can boot. The -s key is used in fdisk to -create Sun disk labels. - - - -Furthermore, on &arch-title; disks, make sure your first partition on -your boot disk starts at cylinder 0. While this is required, it also -means that the first partition will contain the partition table and -the boot block, which are the first two sectors of the disk. You must -not put swap on the first partition of the boot -drive, since swap partitions do not preserve the first few sectors of -the partition. You can put Ext2 or UFS partitions there; these will -leave the partition table and the boot block alone. - - - -It is also advised that the third partition should be of type Whole -disk (type 5), and contain the entire disk (from the first cylinder -to the last). This is simply a convention of Sun disk labels, and -helps the SILO boot loader keep its bearings. - - - \ No newline at end of file diff --git a/da/partitioning/partition/x86.xml b/da/partitioning/partition/x86.xml deleted file mode 100644 index 26c3e4296..000000000 --- a/da/partitioning/partition/x86.xml +++ /dev/null @@ -1,86 +0,0 @@ - - - - - Partitioning for &arch-title; - - -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 BIOS, 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/da/partitioning/partitioning.xml b/da/partitioning/partitioning.xml deleted file mode 100644 index 1ac85cf9b..000000000 --- a/da/partitioning/partitioning.xml +++ /dev/null @@ -1,13 +0,0 @@ - - - - -Partitioning for Debian - -&sizing.xml; -&tree.xml; -&schemes.xml; -&device-names.xml; -&partition-programs.xml; - - diff --git a/da/partitioning/schemes.xml b/da/partitioning/schemes.xml deleted file mode 100644 index 9e6284b37..000000000 --- a/da/partitioning/schemes.xml +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - Recommended Partitioning Scheme - - -For new users, personal Debian boxes, home systems, and other -single-user setups, a single / partition (plus -swap) is probably the easiest, simplest way to go. However, if your -partition is larger than around 6GB, choose ext3 as your partition -type. Ext2 partitions need periodic file system integrity checking, -and this can cause delays during booting when the partition is large. - - - -For multi-user systems or systems with lots of disk space, it's best -to put /usr, /var, -/tmp, and /home each on -their own partitions separate from the / -partition. - - - -You might need a separate /usr/local partition if -you plan to install many programs that are not part of the Debian -distribution. If your machine will be a mail server, you might need -to make /var/mail a separate partition. Often, -putting /tmp on its own partition, for instance -20 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/da/partitioning/sizing.xml b/da/partitioning/sizing.xml deleted file mode 100644 index 3a7441dc6..000000000 --- a/da/partitioning/sizing.xml +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - 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/da/partitioning/tree.xml b/da/partitioning/tree.xml deleted file mode 100644 index bf8bf825b..000000000 --- a/da/partitioning/tree.xml +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - 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 - - mnt - Mount point for mounting a file system temporarily - - proc - Virtual directory for system information - - root - Home directory for the root user - - sbin - Essential system binaries - - 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. - - - - - -The root partition / must always physically -contain /etc, /bin, -/sbin, /lib and -/dev, otherwise you won't be able to boot. -Typically 100 MB is needed for the root partition, but this may vary. - - - - -/usr: all user programs -(/usr/bin), libraries -(/usr/lib), documentation -(/usr/share/doc), etc., are in this -directory. This part of the file system needs most of the space. You -should provide at least 500 MB of disk space. If you want to install -more packages you should increase the amount of space you give this -directory. - - - - -/home: every user will put his data into a -subdirectory of this directory. The size of this 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. - - - - -/var: all variable data like news articles, -e-mails, web sites, the packaging system cache, etc. will be placed -under this directory. The size of this directory depends greatly on -the usage of your computer, 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 gigabytes 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 -megabytes in /var. 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 megabytes in /var. - - - - -/tmp: if a program creates temporary data it will -most likely go in /tmp. 20-50 MB should usually -be enough. - - - - - diff --git a/da/post-install/further-reading.xml b/da/post-install/further-reading.xml deleted file mode 100644 index 0eb4b93ba..000000000 --- a/da/post-install/further-reading.xml +++ /dev/null @@ -1,44 +0,0 @@ - - - - Further Reading and Information - - -If you need information about a particular program, you should first -try man program, or -info program. - - - -There is lots of useful documentation in -/usr/share/doc as well. In particular, -/usr/share/doc/HOWTO and -/usr/share/doc/FAQ contain lots of interesting -information. To submit bugs, look at -/usr/share/doc/debian/bug*. To read about -Debian-specific issues for particular programs, look at -/usr/share/doc/(package name)/README.Debian. - - - -The -Debian web site -contains a large quantity of documentation about Debian. In -particular, see the -Debian FAQ and the -Debian Mailing List Archives. -The Debian community is self-supporting; to subscribe to -one or more of the Debian mailing lists, see the - -Mail List Subscription page. - - - -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/da/post-install/kernel-baking.xml b/da/post-install/kernel-baking.xml deleted file mode 100644 index 8b808858f..000000000 --- a/da/post-install/kernel-baking.xml +++ /dev/null @@ -1,203 +0,0 @@ - - - - Compiling a New Kernel - - -Why would someone want to compile a new kernel? It is often not -necessary since the default kernel shipped with Debian handles most -configurations. 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 - - - - - -The compact and idepci flavors don't come with sound. Although -the vanilla kernel does, it might not work for other reasons. - - - - -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 network firewalling) - - - - -run a 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. - - - -If you are compiling a kernel for UltraSPARC you will need to be sure -you have installed the egcs64 package. This is -the preferred compiler for 64bit SPARC kernels. The default -gcc will also compile 64bit kernels, but is not as -stable. Plus, if you do not use egcs64 and you -encounter kernel problems, you will most likely be asked to recompile -the kernel using egcs64 in order to verify your -problem still exists. After installing egcs64 -be sure to run update-alternatives --config -sparc64-linux-gcc as root, and be sure that -egcs64 is being used for this program. - - - -Hereafter, we'll assume your kernel source will be located in -/usr/local/src and that your kernel version is -&kernelversion;. As root, create a directory under -/usr/local/src and change the owner of that -directory to your normal non-root account. As your normal non-root -account, change your directory to where you want to unpack the kernel -sources (cd /usr/local/src), extract the kernel -sources (tar xjf -/usr/src/kernel-source-&kernelversion;.tar.bz2), change your -directory to it (cd -kernel-source-&kernelversion;/). - - - -Now, you can configure your kernel. Run make -xconfig if X11 is installed, configured and being run, -make menuconfig otherwise (you'll need -ncurses-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'' - - and ``Enhanced Real Time -Clock Support'' in ``Character devices'' (they are - (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/da/post-install/new-to-unix.xml b/da/post-install/new-to-unix.xml deleted file mode 100644 index c011f5583..000000000 --- a/da/post-install/new-to-unix.xml +++ /dev/null @@ -1,32 +0,0 @@ - - - - - - If You Are New to Unix - - -If you are new to Unix, you probably should go out and buy some books -and do some reading. The - -Unix FAQ -contains a number of references to books and Usenet news groups which -should help you out. You can also take a look at the - -User-Friendly Unix FAQ. - - - -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/da/post-install/orientation.xml b/da/post-install/orientation.xml deleted file mode 100644 index d4ba05f3f..000000000 --- a/da/post-install/orientation.xml +++ /dev/null @@ -1,109 +0,0 @@ - - - - - Orienting Yourself to Debian - - -Debian is a little different from other distributions. Even if you're -familiar with Linux in other distributions, there are things you -should know about Debian to help you to keep your system in a good, -clean state. This chapter contains material to help you get oriented; -it is not intended to be a tutorial for how to use Debian, but just a -very brief glimpse of the system for the very rushed. - - - - Debian Packaging System - - -The most important concept to grasp is the Debian packaging system. -In essence, large parts of your system should be considered under the -control of the packaging system. These include: - - - - -/usr (excluding /usr/local) - - - - -/var (you could make -/var/local and be safe in there) - - - - -/bin - - - - -/sbin - - - - -/lib - - - - -For instance, if you replace /usr/bin/perl, that -will work, but then if you upgrade your perl -package, the file you put there will be replaced. Experts can get -around this by putting packages on ``hold'' in -aptitude. - - - -One of the best installation methods is apt. You can use the command -line version apt-get or full-screen text version -aptitude. Note apt will also let you merge -main, contrib, and non-free so you can have export-restricted packages -as well as standard versions. - - - - - Application Version Management - - - -Alternative versions of applications are managed by update-alternatives. If -you are maintaining multiple versions of your applications, read the -update-alternatives man page. - - - - - Cron Job Management - - -Any jobs under the purview of the system administrator should be in -/etc, since they are configuration files. If you -have a root cron job for daily, weekly, or nightly 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/da/post-install/post-install.xml b/da/post-install/post-install.xml deleted file mode 100644 index 9cd02993c..000000000 --- a/da/post-install/post-install.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - - - Next Steps and Where to Go From Here - -&new-to-unix.xml; -&orientation.xml; -&further-reading.xml; -&kernel-baking.xml; - - diff --git a/da/post-install/shutdown.xml b/da/post-install/shutdown.xml deleted file mode 100644 index e326be12d..000000000 --- a/da/post-install/shutdown.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - - 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/da/preparing/backup.xml b/da/preparing/backup.xml deleted file mode 100644 index 35c7e224a..000000000 --- a/da/preparing/backup.xml +++ /dev/null @@ -1,41 +0,0 @@ - - - - - Back Up Your Existing Data! - - -Before you start, make sure to back up every file that is now on your -system. If this is the first time a non-native operating system has -been installed on your computer, it's quite likely you will need to -re-partition your disk to make room for &debian;. Anytime you -partition your disk, you should count on losing everything on the -disk, no matter what program you use to do it. The programs used in -installation are quite reliable and most have seen years of use; but -they are also quite powerful and a false move can cost you. Even after -backing up be careful and think about your answers and actions. Two -minutes of thinking can save hours of unnecessary work. - - - -If you are creating a multi-boot system, make sure that you have the -distribution media of any other present operating systems on hand. -Especially if you repartition your boot drive, you might find that you -have to reinstall your operating system's boot loader, or in many -cases the whole operating system itself and all files on the affected -partitions. - - - - - -With the exception of the BVM and Motorola VMEbus computers, the only -supported installation method for m68k systems is booting from a local -disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these -machines you will need the original operating system in order to boot -Linux. In order to boot Linux on the BVM and Motorola VMEbus machines -you will need the ``BVMBug'' or ``16xBug'' boot ROMs. - - - - diff --git a/da/preparing/bios-setup/i386.xml b/da/preparing/bios-setup/i386.xml deleted file mode 100644 index 36b0c615f..000000000 --- a/da/preparing/bios-setup/i386.xml +++ /dev/null @@ -1,331 +0,0 @@ - - - - - Invoking the BIOS Set-Up Menu - - - -BIOS provides the basic functions needed to boot your machine to allow -your operating system to access your hardware. Your system probably -provides a BIOS setup menu, which is used to configure the BIOS. -Before installing, you must ensure that your BIOS -is set up correctly; not doing so can lead to intermittent crashes or -an inability to install Debian. - - - -The rest of this section is lifted from the -, answering the question, "How do I -enter the CMOS configuration menu?". How you access the BIOS (or -``CMOS'') configuration menu depends on who wrote your BIOS software: - - - - - - - - AMI BIOS - - -Delete key during the POST (power on self test) - - - - - - Award BIOS - - - - CtrlAltEsc -, or Delete key during the POST - - - - -DTK BIOS - - -Esc key during the POST - - - - -IBM PS/2 BIOS - - - - CtrlAltInsert - -after - - CtrlAltDelete - - - - - - - Phoenix BIOS - - - - CtrlAltEsc - -or - - CtrlAltS - -or -F1 - - - - - - - -Information on invoking other BIOS routines can be found in -. - - - -Some &arch-title; machines don't have a CMOS configuration menu in the -BIOS. They require a software CMOS setup program. If you don't have -the Installation and/or Diagnostics diskette for your machine, you can -try using a shareware/freeware program. Try looking in -. - - - - - Boot Device Selection - - - -Many BIOS setup menus allow you to select the devices that will be -used to bootstrap the system. Set this to look for a bootable -operating system on A: (the first floppy disk), -then optionally the first CD-ROM device (possibly appearing as -D: or E:), and then from -C: (the first hard disk). This setting enables -you to boot from either a floppy disk or a CD-ROM, which are the two -most common boot devices used to install Debian. - - - -If you have a newer SCSI controller and you have a CD-ROM device -attached to it, you are usually able to boot from the CD-ROM. All you -have to do is enable booting from a CD-ROM in the SCSI-BIOS of your -controller. - - - -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/da/preparing/bios-setup/m68k.xml b/da/preparing/bios-setup/m68k.xml deleted file mode 100644 index e0b54a403..000000000 --- a/da/preparing/bios-setup/m68k.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - - - 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/da/preparing/bios-setup/powerpc.xml b/da/preparing/bios-setup/powerpc.xml deleted file mode 100644 index 0842c2cdc..000000000 --- a/da/preparing/bios-setup/powerpc.xml +++ /dev/null @@ -1,56 +0,0 @@ - - - - - - Invoking OpenFirmware - - -There is normally no need to set up the BIOS (called OpenFirmware) on -&arch-title; systems. PReP and CHRP are equipped with OpenFirmware, -but unfortunately, the means you use to invoke it vary from -manufacturer to manufacturer. You'll have to consult the hardware -documentation which came with your machine. - - - -On &arch-title; Macintoshes, you invoke OpenFirmware with -Command 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/da/preparing/bios-setup/s390.xml b/da/preparing/bios-setup/s390.xml deleted file mode 100644 index 369b51873..000000000 --- a/da/preparing/bios-setup/s390.xml +++ /dev/null @@ -1,106 +0,0 @@ - - - - - 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 vmrdr -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/da/preparing/bios-setup/sparc.xml b/da/preparing/bios-setup/sparc.xml deleted file mode 100644 index 7aaac58b7..000000000 --- a/da/preparing/bios-setup/sparc.xml +++ /dev/null @@ -1,99 +0,0 @@ - - - - - Invoking OpenBoot - - - -OpenBoot provides the basic functions needed to boot the &arch-title; -architecture. This is rather similar in function to the BIOS in the -x86 architecture, although much nicer. The Sun boot PROMs have a -built-in forth interpreter which lets you do quite a number of things -with your machine, such as diagnostics, 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. - - - - - - 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/da/preparing/install-overview.xml b/da/preparing/install-overview.xml deleted file mode 100644 index e5479abae..000000000 --- a/da/preparing/install-overview.xml +++ /dev/null @@ -1,185 +0,0 @@ - - - - - Overview of the Installation Process - - -First, just a note about re-installations. With Debian, a -circumstance that will require a complete re-installation of your -system is very rare; perhaps mechanical failure of the hard disk would -be the most common case. - - - -Many common operating systems may require a complete installation to -be performed when critical failures take place or for upgrades to new -OS versions. Even if a completely new installation isn't required, -often the programs you use must be re-installed to operate properly in -the new OS. - - - -Under &debian;, it is much more likely that your OS can be repaired -rather than replaced if things go wrong. Upgrades never require a -wholesale installation; you can always upgrade in-place. And the -programs are almost always compatible with successive OS releases. If -a new program version requires newer supporting software, the Debian -packaging system ensures that all the necessary software is -automatically identified and installed. The point is, much effort has -been put into avoiding the need for re-installation, so think of it as -your very last option. The installer is not -designed to re-install over an existing system. - - - -Here's a road map for the steps you will take during the installation -process. - - - - - - -Back up any existing data or documents on the hard disk where you -plan to install. - - - - -Gather information about your computer and any needed documentation, -before starting the installation. - - - - -Create partitionable space for Debian on your hard disk. - - - - -Locate and/or download the installer software and any specialized -driver files your machine requires (except Debian CD users). - - - - -Set up boot tapes/floppies/USB sticks, or place boot files (most Debian -CD users can boot from one of the CDs). - - - - -Boot the installation system. - - - - -Select installation language. - - - - -Activate the ethernet network connection, if available. - - - - - -Configure one network interface. - - - - -Open a ssh connection to the new system. - - - - -Attach one or more DASDs (Direct Access Storage Device). - - - - - -Create and mount the partitions on which Debian will be installed. - - - - -Watch the automatic download/install/setup of the -base system. - - - - -Install a boot loader -which can start up &debian; and/or your existing system. - - - - -Load the newly installed system for the first time, and make some -initial system settings. - - - - -Open a ssh connection to the new system. - - - - -Install additional software (tasks -and/or packages), at your discretion. - - - - - - -If you have problems during the installation, it helps to know which -packages are involved in which steps. Introducing the leading software -actors in this installation drama: - - - -The installer software, debian-installer, is -the primary concern of this manual. It detects hardware and loads -appropriate drivers, uses dhcp-client to set up the -network connection, and runs debootstrap to install -the base system packages. Many more actors play smaller parts in this process, -but debian-installer has completed its task when -you load the new system for the first time. - - - -Upon loading the new base system, base-config -supervises adding users, setting a time zone (via -tzsetup), and setting up the -package installation system (using apt-setup). It then -launches tasksel which can be used to select large -groups of related programs, and in turn can run aptitude -which allows you to choose individual software packages. - - - -When debian-installer finishes, before the -first system load, you have only a very basic command line driven -system. The graphical interface which displays windows on your monitor -will not be installed unless you select it during the final steps, -with either tasksel or -aptitude. It's optional because many &debian; -systems are servers which don't really have any need for a graphical -user interface to do their job. - - - -Just be aware that the X system is completely separate from -debian-installer, and in fact is much more -complicated. Installation and trouble shooting of the X window -installation is not within the scope of this manual. - - - - diff --git a/da/preparing/minimum-hardware-reqts.xml b/da/preparing/minimum-hardware-reqts.xml deleted file mode 100644 index 5a3641a4c..000000000 --- a/da/preparing/minimum-hardware-reqts.xml +++ /dev/null @@ -1,135 +0,0 @@ - - - - -Meeting Minimum Hardware Requirements - - -Once you have gathered information about your computer's hardware, -check that your hardware will let you do the type of installation -that you want to do. - - - -Depending on your needs, you might manage with less than some of the -recommended hardware listed in the table below. However, most users -risk being frustrated if they ignore these suggestions. - - - -A Pentium 100 is the minimum recommended for desktop -systems, and a Pentium II-300 for a Server. - - - -A 68030 or better processor is recommended for m68k -installs. You may get by with a little less drive space than shown. - - - -Any OldWorld or NewWorld PowerPC can serve well -as a Desktop System. For servers, a minimum 132-Mhz machine is -recommended. - - - - -Recommended Minimum System Requirements - - - - Install TypeRAMHard Drive - - - - - - No desktop - 24 megabytes - 450 megabytes - - With Desktop - 64 megabytes - 1 gigabyte - - Server - 128 megabytes - 4 gigabytes - - -
- - - -Here is a sampling of some common Debian system configurations. -You can also get an idea of the disk space used by related groups -of programs by referring to . - - - - - - Standard Server - - -This is a small server profile, useful for a stripped down server -which does not have a lot of niceties for shell users. It includes an -FTP server, a web server, DNS, NIS, and POP. For these 100MB of disk -space would suffice, and then you would need to add space -for any data you serve up. - - - - - - Desktop - - -A standard desktop box, including the X window system, full desktop -environments, sound, editors, etc. You'll need about 2GB using the -standard desktop task, though it can be done in far less. - - - - - - Work Console - - -A more stripped-down user machine, without the X window system or X -applications. Possibly suitable for a laptop or mobile computer. The -size is around 140MB. - - - - - - Developer - - -A desktop setup with all the development packages, such as Perl, C, -C++, etc. Size is around 475MB. Assuming you are adding X11 and some -additional packages for other uses, you should plan around 800MB for -this type of machine. - - - - - - -Remember that these sizes don't include all the other materials which -are usually to be found, such as user files, mail, and data. It is -always best to be generous when considering the space for your own -files and data. Notably, the /var partition contains -a lot of state information specific to Debian in addition to its regular -contents like logfiles. The -dpkg files (with information on all installed -packages) can easily consume 20MB. Also, -apt-get puts downloaded packages here before they are -installed. You should -usually allocate at least 100MB for /var. - - - - - diff --git a/da/preparing/needed-info.xml b/da/preparing/needed-info.xml deleted file mode 100644 index d2a59b07a..000000000 --- a/da/preparing/needed-info.xml +++ /dev/null @@ -1,407 +0,0 @@ - - - - - Information You Will Need - - - Documentation - - - Installation Manual - - - -This file you are now reading, in plain ASCII, HTML or PDF format. - - - - - - - - - - - - - - - - - - - - - - - - Hardware documentation - - -Often contains useful information on configuring or using your hardware. - - - - - - -Linux Hardware Compatibility HOWTO - - - - - -Linux/m68k FAQ - - - - - -Linux/Alpha FAQ - - - - - -Linux for SPARC Processors FAQ - - - - - -Linux/Mips Howto - - - - - - - - - &arch-title; Hardware References - - - -Installation instructions and device drivers (DASD, XPRAM, Console, - tape, z90 crypto, chandev, network) for Linux on &arch-title; using - kernel 2.4 - - - - - - -Device Drivers and Installation Commands - - - - - - -IBM Redbook describing how Linux can be combined with z/VM on -zSeries and &arch-title; hardware. - - - - - - - -Linux for &arch-title; - - - - - - -IBM Redbook describing the Linux distributions available for the -mainframe. It has no chapter about Debian but the basic installation -concepts are the same across all &arch-title; distributions. - - - - - - - -Linux for IBM eServer zSeries and &arch-title;: Distributions - - - - - - - - - Finding Sources of Hardware Information - - -In many cases, the installer will be able to automatically detect your -hardware. But to be prepared, we do recommend familiarising -yourself with your hardware before the install. - - - -Hardware information can be gathered from: - - - - - - -The manuals that come with each piece of hardware. - - - - -The BIOS setup screens of your computer. You can view these screens -when you start your computer by pressing a combination of keys. Check -your manual for the combination. Often, it is the Delete key. - - - - -The cases and boxes for each piece of hardware. - - - - - -The System window in the Windows Control Panel. - - - - - -System commands or tools in another operating system, including file -manager displays. This source is especially useful for information -about RAM and hard drive memory. - - - - -Your system administrator or Internet Service Provider. These -sources can tell you the settings you need to set up your -networking and e-mail. - - - - - - - -Hardware Information Needed for an Install - - - - HardwareInformation You Might Need - - - - - - Hard Drives - How many you have. - -Their order on the system. - - Whether IDE or SCSI (most computers are IDE). - -Available free space. -Partitions. - - Partitions where other operating systems are installed. - - - - Monitor - Model and manufacturer. - -Resolutions supported. -Horizontal refresh rate. -Vertical refresh rate. - - Color depth (number of colors) supported. - -Screen size. - - - Mouse - Type: serial, PS, or USB. - -Port. -Manufacturer. -Number of buttons. - - - Network - Model and manufacturer. - -Type of adapter. - - - Printer - Model and manufacturer. - -Printing resolutions supported. - - - Video Card - Model and manufacturer. - -Video RAM available. - - Resolutions and color depths supported (these should be - checked against your monitor's capabilities). - - - - DASD - Device number(s). - -Available free space. - - - Network - Type of adapter. - -Device numbers. -Relative adapter number for OSA cards. - -
- - - - - - Hardware Compatibility - - - -Many brand name products work without trouble on Linux. Moreover, -hardware for Linux is improving daily. However, Linux still does not -run as many different types of hardware as some operating systems. - - - -In particular, Linux usually cannot run hardware that requires a -running version of Windows to work. - - - -Although some Windows-specific hardware can be made to run on Linux, -doing so usually requires extra effort. In addition, Linux drivers -for Windows-specific hardware are usually specific to one Linux -kernel. Therefore, they can quickly become obsolete. - - - -So called win-modems are the most common type of this hardware. -However, printers and other equipment may also be Windows-specific. - - - -You can check hardware compatibility by: - - - - -Checking manufacturers' web sites for new drivers. - - - - -Looking at web sites or manuals for information about emulation. -Lesser known brands can sometimes use the drivers or settings for -better-known ones. - - - - -Checking hardware compatibility lists for Linux on web sites -dedicated to your architecture. - - - - -Searching the Internet for other users' experiences. - - - - - - - - - Network Settings - - - -If your computer is connected to a network 24 hours a day (i.e., an -Ethernet or equivalent connection — not a PPP connection), you -should ask your network's system administrator for this information. - - - - -Your host name (you may be able to decide this on your own). - - - - -Your domain name. - - - - -Your computer's IP address. - - - - -The netmask to use with your network. - - - - -The IP address of the default gateway system you should route to, if -your network has a gateway. - - - - -The system on your network that you should use as a DNS (Domain Name -Service) server. - - - - - - -On the other hand, if your administrator tells you that a DHCP server -is available and is recommended, then you don't need this information -because the DHCP server will provide it directly to your computer -during the installation process. - - - -If you use a wireless network, you should also find out: - - - - -ESSID of your wireless network. - - - - -WEP security key (if applicable). - - - - - - - - diff --git a/da/preparing/non-debian-partitioning.xml b/da/preparing/non-debian-partitioning.xml deleted file mode 100644 index 2522966be..000000000 --- a/da/preparing/non-debian-partitioning.xml +++ /dev/null @@ -1,204 +0,0 @@ - - - - - Pre-Partitioning for Multi-Boot Systems - - -Partitioning your disk simply refers to the act of breaking up your -disk into sections. Each section is then independent of the others. -It's roughly equivalent to putting up walls inside a house; if you add -furniture to one room it doesn't affect any other room. - - - -Whenever this section talks about ``disks'' you should translate this -into a DASD or VM minidisk in the &arch-title; world. Also a machine means -an LPAR or VM guest in this case. - - - -If you already have an operating system on your system - - -(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, …) - - -and want to stick Linux on the same disk, you will need to repartition -the disk. Debian requires its own hard disk partitions. It cannot be -installed on Windows or MacOS partitions. It may be able to share some -partitions with other Linux systems, but that's not covered here. At -the very least you will need a dedicated partition for the Debian -root. - - - -You can find information about your current partition setup by using -a partitioning tool for your current operating system - -, such as fdisk or PartitionMagic - -, such as Drive Setup, HD Toolkit, or MacTools - -, such as HD SC Setup, HDToolBox, or SCSITool - -, such as the VM diskmap - -. Partitioning tools always provide a way to show existing partitions -without making changes. - - - -In general, changing a partition with a file system already on -it will destroy any information there. Thus you should always make -backups before doing any repartitioning. Using the analogy of the -house, you would probably want to move all the furniture out of the -way before moving a wall or you risk destroying it. - - - -FIXME: write about HP-UX disks? - - - -If your computer has more than one hard disk, you may want to dedicate -one of the hard disks completely to Debian. If so, you don't need to -partition that disk before booting the installation system; the -installer's included partitioning program can handle the job nicely. - - - -If your machine has only one hard disk, and you would like to -completely replace the current operating system with &debian;, -you also can wait to partition as part of the installation process -(), after you have booted the -installation system. However this only works if you plan to boot the -installer system from tapes, CD-ROM or files on a connected machine. -Consider: if you boot from files placed on the hard disk, and then -partition that same hard disk within the installation system, thus -erasing the boot files, you'd better hope the installation is -successful the first time around. At the least in this case, you -should have some alternate means of reviving your machine like the -original system's installation tapes or CDs. - - - -If your machine already has multiple partitions, and enough space can -be provided by deleting and replacing one or more of them, then you -too can wait and use the Debian installer's partitioning program. You -should still read through the material below, because there may be -special circumstances like the order of the existing partitions within -the partition map, that force you to partition before installing -anyway. - - - -If your machine has a FAT filesystem, as used by DOS and older versions of -Windows, you can wait and use Debian installer's partitioning program to -resize the FAT filesystem. - - - -If none of the above apply, you'll need to partition your hard disk before -starting the installation to create partitionable space for -Debian. If some of the partitions will be owned by other operating -systems, you should create those partitions using native operating -system partitioning programs. We recommend that you do -not attempt to create Debian Linux partitions -using another operating system's tools. Instead, you should just -create the native operating system's partitions you will want to -retain. - - - -If you are going to install more than one operating system on the same -machine, you should install all other system(s) before proceeding with -Linux installation. Windows and other OS installations may destroy -your ability to start Linux, or encourage you to reformat non-native -partitions. - - - -You can recover from these actions or avoid them, but installing -the native system first saves you trouble. - - - -In order for OpenFirmware to automatically boot &debian; the Linux -partitions should appear before all other partitions on the disk, -especially MacOS boot partitions. This should be kept in mind when -pre-partitioning; you should create a Linux placeholder partition to -come before the other bootable partitions on the -disk. (The small partitions dedicated to Apple disk drivers are not -bootable.) You can delete the placeholder with the Linux partition -tools later during the actual install, and replace it with Linux -partitions. - - - -If you currently have one hard disk with one partition (a common setup -for desktop computers), and you want to multi-boot the native -operating system and Debian, you will need to: - - - - -Back up everything on the computer. - - - - -Boot from the native operating system installer media such as CD-ROM -or tapes. - -When booting from a MacOS CD, hold the -c key while -booting to force the CD to become the active MacOS system. - - - - -Use the native partitioning tools to create native system -partition(s). Leave either a place holder partition or free space for -&debian;. - - - - -Install the native operating system on its new partition. - - - - -Boot back into the native system to verify everything's OK, - and to download the Debian installer boot files. - - - - -Boot the Debian installer to continue installing Debian. - - - - - - -&nondeb-part-alpha.xml; -&nondeb-part-x86.xml; -&nondeb-part-m68k.xml; -&nondeb-part-sparc.xml; -&nondeb-part-powerpc.xml; - - diff --git a/da/preparing/nondeb-part/alpha.xml b/da/preparing/nondeb-part/alpha.xml deleted file mode 100644 index 591a09791..000000000 --- a/da/preparing/nondeb-part/alpha.xml +++ /dev/null @@ -1,92 +0,0 @@ - - - - - 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 the disk label may overlap. Moreover, 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). Apart from satisfying this requirement, you -should carefully avoid creating overlapping partitions. - - - -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 these two partitions are only required for compatibility; -you must not put a file system onto them, or you'll destroy data. If -you're not going to share the disk with Tru64 Unix or one of the free -4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or NetBSD), -you can ignore these requirements, and use the partitioning tool from -the Debian boot disks. See for details. - - - -Disks can be partitioned with the graphical disk configuration tool that -is accessible through the Application Manager, or with the command-line -disklabel utility. Partition type for the Linux file -system should be set to `resrvd8'. This can only be done via -disklabel; however, all other configuration can easily be -performed with the graphical tool. - - - -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. - - - diff --git a/da/preparing/nondeb-part/m68k.xml b/da/preparing/nondeb-part/m68k.xml deleted file mode 100644 index 332769043..000000000 --- a/da/preparing/nondeb-part/m68k.xml +++ /dev/null @@ -1,127 +0,0 @@ - - - - - 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/da/preparing/nondeb-part/powerpc.xml b/da/preparing/nondeb-part/powerpc.xml deleted file mode 100644 index 31094b54b..000000000 --- a/da/preparing/nondeb-part/powerpc.xml +++ /dev/null @@ -1,43 +0,0 @@ - - - - - MacOS/OSX Partitioning - - - -The Apple Drive Setup application can be found in the -Utilities folder on the MacOS CD. It will not adjust existing -partitions; it is limited to partitioning the entire disk at once. The -disk driver partitions don't show up in Drive Setup. - - - -Remember to create a placeholder partition for GNU/Linux, preferably -positioned first in the disk layout. it doesn't matter what type it -is, it will be deleted and replaced later inside the &debian; 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 HFS+ (aka MacOS Extended) -or UFS 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 and MS-DOS FAT partitions are -supported by both MacOS and Linux. - - - diff --git a/da/preparing/nondeb-part/sparc.xml b/da/preparing/nondeb-part/sparc.xml deleted file mode 100644 index 016d55015..000000000 --- a/da/preparing/nondeb-part/sparc.xml +++ /dev/null @@ -1,44 +0,0 @@ - - - - - Partitioning from SunOS - - - -It's perfectly fine to partition from SunOS; in fact, if you intend to -run both SunOS and Debian on the same machine, it is recommended that -you partition using SunOS prior to installing Debian. The Linux -kernel understands Sun disk labels, so there are no problems there. -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/da/preparing/nondeb-part/x86.xml b/da/preparing/nondeb-part/x86.xml deleted file mode 100644 index a6d1f1be7..000000000 --- a/da/preparing/nondeb-part/x86.xml +++ /dev/null @@ -1,119 +0,0 @@ - - - - - Partitioning From DOS or Windows - - -If you are manipulating existing FAT or NTFS partitions, it is -recommended that you either use the scheme below or native Windows or -DOS tools. Otherwise, it is not really necessary to partition from DOS -or Windows; the 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, -and in most cases you should not need to use the method described below, -unless you need to move the start of the filesystem. - - - -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 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/da/preparing/pre-install-bios-setup.xml b/da/preparing/pre-install-bios-setup.xml deleted file mode 100644 index 049d336bb..000000000 --- a/da/preparing/pre-install-bios-setup.xml +++ /dev/null @@ -1,148 +0,0 @@ - - - - - Pre-Installation Hardware and Operating System Setup - - -This section will walk you through pre-installation hardware setup, if -any, that you will need to do prior to installing Debian. Generally, -this involves checking and possibly changing firmware settings for -your system. The ``firmware'' is the core software used by the -hardware; it is most critically invoked during the bootstrap process -(after power-up). Known hardware issues affecting the reliability of -&debian; on your system are also highlighted. - - - -&bios-setup-i386.xml; -&bios-setup-m68k.xml; -&bios-setup-powerpc.xml; -&bios-setup-sparc.xml; -&bios-setup-s390.xml; - - Hardware Issues to Watch Out For - - -Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It -sometimes works, but is sensitive to temperature and other factors and -can actually damage your system. One of the authors of this document -over-clocked his own system for a year, and then the system started -aborting the gcc program with an unexpected signal -while it was compiling the operating system kernel. Turning the CPU -speed back down to its rated value solved the problem. - - - -The gcc compiler is often the first thing to die -from bad memory modules (or other hardware problems that change data -unpredictably) because it builds huge data structures that it -traverses repeatedly. An error in these data structures will cause it -to execute an illegal instruction or access a non-existent -address. The symptom of this will be gcc dying from -an unexpected signal. - - - -Atari TT RAM boards are notorious for RAM problems under Linux; if you -encounter any strange problems, try running at least the kernel in -ST-RAM. Amiga users may need to exclude RAM using a booter memfile. - - - -FIXME: more description of this needed. - - - - - -The very best motherboards support parity RAM and will actually tell -you if your system has a single-bit error in RAM. Unfortunately, they -don't have a way to fix the error, thus they generally crash -immediately after they tell you about the bad RAM. Still, it's better -to be told you have bad memory than to have it silently insert errors -in your data. Thus, the best systems have motherboards that support -parity and true-parity memory modules; see -. - - - -If you do have true-parity RAM and your motherboard can handle it, be -sure to enable any BIOS settings that cause the motherboard to -interrupt on memory parity errors. - - - - The Turbo Switch - - -Many systems have a turbo switch that controls -the speed of the CPU. Select the high-speed setting. If your BIOS -allows you to disable software control of the turbo switch (or -software control of CPU speed), do so and lock the system in -high-speed mode. We have one report that on a particular system, while -Linux is auto-probing (looking for hardware devices) it can -accidentally touch the software control for the turbo switch. - - - - - Cyrix CPUs and Floppy Disk Errors - - -Many users of Cyrix CPUs have had to disable the cache in their -systems during installation, because the floppy disk has errors if -they do not. If you have to do this, be sure to re-enable your cache -when you are finished with installation, as the system runs -much slower with the cache disabled. - - - -We don't think this is necessarily the fault of the Cyrix CPU. It may -be something that Linux can work around. We'll continue to look into -the problem. For the technically curious, we suspect a problem with -the cache being invalid after a switch from 16-bit to 32-bit code. - - - - - Peripheral Hardware Settings - - -You may have to change some settings or jumpers on your computer's -peripheral cards. Some cards have setup menus, while others rely on -jumpers. This document cannot hope to provide complete information on -every hardware device; what it hopes to provide is useful tips. - - - -If any cards provide ``mapped memory'', the memory should be mapped -somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 -megabyte) or at an address at least 1 megabyte greater than the total -amount of RAM in your system. - - - - - USB keyboards - - -If you have no AT-style keyboard and only a USB model, you may need -to enable legacy AT keyboard emulation in your BIOS setup. Only do this if -the installation system fails to use your keyboard in USB mode. Consult -your main board manual and look in the BIOS for "Legacy keyboard -emulation" or "USB keyboard support" options. - - - - - More than 64 MB RAM - - -The Linux Kernel can not always detect what amount of RAM you have. If -this is the case please look at . - - - - - diff --git a/da/preparing/preparing.xml b/da/preparing/preparing.xml deleted file mode 100644 index 7fb274e80..000000000 --- a/da/preparing/preparing.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - Before Installing &debian; - - -This chapter deals with the preparation for installing Debian before you even -boot the installer. This includes backing up your data, gathering information -about your hardware, and locating any necessary information. - - - -&install-overview.xml; -&backup.xml; -&needed-info.xml; -&minimum-hardware-reqts.xml; -&non-debian-partitioning.xml; -&pre-install-bios-setup.xml; - - diff --git a/da/using-d-i/components.xml b/da/using-d-i/components.xml deleted file mode 100644 index b5de1e2d7..000000000 --- a/da/using-d-i/components.xml +++ /dev/null @@ -1,158 +0,0 @@ - - - - - Using Individual Components - - -In this section we will describe each installer component in -detail. The components have been grouped into stages that should -be recognisable for users. They are presented in the order they -appear during the install. Note that not all modules will be used -for every installation; which modules are actually used depends on -the installation method you use and on your hardware. - - - - - Setting up Debian Installer and Hardware Configuration - - -Let's assume the Debian Installer has booted and you are facing its -first screen. At this time, the capabilities of &d-i; are still quite -limited. It doesn't know much about your hardware, preferred language, -or even the task it should perform. Don't worry. Because &d-i; is quite -clever, it can automatically probe your hardware, locate the rest -of its components and upgrade itself to a capable installation system. - -However, you still need to help &d-i; with some information it can't -determine automatically (like selecting your preferred language, keyboard -layout or desired network mirror). - - - -You will notice that &d-i; performs hardware detection -several times during this stage. The first time is targeted specifically -at the hardware needed to load installer components (e.g. your CD-ROM or -network card). As not all drivers may be available during this first run, -hardware detection needs to be repeated later in the process. - - - -&module-lowmem.xml; -&module-languagechooser.xml; -&module-countrychooser.xml; -&module-kbd-chooser.xml; -&module-s390-netdevice.xml; -&module-s390-dasd.xml; -&module-ddetect.xml; -&module-cdrom-detect.xml; -&module-iso-scan.xml; -&module-anna.xml; -&module-netcfg.xml; -&module-choose-mirror.xml; - - - - - Partitioning and Mount Point Selection - - -At this time, after hardware detection has been executed a final time, -&d-i; should be at its full strength, customized for the user's needs -and ready to do some real work. - -As the title of this section indicates, the main task of the next few -components lies in partitioning your disks, creating filesystems, -assigning mountpoints and optionally configuring closely related issues -like LVM or RAID devices. - - - -&module-partman.xml; -&module-autopartkit.xml; -&module-partitioner.xml; -&module-partconf.xml; -&module-mdcfg.xml; -&module-partman-lvm.xml; - - - - Installing the Base System - - -Although this stage is the least problematic, it consumes most time of -the install because it downloads, verifies and unpacks the whole base -system. If you have a slow computer or network connection, this could -take some time. - - - -&module-base-installer.xml; - - - - Making Your System Bootable - - - -If you are installing a diskless workstation, obviously, booting off -the local disk isn't a meaningful option, and this step will be -skipped. You may wish to set the OpenBoot to boot -from the network by default; see . - - - -Note that multiple operating systems booting on a single machine is -still something of a black art. This document does not even attempt -to document the various boot managers, which vary by architecture and -even by subarchitecture. You should see your boot manager's -documentation for more information. - - - -&module-os-prober.xml; -&module-alpha-aboot-installer.xml; -&module-hppa-palo-installer.xml; -&module-x86-grub-installer.xml; -&module-x86-lilo-installer.xml; -&module-ia64-elilo-installer.xml; -&module-mips-arcboot-installer.xml; -&module-mipsel-colo-installer.xml; -&module-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; - - - - Finishing the First Stage - - -These are the last bits to do before rebooting to your new Debian. It -mostly consists of tidying up after the &d-i;. - - - -&module-finish-install.xml; - - - - Miscellaneous - - -The components listed in this section are usually not involved in the -installation process, but are waiting in the background to help the -user in case something goes wrong. - - - -&module-save-logs.xml; -&module-cdrom-checker.xml; -&module-shell.xml; -&module-baseconfig.xml; - - diff --git a/da/using-d-i/modules/alpha/aboot-installer.xml b/da/using-d-i/modules/alpha/aboot-installer.xml deleted file mode 100644 index 60eb48ed6..000000000 --- a/da/using-d-i/modules/alpha/aboot-installer.xml +++ /dev/null @@ -1,19 +0,0 @@ - - - - - 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/da/using-d-i/modules/anna.xml b/da/using-d-i/modules/anna.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/anna.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/autopartkit.xml b/da/using-d-i/modules/autopartkit.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/autopartkit.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/base-installer.xml b/da/using-d-i/modules/base-installer.xml deleted file mode 100644 index c2efe72e9..000000000 --- a/da/using-d-i/modules/base-installer.xml +++ /dev/null @@ -1,31 +0,0 @@ - - - - - Base System Installation - - - -During the Base installation, package unpacking and setup messages are -redirected to tty3. You can access this -terminal by pressing -Left AltF3; -get back to the main installer process with -Left AltF1. - - - - -The unpack/setup messages generated by the base installation are saved in -/var/log/messages when the installation is -performed over a serial console. - - - -As part of the installation, a Linux kernel will be installed. At the default -priority, the installer will choose one for you that best matches your -hardware. In lower priority modes, you will be able to choose from a list -of available kernels. - - - diff --git a/da/using-d-i/modules/baseconfig.xml b/da/using-d-i/modules/baseconfig.xml deleted file mode 100644 index 8bbae29d6..000000000 --- a/da/using-d-i/modules/baseconfig.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - Running <command>base-config</command> From Within &d-i; - - - -It is possible to configure the base system within the first stage -installer (before rebooting from the hard drive), by running -base-config in a chroot -environment. This is mainly useful for testing the installer and a -vast majority of people should avoid it. - - - - diff --git a/da/using-d-i/modules/cdrom-checker.xml b/da/using-d-i/modules/cdrom-checker.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/da/using-d-i/modules/cdrom-checker.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/cdrom-detect.xml b/da/using-d-i/modules/cdrom-detect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/cdrom-detect.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/choose-mirror.xml b/da/using-d-i/modules/choose-mirror.xml deleted file mode 100644 index 746804ecd..000000000 --- a/da/using-d-i/modules/choose-mirror.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - \ No newline at end of file diff --git a/da/using-d-i/modules/ddetect.xml b/da/using-d-i/modules/ddetect.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/ddetect.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/finish-install.xml b/da/using-d-i/modules/finish-install.xml deleted file mode 100644 index 309739b75..000000000 --- a/da/using-d-i/modules/finish-install.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - - Finish the Installation and Reboot - - - -This is the last step in the initial Debian installation process. You will -be prompted to remove the boot media (CD, floppy, etc) that you used to -boot the installer. The installer will do any last minute tasks, and then -reboot into your new Debian system. - - - -Select the Finish the installation -menu item which will halt the system -because rebooting is not supported on &arch-title; in this case. You -then need to IPL GNU/Linux from the DASD which you selected for the -root filesystem during the first steps of the installation. - - - diff --git a/da/using-d-i/modules/hppa/palo-installer.xml b/da/using-d-i/modules/hppa/palo-installer.xml deleted file mode 100644 index 84a3608e8..000000000 --- a/da/using-d-i/modules/hppa/palo-installer.xml +++ /dev/null @@ -1,20 +0,0 @@ - - - - - <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/da/using-d-i/modules/ia64/elilo-installer.xml b/da/using-d-i/modules/ia64/elilo-installer.xml deleted file mode 100644 index 9c9050d0b..000000000 --- a/da/using-d-i/modules/ia64/elilo-installer.xml +++ /dev/null @@ -1,135 +0,0 @@ - - - - - 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 filesytem. -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/da/using-d-i/modules/iso-scan.xml b/da/using-d-i/modules/iso-scan.xml deleted file mode 100644 index f86cb4954..000000000 --- a/da/using-d-i/modules/iso-scan.xml +++ /dev/null @@ -1,47 +0,0 @@ - - - - - Looking for the Debian Installer ISO Image - - -When installing via the hd-media method, there -will be a moment where you need to find and mount the Debian Installer -iso image in order to get the rest of the installation files. The -component iso-scan does exactly this. - - - -At first, iso-scan automatically mounts all block -devices (e.g. partitions) which have some known filesystem on them and -sequentially searches for filenames ending with -.iso (or .ISO for that -matter). Beware that the first attempt scans only files in the root -directory and in the first level of subdirectories (i.e. it finds -/whatever.iso, -/data/whatever.iso, -but not -/data/tmp/whatever.iso). -After an iso image has been found, iso-scan checks -its content to determine if the image is valid Debian iso image or -not. In the former case we are done, in the latter -iso-scan seeks for another image. - - - -In case the previous attempt to find an installer iso image fails, -iso-scan will ask you whether you would like to -perform more throughly search. This pass doesn't look only into the -topmost directories, but really traverses whole filesystem. - - - -If iso-scan does not discover your installer iso -image, reboot back to your original operating system and check if the -image has correct name (ending in .iso), if it is -placed on a filesystem recognizable by &d-i;, and if it is not -corrupted (verify the checksum). Experienced unix users could do this -without rebooting on the second console. - - - diff --git a/da/using-d-i/modules/kbd-chooser.xml b/da/using-d-i/modules/kbd-chooser.xml deleted file mode 100644 index b108ca1e4..000000000 --- a/da/using-d-i/modules/kbd-chooser.xml +++ /dev/null @@ -1,44 +0,0 @@ - - - - - Choosing a Keyboard - - - -Keyboards are often tailored to the characters used in a language. -Select a layout that conforms to the keyboard you are using, or -select something close if the keyboard layout you want -isn't represented. Once the system installation is complete, you'll be -able to select a keyboard layout from a wider range of choices (run -kbdconfig as root after you have completed the -installation). - - - -Move the highlight to the keyboard selection you desire and press -&enterkey;. Use the arrow keys to move the highlight — they are -in the same place in all national language keyboard layouts, so they -are independent of the keyboard configuration. An 'extended' keyboard -is one with F1 through F10 keys -along the top row. - - - -On DECstations there is currently no loadable keymap available, -so you have to skip the keyboard selection and keep the default -kernel keymap (LK201 US). This may change in the future as it -depends on further Linux/MIPS kernel development. - - - -There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us -(Apple USB) layout will place the Alt function on the -Command/Apple key (in the keyboard position next to -the space key similar to Alt on -PC keyboards), while the qwerty/us (Standard) layout will place the -Alt function on the Option key (engraved with 'alt' -on most Mac keyboards). In other respects the two layouts are similar. - - - diff --git a/da/using-d-i/modules/lowmem.xml b/da/using-d-i/modules/lowmem.xml deleted file mode 100644 index 15cb78f91..000000000 --- a/da/using-d-i/modules/lowmem.xml +++ /dev/null @@ -1,21 +0,0 @@ - - - - - Check available memory - - - -One of the first things &d-i; does, is to check available memory. -If the available memory is limited, this component will make some -changes in the installation process which hopefully will allow -you to install &debian; on your system. - - - -During a low memory install, not all components will be available. -One of the limitations is that you won't be able to choose a -language for the installation. - - - \ No newline at end of file diff --git a/da/using-d-i/modules/mdcfg.xml b/da/using-d-i/modules/mdcfg.xml deleted file mode 100644 index bff80ee04..000000000 --- a/da/using-d-i/modules/mdcfg.xml +++ /dev/null @@ -1,180 +0,0 @@ - - - - - Configuring Multidisk Device (Software RAID) - - -If you have more than one harddrive - -To be honest, you can construct MD device even from partitions -residing on single physical drive, but that won't bring you anything -useful. - - in your computer, you can use -mdcfg to set up your drives for increased -performance and/or better reliability of your data. The result is -called Multidisk Device (or after its most -famous variant software RAID). - - - -MD is basically a bunch of partitions located on different disks and -combined together to form a logical device. This -device can then be used like an ordinary partition (i.e. in -partman you can format it, assign a mountpoint, -etc.). - - - -The benefit you gain depends on a type of a MD device you are -creating. Currently supported are: - - - - -RAID0 - -Is mainly aimed at performance. RAID0 splits all incomming data into -stripes and distributes them equally over each -disk in the array. This can increase the speed of read/write -operations, but when one of the disks fails, you will loose -everything (part of the information is still on -the healthy disk(s), the other part was on the -failed disk). - - - -The typical use for RAID0 is a partition for video editing. - - - - - -RAID1 - -Is suitable for setups where reliability is the first concern. It -consists of several (usualy two) equaly sized partitions where every -partition contains exactly the same data. This essentialy means three -things. First, if one of your disks fails, you still have the data -mirrored on the remaining disks. Second, you can use only a fraction -of the available capacity (more precisely, it is the size of the -smallest partition in the RAID). Third, file reads are load balanced among -the disks, which can improve performance on a server, such as a file -server, that tends to be loaded with more disk reads than writes. - - - -Optionally you can have a spare disk in the array which will take the -place of the failed disk in the case of failure. - - - - - -To sum it up: - - - - - - Type - Minimum Devices - Spare Device - Survives disk failure? - Available Space - - - - - - RAID0 - 2 - no - no - Size of the smallest partition multiplied by number of devices in RAID - - - - RAID1 - 2 - optional - yes - Size of the smallest partition in RAID - - - - - - -If you want to know the whole truth about Software RAID, have a look -at Software RAID HOWTO. - - - -To create an MD device, you need to have the desired partitions it -should consist of marked for use in a RAID. (This is done in -partman in the Partition -settings menu where you should select -Use as: Use the partition as a RAID -device .) - - - -Support for MD is a relatively new addition to the installer. -You may experience problems for some RAID levels and in combination -with some bootloaders if you try to use MD for the root -(/) filesystem. For experienced users, it may be -possible to work around some of these problems by executing some -configuration or installation steps manually from a shell. - - - -Next, you should choose Configure software -RAID from the main partman menu. -On the first screen of mdcfg simply select -Create MD device. You will be presented with -a list of supported types of MD devices, from which you should choose -one (e.g. RAID1). What follows depends on the type of MD you selected. - - - - - -RAID0 is simple — you will be issued with the list of available -RAID partitions and your only task is to select the partitions which -will form the MD. - - - - -RAID1 is a bit more tricky. First, you will be asked to enter the -number of active devices and the number of spare devices which will -form the MD. Next, you need to select from the list of available RAID -partitions those that will be active and then those that will be -spare. The count of selected partitions must be equal to the number -provided few seconds ago. Don't worry. If you make a mistake and -select a different number of partitions, the &d-i; won't let you -continue until you correct the issue. - - - - - - -It is perfectly possible to have several types of MD at once. For -example if you have three 200 GB hard drives dedicated to MD, each -containing two 100 GB partitions, you can combine first partitions on -all three disk into the RAID0 (fast 300 GB video editing partition) -and use the other three partitions (2 active and 1 spare) for RAID1 -(quite reliable 100 GB partition for /home). - - - -After you set up MD devices to your liking, you can -Finish mdcfg to return -back to the partman to create filesystems on your -new MD devices and assign them the usual attributes like mountpoints. - - - diff --git a/da/using-d-i/modules/mips/arcboot-installer.xml b/da/using-d-i/modules/mips/arcboot-installer.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/mips/arcboot-installer.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/mipsel/colo-installer.xml b/da/using-d-i/modules/mipsel/colo-installer.xml deleted file mode 100644 index d4c2f588b..000000000 --- a/da/using-d-i/modules/mipsel/colo-installer.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/mipsel/delo-installer.xml b/da/using-d-i/modules/mipsel/delo-installer.xml deleted file mode 100644 index d355f86b9..000000000 --- a/da/using-d-i/modules/mipsel/delo-installer.xml +++ /dev/null @@ -1,80 +0,0 @@ - - - - - <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/da/using-d-i/modules/netcfg.xml b/da/using-d-i/modules/netcfg.xml deleted file mode 100644 index 3880b0bf8..000000000 --- a/da/using-d-i/modules/netcfg.xml +++ /dev/null @@ -1,58 +0,0 @@ - - - - - Configuring Network - - - -As you enter this step, if the system detects that you have more than -one network device, you'll be asked to choose which device will be -your primary network interface, i.e. the one -which you want to use for installation. The other interfaces won't be -configured at this time. You may configure additional interfaces after -installation is complete; see the -interfaces 5 - man page. - - - -By default, &d-i; tries to configure your computer's network -automatically via DHCP. If DHCP probe succeeds, you are done. If the -probe fails, it may be caused by many factors ranging from unplugged -network cable, to a misconfigured DHCP setup. Or maybe you don't have -DHCP server in your local network at all. For further explanation -check the error messages on the third console. In any case, you will -be asked, if you want to retry, or if you want to perform manual -setup. DHCP servers are sometimes really slow in their responses, so -if you are sure everything is in place, try again. - - - -The manual network setup in turn asks you number of questions about -your network, notably -IP address, -Netmask, -Gateway, -Name server addresses, and a -Hostname. -Moreover, if you have a wireless network interface, you will be asked -to provide your Wireless ESSID and -a WEP key. Fill in the answers from -. - - - -Some technical details you might, or might not, find handy: the -program assumes the network IP address is the bitwise-AND of your -system's IP address and your netmask. It will guess the broadcast -address is the bitwise OR of your system's IP address with the bitwise -negation of the netmask. It will also guess your gateway. If you -can't find any of these answers, use the system's guesses — you -can change them once the system has been installed, if necessary, by -editing /etc/network/interfaces. Alternatively, -you can install etherconf, which will step you -through your network setup. - - - diff --git a/da/using-d-i/modules/nobootloader.xml b/da/using-d-i/modules/nobootloader.xml deleted file mode 100644 index f19398003..000000000 --- a/da/using-d-i/modules/nobootloader.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - Continue Without Boot Loader - - - -This option can be used to complete the installation even when no boot -loader is to be installed, either because the arch/subarch doesn't -provide one, or because none is desired (e.g. you will use existing -boot loader). This option is especially useful for -Macintosh, Atari, and Amiga systems, where the original operating system -must be maintained on the box and used to boot GNU/Linux. - - - diff --git a/da/using-d-i/modules/os-prober.xml b/da/using-d-i/modules/os-prober.xml deleted file mode 100644 index 840cd3d3b..000000000 --- a/da/using-d-i/modules/os-prober.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - - Detecting other operating systems - - - -Before a boot loader is installed, the installer will attempt to probe for -other operating systems which are installed on the machine. If it finds a -supported operating system, you will be informed of this during the boot -loader installation step, and the computer will be configured to boot this -other operating system in addition to Debian. - - - -Note that multiple operating systems booting on a single machine is still -something of a black art. The automatic support for detecting and setting -up boot loaders to boot other operating systems varies by architecture and -even by subarchitecture. If it does not work you should consult your -boot manager's documentation for more information. - - - - - - - -The installer may fail to detect other operating systems if the partitions on -which they reside are mounted when the detection takes place. This may occur if -you select a mountpoint (e.g. /win) for a partition containing another operating -system in partman, or if you have mounted partitions manually -from a console. - - - - diff --git a/da/using-d-i/modules/partconf.xml b/da/using-d-i/modules/partconf.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/partconf.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/partitioner.xml b/da/using-d-i/modules/partitioner.xml deleted file mode 100644 index 0dabd4a41..000000000 --- a/da/using-d-i/modules/partitioner.xml +++ /dev/null @@ -1,3 +0,0 @@ - - - diff --git a/da/using-d-i/modules/partman-lvm.xml b/da/using-d-i/modules/partman-lvm.xml deleted file mode 100644 index de753b72d..000000000 --- a/da/using-d-i/modules/partman-lvm.xml +++ /dev/null @@ -1,58 +0,0 @@ - - - - - Configuring Logical Volume Manager (LVM) - - -If you are working with computers at the level of system administrator -or advanced user, you have surely seen the situation -where some disk partition (usualy the most important one) was short on -space, while some other partition was grossly underused and you had to -manage this situation by moving stuff around, symlinking, etc. - - - -To avoid the described situation you can use Logical Volume Manager -(LVM). Simply said, with LVM you can combine your partitions -(physical volumes in LVM lingo) to form -a virtual disc (so called volume group), which -can then be divided into virtual partitions (logical -volumes). The point is that logical volumes (and of course -underlying volume groups) can span across several physical discs. - - - -Now when you realize you need more space for your old 160GB -/home partition, you can simply add a new 300GB -disc to the computer, join it with your existing volume group and then -resize the logical volume which holds your /home -filesystem and voila - your users have some room again on their -renewed 460GB partition. This example is of course a bit -oversimplified. If you haven't read it yet, you should consult the -LVM HOWTO. - - - -LVM setup in &d-i; is quite simple. At first, you have to mark your -partitions to be used as physical volumes for LVM. (This is done in -partman in the Partition -settings menu where you should select -Use as: physical volume for -LVM .) Then start the -lvmcfg module (either directly from -partman or from the &d-i;'s main menu) and combine -physical volumes to volume group(s) under the Modify -volume groups (VG) menu. After that, you should create -logical volumes on the top of volume groups from the menu -Modify logical volumes (LV). - - - -After returning from lvmcfg back to -partman, you will see any created logical volumes -in the same way as ordinary partitions (and you should treat them like -that). - - - diff --git a/da/using-d-i/modules/partman.xml b/da/using-d-i/modules/partman.xml deleted file mode 100644 index e7e472eb8..000000000 --- a/da/using-d-i/modules/partman.xml +++ /dev/null @@ -1,193 +0,0 @@ - - - - - Partitioning Your Disks - - - -Now it is time to partition your disks. If you are uncomfortable with -partitioning, or just want to know more details, see . - - - -First you will be given the opportunity to automatically partition -either an entire drive, or free space on a drive. This is also called -guided partitioning. If you do not want to -autopartition, choose Manually edit partition -table from the menu. - - - -If you choose guided partitioning, you will be able to choose from the -schemes listed in the table below. All schemes have their pros and cons, -some of which are discussed in . If you are -unsure, choose the first one. Bear in mind, that guided partitioning -needs certain minimal amount of free space to operate with. If you don't -give it at least about 1GB of space (depends on chosen scheme), guided -partitioning will fail. - - - - - - - - Partitioning scheme - Minimum space - Created partitions - - - - - - All files in one partition - 600MB - /, swap - - Desktop machine - 500MB - - /, /home, swap - - - Multi-user workstation - 1GB - - /, /home, - /usr, /var, - /tmp, swap - - - - - - - -If you chose an automatic partitioning for your IA64 system, there -will be an additional partition, formatted as a FAT16 bootable filesystem, -for the EFI boot loader. -There is also an additional menu item in the formatting menu to manually -set up a partition as an EFI boot partition. - - - -After selecting a scheme, the next screen will show your new partition -table, including information on whether and how partitions will be -formatted and where they will be mounted. - - - -The list of partitions might look like this: - - - - IDE1 master (hda) - 6.4 GB WDC AC36400L - #1 primary 16.4 MB ext2 /boot - #2 primary 551.0 MB swap swap - #3 primary 5.8 GB ntfs - pri/log 8.2 MB FREE SPACE - - IDE1 slave (hdb) - 80.0 GB ST380021A - #1 primary 15.9 MB ext3 - #2 primary 996.0 MB fat16 - #3 primary 3.9 GB xfs /home - #5 logical 6.0 GB ext3 / - #6 logical 1.0 GB ext3 /var - #7 logical 498.8 GB ext3 - #8 logical 551.5 GB swap swap - #9 logical 65.8 GB ext2 - - -This example shows two IDE harddrives divided into several partitions; -the first disk has some free space. Each partition line consists of the -partition number, its type, size, optional flags, file system, and -mountpoint (if any). - - - -This concludes the guided partitioning. If you are satisfied with the -generated partition table, you can choose Finish -partitioning and write changes to disk from the menu to -implement the new partition table (as described at the end of this -section). If you are not happy, you can choose to Undo -changes to partitions, to run guided partitioning again -or modify the proposed changes as described below for manual partitioning. - - - -A similar screen to the one shown just above will be displayed if you -choose manual partioning except that your existing partition table will -be shown and without the mount points. How to manually set up your partition -table and the usage of partitions by your new Debian system will be covered -in the remainder of this section. - - - -If you select a pristine disk which doesn't have neither partitions -nor free space on it, you will be offered to create a new partition -table (this is needed so you can create new partitions). After this -a new line entitled FREE SPACE should appear under the -selected disk. - - - -If you select some free space, you will be offered to create new -partition. You will have to answer a quick series of questions about -its size, type (primary or logical), and location (begining or end of -the free space). After this, you will be presented with detailed -overview of your new partition. There are options like mountpoint, -mount options, bootable flag, or way of usage. If you don't like the -preselected defaults, feel free to change them to your liking. E.g. by -selecting the option Use as:, you can -choose different filesystem for this partition including the -possibility to use the partition for swap, software RAID, LVM, or not -use it at all. Other nice feature is the possibility to copy data from -existing partition onto this one. -When you are satisfied with your new partition, select -Finished with partition and you will be -thrown back to the partman's main screen. - - - -If you decide you want to change something about your partition, -simply select the partition, which will bring you to the partition -configuration menu. Because this is the same screen like when creating -a new partition, you can change the same set of options. One thing -which might not be very obvious at a first glance is that you can -resize the partition by selecting the item displaying the size of the -partition. Filesystems known to work are at least fat16, fat32, ext2, -ext3 and swap. This menu also allows you to delete a partition. - - - -Be sure to create at least two partitions: one for the -root filesystem (which must be mounted as -/) and one for swap. If you -forget to mount the root filesystem, partman won't -let you continue until you correct this issue. - - - -If you forget to select and format an EFI boot partition -partman will detect this and will not let you continue -until you allocate one. - - - -Capabilities of partman can be extended with installer -modules, but are dependent on your system's architecture. So if you can't -see all promised goodies, check if you have loaded all required modules -(e.g. partman-ext3, partman-xfs, -or partman-lvm). - - - -After you are satisfied with partitioning, select Finish -partitioning and write changes to disk from the partitioning -menu. You will be presented with a summary of changes made to the disks -and asked to confirm that the filesystems should be created as requested. - - - diff --git a/da/using-d-i/modules/powerpc/quik-installer.xml b/da/using-d-i/modules/powerpc/quik-installer.xml deleted file mode 100644 index ed6aa6a60..000000000 --- a/da/using-d-i/modules/powerpc/quik-installer.xml +++ /dev/null @@ -1,15 +0,0 @@ - - - - - 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/da/using-d-i/modules/powerpc/yaboot-installer.xml b/da/using-d-i/modules/powerpc/yaboot-installer.xml deleted file mode 100644 index 4bba348fb..000000000 --- a/da/using-d-i/modules/powerpc/yaboot-installer.xml +++ /dev/null @@ -1,17 +0,0 @@ - - - - - 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/da/using-d-i/modules/s390/dasd.xml b/da/using-d-i/modules/s390/dasd.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/s390/dasd.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/s390/netdevice.xml b/da/using-d-i/modules/s390/netdevice.xml deleted file mode 100644 index 5c156a8fa..000000000 --- a/da/using-d-i/modules/s390/netdevice.xml +++ /dev/null @@ -1,2 +0,0 @@ - - diff --git a/da/using-d-i/modules/s390/zipl-installer.xml b/da/using-d-i/modules/s390/zipl-installer.xml deleted file mode 100644 index 61aa6465c..000000000 --- a/da/using-d-i/modules/s390/zipl-installer.xml +++ /dev/null @@ -1,16 +0,0 @@ - - - - - <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/da/using-d-i/modules/save-logs.xml b/da/using-d-i/modules/save-logs.xml deleted file mode 100644 index d905024ba..000000000 --- a/da/using-d-i/modules/save-logs.xml +++ /dev/null @@ -1,23 +0,0 @@ - - - - - Saving the installation logs - - - -If the installation is successful, the logfiles created during -the installation process will be automatically saved to -/var/log/debian-installer/ on your new -Debian system. - - - -Choosing Save debug logs from the main -menu allows you to save the log files to a floppy disk. This can -be useful if you encounter fatal problems during the installation -and wish to study the logs on another system or attach them to an -installation report. - - - diff --git a/da/using-d-i/modules/shell.xml b/da/using-d-i/modules/shell.xml deleted file mode 100644 index 0e26048a0..000000000 --- a/da/using-d-i/modules/shell.xml +++ /dev/null @@ -1,41 +0,0 @@ - - - - - Using the Shell and Viewing the Logs - - - - -There is an Execute a Shell item on the -menu. If the menu is not available when you need to use the shell, -press Left Alt F2 -(on a Mac keyboard, Option F2 -) to switch to the second virtual -console. That's the Alt key on the -left-hand side of the space bar, and the -F2 function key, at the same time. This is a separate -window running a Bourne shell clone called ash. - - - -At this point you are booted from the RAM disk, and there is a limited -set of Unix utilities available for your use. You can see what -programs are available with the command ls /bin /sbin /usr/bin -/usr/sbin and by typing help. The -text editor is nano. The shell has some nice features -like autocompletion and history. - - - -Use the menus to perform any task that they are able to do — the -shell and commands are only there in case something goes wrong. In -particular, you should always use the menus, not the shell, to -activate your swap partition, because the menu software can't detect -that you've done this from the shell. Press Left -Alt F1 to get back to menus, or -type exit if you used a menu item to open the -shell. - - - diff --git a/da/using-d-i/modules/sparc/silo-installer.xml b/da/using-d-i/modules/sparc/silo-installer.xml deleted file mode 100644 index f459a8cb1..000000000 --- a/da/using-d-i/modules/sparc/silo-installer.xml +++ /dev/null @@ -1,25 +0,0 @@ - - - - - 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 -along side an existing SunOS/Solaris install. - - - diff --git a/da/using-d-i/modules/x86/grub-installer.xml b/da/using-d-i/modules/x86/grub-installer.xml deleted file mode 100644 index 5a0159b01..000000000 --- a/da/using-d-i/modules/x86/grub-installer.xml +++ /dev/null @@ -1,26 +0,0 @@ - - - - - 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/da/using-d-i/modules/x86/lilo-installer.xml b/da/using-d-i/modules/x86/lilo-installer.xml deleted file mode 100644 index 0f38f727d..000000000 --- a/da/using-d-i/modules/x86/lilo-installer.xml +++ /dev/null @@ -1,70 +0,0 @@ - - - - - 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 linux and the 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 begining -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/da/using-d-i/using-d-i.xml b/da/using-d-i/using-d-i.xml deleted file mode 100644 index b4d13514c..000000000 --- a/da/using-d-i/using-d-i.xml +++ /dev/null @@ -1,365 +0,0 @@ - - - - - Using the Debian Installer - - How the Installer Works - - -The Debian Installer consists of a number of special-purpose -components to perform each installation task. Each component performs -its task, asking the user questions as necessary to do its job. -The questions themselves are given priorities, and the priority -of questions to be asked is set when the installer is started. - - - -When a default installation is performed, only essential (high priority) -questions will be asked. This results in a highly automated installation -process with little user interaction. Components are automatically run -in sequence; which components are run depends mainly on the installation -method you use and on your hardware. The installer will use default values -for questions that are not asked. - - - -If there is a problem, the user will see an error screen, and the -installer menu may be shown in order to select some alternative -action. If there are no problems, the user will never see the -installer menu, but will simply answer questions for each component -in turn. Serious error notifications are set to priority 'critical' -so the user will always be notified. - - - -Some of the defaults that the installer uses can be influenced by passing -boot arguments when &d-i; is started. If, for example, you wish to -force static network configuration (DHCP is used by default if available), -you could add the boot parameter netcfg/disable_dhcp=true. -See for available options. - - - -Power users may be more comfortable with a menu-driven interface, -where each step is controlled by the user rather than the installer -performing each step automatically in sequence. To use the installer -in a manual, menu-driven way, add the boot argument -debconf/priority=medium. - - - -If your hardware requires you to pass options to kernel modules as -they are installed, you will need to start the installer in -expert mode. This can be done by either using the -expert command to start the installer or by adding -the boot argument debconf/priority=low. -Expert mode gives you full control over &d-i;. - - - -The normal installer display is character-based (as opposed to the now -more familiar graphical interface). The mouse is not operational in -this environment. Here are the keys you can use to navigate within the -various dialogs. The Tab or right -arrow keys move `forward', and the Shift -Tab or left arrow keys -move `backward' between displayed buttons and selections. -The up and down arrow select -different items within a scrollable list, and also scroll the list -itself. In addition, in long lists, you can type a letter to cause the -list to scroll directly to the section with items starting with the -letter you typed and use Pg-Up and -Pg-Down to scroll the list in sections. The -space bar selects an item such as a checkbox. Use -&enterkey; to activate choices. - - - -S/390 does not support virtual consoles. You may open a second and third -ssh session to view the logs described below. - - - -Error messages are redirected to the third console. -You can access this console by -pressing Left AltF3 -(hold the left Alt key while pressing the -F3 function key); get back to -the main installer process with -Left AltF1. - - - -These messages can also be found in -/var/log/messages. After installation, this log -is copied to /var/log/debian-installer/messages on your -new system. Other 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. - - - - - - Components Introduction - - -Here is a list of installer components with a brief description -of each component's purpose. Details you might need to know about -using a particular component are in . - - - - - - -main-menu - -Shows the list of components to the user during installer operation, -and starts a component when it is selected. Main-menu's -questions are set to priority medium, so if your priority is set to -high or critical (high is the default), you will not see the menu. On -the other hand, if there is an error which requires your intervention, -the question priority may be downgraded temporarily to allow you -to resolve the problem, and in that case the menu may appear. - - - -You can get to the main menu by selecting the "Back" button -repeatedly to back all the way out of the currently running component. - - - - - -languagechooser - -Shows a list of languages and language variants. The installer will -display messages in the chosen language, unless the translation for -that language is not complete. When a translation is not complete, -English messages are shown. - - - - - -countrychooser - -Shows a list of countries. The user may choose the country he lives -in. - - - - - -kbd-chooser - -Shows a list of keyboards, from which the user chooses the model which -matches his own. - - - - - -hw-detect - -Automatically detects most of the system's hardware, including network -cards, disk drives, and PCMCIA. - - - - - -cdrom-detect - -Looks for and mounts a Debian installation CD. - - - - - -netcfg - -Configures the computer's network connections so it can communicate -over the internet. - - - - - -iso-scan - -Looks for ISO file systems, which may be on a CD-ROM or on the -hard drive. - - - - - -choose-mirror - -Presents a list of Debian archive mirrors. The user may choose -the source of his installation packages. - - - - - -cdrom-checker - -Checks integrity of a CD-ROM. This way the user may assure him/herself -that the installation CD-ROM was not corrupted. - - - - - -lowmem - -Lowmem tries to detect systems with low memory and then does various -tricks to remove unnecessary parts of &d-i; from the memory (at the -cost of some features). - - - - - -anna - -Anna's Not Nearly APT. Installs packages which have been retrieved -from the chosen mirror or CD. - - - - - -partman - -Allows the user to partition disks attached to the system, create file -systems on the selected partitions, and attach them to the -mountpoints. Included are also interesting features like a fully -automatic mode or LVM support. This is the preferred partitioning tool -in Debian. - - - - - -autopartkit - -Automatically partitions an entire disk according to preset -user preferences. - - - - - -partitioner - -Allows the user to partition disks attached to the system. A -partitioning program appropriate to your computer's architecture -is chosen. - - - - - -partconf - -Displays a list of partitions, and creates file systems on -the selected partitions according to user instructions. - - - - - -lvmcfg - -Helps the user with the configuration of the -LVM (Logical Volume Manager). - - - - - -mdcfg - -Allows the user to set up Software RAID -(Redundant Array of Inexpensive Disks). This Software RAID is usually -superior to the cheap IDE (pseudo hardware) RAID controllers found on -newer motherboards. - - - - - -base-installer - -Installs the most basic set of packages which would allow -the computer to operate under Linux when rebooted. - - - - - -os-prober - -Detects currently installed operating systems on the computer and -passes this information to the bootloader-installer, which may offer -you an ability to add discovered operating systems to the bootloader's -start menu. This way the user could easily choose at the boot time -which operating system to start. - - - - - -bootloader-installer - -Installs a boot loader program on the hard disk, which is necessary -for the computer to start up using Linux without using a floppy or -CD-ROM. Many boot loaders allow the user to choose an alternate -operating system each time the computer boots. - - - - - -base-config - -Provides dialogs for setting up the base system packages according -to user preferences. This is normally done after rebooting the -computer; it is the 'first run' of the new Debian system. - - - - - -shell - -Allows the user to execute a shell from the menu, or in the second -console. - - - - - -bugreporter - -Provides a way for the user to record information on a floppy disk -when trouble is encountered, in order to accurately report installer -software problems to Debian developers later. - - - - - - - - -&using-d-i-components.xml; - - - diff --git a/da/welcome/what-is-debian.xml b/da/welcome/what-is-debian.xml deleted file mode 100644 index 34195fcfe..000000000 --- a/da/welcome/what-is-debian.xml +++ /dev/null @@ -1,113 +0,0 @@ - - - - - Hvad er Debian? - - -Debian er en frivillig organisation med det form� at udvikle frie -programmer og fremme Free Software Foundations' idealer. -Debianprojektet startede i 1993, hvor Ian Murdick udsendte en -�en åben invitation for programudviklere til at bidrage til en -komplet og sammenhængende distribution baseret på den -relativt nye Linuxkerne. Denne relativt lille gruppe af dedikerede -enthusiaster startede oprindeligt gruppen -Free Software Foundation -og er påvirket af -GNU-filosofien vokset -gennem årene til en organisation på omkring -&num-of-debian-developers; Debianudviklere. - - - -Debianudviklere er involverede i mange forskellige aktiviteter, herunder -Web - -og FTP-administration, -grafisk design, ophavsretslig juridisk vurdering af program-licenser, -udarbejdelse af dokumentation og --- naturligvis --- vedligeholdelsen -af programpakker. - - - -For at beskrive vores filosofi og tiltrække udviklere, der tror på -de principper, Debian står for, har Debianprojektet udgivet -nogle dokumenter, der tydeliggør vore værdier og fungerer som -retningslinjer for, hvad det vil sige at være Debianudvikler: - - - - -The -Debians Sociale Kontrakt er -en -a statement of Debian's commitments to the Free Software Community. -Anyone who agrees to abide to the Social Contract may become a -maintainer. -Any maintainer can introduce new software into Debian — provided -that the software meets our criteria for being free, and the package -follows our quality standards. - - - - -The -Debian Free Software Guidelines are a -clear and concise statement of Debian's criteria for free software. -The DFSG is a very influential document in the Free Software Movement, -and was the foundation of the -The Open Source Definition. - - - - -The -Debian Policy Manual is an -extensive specification of the Debian Project's standards of quality. - - - - - -Debian developers are also involved in a number of other projects; -some specific to Debian, others involving some or all of the Linux -community. Some examples include: - - - - -The -Linux Standard Base -(LSB) is a project aimed at standardizing the basic GNU/Linux system, -which will enable third-party software and hardware developers to -easily design programs and device drivers for Linux-in-general, rather -than for a specific GNU/Linux distribution. - - - - -The -Filesystem Hierarchy Standard -(FHS) is an effort to standardize the layout of the Linux -file system. The FHS will allow software developers to concentrate -their efforts on designing programs, without having to worry about how -the package will be installed in different GNU/Linux distributions. - - - - -Debian Jr. -er et internt projekt med det formål at sikre at Debian har noget at -tilbyde vore yngste brugere. - - - - - - -For mere generel information om Debian, henviser vi til -Debians FAQ. - - - - - -- cgit v1.2.3