INSTALL.
ext,
where
ext
is one of
.ps
, .html
, .more
,
or
.txt
.
.ps
.html
.more
more(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txt
You 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.
NetBSD 1.4.2 is an upgrade of NetBSD 1.4.1, NetBSD 1.4 and earlier releases of NetBSD such as versions 1.3.3, 1.2 etc.
The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.4 was started are designated by version identifiers such as 1.4A, 1.4B, 1.4P etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.4.2 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD1.4.2 kernel on such a system will in all probability result in problems.
Please also note that it is not possible to do a direct ``version'' comparison between any of the intermediate development versions mentioned above and 1.4.2 to determine if a given feature is present or absent in 1.4.2. The development of 1.4, 1.4.1 and 1.4.2 is done on a separate branch in the CVS repository which was created when the release cylcle for 1.4 was started, and during the release cycles for all these versions selective fixes (with minor impact on the stability of the code on the release branch) have been imported from the main development trunk. So, there are features in 1.4.2 which were not in e.g. 1.4H, but the reverse is also true.
ti(4)
.
rl(4)
.
dpt(4)
.
ioat(4)
.
mktemp(1)
.
amd(8)
has been updated to fix a security problem.
In addition, many, many bugs have been fixed -- more than 100 problems reported through our problem tracking system have been fixed, and many other non-reported problems have also been found and fixed. See the CHANGES-1.4.2 file for the complete list.
ipf(8)
caused a change of the kernel API. Thus, if you are using
ipf(8)
you need to upgrade both the kernel and the user-land utilities to
control that feature in order for it to work.
It is impossible to completely summarize the nearly two years of development that went into the NetBSD1.4 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.
NetBSD1.4.2 is the third public major release of NetBSD for the x68k platform.
In addition to above port-independent improvements, many device drivers are reorganized, and some of them now utilize the machine-independent backend.
Also the boot program is improved to load the kernel from any hard drives.
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, Anonymous CVS access to the NetBSD source tree has been added since NetBSD 1.4.1; see http://www.netbsd.org/Changes/#anoncvs-available We have also added a browsable CVS repository on the web at http://cvsweb.netbsd.org/cgi-bin/cvsweb.cgi/
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.
.../NetBSD-1.4.2/
BUGS
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
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.2 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 NetBSD project maintains a web page at
http://www.NetBSD.ORG/Misc/crypto-export.html
which should contain up-to-date information on this issue.
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 may only be
available 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. Again, see
http://www.NetBSD.ORG/Misc/crypto-export.html
for updated information on this issue.)
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.
x68k
subdirectory of the distribution:
.../NetBSD-1.4.2/x68k/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
sets/
security/
installation/
floppy/
misc/
x68k/binary/sets
subdirectory
of the
NetBSD1.4.2
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.)
/netbsd
.
You must
install this distribution set.
/usr/share
.
groff(1)
,
all related programs, and their manual pages.
The x68k security distribution set is named
secr and can be found in the
x68k/binary/security
subdirectory of the
NetBSD1.4.2
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. See
http://www.NetBSD.ORG/Misc/crypto-export.html
for updated information on this issue.
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.6. Binary sets for the X Window system are distributed with NetBSD. The sets are:
The x68k 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 /.
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/x68k 1.4.2 runs on the Sharp X68030 series PCs with a true MC68030 MPU (not the original MC68EC030). Since the processor of the X68030 series is the MC68EC030, you need to replace it with an MC68030. Simply remove the old chip and put in the new one instead. The largest difficulty might be to open your X68030.
In addition, some accelerators are supported:
This means all models of X680x0 series PC except for CZ-600C and CZ-674C, by using the appropriate accelerator, can run NetBSD!! Note that the processor for the Xellent30 series is MC68EC030, so you need to replace your processor as well as for X68030.
For 68030 systems, installing MC68881 or MC68882 FPCP is highly recommended but not required.
The minimal configuration requires 4M of RAM and about 100M 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.
Here is a table of recommended HD partition sizes for a full install:
Partition | Advised | With X | Needed | With X |
root (/) | 25M | 25M | 20M | 20M |
user (/usr) | 150M | 200M | 100M | 125M |
swap | 2*RAM... | |||
local (/local) | up to you... |
As you may note the recommended size of /usr is 70M 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. (ALL is large and bulky to accommodate all people).
Supported devices include:
Hopefully, the AD-PCM sound device will be supported on the future releases.
Installation is supported from several media types, including:
You'll need to have a install floppy disk. On the first, you'll put the install floppy image.
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 (.fs files) directly to the raw
floppy disks. It is suggested that you read the dd(1) manual page or
ask your system administrator to determine the correct set of
arguments to use; it will be slightly different from system to system,
and a comprehensive list of the possibilities is beyond the scope of
this document.
If you are using Human68k to write the floppy images to disks, you
should use the
rawrite
utility, provided in the
installation/misc
directory of the NetBSD distribution. It will write the file system
images (.fs files) to disks.
If you can retrieve
loadbsd.x
utility and
netbsd.INSTALL
file which can be found in
installation/misc
directory into your Human68k disk, you can run installation kernel
without preparing the special boot floppy. Simply type:
loadbsd netbsd.INSTALL
from the Human68k command line, then
NetBSD
will start the installation sequence.
Obviously, the steps necessary to prepare the distribution sets for installation or upgrade depend on which installation medium you choose. The steps for the various media are outlined below.
To install NetBSD from a removable device
the media
must
be of the IBM
Super-floppy
format. The Human68k format is not recognized
by this release of the NetBSD/x68k. If you have a MS-DOS (or
MS-Windows) machine with an MO drive connected, use it. If
you don't, and if you have a program to handle IBM format MO
for Human68k, copy all the files in the subdirectory
x68k/binaries
and CHANGE THEIR NAMES IN UPPER CASE.
To install or upgrade NetBSD using a tape, you need to do the following:
To install NetBSD from a tape, you need to make a tape that
contains the distribution set files, in "tar" format. If
you're making the tape on a UN*X-like system, the easiest way
to do so is probably something like:
tar cf tape_device dist_directories
where
tape_device
is the name of the tape device that
describes the tape drive you're using (possibly /dev/rst0, or
something similar, but it will vary from system to system.
(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
base and etc
distributions on tape (in order to do the absolute
minimum installation to a new disk), you would do the
following:
cd .../NetBSD-1.4.2 # the top of the tree
cd x68k/binary/sets
tar cf tape_device base.tgz etc.tgz
(Note that you still need to fill in
tape_device
in the example.)
Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
To install or upgrade NetBSD using a remote partition, mounted via NFS, you must do the following:
Place the NetBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the /etc/exports file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.)
You need to know the the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
To install or upgrade NetBSD by using FTP to get the installation sets, you must do the following:
The preparations for this installation/upgrade method are easy; all you make sure that there's some FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. You need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
If you are upgrading NetBSD, you also have the option of installing NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following:
What you have to do to prepare the disk is only to physically format
your hard disk by using FORMAT.x utility of Human68k to install the
master boot program on your disk. You can now proceed with the
installation instructions.
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 should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The NetBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.)
You should now be ready to install NetBSD. It might be handy for you to have a pencil, some paper, and a calculator handy.
The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch.
It will take a while to load the kernel from the floppy, probably around a minute or so.
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under
/mnt
;
you should
probably pick a directory under
/mnt/usr
.)
The
default is /mnt/usr/distrib.
Insert the media onto the drive. Check the device name of your drive from the boot message. The device name is something like "sd2" depending on the SCSI disk drives connected to your machine. Note that the boot message can be displayed with the command more /kern/msgbuf.
Mount the disk on the temporary directory with a
command like:
mount -t msdos /dev/sd2c tmp_dir
if your removable drive's name is sd2.
Run the
Extract
command once for each distribution
set you wish to install. For instance, if you wish to
install the
base
distribution set, followed by the
kern
distribution set, and finally the
etc
distribution set, use the commands:
Extract base
Extract kern
Extract etc
For each extraction, it will ask you if the extraction should be verbose. If you reply affirmatively, it will print out the name of each file that's being extracted.
The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command Set_tmp_dir, and enter the name of the temporary directory. (Don't forget that if your disk is still mounted under /mnt; you should probably pick a directory under /mnt/usr.)
After you have picked a temporary directory, enter the Load_fd command, to load the distribution sets from your floppies.
You will be asked which floppy drive to use. Enter "0" (zero) if you're using the first floppy drive (i.e. what DOS would call "A:"), or enter "1" if you're using the second.
You will be prompted to insert a floppy into the drive, to have its contents copied to your hard disk. Do so, and hit return to begin copying. When that is done, read the remainder of the floppies that contain the distribution sets that you want to install, one by one. When the last is read, and you are being prompted for another, hit Control-C.
Run the "Extract" command once for each distribution
set you wish to install. For instance, if you wish to
install the "base" distribution set, followed by the
"kern" distribution set, and finally the "etc"
distribution set, use the commands:
Extract base
Extract kern
Extract etc
For each extraction, it will ask you if the extraction should be verbose. If you reply affirmatively, it will print out the name of each file that's being extracted.
Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system.
The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the command "Set_tmp_dir", and enter the name of the temporary directory. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib.
After you have picked a temporary directory, enter the "Load_tape" command, to load the distribution sets from tape.
You will be asked which tape drive to use. The default is "rst0", which is correct if you're using the SCSI tape drive with the lowest SCSI ID number. (For the SCSI tape drive with the next lowest SCSI ID number, you should use "rst1", and so on.)
You will be prompted to hit return when you have inserted the tape into the tape drive. When you do, the contents of the tape will be extracted into the temporary directory, and the names of the files being extracted will be printed.
After the tape has been extracted, to go the directory containing the first distribution set you wish to install. (Depending on how you made the tape, it's probably a subdirectory of the temporary directory you specified above.) Once there, run the "Set_tmp_dir" command again, and accept its default answer by hitting return at the prompt.
Use the Extract command to extract the distribution set. For instance, if you're extracting the "base" set, use the command: Extract base 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.
Repeat the previous two steps for each distribution set you wish to install. Change to the set's directory, run "Set_tmp_dir", and then run Extract set_name to extract the set.
Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system.
The first thing you should do is pick a temporary
directory where the distribution files can be stored.
To do this, enter the command "Set_tmp_dir", and enter
the name of the temporary directory. (Don't forget
that your disk is mounted under
/mnt
;
you should
probably pick a directory under
/mnt/usr
.)
The default is
/mnt/usr/distrib
.
Configure the network interface. To use SLIP, type the following
command sequence:
slattach -h -s speed tty00
ifconfig sl0 my_ipaddr peer_ipaddr
where
speed
is the network speed, and
my_ipaddr
is the numeric IP address of the machine you are going
to install NetBSD/x68k, while
peer_ipaddr
is the
address of the peer machine connected with your machine.
You might have to configure the peer SLIP interface
with similar sequence (depending on the peer system).
For instance, the sequence
slattach -h -s 38400 tty00
ifconfig sl0 192.168.0.1 192.168.0.10
configures the SLIP interface for the network between
your machine (with IP address 192.168.0.1) and the peer
(192.168.0.10) with speed 38400 bps. Note that IP
addresses 192.168.*.* are the private IP addresses
described in RFC 1597.
To use ethernet, do following:
ifconfig ne0 my_ipaddr
where
my_ipaddr
is the numeric IP address of the machine you are going
to install NetBSD/x68k. ne0 is the interface name which correspond to
the Neptune-X or clone.
If you are NFS-mounting the distribution sets, mount
them on the temporary directory with a command like:
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, changing to the appropriate directories, running Set_tmp_dir and running Extract as appropriate.
If you are retrieving the distribution sets using ftp,
change into the temporary 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 when transferring the files.
Once you have all of the files for the distribution sets that you wish to install, you can proceed using the instructions above, as if you had installed from a floppy.
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 "base" and "etc" 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, run the command "Configure". It will ask you for the system's host name, domain name, and other network configuration information. It will set up your configuration files and make the device nodes for the newly-installed system.
Congratulations, you have successfully installed NetBSD1.4.2. 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
NetBSD1.4.2
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
including
/etc/rc.conf
will probably need to be modified, as well. If
you are unfamiliar with UN*X-like system administration, it's
recommended that you buy a book that discusses it.
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
README
file there for more information.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
The upgrade to NetBSD1.4.2 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily to interdependencies in the various components.
To do the upgrade, you must have the bootable install floppy
boot.fs
,
or,
loadbsd.x
utility and
netbsd.INSTALL
file which can be found in
installation/misc
in your Human68k disk.
You must also have at least the
base and kern
binary distribution sets available, so that you can upgrade with it,
using one of the upgrade methods described below. 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 boot blocks on your NetBSD partition, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on your disk, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process.
To upgrade your system, follow the following instructions:
loadbsd.x
utility.
Once the distribution sets are transferred to your disk, continue here. (Obviously, if the NetBSD distribution sets are already on your disk, because you've transferred them before starting the upgrade process, you don't need to transfer them again now!)
Your system has now been upgraded to NetBSD1.4.2.
After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.4.2 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, 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 etc 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 in the new versions into yours.
Third, you will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this, but if not, you can just cd into /dev, and run the command "sh MAKEDEV all".
Fourth, you must deal with certain changes in the formats of
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.
*IMPORTANT*: ANY INSTANCES OF "ufs"
IN /etc/fstab MUST BE CHANGED TO "ffs".
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.
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. 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
therefore take advantage of the shared libraries, by default.
For information on how to make statically linked binaries,
see the cc(1) and ld(1) manual pages.)
/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.
Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe 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 Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Soren Jorvang Scott Kaplan Noah M. Keiserman John Kohl Chris Legrow Ted Lemon Neil J. McRae Perry E. Metzger Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise Christos Zoulas
AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology 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 Warped Communications, Inc.
(in alphabetical order)
The NetBSD core group: | ||||||||
Alistair Crooks | agc@NetBSD.ORG | |||||||
Jun-ichiro itojun Hagino | itojun@NetBSD.ORG | |||||||
Frank van der Linden | fvdl@NetBSD.ORG | |||||||
Luke Mewburn | lukem@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 | ||||||
Jun-ichiro itojun Hagino | itojun@NetBSD.ORG | sh3 | ||||||
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 | ||||||
Kazuki Sakamoto | sakamoto@NetBSD.ORG | bebox | ||||||
Wolfgang Solfrank | ws@NetBSD.ORG | ofppc | ||||||
Jonathan Stone | jonathan@NetBSD.ORG | pmax | ||||||
Shin Takemura | takemura@NetBSD.ORG | hpcmips | ||||||
Jason Thorpe | thorpej@NetBSD.ORG | hp300 | ||||||
Frank van der Linden | fvdl@NetBSD.ORG | i386 | ||||||
Leo Weppelman | leo@NetBSD.ORG | atari | ||||||
Nathan Williams | nathanw@NetBSD.ORG | sun3 | ||||||
Steve Woodford | scw@NetBSD.ORG | mvme68k | ||||||
| ||||||||
The NetBSD 1.4.2 Release Engineering team: | ||||||||
Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
Havard Eidnes | he@NetBSD.ORG | |||||||
Ted Lemon | mellon@NetBSD.ORG | |||||||
Perry Metzger | perry@NetBSD.ORG | |||||||
Curt Sampson | cjs@NetBSD.ORG | |||||||
| ||||||||
Developers and other contributors: | ||||||||
Steve Allen | wormey@NetBSD.ORG | |||||||
Julian Assange | proff@NetBSD.ORG | |||||||
Lennart Augustsson | augustss@NetBSD.ORG | |||||||
Christoph Badura | bad@NetBSD.ORG | |||||||
Robert V. Baron | rvb@NetBSD.ORG | |||||||
Erik Berls | cyber@NetBSD.ORG | |||||||
John Birrell | jb@NetBSD.ORG | |||||||
Mason Loring Bliss | mason@NetBSD.ORG | |||||||
Manuel Bouyer | bouyer@NetBSD.ORG | |||||||
John Brezak | brezak@NetBSD.ORG | |||||||
Allen Briggs | briggs@NetBSD.ORG | |||||||
Aaron Brown | abrown@NetBSD.ORG | |||||||
David Brownlee | abs@NetBSD.ORG | |||||||
Frederick Bruckman | fredb@NetBSD.ORG | |||||||
Jon Buller | jonb@NetBSD.ORG | |||||||
Simon Burge | simonb@NetBSD.ORG | |||||||
Dave Burgess | burgess@cynjut.infonet.net | |||||||
Robert Byrnes | byrnes@NetBSD.org | |||||||
D'Arcy J.M. Cain | darcy@NetBSD.ORG | |||||||
Dave Carrel | carrel@NetBSD.ORG | |||||||
Bill Coldwell | billc@NetBSD.ORG | |||||||
Julian Coleman | jdc@NetBSD.ORG | |||||||
Chuck Cranor | chuck@NetBSD.ORG | |||||||
Aidan Cully | aidan@NetBSD.ORG | |||||||
Johan Danielsson | joda@NetBSD.ORG | |||||||
Matt DeBergalis | deberg@NetBSD.ORG | |||||||
Rob Deker | deker@NetBSD.ORG | |||||||
Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
Jaromir Dolecek | jdolecek@NetBSD.ORG | |||||||
Andy Doran | ad@NetBSD.ORG | |||||||
Roland Dowdeswell | elric@NetBSD.ORG | |||||||
Matthias Drochner | drochner@NetBSD.ORG | |||||||
Jun Ebihara | jun@NetBSD.ORG | |||||||
Havard Eidnes | he@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 | |||||||
Castor Fu | castor@NetBSD.ORG | |||||||
Brian R. Gaeke | brg@dgate.org | |||||||
Thomas Gerner | thomas@NetBSD.ORG | |||||||
Simon J. Gerraty | sjg@NetBSD.ORG | |||||||
Justin Gibbs | gibbs@NetBSD.ORG | |||||||
Adam Glass | glass@NetBSD.ORG | |||||||
Michael Graff | explorer@NetBSD.ORG | |||||||
Brian C. Grayson | bgrayson@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 | |||||||
HAYAKAWA Koichi | haya@NetBSD.ORG | |||||||
Rene Hexel | rh@NetBSD.ORG | |||||||
Michael L. Hitch | mhitch@NetBSD.ORG | |||||||
Christian E. Hopps | chopps@NetBSD.ORG | |||||||
Ken Hornstein | kenh@NetBSD.ORG | |||||||
Marc Horowitz | marc@NetBSD.ORG | |||||||
Dean Huxley | dean@netbsd.org | |||||||
ITOH Yasufumi | itohy@NetBSD.ORG | |||||||
Matthew Jacob | mjacob@NetBSD.ORG | |||||||
Lonhyn T. Jasinskyj | lonhyn@NetBSD.ORG | |||||||
Chris Jones | cjones@NetBSD.ORG | |||||||
Soren Jorvang | soren@NetBSD.ORG | |||||||
Antti Kantee | pooka@NetBSD.ORG | |||||||
Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
Thomas Klausner | wiz@NetBSD.ORG | |||||||
Klaus Klein | kleink@NetBSD.ORG | |||||||
John Kohl | jtk@NetBSD.ORG | |||||||
Kevin Lahey | kml@NetBSD.ORG | |||||||
Johnny C. Lam | jlam@NetBSD.ORG | |||||||
Martin J. Laubach | mjl@NetBSD.ORG | |||||||
Ted Lemon | mellon@NetBSD.ORG | |||||||
Joel Lindholm | joel@NetBSD.ORG | |||||||
Mike Long | mikel@NetBSD.ORG | |||||||
Warner Losh | imp@NetBSD.ORG | |||||||
Brett Lymn | blymn@NetBSD.ORG | |||||||
Paul Mackerras | paulus@NetBSD.ORG | |||||||
Dan McMahill | dmcmahill@NetBSD.ORG | |||||||
Neil J. McRae | neil@NetBSD.ORG | |||||||
Perry Metzger | perry@NetBSD.ORG | |||||||
der Mouse | mouse@NetBSD.ORG | |||||||
Joseph Myers | jsm@NetBSD.ORG | |||||||
Ken Nakata | kenn@NetBSD.ORG | |||||||
Bob Nestor | rnestor@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 | |||||||
Waldi Ravens | waldi@moacs.indiv.nl.net | |||||||
Darren Reed | darrenr@NetBSD.ORG | |||||||
Michael Richardson | mcr@NetBSD.ORG | |||||||
Tim Rightnour | garbled@NetBSD.ORG | |||||||
Gordon Ross | gwr@NetBSD.ORG | |||||||
Heiko W. Rupp | hwr@NetBSD.ORG | |||||||
SAITOH Masanobu | msaitoh@NetBSD.ORG | |||||||
Curt Sampson | cjs@NetBSD.ORG | |||||||
Wilfredo Sanchez | wsanchez@NetBSD.ORG | |||||||
Ty Sarna | tsarna@NetBSD.ORG | |||||||
SATO Kazumi | sato@NetBSD.ORG | |||||||
Matthias Scheler | tron@NetBSD.ORG | |||||||
Karl Schilke (rAT) | rat@NetBSD.ORG | |||||||
Konrad Schroder | perseant@NetBSD.ORG | |||||||
Tim Shepard | shep@NetBSD.ORG | |||||||
Takao Shinohara | shin@NetBSD.ORG | |||||||
Chuck Silvers | chs@NetBSD.ORG | |||||||
Thor Lancelot Simon | tls@NetBSD.ORG | |||||||
Noriyuki Soda | soda@NetBSD.ORG | |||||||
Bill Sommerfeld | sommerfeld@NetBSD.ORG | |||||||
Bill Studenmund | wrstuden@NetBSD.ORG | |||||||
Kevin Sullivan | sullivan@NetBSD.ORG | |||||||
Kimmo Suominen | kim@NetBSD.ORG | |||||||
Matt Thomas | matt@NetBSD.ORG | |||||||
Christoph Toshok | toshok@NetBSD.ORG | |||||||
Izumi Tsutsui | tsutsui@NetBSD.ORG | |||||||
UCHIYAMA Yasushi | uch@NetBSD.ORG | |||||||
Todd Vierling | tv@NetBSD.ORG | |||||||
Aymeric Vincent | aymeric@NetBSD.ORG | |||||||
Paul Vixie | vixie@NetBSD.ORG | |||||||
Krister Walfridsson | kristerw@NetBSD.ORG | |||||||
Lex Wennmacher | wennmach@NetBSD.ORG | |||||||
Assar Westerlund | assar@NetBSD.ORG | |||||||
Rob Windsor | windsor@NetBSD.ORG | |||||||
Dan Winship | danw@NetBSD.ORG | |||||||
Jim Wise | jwise@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 Niklas Hallqvist,
C Stone and Job de Haas.
This product includes software developed by Masaru Oki.
This product includes software developed by Masanobu Saitoh.
This product includes software developed by Takumi Nakamura.
This product includes software developed by Kazuhisa Shimizu.
This product includes software developed by Takuya HARAKAWA.
This product includes software developed by MINOURA Makoto.
This product includes software developed by Yasushi YAMASAKI.
This product includes software developed by ITOH Yasufumi.