About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 4.0 and 5.0 Releases................2
General kernel..............................................3
Networking..................................................4
File systems................................................4
Security....................................................5
Drivers.....................................................5
Platforms..................................................10
Userland...................................................16
Components removed from NetBSD.............................20
Known Problems.............................................21
Features to be removed in a later release.....................21
The NetBSD Foundation.........................................21
Sources of NetBSD.............................................21
NetBSD 5.0 Release Contents...................................22
NetBSD/amiga subdirectory structure........................23
Miniroot file system.......................................23
Binary distribution sets...................................23
NetBSD/amiga System Requirements and Supported Devices........25
Supported devices..........................................25
Getting the NetBSD System on to Useful Media..................27
Preparing your System for NetBSD installation.................29
Preparing your hard disk with HDToolBox....................29
Transferring the miniroot file system......................31
Installing the NetBSD System..................................31
Booting....................................................32
Once your kernel boots.....................................32
Post installation steps.......................................34
Upgrading a previously-installed NetBSD System................37
Once your kernel boots.....................................38
Compatibility Issues With Previous NetBSD Releases............39
Issues affecting an upgrade from NetBSD 3.x releases.......39
Issues affecting an upgrade from NetBSD 4.x releases.......40
Using online NetBSD documentation.............................40
Administrivia.................................................41
Thanks go to..................................................42
We are........................................................42
Legal Mumbo-Jumbo.............................................48
The End.......................................................55
This document describes the installation procedure for
NetBSD
5.0 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 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.0 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 NetBSD 5.0 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 the massive development that went into the NetBSD 5.0 release. The complete list of changes can be found in the CHANGES: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-5.0/CHANGES and CHANGES-5.0: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-5.0/CHANGES-5.0 files in the top level directory of the NetBSD 5.0 release tree.
Some highlights include:
mutex(9),
rwlock(9),
and
condvar(9).
pset(3),
cpuset(3),
and
affinity(3).
kpreempt(9).
softint(9).
workqueue(9).
mremap(2),
to remap virtual memory addresses.
putter(9)
(Pass-to-Userspace Transporter), a generic request-response handler for kernel-attached userspace daemons.
pmf(9).
ddb(4)
if it panics. To get the old behavior, set ddb.onpanic to 1 in /etc/sysctl.conf.
ddb(4):
Added a
``whatis''
command, inspired by Solaris.
todr(9).
timecounter(9).
posix_madvise(2).
compat_linux(8)
and compat_linux32.
sockopt(9),
a new kernel API for passing socket options.
init(8)
program can be found, set the RB_ASKNAME flag and prompt users for the init path.
accept_filter(9),
accf_data(9),
and
accf_http(9).
fast_ipsec(4):
Added support for IPsec NAT-T.
pf(4):
Made
``nat''
and
``rdr''
translation rules obey state policy flags. Extended
pf.conf(5)
syntax to express the translation-state policies.
wapbl(4),
a preview of metadata journaling for FFS. Contributed by Wasabi Systems.
mount_hfs(8).
mount_efs(8).
mount_udf(8).
mount_psshfs(8),
to support
puffs(3)
sshfs.
mount_9p(8),
to support 9P file services with
puffs(3).
rump_nfs(8),
a userspace NFS client.
mount_sysctlfs(8),
to support browsing, querying, and modifying the
sysctl(3)
hierarchy.
refuse(3)
for FUSE compatibility functionality, layered on top of
puffs(3).
ukfs(3),
for standalone file system access.
p2k(3),
a
puffs(3)
to kernel vfs adaption library.
puffs(4):
Added support for NFS exporting puffs file servers.
newfs_ext2fs(8)
utility to create Ext2 file systems.
fsck_ext2fs(8),
fsck_ffs(8),
fsck_lfs(8):
Disable userid to username lookups by default and add -U flag to perform them.
scan_ffs(8):
Added -b option to search a partition for valid alternate superblocks.
fsck_ffs(8):
Added -x/-X options, which allow running fsck_ffs -n on a snapshot of a live filesystem.
security(8).
security(8).
opencrypto(9)
provider for VIA ACE (AES encryption instructions).
nsp(4),
a driver for NetOctave NSP2000, contributed by NBMK Encryption Technologies, ported from vendor FreeBSD SDK and integrated with opencrypto by Coyote Point Systems.
opencrypto(9):
Improved performance by adding asynchronous operation and batched submit/retrieve of requests/results. Contributed by Coyote Point Systems.
cgd(4):
Changed the default IV to encblkno1, which is faster without a real loss of security.
openssl(1):
Enabled support for Camellia.
pad(4),
a pseudo-audio device driver for feeding back raw PCM data to userland.
sgsmix(4),
a driver for the SGS 7433 mixer found in some G3 Macs.
umidi(4):
Added support for Roland UA25, UA4FX, and SonicCell devices.
dbri(4):
Added support for audio input.
auvia(4)
now works on big endian machines.
azalia(4):
AD1984 support was greatly improved. Added support for Realtek ALC662-GR and ALC269 codecs, which are found in EeePCs. Added support for ALC268.
auich(4):
Fixed a clock accounting problem that prevented detecting sample rates correctly.
powerd(8).
See
envsys(4)
and
sysmon_envsys(9).
aiboost(4),
a driver for the ASUS AI Booster ACPI Hardware monitor.
smsc(4),
a driver for the hardware monitoring portion of the SMSC LPC47B397.
aps(4),
a driver for the IBM Thinkpad Active Protection System.
coretemp(4),
a driver for Intel Core (and newer) on-die thermal sensors.
finsio(4),
a driver for various Fintek Super I/O chips.
amdtemp(4),
a driver for AMD CPU on-die thermal sensors.
dbcool(4),
a driver for Analog Devices dbCool chips including ADT7460, ADT7463, ADT7467, and ADM1030.
alipm(4),
a driver for the Acer Labs M7101 Power Management Controller.
admtemp(4),
a driver for the Analog Devices ADM1021 temperature sensor.
viaenv(4):
Added support for VIA VT8231.
nsclpcsio(4):
Added support for the VLM logical device.
lm(4):
Added an i2c attachment for the LM78 family of temp sensor and fan controllers.
jme(4),
a driver for the JMicron Technologies JME250 Gigabit Ethernet and JME260 Fast Ethernet controllers.
u3g(4),
a driver for many multi-port 3G datacards.
iwn(4),
a driver for the Intel Wireless LAN 4965AGN adapter.
zyd(4),
a driver for ZyDAS ZD1211/ZD1211B USB IEEE 802.11b/g wireless network devices.
uhmodem(4),
a driver for 3G wireless modems including Huawei E220 and E620, E-mobile D01HW and D02HW, and NTT DoCoMo a2502.
lii(4),
a driver for the Atheros L2 Fast Ethernet controller.
btuart(4),
a driver for Bluetooth HCI UART (H4).
ipw(4),
iwi(4),
wpi(4),
and
iwn(4).
For
ipw(4)
and
iwi(4),
the Intel EULA has to be accepted via
sysctl(8).
fxp(4):
Fixed some TX timeout and RX pool corruption problems. Added a workaround for a hardware ip4csum-tx bug.
bge(4):
Added support for BCM5786 and BCM5906(M). Fixed fiber card support.
nfe(4):
Added support for NVIDIA MCP67/73 Ethernet controllers. Fixed wakeup issues on some newer chips. Fixed a problem with receiving jumbo frames.
btbc(4):
Added support for AnyCom BlueCard devices.
rum(4):
Added support for MELCO WLI-U2-SG54HP, PLANEX GW-US54Mini2, COREGA CG-WLUSB2GL and K.K. CG-WLUSB2GPX, and ABOCOM WUG2700.
makphy(4):
Added support for Marvell 88E1116 Gigabit PHY.
gem(4):
Added support for Sun PCI SX fiber cards and Sun SBus SX fiber cards.
wm(4):
Added support for the Intel PRO/1000 PT Quad Port Server Adapter. Fixed a bug on receiving a jumbo frame which lead to a panic in sbcompress(). Added support for more ICH9 devices. Fixed an EEPROM-trashing bug on ICH8 and ICH9 chipsets.
udav(4):
Added support for Shantou ADM8515.
brgphy(4):
Added support for BCM5708C.
re(4):
Made hardware
vlan(4)
insertion/extraction work properly. Added support for the Realtek 8102E/8102EL PCIe 10/100 Ethernet adapters, as well as the 8111C chips that are found on many Intel-based motherboards.
sk(4),
msk(4):
Fixed a lock panic on receiving jumbo packets.
msk(4):
Fixed a Yukon EC Ultra cold power up issue.
bnx(4):
Added support for SerDes controllers.
vge(4):
Added ifconfig down and ALTQ support.
arcmsr(4),
a driver for Areca Technology Corporation SATA RAID controllers.
siisata(4),
a driver for Silicon Image SteelVine SATA-II controllers (SiI3124, SiI3132, and SiI3531).
isp(4):
Major update, including 4Gb (24XX) card support and new firmware sets.
piixide(4):
Added support for ICH10.
ahcisata(4):
Added support for ATAPI devices.
svwsata(4):
Added support for ServerWorks HT-1000 SATA controller.
njata(4):
Added support for Workbit CF32A CF adapter.
viaide(4):
Added support for VIA CX700, CX700M2, NVIDIA MCP67, and MCP73/77 controllers.
mfi(4):
Added support for LSI SAS1078 and Dell PERC 6 controllers.
mpt(4):
Fixed performance problems for old revisions of the Symbios 53c1030.
cac(4):
Added initial
bio(4)
support; only volume status is handled at this time.
siop(4):
Added support for the non-PCI NCR 53c720/770 in big-endian mode.
twa(4):
Added support for 3ware 9650 and 9690, based on contributions from Wasabi Systems.
ciss(4):
Added
bio(4)
support.
ataraid(4):
Added NVIDIA MediaShield, JMicron RAID, and Intel MatrixRAID support. Added support for status reports through
bio(4).
ixpide(4):
Added support for ATI SB700/SB800 controllers.
aac(4):
Added support for raw I/O mode and >2TB.
umass(4):
Added support for Sony GPS GPS-CS1. Fixed a panic on device removal.
aic(4):
Worked around an rbus resource allocation problem so that aic PCMCIA cards work again.
vnd(4),
and
cgd(4).
uvideo(4),
a driver for USB Video Class capture devices, from Patrick Mahoney's Google Summer of Code 2008 project.
uslsa(4),
a driver for CP210x USB-RS232 devices.
uchcom(4),
a driver for WinChipHead CH341/340 and HL-340 USB-Serial adapters.
uberry(4),
a driver to allow RIM BlackBerries to charge from the USB port.
bus_dmamap_sync(9)
calls to
uhci(4),
ohci(4),
and
ehci(4)
to prevent the CPU from reordering loads and stores against DMA descriptors. This fixes
``host controller process error/host controller halted''
errors.
ehci(4):
Added isochronous transfer support, contributed by Jeremy Morse as part of his Google Summer of Code 2008 project.
ukbd(4):
Added support for function keys F16 through F19.
uplcom(4):
Added support for Willcom WS002IN PHS and SMART Technologies-badged devices. Recognize Corega CG-USBRS232R as a serial device.
ugensa(4):
Added support for Novatel Wireless Merlin CMDA and Ovation U727.
ubsa(4):
Added support for CDMA modems sold by Eurotel/O2.
uftdi(4):
Added support for Sealevel SeaPORT+4 USB to Serial adapter.
slhci(4):
Replaced with Matthew Orgass's driver.
video(4),
a video4linux2 compatible capture interface, part of Patrick Mahoney's Google Summer of Code 2008 project.
uvideo(4),
a driver for USB Video Class capture devices, from Patrick Mahoney's Google Summer of Code 2008 project.
pseye(4),
a driver for the Sony PLAYSTATION(R) Eye USB webcam.
genfb(4),
a generic framebuffer console driver with PCI and SBus frontends.
isv(4),
a driver for the IDEC Supervision/16 image capture board.
wscons(4):
Added scrollback support to vcons.
cgfourteen(4):
Added support for wscons.
agp(4):
Added support for ALI M1689, MB i965Q, Intel Q33/35/G33, Intel 945GME, and Intel 946GZ.
bktr(4)
now works on amd64.
pud(4),
a driver that makes it possible to implement block and character devices in userspace.
spdmem(4),
a Serial Presence Detect driver that decodes technical specs stored in the eeprom on common types of memory modules.
bcsp(4)
to support the BlueCore Serial Protocol.
thinkpad(4),
a driver to support IBM/Lenovo Thinkpad hotkeys, brightness controls, and temperature and fan monitoring.
gcscpcib(4),
a driver for the AMD CS5535 and CS5536 Companion Device with support for the timecounter, watchdog timer, and GPIO.
ichsmb(4),
a driver for Intel ICH SMBus controllers.
asus(4),
a driver for ASUS ACPI hotkeys as found in the EeePC.
acpidalb(4),
a driver for PNP0C32 ACPI hotkeys, aka the Direct Application Launch Buttons.
hpqlb(4),
a driver for hotkeys on some HP notebooks.
adb(4):
New and simplified MI ADB drivers.
ichlpcib(4):
Added support for the TCO (watchdog) on ICH6 or newer chipsets. Now runs on EM64T systems as well.
itesio(4):
Added support for the watchdog timer.
ulpt(4):
Implemented non-blocking read.
puc(4):
Added support for the I-O DATA RSA-PCI 2 port serial board, Digi International 4 and 8 port boards, and B&B Electronics MIPort serial boards.
piixpm(4):
Added support for ATI SB600, SB700, and SB800 SMBus controllers.
wscons(4):
Added support for the Colemak keyboard layout.
com(4):
Added support for PCMCIA Sierra Wireless Aircard 850.
nfsmb(4):
Added support for numerous NVIDIA chipsets.
boot.cfg(5)
to configure the bootloader.
mbr(8)
variants that directly access serial ports.
ddb(4)
session on a VGA console if the system crashed while X11 was running.
boot(8):
Added support for the multiboot protocol. This allows booting Xen without GRUB.
cmos(4),
a driver for CMOS RAM.
delay(9)
issue and now the P5064 kernel works in gxemul.
compat_osf1(8)
again.
wdc(4)
frontend for the buddha and catweazle Z2 hardware.
sysinst(8)
support.
eeprom(8)
from actually changing firmware settings.
wdc(4).
genfb(4).
sysinst(8)
support.
spl(9)
bug which could cause a network freeze on traffic between two network interfaces.
gdb(1)
support.
sysinst(8)
support.
bus_dmamap_load(9)
so that NFS write works with
re(4).
sn(4)
to use the MI SONIC driver.
bus_dma(9),
bus_space(9),
SMP, and IPI frameworks.
genfb(4)
is now the default framebuffer.
gcc(1):
Fix jump table addressing in the M68k codegen.
memcpy(3),
memmove(3),
and
memcmp(3).
eeprom(8)
from actually changing firmware settings.
macekbc(4),
onboard display adapter
crmfb(4),
and audio driver
mavb(4).
tl(4).
light(4).
sq(4)
interface on the Challenge S's IOPLUS mezzanine.
ddb(4).
dhclient(8)
to the install disk image.
wscons(4).
genfb(4).
sysinst(8)
support.
pthread(3):
malloc(3)
with jemalloc, bringing a significant performance boost for many threaded workloads that make heavy use of malloc.
curses(3):
termattrs(3)
and
term_attrs(3).
getwin(3)
and
putwin(3).
util(3):
estrndup(3).
raise_default_signal(3).
math(3).
proplib(3):
prop_dictionary_make_immutable(3).
prop_array_util(3)
functions.
dehumanize_number(3).
posix_memalign(3).
strspn(3),
strcspn(3),
and
strpbrk(3)
with O(n+m) implementations.
getlogin_r(2).
imaxabs(3)
and
imaxdiv(3).
atomic_ops(3)
in userspace.
queue(3):
Added TAILQ_CONCAT() and STAILQ_CONCAT().
httpd(8).
rump(3),
the Runnable Userspace Meta Program framework. Allows running kernel code in userspace applications.
cpuctl(8),
a utility that allows placing CPUs online/offline.
schedctl(8),
a program to control scheduling of processes and threads.
psrset(8),
a utility to control processor sets.
atf(7),
the Automated Testing Framework, Julio M. Merino Vidal's 2007 Google Summer of Code project.
newgrp(1),
a utility to change effective group ID.
tcpdrop(8),
a utility to drop
tcp(4)
connections.
acpidump(8)
and
amldb(8).
dkscan_bsdlabel(8)
to scan disks for BSD disklabels.
btkey(1),
a utility to manage Bluetooth link keys in OS and device storage.
svhlabel(8),
a tool to update
disklabel(5)
from SGI Volume Header, like
mbrlabel(8)
for MBR labels.
pcc(1)
as an alternative compiler.
btpand(8),
a Bluetooth Personal Area Networking profile daemon.
c99(1)
as a wrapper to run
cc(1)
in C99 mode.
ld(1)
can now link 32bit objects on amd64.
vi(1)
has been updated to nvi 1.81, which supports internationalization. It also grew a new NetBSD-specific expandtab option.
pkill(1):
Added the -l (long format) option.
find(1):
Added the -delete and -E (extended regex) options.
xargs(1):
Replaced with FreeBSD's while keeping our GNU compatible exit values.
sdiff(1):
Replaced by OpenBSD's
sdiff(1).
pax(1):
Added a -V flag for verbose summary without listing.
top(1):
Allow a single process to be selected by pid. Added a thread mode that displays LWPs.
scsictl(8):
Added a setspeed command.
split(1):
Added a new option
``-n chunk_count''
that splits the input into chunk_count smaller files.
df(1):
Fixed the -P option and added the -g (gigabytes) option.
wtf(6)
now searches pkgsrc's help database when called inside a package directory.
atactl(8):
Improved SATA support.
wlanctl(8):
Added a -p flag that only prints public nodes.
btconfig(8):
Added a new
``rssi''
option to toggle inquiry results with RSSI.
ifconfig(8):
Added
``list scan''
to ifconfig, which lists access points in the neighborhood.
newsyslog.conf(5)
gained a
``J''
flag to bzip2 logfiles.
fdisk(8)
now reports the first active partition.
bioctl(8)
was rewritten to handle new features like creating and removing hot-spares, pass-through disks and RAID volumes, start/stop consistency checks in volumes.
savecore(8)
now uses the raw device to read crashdumps.
make(1):
Implemented
``-dl''
(aka LOUD) to override
``@''
at the start of script lines.
monop(6):
The save and restore format changed, breaking compatibility with already broken previous save files.
iconv(1)
now allows SUSv3 syntax.
lint(1):
Added _Complex support.
ftp(1):
Added epsv6 and epsv to disable extended passive mode.
getent(1):
Added support for
``netgroup''
databases.
ypserv(8):
Disabled libwrap address to hostname lookups to avoid the chance of ypserv blocking for an extended period of time due to a long DNS timeout.
postfix(1):
Enabled LDAP support for tables.
amd(8):
Enabled LDAP support for maps.
newfs(8):
Added support for the
``t''
(terabytes) suffix.
grep(1):
A warning is now printed if
``-r''
is used without specifying an argument.
db(1):
Added support for encoding or decoding VIS_HTTPSTYLE, and for tuning the page size of the database.
daily.conf(5):
Added run_fsck_flags to allow passing extra options to the daily fsck -n.
sysinst(8)
now supports the Colemak and Dvorak keyboard layouts.
od(1)
Added support for the
``-A addressformat''
flag.
etcupdate(8):
Removed the
``-b binarydir''
and
``-s srcdir/etc''
options which were deprecated in NetBSD-4.0. Deprecate the
``-s tgz1:tgz2''
option; please use
``-s tgz1 -s tgz2''
instead.
postinstall(8):
Deprecated the
``-s tgz1:tgz2''
option; please use
``-s tgz1 -s tgz2''
instead.
sed(1):
Added the -r flag, which is an alias for -E, to be compatible with GNU sed.
patch(1):
Merged improved version from DragonFly. patch -b now behaves as specified by POSIX.
rc.conf(5):
ifconfig_xxN variables may now have multi-line values, just like /etc/ifconfig.xxN files, and semicolons may be used instead of line breaks.
ls(1):
-n now implies -l.
ps(1):
Added the -A option, to display information about all processes. Use
``O''
for LSONPROC like Solaris instead of bundling LSIDL, LSRUN, and LSONPROC to
``R''.
ksh(1):
Fixed POSIX mode interpretation of backslashes inside backquotes inside double quotes.
makefs(8):
Made the allow-multidot option for cd9660 useful.
restore(8)
now works on Linux dump volumes, by ignoring extended attribute records on these volumes.
rc.d(8)
script for
rndctl(8).
MAKEDEV(8)
now creates /dev rather than
init(8).
MAKEDEV(8)
now uses
mtree(8)
in preference to
pax(1)
and
mknod(8),
making node creation more efficient, and
mount_tmpfs(8)
in preference to
mount_mfs(8)
when creating a memory file system.
MAKEDEV.local(8)
can now use functions defined in
MAKEDEV(8).
Besides this list, there have also been innumerable bug fixes and miscellaneous enhancements.
In this release of NetBSD, the following software components have been removed from the system. Some were not useful anymore, or their utility did not justify the maintenance overhead. Others were not working properly and there was a lack of interest in fixing them.
Using block device nodes directly for I/O may cause a kernel
crash when the file system containing
/dev
is FFS and is mounted with -o log.
Workaround: use raw disk devices, or remount the file system
without -o log.
Occassionally, gdb may cause a process that is being debugged to hang when ``single stepped''. Workaround: kill and restart the affected process.
gdb cannot debug running threaded programs correctly.
Workaround: generate a core file from the program using
gcore(1)
and pass the core to gdb, instead of debugging the running program.
Statically linked binaries using pthreads are currently broken.
Certain early revision AMD Opteron and Athlon 64 processors contain a bug that may cause system instability when running with more than one CPU core active. An OS-level workaround for this issue has been prepared but was not ready in time for inclusion in NetBSD 5.0. It will be available as part of a later release in the 5.0 series.
Large filesystems (over 2TB) may sometimes falsely claim to be out of space. A fix for this is available, but was not made in time for 5.0. It will be available as part of a later release in the 5.0 series.
The sparc port does not have functional SMP support in this release.
mount(8))
will be removed in the next major release.
NetBSD
5.0
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.0 release is organized as follows:
.../NetBSD-5.0/
CHANGESCHANGES-5.0CHANGES.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.0 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:
BSDSUMCKSUMMD5SHA512SYSVSUMThe SHA512 digest is the safest checksum, followed by the MD5 digest, and finally the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of systems can check the integrity of the release files.
amiga
subdirectory of the distribution:
.../NetBSD-5.0/amiga/.
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.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
NetBSD
5.0
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 4.5.0. 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 -xzpf
command from the root directory (
/
) of your system.
NetBSD5.0 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 100 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.)
You will probably want to compile your own kernel.
GENERIC
is large and bulky in order to accommodate all people.
For example, most people's machines have an FPU, so you do not need the
bulky FPU_EMULATE option.
If you have less than 8 MB of fast memory, you should make your swap partition large, as your system will be a lot of swapping. In addition, do not place your swap partition onto a old small (and normally slow) disk!
If it's not on the above lists, there is no support for it in this release.
In particular, there are no drivers for: Blizzard III SCSI option,
Ferret SCSI, Oktagon SCSI.
Note that if you are installing or upgrading from writable media, it can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted.
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.
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 or DVD.
Likely locations are
binary/sets
and
amiga/binary/sets.
Proceed to the instructions on installation.
split(1)
command, running e.g.
split -b 235k base.tgz base.
to split the
base.tgz
file from
amiga/binary/sets
into files named
base.aa,
base.ab,
and so on.
Repeat this for all
set_name.tgz
files, splitting them into
set_name.xx
files.
Count the number of
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.190.13
and the IPv6 address is
2001:4f8:3:7:230:48ff:fe31:43f2
(as of April, 2009).
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 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 you don't have DHCP available on your network and 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
kern-GENERIC, 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-5.0
# cd amiga/binary
# tar -cf tape_device kern-GENERIC base etc
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.
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 that 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 now is partition your drives, creating at least root and swap partitions.
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 include (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:
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 mode.
It may also be possible to shutdown to single-user, providing that
the single-user mode processes are not using the swap partition.
On AmigaDOS, run 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 mode on the current NetBSD system, or use the shutdown now command to shutdown to single-user mode. 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, etc.)
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 of 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 will 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 asks 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, and it is up to you to configure the rest.
You may want to start by looking at
/etc/rc.conf.
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. 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,
along the lines of
ifconfig_le0="inet 192.0.2.123 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_le0="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.
amiga/5.0/All
subdir.
You can install them with the following commands under
sh(1):
# PKG_PATH=ftp://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/amiga/5.0/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/amiga/5.0/All
/pub/pkgsrc
directory.
If you would like to use such mirrors, you could also try the
/pub/NetBSD/packages/current-packages/NetBSD/amiga/5.0/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.0 (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 upgrade path to NetBSD5.0 documented here is by binary sets.
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.
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. This is
typically not more than a few megabytes.
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, begin by transferring 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 bootblocks 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 you for a command line. You have a few seconds 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 potentially 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, but normally you don't have to. Note that the upgrade-kit uses its 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 NetBSD5.0.
After a new kernel has been copied to your hard disk, your machine is a complete NetBSD5.0 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.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 5.0.
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.0 kernel defaults to
0
for
kern.no_sa_support,
which covers the first case.
However, please note that a full installation of 5.0
(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