INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/hppa. CONTENTS About this Document What is NetBSD? Dedication Changes Between The NetBSD 9 and 10 Releases Features to be removed in a later release The NetBSD Foundation Sources of NetBSD NetBSD 10.0_RC6 Release Contents NetBSD/hppa subdirectory structure Binary distribution sets NetBSD/hppa System Requirements and Supported Devices Getting the NetBSD System on to Useful Media Preparing your System for NetBSD installation Get to the Boot Administration prompt Change the configuration parameters to netboot Determine netboot method Installing the NetBSD System Installing NetBSD by using a netboot setup Running the sysinst installation program Introduction General Quick install Booting NetBSD Network configuration Installation drive selection and parameters Selecting which sets to install Partitioning the disk Preparing your hard disk Getting the distribution sets Installation from CD-ROM Installation using FTP Installation using NFS Installation from an unmounted file system Installation from a local directory Extracting the distribution sets Configure additional items Finalizing your installation Post installation steps Upgrading a previously-installed NetBSD System Compatibility Issues With Previous NetBSD Releases Using online NetBSD documentation Administrivia Thanks go to Legal Mumbo-Jumbo The End DESCRIPTION About this Document This document describes the installation procedure for NetBSD 10.0_RC6 on the hppa 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 util- ity programs. This is the format in which the on-line man pages are generally presented. .txt Plain old ASCII. You are reading the ASCII version. What is NetBSD? The NetBSD Operating System is a fully functional open- source operating system derived from the University of Cali- fornia, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many different different system architectures (ports) across a variety of distinct CPU families, and is being ported to more. The NetBSD 10.0_RC6 release contains complete binary releases for most of these system architectures, with preliminary support for the others included in source form. Please see the NetBSD website: https://www.NetBSD.org/ for information on them. NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD fea- tures a complete set of user utilities, compilers for sev- eral 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 commu- nity. Without the unique cooperation and coordination the net makes possible, NetBSD would not exist. Dedication NetBSD 10.0 is dedicated to the memory of Ryo SHIMIZU, who passed away in May 2023. Ryo's technical contributions are too many to list here in full. He was a long term contributor and worked on a lot of low-level code over various architectures, from x68k to aarch64. He also worked on various out-of-tree NetBSD items, like the IIJ git repository conversion. The project lost an excellent technical contributor and many of us a good friend. Changes Between The NetBSD 9 and 10 Releases The NetBSD 10.0_RC6 release provides many significant changes, including support for many new devices, hundreds of bug fixes, new and updated kernel subsystems, and numerous userland enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. One important new feature in this release is the support for extended attributes and access controll lists on FFS file systems. For new installations the installer will default to disable this features, so the file system is compatible with older NetBSD releases (before 10), and allow other operating sys- tems to mount this file systems at least in read-only mode. If you want a new installed file system to support extended attributes, change the file system type from ``FFSv2'' to ``FFSv2ea'' in the partitioning menu. You can also convert file systems later, using the fsck_ffs(8) utility. More details are available in this guide: https://wiki.netbsd.org/tutorials/acls_and_extended_attributes_on_ffs. If you are upgrading from a version of NetBSD -current please also check the Compatibility Issues With Previous NetBSD Releases. It is impossible to completely summarize the massive development that went into the NetBSD 10.0_RC6 release. The complete list of changes can be found in the following files: CHANGES: https://cdn.NetBSD.org/pub/NetBSD/NetBSD-10.0_RC6/CHANGES CHANGES-10.0: https://cdn.NetBSD.org/pub/NetBSD/NetBSD-10.0_RC6/CHANGES-10.0 files in the top level directory of the NetBSD 10.0 release tree. Features to be removed in a later release The following features are to be removed from NetBSD in the future: o groff(1). Man pages are now handled with mandoc(1), and groff(1) can still be found in pkgsrc as textproc/groff. o pf(4). This packet filter is obsolete and unmain- tained in NetBSD. It will be eventually removed due to possible long-standing security issues and lack of multiprocessor support. New installations should use npf(7). The NetBSD Foundation The NetBSD Foundation is a tax exempt, not-for-profit 501(c)(3) corporation that devotes itself to the traditional goals and spirit of the NetBSD Project and owns the trade- mark of the word ``NetBSD''. It supports the design, devel- opment, and adoption of NetBSD worldwide. More information on the NetBSD Foundation, its composition, aims, and work can be found at: https://www.NetBSD.org/foundation/ Sources of NetBSD Refer to mirrors: https://www.NetBSD.org/mirrors/ NetBSD 10.0_RC6 Release Contents The root directory of the NetBSD 10.0_RC6 release is orga- nized as follows: .../NetBSD-10.0_RC6/ CHANGES Changes between the 9.0 and 10.0 releases. CHANGES-10.0 Changes between the initial 10.0 branch and final release of 10.0. CHANGES.prev Changes in previous NetBSD releases. LAST_MINUTE Last minute changes and notes about the release. README.files README describing the distribution's contents. images/ Images (ISO 9660 or USB) for installing NetBSD. Depending on your system, these may be bootable. 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 architec- tures for which NetBSD 10.0_RC6 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 dis- tribution 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. sharesrc This set contains the ``share'' sources, which include the sources for the man pages not associ- ated with any particular program; the sources for the typesettable document set; the dictionaries; and more. src This set contains all of the base NetBSD 10.0_RC6 sources which are not in gnusrc, sharesrc, or syssrc. syssrc This set contains the sources to the NetBSD 10.0_RC6 kernel for all architectures as well as the config(1) utility. xsrc This set contains the sources to the X Window Sys- tem. 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: MD5 MD5 digests in the format produced by the com- mand: cksum -a MD5 file. SHA512 SHA512 digests in the format produced by the command: cksum -a SHA512 file. The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files. NetBSD/hppa subdirectory structure The hppa-specific portion of the NetBSD 10.0_RC6 release is found in the hppa subdirectory of the distribution: .../NetBSD-10.0_RC6/hppa/. 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 every- thing supported in this release. sets/ hppa binary distribution sets; see below. installation/ misc/ Miscellaneous hppa installation utilities; see installation section below. Binary distribution sets The NetBSD hppa binary distribution sets contain the bina- ries which comprise the NetBSD 10.0_RC6 release for hppa. The binary distribution sets can be found in the hppa/binary/sets subdirectory of the NetBSD 10.0_RC6 distri- bution tree, and are as follows: base The NetBSD 10.0_RC6 hppa base binary distribution. You must install this distribution set. It con- tains the base NetBSD utilities that are necessary for the system to run and be minimally functional. 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. debug This distribution set contains debug information for all base system utilities. It is useful when reporting issues with binaries or during develop- ment. This set is huge, if the target disk is small, do not install it. etc This distribution set contains the system configu- ration 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. games This set includes the games and their manual pages. kern-GENERIC This set contains a NetBSD/hppa 10.0_RC6 GENERIC kernel, named /netbsd. You must install this dis- tribution set. 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 man- ual pages that are included in the other sets. misc This set includes the system dictionaries, the typesettable document set, and other files from /usr/share. modules This set includes kernel modules to add functional- ity to a running system. rescue This set includes the statically linked emergency recover binaries installed in /rescue. text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibil- ity. These sources are based on X.Org. 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. xcomp The extra libraries and include files needed to compile X source code. xdebug This distribution set contains debug information for all X11 binaries. It is useful when reporting issues with these binaries or during development. This set is huge, if the target disk is small, do not install it. xfont Fonts needed by the X server and by X clients. xetc Configuration files for X which could be locally modified. xserver The X server. The hppa binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the filenames stored in the sets are relative and therefore the files are extracted below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xzpf command from the root directory ( / ) of your system. Note: Each directory in the hppa binary distribution also has its own checksum files, just as the source dis- tribution does. NetBSD/hppa System Requirements and Supported Devices Since NetBSD/hppa is an experimental port, the hardware sup- port is in a constant state of flux. Check the port-hppa@NetBSD.org mailing list and the NetBSD/hppa port homepage for an up-to-date list of known supported hardware. http://www.NetBSD.org/ports/hppa/ NetBSD/hppa 10.0_RC6 works from local disk, once installed, or diskless via netboot. Getting the NetBSD System on to Useful Media To boot NetBSD, you will need a server running the appropri- ate netboot protocol with a Logical Interchange Format (LIF) volume of the kernel you wish to boot, or the netinstall.lif volume available in the hppa/installation directory of the NetBSD distribution. Booting from CD is currently not supported. Installation is supported from several media types, includ- ing: o CD-ROM / DVD / USB stick o FTP o Remote NFS partition o Tape o Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below. CD-ROM / DVD / USB stick Find out where the distribution set files are on the CD-ROM, DVD or USB stick. Likely locations are binary/sets and hppa/binary/sets. (You only need to know this if you are mixing installer and installation media from different versions - the installer will know the proper default location for the sets it comes with). Proceed to the instructions on installation. FTP The preparations for this instal- lation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. If you don't have DHCP available on your net- work, you will need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrad- ing. NFS Place the NetBSD distribution sets you wish to install into a direc- tory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modify- ing the /etc/exports file on the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once the NFS server is set up properly and you have the informa- tion mentioned above, you can pro- ceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on pre- paring your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Tape To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format. If you're making the tape on a UNIX-like system, the easiest way to do so is probably something like: # tar -cf tape_device dist_sets where tape_device is the name of the tape device that represents the tape drive you're using. This might be /dev/rst0, or something similar, but it will vary from system to system. In the above example, dist_sets is a list of filenames corresponding to the distribution sets that you wish to place on the tape. For instance, to put the kern-GENERIC, base, and etc distributions on tape (the absolute minimum required for installation), you would do the following: # cd .../NetBSD-10.0_RC6 # cd hppa/binary # tar -cf tape_device kern-GENERIC.tgz base.tgz etc.tgz Note: You still need to fill in tape_device in the example. Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installa- tion, go directly to the section on upgrading. Preparing your System for NetBSD installation Get to the Boot Administration prompt All hppa workstations have a Boot Administration command line utility in their Boot ROM which lets you configure var- ious settings. For example, you can set whether the system automatically boots an OS, which device to try booting from first, determine the ethernet MAC address, set up a serial console, and possibly do some low level hardware access. To get to the BOOT_ADMIN> prompt, you must press the ESCAPE key before it tries to boot an OS. Since these machines often take a long time between powering on and the brief window of time where you can hit the ESCAPE key, you must pay attention. Depending on how much RAM your system has, it may take over a minute after pressing the power button before anything will show up on screen. Once you have escaped out of the Selecting a system to boot and Searching for Potential Boot Devices you need to type the `a' key to get to the BOOT_ADMIN> prompt. Now, use the online help with the help command. Write down the ethernet address. You will need this later to configure the netboot server for your NetBSD/hppa system. Selecting a system to boot. To stop selection process, press and hold the ESCAPE key. Booting from: scsi.6.0 SEAGATE ST3600N Selection process stopped. Searching for Potential Boot Devices. To terminate search, press and hold the ESCAPE key. Device Selection Device Path Device Type ---------------------------------------------------------------------------- P0 scsi.6.0 SEAGATE ST3600N Search terminated. b) Boot from specified device s) Search for bootable devices a) Enter Boot Administration mode x) Exit and continue boot sequence ?) Help Select from menu: a BOOT_ADMIN> lan_addr LAN Station Address: 080009-123456 BOOT_ADMIN> help Change the configuration parameters to netboot The command syntax is different on the various models. Use the help path, help lan, and help autoselect commands to learn about how to configure your system. On a 735/99, you would type: BOOT_ADMIN> path primary lan BOOT_ADMIN> autoselect on BOOT_ADMIN> reset The first command sets the primary boot device to be the network interface, and the second command sets the system to always try booting from the primary boot path when it is reset or powered on. The last command stores the new set- tings and resets the machine. To return to using the SCSI disk at ID 6 as your primary boot device, you would use something like the following com- mand: BOOT_ADMIN> path primary scsi.6.0 Determine netboot method Most older Series 700 workstations (with PA-7000 (PCXS), PA-7100 (PCXT), or PA-7150 (PCXT)) use the RMP (Remote Main- tenance Protocol) to netboot. Specifically, they retrieve their boot program from an rbootd(8) server. The following list of RMP-only Series 700 workstations is probably com- plete, but has not been tested: o 705 o 710 o 715/33, 715/50, 715/75 o 720 o 725/50, 725/75 o 730 o 735 o 745i o 747i o 750 o 755 Newer Series 700 workstations retrieve their boot program from a server running dhcpd(8) in bootpd(8) compatible mode and tftpd(8). The following list of BOOTP-only Series 700 workstations is probably complete, but has not been tested: o 712 o 715/64, 715/80, 715/100, 715/100XC o 725/64, 725/100 o newer models, such as the B, C, and J class systems Installing the NetBSD System Installing NetBSD by using a netboot setup 1. Introduction To netboot a hppa, you must configure one or more servers to provide information and files to your hppa (the `client'). If you are using NetBSD (any architec- ture) on your netboot server(s), the information pro- vided here should be sufficient to configure every- thing. 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 vari- ety of platforms: https://www.NetBSD.org/docs/network/netboot/ Briefly, the netboot process involves discovery, boot- strap, 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 server contains one large file (a LIF file system) with the bootloader and the kernel. The bootstrap program simply loads the kernel from the LIF image. 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). Early hppa systems use HP's proprietary RMP (the rbootd(8) daemon) for the discovery stage, bootstrap download, and kernel download stages. Later hppa sys- tems use BOOTP for the discovery stage and TFTP for the bootstrap and kernel download. 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. If your system uses RMP to netboot, you must set up rbootd(8) but can skip dhcpd(8) and tftpd(8). If your system uses BOOTP to netboot, then you must set up dhcpd(8) and tftpd(8) but can skip rbootd(8). 2. rbootd(8) Get SYSNBSD from the installation directory of the dis- tribution. # mkdir -p /usr/mdec/rbootd # cp SYSNBSD /usr/mdec/rbootd # chmod -R a+rX /usr/mdec/rbootd Create /etc/rbootd.conf with the following line: CC:CC:CC:CC:CC:CC SYSNBSD You will need to start the rbootd. 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/rbootd restart If your netboot server is not running NetBSD but other OSs (like Linux, Solaris etc.), you have to use YAMAMORI Takenori's sun-rbootd package instead of native rbootd(8). Please refer the "Setting up the rbootd server" section in the NetBSD Diskless HOW-TO: https://www.NetBSD.org/docs/network/netboot/rbootd/ for details. 3. 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 informa- tion): 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 "SYSNBSD"; # # The path on the NFS server. # option root-path "/export/client/root"; # # The host address of the NFS server. This is mandatory for # NetBSD kernels even it's the same host as the DHCP server. # 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 run- ning, 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 4. 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 hppa machine to /tftpboot. Get SYSNBSD from the installation directory of the distribution. # cp SYSNBSD /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 5. 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 6. NetBSD kernel You do not need to place a kernel in /export/client/root since the kernel is contained inside SYSNBSD. 7. Client file system You need to extract and set up the client's installa- tion of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. See for details: https://www.NetBSD.org/docs/network/netboot/nfs.html. o Extracting distribution sets # cd /export/client/root # tar -xpzf /path/to/files/base.tgz # tar -xpzf /path/to/files/etc.tgz Continue with the other non-essential distribution sets if desired. o Set up swap # mkdir /export/client/root/swap # dd if=/dev/zero of=/export/client/swap bs=4k count=4k # echo '/export/client/swap -maproot=root:wheel client.test.net' >> /etc/exports # /etc/rc.d/mountd restart This creates a 16 MB swap file and exports it to the client. o Create device nodes # cd /export/client/root/dev # ./MAKEDEV all This procedure only works on NetBSD hosts. o Set up the client's fstab(5) Create a file in /export/client/root/etc/fstab with the following lines: server:/export/client/swap none swap sw,nfsmntpt=/swap server:/export/client/root / nfs rw 0 0 o Set up the client's rc.conf(5) Edit /export/client/root/etc/rc.conf rc_configured=YES hostname="client" defaultroute="192.168.1.1" nfs_client=YES auto_ifconfig=NO net_interfaces="" Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system. o Set up the client's hosts(5) file. Edit /export/client/root/etc/hosts ::1 localhost 127.0.0.1 localhost 192.168.1.10 client.test.net client 192.168.1.5 server.test.net server 8. 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: rbootd=YES rbootd_flags="" 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. Running the sysinst installation program 1. Introduction Using sysinst, installing NetBSD is a relatively easy process. Still, you should read this document and have it available during the installation process. This document tries to be a good guide to the installation, and as such, covers many details for the sake of com- pleteness. Do not let this discourage you; the install program is not hard to use. 2. General The following is a walk-through of the steps you will take while installing NetBSD on your hard disk. sysinst is a menu-driven program that guides you through the installation process. Sometimes questions will be asked, and in many cases the default answer will be displayed in brackets (``[ ]'') after the ques- tion. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the installation process again from scratch by running the /sysinst program from the command prompt. It is not necessary to reboot. 3. Quick install First, let's describe a quick install. The other sec- tions of this document go into the installation proce- dure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD / DVD as the install medium. o What you need. - The distribution sets (in this example, they are on the CD or DVD). - The netinstall.lif volume on a netboot server as described above. - A minimum of 32 MB of memory installed. - An optical drive. - A hard drive with at least 600 MB of free space for a complete base install, not including room for swap. If you wish to install the X Window System as well, you will need at least 225 MB more. o The Quick Installation - Boot the system as described above. You should be at the sysinst main menu. .***********************************************. * NetBSD-10.0_RC6 Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * f: Config menu * * x: Exit Install System * .***********************************************. - If you wish, you can configure some network settings immediately by choosing the Utility menu and then Configure network. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. - Choose Install. - You will be guided through the setup of your disk. - You will be asked to choose which distribution sets to install. - When prompted, choose CD-ROM as the install medium if booted from CD-ROM. The default val- ues for the path and device should be OK. - After the installation process has completed, you will be brought back to the main menu, where you should select Reboot, after you have removed the bootfloppy from the drive. - NetBSD will now boot. If you didn't set a password for the root user when prompted by sysinst, logging in as root and setting a pass- word should be your first task. You are also advised to read afterboot(8). 4. Booting NetBSD Boot your machine. The boot loader will start, which will print a countdown and begin booting. If the boot loader messages do not appear in a reason- able 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. It will take a while to load the kernel from the floppy, probably around a minute or so, then, the ker- nel boot messages will be displayed. This may take a little while also, as NetBSD will be probing your sys- tem to discover which hardware devices are installed. The most important thing to know is that wd0 is NetBSD's name for your first SATA/PATA disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the sec- ond, etc. Note that once the system has finished booting, you need not leave the floppy in the disk drive. Once NetBSD has booted and printed all the boot mes- sages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. Network configuration If you do not intend to use networking during the installation, but you do want your machine to be con- figured for networking once the system is installed, you should first go to the Utility menu and select the Configure network option. If you only want to tempo- rarily use networking during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response when asked to provide a server. 6. Installation drive selection and parameters To start the installation, select Install NetBSD to hard disk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. You should see disk names like sd0 or sd1. 7. Selecting which sets to install The next step is to choose which distribution sets you wish to install. Options are provided for full, mini- mal, and custom installations. If you choose sets on your own, base, etc, and a kernel must be selected. 8. Partitioning the disk o Choosing which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, sysinst will check for the presence of other operating systems and you will be asked to confirm that you want to overwrite these. 9. Editing the NetBSD disklabel The partition table of the NetBSD part of a disk is called a disklabel. If your disk already has a diskla- bel written to it, you can choose Use existing partition sizes. Otherwise, select Set sizes of NetBSD partitions. After you have chosen your partitions and their sizes (or if you opted to use the existing partitions), you will be presented with the layout of the NetBSD diskla- bel and given one more chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose. a Root partition (/) b Swap partition. c The entire disk. d-p Available for other use. Traditionally, d is the partition mounted on /usr, but this is historical practice and not a fixed value. You will then be asked to name your disk's disklabel. The default response will be OK for most purposes. If you choose to name it something different, make sure the name is a single word and contains no special char- acters. You don't need to remember this name. 10. Preparing your hard disk You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, select yes. The install program will now label your disk and create the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Other- wise, you can continue the installation program after pressing the return key. 11. Getting the distribution sets The NetBSD distribution consists of a number of sets that come in the form of gzipped tar files. At this point, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first transfer the sets to your hard disk, others will extract the sets directly. For all these methods, the first step is to make the sets available for extraction. The sets can be made available in a few different ways. The following sec- tions describe each of the methods. After reading about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'. 12. Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM drive (usually cd0) and the directory name on the CD-ROM where the distribution files are. sysinst will then check that the files are actually present in the specified location and proceed to the extraction of the sets. 13. Installation using FTP To install using FTP, you first need to configure your network setup if you haven't already done so. sysinst will help you with this, asking if you want to use DHCP. If you do not use DHCP, you can enter network configuration details yourself. If you do not have DNS set up for the machine that you are installing on, you can just press RETURN in answer to this question, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using FTP, and optionally a proxy server to use. If you did not set up DNS, you will need to spec- ify an IP address instead of a hostname for the FTP server. sysinst will then transfer the set files from the remote site to your hard disk. 14. Installation using NFS To install using NFS, you first need to configure your network setup if you haven't already done so. sysinst will do this for you, asking you if you want to use DHCP. If you do not use DHCP, you can enter network configuration details yourself. If you do not have DNS set up for the machine that you are installing on, you can just press RETURN in answer to this question, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e., correctly exported to your machine. If you did not set up DNS, you will need to specify an IP address instead of a hostname for the NFS server. 15. Installation from an unmounted file system In order to install from a local file system, you will need to specify the device that the file system resides on (for example wd1e), the type of the file system, and the directory on the specified file system where the sets are located. sysinst will then check if it can indeed access the sets at that location. 16. Installation from a local directory This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is already accessible. sysinst will ask you for the name of this directory. 17. Extracting the distribution sets A progress bar will be displayed while the distribution sets are being extracted. After all the files have been extracted, the device node files will be created. If you have already con- figured 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 configu- ration files. 18. Configure additional items The next menu will allow you to select a number of additional items to configure, including the time zone that you're in, to make sure your clock has the right offset from UTC, the root user's shell, and the initial root password. You can also enable installation of binary packages, which installs the pkgin(1) tool for managing binary packages for third-party software. This will feel familiar to users of package tools such as apt-get or yum. If you prefer to install third-party software from source, you can install the pkgsrc(7) tree. Finally, you can enable some daemons such as sshd(8), ntpd(8), or mdnsd(8). 19. Finalizing your installation Congratulations, you have successfully installed NetBSD 10.0_RC6. You can now reboot the machine and boot NetBSD from hard disk. 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. The most important steps are described below. 1. Before all else, read postinstall(8). 2. Configuring /etc/rc.conf If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst normally 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 what- ever is appropriate for your terminal type) and press RETURN. You may need to type one of the following com- mands to get your delete key to work properly, depend- ing 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 pro- ceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line doc- umentation may be found. More complete documentation can be found in rc.conf(5). When you have finished editing /etc/rc.conf, type exit at the prompt to leave the single-user shell and con- tinue with the multi-user boot. Other values that may need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute. You may also need to add an ifconfig_int for your network interface, along the lines of ifconfig_ie0="inet 192.0.2.123 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_ie0="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 networking, DHCP can be used by setting dhcpcd=YES in /etc/rc.conf. 3. Logging in After reboot, you can log in as root at the login prompt. If you didn't set a password in sysinst, there is no initial password. You should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. By default, root login from the network is disabled (even via ssh(1)). One way to become root over the network is to log in as a different user that belongs to group ``wheel'' (see group(5)) and use su(1) to become root. 4. Adding accounts Use the useradd(8) command to add accounts to your sys- tem. Do not edit /etc/passwd directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database. 5. The X Window System If you installed the X Window System, you may want to read the chapter about X in the NetBSD Guide: https://www.NetBSD.org/docs/guide/en/chap-x.html: 6. 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, pkgsrc. pkgsrc automatically handles any changes nec- essary to make the software run on NetBSD. This includes the retrieval and installation of any other packages the software may depend upon. o More information on the package system is available at https://www.NetBSD.org/docs/software/packages.html o A list of available packages suitable for browsing is at https://cdn.NetBSD.org/pub/pkgsrc/current/pkgsrc/README.html o Precompiled binaries can be found at https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/ usually in the hppa/10.0_RC6/All subdir. If you installed pkgin(1) in the sysinst post-installation configuration menu, you can use it to automatically install binary packages over the network. Assuming that /usr/pkg/etc/pkgin/repositories.conf is cor- rectly configured, you can install them with the following commands: # pkgin install tcsh bash perl apache xfce4 firefox ... The above command will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, Xfce desktop environment and the Firefox web browser as well as all the packages they depend on. If it was not automatically installed, pkgin(1) can be installed on a fresh NetBSD system with pkg_add(1): export PKG_PATH=https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$(uname -p)/$(uname -r | cut -d_ -f1)/All pkg_add pkgin o If you wish to use the pkgsrc(7) framework for com- piling packages and did not install it from the sysinst(8) post-installation configuration menu, you can obtain it by retrieving the file https://cdn.NetBSD.org/pub/pkgsrc/stable/pkgsrc.tar.gz. It is typically extracted into /usr/pkgsrc (though other locations work fine) with the commands: # cd /usr # tar -zxpf pkgsrc.tar.gz After extracting, see the doc/pkgsrc.txt file in the extraction directory (e.g., /usr/pkgsrc/doc/pkgsrc.txt) for more information. 7. Misc o Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. o Edit /etc/rc.local to run any local daemons you use. o Many of the /etc files are documented in section 5 of the manual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System The easiest way to upgrade to NetBSD 10.0_RC6 is with bina- ries, and that is the method documented here. To do the upgrade, you must have one form of boot media available. You must also have at least the base and kern binary distribution sets available. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previously installed or to account for growth of the sets between releases. Since upgrading involves replacing the kernel, boot blocks, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on the NetBSD partition or on another operat- ing system's partition on your disk before beginning the upgrade process. The upgrade procedure is similar to an installation, but without the hard disk partitioning. Fetching the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for help. File systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 10.0_RC6 system. However, that doesn't mean that you're finished with the upgrade process. You will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this, but if not, you can just cd into /dev, and run the command: # sh MAKEDEV all sysinst will attempt to merge the settings stored in your /etc directory with the new version of NetBSD using the postinstall(8) utility. However, postinstall(8) is only able to deal with changes that are easily automated. It is recommended that you use the etcupdate(8) tool to merge any remaining configuration changes. 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 NetBSD 10.0_RC6. Note that sysinst will automatically invoke postinstall fix and thus all issues that are fixed by postinstall by default will be handled. In NetBSD 9 and earlier, filesystems listed in /etc/fstab would be mounted before non-legacy zfs filesystems. Starting from NetBSD 10 this order has been reversed. If you have ever run a version of NetBSD -current between April 18, 2020 and September 23, 2022 (the version numbers used in the affected time range are between 9.99.56 and 9.99.106) your FFS file systems might have broken extended attributes stored. You should follow this guide: https://wiki.netbsd.org/features/UFS2ea/ before booting the updated system multi-user for the first time. Note that you do not need to do anything special if you never did run any affected kernel, especially if you have never run NetBSD -current. The display drivers used for modern GPUs and the whole sub- system supporting it (DRM/KMS) have been updated to a newer version. Unfortunately not all issues with this have been resolved before the NetBSD 10.0 release. You can find a list of issues in the Open issues with new DRM/KMS: https://wiki.netbsd.org/releng/netbsd-10/ section of the release engineering wiki page. A number of things have been removed from the NetBSD 10.0_RC6 release. See the ``Components removed from NetBSD'' section near the beginning of this document for a list. Using online NetBSD documentation Documentation is available if you installed the manual dis- tribution set. Traditionally, the ``man pages'' (documenta- tion) are denoted by `name(section)'. Some examples of this are o intro(1), o man(1), o apropos(1), o passwd(1), and o passwd(5). The section numbers group the topics into several cate- gories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administra- tive 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 num- bered section name will be displayed. For instance, after logging in, enter # man passwd to read the documentation for passwd(1). To view the docu- mentation for passwd(5), enter # man 5 passwd instead. If you are unsure of what man page you are looking for, enter # apropos subject-word where subject-word is your topic of interest; a list of pos- sibly related man pages will be displayed. 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. See https://www.NetBSD.org/mailinglists/ for details. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org. To report bugs, use the send-pr(1) command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Bugs also can be submitted and queried with the web inter- face at https://www.NetBSD.org/support/send-pr.html There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit https://www.NetBSD.org/mailinglists/ If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below). If you'd like to help with NetBSD, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-users@NetBSD.org. As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appro- priate list about it. If you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to o The former members of UCB's Computer Systems Research Group, including (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their work on BSD systems, support, and encourage- ment. o The Internet Systems Consortium, Inc. for hosting the NetBSD FTP, CVS, AnonCVS, mail, mail archive, GNATS, SUP, Rsync and WWW servers. o The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. o The Columbia University Computer Science Department for hosting the build cluster. o The many organizations that provide NetBSD mirror sites. o Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. o We list the individuals and organizations that have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it at https://www.NetBSD.org/donations/ (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to ver- ify that you wanted to be listed.) o Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in Jan- uary, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to be mentioned, tell us!) Legal Mumbo-Jumbo All product names mentioned herein are trademarks or regis- tered trademarks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this docu- ment: NetBSD is a registered trademark of The NetBSD Foundation, Inc. This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the NetBSD Foun- dation. This product includes software developed by The NetBSD Foun- dation, Inc. and its contributors. This product includes software developed for the NetBSD Project. See https://www.NetBSD.org/ for information about NetBSD. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) This product includes cryptographic software written by Eric Young (eay@mincom.oz.au) This product includes software designed by William Allen Simpson. This product includes software developed at Ludd, University of Lulea. This product includes software developed at Ludd, University of Lulea, Sweden and its contributors. This product includes software developed at the Information Technology Division, US Naval Research Laboratory. This product includes software developed by Aaron Brown and Harvard University. This product includes software developed by Adam Ciarcinski for the NetBSD project. This product includes software developed by Adam Glass. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Alex Zepeda. This product includes software developed by Alex Zepeda, and Colin Wood for the NetBSD Project. This product includes software developed by Allen Briggs. This product includes software developed by Amancio Hasty and Roger Hardiman This product includes software developed by Ben Gray. This product includes software developed by Berkeley Soft- ware Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Bodo Moeller. This product includes software developed by Boris Popov. This product includes software developed by Brini. This product includes software developed by Bruce M. Simp- son. This product includes software developed by Causality Lim- ited. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Han- num. This product includes software developed by Charles M. Han- num, 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 Christian E. Hopps. This product includes software developed by Christian E. Hopps, Ezra Story, Kari Mettinen, Markus Wild, Lutz Vieweg and Michael Teske. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Chuck Silvers. This product includes software developed by Cisco Systems, Inc. This product includes software developed by Colin Wood. This product includes software developed by Colin Wood for the NetBSD Project. This product includes software developed by Computing Ser- vices at Carnegie Mellon University (http://www.cmu.edu/com- puting/). This product includes software developed by Daan Vreeken. This product includes software developed by Daishi Kato This product includes software developed by Daniel Widenfalk and Michael L. Hitch. This product includes software developed by Daniel Widenfalk for the NetBSD Project. This product includes software developed by David Jones and Gordon Ross This product includes software developed by David Miller. This product includes software developed by Dean Huxley. This product includes software developed by Emmanuel Dreyfus This product includes software developed by Eric S. Hvozda. This product includes software developed by Eric S. Raymond This product includes software developed by Eric Young (eay@cryptsoft.com) This product includes software developed by Eric Young (eay@mincom.oz.au) This product includes software developed by Ezra Story. This product includes software developed by Ezra Story and by Kari Mettinen. This product includes software developed by Ezra Story, by Kari Mettinen and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, and Michael Teske. This product includes software developed by Ezra Story, by Kari Mettinen, Michael Teske and by Bernd Ernesti. This product includes software developed by Frank van der Linden for the NetBSD Project. This product includes software developed by Gardner Buchanan. This product includes software developed by Garrett D'Amore. This product includes software developed by Gary Thomas. This product includes software developed by Gordon Ross This product includes software developed by Harvard Univer- sity. This product includes software developed by Harvard Univer- sity and its contributors. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch This product includes software developed by Henrik Vester- gaard Draboel. This product includes software developed by Herb Peyerl. This product includes software developed by Hidetoshi Shimokawa. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Ian W. Dall. This product includes software developed by Intel Corpora- tion and its contributors. This product includes software developed by Internet Initia- tive Japan Inc. This product includes software developed by Internet Research Institute, Inc. This product includes software developed by James R. Maynard III. This product includes software developed by Jared D. McNeill. This product includes software developed by Jason L. Wright 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 Joerg Wunsch This product includes software developed by John Birrell. This product includes software developed by John P. Wit- tkoski. This product includes software developed by John Polstra. This product includes software developed by Jonathan R. Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. 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 Julian High- field. This product includes software developed by K. Kobayashi This product includes software developed by K. Kobayashi and H. Shimokawa This product includes software developed by Kazuhisa Shimizu. This product includes software developed by Kazuki Sakamoto. This product includes software developed by Kenneth Stailey. This product includes software developed by Kiyoshi Ikehara. This product includes software developed by Klaus Burkert,by Bernd Ernesti, by Michael van Elst, and by the University of California, Berkeley and its contributors. This product includes software developed by Kyma Systems. This product includes software developed by Leo Weppelman and Waldi Ravens. This product includes software developed by Lloyd Parkes. This product includes software developed by Lutz Vieweg. This product includes software developed by Marc Horowitz. This product includes software developed by Marcus Comstedt. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Brinicombe for the NetBSD Project. This product includes software developed by Mark Tinguely and Jim Lowe This product includes software developed by Markus Wild. This product includes software developed by Marshall M. Mid- den. This product includes software developed by Masanobu Saitoh. This product includes software developed by Masaru Oki. This product includes software developed by Matt DeBergalis This product includes software developed by Matthew Fre- dette. This product includes software developed by Michael Smith. This product includes software developed by Microsoft This product includes software developed by Mika Kortelainen This product includes software developed by Mike Pritchard. This product includes software developed by Mike Pritchard and contributors. This product includes software developed by Minoura Makoto. This product includes software developed by MINOURA Makoto, Takuya Harakawa. This product includes software developed by Niels Provos. This product includes software developed by Niklas Hal- lqvist. This product includes software developed by Niklas Hal- lqvist, Brandon Creighton and Job de Haas. This product includes software developed by Paolo Abeni. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Paul Mackerras . This product includes software developed by Pedro Roque Mar- ques This product includes software developed by Per Fogelstrom. This product includes software developed by Peter Galbavy. This product includes software developed by Phase One, Inc. This product includes software developed by Philip A. Nel- son. This product includes software developed by QUALCOMM Incor- porated. This product includes software developed by Ravikanth. This product includes software developed by RiscBSD. This product includes software developed by Roar Thronaes. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roger Hardiman This product includes software developed by Rolf Grossmann. This product includes software developed by Ross Harvey. This product includes software developed by Ross Harvey for the NetBSD Project. This product includes software developed by Scott Bartram. This product includes software developed by Scott Stevens. This product includes software developed by Shingo WATANABE. This product includes software developed by Softweyr LLC, the University of California, Berkeley, and its contribu- tors. This product includes software developed by Stephan Thesing. This product includes software developed by Steven M. Bellovin This product includes software developed by Takashi Hamada. This product includes software developed by Takumi Nakamura. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Tommi Komulainen . This product includes software developed by TooLs GmbH. This product includes software developed by Trimble Naviga- tion, Ltd. This product includes software developed by Waldi Ravens. This product includes software developed by WIDE Project and its contributors. This product includes software developed by Winning Strate- gies, Inc. This product includes software developed by Yen Yen Lim and North Dakota State University This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Alice Group. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by the Computer Systems Laboratory at the University of Utah. This product includes software developed by the Harvard Uni- versity and its contributors. This product includes software developed by the Kungliga Tekniska Hoegskolan and its contributors. This product includes software developed by the Network Research Group at Lawrence Berkeley Laboratory. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/) This product includes software developed by the PocketBSD project and its contributors. This product includes software developed by the RiscBSD ker- nel team This product includes software developed by the RiscBSD team. This product includes software developed by the SMCC Tech- nology Development Group at Sun Microsystems, Inc. This product includes software developed by the University of California, Lawrence Berkeley Laboratories. This product includes software developed by the University of California, Lawrence Berkeley Laboratory. This product includes software developed by the University of California, Lawrence Berkeley Laboratory and its contrib- utors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed 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 Urbana-Cham- paign Independent Media Center. This product includes software developed for the FreeBSD project This product includes software developed for the NetBSD Project by Allegro Networks, Inc., and Wasabi Systems, Inc. This product includes software developed for the NetBSD Project by Bernd Ernesti. This product includes software developed for the NetBSD Project by Christopher G. Demetriou. This product includes software developed for the NetBSD Project by Eiji Kawauchi. This product includes software developed for the NetBSD Project by Frank van der Linden This product includes software developed for the NetBSD Project by Genetec Corporation. 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 Jonathan Stone. This product includes software developed for the NetBSD Project by Kyma Systems LLC. This product includes software developed for the NetBSD Project by Matthias Drochner. 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 Shigeyuki Fukushima. This product includes software developed for the NetBSD Project by SUNET, Swedish University Computer Network. This product includes software developed for the NetBSD Project by Wasabi Systems, Inc. This product includes software developed or owned by Caldera International, Inc. This product includes software developed under OpenBSD by Per Fogelstrom. This product includes software developed under OpenBSD by Per Fogelstrom Opsycon AB for RTMX Inc, North Carolina, USA. This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Simi- lar operating systems" includes mainly non-profit oriented systems for research and education, including but not restricted to "NetBSD", "FreeBSD", "Mach" (by CMU). The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase ``this text'' refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html. This notice shall appear on any product containing this material. 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. Some files have the following copyright: Mach Operating System Copyright (c) 1991,1990,1989 Carnegie Mellon Univer- sity All Rights Reserved. Permission to use, copy, modify and distribute this software and its documentation is hereby granted, pro- vided that both the copyright notice and this permis- sion notice appear in all copies of the software, de- rivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation. CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABIL- ITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. Carnegie Mellon requests users of this software to return to Software Distribution Coordinator or Software.Dis- tribution@CS.CMU.EDU School of Computer Science Carnegie Mellon University Pittsburgh PA 15213-3890 any improvements or extensions that they make and grant Carnegie the rights to redistribute these changes. Some files have the following copyright: Copyright (c) 1994, 1995 Carnegie-Mellon University. All rights reserved. Author: Chris G. Demetriou Permission to use, copy, modify and distribute this software and its documentation is hereby granted, pro- vided that both the copyright notice and this permis- sion notice appear in all copies of the software, de- rivative works or modified versions, and any portions thereof, and that both notices appear in supporting documentation. CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. Carnegie Mellon requests users of this software to return to Software Distribution Coordinator or Software.Dis- tribution@CS.CMU.EDU School of Computer Science Carnegie Mellon University Pittsburgh PA 15213-3890 any improvements or extensions that they make and grant Carnegie the rights to redistribute these changes. Some files have the following copyright: Copyright 1996 The Board of Trustees of The Leland Stanford Junior University. All Rights Reserved. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies. Stanford Uni- versity makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. The End NetBSD/hppa 10.0_RC6 Mar 12, 2024 NetBSD/hppa 10.0_RC6