INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL -- Installation procedure for NetBSD/evbarm. CCOONNTTEENNTTSS About this Document What is NetBSD? Dedication Changes Between The NetBSD 8 and 9 Releases Installation and Partitioning Changes Features to be removed in a later release The NetBSD Foundation Sources of NetBSD NetBSD 9.0 Release Contents NetBSD/evbarm subdirectory structure Binary distribution sets NetBSD/evbarm System Requirements and Supported Devices Supported devices (Technologic Systems TS-7200) TS-5620 Real Time Clock Serial ports Ethernet adapters Other on-board functions Supported devices (ARM, Ltd. Integrator) PrimeCell PL030 Real Time Clock Serial ports SCSI host adapters Ethernet adapters Supported devices (Intel IQ80310) Serial ports Ethernet adapters i80312 Companion I/O functions Supported devices (Intel IQ80321) Serial ports Ethernet adapters i80321 I/O Processor functions Supported devices (Team ASA Npwr) Serial ports SCSI host adapters Ethernet adapters Supported devices (Intel IXM1200) Serial ports Ethernet adapters Supported devices (Samsung SMDK2800) Serial ports Supported devices (ADI BRH) Serial ports Ethernet adapters Supported devices (Arcom Viper) Serial ports Ethernet adapters Getting the NetBSD System on to Useful Media Preparing your System for NetBSD installation Preparation for the Technologic Systems TS-7200 Preparation for the Intel IQ80310 Preparation for the Intel IQ80321 Installing the NetBSD System Installation for the Technologic Systems TS-7200 Installation for the Intel IQ80310 Installation for the Intel IQ80321 Post installation steps Upgrading a previously-installed NetBSD System Compatibility Issues With Previous NetBSD Releases Important note regarding ABI change on ARM ports Using online NetBSD documentation Administrivia Thanks go to Legal Mumbo-Jumbo The End DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 9.0 on the _e_v_b_a_r_m platform. It is available in four different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is one of _._p_s, _._h_t_m_l, _._m_o_r_e, or _._t_x_t: _._p_s PostScript. _._h_t_m_l Standard Internet HTML. _._m_o_r_e 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 _m_a_n pages are generally presented. _._t_x_t Plain old ASCII. You are reading the _m_o_r_e version. WWhhaatt iiss NNeettBBSSDD?? The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the Univer- sity of California, 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 9.0 release contains complete binary releases for most of these system architectures, with pre- liminary support for the others included in source form. Please see the NetBSD _w_e_b_s_i_t_e_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg// 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. DDeeddiiccaattiioonn NetBSD 9.0 is dedicated to the memory of Matthias Drochner, who passed away in August 2018 and Eric Schnoebelen, who passed away in March 2019. Matthias' technical contributions are too many to list here in full. He was a long term contributor and commited more than 3000 changes all over the NetBSD source tree and lately was especially active in keeping some of our most weired ancient VME architectures in shape. Eric was a long term pkgsrc developer and well known commu- nity member. Beyond their technical contributions, Eric and Matthias were always helpful and friendly. Their example encouraged users to contribute to the project and share their work with the community. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 88 aanndd 99 RReelleeaasseess The NetBSD 9.0 release provides many significant changes, including support for many new devices, hundreds of bug fixes, new and updated kernel subsystems, and numerous user- land enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize the massive devel- opment that went into the NetBSD 9.0 release. The complete list of changes can be found in the following files: _C_H_A_N_G_E_S_: hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--99..00//CCHHAANNGGEESS _C_H_A_N_G_E_S_-_9_._0_: hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--99..00//CCHHAANNGGEESS--99..00 files in the top level directory of the NetBSD 9.0 release tree. _I_n_s_t_a_l_l_a_t_i_o_n _a_n_d _P_a_r_t_i_t_i_o_n_i_n_g _C_h_a_n_g_e_s The sysinst installation program has been reworked for this release. It now supports arbitrary big disks and offers GPT parti- tions as alternative to MBR/fdisk partitions on a lot archi- tectures. Unfortunately it has not been tested on all hardware sup- ported by NetBSD. If you have problems partitioning the target disk or installing the system, please report bugs with as much details as possible. See the Administrivia section below on how to report bugs or contact other users and ask for support. FFeeaattuurreess ttoo bbee rreemmoovveedd iinn aa llaatteerr rreelleeaassee The following features are to be removed from NetBSD in the future: ++oo groff(1). Man pages are now handled with mandoc(1), and groff(1) can still be found in pkgsrc as _t_e_x_t_p_r_o_c_/_g_r_o_f_f. TThhee NNeettBBSSDD FFoouunnddaattiioonn 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: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ffoouunnddaattiioonn// SSoouurrcceess ooff NNeettBBSSDD Refer to _m_i_r_r_o_r_s_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmiirrrroorrss// NNeettBBSSDD 99..00 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 9.0 release is organized as follows: _._._._/_N_e_t_B_S_D_-_9_._0_/ CHANGES Changes between the 8.0 and 9.0 releases. CHANGES-9.0 Changes between the initial 9.0 branch and final release of 9.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. _i_m_a_g_e_s_/ Images (ISO 9660 or USB) for installing NetBSD. Depending on your system, these may be bootable. _s_o_u_r_c_e_/ 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 9.0 has a binary distribution. The source distribution sets can be found in subdirectories of the _s_o_u_r_c_e subdirectory of the distribution tree. They contain the complete sources to the system. The source dis- tribution sets are as follows: ggnnuussrrcc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. sshhaarreessrrcc 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. ssrrcc This set contains all of the base NetBSD 9.0 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. ssyyssssrrcc This set contains the sources to the NetBSD 9.0 kernel for all architectures as well as the config(1) utility. xxssrrcc This set contains the sources to the X Window Sys- tem. All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the ppkkggssrrcc set, which is traditionally unpacked into _/_u_s_r_/_p_k_g_s_r_c, all sets may be unpacked into _/_u_s_r_/_s_r_c with the command: # ccdd // ;; ttaarr --zzxxppff sseett__nnaammee..ttggzz 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: cckkssuumm --aa MMDD55 _f_i_l_e. SHA512 SHA512 digests in the format produced by the command: cckkssuumm --aa SSHHAA551122 _f_i_l_e. 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. _N_e_t_B_S_D_/_e_v_b_a_r_m _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The evbarm-specific portion of the NetBSD 9.0 release is found in the _e_v_b_a_r_m subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_9_._0_/_e_v_b_a_r_m_/. It contains the following files and directories: _I_N_S_T_A_L_L_._h_t_m_l _I_N_S_T_A_L_L_._p_s _I_N_S_T_A_L_L_._t_x_t _I_N_S_T_A_L_L_._m_o_r_e Installation notes in various file formats, including this file. The _._m_o_r_e file contains underlined text using the more(1) conventions for indicating italic and bold display. _b_i_n_a_r_y_/ _k_e_r_n_e_l_/ _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z A gzipped NetBSD kernel containing code for every- thing supported in this release. _s_e_t_s_/ evbarm binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _m_i_s_c_/ Miscellaneous evbarm installation utilities; see installation section below. _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD evbarm binary distribution sets contain the bina- ries which comprise the NetBSD 9.0 release for evbarm. The binary distribution sets can be found in the _e_v_b_a_r_m_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 9.0 distribu- tion tree, and are as follows: bbaassee The NetBSD 9.0 evbarm bbaassee binary distribution. You _m_u_s_t install this distribution set. It con- tains the base NetBSD utilities that are necessary for the system to run and be minimally functional. ccoommpp Things needed for compiling programs. This set includes the system include files (_/_u_s_r_/_i_n_c_l_u_d_e) and the various system libraries (except the shared libraries, which are included as part of the bbaassee 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. ddeebbuugg This distribution set contains debug information for all base system utilities. It is useful when reporting issues with binaries or during develope- ment. This set is huge, if the target disk is small, do not install it. eettcc This distribution set contains the system configu- ration files that reside in _/_e_t_c and in several other places. This set _m_u_s_t be installed if you are installing the system from scratch, but should _n_o_t be used if you are upgrading. ggaammeess This set includes the games and their manual pages. kkeerrnn--IINNTTEEGGRRAATTOORR (see below) kkeerrnn--IIQQ8800331100 (see below) kkeerrnn--IIQQ8800332211 (see below) kkeerrnn--TTEEAAMMAASSAA__NNPPWWRR These sets contain a NetBSD/evbarm 9.0 kernel, named _/_n_e_t_b_s_d. Some of these sets also contain a binary format kernel named _/_n_e_t_b_s_d_._b_i_n and an S- record format kernel named _/_n_e_t_b_s_d_._s_r_e_c that your firmware may need to boot. You _m_u_s_t install the kernel that matches your hardware. mmaann This set includes all of the manual pages for the binaries and other software contained in the bbaassee set. Note that it does not include any of the man- ual pages that are included in the other sets. mmiisscc This set includes the system dictionaries, the typesettable document set, and other files from _/_u_s_r_/_s_h_a_r_e. mmoodduulleess This set includes kernel modules to add functional- ity to a running system. rreessccuuee This set includes the statically linked emergency recover binaries installed in _/_r_e_s_c_u_e. tteexxtt 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: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. xxccoommpp The extra libraries and include files needed to compile X source code. xxddeebbuugg This distribution set contains debug information for all X11 binaries. It is useful when reporting issues with these binaries or during developement. This set is huge, if the target disk is small, do not install it. xxffoonntt Fonts needed by the X server and by X clients. xxeettcc Configuration files for X which could be locally modified. xxsseerrvveerr The X server. The evbarm binary distribution sets are distributed as gzipped tar files named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z. 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 _b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the ttaarr --xxzzppff command from the root directory ( _/ ) of your system. _N_o_t_e_: Each directory in the evbarm binary distribution also has its own checksum files, just as the source dis- tribution does. NNeettBBSSDD//eevvbbaarrmm SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess NetBSD 9.0 runs on the following ARM architecture evaluation boards: ++oo Technologic Systems TS-7200 ++oo ARM, Ltd. Integrator ++oo Intel IQ80310 ++oo Intel IQ80321 ++oo Team ASA, Inc. Npwr ++oo Intel IXM1200 ++oo Samsung SMDK2800 ++oo ADI Engineering, Inc. BRH ("Big Red Head") ++oo Arcom Viper _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_T_e_c_h_n_o_l_o_g_i_c _S_y_s_t_e_m_s _T_S_-_7_2_0_0_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo TS-5620 Real Time Clock ++oo Serial ports -- On-chip EP9302 UARTs -- TS-SER1, TS-SER2, TS-SER4 PC/104 serial adapters -- TS-MODEM, TS-MODEM2 PC/104 land-line/cellular modems ++oo Ethernet adapters -- On-chip EP9302 10/100 ethernet -- TS-ETH10 PC/104 expansion ethernet adapters ++oo Other on-board functions -- CompactFlash socket -- USB OHCI host -- Text-mode HD44780 LCD display header -- Matrix keypad/GPIO header -- Board temperature sensor and watchdog timer _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_A_R_M_, _L_t_d_. _I_n_t_e_g_r_a_t_o_r_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo PrimeCell PL030 Real Time Clock ++oo Serial ports -- PrimeCell PL010 UART ++oo SCSI host adapters -- Adaptec AHA-2910, 2915, 2920, and 2930C adapters. -- Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs using the AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880 and AIC-789x chipsets. -- Adaptec AHA-394x[U][W] cards [b] -- Adaptec AHA-3950U2 cards -- Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters ++oo Ethernet adapters -- Intel i82557, i82558, i82559, i82550 _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_I_n_t_e_l _I_Q_8_0_3_1_0_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo Serial ports -- On-board ST16c550 UARTs ++oo Ethernet adapters -- Intel i82557, i82558, i82559, i82550 ++oo i80312 Companion I/O functions -- General Purpose I/O unit _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_I_n_t_e_l _I_Q_8_0_3_2_1_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo Serial ports -- On-board TI 16550 UART ++oo Ethernet adapters -- Intel i82542, i82543, i85244 Gigabit Ethernet ++oo i80321 I/O Processor functions -- Application Accelerator Unit -- Watchdog timer _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_T_e_a_m _A_S_A _N_p_w_r_) The Npwr is a storage appliance based on the Intel IOP310 I/O processor chipset. This is an exhaustive list of devices supported on the Npwr as the Npwr has no expansion capability. ++oo Serial ports -- On-board TI 16550 UART ++oo SCSI host adapters -- On-board LSI Logic 53c1010 Ultra160 SCSI adapter ++oo Ethernet adapters -- On-board Intel i82544 Gigabit Ethernet _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_I_n_t_e_l _I_X_M_1_2_0_0_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo Serial ports -- IXP1200 on-chip serial port ++oo Ethernet adapters -- Intel i82557, i82558, i82559, i82550 _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_S_a_m_s_u_n_g _S_M_D_K_2_8_0_0_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo Serial ports -- S3C2800 on-chip serial ports _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_A_D_I _B_R_H_) For devices that have machine-independent drivers, this is not an exhaustive list, but merely reflects the devices that have been tested on this platform. ++oo Serial ports -- On-board TI 16752 DUART ++oo Ethernet adapters -- Intel i82557, i82558, i82559, i82550 -- Intel i82544, i82546 Gigabit Ethernet _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s _(_A_r_c_o_m _V_i_p_e_r_) Current this is an exhaustive list, since expansion ports such as PC/104 and USB are not yet supported. ++oo Serial ports -- On-chip PXA255 UARTs Ethernet adapters -- On-board SMC91C111 GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa Installation is supported from several media types, includ- ing: ++oo CD-ROM / DVD / USB-stick ++oo FTP ++oo Remote NFS partition ++oo Tape ++oo 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. _C_D_-_R_O_M _/ _D_V_D _/ _U_S_B_-_s_t_i_c_k Find out where the distribution set files are on the CD-ROM, DVD or USB stick. Likely locations are _b_i_n_a_r_y_/_s_e_t_s and _e_v_b_a_r_m_/_b_i_n_a_r_y_/_s_e_t_s. (You only need to know this if you are mix- ing 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. _F_T_P 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. _N_F_S 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 _/_e_t_c_/_e_x_p_o_r_t_s 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. _T_a_p_e 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: # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e _d_i_s_t___s_e_t_s where _t_a_p_e___d_e_v_i_c_e is the name of the tape device that represents the tape drive you're using. This might be _/_d_e_v_/_r_s_t_0, or something similar, but it will vary from system to system. In the above example, _d_i_s_t___s_e_t_s is a list of filenames corresponding to the distribution sets that you wish to place on the tape. For instance, to put the kkeerrnn--GGEENNEERRIICC,, bbaassee,, and eettcc distributions on tape (the absolute minimum required for installation), you would do the following: # ccdd ......//NNeettBBSSDD--99..00 # ccdd eevvbbaarrmm//bbiinnaarryy # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e kkeerrnn--GGEENNEERRIICC..ttggzz bbaassee..ttggzz eettcc..ttggzz _N_o_t_e_: You still need to fill in _t_a_p_e___d_e_v_i_c_e 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. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn First and foremost, before beginning the installation process, _m_a_k_e _s_u_r_e _y_o_u _h_a_v_e _a _r_e_l_i_a_b_l_e _b_a_c_k_u_p of any data on the target system that you wish to keep. Mistakes in parti- tioning may lead to data loss. _P_r_e_p_a_r_a_t_i_o_n _f_o_r _t_h_e _T_e_c_h_n_o_l_o_g_i_c _S_y_s_t_e_m_s _T_S_-_7_2_0_0 The TS-7200 uses RedBoot firmware which supports loading the kernel via serial port and the on-chip Ethernet. These notes assume that the Ethernet will be used to load the ker- nel. RedBoot can either use TFTP or HTTP to load the kernel via the network. These notes also assume the TS-7200 will be run from the CompactFlash; that a FFS filesystem on the CompactFlash card will provide the root file system. The minimum size of the CompactFlash card is 64MB with 512MB being the recommended minimum size if attempting a full installation. The first step to install NetBSD is to interrupt normal sys- tem bootup and drop to the RedBoot prompt by hitting Ctrl-C immediately after applying power. To load both the instal- lation kernel and the generic post-installation TS7200 ker- nel you will need network connectivity from RedBoot which you will have to configure using the RedBoot ffccoonnffiigg com- mand; see the RedBoot documentation for more information. A compressed kernel image and loader suitable for placing into flash is provided with the distribution. Use of this image is optional; a kernel that can be directly loaded over the network by RedBoot is also provided. The image for the TS-7200 can be found under the NetBSD/evbarm 9.0 distribution directory in _e_v_b_a_r_m_/_b_i_n_a_r_y_/_g_z_i_m_g_/_g_z_i_m_g___T_S_7_2_0_0___f_l_a_s_h___0_x_6_0_6_6_0_0_0_0_._g_z, and corresponds to the kernel in _e_v_b_a_r_m_/_b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_T_S_7_2_0_0_._g_z. The following steps describe how to copy the compressed kernel image into flash. 1. Uncompress the gzimg file and place it into the TFTP server's download area (note, the kernel inside the gzimg is still compressed after this step). server# ggzzccaatt ggzziimmgg__TTSS77220000__ffllaasshh__00xx6600666600000000..ggzz >> //ttffttppbboooott//ggzziimmgg__TTSS77220000__ffllaasshh__00xx6600666600000000 2. Load the gzimg from the TFTP server. RedBoot> load -r -b 0x00200000 gzimg_TS7200_flash_0x60660000 Raw file loaded 0x00200000-0x00605fe0 3. Use the RedBoot ffiiss command to copy the image into flash. For more information on the RedBoot Flash Image System, see the RedBoot documentation. The factory default Linux image may already be present in flash and must be deleted before continuing. RedBoot> fis delete vmlinux RedBoot> fis create -b 0x00200000 -f 0x60660000 -l 0x00160000 netbsd.gz Once the compressed kernel image has been copied into flash, it may be started by jumping to the flash address of the image: RedBoot> g 0x60660000 _P_r_e_p_a_r_a_t_i_o_n _f_o_r _t_h_e _I_n_t_e_l _I_Q_8_0_3_1_0 The IQ80310 uses RedBoot firmware from Red Hat, Inc. Red- Boot supports loading the kernel via the serial port and the on-board Ethernet. These notes assume that the Ethernet will be used to load the kernel. RedBoot uses the Trivial File Transfer Protocol (TFTP) to load the kernel via the network. These notes also assume that the IQ80310 will be run as a diskless system; that an NFS server will provide the root file system. The NetBSD kernel uses the Dynamic Host Con- figuration Protocol (DHCP) to obtain network address and root file system information. The first step is to configure your DHCP, NFS, and TFTP server software. You will need the MAC address for the on- board Ethernet, which RedBoot can provide; see the RedBoot documentation for more information. The next step is to configure RedBoot to obtain its IP address from your DHCP server; see the RedBoot documentation for more information. Once your DHCP server and RedBoot are properly configured, you should see information similar to the following when the IQ80310 is reset or powered-up: RedBoot(tm) debug environment - built 17:16:14, Feb 12 2001 Platform: IQ80310 (XScale) Copyright (C) 2000, Red Hat, Inc. RAM: 0xa0000000-0xa2000000 FLASH: 0x00000000 - 0x00800000, 64 blocks of 0x00020000 bytes each. IP: 192.168.0.10, Default server: 192.168.0.1 RedBoot> A compressed kernel image and loader suitable for placing into flash is provided with the distribution. Use of this image is optional; a kernel that can be directly loaded over the network by RedBoot is also provided. The image for the IQ80310 can be found under the NetBSD/evbarm 9.0 distribution directory in _e_v_b_a_r_m_/_b_i_n_a_r_y_/_g_z_i_m_g_/_g_z_i_m_g___I_Q_8_0_3_1_0___f_l_a_s_h___0_x_0_0_0_8_0_0_0_0_._g_z, and corresponds to the kernel in _e_v_b_a_r_m_/_b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_I_Q_8_0_3_1_0_._g_z. The following steps describe how to copy the compressed kernel image into flash. 1. Uncompress the gzimg file and place it into the TFTP server's download area (note, the kernel inside the gzimg is still compressed after this step). server# ggzzccaatt ggzziimmgg__IIQQ8800331100__ffllaasshh__00xx0000008800000000..ggzz >> //ttffttppbboooott//ggzziimmgg__IIQQ8800331100__ffllaasshh__00xx0000008800000000 2. Load the gzimg from the TFTP server. RedBoot> load -r -b 0xa0200000 gzimg_IQ80310_flash_0x00080000 Raw file loaded 0xa0200000-0xa0305fe0 3. Use the RedBoot ffiiss command to copy the image into flash. For more information on the RedBoot Flash Image System, see the RedBoot documentation. RedBoot> fis create -b 0xa0200000 -f 0x00080000 -l 0x00200000 netbsd.gz ... Erase from 0x00080000-0x00280000: .................... ... Program from 0xa0200000-0xa0400000 at 0x00080000: .................... ... Unlock from 0x007e0000-0x00800000:. ... Erase from 0x007e0000-0x00800000:. ... Program from 0xa1fd0000-0xa1ff0000 at 0x007e0000:. ... Lock from 0x007e0000-0x00800000:. Once the compressed kernel image has been copied into flash, it may be started by jumping to the flash address of the image: RedBoot> g 0x00080000 >> NetBSD/IQ80310 Gzip Boot, Revision 1.1 >> (root@tgm, Thu Mar 28 18:32:45 PST 2002) >> RAM 0xa0000000 - 0xafffffff, heap at 0xaffd0000 >> Load address: 0xa0200000 >> Image size: 741244 Uncompressing image...done. Jumping to image @ 0xa0200000... NetBSD/evbarm (IQ80310) booting ... Resetting secondary PCI bus... initarm: Configuring system ... physmemory: 65536 pages at 0xa0000000 -> 0xafffffff init subsystems: stacks vectors undefined pmap irq done. [ using 155084 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5ZC (IQ80310) #20: Fri Mar 29 10:25:53 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80310 total memory = 256 MB avail memory = 232 MB using 1228 buffers containing 13208 KB of memory mainbus0 (root) cpu0 at mainbus0: i80200 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0: board rev. F, CPLD rev. D, backplane present com0 at obio0 addr 0xfe810000: ns16550a, working fifo com0: console com1 at obio0 addr 0xfe800000: ns16550a, working fifo iopxs0 at mainbus0: i80312 Companion I/O, acting as PCI host iopxs0: configuring Secondary PCI bus pci0 at iopxs0 bus 1 pci0: i/o space, memory space enabled ppb0 at pci0 dev 7 function 0: Digital Equipment DECchip 21154 PCI-PCI Bridge (rev. 0x05) pci1 at ppb0 bus 2 pci1: i/o space, memory space enabled fxp0 at pci1 dev 0 function 0: i82559S Ethernet, rev 9 fxp0: interrupting at iq80310 irq 1 fxp0: Ethernet address 00:80:4d:46:0b:b9 inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: root device: _P_r_e_p_a_r_a_t_i_o_n _f_o_r _t_h_e _I_n_t_e_l _I_Q_8_0_3_2_1 The IQ80321 uses RedBoot firmware from Red Hat, Inc. Red- Boot supports loading the kernel via the serial port and the on-board Ethernet. These notes assume that the Ethernet will be used to load the kernel. RedBoot uses the Trivial File Transfer Protocol (TFTP) to load the kernel via the network. These notes also assume that the IQ80321 will be run as a diskless system; that an NFS server will provide the root file system. The NetBSD kernel uses the Dynamic Host Con- figuration Protocol (DHCP) to obtain network address and root file system information. The first step is to configure your DHCP, NFS, and TFTP server software. You will need the MAC address for the on- board Ethernet, which RedBoot can provide; see the RedBoot documentation for more information. The next step is to configure RedBoot to obtain its IP address from your DHCP server; see the RedBoot documentation for more information. Once your DHCP server and RedBoot are properly configured, you should see information similar to the following when the IQ80321 is reset or powered-up: Ethernet eth0: MAC address 00:07:e9:03:38:40 IP: 192.168.0.11, Default server: 192.168.0.1 RedBoot(tm) bootstrap and debug environment [ROM] Non-certified release, version UNKNOWN - built 11:21:56, Feb 1 2002 Platform: IQ80321 (XScale) Copyright (C) 2000, 2001, 2002, Red Hat, Inc. RAM: 0x00000000-0x08000000, 0x00017008-0x01ddd000 available FLASH: 0xf0000000 - 0xf0800000, 64 blocks of 0x00020000 bytes each. RedBoot> A compressed kernel image and loader suitable for placing into flash is provided with the distribution. Use of this image is optional; a kernel that can be directly loaded over the network by RedBoot is also provided. The image for the IQ80321 can be found under the NetBSD/evbarm 9.0 distribution directory in _e_v_b_a_r_m_/_b_i_n_a_r_y_/_g_z_i_m_g_/_g_z_i_m_g___I_Q_8_0_3_2_1___f_l_a_s_h___0_x_f_0_0_8_0_0_0_0_._g_z, and corresponds to the kernel in _e_v_b_a_r_m_/_b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_I_Q_8_0_3_2_1_._g_z. The following steps describe how to copy the compressed kernel image into flash. 1. Uncompress the gzimg file and place it into the TFTP server's download area (note, the kernel inside the gzimg is still compressed after this step). server# ggzzccaatt ggzziimmgg__IIQQ8800332211__ffllaasshh__00xxff00008800000000..ggzz >> //ttffttppbboooott//ggzziimmgg__IIQQ8800332211__ffllaasshh__00xxff00008800000000 2. Load the gzimg from the TFTP server. RedBoot> load -r -b 0x00200000 gzimg_IQ80321_flash_0xf0080000 Raw file loaded 0x00200000-0x00305fe4 3. Use the RedBoot ffiiss command to copy the image into flash. For more information on the RedBoot Flash Image System, see the RedBoot documentation. RedBoot> fis create -b 0x00200000 -f 0xf0080000 -l 0x00200000 netbsd.gz * CAUTION * about to program 'netbsd.gz' at 0xf0080000..0xf027ffff from 0x00200000 - are you sure (y/n)? y ... Erase from 0xf0080000-0xf0280000: ....................... ... Program from 0x00200000-0x00400000 at 0xf0080000: ...................... ... Unlock from 0xf07e0000-0xf0800000:. ... Erase from 0xf07e0000-0xf0800000:. ... Program from 0x01ddf000-0x01dff000 at 0xf07e0000:. ... Lock from 0xf07e0000-0xf0800000:. Once the compressed kernel image has been copied into flash, it may be started by jumping to the flash address of the image: RedBoot> g 0xf0080000 >> NetBSD/IQ80321 Gzip Boot, Revision 1.1 >> (root@tgm, Thu Mar 28 18:32:45 PST 2002) >> RAM 0xa0000000 - 0xa7ffffff, heap at 0xa7fd0000 >> Load address: 0xa0200000 >> Image size: 739495 Uncompressing image...done. Jumping to image @ 0xa0200000... NetBSD/evbarm (IQ80321) booting ... initarm: Configuring system ... physmemory: 32768 pages at 0xa0000000 -> 0xa7ffffff init subsystems: stacks vectors undefined pmap irq done. [ using 155076 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5ZC (IQ80321) #1: Thu Mar 28 18:31:58 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80321 total memory = 128 MB avail memory = 113 MB using 1228 buffers containing 6656 KB of memory mainbus0 (root) cpu0 at mainbus0: i80321 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0 com0 at obio0 addr 0xfe800000: ns16550a, working fifo com0: console iopxs0 at mainbus0: i80321 I/O Processor, acting as PCI host iopxs0: configuring PCI bus pci0 at iopxs0 bus 0 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok wm0 at pci0 dev 4 function 0: Intel i82544 1000BASE-T Ethernet, rev. 2 wm0: interrupting at iop321 irq 27 wm0: Ethernet address 00:07:e9:03:38:40 makphy0 at wm0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 0 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: root device: IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm _I_n_s_t_a_l_l_a_t_i_o_n _f_o_r _t_h_e _T_e_c_h_n_o_l_o_g_i_c _S_y_s_t_e_m_s _T_S_-_7_2_0_0 The following steps describe how to set up a CompactFlash card for the TS-7200. The TS-7200 can use the interactive installation program ssyyssiinnsstt to perform an internet instal- lation from ftp.netbsd.org on the CompactFlash. 1. Place the netbsd-TS7200_INSTALL.bin kernel into the TFTP server's download area. It must be decompressed from the gzipped image in the release directory evbarm/installation/instkernel/netbsd- TS7200_INSTALL.srec.gz server# gguunnzziipp nneettbbssdd--TTSS77220000__IINNSSTTAALLLL..ssrreecc..ggzz server# ccpp nneettbbssdd--TTSS77220000__IINNSSTTAALLLL..ssrreecc //ttffttppbboooott//nneettbbssdd--TTSS77220000__IINNSSTTAALLLL 2. Load the kernel from the TFTP server. RedBoot> load netbsd-TS7200_INSTALL 3. Start the kernel running. RedBoot> go The kernel will display boot messages, probe for devices, and invoke the interactive sysinst installa- tion tool. Once sysinst has completed installation, the system will reboot back into RedBoot. If the preparation instructions above have been followed, the post-installation NetBSD kernel will be in the FIS ready to be jumped into. You can have RedBoot automat- ically start NetBSD by putting the command ggoo 00xx6600666600000000 into the RedBoot bootscript using the ffccoonnffiigg command. _I_n_s_t_a_l_l_a_t_i_o_n _f_o_r _t_h_e _I_n_t_e_l _I_Q_8_0_3_1_0 The following steps describe how to set up an NFS root envi- ronment for the IQ80310 and how to boot the IQ80310. 1. Place the kernel into the TFTP server's download area. RedBoot only loads S-Records, so select a kernel with the ``.srec'' filename suffix. In this example, we will boot the kernel hard-wired to use the on-board Ethernet as the root device. server# ccpp nneettbbssdd--ffxxpp00..ssrreecc //ttffttppbboooott//nneettbbssdd--iiqq8800331100--ffxxpp00 2. Unpack the distribution sets into the target's root directory. server# ccdd //eexxppoorrtt//cclliieenntt//iiqq8800331100 server# ggzzccaatt ......//bbaassee..ttggzz | ttaarr xxvvppff -- server# ggzzccaatt ......//eettcc..ttggzz | ttaarr xxvvppff -- [repeat for all sets you wish to unpack] 3. Load the kernel from the TFTP server. RedBoot> load netbsd-iq80310-fxp0 Entry point: 0xa0200000, address range: 0xa0200000-0xa035e07c RedBoot> 4. Start the kernel running. The kernel will display boot message, probe for devices, and mount the root file system. If you used a kernel hard-wired to use the on- board Ethernet, it will attempt to mount the root file system automatically. Otherwise, it will prompt for the root device to use. Since the system's run-time environment has not yet been configured, the system should boot into single- user mode. RedBoot> go NetBSD/evbarm (IQ80310) booting ... Resetting secondary PCI bus... initarm: Configuring system ... physmemory: 65536 pages at 0xa0000000 -> 0xafffffff init subsystems: stacks vectors undefined pmap irq done. [ using 155084 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5ZC (IQ80310) #20: Fri Mar 29 10:25:53 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80310 total memory = 256 MB avail memory = 232 MB using 1228 buffers containing 13208 KB of memory mainbus0 (root) cpu0 at mainbus0: i80200 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0: board rev. F, CPLD rev. D, backplane present com0 at obio0 addr 0xfe810000: ns16550a, working fifo com0: console com1 at obio0 addr 0xfe800000: ns16550a, working fifo iopxs0 at mainbus0: i80312 Companion I/O, acting as PCI host iopxs0: configuring Secondary PCI bus pci0 at iopxs0 bus 1 pci0: i/o space, memory space enabled ppb0 at pci0 dev 7 function 0: Digital Equipment DECchip 21154 PCI-PCI Bridge (rev. 0x05) pci1 at ppb0 bus 2 pci1: i/o space, memory space enabled fxp0 at pci1 dev 0 function 0: i82559S Ethernet, rev 9 fxp0: interrupting at iq80310 irq 1 fxp0: Ethernet address 00:80:4d:46:0b:b9 inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: root on fxp0 nfs_boot: trying DHCP/BOOTP nfs_boot: DHCP next-server: 192.168.0.1 nfs_boot: my_name=iq80310.lab.wasabisystems.com nfs_boot: my_domain=wasabisystems.com nfs_boot: my_addr=192.168.0.10 nfs_boot: my_mask=255.255.255.0 nfs_boot: gateway=192.168.0.254 root on 192.168.0.1:/export/client/iq80310 /etc/rc.conf is not configured. Multiuser boot aborted. Enter pathname of shell or RETURN for sh: _I_n_s_t_a_l_l_a_t_i_o_n _f_o_r _t_h_e _I_n_t_e_l _I_Q_8_0_3_2_1 The following steps describe how to set up an NFS root envi- ronment for the IQ80321 and how to boot the IQ80321. 1. Place the kernel into the TFTP server's download area. RedBoot only loads S-Records, so select a kernel with the ``.srec'' filename suffix. In this example, we will boot the kernel hard-wired to use the on-board Ethernet as the root device. server# ccpp nneettbbssdd--wwmm00..ssrreecc //ttffttppbboooott//nneettbbssdd--iiqq8800332211--wwmm00 2. Unpack the distribution sets into the target's root directory. server# ccdd //eexxppoorrtt//cclliieenntt//iiqq8800332211 server# ggzzccaatt ......//bbaassee..ttggzz | ttaarr xxvvppff -- server# ggzzccaatt ......//eettcc..ttggzz | ttaarr xxvvppff -- [repeat for all sets you wish to unpack] 3. Load the kernel from the TFTP server. RedBoot> load netbsd-iq80321-wm0 Entry point: 0x00200000, address range: 0x00200000-0x00396a40 RedBoot> 4. Start the kernel running. The kernel will display boot message, probe for devices, and mount the root file system. If you used a kernel hard-wired to use the on- board Ethernet, it will attempt to mount the root file system automatically. Otherwise, it will prompt for the root device to use. Since the system's run-time environment has not yet been configured, the system should boot into single- user mode. RedBoot> go NetBSD/evbarm (IQ80321) booting ... initarm: Configuring system ... physmemory: 32768 pages at 0xa0000000 -> 0xa7ffffff init subsystems: stacks vectors undefined pmap irq done. [ using 156468 bytes of netbsd ELF symbol table ] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5ZC (IQ80321) #1: Thu Mar 28 18:20:34 PST 2002 root@tgm:/u1/netbsd/src/sys/arch/evbarm/compile/IQ80321 total memory = 128 MB avail memory = 113 MB using 1228 buffers containing 6656 KB of memory mainbus0 (root) cpu0 at mainbus0: i80321 step A-0 (XScale core) cpu0: DC enabled IC enabled WB enabled LABT cpu0: 32KB/32B 32-way Instruction cache cpu0: 32KB/32B 32-way write-back-locking Data cache obio0 at mainbus0 com0 at obio0 addr 0xfe800000: ns16550a, working fifo com0: console iopxs0 at mainbus0: i80321 I/O Processor, acting as PCI host iopxs0: configuring PCI bus pci0 at iopxs0 bus 0 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok wm0 at pci0 dev 4 function 0: Intel i82544 1000BASE-T Ethernet, rev. 2 wm0: interrupting at iop321 irq 27 wm0: Ethernet address 00:07:e9:03:38:40 makphy0 at wm0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 0 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto clock: hz=100 stathz=0 profhz=0 boot device: root on wm0 nfs_boot: trying DHCP/BOOTP nfs_boot: DHCP next-server: 192.168.0.1 nfs_boot: my_name=iq80321.lab.wasabisystems.com nfs_boot: my_domain=wasabisystems.com nfs_boot: my_addr=192.168.0.11 nfs_boot: my_mask=255.255.255.0 nfs_boot: gateway=192.168.0.254 root on 192.168.0.1:/export/client/iq80321 /etc/rc.conf is not configured. Multiuser boot aborted. Enter pathname of shell or RETURN for sh: PPoosstt iinnssttaallllaattiioonn sstteeppss 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 _/_e_t_c_/_r_c_._c_o_n_f If you or the installation software haven't done any configuration of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt 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 _/_b_i_n_/_s_h prompt. If you are asked for a terminal type, respond with vvtt222200 (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: # ssttttyy eerraassee ''^^hh'' # ssttttyy eerraassee ''^^??'' At this point, you need to configure at least one file in the _/_e_t_c directory. You will need to mount your root file system read/write with: # //ssbbiinn//mmoouunntt --uu --ww // Change to the _/_e_t_c directory and take a look at the _/_e_t_c_/_r_c_._c_o_n_f 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 _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where some in-line doc- umentation may be found. More complete documentation can be found in rc.conf(5). When you have finished editing _/_e_t_c_/_r_c_._c_o_n_f, type eexxiitt 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 _/_e_t_c_/_r_c_._c_o_n_f for a networked environment are _h_o_s_t_n_a_m_e and possibly _d_e_f_a_u_l_t_r_o_u_t_e. You may also need to add an _i_f_c_o_n_f_i_g___i_n_t for your network interface, along the lines of ifconfig_fxp0="inet 192.0.2.123 netmask 255.255.255.0" or, if you have _m_y_n_a_m_e_._m_y_._d_o_m in _/_e_t_c_/_h_o_s_t_s: ifconfig_fxp0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f 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 _/_e_t_c_/_r_c_._c_o_n_f. 3. Logging in After reboot, you can log in as root at the login prompt. If you didn't set a password in ssyyssiinnsstt, 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 _/_e_t_c_/_p_a_s_s_w_d 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 _N_e_t_B_S_D _G_u_i_d_e_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//gguuiiddee//eenn//cchhaapp--xx..hhttmmll: 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. ++oo More information on the package system is available at hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll ++oo A list of available packages suitable for browsing is at hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ccuurrrreenntt//ppkkggssrrcc//RREEAADDMMEE..hhttmmll ++oo Precompiled binaries can be found at hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD// usually in the _e_v_b_a_r_m_/_9_._0_/_A_l_l subdir. If you installed pkgin(1) in the ssyyssiinnsstt post-installation configuration menu, you can use it to automatically install binary packages over the network. Assuming that _/_u_s_r_/_p_k_g_/_e_t_c_/_p_k_g_i_n_/_r_e_p_o_s_i_t_o_r_i_e_s_._c_o_n_f is cor- rectly configured, you can install them with the following commands: ## ppkkggiinn iinnssttaallll ttccsshh ## ppkkggiinn iinnssttaallll bbaasshh ## ppkkggiinn iinnssttaallll ppeerrll ## ppkkggiinn iinnssttaallll aappaacchhee ## ppkkggiinn iinnssttaallll kkddee ## ppkkggiinn iinnssttaallll ffiirreeffooxx ... _N_o_t_e_: Some mirror sites don't mirror the _/_p_u_b_/_p_k_g_s_r_c directory. The above commands will install the Tenex-csh and Bourne Again shells, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on. ++oo If you did not install it from the ssyyssiinnsstt post- installation configuration menu, the pkgsrc(7) framework for compiling packages can be obtained by retrieving the file hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppkkggssrrcc..ttaarr..ggzz. It is typically extracted into _/_u_s_r_/_p_k_g_s_r_c (though other locations work fine) with the commands: # ccdd //uussrr # ttaarr --zzxxppff ppkkggssrrcc..ttaarr..ggzz After extracting, see the _d_o_c_/_p_k_g_s_r_c_._t_x_t file in the extraction directory (e.g., _/_u_s_r_/_p_k_g_s_r_c_/_d_o_c_/_p_k_g_s_r_c_._t_x_t) for more information. 7. Misc ++oo Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. ++oo Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you use. ++oo Many of the _/_e_t_c files are documented in section 5 of the manual; so just invoking # mmaann 55 _f_i_l_e_n_a_m_e is likely to give you more information on these files. UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm The easiest way to upgrade to NetBSD 9.0 is with binaries, and that is the method documented here. To do the upgrade, you must have one form of boot media available. You must also have at least the bbaassee and kkeerrnn 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 _b_a_c_k _u_p 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 9.0 system. However, that doesn't mean that you're finished with the upgrade process. You will probably want to update the set of device nodes you have in _/_d_e_v. If you've changed the contents of _/_d_e_v by hand, you will need to be careful about this, but if not, you can just cd into _/_d_e_v, and run the command: # sshh MMAAKKEEDDEEVV aallll ssyyssiinnsstt will attempt to merge the settings stored in your _/_e_t_c 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. CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 9.0. Note that ssyyssiinnsstt will automatically invoke postinstall fix and thus all issues that are fixed by ppoossttiinnssttaallll by default will be handled. A number of things have been removed from the NetBSD 9.0 release. See the ``Components removed from NetBSD'' section near the beginning of this document for a list. _I_m_p_o_r_t_a_n_t _n_o_t_e _r_e_g_a_r_d_i_n_g _A_B_I _c_h_a_n_g_e _o_n _A_R_M _p_o_r_t_s In NetBSD 7.0, most ARM ports (all but acorn32, and epoc32) have switched to the official standard ABI (EABI5) which is recommended by ARM for ELF binaries. Backwards compatibility is provided for binaries using the previous ABI (oabi). A NetBSD 9.0 kernel with the COMPAT_NETBSD32 option enabled will allow you to execute oabi binaries. This option is enabled in the kernels dis- tributed with this release. However, new binaries can not be mixed with old libraries, and shared libraries are incompatible. ssyyssiinnsstt does not provide an automatic mechanism to partlially upgrade an old installation. There are two ways to handle the transition: 1. Do a complete update. This means updating your system with ssyyssiinnsstt, then deleting and recompiling all other binaries, whether they were installed locally or through pkgsrc. This is the preferred, cleanest approach. 2. Move your old binaries and libraries to _/_c_o_m_p_a_t_/_n_e_t_b_s_d_3_2 and replace them one by one. For example, move all of _/_u_s_r_/_p_k_g to _/_c_o_m_p_a_t_/_n_e_t_b_s_d_3_2_/_u_s_r_/_p_k_g and add _/_c_o_m_p_a_t_/_n_e_t_b_s_d_3_2_/_u_s_r_/_p_k_g_/_b_i_n to the end of your PATH. Most binaries should still run, and can be replaced over time with recompiled packages, which will install to _/_u_s_r_/_p_k_g again. UUssiinngg oonnlliinnee NNeettBBSSDD ddooccuummeennttaattiioonn 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 ++oo intro(1), ++oo man(1), ++oo apropos(1), ++oo passwd(1), and ++oo 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 _m_a_n command is used to view the documentation on a topic, and is started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c. 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 # mmaann ppaasssswwdd to read the documentation for passwd(1). To view the docu- mentation for passwd(5), enter # mmaann 55 ppaasssswwdd instead. If you are unsure of what man page you are looking for, enter # aapprrooppooss _s_u_b_j_e_c_t_-_w_o_r_d where _s_u_b_j_e_c_t_-_w_o_r_d is your topic of interest; a list of pos- sibly related man pages will be displayed. AAddmmiinniissttrriivviiaa 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 _m_a_j_o_r_d_o_m_o_@_N_e_t_B_S_D_._o_r_g. See hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss// for details. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: _n_e_t_b_s_d_-_c_o_m_m_e_n_t_s_@_N_e_t_B_S_D_._o_r_g. 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 hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ssuuppppoorrtt//sseenndd--pprr..hhttmmll There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//mmaaiilliinngglliissttss// 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: _n_e_t_b_s_d_-_u_s_e_r_s_@_N_e_t_B_S_D_._o_r_g. 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. TThhaannkkss ggoo ttoo ++oo 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. ++oo The Internet Systems Consortium, Inc. for hosting the NetBSD FTP, CVS, AnonCVS, mail, mail archive, GNATS, SUP, Rsync and WWW servers. ++oo The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. ++oo The Columbia University Computer Science Department for hosting the build cluster. ++oo The many organizations that provide NetBSD mirror sites. ++oo 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. ++oo 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 hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddoonnaattiioonnss// (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.) ++oo 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!) LLeeggaall MMuummbboo--JJuummbboo 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 Luleoa. This product includes software developed at Ludd, University of Luleoa, 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 Projet. 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 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 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 Yasushi Yamasaki 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. TThhee EEnndd NetBSD/evbarm 9.0 Feb 14, 2020 NetBSD/evbarm 9.0