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.
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 fifth ``real'' release of NetBSD for the 68k-based Macintosh.
For the mac68k port, NetBSD1.4.2 brings a number of improvements:
mac68k/adb(4)
driver has undergone a major revamp.
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/
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.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.
mac68k
subdirectory of the distribution:
.../NetBSD-1.4.2/mac68k/
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/mac68k/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.
It is the kernel that you need to boot the system.
If you experience SCSI-related difficulties with your 68030-based system, you
might want to try kern_sbc.tgz instead.
/usr/share.
groff(1),
all related programs, and their manual pages.
The mac68k security distribution set is named
secr and can be found in the
mac68k/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 mac68k 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
mac68k/binary/kernels
subdirectory of the
NetBSD1.4.2
distribution tree. These kernels are generally named something like
netbsd-GENERIC.gz
or some other suitable name. Please note that these kernels are simply
gzipped and are not in tar archives.
The MacOS-based utilities necessary for installing and running
NetBSD
can
be found in the
mac68k/installation/misc
subdirectory of the
NetBSD1.4.2
distribution tree. The important files in this directory are as
follows:
Booter.sea.hqxInstaller.sea.hqxMkfs.sea.hqx
These files are all binhexed, self-extracting archives. If you need them,
the sources for these utilities are in the
src subdirectory.
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/mac68k 1.4.2 runs on several of the older Macintosh computers. About 4MB of RAM might be sufficient to boot, and the system can probably be squeezed onto a 40MB hard disk by leaving off an unnecessary set or two. To actually do much compiling or anything more interesting than booting, at least 8MB of RAM and more disk space is recommended. About 95MB will be necessary to install all of the NetBSD1.4.2 binary system distribution sets (note that this does not count swap space!). An additional 30MB or so is needed for the binary X11 distribution sets. Much more disk space is required to install the source and objects as well (at least another 300MB).
If your 68030 system is not listed above, it may be because of a problem with accessing onboard video, and it may still work with a serial console. Some of the known ones in this category:
If your 68LC040 system is not listed above, it is due to a problem with floating point emulation (FPE) for this type of processor. Machines in this category include:
Known hardware issues with this release:
Installation is currently only supported from the local Macintosh hard drive, from a CD-ROM, or from an AppleShare volume (however, you may upgrade a system from within NetBSD ; see the section on upgrading for more details). If you are installing from a local hard drive, this means that you'll need at least enough room for the largest file that you will have to install. This is the 10.2M base.tgz file. There has been talk of allowing an install from split files. If you have the time, desire, and knowledge, please feel free to add that functionality.
If the install is being done from an AppleShare-mounted volume, the install utility must be in the same folder as the binary distribution sets.
Each distribution file is in raw archive format.
You will also need to collect the MacOS installation tools from the
mac68k/installation/misc subdirectory of the
NetBSD1.4.2
distribution:
Mkfs, NetBSD/Mac68k Installer, and NetBSD/Mac68k Booter. These three are
in binhexed, self-extracting archives as Mkfs.sea.hqx, Installer.sea.hqx,
and Booter.sea.hqx, respectively. Extract them as you would any other
Macintosh application.
Find your favorite disk partitioning utility. Any formatter capable of partitioning a SCSI disk should work. Some of the ones that have been tried and seem to work are:
Apple's HD SC Setup is probably the easiest to use and the most commonly available. Instructions for patching HD SC Setup so that it will recognize non-Apple drives is available at:
http://www.euronet.nl/users/ernstoud/patch.html
First, you need to choose a drive on which to install NetBSD. Try to pick a drive with a low SCSI ID number, especially if you are likely to add or remove drives to your SCSI chain in the future.
Second, decide how you want to set up your partitions. At minimum, you
need a partition to hold the
NetBSD
installation (the root partition) and a
partition to serve as swap. You may choose to use more than one partition
to hold the installation. This allows you to separate the more vital
portions of the filesystem (such as the kernel and the
/etc directory) from
the more volatile parts of the filesystem. Typical setups place the
/usr
directory on a separate partition from the root partition. Generally, the
root partition can be fairly small while the
/usr partition should be
fairly large. If you plan to use this machine as a server, you may also
want a separate
/var partition.
Once you have decided how to lay out your partitions, you need to calculate
how much space to allocate to each partition. A minimal install of
NetBSD
(i.e.
netbsd.tgz, base.tgz, and
etc.tgz)
should just fit in a 32M partition.
For a full installation, you should allocate at least 95M (150M if you
wish to install the X sets as well). A general rule of thumb for sizing
the swap partition is to allocate twice as much swap space as you have
real memory. Having your swap + real memory total at least 20M is also
a good idea. Systems that will be heavily used or that are low on real
memory should have more swap space allocated. Systems that will be only
lightly used or have a very large amount of real memory can get away
with less.
Keep in mind that NetBSD currently requires MacOS in order to boot, so it is likely that you will want to keep at least a minimal install of MacOS around on an HFS partition for this purpose. The size of this partition may vary depending on the size requirements for the version of MacOS you are using. Of course, if you have MacOS on another hard drive or can boot from a floppy, feel free to dedicate the entire drive to NetBSD.
Next, use your favorite partitioning utility to make partitions of the necessary sizes. You can use any type of partition, but partitions of type "Apple_Free" might save you some confusion in the future.
You are now set to install
NetBSD
on your hard drive.
The installation can be broken down into three basic steps:
When you have finished converting each partition, select each partition and click on the "Format" button. You will now be asked for a bunch of parameters for the hard drive and the filesystem. Usually, you can just take the defaults. If you are installing onto removable media (e.g. a Zip, Jaz, or Syquest), please see the FAQ. Note that although this dialog only has the "OK" button, you are not committed, yet. Once you get the values you want, press the "OK" button. A dialog will be presented at this point with two options: "Format" and "Cancel." If you choose "Cancel," nothing will be written to your drive. If you choose "Format," the program will proceed to make a filesystem.
Mkfs is not a well-behaved Macintosh application. It will not allow any other tasks to run while it does (cooperative multitasking at its best). When it's finished, the program will put up a dialog to ask if you have scanned the output for any error messages. Usually there won't have been any errors, but do scan the output to make sure. Simply click on the "I Read It" button and the program will quit.
Repeat as necessary for any extra partitions that you wish to make filesystems on. Note that you do _not_ need a filesystem on your swap partition.
When you are finished, click on the "Done" button and choose "Quit" from the "File" menu to exit Mkfs.
Double-click on the Installer icon to start it up. The Installer will present the same SCSI ID menu that Mkfs did. Select the same SCSI ID that you did for Mkfs--i.e., the one you are installing onto.
If you are installing onto a single root partition, proceed to the Installation of base files section, below.
sd1 at scsi ID 5.
mkdir path
/usr
partition type:
mkdir /usr)
mount device path
/usr, you would type:
mount /dev/sd0g /usr
/etc/fstab
file.
base.tgz, etc.tgz, netbsd.tgz,
and any other sets you wish to
install at this time. (See the contents section for information
about what's in each set.) The Installer will print out the
filename of each file as it is installed, and will take quite some
time to install everything (the base package alone can take over an
hour on a slow hard drive).
/etc/fstab.
The Installer program also has an
option to give you a mini-shell. Do not use this unless you are
sure know what you are doing.
It is probably best to boot your machine with all extensions turned
off[*]. You can do this by booting into MacOS with the
SHIFT key held
down. You may have to restart your Macintosh for changes to take effect
before proceeding.
Double-click on the NetBSD/mac68k Booter icon to start the application.
Select
Booting
from the
Options
menu. Check that all of the items in
the resulting dialog look sane--especially the SCSI ID. If not, correct
them to your preference (the SCSI ID should be the only thing you need to
change). When you are satisfied with your choices, try booting
NetBSD
by selecting
Boot Now from the
Options menu.
If you wish to save your preferences, choose
Save Options
from the
File
menu before Booting (your preferences will not be saved if you
forget to do this).
If the system does not come up, send mail to
port-mac68k@netbsd.org
describing your software, your hardware, and as complete a description of
the problem as you can.
If the system does come up, congratulations, you have successfully installed
NetBSD1.4.2.
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.
If you haven't done any configuration of
Other values that need to be set in
Other files in
After reboot, you can log in as
Use the
If you have installed the X window system, look at the files in
Don't forget to add
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
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.
No automated upgrade procedure exists for upgrading to release 1.4.2 for the
NetBSD/mac68k architecture. The current procedure is essentially to perform
a new install from scratch. It is hoped that there will be a good upgrade
procedure for future releases. Please feel free to volunteer to help
replace these installation tools.
The following steps outline the current upgrade procedure. These steps
should help ease the upgrade process. Please read these instructions
carefully and completely before proceeding.
Keep in mind that there is
no going back once you have installed the base set short of a complete
re-install of an earlier distribution. Continue with the appropriate
command line for each of the other sets you wish to install except for
the etc set. If you are in the Installer, open up the Minishell and do
the following:
If you are in NetBSD, do the following instead:
At this point you have successfully upgraded to
NetBSD1.4.2.
Documentation is available if you first install the manual
distribution set. Traditionally, the
``man pages''
(documentation) are denoted by
``
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
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
Use of
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.
for their ongoing work on BSD systems, support, and encouragement.
for answering lots of questions, fixing bugs, and doing the various work
they've done.
(in alphabetical order)
http://www.netbsd.org/Ports/mac68k/faq/the FAQ
for more information.
Post installation steps
/etc/rc.conf
/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.
/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.
/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.
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.
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.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
/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
man filename
is likely to give you more information on these files.
Upgrading a previously-installed NetBSD System
mac68k/binary/sets
subdirectory of the
NetBSD1.4.2
distribution. You will need the base
set and the kernel at a minimum. Be sure to download the files in
binary
mode. If you will be upgrading from within NetBSD, make sure
that you place the distribution sets on a filesystem you will be able to
reach from single-user mode.
installation/misc
subdirectory) or install from within
NetBSD
(the latter is recommended for speed reasons). If you
choose the former, proceed as you normally would. If you choose to
install from within NetBSD, then boot (or shutdown) into single-user
mode and do the following:
There is no need to backup your old kernel explicitly since it will be
incapable of running many of the newer binaries you are about to
install. (Unless, of course, you have a backup copy of your older
binaries and want to revert to them for some reason.) However, you
might want to keep a backup if you are upgrading from within
NetBSD
just in case the newer kernel has trouble booting your machine.
cd /
pax -zrvpe -f /path/to/kern.tgz
/etc/fstab
file to reflect the new partition layout. Unless you are
familiar with
ex(1)
or
ed(1).
the easiest way to fix your
/etc/fstab
file
is probably to simply do a
cat > /etc/fstab
and type in the corrected file in its entirety.
cd /
pax -zrvpe -f /path/to/base.tgz
Ignore the warning message this will cause. Now, use the Installer to
install the
etc set (it will install into
cd /tmp
exit
/tmp instead of the
/etc directory).
cd /tmp
pax -zrvpe -f /path/to/etc.tgz
/tmp/etc
directory and compare each file
there with your old files in
/etc.
You will probably want to replace
some of your system configuration files, or incorporate some of the
changes in the new versions into yours. You should take note of the
following when upgrading to the
NetBSD1.4.2
etc.tgz set:
/etc/fstab to
ffs.
To find out
more about different filesystem options, read the man page for the
associated mount command (e.g.
mount_mfs(8)
for MFS filesystems; note:
FFS type filesystems are documented in the
mount(8)
man page). If you
have not already done so, you may also need to correct
/etc/fstab
for a shift in the partition numbering scheme. See step 4 above for more
details.
cd /dev
sh MAKEDEV all
Compatibility Issues With Previous NetBSD Releases
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.4.2
/usr/include/machine
directory changed to a symbolic link in NetBSD 1.4.
# rm -r /usr/include/machine
to remove the old directory and it contents and reinstall the
comp
set.
Using online NetBSD documentation
name(section)''.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5)m
enter
man 5 passwd
instead.
Administrivia
If you've got something to say, do so! We'd like your input.
There are various mailing lists available via the mailing list
server at
majordomo@NetBSD.ORG.
To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.
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.
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.
Thanks go to
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
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
(If you're not on that list and should be, tell us! We probably were
not able to get in touch with you, to verify that you wanted to be
listed.)
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.
We are...
| 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 the Alice Group.
This product includes software developed by Allen Briggs.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Bradley A. Grantham.
This product includes software developed by Takashi Hamada.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Scott Reynolds.
This product includes software developed by John P. Wittkoski.
This product includes software developed by Colin Wood.
The following people have made contributions of various sorts specifically for the Macintosh port (in alphabetical order):