diff options
29 files changed, 741 insertions, 269 deletions
diff --git a/fi/appendix/preseed.xml b/fi/appendix/preseed.xml index 4b3bc8def..520dfe9bf 100644 --- a/fi/appendix/preseed.xml +++ b/fi/appendix/preseed.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 34168 untranslated --> +<!-- original version: 35051 untranslated --> <!-- Be carefull with the format of this file as it is parsed to generate @@ -137,7 +137,7 @@ questions being asked. Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing -partitions. You currently cannot use preseeding to set up RAID and LVM. +partitions. You currently cannot use preseeding to set up RAID. </para> </sect2> @@ -278,11 +278,11 @@ load it. </para><para> -For the other preseeding methods you need to tell the installer what file to -use when you boot it. This is done by passing the kernel a boot parameter, -either manually at boot time or by editing the bootloader configuration file -(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end -of the append line(s) for the kernel. +For the other preseeding methods you need to tell the installer what file +to use when you boot it. This is normally done by passing the kernel a boot +parameter, either manually at boot time or by editing the bootloader +configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the +parameter to the end of the append line(s) for the kernel. </para><para> @@ -323,6 +323,43 @@ questions even if the preseeding below misses some. </para> </sect2> + + <sect2 id="preseed-dhcp"> + <title>Using a DHCP server to specify preseed files</title> +<para> + +It's also possible to use DHCP to specify a preseed file to download from +the network. DHCP allows specifying a filename. Normally this is a file to +netboot, but if it appears to be an URL then installation media that +support network preseeding will download the file from the URL and use it +as a preseed file. Here is an example of how to set it up in the dhcpd.conf +for version 3 of the ISC DHCP server (the dhcp3-server Debian package). + +</para> + +<informalexample><screen> +if substring (option vendor-class-identifier, 0, 3) = "d-i" { + filename "http://host/preseed.cfg"; +} +</screen></informalexample> + +<para> + +Note that the above example limits this filename to DHCP clients that identify +themselves as "d-i", so it will not affect regular DHCP clients, but only +the installer. You can also put the text in a stanza for only one particular +host to avoid preseeding all installs on your network. + +</para><para> + +A good way to use the DHCP preseeding is to only preseed values specific to +your network, such as the Debian mirror to use. This way installs on your +network will automatically get a good mirror selected, but the rest of the +installation can be performed interactively. Using DHCP preseeding to fully +automate Debian installs should only be done with care. + +</para> + </sect2> <sect2 id="preseed-bootparms"> <title>Using boot parameters to supplement preseeding</title> @@ -589,8 +626,7 @@ supported by <classname>partman-auto</classname>. You can choose to either partition existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preseed file. It is currently not -possible to partition multiple disks using preseeding nor to set up RAID or -LVM. +possible to partition multiple disks using preseeding nor to set up RAID. </para> @@ -604,6 +640,7 @@ correct one will be selected before using preseeding. <informalexample role="example"><screen> # If the system has free space you can choose to only partition that space. +# Note: the preseed value for this template needs to be localized (translated). #d-i partman-auto/init_automatically_partition \ # select Use the largest continuous free space @@ -612,7 +649,8 @@ correct one will be selected before using preseeding. # 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: +# You can choose from any of the predefined partitioning recipes. +# Note: the preseed value for this template needs to be localized (translated). d-i partman-auto/choose_recipe \ select All files in one partition (recommended for new users) #d-i partman-auto/choose_recipe \ diff --git a/fi/boot-installer/arm.xml b/fi/boot-installer/arm.xml index 505a05323..8b273d74e 100644 --- a/fi/boot-installer/arm.xml +++ b/fi/boot-installer/arm.xml @@ -1,94 +1,101 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35328 untranslated --> <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title> &boot-installer-intro-net.xml; - <sect3 arch="arm"><title>Booting from TFTP on NetWinder</title> - + <sect3 arch="arm"><title>Booting from TFTP on Netwinder</title> <para> -NetWinders have two network interfaces: The 10Mbps NE2000-compatible -card is <filename>eth0</filename> and the 100Mbps Tulip card is -<filename>eth1</filename>. - -</para><note><para> - -You need NeTTrom 2.2.1 or later to boot the -installation system. NeTTrom 2.3.3 is recommended: get these files -from -<ulink url="ftp://ftp.netwinder.org/pub/netwinder/firmware/"></ulink>: -<itemizedlist> -<listitem><para> - -<filename>nettrom-2.3-3.armv4l.rpm</filename> - -</para></listitem> -<listitem><para> +Netwinders have two network interfaces: A 10Mbps NE2000-compatible +card (which is generally referred to as <literal>eth0</literal>) and +a 100Mbps Tulip card. There may be problems loading the image via TFTP +using the 100Mbps card so it is recommended that you use the 10Mbps +interfaced (the one labeled with <literal>10 Base-T</literal>). -<filename>nettrom-2.3.3.bin</filename> +</para> +<note><para> -</para></listitem> -<listitem><para> +You need NeTTrom 2.2.1 or later to boot the installation system, and +version 2.3.3 is recommended. Unfortunately, firmware files are currently +not available for download because of license issues. If this situation +changes, you may find new images at <ulink url="http//www.netwinder.org/"></ulink>. -<filename>nettrom-2.3.3.bin.md5sum</filename> +</para></note> +<para> -</para></listitem> -</itemizedlist> +When you boot your Netwinder you have to interrupt the boot process during the +countdown. This allows you to set a number of firmware settings needed in +order to boot the installer. First of all, start by loading the default +settings: -</para></note><para> +<informalexample><screen> + NeTTrom command-> load-defaults +</screen></informalexample> -After rebooting and interrupting the boot process during the countdown, you -must first configure the network either with a static address: +Furthermore, you must configure the network, either with a static address: <informalexample><screen> + NeTTrom command-> setenv netconfig_eth0 flash NeTTrom command-> setenv eth0_ip 192.168.0.10/24 </screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen> - NeTTrom command-> boot diskless + NeTTrom command-> setenv netconfig_eth0 dhcp </screen></informalexample> You may also need to configure the <userinput>route1</userinput> -settings if the TFTP -server is not on the local subnet. The rest of the config is pretty -standard (the save-all step is optional): +settings if the TFTP server is not on the local subnet. + +Following these settings, you have to specify the TFTP server and the +location of the image. You can then store your settings to flash. <informalexample><screen> NeTTrom command-> setenv kerntftpserver 192.168.0.1 NeTTrom command-> setenv kerntftpfile boot.img NeTTrom command-> save-all - NeTTrom command-> setenv netconfig_eth0 flash +</screen></informalexample> + +Now you have to tell the firmware that the TFTP image should be booted: + +<informalexample><screen> NeTTrom command-> setenv kernconfig tftp NeTTrom command-> setenv rootdev /dev/ram - NeTTrom command-> setenv cmdappend root=/dev/ram </screen></informalexample> -Only the last four of these interfere with normal disk booting, so it is -safe to issue <command>save-all</command> right before them, which will -store the network settings in case you need to boot from the network -again. - -If you want to use the serial console to install your NetWinder, you also -need the following setting: +If you use a serial console to install your Netwinder, you need to add the +following setting: <informalexample><screen> NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 </screen></informalexample> -Use the <command>printenv</command> command to review your -environment settings. Finally, if your <envar>cmdappend</envar> -NeTTrom variable has the <option>noinitrd</option> option, you must -remove it so the downloaded kernel can boot with its attached ramdisk. +Alternatively, for installations using a keyboard and monitor you have to +set: -</para> - </sect3> +<informalexample><screen> + NeTTrom command-> setenv cmdappend root=/dev/ram +</screen></informalexample> + +You can use the <command>printenv</command> command to review your +environment settings. After you have verified that the settings are +correct, you can load the image: + +<informalexample><screen> + NeTTrom command-> boot +</screen></informalexample> + +In case you run into any problems, a <ulink +url="http://www.netwinder.org/howto/Firmware-HOWTO.html">detailed +HOWTO</ulink> is available. - <sect3 arch="arm"><title>Booting from TFTP on CATS</title> +</para> + </sect3> + <sect3 arch="arm"><title>Booting from TFTP on CATS</title> <para> On CATS machines, use <command>boot de0:</command> or similar at the @@ -99,7 +106,6 @@ Cyclone prompt. </sect2> - <sect2 arch="arm"><title>Booting from CD-ROM</title> &boot-installer-intro-cd.xml; @@ -111,3 +117,103 @@ To boot a CD-ROM from the Cyclone console prompt, use the command </para> </sect2> + + + <sect2 arch="arm" id="boot-firmware"><title>Booting from Firmware</title> + +&boot-installer-intro-firmware.xml; + + <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title> +<para> + +There are three ways how to put the installer firmware into flash: + +</para> + + <sect4 arch="arm"><title>Using the NSLU2 web interface</title> +<para> + +Go to the administration section and choose the menu item +<literal>Upgrade</literal>. You can then browse your disk for the +installer image you have previously downloaded. Then press the +<literal>Start Upgrade</literal> button, confirm, wait for a few minutes +and confirm again. The system will then boot straight into the installer. + +</para> + </sect4> + + <sect4 arch="arm"><title>Via the network using Linux/Unix</title> +<para> + +You can use <command>upslug2</command> from any Linux or Unix machine to +upgrade the machine via the network. This software is packaged for +Debian. + +First, you have to put your NSLU2 in upgrade mode: + +<orderedlist> +<listitem><para> + +Disconnect any disks and/or devices from the USB ports. + +</para></listitem> +<listitem><para> + +Power off the NSLU2 + +</para></listitem> +<listitem><para> + +Press and hold the reset button (accessible through the small hole on the +back just above the power input). + +</para></listitem> +<listitem><para> + +Press and release the power button to power on the NSLU2. + +</para></listitem> +<listitem><para> + +Wait for 10 seconds watching the ready/status LED. After 10 seconds it +will change from amber to red. Immediately release the reset button. + +</para></listitem> +<listitem><para> + +The NSLU2 ready/status LED will flash alternately red/green (there is a 1 +second delay before the first green). The NSLU2 is now in upgrade mode. + +</para></listitem> +</orderedlist> + +See the <ulink +url="http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary">NSLU2-Linux +pages</ulink> if you have problems with this. + +Once your NSLU2 is in upgrade mode, you can flash the new image: + +<informalexample><screen> +sudo upslug2 -i di-nslu2.bin +</screen></informalexample> + +Note that the tool also shows the MAC address of your NSLU2, which may come +in handy to configure your DHCP server. After the whole image has been +written and verified, the system will automatically reboot. Make sure you +connect your USB disk again now, otherwise the installer won't be able to +find it. + +</para> + </sect4> + + <sect4 arch="arm"><title>Via the network using Windows</title> +<para> + +There is <ulink +url="http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip">a +tool</ulink> for Windows to upgrade the firmware via the network. + +</para> + </sect4> + </sect3> + </sect2> diff --git a/fi/boot-installer/boot-installer.xml b/fi/boot-installer/boot-installer.xml index ab8ab9784..0a5a08799 100644 --- a/fi/boot-installer/boot-installer.xml +++ b/fi/boot-installer/boot-installer.xml @@ -1,11 +1,11 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> +<!-- original version: 35310 untranslated --> <chapter id="boot-installer"><title>Booting the Installation System</title> <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> @@ -19,7 +19,7 @@ &boot-installer-ia64.xml; &boot-installer-m68k.xml; &boot-installer-mips.xml; -<!-- &boot-installer-mipsel.xml; --> +&boot-installer-mipsel.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; &boot-installer-sparc.xml; diff --git a/fi/boot-installer/intro-firmware.xml b/fi/boot-installer/intro-firmware.xml new file mode 100644 index 000000000..fe869608e --- /dev/null +++ b/fi/boot-installer/intro-firmware.xml @@ -0,0 +1,18 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 35309 untranslated --> + +<para> + +There is an increasing number of consumer devices that directly boot from a +flash chip on the device. The installer can be written to flash so it will +automatically start when you reboot your machines. + +</para><note><para> + +In many cases, changing the firmware of an embedded device voids your +warranty. Sometimes you are also not able to recover your device if there +are problems during the flashing process. Therefore, please take care and +follow the steps precisely. + +</para></note> + diff --git a/fi/boot-installer/mipsel.xml b/fi/boot-installer/mipsel.xml index 270390c53..a059ba7ce 100644 --- a/fi/boot-installer/mipsel.xml +++ b/fi/boot-installer/mipsel.xml @@ -1,12 +1,96 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> +<!-- original version: 35328 untranslated --> - <sect2 arch="mipsel"> - <title></title> + <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>Cobalt TFTP Booting</title> <para> -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> +Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to +install an NFS server and put the installer files in +<filename>/nfsroot</filename>. When you boot your Cobalt, you have to +press the left and the right cursor buttons at the same time and the +machine will boot via the network from NFS. It will then display several +options on the display. There are the following two installation methods: + +<itemizedlist> +<listitem><para> + +Via SSH (default): In this case, the installer will configure the network +via DHCP and start an SSH server. It will then display a random password +and other login information (such as the IP address) on the Cobalt LCD. +When you connect to the machine with an SSH client you can start with +the installation. + +</para></listitem> +<listitem><para> + +Via serial console: Using a null modem cable, you can connect to the serial +port of your Cobalt machine (using 115200 bps) and perform the installation +this way. This option is not available on Qube 2700 (Qube1) machines since +they have no serial port. + +</para></listitem> +</itemizedlist> </para> - </sect2> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + +<informalexample><screen> +ifconfig eth0 -auto +</screen></informalexample> + +Once you have obtained an IP address, you can load SiByl with the following +command: + +<informalexample><screen> +boot 192.168.1.1:/boot/sibyl +</screen></informalexample> + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + +</para> +</sect3> + </sect2> + + <sect2 arch="mipsel"><title>Boot Parameters</title> + + <sect3> + <title>Cobalt TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly. Instead, you have to edit +the <filename>/nfsroot/default.colo</filename> file on the NFS server and +add your parameters to the <replaceable>args</replaceable> variable. + +</para> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP +server and add your parameters to the <replaceable>extra_args</replaceable> +variable. + +</para> + </sect3> + + </sect2> diff --git a/fi/hardware/hardware-supported.xml b/fi/hardware/hardware-supported.xml index 48a47becb..b0216fdea 100644 --- a/fi/hardware/hardware-supported.xml +++ b/fi/hardware/hardware-supported.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 33887 untranslated --> +<!-- original version: 35330 untranslated --> <sect1 id="hardware-supported"> <title>Supported Hardware</title> @@ -91,16 +91,16 @@ variations of each architecture known as <quote>flavors</quote>. </row> <row> - <entry morerows="3">ARM and StrongARM</entry> - <entry morerows="3">arm</entry> - <entry morerows="3"></entry> + <entry morerows="2">ARM and StrongARM</entry> + <entry morerows="2">arm</entry> + <entry>Netwinder and CATS</entry> <entry>netwinder</entry> </row><row> - <entry>riscpc</entry> -</row><row> - <entry>shark</entry> + <entry>Linksys NSLU2</entry> + <entry>nslu2</entry> </row><row> - <entry>lart</entry> + <entry>RiscPC and Riscstation</entry> + <entry>riscpc</entry> </row> <row> @@ -193,7 +193,7 @@ encounter a few bugs. Use our <ulink url="&url-bts;">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the -<ulink url="&url-list-subscribe;">debian-&architecture; mailing list</ulink> +<ulink url="&url-list-subscribe;">debian-&arch-listname; mailing list</ulink> as well. </para> diff --git a/fi/hardware/network-cards.xml b/fi/hardware/network-cards.xml index d296a821e..f24a7f481 100644 --- a/fi/hardware/network-cards.xml +++ b/fi/hardware/network-cards.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35304 untranslated --> <sect1 id="network-cards"> <title>Network Connectivity Hardware</title> @@ -157,7 +157,7 @@ OSA-Express in QDIO mode, HiperSockets and Guest-LANs <para arch="arm"> The following network interface cards are supported directly by the -boot disks on NetWinder and CATS machines: +boot disks on Netwinder and CATS machines: <itemizedlist> <listitem><para> diff --git a/fi/hardware/supported/arm.xml b/fi/hardware/supported/arm.xml index 9ae4bef4e..e15f41c20 100644 --- a/fi/hardware/supported/arm.xml +++ b/fi/hardware/supported/arm.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 25809 untranslated --> +<!-- original version: 35328 untranslated --> <sect2 arch="arm"><title>CPU, Main Boards, and Video Support</title> @@ -15,22 +15,24 @@ a number of the most common systems. The Debian userland however may be used by <para> Most ARM CPUs may be run in either endian mode (big or little). However, -almost every current system implementation uses little-endian mode. +the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems. </para> <para> -The commonly supported systems are +The supported systems are: <variablelist> + <varlistentry> <term>Netwinder</term> <listitem><para> This is actually the name for the group of machines -based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It +based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known +as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff). @@ -39,13 +41,13 @@ personal server (cps, aka skiff). </varlistentry> <varlistentry> -<term>Bast</term> +<term>NSLU2</term> <listitem><para> -This is a modern ARM 920 board with a 266MHz Samsung -processor. It has integrated IDE, USB, Serial, Parallel, audio, video, -flash and two ethernet ports. This system has a good bootloader which -is also found on the CATS and Riscstation systems. +The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small +device which allows you to easily provide storage via the network. It +comes with an Ethernet connection and two USB ports to which hard drives +can be connected. </para></listitem> </varlistentry> @@ -79,16 +81,6 @@ simple bootloader. </para></listitem> </varlistentry> -<varlistentry> -<term>LART</term> -<listitem><para> - -This is a modular open hardware platform intended to be built -by enthusiasts. To be useful to install Debian it requires its KSB -expansion board. - -</para></listitem> -</varlistentry> </variablelist> </para> diff --git a/fi/hardware/supported/mips.xml b/fi/hardware/supported/mips.xml index 7ea1a2bf7..9dd0e3716 100644 --- a/fi/hardware/supported/mips.xml +++ b/fi/hardware/supported/mips.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 22939 untranslated --> +<!-- original version: 35330 untranslated --> <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title> @@ -28,7 +28,7 @@ at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url="&url-list-subscribe;"> -debian-&architecture; mailing list</ulink>. +debian-&arch-listname; mailing list</ulink>. </para> diff --git a/fi/hardware/supported/mipsel.xml b/fi/hardware/supported/mipsel.xml index 63d5a5bc1..823f18eb9 100644 --- a/fi/hardware/supported/mipsel.xml +++ b/fi/hardware/supported/mipsel.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28997 untranslated --> +<!-- original version: 35330 untranslated --> <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title> @@ -15,8 +15,8 @@ DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> -Cobalt Microserver: only MIPS based Cobalt machines are covered here. -This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Cobalt Microserver: only MIPS based Cobalt machines are covered here. This +includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> @@ -33,7 +33,7 @@ at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url="&url-list-subscribe;"> -debian-&architecture; mailing list</ulink>. +debian-&arch-listname; mailing list</ulink>. </para> @@ -97,8 +97,10 @@ The Debian installation system works on the following machines: </para><para> -All Cobalt machines are supported which have a serial console (which is -needed for the installation). +All Cobalt machines are supported. In the past, only machines with a +serial console were supported (that is, all machines except for the Qube +2700, aka Qube1). However, installations are now also possible through +SSH. </para><para> diff --git a/fi/install-methods/download/arm.xml b/fi/install-methods/download/arm.xml index b21ad3ef1..d5c5b1014 100644 --- a/fi/install-methods/download/arm.xml +++ b/fi/install-methods/download/arm.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35372 untranslated --> <sect3 arch="arm" id="riscpc-install-files"> @@ -16,10 +16,10 @@ Download this file onto the RISC OS machine, copy the </sect3> <sect3 arch="arm" id="netwinder-install-files"> - <title>NetWinder Installation Files</title> + <title>Netwinder Installation Files</title> <para> -The easiest way to boot a NetWinder is over the network, using the +The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;. </para> @@ -29,9 +29,20 @@ supplied TFTP image &netwinder-boot-img;. <title>CATS Installation Files</title> <para> -The only supported boot method for CATS is to use the combined image -&cats-boot-img;. This can be loaded from any device accessible to the -Cyclone bootloader. +CATS can be booted either via the network or from CD-ROM. The kernel and +initrd can be obtained from &cats-boot-img;. </para> </sect3> + + <sect3 arch="arm" id="nslu2-install-files"> + <title>NSLU2 Installation Files</title> +<para> + +A firmware image is provided for the Linksys NSLU2 which will automatically +boot <classname>debian-installer</classname>. This firmware image can be +obtained from &nslu2-firmware-img;. + +</para> + </sect3> + diff --git a/fi/preparing/needed-info.xml b/fi/preparing/needed-info.xml index 4a2e392a0..042a13c15 100644 --- a/fi/preparing/needed-info.xml +++ b/fi/preparing/needed-info.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 31136 untranslated --> +<!-- original version: 35130 untranslated --> <sect1 id="needed-info"> <title>Information You Will Need</title> @@ -214,9 +214,12 @@ networking and e-mail. <entry>How many you have.</entry> </row> <row arch="not-s390"><entry>Their order on the system.</entry></row> -<row arch="not-s390"> +<row arch="not-s390;not-m68k"> <entry>Whether IDE or SCSI (most computers are IDE).</entry> </row> +<row arch="m68k"> + <entry>Whether IDE or SCSI (most m68k computers are SCSI).</entry> +</row> <row arch="not-s390"><entry>Available free space.</entry></row> <row arch="not-s390"><entry>Partitions.</entry></row> <row arch="not-s390"> diff --git a/fi/using-d-i/components.xml b/fi/using-d-i/components.xml index e619cdcdc..2d3228e49 100644 --- a/fi/using-d-i/components.xml +++ b/fi/using-d-i/components.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 33730 untranslated --> +<!-- original version: 35395 untranslated --> <sect1 id="module-details"> <title>Using Individual Components</title> @@ -182,6 +182,5 @@ user in case something goes wrong. &module-cdrom-checker.xml; &module-shell.xml; &module-network-console.xml; -&module-baseconfig.xml; </sect2> </sect1> diff --git a/fi/using-d-i/modules/baseconfig.xml b/fi/using-d-i/modules/baseconfig.xml deleted file mode 100644 index a189aa11d..000000000 --- a/fi/using-d-i/modules/baseconfig.xml +++ /dev/null @@ -1,17 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 29903 untranslated --> - - <sect3 id="baseconfig"> - <title>Running <command>base-config</command> From Within &d-i;</title> - -<para> - -It is possible to configure the base system within the first stage -installer (before rebooting from the hard drive), by running -<command>base-config</command> in a <firstterm>chroot</firstterm> -environment. This is mainly useful for testing the installer and -should normally be avoided. -<!-- Feel free to prove me I'm wrong --> - -</para> - </sect3> diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml index 4b3bc8def..520dfe9bf 100644 --- a/nl/appendix/preseed.xml +++ b/nl/appendix/preseed.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 34168 untranslated --> +<!-- original version: 35051 untranslated --> <!-- Be carefull with the format of this file as it is parsed to generate @@ -137,7 +137,7 @@ questions being asked. Although most questions used by &d-i; can be preseeded using this method, there are some notable exceptions. You must (re)partition an entire disk or use available free space on a disk; it is not possible to use existing -partitions. You currently cannot use preseeding to set up RAID and LVM. +partitions. You currently cannot use preseeding to set up RAID. </para> </sect2> @@ -278,11 +278,11 @@ load it. </para><para> -For the other preseeding methods you need to tell the installer what file to -use when you boot it. This is done by passing the kernel a boot parameter, -either manually at boot time or by editing the bootloader configuration file -(e.g. <filename>syslinux.cfg</filename>) and adding the parameter to the end -of the append line(s) for the kernel. +For the other preseeding methods you need to tell the installer what file +to use when you boot it. This is normally done by passing the kernel a boot +parameter, either manually at boot time or by editing the bootloader +configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the +parameter to the end of the append line(s) for the kernel. </para><para> @@ -323,6 +323,43 @@ questions even if the preseeding below misses some. </para> </sect2> + + <sect2 id="preseed-dhcp"> + <title>Using a DHCP server to specify preseed files</title> +<para> + +It's also possible to use DHCP to specify a preseed file to download from +the network. DHCP allows specifying a filename. Normally this is a file to +netboot, but if it appears to be an URL then installation media that +support network preseeding will download the file from the URL and use it +as a preseed file. Here is an example of how to set it up in the dhcpd.conf +for version 3 of the ISC DHCP server (the dhcp3-server Debian package). + +</para> + +<informalexample><screen> +if substring (option vendor-class-identifier, 0, 3) = "d-i" { + filename "http://host/preseed.cfg"; +} +</screen></informalexample> + +<para> + +Note that the above example limits this filename to DHCP clients that identify +themselves as "d-i", so it will not affect regular DHCP clients, but only +the installer. You can also put the text in a stanza for only one particular +host to avoid preseeding all installs on your network. + +</para><para> + +A good way to use the DHCP preseeding is to only preseed values specific to +your network, such as the Debian mirror to use. This way installs on your +network will automatically get a good mirror selected, but the rest of the +installation can be performed interactively. Using DHCP preseeding to fully +automate Debian installs should only be done with care. + +</para> + </sect2> <sect2 id="preseed-bootparms"> <title>Using boot parameters to supplement preseeding</title> @@ -589,8 +626,7 @@ supported by <classname>partman-auto</classname>. You can choose to either partition existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preseed file. It is currently not -possible to partition multiple disks using preseeding nor to set up RAID or -LVM. +possible to partition multiple disks using preseeding nor to set up RAID. </para> @@ -604,6 +640,7 @@ correct one will be selected before using preseeding. <informalexample role="example"><screen> # If the system has free space you can choose to only partition that space. +# Note: the preseed value for this template needs to be localized (translated). #d-i partman-auto/init_automatically_partition \ # select Use the largest continuous free space @@ -612,7 +649,8 @@ correct one will be selected before using preseeding. # 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: +# You can choose from any of the predefined partitioning recipes. +# Note: the preseed value for this template needs to be localized (translated). d-i partman-auto/choose_recipe \ select All files in one partition (recommended for new users) #d-i partman-auto/choose_recipe \ diff --git a/nl/bookinfo.xml b/nl/bookinfo.xml index d479d428c..fe3eb9099 100644 --- a/nl/bookinfo.xml +++ b/nl/bookinfo.xml @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<!-- original version: 29882 --> +<!-- original version: 34719 --> <bookinfo id="debian_installation_guide"> <title>&debian; Installatiehandleiding</title> diff --git a/nl/boot-installer/arm.xml b/nl/boot-installer/arm.xml index 505a05323..8b273d74e 100644 --- a/nl/boot-installer/arm.xml +++ b/nl/boot-installer/arm.xml @@ -1,94 +1,101 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35328 untranslated --> <sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title> &boot-installer-intro-net.xml; - <sect3 arch="arm"><title>Booting from TFTP on NetWinder</title> - + <sect3 arch="arm"><title>Booting from TFTP on Netwinder</title> <para> -NetWinders have two network interfaces: The 10Mbps NE2000-compatible -card is <filename>eth0</filename> and the 100Mbps Tulip card is -<filename>eth1</filename>. - -</para><note><para> - -You need NeTTrom 2.2.1 or later to boot the -installation system. NeTTrom 2.3.3 is recommended: get these files -from -<ulink url="ftp://ftp.netwinder.org/pub/netwinder/firmware/"></ulink>: -<itemizedlist> -<listitem><para> - -<filename>nettrom-2.3-3.armv4l.rpm</filename> - -</para></listitem> -<listitem><para> +Netwinders have two network interfaces: A 10Mbps NE2000-compatible +card (which is generally referred to as <literal>eth0</literal>) and +a 100Mbps Tulip card. There may be problems loading the image via TFTP +using the 100Mbps card so it is recommended that you use the 10Mbps +interfaced (the one labeled with <literal>10 Base-T</literal>). -<filename>nettrom-2.3.3.bin</filename> +</para> +<note><para> -</para></listitem> -<listitem><para> +You need NeTTrom 2.2.1 or later to boot the installation system, and +version 2.3.3 is recommended. Unfortunately, firmware files are currently +not available for download because of license issues. If this situation +changes, you may find new images at <ulink url="http//www.netwinder.org/"></ulink>. -<filename>nettrom-2.3.3.bin.md5sum</filename> +</para></note> +<para> -</para></listitem> -</itemizedlist> +When you boot your Netwinder you have to interrupt the boot process during the +countdown. This allows you to set a number of firmware settings needed in +order to boot the installer. First of all, start by loading the default +settings: -</para></note><para> +<informalexample><screen> + NeTTrom command-> load-defaults +</screen></informalexample> -After rebooting and interrupting the boot process during the countdown, you -must first configure the network either with a static address: +Furthermore, you must configure the network, either with a static address: <informalexample><screen> + NeTTrom command-> setenv netconfig_eth0 flash NeTTrom command-> setenv eth0_ip 192.168.0.10/24 </screen></informalexample> where 24 is the number of set bits in the netmask, or a dynamic address: <informalexample><screen> - NeTTrom command-> boot diskless + NeTTrom command-> setenv netconfig_eth0 dhcp </screen></informalexample> You may also need to configure the <userinput>route1</userinput> -settings if the TFTP -server is not on the local subnet. The rest of the config is pretty -standard (the save-all step is optional): +settings if the TFTP server is not on the local subnet. + +Following these settings, you have to specify the TFTP server and the +location of the image. You can then store your settings to flash. <informalexample><screen> NeTTrom command-> setenv kerntftpserver 192.168.0.1 NeTTrom command-> setenv kerntftpfile boot.img NeTTrom command-> save-all - NeTTrom command-> setenv netconfig_eth0 flash +</screen></informalexample> + +Now you have to tell the firmware that the TFTP image should be booted: + +<informalexample><screen> NeTTrom command-> setenv kernconfig tftp NeTTrom command-> setenv rootdev /dev/ram - NeTTrom command-> setenv cmdappend root=/dev/ram </screen></informalexample> -Only the last four of these interfere with normal disk booting, so it is -safe to issue <command>save-all</command> right before them, which will -store the network settings in case you need to boot from the network -again. - -If you want to use the serial console to install your NetWinder, you also -need the following setting: +If you use a serial console to install your Netwinder, you need to add the +following setting: <informalexample><screen> NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200 </screen></informalexample> -Use the <command>printenv</command> command to review your -environment settings. Finally, if your <envar>cmdappend</envar> -NeTTrom variable has the <option>noinitrd</option> option, you must -remove it so the downloaded kernel can boot with its attached ramdisk. +Alternatively, for installations using a keyboard and monitor you have to +set: -</para> - </sect3> +<informalexample><screen> + NeTTrom command-> setenv cmdappend root=/dev/ram +</screen></informalexample> + +You can use the <command>printenv</command> command to review your +environment settings. After you have verified that the settings are +correct, you can load the image: + +<informalexample><screen> + NeTTrom command-> boot +</screen></informalexample> + +In case you run into any problems, a <ulink +url="http://www.netwinder.org/howto/Firmware-HOWTO.html">detailed +HOWTO</ulink> is available. - <sect3 arch="arm"><title>Booting from TFTP on CATS</title> +</para> + </sect3> + <sect3 arch="arm"><title>Booting from TFTP on CATS</title> <para> On CATS machines, use <command>boot de0:</command> or similar at the @@ -99,7 +106,6 @@ Cyclone prompt. </sect2> - <sect2 arch="arm"><title>Booting from CD-ROM</title> &boot-installer-intro-cd.xml; @@ -111,3 +117,103 @@ To boot a CD-ROM from the Cyclone console prompt, use the command </para> </sect2> + + + <sect2 arch="arm" id="boot-firmware"><title>Booting from Firmware</title> + +&boot-installer-intro-firmware.xml; + + <sect3 arch="arm" id="boot-firmware-nslu2"><title>Booting the NSLU2</title> +<para> + +There are three ways how to put the installer firmware into flash: + +</para> + + <sect4 arch="arm"><title>Using the NSLU2 web interface</title> +<para> + +Go to the administration section and choose the menu item +<literal>Upgrade</literal>. You can then browse your disk for the +installer image you have previously downloaded. Then press the +<literal>Start Upgrade</literal> button, confirm, wait for a few minutes +and confirm again. The system will then boot straight into the installer. + +</para> + </sect4> + + <sect4 arch="arm"><title>Via the network using Linux/Unix</title> +<para> + +You can use <command>upslug2</command> from any Linux or Unix machine to +upgrade the machine via the network. This software is packaged for +Debian. + +First, you have to put your NSLU2 in upgrade mode: + +<orderedlist> +<listitem><para> + +Disconnect any disks and/or devices from the USB ports. + +</para></listitem> +<listitem><para> + +Power off the NSLU2 + +</para></listitem> +<listitem><para> + +Press and hold the reset button (accessible through the small hole on the +back just above the power input). + +</para></listitem> +<listitem><para> + +Press and release the power button to power on the NSLU2. + +</para></listitem> +<listitem><para> + +Wait for 10 seconds watching the ready/status LED. After 10 seconds it +will change from amber to red. Immediately release the reset button. + +</para></listitem> +<listitem><para> + +The NSLU2 ready/status LED will flash alternately red/green (there is a 1 +second delay before the first green). The NSLU2 is now in upgrade mode. + +</para></listitem> +</orderedlist> + +See the <ulink +url="http://www.nslu2-linux.org/wiki/OpenSlug/UsingTheBinary">NSLU2-Linux +pages</ulink> if you have problems with this. + +Once your NSLU2 is in upgrade mode, you can flash the new image: + +<informalexample><screen> +sudo upslug2 -i di-nslu2.bin +</screen></informalexample> + +Note that the tool also shows the MAC address of your NSLU2, which may come +in handy to configure your DHCP server. After the whole image has been +written and verified, the system will automatically reboot. Make sure you +connect your USB disk again now, otherwise the installer won't be able to +find it. + +</para> + </sect4> + + <sect4 arch="arm"><title>Via the network using Windows</title> +<para> + +There is <ulink +url="http://www.everbesthk.com/8-download/sercomm/firmware/all_router_utility.zip">a +tool</ulink> for Windows to upgrade the firmware via the network. + +</para> + </sect4> + </sect3> + </sect2> diff --git a/nl/boot-installer/boot-installer.xml b/nl/boot-installer/boot-installer.xml index ab8ab9784..0a5a08799 100644 --- a/nl/boot-installer/boot-installer.xml +++ b/nl/boot-installer/boot-installer.xml @@ -1,11 +1,11 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> +<!-- original version: 35310 untranslated --> <chapter id="boot-installer"><title>Booting the Installation System</title> <!-- Include only archs that are documented to avoid build-errors --> <!-- The arch="..." condition can be deleted when al archs are present --> - <sect1 arch="alpha;arm;i386;ia64;m68k;mips;s390;powerpc;sparc"> + <sect1 arch="alpha;arm;i386;ia64;m68k;mips;mipsel;s390;powerpc;sparc"> <title>Booting the Installer on &arch-title;</title> <!-- This info is so architecture dependent, that I have turned the --> @@ -19,7 +19,7 @@ &boot-installer-ia64.xml; &boot-installer-m68k.xml; &boot-installer-mips.xml; -<!-- &boot-installer-mipsel.xml; --> +&boot-installer-mipsel.xml; &boot-installer-s390.xml; &boot-installer-powerpc.xml; &boot-installer-sparc.xml; diff --git a/nl/boot-installer/intro-firmware.xml b/nl/boot-installer/intro-firmware.xml new file mode 100644 index 000000000..fe869608e --- /dev/null +++ b/nl/boot-installer/intro-firmware.xml @@ -0,0 +1,18 @@ +<!-- retain these comments for translator revision tracking --> +<!-- original version: 35309 untranslated --> + +<para> + +There is an increasing number of consumer devices that directly boot from a +flash chip on the device. The installer can be written to flash so it will +automatically start when you reboot your machines. + +</para><note><para> + +In many cases, changing the firmware of an embedded device voids your +warranty. Sometimes you are also not able to recover your device if there +are problems during the flashing process. Therefore, please take care and +follow the steps precisely. + +</para></note> + diff --git a/nl/boot-installer/mipsel.xml b/nl/boot-installer/mipsel.xml index 270390c53..a059ba7ce 100644 --- a/nl/boot-installer/mipsel.xml +++ b/nl/boot-installer/mipsel.xml @@ -1,12 +1,96 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 24701 untranslated --> +<!-- original version: 35328 untranslated --> - <sect2 arch="mipsel"> - <title></title> + <sect2 arch="mipsel" id="boot-tftp"><title>Booting with TFTP</title> + + <sect3> + <title>Cobalt TFTP Booting</title> <para> -<!-- Placeholder document; please write and include in - boot-installer.xml and build/templates/docstruct.ent --> +Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to +install an NFS server and put the installer files in +<filename>/nfsroot</filename>. When you boot your Cobalt, you have to +press the left and the right cursor buttons at the same time and the +machine will boot via the network from NFS. It will then display several +options on the display. There are the following two installation methods: + +<itemizedlist> +<listitem><para> + +Via SSH (default): In this case, the installer will configure the network +via DHCP and start an SSH server. It will then display a random password +and other login information (such as the IP address) on the Cobalt LCD. +When you connect to the machine with an SSH client you can start with +the installation. + +</para></listitem> +<listitem><para> + +Via serial console: Using a null modem cable, you can connect to the serial +port of your Cobalt machine (using 115200 bps) and perform the installation +this way. This option is not available on Qube 2700 (Qube1) machines since +they have no serial port. + +</para></listitem> +</itemizedlist> </para> - </sect2> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +On the Broadcom BCM91250A evaluation board, you have to load the SiByl boot +loader via TFTP which will then load and start the Debian installer. In +most cases, you will first obtain an IP address via DHCP but it is also +possible to configure a static address. In order to use DHCP, you can +enter the following command on the CFE prompt: + +<informalexample><screen> +ifconfig eth0 -auto +</screen></informalexample> + +Once you have obtained an IP address, you can load SiByl with the following +command: + +<informalexample><screen> +boot 192.168.1.1:/boot/sibyl +</screen></informalexample> + +You need to substitute the IP address listed in this example with either +the name or the IP address of your TFTP server. Once you issue this +command, the installer will be loaded automatically. + +</para> +</sect3> + </sect2> + + <sect2 arch="mipsel"><title>Boot Parameters</title> + + <sect3> + <title>Cobalt TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly. Instead, you have to edit +the <filename>/nfsroot/default.colo</filename> file on the NFS server and +add your parameters to the <replaceable>args</replaceable> variable. + +</para> + </sect3> + + <sect3> +<!-- Note to translators: this is the same section as in mips.xml --> + <title>Broadcom BCM91250A TFTP Booting</title> +<para> + +You cannot pass any boot parameters directly from the CFE prompt. Instead, +you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP +server and add your parameters to the <replaceable>extra_args</replaceable> +variable. + +</para> + </sect3> + + </sect2> diff --git a/nl/hardware/hardware-supported.xml b/nl/hardware/hardware-supported.xml index 48a47becb..b0216fdea 100644 --- a/nl/hardware/hardware-supported.xml +++ b/nl/hardware/hardware-supported.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 33887 untranslated --> +<!-- original version: 35330 untranslated --> <sect1 id="hardware-supported"> <title>Supported Hardware</title> @@ -91,16 +91,16 @@ variations of each architecture known as <quote>flavors</quote>. </row> <row> - <entry morerows="3">ARM and StrongARM</entry> - <entry morerows="3">arm</entry> - <entry morerows="3"></entry> + <entry morerows="2">ARM and StrongARM</entry> + <entry morerows="2">arm</entry> + <entry>Netwinder and CATS</entry> <entry>netwinder</entry> </row><row> - <entry>riscpc</entry> -</row><row> - <entry>shark</entry> + <entry>Linksys NSLU2</entry> + <entry>nslu2</entry> </row><row> - <entry>lart</entry> + <entry>RiscPC and Riscstation</entry> + <entry>riscpc</entry> </row> <row> @@ -193,7 +193,7 @@ encounter a few bugs. Use our <ulink url="&url-bts;">Bug Tracking System</ulink> to report any problems; make sure to mention the fact that the bug is on the &arch-title; platform. It can be necessary to use the -<ulink url="&url-list-subscribe;">debian-&architecture; mailing list</ulink> +<ulink url="&url-list-subscribe;">debian-&arch-listname; mailing list</ulink> as well. </para> diff --git a/nl/hardware/network-cards.xml b/nl/hardware/network-cards.xml index d296a821e..f24a7f481 100644 --- a/nl/hardware/network-cards.xml +++ b/nl/hardware/network-cards.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35304 untranslated --> <sect1 id="network-cards"> <title>Network Connectivity Hardware</title> @@ -157,7 +157,7 @@ OSA-Express in QDIO mode, HiperSockets and Guest-LANs <para arch="arm"> The following network interface cards are supported directly by the -boot disks on NetWinder and CATS machines: +boot disks on Netwinder and CATS machines: <itemizedlist> <listitem><para> diff --git a/nl/hardware/supported/arm.xml b/nl/hardware/supported/arm.xml index 9ae4bef4e..e15f41c20 100644 --- a/nl/hardware/supported/arm.xml +++ b/nl/hardware/supported/arm.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 25809 untranslated --> +<!-- original version: 35328 untranslated --> <sect2 arch="arm"><title>CPU, Main Boards, and Video Support</title> @@ -15,22 +15,24 @@ a number of the most common systems. The Debian userland however may be used by <para> Most ARM CPUs may be run in either endian mode (big or little). However, -almost every current system implementation uses little-endian mode. +the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems. </para> <para> -The commonly supported systems are +The supported systems are: <variablelist> + <varlistentry> <term>Netwinder</term> <listitem><para> This is actually the name for the group of machines -based upon the StrongARM 110 CPU and Intel 21285 Northbridge. It +based upon the StrongARM 110 CPU and Intel 21285 Northbridge (also known +as Footbridge). It comprises of machines like: Netwinder (possibly one of the most common ARM boxes), CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, aka skiff). @@ -39,13 +41,13 @@ personal server (cps, aka skiff). </varlistentry> <varlistentry> -<term>Bast</term> +<term>NSLU2</term> <listitem><para> -This is a modern ARM 920 board with a 266MHz Samsung -processor. It has integrated IDE, USB, Serial, Parallel, audio, video, -flash and two ethernet ports. This system has a good bootloader which -is also found on the CATS and Riscstation systems. +The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small +device which allows you to easily provide storage via the network. It +comes with an Ethernet connection and two USB ports to which hard drives +can be connected. </para></listitem> </varlistentry> @@ -79,16 +81,6 @@ simple bootloader. </para></listitem> </varlistentry> -<varlistentry> -<term>LART</term> -<listitem><para> - -This is a modular open hardware platform intended to be built -by enthusiasts. To be useful to install Debian it requires its KSB -expansion board. - -</para></listitem> -</varlistentry> </variablelist> </para> diff --git a/nl/hardware/supported/mips.xml b/nl/hardware/supported/mips.xml index 7ea1a2bf7..9dd0e3716 100644 --- a/nl/hardware/supported/mips.xml +++ b/nl/hardware/supported/mips.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 22939 untranslated --> +<!-- original version: 35330 untranslated --> <sect2 arch="mips"><title>CPU, Main Boards, and Video Support</title> @@ -28,7 +28,7 @@ at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url="&url-list-subscribe;"> -debian-&architecture; mailing list</ulink>. +debian-&arch-listname; mailing list</ulink>. </para> diff --git a/nl/hardware/supported/mipsel.xml b/nl/hardware/supported/mipsel.xml index 63d5a5bc1..823f18eb9 100644 --- a/nl/hardware/supported/mipsel.xml +++ b/nl/hardware/supported/mipsel.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28997 untranslated --> +<!-- original version: 35330 untranslated --> <sect2 arch="mipsel"><title>CPU, Main Boards, and Video Support</title> @@ -15,8 +15,8 @@ DECstation: various models of the DECstation are supported. </para></listitem> <listitem><para> -Cobalt Microserver: only MIPS based Cobalt machines are covered here. -This included the Cobalt Qube, RaQ, Qube2 and RaQ2, and the Gateway +Cobalt Microserver: only MIPS based Cobalt machines are covered here. This +includes the Cobalt Qube 2700 (Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></listitem> @@ -33,7 +33,7 @@ at the <ulink url="&url-linux-mips;">Linux-MIPS homepage</ulink>. In the following, only the systems supported by the Debian installer will be covered. If you are looking for support for other subarchitectures, please contact the <ulink url="&url-list-subscribe;"> -debian-&architecture; mailing list</ulink>. +debian-&arch-listname; mailing list</ulink>. </para> @@ -97,8 +97,10 @@ The Debian installation system works on the following machines: </para><para> -All Cobalt machines are supported which have a serial console (which is -needed for the installation). +All Cobalt machines are supported. In the past, only machines with a +serial console were supported (that is, all machines except for the Qube +2700, aka Qube1). However, installations are now also possible through +SSH. </para><para> diff --git a/nl/install-methods/download/arm.xml b/nl/install-methods/download/arm.xml index b21ad3ef1..d5c5b1014 100644 --- a/nl/install-methods/download/arm.xml +++ b/nl/install-methods/download/arm.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> +<!-- original version: 35372 untranslated --> <sect3 arch="arm" id="riscpc-install-files"> @@ -16,10 +16,10 @@ Download this file onto the RISC OS machine, copy the </sect3> <sect3 arch="arm" id="netwinder-install-files"> - <title>NetWinder Installation Files</title> + <title>Netwinder Installation Files</title> <para> -The easiest way to boot a NetWinder is over the network, using the +The easiest way to boot a Netwinder is over the network, using the supplied TFTP image &netwinder-boot-img;. </para> @@ -29,9 +29,20 @@ supplied TFTP image &netwinder-boot-img;. <title>CATS Installation Files</title> <para> -The only supported boot method for CATS is to use the combined image -&cats-boot-img;. This can be loaded from any device accessible to the -Cyclone bootloader. +CATS can be booted either via the network or from CD-ROM. The kernel and +initrd can be obtained from &cats-boot-img;. </para> </sect3> + + <sect3 arch="arm" id="nslu2-install-files"> + <title>NSLU2 Installation Files</title> +<para> + +A firmware image is provided for the Linksys NSLU2 which will automatically +boot <classname>debian-installer</classname>. This firmware image can be +obtained from &nslu2-firmware-img;. + +</para> + </sect3> + diff --git a/nl/preparing/needed-info.xml b/nl/preparing/needed-info.xml index ed2574a07..d86263e77 100644 --- a/nl/preparing/needed-info.xml +++ b/nl/preparing/needed-info.xml @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<!-- original version: 31136 --> +<!-- original version: 35130 --> <sect1 id="needed-info"> <title>Benodigde informatie</title> @@ -208,9 +208,12 @@ uw netwerk en e-mail. <entry>Hoeveel heeft u er.</entry> </row> <row arch="not-s390"><entry>Hun volgorde in het systeem.</entry></row> -<row arch="not-s390"> +<row arch="not-s390;not-m68k"> <entry>Zijn ze IDE of SCSI (de meeste computers hebben IDE).</entry> </row> +<row arch="m68k"> + <entry>Zijn ze IDE of SCSI (de meeste m68k computers hebben SCSI).</entry> +</row> <row arch="not-s390"><entry>Beschikbare vrije ruimte.</entry></row> <row arch="not-s390"><entry>Partities.</entry></row> <row arch="not-s390"> diff --git a/nl/using-d-i/components.xml b/nl/using-d-i/components.xml index 744f28714..8eadbefff 100644 --- a/nl/using-d-i/components.xml +++ b/nl/using-d-i/components.xml @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<!-- original version: 33730 --> +<!-- original version: 35395 --> <sect1 id="module-details"> <title>Individuele modules gebruiken</title> @@ -189,6 +189,5 @@ als er iets mis gaat. &module-cdrom-checker.xml; &module-shell.xml; &module-network-console.xml; -&module-baseconfig.xml; </sect2> </sect1> diff --git a/nl/using-d-i/modules/baseconfig.xml b/nl/using-d-i/modules/baseconfig.xml deleted file mode 100644 index b59f4a9fc..000000000 --- a/nl/using-d-i/modules/baseconfig.xml +++ /dev/null @@ -1,17 +0,0 @@ -<?xml version="1.0" encoding="ISO-8859-1"?> -<!-- original version: 29903 --> - - <sect3 id="baseconfig"> - <title><command>Base-config</command> uitvoeren vanuit &d-i;</title> - -<para> - -Het is mogelijk om het basissysteem te configureren tijdens de eerste fase -van de installatie (dus voordat u het systeem opnieuw opstartvanaf de harde -schijf) door in een <firstterm>chroot</firstterm>-omgeving het commando -<command>base-config</command> uit te voeren. Dit is voornamelijk zinvol -bij het testen van het installatiesysteem en dient normaalgesproken te -worden gemeden. - -</para> - </sect3> |