diff options
| -rw-r--r-- | distrib/notes/m4.common | 30 | ||||
| -rw-r--r-- | distrib/notes/mvme68k/install | 13 | ||||
| -rw-r--r-- | distrib/notes/mvme88k/install | 13 | ||||
| -rw-r--r-- | distrib/notes/sparc/install | 14 | ||||
| -rw-r--r-- | distrib/notes/sparc64/install | 14 |
5 files changed, 30 insertions, 54 deletions
diff --git a/distrib/notes/m4.common b/distrib/notes/m4.common index c4671df7fa9..7061706ec30 100644 --- a/distrib/notes/m4.common +++ b/distrib/notes/m4.common @@ -1,5 +1,5 @@ dnl -dnl $OpenBSD: m4.common,v 1.47 2004/02/08 23:11:31 miod Exp $ +dnl $OpenBSD: m4.common,v 1.48 2004/02/09 13:32:45 todd Exp $ dnl dnl a simple MACHINE->MACHINE_ARCH converter. define(`MACHINE_ARCH', @@ -34,15 +34,15 @@ out as follows: MD5 usable for verification of the correctness of downloaded files.')dnl dnl -dnl Change the quote. There were too many `word' situations that would have -dnl to have been changed to ``word''. The quote gets changed to {:- and -:}. -dnl It can really be anything, but it needs to be unique. +dnl Change the quote. There were too many `word' situations that would +dnl have to have been changed to ``word''. The quote gets changed to +dnl {:- and -:}. It can really be anything, but it needs to be unique. dnl changequote(`{:-',`-:}')dnl dnl dnl Conventions when editing: -dnl o base`'OSrev is required because if it appears as baseOSrev the defined -dnl value OSrev does not get substituted. Same goes for MACHINE, +dnl o base`'OSrev is required because if it appears as baseOSrev the +dnl defined value OSrev does not get substituted. Same goes for MACHINE, dnl MACHINE_ARCH and OSREV, assigned as cmd line parameters to m4 in the dnl Makefile. dnl o `include' and `define' is required as include and define are both m4 @@ -60,8 +60,8 @@ dnl showsize() must not be on a new line. It creates its own new line if dnl there are sizes to display, otherwise, evaluates to NULL dnl dnl XXX fix to allow - empty 1st arg, for files uncompressed -dnl - empty 2nd arg, for files where only compressed size is -dnl known +dnl - empty 2nd arg, for files where only compressed size +dnl is known dnl define({:-showsize-:},{:-ifelse(X$1,X,,X$2,X,,X,X,{:- [ $1 MB gzipped, $2 MB uncompressed ]-:})-:})dnl @@ -913,3 +913,17 @@ the following: put the "base{:--:}OSrev" set somewhere in your file system. It is recommended that you upgrade the other sets, as well.-:})dnl dnl +define({:-OpenBSDInstNFS-:}, +{:-Now you must populate the `/dev' directory for your client. If the server +does not run OpenBSD you might save the MAKEDEV output: + + eo=echo ksh MAKEDEV all > all.sh + +and then tailor it for your server operating system before running it. Note +that MAKEDEV is written specifically for ksh, and may not work on any other +bourne shell. + +There will be error messages about unknown user and groups. These errors are +inconsequential for the purpose of installing OpenBSD. However, you may +want to correct them if you plan to the diskless setup regularly. In that +case, you may re-run MAKEDEV on your OpenBSD machine once it has booted.-:})dnl diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install index 2a283daef35..819ed4b2e32 100644 --- a/distrib/notes/mvme68k/install +++ b/distrib/notes/mvme68k/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.23 2004/01/03 22:40:18 miod Exp $ +dnl $OpenBSD: install,v 1.24 2004/02/09 13:32:47 todd Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -341,13 +341,4 @@ A few configuration files need to be edited: server:/export/root/client / nfs rw 0 0 server:/export/exec/MACHINE.OpenBSD /usr nfs rw 0 0 -Now you must populate the `/dev' directory for your client. If the server -runs SunOS 4.x, you can simply change your working directory to `<root>/dev' -and run the MAKEDEV script: `sh MAKEDEV all' (this might require the edition -of MAKEDEV to change the PATH for it to work properly). - -On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error -messages about unknown user and groups. These errors are inconsequential -for the purpose of installing OpenBSD. However, you may want to correct them -if you plan to the diskless setup regularly. In that case, you may re-run -MAKEDEV on your OpenBSD machine once it has booted. +OpenBSDInstNFS diff --git a/distrib/notes/mvme88k/install b/distrib/notes/mvme88k/install index e4cd8443ec4..1674af541c9 100644 --- a/distrib/notes/mvme88k/install +++ b/distrib/notes/mvme88k/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.14 2004/01/28 13:02:38 miod Exp $ +dnl $OpenBSD: install,v 1.15 2004/02/09 13:32:50 todd Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -311,13 +311,4 @@ A few configuration files need to be edited: server:/export/root/client / nfs rw 0 0 server:/export/exec/MACHINE.OpenBSD /usr nfs rw 0 0 -Now you must populate the `/dev' directory for your client. If the server -runs SunOS 4.x, you can simply change your working directory to `<root>/dev' -and run the MAKEDEV script: `sh MAKEDEV all' (this might require the edition -of MAKEDEV to change the PATH for it to work properly). - -On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error -messages about unknown user and groups. These errors are inconsequential -for the purpose of installing OpenBSD. However, you may want to correct them -if you plan to the diskless setup regularly. In that case, you may re-run -MAKEDEV on your OpenBSD machine once it has booted. +OpenBSDInstNFS diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index 814590bd69b..ff435f12979 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.58 2003/03/24 11:33:57 miod Exp $ +dnl $OpenBSD: install,v 1.59 2004/02/09 13:32:51 todd Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -513,14 +513,4 @@ A few configuration files need to be edited: server:/export/root/client / nfs rw 0 0 server:/export/exec/sun4.OpenBSD /usr nfs rw 0 0 -Now you must populate the `/dev' directory for your client. If the server -runs SunOS 4.x, you can simply change your working directory to `<root>/dev' -and run the MAKEDEV script: `sh MAKEDEV all' (this might require the edition -of MAKEDEV to change the PATH for it to work properly). - -On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error -messages about unknown user and groups. These errors are inconsequential -for the purpose of installing OpenBSD. However, you may want to correct them -if you plan to the diskless setup regularly. In that case, you may re-run -MAKEDEV on your OpenBSD machine once it has booted. - +OpenBSDInstNFS diff --git a/distrib/notes/sparc64/install b/distrib/notes/sparc64/install index e2e9d40a9bd..e0d2845fe00 100644 --- a/distrib/notes/sparc64/install +++ b/distrib/notes/sparc64/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.31 2003/10/01 09:58:14 miod Exp $ +dnl $OpenBSD: install,v 1.32 2004/02/09 13:32:52 todd Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -346,14 +346,4 @@ A few configuration files need to be edited: server:/export/root/client / nfs rw 0 0 server:/export/exec/MACHINE.OpenBSD /usr nfs rw 0 0 -Now you must populate the `/dev' directory for your client. If the server -runs SunOS 4.x, you can simply change your working directory to `<root>/dev' -and run the MAKEDEV script: `sh MAKEDEV all' (this might require the edition -of MAKEDEV to change the PATH for it to work properly). - -On Solaris (SunOS 5.x) systems, MAKEDEV can also be used, but there'll be -error messages about unknown user and groups. These errors are -inconsequential for the purpose of installing OpenBSD. However, you may -want to correct them if you plan to the diskless setup regularly. In that -case, you may re-run MAKEDEV on your OpenBSD machine once it has booted. - +OpenBSDInstNFS |