diff options
Diffstat (limited to 'nl/install-methods')
-rw-r--r-- | nl/install-methods/automatic-install.xml | 34 | ||||
-rw-r--r-- | nl/install-methods/boot-drive-files.xml | 176 | ||||
-rw-r--r-- | nl/install-methods/boot-usb-files.xml | 159 | ||||
-rw-r--r-- | nl/install-methods/create-floppy.xml | 108 | ||||
-rw-r--r-- | nl/install-methods/download/arm.xml | 88 | ||||
-rw-r--r-- | nl/install-methods/download/powerpc.xml | 28 | ||||
-rw-r--r-- | nl/install-methods/downloading-files.xml | 34 | ||||
-rw-r--r-- | nl/install-methods/floppy/i386.xml | 35 | ||||
-rw-r--r-- | nl/install-methods/floppy/powerpc.xml | 122 | ||||
-rw-r--r-- | nl/install-methods/install-methods.xml | 16 | ||||
-rw-r--r-- | nl/install-methods/install-tftp.xml | 341 | ||||
-rw-r--r-- | nl/install-methods/ipl-tape.xml | 24 | ||||
-rw-r--r-- | nl/install-methods/official-cdrom.xml | 69 | ||||
-rw-r--r-- | nl/install-methods/tftp/bootp.xml | 73 | ||||
-rw-r--r-- | nl/install-methods/tftp/dhcp.xml | 94 | ||||
-rw-r--r-- | nl/install-methods/tftp/rarp.xml | 32 | ||||
-rw-r--r-- | nl/install-methods/usb-setup/powerpc.xml | 119 | ||||
-rw-r--r-- | nl/install-methods/usb-setup/x86.xml | 117 |
18 files changed, 0 insertions, 1669 deletions
diff --git a/nl/install-methods/automatic-install.xml b/nl/install-methods/automatic-install.xml deleted file mode 100644 index 6aaddea31..000000000 --- a/nl/install-methods/automatic-install.xml +++ /dev/null @@ -1,34 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 33725 untranslated --> - - <sect1 id="automatic-install"> - <title>Automatic Installation</title> -<para> - -For installing on multiple computers it's possible to do fully -automatic installations. &debian; packages intended for this include -<classname>fai</classname> (which uses an install server), -<classname>replicator</classname>, -<classname>systemimager</classname>, -<classname>autoinstall</classname>, and -the &debian; Installer itself. - -</para> - - <sect2 id="preseed"> - <title>Automatic Installation Using the &debian; Installer</title> -<para> - -The &debian; Installer supports automating installs via preconfiguration -files. A preconfiguration file can be loaded from the network or from -removable media, and used to fill in answers to questions asked during the -installation process. - -</para><para> - -Full documentation on preseeding including a working example that you can -edit is in <xref linkend="appendix-preseed"/>. - -</para> - </sect2> - </sect1> diff --git a/nl/install-methods/boot-drive-files.xml b/nl/install-methods/boot-drive-files.xml deleted file mode 100644 index 22205ddd1..000000000 --- a/nl/install-methods/boot-drive-files.xml +++ /dev/null @@ -1,176 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39614 untranslated --> - - <sect1 condition="bootable-disk" id="boot-drive-files"> - <title>Preparing Files for Hard Disk Booting</title> -<para> - -The installer may be booted using boot files placed on an -existing hard drive partition, either launched from another operating -system or by invoking a boot loader directly from the BIOS. - -</para><para> - -A full, <quote>pure network</quote> installation can be achieved using this -technique. This avoids all hassles of removable media, like finding -and burning CD images or struggling with too numerous and -unreliable floppy disks. - -</para><para arch="x86"> - -The installer cannot boot from files on an NTFS file system. - -</para><para arch="powerpc"> - -The installer cannot boot from files on an HFS+ file system. MacOS -System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all -use HFS+. To determine whether your existing file system is HFS+, -select <userinput>Get Info</userinput> for the volume in question. HFS -file systems appear as <userinput>Mac OS Standard</userinput>, while -HFS+ file systems say <userinput>Mac OS Extended</userinput>. You must -have an HFS partition in order to exchange files between MacOS and -Linux, in particular the installation files you download. - -</para><para arch="powerpc"> - -Different programs are used for hard disk installation system booting, -depending on whether the system is a <quote>NewWorld</quote> or an -<quote>OldWorld</quote> model. - -</para> - - <sect2 arch="x86" id="files-lilo"> - <title>Hard disk installer booting using <command>LILO</command> or - <command>GRUB</command></title> -<para> - -This section explains how to add to or even replace an existing linux -installation using either <command>LILO</command> or -<command>GRUB</command>. - -</para><para> - -At boot time, both bootloaders support loading in memory not -only the kernel, but also a disk image. This RAM disk can be used as -the root file-system by the kernel. - -</para><para> - -Copy the following files from the &debian; archives to a -convenient location on your hard drive, for instance to -<filename>/boot/newinstall/</filename>. - -<itemizedlist> -<listitem><para> - -<filename>vmlinuz</filename> (kernel binary) - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> (ramdisk image) - -</para></listitem> -</itemizedlist> - -</para><para> - -Finally, to configure the bootloader proceed to -<xref linkend="boot-initrd"/>. - -</para> - </sect2> - - - <sect2 arch="powerpc" id="files-oldworld"> - <title>Hard Disk Installer Booting for OldWorld Macs</title> -<para> - -The <filename>boot-floppy-hfs</filename> floppy uses -<application>miBoot</application> to launch Linux installation, but -<application>miBoot</application> cannot easily be used for hard disk -booting. <application>BootX</application>, launched from MacOS, -supports booting from files placed on the hard -disk. <application>BootX</application> can also be used to dual-boot -MacOS and Linux after your &debian; installation is complete. For the -Performa 6360, it appears that <command>quik</command> cannot make the -hard disk bootable. So <application>BootX</application> is required -on that model. - -</para><para> - -Download and unstuff the <application>BootX</application> -distribution, available from <ulink url="&url-powerpc-bootx;"></ulink>, -or in the -<filename>dists/woody/main/disks-powerpc/current/powermac</filename> -directory on &debian; http/ftp mirrors and official &debian; CDs. Use -<application>Stuffit Expander</application> to extract it from its -archive. Within the package, there is an empty folder called -<filename>Linux Kernels</filename>. Download -<filename>linux.bin</filename> and -<filename>ramdisk.image.gz</filename> from the -<filename>disks-powerpc/current/powermac</filename> folder, and place -them in the <filename>Linux Kernels</filename> folder. Then place the -<filename>Linux Kernels</filename> folder in the active System Folder. - -</para> - </sect2> - - <sect2 arch="powerpc" id="files-newworld"> - <title>Hard Disk Installer Booting for NewWorld Macs</title> -<para> - -NewWorld PowerMacs support booting from a network or an ISO9660 -CD-ROM, as well as loading ELF binaries directly from the hard -disk. These machines will boot Linux directly via -<command>yaboot</command>, which supports loading a kernel and RAMdisk -directly from an ext2 partition, as well as dual-booting with -MacOS. Hard disk booting of the installer is particularly appropriate -for newer machines without floppy drives. <command>BootX</command> is -not supported and must not be used on NewWorld PowerMacs. - -</para><para> - -<emphasis>Copy</emphasis> (not move) the following four files which -you downloaded earlier from the &debian; archives, onto the root level -of your hard drive (this can be accomplished by -<keycap>option</keycap>-dragging each file to the hard drive icon). - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> - -</para></listitem> -</itemizedlist> - -</para><para> - -Make a note of the partition number of the MacOS partition where you -place these files. If you have the MacOS <command>pdisk</command> -program, you can use the <command>L</command> command to check for the -partition number. You will need this partition number for the command -you type at the Open Firmware prompt when you boot the installer. - -</para><para> - -To boot the installer, proceed to <xref linkend="boot-newworld"/>. - -</para> - </sect2> - </sect1> diff --git a/nl/install-methods/boot-usb-files.xml b/nl/install-methods/boot-usb-files.xml deleted file mode 100644 index afffe991d..000000000 --- a/nl/install-methods/boot-usb-files.xml +++ /dev/null @@ -1,159 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 57590 untranslated --> - - <sect1 condition="bootable-usb" id="boot-usb-files"> - <title>Preparing Files for USB Memory Stick Booting</title> - -<para> - -There are two installation methods possible when booting from USB stick. -The first is to install completely from the network. The second is to -also copy a CD image onto the USB stick and use that as a source for -packages, possibly in combination with a mirror. This second method is -the more common. - -</para><para> - -For the first installation method you'll need to download an installer -image from the <filename>netboot</filename> directory (at the location -mentioned in <xref linkend="where-files"/>) and use the -<quote>flexible way</quote> explained below to copy the files to the USB -stick. - -</para><para> - -Installation images for the second installation method can be found in -the <filename>hd-media</filename> directory and either the <quote>easy -way</quote> or the <quote>flexible way</quote> can be used to copy the -image to the USB stick. For this installation method you will also need -to download a CD image. The installation image and the CD image must be -based on the same release of &d-i;. If they do not match you are likely -to get errors<footnote> - -<para> -The error message that is most likely to be displayed is that no kernel -modules can be found. This means that the version of the kernel module -udebs included on the CD image is different from the version of the -running kernel. -</para> - -</footnote> during the installation. - -</para><para> - -To prepare the USB stick, you will need a system where GNU/Linux is -already running and where USB is supported. With current GNU/Linux systems -the USB stick should be automatically recognized when you insert it. If -it is not you should check that the usb-storage kernel module is loaded. -When the USB stick is inserted, it will be mapped to a device named -<filename>/dev/sdX</filename>, where the <quote>X</quote> is a letter -in the range a-z. You should be able to see to which device the USB -stick was mapped by running the command <command>dmesg</command> after -inserting it. To write to your stick, you may have to turn off its write -protection switch. - -</para> -<warning><para> - -The procedures described in this section will destroy anything already -on the device! Make very sure that you use the correct device name for -your USB stick. If you use the wrong device the result could be that all -information on for example a hard disk could be lost. - -</para></warning> -<para> - -Note that the USB stick should be at least 256 MB in size (smaller -setups are possible if you follow <xref linkend="usb-copy-flexible"/>). - -</para> - - <sect2 id="usb-copy-easy"> - <title>Copying the files — the easy way</title> -<para> - -There is an all-in-one file <filename>hd-media/boot.img.gz</filename> -which contains all the installer files (including the kernel) -<phrase arch="x86">as well as <classname>syslinux</classname> and its -configuration file.</phrase> -<phrase arch="powerpc">as well as <classname>yaboot</classname> and its -configuration file.</phrase> - -</para><para> - -Note that, although convenient, this method does have one major -disadvantage: the logical size of the device will be limited to 256 MB, -even if the capacity of the USB stick is larger. You will need to -repartition the USB stick and create new file systems to get its full -capacity back if you ever want to use it for some different purpose. -A second disadvantage is that you cannot copy a full CD image onto -the USB stick, but only the smaller businesscard or netinst CD images. - -</para><para arch="x86"> - -To use this image simply extract it directly to your USB stick: - -<informalexample><screen> -# zcat boot.img.gz > /dev/<replaceable>sdX</replaceable> -</screen></informalexample> - -</para><para arch="powerpc"> - -Create a partition of type "Apple_Bootstrap" on your USB stick using -<command>mac-fdisk</command>'s <userinput>C</userinput> command and -extract the image directly to that: - -<informalexample><screen> -# zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable> -</screen></informalexample> - -</para><para> - -After that, mount the USB memory stick -<phrase arch="x86">(<userinput>mount -/dev/<replaceable>sdX</replaceable> /mnt</userinput>),</phrase> -<phrase arch="powerpc">(<userinput>mount -/dev/<replaceable>sdX2</replaceable> /mnt</userinput>),</phrase> -which will now have -<phrase arch="x86">a FAT filesystem</phrase> -<phrase arch="powerpc">an HFS filesystem</phrase> -on it, and copy a &debian; netinst or businesscard ISO image to it. -Unmount the stick (<userinput>umount /mnt</userinput>) and you are done. - -</para> - </sect2> - - <sect2 id="usb-copy-flexible"> - <title>Copying the files — the flexible way</title> -<para> - -If you like more flexibility or just want to know what's going on, you -should use the following method to put the files on your stick. One -advantage of using this method is that — if the capacity of your -USB stick is large enough — you have the option of copying a -full CD ISO image to it. - -</para> - -&usb-setup-x86.xml; -&usb-setup-powerpc.xml; - - </sect2> - - <!-- TODO: doesn't this section belong later? --> - <sect2 arch="x86"> - <title>Booting the USB stick</title> -<warning><para> - -If your system refuses to boot from the memory stick, the stick may -contain an invalid master boot record (MBR). To fix this, use the -<command>install-mbr</command> command from the package -<classname>mbr</classname>: - -<informalexample><screen> -# install-mbr /dev/<replaceable>sdX</replaceable> -</screen></informalexample> - -</para></warning> - </sect2> - </sect1> diff --git a/nl/install-methods/create-floppy.xml b/nl/install-methods/create-floppy.xml deleted file mode 100644 index 6722dcde4..000000000 --- a/nl/install-methods/create-floppy.xml +++ /dev/null @@ -1,108 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61133 untranslated --> - - <sect1 condition="supports-floppy-boot" id="create-floppy"> - <title>Creating Floppies from Disk Images</title> -<para> - -Bootable floppy disks are generally used as a last resort to boot the -installer on hardware that cannot boot from CD or by other means. - -</para><para arch="powerpc"> - -Booting the installer from floppy disk reportedly fails on Mac USB -floppy drives. - -</para><para> - -Disk images are files containing the complete contents of a floppy -disk in <emphasis>raw</emphasis> form. Disk images, such as -<filename>boot.img</filename>, cannot simply be copied to floppy -drives. A special program is used to write the image files to floppy -disk in <emphasis>raw</emphasis> mode. This is required because these -images are raw representations of the disk; it is required to do a -<emphasis>sector copy</emphasis> of the data from the file onto the -floppy. - -</para><para> - -There are different techniques for creating floppies from disk images. -This section describes how to create floppies from disk images on -different platforms. - -</para><para> - -Before you can create the floppies, you will first need to download them -from one of the &debian; mirrors, as explained in -<xref linkend="downloading-files"/>. <phrase arch="i386">If you already -have an installation CD-ROM or DVD, the floppy images may also be included -on the CD/DVD.</phrase> - -</para><para> - -No matter which method you use to create your floppies, you should -remember to flip the write-protect tab on the floppies once you have -written them, to ensure they are not damaged unintentionally. - -</para> - - <sect2><title>Writing Disk Images From a Linux or Unix System</title> -<para> - -To write the floppy disk image files to the floppy disks, you will -probably need root access to the system. Place a good, blank floppy -in the floppy drive. Next, use the command - -<informalexample><screen> -$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync -</screen></informalexample> - -where <replaceable>filename</replaceable> is one of the floppy disk image -files. -<filename>/dev/fd0</filename> is a commonly used name of the floppy -disk device, it may be different on your workstation<phrase arch="sparc"> -(on Solaris, it is <filename>/dev/fd/0</filename>)</phrase>. -The command may return to the -prompt before Unix has finished writing the floppy disk, so look for -the disk-in-use light on the floppy drive and be sure that the light -is out and the disk has stopped revolving before you remove it from -the drive. On some systems, you'll have to run a command to eject the -floppy from the drive <phrase arch="sparc"> (on Solaris, use -<command>eject</command>, see the manual page)</phrase>. - -</para><para> - -Some systems attempt to automatically mount a floppy disk when you -place it in the drive. You might have to disable this feature before -the workstation will allow you to write a floppy in <emphasis>raw -mode</emphasis>. Unfortunately, how to accomplish this will vary -based on your operating system. -<phrase arch="sparc"> -On Solaris, you can work around -volume management to get raw access to the floppy. First, make sure -that the floppy is auto-mounted (using <command>volcheck</command> or -the equivalent command in the file manager). Then use a -<command>dd</command> command of the form given above, just replace -<filename>/dev/fd0</filename> with -<filename>/vol/rdsk/<replaceable>floppy_name</replaceable></filename>, -where <replaceable>floppy_name</replaceable> is the name the floppy -disk was given when it was formatted (unnamed floppies default to the -name <filename>unnamed_floppy</filename>). On other systems, ask your -system administrator. -</phrase> - -</para><para arch="powerpc"> - -If writing a floppy on powerpc Linux, you will need to eject it. The -<command>eject</command> program handles this nicely; you might need -to install it. - -</para> - - </sect2> - -&floppy-i386.xml; <!-- can be used for other arches --> -&floppy-powerpc.xml; - - </sect1> - diff --git a/nl/install-methods/download/arm.xml b/nl/install-methods/download/arm.xml deleted file mode 100644 index d4f3650a3..000000000 --- a/nl/install-methods/download/arm.xml +++ /dev/null @@ -1,88 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61346 untranslated --> - - - <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 image can be uploaded -via the Linksys web frontend or with upslug2. This firmware image can be -obtained from &nslu2-firmware-img;. - -</para> - </sect3> - - - <sect3 arch="arm" id="n2100-install-files"> - <title>Thecus N2100 Installation Files</title> -<para> - -A firmware image is provided for the Thecus N2100 which will automatically -boot <classname>debian-installer</classname>. This image can be installed -using the Thecus firmware upgrade process. This firmware image can be -obtained from &n2100-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="glantank-install-files"> - <title>GLAN Tank Installation Files</title> -<para> - -The GLAN Tank requires a kernel and ramdisk on an ext2 partition on the -disk on which you intend to install &debian;. These images can be obtained -from &glantank-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="kuroboxpro-install-files"> - <title>Kurobox Pro Installation Files</title> -<para> - -The Kurobox Pro requires a kernel and ramdisk on an ext2 partition on the -disk on which you intend to install &debian;. These images can be obtained -from &kuroboxpro-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="mv2120-install-files"> - <title>HP mv2120 Installation Files</title> -<para> - -A firmware image is provided for the HP mv2120 which will automatically -boot <classname>debian-installer</classname>. This image can be installed -with uphpmvault on Linux and other systems and with the HP Media -Vault Firmware Recovery Utility on Windows. The firmware image can be -obtained from &mv2120-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="qnap-install-files"> - <title>QNAP Turbo Station Installation Files</title> -<para> - -The installation files for the QNAP Turbo Station consist of a kernel and -ramdisk as well as a script to write these images to flash. You can obtain -the installation files for QNAP TS-109 and TS-209 from -&qnap-orion-firmware-img; and for QNAP TS-110, TS-119, TS-210, TS-219, -TS-219P from &qnap-kirkwood-firmware-img;. - -</para> - </sect3> - - <sect3 arch="arm" id="marvell-install-files"> - <title>SheevaPlug and OpenRD Installation Files</title> -<para> - -The installation files for the Marvell SheevaPlug and OpenRD devices -consist of a kernel and initrd for U-Boot. You can obtain these files -from &kirkwood-marvell-firmware-img;. - -</para> - </sect3> - diff --git a/nl/install-methods/download/powerpc.xml b/nl/install-methods/download/powerpc.xml deleted file mode 100644 index d1dd228f9..000000000 --- a/nl/install-methods/download/powerpc.xml +++ /dev/null @@ -1,28 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - -<!-- commented out as it seems out of date and the links are broken - - <sect3 arch="powerpc" id="newworld-install-files"> - <title>NewWorld MacOS Installation Files </title> -<para> - -For floppy-less installation on NewWorld Macs, it may be most -convenient to obtain all the necessary files packaged into one Stuffit -archive from -<ulink url="&url-powerpc-of;"></ulink> (separate instructions are -included in the archive). Otherwise, obtain the normal installation -files listed above. Retrieve the files to an HFS (not HFS+) partition -on your system. You will also need the <filename>yaboot</filename> and -<filename>yaboot.conf</filename> files from the -<ulink url="&downloadable-file;new-powermac/">new-powermac</ulink> or -<ulink url="&downloadable-file;powermac/">powermac</ulink> archive folder. -However, the newest G4 PowerMacs, and those that work without MacOS 9, -need the newest version of <command>yaboot</command>; the one in the -archive will not work. Obtain the newest version from -<ulink url="http://penguinppc.org/projects/yaboot/"></ulink>. - -</para> - </sect3> - ---> diff --git a/nl/install-methods/downloading-files.xml b/nl/install-methods/downloading-files.xml deleted file mode 100644 index e799e7354..000000000 --- a/nl/install-methods/downloading-files.xml +++ /dev/null @@ -1,34 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61147 untranslated --> - - <sect1 id="downloading-files"> - <title>Downloading Files from &debian; Mirrors</title> - -<para> - -To find the nearest (and thus probably the fastest) mirror, see the -<ulink url="&url-debian-mirrors;">list of Debian mirrors</ulink>. - -</para><para> - -When downloading files from a &debian; mirror using FTP, be sure to download the -files in <emphasis>binary</emphasis> mode, not text or automatic mode. - -</para> - - <sect2 id="where-files"> - <title>Where to Find Installation Images</title> - -<para> -The installation images are located on each &debian; mirror in the directory -<ulink url="&url-debian-installer;images">debian/dists/&releasename;/main/installer-&architecture;/current/images/</ulink> -— the <ulink url="&url-debian-installer;images/MANIFEST">MANIFEST</ulink> -lists each image and its purpose. -</para> - -&download-arm.xml; -&download-powerpc.xml; - - </sect2> - - </sect1> diff --git a/nl/install-methods/floppy/i386.xml b/nl/install-methods/floppy/i386.xml deleted file mode 100644 index dba3753e2..000000000 --- a/nl/install-methods/floppy/i386.xml +++ /dev/null @@ -1,35 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 39870 untranslated --> - - -<!-- This is not set off for i386 only, because many people will have --> -<!-- access to a PC in order to make a floppy for other arches. --> - - <sect2><title>Writing Disk Images From DOS, Windows, or OS/2</title> - -<para> - -If you have access to an i386 or amd64 machine, you can use one of the -following programs to copy images to floppies. - -</para><para> - -The <command>rawrite1</command> and <command>rawrite2</command> programs -can be used under MS-DOS. To use these programs, first make sure that you -are booted into DOS. Trying to use these programs from within a DOS box in -Windows, or double-clicking on these programs from the Windows Explorer is -<emphasis>not</emphasis> expected to work. - -</para><para> - -The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, -ME, XP and probably later versions. To use it you will need to unpack -diskio.dll in the same directory. - -</para><para> - -These tools can be found on the Official &debian; CD-ROMs under the -<filename>/tools</filename> directory. - -</para> - </sect2> diff --git a/nl/install-methods/floppy/powerpc.xml b/nl/install-methods/floppy/powerpc.xml deleted file mode 100644 index ffaa8ab70..000000000 --- a/nl/install-methods/floppy/powerpc.xml +++ /dev/null @@ -1,122 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28997 untranslated --> - - - <sect2 arch="powerpc"><title>Writing Disk Images From MacOS</title> -<para> - -An AppleScript, <application>Make Debian Floppy</application>, is -available for burning floppies from the provided disk image files. It -can be downloaded from -<ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/debian-imac/MakeDebianFloppy.sit"></ulink>. To -use it, just unstuff it on your desktop, and then drag any floppy -image file to it. You must have Applescript installed and enabled in -your extensions manager. Disk Copy will ask you to confirm that you -wish to erase the floppy and proceed to write the file image to it. - -</para><para> - -You can also use the MacOS utility <command>Disk Copy</command> -directly, or the freeware utility <command>suntar</command>. The -<filename>root.bin</filename> file is an example of a floppy -image. Use one of the following methods to create a floppy from the -floppy image with these utilities. - -</para> - - <sect3> - <title>Writing Disk Images with <command>Disk Copy</command></title> -<para> - -If you are creating the floppy image from files which were originally -on the official &debian-gnu; CD, then the Type and Creator are already set -correctly. The following <command>Creator-Changer</command> steps are -only necessary if you downloaded the image files from a &debian; mirror. - -</para> -<orderedlist> -<listitem><para> - -Obtain -<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink> -and use it to open the <filename>root.bin</filename> file. - -</para></listitem> -<listitem><para> - -Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the -Type to <userinput>DDim</userinput> (binary floppy image). The case is -sensitive for these fields. - -</para></listitem> -<listitem><para> - -<emphasis>Important:</emphasis> In the Finder, use <userinput>Get -Info</userinput> to display the Finder information about the floppy -image, and <quote>X</quote> the <userinput>File Locked</userinput> check box so -that MacOS will be unable to remove the boot blocks if the image is -accidentally mounted. - -</para></listitem> - <listitem><para> - -Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it -will very likely be there already, otherwise try -<ulink url="&url-powerpc-diskcopy;"></ulink>. - -</para></listitem> -<listitem><para> - -Run <command>Disk Copy</command>, and select <menuchoice> -<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> -</menuchoice>, then select the -<emphasis>locked</emphasis> image file from the resulting dialog. It -will ask you to insert a floppy, then ask if you really want to erase -it. When done it should eject the floppy. - -</para></listitem> -</orderedlist> - - </sect3> - - <sect3> - <title>Writing Disk Images with <command>suntar</command></title> -<para> - -<orderedlist> -<listitem><para> - -Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;"> -</ulink>. Start the <command>suntar</command> program and select -<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> -menu. - -</para></listitem> -<listitem><para> - -Insert the floppy disk as requested, then hit &enterkey; (start at -sector 0). - -</para></listitem> -<listitem><para> - -Select the <filename>root.bin</filename> file in the file-opening dialog. - -</para></listitem> -<listitem><para> - -After the floppy has been created successfully, select <menuchoice> -<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. -If there are any errors writing the floppy, simply toss that floppy and -try another. - -</para></listitem> -</orderedlist> - -Before using the floppy you created, <emphasis>set the write protect -tab</emphasis>! Otherwise if you accidentally mount it in MacOS, -MacOS will helpfully ruin it. - -</para> - </sect3> - </sect2> diff --git a/nl/install-methods/install-methods.xml b/nl/install-methods/install-methods.xml deleted file mode 100644 index 0956b911b..000000000 --- a/nl/install-methods/install-methods.xml +++ /dev/null @@ -1,16 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 11648 untranslated --> - -<chapter id="install-methods"> - <title>Obtaining System Installation Media</title> - -&official-cdrom.xml; -&downloading-files.xml; -&ipl-tape.xml; -&create-floppy.xml; -&boot-usb-files.xml; -&boot-drive-files.xml; -&install-tftp.xml; -&automatic-install.xml; - -</chapter> diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml deleted file mode 100644 index 6c54a89c4..000000000 --- a/nl/install-methods/install-tftp.xml +++ /dev/null @@ -1,341 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62454 untranslated --> - - <sect1 condition="supports-tftp" id="install-tftp"> - <title>Preparing Files for TFTP Net Booting</title> -<para> - -If your machine is connected to a local area network, you may be able -to boot it over the network from another machine, using TFTP. If you -intend to boot the installation system from another machine, the -boot files will need to be placed in specific locations on that machine, -and the machine configured to support booting of your specific machine. - -</para><para> - -You need to set up a TFTP server, and for many machines a DHCP -server<phrase condition="supports-rarp">, or RARP -server</phrase><phrase condition="supports-bootp">, or BOOTP -server</phrase>. - -</para><para> - -<phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) is -one way to tell your client what IP address to use for itself. Another -way is to use the BOOTP protocol.</phrase> - -<phrase condition="supports-bootp">BOOTP is an IP protocol that -informs a computer of its IP address and where on the network to obtain -a boot image.</phrase> - -The DHCP (Dynamic Host Configuration Protocol) is a more flexible, -backwards-compatible extension of BOOTP. -Some systems can only be configured via DHCP. - -</para><para arch="powerpc"> - -For PowerPC, if you have a NewWorld Power Macintosh machine, it is a -good idea to use DHCP instead of BOOTP. Some of the latest machines -are unable to boot using BOOTP. - -</para><para arch="hppa"> - -Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. -There is an <classname>rbootd</classname> package available in &debian;. - -</para><para> - -The Trivial File Transfer Protocol (TFTP) is used to serve the boot -image to the client. Theoretically, any server, on any platform, -which implements these protocols, may be used. In the examples in -this section, we shall provide commands for SunOS 4.x, SunOS 5.x -(a.k.a. Solaris), and GNU/Linux. - -<note arch="x86"><para> - -For a &debian-gnu; server we recommend <classname>tftpd-hpa</classname>. -It's written by the same author as the <classname>syslinux</classname> -bootloader and is therefore least likely to cause issues. -A good alternative is <classname>atftpd</classname>. - -</para></note> - -</para> - -&tftp-rarp.xml; -&tftp-dhcp.xml; -&tftp-bootp.xml; - - <sect2 id="tftpd"> - <title>Enabling the TFTP Server</title> -<para> - -To get the TFTP server ready to go, you should first make sure that -<command>tftpd</command> is enabled. - -</para><para> - -In the case of <classname>tftpd-hpa</classname> there are two ways the -service can be run. It can be started on demand by the system's -<classname>inetd</classname> daemon, or it can be set up to run as an -independent daemon. Which of these methods is used is selected when the -package is installed and can be changed by reconfiguring the package. - -</para> -<note><para> - -Historically, TFTP servers used <filename>/tftpboot</filename> as directory -to serve images from. However, &debian-gnu; packages may use other directories -to comply with the <ulink url="&url-fhs-home;">Filesystem Hierarchy -Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default -uses <filename>/srv/tftp</filename>. You may have to adjust the -configuration examples in this section accordingly. - -</para></note> -<para> - -All <command>in.tftpd</command> alternatives available in &debian; should -log TFTP requests to the system logs by default. Some of them support a -<userinput>-v</userinput> argument to increase verbosity. -It is recommended to check these log messages in case of boot problems -as they are a good starting point for diagnosing the cause of errors. - -</para><para arch="mips"> - -If you intend to install &debian; on an SGI machine and your TFTP server is a -GNU/Linux box running Linux 2.4, you'll need to set the following on your -server: - -<informalexample><screen> -# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc -</screen></informalexample> - -to turn off Path MTU discovery, otherwise the SGI's PROM can't -download the kernel. Furthermore, make sure TFTP packets are sent from -a source port no greater than 32767, or the download will stall after -the first packet. Again, it's Linux 2.4.X tripping this bug in the -PROM, and you can avoid it by setting - -<informalexample><screen> -# echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range -</screen></informalexample> - -to adjust the range of source ports the Linux TFTP server uses. - -</para> - </sect2> - - <sect2 id="tftp-images"> - <title>Move TFTP Images Into Place</title> -<para> - -Next, place the TFTP boot image you need, as found in -<xref linkend="where-files"/>, in the <command>tftpd</command> -boot image directory. You may have to make a link from that -file to the file which <command>tftpd</command> will use for booting a -particular client. Unfortunately, the file name is determined by the -TFTP client, and there are no strong standards. - -</para><para arch="powerpc"> - -On NewWorld Power Macintosh machines, you will need to set up the -<command>yaboot</command> boot loader as the TFTP boot image. -<command>Yaboot</command> will then retrieve the kernel and RAMdisk -images via TFTP itself. You will need to download the following files -from the <filename>netboot/</filename> directory: - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot</filename> - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> - -</para></listitem> -<listitem><para> - -<filename>boot.msg</filename> - -</para></listitem> -</itemizedlist> - -</para><para arch="x86"> - -For PXE booting, everything you should need is set up in the -<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this -tarball into the <command>tftpd</command> boot image directory. Make sure -your dhcp server is configured to pass <filename>pxelinux.0</filename> -to <command>tftpd</command> as the filename to boot. - -</para><para arch="ia64"> - -For PXE booting, everything you should need is set up in the -<filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this -tarball into the <command>tftpd</command> boot image directory. Make sure -your dhcp server is configured to pass -<filename>/debian-installer/ia64/elilo.efi</filename> -to <command>tftpd</command> as the filename to boot. - -</para> - - <sect3 arch="sparc"> - <title>SPARC TFTP Booting</title> -<para> - -Some SPARC architectures add the subarchitecture names, such as -<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, -if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, -the filename would be <filename>C0A80103.SUN4C</filename>. However, -there are also subarchitectures where the file the client looks for is -just <filename>client-ip-in-hex</filename>. An easy way to determine the -hexadecimal code for the IP address is to enter the following command -in a shell (assuming the machine's intended IP is 10.0.0.4). - -<informalexample><screen> -$ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 -</screen></informalexample> - -To get to the correct filename, you will need to change all letters to -uppercase and if necessary append the subarchitecture name. - -</para><para> - -If you've done all this correctly, giving the command <userinput>boot -net</userinput> from the OpenPROM should load the image. If the image -cannot be found, try checking the logs on your tftp server to see which -image name is being requested. - -</para><para> - -You can also force some sparc systems to look for a specific file name -by adding it to the end of the OpenPROM boot command, such as -<userinput>boot net my-sparc.image</userinput>. This must still reside -in the directory that the TFTP server looks in. - -</para> - </sect3> - - <sect3 arch="mips"> - <title>SGI TFTP Booting</title> -<para> - -On SGI machines you can rely on the <command>bootpd</command> to supply -the name of the TFTP file. It is given either as the -<userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as -the <userinput>filename=</userinput> option in -<filename>/etc/dhcpd.conf</filename>. - -</para> - </sect3> - - </sect2> - -<!-- FIXME: commented out since it seems too old to be usable and a current - way is not known - - <sect2 id="tftp-low-memory"> - <title>TFTP Installation for Low-Memory Systems</title> -<para> - -On some systems, the standard installation RAMdisk, combined with the -memory requirements of the TFTP boot image, cannot fit in memory. In -this case, you can still install using TFTP, you'll just have to go -through the additional step of NFS mounting your root directory over -the network as well. This type of setup is also appropriate for -diskless or dataless clients. - -</para><para> - -First, follow all the steps above in <xref linkend="install-tftp"/>. - -<orderedlist> -<listitem><para> - -Copy the Linux kernel image on your TFTP server using the -<userinput>a.out</userinput> image for the architecture you are -booting. - -</para></listitem> -<listitem><para> - -Untar the root archive on your NFS server (can be the same system as -your TFTP server): - -<informalexample><screen> -# cd /tftpboot -# tar xvzf root.tar.gz -</screen></informalexample> - -Be sure to use the GNU <command>tar</command> (other tar programs, like the -SunOS one, badly handle devices as plain files). - -</para></listitem> -<listitem><para> - -Export your <filename>/tftpboot/debian-sparc-root</filename> directory -with root access to your client. E.g., add the following line to -<filename>/etc/exports</filename> (GNU/Linux syntax, should be similar -for SunOS): - -<informalexample><screen> -/tftpboot/debian-sparc-root <replaceable>client</replaceable>(rw,no_root_squash) -</screen></informalexample> - -NOTE: <replaceable>client</replaceable> is the host name or IP address recognized -by the server for the system you are booting. - -</para></listitem> -<listitem><para> - -Create a symbolic link from your client IP address in dotted notation -to <filename>debian-sparc-root</filename> in the -<filename>/tftpboot</filename> directory. For example, if the client -IP address is 192.168.1.3, do - -<informalexample><screen> -# ln -s debian-sparc-root 192.168.1.3 -</screen></informalexample> - -</para></listitem> -</orderedlist> - -</para> - - </sect2> - - <sect2 condition="supports-nfsroot"> - <title>Installing with TFTP and NFS Root</title> -<para> - -Installing with TFTP and NFS Root is similar to -<xref linkend="tftp-low-memory"/> because you don't want to -load the RAMdisk anymore but boot from the newly created NFS-root file -system. You then need to replace the symlink to the tftpboot image by -a symlink to the kernel image (for example, -<filename>linux-a.out</filename>). - -</para><para> - -RARP/TFTP requires all daemons to be running on the same server (the -workstation is sending a TFTP request back to the server that replied -to its previous RARP request). - -</para> - - - </sect2> -END FIXME --> - </sect1> diff --git a/nl/install-methods/ipl-tape.xml b/nl/install-methods/ipl-tape.xml deleted file mode 100644 index c99ac8b98..000000000 --- a/nl/install-methods/ipl-tape.xml +++ /dev/null @@ -1,24 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 36841 untranslated --> - - <sect1 arch="s390" id="ipl-tape"> - <title>Creating an IPL tape</title> - -<para> - -If you can't boot (IPL) from the CD-ROM and you are not using VM -you need to create an IPL tape first. This is described in section -3.4.3 in the -<ulink url="http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf"> -Linux for IBM eServer zSeries and S/390: Distributions</ulink> -Redbook. The files you -need to write to the tape are (in this order): -<filename>kernel.debian</filename>, -<filename>parmfile.debian</filename> and -<filename>initrd.debian</filename>. The files can be downloaded -from the <filename>tape</filename> sub-directory, see -<xref linkend="where-files"/>. - -</para> - </sect1> - diff --git a/nl/install-methods/official-cdrom.xml b/nl/install-methods/official-cdrom.xml deleted file mode 100644 index 0965582c3..000000000 --- a/nl/install-methods/official-cdrom.xml +++ /dev/null @@ -1,69 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 28672 untranslated --> - - <sect1 id="official-cdrom"> - <title>Official &debian-gnu; CD-ROM Sets</title> -<para> - -By far the easiest way to install &debian-gnu; is from an Official -&debian; CD-ROM Set. You can buy a set from a vendor (see the -<ulink url="&url-debian-cd-vendors;">CD vendors page</ulink>). -You may also download the CD-ROM images from a &debian; mirror and make -your own set, if you have a fast network connection and a CD burner -(see the <ulink url="&url-debian-cd;">Debian CD page</ulink> for -detailed instructions). If you have a &debian; CD set and CDs are -bootable on your machine, you can skip right to -<xref linkend="boot-installer"/>; much effort has been expended to ensure -the files most people need are there on the CD. Although a full set of -binary packages requires several CDs, it is unlikely you will need -packages on the third CD and above. You may also consider using the -DVD version, which saves a lot of space on your shelf and you avoid -the CD shuffling marathon. - -</para><para> - -If your machine doesn't support CD booting, but you do have a CD set, -you can use an alternative strategy such as - -<phrase condition="supports-floppy-boot">floppy disk,</phrase> - -<phrase arch="s390">tape, emulated tape,</phrase> - -<phrase condition="bootable-disk">hard disk,</phrase> - -<phrase condition="bootable-usb">usb stick,</phrase> - -<phrase condition="supports-tftp">net boot,</phrase> - -or manually loading the kernel from the CD to initially boot the -system installer. The files you need for booting by another means are -also on the CD; the &debian; network archive and CD folder organization -are identical. So when archive file paths are given below for -particular files you need for booting, look for those files in the -same directories and subdirectories on your CD. - -</para><para> - -Once the installer is booted, it will be able to obtain all the other -files it needs from the CD. - -</para><para> - -If you don't have a CD set, then you will need to download the -installer system files and place them on the - -<phrase arch="s390">installation tape</phrase> - -<phrase condition="supports-floppy-boot">floppy disk or</phrase> - -<phrase condition="bootable-disk">hard disk or</phrase> - -<phrase condition="bootable-usb">usb stick or</phrase> - -<phrase condition="supports-tftp">a connected computer</phrase> - -so they can be used to boot the installer. - -</para> - - </sect1> diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml deleted file mode 100644 index 86be45104..000000000 --- a/nl/install-methods/tftp/bootp.xml +++ /dev/null @@ -1,73 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59293 untranslated --> - - - <sect2 condition="supports-bootp" id="tftp-bootp"> - <title>Setting up a BOOTP server</title> -<para> - -There are two BOOTP servers available for GNU/Linux. The first is CMU -<command>bootpd</command>. The other is actually a DHCP server: ISC -<command>dhcpd</command>. In &debian-gnu; these are contained in the -<classname>bootp</classname> and <classname>dhcp3-server</classname> -packages respectively. - -</para><para> - -To use CMU <command>bootpd</command>, you must first uncomment (or -add) the relevant line in <filename>/etc/inetd.conf</filename>. On -&debian-gnu;, you can run <userinput>update-inetd --enable -bootps</userinput>, then <userinput>/etc/init.d/inetd -reload</userinput> to do so. Just in case your BOOTP server does not -run &debian;, the line in question should look like: - -<informalexample><screen> -bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120 -</screen></informalexample> - -Now, you must create an <filename>/etc/bootptab</filename> file. This -has the same sort of familiar and cryptic format as the good old BSD -<filename>printcap</filename>, <filename>termcap</filename>, and -<filename>disktab</filename> files. See the -<filename>bootptab</filename> manual page for more information. For -CMU <command>bootpd</command>, you will need to know the hardware -(MAC) address of the client. Here is an example -<filename>/etc/bootptab</filename>: - -<informalexample><screen> -client:\ - hd=/tftpboot:\ - bf=tftpboot.img:\ - ip=192.168.1.90:\ - sm=255.255.255.0:\ - sa=192.168.1.1:\ - ha=0123456789AB: -</screen></informalexample> - -You will need to change at least the <quote>ha</quote> option, which -specifies the hardware address of the client. The <quote>bf</quote> -option specifies the file a client should retrieve via TFTP; see -<xref linkend="tftp-images"/> for more details. - -<phrase arch="mips"> -On SGI machines you can just enter the command monitor and type -<userinput>printenv</userinput>. The value of the -<userinput>eaddr</userinput> variable is the machine's MAC address. -</phrase> - -</para><para> - -By contrast, setting up BOOTP with ISC <command>dhcpd</command> is -really easy, because it treats BOOTP clients as a moderately special -case of DHCP clients. Some architectures require a complex -configuration for booting clients via BOOTP. If yours is one of -those, read the section <xref linkend="dhcpd"/>. Otherwise you -will probably be able to get away with simply adding the -<userinput>allow bootp</userinput> directive to the configuration -block for the subnet containing the client in -<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart -<command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server -restart</userinput>. - -</para> - </sect2> diff --git a/nl/install-methods/tftp/dhcp.xml b/nl/install-methods/tftp/dhcp.xml deleted file mode 100644 index 6f1a89b81..000000000 --- a/nl/install-methods/tftp/dhcp.xml +++ /dev/null @@ -1,94 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62402 untranslated --> - - <sect2 id="dhcpd"> - <title>Setting up a DHCP server</title> -<para> - -One free software DHCP server is ISC <command>dhcpd</command>. -For &debian-gnu;, the <classname>dhcp3-server</classname> package is -recommended. Here is a sample configuration file for it (see -<filename>/etc/dhcp3/dhcpd.conf</filename>): - -<informalexample><screen> -option domain-name "example.com"; -option domain-name-servers ns1.example.com; -option subnet-mask 255.255.255.0; -default-lease-time 600; -max-lease-time 7200; -server-name "servername"; - -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option routers 192.168.1.1; -} - -host clientname { - filename "/tftpboot.img"; - server-name "servername"; - next-server servername; - hardware ethernet 01:23:45:67:89:AB; - fixed-address 192.168.1.90; -} -</screen></informalexample> - -</para><para> - -In this example, there is one server -<replaceable>servername</replaceable> which performs all of the work -of DHCP server, TFTP server, and network gateway. You will almost -certainly need to change the domain-name options, as well as the -server name and client hardware address. The -<replaceable>filename</replaceable> option should be the name of the -file which will be retrieved via TFTP. - -</para><para> - -After you have edited the <command>dhcpd</command> configuration file, -restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>. - -</para> - - <sect3 arch="x86"> - <title>Enabling PXE Booting in the DHCP configuration</title> -<para> -Here is another example for a <filename>dhcp.conf</filename> using the -Pre-boot Execution Environment (PXE) method of TFTP. - -<informalexample><screen> -option domain-name "example.com"; - -default-lease-time 600; -max-lease-time 7200; - -allow booting; -allow bootp; - -# The next paragraph needs to be modified to fit your case -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option broadcast-address 192.168.1.255; -# the gateway address which can be different -# (access to the internet for instance) - option routers 192.168.1.1; -# indicate the dns you want to use - option domain-name-servers 192.168.1.3; -} - -group { - next-server 192.168.1.3; - host tftpclient { -# tftp client hardware address - hardware ethernet 00:10:DC:27:6C:15; - filename "pxelinux.0"; - } -} -</screen></informalexample> - -Note that for PXE booting, the client filename <filename>pxelinux.0</filename> -is a boot loader, not a kernel image (see <xref linkend="tftp-images"/> -below). - -</para> - </sect3> - </sect2> diff --git a/nl/install-methods/tftp/rarp.xml b/nl/install-methods/tftp/rarp.xml deleted file mode 100644 index 47715f8db..000000000 --- a/nl/install-methods/tftp/rarp.xml +++ /dev/null @@ -1,32 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62401 untranslated --> - - <sect2 condition="supports-rarp" id="tftp-rarp"> - <title>Setting up RARP server</title> -<para> - -To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) -of the client computers to be installed. -If you don't know this information, you can - -<phrase arch="sparc"> pick it off the initial OpenPROM boot messages, use the -OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> - -boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the -command <userinput>ip addr show dev eth0</userinput>. - -</para><para> - -On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, -you use the <command>rarpd</command> program. -You need to ensure that the Ethernet hardware address for the client is -listed in the <quote>ethers</quote> database (either in the -<filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the -<quote>hosts</quote> database. Then you need to start the RARP daemon. -Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> -on most Linux systems and SunOS 5 (Solaris 2), -<userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, -or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1). - -</para> - </sect2> diff --git a/nl/install-methods/usb-setup/powerpc.xml b/nl/install-methods/usb-setup/powerpc.xml deleted file mode 100644 index 6eba27fb6..000000000 --- a/nl/install-methods/usb-setup/powerpc.xml +++ /dev/null @@ -1,119 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 56442 untranslated --> - - <sect3 arch="powerpc"> - <title>Partitioning the USB stick</title> -<para> - -Most USB sticks do not come pre-configured in such a way that Open -Firmware can boot from them, so you will need to repartition the stick. -On Mac systems, run -<userinput>mac-fdisk /dev/<replaceable>sdX</replaceable></userinput>, -initialise a new partition map using the <userinput>i</userinput> -command, and create a new partition of type Apple_Bootstrap using the -<userinput>C</userinput> command. (Note that the first "partition" will -always be the partition map itself.) Then type - -<informalexample><screen> -$ hformat /dev/<replaceable>sdX2</replaceable> -</screen></informalexample> - -Take care that you use the correct device name for your USB stick. The -<command>hformat</command> command is contained in the -<classname>hfsutils</classname> &debian; package. - -</para><para> - -In order to start the kernel after booting from the USB stick, we will -put a boot loader on the stick. The <command>yaboot</command> boot -loader can be installed on an HFS filesystem and can be reconfigured by -just editing a text file. Any operating system which supports the HFS -file system can be used to make changes to the configuration of the boot -loader. - -</para><para> - -The normal <command>ybin</command> tool that comes with -<command>yaboot</command> does not yet understand USB storage devices, -so you will have to install <command>yaboot</command> by hand using the -<classname>hfsutils</classname> tools. Type - -<informalexample><screen> -$ hmount /dev/<replaceable>sdX2</replaceable> -$ hcopy -r /usr/lib/yaboot/yaboot : -$ hattrib -c UNIX -t tbxi :yaboot -$ hattrib -b : -$ humount -</screen></informalexample> - -Again, take care that you use the correct device name. The partition -must not be otherwise mounted during this procedure. This procedure -writes the boot loader to the partition, and uses the HFS utilities to -mark it in such a way that Open Firmware will boot it. Having done this, -the rest of the USB stick may be prepared using the normal Unix -utilities. - -</para> - </sect3> - - <sect3 arch="powerpc"> - <title>Adding the installer image</title> -<para> - -Mount the partition -(<userinput>mount /dev/<replaceable>sdX2</replaceable> /mnt</userinput>) -and copy the following installer image files to the stick: - -<itemizedlist> -<listitem><para> - -<filename>vmlinux</filename> (kernel binary) - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> (initial ramdisk image) - -</para></listitem> -<listitem><para> - -<filename>yaboot.conf</filename> (yaboot configuration file) - -</para></listitem> -<listitem><para> - -<filename>boot.msg</filename> (optional boot message) - -</para></listitem> -</itemizedlist> - -</para><para> - -The <filename>yaboot.conf</filename> configuration file should -contain the following lines: - -<informalexample><screen> -default=install -root=/dev/ram - -message=/boot.msg - -image=/vmlinux - label=install - initrd=/initrd.gz - initrd-size=10000 - read-only -</screen></informalexample> - -Please note that the <userinput>initrd-size</userinput> parameter -may need to be increased, depending on the image you are booting. - -</para><para> - -If you used an <filename>hd-media</filename> image, you should now copy a -&debian; ISO image (businesscard, netinst or full CD image; be sure to select -one that fits) onto the stick. When you are done, unmount the USB memory -stick (<userinput>umount /mnt</userinput>). - -</para> - </sect3> diff --git a/nl/install-methods/usb-setup/x86.xml b/nl/install-methods/usb-setup/x86.xml deleted file mode 100644 index 36a96af21..000000000 --- a/nl/install-methods/usb-setup/x86.xml +++ /dev/null @@ -1,117 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 61286 untranslated --> - - <sect3 arch="x86"> - <title>Partitioning the USB stick</title> -<para> - -We will show how to set up the memory stick to use the first partition, -instead of the entire device. - -</para><note><para> - -Since most USB sticks come pre-configured with a single FAT16 -partition, you probably won't have to repartition or reformat the -stick. If you have to do that anyway, use <command>cfdisk</command> -or any other partitioning tool to create a FAT16 partition<footnote> - -<para> -Don't forget to set the <quote>bootable</quote> bootable flag. -</para> - -</footnote>, and then create the filesystem using: - -<informalexample><screen> -# mkdosfs /dev/<replaceable>sdX1</replaceable> -</screen></informalexample> - -Take care that you use the correct device name for your USB stick. The -<command>mkdosfs</command> command is contained in the -<classname>dosfstools</classname> &debian; package. - -</para></note><para> - -In order to start the kernel after booting from the USB stick, we will -put a boot loader on the stick. Although any boot loader -(e.g. <classname>lilo</classname>) should work, it's convenient to use -<classname>syslinux</classname>, since it uses a FAT16 partition and can -be reconfigured by just editing a text file. Any operating system -which supports the FAT file system can be used to make changes to the -configuration of the boot loader. - -</para><para> - -To put <classname>syslinux</classname> on the FAT16 partition on your USB -stick, install the <classname>syslinux</classname> and -<classname>mtools</classname> packages on your system, and do: - -<informalexample><screen> -# syslinux /dev/<replaceable>sdX1</replaceable> -</screen></informalexample> - -Again, take care that you use the correct device name. The partition -must not be mounted when starting <command>syslinux</command>. This -procedure writes a boot sector to the partition and creates the file -<filename>ldlinux.sys</filename> which contains the boot loader code. - -</para> - </sect3> - - <sect3 arch="x86"> - <title>Adding the installer image</title> -<para> - -Mount the partition -(<userinput>mount /dev/<replaceable>sdX1</replaceable> /mnt</userinput>) -and copy the following installer image files to the stick: - -<itemizedlist> -<listitem><para> - -<filename>vmlinuz</filename> or <filename>linux</filename> (kernel binary) - -</para></listitem> -<listitem><para> - -<filename>initrd.gz</filename> (initial ramdisk image) - -</para></listitem> -</itemizedlist> - -You can choose between either the regular version or the graphical version -of the installer. The latter can be found in the <filename>gtk</filename> -subdirectory. If you want to rename the files, please note that -<classname>syslinux</classname> can only process DOS (8.3) file names. - -</para><para> - -Next you should create a <filename>syslinux.cfg</filename> configuration -file, which at a bare minimum should contain the following two lines (change -the name of the kernel binary to <quote><filename>linux</filename></quote> -if you used a <filename>netboot</filename> image): - -<informalexample><screen> -default vmlinuz -append initrd=initrd.gz -</screen></informalexample> - -For the graphical installer you should add -<userinput>vga=788</userinput> to the second line. - -</para><para> - -If you used an <filename>hd-media</filename> image, you should now copy a -&debian; ISO image<footnote> - -<para> -You can use either a businesscard, a netinst or a full CD image (see -<xref linkend="official-cdrom"/>). Be sure to select one that fits. -Note that the <quote>netboot <filename>mini.iso</filename></quote> image is -not usable for this purpose. -</para> - -</footnote> onto the stick. When you are done, unmount the USB memory stick -(<userinput>umount /mnt</userinput>). - -</para> - </sect3> |