Note that a ./MAKEDEV all is needed, document the install script
functions, briefly describe a manual install, fix section cross references, and other misc edits.
This commit is contained in:
parent
6c0386cefa
commit
f1e5d2be9f
|
@ -1,4 +1,4 @@
|
|||
# $NetBSD: Makefile,v 1.5 1998/05/02 08:50:12 ross Exp $
|
||||
# $NetBSD: Makefile,v 1.6 1998/05/13 19:07:46 ross Exp $
|
||||
|
||||
TOP= ${.CURDIR}/..
|
||||
|
||||
|
@ -20,11 +20,14 @@ IMAGE?= xxx-${REV}.fs
|
|||
MDEC= ${DESTDIR}/usr/mdec
|
||||
|
||||
LISTS= list
|
||||
CRUNCHCONF= ${CBIN}.conf
|
||||
MTREE= mtree.conf
|
||||
|
||||
DISKTYPE= floppy
|
||||
|
||||
CRUNCHCONF= ${CBIN}.conf
|
||||
CRUNCHFILES= ${CBIN}.mk ${CBIN}.cache ${CBIN}.c
|
||||
CRUNCHCMD= crunchgen -D ${TOP}/../../.. -L ${DESTDIR}/usr/lib ${.ALLSRC}
|
||||
|
||||
install.sh: install.tmpl
|
||||
sed "s/@@VERSION@@/${VER}/" < ${.ALLSRC} > ${.TARGET}
|
||||
|
||||
|
@ -56,8 +59,8 @@ unconfig:
|
|||
-vnconfig -u ${VND_DEV}
|
||||
-/bin/rm -f ${IMAGE}
|
||||
|
||||
${CBIN}.mk ${CBIN}.cache ${CBIN}.c! ${CRUNCHCONF}
|
||||
crunchgen -D ${TOP}/../../.. -L ${DESTDIR}/usr/lib ${.ALLSRC}
|
||||
${CRUNCHFILES}: ${CRUNCHCONF}
|
||||
if ${CRUNCHCMD}; then exit 0; else rm -f ${CRUNCHFILES}; exit 1; fi
|
||||
|
||||
${CBIN}: ${CBIN}.mk ${CBIN}.cache ${CBIN}.c libhack.o
|
||||
make -f ${CBIN}.mk all
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
$NetBSD: install,v 1.6 1998/05/12 00:00:18 ross Exp $
|
||||
$NetBSD: install,v 1.7 1998/05/13 19:07:46 ross Exp $
|
||||
|
||||
0. Introduction
|
||||
|
||||
|
@ -176,7 +176,27 @@
|
|||
`install' script from the boot floppy (or boot kernel, if you
|
||||
booted it via NFS with the INSTALL kernel).
|
||||
|
||||
3.1 Running Install
|
||||
3.1 Manual Install from the Shell Prompt
|
||||
|
||||
The normal installation involves running the install shell script
|
||||
and interactively configuring the file systems, and then simply
|
||||
unpacking the tar files into these followed by running MAKEDEV.
|
||||
|
||||
However, it is also possible to do the installation yourself
|
||||
from the shell, and in any case it is helpful to understand
|
||||
what the install script does. The procedure is:
|
||||
|
||||
1. create /etc/disktab(5)
|
||||
2. run disklabel(8),
|
||||
3. run newfs(8)
|
||||
4. mount(8) the new root on /mnt
|
||||
5. cd to /usr/mdec and run ./installboot(8)
|
||||
|
||||
If you are reviewing man pages on NetBSD platforms other than
|
||||
alpha, be sure when reading installboot that you read the alpha
|
||||
version by typing: "man 8 alpha/installboot".
|
||||
|
||||
3.2 Running Install
|
||||
|
||||
When you first boot the INSTALL kernel you will be given the
|
||||
options of `install' or `shell'. Choose `install' and the
|
||||
|
@ -187,7 +207,7 @@
|
|||
prompt. You can then restart the install script by typing
|
||||
`/install', or halt the machine by typing `halt'.
|
||||
|
||||
3.1 Answering the Install Questions
|
||||
3.3 Answering the Install Questions
|
||||
|
||||
These will for the most part be fairly obvious. You may install
|
||||
on either a SCSI or an IDE disk, and you will be prompted for
|
||||
|
@ -330,10 +350,24 @@
|
|||
|
||||
The sets and kernel are extracted with
|
||||
|
||||
cd /mnt
|
||||
for file in base kern comp etc games man misc text; do
|
||||
tar xpfz /mnt/var/tmp/$file.tgz;
|
||||
done
|
||||
|
||||
or (but do NOT unpack source/toolchain.tgz from / or /mnt) perhaps:
|
||||
|
||||
cd /mnt
|
||||
for file in /mnt/var/tmp/*.tgz; do
|
||||
echo $i
|
||||
tar xpfz $i
|
||||
done
|
||||
|
||||
Now make the device nodes:
|
||||
|
||||
cd /mnt/dev
|
||||
sh ./MAKEDEV all
|
||||
|
||||
You will now be ready to reboot from your hard disk. Type `sync'
|
||||
twice to make sure all the data is written out to disk and then
|
||||
type `halt' to halt your system and go back to the monitor. At
|
||||
|
@ -380,5 +414,3 @@
|
|||
accounts to your system, edit /etc/aliases to forward root mail to
|
||||
the right place (run `newaliases' afterwards) and edit /etc/rc.local
|
||||
to run any local daemons you use.
|
||||
|
||||
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
$NetBSD: upgrade,v 1.6 1998/05/12 00:00:18 ross Exp $
|
||||
$NetBSD: upgrade,v 1.7 1998/05/13 19:07:46 ross Exp $
|
||||
|
||||
The upgrade to NetBSD _VER is a binary upgrade; it can be quite difficult
|
||||
to advance to a later version by recompiling from source due primarily
|
||||
|
@ -11,14 +11,15 @@ IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on
|
|||
another operating system's partition, before beginning the upgrade
|
||||
process.
|
||||
|
||||
The upgrade is done entirely `by hand.' You will need first to boot
|
||||
the new boot floppy or INSTALL kernel and use /usr/mdec/installboot
|
||||
to install new boot blocks. Then you may extract a new kernel and the
|
||||
distribution sets as described in section 5 of the installation
|
||||
instructions.
|
||||
The upgrade is mainly a simple matter of unpacking the distribution
|
||||
tar archives on top of the previous distribution. You will need
|
||||
first to boot the new boot floppy or INSTALL kernel and use
|
||||
/usr/mdec/installboot to install new boot blocks. Then you may
|
||||
extract a new kernel and the distribution sets as described in
|
||||
section 4 of the installation instructions.
|
||||
|
||||
After this point your machine is a complete NetBSD _VER system.
|
||||
However, that doesn't mean that you're finished with the upgrade
|
||||
However, that doesn't mean that you are finished with the upgrade
|
||||
process. You will probably want to update the set of device nodes
|
||||
you have in /dev. If you've changed the contents of /dev by hand,
|
||||
you will need to be careful about this, but if not, you can just
|
||||
|
@ -35,6 +36,6 @@ example mount_nfs(8) for NFS.
|
|||
|
||||
Finally, you will want to delete old binaries that were part of
|
||||
the version of NetBSD that you upgraded from and have since been
|
||||
removed from the NetBSD distribution. Especially important, if you
|
||||
use NFS, is removing /sbin/nfsd and /sbin/nfsiod; the new versions
|
||||
removed from the NetBSD distribution. IMPORTANT NOTE: if you
|
||||
use NFS, remove /sbin/nfsd and /sbin/nfsiod; the new versions
|
||||
of these programs are in /usr/sbin.
|
||||
|
|
Loading…
Reference in New Issue