Return to BSD News archive
Xref: sserve comp.os.386bsd.announce:32 comp.unix.bsd:11850 comp.os.386bsd.misc:180
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate!usenet
From: cgd@agate.berkeley.edu (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.announce,comp.unix.bsd,comp.os.386bsd.misc
Subject: So you say you want an interim release of 386bsd?
Followup-To: comp.os.386bsd.misc
Date: 19 Apr 1993 20:06:49 -0700
Organization: Kernel Hackers 'r' Us
Lines: 975
Approved: 386bsd-announce-request@agate.berkeley.edu
Distribution: world
Message-ID: <1qvpc9$1e8@agate.berkeley.edu>
NNTP-Posting-Host: agate.berkeley.edu
Summary: you want it, you got it.
Keywords: 386BSD, NetBSD, free, BSD, sleep
Some of you have undoubtedly been wondering what i've been up
to lately... I've told some, i've randomly babbled to more,
and now everybody gets to know.
Reading the first three sections is probably useful to most.
Reading the rest in up in the air...
if you'd like to know more of the reasons behind this, ask;
they don't belong in this document, for reasons stated.
have a ball with it!
chris
==================
INSTALLATION NOTES for NetBSD 0.8 <1.2>
Be sure to read _ALL_ of this document before you try to
install NetBSD. NetBSD probably looks a bit similar to
things that you've seen before (e.g. 386BSD), but the
installation procedures have changed a LOT.
"We can walk our road together if our goals are all the same;
We can run alone and free if we pursue a different aim."
- Rush
What is NetBSD:
---- -- ------
NetBSD is a new system, based heavily on 386BSD 0.1, with
many improvements over 386BSD 0.1, and with different goals
than those which are espoused by the principal developers
of 386BSD. 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.
The source for NetBSD is derived from 386BSD 0.1, patched
with the 0.2.2 patch kit. In addition, many programs in
UCB's second BSD Networking Software Release which were
missing from 386BSD have been integrated into NetBSD, some
of the changes from the upcoming 0.2.3 patch kit have been
included, and many local additions and bug fixes have
been performed. NetBSD is currently 100% binary compatible
with 386BSD, so programs like XFree86 which are already
available for 386BSD will install and run on NetBSD as easily
as on 386BSD.
NetBSD would not be possible were it not for the work
of the UCB Computer Systems Research Group, which
released Net/2, or the work of William and Lynne Jolitz,
who brought 386BSD into the world, or the work of the
thousands of contributors to Net/2 and 386BSD. NetBSD
is the product of the efforts of a large group of people,
and we believe that that group should have a say in deciding
NetBSD's future.
Differences Between 386BSD and NetBSD:
----------- ------- ------ --- ------
NetBSD is currently 386BSD 0.1, with lots of patches applied.
As such, it is completely binary-compatible with 386BSD 0.1,
and is much more stable. It, like 386BSD, is intended to be
used for research.
Some could look at NetBSD as simply an interim release of
386BSD. We look it as more, and therefore have named it
differently. The new name and version number reflect two
of our goals for NetBSD: an escape from the political wars
surrounding what we consider a wonderful operating system,
and the rapid development of a stable release which we
would consider of "production quality."
The Future of NetBSD:
--- ------ -- ------
We have several plans for the future of NetBSD.
The first is to organize regular releases of patches to
the source tree. These will probably be done using "cron"
to automate the process and ensure that it actually
happens. We believe these are necessary in order to
minimize duplicated work. We also hope to have
regular releases of the full binary and source trees,
but as these are much more difficult to coordinate,
this can only happen if someone volunteers for
the job.
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
changes from 386BSD 0.2 when it appears, as well
as from 4.4BSD, and perhaps even going back to Net/2
in order to re-integrate support for other architectures,
such as the Hewlett-Packard 9000/300 family of workstations.
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 and because of them that NetBSD exists.
Sources of NetBSD:
------- -- ------
Currently, the NetBSD system is available from the host
agate.berkeley.edu [128.32.155.1] in the directory
pub/NetBSD/NetBSD-0.8, by anonymous FTP.
The distribution as provided on agate.berkeley.edu does not
contain crypt(3), for password and data encryption, because
it is an implementation of DES and not exportable from the
United States. If you wish to obtain the files containing
the crypt(3) functionality and are in the United States,
you may obtain it from sun-lamp.cs.berkeley.edu [128.32.240.164]
in the directory "NetBSD/NetBSD-0.8".
Hopefully, other sources of the distribution will become
available in the near future, as agate.berkeley.edu can
accept a very limited number of anonymous FTP connections.
(If you wish to become a distribution site for NetBSD,
contact Chris Demetriou, cgd@sun-lamp.cs.berkeley.edu.)
NetBSD 0.8 Release Contents:
------ --- ------- --------
The NetBSD 0.8 Release consists of the following elements:
Bootable Kernel-copy floppies
These disks contain file systems, are bootable, and
have enough utilities on board to copy a new
kernel to your hard disk, once you have it partitioned
for NetBSD. They make upgrading to a new kernel
easy, because all you have to do is get a new
kernel-copy floppy with a new kernel, boot from it,
and confirm that you want to have the kernel copied
to your disk.
There are currently two different kernel copy floppy
images, "kc-aha.fs", and "kc-ahbbt.fs". The first
has the driver for the Adaptec 154x host adapter,
the second has the drivers for the Adaptec 1742 host
adapter and the Bustec 742 host adapter.
Installation floppies
These are currently two disks which contain the
software necessary to prepare your hard drive
for NetBSD and install the NetBSD distribution.
They are not bootable, and must be used in
conjunction with the kernel-copy floppies.
NetBSD distribution sets
These are collections of software, and include
both the binaries necessary to run the system
and the sources to the entire system.
NetBSD 0.8 is split up into ten different
distribution sets, six of which contain binaries,
three of which contain the NetBSD source, and
the last of which contains the tools which
could not be included in the base distribution
because they contain crypt(3).
The binary distribution sets can be found in
under "binary" subdirectory of the distribution,
and are as follows:
base08 The NetBSD 0.8 base binary distribution.
You need to install this distribution set.
This contains no compiler tools, no text
formatting tools, no games, and, in short,
nothing listed in the remaining sets;
its purpose is to be as small as possible,
and, in fact, if you've got a 30Meg
hard disk, you should be able to install
the base distribution with no problems.
It does include the man pages for the
included utilities, however, as we consider
them essential to the use of the system.
(In fact, the files in the base distribution
use approximately 16Megs, but you need
space for swap, and there's some overhead
in installation.)
[ 5.7M gzipped, 16M uncompressed ]
comp08 The compiler tools set. This includes
gcc 1.39, g++, and the full set of include
files, libraries, and profiling tools.
[ 2.1M gzipped, 7.9M uncompressed ]
text08 The text formatting tools set.
[ 0.4M gzipped, 1.3M uncompressed ]
doc08 The BSD PS1, SMM, and USD manuals,
in source form. (In other words, the
contents of /usr/share/doc.) You need
the "text08" set for this to be useful.
[ 0.6M gzipped, 2.2M uncompressed ]
game08 The games and their man pages.
[ 1.4M gzipped, 3.6M uncompressed ]
misc08 Miscellaneous files: the dictionary
and non-i386 machine-specific man-pages.
[ 1.1M gzipped, 3.9M uncompressed ]
The source distribution sets can be found in
under "source" subdirectory of the distribution,
and are as follows:
ksrc08 The sources to the NetBSD 0.8 kernel.
[ 2.6M gzipped, 5.9M uncompressed ]
src08 The sources to the rest of the NetBSD
system, excluding the "share" sources
[ 20M gzipped, 43M uncompressed ]
ssrc08 The "share" sources. These include
sources for the man pages not associated
with specific programs, the sources
for the dictionary, and so on.
[ 5.1M gzipped, 9.3M uncompressed ]
It is worth noting that unless all of the source
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 this case is a trivial modification
to one Makefile.
Finally, the security distribution set contains
crypt.c, the source file for the DES encryption
algorithm, and the binaries which depend on it.
It is named "secr08", and can be found in the
"security" subdirectory on sites which choose
to carry the complete NetBSD distribution.
[ 0.5M gzipped, 1.1M uncompressed ]
All of the sets are distributed as groups of files
named "set_name.nnn" where "set_name" is the
distribution set name, and "nnn" is the sequence
number of the file, starting with 000 for the first
file. All of these files except the last files
for each set are 240,640 bytes long. (The last
file is just long enough to contain the rest
of the data for that distribution set.)
Put together, the files for a set comprise a
gzipped tar file. If you don't want to
go through the install process, but want to
look at the contents of the files, you could use
the command
cat set_name.??? | gunzip | tar tvf -
to get a table of contents of the file set, or
cat set_name.??? | gunzip | tar xvf -
to actually extract the files.
Using this method, the files are extracted,
"below" the current directory. That is, if you
want to extract the binaries "into" your system,
i.e. replace the system binares with them, you have
to run the "tar xvf" from /.
In each of the distribution 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
check the integrity of the archives, if you suspect
one of the files is corrupt and have access to a
cksum binary.
System Requirements and Supported Devices:
------ ------------ --- --------- -------
NetBSD 0.8 runs on ISA (AT-Bus) and EISA systems, with
386 and 486 processors, with or without math coprocessors.
It does NOT support Micro-channel systems, such as some
IBM PS/2 systems. The minimal configuration includes
4Meg of RAM, and a 30Meg hard disk, but to install the entire
system you'll need much more disk space, and to run X
or compile the system more RAM is recommended. (4Meg
will actually allow you to run X and/or compile, but it's
extremely slow.)
Supported devices include:
Standard floppy controllers
Standard hard disk controllers:
MFM
ESDI
IDE
RLL
SCSI hard disk controllers:
Adaptec AHA-1542A, -1542B [ only on kc-aha floppy ]
Adaptec AHA-1742 (EISA) [ only on kc-ahb floppy ]
Bustec 742 (EISA) [ only on kc-ahb floppy ]
Ultrastor 14f
Display Adaptors:
MDA
CGA
VGA (and SVGA)
HGC
Serial communications ports
Ethernet controllers
SMC/WD 8003, 8013, and equivalents
(including the SMC "Elite" series)
Novell NE1000, NE2000
3COM 3c503
ISOLAN ISOLink
Tape drives:
QIC-02 format tape drives
most SCSI tape drives should work
_NO_ QIC-40 or QIC-80 tape drives will work
CD-ROM drives:
most SCSI CD-ROM drives should work
_NO_ non-SCSI CD-ROM drives will work
To be detected by the distributed kernels, the devices must
be configured as follows:
Device Name Port IRQ DRQ Misc
------ ---- ---- --- --- ----
Floppy Cntlr. fdc0 0x3f0 6 2
Std. Hard Disk Cntlr.
wdc0 0x1f0 14
AHA-154x SCSI Cntlr. 0x330 11 5 [ only on kc-aha floppy ]
AHA-1742 SCSI Cntlr. automagically configured [ only on kc-ahbbt floppy ]
BT742 SCSI Cntlr. 0x330 12 [ only on kc-ahbbt floppy ]
UHA-14f SCSI Cntlr. 0x330 11 5
SCSI Disks sd[0-2] automagically configured
SCSI Tapes st[01] automagically configured
SCSI CD-ROMs cd0 automagically configured
Serial Ports com0 0x3f8 4
com1 0x2f8 3
SMC/WD Ethernet wd0 0x280 2 iomem 0xd0000 iosize 8192
Novell Ethernet ne0 0x300 2
3COM 3c50 ec0 0x250 2 iomem 0xd8000 iosize 8192
ISOLAN ISOLink is0 0x320 10 7
QIC-02 Tape wt0 0x300 5 1
Getting the System on to Useful Media:
------- --- ------ -- -- ------ -----
Installation is supported from several media types, including:
MS-DOS floppies
Tape
NFS partitions
FTP
No matter what you do, however, you'll need to have
three disks (1.2M or 1.44M) handy, on which you will put
the kernel-copy image and the install floppy images.
The images are available from the directory "floppies",
under the root of the NetBSD tree at your favorite
archive site. They're available both as raw
disk images, and gzipped, to save time downloading.
If you are using an AHA-154x SCSI host adapter, you need
the kc-aha.fs image. If you're using an AHA-1742 or
BT-742 SCSI host adapter, then you'll need the kc-ahbbt.fs
image. If you're using none of these disk controllers,
you can use either kernel-copy floppy image.
If you are using UNIX to make the floppies, you should
use the command dd(1) to write the raw floppy images
(.fs files) to the disks. "man dd" or ask your system
administrator for details on the correct set of arguments
to use; it will be slightly different from system to system,
and the exact set of necessary arguments to dd is beyond the
scope of this document.
If you are using DOS to make the floppies, you should
use the rawrite utilitiy, provided in the directory
"utilities" in the distribution. It will write a raw (.fs file)
image to a disk.
The steps necessary to prepare the distribution sets
for installation depend on which method of installation
you choose. The various methods are explained below.
To prepare for installing via MS-DOS floppies:
To install NetBSD from MS-DOS floppies, you need to do
the following:
Count the number of "set_name.nnn" files
you have. Call this number N. You will
need N/6 1.44M floppies, or N/5 1.2M
floppies to install the distribution
in this manner.
Format all of the floppies, with MS-DOS.
Don't make any of them MS-DOS bootable
floppies. (i.e. don't use "format /s"!)
Place all of the "set_name.nnn" files on
the DOS disks. (How you do this is up to
you. You could, for instance, use a DOS
terminal program to download them on to
the floppies, or perhaps use a UNIX machine
capable of reading and writing DOS filesystems
to place the files on the disk. The
possibilities are almost endless.)
Once you have the files on DOS disks, you can
proceed to the next step in the installation
process, preparing your hard disk.
To prepare for installing via a tape:
To install NetBSD from a tape, you need to be somehow
to get the NetBSD filesets you wish to install on
your system on to the appropriate kind of tape,
in tar format.
If you're making the tape on a UN*X system, the easiest
way to do so is:
tar cvf <tape_device> <files>
where "<tape_device>" is the name of the tape device
that describes the tape drive you're using (possibly
something like /dev/nrst0, but we make no guarantees 8-).
If you can't figure it out, ask your system administrator.
"<files>" are the names of the "set_name.nnn" files
which you want to be placed on the tape.
To prepare for installing via an NFS partition:
NOTE: this method of installation is recommended
only for those already familiar with using
the BSD network-manipulation commands and
interfaces. If you aren't, this documentation
should help, but is not intended to be
all-encompassing.
Place the NetBSD software you wish to install into
a directory on an NFS server, and make that directory
mountable by the machine which you will be installing
NetBSD on. This will probably require modifying the
/etc/exports file of the NFS server and resetting
mountd, acts which will require superuser privileges.
Note the numeric IP address of the NFS server and of
the router closest to the the new NetBSD machine,
if the NFS server is not on a network which is
directly attached to the NetBSD machine.
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
To prepare for installing via via FTP:
NOTE: this method of installation is recommended
only for those already familiar with using
the BSD network-manipulation commands and
interfaces. If you aren't, this documentation
should help, but is not intended to be
all-encompassing.
The preparations for this method of installation
are easy: all you have to do is make sure that
there's some FTP site from which you can retrieve
the NetBSD installation when it's time to do
the install. You should know the numeric IP
address of that site, the numeric IP address of
your nearest router if one is necessary
Once you have done this, you can proceed to the next
step in the installation process, preparing your hard disk.
Preparing your Hard Disk for NetBSD Installation:
--------- ---- ---- ---- --- ------ ------------
NOTE: If you wish to install NetBSD on your whole drive,
(i.e. you do not want DOS or any other operating system
on your hard disk), you can skip this section, and go on
to "Installing the NetBSD 0.8 System."
First, be sure you have a reliable back up of any data
which you may want to keep; repartitioning your hard
drive is an excellent way to destroy important data.
WARNING: If you are using a disk controller which
supports disk geometry translation, and a large disk,
you MUST turn off geometry translation before
repartitioning your disk. If you do not, NetBSD
will become hopelessly confused when you give
it partition information, as it uses the raw,
untranslated disk parameters for all operations.
Second, using the DOS "fdisk" program, repartition
your hard drive to create a new partition of at least
30Megs in size. Note the starting location and size
of this new partition; you will need this information
when you install NetBSD.
Third, using fdisk, set the other partition to be "active",
then, after leaving fdisk, do whatever is necessary
to restore order to that partition. (If that partition
used to contain DOS, this will probably involve invoking
the DOS "format" command, probably in the manner of
"format c:/s". You will then have to restore your
backed-up data to the partition.)
You are now set to install NetBSD on your hard drive.
Installing the NetBSD 0.8 System:
---------- --- ------ --- ------
Installing NetBSD is a relatively complex process, but,
if you have this document in hand and are careful to
read and remember the information which is presented
to you by the install program, it shouldn't be too
much trouble.
Before you begin, you must know several of your hard
disk's parameters. You must know the number of sectors
per track, the number of tracks per cyliner (i.e. the
number of heads), the number of bytes per sector,
and the number of cylinders on the disk. If you
use a disk controller which supports disk geometry
translation, you must turn geometry translation off,
or NetBSD will not operate properly.
If you are installing NetBSD into a partition on your
hard disk, you should have completed the section
regarding the preparation of your hard disk, and you should
know the size and offset from the beginning of the disk
of the NetBSD partition.
Once you know that information you should be ready
to proceed with the NetBSD installation. It will probably
be useful to have a pencil, paper, and calculator handy.
That all being said, it's finally time to install the system!
The following is a walk-through of the steps necessary
to get NetBSD 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.
Insert the kernel-copy floppy into the boot
drive. Boot from it. It will take a while to
load the kernel from the floppy, probably
on the order of a minute or two.
You should see a copyright notice and some information
about the hardware in your machine. This could take
a long time (up to two minutes) to print out, especially
if you're using a non-SCSI hard disk controller. Eventually,
you should see two lines:
"* insert the floppy you want to have mounted as
* root, and hit any key to continue booting:"
If you do not see this message after a reasonable period of
time, try it again. If you still don't see it, you can't
install NetBSD on your hardware. If you were able to
install 386BSD, this is definitely a bug in our software;
please report it! Please include your system configuration,
and any other relevant information in your bug report.
Once you have reached that prompt, remove the kernel-copy
floppy from the drive, insert the first installation disk,
and hit any key.
After a short while (approximately 30 seconds), 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.
You will then be asked what type of disk drive you have.
The valid options are listed on the screen. You may
be asked if your disk supports automatic sector forwarding.
Answer yes if and only if you know that it automatically
re-maps bad blocks for you.
The install program will then print out what it thinks
your disk is. It can only install on the first
"wd" (i.e. ESDI, ST506, or IDE) disk, or the first "sd"
(SCSI) disk in the system.
You will then be asked for a label name for your disk.
This should be a short, one-word name for your disk,
e.g. "cp3100-mine" for a Conner Peripherals "3100" disk.
You needn't remember this name.
Next, you will be prompted for the information you were
supposed to remember about your disk. Enter it when the
install program asks for it.
When asked for the size of the NetBSD portion of the disk,
either input the number listed as the total size of your
disk, or multiply the number of cylinders in the NetBSD
portion of your disk by the number of sectors per cylinder
(also listed by the install program) and input the result.
If you are not installing on the whole disk, you will
be asked for the offset of the NetBSD partition from
the beginning of the disk. Again, calculate this
number from the information you recorded when partitioning
your disk with fdisk, and input the result.
You will then be asked for the size of your root partition,
in sectors. Enter a number which is a multiple of the
number of sectors per cylinder for your disk, in the
range of 12000 to 16000, assuming your disk uses 512 byte
sectors and depending on how large you want your root
partition to be.
Next, you will be asked for the size of your swap partition.
You should probably allocate around twice as much swap
space as you do real memory, and, again, this number should be
a multiple of the number of sectors per cylinder. As an example,
if you've got 8Meg memory and 512 byte sectors, you want
a multiple of your sects/cyl close to 32000 as your swap size.
The install program will then ask you for information
about the rest of the partitions you want on your disk.
For the purposes of this document, you only want
one more: /usr. Therefore, at the prompt, when in asks
you to enter the size of the next partition, enter
the number of sectors remaining in the NetBSD portion of
the disk. (It is displayed on the previous line.)
When it asks you for the mount point for this partition,
say "/usr".
YOU ARE NOW AT THE POINT OF NO RETURN.
If you confirm that you want to install NetBSD, your
hard drive will be modified, and perhaps it contents
scrambled at the whim of the install program.
This is especially likely if you gave the install
program incorrect information.
If you are sure you want to proceed, enter "yes" at the prompt.
The install program will now make the filesystems you
specified. There should be no errors in this section
of the installation. If there are, restart from the
the beginning of the installation process.
After the installation program prompts you to see if you'd
like to be told about all of the files it's going to copy
to your hard drive, it will spend a few minutes copying these
files and then will print out an informative message and
place you at a "#" prompt.
Read the message and note which partition you need
to copy a kernel to. Reboot the machine according
to the instructions given and boot once again
off of the kernel-copy floppy.
At the prompt asking you to replace the floppy and
press any key, do _not_ replace the floppy, just
press any key.
At the ">" prompt, enter "copy" to prepare to copy
the kernel on the floppy to your hard disk.
At the next ">" prompt, enter the disk partition to
which you want to copy the kernel.
It will work for a minute or two, then present you
with another prompt. Follow the instructions given,
and reboot from the hard disk.
When the machine begins to boot, a three-line banner
should appear at the top of the screen. In a few
seconds, a bunch of messages should appear,
describing the hardware in your machine. Once again,
this stage can take up to two minutes, so DO NOT PANIC!
It will ask you to insert the second install floppy
into a floppy drive, and enter that drive's number.
"0" corresponds to DOS's "A:" drive, "1" corresponds
to DOS's "B:" drive.
After you enter the number it will ask you if you'd
like to watch its progress, and after you answer this
question it will begin installing still more files
on your hard disk. This should take no more than
3 minutes.
You will be given (more) instructions, and you
should reboot the machine again, from the hard drive.
CONGRATULATIONS: You now have the minimum base of
NetBSD files on your hard disk! Now you get to
install the dxistribution file sets.
After the machine is done booting, you will be presented
with a screenful of information about what to do next.
What you do from this point on depends on which
media you're using to install NetBSD. Follow the appropriate
instructions, given below.
To install from tape or floppy:
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, use the command "set_tmp_dir" and enter
your choice. The default is /usr/distrib.
After you have picked a temporary directory,
you should issue the appropriate load command:
load_fd if you're loading from floppies
load_qic_tape if loading from QIC-02 tape
load_scsi_tape if you're loading from the first
SCSI tape drive in the system.
You will then be prompted for information as to which
floppy drive to load from, if you choose that
method of isntallation.
Next, you will be told to insert the media into
the appropriate drive, and hit return. Continue
to follow instructions until you are returned to
the "#" prompt.
Go to the directory which contains the first
distribution set you wish to install. This is
either the directory you specified above, if loading
from floppy, or possibly a subdirectory of that
directory, if you loaded from tape.
When there, run "set_tmp_dir" again, and choose
the default temporary directory, by hitting
return at the prompt.
Run the "extract" command, giving it as its sole
argument the name of the distribution set you
wish to extract. For example, to extract the base
distribution, use the command:
extract base08
and to extract the games distribution:
extract game08
After the extraction is complete, go to the location
of the next set you want to extract, "set_tmp_dir"
again, and once again issue the appropriate
extract command. Continue this process until
you've finished installing all of the sets which you
desire to have on your hard disk.
After each set is finished, if you know that you
are running low on space you can remove the
distribution files for that set by saying:
rm set_name.???
For example, if you wish to remove the distribution
files for the game08 set, after the "extract game08"
command has completed, issue the command:
rm game08.???
Once you have extracted all sets and are at the "#" prompt
again, proceed to the section "Configuring Your System,"
below.
To install via FTP or NFS:
First, use set_tmp_dir to pick a temporary directory
for the installation files. /usr/distrib is suggested.
configure the appropriate ethernet interface (e.g. we0,
ne0, etc.) up, with a command like:
ifconfig <ifname> <ipaddr> [netmask <netmask>]
where <ifname> is the interface name (e.g. we0, etc.),
and <ipaddr> is the numeric IP address of the interface.
If the interface has a special netmask, supply
the word "netmask" and that netmask at the end of the
command line. For instance, without a special netmask:
ifconfig we0 129.133.10.10
or with a special netmask
ifconfig we0 128.32.240.167 netmask 0xffffff00
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:
route add default <gate_ipaddr>
where <gate_ipaddr> is your gateway's numeric IP address.
If you are NFS-mounting the distribution sets,
mount them on the temporary directory with the command:
mount -t nfs <serv_ipaddr>:<dist_dir> <tmp_dir>
where <serv_ipaddr> is the server's numeric IP address,
<dist_dir> is the path to the distribution files on
the server, and <tmp_dir> is the name of the local
temporary directory.
Once this is done, proceed as if you had loaded the
files from tape, "cd"ing to the appropriate directories
and running "set_tmp_dir" and "extract" as appropriate.
If you are retrieving the distribution sets using ftp,
cd into the temp directory, and execute the command:
ftp <serv_ipaddr>
where <serv_ipaddr> is once again the server's
numeric IP address. Get the files with FTP,
taking care to use binary mode to transfer
all files.
Once you have all of the files for the distribution sets
you wish to install, you can proceed using the instructions
above as if you had installed the files from a floppy.
Configuring Your System:
----------- ---- ------
Once you have finished extracting all of the distribution sets that
you want on your hard drive and are back at the "#" prompt,
you are ready to configure your system.
The configuration utilitiy expects that you have installed the base
system. If you have not, you will not be able to run it successfully
(nor will you have a functional system regarless of configuration).
To configure the newly installed operating system, run the
command "configure".
Configure will ask for the machine's hostname, domain name, and other
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 be a completely functional NetBSD system. It is not
completely configured, however; you should adjust the /etc/sendmail.cf
file as necessary to suit your site and/or disable sendmail in
/etc/rc and you should look in /etc/netstart to make sure the flags
are defined correctly for your site.
Once you are done with configuration, reboot with the "reboot" command.
When it boots off of the hard drive, you will have a complete
NetBSD system! CONGRATULATIONS! (You really deserve them!!!)
Administrivia:
-------------
Registration? What's that?
If you've got something to say, do so! We'd like your input.
Please send random comments to:
netbsd-comments@sun-lamp.cs.berkeley.edu
Please send bug reports, and that sort of material to:
netbsd-bugs@sun-lamp.cs.berkeley.edu
If you'd like to help with this effort, and have an idea as to how
you could be useful, send mail to:
netbsd-help@sun-lamp.cs.berkeley.edu
THANKS FOR USING THIS; that's what makes it all worthwhile.
Thanks go to:
------ -- --
Members of UCB's Computer Systems Research Group, including but not limited to:
Keith Bostic
Marshall Kirk McKusick
Mike Karels
for their ongoing work on BSD systems.
William and Lynne Jolitz for providing 386BSD.
Brian Berliner, Jeff Polk, et al., because without CVS this
would have been MUCH harder.
All of the people involved in the patch kit, including but not limited to:
Terry Lambert
Nate Williams
Jordan Hubbard
Rod Grimes
and the many people who've submitted patches!
for a good number of the bug fixes and improvements to be found in
this release.
Rob Robertson, for the disk space on agate.berkeley.edu that got
this _whole_ thing going.
Dave Silvia for a head start on a reasonable install program.
The attendees of the Winter '93 USENIX 386BSD BOF, whose discussions
of various issues surrounding 386BSD caused cgd to decide to jump in
head first.
Carl Staelin, for his patience...
And, of course, all of the people who've put sweat and tears into that
which constitutes this package over the last year.
(Obviously, there are a lot more people who deserve thanks here.
If you're one of them, and would like to be here, by all means,
_SAY SOMETHING_... We've probably forgotten you!)
We are:
-- ---
Chris G. Demetriou <cgd@sun-lamp.cs.berkeley.edu>
Adam Glass <glass@sun-lamp.cs.berkeley.edu>
Theo Deraadt <deraadt@sun-lamp.cs.berkeley.edu>
Sean Eric Fagan <sef@kithrup.com>
Charles Hannum <mycroft@sun-lamp.cs.berkeley.edu>
Rodney Grimes <rgrimes@sun-lamp.cs.berkeley.edu>
Chris Provenzano <proven@sun-lamp.cs.berkeley.edu>
Peter da Silva <pds@sun-lamp.cs.berkeley.edu>
--
Chris G. Demetriou cgd@agate.berkeley.edu
"Sometimes it is better to have twenty million instructions by
Friday than twenty million instructions per second." -- Wes Clark