INSTALL.ext,
where
ext
is one of
.ps, .html, .more,
or .txt.
.ps.html.moremore(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txtYou are reading the HTML version.
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, The X Window System, and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
It is impossible to completely summarize the nearly two years of development that went into the NetBSD1.4.1 release. Some highlights include:
ftp(1)
client has been improved even further. See the man page for details.
wscons(4),
has been integrated into many ports.
usb(4)
for an overview.
nsswitch.conf(5)
functionality to the system to specify the search order for system databases.
syslogd(8)
now supports listening on multiple sockets, to make the
chrooting of servers easier.
As has been noted, there have also been innumerable bug fixes.
Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
The Atari release stepped in in March 1995. The first official release was NetBSD1.1. About a year later, NetBSD1.2 was released for the Atari. This release fixed a large number of bugs and made the Atari-port a stable member of the NetBSD family. The saga continued with the NetBSD1.3 release. In this release, support was added for the Medusa Hades, Riebl ethernet and Falcon IDE support. And now, yet another release is emerging!
New on the NetBSD1.4 release (atari specific):
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis. In addition, we intend to provide Anonymous CVS access to the NetBSD source tree in the near future, so that anyone on the internet can examine the full NetBSD source code repository.
We intend to integrate free, positive changes from whatever sources submit 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
and because of them that
NetBSD
exists.
If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org.
ftp.au.netbsd.org
RMIT University, Melbourne
ftp://ftp.au.netbsd.org/pub/NetBSD/
ftp2.au.netbsd.org
University of Queensland, Brisbane
ftp://ftp2.au.netbsd.org/pub/NetBSD/
ftp.at.netbsd.org
University of Technology, Vienna
ftp://ftp.at.netbsd.org/pub/NetBSD/
ftp.ravel.ufrj.br
Cidade Universitaria
ftp://ftp.ravel.ufrj.br/pub/NetBSD/
ftp.dk.netbsd.org
Aalborg University
ftp://ftp.dk.netbsd.org/pub/NetBSD/
ftp.fi.netbsd.org
The Finnish University and Research Network, Espoo
ftp://ftp.fi.netbsd.org/pub/NetBSD/
ftp.fr.netbsd.org
Paris University
ftp://ftp.fr.netbsd.org/pub/NetBSD/
ftp.de.netbsd.org
University of Trier
ftp://ftp.de.netbsd.org/pub/NetBSD/
ftp2.de.netbsd.org
University of Erlangen-Nuremberg
ftp://ftp2.de.netbsd.org/pub/NetBSD/
ftp.uni-regensburg.de
University of Regensburg
ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD/
ftp.jp.netbsd.org
Internet Research Institute Inc., Tokyo
ftp://ftp.jp.netbsd.org/pub/NetBSD/
core.ring.gr.jp
Electrotechnical Laboratory
ftp://core.ring.gr.jp/pub/NetBSD/
ftp.dti.ad.jp
Dream Train Internet Inc., Tokyo
ftp://ftp.dti.ad.jp/pub/NetBSD/
mirror.nucba.ac.jp
Nagoya University of Commerce and Business
ftp://mirror.nucba.ac.jp/mirror/NetBSD/
netbsd.tohoku.ac.jp
Tohoku University, Sendai
ftp://netbsd.tohoku.ac.jp/NetBSD/
ring.asahi-net.or.jp
ASAHI Net
ftp://ring.asahi-net.or.jp/pub/NetBSD/
ftp.nl.netbsd.org
University of Amsterdam
ftp://ftp.nl.netbsd.org/pub/NetBSD/
ftp.no.netbsd.org
Bergen IT Consult AS
ftp://ftp.no.netbsd.org/pub/NetBSD/
ftp.ntnu.no
Norwegian University of Science and Technology
ftp://ftp.ntnu.no/pub/NetBSD/
ftp.ru.netbsd.org
Landau Institute for Theoretical Physics, Chernogolovka
ftp://ftp.ru.netbsd.org/pub/NetBSD/
ftp.stacken.kth.se
Royal Institute of Technology, Stockholm
ftp://ftp.stacken.kth.se/pub/OS/NetBSD/
ftp.sunet.se
Swedish University NETwork, Uppsala
ftp://ftp.sunet.se/pub/os/NetBSD/
ftp.uk.netbsd.org
Domino, London
ftp://ftp.uk.netbsd.org/pub/NetBSD/
sunsite.org.uk
ftp://sunsite.org.uk/packages/netbsd/
ftp.netbsd.org
Silicon Valley, California
ftp://ftp.netbsd.org/pub/NetBSD/
ftp.cs.umn.edu
University of Minnesota
ftp://ftp.cs.umn.edu/pub/NetBSD
ftp.eecs.umich.edu
University of Michigan, Ann Arbor
ftp://ftp.eecs.umich.edu/pub/NetBSD/
ftp.iastate.edu
Iowa State University
ftp://ftp.iastate.edu/pub/netbsd/
ftp.op.net
ftp://ftp.op.net/pub/NetBSD/
ftp.stacken.kth.se
Royal Institute of Technology, Stockholm
AFS path: /afs/stacken.kth.se/ftp/pub/OS/NetBSD
ftp.iastate.edu
Iowa State University
AFS path: /afs/iastate.edu/public/ftp/pub/netbsd
sunsite.org.uk
Instructions: mount -o ro sunsite.org.uk:/public/packages/netbsd /mnt
sup.au.netbsd.org
RMIT University, Melbourne
Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup
sup.fr.netbsd.org
Paris University
Instructions: Similar to sup.netbsd.org
sup.de.netbsd.org
University of Trier
Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example
sup.jp.netbsd.org
Internet Research Institute Inc., Tokyo
Instructions: ftp://sup.jp.netbsd.org/pub/NetBSD/sup/README.sup
sup.no.netbsd.org
Norwegian University of Science and Technology
Instructions: See /usr/src/share/examples/supfiles/sup.no.netbsd.org
sup.uk.netbsd.org
Domino, London
Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup
sup.netbsd.org
Silicon Valley, California
Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup
ftp.cs.umn.edu
University of Minnesota
Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG
www.au.netbsd.org
RMIT University, Melbourne
http://www.au.netbsd.org/
www.at.netbsd.org
University of Technology, Vienna
http://www.at.netbsd.org/
www.fi.netbsd.org
Global Wire Oy, Lappeenranta
http://www.fi.netbsd.org/
www.fr.netbsd.org
Paris University
http://www.fr.netbsd.org/
www.de.netbsd.org
http://www.de.netbsd.org/
www.jp.netbsd.org
Internet Research Institute Inc., Tokyo
http://www.jp.netbsd.org/
www.no.netbsd.org
Bergen IT Consult AS
http://www.no.netbsd.org/
www.netbsd.org
Western Washington State University
http://www.netbsd.org/
www2.us.netbsd.org
New York
http://www.us.netbsd.org/
.../NetBSD-1.4.1/
BUGSCHANGESLAST_MINUTEMIRRORSREADME.filesTODOpatches/source/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD1.4.1 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly.
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. The source distribution sets are as follows:
Most of the above source sets are located in the
source/sets
subdirectory of the distribution tree. The secrsrc.tgz set is
contained in the
source/security
subdirectory. This set, which is
available only to users in the United States and Canada, contains the
sources normally found in
/usr/src/domestic
- primarily kerberos and
other cryptographic security related software. (Remember, because of
United States law, it may not be legal to distribute this set to
locations outside of the United States and Canada.)
The source sets are distributed as compressed tar files. They may be
unpacked into
/usr/src
with the command:
cat set_name.tgz | gunzip | (cd /; tar xpf - )
The sets/Split/
and security/Split/
subdirectories contain split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution. The
split sets are are named "set_name.xx" where "set_name" is the
distribution set name, and "xx" is the sequence number of the file,
starting with "aa" for the first file in the distribution set, then
"ab" for the next, and so on. All of these files except the last one
of each set should be exactly 240,640 bytes long. (The last file is
just long enough to contain the remainder of the data for that
distribution set.)
The split distributions may be reassembled and extracted with
cat as follows:
cat set_name.?? | gunzip | (cd /; tar xpf - )
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)
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. Checksums based on
other algorithms may also be present - see the
release(7)
man page for details.
atari
subdirectory of the distribution:
.../NetBSD-1.4.1/atari/
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/sets/security/installation/atari/binary/sets
subdirectory
of the
NetBSD1.4.1
distribution tree, and are as follows:
/usr/include)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set). This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/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.)
/usr/share.
groff(1),
all related programs, and their manual pages.
The atari security distribution set is named
secr and can be found in the
atari/binary/security
subdirectory of the
NetBSD1.4.1
distribution tree. It contains security-related binaries
which depend on cryptographic source code. You do not need this
distribution set to use encrypted passwords in your password file; the
base
distribution includes a crypt library which can perform
only the one-way encryption function. The security distribution
includes a version of the Kerberos IV network security system, and
a Kerberized version of
telnet(1)
program. The secr
distribution set can be found only on those sites which carry the complete
NetBSD
distribution and which can legally obtain it. Because
of United States law, it may not be legal to distribute this set
to locations outside of the United States and Canada.
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.3.1. Binary sets for the X Window system are distributed with NetBSD. The sets are:
The atari binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz, e.g.
base.tgz.
The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are /-relative and therefore are extracted below the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar xfp command from /.
Additional kernels to those included in the distribution sets may be found
in the
atari/binary/kernel
subdirectory of the
NetBSD1.4.1
distribution tree. These kernels are generally named something like
netbsd.BOOT.gz
or some other suitable name. Please note that these kernels are simply
gzipped and are not in tar archives.
There are three atari floppy images to be found in the
atari/installation/floppies
subdirectory of the
NetBSD1.4.1
distribution. One of them is a bootable TOS kernel floppy and the other
two are installation floppies. They are described in more detail below.
There are gzipped versions of each available, for easier downloading.
(The gzipped versions have the
.gz
extension added to their names.)
For the TT030 and Falcon, the (720KB) floppy is named boot.fs and the kernel supplied is 'BOOT'. For the Hades, you need the hades-boot.fs floppy (1.44MB), the kernel is 'HADES'.
The floppies meant for 720KB disks are named
miniroot.fs.1 and miniroot.fs.2.
There is also an image for an 1.44MB disk:
miniroot.fs.
There are also TOS utilities in the
atari/installation/misc
subdirectory, which you will need to get NetBSD/Atari 'up-and-running'.
atari/floppies
directory.
All BSDSUM
files are historic
BSD checksums for the various files
in that directory, in the format produced by the command:
cksum -o 1 file
All CKSUM files are
POSIX
checksums for the various files in that
directory, in the format produced by the command:
cksum file.
All MD5 files are
MD5
digests for the various files in that
directory, in the format produced by the command:
cksum -m file.
All SYSVSUM
files are historic AT&T System V
UNIX
checksums for the various files in that directory, in the format produced by
the command:
cksum -o -2 file.
The MD5 digest is the safest checksum, followed by the POSIX
checksum. The other two checksums are provided only to ensure
that the widest possible range of system can check the integrity
of the release files.
NetBSD/atari 1.4.1 runs on a TT030, Falcon and Hades. An FPU is not required. The minimum amount of RAM required is 4Mb. On the Hades, only the Tseng PCI VGA cards (et4000/et6000/et6100) are supported in the 1.4.1 release. When an unsupported video card is present, you can use NetBSD with a serial console only.
Here is a table of recommended HD partition sizes for a full install:
partition: advise, with X, needed, with X
root (/) 20M 20M 15M 15M
user (/usr) 95M 125M 75M 105M
swap ----- 2M for every M ram -----
local (/local) up to you
Supported devices include:
This list is incomplete by definition. I can not test all SCSI peripherals,
ISA cards or PCI cards... If you have problems with such a peripheral, please
contact the port-atari mailing list.
Installation is supported from several media types, including:
No matter what you do, however, you'll need to have three disks handy, on which you will put the install and boot floppy images.
All the images are available from the directory "installation/floppies" under the root of the NetBSD/atari tree at your favorite archive site.
If you are using NetBSD/atari to make the floppies, you should use
the command dd(1) to write the raw floppy images (.fs files) to
the disk. As an example, to write the first part of the miniroot filesystem
onto a 720KB floppy in fd0 use:
dd if=miniroot.fs.1 of=/dev/rfd0b bs=9b
If you are using TOS to make the floppies, grab the 'rawwrite' utility
from the "atari/utils" directory and issue the command:
rawwrite boot.fs
This will create the boot-floppy on the floppy in drive a. The floppies should be pre-formatted on 720Kb/1.44Mb for both the 'dd' and 'rawwrite' commands to work. Pre-formatting can be best done using the desktop format command. Some other utilities seem to be giving problems.
Since the 1.3 release, it is also possible to use HD-floppies. You should than use the floppy device '/dev/rfd0c' or add the '-H' flag to 'rawwrite'.
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 install NetBSD from an GEMDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an GEMDOS partition.
Note where you placed the files, you will need this later.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
To install NetBSD from a tape, you need to somehow
get the NetBSD filesets you wish to install on
your system on to the appropriate kind of tape. If you make
the tape on a UN*X-like system, you can create it as follows:
where "<tape_device>" is the name of the (non-rewinding!) tape
device that you're using (probably something like /dev/nrst0,
but we make no guarantees 8-).
If you can't figure it out, ask your system administrator.
cd .../NetBSD-1.3/atari/binary/sets
T=<tape_device>
mt -f $T rewind
for f in base etc comp games man misc text
dd if=$f.tgz of=$T conv=sync bs=5k
done
mt -f $T rewind
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
Note you will be modifying your HD's if you mess something up here you could lose everything on all the drives that you work with. It is therefore advised that you:
If NetBSD has a disk of it's own, you can delay the partitioning until the installer requests you to do it. This means that you can safely skip the rest of this section.
If NetBSD has to share the disk with another operating system, you must take care of partitioning your harddisk before installing NetBSD; creating space for at least root, swap and /usr partitions and possibly at least one more for /local if you have the space.
As you might know; every hard disk has a "root sector" that contains information about the size of the hard disk and the partitions on the hard disk. The root sector can only contain the neccessary data for four partitions. Nobody thought that this limitation would cause any problems. After all, 640 KByte should be enough. As hard disk grew, it was neccessary to define more than four partitions. In order to be more or less compatible with the old format, a new type of partition entry was defined: XGM partions.
An XGM partition is a "look over there" sign: Another root sector can be found at the start of the XGM partition. This root sector contains the remaining real partitions. And this is the big mystery: Partitions defined in the root sector of the hard disk are called "primary partitions", partitions defined in the root sector of an XGM partition are called "extended partitions".
The bootblock will only work if the first NBD partition is a primary partition. This is not a limitation of NetBSD but a limitation of TOS/AHDI: You can only boot from primary partitions.
If you are creating your partitions with HDX, you'll have to be very careful to fulfill this rule. HDX has some very strange ideas when it comes to extended partitions. Fortunately, you can edit this stuff: The "Edit partition scheme of the unit" dialog box has a button label "expert". This button is inactive unless you have defined more than four partitions. Click on it *after* you have defined the sizes of the partitions.
A new dialog box appears on the screen. The left side contains two blocks of partitions: The upper block always contains the first four partitions, the lower block contains the last three partitions. If you have defined less than 7 partitions, some fields of the lower block will contain the string "unused". Some of the partitions will be displayed in reverse video: These are the extended partitions.
The right side contains six possible ranges for the extended partitions. It is not possible to define your own range, you will have to use one of the schemes offered by HDX. To quote from Ghostbusters: Choose and die. The default scheme used by HDX is the first scheme: Extended partitions start with the second partition and end with the second to last partition. If you have defined 7 partitions, partitions #2 to #5 will be extended partitions, while partitions #1, #6 and #7 will be primary partitions.
You can move the extended partition range by clicking on one of the buttons on the right side of the dalog box. Try to find one where your first NetBSD partition is a primary partition. Golden rules:
Good luck, you'll need it...
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 have already prepared your hard disk as detailed in the section on preparing your system for install.
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.
loadbsd -b a:/netbsd
You should see the screen clear and some information about your system as the kernel configures the hardware. Then you will be prompted for a root device. At this time remove the GEMDOS kernel boot floppy from the drive if present and insert the BSD install floppy 1. Now type `md0a' to tell the kernel to load the install filesystem into RAMdisk. While While the kernel is loading, it will show a '.' for each track loaded. After loading 80 tracks, it will ask you to insert the next floppy. At this time, insert the BSD install floppy 2 and hit any key. The kernel continous loading another 40 tracks before it continues to boot.
You are now at the point of no return! The programs in section 4 will modify your harddisk. Type Control-C now if you don't want this.
Once you've got the operating system running, there are a few things you need to do in order to bring the system into a propperly configured state, with the most important ones described below.
/etc/rc.conf
If you haven't done any configuration of
/etc/rc.conf,
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf is not configured. Multiuser boot aborted.
and with the root filesystem mounted read-write. When the system
asks you to choose a shell, simply hit return to get to a
prompt. If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and hit return. At this point, you need to configure at least
one file in the
/etc directory. Change to the
/etc
directory and take a look at the
/etc/rc.conf
file. Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed. If your
/usr directory is on a separate partition
and you do not know how to use 'ed' or 'ex', you will have to mount your
/usr
partition to gain access to 'vi'. Do the following:
mount /usr
export TERM=vt220
If you have
/var
on a seperate partition, you need to repeat
that step for it. After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname and possibly
defaultroute,
furthermore add an
ifconfig_int
for your interface
<int>,
along the lines of
ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom in /etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Other files in
/etc
that are new to NetBSD 1.4 and may require modification or
setting up include
/etc/mailer.conf,
/etc/nsswitch.conf
and
/etc/wscons.conf.
After reboot, you can 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 an account for yourself
(see below) and protect it and the "root" account with good
passwords.
Use the
vipw(8)
command to add accounts to your system,
do not edit /etc/passwd
directly. See
adduser(8)
for more information on the process of how to add a new user to the system.
If you have installed the X window system, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
There is a lot of software freely available for Unix-based systems, almost all of which can run on NetBSD. Modifications are usually needed to when transferring programs between different Unix-like systems, so the NetBSD packages collection incorporates any such changes necessary to make that software run on NetBSD, and makes the installation (and deinstallation) of the software packages easy. There's also the option of building a package from source, in case there's no precompiled binary available.
Precompiled binaries can be found at
ftp://ftp.netbsd.org/pub/NetBSD/packages/
Package sources for compiling packages can be obtained by
retrieving the file
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz
and extracting it into
/usr/pkgsrc.
See
/usr/pkgsrc/README
then for more information.
/etc/localtime
symlink to the appropriate file under
/usr/share/zoneinfo.
/etc/aliases
to forward root mail to the right place (run
newaliases(1)
afterwards.)
/etc/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
Before updating, you probably would want to backup your original filesystems!
The update procedure will not overwrite or remove any files not present in the sets you install. If you've replaced programs present in the distribution, you have to replace them again after you did the update. The etc-set needs special caution. You generally don't want to install this one when upgrading. It is recommended that you get a copy of this set and _carefully_ upgrade your configuration files by hand.
Ok, let's go. Insert the bootfloppy and follow the 'normal' installation procedure until it asks you if you wish to install or upgrade. At this time, select upgrade. You will now be greeted and reminded of the fact that this is a potential dangerous procedure and that you should not upgrade the etc-set.
When you decide to proceed, you will be prompted to enter your root disk. After you've done this, it will be checked automatically to make sure that the filesystem is in a sane state before making any modifications. After this is done, you will be asked if you want to configure your network. You can skip this section on NetBSD/Atari for now.
You are now allowed to edit your fstab. Normally you don't have to. Note that the upgrade-kit uses it's own copy of the fstab. Whatever you do here *won't* affect your actual fstab. After you are satisfied with your fstab, the upgrade-kit will check all filesystems mentioned in it. When they're ok, they will be mounted.
You will now be asked if your sets are stored on a normally mounted filesystem. You should answer 'y' to this question if you have the sets stored on a filesystem that was present in the fstab. The actions you should take for the set extraction are pretty logical (I think). You might want to read the notes in section 9 (Installing the distribution sets) of the installation section.
After you have extracted the sets, the upgrade kit will proceed with setting the timezone and installing the kernel and bootcode. This is all exactly the same as described in the installation section.
/usr/include/machine
Documentation is available if you first install the manual
distribution set. Traditionally, the
``man pages''
(documentation) are denoted by
``name(section)''.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man
command is used to view the documentation on a topic, and is
started by entering
man[ section]
topic.
The brackets
[]
around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
lowest numbered section name will be displayed. For instance, after
logging in, enter
man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5)m
enter
man 5 passwd
instead.
If you are unsure of what man page you are looking for, enter apropos subject-word
where subject-word is your topic of interest; a list of possibly related man pages will be displayed.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.ORG.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
netbsd-bugs@NetBSD.ORG.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses. If you're interested in doing a serious amount of work on a specific port, you probably should contact the "owner" of that port (listed below).
If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@NetBSD.ORG.
As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.
Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick
for their ongoing work on BSD systems, support, and encouragement.
Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek
for answering lots of questions, fixing bugs, and doing the various work they've done.
Jason Birnschein Jason Brazile David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Greg Gingerich Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Jordan K. Hubbard Scott Kaplan Noah M. Keiserman Chris Legrow Neil J. McRae Perry E. Metzger Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow
Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Canada Connect Corporation Demon Internet, UK Digital Equipment Corporation Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. VMC Harald Frank, Germany
(in alphabetical order)
| The NetBSD core group: | ||||||||
| Paul Kranenburg | pk@NetBSD.ORG | |||||||
| Scott Reynolds | scottr@NetBSD.ORG | |||||||
| Christos Zoulas | christos@NetBSD.ORG | |||||||
|
| ||||||||
| The portmasters (and their ports): | ||||||||
| Mark Brinicombe | mark@NetBSD.ORG | arm32 | ||||||
| Jeremy Cooper | jeremy@NetBSD.ORG | sun3x | ||||||
| Ross Harvey | ross@NetBSD.ORG | alpha | ||||||
| Ignatios Souvatzis | is@NetBSD.ORG | amiga | ||||||
| Eduardo Horvath | eeh@NetBSD.ORG | sparc64 | ||||||
| Paul Kranenburg | pk@NetBSD.ORG | sparc | ||||||
| Anders Magnusson | ragge@NetBSD.ORG | vax | ||||||
| Tsubai Masanari | tsubai@NetBSD.ORG | macppc | ||||||
| Tsubai Masanari | tsubai@NetBSD.ORG | newsmips | ||||||
| Minoura Makoto | minoura@NetBSD.ORG | x68k | ||||||
| Phil Nelson | phil@NetBSD.ORG | pc532 | ||||||
| Scott Reynolds | scottr@NetBSD.ORG | mac68k | ||||||
| Darrin Jewell | dbj@NetBSD.ORG | next68k | ||||||
| Gordon Ross | gwr@NetBSD.ORG | sun3, sun3x | ||||||
| Kazuki Sakamoto | sakamoto@NetBSD.ORG | bebox | ||||||
| Wolfgang Solfrank | ws@NetBSD.ORG | powerpc | ||||||
| Jonathan Stone | jonathan@NetBSD.ORG | pmax | ||||||
| Jason Thorpe | thorpej@NetBSD.ORG | hp300 | ||||||
| Frank van der Linden | fvdl@NetBSD.ORG | i386 | ||||||
| Leo Weppelman | leo@NetBSD.ORG | atari | ||||||
| Steve Woodford | scw@NetBSD.ORG | mvme68k | ||||||
|
| ||||||||
| The NetBSD 1.4.1 Release Engineering team: | ||||||||
| Ted Lemon | mellon@NetBSD.ORG | |||||||
| Perry Metzger | perry@NetBSD.ORG | |||||||
| Curt Sampson | cjs@NetBSD.ORG | |||||||
|
| ||||||||
| Developers and other contributors: | ||||||||
| Steve Allen | wormey@NetBSD.ORG | |||||||
| Lennart Augustsson | augustss@NetBSD.ORG | |||||||
| Christoph Badura | bad@NetBSD.ORG | |||||||
| Manuel Bouyer | bouyer@NetBSD.ORG | |||||||
| Robert V. Baron | rvb@NetBSD.ORG | |||||||
| John Brezak | brezak@NetBSD.ORG | |||||||
| Allen Briggs | briggs@NetBSD.ORG | |||||||
| Aaron Brown | abrown@NetBSD.ORG | |||||||
| David Brownlee | abs@NetBSD.ORG | |||||||
| Simon Burge | simonb@NetBSD.ORG | |||||||
| Dave Burgess | burgess@cynjut.infonet.net | |||||||
| Dave Carrel | carrel@NetBSD.ORG | |||||||
| Bill Coldwell | billc@NetBSD.ORG | |||||||
| Chuck Cranor | chuck@NetBSD.ORG | |||||||
| Alistair Crooks | agc@NetBSD.ORG | |||||||
| Aidan Cully | aidan@NetBSD.ORG | |||||||
| Rob Deker | deker@NetBSD.ORG | |||||||
| Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
| Matthias Drochner | drochner@NetBSD.ORG | |||||||
| Enami Tsugutomo | enami@NetBSD.ORG | |||||||
| Bernd Ernesti | veego@NetBSD.ORG | |||||||
| Erik Fair | fair@NetBSD.ORG | |||||||
| Hubert Feyrer | hubertf@NetBSD.ORG | |||||||
| Thorsten Frueauf | frueauf@NetBSD.ORG | |||||||
| Brian R. Gaeke | brg@dgate.org | |||||||
| Thomas Gerner | thomas@NetBSD.ORG | |||||||
| Justin Gibbs | gibbs@NetBSD.ORG | |||||||
| Adam Glass | glass@NetBSD.ORG | |||||||
| Michael Graff | explorer@NetBSD.ORG | |||||||
| Brad Grantham | grantham@tenon.com | |||||||
| Matthew Green | mrg@NetBSD.ORG | |||||||
| Juergen Hannken-Illjes | hannken@NetBSD.ORG | |||||||
| Charles M. Hannum | mycroft@NetBSD.ORG | |||||||
| Eric Haszlakiewicz | erh@NetBSD.ORG | |||||||
| Michael L. Hitch | osymh@NetBSD.ORG | |||||||
| Ken Hornstein | kenh@NetBSD.ORG | |||||||
| Marc Horowitz | marc@NetBSD.ORG | |||||||
| ITOH Yasufumi | itohy@NetBSD.ORG | |||||||
| Matthew Jacob | mjacob@NetBSD.ORG | |||||||
| Lonhyn T. Jasinskyj | lonhyn@NetBSD.ORG | |||||||
| Darrin Jewell | dbj@NetBSD.ORG | |||||||
| Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
| Klaus Klein | kleink@NetBSD.ORG | |||||||
| John Kohl | jtk@NetBSD.ORG | |||||||
| Kevin Lahey | kml@NetBSD.ORG | |||||||
| Ted Lemon | mellon@NetBSD.ORG | |||||||
| Mike Long | mikel@NetBSD.ORG | |||||||
| Paul Mackerras | paulus@NetBSD.ORG | |||||||
| Neil J. McRae | neil@NetBSD.ORG | |||||||
| Perry Metzger | perry@NetBSD.ORG | |||||||
| Luke Mewburn | lukem@NetBSD.ORG | |||||||
| der Mouse | mouse@NetBSD.ORG | |||||||
| Tohru Nishimura | nisimura@NetBSD.ORG | |||||||
| Masaru Oki | oki@NetBSD.ORG | |||||||
| Greg Oster | oster@NetBSD.ORG | |||||||
| Herb Peyerl | hpeyerl@NetBSD.ORG | |||||||
| Matthias Pfaller | matthias@NetBSD.ORG | |||||||
| Dante Profeta | dante@NetBSD.ORG | |||||||
| Chris Provenzano | proven@NetBSD.ORG | |||||||
| Darren Reed | darrenr@NetBSD.ORG | |||||||
| Tim Rightnour | garbled@NetBSD.ORG | |||||||
| Heiko W. Rupp | hwr@NetBSD.ORG | |||||||
| SAITOH Masanobu | msaitoh@NetBSD.ORG | |||||||
| Kazuki Sakamoto | sakamoto@NetBSD.ORG | |||||||
| Curt Sampson | cjs@NetBSD.ORG | |||||||
| Wilfredo Sanchez | wsanchez@NetBSD.ORG | |||||||
| Ty Sarna | tsarna@NetBSD.ORG | |||||||
| Matthias Scheler | tron@NetBSD.ORG | |||||||
| Karl Schilke (rAT) | rat@NetBSD.ORG | |||||||
| Tim Shepard | shep@NetBSD.ORG | |||||||
| Chuck Silvers | chs@NetBSD.ORG | |||||||
| Thor Lancelot Simon | tls@NetBSD.ORG | |||||||
| Noriyuki Soda | soda@NetBSD.ORG | |||||||
| Wolfgang Solfrank | ws@NetBSD.ORG | |||||||
| Bill Sommerfeld | sommerfeld@NetBSD.ORG | |||||||
| Ignatios Souvatzis | is@NetBSD.ORG | |||||||
| Bill Studenmund | wrstuden@NetBSD.ORG | |||||||
| Kevin Sullivan | sullivan@NetBSD.ORG | |||||||
| Kimmo Suominen | kim@NetBSD.ORG | |||||||
| Matt Thomas | matt@NetBSD.ORG | |||||||
| Jason Thorpe | thorpej@NetBSD.ORG | |||||||
| Christoph Toshok | toshok@NetBSD.ORG | |||||||
| Todd Vierling | tv@NetBSD.ORG | |||||||
| Paul Vixie | vixie@NetBSD.ORG | |||||||
| Krister Walfridsson | kristerw@NetBSD.ORG | |||||||
| Nathan Williams | nathanw@NetBSD.ORG | |||||||
| Colin Wood | ender@NetBSD.ORG | |||||||
This product includes software developed by the University of
California, Berkeley and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Berkeley Software
Design, Inc.
This product includes software developed by Charles D. Cranor
and Washington University.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum,
by the University of Vermont and State Agricultural College
and Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley Laboratory,
and its contributors.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum.
This product includes software developed by Chris Provenzano.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Christopher G. Demetriou
for the NetBSD Project.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by David Jones and Gordon Ross.
This product includes software developed by Dean Huxley.
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Ezra Story.
This product includes software developed by Gordon Ross.
This product includes software developed by Gordon W. Ross
and Leo Weppelman.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Herb Peyerl.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ignatios Souvatzis
for the NetBSD Project.
This product includes software developed by Jason R. Thorpe
for And Communications, http://www.and.com/.
This product includes software developed by Joachim Koenig-Baltes.
This product includes software developed by Jochen Pohl
for The NetBSD Project.
This product includes software developed by John Polstra.
This product includes software developed by Jonathan Stone
and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone
for the NetBSD Project.
This product includes software developed by Jonathan Stone.
This product includes software developed by Julian Highfield.
This product includes software developed by Kenneth Stailey.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Markus Wild.
This product includes software developed by Martin Husemann
and Wolfgang Solfrank.
This product includes software developed by Mats O Jansson
and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Peter Galbavy.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Theo de Raadt
and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by the Center for
Software Science at the University of Utah.
This product includes software developed by the University of Calgary
Department of Computer Science and its contributors.
This product includes software developed by the University of Vermont
and State Agricultural College and Garrett A. Wollman.
This product includes software developed for the FreeBSD project.
This product includes software developed for the Internet
Software Consortium by Ted Lemon.
This product includes software developed for the NetBSD Project
by Frank van der Linden.
This product includes software developed for the NetBSD Project
by Jason R. Thorpe.
This product includes software developed for the NetBSD Project
by John M. Vinopal.
This product includes software developed for the NetBSD Project
by Matthias Drochner.
This product includes software developed for the NetBSD Project
by Matthieu Herrb.
This product includes software developed for the NetBSD Project
by Perry E. Metzger.
This product includes software developed for the NetBSD Project
by Piermont Information Systems Inc.
This product includes software developed for the NetBSD Project
by Ted Lemon.
This product includes software developed by LAN Media Corporation
and its contributors.
This product includes software developed by Michael Graff for
the NetBSD Project.
This product includes software developed by Gordon Ross
This product includes software developed by Leo Weppelman.
This product includes software developed by Markus Wild.
This product includes software developed by Thomas Gerner
This product includes software developed by Waldi Ravens.