About this Document............................................2
What is NetBSD?................................................2
Changes Between The NetBSD 4.0 and 5.0 Releases................3
General kernel..............................................3
Networking..................................................4
File systems................................................5
Security....................................................5
Drivers.....................................................6
Platforms..................................................11
Userland...................................................16
Components removed from NetBSD.............................21
Known Problems.............................................21
Features to be removed in a later release.....................21
The NetBSD Foundation.........................................22
Sources of NetBSD.............................................22
NetBSD 5.0 Release Contents...................................22
NetBSD/cats subdirectory structure.........................23
Binary distribution sets...................................23
NetBSD/cats System Requirements and Supported Devices.........25
Supported Chalice CATS devices.............................25
Supported Intel EBSA285 & Chalice CATS PCI devices.........25
Getting the NetBSD System on to Useful Media..................26
Preparing your System for NetBSD installation.................28
Available Boot Media.......................................28
Preparing the Bootable Media...............................28
Booting from CD-ROM........................................29
Installing the NetBSD System..................................29
Running the sysinst installation program...................29
Introduction............................................29
Possible hardware problems..............................29
General.................................................29
Quick install...........................................29
Booting NetBSD..........................................30
Network configuration...................................30
Installation drive selection and parameters.............31
Selecting which sets to install.........................31
Partitioning the disk...................................31
Preparing your hard disk................................31
Getting the distribution sets...........................32
Installation from CD-ROM................................32
Installation using ftp..................................32
Installation using NFS..................................32
Installation from an unmounted file system..............33
Installation from a local directory.....................33
Extracting the distribution sets........................33
Finalizing your installation............................33
Post installation steps.......................................34
Upgrading a previously-installed NetBSD System................36
Compatibility Issues With Previous NetBSD Releases............37
Issues affecting an upgrade from NetBSD 3.x releases.......37
Issues affecting an upgrade from NetBSD 4.x releases.......38
Using online NetBSD documentation.............................39
Administrivia.................................................39
Thanks go to..................................................40
We are........................................................40
Legal Mumbo-Jumbo.............................................47
The End.......................................................53
This document describes the installation procedure for
NetBSD
5.0 on the
cats
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.
cats
subdirectory of the distribution:
.../NetBSD-5.0/cats/.
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/kernel/cats/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.
This set also contains an a.out kernel named
/netbsd.aout
that your system may need to boot.
/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 cats 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.
NetBSD/cats 5.0 runs on a Chalice CATS systems from Simtec Electronics and Intel EBSA boards. The minimal configuration is said to require 8 MB of RAM and 100 MB of disk space, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space. 8 MB of RAM might actually allow you to run X and/or compile, but it won't be speedy. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU.
Drivers for hardware marked with ``[*]'' are not present in installation kernels.
Other PCI devices may be supported by Intel EBSA285 & Chalice CATS but
have not been tested.
You will need to create a CD with an install kernel on it or have another machine available to allow net booting.
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.
binary/sets
and
cats/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
cats/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 cats/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.
A cats machine usually needs little or no preparation before installing NetBSD, other than the usual, well advised precaution of backing up all data on any attached storage devices.
Booting from floppy disk is not currently supported.
Go to one of the
NetBSD
mirror sites and download CD-R image from the
pub/NetBSD/iso
directory.
http://www.NetBSD.org/mirrors/#iso
Get and install cdrecord.
This is available in the packages collection under pkgsrc/sysutils/cdrtools.
Systems not supported by the packages
collection should get it from the official website:
ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/cdrtools/README.html
http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html
# cdrecord -v speed=4 dev=/dev/cd1d output.iso
You will need to substitute the correct name of the disk image file,
speed for your CD writer, and the
correct device for your system (for i386 it would be
/dev/cd1d).
boot> boot cd0:/netbsd
Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it in hand when doing the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use.
Should you encounter hardware problems during installation, try rebooting after unplugging removable devices you don't need for installation. Non-removable devices can be disabled with userconf (use boot -c to enter it).
The following is a walk-through of the steps you will take while
getting
NetBSD
installed on your hard disk.
sysinst
is a menu driven
installation system that allows for some freedom in doing the
installation.
Sometimes, questions will be asked and in many cases
the default answer will be displayed in brackets
(``[ ]'')
after the question.
If you wish to stop the installation, you may press
CONTROL-C
at any time, but if you do, you'll have to begin the installation
process again from scratch by running the
/sysinst
program from the command prompt.
It is not necessary to reboot.
First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example.
.***********************************************.
* NetBSD-5.0 Install System *
* *
*>a: Install NetBSD to hard disk *
* b: Upgrade NetBSD on a hard disk *
* c: Re-install sets or install additional sets *
* d: Reboot the computer *
* e: Utility menu *
* x: Exit Install System *
.***********************************************.
root
and set a password for that account.
You are also advised to edit
/etc/rc.conf
to match your needs.
You may want to read the
boot messages, to notice your disk's name and capacity.
Its name will be something like
sd0
or
wd0
and the geometry will be
printed on a line that begins with its name.
As mentioned above, you may need your disk's geometry when creating
NetBSD's
partitions.
You will also need to know the name, to tell
sysinst
which disk to use.
The most important thing to know is that
wd0
is
NetBSD's
name for your first IDE disk,
wd1
the second, etc.
sd0
is your first SCSI disk,
sd1
the second, etc.
Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus.
If you do not intend to use networking during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu and select the Configure network option. If you only want to temporarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response when asked to provide a server.
To start the installation, select Install NetBSD to hard disk from the main menu.
The first thing is to identify the disk on which you want to
install
NetBSD.
sysinst
will report a list of disks it finds
and ask you for your selection.
You should see disk names like
wd0,
wd1,
sd0
or
sd1.
The next step is to choose which distribution sets you wish to install. Options are provided for full, minimal, and custom installations. If you choose sets on your own, base, etc, and a kernel must be selected.
You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, sysinst will check for the presence of other operating systems and you will be asked to confirm that you want to overwrite these.
The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a disklabel written to it, you can choose Use existing partition sizes. Otherwise, select Set sizes of NetBSD partitions.
After you have chosen your partitions and their sizes (or if you opted to use the existing partitions), you will be presented with the layout of the NetBSD disklabel and given one more chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose.
a/)
bcd-he
is the partition mounted on
/usr,
but this is historical practice and not a fixed value.
You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name.
You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, select yes.
The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key.
The NetBSD distribution consists of a number of sets that come in the form of gzipped tarfiles. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly.
For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM drive
(usually cd0),
and the directory name on the CD-ROM where the distribution files are.
sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets.
To be able to install using ftp, you first need to configure
your network setup if you haven't already done so.
sysinst
will do this for you, asking you
if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the ftp server.
sysinst will proceed to transfer all the default set files from the remote site to your hard disk.
To be able to install using NFS, you first need to configure
your network setup if you haven't already done so.
sysinst
will do this for you, asking you
if you want to use DHCP.
If you do not use DHCP, you can enter network configuration
details yourself.
If you do not have DNS set up for the machine that you
are installing on, you can just press
RETURN
in answer to this question, and DNS will not be used.
You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine.
If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server.
In order to install from a local file system, you will
need to specify the device that the file system resides
on
(for example sd1e)
the type of the file system,
and the directory on the specified file system where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory.
Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably on machines with slow graphics consoles or serial consoles. Alternatively, you can choose to see a progress bar. This is the preferred option as it shows progress without significantly slowing down the installation process.
After all the files have been extracted, the device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can then set a password for the "root" account, to prevent the machine from coming up without access restrictions.
Congratulations, you have successfully installed NetBSD 5.0.
To finalize the installation of NetBSD/cats certain parameters on the Cyclone firmware need to changed. The reason is that the Cyclone firmware is unable to boot anything other than an a.out format kernels.
Kernels created on a NetBSD/cats 5.0 system are natively ELF and converted to a.out. This conversion process loses the symbol information used for, amongst other things, kernel memory grovelers such as vmstat. The workaround to the problem is to provide both the native ELF kernel (with all the symbol information) and the a.out kernel. These are available as /netbsd and /netbsd.aout respectively. As the a.out format kernel is not named in such a way that the Cyclone firmware will automatically find it the following command should be issued as the firmware prompt.
boot> set boot wd0:/netbsd.aout
You can now reboot the machine and boot NetBSD from hard disk.
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_tlp0="inet 192.0.2.123 netmask 255.255.255.0"
or, if you have
myname.my.dom
in
/etc/hosts:
ifconfig_tlp0="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.
For the
savecore(8)
facility to work with the a.out and elf kernel images supplied with
cats installations you will need to set
savecore_flags="-z -N /netbsd"
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.
cats/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/cats/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/cats/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/cats/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 easiest way to upgrade to NetBSD 5.0 is with binaries, and that is the method documented here.
To do the upgrade, you must have one form of boot media available.
You must also have at least the
base
and
kern
binary distribution sets available.
Finally, you must have sufficient disk space available to install the
new binaries.
Since files already installed on the system are overwritten in place,
you only need additional free space for files which weren't previously
installed or to account for growth of the sets between releases.
If you have a few megabytes free on each of your root
(/)
and
/usr
partitions, you should have enough space.
Since upgrading involves replacing the kernel, boot blocks, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on the NetBSD partition or on another operating system's partition on your disk before beginning the upgrade process.
The upgrade procedure
is similar to an installation, but without the hard disk partitioning.
sysinst
will attempt to merge the settings stored in your
/etc
directory with the new version of
NetBSD.
Also, file systems are checked before unpacking the sets.
Fetching the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document for help.
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD
5.0
system.
However, that doesn't mean that you're finished with the upgrade process.
You will probably want to update the set of device
nodes you have in
/dev.
If you've changed the contents of
/dev
by hand, you will need to be careful about this, but if
not, you can just cd into
/dev,
and run the command:
# sh MAKEDEV all
Finally, you will want to delete old binaries that were part
of the version of
NetBSD
that you upgraded from and have since been removed from the
NetBSD
distribution.
Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 5.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