August 22, 2004 INSTALL 8 NetBSD

NAME

INSTALL - Installation procedure for NetBSD/next68k.

CONTENTS

                                                              

About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 2.0 and 3.0 Releases................2 Supported platforms and machines............................3 Supported devices...........................................3 Kernel......................................................5 Networking..................................................5 File system.................................................6 Libraries...................................................6 Security....................................................6 System administration and user tools........................6 Miscellaneous...............................................7 next68k specific............................................7 The Future of NetBSD...........................................7 Sources of NetBSD..............................................8 NetBSD 3.0 Release Contents....................................8 NetBSD/next68k subdirectory structure.......................9 Binary distribution sets....................................9 NetBSD/next68k System Requirements and Supported Devices......11 Supported hardware.........................................11 Unsupported hardware.......................................11 Getting the NetBSD System on to Useful Media..................12 Preparing your System for NetBSD installation.................12 Get to the ROM Monitor prompt..............................12 Change the configuration parameters to netboot.............12 Installing the NetBSD System..................................13 Post installation steps.......................................16 Upgrading a previously-installed NetBSD System................19 Compatibility Issues With Previous NetBSD Releases............19 Issues affecting an upgrade from NetBSD 2.1 and older......19 Using online NetBSD documentation.............................20 Administrivia.................................................20 Thanks go to..................................................21 We are........................................................26 Legal Mumbo-Jumbo.............................................31 The End.......................................................37

DESCRIPTION

About this Document

This document describes the installation procedure for NetBSD3.0 on the next68k platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt:

.ps
PostScript.

.html
Standard Internet HTML.

.more
The enhanced text format used on UNIX-like systems by the more(1) and less(1) pager utility programs. This is the format in which the on-line man pages are generally presented.

.txt
Plain old ASCII.

You are reading the HTML version.

What is NetBSD?

The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring seventeen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD3.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. For information on them, please see the NetBSD web site at http://www.NetBSD.org/.)

NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code.

NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist.

Changes Between The NetBSD 2.0 and 3.0 Releases

The NetBSD3.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 a year of development that went into the NetBSD3.0 release. Some highlights include:

Supported platforms and machines
Supported devices
Kernel
Networking
File system
Libraries
Security
System administration and user tools
Miscellaneous

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.

next68k specific

This is the fifth major release of NetBSD for the NeXT series of computers.

The Future of NetBSD

The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project.

The NetBSD Foundation will help improve the quality of NetBSD by:

We intend to begin narrowing the time delay between releases. Our ambition is to provide a full release every six to eight months.

We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD.

We intend to continue our current practice of making the NetBSD-current development source available on a daily basis.

We intend to integrate free, positive changes from whatever sources submit them, providing that they are well thought-out and increase the usability of the system.

Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists.

Sources of NetBSD

Refer to http://www.NetBSD.org/mirrors/.

NetBSD 3.0 Release Contents

The root directory of the NetBSD3.0 release is organized as follows:

.../NetBSD-3.0/

CHANGES
Changes since earlier NetBSD releases.

LAST_MINUTE
Last minute changes.

MIRRORS
A list of sites that mirror the NetBSD3.0 distribution.

README.files
README describing the distribution's contents.

TODO
NetBSD's todo list (also somewhat incomplete and out of date).

patches/
Post-release source code patches.

source/
Source distribution sets; see below.

In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD3.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:

gnusrc
This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets.
79 MB gzipped, 367 MB uncompressed

pkgsrc
This set contains the ``pkgsrc'' sources, which contain the infrastructure to build third-party packages.
24 MB gzipped, 200 MB uncompressed

sharesrc
This set contains the ``share'' sources, which include the sources for the man pages not associated with any particular program; the sources for the typesettable document set; the dictionaries; and more.
5 MB gzipped, 20 MB uncompressed

src
This set contains all of the base NetBSD3.0 sources which are not in gnusrc, sharesrc, or syssrc.
37 MB gzipped, 176 MB uncompressed

syssrc
This set contains the sources to the NetBSD3.0 kernel for all architectures; config(8); and dbsym(8).
26 MB gzipped, 140 MB uncompressed

xsrc
This set contains the sources to the X Window System.
84 MB gzipped, 450 MB uncompressed

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:

BSDSUM
Historic BSD checksums for the various files in that directory, in the format produced by the command:
cksum -o 1 file.

CKSUM
POSIX checksums for the various files in that directory, in the format produced by the command:
cksum file.

MD5
MD5 digests for the various files in that directory, in the format produced by the command:
cksum-m file.

SYSVSUM
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.

NetBSD/next68k subdirectory structure
The next68k-specific portion of the NetBSD3.0 release is found in the next68k subdirectory of the distribution: .../NetBSD-3.0/next68k/. It contains the following files and directories:

INSTALL.html
INSTALL.ps
INSTALL.txt
INSTALL.more
Installation notes in various file formats, including this file. The .more file contains underlined text using the more(1) conventions for indicating italic and bold display.
binary/
kernel/
netbsd-GENERIC.gz
A gzipped NetBSD kernel containing code for everything supported in this release.
sets/
next68k binary distribution sets; see below.
installation/
misc/
Binary distribution sets
The NetBSD next68k binary distribution sets contain the binaries which comprise the NetBSD3.0 release for the next68k. The binary distribution sets can be found in the next68k/binary/sets subdirectory of the NetBSD3.0 distribution tree, and are as follows:

base
The NetBSD3.0 next68k base binary distribution. You must install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below.
16 MB gzipped, 45 MB uncompressed

comp
Things needed for compiling programs. This set includes the system include files (/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.
18 MB gzipped, 69 MB uncompressed

etc
This distribution set contains the system configuration files that reside in /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.
1 MB gzipped, 1 MB uncompressed

games
This set includes the games and their manual pages.
3 MB gzipped, 7 MB uncompressed

kern-GENERIC
This set contains a NetBSD/next68k 3.0 GENERIC kernel, named /netbsd. You must install this distribution set.
1 MB gzipped, 3 MB uncompressed

man
This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets.
8 MB gzipped, 30 MB uncompressed

misc
This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share.
3 MB gzipped, 9 MB uncompressed

text
This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages.
2 MB gzipped, 7 MB uncompressed

NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. NetBSD/next68k currently does not ship with an X server or X clients. Binary sets for the X Window System are distributed with NetBSD. The sets are:

xbase
The basic files needed for a complete X client environment. This does not include the X servers.
6 MB gzipped, 17 MB uncompressed

xcomp
The extra libraries and include files needed to compile X source code.
10 MB gzipped, 37 MB uncompressed

xfont
Fonts needed by X.
31 MB gzipped, 39 MB uncompressed

xetc
Configuration files for X which could be locally modified.
0.03 MB gzipped, 0.17 MB uncompressed

xserver
The X server.
3 MB gzipped, 7 MB uncompressed

The next68k binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz.

The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the filenames stored in the sets are relative and therefore the files are extracted below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xpf command from the root directory ( / ) of your system. This utility is used only in a Traditional method installation.

Note:
Each directory in the next68k binary distribution also has its own checksum files, just as the source distribution does.

NetBSD/next68k System Requirements and Supported Devices

NetBSD/next68k 3.0 will run on the 25 MHz 68040-based NeXT workstations. The Turbo (33 MHz) models are not supported. The 68030 model is not supported. NetBSD/next68k 3.0 does not have any local disk support, so you must netboot and run diskless.

The minimum configuration requires 4 MB of RAM and a network server capable of netbooting NetBSD/next68k. Serial consoles are poorly supported by the hardware, see the FAQ for help. Typically it is just easier to use the NeXT monitor and keyboard. http://www.NetBSD.org/Ports/next68k/faq.html

Supported hardware

Unsupported hardware

Getting the NetBSD System on to Useful Media

Because NetBSD/next68k must run diskless, the distribution must be installed to a remote machine that NFS exports to the NeXT machine. As a result, there is no automated install procedure. Begin by retrieving the NetBSD set files onto the serving machine. These can be found at ftp.NetBSD.org. You may want to keep the following information handy:

IP Address: ftp.NetBSD.org
Login: anonymous
Password: <your e-mail address>
Server path: /pub/NetBSD/NetBSD-3.0/next68k/binary/sets

Preparing your System for NetBSD installation

Get to the ROM Monitor prompt
After the system performs its power-on self test, and while it tries to boot an operating system, press the COMMAND-` keys (the backquote is above 7 on the keypad on the right of the keyboard). You should see a prompt like this:
                        NeXT ROM Monitor 2.5 (v66)
                                                                                     

CPU MC68040 25 MHz, memory 100 nS Backplane slot #0 Ethernet address: 0:0:f:0:fb:90 Memory size 40 MB NeXT>

Write down the ethernet address. You will need this later to configure the netboot server for your NetBSD/next68k system.

Change the configuration parameters to netboot
Press the p key to modify the configuration parameters. You will need to change the boot command to en()netbsd which is to boot from the en() ethernet device the kernel named netbsd. You should wite down what the original boot command was in case you wish to boot NEXTSTEP in the future. It will probably be sd(). While modifying the parameters, you may wish to set the system to use verbose test mode which will print detailed messages while it is attempting to load the kernel, as opposed to the normal graphic of a network cable. You should not set the extended diagnostics as the system will try to boot a diagnostic kernel. Here is an example configuration session:
NeXT> p
boot command: sd()? en()netbsd
DRAM tests:  yes? yes
perform power-on system test:  yes? yes
sound out tests:  yes? yes
SCSI tests:  yes? yes
loop until keypress:  no? no
verbose test mode:  no? yes
boot extended diagnostics:  no? no
serial port A is alternate console:  no? yes
allow any ROM command even if password protected:  no? no
allow boot from any device even if password protected:  no? no
allow optical drive #0 eject even if password protected:  yes? yes
enable parity checking if parity memory is present:  no? no

Now, whenever you reset or power on your system, it will attempt to netboot. From the ROM Monitor prompt, you can simply type b to netboot. You can also press the power key (above the arrows) to turn off the system.

Installing the NetBSD System

  1. Introduction

    To netboot a next68k, you must configure one or more servers to provide information and files to your next68k (the `client ).' If you are using NetBSD (any architecture) on your netboot server(s), the information provided here should be sufficient to configure everything. Additionally, you may wish to look at the diskless(8) manual page and the manual pages for each daemon you'll be configuring. If the server(s) are another operating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps necessary to configure the netboot services on a variety of platforms. http://www.NetBSD.org/Documentation/network/netboot/

    Briefly, the netboot process involves discovery, bootstrap, kernel and file system stages. In the first stage, the client discovers information about where to find the bootstrap program. Next, it downloads and executes the bootstrap program. The bootstrap program goes through another discovery phase to determine where the kernel is located. The bootstrap program tries to mount the NFS share containing the kernel. Once the kernel is loaded, it starts executing. The kernel tries to mount the NFS share that had the kernel and starts executing init(8). All next68k systems use BOOTP for the discovery stage. TFTP is used in the bootstrap phase to download the bootstrap program, boot. NFS is used in both the kernel and file system stages to download the kernel, and to access files on the file server.

    We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hardware address) of your netboot client machine. You should have determined this address in an earlier stage. In this example, we will use `192.168.1.10' as the IP address of your client and `client.test.net' as its name. We will assume you're providing all of your netboot services on one machine called `server.test.net' with the client's files exported from the directory /export/client/root. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environment.

    You should set up each netboot stage in order (i.e. discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed.

  2. dhcpd(8) in bootpd(8) compatible mode

    Put the following lines in your /etc/dhcpd.conf (see dhcpd.conf(5) and dhcp-options(5) for more information):

    ddns-update-style none;
                    # Do not use any dynamic DNS features
                    #
    allow bootp;    # Allow bootp requests, thus the dhcp server
                    # will act as a bootp server.
                    #
    authoritative;  # master DHCP server for this subnet
                    #
    subnet 192.168.1.0 netmask 255.255.255.0 {
                    # Which network interface to listen on.
                    # The zeros indicate the range of addresses
                    # that are allowed to connect.
    }
    group {
                    # Set of parameters common to all clients
                    # in this "group".
                    #
            option broadcast-address        192.168.1.255;
            option domain-name              "test.net";
            option domain-name-servers      dns.test.net;
            option routers                  router.test.net;
            option subnet-mask              255.255.255.0;
                    #
                    # An individual client.
                    #
            host client.test.net {
                    hardware ethernet       CC:CC:CC:CC:CC:CC;
                    fixed-address           192.168.1.10;
                    #
                    # Name of the host (if the fixed address
                    # doesn't resolve to a simple name).
                    #
                    option host-name        "client";
                    #
                    # Name of the bootloader or kernel
                    # to download via tftp.
    #
                    filename                "boot";
                                                                                         

    # # The path on the NFS server. # option root-path "/export/client/root";

    # #next68k machines require non-RFC1048 BOOTP # always-reply-rfc1048 false;

    # # If your DHCP server is not your NFS server, supply the # address of the NFS server. Since we assume you run everything # on one server, this is not needed. # # next-server server.test.net; } #you may paste another "host" entry here for additional #clients on this network }

    You will need to make sure that the dhcpd.leases file exists.

    # touch /var/db/dhcpd.leases
    

    You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with:

    # /etc/rc.d/dhcpd restart
    

  3. tftpd(8)

    The default configuration of the TFTP server is to run in a chroot(8) environment in the /tftpboot directory. Thus, the first order of business is to create this directory:

    # mkdir -p /tftpboot
    

    Next, edit /etc/inetd.conf and uncomment the line with the TFTP daemon:

    tftp  dgram  udp  wait  root  /usr/libexec/tftpd tftpd -l -s /tftpboot
    

    Now, restart inetd(8). If the server is running NetBSD, you can achieve this with:

    # /etc/rc.d/inetd restart
    

    Now, you need to copy the bootloader for your next68k machine to /tftpboot. Get boot from the installation directory of the distribution.

    # cp boot /tftpboot
    
    Just to be sure, let's make everything readable.
    # chmod -R a+rX /tftpboot
    

    Sometimes, the arp(8) table gets messed up, and the TFTP server can't communicate with the client. In this case, it will write a log message (via syslogd(8)) to /var/log/messages saying: `tftpd: write: Host is down'. If this is the case, you may need to force the server to map your client's ethernet address to its IP address:

    # arp -s client CC:CC:CC:CC:CC:CC
    

  4. nfsd(8), mountd(8), and rpcbind(8)

    Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. Create the directory you are exporting for the netboot client:

    # mkdir -p /export/client/root
    

    Put the following line in /etc/exports to enable NFS sharing:

    /export/client/root -maproot=root client.test.net
    

    If your server is currently running an NFS server, you only need to restart mountd(8). Otherwise, you need to start rpcbind(8) and nfsd(8). If the server is running NetBSD, you can achieve this with:

    # /etc/rc.d/rpcbind start
    # /etc/rc.d/nfsd start
    # /etc/rc.d/mountd restart
    

  5. NetBSD kernel

    Now, if you place a kernel named netbsd in /export/client/root your client should boot the kernel. Use binary/kernel/netbsd-GENERIC.gz.

    # gunzip netbsd-GENERIC.gz
    # mv netbsd-GENERIC /export/client/root/netbsd
    

  6. Client file system

    You need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. http://www.NetBSD.org/Documentation/network/netboot/nfs.html

  7. Setting up the server daemons

    You need these services to start up every time you boot your server, make sure the following lines are present in your /etc/rc.conf:

    dhcpd=YES        dhcpd_flags="-q"
    nfs_server=YES         # enable server daemons
    mountd=YES
    rpcbind=YES      rpcbind_flags="-l"   # -l logs libwrap
    

    Also, you'll need to make sure the tftpd line in /etc/inetd.conf remains uncommented.


Post installation steps

Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below.

  1. Configuring /etc/rc.conf

    If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst usually will), the system will drop you into single user mode on first reboot with the message

           /etc/rc.conf is not configured. Multiuser boot aborted.

    and with the root file system (/) mounted read-only. When the system asks you to choose a shell, simply press RETURN to get to a /bin/sh prompt. If you are asked for a terminal type, respond with vt220 (or whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard:
           # stty erase '^h'
           # stty erase '^?'
    At this point, you need to configure at least one file in the /etc directory. You will need to mount your root file system read/write with:
           # /sbin/mount -u -w /
    Change to the /etc directory and take a look at the /etc/rc.conf file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi-user boot can proceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5).

    If your /usr directory is on a separate partition and you do not know how to use ed, you will have to mount your /usr partition to gain access to ex or vi. Do the following:


           # mount /usr
           # export TERM=vt220

    If you have /var on a separate partition, you need to repeat that step for it. After that, you can edit /etc/rc.conf with vi(1). When you have finished, type exit at the prompt to leave the single-user shell and continue with the multi-user boot.

    Other values that need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your <int> network interface, along the lines of


           ifconfig_xe0="inet 123.45.67.89 netmask 255.255.255.0"

    or, if you have myname.my.dom in /etc/hosts:


           ifconfig_xe0="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.

  2. Logging in

    After reboot, you can log in as root at the login prompt. Unless you've set a password in sysinst, there is no initial password. If you're using the machine in a networked environment, you should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. 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.

    Unless you have connected an unusual terminal device as the console you can just press RETURN when it prompts for Terminal type? [...].

  3. Adding accounts

    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.

    Don't forget to add /usr/X11R6/bin to your path in your shell's dot file so that you have access to the X binaries.

  4. Installing third party packages

    If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries.

  5. Misc

Upgrading a previously-installed NetBSD System

NetBSD/next68k does not currently support an upgrade procedure.

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 NetBSD3.0.

Issues affecting an upgrade from NetBSD 2.1 and older releases.
It is very important that you populate the directory /etc/pam.d with appropriate configuration files for the Pluggable Authentication Modules (PAM) because you will not be able to login any more otherwise. Using postinstall as described below will take care of this. Please refer to http://www.netbsd.org/guide/en/chap-pam.html for documentation about PAM.

The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall:

postinstall -s /path/to/etc.tgz check
postinstall -s /path/to/etc.tgz fix

Issues fixed by postinstall: