-Systems boot to multi-user and full snapshots are made periodically.
-There are several projects being under development to support
-SCSI controllers and input devices,
-to solve certain stability issues.
+OpenBSD/hppa runs on a large set of the 32-bit Hewlett Packard Precision
+Architecture workstations and servers (HP PA-RISC).
+
+
+
+A mailing list dedicated to the OpenBSD/hppa port is available at
+hppa@openbsd.org.
+To join the OpenBSD/hppa mailing list, send a message body of "subscribe
+hppa" to majordomo@openbsd.org.
+Please be sure to check our mailing list policy before
+subscribing.
+
+
+
+The current port maintainer is
+Michael Shalayeff.
+Others are definitely welcome to contribute!
+
This project was started in those days when the only
open source operating systems for HP PA-RISC computers were
Lites and
@@ -33,78 +69,187 @@
is encumbered by HP proprietary code and USL licensing and is
not publicly available.
One of the major direct benefits from previous porting efforts
-(besides the code, of course ;) is
-support for HP PA-RISC in GCC and binutils, which allowed quick
-building of a cross-tools environment for development.
+(besides the code, of course) was support for HP PA-RISC in GCC and
+binutils, which allowed quick building of a cross-tools environment
+for development.
+
+
-Later on HP decided to sponsor a
-Linux port to PA-RISC
-machines which actually resulted in some proprietary documentation
-release, even though they target a different class of 9000 machines.
+Later on, Hewlett-Packard decided to sponsor a
+Linux port to the PA-RISC
+family, which actually resulted in some proprietary documentation
+being released, even though their target was a different class of 9000
+machines back then.
+
+
+
+
+
Current status:
+
+Although there have been no official releases of this port yet,
+the supported systems boot to multi-user and full snapshots are made
+periodically.
+
-
Supported Hardware:
+
+Currently, no storage devices are supported, so the only way to run this
+port is in a diskless environment.
+
-
-Hardware is needed for this project,
-see "Wanted List"
+
+
+
+
Supported peripherals
+
+
+
+The list of supported hardware below is not meant to be exhaustive.
+Hardware is needed for developers, to further help development and testing.
+Please see our "Wanted List"
(contact mickey).
+
-One will have a boot.lif
-file to boot then in the obj-directory.
-That image may include diskless kernel image if one was available
-in the sys/arch/hppa/compile/SHEPHERD_PIE/bsd.
-
-Kernel cross-build process is similar to the one for boot, consult
-config(8)
-and
-options(8)
-for kernel build options and configuration.
+Snapshots are made available from time to time, in
+this location
+as well as in a few
+mirrors.
+Here are the
+
+OpenBSD/hppa snapshot installation instructions
+ as well.
+
-In order to use the boot.lif files
-you must prepare your server and instruct your machine to boot off the network:
+
+
Netbooting OpenBSD/hppa:
+
+
+The boot.lif file contains both a bootloader and a kernel.
+To boot it from the network, a server machine has to be setup so as to
+let the hppa machine retrieve it:
Server setup
-
For older machines (705, 7[1235]0, old 715)
- rbootd must be setup and started.
+
For older machines (705, 7[1235]0, old 715)
+ 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:
+
/etc/rbootd.conf contains a single line per machine
+ needing 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 (relative to /usr/mdec/rbootd).
+ For example:
Recent machines (712, new 715, 725) won't look for rbootd at all, but require a
-bootp setup.
+
Recent machines (712, newer 715, 725) will not look for rbootd at all,
+ but instead require a bootp setup.
-
/etc/bootptab contains an information block for each machine. For example:
+
/etc/bootptab
+ contains an information block for each machine. For example:
# 9000/715
boron:\
@@ -207,71 +361,159 @@
- Create directory /tftpboot and put the boot.lif in it.
+ Create directory /tftpboot and put the
+ boot.lif file in it.
- Write an entry for your hppa in the /etc/ethers file:
+ Write an entry for the hppa in /etc/ethers:
08:00:09:5f:5a:6e boron
- Write an entry for 'boron' in the /etc/hosts file:
+ Write another entry for it in /etc/hosts:
10.0.1.143 boron
- Create directory /usr/local/exports/boron/root and put /dev/MAKEDEV,
- /sbin/init, /bin/ksh
- in their relative locations.
+ Create directory /usr/local/exports/boron/root and unpack
+ at least base32.tgz and etc32.tgz in it.
- Write an entry in /etc/exports so the root directory gets exported to the client:
+ After the sets are unpacked, create device nodes in dev/ by
+ running MAKEDEV and alter the configuration files in
+ /etc (refer to the installation notes for details).
+
+
+ Finally, add an entry to /etc/exports in order to export
+ the root directory to the client:
/usr/local/exports/boron/root boron
+ You might want to also create and export a swap area.
- Remember you will have to enable bootpd
- and tftpd
- in /etc/inetd.conf, and restart inetd.
-
+ The last step is to enable the necessary daemons for all of this to
+ work.
+ bootpd
+ and
+ tftpd
+ are usually run from
+ inetd,
+ so /etc/inetd.conf has to be modified and
+ inetd
+ restarted.
For further reading on server setup for network booting in general, see also: diskless(8).
+
For further reading on server setup for network booting in general,
+ please refer to the
+ diskless(8)
+ manual page.
+
Client Network Boot
BOOT_ADMIN
- In order to get to the BOOT_ADMIN prompt, you must hit <esc> as the
- machine is coming up. Once it probes bootable devices, type 'a' for
- the 'BOOT_ADMIN' prompt.
+ In order to get to the BOOT_ADMIN prompt, hit the <esc>
+ key as the machine is coming up. Once it has probed bootable devices,
+ a menu will be displayed; if the prompt is notBOOT_ADMIN,
+ it will be necessary to type ``a'' to access it.
-
network boot command
- Once at the 'BOOT_ADMIN' prompt, type:
+
Network boot command
+ Once at the 'BOOT_ADMIN' prompt, the command
BOOT_ADMIN> boot lan isl
+ will proceed to the bootstrap of boot.lif.
- ... and you are on your way to booting boot.lif!
-
+The OpenBSD source tree provides some cross-compilation facilities.
+First, a set of hppa cross tools (cross compiler, cross binutils, etc) must
+be created:
+
+# cd /usr/src
+# make TARGET=hppa cross-includes cross-binutils cross-gcc
+
+This will build and install the various utilities in /usr/cross/hppa.
+Note that this step must be run as root, or using
+sudo.
+
+
+
+
Building boot.lif using cross-tools
+
+
+
+
Building mkboot
+
+ mkboot is the only specific host tool needed for the boot.lif build.
+
+$ cd /usr/src/sys/arch/hppa/stand/mkboot
+$ MACHINE=hppa make obj depend all
+
+
+
Building the kernel
+
+ The kernel can be configured as usual, and then built using the cross-tools.
+
![[OpenBSD]](images/smalltitle.gif){kind=small}
-www@openbsd.org
-