=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/hppa.html,v retrieving revision 1.44 retrieving revision 1.45 diff -u -r1.44 -r1.45 --- www/hppa.html 2001/05/18 20:48:09 1.44 +++ www/hppa.html 2001/06/04 04:42:10 1.45 @@ -128,6 +128,10 @@
+Currently, the in-tree binutils can't be used to generate cross-tools. +You should use a 2.7 source tree to build them, 2.8 and later will not +work. +
cd /usr/src sudo make TARGET=hppa cross-tools @@ -214,22 +218,48 @@... and you are on your way to booting boot.lif! - +
In order to use the boot.lif files you must prepare your server and instruct your machine to boot off the network: -
- Server setup
-
- -rbootd must be setup and started
-+
- /etc/rbootd.conf contains a single line per machine - you entered to boot from the server. Each line contains the - ethernet address of the client hppa machine, and the filename - to be loaded from the tftp server. For example: +
++
- Server setup
++
-- rbootd must be setup and started.
-
+- For further reading on server setup for network booting in general, see also: diskless(8).
-- Client Network Boot
-+
- BOOT_ADMIN
+
+- Recent machines won't look for rbootd at all, but require a +bootp setup.
+
++
+- /etc/bootptab contains an information block for each machine. For example: +
++ # 9000/715 + boron:\ + ha=0800095f5a6e:\ + bf=boot.lif:\ + hd=:\ + ht=ethernet:\ + ip=192.168.3.43:\ + rp=/netboot/boron/root:\ + sm=255.255.255.0:\ + td=/tftpboot: ++- Remember you will have to enable bootpd in /etc/inetd.conf, and restart inetd. +
+- For further reading on server setup for network booting in general, see also: diskless(8).
+- Client Network Boot
++
- BOOT_ADMIN
In order to get to the BOOT_ADMIN prompt, you must hit \as the machine is coming up. Once it probes bootable devices, type 'a' for the 'BOOT_ADMIN' prompt. @@ -241,13 +271,13 @@