diff options
Diffstat (limited to 'en/install-methods')
| -rw-r--r-- | en/install-methods/boot-drive-files.xml | 100 | ||||
| -rw-r--r-- | en/install-methods/boot-usb-files.xml | 12 | ||||
| -rw-r--r-- | en/install-methods/install-tftp.xml | 201 | ||||
| -rw-r--r-- | en/install-methods/tftp/bootp.xml | 6 | ||||
| -rw-r--r-- | en/install-methods/tftp/rarp.xml | 3 | ||||
| -rw-r--r-- | en/install-methods/usb-setup/powerpc.xml | 2 |
6 files changed, 30 insertions, 294 deletions
diff --git a/en/install-methods/boot-drive-files.xml b/en/install-methods/boot-drive-files.xml index 1cf0274d9..59741e5a6 100644 --- a/en/install-methods/boot-drive-files.xml +++ b/en/install-methods/boot-drive-files.xml @@ -17,7 +17,10 @@ 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/DVD images. -</para><para arch="powerpc"> +</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 @@ -35,6 +38,7 @@ depending on whether the system is a <quote>NewWorld</quote> or an <quote>OldWorld</quote> model. </para> +--> <sect2 arch="x86" id="files-grub"> <title>Hard disk installer booting from Linux using @@ -124,98 +128,4 @@ Copy the following directories from a &debian; installation image to <filename>c </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/en/install-methods/boot-usb-files.xml b/en/install-methods/boot-usb-files.xml index 062aed26f..9815ac2eb 100644 --- a/en/install-methods/boot-usb-files.xml +++ b/en/install-methods/boot-usb-files.xml @@ -141,8 +141,6 @@ setups are possible using the files from netboot, following There is an all-in-one file &hdmedia-boot-img; 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><note><para> @@ -161,7 +159,10 @@ Simply extract this image directly to your USB stick: # zcat boot.img.gz > /dev/<replaceable>sdX</replaceable> </screen></informalexample> -</para><para arch="powerpc"> +</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 @@ -171,7 +172,10 @@ extract the image directly to that: # zcat boot.img.gz > /dev/<replaceable>sdX2</replaceable> </screen></informalexample> -</para><para> +</para> +--> + +<para> After that, mount the USB memory stick <phrase arch="x86">(<userinput>mount diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index 3094cf769..d37ee87d3 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -32,18 +32,19 @@ 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"> +</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><para> +<para> The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, @@ -100,28 +101,6 @@ log TFTP requests to the system logs by default. Some of them support a 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> @@ -136,7 +115,10 @@ 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"> +</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. @@ -172,7 +154,10 @@ from the <filename>netboot/</filename> directory: </para></listitem> </itemizedlist> -</para><para arch="x86"> +</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 @@ -182,162 +167,6 @@ to <command>tftpd</command> as the filename to boot. For UEFI machines, you will need to pass an appropriate EFI boot image name (such as <filename>/debian-installer/amd64/bootnetx64.efi</filename>). -</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/en/install-methods/tftp/bootp.xml b/en/install-methods/tftp/bootp.xml index 4e89b8622..678e1cb3a 100644 --- a/en/install-methods/tftp/bootp.xml +++ b/en/install-methods/tftp/bootp.xml @@ -49,12 +49,6 @@ 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 diff --git a/en/install-methods/tftp/rarp.xml b/en/install-methods/tftp/rarp.xml index 289d3a5c0..dc6b1f4d7 100644 --- a/en/install-methods/tftp/rarp.xml +++ b/en/install-methods/tftp/rarp.xml @@ -9,9 +9,6 @@ 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 and use the command <userinput>ip addr show dev eth0</userinput>. diff --git a/en/install-methods/usb-setup/powerpc.xml b/en/install-methods/usb-setup/powerpc.xml index 9e22dc6a7..078d37d2e 100644 --- a/en/install-methods/usb-setup/powerpc.xml +++ b/en/install-methods/usb-setup/powerpc.xml @@ -1,6 +1,7 @@ <!-- retain these comments for translator revision tracking --> <!-- $Id$ --> +<!-- <sect3 arch="powerpc"> <title>Partitioning the USB stick</title> <para> @@ -125,3 +126,4 @@ stick (<userinput>umount /mnt</userinput>). </para> </sect3> +-->
\ No newline at end of file |