<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->

<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->

<version>1.1</version>

<version>1.2</version>

<date>2005-06-25</date>

<date>2005-08-07</date>

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

This document will describe how to setup a network booting environment for a 

This document will describe how to setup a network booting environment for a Sun

Sun Microsystems SPARC or UltraSPARC based computer.  The document assumes that

Microsystems SPARC or UltraSPARC based computer.  The document assumes that you

you have an existing Gentoo Linux computer available to act as the netboot

have an existing Gentoo Linux computer available to act as the netboot server.

server.

Both the netboot server and netboot client will need to be on the same

Both the netboot server and netboot client will need to be on the same network

network subnet, as the ARP protocol is typically not forwarded across

subnet, as the ARP protocol is typically not forwarded across different network

different network subnets.

subnets.

Currently, there are two choices for a reverse ARP daemon.  They are

Currently, there are two choices for a reverse ARP daemon. They are

<path>/etc/ethers</path> file.  This file indicates which hosts rarpd should 

<path>/etc/ethers</path> file. This file indicates which hosts rarpd should

If you desire to add additional hosts to /etc/ethers, you do not need to

If you desire to add additional hosts to <path>/etc/ethers</path>, you do not

restart the rarpd services as the file is checked each time a request is

need to restart the rarpd services as the file is checked each time a request is

Since each entry in /etc/ethers has a hostname, the netboot server needs to

Since each entry in <path>/etc/ethers</path> has a hostname, the netboot server

be able to resolve the hostname into its IP address.  This can be done two

needs to be able to resolve the hostname into its IP address.  This can be done

ways, /etc/hosts or the nameserver the netboot server uses.

two ways, <path>/etc/hosts</path> or the nameserver the netboot server uses.

An /etc/hosts entry for resolving a hostname will look very similar to the one

An <path>/etc/hosts</path> entry for resolving a hostname will look very similar

that probably exists from when you installed Gentoo on the netboot server.

to the one that probably exists from when you installed Gentoo on the netboot

For our example host, sparc-netboot.gentoo.org, we'll assume that it has an IP

server.  For our example host, sparc-netboot.gentoo.org, we'll assume that it

address of 10.0.1.15.  So the /etc/hosts entry would look like;

has an IP address of 10.0.1.15.  So the <path>/etc/hosts</path> entry would look

like;

If you use a nameserver, then the DNS server administrator will need to add a 

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 

record for the hostname, in our example sparc-netboot.gentoo.org, to point to

the appropriate IP address.

the appropriate IP address.  Please consult your DNS server administrator and/or

Please consult your DNS server administrator and/or the documentation for the

the documentation for the DNS server's DNS software for how to add the entry.

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

If both <path>/etc/hosts</path> and the nameserver have an entry for the host to

netbooted, /etc/hosts will be used first (granted the order of

be netbooted, <path>/etc/hosts</path> will be used first (granted the order of

/etc/nsswitch.conf has not been changed from the default).

<path>/etc/nsswitch.conf</path> has not been changed from the default).

an entry will need to be added to /etc/conf.d/local.start if you want to enable

an entry will need to be added to <path>/etc/conf.d/local.start</path> if you

rarpd servies at boot time.  A sample entry is as follows;

want to enable rarpd servies at boot time.  A sample entry is as follows;

    resolves to a valid IP address using /etc/ethers database and DNS

    resolves to a valid IP address using <path>/etc/ethers</path> database and

    DNS

adjust /etc/conf.d/rarpd to look like the following

adjust <path>/etc/conf.d/rarpd</path> to look like the following:

net-misc/netkit-tftp and net-misc/tftp-hpa.  You only need to install one of

net-misc/netkit-tftp and net-misc/tftp-hpa. You only need to install one of the

the tftp daemons for proper operation.

tftp daemons for proper operation.

will appear as the root (/) directory to the clients when requests are 

will appear as the root (<path>/</path>) directory to the clients when requests

received.  Additionally, we'll setup the system to run the tftp daemon with the

are received.  Additionally, we'll setup the system to run the tftp daemon with

user and group nobody.

the user and group nobody.

created with the mkdir command.  The command for the example /tftpboot is;

created with the mkdir command.  The command for the example

<path>/tftpboot</path> is;

Then we will need to change the owner of /tftpboot so that it is owned by user

Then we will need to change the owner of <path>/tftpboot</path> so that it is

nobody and group nobody;

owned by user nobody and group nobody;

configured.  If tftpd services are desired at boot time, an entry to

configured. If tftpd services are desired at boot time, an entry to

/etc/conf.d/local.start will need to be added as atftp has no init.d, inetd or

<path>/etc/conf.d/local.start</path> will need to be added as atftp has no

xinetd scripts of its own.  If you want to use inetd or xinetd for controlling

init.d, inetd or xinetd scripts of its own. If you want to use inetd or xinetd

the tftpd service, please see their respective man pages.

for controlling the tftpd service, please see their respective man pages.

experimental/sparc/tftpboot for the appropriate image.  We'll assume you are

<path>experimental/sparc/tftpboot</path> for the appropriate image.  We'll

planning to boot a sparc64 host using the

assume you are planning to boot a sparc64 host using the

gentoo-sparc64-1.4_rc4-20040102.tftpboot image.

<path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path> image.

Once you have an image, copy the image into /tftpboot;

Once you have an image, copy the image into <path>/tftpboot</path>;

the hexidecimal number of its current IP address, and on some platforms an

the hexidecimal number of its current IP address, and on some platforms an .ARCH

.ARCH suffix. The hexidecimal number should use <e>capital</e> characters.

suffix. The hexidecimal number should use <e>capital</e> characters.

For each octet in the IP address (the 10 in 10.0.1.15 for instance), you

For each octet in the IP address (the 10 in 10.0.1.15 for instance), you will

will need to convert it to hexidecimal, rather than converting the IP address asa singular number.

need to convert it to hexidecimal, rather than converting the IP address asa

singular number.

<p>So for our example IP address, 10.0.1.15, let's look at its hexidecimal

<p>

equivalent;

So for our example IP address, 10.0.1.15, let's look at its hexidecimal

equivalent:

sparc64 host and the gentoo-sparc64-1.4_rc4-20040102.tftpboot, use the

sparc64 host and the <path>gentoo-sparc64-1.4_rc4-20040102.tftpboot</path>, use

following command;

the following command;

ARP/RARP packet" messages.

ARP/RARP packet" messages.</b>

</b>

    The client does not think its NIC has a link to the network hub/switch

    The client does not think its NIC has a link to the network hub/switch it is

    it is plugged into.  Check to see if the NIC and the port on the network

    plugged into. Check to see if the NIC and the port on the network hub or

    hub or switch has a link light.  If the link light is on, check

    switch has a link light. If the link light is on, check to see what the

    to see what the setting of tpe-link-test? is in OBP with the command;

    setting of tpe-link-test? is in OBP with the command; <c>printenv

    <c>printenv tpe-link-test?</c>. You should receive something like 

    tpe-link-test?</c>. You should receive something like <path>tpe-link-test?

    <path>tpe-link-test?   false     true</path>.

    false true</path>. The first column represents the parameter name, the

    The first column represents the parameter name, the second column shows the

    second column shows the current value for the the parameter, and the third

    current value for the the parameter, and the third column shows the default

    column shows the default value for the parameter. In the example above, we

    value for the parameter.  In the example above, we can see that the current

    can see that the current value is false, which means that the client is not

    value is false, which means that the client is not checking to see if the

    checking to see if the client and network hub or switch can establish a link

    client and network hub or switch can establish a link before issuing its

    before issuing its RARP request. Often times this can cause the problem.

    RARP request.  Often times this can cause the problem.