merge in changes from 1.1 release branch

This commit is contained in:
jtc 1995-11-28 23:56:58 +00:00
parent ed63b163c8
commit 36cd716562
65 changed files with 807 additions and 570 deletions

View File

@ -1,4 +1,4 @@
# $Id: Makefile.inc,v 1.6 1995/10/02 13:10:53 chopps Exp $
# $Id: Makefile.inc,v 1.7 1995/11/28 23:57:03 jtc Exp $
# TOP is assumed to be defined by Makefile including this one.
@ -17,10 +17,10 @@ CRUNCHCONF= ${COMMONDIR}/${CBIN}.conf
MTREE= ${COMMONDIR}/mtree.conf
all: ${CBIN}
dd if=/dev/zero of=${IMAGE} bs=80k count=22
dd if=/dev/zero of=${IMAGE} bs=128k count=32
vnconfig -v -c ${VND_DEV} ${IMAGE}
newfs -O -m 0 -o space ${VND_RDEV} floppyhd
mount ${VND_DEV} ${MOUNT_POINT}
newfs -c 64 -O -m 0 -o space ${VND_RDEV} miniroot
mount -t ffs ${VND_DEV} ${MOUNT_POINT}
mtree -def ${MTREE} -p ${MOUNT_POINT}/ -u
TOPDIR=${TOP} CURDIR=${.CURDIR} OBJDIR=${.OBJDIR} \
TARGDIR=${MOUNT_POINT} sh ${TOP}/runlist.sh ${LISTS}

View File

@ -27,7 +27,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: dot.commonutils,v 1.3 1995/10/09 02:41:31 chopps Exp $
# $Id: dot.commonutils,v 1.4 1995/11/28 23:57:04 jtc Exp $
# Installation utilites (functions), to get NetBSD installed on
# the hard disk. These are meant to be invoked from the shell prompt,
@ -102,7 +102,7 @@ Load_tape()
echo -n "continue..."
read foo
echo "Extracting files from the tape..."
$TAR xvpf --unlink /dev/$which
$TAR --unlink -xvpf /dev/$which
echo "Done."
}

View File

@ -1,4 +1,4 @@
# $Id: list,v 1.4 1995/09/30 08:12:24 chopps Exp $
# $Id: list,v 1.5 1995/11/28 23:57:05 jtc Exp $
# copy the crunched binary, link to it, and kill it
COPY ${OBJDIR}/instbin instbin
@ -24,6 +24,7 @@ LINK instbin bin/[
LINK instbin sbin/disklabel
LINK instbin sbin/fsck
LINK instbin sbin/ifconfig
LINK instbin sbin/halt
LINK instbin sbin/init
LINK instbin sbin/mknod
LINK instbin sbin/mount

View File

@ -1,8 +1,11 @@
# $Id: list,v 1.1 1994/10/06 20:25:48 chopps Exp $
# $Id: list,v 1.2 1995/11/28 23:56:58 jtc Exp $
# the disktab explanation file
COPY disktab.preinstall etc
# copy the kernel
COPY ${CURDIR}/../../../../sys/arch/amiga/compile/INSTALL/netbsd netbsd
# and the installation tools
COPY dot.profile .profile
COPY dot.instutils .instutils

View File

@ -1,4 +1,7 @@
# $Id: list,v 1.2 1995/10/09 02:41:34 chopps Exp $
# $Id: list,v 1.3 1995/11/28 23:57:07 jtc Exp $
# copy the kernel
COPY ${CURDIR}/../../../../sys/arch/amiga/compile/INSTALL/netbsd netbsd
# and the upgrade tools
COPY dot.profile .profile

View File

@ -1,4 +1,4 @@
# $NetBSD: Makefile.inc,v 1.1.1.1 1995/04/17 19:08:49 leo Exp $
# $NetBSD: Makefile.inc,v 1.2 1995/11/28 23:57:10 jtc Exp $
# Revision is 1.0
REV= 10
# Revision is 1.1
REV= 11

View File

@ -1,5 +1,5 @@
#
# $NetBSD: dot.commonutils,v 1.2 1995/05/28 10:50:13 leo Exp $
# $NetBSD: dot.commonutils,v 1.3 1995/11/28 23:57:12 jtc Exp $
#
# Copyright (c) 1994 Christopher G. Demetriou
# All rights reserved.
@ -34,11 +34,17 @@
# the hard disk. These are meant to be invoked from the shell prompt,
# by people installing NetBSD.
# we know that /etc/fstab is only generated on the hard drive
dest_dir=/
if [ ! -f /etc/fstab ]; then
dest_dir=/mnt/
fi
Set_tmp_dir()
{
def_tmp_dir=`pwd`
if [ "$def_tmp_dir" = "/" -o "$def_tmp_dir" = "/mnt" ]; then
def_tmp_dir=/mnt/usr/distrib
def_tmp_dir="$dest_dir"usr/distrib
fi
echo -n "What directory should be used to find and/or store "
@ -122,8 +128,10 @@ Extract()
esac
if [ $snapshot = n ]
then
cat "$1".??? | gunzip | (cd / ; tar xfp$tarverbose -)
cat "$1".??? | gunzip |
(cd $dest_dir ; tar --unlink -xp"$tarverbose"f -)
else
cat "$1".tar.gz | gunzip | (cd /mnt ; tar xfp$tarverbose -)
cat "$1".tar.gz | gunzip |
(cd $dest_dir ; tar --unlink -xp"$tarverbose"f -)
fi
}

View File

@ -1,4 +1,4 @@
# $NetBSD: Makefile.inc,v 1.1 1995/10/03 22:47:55 thorpej Exp $
# $NetBSD: Makefile.inc,v 1.2 1995/11/28 23:57:15 jtc Exp $
# Revision is 1.0A
REV= 10A
# Revision is 1.1
REV= 11

View File

@ -1,5 +1,5 @@
#!/bin/sh
# $NetBSD: install.sh,v 1.5 1995/11/16 07:33:48 thorpej Exp $
# $NetBSD: install.sh,v 1.6 1995/11/28 23:57:17 jtc Exp $
#
# Copyright (c) 1995 Jason R. Thorpe.
# All rights reserved.
@ -35,7 +35,7 @@
# In a perfect world, this would be a nice C program, with a reasonable
# user interface.
VERSION=1.0A
VERSION=1.1A
export VERSION # XXX needed in subshell
ROOTDISK="" # filled in below
FILESYSTEMS="/tmp/filesystems" # used thoughout

View File

@ -1,5 +1,5 @@
#!/bin/sh
# $NetBSD: upgrade.sh,v 1.1 1995/11/14 09:53:15 thorpej Exp $
# $NetBSD: upgrade.sh,v 1.2 1995/11/28 23:57:19 jtc Exp $
#
# Copyright (c) 1995 Jason R. Thorpe.
# All rights reserved.
@ -35,7 +35,7 @@
# In a perfect world, this would be a nice C program, with a reasonable
# user interface.
VERSION=1.0A
VERSION=1.1
export VERSION # XXX needed in subshell
ROOTDISK="" # filled in below

View File

@ -27,7 +27,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: dot.commonutils,v 1.4 1994/10/18 07:03:06 glass Exp $
# $Id: dot.commonutils,v 1.5 1995/11/28 23:57:28 jtc Exp $
# Installation utilites (functions), to get NetBSD installed on
# the hard disk. These are meant to be invoked from the shell prompt,
@ -111,7 +111,7 @@ Load_tape()
echo -n "continue..."
read foo
echo "Extracting files from the tape..."
$TAR xvpf --unlink /dev/$which
$TAR --unlink -xvpf /dev/$which
echo "Done."
}

View File

@ -1,13 +1,14 @@
#
# kcbin.conf - unified binary for the kc floppy
# $Id: instbin.conf,v 1.5 1995/08/13 03:59:07 cgd Exp $
# $Id: instbin.conf,v 1.6 1995/11/28 23:57:30 jtc Exp $
#
srcdirs bin sbin usr.bin usr.sbin gnu/usr.bin
progs bad144 cat chmod chown chroot cp dd df disklabel ed expr fsck ftp gawk
progs gzip ifconfig init ln ls mkdir mknod more mount mount_cd9660
progs mount_ffs mount_msdos mount_nfs mv newfs ping pwd reboot rm route
progs mount_ffs mount_msdos mount_nfs mount_kernfs
progs mv newfs ping pwd reboot rm route
progs sed sh shutdown slattach strings stty sync tar test tip umount
progs update
@ -20,6 +21,7 @@ ln mount_cd9660 cd9660
ln mount_ffs ffs
ln mount_msdos msdos
ln mount_nfs nfs
ln mount_kernfs kernfs
ln reboot halt
libs -ledit -lutil -ltermcap -lcrypt -ll -lm

View File

@ -1,4 +1,4 @@
# $Id: list,v 1.4 1995/08/14 01:50:19 cgd Exp $
# $Id: list,v 1.5 1995/11/28 23:57:31 jtc Exp $
# copy the crunched binary, link to it, and kill it
COPY ${OBJDIR}/instbin instbin
@ -31,6 +31,7 @@ LINK instbin sbin/mount_cd9660
LINK instbin sbin/mount_ffs
LINK instbin sbin/mount_msdos
LINK instbin sbin/mount_nfs
LINK instbin sbin/mount_kernfs
LINK instbin sbin/newfs
LINK instbin sbin/ping
LINK instbin sbin/reboot

View File

@ -1,4 +1,4 @@
# $Id: mtree.conf,v 1.1.1.1 1994/08/29 15:30:23 cgd Exp $
# $Id: mtree.conf,v 1.2 1995/11/28 23:57:33 jtc Exp $
/set type=dir uname=root gname=wheel mode=0755
# .
@ -29,6 +29,11 @@ mnt2
# ./mnt2
..
# ./kern
kern
# ./kern
..
# ./sbin
sbin
# ./sbin

View File

@ -27,7 +27,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: dot.hdprofile,v 1.1 1994/10/18 07:02:57 glass Exp $
# $Id: dot.hdprofile,v 1.2 1995/11/28 23:57:23 jtc Exp $
PATH=/sbin:/bin:/usr/bin:/usr/sbin:/
export PATH
@ -44,6 +44,7 @@ if [ "X${DONEPROFILE}" = "X" ]; then
echo "Mounting filesystems..."
mount -a
mount -t kernfs /kern /kern
# set up some sane defaults
echo 'erase ^?, werase ^W, kill ^U, intr ^C'

View File

@ -27,7 +27,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: dot.profile,v 1.1.1.1 1994/08/29 15:30:21 cgd Exp $
# $Id: dot.profile,v 1.2 1995/11/28 23:57:24 jtc Exp $
PATH=/sbin:/bin:/usr/bin:/usr/sbin:/
export PATH
@ -47,6 +47,9 @@ if [ "X${DONEPROFILE}" = "X" ]; then
# run update, so that installed software is written as it goes.
update
# mount the kern_fs so that we can examine the dmesg state
mount -t kernfs /kern /kern
# pull in the functions that people will use from the shell prompt.
. /.commonutils
. /.instutils

View File

@ -28,7 +28,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: install.sh,v 1.5 1995/10/30 02:14:04 tls Exp $
# $Id: install.sh,v 1.6 1995/11/28 23:57:26 jtc Exp $
# NetBSD installation script.
# In a perfect world, this would be a nice C program, with a reasonable
@ -162,6 +162,23 @@ echo "geometry. This should either be in the User's Manual for your disk,"
echo "or you should have written down what NetBSD printed when booting."
echo "(Note that he geometry that's printed at boot time is preferred.)"
echo ""
echo "You may choose to view the initial boot messages for your system"
echo "again right now if you like."
echo -n "View the boot messages again? [n] "
getresp "n"
case "$resp" in
y*|Y*)
more /kern/msgbuf
;;
*)
echo ""
;;
esac
echo ""
echo "You will now enter the disk geometry information"
echo ""
echo -n "Number of bytes per disk sector? [512] "
getresp 512
bytes_per_sect="$resp"

View File

@ -1,8 +1,8 @@
# $Id: Makefile,v 1.1.1.1 1994/08/29 15:30:19 cgd Exp $
# $Id: Makefile,v 1.2 1995/11/28 23:57:35 jtc Exp $
TOP= ${.CURDIR}/..
.include "${TOP}/Makefile.inc"
IMAGE= upgr-${REV}.fs
IMAGE= upgr${REV}.fs
.include "${TOP}/inst-common/Makefile.inc"

View File

@ -28,7 +28,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: upgrade.sh,v 1.3 1994/10/18 07:03:16 glass Exp $
# $Id: upgrade.sh,v 1.4 1995/11/28 23:57:37 jtc Exp $
# NetBSD upgrade script.
# In a perfect world, this would be a nice C program, with a reasonable
@ -38,7 +38,7 @@ DT=/etc/disktab # /etc/disktab
FSTABDIR=/mnt/etc # /mnt/etc
#DONTDOIT=echo
VERSION=1.0
VERSION=1.1
FSTAB=${FSTABDIR}/fstab
getresp() {
@ -236,7 +236,7 @@ $DONTDOIT cp /tmp/.hdprofile /mnt/.profile
echo ""
echo "Mounting remaining partitions..."
chroot /mnt mount -at ufs > /dev/null 2>&1
chroot /mnt mount -at ffs > /dev/null 2>&1
echo "Done."
echo ""

View File

@ -1,4 +1,4 @@
INSTALLATION NOTES for NetBSD/MACHINE 1.0
INSTALLATION NOTES for NetBSD/MACHINE 1.1
@ -11,36 +11,39 @@ What is NetBSD?
---- -- ------
NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite
-derived system. It is a fully functional UN*X-like system which runs
on several architectures and is being ported to more. NetBSD, as the
name implies, is a creation of the members of the network community
-derived Operating System. It is a fully functional UN*X-like system
which runs on many architectures and is being ported to more. NetBSD,
as the name implies, is a creation of the members of the network community
and without the net it's likely that this release wouldn't have come
about.
NetBSD 1.0 is a milestone release. The hardest part of the 4.4BSD-Lite
integration, the kernel, has been completed and has been running in
"production use" for quite some time. Also, NetBSD 1.0 is the first
true multi-architecture release of NetBSD. At the time of NetBSD 0.9,
the i386 port was considered 'production quality' and the hp300 port was
barely working. The NetBSD 1.0 source supports nine architectures, and
complete binary releases for most of them will be made available.
NetBSD 1.1 is a evolutionary release which contains over a year of
changes to the kernel, user-level utilities, and documentation.
NetBSD 1.0 supports many new and improved features, the most important
relating to file systems. New and improved versions of both the
Berkeley Fast File System and the free implementation of the NFS
protocol were provided, as part of the 4.4-Lite release. The new
versions include such improvements as support for 64-bit file sizes,
for local files, and "lease" support for NFS, to improve performance.
In addition to the file system improvements, many other parts of the
system have been improved considerably. For instance, the virtual
memory code has substantially improved performance, and many of the
kernel's interfaces have been cleaned up.
Continuing the multi-platform tradition, NetBSD has added ports to
atari and mvme68k based machines. Kernel interfaces have continued to
be refined, and now several subsystems and device drivers are shared
among the different ports. You can look for this trend to continue.
Many new user programs have been added in NetBSD 1.0, as well,
NetBSD 1.1 has significantly enhanced the binary emulation subsystem
(which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix
compatibility) and several kernel subsystems have been generalized
to support this more readily. The binary emulation strategy is
aimed at making the emulation as accurate as possible.
NetBSD 1.1 is also the first release to see machine-independent disk
striping. The concatenated disk driver (ccd), which was previously
supported only by the hp300 port, has been vastly improved. Many
bugs were fixed, and explicit references to device-dependent routines
removed and replaced by calls to the generic "vnode operation"
routines. In addition, several features were added, including partition
support, dynamic configuration and unconfiguration via a user space system
utility program, and virtually unlimited number of component devices.
Many new user programs have been added in NetBSD 1.1, as well,
bringing it closer to our goal of supplying a complete UN*X-like
environment. Additionally, support for shared libraries has been
added, for most architectures, allowing a significant savings in both
RAM consumption and disk space.
environment.
#include "whatis"
@ -48,6 +51,31 @@ RAM consumption and disk space.
The Future of NetBSD:
--- ------ -- ------
The NetBSD Foundation was recently incorporated as a non-profit
organization. It's purpose is to encourage, foster and promote the
free exchange of computer software, namely the NetBSD Operating
System. The foundation will allow for many things to be handled more
smoothly than could be done with our previous informal organization.
In particular, it provides the framework to deal with other parties
that wish to become involved in the NetBSD Project. (IN WHAT WAY? Money, donations, etc)
We believe that the NetBSD Foundation will help improve the quality
of NetBSD by:
* providing better organization to keep track of development
efforts, including co-ordination with groups working in
related fields.
* providing a framework to receive donations of goods and
services and to own the resources necessary to run the
NetBSD Project.
* providing a better position from which to undertake
promotional activities.
* periodically organizing workshops for developers and other
interested people to discuss ongoing work.
We hope to have regular releases of the full binary and source trees,
but these are difficult to coordinate, especially with all of the
architectures which we now support! We hope to support even _more_
@ -57,10 +85,8 @@ current practice of making the NetBSD-current development source
available on a daily or nearly-daily basis.
We intend to integrate free, positive changes from whatever sources
will provide them, providing that they are well thought-out and increase
the usability of the system. This includes integrating the remainder of
the 4.4BSD-Lite tape, as quickly as we can ensure that everything works
properly.
will provide them, providing that they are well thought-out and
increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of NetBSD users, because it is for
@ -72,12 +98,12 @@ Sources of NetBSD:
#include "mirrors"
NetBSD 1.0 Release Contents:
NetBSD 1.1 Release Contents:
------ --- ------- --------
The NetBSD 1.0 release is organized in the following way:
The NetBSD 1.1 release is organized in the following way:
.../NetBSD-1.0/
.../NetBSD-1.1/
BUGS Known bugs list (incomplete
and out of date).
@ -87,7 +113,7 @@ The NetBSD 1.0 release is organized in the following way:
LAST_MINUTE Last minute changes.
MIRRORS A list of sites that mirror
the NetBSD 1.0 distribution.
the NetBSD 1.1 distribution.
README.files README describing the
distribution's contents.
@ -103,7 +129,7 @@ The NetBSD 1.0 release is organized in the following way:
In addition to the files and directories listed above, there is one
directory per architecture, for each of the architectures that NetBSD
1.0 has a binary distribution for. There are also
1.1 has a binary distribution for. There are also
'README.export-control' files sprinkled liberally throughout the
distribution tree, which point out that there are some portions of the
distribution (e.g. those containing crypt(3)) that should not be
@ -112,35 +138,39 @@ your fault, not ours.
The source distribution sets can be found in subdirectories of the
"source" subdirectory of the distribution tree. They contain the
complete sources to the system, excluding those portions which should
not be exported from the U.S. (Those are contained in each
architecture's "security" binary distribution set.) The source
distribution sets are as follows:
complete sources to the system. The source distribution sets
are as follows:
gsrc10 This set contains the "gnu" sources, including
dsrc11 This set contains the "domestic" sources. These
sources contain export-restricted encryption code
and should not be exported from the U.S.
[ 140K gzipped, 655K uncompressed ]
gsrc11 This set contains the "gnu" sources, including
the source for the compiler, assembler, groff,
and the other GNU utilities in the binary distribution
sets.
[ 7.7M gzipped, 32.0M uncompressed ]
[ 7.1M gzipped, 30.4M uncompressed ]
ksrc10 This set contains the sources to the NetBSD 1.0
kernel, config(8), config.new(8) and dbsym(8).
[ 4.5M gzipped, 20.8M uncompressed ]
ksrc11 This set contains the sources to the NetBSD 1.1
kernel, config(8), config.old(8) and dbsym(8).
[ 6.0M gzipped, 27.0M uncompressed ]
ssrc10 This set contains the "share" sources, which include
ssrc11 This set contains the "share" sources, which include
the sources for the man pages not associated with
any particular program, the sources for the
typesettable document set, the dictionaries, and more.
[ 2.3M gzipped, 8.5M uncompressed ]
[ 2.4M gzipped, 8.9M uncompressed ]
src10 This set contains all of the NetBSD 1.0 sources which
src11 This set contains all of the NetBSD 1.1 sources which
are not mentioned above.
[ 7.1M gzipped, 33.4M uncompressed ]
[ 9.3M gzipped, 41.6M uncompressed ]
It is worth noting that unless all of the source distribution sets
are installed, you can't rebuild and install the system from scratch,
straight out of the box. However, all that is required to rebuild the
system in that case is a trivial modification to one Makefile.
are installed (except the domestic set), you can't rebuild and install
the system from scratch, straight out of the box. However, all that is
required to rebuild the system in that case is a trivial modification
to one Makefile.
The source distribution sets are distributed as groups of files named
"set_name.xx" where "set_name" is the distribution set name, and "xx"
@ -162,7 +192,7 @@ or to actually extract the files contained in the set:
In each of the source distribution set directories, there is a file
named "CKSUMS" which contains the checksums of the files in that
directory, as generated by the cksum(1) command. You can use cksum to
directory, as generated by the cksum(1) utility. You can use cksum to
check the integrity of the archives, if you suspect that one of the
files is corrupt and have access to a cksum binary.
@ -263,15 +293,23 @@ Also, our thanks go to:
for answering lots of questions, fixing bugs, and doing the various work
they've done.
UC Berkeley's Experimental Computing Facility has provided a home for
sun-lamp, people to look after it, and a sense of humor. Rob
Robertson, too, has added his unique sense of humor to things, and for
a long time provided the primary FTP site for NetBSD.
UC Berkeley's Experimental Computing Facility provided a home for
sun-lamp in the past, people to look after it, and a sense of humor.
Rob Robertson, too, has added his unique sense of humor to things, and
for a long time provided the primary FTP site for NetBSD.
Without CVS, this project would be impossible to manage, so our hats
go off to Brian Berliner, Jeff Polk, and the various other people
who've had a hand in making CVS a useful tool.
Alistair G. Crooks <agc@westley.demon.co.uk> has been producing tar
file snapshot reports for NetBSD-current users, a very valuable
service.
Dave Burgess <burgess@cynjut.infonet.net> has been maintaining the
386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be
recognized for it.
The following people (in alphabetical order) have made donations or
loans of hardware and/or money, to support NetBSD development, and
deserve credit for it:
@ -280,10 +318,6 @@ deserve credit for it:
not able to get in touch with you, to verify that you wanted to be
listed.)
Dave Burgess <burgess@cynjut.infonet.net> has been maintaining the
386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be
recognized for it.
Finally, we thank all of the people who've put sweat and tears into
developing NetBSD since its inception in January, 1993. (Obviously,
there are a lot more people who deserve thanks here. If you're one of
@ -294,38 +328,48 @@ We are:
-- ---
(in alphabetical order)
The NetBSD core team:
Chris G. Demetriou <cgd@sun-lamp.cs.berkeley.edu>
Theo de Raadt <deraadt@sun-lamp.cs.berkeley.edu>
Adam Glass <glass@sun-lamp.cs.berkeley.edu>
Charles Hannum <mycroft@sun-lamp.cs.berkeley.edu>
The NetBSD core group:
J.T. Conklin <jtc@NetBSD.ORG>
Charles Hannum <mycroft@NetBSD.ORG>
Paul Kranenburg <pk@NetBSD.ORG>
The port-masters (and their ports):
Allen Briggs <briggs@mail.vt.edu> (mac68k)
(and the rest of the 'Alice' group)
Theo de Raadt <deraadt@sun-lamp.cs.berkeley.edu> (sparc)
Charles Hannum <mycroft@sun-lamp.cs.berkeley.edu> (i386, hp300)
Chris Hopps <chopps@sun-lamp.cs.berkeley.edu> (amiga)
Adam Glass <glass@sun-lamp.cs.berkeley.edu> (pmax)
Paul Mackerras <paulus@sun-lamp.cs.berkeley.edu> (da30)
Anders Magnusson <ragge@sun-lamp.cs.berkeley.edu> (vax)
Phil Nelson <phil@sun-lamp.cs.berkeley.edu> (pc532)
Gordon Ross <gwr@sun-lamp.cs.berkeley.edu> (sun3)
Allen Briggs <briggs@mail.vt.edu> (mac68k)
Chuck Cranor <chuck@NetBSD.ORG> (mvme68k)
Chris G. Demetriou <cgd@NetBSD.ORG> (alpha)
Charles Hannum <mycroft@NetBSD.ORG> (i386)
Chris Hopps <chopps@NetBSD.ORG> (amiga)
Paul Kranenburg <pk@NetBSD.ORG> (sparc)
Ted Lemon <mellon@NetBSD.ORG> (pmax)
Anders Magnusson <ragge@NetBSD.ORG> (vax)
Phil Nelson <phil@NetBSD.ORG> (pc532)
Gordon Ross <gwr@NetBSD.ORG> (sun3)
Jason Thorpe <thorpej@NetBSD.ORG> (hp300)
Leo Weppelman <leo@NetBSD.ORG> (atari)
Supporting cast:
Steve Allen <wormey@eskimo.com>
John Brezak <brezak@sun-lamp.cs.berkeley.edu>
John Brezak <brezak@NetBSD.ORG>
Dave Burgess <burgess@cynjut.infonet.net>
J.T. Conklin <jtc@sun-lamp.cs.berkeley.edu>
Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>
Adam Glass <glass@NetBSD.ORG>
Brad Grantham <grantham@tenon.com>
Matthew Green <mrg@eterna.com.au>
Michael L. Hitch <osymh@gemini.oscs.montana.edu>
Lawrence Kesteloot <kesteloo@cs.unc.edu>
Paul Kranenburg <pk@sun-lamp.cs.berkeley.edu>
John Kohl <jtk@NetBSD.ORG>
Paul Mackerras <paulus@NetBSD.ORG>
Neil J. McRae <neil@domino.org>
Perry Metzger <perry@NetBSD.ORG>
Herb Peyerl <hpeyerl@beer.org>
Matthias Pfaller <leo@marco.de>
Chris Provenzano <proven@sun-lamp.cs.berkeley.edu>
Chris Provenzano <proven@NetBSD.ORG>
Waldi Ravens <waldi@moacs.indiv.nl.net>
Scott Reynolds <scottr@edsi.org>
Thor Lancelot Simon <tls@netbd.org>
Wolfgang Solfrank <ws@tools.de>
Frank van der Linden <fvdl@NetBSD.ORG>
Christos Zoulas <christos@NetBSD.ORG>
Legal Mumbo-jumbo:
----- ----- -----

View File

@ -6,8 +6,7 @@ out as follows:
binary/ amiga binary distribution sets;
see below.
floppies/ amiga installation and upgrade
>>> ^^^^^^^^ should this be miniroot/?
miniroot/ amiga installation and upgrade
file system images; see below.
security/ amiga security distribution;
@ -17,8 +16,7 @@ out as follows:
installation utilities; see
installation section, below.
There are two amiga file system images to be found in the "amiga/floppy"
>>> ^^^^^^
There are two amiga file system images to be found in the "amiga/miniroot"
subdirectory of the NetBSD 1.1 distribution. One of them is a upgrade
image and one is an installation image. They are described in more
detail below. There are gzipped versions of each available, for easier
@ -43,16 +41,16 @@ Upgrade file system:
This file contains a BSD root file system setup to help
you upgrade a previous version of NetBSD. This includes
converting existing partitions
and mounting your root and /usr partitions and getting
ready to extract (and possibly first fetching) the distribution
sets. There is enough on this file system to allow you to
make a slip or ppp connection, configure an ethernet, mount an
NFS file system or ftp. You can also load distribution sets from
a SCSI tape, from one of your existing AmigaDOS partitions, or
from an existing NetBSD partition.
converting existing partitions and mounting your root and
/usr partitions and getting ready to extract (and possibly
first fetching) the distribution sets. There is enough on
this file system to allow you to make a slip or ppp connection,
configure an ethernet, mount an NFS file system or ftp.
You can also load distribution sets from a SCSI tape, from
one of your existing AmigaDOS partitions, or from an existing
NetBSD partition.
This file is named "inst-11.fs".
This file is named "upgr-11.fs".
The NetBSD/amiga binary distribution sets contain the binaries which
comprise the NetBSD 1.1 release for the amiga. There are seven binary
@ -66,8 +64,7 @@ subdirectory of the NetBSD 1.1 distribution tree, and are as follows:
system to run and be minimally functional. It
includes shared library support, and excludes
everything described below.
[ 7M gzipped, 19M uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 7M gzipped, 20M uncompressed ]
comp11 The NetBSD/amiga Compiler tools. All of the tools
relating to C, C++, and FORTRAN (yes, there are two!).
@ -78,8 +75,7 @@ subdirectory of the NetBSD 1.1 distribution tree, and are as follows:
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.
[ 4M gzipped, 12M uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 5M gzipped, 15M uncompressed ]
etc11 This distribution set contains the system
configuration files that reside in /etc and in several
@ -88,32 +84,27 @@ subdirectory of the NetBSD 1.1 distribution tree, and are as follows:
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.)
[ 50K gzipped, 280K uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 60K gzipped, 340K uncompressed ]
games11 This set includes the games and their manual pages.
[ 1M gzipped, 3M uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 3M gzipped, 7M uncompressed ]
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.
[ 730K gzipped, 3M uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 850K gzipped, 3M uncompressed ]
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.
[ 2M gzipped, 6M uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 2M gzipped, 7M uncompressed ]
text11 This set includes NetBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 784K gzipped, 3M uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The amiga security distribution set is named "secr11" and can be found
in the "amiga/security" subdirectory of the NetBSD 1.1 distribution
@ -122,8 +113,7 @@ 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, 300K uncompressed ]
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
United States and Canada.) [ 128K gzipped, 307K uncompressed ]
The amiga binary distribution sets are distributed in the same form as
the source distribution sets; catted together, the members of a set

View File

@ -1,7 +1,6 @@
NetBSD/amiga 1.1 runs on any amiga that has a 68020 or better CPU
with some form of FPU and MMU. The minimal configuration requires
4M of RAM and about 65M of disk space. To install the entire system
>>> ^^^
requires much more disk space, and to run X or compile the system,
more RAM is recommended. (4M of RAM will actually allow you to
compile, however it won't be speedy. X really isn't usable on a
@ -13,13 +12,16 @@ Here is a table of recommended HD partition sizes for a full install:
user (/usr) 65M 100M 45M 80M
swap ----- 2M for every M ram -----
local (/local) up to you
>>> adjust sizes?
As you may note the recommended size of /usr is 20M greater than
needed. This is to leave room for a kernel source and compile tree
as you will probably want to compile your own kernel. (GENERIC is
large and bulky to accommodate all people).
If you only have 4M of fast memory, you should make your swap partition
larger, as your system will be doing much more swapping.
Supported devices include:
A4000/A1200 IDE controller.
SCSI host adapters:
@ -34,12 +36,14 @@ Supported devices include:
GVP Spectrum.
Piccalo.
A2410.
Cybervision 64.
Ethernet controllers:
A2065 Ethernet
Hydra Ethernet
ASDG Ethernet
A4066 Ethernet
Ariadne Ethernet
Quicknet Ethernet
Arcnet controllers:
A2060 Arcnet
Tape drives:

View File

@ -11,36 +11,48 @@ installed on your hard disk. If you wish to stop the installation,
you may hit Control-C at any prompt, but if you do, you'll have to
begin again from scratch.
>>> transfer installation file system to the swap partition.
>>> Does this go here, or in the hard disk prep section?
Transfer the install miniroot filesystem onto the hard disk
partition used by NetBSD for swapping, as described in the
"Preparing your System for NetBSD Installation" section above.
You then need to have "ixemul.library" in your LIBS: directory
on AmigaDOS. You also need to have the "loadbsd" program
in your command path. If AmigaDOS complains about loadbsd
not being an executable file, be sure that the "Execute"
protection bit is set. If not, set it with the command:
Protect loadbsd add e
>>> Getting loadbsd, ixemul.library, and netbsd onto AmigaDOS
>>> partition.
Next you need to get yourself into NetBSD by loading the
kernel from AmigaDOS with loadbsd like so:
loadbsd -b netbsd
If you have an AGA machine, and your monitor will handle
the dblNTSC mode, you may also include the "-A" option to
enable the dblNTSC display mode.
You should see the screen clear and some information about
your system as the kernel configures the hardware. Note which
hard disk device(s) are configured (sd0, sd1, etc). Then
you will be prompted for a root device. At this time type
'sd0*'.
>>> Need to document what device number to actually use.
'sd0*', where '0' is the device which contains the swap
partition you created during the hard disk preparation.
The system should continue to boot. For now ignore WARNING:
messages about bad dates in clocks and swap space. Eventually
>>> ^^^^^^^^^^???
you will be asked to enter the pathname of the shell, just
hit return. After a short while you should see a welcome
message and a prompt, asking if you wish to proceed with the
installation.
messages about bad dates in clocks. Eventually you will be
asked to enter the pathname of the shell, just hit return.
After a short while you should see a welcome message and a
prompt, asking if you wish to proceed with the installation.
If you wish to proceed, enter "y" and then return.
If you have configured your hard drive[s] correctly it
should find the drive and partition that you selected to
use as your root.
use as your root. You will be prompted for which device
you want to use for your root. If you have multiple disks
present with root partitions defined, you will need to be
sure you enter the device name of the correct partition you
want to install NetBSD on.
YOU ARE NOW AT THE POINT OF NO RETURN. If you confirm that
you want to install NetBSD, your hard drive will be modified,
@ -192,7 +204,6 @@ begin again from scratch.
for the installation files. /mnt/usr/distrib is
suggested.
>>> Document using ppp or slip?
Configure the appropriate ethernet interface i.e. le0
if you have a 2065 or ed0 if you have a AMIGNET from
Hydra Systems.
@ -211,6 +222,11 @@ begin again from scratch.
ifconfig ed0 128.32.240.167 netmask 0xffffff00
You should also be able to use SLIP or PPP as the network
connection.
[XXX instructions for ppp or slip would be usefull
perhaps the next release]
If the NFS server or FTP server is not on a directly-
connected network, you should set up a route to it
with the command:
@ -267,8 +283,9 @@ network configuration information.
Once you have supplied `Configure' all that it requests, your machine
will be configured well enough that when you reboot it it will
almost be a completely functional NetBSD system. Note you should
ignore the errors from `chown' they will be corrected shortly.
almost be a completely functional NetBSD system.
>>> Copy the kernel from the miniroot filesystem at this point <<<
Once you are done with `Configure', halt the system with the "halt"
command (wait for "halted" to be displayed) and reboot. Then again
@ -282,12 +299,6 @@ like so:
mount -av
Next you need to re-make your devices to get the ownership correct:
cd /dev
MAKEDEV all
>>> Is this step still needed? - check on it!
Your system is now complete but not completely configured; you
should adjust the /etc/sendmail.cf file as necessary to suit your
site and/or disable sendmail and other network related programs.
@ -295,6 +306,15 @@ These things can be found in /etc/netstart. Use vi, if you installed
the man pages you can type `man vi' or `man ed' for instructions
on how to use these somewhat non-intuitive editors.
You should also put a copy of the netbsd kernel in your root partition.
This can be done easily by mounting the AmigaDOS partition containing
the kernel you used to start NetBSD and copying the "netbsd" file to
the root:
mount -r -t ados /dev/sd0d /mnt
cp /mnt/netbsd /
(where /dev/sd0d is the AmigaDOS partition where you have netbsd, and
/mnt/netbsd is the appropriate path of the netbsd file).
Once you are done with the rest of configuration unmount your file
systems and halt your system, then reboot:
@ -310,5 +330,3 @@ functional:
When it boots off of the hard drive, you will have a complete
NetBSD system! CONGRATULATIONS! (You really deserve them!!!)
>>> Missing the step to transfer the netbsd kernel to /

View File

@ -1,7 +1,28 @@
This product includes software developed by Klaus Burkert.
This product includes software developed by Michael van Elst.
This product includes software developed by Bernd Ernesti.
This product includes software developed by Michael L. Hitch.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Timo Rossi
This product includes software developed by Mika Kortelainen.
This product includes software developed by Michael L. Hitch
This product includes software developed by Jukka Marin.
This product includes software developed by Kari Mettinen.
This product includes software developed by Brad Pepers.
This product includes software developed by Ignatios Souvatzis.
This product includes software developed by Ezra Story.
This product includes software developed by Lutz Vieweg.
This product includes software developed by Daniel Widenfalk.
This product includes software developed by Markus Wild.
>>> any others?

View File

@ -76,5 +76,46 @@ Preparing you hard disk with HDToolBox:
Once this is done NetBSD/amiga will be able to recognize your
disks and which partitions it should use.
>>> Should the miniroot transfer to the swap partition instructions
>>> go here?
Transferring the miniroot filesystem:
The NetBSD/amiga installation or upgrade now uses a "miniroot"
fileystem which is installed on the partition used by NetBSD
for swapping. This removes the requirement of using a floppy
disk for the filesystem used by the installation or upgrade
process. It also allows more utilities to be present on the
filesystem than would be available when using an 880K floppy
disk.
Once the hard disk has been prepared for NetBSD, the appropriate
miniroot filesystem (inst-11.fs for a new install or upgr-11.fs
for an upgrade) is transferred to the swap partition configured
during the hard disk prep (or the existing swap parition in
the case of an upgrade). The xstreamtodev utility provided in
the "amiga/utilities" directory can be used on AmigaDOS to
transfer the filesystem for either a new installation or an
upgrade. The filesystem can also be transferred on an existing
NetBSD system for an update by using dd. This should only be
done after booting NetBSD into single-user state. It may also
be possible to shutdown to single-user, providing that the
single-user state processes are not using the swap partition.
On AmigaDOS, the command:
xstreamtodev -input=inst-11.fs -rdb-name=<swap partition>
where <swap partition> is the name you gave to the NetBSD
partition to be used for swapping. Use upgr-11.fs if you
are going to do an upgrade of an existing NetBSD system. If
xstreamtodev is unable to determine the SCSI driver device
name or the unit number of the specified partition, you may
also need to include the option "-device=<driver.name>" and/or
"-unit=<SCSI unit number>".
To transfer the miniroot using NetBSD, you should be booted up
in single user state on the current NetBSD system, or use the
"shutdown now" command to shutdown to single-uyser state. Then
copy the miniroot using dd:
dd if=upgr-11.fs of=/dev/rsd0b
where /dev/rsd0b should be the device path of the swap partition
your system is configured to use. Once the file is copied,
reboot back to AmigaDOS to boot the upgrade kernel. NOTE: the
release kernel is a "generic" kernel, and requires that the
swap partition be on the same device as the root partition.

View File

@ -3,22 +3,19 @@ to make users upgrade by compiling and installing the 1.1 sources, and
it would be very difficult to even compile a set of instructions that
allowed them to do so. Because of the various changes to the system,
the largest being the 64-bit file size support and shared libraries,
>>> just what are the major differences between 1.0 and 1.1??
it is impractical to upgrade by recompiling from the sources and
installing.
>>> no kernel-copy!
To do the upgrade, you must have the appropriate kernel-copy floppy
image on a disk, and the upgr-11.fs floppy image on another. You must
>>>
also have at least the "base11" binary distribution set available,
so that you can upgrade with it, using one of the upgrade methods
described above. Finally, you must have sufficient disk space
available to install the new binaries. Since the old binaries are
being overwritten in place, you only need space for the new binaries,
which weren't previously on the system. If you have a few megabytes
free on each of your root and /usr partitions, you should have enough
space.
To do the upgrade, you must have the NetBSD kernel on AmigaDOS and
you must transfer the upgrade filesystem upgr-11.fs onto the swap
partition of the NetBSD hard disk. You must also have at least the
"base11" binary distribution set available, so that you can upgrade
with it, using one of the upgrade methods described above. Finally,
you must have sufficient disk space available to install the new
binaries. Since the old binaries are being overwritten in place,
you only need space for the new binaries, which weren't previously
on the system. If you have a few megabytes free on each of your
root and /usr partitions, you should have enough space.
Since upgrading involves replacing the kernel, and most of the system
binaries, it has the potential to cause data loss. You are strongly
@ -28,20 +25,24 @@ beginning the upgrade process.
To upgrade your system, follow the following instructions:
>>> transfer upgrade file system image to swap partition
>>> should this be in the hard disk prep section?
Transfer the upgrade miniroot filesystem onto the hard disk
partition used by NetBSD for swapping, as described in the
"Preparing your System for NetBSD Installation" section above.
Boot your machine using of the appropriate kernel-copy floppy.
When presented with the boot prompt (the prompt begins with
"Boot" and ends with ":-"), hit return.
Now boot up NetBSD using the 1.1 kernel using the loadbsd
command:
While booting, you will probably see several warnings. You
should be warned that no swap space is present, and that
>>> ^^^^^^^^^^^^^^^^^^^^^
init(8) cannot find /etc/rc. Do not be alarmed, these are
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
completely normal. When you reach the prompt asking you for a
shell name, just hit return.
loadbsd -b netbsd
You should see the screen clear and some information about
your system as the kernel configures the hardware. Note which
hard disk device is configured that contains your root and
swap partition. When prompted for the root device, type
'sd0*' (replacing 0 with the disk number that NetBSD used for
your root/swap device). The '*' character indicates that the
root filesystem is contained on the swap partition.
When you reach the prompt asking you for a shell name, just
hit return.
You will be presented with some information about the upgrade
process and a warning message, and will be asked if you wish
@ -59,9 +60,6 @@ To upgrade your system, follow the following instructions:
probably do it manually after the install process is complete,
by using "fsck -c 2". Read the fsck(8) manual page for more
details.
>>> Is this needed for 1.0 to 1.1 upgrade? Or mention that the upgrade
>>> should be done if it wasn't previously done? [It shouldn't hurt
>>> to run through the upgrade steps.]
The upgrade program will then check your root file system,
and, if you approved, will upgrade it to the new file system
@ -78,7 +76,6 @@ To upgrade your system, follow the following instructions:
If you don't already have the NetBSD distribution sets on your
disk, look in the installation section for information on how
to transfer them to your disk.
>>> NetBSD or AmigaDOS partitions...
Once the distribution sets are transferred to your disk,
continue here. (Obviously, if the NetBSD distribution sets
@ -113,8 +110,9 @@ To upgrade your system, follow the following instructions:
up the installation, by remaking some system databases. When
it is complete, you should use "halt" to halt the system.
>>> transfer new kernel to /
You will probably also want to copy the release "netbsd" kernel
image to your root at some point.
Your system has now been upgraded to NetBSD 1.1.
After a new kernel has been copied to your hard disk, your
@ -150,7 +148,6 @@ After a new kernel has been copied to your hard disk, your
NFS. (Note that the information for mounts of type "ufs",
i.e. Fast File Systems, are contained in the mount(8) man
page.)
>>> Is this needed for 1.0 -> 1.1 upgrade?
Finally, you will want to delete old binaries that were part
of the version of NetBSD that you upgraded from and have since

View File

@ -1,4 +1,5 @@
>>> What should go here?
This is the first public release of NetBSD for the Amiga line of
computers.
This is the second public release of NetBSD for the Amiga line of
computers. Several additional graphics and network boards are now
supported. Some of the SCSI drivers have been enhanced and (hopefully)
improved.

View File

@ -5,28 +5,11 @@ Installation is supported from several media types, including:
FTP
NetBSD partitions, if doing an upgrade.
>>> Transfering install/upgrade file system image to swap partition
No matter what you do, however, you'll need to have one disk handy,
on which you will put the install floppy image.
All the images are available from the directory "amiga/floppies",
>>> ^^^^^^^^
under the root of the NetBSD tree at your favorite archive site.
If you are using NetBSD/amiga to make the floppies, you should use
the command dd(1) to write the raw floppy images (.fs files) to
the disk. To write onto fd0 use:
dd if=inst-11.fs of=/dev/rfd0a bs=11b
If you are using AmigaDOS to make the floppies, you should
use the rawwrite utility, provided in the directory
"amiga/utilities" in the distribution. To write the image to
the floppy in df0 use (from cli):
rawwrite 0 inst-11.fs
>>> fix above to document file system transfer to swap paritition
>>> using xstreamtodev
The install or upgrade miniroot filesystem needs to be transferred
to the NetBSD swap partition. This can be done from AmigaDOS in
the case of a new install or upgrade, or from NetBSD when doing an
upgrade. See the "Preparing your System for NetBSD Installation"
section for details.
The steps necessary to prepare the distribution sets
for installation depend on which method of installation

View File

@ -233,7 +233,7 @@ like so:
Next you need to re-make your devices to get the ownership correct:
cd /dev
MAKEDEV all
./MAKEDEV all
Your system is now complete but not completely configured; you
should adjust the /etc/sendmail.cf file as necessary to suit your

View File

@ -33,4 +33,4 @@ Once you are done installing the upgrade sets, then reboot:
Now you can boot your upgraded system as usually, but take the
new kernel! To finish up, you should rebuild your /dev-directory:
cd /dev
MAKEDEV all
./MAKEDEV all

View File

@ -1,8 +1,8 @@
The i386-specific portion of the NetBSD 1.0 release is found in the
The i386-specific portion of the NetBSD 1.1 release is found in the
"i386" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../NetBSD-1.0/i386/
.../NetBSD-1.1/i386/
INSTALL Installation notes; this file.
binary/ i386 binary distribution sets;
@ -19,7 +19,7 @@ out as follows:
installation section, below.
There are four i386 floppy images to be found in the "i386/floppy"
subdirectory of the NetBSD 1.0 distribution. Two of them are bootable
subdirectory of the NetBSD 1.1 distribution. Two of them are bootable
kernel-copy floppies, one is an installation floppy, and one is an
upgrade floppy. They are all described in more detail below. There
are gzipped versions of each available, for easier downloading. (The
@ -36,41 +36,64 @@ Bootable Kernel-copy floppies:
disk.
There are two different kernel copy floppy images,
"kcaha-10.fs", and "kcbt-10.fs". They are identical except
that the first has the driver for the Adaptec 1542 SCSI host
adapter and does not contain the driver for the Buslogic 74x
SCSI host adapters, and vice-versa for the second. (All other
drivers are present on both disks.)
"kcadp11.fs", and "kcoth11.fs". They are identical except
that the kcadp floppy has the drivers for the supported Adaptec SCSI
controllers -- the Adaptec 1520, 1522, 1540, 1542, 1740, 1742, 1744,
and 2940 SCSI host adapters and the AIC6x60 and AIC7870 chips on
motherboards or other brands of SCSI controllers -- and does not
contain the drivers for any other SCSI host adapters, which
are in the kernel on the kcoth floppy. (The kernels on the install
disks are otherwise identical.)
Please note that because of space considerations the kernel
copy floppies no longer contain drivers that are not needed
during installation -- in particular, no drivers needed to run
the X Window System are available in these kernels. It is
recommended that you configure a custom kernel following
installation.
For those that cannot configure a custom kernel, two "generic"
kernel images, named "netbsd-adp.gz" and "netbsd-oth.gz", have
been placed in the binaries directory. These are identical
except that "netbsd-adp.gz" contains support for Adaptec SCSI
controllers, but no other SCSI controllers, and
"netbsd-oth.gz" contains support only for SCSI controllers
other than the Adaptec. (These are similar in nature to the
kernels on the kernel copy floppies but with additional device
support.) It is strongly encouraged that you build a custom
kernel for your installation rather than use a prebuilt generic
kernel.
Installation floppy:
This disk contains the software necessary to prepare your hard
drive for NetBSD and install the NetBSD distribution. It is
not bootable, and must be used in conjunction with one of the
kernel-copy floppies. This floppy is named "inst-10.fs".
kernel-copy floppies. This floppy is named "inst-11.fs".
Upgrade floppy:
This disk contains the software to be used in upgrading the
system from a previous version of NetBSD. It is not bootable,
and must be used in conjunction with one of the kernel-copy
floppies. This floppy is named "upgr-10.fs"
floppies. This floppy is named "upgr11.fs"
The NetBSD/i386 binary distribution sets contain the binaries which
comprise the NetBSD 1.0 release for the i386. There are seven binary
comprise the NetBSD 1.1 release for the i386. There are seven binary
distribution sets, and the "security" distribution set. The binary
distribution sets can be found in subdirectories of the "i386/binary"
subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
subdirectory of the NetBSD 1.1 distribution tree, and are as follows:
base10 The NetBSD/i386 1.0 base binary distribution. You
base11 The NetBSD/i386 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.2M gzipped, 16.7M uncompressed ]
[ 7.5M gzipped, 19.5M uncompressed ]
comp10 The NetBSD/i386 Compiler tools. All of the tools
comp11 The NetBSD/i386 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,
@ -79,45 +102,49 @@ subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
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.2M gzipped, 12.9M uncompressed ]
[ 4.9M gzipped, 15.0M uncompressed ]
etc10 This distribution set contains the system
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.)
[ 50K gzipped, 263K uncompressed ]
[ 63K gzipped, 338K uncompressed ]
games10 This set includes the games and their manual pages.
[ 1.0M gzipped, 2.7M uncompressed ]
games11 This set includes the games and their manual pages.
[ 2.8M gzipped, 6.9M 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.
[ 0.7M gzipped, 2.8M uncompressed ]
[ 0.8M gzipped, 3.4M 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.9M gzipped, 6.6M 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.
[ 0.8M gzipped, 2.8M uncompressed ]
[ 0.8M gzipped, 2.9M uncompressed ]
The i386 security distribution set is named "secr10" and can be found
in the "i386/security" subdirectory of the NetBSD 1.0 distribution
The i386 security distribution set is named "secr11" and can be found
in the "i386/security" subdirectory of the NetBSD 1.1 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.) [ 114K gzipped, 253K uncompressed ]
algorithm) and the binaries which depend on it, as well as the "bdes"
DES encryption program. You do not need this distribution set to use
encrypted passwords in your password file; the "base11" distribution
includes a crypt library which can perform only the decryption function.
The "secr11" distribution set can be found only on those sites which
carry the complete NetBSD distribution and which 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.)
[ 154K gzipped, 358K uncompressed ]
The i386 binary distribution sets are distributed in the same form as
the source distribution sets; catted together, the members of a set

View File

@ -1,8 +1,9 @@
NetBSD/i386 1.0 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems
NetBSD/i386 1.1 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems
with 386-family processors, with or without math coprocessors. It
does NOT support MCA systems, such as some IBM PS/2 systems. The
minimal configuration requires 4M of RAM and 40M of disk space. To
install the entire system requires much more disk space, and to run X
minimal configuration is said to require 4M of RAM and 50M of disk space,
though we do not know of anyone running with a system quite this minimal today.
To install the entire system requires much more disk space, and to run X
or compile the system, more RAM is recommended. (4M of RAM will
actually allow you to run X and/or compile, but it won't be speedy.
Note that until you have around 16M of RAM, getting more RAM is more
@ -12,17 +13,30 @@ Supported devices include:
Floppy controllers.
MFM, ESDI, IDE, and RLL hard disk controllers.
SCSI host adapters:
Adaptec AHA-154xA, -B, -C, and -CF [only on kcaha floppy]
[Adaptec host adapters only on kcadp floppy]
Adaptec AHA-154xA, -B, -C, and -CF
Adaptec AHA-174x
Adaptec AIC-6260- and AIC-6360-based boards, including
Adaptec AIC-6260 and AIC-6360 based boards, including
the Adaptec AHA-152x and the SoundBlaster SCSI
host adapter. (Note that you cannot boot from
these boards if they do not have a boot ROM,
and many do not.)
Buslogic 54x [AHA-154x clones; only on kcaha floppy]
Buslogic 445, 74x, 9xx [only on kcbt floppy]
NCR 53C810 PCI SCSI host adapter
these boards if they do not have a boot ROM;
only the AHA-152x and motherboards using this chip
are likely to be bootable, consequently.)
Adaptec AHA-294x[W] cards and some onboard PCI designs using
the AIC7870 chip. This driver does *not* currently
work with non-PCI AIC-7xxx boards or the Adaptec 3940.
Buslogic 54x (Adaptec AHA-154x clones; driver on kcadp floppy)
[Other host adapters only on kcoth floppy]
BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series
of BusLogic SCSI adapters)
Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters
Ultrastor 14f, 34f, and (possibly) 24f
Seagate/Future Domain ISA SCSI adapter cards, including
ST01/02
Future Domain TMC-885
Future Domain TMC-950
MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not
all of the display adapters NetBSD/i386 can work with
are supported by X. See the XFree86 FAQ for more
@ -31,35 +45,56 @@ Supported devices include:
8250/16450-based ports
16550-based ports
AST-style 4-port serial boards [*]
BOCA 8-port serial cards [*]
Cyclades Cyclom-{4, 8, 16}Y serial boards [*]
IBM PC-RT 4-port serial boards [*]
Parallel ports.
Ethernet controllers:
Ethernet adapters:
AMD LANCE and PCnet-based ISA Ethernet adapters [*], including:
Novell NE1500T
Novell NE2100
Kingston 21xx
AMD PCnet-based PCI Ethernet adapters, including:
BOCALANcard/PCI
AT&T StarLAN 10, EN100, and StarLAN Fiber
3COM 3c501 [*]
3COM 3c501
3COM 3c503
3COM 3c505 [*]
3COM 3c507
3COM 3c509 and 3c579
Digital DEPCA [*]
3COM 3c509 and 3c579 (But not the PCI 3c59X series)
Digital DC21x4x-based PCI Ethernet adapters, including:
SMC EtherPower 10, 10/100 (PCI only!)
Znyx ZX34X
Cogent EM100
Digital DE450
Digital DE500
BICC Isolan [* and not recently tested]
Intel EtherExpress 16
SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards
SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards)
Novell NE1000, NE2000
Novell NE2100 [* and not recently tested]
Tape drives:
Most SCSI tape drives
QIC-02 and QIC-36 format (Archive- and Wangtek-
compatible) tape drives [*]
compatible) tape drives [*] [+]
CD-ROM drives:
Mitsumi CD-ROM drives [*]
Mitsumi CD-ROM drives [*] [+]
[Note: The Mitsumi driver device probe is known
to cause trouble with several devices!]
Most SCSI CD-ROM drives
Mice:
"Logitech"-style bus mice [*]
"Microsoft"-style bus mice [*]
"PS/2"-style mice [*]
"Logitech"-style bus mice [*] [+]
"Microsoft"-style bus mice [*] [+]
"PS/2"-style mice [*] [+]
Serial mice (no kernel support necessary)
Sound Cards:
SoundBlaster [*] [+]
Gravis Ulrasound and Ultrasound Max [*] [+]
[The following drivers are not extensively tested]
Personal Sound System [*] [+]
Windows Sound System [*] [+]
ProAudio Spectrum [*] [+]
Miscellaneous:
SoundBlaster [*]
Drivers for hardware marked with "[*]" are NOT included on the
distribution floppies. Except as noted above, all other drivers are
@ -69,18 +104,31 @@ NetBSD normally allows more, though, so if you have more than one, you
can use all of them by compiling a custom kernel once NetBSD is
installed.
Support for devices marked with "[+]" IS included in the "generic" kernels,
although it is not in the kernels which are on the distribution floppies.
Hardware the we do NOT currently support, but get many questions
about:
Adaptec AIC-7770-based SCSI host adapters (including the
Adaptec AHA-274x, AHA-284x, and AHA-294x families).
Intel EtherExpress Ethernet boards.
Adaptec AHA-274x, AHA-284x families).
NCR 5380-based SCSI host adapters.
PCMCIA devices.
APM power management -- if your system supports it, turn it off!
PCMCIA ("PC Card") devices, including some miniature "IDE" hard disks.
QIC-40 and QIC-80 tape drives. (Those are the tape drives
that connect to the floppy disk controller.)
WD-7000 SCSI host adapters.
PCI-PCI bridges and cards which include them, such as the AHA-394x
SCSI host adapter and some DC21x4x-based multi-Ethernet cards.
3Com 3c59x series PCI Ethernet and Fast Ethernet adapters.
Multiprocessor Pentium and Pentium Pro systems. (Though they should
run fine using one processor only.)
Intel EtherExpress 100 Fast Ethernet adapters.
Digital DEFPA PCI FDDI adapters (support barely missed this release;
it works in other ports, and will work in this one in the
next release)
We are planning future support for most of these devices.
We are planning future support for many of these devices.
To be detected by the distributed kernels, the devices must
be configured as follows:
@ -102,22 +150,22 @@ Floppy controller
fdc0 0x3f0 6 2 [supports two disks]
AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters
aha0 0x330 any any [only on kcaha kernel floppy]
aha0 0x330 any any [only on kcadp kernel floppy]
AHA-174x SCSI host adapters (in enhanced mode)
ahb0 any any any
ahb0 any any any [only on kcadp kernel floppy]
BT445, BT74x, or BT9xx SCSI host adapters
bt0 0x330 any any [only on kcbt kernel floppy]
bt0 0x330 any any [only on kcoth kernel floppy]
Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters
uha0 0x330 any any
uha0 0x330 any any [only on kcoth kernel floppy]
AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters
aic0 0x340 11 6
aic0 0x340 11 6 [only on kcadp kernel floppy]
NCR 53C810 PCI SCSI host adapter
ncr0 any any any
Symbios Logic/NCR 53C8xx based PCI SCSI host adapters
ncr0 any any any [only on kcoth kernel floppy]
SCSI disks sd0 first SCSI disk (by SCSI id)
sd1 second SCSI disk (by SCSI id)
@ -141,3 +189,11 @@ Novell NE1000, or NE2000 Ethernet boards
AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards
ie0 0x360 7 iomem 0xd0000
PCNet-PCI based Ethernet boards; see above for partial list
le0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
DC21x4x based Ethernet boards; see above for partial list
de0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]

View File

@ -56,7 +56,7 @@ process again from scratch.
Once you have reached that prompt, remove the kernel-copy
floppy from the floppy drive. Make sure that the installation
disk (the "inst-10" floppy) is writable, insert it into the
disk (the "inst-11" floppy) is writable, insert it into the
floppy drive, and hit any key.
You will then be presented with the NetBSD kernel boot
@ -223,12 +223,12 @@ process again from scratch.
Run the "Extract" command once for each distribution
set you wish to install. For instance, if you wish to
install the "base10" distribution set, followed by the
"man10" distribution set, and finally the "etc10"
install the "base11" distribution set, followed by the
"man11" distribution set, and finally the "etc11"
distribution set, use the commands:
Extract base10
Extract man10
Extract etc10
Extract base11
Extract man11
Extract etc11
For each extraction, it will ask you if the extraction
should be verbose. If you reply affirmatively, it
@ -283,9 +283,9 @@ process again from scratch.
hitting return at the prompt.
Use the "Extract" command to extract the distribution
set. For instance, if you're extracting the "base10"
set. For instance, if you're extracting the "base11"
set, use the command:
Extract base10
Extract base11
You will be asked if you wish the extraction to be
verbose. If you reply affirmatively, the name of each
file being extracted will be printed.
@ -403,7 +403,7 @@ process again from scratch.
Once you have finished extracting all of the distribution sets
that you wish to install, and are back at the "#" prompt, you
are ready to configure your system. The configuration utility
expects that you have installed the "base10" and "etc10"
expects that you have installed the "base11" and "etc11"
distribution sets. If you have not, you will not be able to
run it successfully (nor will you have a functional system, in
any case). To configure your newly-installed NetBSD system,
@ -415,8 +415,8 @@ process again from scratch.
Kernel Installation:
Enter "halt" at the prompt to halt the system. When the
system is halted, remove the "inst-10" floppy from the floppy
drive, and replace it with the NetBSD 1.0 kernel-copy floppy
system is halted, remove the "inst-11" floppy from the floppy
drive, and replace it with the NetBSD 1.1 kernel-copy floppy
that you previously booted from. Reboot with that floppy.
with that floppy.
@ -445,13 +445,13 @@ Kernel Installation:
Once the system is halted, remove the kernel-copy floppy from
the floppy disk drive, and hit any key to reboot.
Congratulations, you have successfully installed NetBSD 1.0. When you
Congratulations, you have successfully installed NetBSD 1.1. When you
reboot into NetBSD, you should log in as "root" at the login prompt.
There is no initial password, but if you're using the machine in a
networked environment, you should create yourself an account and
protect it and the "root" account with good passwords.
Some of the files in the NetBSD 1.0 distribution might need to be
Some of the files in the NetBSD 1.1 distribution might need to be
tailored for your site. In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc will
probably need to be modified, as well. If you are unfamiliar with

View File

@ -15,18 +15,33 @@ Second, if you are using a disk controller which supports disk
geometry translation, be sure to use the same parameters for NetBSD as
for DOS or the other operating systems installed on your disk. If you
do not, it will be much harder to make NetBSD properly coexist with
them.
them. Utilities exist which will print out the disk geometry which DOS
sees; some versions of DOS "fdisk" also do this. If you have an "EIDE"
hard disk, DOS and NetBSD probably won't see the same geometry, and you
must be careful to find out the DOS geometry and tell NetBSD about it
during the installation.
Third, use the DOS "fdisk" program or another partition editor to
Third (but related to the second point above), if you are using a hard
disk with more sectors than DOS or your controller's BIOS supports without
some kind of software translation utility or other kludge, you MUST
BE SURE that all partitions which you want to boot from must start below
cylinder 1024 by the BIOS's idea of the disk, and that all DOS partitions
MUST EXIST ENTIRELY BELOW cylinder 1024, or you will either not be able to
boot NetBSD, not be able to boot DOS, or you may experience data loss or
filesystem corruption. Be sure you aren't using geometry translation that
you don't know about, but that the DOS "fdisk" program does!
Fourth, use the DOS "fdisk" program or another partition editor to
repartition your hard disk. Create a partition of at least 40M in
size, and note its starting offset and its length (preferably in units
of disk sectors or cylinders). You will need that information when
installing NetBSD (and if the offset and length are not in those
units, you will have to convert them). Once you have created the new
NetBSD partition, mark it as having a partition type of 0xA5 (165, in
decimal). If you used "fdisk" to partition your disk, you will
probably have to use a different partition editor to mark the
partition with the correct type.
size (preferably much larger), and note its starting offset and its
length (preferably in units of disk sectors or cylinders). You will
need that information when installing NetBSD (and if the offset and
length are not in those units, you will have to convert them). Once
you have created the new NetBSD partition, mark it as having a
partition type of 0xA5 (165, in decimal). If you used "fdisk" to
partition your disk, you will probably have to use a different
partition editor to mark the partition with the correct type.
Finally, do whatever is necessary to restore order to the partition
you took space away from. If it was a DOS partition, you probably

View File

@ -1,14 +1,13 @@
The upgrade to NetBSD 1.0 is a binary upgrade; it would be prohibitive
to make users upgrade by compiling and installing the 1.0 sources, and
The upgrade to NetBSD 1.1 is a binary upgrade; it would be prohibitive
to make users upgrade by compiling and installing the 1.1 sources, and
it would be very difficult to even compile a set of instructions that
allowed them to do so. Because of the various changes to the system,
the largest being the 64-bit file size support and shared libraries,
it is impractical to upgrade by recompiling from the sources and
installing.
allowed them to do so. Because of the many changes to the system, it
is difficult impractical to upgrade by recompiling from the sources
and installing.
To do the upgrade, you must have the appropriate kernel-copy floppy
image on a disk, and the upgr-10.fs floppy image on another. You must
also have at least the "base10" binary distribution set available,
image on a disk, and the upgr11.fs floppy image on another. You must
also have at least the "base11" binary distribution set available,
so that you can upgrade with it, using one of the upgrade methods
described above. Finally, you must have sufficient disk space
available to install the new binaries. Since the old binaries are
@ -31,7 +30,7 @@ To upgrade your system, follow the following instructions:
"Boot" and ends with ":-"), hit return.
You will be prompted to insert a file system floppy. Remove
the kernel-copy floppy and insert the upgr-10 floppy, then hit
the kernel-copy floppy and insert the upgr11 floppy, then hit
any key to continue booting.
While booting, you will probably see several warnings. You
@ -55,7 +54,8 @@ To upgrade your system, follow the following instructions:
If you don't have your file systems upgraded now, you should
probably do it manually after the install process is complete,
by using "fsck -c 2". Read the fsck(8) manual page for more
details.
details. Note that this step is only important when upgrading
from a pre-NetBSD 1.0 release.
The upgrade program will then check your root file system,
and, if you approved, will upgrade it to the new file system
@ -91,13 +91,13 @@ To upgrade your system, follow the following instructions:
After the software has been transferred to the machine (or
mounted, in the case of upgrading via NFS), change into the
directory containing the "base10" distribution set. Once you
directory containing the "base11" distribution set. Once you
are there, run the "Set_tmp_dir" command, and hit return at
the prompt to select the default answer for the temporary
directory's path name. (It should be the path name of the
directory that you're in.)
Run the command "Extract base10" to upgrade the base
Run the command "Extract base11" to upgrade the base
distribution.
Repeat the above two steps for all of the sets you wish to
@ -116,8 +116,8 @@ To upgrade your system, follow the following instructions:
up the installation, by remaking some system databases. When
it is complete, you should use "halt" to halt the system.
When the system is halted, remove the "upgr-10" floppy from
the floppy drive, and replace it with the NetBSD 1.0
When the system is halted, remove the "upgr11" floppy from
the floppy drive, and replace it with the NetBSD 1.1
kernel-copy floppy that you previously booted from. Reboot
with that floppy.
@ -146,20 +146,21 @@ To upgrade your system, follow the following instructions:
Once the system is halted, remove the kernel-copy floppy from
the floppy disk drive, and hit any key to reboot.
Your system has now been upgraded to NetBSD 1.0.
Your system has now been upgraded to NetBSD 1.1.
After a new kernel has been copied to your hard disk, your
machine is a complete NetBSD 1.0 system. However, that
After a new kernel has been copied to your hard disk, your
machine is a complete NetBSD 1.1 system. However, that
doesn't mean that you're finished with the upgrade process.
There are several things that you should do, or might have to
do, to insure that the system works properly.
First, if you did not upgrade your file systems to the new
file system format during the upgrade process, you may want to
do so now, with "fsck -c 2". If you are unsure about the
process, it's suggested that you read the fsck(8) manual page.
file system format during the upgrade process, and you are
upgrading from a pre-1.0 NetBSD, you may want to do so now,
with "fsck -c 2". If you are unsure about the process, it's
suggested that you read the fsck(8) manual page.
Second, you will probably want to get the etc10 distribution,
Second, you will probably want to get the etc11 distribution,
extract it, and compare its contents with those in your /etc/
directory. You will probably want to replace some of your
system configuration files, or incorporate some of the changes
@ -175,16 +176,18 @@ After a new kernel has been copied to your hard disk, your
some of the configuration files. The most notable change is
that the "options" given to many of the file systems in
/etc/fstab or by hand have changed, and some of the file
systems have changed names. To find out what the new options
are, it's suggested that you read the manual page for the
file systems' mount commands, for example mount_nfs(8) for
NFS. (Note that the information for mounts of type "ufs",
systems have changed names. *IMPORTANT*: ANY INSTANCES OF "ufs"
IN /etc/fstab MUST BE CHANGED TO "ffs". To find out what the
new options are, it's suggested that you read the manual page
for the file systems' mount commands, for example mount_nfs(8)
for NFS. (Note that the information for mounts of type "ffs",
i.e. Fast File Systems, are contained in the mount(8) man
page.)
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. You might also
been removed from the NetBSD distribution. If you are
upgrading from a pre-1.0 NetBSD, you might also
want to recompile any locally-built binaries, to take
advantage of the shared libraries. (Note that any new
binaries that you build will be dynamically linked, and

View File

@ -1,9 +1,13 @@
For the i386, NetBSD 1.0 brings greatly improved performance, stability,
and device support. To complement the added device drivers, NetBSD
1.0's i386 port has greatly improved device autoconfiguration,
allowing it to correctly find more devices on more machines. The
final, and perhaps most important point about NetBSD 1.0's i386
support is that it is fully backward compatible with old NetBSD
binaries, so you don't need to recompile all your local programs.
(Note, however, that because of the shared library support, you still
have a lot to gain by doing so.)
For the i386, NetBSD 1.1 brings greatly improved performance,
stability, and device support. Emulation for several UN*X and UN*X
like operating systems, including Linux and FreeBSD, has been added.
Many new PCI devices are supported, such as cards based on the AMD
PCnet-PCI Ethernet chip, the Digital DC21x4x family of Ethernet chips,
and the Adaptec AIC7870 SCSI host adapter chip. Some drivers such as
"ccd" which previously only worked on other ports of NetBSD now work
on the i386 port. Though still not known to be entirely stable, the
"ncr" driver for 53c8xx-series SCSI adapters has had substantial bugs
and performance issues resolved.
NetBSD 1.1 on i386 is also fully backward compatible with old NetBSD
i386 binaries, so you don't need to recompile all your local programs.

View File

@ -6,19 +6,16 @@ Installation is supported from several media types, including:
FTP
No matter which installation medium you choose, you'll need to have
two floppy disks available (either 1.2M or 1.44 will work, though
both should be the same type). On the first, you'll put the
kernel-copy image that's appropriate for your system. On the second,
you'll put the install or upgrade floppy image, depending on whether
you're installing NetBSD for the first time, or upgrading a previous
installation.
two floppy disks (either 1.2M or 1.44 will work, though both should be
the same type). On the first, you'll put the kernel-copy image that's
appropriate for your system. On the second, you'll put the install or
upgrade floppy image, depending on whether you're installing NetBSD
for the first time, or upgrading a previous installation.
If you are using an Adaptec AHA-154x or Buslogic BT-54x SCSI host
adapter, you need the kcaha-10.fs kernel-copy image. If you're using
a Buslogic BT-445, BT-74x, or BT-9xx SCSI host adapter, you'll need
the kcbt-10.fs image. If you're using a disk controller other than
those mentioned above, either kernel-copy disk image will work for
you.
If you are using an Adaptec SCSI host adapter, you need the kcadp11.fs
kernel-copy image. If you're using any other SCSI host adapter,
you'll need the kcoth11.fs image. If you're using a non-SCSI disk
controller, either kernel-copy disk image will work for you.
If you are using a UN*X-like system to write the floppy images to
disks, you should use the "dd" command to copy the file system images
@ -93,14 +90,14 @@ following:
(If you can't figure it out, ask your system administrator.)
In the above example, "<dist_directories>" are the
distribution sets' directories, for the distribution sets you
wish to place on the tape. For instance, to put the "base10"
and "etc10" distributions on tape (in order to do the absolute
wish to place on the tape. For instance, to put the "base11"
and "etc11" distributions on tape (in order to do the absolute
minimum installation to a new disk), you would do the
following:
cd .../NetBSD-1.0 # the top of the tree
cd .../NetBSD-1.1 # the top of the tree
cd i386/binary
tar cf <tape_device> base10 etc10
tar cf <tape_device> base11 etc11
(Note that you still need to fill in "<tape_device>" in the
example.)
@ -176,7 +173,7 @@ following:
Place the distribution sets you wish to upgrade somewhere in
your current file system tree. At a bare minimum, you must
upgrade the "base" binary distribution, and so must put the
"base10" set somewhere in your file system. If you wish,
"base11" set somewhere in your file system. If you wish,
you can do the other sets, as well, but you should NOT upgrade
the "etc" distribution; the "etc" distribution contains system
configuration files that you should review and update by hand.

View File

@ -10,6 +10,8 @@
This product includes software developed by Christian E. Hopps.
This product includes software developed by John Kohl.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Terrence R. Lambert.
@ -32,7 +34,5 @@
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by Christos Zoulas.

View File

@ -1,8 +1,8 @@
The mac68k-specific portion of the NetBSD 1.0 release is found in the
The mac68k-specific portion of the NetBSD 1.1 release is found in the
"mac68k" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../NetBSD-1.0/mac68k/
.../NetBSD-1.1/mac68k/
binary/ mac68k binary distribution sets;
see below.
@ -12,17 +12,17 @@ out as follows:
utils/ The mac68k installation utilities.
The NetBSD/mac68k binary distribution sets contain the binaries which
comprise the NetBSD 1.0 release for the mac68k. There are eight binary
comprise the NetBSD 1.1 release for the mac68k. There are eight binary
distribution sets, and the "security" distribution set. The binary
distribution sets can be found in subdirectories of the "mac68k/binary"
subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
subdirectory of the NetBSD 1.1 distribution tree, and are as follows:
netbsd10 The NetBSD/mac68k 1.0 kernel binary. You MUST
netbsd10 The NetBSD/mac68k 1.1 kernel binary. You MUST
install this file. It is the kernel that you need
to boot the system.
[ 307K gzipped, 610K uncompressed ]
base10 The NetBSD/mac68k 1.0 base binary distribution. You
base11 The NetBSD/mac68k 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
@ -30,7 +30,7 @@ subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
everything described below.
[ 6.2M gzipped, 18.4M uncompressed ]
comp10 The NetBSD/mac68k Compiler tools. All of the tools
comp11 The NetBSD/mac68k 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,
@ -41,7 +41,7 @@ subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
call and library manual pages.
[ 4.0M gzipped, 12.7M uncompressed ]
etc10 This distribution set contains the system
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
@ -50,28 +50,28 @@ subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
CAREFULLY upgrade your configuration files by hand.)
[ 50K gzipped, 280K uncompressed ]
games10 This set includes the games and their manual pages.
games11 This set includes the games and their manual pages.
[ 1.0M gzipped, 3.0M 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.
[ 0.7M gzipped, 2.8M 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.7M 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.
[ 0.8M gzipped, 2.9M uncompressed ]
The mac68k security distribution set is named "secr10" and can be found
in the "mac68k/security" subdirectory of the NetBSD 1.0 distribution
The mac68k security distribution set is named "secr11" and can be found
in the "mac68k/security" subdirectory of the NetBSD 1.1 distribution
tree. It contains the crypt libraries (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

View File

@ -1,37 +1,38 @@
NetBSD/mac68k 1.0 runs on several of the older Macintosh computers.
NetBSD/mac68k 1.1 runs on several of the older Macintosh computers.
4MB of RAM should be sufficient to boot and the system can probably
be squeezed onto a 40MB hard disk by leaving off a package or two.
To actually do much compiling or anything more interesting than
booting, at least 8MB of RAM and more disk space is recommended.
About 50MB will be necessary to install all of the NetBSD 1.0 binary
About 50MB will be necessary to install all of the NetBSD 1.1 binary
distribution (note that this does not count swap space!). Much more
disk space is required to install the source and objects as well (about
another 105MB).
Supported models:
Mac II
Mac IIx
Mac IIcx
Mac IIci
Mac SE/30
Mac II, Mac IIx, Mac IIcx, Mac IIci, Mac SE/30,
Mac IIsi, Mac IIvx, Mac IIvi, Performa 600
Supported devices on all of the above systems include:
Internal SCSI bus and most SCSI tapes, hard drives, and CD-ROMs
Internal sound--enough to beep, anyway
Internal sound--enough to beep on some machines, anyway
Most basic NuBUS video cards (there have been some
problems with some 24-bit color cards)
Both internal serial ports
ADB keyboards and mice
Ethernet cards based on the Natl. Semiconductor 8390
(Asante, Apple, and a few others) [problems
reported on the Performa 600, though].
Some systems will boot and are usable from an external terminal
(serial tty or SL/IP):
Mac IIsi
Mac IIvx
LC III
Performa 550
possibly others
What isn't supported, but often asked about:
Ethernet cards. There is a driver that is very close to working
for a number of cards. Contributions are very welcome.
68040-based Macs. Work is in progress on getting a Quadra 700
running. This requires a new scsi driver and a new
ethernet driver.
PowerPC-based Macs. Work will begin on this, sometime soon.
It will be separate from this port, though. The PowerPC
is a much different processor.

View File

@ -69,7 +69,7 @@ If you are installing onto a single root partition, proceed to the
Installation of base files:
Select the "Install" menu item from the "File" menu and install
base10, netbsd, and any other packages you wish to install at
base11, netbsd, and any other packages you wish to install at
this time (see the contents section for information about what's
in each package). The installer will print out the filename of
each file as it is installed, and will take quite some time to
@ -105,13 +105,13 @@ If the system does not come up:
you saw.
If the system does come up, congratulations, you have successfully
installed NetBSD 1.0. When you reboot into NetBSD, you should log
installed NetBSD 1.1. When you reboot into NetBSD, you should log
in as "root" at the login prompt. There is no initial password, but
if you're using the machine in a networked environment, you should
create yourself an account and protect it and the "root" account with
good passwords.
Some of the files in the NetBSD 1.0 distribution might need to be
Some of the files in the NetBSD 1.1 distribution might need to be
tailored for your site. In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc will
probably need to be modified, as well. If you are unfamiliar with

View File

@ -1,4 +1,4 @@
There is no upgrade to release 1.0 for the NetBSD/mac68k architecture.
This is impractical as there is no good, standard point to provide an
upgrade path from. It is hoped that there will be a good upgrade
procedure for future releases.
There is no upgrade to release 1.1 for the NetBSD/mac68k architecture.
It is hoped that there will be a good upgrade procedure for future
releases. Please feel free to volunteer to help replace these
installation tools.

View File

@ -1,6 +1,3 @@
NetBSD 1.0 is the first "real" release of NetBSD for the mac68k.
Previous releases have been alpha or beta quality. There is still a
lot of work to be done, but this should be a usable system for a number
of people. Quite a few features are available: shared libraries, new
file systems, binary compatibility with the other m68k ports for most
binaries, SunOS compatibility, and numerous others.
NetBSD 1.1 is the second "real" release of NetBSD for the mac68k.
There is still a lot of work to be done and help is welcomed, but
this should be a usable system for a number of people.

View File

@ -1,7 +1,7 @@
Installation is really only supported from the local Macintosh
hard drive or from an AppleShare volume. This means that you'll
need at least enough room for the largest file that you will have
to install. This is the 6.2M base10 file. There has been talk
to install. This is the 6.2M base11 file. There has been talk
of allowing an install from split files. If you have the time,
desire, and knowledge, please feel free to add that functionality.
@ -9,10 +9,10 @@ If the install is being done from an AppleShare-mounted volume,
the install utility must be in the same folder as the data files.
There will be two images of each file. One in "raw" Unix format
and one in a binhex format. Therefore, base10 and base10.hqx both
contain the same information, but base10.hqx has been encoded in
and one in a binhex format. Therefore, base11 and base11.hqx both
contain the same information, but base11.hqx has been encoded in
binhex format. Download the files; if necessary, decode them so
you have all of the files as base10, etc10, etc. This can be
you have all of the files as base11, etc11, etc. This can be
accomplished from the .hqx files by using _Stuffit Expander_ or
any one of a number of freeware and shareware Macintosh tools.
@ -22,7 +22,7 @@ You will also need to collect the MacOS tools:
MacBSD Booter.
These three are compacted and in binhex form as mkfs.cpt.hqx,
installer.1.0.cpt.hqx, and booter.1.4.cpt.hqx, respectively.
installer.1.0.cpt.hqx, and booter.1.9.cpt.hqx, respectively.
Extract them as you would any other Macintosh applications. The
sources should be in the same place with "src" somewhere in the

View File

@ -2,57 +2,57 @@ Host name Services Provided
---- ---- -------- --------
ftp.iastate.edu Anonymous FTP, AFS
Anon-FTP path: pub/netbsd/NetBSD-1.0
AFS path: /afs/iastate.edu/public/ftp/pub/netbsd/NetBSD-1.0
Anon-FTP path: pub/netbsd
AFS path: /afs/iastate.edu/public/ftp/pub/netbsd
ftp.eecs.umich.edu Anonymous FTP
Anon-FTP path: BSD/NetBSD/NetBSD-1.0
Anon-FTP path: BSD/NetBSD
gatekeeper.dec.com Anonymous FTP
Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0
Anon-FTP path: pub/BSD/NetBSD
wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP
Anon-FTP path: pub/NetBSD/NetBSD-1.0
Anon-FTP path: pub/NetBSD
SUP: get the file pub/misc/sup/supfile.example via
anonymous FTP and read it as an example.
ftp.demon.co.uk Anonymous FTP, possibly SUP
Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0
Anon-FTP path: pub/BSD/NetBSD
SUP: contact peter@demon.net for SUP server status/information
ftp.uni-regensburg.de Anonymous FTP
Anon-FTP path: pub/NetBSD/NetBSD-1.0
Anon-FTP path: pub/NetBSD
ftp.unit.no Anonymous FTP
Anon-FTP path: pub/NetBSD/NetBSD-1.0
Anon-FTP path: pub/NetBSD
ftp.stacken.kth.se Anonymous FTP
Anon-FTP path: pub/OS/NetBSD/NetBSD-1.0
Anon-FTP path: pub/OS/NetBSD
flick.lerc.nasa.gov Anonymous FTP
Anon-FTP path: pub/NetBSD/NetBSD-1.0
Anon-FTP path: pub/NetBSD
coombs.anu.edu.au Anonymous FTP
Anon-FTP path: pub/NetBSD/NetBSD-1.0
Anon-FTP path: pub/NetBSD
ftp.funet.fi Anonymous FTP
Anon-FTP path: pub/unix/NetBSD/NetBSD-1.0
Anon-FTP path: pub/unix/NetBSD
ftp.netbsd.org Anonymous FTP, SUP
Anon-FTP path: pub/NetBSD/NetBSD-1.0
Anon-FTP path: pub/NetBSD
SUP: get the file pub/sup/README.sup via anonymous FTP from
ftp.netbsd.org, and read it for instructions.
If you wish to become a distribution site for NetBSD, contact Chris
Demetriou <cgd@NetBSD.ORG>.
If you wish to become a distribution site for NetBSD, contact
mirrors@netbsd.org.

View File

@ -1,19 +1,14 @@
The pc532-specific portion of the NetBSD 1.0 release is found in the
The pc532-specific portion of the NetBSD 1.1 release is found in the
"pc532" subdirectory of the distribution. That subdirectory contains
the files as follows:
.../NetBSD-1.0/pc532/
.../NetBSD-1.1/pc532/
INSTALL Installation notes; this file.
CKSUM output of "cksum *.gz"
ram.root.gz Ram root disk
util.tar.gz things to help the install
netbsd.rd.9600.gz "ram disk" root kernel, 9600 baud
netbsd.rd.19200.gz "ram disk" root kernel, 19200 baud
netbsd.sd0.9600.gz sd0a root, 9600 baud console
netbsd.sd0.19200.gz sd0a root, 19200 baud console
netbsd.sd1.9600.gz sd1a root, 9600 baud console
netbsd.sd1.19200.gz sd1a root, 19200 baud console
inst-11.fs.gz Installation file system.
download.c.gz Source for a pc532 ROM compat download pgm
netbsd.default.gz Upgrade kernel
base.tar.gz base distribution
comp.tar.gz compiler tools & libraries
etc.tar.gz files for /etc
@ -26,12 +21,12 @@ the files as follows:
The binary distribution consists of the following files:
base.tar.gz
The NetBSD/pc532 1.0 base binary distribution. You
The NetBSD/pc532 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
excludes everything described below.
[ 15.1M gzipped ]
[ 6.8M gzipped ]
comp.tar.gz
The NetBSD/pc532 Compiler tools. All of the tools
@ -41,7 +36,7 @@ The binary distribution consists of the following files:
and the various system libraries. This set also includes
the manual pages for all the utilities it contains, as well
as the system call and library manual pages.
[ 4.2M gzipped ]
[ 4.7M gzipped ]
etc.tar.gz
This distribution set contains the system
@ -51,31 +46,31 @@ The binary distribution consists of the following files:
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.)
[ 50K gzipped ]
[ 63K gzipped ]
games.tar.gz
This set includes the games and their manual pages.
[ 2.4M gzipped ]
[ 2.8M gzipped ]
man.tar.gz
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.
[ 0.7M gzipped ]
[ 0.8M gzipped ]
misc.tar.gz
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.7M gzipped, 5.6M uncompressed ]
[ 1.9M gzipped ]
text.tar.gz
This set includes NetBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 1.1M gzipped ]
[ 0.8M gzipped ]
The pc532 distribution set does not include a security distribution.
If you are in the US and want the security distribution you must
@ -88,26 +83,20 @@ recompile the following programs:
The initial installation process on a pc532 without NetBSD/pc532
is supported by the following files:
Initial kernels to loaded into memory and run:
Initial file system used via SCSI floppy or downloaded into
memory:
netbsd.rd.9600.gz "ram disk" root kernel, 9600 baud
netbsd.rd.19200.gz "ram disk" root kernel, 19200 baud
inst-11.fs -- file system containing boot loader
and install kernel with 2MB
ram root file system.
The initial root file system for the above kernels
ram.root.gz Ram root disk
Utility programs for helping with the install after a
mini-root has been built on a hard disk
util.tar.gz things to help the install
Bootable kernels for placement in the file system to boot
from hard disk.
netbsd.sd0.9600.gz sd0a root, 9600 baud console
netbsd.sd0.19200.gz sd0a root, 19200 baud console
netbsd.sd1.9600.gz sd1a root, 9600 baud console
netbsd.sd1.19200.gz sd1a root, 19200 baud console
download.c -- source for the program to download
inst-11.fs into memory via the
pc532 ROM monitor.
The upgrade process is supported by having a copy of a 1.1 kernel
available. This file is:
netbsd.default.gz -- a kernel produced from the DEFAULT
configuration file in pc532/conf.

View File

@ -1,4 +1,4 @@
NetBSD/pc532 1.0 runs on a PC532 computer. It supports a subset of the
NetBSD/pc532 1.1 runs on a PC532 computer. It supports a subset of the
"standard" hardware to date. This is defined as:
4 - 32 Megs of memory
@ -7,6 +7,7 @@ NetBSD/pc532 1.0 runs on a PC532 computer. It supports a subset of the
Most SCSI disks work (fixed and floppy)
A few SCSI tapes work
Some SCSI CD-ROM drives work
The Matthias Pfaller Parallel Port.
NetBSD/pc532 currently expects the ROM monitor to be the "autoboot
monitor" of Oct/Nov 1991. It includes support to set up auto booting

View File

@ -46,8 +46,10 @@ The Install Procedure:
these settings. The monitor's baud rate can be changed with
"baud d'9600".
b) Get inst-11.fs.
If you have a 1.44 meg SCSI floppy drive, you can put this
b) Get inst-11.fs and boot the kernel.
From Floppy: (and using the autoboot monitor)
If you have a 1.44 meg SCSI floppy drive, you can put inst-11.fs
onto a 3.5" floppy disk. Insert the disk into your floppy
drive and use the monitor's boot command to boot the default
image from the floppy. The image booted will ask you for a
@ -55,12 +57,23 @@ The Install Procedure:
sdXa:/netbsd
Replace X with your drive number. For KLONDIKE X would be "2".
If you don't have a floppy drive, you will have to
Tape:
You will need to load a copy of inst-11.fs into RAM.
- load the inst-11.fs at 0x288000
- run at 0x3EB820
- run at 0x3E8820
The boot program will ask you now for a kernel to load. Answer
rd0a:/netbsd
Serial line:
Provided with the distribution is source for program called
download. (download.c) This program when used as
"download file" will read the contents of the file and
output to standard output a byte sequence used by the pc532
ROM monitor to download a binary file into RAM. Using this
program on a computer connected to the pc532, one can
load a copy of inst-11.fs into RAM at 0x288000. The boot
sequence is now the same as with tape.
c) Choose a disk geometry. For me, the reported geometry left
some sectors "unallocated". That is, the autoconfig message
said the disk had 2428 cylinders, 9 heads, and 93 sectors/track.
@ -87,7 +100,7 @@ The Install Procedure:
steelhead[5]$ echo "2 * 997"|bc
1994
Now I the number of tracks:
Now I need the number of tracks (or cylinders):
steelhead[5]$ echo "2 * 5 * 103"|bc
1030
@ -103,9 +116,9 @@ The Install Procedure:
partitions, it will ask for a mount point. The mount point will
be "relative to /" and should not include the leading "/". Also,
IF you do not want the partition to have newfs run on it (that is
it might be the last one and have a copy of ram.root and your
kernels) enter "NO" to the mount point and it will not run newfs
on the partition. It will enter the partition into the disklabel.
it might be the last one and have a copy of inst-11.fs) enter "NO"
to the mount point and it will not run newfs on the partition.
It will enter the partition into the disklabel.
e) look around, if you want ... and then halt NetBSD.
@ -125,6 +138,8 @@ The Install Procedure:
use nfs...
Plip is only an option if you have installed a
centronics port in your pc532.
You do have access to vi to edit your network
files. (/etc/resolv.conf, ...)
b) floppy disk
@ -132,7 +147,12 @@ The Install Procedure:
d) cdrom (If you have a CD with NetBSD/532 ...)
e) using kermit. (See the notes at the end of this file.)
e) Use the ROM compatable "download" program. The program
download is included in the initial installation and
can be used as the receive end of the download by
using it as "download -r file_to_write". If the CRC is
correct, the file is retained. If the CRC is not
correct, the file is deleted.
f) some other method? (Let me know about it.)
@ -149,8 +169,8 @@ The Install Procedure:
- tar -xpzf /gz.files/base.tar.gz --unlink
Add v to the flags if you want a verbose extract.
The --unlink is to make sure that the "ram.root" versions
of sh, init, ... are replaced by their full featured versons
The --unlink is to make sure that the install versions
of sh, init, ... are replaced by their proper versons
in base.tar.gz. I think it is wise to include the --unlink
for other things.
@ -179,42 +199,14 @@ The Install Procedure:
gdb -w /netbsd
set scndefaultrate = YOUR_BAUD_RATE
quit
where YOUR_BAUD_RATE is the actual value, 19200, 38400 or
something slower than 9600.
If you set scndefaultrate to something bogus, you'll probably
not be able to reboot... So be carefull!
l) Reboot the machine and it should come up in multi-user mode *IF*
you got it configured correctly.
m) Enjoy! And help fix bugs and improve NetBSD/pc532!
For those who choose to use kermit to help in getting NetBSD/pc532
installed:
The following is the Kermit copyright:
Copyright (C) 1985, 1994, Trustees of Columbia University in the
City of New York. The C-Kermit software may not be, in whole or
in part, licensed or sold for profit as a software product
itself, nor may it be included in or distributed with commercial
products or otherwise distributed by commercial concerns to their
clients or customers without written permission of the Office of
Kermit Development and Distribution, Columbia University. This
copyright notice must not be removed, altered, or obscured.
Due to this copyright, we can not include kermit with the standard
NetBSD/pc532 distribution.
The Office of Kermit Development and Distribution of Columbia
University in the City of New York has given permission for
us to distribute a NetBSD/pc532 binary. It is available primarily
for bootstrapping purposes and therefore is not a complete package,
lacking source code, various supporting text files, and the user
manual. Users who wish to use C-Kermit after the bootstrapping
process should obtain the full package, including the manual
"Using C-Kermit", from Columbia University.
The NetBSD/pc532 binary is available via ftp from
iceberg.cs.wwu.edu in the directory pub/NetBSD/pc532 as the file
kermitbin.tar.gz.

View File

@ -1,10 +1,10 @@
The upgrade to NetBSD 1.0 is a binary upgrade; it would be prohibitive
to make users upgrade by compiling and installing the 1.0 sources, and
The upgrade to NetBSD 1.1 is a binary upgrade; it would be prohibitive
to make users upgrade by compiling and installing the 1.1 sources, and
it would be very difficult to even compile a set of instructions that
allowed them to do so.
To do the upgrade, you must have at least base.tar.gz on disk and
a copy of the proper netbsd.sdx.yyyy. It will require quite a bit
a copy of the proper netbsd.default. It will require quite a bit
of disk space to do the upgrade.
Since upgrading involves replacing the kernel, and most of the system
@ -31,25 +31,15 @@ To upgrade your system, follow the following instructions:
work at upgrading /etc. There may be changes to file formats
depending on what version of NetBSD/pc532 you are running.
BE CAREFUL IF YOU ARE RUNNING WITH SECURITY. The distribution
binaries don't support it. It would be reasonable to save a
copy of master.passwd and remove all passwords until after
you upgrade to the new security level.
BE CAREFUL IF YOU ARE NOT RUNNING WITH SECURITY. The
1.1 distribution does contain support for password encription.
It would be reasonable to save a copy of master.passwd and
remove all passwords until after you upgrade.
Place the proper netbsd.sdX.YYYY in / as the file netbsd.
Place netbsd.default in / as the file netbsd.
Reboot.
Reboot. (Remember, detbsd.default is a 9600 console line
kernel. Read the last part of the new installation part of
these notes to find out how to change your default speed.)
After reboot, you should make sure you check your new file systems.
Also, you may wish to upgrade your file systems to the new file
system format. After the install process is complete,
use "fsck -c 2" to upgrade the file systems. Read the fsck(8)
manual page for more details.
If you upgrade your file systems, you will want to make sure
you have the most recent ufs boot program if you use the
NetBSD boot program to read the kernel off a ufs file system.
Use bim(8) to remove your old boot program and install the
newest one if you are using the autoboot monitor.

View File

@ -9,6 +9,3 @@ For the pc532 port, there are a few known problems. They include:
d) The disk driver is polled, not interrupt driven.
e) kernel support for debugging is not working correctly.
f) shared libraries are not used yet.

View File

@ -3,7 +3,9 @@ via the console terminal and using the downloading parts of the
ROM monitor. As such, usually another computer has the distribution
on disk and is connected via a serial line to your pc532's console
port. A terminal connected to the attached host computer is used
to access the pc532 console via a terminal program.
to access the pc532 console via a terminal program. The source for
a program called download is part of this distribution. Download
sends data to the ROM monitor over the serial line.
You may need to find and read the documentation about the ROM monitor
download command and other low level comands.
@ -16,4 +18,4 @@ If you have some operating system already running on your pc532,
you can use that OS to get NetBSD/pc532 on a hard disk much easier than
with the ROM monitor. (NetBSD/pc532 was developed from Minix/pc532
until it was self hosting. You can run NetBSD and Minix or other OS
off the same disk.)
off the same disk.)

View File

@ -1,5 +1,5 @@
# $Id
# $NetBSD: Makefile,v 1.2 1995/11/28 23:58:45 jtc Exp $
SUBDIR= inst upgr
SUBDIR= inst # upgr
.include <bsd.subdir.mk>

View File

@ -1,4 +1,4 @@
# $Id: Makefile.inc,v 1.2 1995/09/26 21:24:41 phil Exp $
# $Id: Makefile.inc,v 1.3 1995/11/28 23:58:47 jtc Exp $
# Revision is 1.0A
REV= 10A
# Revision is 1.1
REV= 11

View File

@ -1,4 +1,4 @@
# $Id: Makefile.inc,v 1.4 1995/09/29 04:00:18 phil Exp $
# $NetBSD: Makefile.inc,v 1.5 1995/11/28 23:58:56 jtc Exp $
# TOP is assumed to be defined by Makefile including this one.
@ -59,6 +59,7 @@ unconfig:
-/bin/rm -f ${IMAGE}
${CBIN}.mk ${CBIN}.cache ${CBIN}.c: ${CRUNCHCONF}
(cd ${COMMONDIR}; ${MAKE} download.o)
crunchgen -D ${TOP}/../../.. -L ${DESTDIR}/usr/lib ${CRUNCHCONF}
${CBIN}: ${CBIN}.mk ${CBIN}.cache ${CBIN}.c

View File

@ -27,7 +27,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: dot.commonutils,v 1.2 1995/09/26 21:25:05 phil Exp $
# $Id: dot.commonutils,v 1.3 1995/11/28 23:58:57 jtc Exp $
# Installation utilites (functions), to get NetBSD installed on
# the hard disk. These are meant to be invoked from the shell prompt,
@ -111,7 +111,7 @@ Load_tape()
echo -n "continue..."
read foo
echo "Extracting files from the tape..."
$TAR xvpf --unlink /dev/$which
$TAR --unlink -xvpf /dev/$which
echo "Done."
}

View File

@ -1,22 +1,24 @@
#
# kcbin.conf - unified binary for the kc floppy
# $Id: instbin.conf,v 1.5 1995/10/06 21:00:17 phil Exp $
# $Id: instbin.conf,v 1.6 1995/11/28 23:58:59 jtc Exp $
#
srcdirs bin sbin usr.bin usr.sbin gnu/usr.bin games
progs basename bc bim cat chat chmod chown chroot cp
progs date dd df dirname disklabel dmesg domainname dump
progs expr factor find fsck ftp gawk gzip hostname hexdump ifconfig init
progs date dd df dirname disklabel dmesg domainname download dump
progs expr factor find fsck ftp
progs gawk gzip hostname hexdump ifconfig init
progs kill kvm_mkdb ln ls mkdir mknod more
progs mount mount_cd9660 mount_ffs mount_msdos mount_nfs mt mv netstat newfs
progs pax ping pppd pppstats ps pwd rcp reboot restore rm rmdir route
progs sed sh shutdown slattach strings stty swapon sync test tip traceroute
progs umount update vi
progs ping pppd pppstats ps pwd rcp reboot restore rm rmdir route
progs sed sh slattach strings stty swapon sync sysctl
progs tar test tip traceroute umount update vi
special chat srcdir /usr/src/usr.sbin/pppd/chat
special pppstats srcdir /usr/src/usr.sbin/pppd/pppstats
special vi srcdir /usr/src/usr.bin/vi/common
special download srcdir /usr/src/distrib/pc532/floppies/inst-common
ln chown chgrp
ln dump rdump
@ -28,8 +30,6 @@ ln mount_cd9660 cd9660
ln mount_ffs ffs
ln mount_msdos msdos
ln mount_nfs nfs
ln pax tar
ln pax cpio
ln restore rrestore
ln vi ex
ln vi view

View File

@ -1,4 +1,4 @@
# $Id: list,v 1.5 1995/10/06 21:00:20 phil Exp $
# $Id: list,v 1.6 1995/11/28 23:59:00 jtc Exp $
# copy the MAKEDEV script and make some devices
COPY ${DESTDIR}/dev/MAKEDEV dev/MAKEDEV
@ -36,7 +36,6 @@ LINK instbin bin/ls
LINK instbin bin/mkdir
LINK instbin bin/mt
LINK instbin bin/mv
LINK instbin bin/pax
LINK instbin bin/ps
LINK instbin bin/pwd
LINK instbin bin/rcp
@ -68,14 +67,12 @@ LINK instbin sbin/reboot
LINK instbin sbin/restore
LINK instbin sbin/route
LINK instbin sbin/rrestore
LINK instbin sbin/shutdown
LINK instbin sbin/slattach
LINK instbin sbin/swapon
LINK instbin sbin/umount
SYMLINK /instbin usr/bin/awk
SYMLINK /instbin usr/bin/basename
SYMLINK /instbin usr/bin/chgrp
SYMLINK /instbin usr/bin/cpio
SYMLINK /instbin usr/bin/dirname
SYMLINK /instbin usr/bin/hexdump
SYMLINK /instbin usr/bin/ex
@ -99,8 +96,10 @@ SYMLINK /instbin usr/sbin/chroot
SYMLINK /instbin usr/sbin/kvm_mkdb
SYMLINK /instbin usr/sbin/pppd
SYMLINK /instbin usr/sbin/pppstats
SYMLINK /instbin usr/sbin/sysctl
SYMLINK /instbin usr/sbin/traceroute
SYMLINK /instbin usr/sbin/update
SYMLINK /instbin usr/local/bin/download
#SPECIAL /bin/rm instbin

View File

@ -1,4 +1,4 @@
# $Id: mtree.conf,v 1.3 1995/10/03 22:31:08 phil Exp $
# $Id: mtree.conf,v 1.4 1995/11/28 23:59:02 jtc Exp $
/set type=dir uname=root gname=wheel mode=0755
# .
@ -107,5 +107,17 @@ misc
# ./usr/share
..
# ./usr/local
local
# ./usr/local/bin
bin
# ./usr/local/bin
..
# ./usr/local
..
# ./usr
..

View File

@ -27,7 +27,7 @@
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
# THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# $Id: install.sh,v 1.3 1995/10/03 22:31:01 phil Exp $
# $Id: install.sh,v 1.4 1995/11/28 23:58:51 jtc Exp $
# NetBSD installation script.
# In a perfect world, this would be a nice C program, with a reasonable
@ -440,19 +440,19 @@ $DONTDOIT gzip -d /mnt/netbsd.gz
echo ""
echo -n "Creating an fstab..."
echo /dev/${drivename}a / ffs rw 1 1 | sed -e s,//,/, > $FSTAB
if [ "$dname" != "" ]; then
if [ "$dname" != "" -a "$dname" != "NO" ]; then
echo /dev/${drivename}d /$dname ffs rw 1 2 | sed -e s,//,/, >> $FSTAB
fi
if [ "$ename" != "" ]; then
if [ "$ename" != "" -a "$ename" != "NO" ]; then
echo /dev/${drivename}e /$ename ffs rw 1 2 | sed -e s,//,/, >> $FSTAB
fi
if [ "$fname" != "" ]; then
if [ "$fname" != "" -a "$fname" != "NO" ]; then
echo /dev/${drivename}f /$fname ffs rw 1 3 | sed -e s,//,/, >> $FSTAB
fi
if [ "$gname" != "" ]; then
if [ "$gname" != "" -a "$gname" != "NO" ]; then
echo /dev/${drivename}g /$gname ffs rw 1 4 | sed -e s,//,/, >> $FSTAB
fi
if [ "$hname" != "" ]; then
if [ "$hname" != "" -a "$hname" != "NO" ]; then
echo /dev/${drivename}h /$hname ffs rw 1 5 | sed -e s,//,/, >> $FSTAB
fi
sync

View File

@ -5,7 +5,7 @@
./usr/lib/libedit.so.0.0
./usr/lib/libg++.so.2.0
./usr/lib/libgnumalloc.so.0.0
./usr/lib/libi386.so.0.0
./usr/lib/libi386.so.0.1
./usr/lib/libkvm.so.4.0
./usr/lib/libm.so.0.1
./usr/lib/libpcap.so.0.0

View File

@ -17,7 +17,6 @@
./usr/mdec/bootxx
./usr/mdec/boot
./usr/mdec/binstall
./usr/bin/fdeject
./usr/sbin/eeprom
./usr/sbin/installboot
./usr/sbin/screenblank

View File

@ -150,6 +150,7 @@
./usr/bin/dirname
./usr/bin/du
./usr/bin/egrep
./usr/bin/eject
./usr/bin/env
./usr/bin/error
./usr/bin/ex
@ -639,6 +640,7 @@
./usr/share/man/cat4/mac68k
./usr/share/man/cat4/pc532
./usr/share/man/cat4/sparc
./usr/share/man/cat4/sun3
./usr/share/man/cat4/tahoe
./usr/share/man/cat4/vax
./usr/share/man/cat5
@ -652,6 +654,7 @@
./usr/share/man/cat8/mac68k
./usr/share/man/cat8/pc532
./usr/share/man/cat8/sparc
./usr/share/man/cat8/sun3
./usr/share/man/cat8/tahoe
./usr/share/man/cat8/vax
./usr/share/man/makewhatis.sed

View File

@ -11,6 +11,8 @@
./usr/include/machine/exec.h
./usr/include/machine/float.h
./usr/include/machine/frame.h
./usr/include/machine/freebsd_machdep.h
./usr/include/machine/gdt.h
./usr/include/machine/ieeefp.h
./usr/include/machine/limits.h
./usr/include/machine/linux_machdep.h
@ -58,5 +60,8 @@
./usr/lib/libtermcap_pic.a
./usr/lib/libutil_pic.a
./usr/lib/scrt0.o
./usr/share/man/cat2/i386_get_ioperm.0
./usr/share/man/cat2/i386_get_ldt.0
./usr/share/man/cat2/i386_iopl.0
./usr/share/man/cat2/i386_set_ioperm.0
./usr/share/man/cat2/i386_set_ldt.0

View File

@ -39,11 +39,13 @@
./usr/include/dev/audiovar.h
./usr/include/dev/ccdvar.h
./usr/include/dev/cons.h
./usr/include/dev/ramdisk.h
./usr/include/dev/eisa
./usr/include/dev/eisa/eisareg.h
./usr/include/dev/eisa/eisavar.h
./usr/include/dev/ic
./usr/include/dev/ic/ad1848reg.h
./usr/include/dev/ic/aic7xxxvar.h
./usr/include/dev/ic/am7930reg.h
./usr/include/dev/ic/am7990reg.h
./usr/include/dev/ic/am7990var.h

View File

@ -57,6 +57,7 @@
./usr/share/man/cat1/echo.0
./usr/share/man/cat1/ed.0
./usr/share/man/cat1/egrep.0
./usr/share/man/cat1/eject.0
./usr/share/man/cat1/env.0
./usr/share/man/cat1/error.0
./usr/share/man/cat1/ex.0
@ -470,6 +471,7 @@
./usr/share/man/cat8/rbootd.0
./usr/share/man/cat8/rc.0
./usr/share/man/cat8/rdate.0
./usr/share/man/cat8/rdconfig.0
./usr/share/man/cat8/rdump.0
./usr/share/man/cat8/reboot.0
./usr/share/man/cat8/renice.0