diff options
Diffstat (limited to 'nl/install-methods/install-tftp.xml')
| -rw-r--r-- | nl/install-methods/install-tftp.xml | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/nl/install-methods/install-tftp.xml b/nl/install-methods/install-tftp.xml index 5f4291999..51730ad2a 100644 --- a/nl/install-methods/install-tftp.xml +++ b/nl/install-methods/install-tftp.xml @@ -1,5 +1,5 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 35613 untranslated --> +<!-- original version: 36841 untranslated --> <sect1 condition="supports-tftp" id="install-tftp"> <title>Preparing Files for TFTP Net Booting</title> @@ -186,7 +186,8 @@ to <command>tftpd</command> as the filename to boot. 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. +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. @@ -262,22 +263,21 @@ these methods. <title>SPARC TFTP Booting</title> <para> -SPARC architectures for instance use the subarchitecture names, such -as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the -architecture is left blank, so the file the client looks for is just -<filename>client-ip-in-hex</filename>. Thus, if your system -subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename -would be <filename>C0A80103.SUN4C</filename>. An easy way to determine -this is to enter the following command in a shell (assuming the -machine's intended IP is 10.0.0.4). +Some SPARC architectures add the subarchitecture names, such as +<quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, +if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, +the filename would be <filename>C0A80103.SUN4C</filename>. However, +there are also subarchitectures where the file the client looks for is +just <filename>client-ip-in-hex</filename>. An easy way to determine the +hexadecimal code for the IP address is to enter the following command +in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen> $ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 </screen></informalexample> -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. +To get to the correct filename, you will need to change all letters to +uppercase and if necessary append the subarchitecture name. </para><para> @@ -325,7 +325,7 @@ the <userinput>filename=</userinput> option in <para> 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. +full path of the file to be loaded to CFE. </para> </sect3> |