Gentoo Linux based Netboot HOWTO

From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1E5lN4-0007I0-9Q for garchives@archives.gentoo.org; Thu, 18 Aug 2005 14:27:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7IERgjt000839; Thu, 18 Aug 2005 14:27:42 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7IERf60029962 for ; Thu, 18 Aug 2005 14:27:42 GMT Message-Id: <200508181427.j7IERf60029962@robin.gentoo.org> Received: from lark.gentoo.osuosl.org ([140.211.166.177] helo=lark.gentoo.org) by smtp.gentoo.org with smtp (Exim 4.43) id 1E5lMq-0004yT-GE for gentoo-doc-cvs@lists.gentoo.org; Thu, 18 Aug 2005 14:27:40 +0000 Received: by lark.gentoo.org (sSMTP sendmail emulation); Thu, 18 Aug 2005 14:27:28 +0000 From: "Xavier Neys" Date: Thu, 18 Aug 2005 14:27:28 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: gentoo-sparc-netboot-howto.xml Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: 6ece5753-9d8e-48d7-a9fd-abb2cdf02fce X-Archives-Hash: 93da3299016e58e219a80583047838de neysx 05/08/18 14:27:28 Modified: xml/htdocs/doc/en gentoo-sparc-netboot-howto.xml Log: Improved coding style **No content change** Revision Changes Path 1.8 +170 -166 xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo Index: gentoo-sparc-netboot-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- gentoo-sparc-netboot-howto.xml 18 Aug 2005 13:59:23 -0000 1.7 +++ gentoo-sparc-netboot-howto.xml 18 Aug 2005 14:27:28 -0000 1.8 @@ -1,15 +1,20 @@ - + + Gentoo Linux based Netboot HOWTO + Jason Wever + -Guide for setting up a netboot server for use with the Gentoo/SPARC netboot installation images. +Guide for setting up a netboot server for use with the Gentoo/SPARC netboot +installation images. + @@ -23,21 +28,21 @@ -This howto is currently very SPARC-centric and expecting that you will be +This howto is currently very SPARC-centric and expecting that you will be setting up your netboot server on an existing Gentoo Linux machine.

-This document will describe how to setup a network booting environment for a -Sun Microsystems SPARC or UltraSPARC based computer. The document assumes that +This document will describe how to setup a network booting environment for a +Sun Microsystems SPARC or UltraSPARC based computer. The document assumes that you have an existing Gentoo Linux computer available to act as the netboot server.

-Both the netboot server and netboot client will need to be on the same -network subnet, as the ARP protocol is typically not forwarded across -different network subnets. +Both the netboot server and netboot client will need to be on the same network +subnet, as the ARP protocol is typically not forwarded across different network +subnets.

@@ -46,18 +51,14 @@

- Client machine sends out a reverse ARP (RARP) request to get an IP address. -
- A server machine returns a response to the client with the IP address. -
- The client then attempts to download a boot image from the RARP server - using the tftp protocol. + Client machine sends out a reverse ARP (RARP) request to get an IP address
A server machine returns a response to the client with the IP address
- Once the image is downloaded, the netboot client then boots the image. + The client then attempts to download a boot image from the RARP server + using the tftp protocol
Once the image is downloaded, the netboot client then boots the image

@@ -75,9 +76,8 @@ The Reverse ARP Daemon -

-Currently, there are two choices for a reverse ARP daemon. They are +Currently, there are two choices for a reverse ARP daemon. They are net-misc/iputils (installed as part of the system profile) and net-misc/rarpd.

@@ -91,31 +91,31 @@

-No matter which rarpd you choose to use, you will need to setup the -/etc/ethers file. This file indicates which hosts rarpd should +No matter which rarpd you choose to use, you will need to setup the +/etc/ethers file. This file indicates which hosts rarpd should respond to when a request is seen, and what address to reply with.

-The format of /etc/ethers is MAC address of the NIC the machine -will be netbooting from and the hostname. Whitespace delimits the MAC address -from the hostname, and each entry should have its own line. The following +The format of /etc/ethers is MAC address of the NIC the machine +will be netbooting from and the hostname. Whitespace delimits the MAC address +from the hostname, and each entry should have its own line. The following example is for a host named sparc-netboot.gentoo.org:

-08:00:20:77:1f:3e	sparc-netboot.gentoo.org
+08:00:20:77:1f:3e  sparc-netboot.gentoo.org

-If a given hexidecimal number in the MAC address starts or is 0, you can -chose to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e). +If a given hexadecimal number in the MAC address starts or is 0, you can chose +to omit the first 0 (i.e. 08:00:20:77:1f:3e becomes 8:0:20:77:1f:3e).

-If you desire to add additional hosts to /etc/ethers, you do not need to -restart the rarpd services as the file is checked each time a request is -received. +If you desire to add additional hosts to /etc/ethers, you do not +need to restart the rarpd services as the file is checked each time a request +is received.

@@ -123,16 +123,17 @@

-Since each entry in /etc/ethers has a hostname, the netboot server needs to -be able to resolve the hostname into its IP address. This can be done two -ways, /etc/hosts or the nameserver the netboot server uses. +Since each entry in /etc/ethers has a hostname, the netboot server +needs to be able to resolve the hostname into its IP address. This can be done +two ways, /etc/hosts or the nameserver the netboot server uses.

-An /etc/hosts entry for resolving a hostname will look very similar to the one -that probably exists from when you installed Gentoo on the netboot server. -For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP -address of 10.0.1.15. So the /etc/hosts entry would look like; +An /etc/hosts entry for resolving a hostname will look very +similar to the one that probably exists from when you installed Gentoo on the +netboot server. For our example host, sparc-netboot.gentoo.org, we'll assume +that it has an IP address of 10.0.1.15. So the /etc/hosts entry +would look like;

@@ -142,33 +143,33 @@
 
 
 Depending on the environment, you may need to consult your network
-administrator to get an appropriate IP address or addresses to netboot
-the host with.
+administrator to get an appropriate IP address or addresses to netboot the host
+with.
 
 
 
-If you use a nameserver, then the DNS server administrator will need to add a 
-record for the hostname, in our example sparc-netboot.gentoo.org, to point to 
-the appropriate IP address.
-Please consult your DNS server administrator and/or the documentation for the
-DNS server's DNS software for how to add the entry.
+If you use a nameserver, then the DNS server administrator will need to add a
+record for the hostname, in our example sparc-netboot.gentoo.org, to point to
+the appropriate IP address. Please consult your DNS server administrator and/or
+the documentation for the DNS server's DNS software for how to add the entry.
 
 
 
-If both /etc/hosts and the nameserver have an entry for the host to be
-netbooted, /etc/hosts will be used first (granted the order of
-/etc/nsswitch.conf has not been changed from the default).
+If both /etc/hosts and the nameserver have an entry for the host
+to be netbooted, /etc/hosts will be used first (granted the order
+of /etc/nsswitch.conf has not been changed from the default).
 
 
 
 Setting up net-misc/iputils rarpd
 
 
-First, we will need to determine the options to use for rarpd.  While there
-are more options than we'll cover here, these options should get you started



-- 
gentoo-doc-cvs@gentoo.org mailing list