From 35aa54a022ca3fac5b1c91993e5bdaef2ad7ea57 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Tue, 26 Dec 2006 19:46:26 +0000 Subject: - All architectures that support TFTP booting also support DCHP, so remove the "supports-dhcp" condition - According to the text, Alpha supports BOOTP - Use dhcp3-server for examples rather than dhcp (version 2) - tftpd-hpa does not use /tftpboot by default; allow for this in examples --- en/install-methods/install-tftp.xml | 61 +++++++++++++++++++++++-------------- en/install-methods/tftp/bootp.xml | 10 +++--- en/install-methods/tftp/dhcp.xml | 19 +++++------- en/preparing/needed-info.xml | 2 +- 4 files changed, 52 insertions(+), 40 deletions(-) (limited to 'en') diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index 39c528be2..6376874e4 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -13,26 +13,27 @@ and the machine configured to support booting of your specific machine. -You need to setup a TFTP server, and for many machines, a BOOTP server -, or RARP server -, or DHCP server. +You need to setup a TFTP server, and for many machines a DHCP +server, or RARP +server, or BOOTP +server. 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. +way is to use the BOOTP protocol. BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain -a boot image. +a boot image. - Yet another alternative exists on VMEbus -systems: the IP address can be manually configured in boot ROM. +Yet another alternative exists on VMEbus +systems: the IP address can be manually configured in boot ROM. -The DHCP (Dynamic Host Configuration -Protocol) is a more flexible, backwards-compatible extension of BOOTP. -Some systems can only be configured via DHCP. +The DHCP (Dynamic Host Configuration Protocol) is a more flexible, +backwards-compatible extension of BOOTP. +Some systems can only be configured via DHCP. @@ -101,18 +102,33 @@ tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot Debian packages will in general set this up correctly by default when they are installed. - + + + +Historically TFTP servers used /tftpboot as directory +to serve images from. However, &debian; packages may use other directories +to comply with the Filesystem Hierarchy +Standard. For example, tftpd-hpa by default +uses /var/lib/tftpboot. You may have to adjust the +configuration examples in this section accordingly. + + + + +Look in /etc/inetd.conf and remember the directory which +is used as the argument of in.tftpd -Look in that file and remember the directory which is used as the -argument of in.tftpd; you'll need that below. The --l argument enables some versions of + +The -l argument enables some versions of in.tftpd to log all requests to the system logs; -this is useful for diagnosing boot errors. If you've had to change -/etc/inetd.conf, you'll have to notify the -running inetd process that the file has changed. -On a Debian machine, run /etc/init.d/inetd -reload; on other machines, -find out the process ID for inetd, and run +this is useful for diagnosing boot errors. + + +; you'll need that below. +If you've had to change /etc/inetd.conf, you'll have to +notify the running inetd process that the file has changed. +On a Debian machine, run /etc/init.d/inetd reload; on +other machines, find out the process ID for inetd, and run kill -HUP inetd-pid. @@ -146,8 +162,7 @@ to adjust the range of source ports the Linux TFTP server uses. Next, place the TFTP boot image you need, as found in , in the tftpd -boot image directory. Generally, this directory will be -/tftpboot. You'll have to make a link from that +boot image directory. You may have to make a link from that file to the file which tftpd will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards. @@ -166,7 +181,7 @@ images via TFTP itself. For net booting, use the For PXE booting, everything you should need is set up in the netboot/netboot.tar.gz tarball. Simply extract this tarball into the tftpd boot image directory. Make sure -your dhcp server is configured to pass /pxelinux.0 +your dhcp server is configured to pass pxelinux.0 to tftpd as the filename to boot. diff --git a/en/install-methods/tftp/bootp.xml b/en/install-methods/tftp/bootp.xml index cda0f9c66..f0b0eab42 100644 --- a/en/install-methods/tftp/bootp.xml +++ b/en/install-methods/tftp/bootp.xml @@ -3,14 +3,14 @@ - Setting up BOOTP server + Setting up a BOOTP server There are two BOOTP servers available for GNU/Linux. The first is CMU bootpd. The other is actually a DHCP server: ISC dhcpd. In &debian; these are contained in the -bootp and dhcp packages -respectively. +bootp and dhcp3-server +packages respectively. @@ -61,11 +61,11 @@ By contrast, setting up BOOTP with ISC dhcpd 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 . Otherwise, you +those, read the section . In that case, you will probably be able to get away with simply adding the allow bootp directive to the configuration block for the subnet containing the client, and restart -dhcpd with /etc/init.d/dhcpd +dhcpd with /etc/init.d/dhcpd3-server restart. diff --git a/en/install-methods/tftp/dhcp.xml b/en/install-methods/tftp/dhcp.xml index fb9c624ea..39327ae23 100644 --- a/en/install-methods/tftp/dhcp.xml +++ b/en/install-methods/tftp/dhcp.xml @@ -1,14 +1,14 @@ - + Setting up a DHCP server One free software DHCP server is ISC dhcpd. -In &debian;, this is available in the dhcp package. -Here is a sample configuration file for it (usually -/etc/dhcpd.conf): +For &debian;, the dhcp3-server package is +recommended. Here is a sample configuration file for it (see +/etc/dhcp3/dhcpd.conf): option domain-name "example.com"; @@ -32,9 +32,6 @@ host clientname { } -Note: the new (and preferred) dhcp3 package uses -/etc/dhcp3/dhcpd.conf. - In this example, there is one server @@ -48,7 +45,7 @@ file which will be retrieved via TFTP. After you have edited the dhcpd configuration file, -restart it with /etc/init.d/dhcpd restart. +restart it with /etc/init.d/dhcpd3-server restart. @@ -79,11 +76,11 @@ subnet 192.168.1.0 netmask 255.255.255.0 { } group { - next-server 192.168.1.3; - host tftpclient { + next-server 192.168.1.3; + host tftpclient { # tftp client hardware address hardware ethernet 00:10:DC:27:6C:15; - filename "/tftpboot/pxelinux.0"; + filename "pxelinux.0"; } } diff --git a/en/preparing/needed-info.xml b/en/preparing/needed-info.xml index 8f68abd37..4a7b21e3c 100644 --- a/en/preparing/needed-info.xml +++ b/en/preparing/needed-info.xml @@ -390,7 +390,7 @@ Service) server. - + On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information -- cgit v1.2.3