INSTALL.
ext,
where
ext
is one of
.ps
, .html
, .more
,
or
.txt
.
.ps
.html
.more
more(1)
and
less(1)
pager utility programs. This is the format in which the on-line
man
pages are generally presented.
.txt
You are reading the HTML version.
NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, The X Window System, and numerous other tools, all accompanied by full source code.
NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.
It is impossible to completely summarize the nearly two years of development that went into the NetBSD1.4.1 release. Some highlights include:
ftp(1)
client has been improved even further. See the man page for details.
wscons(4)
,
has been integrated into many ports.
usb(4)
for an overview.
nsswitch.conf(5)
functionality to the system to specify the search order for system databases.
syslogd(8)
now supports listening on multiple sockets, to make the
chrooting of servers easier.
As has been noted, there have also been innumerable bug fixes.
Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue.
As is usual between releases, the i386 port has had many improvements made to it -- too many to detail all of them here.
Numerous new drivers have been added. See the supported hardware list for details.
Some (but not all!) notable i386-specific improvements include:
NetBSD1.4 on i386 is, as usual, also fully backward compatible with old NetBSD i386 binaries, so you don't need to recompile all your local programs provided you set the appropriate binary compatibility options in your kernel configuration.
The i386 will be switching executable formats from a.out to ELF in the next release. The support for this has already been completed, but was judged too new to be included in NetBSD1.4.
The NetBSD Foundation will help improve the quality of NetBSD by:
We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.
We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.
We intend to continue our current practice of making the NetBSD-current development source available on a daily basis. In addition, we intend to provide Anonymous CVS access to the NetBSD source tree in the near future, so that anyone on the internet can examine the full NetBSD source code repository.
We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.
Above all, we hope to create a stable and accessible system, and to be
responsive to the needs and desires of
NetBSD
users, because it is for
and because of them that
NetBSD
exists.
If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org.
ftp.au.netbsd.org
RMIT University, Melbourne
ftp://ftp.au.netbsd.org/pub/NetBSD/
ftp2.au.netbsd.org
University of Queensland, Brisbane
ftp://ftp2.au.netbsd.org/pub/NetBSD/
ftp.at.netbsd.org
University of Technology, Vienna
ftp://ftp.at.netbsd.org/pub/NetBSD/
ftp.ravel.ufrj.br
Cidade Universitaria
ftp://ftp.ravel.ufrj.br/pub/NetBSD/
ftp.dk.netbsd.org
Aalborg University
ftp://ftp.dk.netbsd.org/pub/NetBSD/
ftp.fi.netbsd.org
The Finnish University and Research Network, Espoo
ftp://ftp.fi.netbsd.org/pub/NetBSD/
ftp.fr.netbsd.org
Paris University
ftp://ftp.fr.netbsd.org/pub/NetBSD/
ftp.de.netbsd.org
University of Trier
ftp://ftp.de.netbsd.org/pub/NetBSD/
ftp2.de.netbsd.org
University of Erlangen-Nuremberg
ftp://ftp2.de.netbsd.org/pub/NetBSD/
ftp.uni-regensburg.de
University of Regensburg
ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD/
ftp.jp.netbsd.org
Internet Research Institute Inc., Tokyo
ftp://ftp.jp.netbsd.org/pub/NetBSD/
core.ring.gr.jp
Electrotechnical Laboratory
ftp://core.ring.gr.jp/pub/NetBSD/
ftp.dti.ad.jp
Dream Train Internet Inc., Tokyo
ftp://ftp.dti.ad.jp/pub/NetBSD/
mirror.nucba.ac.jp
Nagoya University of Commerce and Business
ftp://mirror.nucba.ac.jp/mirror/NetBSD/
netbsd.tohoku.ac.jp
Tohoku University, Sendai
ftp://netbsd.tohoku.ac.jp/NetBSD/
ring.asahi-net.or.jp
ASAHI Net
ftp://ring.asahi-net.or.jp/pub/NetBSD/
ftp.nl.netbsd.org
University of Amsterdam
ftp://ftp.nl.netbsd.org/pub/NetBSD/
ftp.no.netbsd.org
Bergen IT Consult AS
ftp://ftp.no.netbsd.org/pub/NetBSD/
ftp.ntnu.no
Norwegian University of Science and Technology
ftp://ftp.ntnu.no/pub/NetBSD/
ftp.ru.netbsd.org
Landau Institute for Theoretical Physics, Chernogolovka
ftp://ftp.ru.netbsd.org/pub/NetBSD/
ftp.stacken.kth.se
Royal Institute of Technology, Stockholm
ftp://ftp.stacken.kth.se/pub/OS/NetBSD/
ftp.sunet.se
Swedish University NETwork, Uppsala
ftp://ftp.sunet.se/pub/os/NetBSD/
ftp.uk.netbsd.org
Domino, London
ftp://ftp.uk.netbsd.org/pub/NetBSD/
sunsite.org.uk
ftp://sunsite.org.uk/packages/netbsd/
ftp.netbsd.org
Silicon Valley, California
ftp://ftp.netbsd.org/pub/NetBSD/
ftp.cs.umn.edu
University of Minnesota
ftp://ftp.cs.umn.edu/pub/NetBSD
ftp.eecs.umich.edu
University of Michigan, Ann Arbor
ftp://ftp.eecs.umich.edu/pub/NetBSD/
ftp.iastate.edu
Iowa State University
ftp://ftp.iastate.edu/pub/netbsd/
ftp.op.net
ftp://ftp.op.net/pub/NetBSD/
ftp.stacken.kth.se
Royal Institute of Technology, Stockholm
AFS path: /afs/stacken.kth.se/ftp/pub/OS/NetBSD
ftp.iastate.edu
Iowa State University
AFS path: /afs/iastate.edu/public/ftp/pub/netbsd
sunsite.org.uk
Instructions: mount -o ro sunsite.org.uk:/public/packages/netbsd /mnt
sup.au.netbsd.org
RMIT University, Melbourne
Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup
sup.fr.netbsd.org
Paris University
Instructions: Similar to sup.netbsd.org
sup.de.netbsd.org
University of Trier
Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example
sup.jp.netbsd.org
Internet Research Institute Inc., Tokyo
Instructions: ftp://sup.jp.netbsd.org/pub/NetBSD/sup/README.sup
sup.no.netbsd.org
Norwegian University of Science and Technology
Instructions: See /usr/src/share/examples/supfiles/sup.no.netbsd.org
sup.uk.netbsd.org
Domino, London
Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup
sup.netbsd.org
Silicon Valley, California
Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup
ftp.cs.umn.edu
University of Minnesota
Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG
www.au.netbsd.org
RMIT University, Melbourne
http://www.au.netbsd.org/
www.at.netbsd.org
University of Technology, Vienna
http://www.at.netbsd.org/
www.fi.netbsd.org
Global Wire Oy, Lappeenranta
http://www.fi.netbsd.org/
www.fr.netbsd.org
Paris University
http://www.fr.netbsd.org/
www.de.netbsd.org
http://www.de.netbsd.org/
www.jp.netbsd.org
Internet Research Institute Inc., Tokyo
http://www.jp.netbsd.org/
www.no.netbsd.org
Bergen IT Consult AS
http://www.no.netbsd.org/
www.netbsd.org
Western Washington State University
http://www.netbsd.org/
www2.us.netbsd.org
New York
http://www.us.netbsd.org/
.../NetBSD-1.4.1/
BUGS
CHANGES
LAST_MINUTE
MIRRORS
README.files
TODO
patches/
source/
In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD1.4.1 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly.
The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows:
Most of the above source sets are located in the
source/sets
subdirectory of the distribution tree. The secrsrc.tgz set is
contained in the
source/security
subdirectory. This set, which is
available only to users in the United States and Canada, contains the
sources normally found in
/usr/src/domestic
- primarily kerberos and
other cryptographic security related software. (Remember, because of
United States law, it may not be legal to distribute this set to
locations outside of the United States and Canada.)
The source sets are distributed as compressed tar files. They may be
unpacked into
/usr/src
with the command:
cat set_name.tgz | gunzip | (cd /; tar xpf - )
The sets/Split/
and security/Split/
subdirectories contain split
versions of the source sets for those users who need to load the
source sets from floppy or otherwise need a split distribution. The
split sets are are named "set_name.xx" where "set_name" is the
distribution set name, and "xx" is the sequence number of the file,
starting with "aa" for the first file in the distribution set, then
"ab" for the next, and so on. All of these files except the last one
of each set should be exactly 240,640 bytes long. (The last file is
just long enough to contain the remainder of the data for that
distribution set.)
The split distributions may be reassembled and extracted with
cat as follows:
cat set_name.?? | gunzip | (cd /; tar xpf - )
In each of the source distribution set directories, there is a file
named
CKSUMS
which contains the checksums of the files in that
directory, as generated by the
cksum(1)
utility. You can use cksum to
check the integrity of the archives, if you suspect that one of the
files is corrupt and have access to a cksum binary. Checksums based on
other algorithms may also be present - see the
release(7)
man page for details.
i386
subdirectory of the distribution:
.../NetBSD-1.4.1/i386/
INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
.more
file contains underlined text using the
more(1)
conventions for indicating italic and bold display.
binary/
sets/
security/
installation/
floppy/
misc/
i386/binary/sets
subdirectory
of the
NetBSD1.4.1
distribution tree, and are as follows:
/usr/include
)
and the various system libraries (except the shared
libraries, which are included as part of the
base
set). This set also includes the manual pages for
all of the utilities it contains, as well as the
system call and library manual pages.
/etc
and in several other places. This set
must
be installed if you are installing the system from scratch, but should
not
be used if you are upgrading. (If you are upgrading,
it's recommended that you get a copy of this set and
carefully
upgrade your configuration files by hand.)
/netbsd
.
You must
install this distribution set.
/usr/share
.
groff(1)
,
all related programs, and their manual pages.
The i386 security distribution set is named
secr and can be found in the
i386/binary/security
subdirectory of the
NetBSD1.4.1
distribution tree. It contains security-related binaries
which depend on cryptographic source code. You do not need this
distribution set to use encrypted passwords in your password file; the
base
distribution includes a crypt library which can perform
only the one-way encryption function. The security distribution
includes a version of the Kerberos IV network security system, and
a Kerberized version of
telnet(1)
program. The secr
distribution set can be found only on those sites which carry the complete
NetBSD
distribution and which can legally obtain it. Because
of United States law, it may not be legal to distribute this set
to locations outside of the United States and Canada.
798K gzipped, 2.4M uncompressed
NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.3.1. Binary sets for the X Window system are distributed with NetBSD. The sets are:
The i386 binary distribution sets are distributed as gzipped tar files
named with the extension
.tgz, e.g.
base.tgz
.
They are also
available in split form - catted together, the members of a split set
form a gzipped tar file.
The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are /-relative and therefore are extracted below the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar xfp command from /.
All BSDSUM
files are historic
BSD checksums for the various files
in that directory, in the format produced by the command:
cksum -o 1 file
All CKSUM files are
POSIX
checksums for the various files in that
directory, in the format produced by the command:
cksum file.
All MD5 files are
MD5
digests for the various files in that
directory, in the format produced by the command:
cksum -m file.
All SYSVSUM
files are historic AT&T System V
UNIX
checksums for the various files in that directory, in the format produced by
the command:
cksum -o -2 file.
The MD5 digest is the safest checksum, followed by the POSIX
checksum. The other two checksums are provided only to ensure
that the widest possible range of system can check the integrity
of the release files.
NetBSD1.4.1 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems with 386-family processors, with or without math coprocessors. It does NOT support MCA systems, such as some IBM PS/2 systems. The minimal configuration is said to require 4M of RAM and 50M 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 (the unpacked binary distribution, without sources, requires at least 65M without counting space needed for swap space, etc), and to run X or compile the system, more RAM is recommended. (4M of RAM will actually allow you to run X and/or compile, but it won't be speedy. Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.)
Supported devices include:
Floppy controllers.
MFM, ESDI, IDE, and RLL hard disk controllers.
There is complete support (including IDE DMA or Ultra-
DMA) for the following PCI controllers:
- Acer labs M5229 IDE Controller
- CMD Tech PCI0643 and PCI0646 IDE Controllers
- Contaq Microsystems/Cypress CY82C693 IDE Controller
- Intel PIIX, PIIX3 and PIIX4 IDE Controllers
- Silicon Integrated System 5597/5598 IDE controller
- VIA Technologies VT82C586 and VT82C586A IDE Controllers
Most of these controllers are only available in
multifunction PCI chips.
Other PCI IDE controllers are supported, but
performances may not be optimal.
ISA, ISA plug and play and PCMCIA IDE controllers
are supported as well.
SCSI host adapters
Adaptec AHA-154xA, -B, -C, and -CF
Adaptec AHA-174x
Adaptec AIC-6260 and AIC-6360 based boards, including
the Adaptec AHA-152x, Adaptec APA-1460 (PCMCIA),
and the SoundBlaster SCSI host adapter. (Note
that you cannot boot from these boards if they
do not have a boot ROM; only the AHA-152x and
motherboards using this chip are likely to be
bootable, consequently.)
Adaptec AHA-2x4x[U][W] cards and some onboard PCI designs
using the AIC-7770, AIC-7850, AIC-7860, AIC-7870, or
AIC-7880 chip.
Adaptec AHA-3940[U][W] cards [b]
AdvanSys ABP-9x0[U][A] cards
AdvanSys ABP-940UW[68], ABP-970UW[68] ASB3940UW-00 cards
AMD PCscsi-PCI (Am53c974) based SCSI adapters, including
Tekram DC-390
BusLogic 54x (Adaptec AHA-154x clones)
BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series
of BusLogic SCSI adapters)
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
Seagate/Future Domain ISA SCSI adapter cards, including
ST01/02
Future Domain TMC-885
Future Domain TMC-950
Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters:
Acculogic PCIpport
ASUS SC-200 (requires NCR BIOS on motherboard to
boot from disks)
ASUS SC-875
ASUS SP3[G] motherboard onboard SCSI
DEC Celebris XL/590 onboard SCSI
Diamond FirePort 40
Lomas Data SCSI adapters
NCR/SYM 8125 (and its many clones; be careful, some
of these cards have a jumper to set
the PCI interrupt; leave it on INT A!)
Promise DC540 (a particularly common OEM model of
the SYM 8125)
Tekram DC-390U/F
Tyan Yorktown
Symbios Logic (NCR) 5380/53C400-based ISA SCSI host adapters [*] [+]
Ultrastor 14f, 34f, and (possibly) 24f
Western Digital WD7000 SCSI and TMC-7000 host adapters
(ISA cards only)
MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not
all of the display adapters NetBSD/i386 can work with
are supported by X. See the XFree86 FAQ for more
information.)
Serial ports:
8250/16450-based ports
16550/16650/16750-based ports
AST-style 4-port serial cards [*]
BOCA 8-port serial cards [*]
IBM PC-RT 4-port serial cards [*]
Single-port Hayes ESP serial cards [*]
Cyclades Cyclom-Y serial cards [*] [+]
PCI universal communication cards
Parallel ports. [*] [+]
Ethernet adapters:
AMD LANCE and PCnet-based ISA Ethernet adapters [*], including:
Novell NE1500T
Novell NE2100
Kingston 21xx
Digital EtherWORKS II ISA adapters (DE200/DE201/DE202)
AMD PCnet-based PCI Ethernet adapters, including:
Addtron AE-350
BOCALANcard/PCI
SVEC FD0455
X/Lan Add-On Adapter
IBM #13H9237 PCI Ethernet Adapter
AT&T StarLAN 10, EN100, and StarLAN Fiber
3COM 3c501
3COM 3c503
3COM 3c505 [*]
3COM 3c507
3COM 3c509, 3c579, 3c589, and 3c59X
3COM 3c90X (including 3c905B)
Digital DC21x4x-based PCI Ethernet adapters, including:
ASUS PCI-DEC100TX+
Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX)
Cogent EM964 [b]
Cogent EM4XX [b]
Compex Readylink PCI
DANPEX EN-9400P3
Digital Celebris GL, GLST on-board ethernet
Digital (DEC) PCI Ethernet/Fast Ethernet adapters (all)
DLINK DFE500-TX
JCIS Condor JC1260
Linksys PCI Fast Ethernet
SMC EtherPower 10, 10/100 (PCI only!)
SMC EtherPower^2 [b]
SVEC PN0455
SVEC FD1000-TP
Znyx ZX34X
Digital EtherWORKS III ISA adapters (DE203/DE204/DE205) [*]
Digital DEPCM-BA (PCMCIA) and DE305 (ISA) NE2000-compat. cards
BICC Isolan [* and not recently tested]
Efficient Networks EN-155 and Adaptec AIC-590x ATM interfaces
Essential Communications Hippi (800Mbit/s)
Fujitsu MB86960A/MB86965A based cards:
Fujitsu FMV-180 series
Allied-Telesis AT1700 series
Allied-Telesis RE2000 series
Intel EtherExpress 16
Intel EtherExpress PRO/10
Intel EtherExpress 100 Fast Ethernet adapters
Novell NE1000, NE2000 (ISA, PCI, PCMCIA, ISA PnP)
SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards
SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards)
SMC 91C9x-based boards (ISA and PCMCIA)
SMC EPIC/100 Fast Ethernet boards:
SMC Etherpower-II
Texas Instruments ThunderLAN based ethernet boards:
Compaq Netelligent 10/100 TX
Compaq ProLiant Integrated Netelligent 10/100 TX
Compaq Netelligent 10 T (untested)
Compaq Integrated NetFlex 3/P
Compaq NetFlex 3/P in baseboard variant (the PCI
(variant doesn't use the same chip !).
Compaq Dual Port Netelligent 10/100 TX (untested)
Compaq Deskpro 4000 5233MMX (untested)
Texas Instruments TravelMate 5000 series laptop
docking station Ethernet board
VIA VT3043(Rhine) and VT86C100A(Rhine-II) based ethernet boards [*] [+]:
D-Link DFE530TX
FDDI adapters:
Digital DEFPA PCI FDDI adapters [*] [+]
Digital DEFEA EISA FDDI adapters [*] [+]
Token-Ring adapters:
IBM Token-Ring Network PC Adapter [+]
IBM Token-Ring Network PC Adapter II [+]
IBM Token-Ring Network Adapter/A [+]
IBM Token-Ring Network 16/4 Adapter [+]
IBM Token-Ring Network 16/4 Adapter/A [+]
IBM 16/4 ISA Adapter [+]
IBM Auto 16/4 Token-Ring ISA Adapter [+]
3COM 3C619 TokenLink [+]
3COM 3C319 TokenLink Velocity [+]
High Speed Serial:
LAN Media Corporation SSI/LMC10000 (up to 10Mbps) [*] [+]
LAN Media Corporation HSSI/LMC5200 [*] [+]
LAN Media Corporation DS3/LMC5245 [*] [+]
Tape drives:
Most SCSI tape drives
QIC-02 and QIC-36 format (Archive- and Wangtek-
compatible) tape drives [*] [+]
CD-ROM drives:
Non-IDE Mitsumi CD-ROM drives [*] [+]
[Note: The Mitsumi driver device probe is known
to cause trouble with several devices!]
Most SCSI CD-ROM drives
Most ATAPI CD-ROM drives.
[ Note: Some low-priced IDE CDROM drives are known
for being not or not fully ATAPI compliant, and thus
requires some hack (generally an entry to a quirk
table) to work with NetBSD.]
Mice:
"Logitech"-style bus mice [*] [+]
"Microsoft"-style bus mice [*] [+]
"PS/2"-style mice [*] [+]
Serial mice (no kernel support necessary)
Sound Cards:
SoundBlaster, SoundBlaster Pro, SoundBlaster 16 [*] [+]
Gravis Ultrasound and Ultrasound Max [*] [+]
Windows Sound System [*] [+]
[The following drivers are not extensively tested]
Personal Sound System [*] [+]
ProAudio Spectrum [*] [+]
Gravis Ultrasound Plug&Play [*] [+]
Ensoniq AudioPCI [*] [+]
Yamaha OPL3-SA3 [*] [+]
Aria based sound cards [*] [+]
S3 SonicVibes [*] [+]
ESS Technology ES1777/1868/1869/1887/1888/888 audio [*] [+]
Game Ports (Joysticks). [*] [+]
Miscellaneous:
Advanced power management (APM) [*]
Universal Serial Bus:
UHCI host controllers [*] [+]
OHCI host controllers [*] [+]
Hubs [*] [+]
Keyboards using the boot protocol [*] [+]
Mice [*] [+]
Printers [*] [+]
Generic support for HID devices [*] [+]
Drivers for hardware marked with "[*]" are NOT present in kernels on the distribution floppies. Except as noted above, all drivers are present on all disks. Also, at the present time, the distributed kernels support only one SCSI host adapter per machine. NetBSD normally allows more, though, so if you have more than one, you can use all of them by compiling a custom kernel once NetBSD is installed.
Support for devices marked with "[+]" IS included in the "generic" kernels, although it is not in the kernels which are on the distribution floppies.
Support for devices marked with "[b]" requires BIOS support for PCI-PCI bridging on your motherboard. Most reasonably modern Pentium motherboards have this support, or can acquire it via a BIOS upgrade.
Hardware the we do NOT currently support, but get many questions about:
We are planning future support for many of these devices.
To be detected by the distributed kernels, the devices must
be configured as follows:
Parallel ports lpt0 0x378 7 [interrupt-driven or polling]
lpt1 0x278 [polling only]
lpt2 0x3bc [polling only]
Floppy controller
fdc0 0x3f0 6 2 [supports two disks]
AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters
aha0 0x330 any any
aha1 0x334 any any
AHA-174x SCSI host adapters (in enhanced mode)
ahb0 any any any
AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters
aic0 0x340 11 6
AHA-2X4X or AIC-7XXX-based SCSI host adapters [precise list: see NetBSD
ahc0 any any any System Requirements and
Supported Devices]
AdvanSys ABP-9x0[U][A] SCSI host adapters
adv0 any any any
AdvanSys ABP-940UW[68], ABP-970UW[68], ASB3940UW-00 SCSI host adapters
adw0 any any any
AMD PCscsi-PCI based SCSI host adapters
pcscp0 any any any
BusLogic BT445, BT74x, or BT9xx SCSI host adapters
bha0 0x330 any any
bha1 0x334 any any
Symbios Logic/NCR 5380/53C400 based ISA SCSI host adapters
nca0 0x360 15
nca1 5 iomem 0xd8000
Symbios Logic/NCR 53C8xx based PCI SCSI host adapters
ncr0 any any any
Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters
uha0 0x330 any any
uha1 0x340 any any
Western Digital WD7000 based ISA SCSI host adapters
wds0 0x350 15 6
wds1 0x358 11 5
PCI IDE hard disk controllers
pciide0 any any any [supports four devices]
MFM/ESDI/IDE/RLL hard disk controllers
wdc0 0x1f0 14 [supports two devices]
wdc1 0x170 15 [supports two devices]
ATA disks wd0, wd1, ...
SCSI and ATAPI disks sd0, sd1, ...
SCSI tapes st0, st1, ...
SCSI and ATAPI CD-ROMs cd0, cd1, ...
For each SCSI and IDE controller found, the SCSI or ATA(PI) devices
present on the bus are probed in increasing id order for SCSI and
master/slave order for ATA(PI). So the first SCSI drive found will
be called sd0, the second sd1, and so on ...
3Com 3c501 Ethernet cards
el0 0x300 9
3Com 3c503 Ethernet cards
ec0 0x250 9 iomem 0xd8000
3Com 3c505 Ethernet cards
eg0 0x280 9
3Com 3c507 Ethernet cards
ef0 0x360 7 iomem 0xd0000
Novell NE1000, or NE2000 Ethernet boards
ne0 0x280 9
ne1 0x300 10
SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards
we0 0x280 9 iomem 0xd0000
we1 0x300 10 iomem 0xcc000
3COM 3c509 or 3COM 3c579 Ethernet boards
ep0 any any
3COM 3x59X PCI Ethernet boards
ep0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
3COM 3x90X PCI Ethernet boards
ex0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
AT&T StarLAN 10, EN100, or StarLAN Fiber, 3COM 3c507 or Intel
EtherExpress 16 Ethernet boards
ie0 0x360 7 iomem 0xd0000
ie1 0x300 10 iomem 0xd0000
Intel EtherExpress PRO 10 ISA
iy0 0x360 any
Intel EtherExpress 100 Fast Ethernet adapters
fxp0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
SMC91C9x based Ethernet cards
sm0 0x300 10
PCnet-PCI based Ethernet boards; see above for partial list
le0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
DC21x4x based Ethernet boards; see above for partial list
de0 any any [you must assign an interrupt in your
PCI BIOS, or let it do so for you]
Digital EtherWORKS III (DE203/DE204/DE205)
lc0 any any
Qlogic ISP [12]0x0 SCSI/FibreChannel boards
isp0 any any
Efficient Networks EN-155 and Adaptec AIC-590x ATM interfaces
en0 any any
SMC EPIC/100 Fast Ethernet boards:
epic0 any any
Texas Instruments ThunderLAN based ethernet boards:
tl0 any any
VIA VT3043(Rhine) and VT86C100A(Rhine-II) based ethernet boards
vr0 any any
Device Name Port IRQ DRQ Misc
------ ---- ---- --- --- ----
Serial ports com0 0x3f8 4 [8250/16450/16550/clones]
com1 0x2f8 3 [8250/16450/16550/clones]
com2 0x3e8 5 [8250/16450/16550/clones]
Installation is supported from several media types, including:
No matter which installation medium you choose, you'll need to have a floppy disk (either 1.2M or 1.44M will work). You'll put the boot floppy image ("boot1.fs" and "boot2.fs" for 1.44M floppies, "boot-tiny.fs" for 1.2M floppies) onto this disk, which contains software to install or upgrade your NetBSD system. Note that the "boot-tiny.fs" image is tailored for "small" machines, this install image does not have drivers for PCI, PCMCIA, EISA or SCSI (i.e. ISA-only), but can be used on machines with only 4MB of RAM.
If you are using a UN*X-like system to write the floppy images to
disks, you should use the
dd
command to copy the file system image(s)
(.fs file) directly to the raw floppy disk. It is suggested that you
read the
dd(1)
manual page or ask your system administrator to determine the correct
set of arguments to use; it will be slightly different from system to
system, and a comprehensive list of the possibilities is beyond the
scope of this document.
If you are using
DOS
to write the floppy image(s) to floppy disk, you should use the
Note that, when installing or upgrading, the floppy can be
write-protected if you wish. These systems mount ramdisks as their
root file systems once booted, and will not need to write to the
floppy itself at any time -- indeed, once booted, the floppy may be
removed from the disk drive.
Obviously, the steps necessary to prepare the distribution sets for
installation or upgrade depend on which installation medium you
choose. The steps for the various media are outlined below.
To install or upgrade
NetBSD
using
DOS
floppies, you need to do the following:
Once you have the files on
DOS
disks, you can start the actual installation or upgrade process.
To install or upgrade
NetBSD
using NFS, you must do the following:
Once the
NFS
server is set up properly and you have the
information mentioned above, you can start the actual
installation or upgrade process.
To install or upgrade
NetBSD
by using FTP to get the installation
sets, you must do the following:
Once you have this information, you can proceed to the actual
installation or upgrade.
If you are upgrading
NetBSD,
you also have the option of installing
NetBSD
by putting the new distribution sets somewhere in your existing
file system, and using them from there. To do that, you must do the
following:
Once you have done this, you can proceed to the next step in
the upgrade process, actually upgrading your system.
First and foremost, before beginning the installation process,
make sure you have a reliable backup
of any data on your hard disk that you
wish to keep. Mistakes in partitioning your hard disk may lead
to data loss.
Before you begin, you should be aware of the geometry issues that may
arise in relation to your hard disk. First of all, you should know
about sector size. You can count on this to be 512 bytes; other sizes
are rare (and currently not supported). Of particular interest are
the number of sectors per track, the number of tracks per cylinder
(also known as the number of heads), and the number of cylinders.
Together they describe the disk geometry.
The
BIOS
has a limit of 1024 cylinders and 63 sectors per track for
doing
BIOS
I/O. This is because of the old programming interface
to the
BIOS
that restricts these values. Most of the big disks
currently being used have more than 1024 real cylinders. Some have
more than 63 sectors per track. Therefore, the
BIOS
can be instructed
to use a fake geometry that accesses most of the disk and the fake
geometry has less than or equal to 1024 cylinders and less than or
equal to 63 sectors. This is possible because the disks can be
addressed in a way that is not restricted to these values, and the
BIOS
can internally perform a translation. This can be activated
in most modern BIOSes by using
Large
or
LBA
mode for the disk.
NetBSD
does not have the mentioned limitations with regard to the
geometry. However, since the
BIOS
has to be used during startup,
it is important to know about the geometry the
BIOS
uses. The
NetBSD
kernel should be on a part of the disk where it can be loaded using the
BIOS,
within the limitations of the
BIOS
geometry. The install program will check this for you, and
will give you a chance to correct this if this is not the case.
If you have not yet installed any other systems on the hard disk
that you plan to install
NetBSD
on, or if you plan to use the
disk entirely for
NetBSD,
you may wish to check your
BIOS
settings for the 'Large' or 'LBA' modes, and activate
them for the hard disk in question. While they are not needed
by
NetBSD
as such, doing so will remove the limitations mentioned
above, and will avoid hassle should you wish to share the disk with
other systems. Do
not
change these settings if you already have
data on the disk that you want to preserve!
In any case, it is wise to check your the
BIOS
settings for the
hard disk geometry before beginning the installation, and write
them down. While this should usually not be needed, it enables
you to verify that the install program determines these values
correctly.
The geometry that the
BIOS
uses will be referred to as the
BIOS
geometry,
the geometry that
NetBSD
uses is the
real geometry.
It is
important
that
Using
sysinst,
installing
NetBSD
is a relatively easy process. You
still should read this document and have it in hand when doing the
installation process. This document tries to be a good guideline
for the installation and as such covers many details to be completed.
Do not let this discourage you, the install program is not hard
to use.
There is a serious bug that may make installation of
NetBSD
on
PCMCIA
machines difficult. This bug does not make
use
of
PCMCIA
difficult once a machine is installed. If you do not have
PCMCIA
on your
machine
[PCMCIA]
is only really used on laptop machines), you
can skip this section, and ignore the
``[PCMCIA]''
notes.
This will explains how to work around the installation problem.
What is the bug: The kernel keeps careful track of what interrupts
and i/o ports are in use during autoconfiguration. It then allows
the
PCMCIA
devices to pick unused interrupts and ports.
Unfortunately, not all devices are included in the
This problem will impact some, but not all, users of
PCMCIA.
If this bug is affecting you, watch the
[PCMCIA]
notes that will appear in this document.
If the kernel by default allocates an interrupt for PCMCIA which is
allocated to other (typically undetected) hardware, you may use a
workaround by booting the install kernel with "boot -d" to drop into
DDB (the in-kernel debugger) and set pcic_isa_intr_alloc_mask to mask
out the offending interrupt before continuing. By default the kernel
masks out IRQ 10, and the corresponding mask is 0xfbff.
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 hit Control-C
at any time, but if you do, you'll have to begin the installation
process again from scratch.
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 section 3. This section
describes a basic installation, using a CD-ROM install as
an example.
Boot your machine using the boot floppy. The boot loader will
start, and will print a countdown and begin booting.
If the boot loader messages do not appear in a reasonable
amount of time, you either have a bad boot floppy or a
hardware problem. Try writing the install floppy image to
a different disk, and using that.
If that doesn't work, try booting after disabling your CPU's
internal and external caches (if any). If it still doesn't
work,
NetBSD
probably can't be run on your hardware. This can
probably be considered a bug, so you might want to report it.
If you do, please include as many details about your system
configuration as you can.
It will take a while to load the kernel from the floppy,
probably around a minute or so, then, the kernel boot messages
will be displayed. This may take a little while also, as
NetBSD
will be probing your system to discover which hardware devices are
installed.
You may want to read the
boot messages, to notice your disk's name and geometry. Its name
will be something like
Note that, once the system has finished booting, you need not
leave the floppy in the disk drive.
Earlier version of
the
NetBSD
install floppies mounted the floppy as the system's
root partition, but the new installation floppies use a
ramdisk file system and are no longer dependent on the floppy
once it has booted.
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 will not use network operation during the installation,
but you do want your machine to be configured for networking once
it is installed, you should first go to the utilities menu, and select
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 Domain Name Service (DNS),
you can give an empty response in reply to answers relating to
this.
To start the installation, select the menu option to install
NetBSD
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. Depending on how many disks
are found, you may get a different message. You should see
disk names like
sysinst
next tries to figure out the real and BIOS geometry
of your disk. It will present you with the values it found,
if any, and will give you a chance to change them.
Next, depending on whether you are using a
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,
it will be checked if there are already other
systems present on the disk, and you will be asked to confirm
whether you want to overwrite these.
If you want to use the entire disk for
NetBSD,
you can skip
the following section and go to
Editing the
NetBSD
disklabel.
First, you will be prompted to specify the units of size
that you want to express the sizes of the partitions in.
You can either pick megabytes, cylinders or sectors.
After this, you will be presented with the current values
stored in the MBR, and will be given the opportunity to
change, create or delete partitions. For each partition
you can set the type, the start and the size. Setting the type to
unused
will delete a partition. You can
also mark a partition as active, meaning that this is
the one that the BIOS will start from at boot time.
Be sure to mark the partition you want to boot from as active!
After you are done editing the MBR, a sanity check
will be done, checking for partitions that overlap.
Depending on the BIOS capabilities of your machine and the
parameters of the NetBSD partition you have specified, you
may also be asked if you want to install newer bootcode in
your MBR. If you have multiple operating systems on the
disk that you are installing on, you will also be given
the option to install a bootselector, that will allow you
to pick the operating system to start up when your computer
is (re-)started.
If everything is ok, you can go on to the next step,
editing the
NetBSD
disklabel.
The partition table of the
NetBSD
part of a disk is called a
disklabel.
There are 3 layouts for the
NetBSD
part of the disk that you can pick from:
Standard, Standard with X
and
Custom.
The first two use a set of default
values (that you can change) suitable for a normal
installation, possibly including X. The last option
lets you specify everything yourself.
You will be presented with the current layout of the
NetBSD
disklabel, and given a 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.
You can also specify a partition as type
msdos.
This is useful if you share the disk with
MS-DOS
or Windows95;
NetBSD
is able to access the files on these partitions.
You can use the values from the MBR for the MS-DOS part
of the disk to specify the partition of type
msdos
(you don't have to do this now, you can always re-edit
the disklabel to add this once you have installed NetBSD).
Some partitions in the disklabel have a fixed purpose.
Partition
a
is always the root partition,
b
is the swap partition,
c
is the entire
NetBSD
part of the disk, and
d
is the whole disk. Partitions
e-h
are available
for other use. Traditionally,
e
is the partition mounted on the
You will then be asked to name your disk's disklabel. The
default response is
mydisk.
For most purposes this will be OK.
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, enter
The install program will now label your disk and make the file
systems you specified. The filesystems 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.
NOTE: In previous versions of
NetBSD,
the kernel from the
install floppy was copied onto the hard drive in a special
step. In the new install system, the kernel on the floppy is
unsuited to being copied onto the hard drive. Instead, a new set,
kern,
has been added which contains a generic kernel to
be unloaded onto the drive. So, you can not boot from your
hard drive yet at this point.
cat kern.* | tar vxzf -
Then halt the machine using the 'halt' command. Power
the machine down, and re-insert all the
PCMCIA
devices.
Remove any floppy from the floppy drive.
Start the machine up. After booting
NetBSD,
you will
be presented with the main
sysinst
menu. Choose the
option to re-install sets. Wait for the filesystem
checks that it will do to finish, and then proceed
as described below.
The
NetBSD
distribution consists of a number of
sets,
that come in the form of gzipped tarfiles. A few sets must be
installed for a working system, others are optional. At this
point of the installation, 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 section 9
To be able to install using ftp, you first need to configure
your network setup, if you haven't already at the start of
the install procedure.
sysinst
will do this for you, asking you
to provide some data, like IP number, hostname, etc. If you
do not have name service set up for the machine that you
are installing on, you can just press return in answer
to these questions, 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,
and the account name and password used to log into that
host using ftp. If you did not set up DNS when answering
the questions to configure networking, you will need to
specify an IP number 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 at the start of
the install procedure.
sysinst
will do this for you, asking you
to provide some data, like IP number, hostname, etc. If you
do not have name service set up for the machine that you
are installing on, you can just press return in answer
to these questions, 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 when answering the questions to
configure networking, you will need to specify an IP number
instead of a hostname for the NFS server.
When installing from a CD-ROM, you will be asked to specify
the device name for your CD-ROM player
(usually
sysinst
will then check if the files are indeed available
in the specified location, and proceed to the actual
extraction of the sets.
In order to install from a local filesystem, you will
need to specify the device that the filesystem resides
on
(for example
This option assumes that you have already done some preparation
yourself. The sets should be located in a directory on a
filesystem that is already accessible.
sysinst
will ask you
for the name of this directory.
After the install sets containing the
NetBSD
distribution
have been made available, you can either extract all the
sets (a full installation), or only extract sets that
you have selected. In the latter case you will be shown the
currently selected sets, and given the opportunity to select
the sets you want. Some sets always need to be installed
(kern, base and etc)
they will not be shown in this selection menu.
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, especially
on machines with slow graphics consoles or serial consoles.
After all the files have been extracted, all the necessary
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.
Congratulations, you have successfully installed
NetBSD1.4.1.
You can now reboot the machine, and boot from harddisk.
Once you've got the operating system running, there are a few
things you need to do in order to bring the system into a propperly
configured state, with the most important ones described below.
If you haven't done any configuration of
Other values that need to be set in
Other files in
After reboot, you can log in as
Use the
If you have installed the X window system, look at the files in
You will need to set up a configuration file, see
Don't forget to add
There is a lot of software freely available for Unix-based systems,
almost all of which can run on
NetBSD.
Modifications are usually needed to
when transferring programs between different Unix-like systems, so
the
NetBSD
packages collection incorporates any such
changes necessary to make that software run on
NetBSD,
and makes
the installation (and deinstallation) of the software packages
easy. There's also the option of building a package from source, in
case there's no precompiled binary available.
Precompiled binaries can be found at
ftp://ftp.netbsd.org/pub/NetBSD/packages/
Package sources for compiling packages can be obtained by
retrieving the file
ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz
and extracting it into
The upgrade to
NetBSD1.4.1
is a binary upgrade; it can be quite difficult
to advance to a later version by recompiling from source due primarily
to interdependencies in the various components.
To do the upgrade, you must have the boot floppy
available.
You must also have at least the
base and kern
binary distribution sets available, so that you can upgrade with them,
using one of the upgrade methods described above. Finally, you must
have sufficient disk space available to install the new binaries.
Since the old binaries are being overwritten in place, you only need
space for the new binaries, which weren't previously on the system.
If you have a few megabytes free on each of your root and
Since upgrading involves replacing the boot blocks on your
NetBSD
partition, 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.
The upgrade procedure using the
sysinst tool is similar to
an installation, but without the hard disk partitioning.
Another difference is that existing configuration files in
After a new kernel has been copied to your hard disk, your
machine is a complete
NetBSD1.4.1
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
You must also deal with certain changes in the formats of
some of the configuration files. The most notable change is
that the options given to many of the file systems in
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.
Documentation is available if you first install the manual
distribution set. Traditionally, the
``man pages''
(documentation) are denoted by
``
The section numbers group the topics into several categories, but three
are of primary interest: user commands are in section 1, file formats
are in section 5, and administrative information is in section 8.
The man
command is used to view the documentation on a topic, and is
started by entering
man[ section]
topic.
The brackets
[]
around the
section should not be entered, but rather indicate that the section is
optional. If you don't ask for a particular section, the topic with the
lowest numbered section name will be displayed. For instance, after
logging in, enter
If you are unsure of what man page you are looking for, enter
apropos subject-word
where
subject-word
is your topic of interest; a list of possibly
related man pages will be displayed.
There are various mailing lists set up to deal with comments and
questions about this release. Please send comments to:
netbsd-comments@NetBSD.ORG.
To report bugs, use the
Use of
There are also port-specific mailing lists, to discuss aspects of
each port of
NetBSD.
Use majordomo to find their addresses. If
you're interested in doing a serious amount of work on a specific
port, you probably should contact the "owner" of that port (listed
below).
If you'd like to help with this effort, and have an idea as to how
you could be useful, send us mail or subscribe to:
netbsd-help@NetBSD.ORG.
As a favor, please avoid mailing huge documents or files to these
mailing lists. Instead, put the material you would have sent up
for FTP somewhere, then mail the appropriate list about it, or, if
you'd rather not do that, mail the list saying you'll send the data
to those who want it.
for their ongoing work on BSD systems, support, and encouragement.
for answering lots of questions, fixing bugs, and doing the various work
they've done.
(in alphabetical order)
rawrite
utility, provided in the
i386/utilities
directory of the
NetBSD
distribution. It will write a file system image (.fs file) to a floppy
disk.
format/s
to format them. (If the floppies are bootable, then the
DOS
system
files that make them bootable will take up some space, and you
won't be able to fit as many distribution set parts per disk.)
If you're using floppies that are formatted for
DOS
by their
manufacturers, they probably aren't bootable, and you can use
them out of the box.
/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.)
/dev
on the floppy used for upgrades only knows about wd0, wd1, sd0, sd1
and sd2. If you have more than two IDE drives or more than
three SCSI drives, you should take care not to place the sets
on the high numbered drives.
Preparing your System for NetBSD Installation
Sysinst
will try to discover both the real geometry and
BIOS
geometry.
sysinst
know the proper
BIOS
geometry to be able
to get
NetBSD
to boot, regardless of where on your disk you put it.
It is less of a concern if the disk is going to be used entirely for
NetBSD.
If you intend to have several OSes on your disk, this becomes
a much larger issue.
Installing the NetBSD System
Running the Sysinst Installation Program
INSTALL
kernels in order to save space. Let's say your laptop has a
soundblaster device built in. The
INSTALL
kernel has no sound support. The
PCMCIA code might allocate your soundblaster's
IRQ and I/O ports to
PCMCIA
devices, causing them not to work. This
is especially bad if one of the devices in question is your
ethernet card.
cd \NetBSD-1.4.1\installation\misc
rawrite
When asked for a source filename, answer
..\floppy\boot1.fs for the first diskette and
..\floppy\boot2.fs for the second diskette
When asked for a destination drive answer
a
dd if=.../boot1.fs bs=18k of=/dev/rfd0a
root
,
and set a password for that account. You are also
advised to edit the file
/etc/rc.conf
to match your system needs.
/usr/X11R6/lib/X11/doc
.
Further information can be found on
http://www.xfree86.org/
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
on which disk
to install.
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.
wd0
,
wd1
,
sd0
,
or
sd1
.
wd
x
or
wd
x
disk,
you will either be asked for the type of disk
(wd
x)
you are
using or you will be asked if you want to specify a fake geometry
for your SCSI disk
(sd
x).
The types of disk are be
IDE, ST-506
or
ESDI.
If you're installing on an
ST-506
or
ESDI
drive, you'll be asked if your disk supports automatic sector forwarding.
If you are
sure
that it does, reply affirmatively. Otherwise, the install
program will automatically reserve space for bad144 tables.
/usr
directory, but this is historical practice, not a fixed value.
yes
at the prompt.
mount /dev/wd0a /mnt
cd /mnt
<repeat following 3 steps until all kern.* files are there>
mount -t msdos /dev/fd0a /mnt2
cp /mnt2/kern.* .
umount /mnt2
cd0
),
and the directory name on the CD-ROM where the distribution files are.
wd1e
)
the type of the filesystem,
and the directory on the specified filesystem where the sets are located.
sysinst
will then check if it
can indeed access the sets at that location.
Post installation steps
/etc/rc.conf
/etc/rc.conf
,
the system will drop you into single user mode on first reboot with the
message
/etc/rc.conf
is
not
configured.
Multiuser
boot
aborted.
and with the root filesystem mounted read-write. When the system
asks you to choose a shell, simply hit return to get to a
prompt. If you are asked for a terminal type, respond with
vt220
(or whatever is appropriate for your terminal type)
and hit return. At this point, you need to configure at least
one file in the
/etc
directory. Change to the
/etc
directory and take a look at the
/etc/rc.conf
file. Modify it to your tastes, making sure that you set
rc_configured=YES
so that your changes will be enabled and a multi-user boot can
proceed. If your
/usr
directory is on a separate partition
and you do not know how to use 'ed' or 'ex', you will have to mount your
/usr
partition to gain access to 'vi'. Do the following:
mount /usr
export TERM=vt220
If you have
/var
on a seperate partition, you need to repeat
that step for it. After that, you can edit
/etc/rc.conf
with
vi(1)
.
When you have finished, type
exit
at the prompt to
leave the single-user shell and continue with the multi-user boot.
/etc/rc.conf
for a networked environment are
hostname and possibly
defaultroute,
furthermore add an
ifconfig_int
for your interface
<int>,
along the lines of
ifconfig_de0="inet
123.45.67.89
netmask
255.255.255.0"
or, if you have
myname.my.dom in /etc/hosts
:
ifconfig_de0="inet
myname.my.dom
netmask
255.255.255.0"
To enable proper hostname resolution, you will also want to add an
/etc/resolv.conf
file or (if you are feeling a little more adventurous) run
named(8)
.
See
resolv.conf(5)
or
named(8)
for more information.
/etc
that are new to NetBSD 1.4 and may require modification or
setting up include
/etc/mailer.conf
,
/etc/nsswitch.conf
and
/etc/wscons.conf
.
root
at the login prompt. There
is no initial password, but if you're using the machine in a
networked environment, you should create an account for yourself
(see below) and protect it and the "root" account with good
passwords.
vipw(8)
command to add accounts to your system,
do not edit /etc/passwd
directly. See
adduser(8)
for more information on the process of how to add a new user to the system.
/usr/X11R6/lib/X11/doc
for information.
/usr/X11R6/lib/X11/XF86Config.eg
for an example. See
http://www.xfree86.org/
and the XFree86 manual page for more information.
/usr/X11R6/bin
to your path in your shell's dot file so that you have access to the X binaries.
/usr/pkgsrc
.
See
/usr/pkgsrc/README
then for more information.
/etc/localtime
symlink to the appropriate file under
/usr/share/zoneinfo
.
/etc/aliases
to forward root mail to the right place (run
newaliases(1)
afterwards.)
/etc/sendmail.cf
file will almost definitely need to be adjusted;
files aiding in this can be found in
/usr/share/sendmail
.
See the
README
file there for more information.
/etc/rc.local
to run any local daemons you use.
/etc
files are documented in section 5 of the manual; so just invoking
man filename
is likely to give you more information on these files.
Upgrading a previously-installed NetBSD System
/usr
partitions, you should have enough space.
/etc
are backed up and merged with the new files. Getting the binary
sets is done in the same manner as the installation procedure;
refer to the installation part of the document
for how to do this. Also, some sanity checks are done, i.e.
filesystems are checked before unpacking the sets.
/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
/etc/fstab
have changed, and some of the file
systems have changed names. To find out what the new options
are, it's suggested that you read the manual page
for the file systems' mount commands, for example
mount_nfs(8)
for NFS.
Compatibility Issues With Previous NetBSD Releases
Users upgrading from previous versions of
NetBSD
may wish to bear the
following problems and compatibility issues in mind when upgrading to
NetBSD1.4.1
/usr/include/machine
directory changed to a symbolic link in NetBSD 1.4.
# rm -r /usr/include/machine
to remove the old directory and it contents and reinstall the
comp
set.
Using online NetBSD documentation
name(section)
''.
Some examples of this are
intro(1)
,
man(1)
,
apropros(1)
,
passwd(1)
,
and
passwd(5)
.
man passwd
to read the documentation for
passwd(1)
.
To view the documentation for
passwd(5)
m
enter
man 5 passwd
instead.
Administrivia
If you've got something to say, do so! We'd like your input.
There are various mailing lists available via the mailing list
server at
majordomo@NetBSD.ORG.
To get help on using the mailing
list server, send mail to that address with an empty body, and it will
reply with instructions.
send-pr(1)
command shipped with
NetBSD,
and fill in as much information about the problem as you can. Good
bug reports include lots of details. Additionally, bug reports can
be sent by mail to:
netbsd-bugs@NetBSD.ORG.
send-pr(1)
is encouraged, however, because bugs reported with it
are entered into the
NetBSD
bugs database, and thus can't slip through
the cracks.
Thanks go to
Keith Bostic
Ralph Campbell
Mike Karels
Marshall Kirk McKusick
Mike Hibler
Rick Macklem
Jan-Simon Pendry
Chris Torek
Jason Birnschein
Jason Brazile
David Brownlee
Simon Burge
Dave Burgess
Ralph Campbell
Brian Carlstrom
James Chacon
Bill Coldwell
Charles Conn
Tom Coulter
Charles D. Cranor
Christopher G. Demetriou
Scott Ellis
Hubert Feyrer
Greg Gingerich
Guenther Grau
Ross Harvey
Charles M. Hannum
Michael L. Hitch
Jordan K. Hubbard
Scott Kaplan
Noah M. Keiserman
Chris Legrow
Neil J. McRae
Perry E. Metzger
Herb Peyerl
Mike Price
Thor Lancelot Simon
Bill Sommerfeld
Paul Southworth
Ted Spradley
Kimmo Suominen
Jason R. Thorpe
Steve Wadlow
(If you're not on that list and should be, tell us! We probably were
not able to get in touch with you, to verify that you wanted to be
listed.)
Advanced System Products, Inc.
Avalon Computer Systems
Bay Area Internet Solutions
Canada Connect Corporation
Demon Internet, UK
Digital Equipment Corporation
Easynet, UK
Free Hardware Foundation
Innovation Development Enterprises of America
Internet Software Consortium
MS Macro System GmbH, Germany
Numerical Aerospace Simulation Facility, NASA Ames Research Center
Piermont Information Systems Inc.
VMC Harald Frank, Germany
We are...
The NetBSD core group: | ||||||||
Paul Kranenburg | pk@NetBSD.ORG | |||||||
Scott Reynolds | scottr@NetBSD.ORG | |||||||
Christos Zoulas | christos@NetBSD.ORG | |||||||
| ||||||||
The portmasters (and their ports): | ||||||||
Mark Brinicombe | mark@NetBSD.ORG | arm32 | ||||||
Jeremy Cooper | jeremy@NetBSD.ORG | sun3x | ||||||
Ross Harvey | ross@NetBSD.ORG | alpha | ||||||
Ignatios Souvatzis | is@NetBSD.ORG | amiga | ||||||
Eduardo Horvath | eeh@NetBSD.ORG | sparc64 | ||||||
Paul Kranenburg | pk@NetBSD.ORG | sparc | ||||||
Anders Magnusson | ragge@NetBSD.ORG | vax | ||||||
Tsubai Masanari | tsubai@NetBSD.ORG | macppc | ||||||
Tsubai Masanari | tsubai@NetBSD.ORG | newsmips | ||||||
Minoura Makoto | minoura@NetBSD.ORG | x68k | ||||||
Phil Nelson | phil@NetBSD.ORG | pc532 | ||||||
Scott Reynolds | scottr@NetBSD.ORG | mac68k | ||||||
Darrin Jewell | dbj@NetBSD.ORG | next68k | ||||||
Gordon Ross | gwr@NetBSD.ORG | sun3, sun3x | ||||||
Kazuki Sakamoto | sakamoto@NetBSD.ORG | bebox | ||||||
Wolfgang Solfrank | ws@NetBSD.ORG | powerpc | ||||||
Jonathan Stone | jonathan@NetBSD.ORG | pmax | ||||||
Jason Thorpe | thorpej@NetBSD.ORG | hp300 | ||||||
Frank van der Linden | fvdl@NetBSD.ORG | i386 | ||||||
Leo Weppelman | leo@NetBSD.ORG | atari | ||||||
Steve Woodford | scw@NetBSD.ORG | mvme68k | ||||||
| ||||||||
The NetBSD 1.4.1 Release Engineering team: | ||||||||
Ted Lemon | mellon@NetBSD.ORG | |||||||
Perry Metzger | perry@NetBSD.ORG | |||||||
Curt Sampson | cjs@NetBSD.ORG | |||||||
| ||||||||
Developers and other contributors: | ||||||||
Steve Allen | wormey@NetBSD.ORG | |||||||
Lennart Augustsson | augustss@NetBSD.ORG | |||||||
Christoph Badura | bad@NetBSD.ORG | |||||||
Manuel Bouyer | bouyer@NetBSD.ORG | |||||||
Robert V. Baron | rvb@NetBSD.ORG | |||||||
John Brezak | brezak@NetBSD.ORG | |||||||
Allen Briggs | briggs@NetBSD.ORG | |||||||
Aaron Brown | abrown@NetBSD.ORG | |||||||
David Brownlee | abs@NetBSD.ORG | |||||||
Simon Burge | simonb@NetBSD.ORG | |||||||
Dave Burgess | burgess@cynjut.infonet.net | |||||||
Dave Carrel | carrel@NetBSD.ORG | |||||||
Bill Coldwell | billc@NetBSD.ORG | |||||||
Chuck Cranor | chuck@NetBSD.ORG | |||||||
Alistair Crooks | agc@NetBSD.ORG | |||||||
Aidan Cully | aidan@NetBSD.ORG | |||||||
Rob Deker | deker@NetBSD.ORG | |||||||
Chris G. Demetriou | cgd@NetBSD.ORG | |||||||
Matthias Drochner | drochner@NetBSD.ORG | |||||||
Enami Tsugutomo | enami@NetBSD.ORG | |||||||
Bernd Ernesti | veego@NetBSD.ORG | |||||||
Erik Fair | fair@NetBSD.ORG | |||||||
Hubert Feyrer | hubertf@NetBSD.ORG | |||||||
Thorsten Frueauf | frueauf@NetBSD.ORG | |||||||
Brian R. Gaeke | brg@dgate.org | |||||||
Thomas Gerner | thomas@NetBSD.ORG | |||||||
Justin Gibbs | gibbs@NetBSD.ORG | |||||||
Adam Glass | glass@NetBSD.ORG | |||||||
Michael Graff | explorer@NetBSD.ORG | |||||||
Brad Grantham | grantham@tenon.com | |||||||
Matthew Green | mrg@NetBSD.ORG | |||||||
Juergen Hannken-Illjes | hannken@NetBSD.ORG | |||||||
Charles M. Hannum | mycroft@NetBSD.ORG | |||||||
Eric Haszlakiewicz | erh@NetBSD.ORG | |||||||
Michael L. Hitch | osymh@NetBSD.ORG | |||||||
Christian E. Hopps | chopps@NetBSD.ORG | |||||||
Ken Hornstein | kenh@NetBSD.ORG | |||||||
Marc Horowitz | marc@NetBSD.ORG | |||||||
ITOH Yasufumi | itohy@NetBSD.ORG | |||||||
Matthew Jacob | mjacob@NetBSD.ORG | |||||||
Lonhyn T. Jasinskyj | lonhyn@NetBSD.ORG | |||||||
Darrin Jewell | dbj@NetBSD.ORG | |||||||
Lawrence Kesteloot | kesteloo@cs.unc.edu | |||||||
Klaus Klein | kleink@NetBSD.ORG | |||||||
John Kohl | jtk@NetBSD.ORG | |||||||
Kevin Lahey | kml@NetBSD.ORG | |||||||
Ted Lemon | mellon@NetBSD.ORG | |||||||
Mike Long | mikel@NetBSD.ORG | |||||||
Paul Mackerras | paulus@NetBSD.ORG | |||||||
Neil J. McRae | neil@NetBSD.ORG | |||||||
Perry Metzger | perry@NetBSD.ORG | |||||||
Luke Mewburn | lukem@NetBSD.ORG | |||||||
der Mouse | mouse@NetBSD.ORG | |||||||
Tohru Nishimura | nisimura@NetBSD.ORG | |||||||
Masaru Oki | oki@NetBSD.ORG | |||||||
Greg Oster | oster@NetBSD.ORG | |||||||
Herb Peyerl | hpeyerl@NetBSD.ORG | |||||||
Matthias Pfaller | matthias@NetBSD.ORG | |||||||
Dante Profeta | dante@NetBSD.ORG | |||||||
Chris Provenzano | proven@NetBSD.ORG | |||||||
Darren Reed | darrenr@NetBSD.ORG | |||||||
Tim Rightnour | garbled@NetBSD.ORG | |||||||
Heiko W. Rupp | hwr@NetBSD.ORG | |||||||
SAITOH Masanobu | msaitoh@NetBSD.ORG | |||||||
Kazuki Sakamoto | sakamoto@NetBSD.ORG | |||||||
Curt Sampson | cjs@NetBSD.ORG | |||||||
Wilfredo Sanchez | wsanchez@NetBSD.ORG | |||||||
Ty Sarna | tsarna@NetBSD.ORG | |||||||
Matthias Scheler | tron@NetBSD.ORG | |||||||
Karl Schilke (rAT) | rat@NetBSD.ORG | |||||||
Tim Shepard | shep@NetBSD.ORG | |||||||
Chuck Silvers | chs@NetBSD.ORG | |||||||
Thor Lancelot Simon | tls@NetBSD.ORG | |||||||
Noriyuki Soda | soda@NetBSD.ORG | |||||||
Wolfgang Solfrank | ws@NetBSD.ORG | |||||||
Bill Sommerfeld | sommerfeld@NetBSD.ORG | |||||||
Ignatios Souvatzis | is@NetBSD.ORG | |||||||
Bill Studenmund | wrstuden@NetBSD.ORG | |||||||
Kevin Sullivan | sullivan@NetBSD.ORG | |||||||
Kimmo Suominen | kim@NetBSD.ORG | |||||||
Matt Thomas | matt@NetBSD.ORG | |||||||
Jason Thorpe | thorpej@NetBSD.ORG | |||||||
Christoph Toshok | toshok@NetBSD.ORG | |||||||
Todd Vierling | tv@NetBSD.ORG | |||||||
Paul Vixie | vixie@NetBSD.ORG | |||||||
Krister Walfridsson | kristerw@NetBSD.ORG | |||||||
Nathan Williams | nathanw@NetBSD.ORG | |||||||
Colin Wood | ender@NetBSD.ORG |
This product includes software developed by the University of
California, Berkeley and its contributors.
This product includes software developed by the Computer
Systems Engineering Group at Lawrence Berkeley Laboratory.
This product includes software developed by the NetBSD
Foundation, Inc. and its contributors.
This product includes software developed by Adam Glass
and Charles Hannum.
This product includes software developed by Adam Glass.
This product includes software developed by Berkeley Software
Design, Inc.
This product includes software developed by Charles D. Cranor
and Washington University.
This product includes software developed by Charles D. Cranor.
This product includes software developed by Charles Hannum,
by the University of Vermont and State Agricultural College
and Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley Laboratory,
and its contributors.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles M. Hannum.
This product includes software developed by Chris Provenzano.
This product includes software developed by Christian E. Hopps.
This product includes software developed by Christopher G. Demetriou
for the NetBSD Project.
This product includes software developed by Christopher G. Demetriou.
This product includes software developed by Christos Zoulas.
This product includes software developed by David Jones and Gordon Ross.
This product includes software developed by Dean Huxley.
This product includes software developed by Eric S. Hvozda.
This product includes software developed by Ezra Story.
This product includes software developed by Gordon Ross.
This product includes software developed by Gordon W. Ross
and Leo Weppelman.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Herb Peyerl.
This product includes software developed by Ian W. Dall.
This product includes software developed by Ignatios Souvatzis
for the NetBSD Project.
This product includes software developed by Jason R. Thorpe
for And Communications, http://www.and.com/.
This product includes software developed by Joachim Koenig-Baltes.
This product includes software developed by Jochen Pohl
for The NetBSD Project.
This product includes software developed by John Polstra.
This product includes software developed by Jonathan Stone
and Jason R. Thorpe for the NetBSD Project.
This product includes software developed by Jonathan Stone
for the NetBSD Project.
This product includes software developed by Jonathan Stone.
This product includes software developed by Julian Highfield.
This product includes software developed by Kenneth Stailey.
This product includes software developed by Leo Weppelman.
This product includes software developed by Lloyd Parkes.
This product includes software developed by Mark Brinicombe.
This product includes software developed by Markus Wild.
This product includes software developed by Martin Husemann
and Wolfgang Solfrank.
This product includes software developed by Mats O Jansson
and Charles D. Cranor.
This product includes software developed by Mats O Jansson.
This product includes software developed by Matthias Pfaller.
This product includes software developed by Paul Kranenburg.
This product includes software developed by Paul Mackerras.
This product includes software developed by Peter Galbavy.
This product includes software developed by Philip A. Nelson.
This product includes software developed by Rodney W. Grimes.
This product includes software developed by Scott Bartram.
This product includes software developed by SigmaSoft, Th. Lockert.
This product includes software developed by Terrence R. Lambert.
This product includes software developed by Theo de Raadt
and John Brezak.
This product includes software developed by Theo de Raadt.
This product includes software developed by TooLs GmbH.
This product includes software developed by Winning Strategies, Inc.
This product includes software developed by the Center for
Software Science at the University of Utah.
This product includes software developed by the University of Calgary
Department of Computer Science and its contributors.
This product includes software developed by the University of Vermont
and State Agricultural College and Garrett A. Wollman.
This product includes software developed for the FreeBSD project.
This product includes software developed for the Internet
Software Consortium by Ted Lemon.
This product includes software developed for the NetBSD Project
by Frank van der Linden.
This product includes software developed for the NetBSD Project
by Jason R. Thorpe.
This product includes software developed for the NetBSD Project
by John M. Vinopal.
This product includes software developed for the NetBSD Project
by Matthias Drochner.
This product includes software developed for the NetBSD Project
by Matthieu Herrb.
This product includes software developed for the NetBSD Project
by Perry E. Metzger.
This product includes software developed for the NetBSD Project
by Piermont Information Systems Inc.
This product includes software developed for the NetBSD Project
by Ted Lemon.
This product includes software developed by LAN Media Corporation
and its contributors.
This product includes software developed by Michael Graff for
the NetBSD Project.
This product includes software developed by Charles Hannum.
This product includes software developed by Charles Hannum, by
the University of Vermont and State Agricultural College and
Garrett A. Wollman, by William F. Jolitz, and by the
University of California, Berkeley, Lawrence Berkeley
Laboratory, and its contributors.
This product includes software developed by the University of
Vermont and State Agricultural College and Garrett A. Wollman.
This product includes software developed by Dean Huxley.
This product includes software developed by Herb Peyerl.
In the following statement, "This software" refers to the Mitsumi
CD-ROM driver:
This software was developed by Holger Veit and Brian Moore for
use with "386BSD" and similar operating systems. "Similar
operating systems" includes mainly non-profit oriented systems
for research and education, including but not restricted to
"NetBSD", "FreeBSD", "Mach" (by CMU).
In the following statement, "This software" refers to the parallel
port driver:
This software is a component of "386BSD" developed by
William F. Jolitz, TeleMuse.