diff options
Diffstat (limited to 'nl/install-methods/tftp')
-rw-r--r-- | nl/install-methods/tftp/bootp.xml | 73 | ||||
-rw-r--r-- | nl/install-methods/tftp/dhcp.xml | 94 | ||||
-rw-r--r-- | nl/install-methods/tftp/rarp.xml | 32 |
3 files changed, 0 insertions, 199 deletions
diff --git a/nl/install-methods/tftp/bootp.xml b/nl/install-methods/tftp/bootp.xml deleted file mode 100644 index 86be45104..000000000 --- a/nl/install-methods/tftp/bootp.xml +++ /dev/null @@ -1,73 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 59293 untranslated --> - - - <sect2 condition="supports-bootp" id="tftp-bootp"> - <title>Setting up a BOOTP server</title> -<para> - -There are two BOOTP servers available for GNU/Linux. The first is CMU -<command>bootpd</command>. The other is actually a DHCP server: ISC -<command>dhcpd</command>. In &debian-gnu; these are contained in the -<classname>bootp</classname> and <classname>dhcp3-server</classname> -packages respectively. - -</para><para> - -To use CMU <command>bootpd</command>, you must first uncomment (or -add) the relevant line in <filename>/etc/inetd.conf</filename>. On -&debian-gnu;, you can run <userinput>update-inetd --enable -bootps</userinput>, then <userinput>/etc/init.d/inetd -reload</userinput> to do so. Just in case your BOOTP server does not -run &debian;, the line in question should look like: - -<informalexample><screen> -bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120 -</screen></informalexample> - -Now, you must create an <filename>/etc/bootptab</filename> file. This -has the same sort of familiar and cryptic format as the good old BSD -<filename>printcap</filename>, <filename>termcap</filename>, and -<filename>disktab</filename> files. See the -<filename>bootptab</filename> manual page for more information. For -CMU <command>bootpd</command>, you will need to know the hardware -(MAC) address of the client. Here is an example -<filename>/etc/bootptab</filename>: - -<informalexample><screen> -client:\ - hd=/tftpboot:\ - bf=tftpboot.img:\ - ip=192.168.1.90:\ - sm=255.255.255.0:\ - sa=192.168.1.1:\ - ha=0123456789AB: -</screen></informalexample> - -You will need to change at least the <quote>ha</quote> option, which -specifies the hardware address of the client. The <quote>bf</quote> -option specifies the file a client should retrieve via TFTP; see -<xref linkend="tftp-images"/> for more details. - -<phrase arch="mips"> -On SGI machines you can just enter the command monitor and type -<userinput>printenv</userinput>. The value of the -<userinput>eaddr</userinput> variable is the machine's MAC address. -</phrase> - -</para><para> - -By contrast, setting up BOOTP with ISC <command>dhcpd</command> is -really easy, because it treats BOOTP clients as a moderately special -case of DHCP clients. Some architectures require a complex -configuration for booting clients via BOOTP. If yours is one of -those, read the section <xref linkend="dhcpd"/>. Otherwise you -will probably be able to get away with simply adding the -<userinput>allow bootp</userinput> directive to the configuration -block for the subnet containing the client in -<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart -<command>dhcpd</command> with <userinput>/etc/init.d/dhcp3-server -restart</userinput>. - -</para> - </sect2> diff --git a/nl/install-methods/tftp/dhcp.xml b/nl/install-methods/tftp/dhcp.xml deleted file mode 100644 index 6f1a89b81..000000000 --- a/nl/install-methods/tftp/dhcp.xml +++ /dev/null @@ -1,94 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62402 untranslated --> - - <sect2 id="dhcpd"> - <title>Setting up a DHCP server</title> -<para> - -One free software DHCP server is ISC <command>dhcpd</command>. -For &debian-gnu;, the <classname>dhcp3-server</classname> package is -recommended. Here is a sample configuration file for it (see -<filename>/etc/dhcp3/dhcpd.conf</filename>): - -<informalexample><screen> -option domain-name "example.com"; -option domain-name-servers ns1.example.com; -option subnet-mask 255.255.255.0; -default-lease-time 600; -max-lease-time 7200; -server-name "servername"; - -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option routers 192.168.1.1; -} - -host clientname { - filename "/tftpboot.img"; - server-name "servername"; - next-server servername; - hardware ethernet 01:23:45:67:89:AB; - fixed-address 192.168.1.90; -} -</screen></informalexample> - -</para><para> - -In this example, there is one server -<replaceable>servername</replaceable> which performs all of the work -of DHCP server, TFTP server, and network gateway. You will almost -certainly need to change the domain-name options, as well as the -server name and client hardware address. The -<replaceable>filename</replaceable> option should be the name of the -file which will be retrieved via TFTP. - -</para><para> - -After you have edited the <command>dhcpd</command> configuration file, -restart it with <userinput>/etc/init.d/dhcp3-server restart</userinput>. - -</para> - - <sect3 arch="x86"> - <title>Enabling PXE Booting in the DHCP configuration</title> -<para> -Here is another example for a <filename>dhcp.conf</filename> using the -Pre-boot Execution Environment (PXE) method of TFTP. - -<informalexample><screen> -option domain-name "example.com"; - -default-lease-time 600; -max-lease-time 7200; - -allow booting; -allow bootp; - -# The next paragraph needs to be modified to fit your case -subnet 192.168.1.0 netmask 255.255.255.0 { - range 192.168.1.200 192.168.1.253; - option broadcast-address 192.168.1.255; -# the gateway address which can be different -# (access to the internet for instance) - option routers 192.168.1.1; -# indicate the dns you want to use - option domain-name-servers 192.168.1.3; -} - -group { - next-server 192.168.1.3; - host tftpclient { -# tftp client hardware address - hardware ethernet 00:10:DC:27:6C:15; - filename "pxelinux.0"; - } -} -</screen></informalexample> - -Note that for PXE booting, the client filename <filename>pxelinux.0</filename> -is a boot loader, not a kernel image (see <xref linkend="tftp-images"/> -below). - -</para> - </sect3> - </sect2> diff --git a/nl/install-methods/tftp/rarp.xml b/nl/install-methods/tftp/rarp.xml deleted file mode 100644 index 47715f8db..000000000 --- a/nl/install-methods/tftp/rarp.xml +++ /dev/null @@ -1,32 +0,0 @@ -<!-- retain these comments for translator revision tracking --> -<!-- original version: 62401 untranslated --> - - <sect2 condition="supports-rarp" id="tftp-rarp"> - <title>Setting up RARP server</title> -<para> - -To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) -of the client computers to be installed. -If you don't know this information, you can - -<phrase arch="sparc"> pick it off the initial OpenPROM boot messages, use the -OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> - -boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the -command <userinput>ip addr show dev eth0</userinput>. - -</para><para> - -On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, -you use the <command>rarpd</command> program. -You need to ensure that the Ethernet hardware address for the client is -listed in the <quote>ethers</quote> database (either in the -<filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the -<quote>hosts</quote> database. Then you need to start the RARP daemon. -Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> -on most Linux systems and SunOS 5 (Solaris 2), -<userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, -or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1). - -</para> - </sect2> |