From d6583bb2a13f329cf0332ef2570eb8bb8fc0e39c Mon Sep 17 00:00:00 2001 From: Theo de Raadt Date: Wed, 18 Oct 1995 08:53:40 +0000 Subject: initial import of NetBSD tree --- sys/arch/sun3/stand/README | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 sys/arch/sun3/stand/README (limited to 'sys/arch/sun3/stand/README') diff --git a/sys/arch/sun3/stand/README b/sys/arch/sun3/stand/README new file mode 100644 index 00000000000..2997060575b --- /dev/null +++ b/sys/arch/sun3/stand/README @@ -0,0 +1,35 @@ +/* $NetBSD: README,v 1.2 1995/08/12 18:38:30 gwr Exp $ */ + +The sun bootblocks are split into two parts: a small 1st-level program that +gets written right after the superblock in a partition (and is hence limited +in size to SBSIZE - DEV_BSIZE bytes), and a 2nd-level program that resides +in the filesystem proper. + +The 1st-level program is loaded into memory by the PROM. It loads the second +stage program from a set of filesystem block numbers that are hard-coded +into it by the `installboot' program. The prototype code for the 1st-level +bootblocks are in `bootxx'. + +The 2nd-level program (`ufsboot') is normally installed in the root FS +as `/ufsboot'. It uses the device drivers in the PROM and the stand-alone +filesystem code in `libsa.a' to locate and load the kernel. + +Use the following command to install the 1st-level bootblocks in the +root filesystem (on `sd0a') using the file `/boot' as the second level +boot program: + + mount /dev/sd0a /mnt + installboot /mnt/ufsboot bootxx /dev/rsd0a + +The above only works with securelevel <= 0 (see init.8 manual). + +Status: + +netboot works. + +bootxx, installboot are tested and working. It would be nice if +installboot would find the inumber for the 2nd stage boot program +without having the filesystem mounted so this command can work +with securelevel==1 (the default). Doing this requies adding +code to read and do a directory lookup in the root... + -- cgit v1.2.3