About this Document............................................1
Dedication.....................................................2
What is NetBSD?................................................2
Upgrade path to NetBSD 1.6.2...................................2
Changes Between The NetBSD 1.6.1 and 1.6.2 Releases............3
Kernel......................................................3
Networking..................................................3
Security....................................................4
System administration and user tools........................4
Miscellaneous...............................................4
amiga specific..............................................4
Changes Between The NetBSD 1.6 and 1.6.1 Releases..............4
Kernel......................................................5
Networking..................................................5
File system.................................................6
Security....................................................6
System administration and user tools........................6
Miscellaneous...............................................6
Changes Between The NetBSD 1.5 and 1.6 Releases................7
Kernel......................................................7
Networking..................................................7
File system.................................................8
Security....................................................9
System administration and user tools........................9
Miscellaneous...............................................9
The Future of NetBSD..........................................10
Sources of NetBSD.............................................11
NetBSD 1.6.2 Release Contents.................................11
NetBSD/amiga subdirectory structure........................13
Miniroot file system.......................................13
Binary distribution sets...................................13
NetBSD/amiga System Requirements and Supported Devices........15
Supported devices..........................................15
Getting the NetBSD System on to Useful Media..................17
Preparing your System for NetBSD installation.................19
Preparing your hard disk with HDToolBox....................20
Transferring the miniroot file system......................21
Installing the NetBSD System..................................22
Booting....................................................22
Once your kernel boots.....................................23
Post installation steps.......................................25
Upgrading a previously-installed NetBSD System................27
Once your kernel boots.....................................28
Compatibility Issues With Previous NetBSD Releases............29
Issues affecting an upgrade from NetBSD 1.5................29
Issues affecting an upgrade from NetBSD 1.4 or prior.......30
Using online NetBSD documentation.............................31
Administrivia.................................................31
Thanks go to..................................................32
We are........................................................34
Legal Mumbo-Jumbo.............................................38
The End.......................................................41
This document describes the installation procedure for
NetBSD1.6.2
on the
amiga
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 Foundation would like to dedicate the NetBSD 1.6.2 release to the memory of Erik Reid, who went missing and is presumed dead in a sailing accident on 18 February 2004. Erik's contributions to NetBSD included work on support for SGI MIPS R4000, integrating XFree86 Direct Rendering Interface (DRI), and managing the build lab. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace.
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 fifty three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD1.6.2 release contains complete binary releases for thirty eight different system architectures. (The fifteen remaining are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at http://www.netbsd.org/.)
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.
NetBSD1.6.2 is an upgrade of NetBSD1.6.1 and earlier major and patch releases of NetBSD.
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.6 was started are designated by version identifiers such as 1.6A, 1.6B, etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 kernel on such a system will probably 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.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk.
The NetBSD1.6.2 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, patches and updates to kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over nine months of development that went into the NetBSD1.6.2 release. Some highlights include:
pciide(4),
make Promise controllers do DMA with large disks
requiring 48-bit LBA drives.
pciide(4).
mlx(4)
stability improved.
pciide(4).
userconf(4)
for more information.
wdc(4)
to work with pre-ATA drives.
rtk(4)
multicast problem fixed.
fxp(4)
support yet a few more chip variants.
tulip(4)
driver fixed so that the DEC Alpha PWS no longer panics.
bce(4)
driver added for Broadcom BCM4401 chipset, as seen in recent
Dell laptops.
vi(1)
triggered by an error was fixed.
scsictl(8)
now supports a few new commands.
And of course there have also been innumerable bug fixes and other miscellaneous enhancements. You can look for this trend to continue.
The NetBSD1.6.1 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, patches and updates to kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over seven months of development that went into the NetBSD1.6.1 release. Some highlights include:
aac(4).
audio(4),
dpt(4),
eap(4),
emuxki(4),
iop(4),
siop(4)
and
umass(4).
pciide(4)
support has been extended to support Promise
Ultra133TX2, Promise Ultra133TX2v2, HighPoint HPT372, Ultra/133
on VIA VT8233A, and the VIA VT8235.
tlp(4)
and
xi(4)
drivers.
pcn(4)
driver.
rtk(4)
now supports Planex FNW-3603 cardbus ethernet card.
ex(4)
multicast handling has been fixed.
wi(4)
now supports Netgear MA401RA card.
wm(4)
now supports more chip variants.
aue(4)
now supports SMC 2206USB/ETH EZ Connect adapter.
sip(4)
now has some Tx interrupt mitigation code, and improved
support for 64-bit DP83820 cards.
fxp(4)
driver has been improved for better support of
certain i82558 revisions, and has been fixed to recognize
some more chips.
bge(4)
driver.
ftpd(8)
interoperability bugs have been fixed.
mopd(8)
fixes to make the program load correctly.
pppoe(4)
bugs have been fixed.
ffs(4)
soft dependencies handling have been incorporated.
amd(8).
fsck(8)
bugs have been fixed.
named(8)
and the libc resolver.
file(1)
have been fixed.
tar(1)
has been fixed.
user(8)
has seen several fixes, some of them related to MD5 and
blowfish password encryption support.
And of course there have also been innumerable bug fixes and other miscellaneous enhancements. You can look for this trend to continue.
The NetBSD1.6 release provides numerous significant functional enhancements, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems.
It is impossible to completely summarize over eighteen months of development that went into the NetBSD1.6.2 release. Some highlights include:
scsipi(9).
userconf(4),
activated with the
-c
boot loader flag.
ehci(4)
host controller.
irframe(4)
IrDA frame level driver.
Serial dongles and the
oboe(4)
driver are currently supported.
INCLUDE_CONFIG_FILE
in
options(4)
for more information.
sysctl(8).
vlan(4).
ndbootd(8)
added;
used to netboot
NetBSD/sun2
machines.
racoon(8)
added;
IKE key management daemon for IPsec key negotiation, from the KAME project.
ifconfig(8)
and
awi(4)
driver.
wi(4)
and
wiconfig(8)
now support scanning for access points,
and defaults to BSS instead of ad-hoc mode.
bridge(4).
pppoe(4).
ifwatchd(8)
added;
invokes up-script and down-script when a network interface goes up and down.
Used by
pppoe(4).
dump(8),
dumpfs(8),
fsck_ffs(8),
fsirand(8),
newfs(8),
and
tunefs(8)
support a
-F
option to manipulate file system images in regular files.
makefs(8)
added;
creates file system images from a directory tree.
(Currently ffs only.)
newfs(8)
calculates default block size from the file system size,
and uses the largest possible cylinders/group (cpg) value if
-c
isn't given.
dpti(4)
driver added;
an implementation of the DPT/Adaptec SCSI/I2O RAID management interface.
Allows the use of the Linux versions of
dptmgr,
raidutil,
dptelog,
(etc).
chroot(8)
hierarchy for services including
named(8),
ntpd(8),
and
sshd(8).
passwd(5)
ciphers:
MD5, and
DES with more encryption rounds.
See
passwd.conf(5).
/etc/security
performs many more checks and is far more flexible in how it monitors
changes.
See
security.conf(5).
sushi(8)
added;
a menu based system administration tool.
pgrep(1)
and
pkill(1)
added;
find or signal processes by name or other attributes.
etcupdate(8)
script which helps updating the
/etc
config files interactively, and the
/etc/postinstall
script which is provided to check for or fix configuration changes
that have occurred in
NetBSD.
stat(1)
added;
a user interface to the information returned by the
stat(2)
system call.
sort(1)
replaces
GNU
sort(1).
rc.d(8)
scripts waits until the service terminates before returning.
This improves the reliability of
``restart''
operations as well.
swapoff
in
rc.conf(5).
rc.shutdown(8)
after the number of seconds provided in
rcshutdown_timeout
from
rc.conf(5).
src/build.sh
is available for doing arbitrary cross-builds; see
src/BUILDING
for more information.
At least 38 ports for the
NetBSD1.6.2
release were cross-built on a
NetBSD/i386
system using this mechanism.
agp(4)
for faster access to graphics boards.
init(8)
will create an mfs (memory based file system)
/dev
if
/dev/console
is missing.
vmstat(8)
displays kernel hash statistics with
-H
and
-h hash.
wscons(4)
supports blanking of VGA consoles.
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.
This is the eighth major release of NetBSD for the Amiga and DraCo line of computers.
New port-specific features include:
The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.
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.
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.
Refer to
http://www.netbsd.org/Sites/net.html.
The root directory of the NetBSD1.6.2 release is organized as follows:
.../NetBSD-1.6.2/
CHANGESLAST_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.6.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 that may be subject to
export regulations of the United States, e.g.
code under
src/crypto
and
src/sys/crypto.
It is your responsibility
to determine whether or not it is legal for you to export these portions
and to act accordingly.
The source distribution sets can be found in subdirectories of the
source
subdirectory of the distribution tree.
They contain the complete sources to the system.
The source distribution sets are as follows:
config(8);
and
dbsym(8).
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
The
sets/Split/
subdirectory contains 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 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.?? | ( cd / ; tar -zxpf - )
In each of the source distribution set directories, there are files which contain the checksums of the files in the directory:
BSDSUMCKSUMMD5SYSVSUMThe 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.
amiga
subdirectory of the distribution:
.../NetBSD-1.6.2/amiga/
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.INSTALL.gzsets/installation/floppy/miniroot/misc/miniroot.fs/
(root) and
/usr
partitions and getting ready to extract (and possibly first
fetching) the distribution sets.
There is enough on this file system to allow you to make a SLIP or
PPP connection, configure an Ethernet, mount an NFS file system or ftp.
You can also load distribution sets from a SCSI tape or from one of
your existing
AmigaDOS
partitions.
amiga/binary/sets
subdirectory
of the
NetBSD1.6.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 this distribution set.
/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, 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 amiga 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 -xpf
command from the root directory (
/
) of your system.
This utility is used only in a Traditional method installation.
NetBSD1.6.2 runs on any Amiga that has a 68020 or better CPU with some form of MMU, and on 68060 DraCos.
NetBSD does not, and will never, run on run on A1000, A500, A600, A1200, A2000, A4000/EC030, CDTV and CD32 systems that are not enhanced by a CPU board.
For 68020 and 68030 systems, a FPU is recommended but not required for the system utilities. 68LC040, 68040V and 68LC060 systems don't work correctly at the moment.
The minimal configuration requires 6 MB of RAM (not including CHIPMEM!) and about 75 MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (6 MB of RAM will actually allow you to compile, however it won't be speedy. X really isn't usable on a 6 MB system.)
Here is a table of recommended HD partition sizes for a full install:
| Partition | Suggested | + X | Needed | + X |
| / (root) | 25 MB | 25 MB | 20 MB | 20 MB |
| /usr | 245 MB | 270 MB | 120 MB | 145 MB |
| /var | 20 MB | 20 MB | 5 MB | 5 MB |
| swap | 2*RAM below 32 MB, then up to you |
As you may note the recommended size of
/usr
is 125 MB greater than needed.
This is to leave room for a kernel source and compile tree as
you will probably want to compile your own kernel.
GENERIC
is large and bulky to accommodate all people.
For example, most people's machines have an FPU, so you do not need the
bulky FPU_EMULATE option.
Preconfigured or precompiled packages are installed below
/usr/pkg
by default.
You should either make
/usr
larger (if you intend to install a lot of them), make
/usr/pkg
an additional partition, use the
-p
option to
pkg_add
to install them in a different place, or link
/usr/pkg
to a different place.
If you only have less than 8 MB of fast memory, you should make your swap partition larger, as your system will be doing much more swapping. Especially: do not place it onto a old small (and normally slow) disk!
If its not on the above lists, there is no support for it in this release.
Especially (but this is an incomplete list), there are no
drivers for: Blizzard III SCSI option,
Ferret SCSI, Oktagon SCSI.
Installation is supported from several media types, including:
The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below.
set_name.xx
pieces can be placed in a single directory instead of separate ones for each
distribution set.
This will also simplify the installation work later on.
Note where you place the files as you will need this later.
Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk.
If your SCSI CD-ROM is connected to a supported SCSI host adapter, or it is an ATAPI cd-rom connected to the A1200/A4000 internal IDE connector, simply put the CD into the drive before installation.
Find out where the distribution set files are on the CD-ROM.
Proceed to the instruction on installation.
set_name.xx
files that make up the
distribution sets you want to install or upgrade.
You will need one sixth that number of 1.44 MB floppies.
Format all of the floppies with
MS-DOS.
Do
not
make any of them bootable
MS-DOS
floppies, i.e. don't use
format /s
to format them.
(If the floppies are bootable, then the
MS-DOS
system files that make them bootable will take up some space, and you
won't be able to fit the distribution set parts on the disks.)
If you're using floppies that are formatted for
MS-DOS
by their manufacturers, they probably aren't bootable, and you can use
them out of the box.
Place all of the
set_name.xx
files on the
MS-DOS
disks.
Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
204.152.184.75
(as of June, 2002).
Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
/etc/exports
file on of the NFS server and resetting its mount daemon (mountd).
(Both of these actions will probably require superuser
privileges on the server.)
You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself.
Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like:
# tar -cf tape_device dist_directories
where
tape_device
is the name of the tape device that
describes the tape drive you're using; possibly
/dev/rst0,
or something similar, but it will vary from system to system.
(If you can't figure it out, ask your system administrator.)
In the above example,
dist_directories
are the
distribution sets' directories, for the distribution sets you
wish to place on the tape.
For instance, to put the
misc, base, and etc
distributions on tape (in
order to do the absolute minimum installation to a new disk),
you would do the following:
# cd .../NetBSD-1.6.2
# cd amiga/binary
# tar -cf tape_device misc etc kern
Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading.
Place the distribution sets you wish to upgrade somewhere in
your current file system tree.
Please note that the
/dev
on the floppy used for upgrades only knows about
wd0,
wd1,
sd0,
sd1,
and
sd2.
If you have more than two IDE drives or more than three SCSI drives, you
should take care not to place the sets on the high-numbered drives.
At a bare minimum, you must upgrade the base and kern binary distributions, and so must put the base and kern sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should not upgrade the etc distribution; it contains contains system configuration files that you should review and update by hand.
Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system.
You will need an AmigaDOS hard drive prep tool to prepare your hard drives for use with NetBSD/amiga. HDToolBox is provided with the system software and on floppy installation disks since Release 2.0 of AmigaDOS, so we will provide instructions for its use.
Note that NetBSD can't currently be installed on disks with a sector size other than 512 bytes (e.g., ``640 MB'' 90mm M-O media). You can, however, mount ADOSFS partitions on such M-O's.
A full explanation of HDToolBox can be found with your AmigaDOS manuals and is beyond the scope of this document.
The first time you partition a drive, you need to set its drive type so that you have working geometry parameters. To do this you enter the ``Change drive type'' menu, and either use ``read parameters from drive'' or set them manually.
Note you will be modifying your HD's. If you mess something up here you could lose everything on all the drives that you configure. It is therefore advised that you:
What you need to do is partition your drives; creating at least
root, swap and
/usr
partitions and possibly at least one more for
/usr/local
if you have the space.
This should be done as the HDToolBox manual describes. One thing to note is that if you are not using a Commodore controller you will need to specify the device your SCSI controller uses, e.g. if you have a Warp Engine you would:
SCSI_DEVICE_NAME=warpdrive.device
The important things you need to do above and beyond normal partitioning includes (from Partition Drive section):
/),
if you want to boot
NetBSD
directly, or the swap partition, if you want
to boot the installation miniroot directly.
To make the needed changes:
root partition : 0x4e425207 (NBR\007)
swap partition : 0x4e425301 (NBS\001)
other partitions: 0x4e425507 (NBU\007)
Here
`other'
refers to other partitions you will
format for reading and writing under
NetBSD
(e.g.
/usr)
Make sure you press
RETURN
to enter this value as some versions of HDToolBox will forget your entry
if you don't.
On the root
(/)
(and, for installation, swap) partition,
set instead this:
Mask and maxtransfer are not used with NetBSD.
Once this is done NetBSD/amiga will be able to recognize your disks and which partitions it should use.
Once the hard disk has been prepared for
NetBSD,
the miniroot file system
(miniroot.fs)
is transferred to the swap
partition configured during the hard disk prep (or the existing
swap partition in the case of an upgrade).
The xstreamtodev utility provided in the
amiga/installation/misc
directory can
be used on
AmigaDOS
to transfer the file system for either a new
installation or an upgrade.
The file system can also be transferred on an existing
NetBSD
system for an update by using dd.
This should only be done after booting
NetBSD
into single-user state.
It may also be possible to shutdown to single-user, providing that
the single-user state processes are not using the swap partition.
On AmigaDOS, the command:
xstreamtodev --input=miniroot.fs --rdb-name=<swap partition>
where <swap partition> is the name you gave to the NetBSD partition to be used for swapping. If xstreamtodev is unable to determine the SCSI driver device name or the unit number of the specified partition, you may also need to include the option
--device=<driver.name>
and/or
--unit=<SCSI unit number>
To transfer the miniroot using NetBSD, you should be booted up in single user state on the current NetBSD system, or use the shutdown now command to shutdown to single-user state. Then copy the miniroot using dd:
dd if=miniroot.fs of=/dev/rsd0b
where
/dev/rsd0b
should be the device path of the swap partition
your system is configured to use.
Once the file is copied, reboot back to
AmigaDOS
to boot the upgrade kernel.
miniroot.fs
on the swap partition.
Installing NetBSD is a relatively complex process, but, if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble.
Before you begin, you must have already prepared your hard disk as detailed in the section on preparing your system for install.
The following is a walk-through of the steps necessary to get
NetBSD
installed on your hard disk.
If you wish to stop the installation, you may press
CONTROL-C
at any prompt, but if you do, you'll have to
begin again from scratch.
Transfer the miniroot file system onto the hard disk partition used by NetBSD for swapping, as described in the "Preparing your System for NetBSD Installation" section above.
[This description is for V40 (OS 3.1) ROMs. For older ROMs, there might be small differences. Check your AmigaDOS documentation to learn about the exact procedure.] Using bootblocks may not work on some systems, and may require a mountable file system on others.
Reboot your machine, holding down both mouse buttons if you have a 2-button mouse, the outer mouse buttons if you have a 3-button mouse. On the DraCo, press the left mouse button instead, when the boot screen prompts you for it.
From the boot menu, select Boot Options. Select the swap partition with the miniroot, and then ok. Select Boot now. The machine will boot the bootblock, which will prompt your for a command line. You have a few seconds time to change the default. Entering an empty line will accept the default.
The bootblock uses command lines of the form:
file[ options]
where file
is the kernel file name on the partition where the
boot block is on, and
[options]
may contain the following:
If you have an AGA machine, and your monitor will handle the dblNTSC mode, you may include the -A option to enable the dblNTSC display mode.
If your machine has a fragmented physical memory space, as, e.g., DraCo machines, you should add the -n2 option to enable the use of all memory segments.
sd0, sd1,)
Then you will be prompted for a root device.
At this time type
sd0b,
where
sd0
is the device which contains the swap
partition you created during the hard disk preparation.
When prompted for a dump device, answer
`none'
for the install
(normally, you would tell it one of the swap devices).
When prompted for the root file system type, confirm
`generic',
which will auto-detect it.
If the system should hang after entering the root device, try again with
netbsd -I ff -b
This disables synchronous transfer on all SCSI devices on the first bus.
The system should continue to boot.
For now ignore
``WARNING''
messages about bad dates in clocks, and a warning about
/etc/rc
not existing.
Eventually you will be be asked to enter the pathname of the shell, just press
RETURN.
After a short while, you will be asked to select the type of your keyboard.
After
you have entered a valid response here, the system asks you if
you want to install or upgrade your system.
Since you are reading the
install
section,
`i'
would be the proper response here...
The installer starts with a nice welcome messages. Read this message carefully, it also informs you of the risks involved in continuing! If you still want to go on, type `y'. The installer now continues by trying to figure out your disk configuration. When it is done, you will be prompted to select a root device from the list of disks it has found.
You should know at this point that the disks are
not
numbered according to their SCSI-ID!
The
NetBSD
kernel numbers the SCSI
drives (and other devices on the SCSI bus) sequentially as it finds them.
The drive with the lowest SCSI-ID will be called
sd0,
the next one
sd1,
etc.
Also, any ATAPI disk drives (e.g. ZIP)
will be configured as
``SCSI''
drives, too, and will be configured
before any
`real'
SCSI drives if connected to the Amiga internal port on A4000/A1200
(if any are present). Real IDE drives will be configured as
wd0,
wd1,
etc.
The installer will offer you to look at the NetBSD disk label of the disks at this point. You should do this, to find out what partition letters the NetBSD kernel assigned to the partitions you created, and as a check whether the disk number you are going to use is right.
you are now at the point of no return.
If you confirm that
you want to install
NetBSD,
your hard drive will be modified,
and perhaps its contents scrambled at the whim of the install
program.
Type
Control-C
now
if you don't want this.
At this time, you will need to tell the installer which partition
will be associated with the different file systems.
Normally, you'll want to add a partition for
/usr,
at least.
rsdNc
or
sdNc
partitions for anything!
They are for access to the whole disk only and do
not
correspond to any Amiga partition!
The install program will now make the file systems you specified. There should be only one error per file system in this section of the installation. It will look like this:
newfs: ioctl (WDINFO): Invalid argument
newfs: /dev/rsd0a: can't rewrite disk label
If there are any others, restart from the beginning of the installation process. This error is ok as the Amiga does not write disklabels currently. You should expect this error whenever using newfs.
The install will now ask you want to configure any network information. It ill ask for the machine's host name, domain name, and other network configuration information.
Since the network configuration might have lead to additional (nfs) file system entries, you get another chance to modify your fstab.
You are finally at the point where some real data will be put on your freshly made file systems. Select the device type you wish to install from and off you go....
Some notes:
nrst0).
Try
nrst0h,
nrst0m,
or
nrst0l
instead.
.'.
Next you will be asked to specify the timezone.
Just select the timezone you are in.
The installer will make the correct setup on your root file system
(/).
After the timezone-link is installed,
the installer will proceed by creating the device nodes on your
root file system under
/dev.
Be patient, this will take a while...
Next, the installer will copy your keymap settings to the new system. After this, it will copy the kernel from the installation miniroot to the newly installed / upgraded system. If the installed system already has a kernel, it will ask you for confirmation.
kern.tgz distribution set, this is an old kernel, and you should answer "y" to install a working (although restricted) INSTALL kernel.
If you did install the kern.tgz kernel, you normally should answer "n".
Finally, the installer ask you if you want to install the bootblock
code on your root disk.
This is a matter of personal choice and can also be done from a running
NetBSD
system.
See the
installboot(8)
manual page about how to do this.
Once the installer is done, halt the system with the
halt
command
(wait for
halted
to be displayed) and reboot.
Then again boot
NetBSD
this time selecting the root partition
(/)
from the boot menu, and tell it to boot
netbsd -s
You need to do your final tweaks now. First mount your file systems like so:
mount -av
Your system is now complete but not completely configured; you
should adjust the
/etc/sendmail.cf
file as necessary to suit your site.
You should also examine and adjust the settings in
/etc/rc.conf.
You can use
vi(1)
or
ed(1)
to edit the files.
If you installed the man pages you can type
man vi or man ed
for instructions on how to use these somewhat non-intuitive editors.
Once you are done with the rest of configuration unmount your file systems and halt your system, then reboot:
# cd /
# umount -av
# halt
Finally you can now boot your system and it will be completely functional:
netbsd
When it boots off of the hard drive, you will have a complete
NetBSD
system!
Congratulations!
(You really deserve them!!!)
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, with the most important ones 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).
If your
/usr
directory is on a separate partition and you do not know how to use
ed,
you will have to mount your
/usr
partition to gain access to
ex
or
vi.
Do the following:
# mount /usr
# export TERM=vt220
If you have
/var
on a separate partition, you need to repeat that step for it.
After that, you can edit
/etc/rc.conf
with
vi(1).
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
Other values that need to be set in
/etc/rc.conf
for a networked environment are
hostname
and possibly
defaultroute,
furthermore add an
ifconfig_int
for your
<int>
network interface,
along the lines of
ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_de0="inet myname.my.dom netmask 255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8).
See
resolv.conf(5)
or
named(8)
for more information.
Other files in
/etc
that 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.
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.
Unless you have connected an unusual terminal device as the console
you can just press
RETURN
when it prompts for
Terminal type? [...].
Use the
useradd(8)
command to add accounts to your system;
do not
edit
/etc/passwd
directly.
See
useradd(8)
for more information on how to add a new user to the system.
If you have installed the X Window System, look at the files in
/usr/X11R6/lib/X11/doc
for information.
Don't forget to add
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
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. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.
1.6.2/amiga/All
subdir.
You can install them with the following commands:
# PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/1.6.2/amiga/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v apache # pkg_add -v perl ...
The above commands will install the tcsh shell, the Apache web server and the perl programming language as well as all the packages they depend on.
/usr/pkgsrc
(though other locations work fine), with the commands:
# mkdir /usr/pkgsrc
#( cd /usr/pkgsrc ; tar -zxpf - ) < pkgsrc.tar.gz
After extracting, then see the
README
file in the extraction directory (e.g.
/usr/pkgsrc/README)
for more information.
/etc/mail/aliases
to forward root mail to the right place.
Don't forget to run
newaliases(1)
afterwards.
/etc/mail/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail.
See the
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
# man 5 filename
is likely to give you more information on these files.
The upgrade to NetBSD1.6.2 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily to interdependencies in the various components.
To do the upgrade, you must have the
NetBSD
kernel on
AmigaDOS
and you must transfer the miniroot file system
miniroot.fs
onto the swap partition of the
NetBSD
hard disk.
You must also have at least the
base
binary distribution set available, so that you can upgrade
with it, using one of the upgrade methods described above.
Finally, you must have sufficient disk space available to install the new
binaries.
Since the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
If you have a few megabytes free on each of your
/
(root) and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process.
To upgrade your system, follow the following instructions:
Transfer the miniroot file system onto the hard disk partition used by NetBSD for swapping, as described in the "Preparing your System for NetBSD Installation" section above.
Now boot up NetBSD, with boot blocks installed
Reboot your machine, holding down both mouse buttons if you have a 2-button mouse, the outer mouse buttons if you have a 3-button mouse. On the DraCo, press the left mouse button instead, when the boot screen prompts you for it.
From the boot menu, select Boot Options. Select the swap partition with the miniroot, and then ok. Select Boot now. The machine will boot the bootblock, which will prompt your for a command line. You have a few seconds time to change the default. Entering an empty line will accept the default.
The bootblock uses command lines of the form:
file[ options]
where
file
is the kernel file name on the partition where the
boot block is on, and
options
may contain the same as described in the INSTALL section.
For installing, use
netbsd -b
If you machine has a split memory space, like, e.g., DraCo machines, use this instead:
netbsd -bn2
/)
and swap partitions.
When prompted for the root device, type
sd0b
(replacing
`0'
with the disk number that
NetBSD
used for
your root/swap device).
When prompted for a dump device, answer
`none'
for the upgrade.
(For a normal boot, you would tell it one of the swap devices).
When prompted for the root file system type, confirm
`generic',
which will auto-detect it.
You will be presented with some information about the upgrade
process and a warning message, and will be asked if you wish
to proceed with the upgrade process.
If you answer negatively, the upgrade process will stop, and your disk will
not be modified.
If you answer affirmatively, the upgrade process will begin,
and your disk will be modified.
You may press
CONTROL-C
to stop the upgrade process at any time.
However, if you press it at an inopportune moment, your system
may be left in an inconsistent (and possibly unusable) state.
You will now be greeted and reminded of the fact that this is a potential dangerous procedure and that you should not upgrade the etc set.
When you decide to proceed, you will be prompted to enter your root disk. After you've done this, it will be checked automatically to make sure that the file system is in a sane state before making any modifications. After this is done, you will be asked if you want to configure your network.
You are now allowed to edit your fstab. Normally you don't have to. Note that the upgrade-kit uses it's own copy of the fstab. Whatever you do here won't affect your actual fstab. After you are satisfied with your fstab, the upgrade-kit will check all file systems mentioned in it. When they're ok, they will be mounted.
You will now be asked if your sets are stored on a normally mounted file system. You should answer `y' to this question if you have the sets stored on a file system that was present in the fstab. The actions you should take for the set extraction are pretty logical (we think).
After you have extracted the sets, the upgrade kit will proceed with setting the timezone and installing the kernel and bootcode. This is all exactly the same as described in the installation section.
Your system has now been upgraded to NetBSD1.6.2.
After a new kernel has been copied to your hard disk, your machine is a complete NetBSD1.6.2 system. However, that doesn't mean that you're finished with the upgrade process. There are several things that you should do, or might have to do, to insure that the system works properly.
You will probably want to get the
etc
distribution,
extract it, and compare its contents with those in your
/etc
directory.
You will probably want to replace some of your
system configuration files, or incorporate some of the changes
in the new versions into yours.
You will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since
been removed from the
NetBSD
distribution.
If upgrading from a
NetBSD
version older than 1.0, you might also want to
recompile any locally-built binaries, to take advantage of the
shared libraries.
(Note that any new binaries that you build
will be dynamically linked, and therefore take advantage of
the shared libraries, by default.
For information on how to make statically linked binaries, see the
cc(1)
and
ld(1)
manual pages.)
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD1.6.2.
mkdir /tmp/upgrade
cd /tmp/upgrade
pax -zrpe -f /path/to/etc.tgz
./etc/postinstall -s `pwd` check
./etc/postinstall -s `pwd` 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/rc.d/NETWORK
and
/etc/rc.d/gated.
rc.conf(5)
entries are now obsolete:
amd_master,
ip6forwarding,
defcorename,
and
nfsiod_flags.
critical_filesystems_beforenet
has been replaced by
critical_filesystems_local.
critical_filesystems
has been replaced by
critical_filesystems_remote.
ssh(1)
and
sshd(8)
were moved from
/etc
to
/etc/ssh,
including
ssh_known_hosts*
files and the
host key files
ssh_host*_key*.
/etc/ssh.conf
was renamed to
/etc/ssh/ssh_config,
and
/etc/sshd.conf
was renamed to
/etc/ssh/sshd_config.
wscons.conf(5)
are now obsolete.
The following issues need to be resolved manually:
postfix(8)
configuration files require upgrading.
cd /usr/share/examples/postfix
cp post-install postfix-files postfix-script /etc/postfix
postfix check
/etc/ifconfig.de*
to
/etc/ifconfig.tlp*,
renaming of
rc.conf(5)
entries
ifconfig_de*
to
ifconfig_tlp*,
and the reconfiguration of files such as
/etc/dhclient.conf
and
/etc/ipf.conf.
/etc/rc
modified to use
/etc/rc.d/*
Prior to
NetBSD1.5,
/etc/rc
was a traditional
BSD
style monolithic file; each discrete program or substem from
/etc/rc
and
/etc/netstart
has been moved into separate scripts in
/etc/rc.d/.
At system startup,
/etc/rc
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
and then executes each script in turn with an argument of
`start'.
Many
rc.d
scripts won't start unless the appropriate
rc.conf(5)
entry in
/etc/rc.conf
is set to
`YES.'
At system shutdown,
/etc/rc.shutdown
uses
rcorder(8)
to build a dependency list of the files in
/etc/rc.d
that have a
``KEYWORD: shutdown''
line, reverses the resulting list, and then executes each script in turn
with an argument of
`stop'.
The following scripts support a specific shutdown method:
cron,
inetd,
local,
and
xdm.
Local and third-party scripts may be installed into
/etc/rc.d
as necessary.
Refer to the other scripts in that directory and
rc(8)
for more information on implementing
rc.d
scripts.
named(8)
leaks version information.
Previous releases of
NetBSD
disabled a feature of
named(8)
where the version number of the server could be determined by remote clients.
This feature has not been disabled in
NetBSD1.5,
because there is a
named.conf(5)
option to change the version string:
option {
version "newstring";
};
sysctl(8)
was moved from
/usr/sbin/sysctl
to
/sbin/sysctl.
If you have hardcoded references to the full pathname
(in shell scripts, for example)
please be sure to update those.
sendmail(8)
configuration file pathname changed.
Due to
sendmail(8)
upgrade from 8.9.x to 8.10.x,
/etc/sendmail.cf
is moved to
/etc/mail/sendmail.cf.
Also, the default
sendmail.cf(5)
refers different pathnames than before.
For example,
/etc/aliases
is now located at
/etc/mail/aliases,
/etc/sendmail.cw
is now called
/etc/mail/local-host-names,
and so forth.
If you have customized
sendmail.cf(5)
and friends, you will need to move the files to the new locations.
See
/usr/share/sendmail/README
for more information.
Documentation is available if you first install the manual
distribution set.
Traditionally, the
``man pages''
(documentation) are denoted by
`name(section)'.
Some examples of this are
intro(1),
man(1),
apropros(1),
passwd(1),
and
passwd(5).
The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8.
The man command is used to view the documentation on a topic, and is started by entering man[ section] topic. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter
# man passwd
to read the documentation for
passwd(1).
To view the documentation for
passwd(5),
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.
There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@netbsd.org.
To report bugs, use the
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can.
Good bug reports include lots of details.
Additionally, bug reports can be sent by mail to:
netbsd-bugs@netbsd.org.
Use of
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, 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-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 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 ongoing work on BSD systems, support, and encouragement.
Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek
for answering lots of questions, fixing bugs, and doing the various work they've done.
Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Søren Jørvang Scott Kaplan Noah M. Keiserman Harald Koerfgen John Kohl Chris Legrow Ted Lemon Norman R. McBride Neil J. McRae Perry E. Metzger Luke Mewburn Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Rob Windsor Jim Wise Reinoud Zandijk Christos Zoulas
AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology 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. Precedence Technologies Ltd Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd.
(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:
This product includes software developed by the University of
California, Berkeley and its contributors.