[src/trunk]: src/distrib/notes/hp300 move netboot stuff to ../common/netboot

[mbw <mbw%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/7c7f4384f701
branches:  trunk
changeset: 526413:7c7f4384f701
user:      mbw <mbw%NetBSD.org@localhost>
date:      Fri May 03 05:18:14 2002 +0000

description:
move netboot stuff to ../common/netboot
major overhaul

diffstat:

 distrib/notes/hp300/prep |  689 ++++++++++++++++++++++++++++++++++++----------
 1 files changed, 535 insertions(+), 154 deletions(-)

diffs (truncated from 750 to 300 lines):

diff -r 3bed98480e4d -r 7c7f4384f701 distrib/notes/hp300/prep
--- a/distrib/notes/hp300/prep  Fri May 03 05:17:30 2002 +0000
+++ b/distrib/notes/hp300/prep  Fri May 03 05:18:14 2002 +0000
@@ -1,21 +1,137 @@
-.\"    $NetBSD: prep,v 1.11 2002/04/23 05:56:44 gmcgarry Exp $
+.\"    $NetBSD: prep,v 1.12 2002/05/03 05:18:14 mbw Exp $
 .
-Currently, only installing the miniroot from the network is supported.
-A ramdisk kernel with the sysinst installation utility is provided on
-the installation media, however it has not been extensively tested.
+There are two installation tools available.  The traditional miniroot
+installer is script-based and may be netbooted or may be dumped to a disk
+and run locally.   The ramdisk kernel with the sysinst installation
+utility is more flexible, but can only be netbooted and has not been
+extensively tested.
+.Pp
+There are several possible installation configurations described in this
+document.  Other configurations are possible, but less common.  If you are
+unable to install based on the information in this document, post a
+message to 
+.Mt port-hp300%netbsd.org@localhost
+asking for help.  The configurations described in this document are as follows:
+.Pp
+.(bullet -compact
+\*M netboots
+.Li SYS_UBOOT
+and then runs the miniroot installation tools or a purely diskless
+installation from a 
+.Nx
+server on the same subnet (you must have root access).
+Other server platforms will work, but are described in the NetBSD Diskless
+HOW-TO.  
+.Lk http://www.netbsd.org/Documentation/network/netboot/
+.Pp
+.It
+\*M loads 
+.Li SYS_UBOOT
+from a local disk, tape, or floppy
+and then runs the miniroot installation tools or a purely diskless
+installationf rom a 
+.Nx
+server on the same subnet (you must have root access).  
+Other server platforms will work, but are described in the NetBSD Diskless
+HOW-TO.  
+.Lk http://www.netbsd.org/Documentation/network/netboot/
+You will need
+.Tn HP-UX
+on your \*M if it does not have a SCSI interface or a floppy drive.
 .Pp
-You will need information about your disk's geometry, based on 512-byte
-sectors. You must have this information before proceeding. The
-file
-.Pa .../installation/misc/HP-IB.geometry
-has geometry information for
+.It
+\*M loads 
+.Li SYS_INST
+from a local disk.  You partition the drive
+and then run the miniroot installation tools from that drive.
+You will need
+.Tn HP-UX
+on your \*M if it does not have a SCSI interface.
+.bullet)
+The preferred method is to use another
+.Nx
+server to netboot the \*M client.  This procedure will not
+work on the handful of models which are incapable of netbooting.
+In particular, the 320, 350, 330, 318, and
+319 might not have a recent enough BootROM. The BootROM revision is
+printed when your workstation is first powered on (or
+rebooted). Revision B or later will definitely work. BootROMs with
+numeric revisions such as 1.1 (on a 400s) will netboot without any
+problems.   You can netboot from any built-in or add-on ethernet board on
+a model with a supported BootROM.
+.Pp
+If you have access to a
+.Nx*M
+system, it is 
+.Em much
+easier to simply upgrade than to install from scratch.  Skip down to the
+section on
+.Sx Upgrading a previously-installed NetBSD System 
+.
+.Ss2 Formatting your hard drives
+.
+.Nx*M
+does not have the capability to perform a low-level format of hard
+drives.  SCSI disks can be formatted on any platform with SCSI support and
+then used on 
+.Nx*M .
+HP-IB disks can only be formatted by the
+.Tn HP-UX 
+.Xr mediainit 1
+command.  You may need to first create the device nodes for your disk, as
+.Tn HP-UX
+was never very good about populating
+.Pa /dev/rdsk
+propertly.
+.(disp
+.No # Ic "mknod /dev/dsk/IDs0 b 0 0xSCID00"
+.No # Ic "mknod /dev/rdsk/IDs0 c 4 0xSCID00"
+.No # Ic "mediainit -v /dev/rdsk/IDs0"
+.disp)
+.(item
+.Em ID
+is the HP-IB address (a.k.a. slave) of the disk in hexadecimal.
+This is usually between 
+.Li 00
+and
+.Li 07 ,
+but possibly up to
+.Li 1F 
+(31 decimal) .
+.item)
+.(item
+.Em SC
+is the Select Code of the disk controller.
+This is usually 
+.Li 07
+for slow (i.e. built-in) HP-IB or
+.Li 0E
+(14 decimal) for SCSI or fast HP-IB.
+.item)
+.
+.Ss2 Designing your disk's partition table
+.
+This step can sometimes be a real pain, especially when using
+.Pa SYS_INST .
+It's best to calculate it ahead of time.
+.Pp
+If you are installing to an HP-IB disk,
+you will need information about your disk's geometry, based on 512-byte
+sectors.  The file
+.Pa installation/misc/HP-IB.geometry
+in the distribution has geometry information for
 several HP-IB disks, but may be incomplete. Geometry may be calculated
 from an HP-UX
 .Pa /etc/disktab
 entry, but note that HP-UX geometry is based
 on 1024 byte sectors, while
 .Nx 's
-is based on 512 byte sectors.
+is based on 512 byte sectors.  You should have all partitions start on
+cylinder boundaries.
+.Pp
+If you are installing to a SCSI disk, you don't need to worry about the
+details of the geometry.  Just create a disklabel based on the total
+number of sectors available on the disk.
 .Pp
 .Em A quick note about partitions:
 Since the target disk will become the boot
@@ -28,13 +144,14 @@
 partitions in a special manner. Due to the size of the
 .Nx*M
 boot program (it spills into the area after the disklabel),
-it is necessary to offset the
+it is necessary to offset the beginning of the
 .Sq Li a
-partition one cylinder from the beginning
-of the disk. Later, the
+partition.  For HP-IB disks, it is best to offset it by one cylinder from
+the beginning of the disk.  For SCSI disks, just offset it by 100 KB (200
+sectors).  Later, the
 .Sq Li c
 partition will be marked with the type
-.Li FS_BOOT
+.Sq Li boot
 and may not be used for a file system. (For those unfamiliar
 with historic
 .Bx
@@ -45,133 +162,377 @@
 or the
 .Sq raw partition . )
 .Pp
-.Em A quick note about disk numbers:
-While in the SYS_INST program, you
-may use different unit numbers for the disks than when the
+Here is a table of recommended partition sizes for a full install:
+.Bl -column -offset indent Partition Suggested Needed
+.It Partition Ta Suggested Ta Needed
+.It /\ (root) Ta "25 MB"   Ta "15 MB"
+.It /usr      Ta "150 MB"  Ta "100 MB"
+.It /var      Ta "20 MB"   Ta "5 MB"
+.It swap      Ta Em "2-3 *RAM" Ta 6 MB
+.El
+.Pp
+.(Note
+You will need at least a 6 MB swap partition if you are unable to netboot
+the installer, as the miniroot is temporarily placed in this partition.
+.Note)
+.Pp
+Here is an example disklabel from a 7959B HP-IB hard drive:
+.(disp
+# /dev/rrd0a:
+type: HP-IB
+disk: rd7959B
+label: 
+flags:
+bytes/sector: 512
+sectors/track: 42
+tracks/cylinder: 9
+sectors/cylinder: 378
+cylinders: 1572
+total sectors: 594216
+rpm: 3600
+interleave: 1
+trackskew: 0
+cylinderskew: 0
+headswitch: 0           # milliseconds
+track-to-track seek: 0  # milliseconds
+drivedata: 0 
+
+8 partitions:
+#        size   offset    fstype   [fsize bsize   cpg]
+  a:    37800      378    4.2BSD     1024  8192    16   #
+  b:    66150    38178      swap     1024  8192    16   #
+  c:   594216        0      boot                        # (Cyl.    0 - 1571)
+  d:   489888   104328    4.2BSD     1024  8192    16   #
+.disp)
+.
+.Ss2 Installing the bootstrap program locally
+.
+For earlier models incapable of netbooting, you need to install the
+bootstrap program on a bootable local device, such as a hard disk, floppy
+disk, or tape drive.  If you will be booting the miniroot over the
+network, then you will be installing 
+.Pa installation/misc/SYS_UBOOT .
+.Pp
+If you do not have access to a netboot server to serve the miniroot
+installer, you can use a primitive bootstrap program
+.Pa installation/misc/SYS_INST 
+to load the miniroot from a locally attached device (such as a
+disk, tape or CD-R).  This is not recommended, as 
+.Pa SYS_INST
+is difficult to use, buggy, and provides no error checking when
+partitioning your disk.
+.Pp
+If your system has SCSI, this is easy.  Just take a
+scratch SCSI disk (hard disk, zip disk, or CD-R) and use any computer
+to dump the bootstrap program to it.  For example, to dump it to the
+.Li sd1
+disk on a non-i386 platform:
+.(disp
+.No # Ic "dd if=SYS_UBOOT of=/dev/sd1c"
+.disp)
+.Pp
+If your system has a floppy drive, you can write the bootstrap program to
+it using any computer with a floppy drive.  You will need to dump it using
+a utility like
+.Ic rawrite
+or
+.Xr dd 1 .
+Make sure to read back from the floppy to verify that the file has been
+written correctly.
+.Pp
+If your system does not have SCSI or a floppy drive, you will need a
+bootable operating system on your \*M so you can write files to the HP-IB
+device. You should probably write the bootstrap program to the disk you
+will be installing
+.Nx
+onto.
+.Pp
+Using
+.Tn HP-UX 
+to write to an HP-IB disk:
+.(disp
+.No # Ic "dd if=SYS_UBOOT of=/dev/rdsk/IDs0"
+.disp)
+.(item
+.Em ID
+is the HP-IB address (a.k.a. slave) of the disk in hexadecimal.
+This is usually between 
+.Li 00
+and
+.Li 07 ,
+but possibly up to
+.Li 1F 
+(31 decimal) .
+.item)
+.Pp
+Using
+.Tn HP-UX 
+to write to an HP-IB tape:
+.(disp
+.No # Ic "dd if=SYS_UBOOT of=/dev/rmt/0mnb obs=20b conv=sync"
+.disp)
+.
+.Ss2 Installing the miniroot filesystem locally
+.
+This step is only necessary if you are not loading the miniroot
+installer from a netboot server.
+Follow the same procedure for the bootstrap program, except use the 
+uncompressed miniroot filesystem 
+.No ( Pa installation/miniroot/miniroot.fs.gz No )
+instead of the bootstrap program.
+The only quirk is that you should place it at the offset of the swap
+partition you calculated above in the disklabel.  In the example disklabel
+above, the offset is 38178 sectors of 512 bytes.  Therfore, the 
+.Xr dd 1
+command would be something like: