222
222
#: install-methods.xml:320
224
msgid "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>"
228
#: install-methods.xml:328
224
230
msgid "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."
228
#: install-methods.xml:328
234
#: install-methods.xml:336
230
236
msgid "Writing Disk Images From a Linux or Unix System"
234
#: install-methods.xml:329
240
#: install-methods.xml:337
237
243
"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>\n"
238
244
"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; sync\n"
239
"</screen></informalexample> where <replaceable>filename</replaceable> is one of the floppy disk image files (see <xref linkend=\"downloading-files\"/> for what <replaceable>filename</replaceable> should be). <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>."
245
"</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>."
243
#: install-methods.xml:353
249
#: install-methods.xml:358
245
251
msgid "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>"
249
#: install-methods.xml:374
255
#: install-methods.xml:379
251
257
msgid "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."
255
#: install-methods.xml:392
261
#: install-methods.xml:397
257
263
msgid "Writing Disk Images From DOS, Windows, or OS/2"
261
#: install-methods.xml:394
263
msgid "If you have access to an i386 machine, you can use one of the following programs to copy images to floppies."
267
267
#: install-methods.xml:399
269
msgid "If you have access to an i386 or amd64 machine, you can use one of the following programs to copy images to floppies."
273
#: install-methods.xml:404
269
275
msgid "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."
273
#: install-methods.xml:407
279
#: install-methods.xml:412
275
281
msgid "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."
279
#: install-methods.xml:413
285
#: install-methods.xml:418
281
287
msgid "These tools can be found on the Official Debian CD-ROMs under the <filename>/tools</filename> directory."
285
#: install-methods.xml:426
291
#: install-methods.xml:431
287
293
msgid "Writing Disk Images on Atari Systems"
291
#: install-methods.xml:427
297
#: install-methods.xml:432
293
299
msgid "You'll find the &rawwrite.ttp; program in the same directory as the floppy disk images. Start the program by double clicking on the program icon, and type in the name of the floppy image file you want written to the floppy at the TOS program command line dialog box."
297
#: install-methods.xml:438
303
#: install-methods.xml:443
299
305
msgid "Writing Disk Images on Macintosh Systems"
303
#: install-methods.xml:439
309
#: install-methods.xml:444
305
msgid "There is no MacOS application to write images to floppy disks (and there would be no point in doing this as you can't use these floppies to boot the installation system or install kernel and modules from on Macintosh). However, these files are needed for the installation of the operating system and modules, later in the process."
311
msgid "Since the current release does not yet support booting from floppies to start the installation, there would be no point in doing this on Macintosh Systems. However, these files are needed for the installation of the operating system and modules, later in the process."
309
#: install-methods.xml:457
315
#: install-methods.xml:460
311
317
msgid "Writing Disk Images From MacOS"
315
#: install-methods.xml:458
321
#: install-methods.xml:461
317
323
msgid "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."
321
#: install-methods.xml:469
327
#: install-methods.xml:472
323
329
msgid "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."
327
#: install-methods.xml:480
333
#: install-methods.xml:483
329
335
msgid "Writing Disk Images with <command>Disk Copy</command>"
333
#: install-methods.xml:481
339
#: install-methods.xml:484
335
341
msgid "If you are creating the floppy image from files which were originally on the official &debian; CD, then the Type and Creator are already set correctly. The following <command>Creator-Changer</command> steps are only necessary if you downloaded the image files from a Debian mirror."
339
#: install-methods.xml:490
345
#: install-methods.xml:493
341
347
msgid "Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> and use it to open the <filename>root.bin</filename> file."
345
#: install-methods.xml:497
351
#: install-methods.xml:500
347
353
msgid "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."
351
#: install-methods.xml:504
357
#: install-methods.xml:507
353
359
msgid "<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."
357
#: install-methods.xml:513
363
#: install-methods.xml:516
359
365
msgid "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>."
363
#: install-methods.xml:520
369
#: install-methods.xml:523
365
371
msgid "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."
369
#: install-methods.xml:535
375
#: install-methods.xml:538
371
377
msgid "Writing Disk Images with <command>suntar</command>"
375
#: install-methods.xml:539
381
#: install-methods.xml:542
377
383
msgid "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."
381
#: install-methods.xml:547
387
#: install-methods.xml:550
383
389
msgid "Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)."
387
#: install-methods.xml:553
393
#: install-methods.xml:556
389
395
msgid "Select the <filename>root.bin</filename> file in the file-opening dialog."
393
#: install-methods.xml:558
399
#: install-methods.xml:561
395
401
msgid "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."
399
#: install-methods.xml:566
405
#: install-methods.xml:569
401
407
msgid "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."
405
#: install-methods.xml:585
411
#: install-methods.xml:588
407
413
msgid "Preparing Files for USB Memory Stick Booting"
411
#: install-methods.xml:587
417
#: install-methods.xml:590
413
419
msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. You should ensure that the usb-storage kernel module is loaded (<userinput>modprobe usb-storage</userinput>) and try to find out which SCSI device the USB stick has been mapped to (in this example <filename>/dev/sda</filename> is used). To write to your stick, you may have to turn off its write protection switch."
417
#: install-methods.xml:597
423
#: install-methods.xml:600
419
425
msgid "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\"/>)."
423
#: install-methods.xml:605
429
#: install-methods.xml:608
425
431
msgid "Copying the files — the easy way"
429
#: install-methods.xml:606
435
#: install-methods.xml:609
431
437
msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>SYSLINUX</command> and its configuration file. You only have to extract it directly to your USB stick:"
435
#: install-methods.xml:613
441
#: install-methods.xml:616
437
443
msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>"
441
#: install-methods.xml:615
447
#: install-methods.xml:618
443
449
msgid "There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which contains all the installer files (including the kernel) as well as <command>yaboot</command> and its configuration file. 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:"
447
#: install-methods.xml:624
453
#: install-methods.xml:627
449
455
msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>"
453
#: install-methods.xml:627
459
#: install-methods.xml:630
455
461
msgid "Using this method will destroy anything already on the device. Make sure that you use the correct device name for your USB stick."
459
#: install-methods.xml:633
465
#: install-methods.xml:636
461
msgid "After that, mount the USB memory stick (<userinput>mount <replaceable arch=\"i386\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</replaceable> /mnt</userinput>), which will now have <phrase arch=\"i386\">a FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> on it, and copy a Debian netinst or businesscard ISO image to it. Please note that the file name must end in <filename>.iso</filename>. Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
467
msgid "After that, mount the USB memory stick (<userinput>mount <replaceable arch=\"x86\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</replaceable> /mnt</userinput>), 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 (see <xref linkend=\"usb-add-iso\"/>). Unmount the stick (<userinput>umount /mnt</userinput>) and you are done."
465
#: install-methods.xml:649
471
#: install-methods.xml:652
467
473
msgid "Copying the files — the flexible way"
471
#: install-methods.xml:650
477
#: install-methods.xml:653
473
479
msgid "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."
477
#: install-methods.xml:662 install-methods.xml:754
483
#: install-methods.xml:665 install-methods.xml:754
479
485
msgid "USB stick partitioning on &arch-title;"
483
#: install-methods.xml:663
489
#: install-methods.xml:666
485
491
msgid "We will show how to setup the memory stick to use the first partition, instead of the entire device."
489
#: install-methods.xml:668
495
#: install-methods.xml:671
492
498
"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, and then create the filesystem using: <informalexample><screen>\n"
611
#: install-methods.xml:845
621
#: install-methods.xml:846
613
623
msgid "Adding an ISO image"
617
#: install-methods.xml:846
627
#: install-methods.xml:847
619
629
msgid "The installer will look for a Debian ISO image on the stick as its source for additional data needed for the installation. So your next step is to copy a Debian ISO image (businesscard, netinst or even a full CD image) onto your stick (be sure to select one that fits). The file name of the image must end in <filename>.iso</filename>."
623
#: install-methods.xml:854
633
#: install-methods.xml:855
625
635
msgid "If you want to install over the network, without using an ISO image, you will of course skip the previous step. Moreover you will have to use the initial ramdisk from the <filename>netboot</filename> directory instead of the one from <filename>hd-media</filename>, because <filename>hd-media/initrd.gz</filename> does not have network support."
629
#: install-methods.xml:863
639
#: install-methods.xml:864
631
641
msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch."
635
#: install-methods.xml:873
645
#: install-methods.xml:874
637
647
msgid "Booting the USB stick"
641
#: install-methods.xml:874
651
#: install-methods.xml:875
643
653
msgid "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>:"
647
#: install-methods.xml:881
657
#: install-methods.xml:882
649
659
msgid "# install-mbr /dev/<replaceable>sda</replaceable>"
653
#: install-methods.xml:892
663
#: install-methods.xml:893
655
665
msgid "Preparing Files for Hard Disk Booting"
659
#: install-methods.xml:893
669
#: install-methods.xml:894
661
671
msgid "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."
665
#: install-methods.xml:899
675
#: install-methods.xml:900
667
677
msgid "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."
671
#: install-methods.xml:906
681
#: install-methods.xml:907
673
683
msgid "The installer cannot boot from files on an NTFS file system."
677
#: install-methods.xml:910
687
#: install-methods.xml:911
679
689
msgid "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."
683
#: install-methods.xml:921
693
#: install-methods.xml:922
685
695
msgid "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."
689
#: install-methods.xml:930
699
#: install-methods.xml:931
691
701
msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
695
#: install-methods.xml:932
705
#: install-methods.xml:933
697
707
msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
701
#: install-methods.xml:938
711
#: install-methods.xml:939
703
713
msgid "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."
707
#: install-methods.xml:944
717
#: install-methods.xml:945
709
719
msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>."
713
#: install-methods.xml:951
723
#: install-methods.xml:952
715
725
msgid "<filename>vmlinuz</filename> (kernel binary)"
719
#: install-methods.xml:956
729
#: install-methods.xml:957
721
731
msgid "<filename>initrd.gz</filename> (ramdisk image)"
725
#: install-methods.xml:963
735
#: install-methods.xml:964
727
737
msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
731
#: install-methods.xml:973
741
#: install-methods.xml:974
733
743
msgid "Hard Disk Installer Booting for OldWorld Macs"
737
#: install-methods.xml:974
747
#: install-methods.xml:975
739
749
msgid "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."
743
#: install-methods.xml:987
753
#: install-methods.xml:988
745
755
msgid "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."
749
#: install-methods.xml:1007
759
#: install-methods.xml:1008
751
761
msgid "Hard Disk Installer Booting for NewWorld Macs"
755
#: install-methods.xml:1008
765
#: install-methods.xml:1009
757
767
msgid "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."
761
#: install-methods.xml:1019
771
#: install-methods.xml:1020
763
773
msgid "<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)."
767
#: install-methods.xml:1029
777
#: install-methods.xml:1030
773
#: install-methods.xml:1034
783
#: install-methods.xml:1035
775
785
msgid "initrd.gz"
779
#: install-methods.xml:1039
789
#: install-methods.xml:1040
785
#: install-methods.xml:1044
795
#: install-methods.xml:1045
787
797
msgid "yaboot.conf"
791
#: install-methods.xml:1049
801
#: install-methods.xml:1050
793
803
msgid "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."
797
#: install-methods.xml:1057
807
#: install-methods.xml:1058
799
809
msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
803
#: install-methods.xml:1070
813
#: install-methods.xml:1071
805
815
msgid "Preparing Files for TFTP Net Booting"
809
#: install-methods.xml:1071
819
#: install-methods.xml:1072
811
821
msgid "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."
815
#: install-methods.xml:1079
817
msgid "You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase condition=\"supports-dhcp\">, or DHCP server</phrase>."
821
#: install-methods.xml:1085
823
msgid "<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> <phrase arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM. </phrase> <phrase condition=\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. </phrase>"
827
#: install-methods.xml:1102
825
#: install-methods.xml:1080
827
msgid "You need to setup 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>."
831
#: install-methods.xml:1087
833
msgid "<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> <phrase arch=\"m68k\">Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP."
837
#: install-methods.xml:1104
829
839
msgid "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."
833
#: install-methods.xml:1108
843
#: install-methods.xml:1110
835
845
msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console."
839
#: install-methods.xml:1125
849
#: install-methods.xml:1127
841
851
msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian."
845
#: install-methods.xml:1130
855
#: install-methods.xml:1132
847
857
msgid "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."
851
#: install-methods.xml:1138
861
#: install-methods.xml:1140
853
863
msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>."
857
#: install-methods.xml:1156
867
#: install-methods.xml:1158
859
869
msgid "Setting up RARP server"
863
#: install-methods.xml:1157
865
msgid "To setup RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <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>/sbin/ifconfig eth0</userinput>."
869
#: install-methods.xml:1169
872
"On a RARP server system using a Linux 2.2.x kernel, you need to populate the kernel's RARP table. To do this, run the following commands: <informalexample><screen>\n"
873
"# <userinput>/sbin/rarp -s\n"
874
"<replaceable>client-hostname</replaceable>\n"
875
"<replaceable>client-enet-addr</replaceable></userinput>\n"
877
"# <userinput>/usr/sbin/arp -s\n"
878
"<replaceable>client-ip</replaceable>\n"
879
"<replaceable>client-enet-addr</replaceable></userinput>\n"
880
"</screen></informalexample> If you get <informalexample><screen>\n"
881
"SIOCSRARP: Invalid argument\n"
882
"</screen></informalexample> you probably need to load the RARP kernel module or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</userinput> and then try the <command>rarp</command> command again."
886
#: install-methods.xml:1185
888
msgid "On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, and you should instead use the <command>rarpd</command> program. The procedure is similar to that used under SunOS in the following paragraph."
873
#: install-methods.xml:1159
875
msgid "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>/sbin/ifconfig eth0</userinput>."
879
#: install-methods.xml:1171
881
msgid "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)."
892
885
#: install-methods.xml:1193
894
msgid "Under SunOS, 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. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>."
898
#: install-methods.xml:1212
900
msgid "Setting up BOOTP server"
904
#: install-methods.xml:1213
906
msgid "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; these are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages respectively."
910
#: install-methods.xml:1221
887
msgid "Setting up a BOOTP server"
891
#: install-methods.xml:1194
893
msgid "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; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively."
897
#: install-methods.xml:1202
913
900
"To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, 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>\n"
1051
#: install-methods.xml:1371
1048
#: install-methods.xml:1364
1053
1050
msgid "Move TFTP Images Into Place"
1057
#: install-methods.xml:1372
1054
#: install-methods.xml:1365
1059
msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll 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."
1056
msgid "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."
1063
#: install-methods.xml:1382
1060
#: install-methods.xml:1374
1065
1062
msgid "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. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory."
1066
#: install-methods.xml:1383
1068
msgid "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."
1069
1072
#: install-methods.xml:1391
1071
msgid "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."
1075
#: install-methods.xml:1399
1077
1074
msgid "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."
1081
#: install-methods.xml:1411
1078
#: install-methods.xml:1403
1083
1080
msgid "DECstation TFTP Images"
1087
#: install-methods.xml:1412
1084
#: install-methods.xml:1404
1089
1086
msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above."
1093
#: install-methods.xml:1422
1090
#: install-methods.xml:1414
1095
1092
msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:"
1098
1095
#. Tag: userinput
1099
#: install-methods.xml:1434
1096
#: install-methods.xml:1426
1101
1098
msgid "boot #/tftp/filename param1=value1 param2=value2 ..."
1105
#: install-methods.xml:1436
1102
#: install-methods.xml:1428
1107
1104
msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>."
1111
#: install-methods.xml:1474
1108
#: install-methods.xml:1466
1113
1110
msgid "Alpha TFTP Booting"
1117
#: install-methods.xml:1475
1114
#: install-methods.xml:1467
1119
1116
msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods."
1123
#: install-methods.xml:1490
1120
#: install-methods.xml:1482
1125
1122
msgid "SPARC TFTP Booting"
1129
#: install-methods.xml:1491
1126
#: install-methods.xml:1483
1132
1129
"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>\n"
1138
#: install-methods.xml:1507
1135
#: install-methods.xml:1499
1137
msgid "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."
1141
#: install-methods.xml:1506
1140
1143
msgid "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."
1147
#: install-methods.xml:1517
1149
msgid "BVM/Motorola TFTP Booting"
1144
1153
#: install-methods.xml:1518
1146
msgid "BVM/Motorola TFTP Booting"
1150
#: install-methods.xml:1519
1152
1155
msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>."
1156
#: install-methods.xml:1524
1159
#: install-methods.xml:1523
1158
1161
msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information."
1165
#: install-methods.xml:1535
1167
msgid "SGI TFTP Booting"
1162
1171
#: install-methods.xml:1536
1164
msgid "SGI TFTP Booting"
1168
#: install-methods.xml:1537
1170
1173
msgid "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>."
1177
#: install-methods.xml:1548
1179
msgid "Broadcom BCM91250A and BCM91480B TFTP Booting"
1174
1183
#: install-methods.xml:1549
1176
msgid "Broadcom BCM91250A and BCM91480B TFTP Booting"
1180
#: install-methods.xml:1550
1182
1185
msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE."
1189
#: install-methods.xml:1654
1191
msgid "Automatic Installation"
1186
1195
#: install-methods.xml:1655
1188
msgid "Automatic Installation"
1192
#: install-methods.xml:1656
1194
1197
msgid "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."
1201
#: install-methods.xml:1668
1203
msgid "Automatic Installation Using the Debian Installer"
1198
1207
#: install-methods.xml:1669
1200
msgid "Automatic Installation Using the Debian Installer"
1204
#: install-methods.xml:1670
1206
1209
msgid "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."
1210
#: install-methods.xml:1677
1213
#: install-methods.xml:1676
1212
1215
msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>."
added
removed
po/pot/install-methods.pot
