About this Document............................................2
What is NetBSD?................................................2
Security Advisory Fixes.....................................3
Other Security Fixes........................................4
Kernel......................................................4
File Systems................................................4
Networking..................................................4
Miscellaneous Drivers.......................................5
Audio.......................................................5
Storage.....................................................5
Platform specific...........................................5
Miscellaneous...............................................6
Features to be removed in a later release......................7
The NetBSD Foundation..........................................7
Sources of NetBSD..............................................7
NetBSD 5.2 Release Contents....................................7
NetBSD/mac68k subdirectory structure........................8
Binary distribution sets....................................9
NetBSD/mac68k System Requirements and Supported Devices.......11
Supported models...........................................11
Supported devices..........................................11
Unsupported models.........................................12
Known hardware issues with this release....................12
Getting the NetBSD System on to Useful Media..................12
Preparing your System for NetBSD installation.................13
Installing the NetBSD System (Sysinst Method).................15
Running the sysinst installation program...................15
Introduction............................................15
Possible hardware-specific issues.......................15
General.................................................15
Quick install...........................................16
Booting NetBSD..........................................17
Preparing your hard disk................................18
Getting the distribution sets...........................18
Installation from CD-ROM................................19
Installation using ftp..................................19
Installation using NFS..................................19
Installation from Mac OS file systems...................19
Installation from an unmounted file system..............19
Installation from a local directory.....................20
Extracting the distribution sets........................20
Finalizing your installation............................20
Installing the NetBSD System (Traditional Method).............20
Preparing the file system(s)...............................20
Installing the files.......................................21
Installation of base files.................................22
Booting the system.........................................22
Post installation steps.......................................23
Upgrading a previously-installed NetBSD System................26
Compatibility Issues With Previous NetBSD Releases............26
Issues when running older binaries on NetBSD 5.2...........27
Issues affecting an upgrade from NetBSD 3.x releases.......27
Issues affecting an upgrade from NetBSD 4.x releases.......28
Using online NetBSD documentation.............................29
Administrivia.................................................29
Thanks go to..................................................30
We are........................................................30
Legal Mumbo-Jumbo.............................................37
The End.......................................................43
This document describes the installation procedure for
NetBSD
5.2 on the
mac68k
platform.
It is available in four different formats titled
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.
The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on 57 different system architectures (ports) across 15 distinct CPU families, and is being ported to more. The NetBSD 5.2 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distribution. Please see the NetBSD web site at http://www.NetBSD.org/ for information on them.)
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, firewall software 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.
The complete list of changes can be found in the CHANGES-5.2: http://ftp.NetBSD.org/pub/NetBSD/NetBSD-5.2/CHANGES-5.2 file in the top level directory of the NetBSD 5.2 release tree. An abbreviated list is as follows:
Advisories prior to NetBSD-SA2010-012 do not affect NetBSD 5.2: http://www.NetBSD.org/support/security/patches-5.2.html.
dhcpcd(8):
Fix CVE-2011-996.
bpf(4):
avoid stack memory disclosure.
ptrace(2)
PT_SYSCALL.
fss(4):
various fixes for snapshots.
wm(4):
add support for more chips, work around some other issues.
bge(4):
add support for many more chips, and many bugfixes.
ne(4):
add NE2000 with 8bit bus width support, and EtherNEC support.
btmagic(4):
add Apple Magic Mouse driver.
rnd(4):
prevent crash if len field in ioctl(RNDADDDATA) is garbage.
uts(4):
driver for USB touchscreens.
hdaudio(4):
esiop(4)
/
siop(4):
Improve error paths. PR#43278.
aac(4):
support more boards.
dk(4):
avoid a LOCKDEBUG panic on
raid(4).
ciss(4):
Fix a performance problem. Also fix a DIAGNOSTIC panic.
raid(4):
mpt(4):
Add byte-swapping so this works on bigendian platforms. Allow
mpt(4)
to use tagged queueing on SAS adapters.
vnd(4):
fix using sparse files as backing store.
raid(4):
parity maps always have at least one parity region.
binpatch(8).
cd(4)
devices properly.
mmap(2),
mremap(2),
shmat(2)
or
sbrk(2)
return -1 in case of an error. A side benefit of this is to fix a segfault caused by jemalloc when
mmap(2)
failed.
ksyms(4)
actually work.
passwd(1):
Log successful and unsuccessful attempts to change passwords, via -l or PAM.
ftp(1):
top(1):
improve the default display for large numbers of CPUs.
nfsd(8)
from exiting prematurely during port-scan.
resize_ffs(8):
support growing and shrinking all FFSv1 and growing all FFSv2 file systems.
mount(8))
will be removed in the next major release.
NetBSD
5.2
includes a preview of WAPBL
(Write Ahead Physical Block Logging),
which will replace soft dependencies in the next major release.
See
wapbl(4)
and
http://mail-index.netbsd.org/netbsd-announce/2008/12/14/msg000051.html
for details.
It should be considered as deprecated. Users are expected to not rely on it any more beyond this major release.
Further, at least version 3.1 of Xen will be required to run NetBSD as Dom0 or DomU.
The
NetBSD
Foundation is a tax exempt, not-for-profit 501(c)(3) corporation
that devotes itself to the traditional goals and Spirit of the
NetBSD
Project and owns the trademark of the word
``NetBSD''.
It supports the design, development, and adoption of
NetBSD
worldwide.
More information on the
NetBSD
Foundation, its composition, aims, and work can be found at:
http://www.NetBSD.org/foundation/
Refer to
http://www.NetBSD.org/mirrors/
The root directory of the NetBSD 5.2 release is organized as follows:
.../NetBSD-5.2/
CHANGESCHANGES-5.0CHANGES-5.1CHANGES-5.2CHANGES.prevLAST_MINUTEREADME.filessource/In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 5.2 has a binary distribution.
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:
config(1)
utility.
All the above source sets are located in the
source/sets
subdirectory of the distribution tree.
The source sets are distributed as compressed tar files.
Except for the
pkgsrc
set, which is traditionally unpacked into
/usr/pkgsrc,
all sets may be unpacked into
/usr/src
with the command:
# cd / ; tar -zxpf set_name.tgz
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
MD5SHA512The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files.
mac68k
subdirectory of the distribution:
.../NetBSD-5.2/mac68k/.
It contains the following files and directories:
INSTALL.htmlINSTALL.psINSTALL.txtINSTALL.more.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/kernel/netbsd-GENERIC.gznetbsd-GENERICSBC.gzsets/installation/instkernel/misc/mac68k/binary/sets
subdirectory
of the
NetBSD
5.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.
GENERIC
kernel, named
/netbsd.
You
must
install either this distribution set or kern-GENERICSBC.
GENERICSBC
kernel, named
/netbsd.
You
must
install either this distribution set or kern-GENERIC.
/usr/share.
groff(1),
all related programs, and their manual pages.
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 4.5.0. 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 filenames stored in the sets are relative and therefore
the files are extracted
below the current directory.
Therefore, if you want to extract the binaries into your system, i.e.
replace the system binaries with them, you have to run the
tar -xzpf
command from the root directory (
/
) of your system.
Kernels suitable for booting from an AppleShare server may be found
in the
mac68k/binary/kernels
subdirectory of the
NetBSD
5.2 distribution tree.
These kernels are generally named something like
netbsd-GENERIC.gz
and can be booted as-is by the
NetBSD/mac68k
Booter utility, if desired.
Please note that these kernels are simply gzipped and are not in tar archives.
The
Mac OS
based utilities necessary for installing and running
NetBSD
can
be found in the
mac68k/installation/misc
subdirectory of the
NetBSD
5.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.
NetBSD/mac68k 5.2 runs on several of the older Macintosh computers. About 4 MB of RAM is sufficient to boot a stripped-down custom kernel, and a subset of the system can be squeezed onto a 40 MB hard disk with considerable creativity and persistence. However, 100 MB of disk should be considered a practical minimum, and to do anything more interesting than booting at least 8 MB of RAM and more disk space is recommended.
Please note that to install NetBSD/mac68k 5.2 using the sysinst method, your system must have a minimum of 6 MB of RAM and 60 MB of available disk space (i.e. not part of an in-use HFS partition).
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:
This machine has unusual custom chips for the ADB and serial interfaces which make support for it difficult. Work is in progress on this, though.
These machines have I/O processor chips for their ADB interfaces similar to those used in the IIfx and thus face similar support problems. Note that you can use a serial console on these systems.
This is a separate effort from the mac68k port. PowerMacs use hardware that is quite different from that of the mac68k port. See the NetBSD/macppc port webpage at http://www.NetBSD.org/ports/macppc/ for more information.
Due to oddities of the Macintosh hardware interrupt priority scheme, NetBSD/mac68k keeps very poor time. Under a high interrupt load (e.g. SCSI or serial port activity), a machine can lose several minutes per hour. A consequence of this problem is that attempting to run ntpd is generally rather pointless.
The NetBSD/mac68k SCSI drivers are not quite as robust as their Mac OS counterparts. Symptoms of these problems are that some SCSI disks will not work under NetBSD that work fine under Mac OS. Other problems include occasional file system corruption with some types of drives and the general unreliability of removable SCSI media. Keep in mind that there are no clear patterns with these problems, and they do not appear to affect the majority of users.
There are currently two installation methods available for initial installation of NetBSD on Apple Macintosh 68000-based systems. Neither supports all installation media types at this time, so the one you select must be compatible with the media you have available on your system.
The Traditional method of installation is currently 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 Upgrading a previously-installed NetBSD System section 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.
If the install is being done from an AppleShare-mounted volume, the NetBSD/mac68k Installer 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
Mac OS
installation tools from the
mac68k/installation/misc subdirectory of the
NetBSD5.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.
No matter which installation method you use, there is some planning and preparation that is required beforehand. First and foremost, before beginning the installation process, make sure you have a reliable backup of any data on your hard disk that you wish to keep. Mistakes in partitioning your hard disk may lead to data loss.
NetBSD/mac68k uses the same disk mapping scheme as Mac OS: the Apple Disk Partition Map. This permits both systems to reside on the same disk, but introduces some installation problems unique to the Macintosh. There are very few, if any, reliable ways to reduce the size of an existing Mac OS disk partition, so partitioning a disk that currently contains Mac OS will almost always require a backup and reload step under Mac OS.
If you are using the sysinst method of installation you will be able to do most, if not all, of your disk partitioning during the install process. Partitioning the disk with sysinst will destroy any partition that is resized, deleted, converted, or designated for use by NetBSD. All space not planned to be used for Mac OS HFS partitions may be used by NetBSD and can be sub-divided by the sysinst process. This space may be defined within one or more existing disk partitions of any type, including HFS partitions that are no longer needed for Mac OS. However it is best if this space is physically contiguous on the disk as sysinst is not capable of merging non-contiguous disk partitions. If you are using the sysinst method and have sufficient disk space in one or more disk partitions you should skip forward to the section labeled Installing the NetBSD System (Sysinst Method) in this document.
If you are using the Traditional method of installation you must use a disk partitioning utility to designate the different partitions you will want in your final NetBSD configuration. It is not necessary to create NetBSD (or AU/X) type partitions at this stage; the Mkfs utility can convert a partition of any type to one usable for NetBSD.
If disk partitioning is required because you've selected the Traditional method of installation, or because disk space needs to be freed up for use for the sysinst method of installation, follow the directions in the remainder of this section.
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 target number (or "SCSI ID"), 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 space. You may choose to use more than one partition
to hold the installation. This allows you to separate the more vital
portions of the file system (such as the kernel and the
/etc
directory) from the more volatile parts of the file system.
Typical setups place the
/usr
directory on a separate partition from the root partition
(/).
Generally,
/
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.
base.tgz, etc.tgz, and either
kern-GENERIC.tgz or
kern-GENERICSBC.tgz)
requires about 100MB.
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 20 MB 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 Mac OS in order to boot, so it is likely that you will want to keep at least a minimal install of Mac OS around on an HFS partition for this purpose. The size of this partition may vary depending on the size requirements for the version of Mac OS you are using. Of course, if you have Mac OS 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.
Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it in hand when doing the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
The SCSI driver used in the kernel on many older Macintosh systems is, by default, the ncrscsi driver. It contains a recognized but as yet unfixed bug that affects some disk drive/controller combinations, usually Quantum disks. Under heavy load these systems may hang or corrupt the file system; or, you may experience frequent Segmentation fault and Illegal instruction errors that may or may not be consistently repeatable. This latter condition is particularly prevalent on systems with minimal RAM installed.
If either of these problems occur on your system you are advised to use the SBC variants of the Kernel and Installation Kernel. However, be aware that this issue does not affect e.g. Centris or Quadra systems.
NetBSD has known but unresolved problems running on the 68LC040 processor, the variant of the 68040 that does not contain the floating point unit (FPU). The kernel is thus forced to emulate the missing operations in software. Unfortunately the 68LC040 processor has a design problem that causes the emulation to fail intermittently. We hope to provide a solution for this issue in a future NetBSD release.
Software emulation of floating point operations is not a problem on the 68020 and 68030 processors.
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example.
netbsd-INSTALL.gz
or
netbsd-INSTALLSBC.gz.
Close the window using the
Close
button.
The main menu will be displayed. Insert the first boot floppy you just created and boot the computer. After language selection, the main menu will be displayed.
.***********************************************.
* NetBSD-5.2 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root
and set a password for that account.
You are also advised to edit
/etc/rc.conf
to match your needs.
Prior to attempting to boot NetBSD/mac68k verify that all the following are done:
It is probably best to boot your machine with all extensions turned off [1].
You can do this by booting into Mac OS 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. Select the Kernel Location to be from Mac OS with the filename corresponding to the name of the Installation Kernel you are using. Typically this will be netbsd-INSTALL.gz.
If you haven't already put your Macintosh into B&W mode, select the Monitor Options from the Options menu and check the box for B&W mode.
Try booting NetBSD by selecting Boot Now from the Options menu.
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. As an alternative, try using the Traditional method of installation described in the next section.
You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, select yes.
The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
The NetBSD distribution consists of a number of sets that come in the form of gzipped tarfiles. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly.
For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM drive
(usually cd0),
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.
To be able to install using ftp, you first need to configure
your network setup if you haven't already done so.
sysinst
will do this for you, asking you
if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will proceed to transfer all the default set files from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup if you haven't already done so.
sysinst
will do this for you, asking you
if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine.
If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server.
NetBSD/mac68k does not currently have in-kernel support for Mac OS HFS/HFS+ or AppleShare filesystems. sysinst therefore can not access the file sets if they are on these filesystems.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example sd1e)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.
Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably on machines with slow graphics consoles or serial consoles. Alternatively, you can choose to see a progress bar. This is the preferred option as it shows progress without significantly slowing down the installation process.
After all the files have been extracted, the device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can then set a password for the "root" account, to prevent the machine from coming up without access restrictions.
Congratulations, you have successfully installed NetBSD 5.2. You can now reboot the machine and boot NetBSD from hard disk.
/)
and
NetBSD Usr
for all the other partitions. You should select
NetBSD Swap
for the swap partition.
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 file system. 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 file system.
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 file systems on. Note that you do not need a file system 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 (SCSI target number) that you did for Mkfs - i.e., the one you are installing NetBSD on.
If you are installing onto a single root partition
(/),
proceed to the
Installation of base files
section, below.
If you have not created file systems for
/
(root),
usr,
and any other file systems, go back to
Preparing the file system(s)
above.
When you started the Installer, it mounted your root partition
(/).
Just before it printed
Mounting partition 'A' as /
it printed lines like:
sd1 at scsi ID 5
This means that the device for SCSI target 5 ("SCSI ID 5") is
sd1.
The partitions
are signified by a trailing letter. For instance,
sd1a
would be
the root partition
(/)
of the second SCSI disk in the chain, and
sd0g
would be the first Usr partition on the first SCSI disk.
You will need to know the proper device to mount the remaining partition(s) by hand:
# mkdir path
E.g. for the
/usr
partition type:
# mkdir /usr
# mount device path
For example, if you wish to mount a
/usr
partition from the first SCSI disk
sd0,
on
/usr, you would type:
# mount /dev/sd0g /usr
# fstab force
/etc/fstab
file.
base.tgz, etc.tgz, either kern-GENERIC.tgz or kern-GENERICSBC.tgz,
and any other sets you wish to
install at this time (see the
NetBSD 5.2 Release Contents
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 two
hours on a slow hard drive).
As is the case with Mkfs, this is not a particularly well-behaved Macintosh application and the machine will be completely tied up while the installation takes place.
At some point after installing the base set, select the
Build Devices
option from the
File
menu if you have not already done
so. This will create a bunch of device nodes for you and will
create your initial
/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.
When you are finished installing all of the sets you wish to install, exit the Installer by choosing Quit from the File menu.
It is probably best to boot your machine with all extensions turned off [2]. You can do this by booting into Mac OS 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 target number. If not, correct them to your preference (the SCSI target number, or "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
NetBSD5.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 properly configured state. The most important steps are described below.
/etc/rc.conf
If you or the installation software haven't done any configuration of
/etc/rc.conf
(sysinst
usually will),
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 file system
(/)
mounted read-only.
When the system asks you to choose a shell, simply press
RETURN
to get to a
/bin/sh
prompt.
If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and press
RETURN.
You may need to type one of the following commands to get your delete key
to work properly, depending on your keyboard:
# stty erase '^h'
# stty erase '^?'
At this point, you need to configure at least
one file in the
/etc
directory.
You will need to mount your root file system read/write with:
# /sbin/mount -u -w /
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.
Default values for the various programs can be found in
/etc/defaults/rc.conf,
where some in-line documentation may be found.
More complete documentation can be found in
rc.conf(5).
When you have finished editing
/etc/rc.conf,
type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that may need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute.
You may also need to add an
ifconfig_int
for your
<int>
network interface,
where your on-board, NuBus or PDS interface may be
ae0,
mc0
or
sn0.
For example:
ifconfig_sn0="inet 192.0.2.123 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_sn0="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.
Instead of manually configuring network and naming service,
DHCP can be used by setting
dhclient=YES
in
/etc/rc.conf.
Other files in
/etc
that 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.
Unless you've set a password in
sysinst,
there
is no initial password.
You should create an account for yourself (see below) and protect it and the
``root''
account with good passwords.
By default, root login from the network is disabled (even via
ssh(1)).
One way to become root over the network is to log in as a different
user that belongs to group
``wheel''
(see
group(5))
and use
su(1)
to become root.
Use the
useradd(8)
command to add accounts to your system.
Do not
edit
/etc/passwd
directly! See
vipw(8)
and
pwd_mkdb(8)
if you want to edit the password database.
If you installed the X Window System, you may want to read the chapter about X in the NetBSD Guide: http://netbsd.org/docs/guide/en/chap-x.html
If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system, pkgsrc. pkgsrc automatically handles any changes necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages on which the software may depend.
mac68k/5.2/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/mac68k/5.2/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v firefox ...
If you are using
csh(1)
then replace the first two lines with the following:
# setenv PKG_PATH ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/mac68k/5.2/All
/pub/pkgsrc
directory.
If you would like to use such mirrors, you could also try the
/pub/NetBSD/packages/current-packages/NetBSD/mac68k/5.2/All
directory, which may have the same contents.
The above commands will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on.
pkg_add(1)
command will complain about a version mismatch of packages with a message
like the following:
Warning: package `foo' was built for a different version of the OS:
NetBSD/i386 M.N (pkg) vs. NetBSD/i386 5.2 (this host),
/usr/pkgsrc
(though other locations work fine) with the commands:
# cd /usr
# tar -zxpf pkgsrc.tar.gz
After extracting, see the
doc/pkgsrc.txt
file in the extraction directory (e.g.,
/usr/pkgsrc/doc/pkgsrc.txt)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/postfix/main.cf
file will almost definitely need to be adjusted.
If you prefer a different MTA, then install it using
pkgsrc or by hand and adjust
/etc/mailer.conf.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The easiest way to upgrade to NetBSD 5.2 is with binaries, and that is the method documented here.
To do the upgrade, you must boot the install kernel using one of
the methods described above.
You must also have at least the
base
and
kern
binary distribution sets available.
Finally, you must have sufficient disk space available to install the
new binaries.
Since files already installed on the system are overwritten in place,
you only need additional free space for files which weren't previously
installed or to account for growth of the sets between releases.
If you have a few megabytes free on each of your root
(/)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the kernel, boot blocks, 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 the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process.
The upgrade procedure
is similar to an installation, but without the hard disk partitioning.
sysinst
will attempt to merge the settings stored in your
/etc
directory with the new version of
NetBSD.
Also, file systems are checked before unpacking the sets.
Fetching the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document for help.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD
5.2
system.
However, that doesn't mean that you're finished with the upgrade process.
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
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.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 5.2.
If your port uses X.Org and you see messages from the X server indicating that no devices were found, you may need to run X -configure and update your existing xorg.conf to use the BusID line from the newly-generated config file.
Dual-head support for PC systems has become broken for many configurations with the update to xorg-server 1.6.x, which has removed the userland PCI configuration mechanism, and needs to rely upon the OS. We hope to correct this for future releases. Workaround: The only workaround is non-trivial and requires programming several PCI BAR registers as they previously were in NetBSD 5.0.
If you are updating to
NetBSD
5.2
without the aid of sysinst or postinstall and your port uses X.Org, be sure
to remove
/usr/X11R7/lib/X11/xkb/symbols/pc
before extracting the xbase set.
In the version of X.Org shipped with 5.0, this was a directory, but in more
recent X.Org versions it is a file.
pkg_install now depends on the pkgdb cache for automatic conflict detection. It is recommended to rebuild the cache with
# pkg_admin rebuild
audit-packages.conf(5)
has been superseded by
pkg_install.conf(5).
The default configuration is the same.
Support for
pkg_view(1)
has been retired.
The functionality of
audit-packages(1)
and
download-vulnerability-list(1)
has moved into
pkg_admin(1).
However, wrapper scripts that handle the common use cases are provided.
The pthread libraries from previous versions of
NetBSD
require that the
sysctl(3)
node
kern.no_sa_support
be set to
0.
This affects the following environments:
The 5.x kernel defaults to
0
for
kern.no_sa_support,
which covers the first case.
However, please note that a full installation of 5.x
(either from scratch or through an upgrade)
will set
kern.no_sa_support
to 1 during the boot process.
This means that for the last two cases, you will have to manually set
kern.no_sa_support
to
0,
using either the
sysctl(8)
command or through
sysctl.conf(5).
Note that sysinst will automatically invoke
postinstall fix
The following issues can generally be resolved by running postinstall with the etc set:
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/envsys.conf
The following issues need to be resolved manually:
postinstall -s /path/to/etc.tgz fix mailerconf
/etc/mailer.conf
file to use Postfix as the MTA. When using
sysinst
to upgrade the system, it will ask if you want this to be done.
Note that if you have a customized Sendmail setup, you need to set up Postfix in an equivalent way; there is no tool for automatic conversion of Sendmail configuration to a Postfix one.
Postfix will be started automatically when the system boots.
You may see messages like "$sendmail is not set properly" at boot.
You can suppress them by removing
/etc/rc.d/sendmail
and
/etc/rc.d/smmsp.
Those files and other parts of sendmail configuration like files under
/usr/share/sendmail
are not removed by default
while upgrading for those who want to continue using sendmail from
outside the base system.
If you want to delete them,
postinstall
can be used:
postinstall -s /path/to/etc.tgz fix sendmail
The following issues can generally be resolved by running postinstall with the etc set:
postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix
Issues fixed by postinstall:
/etc
need upgrading.
These include:
/etc/defaults/*
/etc/mtree/*
/etc/daily
/etc/weekly
/etc/monthly
/etc/security
/etc/rc.subr
/etc/rc
/etc/rc.shutdown
/etc/rc.d/*
/etc/envsys.conf
The following issues need to be resolved manually:
mount(8)
command now requires the
nosuid
and
nodev
options to be explicitly specified.
Previously, these options were automatically enforced even if they
were not explicitly specified.
Documentation is available if you installed the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)'.
Some examples of this are
intro(1),
man(1),
apropos(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),
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.
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. See http://www.NetBSD.org/mailinglists/ for a web interface.
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.
Bugs also can be submitted and queried with the web interface at http://www.NetBSD.org/support/send-pr.html
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/mailinglists/
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-users@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 or WWW 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 work on BSD systems, support, and encouragement.
(in alphabetical order)
All product names mentioned herein are trademarks or registered trademarks of their respective owners.
The following notices are required to satisfy the license terms of the software that we have mentioned in this document:
NetBSD is a registered trademark of The NetBSD Foundation, Inc.
In the following statement, the phrase ``this text'' refers to portions
of the system documentation.
Portions of this text are reprinted and reproduced in electronic form in
NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for
Information Technology -- Portable Operating System Interface (POSIX),
The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the
Institute of Electrical and Electronics Engineers, Inc and The Open Group.
In the event of any discrepancy between these versions and the original
IEEE and The Open Group Standard, the original IEEE and The Open Group
Standard is the referee document.
The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html.
This notice shall appear on any product containing this material