From: "Xavier Neys" <neysx@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gentoo-sparc-netboot-howto.xml
Date: Thu, 18 Aug 2005 14:27:28 +0000 [thread overview]
Message-ID: <200508181427.j7IERf60029962@robin.gentoo.org> (raw)
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 @@
<?xml version='1.0' encoding="UTF-8"?>
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.7 2005/08/18 13:59:23 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-sparc-netboot-howto.xml,v 1.8 2005/08/18 14:27:28 neysx Exp $ -->
<guide link="/doc/en/gentoo-sparc-netboot-howto.xml">
+
<title>Gentoo Linux based Netboot HOWTO</title>
+
<author title="SPARC Developer">
<mail link="weeve@gentoo.org">Jason Wever</mail>
</author>
+
<abstract>
-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.
</abstract>
+
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
@@ -23,21 +28,21 @@
<body>
<note>
-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.
</note>
<p>
-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.
</p>
<p>
-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.
</p>
<p>
@@ -46,18 +51,14 @@
<ol>
<li>
- Client machine sends out a reverse ARP (RARP) request to get an IP address.
- </li>
- <li>
- A server machine returns a response to the client with the IP address.
- </li>
- <li>
- 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
</li>
+ <li>A server machine returns a response to the client with the IP address</li>
<li>
- 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
</li>
+ <li>Once the image is downloaded, the netboot client then boots the image</li>
</ol>
<p>
@@ -75,9 +76,8 @@
<title>The Reverse ARP Daemon</title>
<body>
-
<p>
-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.
</p>
@@ -91,31 +91,31 @@
</p>
<p>
-No matter which rarpd you choose to use, you will need to setup the
-<path>/etc/ethers</path> file. This file indicates which hosts rarpd should
+No matter which rarpd you choose to use, you will need to setup the
+<path>/etc/ethers</path> file. This file indicates which hosts rarpd should
respond to when a request is seen, and what address to reply with.
</p>
<p>
-The format of <path>/etc/ethers</path> 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 <path>/etc/ethers</path> 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:
</p>
<pre caption="Example /etc/ethers">
-08:00:20:77:1f:3e sparc-netboot.gentoo.org
+08:00:20:77:1f:3e sparc-netboot.gentoo.org
</pre>
<note>
-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).
</note>
<p>
-If you desire to add additional hosts to <path>/etc/ethers</path>, 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 <path>/etc/ethers</path>, you do not
+need to restart the rarpd services as the file is checked each time a request
+is received.
</p>
<p>
@@ -123,16 +123,17 @@
</p>
<p>
-Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server needs to
-be able to resolve the hostname into its IP address. This can be done two
-ways, <path>/etc/hosts</path> or the nameserver the netboot server uses.
+Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server
+needs to be able to resolve the hostname into its IP address. This can be done
+two ways, <path>/etc/hosts</path> or the nameserver the netboot server uses.
</p>
<p>
-An <path>/etc/hosts</path> 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 <path>/etc/hosts</path> entry would look like;
+An <path>/etc/hosts</path> 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 <path>/etc/hosts</path> entry
+would look like;
</p>
<pre caption="/etc/hosts">
@@ -142,33 +143,33 @@
<note>
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.
</note>
<p>
-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.
</p>
<note>
-If both <path>/etc/hosts</path> and the nameserver have an entry for the host to be
-netbooted, <path>/etc/hosts</path> will be used first (granted the order of
-<path>/etc/nsswitch.conf</path> has not been changed from the default).
+If both <path>/etc/hosts</path> and the nameserver have an entry for the host
+to be netbooted, <path>/etc/hosts</path> will be used first (granted the order
+of <path>/etc/nsswitch.conf</path> has not been changed from the default).
</note>
<p>
<b>Setting up net-misc/iputils rarpd</b>
</p>
-<p>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
next reply other threads:[~2005-08-18 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 14:27 Xavier Neys [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-20 18:46 [gentoo-doc-cvs] cvs commit: gentoo-sparc-netboot-howto.xml Sven Vermeulen
2007-07-26 20:55 Jose Luis Rivero
2005-08-18 13:59 Xavier Neys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508181427.j7IERf60029962@robin.gentoo.org \
--to=neysx@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox