<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML ><HEAD ><TITLE >Booting from network</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="PA-RISC/Linux Boot HOWTO" HREF="index.html"><LINK REL="UP" TITLE="Available boot solutions" HREF="bootsolutions.html"><LINK REL="PREVIOUS" TITLE="Booting from hard drive" HREF="boothd.html"><LINK REL="NEXT" TITLE="Building and installing a custom kernel" HREF="vmlinux.html"></HEAD ><BODY CLASS="sect1" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >PA-RISC/Linux Boot HOWTO</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="boothd.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" >Chapter 4. Available boot solutions</TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="vmlinux.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A NAME="bootnetwork" ></A >4.3. Booting from network</H1 ><DIV CLASS="highlights" ><A NAME="AEN1006" ></A ><P > Booting from the network is only required in certain cases. Booting from the network is very usefull when you have unsupported I/O devices, diskless systems, or systems with broken hardware. Network booting is detailed below. </P ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="preparingnetboot" ></A >4.3.1. Preparing to boot from network</H2 ><DIV CLASS="highlights" ><A NAME="AEN1010" ></A ><P > Booting from the network involves two machines: the <EM >boot server</EM > and the <EM >boot client</EM >, the latter being the PA-RISC system you are trying to start up, and the former, the machine that will serve over the network the files which the client needs. The rest of this section will extensively deal with setting up the <EM >boot server</EM > since this is probably the trickiest part. </P ></DIV ><DIV CLASS="important" ><P ></P ><TABLE CLASS="important" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/important.gif" HSPACE="5" ALT="Important"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > You will need a <EM >lifimage</EM > to perform a network boot. See <A HREF="whatdoespalo.html" >Section 3.2</A > to learn how to create one. You can also use the one from <A HREF="http://ftp.debian.org/debian/dists/sarge/main/installer-hppa/current/images/netboot/2.6/boot.img" TARGET="_top" > Debian Installer</A >. </P ></TD ></TR ></TABLE ></DIV ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > Needless to say, all server-side setup is meant to be performed by the <EM >super-user</EM >, also known as <TT CLASS="literal" >root</TT >. </P ></TD ></TR ></TABLE ></DIV ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="rbootorbootp" ></A >4.3.2. rboot or bootp?</H2 ><DIV CLASS="highlights" ><A NAME="AEN1026" ></A ><P > All 'recent' machines can boot using <TT CLASS="literal" >BOOTP</TT >, starting from 715/100, 715/120, and 712s. Older ones, mostly early 715s, 710s and 725s need <TT CLASS="literal" >RBOOT</TT >. </P ></DIV ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > To use <TT CLASS="literal" >BOOTP</TT > you have to enable the <SPAN CLASS="guimenu" >IP: Kernel level autoconfiguration</SPAN >-><SPAN CLASS="guimenuitem" >IP: BOOTP support</SPAN > within the '<TT CLASS="literal" >Networking options</TT >' section of the kernel configuration, if you want to use a <EM >home-made</EM > kernel. See <A HREF="vmlinux.html" >Chapter 5</A > for details. </P ></TD ></TR ></TABLE ></DIV ><P > Please note that though <A HREF="bootnetwork.html#usingrbootd" >Section 4.3.3</A > deals with <TT CLASS="literal" >RBOOT</TT > only, two different implementations of the <TT CLASS="literal" >BOOTP</TT > protocol are detailed in <A HREF="bootnetwork.html#usingdhcp" >Section 4.3.4</A > and <A HREF="bootnetwork.html#usingbootp" >Section 4.3.5</A >. We detail these two <EM >because we can</EM >, but if you need to use the <TT CLASS="literal" >BOOTP</TT > protocol, you will have to choose one. </P ><DIV CLASS="tip" ><P ></P ><TABLE CLASS="tip" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/tip.gif" HSPACE="5" ALT="Tip"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > If you don't know which <TT CLASS="literal" >BOOTP</TT > implementation to use, go for the <B CLASS="command" >dhcp</B > one, it is much easier to deal with. </P ></TD ></TR ></TABLE ></DIV ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="usingrbootd" ></A >4.3.3. Using rboot</H2 ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN1053" ></A >4.3.3.1. Obtaining rbootd</H3 ><P > If you have an old machine that requires <B CLASS="command" >rboot</B > to boot over network, use the following procedure to set up and configure a boot server, and boot using the PA-RISC/Linux kernel. </P ><P > Old machines, including the Scorpio 715s, use the <TT CLASS="literal" >RBOOT</TT > protocol. You need <B CLASS="command" >rbootd</B > to handle their boot requests. Look for it in your favorite distribution archive (assuming you will be servicing boot requests from a Linux box). Here are two ways of getting the <B CLASS="command" >rboot</B > daemon: </P ><P ></P ><UL ><LI ><P > If you are using a Debian-powered server (which you really should be doing ;o), you're almost done. Run from a command shell: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > <TT CLASS="prompt" >[user@machine ~/dir]></TT > <B CLASS="command" >apt-get</B > <TT CLASS="userinput" ><B >install rbootd</B ></TT > </PRE ></FONT ></TD ></TR ></TABLE ></LI ><LI ><P > If you can't find any <B CLASS="command" >rbootd</B > package for your system (which is very possible since it is a very old netboot protocol), you can find its source in the Debian archive: <A HREF="http://packages.debian.org/stable/net/rbootd.html" TARGET="_top" >rbootd</A >. You will have to build it from source. </P ></LI ></UL ></DIV ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="rbootd" ></A >4.3.3.2. Configuring rbootd</H3 ><P > As we already said, to boot a <TT CLASS="literal" >RBOOT</TT >-aware system, you need a separate machine with <B CLASS="command" >rbootd</B > installed (this is the 'boot server') on which you will store the PA-RISC/Linux kernel <EM >lifimage</EM > that you want to use to boot your PA-RISC system with. </P ><P > Once the <B CLASS="command" >rbootd</B > server software is installed, read the following to configure it to work with your PA-RISC system: </P ><P > In <TT CLASS="filename" >/etc/rbootd.conf</TT > you will have to add a line like: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" >ethernet_addr bootfile</PRE ></FONT ></TD ></TR ></TABLE ><P ></P ><OL TYPE="1" ><LI ><P > Replace <TT CLASS="replaceable" ><I >bootfile</I ></TT > with the name of your PA-RISC/Linux kernel image, usually '<TT CLASS="filename" >lifimage</TT >'. </P ></LI ><LI ><A NAME="getmac" ></A ><P > Now get the Ethernet address of your PA-RISC system by typing <B CLASS="command" >lanaddress</B > at the '<TT CLASS="computeroutput" >BOOT_ADMIN></TT >' prompt (see <A HREF="bootadmin.html#bootadminfo" >Section 2.1.2.3</A >). </P ><P > It will return a number like <TT CLASS="computeroutput" >080009-7004b6</TT >. Take note of this number. </P ></LI ><LI ><P > In <TT CLASS="filename" >/etc/rbootd.conf</TT > on your boot server, the Ethernet address has to be colon-delimited. That means you will have to modify the number you just obtained so that every set of two characters (after removing the '-') is separated by a colon. For example: <TT CLASS="computeroutput" >080009-7004b6</TT > becomes <TT CLASS="computeroutput" >08:00:09:70:04:b6</TT >. Add the colon delimited Ethernet address to <TT CLASS="filename" >/etc/rbootd.conf</TT > on your boot server. The resulting file will look something like this: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > # ethernet addr boot file comments 08:00:09:87:e4:8f lifimage_715 # PA/Linux kernel for 715/33 08:00:09:70:04:b6 lifimage_720 # PA/Linux kernel for 720 </PRE ></FONT ></TD ></TR ></TABLE ><P > This <TT CLASS="filename" >rbootd.conf</TT > example contains the Ethernet addresses and boot file names for two different machines. </P ><P > Once you have changed the configuration file, restart <B CLASS="command" >rbootd</B >. </P ></LI ></OL ><P > By default, <B CLASS="command" >rbootd</B > assumes that bootfiles are located in <TT CLASS="filename" >/var/lib/rbootd/</TT >. Therefore, you will have to put your bootable kernel image in that directory, or, if you really hate that directory for some reason, you can rebuild <B CLASS="command" >rbootd</B > to use a different directory. </P ><P > The easiest thing, of course, is just to drop your kernel images in the default directory! </P ></DIV ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="usingdhcp" ></A >4.3.4. Using dhcp/tftp</H2 ><P > We will see here how to setup a <TT CLASS="literal" >DHCP</TT > server to handle <TT CLASS="literal" >BOOTP</TT > requests (since PA-RISC box use <TT CLASS="literal" >BOOTP</TT >, unless they need <TT CLASS="literal" >RBOOT</TT >, as mentioned above). </P ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > <SPAN CLASS="trademark" >Windows</SPAN >™ users might want to look at <A HREF="win2kdhcp.html" >Appendix A</A >. </P ></TD ></TR ></TABLE ></DIV ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN1122" ></A >4.3.4.1. Obtaining dhcp/tftp</H3 ><P > Debian users will just have to install the packages using the following commands, executed as <TT CLASS="literal" >root</TT >: </P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > <TT CLASS="prompt" >[user@machine ~/dir]></TT > <B CLASS="command" >apt-get</B > <TT CLASS="userinput" ><B >install dhcp tftpd</B ></TT > </PRE ></FONT ></TD ></TR ></TABLE ><P > If you need rpm packages (for the ISC dhcp server), the best way is to go to <A HREF="http://rpmfind.net/" TARGET="_top" >http://rpmfind.net/</A >. </P ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > The dhcp package can do much more than a simple bootp daemon. Nevertheless, it is also known to be much easier to configure. If you really want to try regular <B CLASS="command" >bootp</B >, skip this and go to <A HREF="bootnetwork.html#usingbootp" >Section 4.3.5</A >. </P ></TD ></TR ></TABLE ></DIV ></DIV ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN1136" ></A >4.3.4.2. Configuring dhcp/tftp</H3 ><P > Here are the instructions to set up <B CLASS="command" >dhcp</B > on your boot server. To keep this explanation simple, we will assume that you want to assign a fixed IP to your box, without DNS update. Your subnet will be <TT CLASS="literal" >192.168.1.0/24</TT >, with optional: gateway at <TT CLASS="literal" >192.168.1.1</TT >, domain name <TT CLASS="literal" >foo.com</TT > and DNS at <TT CLASS="literal" >192.168.1.4</TT >. Feel free to replace these values with those which would suit your needs in the next sections. </P ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > This section is dedicated to Debian users. For others distributions, it should be similar though there may be some differences like default directories. </P ></TD ></TR ></TABLE ></DIV ><P ></P ><OL TYPE="1" ><LI ><P > Edit <TT CLASS="filename" >/etc/inetd.conf</TT > on your boot server to add the following line, if it doesn't already exist: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > tftp dgram udp wait nobody /usr/sbin/tcpd \ /usr/sbin/in.tftpd /tftpboot </PRE ></FONT ></TD ></TR ></TABLE > Here, <TT CLASS="filename" >/tftpboot/</TT > is being used as tftpd server's root (this is where you will put the <EM >lifimage</EM > file). You can choose another directory if you want. According to <B CLASS="command" >man tftpd</B >, this is the usual default directory. </P ><P > When this is done, reload <B CLASS="command" >inetd</B > with: <B CLASS="command" >/etc/init.d/inetd reload</B >. Non-Debian users can also issue a <B CLASS="command" >killall -HUP inetd</B >. </P ></LI ><LI ><P > According to <B CLASS="command" >man 5 dhcpd.conf</B >, edit the <TT CLASS="filename" >/etc/dhcpd.conf</TT > file to contain something like: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > allow bootp; default-lease-time 600; max-lease-time 7200; # This will tell the box its hostname while booting: use-host-decl-names on; subnet <TT CLASS="replaceable" ><I >192.168.1.0</I ></TT > netmask 255.255.255.0 { option routers <TT CLASS="replaceable" ><I >192.168.1.1</I ></TT >; option domain-name "<TT CLASS="replaceable" ><I >foo.com</I ></TT >"; option domain-name-server <TT CLASS="replaceable" ><I >192.168.1.4</I ></TT >; } host <TT CLASS="replaceable" ><I >[hostname]</I ></TT > { hardware ethernet <TT CLASS="replaceable" ><I >[mac address]</I ></TT >; fixed-address <TT CLASS="replaceable" ><I >[ip address]</I ></TT >; filename "<TT CLASS="replaceable" ><I >[boot filename]</I ></TT >"; option root-path "<TT CLASS="replaceable" ><I >[root path]</I ></TT >"; } </PRE ></FONT ></TD ></TR ></TABLE > You have to fill in the <TT CLASS="replaceable" ><I >[hostname]</I ></TT >, <TT CLASS="replaceable" ><I >[mac address]</I ></TT >, <TT CLASS="replaceable" ><I >[ip address]</I ></TT >, <TT CLASS="replaceable" ><I >[boot filename]</I ></TT > and <TT CLASS="replaceable" ><I >[root path]</I ></TT > fields with the appropriate information, where: </P ><P ></P ><UL ><LI ><P > <TT CLASS="replaceable" ><I >[hostname]</I ></TT > is the name of the PA-RISC system. </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[mac address]</I ></TT > is the colon-delimited ethernet address of the PA-RISC system, which can be obtained by typing <B CLASS="command" >lanaddress</B > at the '<TT CLASS="computeroutput" >BOOT_ADMIN></TT >' prompt (see <A HREF="bootadmin.html#bootadminfo" >Section 2.1.2.3</A >). </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[ip address]</I ></TT > is the IP address you wish to assign to the PA-RISC system. </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[boot filename]</I ></TT > is the name of the bootable kernel image you want to boot your system with. </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[root path]</I ></TT > is the path to the NFS root filesystem exported by the server. </P ></LI ><LI ><P > Additionally, if the tftp server you want to use is not the same as the one running the dhcp server, you can add <TT CLASS="computeroutput" >next-server <TT CLASS="replaceable" ><I >[ip address]</I ></TT >;</TT >, replacing <TT CLASS="replaceable" ><I >[ip address]</I ></TT > with the actual IP of the tftp server, to the dhcp configuration. </P ></LI ></UL ><P > You'll end up with something like this for each box you want to <EM >netboot</EM >: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > host tatooine { hardware ethernet 00:40:05:18:0c:dd; fixed-address 192.168.1.22; filename "lifimage-tatooine"; option root-path "/exports/tatooineroot"; } </PRE ></FONT ></TD ></TR ></TABLE > </P ></LI ></OL ></DIV ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="usingbootp" ></A >4.3.5. Using bootp/tftp</H2 ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN1206" ></A >4.3.5.1. Obtaining bootp/tftp</H3 ><P > For Debian users, you just have to install the packages by typing these commands as user <TT CLASS="literal" >root</TT >: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > <TT CLASS="prompt" >[user@machine ~/dir]></TT > <B CLASS="command" >apt-get</B > <TT CLASS="userinput" ><B >install bootp tftpd</B ></TT > </PRE ></FONT ></TD ></TR ></TABLE > If you need rpm packages, the best way is to go to <A HREF="http://rpmfind.net/" TARGET="_top" >http://rpmfind.net/</A >. </P ><DIV CLASS="warning" ><P ></P ><TABLE CLASS="warning" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/warning.gif" HSPACE="5" ALT="Warning"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > You'll have been warned! This daemon is far more obfuscated in its configuration. </P ></TD ></TR ></TABLE ></DIV ></DIV ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN1217" ></A >4.3.5.2. Configuring bootp/tftp</H3 ><P > Follow these instructions to use the <B CLASS="command" >bootp</B > daemon on your boot server: </P ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > This section is dedicated to Debian users. For others distributions, it should be similar though there may be some differences like default directories. </P ></TD ></TR ></TABLE ></DIV ><P ></P ><OL TYPE="1" ><LI ><P > Edit <TT CLASS="filename" >/etc/inetd.conf</TT > on your boot server to add the following lines, if they don't already exist: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > tftp dgram udp wait nobody /usr/sbin/tcpd \ /usr/sbin/in.tftpd /tftpboot bootps dgram udp wait root /usr/sbin/bootpd \ bootpd -i -t 120 </PRE ></FONT ></TD ></TR ></TABLE > Here, <TT CLASS="filename" >/tftpboot/</TT > is being used as tftpd server's root (this is where you will put the <EM >lifimage</EM > file). You can choose another directory if you want. According to <B CLASS="command" >man tftpd</B >, this is the usual default directory. </P ><P > When this is done, reload <B CLASS="command" >inetd</B > with: <B CLASS="command" >/etc/init.d/inetd reload</B >. Non-Debian users can also issue a <B CLASS="command" >killall -HUP inetd</B >. </P ></LI ><LI ><P > According to <B CLASS="command" >man 5 bootptab</B >, edit the <TT CLASS="filename" >/etc/bootptab</TT > file to contain: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > <TT CLASS="replaceable" ><I >[hostname]</I ></TT >:hd=/tftpboot:\ :rp=<TT CLASS="replaceable" ><I >[root path]</I ></TT >:\ :ht=ethernet:\ :ha=<TT CLASS="replaceable" ><I >[mac address]</I ></TT >:\ :ip=<TT CLASS="replaceable" ><I >[ip address]</I ></TT >:\ :bf=<TT CLASS="replaceable" ><I >[boot filename]</I ></TT >:\ :sm=255.255.255.0:\ :to=7200: </PRE ></FONT ></TD ></TR ></TABLE > You have to fill in the <TT CLASS="replaceable" ><I >[hostname]</I ></TT >, <TT CLASS="replaceable" ><I >[mac address]</I ></TT >, <TT CLASS="replaceable" ><I >[ip address]</I ></TT > and <TT CLASS="replaceable" ><I >[root path]</I ></TT > fields with the appropriate information, where: </P ><P ></P ><UL ><LI ><P > <TT CLASS="replaceable" ><I >[hostname]</I ></TT > is the name of the PA-RISC system. </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[mac address]</I ></TT > is the NOT-delimited ethernet address of the PA-RISC system, which can be obtained by typing <B CLASS="command" >lanaddress</B > at the '<TT CLASS="computeroutput" >BOOT_ADMIN></TT >' prompt (see <A HREF="bootadmin.html#bootadminfo" >Section 2.1.2.3</A >). </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[ip address]</I ></TT > is the IP address you wish to assign to the PA-RISC system. </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[boot filename]</I ></TT > is the name of the bootable kernel image you want to boot your system with. </P ></LI ><LI ><P > <TT CLASS="replaceable" ><I >[root path]</I ></TT > is the path to the NFS root filesystem exported by the server. </P ></LI ></UL ><P >You'll end up with something like this:</P ><TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > vodka:hd=/tftpboot:\ :rp=/usr/src/parisc/:\ :ht=ethernet:\ :ha=080069088717:\ :ip=140.244.9.208:\ :bf=lifimage:\ :sm=255.255.255.0:\ :to=7200: </PRE ></FONT ></TD ></TR ></TABLE ></LI ></OL ></DIV ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="realnetboot" ></A >4.3.6. Effectively booting from network</H2 ><DIV CLASS="highlights" ><A NAME="AEN1272" ></A ><P > To conclude with the developers' way to boot the kernel, this section will tell you how to actually boot your system from a network server. But it tends to be less and less used. Most users will prefer to stick to <A HREF="boothd.html" >Section 4.2</A > once their system is properly setup. </P ></DIV ><P > Here we are. We assume that you've done everything outlined above, your network boot server is on the same physical subnet as your PA-RISC machine, you've got a bootable PA/Linux kernel lifimage on your boot server, and you're willing to give it a try. If everything is ready (including you!), the following procedure will introduce you to the joy of network booting your PA box into Linux. </P ><P ></P ><OL TYPE="1" ><LI ><P >Fire up your PA-RISC system.</P ></LI ><LI ><P > Watch your PA-RISC box starting up. When the following message appears during the PA-RISC machine's boot process, press and hold the <B CLASS="keycap" >Esc</B > key: <TABLE BORDER="0" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="programlisting" > Searching for Potential Boot Devices. To terminate search, press and hold the ESCAPE key. </PRE ></FONT ></TD ></TR ></TABLE > </P ></LI ><LI ><P > If needed, select '<TT CLASS="computeroutput" >a) Enter Boot Administration mode</TT >' from the menu. This brings up the '<TT CLASS="computeroutput" >BOOT_ADMIN></TT >' prompt. </P ></LI ><LI ><P > Type the following at the prompt: <B CLASS="command" >boot lan</B >. </P ></LI ><LI ><P > Watch your PA-RISC system magically becoming a PA/Linux system. Ta dah! </P ></LI ></OL ><DIV CLASS="note" ><P ></P ><TABLE CLASS="note" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > Of course your are supposed to run only one boot server at a time on your network, in order to avoid conflicts... </P ></TD ></TR ></TABLE ></DIV ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="boothd.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="vmlinux.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Booting from hard drive</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="bootsolutions.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Building and installing a custom kernel</TD ></TR ></TABLE ></DIV ></BODY ></HTML >