diff --git a/distrib/notes/hp300/contents b/distrib/notes/hp300/contents index e49dfb062998..92aea172da67 100644 --- a/distrib/notes/hp300/contents +++ b/distrib/notes/hp300/contents @@ -1,85 +1,103 @@ -The hp300-specific portion of the NetBSD 1.0 release is found in the -"hp300" subdirectory of the distribution. That subdirectory is layed +The hp300-specific portion of the NetBSD 1.1 release is found in the +"hp300" subdirectory of the distribution. That subdirectory is laid out as follows: -.../NetBSD-1.0/hp300/ +.../NetBSD-1.1/hp300/ binary/ hp300 binary distribution sets; see below. - install/ installation utilities and - bootstrap root filesystem - image; see below. + install/ a GENERIC kernel, installation + utilities and a miniroot filesystem; + see below. security/ hp300 security distribution; - see below; + see below. The NetBSD/hp300 binary distribution sets contain the binaries which -comprise the NetBSD 1.0 release for the hp300. There are seven binary +comprise the NetBSD 1.1 release for the hp300. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in the "hp300/binary" subdirectory of -the NetBSD 1.0 distribution tree, and are as follows: +the NetBSD 1.1 distribution tree, and are as follows: - base10 The NetBSD/hp300 1.0 base binary distribution. You + base11 The NetBSD/hp300 1.1 base binary distribution. You MUST install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. - [ 6.1M gzipped, 16.3M uncompressed ] + [ 7.2M gzipped, 19M uncompressed ] - comp10 The NetBSD/hp300 Compiler tools. All of the tools - relating to C, C++, and FORTRAN (yes, there are two!). - This set includes the system include files - (/usr/include), the linker, the compiler tool chain, - and the various system libraries (except the shared - libraries, which are included as part of the base - set). This set also includes the manual pages for all - of the utilities it contains, as well as the system + comp11 The NetBSD/hp300 Compiler tools. All of the tools + relating to C and C++. This set includes the system + include files (/usr/include), the linker, the compiler + tool chain, and the various system libraries (except + the shared libraries, which are included as part of the + base set). This set also includes the manual pages for + all of the utilities it contains, as well as the system call and library manual pages. - [ 4.1M gzipped, 12.6M uncompressed ] + [ 4.6M gzipped, 14.7M uncompressed ] - etc10 This distribution set contains the system - configuration files that reside in /etc and in several - other places. This set MUST be installed if you are - installing the system from scratch, but should NOT be - used if you are upgrading. (If you are upgrading, - it's recommended that you get a copy of this set and - CAREFULLY upgrade your configuration files by hand.) - [ 51K gzipped, 290K uncompressed ] + etc11 This distribution set contains the system configuration + files that reside in /etc and in several other places. + This set MUST be installed if you are installing the + system from scratch, but should NOT be used if you are + upgrading. (If you are upgrading, it's recommended that + you get a copy of this set and CAREFULLY upgrade your + configuration files by hand.) + [ 64K gzipped, 348K uncompressed ] - games10 This set includes the games and their manual pages. - [ 1.1M gzipped, 2.7M uncompressed ] + games11 This set includes the games and their manual pages. + [ 2.8M gzipped, 6.8M uncompressed ] - man10 This set includes all of the manual pages for the + man11 This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. - [ 752K gzipped, 2.9M uncompressed ] + [ 850K gzipped, 3.3M uncompressed ] - misc10 This set includes the system dictionaries (which are + misc11 This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. - [ 1.6M gzipped, 5.6M uncompressed ] + [ 1.8M gzipped, 6.5M uncompressed ] - text10 This set includes NetBSD's text processing tools, + text11 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. - [ 782K gzipped, 2.8M uncompressed ] + [ 770K gzipped, 2.8M uncompressed ] -The hp300 security distribution set is named "secr10" and can be found -in the "hp300/security" subdirectory of the NetBSD 1.0 distribution -tree. It contains crypt.c (the source file for the DES encryption -algorithm) and the binaries which depend on it. It can only be found -on those sites which carry the complete NetBSD distribution and that -can legally obtain it. (Remember, because of United States law, this -distribution set may not be exported to locations outside of the -United States and Canada.) [ 119K gzipped, 270K uncompressed ] +The hp300 security distribution set is named "secr11" and can be found +in the "hp300/security" subdirectory of the NetBSD 1.1 distribution +tree. It contains executables which are built in the "src/domestic" portion +if the NetBSD source tree. It can only be found on those sites which carry +the complete NetBSD distribution and that can legally obtain it. (Remember, +because of United States law, this distribution set may not be exported to +locations outside of the United States and Canada.) +[ 128K gzipped, 275K uncompressed ] The hp300 binary distribution sets are distributed as gzipped tar files. Each hp300 binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. +The following are included in the `.../install' directory: + + SYS_INST.gz A gzipped copy of the SYS_INST miniroot + installation program. + + SYS_NBOOT.gz A gzipped copy of the network boot block. + This is useful if you are installing + a diskless NetBSD/hp300 system. + + inst-11.fs.gz A gzipped copy of the miniroot filesystem. + + netbsd.gz A gzipped GENERIC kernel. + + rbootd.tar.gz Source code for the rbootd(8) program, required + for netbooting an HP workstation. + + HP-IB.geometry A file containing geometry for some HP-IB + disk drives. + The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are extracted "below" the current directory. That diff --git a/distrib/notes/hp300/hardware b/distrib/notes/hp300/hardware index 48f2ef8085cf..c2601896637c 100644 --- a/distrib/notes/hp300/hardware +++ b/distrib/notes/hp300/hardware @@ -1,40 +1,37 @@ -NetBSD/hp300 1.0 will run on most HP 9000/300 series machines. +NetBSD/hp300 1.1 will run on most HP 9000/300- and 400-series machines. The lowest amount of RAM that has been tested is 7.5M, though it may run with less. Certainly, if you wish to run X, more RAM is -recommended. Until you reach 16M, more RAM is more important than -a faster CPU. +recommended. Here is a table of recommended HD partition sizes for a full install: - partition: advise needed - root (/) 15M 15M (see note below) - user (/usr) 80M 45M - swap ----- 2M for every 1M of RAM ----- - local (/local) up to you + partition: advise needed + root (/) 15M 10M + user (/usr) 80M 45M + swap (2 or 3 * RAM) 6M (see note below) + Anything else is up to you! -NOTE: Because of the nature of the hp300 bootstrap procedure, the root -filesystem is a _fixed_size_! You may want to consider placing /var and -/tmp on their own partitions. This, of course is up to you and your -judgement. Also, note that the recommended size of /usr is 15M greater -than the needed size. This is to allow room for kernel source and -compile areas, as you may want to compile your own kernel. +NOTE: The hp300 installation procedure utilizes a `miniroot' filesystem +which is placed into the swap area of the disk. The swap are must be +at least large enough to hold this miniroot image. The following HP hardware is supported: CPUs: 68020-based: 318, 319, 320, 330, and 350. - 68030-based: 340, 345, 360, 370, 375, and 400. - 68040-based: 380, 425, and 433. + 68030-based: 340, 345, 360, 370, 375, and 400(*). + 68040-based: 380, 425(*), and 433(*). Disks: HP-IB/CS80: 7912, 7914, 7933, 7936, 7937, 7945, 7957, 7958, 7959, 2200, and 2203. - SCSI-I, including magneto-optical and CD-ROM. SCSI-II - drives should work if they can talk SCSI-I. + SCSI-I(**), including magneto-optical and CD-ROM. Tape drives: - Low-density CS80 cartridge: 7914, 7946, 9144. - High-density CS80 cartridge: 9145. - SCSI: HP DAT and Exabyte. + Low-density HP-IB/CS80 cartridge: 7914, 7946, and 9144. + High-density HP-IB/CS80 cartridge: 9145. + HP-IB/CS80 1/2": 7974A, 7978A/B, 7979A, 7980A, and 7980XC. + SCSI: HP DAT, Exabyte, and SCSI QIC drives such as + the Archive Viper. RS232 interfaces: 98644 built-in single port (dca). @@ -54,13 +51,23 @@ The following HP hardware is supported: Input devices: General interface supporting all HIL devices: keyboard, - 2 and 3 button mice, and ID module. + 2 and 3 button mice(***), and ID module. Miscellaneous: Battery-backed real-time clock. - 98625A and 98625B built-in HP-IB interface. - 98658A built-in SCSI interface. + 98624 built-in HP-IB interface. + 98625A and 98625B `fast' HP-IB interface. + 98658A built-in and add-on SCSI interface. Printers and plotters on RS232 and HP-IB. SCSI autochanger. -If it's not on this list, there is no support for it in this release. +(*) 400-series machines configured for Domain/OS are not fully supported, + notably, the keyboard doesn't work and the ROMs must be in `HP-UX mode'. + +(**) SCSI-II drives are known to work, though this may require changing a + jumper on some drives. See your disk's documentation for details. + +(***) Serial mice connected to a `HIL to quad' converter are also known + to work. + +If it's not on this list, there is no official support for it in this release. diff --git a/distrib/notes/hp300/install b/distrib/notes/hp300/install index 9f33d0bc7aec..446ebec2b0a9 100644 --- a/distrib/notes/hp300/install +++ b/distrib/notes/hp300/install @@ -1,222 +1,78 @@ -NOTE: In the following examples you will see references to -disk devices. For those not familiar with NetBSD, the following -prefixes are used to denote drive types: +The miniroot's install program is very simple to use. It will guide +you through the entire process, and is well automated. Additional +improvements are planned for future releases. - sd SCSI disk - rd HP-IB disk +The miniroot's install program will: -In the examples that follow, `rd' will be used. The steps are -exactly the same for `sd' disks. Only the names have changed -to protect the innocent. + * Allow you to place disklabels on additional disks. + Note that partition sizes and offsets are expressed + in sectors. When you fill out the disklabel, you will + need to specify partition types and filesystem parameters. + If you're unsure what the these values should be, use the + following: -Assuming you have read this document thoroughly and kept good notes -about your partitions, the rest should be fairly straight forward. + fstype: 4.2BSD + fsize: 1024 + bsize: 4096 + cpg: 16 -Before you begin, you must have already prepared the target disk -as detailed in the section on preparing your system for install. + If the partition will be a swap partition, use the following: -The following is a walk-through of the steps necessary to finish -what the preparation process has already begun. You may choose to -stop the process at any time, but if you do, it's recommended that -you start over from scratch. + fstype: swap + fsize: 0 (or blank) + bsize: 0 (or blank) + cpg: 0 (or blank) - First you need to boot off of the target disk which - you have made in the preparation process. To do this, - halt HP-UX, power-cycle your machine, and hit the space - bar during the boot ROM's probing/testing sequence. - You should eventually be presented with a list of systems - from which to boot. You want the one called `SYS_PBOOT'. + You will also need to specify the number of partitions. + The number of partitions is determined by the `index' of + the last partition letter, where a == 1, b == 2, etc. + Therefore, if the last filled partition is partition `g', + there are 7 partitions. Any partitions with size of 0 + may be removed from the list. - After selecting `SYS_PBOOT', your system should load the - NetBSD boot block and ask you for a kernel to load. - Enter the following to boot NetBSD into single-user mode. - (Note: it will come into single-user anyway, as there is - not yet an fstab, but this makes it happen more gracefully.) + If the disk is the boot disk, you _must_ offset the root + partition (`a') one cylinder, as the hp300 boot code + if large enough to spill past the label area. In this case, + the `c' partition must be fstype `boot'. - netbsd -s + Anything after a `#' is a comment. - The kernel will now load, and configure your hardware. - Make a note of the device it lists when mounting the - root filesystem. It should look something like this: + The following is an example disklabel partition map: - Changing root device to rd0a +7 partitions: +# size offset fstype [fsize bsize cpg] + a: 30912 448 4.2BSD 1024 8192 16 # (Cyl. 1 - 69) + b: 130816 31360 swap # (Cyl. 70 - 361) + c: 1296512 0 boot # (Cyl. 0 - 2893) + e: 81984 162176 4.2BSD 1024 8192 16 # (Cyl. 362 - 544) + f: 102592 244160 4.2BSD 1024 4096 16 # (Cyl. 545 - 773) + g: 949760 346752 4.2BSD 1024 8192 16 # (Cyl. 774 - 2893) - The message above is an example only. Your message may - be different. + * Create filesystems on target partitions. - Check the root filesystem. Use the raw flavor of the - device listed during the `Changing root device...' - message. Example: + * Allow you to set up your system's network configuration. + Remember to specify host names without the domain name + appended to the end. For example use `foo' instead of + `foo.bar.org'. If, during the process of configuring + the network interfaces, you make a mistake, you will + be able to re-configure that interface by simply selecting + it for configuration again. - fsck -p /dev/rrd0a + * Mount target filesystems. You will be given the opportunity + to manually edit the resulting /etc/fstab. - Mount the root filesystem: + * Extract binary sets from the media of your choice. - mount /dev/rd0a / + * Copy configuration information gathered during the + installation process to your root filesystem. - It's now time to newfs all of the other partitions you - listed in your disk label. So, for example, if rd0e and - rd0f were to have filesystems put on them, you would - do the following: + * Make device nodes in your root filesystem. - newfs /dev/rrd0e - newfs /dev/rrd0f + * Copy a new kernel onto your root partition. - Ensure that the mount-points for these filesystems are clean. - If these filesystems are to be /var and /usr, respectively, - just check that there are no files in those directories. - There shouldn't be. Once you've made sure, go ahead and - mount those filesystems. + * Install a new boot block. - It's now time to get the distribution sets onto the root - or other filesystem. There are several programs in /ibin - to help you with this. At your disposal, you have: + * Check your filesystems for integrity. - ftp - gzip - tar - extract - - Except for extract, which is just a script to help the - process along, these are statically-linked versions of - themselves, which normally appear in /usr/bin. - - If you placed the distribution sets on tape, go to the - directory where you wish to temporarily place them and - extract them from tape, using /dev/nrstX for SCSI tapes - or /dev/nrctX for HP-IB cartridge tapes, where X is the - unit number of the tape, probably 0. - - tar xvf /dev/nrst0 - - If this extracts the sets directly into your current - directory, terrific. Otherwise, go to the directory in - which they live. Skip on to extracting the sets. - - If you will be grabbing the sets off of the network somehow, - configure your network interface: - - ifconfig le0 inet - route add default - - If you will be ftp'ing the sets from one of the NetBSD ftp - sites, go to the directory where you wish to temporarily - place them and download them from the ftp site of your choice. - Since you haven't yet created a resolv.conf, you'll need to - use the IP address. - - /ibin/ftp - - If you will be getting the sets from an NFS server, mount - the filesystem on the server which has the sets, and go - to the directory that has them. Again, you'll need to use - the IP address of the server. - - mount -t nfs : - - At this point, you have everything necessary to label any - additional disks that you wish to label. If you created - additional labels in the preparation phase, and have - access to them now, go ahead and label the disks they - correspond to: - - disklabel -W rd1 - disklabel -r -R rd1 rd1.label - where: - rd1 additional disk you wish to label - rd1.label file containing disk label information - - You may check these labels once they are on the disk: - - disklabel -r rd1 - where: - rd1 additional disk you wish to label - - A problem with a partition (such as overlaps or not falling - on a cylinder boundary) will be noted with a `*'. If you see - these, re-edit your label by the method of your choice (on - another machine, perhaps, or with ed(1), for the brave), - transfer it to a place that's usable (if necessary) and - label the disk again. - - Once these disks have been labeled, you may newfs the - partitions that are to contain filesystems and mount them. - - You should now be ready to extract the filesets. The program - /ibin/extract should help you with this. For example: - - /ibin/extract base - -or- /ibin/extract base.tar.gz - - Do this for all of the filesets you wish to extract. As your disk - fills up, you may wish to remove the sets once you have extracted - them. - - You should have everything necessary to use an editor by now. - Set your TERM environment variable: - - setenv TERM hp300h (csh) - -or- export TERM=hp300h (sh) - - hp300h is the terminal type for the HP 9000/300 ITE console. - If you are using a serial console, change the TERM variable - appropriately. Now, initialize the terminal: - - tset - - You should be able to use vi now. - - Create an /etc/fstab. Example fstabs are provided in - /etc/fstab.sd and /etc/fstab.rd. - - Edit your host table, /etc/hosts. In it, place the IP - address of this host and the IP address of your default - router. - - Edit the file /etc/myname. In it, place the symbolic name - of your machine. - - Edit the file /etc/defaultdomain. In it, place the name - of your YP domain. If you will not be using YP, simply - enter the domain name of your site. - - Edit the file /etc/mygate. In it, place the name of - your default router, as your listed it in /etc/hosts. - - Edit the file /etc/hostname.le0. In it, place the following - information: - - inet - - where: - is the name corresponsing to - the IP address for that interface, as you listed in - /etc/hosts. - - is the netmask for your network. - - is the broadcast address for your network. - - Repeat this step for any additional network interfaces you - may have. - - Edit the file /etc/ttys. Make sure that the entries are - correct for whichever console type you have. /dev/console - is correct for ITE, /dev/tty0 for console on dca, and - /dev/tty00 for console on dcm. You may get more information - about /etc/ttys by doing `man ttys', providing you have - installed the system manual set. - - Ok, cross your fingers and reboot: - - sync; sync; sync; reboot - - Providing you entered all information correctly, your - machine will boot into multi-user mode. Your system - will need a few tweaks here and there (like /etc/sendmail.cf - and /etc/netstart, perhaps), but that's the easy stuff. - - CONGRATULATIONS! You have successfully installed NetBSD - onto your hp300! Pat yourself on the back. This might also - be a good time to remove /ibin, as you will no longer need - it, and it is provided solely for bootstrapping purposes. +First-time installation on a system through a method other than the +installation program is possible, but strongly discouraged. diff --git a/distrib/notes/hp300/legal b/distrib/notes/hp300/legal index 9ee96f95125b..f2b01450f4af 100644 --- a/distrib/notes/hp300/legal +++ b/distrib/notes/hp300/legal @@ -1,3 +1,7 @@ - This product includes software developed by Adam Glass. + This product includes software developed by the Computer + Systems Laboratory at the University of Utah. - This product includes software developed by Jason R. Thorpe. + This product includes software developed at Ludd, University of + Lule}, Sweden and its contributors. + + This product includes software developed by Gordon W. Ross. diff --git a/distrib/notes/hp300/prep b/distrib/notes/hp300/prep index 5da019a2a6a2..ada1d72e51f4 100644 --- a/distrib/notes/hp300/prep +++ b/distrib/notes/hp300/prep @@ -1,125 +1,164 @@ -NOTE: These instructions are explicitly for installing NetBSD -from an HP-UX system, version 7 or later. It has not been -tested with HP-UX versions earlier than 7, and has also not -been tested with HP-UX 8, although it is presumed to work. -For the creative, similar steps may be taken from a system such -as Utah's 4.3BSD release for the hp300, although bootstrapping -from such a system has not been tested. +Currently, only installing the miniroot from the network is supported. +This may change in a future release. -Bootstrapping the hp300 is a complicated process, but it's a lot -easier than it used to be. For this process you need the -following items from the install/ directory: +You will need information about your disk's geometry, based on 512-byte +sectors. You must have this information before proceeding. The +file `.../install/HP-IB.geometry' has geometry inforomation for several +HP-IB disks, but may be incomplete. Geometry may be calculated from an +HP-UX `/etc/disktab' entry, but note that HP-UX geometry is based on +1024 byte sectors, while NetBSD's is based on 512 byte sectors. - boot NetBSD/hp300 boot block for - HP-IB and SCSI disks +QUICK NOTE ABOUT PARTITIONS: Since the target disk will become the boot +disk for your new NetBSD/hp300 installation, you will need to treat the +`a' and `c' partitions in a special manner. Due to the size of the +NetBSD/hp300 boot program (it spills into the area after the disklabel), +it is necessary to offset the `a' partition one cylinder from the beginning +of the disk. Later, the `c' partition will be marked with the type +`FS_BOOT' and may not be used for a filesystem. (For those unfamiliar +with historic BSD partition conventions, the `c' partition is defined +as `the entire disk', or the `raw partition'.) - rootimage.gz bootstrap root filesystem - image +A QUICK NOTE ABOUT DISK NUMBERS: While in the SYS_INST program, you +may use different unit numbers for the disks than when the NetBSD +kernel is running. The unit number for a disk while in SYS_INST is +calculated with the following formula: - label prototype disk label + unit = (controller * 8) + slave - makedisk a program for HP-UX that will - write a NetBSD disk label, - boot block, and root filesystem - image to the target disk - (NOTE: This is an HP-UX 7.x binary. - while it will work under HP-UX 9.x, - you may want to compile this yourself. - The source may be found in makedisk.tar.gz) +Controllers are numbered 0, 1, ... starting with the lowest select code. +SCSI controllers and HP-IB controllers are counted separately. Therefore, +if you had a system with an internal HP-IB interface at select code 7, +a fast HP-IB interface at select code 14, and a SCSI interface at select +code 16, unit numers might be something like the following: -VERY IMPORTANT NOTE: This procedure will destroy all data on the -target disk. Because NetBSD uses a different filesystem format than -HP-UX, your old data will be useless. If you wish to save anything, -use tar(1) instead of dump(1M), again because of filesystem differences. + Location Unit + -------- ---- + HP-IB at 7, slave 2 2 (disk: rd2) + HP-IB at 14, slave 5 13 (disk: rd13) + SCSI at 16, slave 0 0 (disk: sd0) -First of all, you must have a second disk on which to install NetBSD. -If possible, this disk should first be prepared with mediainit(1M). -Once this disk is spotless, you should generate a disk label for it. -Using the prototype label provided, fill in all of the necessary -information. Remember, if you derive geometry information from an -HP-UX disktab, your partition size will be off. This is because HP-UX -uses a 1024-byte sector size, while NetBSD uses a 512-byte sector size. -To avoid the problem, you may simply double the number of cylinders. -(That's what I do...works great. -- JRT) -IMPORTANT: Partition 'a' must be offset one cylinder. Since -partition information is expressed in sectors, the offset of -partition 'a' must be the value of `sectors/cylinder'. This is -to leave room for the boot block. + Miniroot installation via network + --------------------------------- +NOTE: BOOTING SYS_INST VIA THE NETWORK IS ONLY POSSIBLE IF YOUR BOOTROM +IS `REV. C' OR LATER. -When you create your disklabel, be sure to specify whether or not -the disk is HP-IB or SCSI in the `type:' field. +In order to complete this process, you will need the following from the +`.../install' directory of the distribution: -Below is an example of what a disk label should look like. This -is an example only! Do not attempt this at home! + SYS_INST The standalone disklabel and miniroot + installation tool - + inst-11.fs.gz A gzipped miniroot filesystem image. This image + must be un-gzipped before copying to disk. -# Sample disklabel for example only. This is a comment. -type: HP-IB -disk: -label: INSTALL-1_0 -flags: -bytes/sector: 512 -sectors/track: 36 -tracks/cylinder: 7 -sectors/cylinder: 252 -cylinders: 1013 -rpm: 3600 -interleave: 1 -trackskew: 0 -cylinderskew: 0 -headswitch: 0 # milliseconds -track-to-track seek: 0 # milliseconds -drivedata: 0 +To boot SYS_INST via the network, you will need a system capable of handling +boot requests for an HP workstation. If you will use this method, see the +special note below. -7 partitions: -# size offset fstype [fsize bsize cpg] - a: 30744 252 4.2BSD 1024 8192 16 # (Cyl. 1 - 122) - b: 32760 30996 swap # (Cyl. 123 - 252) - c: 255276 0 boot # (Cyl. 0 - 1012) - e: 20412 63756 4.2BSD 1024 4096 16 # (Cyl. 253 - 333) - f: 40824 84168 4.2BSD 1024 8192 16 # (Cyl. 334 - 495) - g: 130284 124992 4.2BSD 1024 8192 16 # (Cyl. 496 - 1012) +To boot SYS_INST from tape, you need only place SYS_INST on the tape as +the first file. -NOTE: Due to the nature of the bootstrapping procedure, your 'a' -partition must be at least 30744 sectors long. Increase the size of -your 'a' partition just enough to make it end on a cylinder boundary. -If you make it any larger, you will just be wasting space, as the -filesystem ends after 30744 sectors. +-- The following section is specific for loading SYS_INST via the network. -- -Remember to write down the names of the partitions and what you -will be using them for (i.e. 'a - root, b - swap, e - /usr, etc.') -as you will need this information later on in the installation -process. +If you wish to load the SYS_INST program via the network, you may need +the following from the `.../install' directory in addition to the items +listed above: -Once you are satisfied with your disklabel, you can write the -root filesystem image to the target disk. Use the `makedisk' -program for this. So, under HP-UX, do: + rbootd.tar.gz Source code for the rbootd program included with + NetBSD. It requires that the server have a + Berkeley Packet Filter (bpf). You will need to + compile this version of rbootd if your server + system does not have this utility already. - ./makedisk /dev/rdsk/c7d0s0 mylabel boot rootimage.gz +First of all, configure your rbootd to handle boot requests from the +client. NOTE: NetBSD's `rbootd' is slightly different from HP-UX's. +To configure NetBSD's `rbootd', create a file called `/etc/rbootd.conf' +and place in it an entry like the following: -where: - /dev/rdsk/c7d0s0 raw flavor of target disk device + 08:00:09:04:AA:33 SYS_INST # thunder-egg - mylabel disk label you just wrote +The first column is the ethernet address of the client's network interface. +The second column is the program to send to the client, and anything after +the `#' is a comment. Once you have rbootd running, copy the SYS_INST +program to the /usr/mdec/rbootd directory on your server. If this +directory doesn't exist already, you will need to create it. - boot supplied boot block +For information on configuring rbootd under HP-UX, see the rbootd(1M) +manual page on your server system. - rootimage.gz gzipped root filesystem image - NOTE: This requires that gzip be - installed on your HP-UX system. - If it is not, a gzip binary is - provided in the install/ directory. - Source for gzip may be found in the - gsrc10 distribution set. Again, this - gzip is an HP-UX 7.x binary. +Once `rbootd' is configured and running, you will be ready to continue. -If you wish to label any additional disks, you will have to do this -from NetBSD, although you will not have an editor at your disposal. -To do this, simply generate the labels now, and then grab them at -the same time and by the same method you use to grab the distrubtion -sets. +------------------ End of network boot-specific section ---------------------- -Once this is done, you should be ready to boot NetBSD from the target -disk. +Make sure that the miniroot filesystem image has been un-gzipped, and +that it resides in a filesystem what is exported to the client. See the +manual pages on your server system if you need more information about +exporting filesystems. + +You are now ready to SYS_INST. During the client's self-test cycle, press +the space bar a few times. Shortly, you should see a menu of possible boot +options appear. Select the option corresponding to SYS_INST. SYS_INST will +load and prompt you for a command. + +If this is a new NetBSD installation, you will need to place a disklabel +on the disk. + + sys_inst> disklabel + +NOTE: it may be worth selecting the `zap' option initially to ensure that +the disklabel area is clear. This may be especially important if an +HP-UX boot block had been previously installed on the disk. + +Select the `edit' option, and answer the questions about your disk. +There may be several questions which you may not be sure of the answers +to. Listed below are guidelines for SCSI and HP-IB disks: + + Bad sectoring? NO + Ecc? NO + Interleave? 1 + Trackskew? 0 + Cylinderskew? 0 + Headswitch? 0 + Track-to-track? 0 + Drivedata 0-4? 0 (for all Drivedata values) + +Next, you will be asked to fill out the partition map. You must provide +responses for all 8 partitions. Remember, you must allocate at least 6M +for the `b' partition, or else the miniroot will not fit. Set the size and +offset of any unused partition to 0. Note that sizes and offsets are +expressed in `n sectors', assuming 512 byte sectors. Care should be taken +to ensure that partitions begin and end on cylinder boundaries (i.e. size +and offset is an even multiple of the number of sectors per cylinder). +While this is not technically necessary, it is generally encouraged. Note +that you cannot enter partition types at this time. You will be given an +oppotinuty to `clean up' the disklabel later on in the installation procedure. + +Once you have edited the label, select the `show' option to verify that +it is correct. If so, select `write' and `done'. Otherwise, you may +re-edit the label. + +The next step is to copy the miniroot image onto the target disk. + + sys_inst> miniroot + +You will be prompted for the target disk and the source of the miniroot +filesytem image. + +Enter the filename of the miniroot image. Note that this file _must_ reside +in the server directory being mounted. Next you will be asked for the +client's IP address, netmask, and default router, the server's IP address, +and the directory on the server to mount. Once you have entered this +information, SYS_INST will attempt to mount the NFS server and begin copying +the miniroot filesystem to the `b' partition of the target disk. + +Is is worth noting that this copy may take a while. It might be worth +grabbing a cup of coffee at this point. + +Once the miniroot filesystem image has been copied onto the target disk, +you may boot from the miniroot filesystem. + + sys_inst> boot + +Enter the disk from which to boot. The kernel in the miniroot filesystem +will be booted into single-user mode. diff --git a/distrib/notes/hp300/upgrade b/distrib/notes/hp300/upgrade index 25bcdb9f97c0..aa51832ae4e8 100644 --- a/distrib/notes/hp300/upgrade +++ b/distrib/notes/hp300/upgrade @@ -1 +1,92 @@ -There is no previous release of NetBSD/hp300 to upgrade. +It is possible to easily upgrade your existing NetBSD/hp300 system +using the upgrade program in the miniroot. If you wish to upgrade +your system by this method, simply select the `upgrade' option once +the miniroot has booted. The upgrade program with then guide you +through the procedure. The upgrade program will: + + * Enable the network based on your system's current + network configuration. + + * Mount your existing filesystems. + + * Extract binary sets from the media of your choice. + + * Fixup your system's existing /etc/fstab, changing the + occurrences of `ufs' to `ffs' and let you edit the + resulting file. + + * Make new device nodes in your root filesystem. + + * Copy a new kernel onto your root partition. + NOTE: the existing kernel WILL NOT be backed up; doing + so would be pointless, since a NetBSD 1.0 kernel will + not run NetBSD 1.1 executables. + + * Install a new boot block. + + * Check your filesystems for integrity. + +While using the miniroot's upgrade program is the preferred method +of upgrading your system, it is possible to upgrade your system +manually. To do this, follow the following procedure: + + * Place _at least_ the `base' binary set in a filesystem + accessible to the target machine. A local filesystem + is preferred, since there may be incompatibilities + between the NetBSD 1.1 kernel and older route(8) + binaries. + + * Back up your pre-existing kernel and copy the 1.1 + kernel into your root partition. + + * Reboot with the 1.1 kernel into single-user mode. + + * Check all filesystems: + + /sbin/fsck -p + + * Mount all local filesystems: + + /sbin/mount -a -t nonfs + + * If you keep /usr or /usr/share on an NFS server, you + will want to mount those filesystems as well. To do + this, you will need to enable the network: + + sh /etc/netstart + + NOTE: the route(8) commands may fail due to potential + incompatibilities between route(8) and the NetBSD 1.1 + kernel. Once you have enabled the network, mount the + NFS filesystems. If you use amd(8), you may or may not + have to mount these filesystems manually. Your mileage + may vary. + + * Make sure you are in the root filesystem and extract + the `base' binary set: + + cd / + tar --unlink -zxvpf /path/to/base11.tar.gz + + NOTE: the `--unlink' option is _very_ important! + + * Install a new boot block: + + cd /usr/mdec + disklabel -B + + * Sync the filesystems: + + sync + + * At this point you may extract any other binary sets + you may have placed on local filesystems, or you may + wish to extract additional sets at a later time. + To extract these sets, use the following commands: + + cd / + tar --unlink -zxvpf + +NOTE: you SHOULD NOT extract the `etc' set if upgrading. Instead, you +should extract that set into another area and carefully merge the changes +by hand. diff --git a/distrib/notes/hp300/whatis b/distrib/notes/hp300/whatis index 7a1b6055ef73..ba2c5cba8690 100644 --- a/distrib/notes/hp300/whatis +++ b/distrib/notes/hp300/whatis @@ -1,2 +1,2 @@ -This is the first public release of NetBSD for the HP 9000/300 series of +This is the second public release of NetBSD for the HP 9000/300 series of computers. diff --git a/distrib/notes/hp300/xfer b/distrib/notes/hp300/xfer index a912c45d826e..799a932f52f7 100644 --- a/distrib/notes/hp300/xfer +++ b/distrib/notes/hp300/xfer @@ -1,6 +1,7 @@ Installation is supported from several media types, including: Tape - NFS partitions + CD-ROM + NFS FTP The steps necessary to prepare the distribution sets @@ -9,70 +10,71 @@ you choose. The various methods are explained below. To prepare for installing via a tape: - To install NetBSD from a tape, you need to somehow - get the NetBSD filesets you wish to install on - your system on to the appropriate kind of tape, - in tar format. + If you wish to load SYS_INST from tape, it must + appear on the tape before any other files. To copy + this onto tape, use a command like the following: - If you're making the tape on a UN*X system, the easiest - way to do so is: + dd if=SYS_INST of= bs=20b - tar cvf + Note that not all HP BOOTROMs support booting from + SCSI tapes. - where "" is the name of the tape device - that describes the tape drive you're using (possibly - something like /dev/nrst0, but we make no guarantees 8-). - Under HP-UX, this would be something like /dev/rmt/c0ed03inb. - Again, your mileage may vary. If you can't figure it out, - ask your system administrator. "" are the names - of the "set_name.nnn" files which you want to be placed - on the tape. + Copying the miniroot to disk from tape is not currently + supported. However, it is planned for a future release. - Once you have done this, you can proceed to the next - step in the installation process, preparing your - system for NetBSD installation. + If you wish to extract binary sets onto your disk from + tape, you must first place them on the tape. The easiest + way to do this is with the dd(1) command. Make sure you + use a `no-rewind-on-close' tape device. For example: -To prepare for installing via an NFS partition: + for file in base11.tar.gz etc11.tar.gz; do + dd if=${file} of=/dev/nrst0 bs=20b + done - NOTE: this method of installation is recommended - only for those already familiar with using - the BSD network-manipulation commands and - interfaces. If you aren't, this documentation - should help, but is not intended to be - all-encompassing. + Note that depending on your tape drive, you may need to + explicitly set the EOF marker at the end of each file. + It may also be necessary to use the `conv=osync' argument + to dd(1). Note that this argument is incompatible with the + `bs=' argument. Consult the tape-related manual pages on the + system where the tapes are created for more details. - Place the NetBSD software you wish to install into - a directory on an NFS server, and make that directory - mountable by the machine which you will be installing - NetBSD on. This will probably require modifying the - /etc/exports file of the NFS server and resetting - mountd, acts which will require superuser privileges. - Note the numeric IP address of the NFS server and of - the router closest to the the new NetBSD machine, - if the NFS server is not on a network which is - directly attached to the NetBSD machine. +To prepare for installing via NFS: - Once you have done this, you can proceed to the next - step in the installation process, preparing your - system for NetBSD installation. + SYS_INST currently requires an NFS server from which to + copy the miniroot. + + * This filesystem must be exported with root permissions, + but may be exported read-only. + + * The miniroot image _must_ reside in the `root' of the + mounted filesystem. For example, if the client system + mounts `server:/u', then the miniroot image must reside + in /u on the server. This is due to limitations in the + file lookup code used in SYS_INST, and may be fixed in + a future release. + + * If you also wish to install the binary sets from the + NFS server, place them in a properly exported filesystem + on the server. Note that these files do not suffer from + the same placement restrictions as the miniroot. To prepare for installing via FTP: - NOTE: this method of installation is recommended - only for those already familiar with using - the BSD network-manipulation commands and - interfaces. If you aren't, this documentation - should help, but is not intended to be - all-encompassing. + It is possible, using the `install' and `upgrade' + programs in the miniroot, to extract the binary sets + directly onto disk from an FTP server. This is by far + the easiest installation method, as you may specify to + have all sets extracted at once, providing that they + are located in the same directory on the server. - The preparations for this method of installation - are easy: all you have to do is make sure that - there's some FTP site from which you can retrieve - the NetBSD installation when it's time to do - the install. You should know the numeric IP - address of that site, the numeric IP address of - your nearest router if one is necessary + All that is required in this case is that you have + network access to an FTP server. This may be your + account on another system, or may even be ftp.NetBSD.ORG + itself. If you wish to use ftp.NetBSD.ORG as your FTP + file server, you may want to keep the following information + handy: - Once you have done this, you can proceed to the next - step in the installation process, preparing your - system for NetBSD installation. + IP Address: 205.149.163.23 + Login: anonymous + Password: + Server path: /pub/NetBSD/NetBSD-1.1/hp300/binary