/[d-i]/trunk/installer/doc/manual/po/pot/install-methods.pot
ViewVC logotype

Diff of /trunk/installer/doc/manual/po/pot/install-methods.pot

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 26484 by fjpop-guest, Tue Mar 29 17:24:28 2005 UTC revision 27563 by fjpop-guest, Sat May 14 11:27:40 2005 UTC
# Line 449  msgstr "" Line 449  msgstr ""
449  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."  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."
450  msgstr ""  msgstr ""
451    
452  #: install-methods.xml:645 install-methods.xml:739  #: install-methods.xml:645 install-methods.xml:741
453  #, no-c-format  #, no-c-format
454  #. Tag: title  #. Tag: title
455  msgid "USB stick partitioning on &arch-title;"  msgid "USB stick partitioning on &arch-title;"
# Line 498  msgid "" Line 498  msgid ""
498        "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines: <informalexample><screen>\n"        "The <filename>syslinux.cfg</filename> configuration file should contain the following two lines: <informalexample><screen>\n"
499        "default vmlinuz\n"        "default vmlinuz\n"
500        "append initrd=initrd.gz ramdisk_size=12000 root=/dev/rd/0 init=/linuxrc rw\n"        "append initrd=initrd.gz ramdisk_size=12000 root=/dev/rd/0 init=/linuxrc rw\n"
501        "</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting. If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>append</quote> line."        "</screen></informalexample> Please note that the <userinput>ramdisk_size</userinput> parameter may need to be increased, depending on the image you are booting. <phrase condition=\"sarge\"> If the boot fails, you can try adding <userinput>devfs=mount,dall</userinput> to the <quote>append</quote> line. </phrase>"
502  msgstr ""  msgstr ""
503    
504  #: install-methods.xml:740  #: install-methods.xml:742
505  #, no-c-format  #, no-c-format
506  #. Tag: para  #. Tag: para
507  msgid ""  msgid ""
# Line 510  msgid "" Line 510  msgid ""
510        "</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."        "</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."
511  msgstr ""  msgstr ""
512    
513  #: install-methods.xml:756  #: install-methods.xml:758
514  #, no-c-format  #, no-c-format
515  #. Tag: para  #. Tag: para
516  msgid "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."  msgid "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."
517  msgstr ""  msgstr ""
518    
519  #: install-methods.xml:765  #: install-methods.xml:767
520  #, no-c-format  #, no-c-format
521  #. Tag: para  #. Tag: para
522  msgid ""  msgid ""
# Line 529  msgid "" Line 529  msgid ""
529        "</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."        "</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."
530  msgstr ""  msgstr ""
531    
532  #: install-methods.xml:781  #: install-methods.xml:783
533  #, no-c-format  #, no-c-format
534  #. Tag: para  #. Tag: para
535  msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:"  msgid "Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy the following files from the Debian archives to the stick:"
536  msgstr ""  msgstr ""
537    
538  #: install-methods.xml:787  #: install-methods.xml:789
539  #, no-c-format  #, no-c-format
540  #. Tag: para  #. Tag: para
541  msgid "<filename>vmlinux</filename> (kernel binary)"  msgid "<filename>vmlinux</filename> (kernel binary)"
542  msgstr ""  msgstr ""
543    
544  #: install-methods.xml:792  #: install-methods.xml:794
545  #, no-c-format  #, no-c-format
546  #. Tag: para  #. Tag: para
547  msgid "<filename>initrd.gz</filename> (initial ramdisk image)"  msgid "<filename>initrd.gz</filename> (initial ramdisk image)"
548  msgstr ""  msgstr ""
549    
550  #: install-methods.xml:797  #: install-methods.xml:799
551  #, no-c-format  #, no-c-format
552  #. Tag: para  #. Tag: para
553  msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"  msgid "<filename>yaboot.conf</filename> (yaboot configuration file)"
554  msgstr ""  msgstr ""
555    
556  #: install-methods.xml:802  #: install-methods.xml:804
557  #, no-c-format  #, no-c-format
558  #. Tag: para  #. Tag: para
559  msgid "<filename>boot.msg</filename> (optional boot message)"  msgid "<filename>boot.msg</filename> (optional boot message)"
560  msgstr ""  msgstr ""
561    
562  #: install-methods.xml:807  #: install-methods.xml:809
563  #, no-c-format  #, no-c-format
564  #. Tag: para  #. Tag: para
565  msgid "Optional kernel modules"  msgid "Optional kernel modules"
566  msgstr ""  msgstr ""
567    
568  #: install-methods.xml:814  #: install-methods.xml:816
569  #, no-c-format  #, no-c-format
570  #. Tag: para  #. Tag: para
571  msgid ""  msgid ""
# Line 578  msgid "" Line 578  msgid ""
578        "image=/vmlinux\n"        "image=/vmlinux\n"
579        "        label=install\n"        "        label=install\n"
580        "        initrd=/initrd.gz\n"        "        initrd=/initrd.gz\n"
581        "        initrd-size=10000\n"        "        initrd-size=10000<phrase condition=\"sarge\">\n"
582        "        append=\"devfs=mount,dall --\"\n"        "        append=\"devfs=mount,dall --\"</phrase>\n"
583        "        read-only\n"        "        read-only\n"
584        "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."        "</screen></informalexample> Please note that the <userinput>initrd-size</userinput> parameter may need to be increased, depending on the image you are booting."
585  msgstr ""  msgstr ""
586    
587  #: install-methods.xml:829  #: install-methods.xml:831
588  #, no-c-format  #, no-c-format
589  #. Tag: title  #. Tag: title
590  msgid "Adding an ISO image"  msgid "Adding an ISO image"
591  msgstr ""  msgstr ""
592    
593  #: install-methods.xml:830  #: install-methods.xml:832
594  #, no-c-format  #, no-c-format
595  #. Tag: para  #. Tag: para
596  msgid "Now you should put any Debian ISO image (businesscard, netinst or even a full one) onto your stick (if it fits). The file name of such an image must end in <filename>.iso</filename>."  msgid "Now you should put any Debian ISO image (businesscard, netinst or even a full one) onto your stick (if it fits). The file name of such an image must end in <filename>.iso</filename>."
597  msgstr ""  msgstr ""
598    
599  #: install-methods.xml:836  #: install-methods.xml:838
600  #, no-c-format  #, no-c-format
601  #. Tag: para  #. Tag: para
602  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."  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."
603  msgstr ""  msgstr ""
604    
605  #: install-methods.xml:845  #: install-methods.xml:847
606  #, no-c-format  #, no-c-format
607  #. Tag: para  #. Tag: para
608  msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch."  msgid "When you are done, unmount the USB memory stick (<userinput>umount /mnt</userinput>) and activate its write protection switch."
609  msgstr ""  msgstr ""
610    
611  #: install-methods.xml:855  #: install-methods.xml:857
612  #, no-c-format  #, no-c-format
613  #. Tag: title  #. Tag: title
614  msgid "Booting the USB stick"  msgid "Booting the USB stick"
615  msgstr ""  msgstr ""
616    
617  #: install-methods.xml:856  #: install-methods.xml:858
618  #, no-c-format  #, no-c-format
619  #. Tag: para  #. Tag: para
620  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>:"  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>:"
621  msgstr ""  msgstr ""
622    
623  #: install-methods.xml:863  #: install-methods.xml:865
624  #, no-c-format  #, no-c-format
625  #. Tag: screen  #. Tag: screen
626  msgid "# install-mbr /dev/<replaceable>sda</replaceable>"  msgid "# install-mbr /dev/<replaceable>sda</replaceable>"
627  msgstr ""  msgstr ""
628    
629  #: install-methods.xml:875  #: install-methods.xml:877
630  #, no-c-format  #, no-c-format
631  #. Tag: title  #. Tag: title
632  msgid "Preparing Files for Hard Disk Booting"  msgid "Preparing Files for Hard Disk Booting"
633  msgstr ""  msgstr ""
634    
635  #: install-methods.xml:876  #: install-methods.xml:878
636  #, no-c-format  #, no-c-format
637  #. Tag: para  #. Tag: para
638  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."  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."
639  msgstr ""  msgstr ""
640    
641  #: install-methods.xml:882  #: install-methods.xml:884
642  #, no-c-format  #, no-c-format
643  #. Tag: para  #. Tag: para
644  msgid "A full, \"pure network\" installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."  msgid "A full, \"pure network\" installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks."
645  msgstr ""  msgstr ""
646    
647  #: install-methods.xml:889  #: install-methods.xml:891
648  #, no-c-format  #, no-c-format
649  #. Tag: para  #. Tag: para
650  msgid "The installer cannot boot from files on an NTFS file system."  msgid "The installer cannot boot from files on an NTFS file system."
651  msgstr ""  msgstr ""
652    
653  #: install-methods.xml:893  #: install-methods.xml:895
654  #, no-c-format  #, no-c-format
655  #. Tag: para  #. Tag: para
656  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."  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."
657  msgstr ""  msgstr ""
658    
659  #: install-methods.xml:904  #: install-methods.xml:906
660  #, no-c-format  #, no-c-format
661  #. Tag: para  #. Tag: para
662  msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a ``NewWorld'' or an ``OldWorld'' model."  msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a ``NewWorld'' or an ``OldWorld'' model."
663  msgstr ""  msgstr ""
664    
665  #: install-methods.xml:913  #: install-methods.xml:915
666  #, no-c-format  #, no-c-format
667  #. Tag: title  #. Tag: title
668  msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"  msgid "Hard disk installer booting using <command>LILO</command> or <command>GRUB</command>"
669  msgstr ""  msgstr ""
670    
671  #: install-methods.xml:915  #: install-methods.xml:917
672  #, no-c-format  #, no-c-format
673  #. Tag: para  #. Tag: para
674  msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."  msgid "This section explains how to add to or even replace an existing linux installation using either <command>LILO</command> or <command>GRUB</command>."
675  msgstr ""  msgstr ""
676    
677  #: install-methods.xml:921  #: install-methods.xml:923
678  #, no-c-format  #, no-c-format
679  #. Tag: para  #. Tag: para
680  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."  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."
681  msgstr ""  msgstr ""
682    
683  #: install-methods.xml:927  #: install-methods.xml:929
684  #, no-c-format  #, no-c-format
685  #. Tag: para  #. Tag: para
686  msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>."  msgid "Copy the following files from the Debian archives to a convenient location on your hard drive, for instance to <filename>/boot/newinstall/</filename>."
687  msgstr ""  msgstr ""
688    
689  #: install-methods.xml:934  #: install-methods.xml:936
690  #, no-c-format  #, no-c-format
691  #. Tag: para  #. Tag: para
692  msgid "<filename>vmlinuz</filename> (kernel binary)"  msgid "<filename>vmlinuz</filename> (kernel binary)"
693  msgstr ""  msgstr ""
694    
695  #: install-methods.xml:939  #: install-methods.xml:941
696  #, no-c-format  #, no-c-format
697  #. Tag: para  #. Tag: para
698  msgid "<filename>initrd.gz</filename> (ramdisk image)"  msgid "<filename>initrd.gz</filename> (ramdisk image)"
699  msgstr ""  msgstr ""
700    
701  #: install-methods.xml:946  #: install-methods.xml:948
702  #, no-c-format  #, no-c-format
703  #. Tag: para  #. Tag: para
704  msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."  msgid "Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd\"/>."
705  msgstr ""  msgstr ""
706    
707  #: install-methods.xml:956  #: install-methods.xml:958
708  #, no-c-format  #, no-c-format
709  #. Tag: title  #. Tag: title
710  msgid "Hard Disk Installer Booting for OldWorld Macs"  msgid "Hard Disk Installer Booting for OldWorld Macs"
711  msgstr ""  msgstr ""
712    
713  #: install-methods.xml:957  #: install-methods.xml:959
714  #, no-c-format  #, no-c-format
715  #. Tag: para  #. Tag: para
716  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."  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."
717  msgstr ""  msgstr ""
718    
719  #: install-methods.xml:970  #: install-methods.xml:972
720  #, no-c-format  #, no-c-format
721  #. Tag: para  #. Tag: para
722  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."  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."
723  msgstr ""  msgstr ""
724    
725  #: install-methods.xml:990  #: install-methods.xml:992
726  #, no-c-format  #, no-c-format
727  #. Tag: title  #. Tag: title
728  msgid "Hard Disk Installer Booting for NewWorld Macs"  msgid "Hard Disk Installer Booting for NewWorld Macs"
729  msgstr ""  msgstr ""
730    
731  #: install-methods.xml:991  #: install-methods.xml:993
732  #, no-c-format  #, no-c-format
733  #. Tag: para  #. Tag: para
734  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."  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."
735  msgstr ""  msgstr ""
736    
737  #: install-methods.xml:1002  #: install-methods.xml:1004
738  #, no-c-format  #, no-c-format
739  #. Tag: para  #. Tag: para
740  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)."  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)."
741  msgstr ""  msgstr ""
742    
743  #: install-methods.xml:1012  #: install-methods.xml:1014
744  #, no-c-format  #, no-c-format
745  #. Tag: filename  #. Tag: filename
746  msgid "vmlinux"  msgid "vmlinux"
747  msgstr ""  msgstr ""
748    
749  #: install-methods.xml:1017  #: install-methods.xml:1019
750  #, no-c-format  #, no-c-format
751  #. Tag: filename  #. Tag: filename
752  msgid "initrd.gz"  msgid "initrd.gz"
753  msgstr ""  msgstr ""
754    
755  #: install-methods.xml:1022  #: install-methods.xml:1024
756  #, no-c-format  #, no-c-format
757  #. Tag: filename  #. Tag: filename
758  msgid "yaboot"  msgid "yaboot"
759  msgstr ""  msgstr ""
760    
761  #: install-methods.xml:1027  #: install-methods.xml:1029
762  #, no-c-format  #, no-c-format
763  #. Tag: filename  #. Tag: filename
764  msgid "yaboot.conf"  msgid "yaboot.conf"
765  msgstr ""  msgstr ""
766    
767  #: install-methods.xml:1032  #: install-methods.xml:1034
768  #, no-c-format  #, no-c-format
769  #. Tag: para  #. Tag: para
770  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 L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."  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 L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer."
771  msgstr ""  msgstr ""
772    
773  #: install-methods.xml:1040  #: install-methods.xml:1042
774  #, no-c-format  #, no-c-format
775  #. Tag: para  #. Tag: para
776  msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."  msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>."
777  msgstr ""  msgstr ""
778    
779  #: install-methods.xml:1053  #: install-methods.xml:1055
780  #, no-c-format  #, no-c-format
781  #. Tag: title  #. Tag: title
782  msgid "Preparing Files for TFTP Net Booting"  msgid "Preparing Files for TFTP Net Booting"
783  msgstr ""  msgstr ""
784    
785  #: install-methods.xml:1054  #: install-methods.xml:1056
786  #, no-c-format  #, no-c-format
787  #. Tag: para  #. Tag: para
788  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."  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."
789  msgstr ""  msgstr ""
790    
791  #: install-methods.xml:1062  #: install-methods.xml:1064
792  #, no-c-format  #, no-c-format
793  #. Tag: para  #. Tag: para
794  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>."  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>."
795  msgstr ""  msgstr ""
796    
797  #: install-methods.xml:1068  #: install-methods.xml:1070
798  #, no-c-format  #, no-c-format
799  #. Tag: para  #. Tag: para
800  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>"  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>"
801  msgstr ""  msgstr ""
802    
803  #: install-methods.xml:1085  #: install-methods.xml:1087
804  #, no-c-format  #, no-c-format
805  #. Tag: para  #. Tag: para
806  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."  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."
807  msgstr ""  msgstr ""
808    
809  #: install-methods.xml:1091  #: install-methods.xml:1093
810  #, no-c-format  #, no-c-format
811  #. Tag: para  #. Tag: para
812  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. You can also enter the IP configuration for network interfaces directly in the SRM console."  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. You can also enter the IP configuration for network interfaces directly in the SRM console."
813  msgstr ""  msgstr ""
814    
815  #: install-methods.xml:1100  #: install-methods.xml:1102
816  #, no-c-format  #, no-c-format
817  #. Tag: para  #. Tag: para
818  msgid "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."  msgid "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."
819  msgstr ""  msgstr ""
820    
821  #: install-methods.xml:1108  #: install-methods.xml:1110
822  #, no-c-format  #, no-c-format
823  #. Tag: para  #. Tag: para
824  msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. An RBOOTD package is available on the parisc-linux web site."  msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. An RBOOTD package is available on the parisc-linux web site."
825  msgstr ""  msgstr ""
826    
827  #: install-methods.xml:1113  #: install-methods.xml:1115
828  #, no-c-format  #, no-c-format
829  #. Tag: para  #. Tag: para
830  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."  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."
831  msgstr ""  msgstr ""
832    
833  #: install-methods.xml:1121  #: install-methods.xml:1123
834  #, no-c-format  #, no-c-format
835  #. Tag: para  #. Tag: para
836  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>."  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>."
837  msgstr ""  msgstr ""
838    
839  #: install-methods.xml:1139  #: install-methods.xml:1141
840  #, no-c-format  #, no-c-format
841  #. Tag: title  #. Tag: title
842  msgid "Setting up RARP server"  msgid "Setting up RARP server"
843  msgstr ""  msgstr ""
844    
845  #: install-methods.xml:1140  #: install-methods.xml:1142
846  #, no-c-format  #, no-c-format
847  #. Tag: para  #. Tag: para
848  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 ``Rescue'' mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>."  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 ``Rescue'' mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>."
849  msgstr ""  msgstr ""
850    
851  #: install-methods.xml:1152  #: install-methods.xml:1154
852  #, no-c-format  #, no-c-format
853  #. Tag: para  #. Tag: para
854  msgid ""  msgid ""
# Line 865  msgid "" Line 865  msgid ""
865        "</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."        "</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."
866  msgstr ""  msgstr ""
867    
868  #: install-methods.xml:1168  #: install-methods.xml:1170
869  #, no-c-format  #, no-c-format
870  #. Tag: para  #. Tag: para
871  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."  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."
872  msgstr ""  msgstr ""
873    
874  #: install-methods.xml:1176  #: install-methods.xml:1178
875  #, no-c-format  #, no-c-format
876  #. Tag: para  #. Tag: para
877  msgid "Under SunOS, you need to ensure that the Ethernet hardware address for the client is listed in the ``ethers'' database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the ``hosts'' database. Then you need to start the RARP daemon. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>."  msgid "Under SunOS, you need to ensure that the Ethernet hardware address for the client is listed in the ``ethers'' database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the ``hosts'' database. Then you need to start the RARP daemon. In SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>."
878  msgstr ""  msgstr ""
879    
880  #: install-methods.xml:1195  #: install-methods.xml:1197
881  #, no-c-format  #, no-c-format
882  #. Tag: title  #. Tag: title
883  msgid "Setting up BOOTP server"  msgid "Setting up BOOTP server"
884  msgstr ""  msgstr ""
885    
886  #: install-methods.xml:1196  #: install-methods.xml:1198
887  #, no-c-format  #, no-c-format
888  #. Tag: para  #. Tag: para
889  msgid "There are two BOOTP servers available for GNU/Linux, the CMU <command>bootpd</command> and the other is actually a DHCP server, ISC <command>dhcpd</command>, which are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages in &debian;."  msgid "There are two BOOTP servers available for GNU/Linux, the CMU <command>bootpd</command> and the other is actually a DHCP server, ISC <command>dhcpd</command>, which are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages in &debian;."
890  msgstr ""  msgstr ""
891    
892  #: install-methods.xml:1204  #: install-methods.xml:1206
893  #, no-c-format  #, no-c-format
894  #. Tag: para  #. Tag: para
895  msgid ""  msgid ""
# Line 906  msgid "" Line 906  msgid ""
906        "</screen></informalexample> You will need to change at least the \"ha\" option, which specifies the hardware address of the client. The \"bf\" option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys 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>"        "</screen></informalexample> You will need to change at least the \"ha\" option, which specifies the hardware address of the client. The \"bf\" option specifies the file a client should retrieve via TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=\"mips\"> On SGI Indys 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>"
907  msgstr ""  msgstr ""
908    
909  #: install-methods.xml:1237  #: install-methods.xml:1239
910  #, no-c-format  #, no-c-format
911  #. Tag: para  #. Tag: para
912  msgid "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, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>."  msgid "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, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>."
913  msgstr ""  msgstr ""
914    
915  #: install-methods.xml:1258  #: install-methods.xml:1260
916  #, no-c-format  #, no-c-format
917  #. Tag: title  #. Tag: title
918  msgid "Setting up a DHCP server"  msgid "Setting up a DHCP server"
919  msgstr ""  msgstr ""
920    
921  #: install-methods.xml:1259  #: install-methods.xml:1261
922  #, no-c-format  #, no-c-format
923  #. Tag: para  #. Tag: para
924  msgid ""  msgid ""
# Line 945  msgid "" Line 945  msgid ""
945        "</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>."        "</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>."
946  msgstr ""  msgstr ""
947    
948  #: install-methods.xml:1271  #: install-methods.xml:1273
949  #, no-c-format  #, no-c-format
950  #. Tag: para  #. Tag: para
951  msgid "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."  msgid "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."
952  msgstr ""  msgstr ""
953    
954  #: install-methods.xml:1281  #: install-methods.xml:1283
955  #, no-c-format  #, no-c-format
956  #. Tag: para  #. Tag: para
957  msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."  msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>."
958  msgstr ""  msgstr ""
959    
960  #: install-methods.xml:1289  #: install-methods.xml:1291
961  #, no-c-format  #, no-c-format
962  #. Tag: title  #. Tag: title
963  msgid "Enabling PXE Booting in the DHCP configuration"  msgid "Enabling PXE Booting in the DHCP configuration"
964  msgstr ""  msgstr ""
965    
966  #: install-methods.xml:1290  #: install-methods.xml:1292
967  #, no-c-format  #, no-c-format
968  #. Tag: para  #. Tag: para
969  msgid ""  msgid ""
# Line 998  msgid "" Line 998  msgid ""
998        "</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)."        "</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)."
999  msgstr ""  msgstr ""
1000    
1001  #: install-methods.xml:1306  #: install-methods.xml:1308
1002  #, no-c-format  #, no-c-format
1003  #. Tag: title  #. Tag: title
1004  msgid "Enabling the TFTP Server"  msgid "Enabling the TFTP Server"
1005  msgstr ""  msgstr ""
1006    
1007  #: install-methods.xml:1307  #: install-methods.xml:1309
1008  #, no-c-format  #, no-c-format
1009  #. Tag: para  #. Tag: para
1010  msgid ""  msgid ""
# Line 1013  msgid "" Line 1013  msgid ""
1013        "</screen></informalexample> Debian packages will in general set this up correctly by default when they are installed."        "</screen></informalexample> Debian packages will in general set this up correctly by default when they are installed."
1014  msgstr ""  msgstr ""
1015    
1016  #: install-methods.xml:1318  #: install-methods.xml:1320
1017  #, no-c-format  #, no-c-format
1018  #. Tag: para  #. Tag: para
1019  msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>."  msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>."
1020  msgstr ""  msgstr ""
1021    
1022  #: install-methods.xml:1332  #: install-methods.xml:1334
1023  #, no-c-format  #, no-c-format
1024  #. Tag: para  #. Tag: para
1025  msgid ""  msgid ""
# Line 1030  msgid "" Line 1030  msgid ""
1030        "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."        "</screen></informalexample> to adjust the range of source ports the Linux TFTP server uses."
1031  msgstr ""  msgstr ""
1032    
1033  #: install-methods.xml:1354  #: install-methods.xml:1356
1034  #, no-c-format  #, no-c-format
1035  #. Tag: title  #. Tag: title
1036  msgid "Move TFTP Images Into Place"  msgid "Move TFTP Images Into Place"
1037  msgstr ""  msgstr ""
1038    
1039  #: install-methods.xml:1355  #: install-methods.xml:1357
1040  #, no-c-format  #, no-c-format
1041  #. Tag: para  #. Tag: para
1042  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."  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."
1043  msgstr ""  msgstr ""
1044    
1045  #: install-methods.xml:1365  #: install-methods.xml:1367
1046  #, no-c-format  #, no-c-format
1047  #. Tag: para  #. Tag: para
1048  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."  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."
1049  msgstr ""  msgstr ""
1050    
1051  #: install-methods.xml:1374  #: install-methods.xml:1376
1052  #, no-c-format  #, no-c-format
1053  #. Tag: para  #. Tag: para
1054  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."  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."
1055  msgstr ""  msgstr ""
1056    
1057  #: install-methods.xml:1382  #: install-methods.xml:1384
1058  #, no-c-format  #, no-c-format
1059  #. Tag: para  #. Tag: para
1060  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."  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."
1061  msgstr ""  msgstr ""
1062    
1063  #: install-methods.xml:1394  #: install-methods.xml:1396
1064  #, no-c-format  #, no-c-format
1065  #. Tag: title  #. Tag: title
1066  msgid "DECstation TFTP Images"  msgid "DECstation TFTP Images"
1067  msgstr ""  msgstr ""
1068    
1069  #: install-methods.xml:1395  #: install-methods.xml:1397
1070  #, no-c-format  #, no-c-format
1071  #. Tag: para  #. Tag: para
1072  msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. 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."  msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. 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."
1073  msgstr ""  msgstr ""
1074    
1075  #: install-methods.xml:1404  #: install-methods.xml:1406
1076  #, no-c-format  #, no-c-format
1077  #. Tag: para  #. Tag: para
1078  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 \"3\". If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:"  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 \"3\". If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:"
1079  msgstr ""  msgstr ""
1080    
1081  #: install-methods.xml:1416  #: install-methods.xml:1418
1082  #, no-c-format  #, no-c-format
1083  #. Tag: userinput  #. Tag: userinput
1084  msgid "boot #/tftp/filename param1=value1 param2=value2 ..."  msgid "boot #/tftp/filename param1=value1 param2=value2 ..."
1085  msgstr ""  msgstr ""
1086    
1087  #: install-methods.xml:1418  #: install-methods.xml:1420
1088  #, no-c-format  #, no-c-format
1089  #. Tag: para  #. Tag: para
1090  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>."  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>."
1091  msgstr ""  msgstr ""
1092    
1093  #: install-methods.xml:1456  #: install-methods.xml:1458
1094  #, no-c-format  #, no-c-format
1095  #. Tag: title  #. Tag: title
1096  msgid "Alpha TFTP Booting"  msgid "Alpha TFTP Booting"
1097  msgstr ""  msgstr ""
1098    
1099  #: install-methods.xml:1457  #: install-methods.xml:1459
1100  #, no-c-format  #, no-c-format
1101  #. Tag: para  #. Tag: para
1102  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."  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."
1103  msgstr ""  msgstr ""
1104    
1105  #: install-methods.xml:1472  #: install-methods.xml:1474
1106  #, no-c-format  #, no-c-format
1107  #. Tag: title  #. Tag: title
1108  msgid "SPARC TFTP Booting"  msgid "SPARC TFTP Booting"
1109  msgstr ""  msgstr ""
1110    
1111  #: install-methods.xml:1473  #: install-methods.xml:1475
1112  #, no-c-format  #, no-c-format
1113  #. Tag: para  #. Tag: para
1114  msgid ""  msgid ""
# Line 1117  msgid "" Line 1117  msgid ""
1117        "</screen></informalexample> This will spit out the IP in hexadecimal; to get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."        "</screen></informalexample> This will spit out the IP in hexadecimal; to get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name."
1118  msgstr ""  msgstr ""
1119    
1120  #: install-methods.xml:1490  #: install-methods.xml:1492
1121  #, no-c-format  #, no-c-format
1122  #. Tag: para  #. Tag: para
1123  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."  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."
1124  msgstr ""  msgstr ""
1125    
1126  #: install-methods.xml:1501  #: install-methods.xml:1503
1127  #, no-c-format  #, no-c-format
1128  #. Tag: title  #. Tag: title
1129  msgid "BVM/Motorola TFTP Booting"  msgid "BVM/Motorola TFTP Booting"
1130  msgstr ""  msgstr ""
1131    
1132  #: install-methods.xml:1502  #: install-methods.xml:1504
1133  #, no-c-format  #, no-c-format
1134  #. Tag: para  #. Tag: para
1135  msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>."  msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>."
1136  msgstr ""  msgstr ""
1137    
1138  #: install-methods.xml:1507  #: install-methods.xml:1509
1139  #, no-c-format  #, no-c-format
1140  #. Tag: para  #. Tag: para
1141  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."  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."
1142  msgstr ""  msgstr ""
1143    
1144  #: install-methods.xml:1519  #: install-methods.xml:1521
1145  #, no-c-format  #, no-c-format
1146  #. Tag: title  #. Tag: title
1147  msgid "SGI Indys TFTP Booting"  msgid "SGI Indys TFTP Booting"
1148  msgstr ""  msgstr ""
1149    
1150  #: install-methods.xml:1520  #: install-methods.xml:1522
1151  #, no-c-format  #, no-c-format
1152  #. Tag: para  #. Tag: para
1153  msgid "On SGI Indys 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>."  msgid "On SGI Indys 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>."
1154  msgstr ""  msgstr ""
1155    
1156  #: install-methods.xml:1532  #: install-methods.xml:1534
1157  #, no-c-format  #, no-c-format
1158  #. Tag: title  #. Tag: title
1159  msgid "Broadcom BCM91250A TFTP Booting"  msgid "Broadcom BCM91250A TFTP Booting"
1160  msgstr ""  msgstr ""
1161    
1162  #: install-methods.xml:1533  #: install-methods.xml:1535
1163  #, no-c-format  #, no-c-format
1164  #. Tag: para  #. Tag: para
1165  msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to the loaded to CFE."  msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to the loaded to CFE."
1166  msgstr ""  msgstr ""
1167    
1168  #: install-methods.xml:1638  #: install-methods.xml:1640
1169  #, no-c-format  #, no-c-format
1170  #. Tag: title  #. Tag: title
1171  msgid "Automatic Installation"  msgid "Automatic Installation"
1172  msgstr ""  msgstr ""
1173    
1174  #: install-methods.xml:1639  #: install-methods.xml:1641
1175  #, no-c-format  #, no-c-format
1176  #. Tag: para  #. Tag: para
1177  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."  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."
1178  msgstr ""  msgstr ""
1179    
1180  #: install-methods.xml:1652  #: install-methods.xml:1654
1181  #, no-c-format  #, no-c-format
1182  #. Tag: title  #. Tag: title
1183  msgid "Automatic installation using the Debian Installer"  msgid "Automatic Installation Using the Debian Installer"
1184  msgstr ""  msgstr ""
1185    
1186  #: install-methods.xml:1654  #: install-methods.xml:1655
1187  #, no-c-format  #, no-c-format
1188  #. Tag: para  #. Tag: para
1189  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 question asked during the installation process."  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 question asked during the installation process."
1190  msgstr ""  msgstr ""
1191    
1192  #: install-methods.xml:1660  #: install-methods.xml:1662
1193    #, no-c-format
1194    #. Tag: para
1195    msgid "Although most dialogs used by &d-i; can be preseeded using this method, there are some notable exceptions. You can (re)partition an entire disk or use available free space on a disk; it is not possible to use existing partitions. You currently cannot use preseeding to set up RAID and LVM. <phrase condition=\"sarge\">Also, with the exception of network driver modules, it is not possible to preconfigure kernel module parameters.</phrase>"
1196    msgstr ""
1197    
1198    #: install-methods.xml:1671
1199  #, no-c-format  #, no-c-format
1200  #. Tag: para  #. Tag: para
1201  msgid "The preconfiguration file is in the format used by the debconf-set-selections command. A well documented and working example that you can edit is in <xref linkend=\"example-preseed\"/>."  msgid "The preconfiguration file is in the format used by the debconf-set-selections command. A well documented and working example that you can edit is in <xref linkend=\"example-preseed\"/>."
1202  msgstr ""  msgstr ""
1203    
1204  #: install-methods.xml:1666  #: install-methods.xml:1677
1205  #, no-c-format  #, no-c-format
1206  #. Tag: para  #. Tag: para
1207  msgid ""  msgid ""
# Line 1205  msgid "" Line 1211  msgid ""
1211        "</screen></informalexample> However, a file generated in this manner will have some items that should not be preseeded, and the file in <xref linkend=\"example-preseed\"/> is a better starting place for most users."        "</screen></informalexample> However, a file generated in this manner will have some items that should not be preseeded, and the file in <xref linkend=\"example-preseed\"/> is a better starting place for most users."
1212  msgstr ""  msgstr ""
1213    
1214  #: install-methods.xml:1681  #: install-methods.xml:1692
1215  #, no-c-format  #, no-c-format
1216  #. Tag: para  #. Tag: para
1217  msgid "Once you have a preconfiguration file, you can edit it if necessary, and place it on a web server, or copy it onto the installer's boot media. Wherever you place the file, you need to pass a parameter to the installer at boot time to tell it to use the file."  msgid "Once you have a preconfiguration file, you can edit it if necessary, and place it on a web server, or copy it onto the installer's boot media. Wherever you place the file, you need to pass a parameter to the installer at boot time to tell it to use the file."
1218  msgstr ""  msgstr ""
1219    
1220  #: install-methods.xml:1688  #: install-methods.xml:1699
1221  #, no-c-format  #, no-c-format
1222  #. Tag: para  #. Tag: para
1223  msgid "To make the installer use a preconfiguration file downloaded from the network, add preseed/url=http://url/to/preseed.cfg to the kernel boot parameters. Of course the preconfiguration will not take effect until the installer manages to set up the network to download the file, so this is most useful if the installer can set up the network via DHCP without asking any questions. You may want to set the installation priority to critical to avoid any questions while the network is being configured. See <xref linkend=\"installer-args\"/>."  msgid "To make the installer use a preconfiguration file downloaded from the network, add preseed/url=http://url/to/preseed.cfg to the kernel boot parameters. Of course the preconfiguration will not take effect until the installer manages to set up the network to download the file, so this is most useful if the installer can set up the network via DHCP without asking any questions. You may want to set the installation priority to critical to avoid any questions while the network is being configured. See <xref linkend=\"installer-args\"/>."
1224  msgstr ""  msgstr ""
1225    
1226  #: install-methods.xml:1699  #: install-methods.xml:1710
1227  #, no-c-format  #, no-c-format
1228  #. Tag: para  #. Tag: para
1229  msgid "To place a preconfiguration file on a CD, you would need to remaster the ISO image to include your preconfiguration file. See the manual page for mkisofs for details. Alternatively, put the preseed file on a floppy, and use preseed/file=/floppy/preseed.cfg"  msgid "To place a preconfiguration file on a CD, you would need to remaster the ISO image to include your preconfiguration file. See the manual page for mkisofs for details. Alternatively, put the preseed file on a floppy, and use preseed/file=/floppy/preseed.cfg"
1230  msgstr ""  msgstr ""
1231    
1232  #: install-methods.xml:1706  #: install-methods.xml:1717
1233  #, no-c-format  #, no-c-format
1234  #. Tag: para  #. Tag: para
1235  msgid "If you'll be booting from a USB memory stick, then you can simply copy your preconfiguration file onto the memory stick's filesystem, and edit the syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel boot parameters."  msgid "If you'll be booting from a USB memory stick, then you can simply copy your preconfiguration file onto the memory stick's filesystem, and edit the syslinux.cfg file to add preseed/file=/hd-media/preseed.cfg to the kernel boot parameters."
1236  msgstr ""  msgstr ""
1237    
1238    #: install-methods.xml:1727
1239    #, no-c-format
1240    #. Tag: title
1241    msgid "Using Preseeding to Change Default Values"
1242    msgstr ""
1243    
1244    #: install-methods.xml:1728
1245    #, no-c-format
1246    #. Tag: para
1247    msgid "It is also possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the <firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after setting the value for a template."
1248    msgstr ""
1249    
1250    #: install-methods.xml:1735
1251    #, no-c-format
1252    #. Tag: screen
1253    msgid ""
1254          "d-i foo/bar string value\n"
1255          "d-i foo/bar seen false"
1256    msgstr ""
1257    
Legend:
Removed from v.26484  
changed lines
  Added in v.27563
  ViewVC Help
Powered by ViewVC 1.1.5