INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL -- Installation procedure for NetBSD/sparc64. CCOONNTTEENNTTSS About this Document Quick install notes for the impatient What is NetBSD? Changes Between The NetBSD 9 and 10 Releases, and newer Features to be removed in a later release The NetBSD Foundation Sources of NetBSD NetBSD 10.99.12 Release Contents NetBSD/sparc64 subdirectory structure Binary distribution sets NetBSD/sparc64 System Requirements and Supported Devices Supported machines Unsupported machines Supported devices Unsupported devices Getting the NetBSD System on to Useful Media Preparing your System for NetBSD installation Deciding on partition sizes Setting up Open Firmware Determining how to boot from an SBUS or PCI card Configuration of network interfaces Installing the NetBSD System Installing NetBSD from CD-ROM Installing NetBSD by using the NetBSD miniroot Installing NetBSD by using a NetBSD kernel on a Solaris partition 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 Ensure you have the correct kernel installed Finalizing your installation Manual Installation of NetBSD using Solaris Preparing the disk in Solaris Installing NetBSD Software from Solaris Creating NetBSD Device Nodes under Solaris Configuring the NetBSD system from Solaris Booting NetBSD for the first time 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 DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 10.99.12 on the _s_p_a_r_c_6_4 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. QQuuiicckk iinnssttaallll nnootteess ffoorr tthhee iimmppaattiieenntt This section contains some brief notes describing what you need to install NetBSD 10.99.12 on a machine of the sparc64 architecture. ++oo Fetch files needed to install NetBSD. This is either a CD image (_N_e_t_B_S_D_-_1_0_._9_9_._1_2_-_s_p_a_r_c_6_4_._i_s_o) which can be booted directly, or the installation kernel and boot- loader (_s_p_a_r_c_6_4_/_b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z and _s_p_a_r_c_6_4_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_o_f_w_b_o_o_t) which can be booted from a Solaris or NetBSD partition. Alternatively, you may netboot the installation kernel. This process is covered below, in detail. ++oo The actual binary distribution is in the _s_p_a_r_c_6_4_/_b_i_n_a_r_y_/_s_e_t_s_/ directory. When you boot the install CD-ROM or installation kernel, the installation program can fetch these files for you (using, e.g., ftp) if you have a network connection. There are several other methods to get the binary sets onto your machine. You will at a minimum need the following sets: _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z, _b_a_s_e_._t_g_z and _e_t_c_._t_g_z. In a typical workstation installation you will probably want all the installation sets. ++oo Burn the CD or put the installation kernel and boot- loader at the root level of a bootable Solaris or NetBSD partition. The media you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD. ++oo You will need to get to the OpenFirmware ``ookk'' prompt. After your system first powers on and displays some ini- tial information, press the STOP-A keys, or send a BREAK if you're on a serial console. At the ``ookk'' prompt, type the command to boot your system into NetBSD. The command to boot from CD is: ``bboooott ccddrroomm''. The command to boot the NetBSD kernel from a Solaris or NetBSD par- tition depends on which disk and partition it is on. To boot from the first partition of the first (primary) disk: ``bboooott ddiisskk::aa //ooffwwbboooott --aa''. When it asks you for a kernel, specify ``nneettbbssdd--IINNSSTTAALLLL..ggzz'' ++oo For third-party programs which are not part of the base NetBSD distribution, you will want to explore the ppkkggssrrcc package management system, which contains thousands of third-party software applications. WWhhaatt iiss NNeettBBSSDD?? 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.99.12 release contains complete binary releases for most of these system architectures, with preliminary support for the others included in source form. For more information please visit hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//. 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. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 99 aanndd 1100 RReelleeaasseess,, aanndd nneewweerr The NetBSD 10.99.12 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. Please note that this build is a development snapshot, not a formal release. You are testing the bleeding edge of NetBSD development, and no formal or informal testing may have been done for this snapshot (yet). One important new feature in this release is the support for extended attributes and access control lists on FFS file systems. For new installations the installer will by default disable these 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 _t_h_i_s _g_u_i_d_e_: hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ttuuttoorriiaallss//aaccllss__aanndd__eexxtteennddeedd__aattttrriibbuutteess__oonn__ffffss. If you are upgrading from a version of NetBSD -current please also check the _C_o_m_p_a_t_i_b_i_l_i_t_y _I_s_s_u_e_s _W_i_t_h _P_r_e_v_i_o_u_s _N_e_t_B_S_D _R_e_l_e_a_s_e_s. It is impossible to completely summarize the massive development that went into the NetBSD 10.99.12 release. The complete list of changes can be found in the following files: _C_H_A_N_G_E_S_: hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//HHEEAADD//llaatteesstt//CCHHAANNGGEESS _C_H_A_N_G_E_S_._p_r_e_v_: hhttttppss::////nnyyccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD--ddaaiillyy//HHEEAADD//llaatteesstt//CCHHAANNGGEESS..pprreevv 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. ++oo 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). 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 1100..9999..1122 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 10.99.12 release is orga- nized as follows: _._._._/_N_e_t_B_S_D_-_1_0_._9_9_._1_2_/ CHANGES Changes after the netbsd-10 branch. CHANGES.prev Changes in previous NetBSD releases. 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 10.99.12 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 10.99.12 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. ssyyssssrrcc This set contains the sources to the NetBSD 10.99.12 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. Individual sets may be unpacked into _/_u_s_r_/_s_r_c with the com- mand: # 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_/_s_p_a_r_c_6_4 _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The sparc64-specific portion of the NetBSD 10.99.12 release is found in the _s_p_a_r_c_6_4 subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_0_._9_9_._1_2_/_s_p_a_r_c_6_4_/. 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 system supported in this release. This kernel sup- ports SMP on systems with more than one CPU. _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._U_P_._g_z A gzipped NetBSD kernel containing code for every system supported in this release. This kernel dis- ables SMP support. _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z The install kernel. _s_e_t_s_/ sparc64 binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _m_i_n_i_r_o_o_t_/ sparc64 miniroot file system image; see below. _m_i_s_c_/ Miscellaneous sparc64 installation utilities; see installation section below. _n_e_t_b_o_o_t_/ Netboot bootloader; see 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 sparc64 binary distribution sets contain the binaries which comprise the NetBSD 10.99.12 release for sparc64. The binary distribution sets can be found in the _s_p_a_r_c_6_4_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 10.99.12 dis- tribution tree. _N_o_t_e_: If you want to install 32-bit only binaries, you will still need to boot using the sparc64 installation tools. When sysinst asks you for the distribution set to install, provide the NetBSD/sparc _b_i_n_a_r_y_/_s_e_t_s. Be sure to use the 32 bit sparc _k_e_r_n_-_G_E_N_E_R_I_C___S_U_N_4_U_._t_g_z kernel distribution. Other- wise, continue to follow the sparc64 installation procedure, not the sparc instructions. Most people will want the 64-bit sparc64 distribution tree: bbaassee The NetBSD 10.99.12 sparc64 bbaassee binary distribu- tion. You _m_u_s_t install this distribution set. It contains the base NetBSD utilities that are neces- sary for the system to run and be minimally func- tional. 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 develop- 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--GGEENNEERRIICC This set contains a NetBSD/sparc64 10.99.12 GENERIC kernel named _/_n_e_t_b_s_d. You _m_u_s_t install this or the kern-GENERIC.UP distribution set. kkeerrnn--GGEENNEERRIICC..UUPP This set contains a NetBSD/sparc64 10.99.12 GENERIC.UP kernel named _/_n_e_t_b_s_d, with SMP support disabled. 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 recovery 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 development. 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. This includes the modular Xorg and Xvfb servers. The sparc64 binary distribution sets are distributed as tar files compressed with ggzziipp 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 sparc64 binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//ssppaarrcc6644 SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess _S_u_p_p_o_r_t_e_d _m_a_c_h_i_n_e_s The minimal configuration requires 32 MB of RAM and ~180 MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. Note that until you have at least 64 MB of RAM, getting more RAM is more important than getting a faster CPU. Not all of the machines listed here have been tested. Often Sun used the same motherboard design in multiple models. For example, there might be a Blade ("workstation") model, Enterprise or Fire ("server") model, and Netra or ft ("telco") model with essentially the same devices, as far as NetBSD is concerned. If one model in this scheme works, it is highly likely another will work. Sun has also released a few models with names that might imply the systems are UltraSPARC-based but actually have an i386/amd64 class CPU. These systems might be supported by the i386 or amd64 ports of NetBSD. ++oo Sbus-based UltraSPARC I or II systems -- Ultra 1 family (Ultra 1, Ultra 1 Creator, Ultra 1 Creator 3D, Netra i 150, Netra nfs 150, Enterprise 1, Enterprise 150) -- Ultra 2 family (Ultra 2, Ultra 2 Creator, Ultra 2 Creator 3D, Enterprise 2) -- Enterprise (3000, 3500, 4000, 4500, 500x, 5500, 600x, 6500, 10000) ++oo PCI-based UltraSPARC II, IIi, IIe, III, or IIIi systems -- Ultra 5/10 family (Ultra 5, Ultra 10, Enter- prise 5, Enterprise 10) -- Ultra 30 family (Ultra 30, Netra T 1100) -- Ultra 60 family (Ultra 60, E220R, Netra T 1120 and T 1125) -- Ultra 80 family (Ultra 80, E420R, Netra T 1400 and T 1405) -- Ultra 250 family (Enterprise 250 and E250R) -- Ultra 450 family (Ultra 450, Enterprise 450, Netra ft 1800) -- SunBlade 100 and 150 -- SPARCengine CP1400 or SPARCengine CP1500 sys- tem boards (Netra T1 (models 100 and 105), CT400, CT800, CT1600) -- SPARCengine Ultra AXi family (Netra X1, Fire v100, Fire v120, Netra 120, Netra AC 200, Netra DC 200) -- SPARCengine Ultra AXe system board -- SunBlade 1000 and 2000 -- SunBlade 1500, 2500 (Red and Silver) -- Ultra 25 and 45 -- Sun Fire v125, v210, v215, v240, v245, v250, v440, v445, v480 _U_n_s_u_p_p_o_r_t_e_d _m_a_c_h_i_n_e_s ++oo Systems with an UltraSPARC IV CPU ++oo Systems with an UltraSPARC T1-T5 CPU ++oo Systems with a Fujitsu SPARC64 CPU _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s ++oo Ethernet devices -- Sbus LANCE ethernet (_l_e) -- Sbus BigMac ethernet (_b_e) -- On-board, PCI, and Sbus HME ethernet (_h_m_e) -- PCI ERI (_g_e_m) -- Many other PCI and PCMCIA Ethernet interfaces, including: ++oo Tulip-compatible (_t_l_p) ++oo Intel (_f_x_p) ++oo Intel gigabit (_w_m) ++oo NE2000-compatible (_n_e) ++oo Realtek (_r_t_k or _r_e) ++oo SysKonnect XMAC II (_s_k) ++oo Marvell GMAC (_m_s_k) -- Several USB Ethernet interfaces, such as (_a_u_e, _c_u_e, and _k_u_e) ++oo Wireless network adapters -- Atheros wireless cards (_a_t_h) ++oo Video devices -- All on-board frame buffers Unless otherwise specified, only text console is supported -- On-board and SBUS card (GX, GX+, TGX, TGX+) (_c_g_s_i_x) 8 bpp accelerated framebuffer. Accelerated X via the integrated Xorg. -- UPA devices (ffb and afb, also called Creator3D) 24 bpp accelerated framebuffer. Accelerated X via the integrated Xorg. -- On-board ATI mach64 framebuffers (found in Ultra 5/10). ++oo SCSI host controllers -- ncr53c9x based controllers (_e_s_p) -- ncr53c8xx based controllers (_s_i_o_p or _e_s_i_o_p) -- ISP10x0 based controllers (_i_s_p) -- 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. _N_o_t_e_: Some Adaptec cards that support booting on MacOS may be bootable on sparc64 systems. -- Many other PCI SCSI controllers should work, but no one has tried them -- Most SCSI disk/tape/CD-ROM devices should work ++oo PCI IDE host controllers -- Generic IDE controllers (_p_c_i_i_d_e) -- Acard ATP-850/860 based IDE controllers (_p_c_i_i_d_e) (including the Acard AEC-6210/6260 and the Sonnet Tempo ATA/66 cards) -- CMD Tech PCI064[3689] and Silicon Image 0680 IDE Controllers (_c_m_d_i_d_e) -- Silicon Image 3112, 3114, and 3512 SATA Con- troller (_s_a_t_a_l_i_n_k) _N_o_t_e_: Some IDE cards that support booting on MacOS may be bootable on sparc64 sys- tems. -- Many other PCI IDE controllers should work, but no one has tried them -- Most IDE and ATAPI disk/tape/CD-ROM devices should work ++oo Floppy drives -- On-board Floppy Disk Controller -- SBus machines only for now (_f_d_c) ++oo Serial devices -- On-board Sbus z8530 serial (_z_s) -- On-board PCI 16550-based su and su-pnp serial (_c_o_m) -- On-board PCI SAB82532 dual UART serial (_s_a_b) ++oo Parallel devices -- On-board and Sbus parallel ports (_b_p_p) -- On-board PCI/Ebus parallel ports (_l_p_t) ++oo Audio devices -- On-board, PCI, and SBus based CS4231-based 44 KHz, 16 bit, stereo, PCM audio (_a_u_d_i_o_c_s) ++oo Other PCI devices -- PCI ``universal'' communications cards (_p_u_c) There are a large number of untested PCI drivers that have never been tested on UltraSPARC PCI systems that may `just work'. _U_n_s_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s Smart card readers. 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. _N_o_t_e_: If you are installing the 32-bit sparc distribution sets, you will need to rename _s_p_a_r_c_/_b_i_n_a_r_y_/_s_e_t_s_/_k_e_r_n_-_G_E_N_E_R_I_C___S_U_N_4_U_._t_g_z to _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z since the sparc64 installation tools would otherwise attempt to install the kernel for 32-bit sparc computers which does not boot on sparc64 systems. _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 _s_p_a_r_c_6_4_/_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--1100..9999..1122 # ccdd ssppaarrcc6644//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 _D_e_c_i_d_i_n_g _o_n _p_a_r_t_i_t_i_o_n _s_i_z_e_s If you're installing NetBSD/sparc64 for the first time it's a good idea to look at the partition sizes of the disk you plan to install NetBSD on. Will you be installing NetBSD onto the same disk as Solaris, on its own disk, or will you be netbooting? While NetBSD can work just fine on a disk shared with Solaris, the NetBSD installer does not currently support this. The limitation is that the NetBSD disklabel(8) writes partition info that Solaris is not familiar with. Therefore, if you are sharing a disk with Solaris, any time you change a partition table, you must do it from Solaris. Assuming a classic partition scheme with _/ (root) and _/_u_s_r file systems, a comfortable size for the NetBSD _/ partition is about 200 MB. A full binary installation including X takes over 600 MB in _/_u_s_r. Since the pkgsrc binaries are typically installed in _/_u_s_r_/_p_k_g you may want a significantly larger _/_u_s_r partition. A good initial size for the swap partition is the amount of physical memory in your machine if you've got more than 128 MB RAM. If you've got less RAM, you may want swap to be at least 128 MB. Note that the OBP on Ultra 1 and Ultra 2 machines can only boot from the first 4Gb of the disk, so this limits the size of the root partition on these models. _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e First, you need to stop your system from automatically boot- ing when powered on. Pressing the STOP key (sometimes called the L1 key, found on the left side of your keyboard) and the a key will halt your system and give you the ``ok'' prompt. If you are using a serial console, send a ``BREAK'' signal from your terminal (the method of sending ``BREAK'' varies from terminal to terminal). If the ethernet address of your sparc64 system is ff:ff:ff:ff:ff:ff (check with the Open Firmware ``banner'' command), then your NVRAM battery is dead and you will have trouble using ethernet (among other problems). Read the _S_u_n _N_V_R_A_M_/_H_o_s_t_i_d _F_A_Q_: hhttttppss::////wweebb..aarrcchhiivvee..oorrgg//wweebb//2200115500661111009911661166//hhttttppss::////wwwwww..ssqquuiirrrreell..ccoomm//ssqquuiirrrreell//ssuunn--nnvvrraamm--hhoossttiidd..ffaaqq..hhttmmll. If you have a valid ethernet address and you plan to net- boot, write down your system's ethernet address. You cannot use the security modes of the SPARC OpenFirmware. ok sseetteennvv sseeccuurriittyy--mmooddee nnoonnee If you are using a serial console, the NetBSD/sparc64 installer defaults to using 9600 bps, 8N1 settings. You may want to configure your system and serial terminal like this prior to booting the installer. A new installation of NetBSD/sparc64 will default to these settings as well. SCSI devices are specified by an Open Firmware ddeevvaalliiaass which provides simple mnemonics for the full path to the device. Type ddeevvaalliiaass to get a list of all of the available aliases. At a minimum, the alias and partition are neces- sary when booting. Therefore, to boot from the swap partition on the internal hard drive one would use: ok bboooott ddiisskk::bb To boot from a CD-ROM (Open Firmware assumes SCSI CD-ROMs are at target 6), one would use: ok bboooott ccddrroomm And to boot from a kernel named netbsd-GENERIC on the fourth partition ( `d', often the _/_u_s_r partition) on an external SCSI hard drive (target 2, partition 3), one would use: ok bboooott ddiisskk22::dd nneettbbssdd--GGEENNEERRIICC If you get ``.... Fast Data MMU Miss'' when booting after the NetBSD installation, your OpenBoot PROM may need updat- ing. It has been reported that version 3.31 lead to a suc- cessful boot on an Ultra Enterprise 420R, while version 3.23 did not. Exact values may vary, depending on your hardware, current OpenBoot PROM version and moon phase. _D_e_t_e_r_m_i_n_i_n_g _h_o_w _t_o _b_o_o_t _f_r_o_m _a_n _S_B_U_S _o_r _P_C_I _c_a_r_d Some SBUS and PCI cards have firmware that lets you use them as boot devices. These cards do not automatically create ddeevvaalliiaass entries, so you must traverse the device tree to figure out what Open Firmware calls your card. You will be using Open Firmware commands at the `ok' prompt. First `cd' to the top of the device tree and list the nodes there. The following is the procedure to boot from an IDE card in an UltraSPARC 30. ok ccdd // ok llss f006cf08 SUNW,ffb@1e,0 f006c32c SUNW,UltraSPARC-II@0,0 f006002c counter-timer@1f,1c00 f005f410 pci@1f,2000 f005eb54 pci@1f,4000 f004cf84 virtual-memory f004c9a4 memory@0,0 f002ce38 aliases f002cdc8 options f002cc90 openprom f002cc24 chosen f002cbb4 packages Usually, you can simply type in the name before the at (@) sign and OpenFirmware will fill in the rest. ok ccdd ppccii@@11ff,,44000000 ok llss f0081524 ide@2 f007be50 scsi@3 f0074688 network@1,1 f0060324 ebus@1 ok ccdd iiddee@@22 ok llss 0081fe4 cdrom f0081938 disk ok ccdd ddiisskk ok llss ok ppwwdd /pci@1f,4000/ide@2/disk OK, now we know the path to the IDE device in this example. Now, we need to determine if it's capable of booting. If it is, it will have the wwoorrdd `open'. ok wwoorrddss close load write read seek open write-blocks read-blocks max-transfer block-size dma-free dma-alloc spin-down spin-up Great! Also, in case you're interested in further details about your hardware, you can use the ..pprrooppeerrttiieess command. So, when it's time to type in a boot command, use the short- ened version of the ppwwdd command. You need to be more spe- cific if there are two devices with the same name (in this case, two /pci entries). In this example, you'd type: ok bboooott //ppccii@@11ff,,44000000//iiddee//ddiisskk@@00,,00 You can also store this device path across reboots using the nnvvaalliiaass command. ok nnvvaalliiaass wwdd00 //ppccii@@11ff,,44000000//iiddee//ddiisskk@@00,,00::aa And when the kernel is done booting, it may not automati- cally use your card as the root device -- you may need to type in the NetBSD/sparc64 name for that device: root on sd0a dumps on sd0b no file system for sd0 (dev 0x700) cannot mount root, error = 79 root device (default sd0a): ? use one of: hme0 sd0[a-h] wd0[a-h] halt root device (default sd0a): wwdd00aa dump device: wwdd00aa file system (default generic): ffffss root on wd0a The root device can also be specified in your kernel config file. _C_o_n_f_i_g_u_r_a_t_i_o_n _o_f _n_e_t_w_o_r_k _i_n_t_e_r_f_a_c_e_s Some network devices (i.e., certain SBus cards) allow a choice between operating on a UTP or a AUI port. The le driver supports automatic detection of the port which is actually connected to the wire. If automatic detection is not available or not working properly in your environment, you may have to specify the type connection using the _m_e_d_i_a parameter of ifconfig(8). During installation, you'll get the opportunity to specify the appropriate medium. Use 10base5/AUI to select the AUI connector, or 10baseT/UTP to select the UTP connector. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm Installing NetBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. There are several ways to install NetBSD onto a disk. The easiest way in terms of preliminary setup is to install from CD-ROM. If you don't have access to a CD-ROM or CD-ROM burner, you can use a miniroot image that can be booted off your local disk's swap partition. Alternatively, if your UltraSPARC is hooked up in a network you can find a server and arrange for a diskless setup which is a convenient way to install on a machine whose disk does not currently hold a usable operating system (see the section _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _d_i_s_k_l_e_s_s _s_e_t_u_p below). If you have problems with these or you are installing NetBSD onto the same disk as Solaris, see the section below on _M_a_n_u_a_l _I_n_s_t_a_l_l_a_t_i_o_n _o_f _N_e_t_B_S_D _u_s_i_n_g _S_o_l_a_r_i_s _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _f_r_o_m _C_D_-_R_O_M Installing from CD-ROM is the least painful way to install NetBSD. Simply insert the CD-ROM in the drive, power up the computer, and type: ok bboooott ccddrroomm This Open Firmware boot command will cause the NetBSD kernel contained in the CD-ROM to be booted. After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _t_h_e _N_e_t_B_S_D _m_i_n_i_r_o_o_t The miniroot is a self-contained NetBSD file system holding all utilities necessary to install NetBSD on a local disk. It is distributed as a plain file designed to be transferred to a raw disk partition from which it can be booted using the appropriate OpenFirmware command. Usually, the miniroot will be loaded into the swap partition of a disk. If needed, you can use any other unused partition, but remember that the partition will then not available during the installation process. Loading the miniroot onto your raw partition is simple using the dd(1) command. Just remember to first uncompress the miniroot image and boot your OS with the -s flag so that it runs ``single-user'' and does not attempt to start swapping. ok bboooott --ss On Solaris you use a command like: # gguunnzziipp mmiinniirroooott..ffss..ggzz # dddd iiff==mmiinniirroooott..ffss ooff==//ddeevv//rrddsskk//cc00tt00dd00ss11 bbss==44kk On NetBSD the command is: # gguunnzziipp mmiinniirroooott..ffss..ggzz # dddd iiff==mmiinniirroooott..ffss ooff==//ddeevv//rrssdd00bb bbss==44kk Replace /dev/rdsk/c0t0d0s1 or /dev/rsd0b with your swap par- tition. After transferring the miniroot to disk, bring the system down by: # hhaalltt Then boot the miniroot by typing the appropriate command at the OpenFirmware prompt: ok bboooott ddiisskk::bb nneettbbssdd If you've loaded the miniroot onto some other disk than sd0 use the correct _d_e_v_a_l_i_a_s, such as ok bboooott ddiisskk11::bb nneettbbssdd This Open Firmware boot command will cause the NetBSD kernel contained in the miniroot image to be booted. After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _N_e_t_B_S_D _k_e_r_n_e_l _o_n _a _S_o_l_a_r_i_s _p_a_r_t_i_t_i_o_n This procedure is very straightforward. You will be putting the NetBSD installation kernel (kernel with a RAM disk installer) on your Solaris partition and telling Open Firmware to boot the NetBSD kernel. CAVEAT: this method is a bit fragile. Depending on physical partition layout, partition size, and parameters used to create the filesystem of your Solaris root partition, bugs in the bootloader might be triggered and cause this method to fail. First, copy the _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z kernel and bootloader to the root level of your hard drive and halt your system # ccpp bbiinnaarryy//kkeerrnneell//nneettbbssdd--IINNSSTTAALLLL..ggzz // # ccpp iinnssttaallllaattiioonn//mmiisscc//ooffwwbboooott // # hhaalltt At the Open Firmware prompt, boot NetBSD. ok bboooott ddiisskk::aa //ooffwwbboooott --aa The -a flag is needed so that the bootloader will ask you to find your installation kernel. Rebooting with command: boot disk:a /ofwboot -a Boot device: /pci@1f,4000/scsi@3/disk@0,0:a File and args: /ofwboot -a Enter filename [/ofwboot]: <> >> NetBSD/sparc64 OpenFirmware Boot, Revision 1.7 >> (autobuild@tgm.netbsd.org, Thu May 20 16:29:20 UTC 2004) Boot: nneettbbssdd--IINNSSTTAALLLL..ggzz After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _n_e_t_b_o_o_t _s_e_t_u_p 1. Introduction To netboot a sparc64, you must configure one or more servers to provide information and files to your sparc64 (the `client'). If you are using NetBSD (any architecture) on your netboot server(s), the informa- tion provided here should be sufficient to configure everything. Additionally, you may wish to look at the diskless(8) manual page and the manual pages for each daemon you'll be configuring. If the server(s) are another operating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps necessary to configure the netboot services on a vari- ety of platforms: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott// You may either netboot the installer so you can install onto a locally attached disk, or you may run your sys- tem entirely over the network. 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 bootstrap program goes through another discovery phase to determine where the kernel is located. The bootstrap program tries to mount the NFS share containing the kernel. Once the kernel is loaded, it starts executing. For RAM disk kernels, it mounts the RAM disk file system and begins executing the installer from the RAM disk. For normal (non-RAM disk) kernels, the kernel tries to mount the NFS share that had the kernel and starts executing the installation tools or init(8). All sparc64 systems use a combination of RARP and DHCP for the discovery stage. TFTP is used in the bootstrap phase to download the bootstrap program, _o_f_w_b_o_o_t_._n_e_t, which has been linked to a file name appropriate to the client's IP address as described in the TFTP section below. NFS is used in both the kernel and file system stages to download the kernel, and to access files on the file server. We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hardware address) of your netboot client machine. You should have determined this address in an earlier stage. In this example, we will use `192.168.1.10' as the IP address of your client and `client.test.net' as its name. We will assume you're providing all of your netboot services on one machine called `server.test.net' with the client's files exported from the directory _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environment. You should set up each netboot stage in order (i.e., discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed. 2. dhcpd(8) in bootpd(8) compatible mode Put the following lines in your _/_e_t_c_/_d_h_c_p_d_._c_o_n_f (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. # # 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 _d_h_c_p_d_._l_e_a_s_e_s file exists. # ttoouucchh //vvaarr//ddbb//ddhhccppdd..lleeaasseess You will need to start the ddhhccppdd. 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: # //eettcc//rrcc..dd//ddhhccppdd rreessttaarrtt 3. rarpd(8) Create an _/_e_t_c_/_e_t_h_e_r_s file with the following line: CC:CC:CC:CC:CC:CC client Add your client to the server's _/_e_t_c_/_h_o_s_t_s file: 192.168.1.10 client You will need to start the rraarrppdd. 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: # //eettcc//rrcc..dd//rraarrppdd rreessttaarrtt 4. tftpd(8) The default configuration of the TFTP server is to run in a chroot(8) environment in the _/_t_f_t_p_b_o_o_t directory. Thus, the first order of business is to create this directory: # mmkkddiirr --pp //ttffttppbboooott Next, edit _/_e_t_c_/_i_n_e_t_d_._c_o_n_f 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: # //eettcc//rrcc..dd//iinneettdd rreessttaarrtt Now, you need to copy the bootloader for your sparc64 machine to _/_t_f_t_p_b_o_o_t. Get _o_f_w_b_o_o_t_._n_e_t from the _i_n_s_t_a_l_l_a_t_i_o_n_/_n_e_t_b_o_o_t directory of the distribution. # ccpp ooffwwbboooott..nneett //ttffttppbboooott Now, you need to link _o_f_w_b_o_o_t_._n_e_t to the filename that your sparc64 will look for. It will look for a file- name composed of the machine's IP address (in hexadeci- mal). For example, a machine which has been assigned IP address 192.168.1.10, will make a TFTP request for _C_0_A_8_0_1_0_A. You can use bc(1) to help calculate the filename: # bbcc oobbaassee==1166 119922 C0 116688 A8 11 1 1100 A qquuiitt # ccdd //ttffttppbboooott # llnn --ss ooffwwbboooott..nneett CC00AA88001100AA Just to be sure, let's make everything readable. # cchhmmoodd --RR aa++rrXX //ttffttppbboooott 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 _/_v_a_r_/_l_o_g_/_m_e_s_s_a_g_e_s 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: # aarrpp --ss cclliieenntt CCCC::CCCC::CCCC::CCCC::CCCC::CCCC 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: # mmkkddiirr --pp //eexxppoorrtt//cclliieenntt//rroooott Put the following line in _/_e_t_c_/_e_x_p_o_r_t_s 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: # //eettcc//rrcc..dd//rrppccbbiinndd ssttaarrtt # //eettcc//rrcc..dd//nnffssdd ssttaarrtt # //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt 6. NetBSD kernel and installation tools Now, if you place a kernel named _n_e_t_b_s_d in _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t your client should boot the kernel. Use _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. # gguunnzziipp nneettbbssdd--GGEENNEERRIICC..ggzz # mmvv nneettbbssdd--GGEENNEERRIICC //eexxppoorrtt//cclliieenntt//rroooott//nneettbbssdd If you are netbooting the installer, copy the distribu- tion files to the client's root directory and extract the tools from _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c_/_i_n_s_t_f_s_._t_g_z. # ccpp **..ttggzz //eexxppoorrtt//cclliieenntt//rroooott # ccdd //eexxppoorrtt//cclliieenntt//rroooott # ttaarr --xxppzzff iinnssttffss..ttggzz 7. Client file system You can skip this step if you do not plan to run your client diskless after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. See _f_o_r _d_e_t_a_i_l_s_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//nneettwwoorrkk//nneettbboooott//nnffss..hhttmmll. ++oo Extracting distribution sets # ccdd //eexxppoorrtt//cclliieenntt//rroooott # ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//bbaassee..ttggzz # ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//eettcc..ttggzz Continue with the other non-essential distribution sets if desired. ++oo Set up swap # mmkkddiirr //eexxppoorrtt//cclliieenntt//rroooott//sswwaapp # dddd iiff==//ddeevv//zzeerroo ooff==//eexxppoorrtt//cclliieenntt//sswwaapp bbss==44kk ccoouunntt==44kk # eecchhoo ''//eexxppoorrtt//cclliieenntt//sswwaapp --mmaapprroooott==rroooott::wwhheeeell cclliieenntt..tteesstt..nneett'' >>>> //eettcc//eexxppoorrttss # //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt This creates a 16 MB swap file and exports it to the client. ++oo Create device nodes # ccdd //eexxppoorrtt//cclliieenntt//rroooott//ddeevv # ..//MMAAKKEEDDEEVV aallll This procedure only works on NetBSD hosts. ++oo Set up the client's fstab(5) Create a file in _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_f_s_t_a_b with the following lines: server:/export/client/swap none swap sw,nfsmntpt=/swap server:/export/client/root / nfs rw 0 0 ++oo Set up the client's rc.conf(5) Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_r_c_._c_o_n_f 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. ++oo Set up the client's hosts(5) file. Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_h_o_s_t_s ::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 If you want these services to start up every time you boot your server, make sure the following lines are present in your _/_e_t_c_/_r_c_._c_o_n_f: dhcpd=YES dhcpd_flags="-q" rarpd=YES rarpd_flags="-a" nfs_server=YES # enable server daemons mountd=YES rpcbind=YES rpcbind_flags="-l" # -l logs libwrap Also, you'll need to make sure the _t_f_t_p_d line in _/_e_t_c_/_i_n_e_t_d_._c_o_n_f remains uncommented. Now, netboot your system from the server by entering the appropriate bboooott command at the Open Firmware prompt. ok bboooott nneett nneettbbssdd After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m below. _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m 1. _I_n_t_r_o_d_u_c_t_i_o_n Using ssyyssiinnsstt, 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. _G_e_n_e_r_a_l The following is a walk-through of the steps you will take while installing NetBSD on your hard disk. ssyyssiinnsstt 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 _/_s_y_s_i_n_s_t program from the command prompt. It is not necessary to reboot. 3. _Q_u_i_c_k _i_n_s_t_a_l_l 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. ++oo What you need. -- The distribution sets (in this example, they are on the CD or DVD). -- A minimum of 32 MB of memory installed. -- An optical drive. -- A hard drive with at least 700 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. ++oo The Quick Installation -- Boot the system as described above. You should be at the ssyyssiinnsstt main menu. .***********************************************. * NetBSD-10.99.12 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 UUttiilliittyy mmeennuu and then CCoonnffiigguurree nneettwwoorrkk. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. -- Choose IInnssttaallll. -- You will be guided through the setup of your disk. -- You will be asked to choose which distribution sets to install. WARNING: If you are installing onto a disk which you want to use with Solaris, stop here. You will need to perform a manual installation as ssyyssiinnsstt overwrites the Solaris partition ta- ble. See the section on _M_a_n_u_a_l _I_n_s_t_a_l_l_a_t_i_o_n _o_f _N_e_t_B_S_D _u_s_i_n_g _S_o_l_a_r_i_s -- When prompted, choose CCDD--RROOMM 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 RReebboooott.. -- Once the system reaches the Open Firmware prompt, you will need to type the correct com- mand to boot from your hard drive. -- NetBSD will now boot. If you didn't set a password for the root user when prompted by ssyyssiinnsstt, logging in as root and setting a pass- word should be your first task. You are also advised to read afterboot(8). 4. _B_o_o_t_i_n_g _N_e_t_B_S_D You may want to read the boot messages, to notice your disk's name and capacity. Its name will be something like sd0 or wd0 and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell ssyyssiinnsstt which disk to use. The most important thing to know is that wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc. Once NetBSD has booted and printed all the boot mes- sages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n 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 UUttiilliittyy mmeennuu and select the CCoonnffiigguurree nneettwwoorrkk 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. _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s To start the installation, select IInnssttaallll NNeettBBSSDD ttoo hhaarrdd ddiisskk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. ssyyssiinnsstt will report a list of disks it finds and ask you for your selection. You should see disk names like wd0, wd1, sd0 or sd1. 7. _S_e_l_e_c_t_i_n_g _w_h_i_c_h _s_e_t_s _t_o _i_n_s_t_a_l_l 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, bbaassee, eettcc, and a kernel must be selected. 8. _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k ++oo 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, ssyyssiinnsstt will check for the presence of other operating systems and you will be asked to confirm that you want to overwrite these. 9. _E_d_i_t_i_n_g _t_h_e _N_e_t_B_S_D _d_i_s_k_l_a_b_e_l The partition table of the NetBSD part of a disk is called a _d_i_s_k_l_a_b_e_l. If your disk already has a diskla- bel written to it, you can choose UUssee eexxiissttiinngg ppaarrttiittiioonn ssiizzeess. Otherwise, select SSeett ssiizzeess ooff NNeettBBSSDD ppaarrttiittiioonnss. 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 44..22BBSSDD. A swap partition has a special type called sswwaapp. Some partitions in the disklabel have a fixed purpose. a Root partition (_/) b Swap partition. c The entire disk. d-h Available for other use. Traditionally, g is the partition mounted on _/_u_s_r, 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. _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k _Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n. 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 yyeess. 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. _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD distribution consists of a number of _s_e_t_s 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. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _C_D_-_R_O_M 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. ssyyssiinnsstt will then check that the files are actually present in the specified location and proceed to the extraction of the sets. 13. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _F_T_P To install using FTP, you first need to configure your network setup if you haven't already done so. ssyyssiinnsstt 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. ssyyssiinnsstt will then transfer the set files from the remote site to your hard disk. 14. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S To install using NFS, you first need to configure your network setup if you haven't already done so. ssyyssiinnsstt 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. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e _s_y_s_t_e_m 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. ssyyssiinnsstt will then check if it can indeed access the sets at that location. 16. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y 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. ssyyssiinnsstt will ask you for the name of this directory. 17. _E_x_t_r_a_c_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s 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. _C_o_n_f_i_g_u_r_e _a_d_d_i_t_i_o_n_a_l _i_t_e_m_s 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 aapptt--ggeett or yyuumm. 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. _E_n_s_u_r_e _y_o_u _h_a_v_e _t_h_e _c_o_r_r_e_c_t _k_e_r_n_e_l _i_n_s_t_a_l_l_e_d If you are installing from the 32-bit sparc distribu- tion set, make sure that you installed the correct ker- nel. The sparc64 installation tools do not by default copy the correct 32-bit kernel. Unless you prepared ahead of time by renaming the _k_e_r_n_-_G_E_N_E_R_I_C___S_U_N_4_U_._t_g_z to _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z then you will need to follow the next few instructions. Go to the main installation menu, and select UUttiilliittyy mmeennuu and then select the RRuunn //bbiinn//sshh option, which will give you a shell prompt. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # ssttttyy eerraassee ''^^hh'' # ssttttyy eerraassee ''^^??'' Type the following command (replacing _w_d_0_a with the partition name of your destination root partition): # mmoouunntt //ddeevv//wwdd00aa //mmnntt # ccdd //mmnntt Now you need to mount the location of your distribution sets: # mmoouunntt //ddeevv//ccdd00aa //mmnntt22 # ttaarr xxppzzvvff //mmnntt22//ssppaarrcc//bbiinnaarryy//kkeerrnneell//kkeerrnn-- GGEENNEERRIICC__SSUUNN44UU..ttggzz # uummoouunntt //mmnntt # uummoouunntt //mmnntt22 # eexxiitt 20. _F_i_n_a_l_i_z_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n Congratulations, you have successfully installed NetBSD 10.99.12. You can now reboot the machine and boot NetBSD from hard disk. Skip down to the section on _B_o_o_t_i_n_g _N_e_t_B_S_D _f_o_r _t_h_e _f_i_r_s_t _t_i_m_e _M_a_n_u_a_l _I_n_s_t_a_l_l_a_t_i_o_n _o_f _N_e_t_B_S_D _u_s_i_n_g _S_o_l_a_r_i_s (Adapted from Murray Stokely's instructions) You can use Solaris to prepare the NetBSD user-friendly installer or to perform a full manual installation of NetBSD. If you want to use the user-friendly miniroot installer or RAM disk installation kernel, follow the sec- tions _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _t_h_e _N_e_t_B_S_D _m_i_n_i_r_o_o_t or _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _N_e_t_B_S_D _k_e_r_n_e_l _o_n _a _S_o_l_a_r_i_s _p_a_r_t_i_t_i_o_n. Manual installation from Solaris 10 is not possible because NetBSD cannot use the resulting UFS file system. It is pos- sible to install Solaris 10 and NetBSD on the same disk. To do so, partition the disk with the Solaris format command, then boot NetBSD and perform a manual installation. Be careful not to write a NetBSD disklabel. Use the disklabel command to read the partition size, as constructed from the Solaris disklabel. By default the NetBSD newfs command writes a NetBSD disklabel. Avoid this by using the -F and -s arguments to newfs. ++oo _P_r_e_p_a_r_i_n_g _t_h_e _d_i_s_k _i_n _S_o_l_a_r_i_s The first step is to format and label the disk that you would like to use with NetBSD. This can be accomplished with the format(1M) command in Solaris, which allows you to partition a disk and write a disklabel. It also is used to perform a low-level format on SCSI drives. You will want to create a root partition and a swap parti- tion. Depending on your preferences, you may also wish to create separate _/_u_s_r or _/_v_a_r partitions. # //uussrr//ssbbiinn//ffoorrmmaatt Searching for disks... Mode sense page(3) reports nsect value as 280, adjusting it to 218 done c0t1d0: configured with capacity of 16.95GB AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@1f,4000/scsi@3/sd@0,0 1. c0t1d0 /pci@1f,4000/scsi@3/sd@1,0 Specify disk (enter its number): 11 selecting c0t1d0 [disk formatted] Disk not labeled. Label it now? yy format> ffoorrmmaatt Ready to format. Formatting cannot be interrupted and takes 114 minutes (estimated). Continue? y Beginning format. The current time is Sat May 29 22:15:13 2004 Formatting... done Verifying media... pass 0 - pattern = 0xc6dec6de 8151/19/208 pass 1 - pattern = 0x6db6db6d 8151/19/208 Total of 0 defective blocks repaired. format> ppaarrttiittiioonn partition> pprriinntt Current partition table (original): Total disk cylinders available: 8152 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 60 129.86MB (61/0/0) 265960 1 swap wu 61 - 121 129.86MB (61/0/0) 265960 2 backup wu 0 - 8151 16.95GB (8152/0/0) 35542720 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 122 - 8151 16.69GB (8030/0/0) 35010800 7 unassigned wm 0 0 (0/0/0) 0 partition> llaabbeell Ready to label disk, continue? yy partition> qquuiitt format> qquuiitt After your disk has been labeled you need to create file systems on your slices. The Solaris newfs(1M) command will create ffs file systems that can be used by NetBSD. # //uussrr//ssbbiinn//nneewwffss //ddeevv//ddsskk//cc00tt11dd00ss00 # //uussrr//ssbbiinn//nneewwffss //ddeevv//ddsskk//cc00tt11dd00ss66 ++oo _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _S_o_f_t_w_a_r_e _f_r_o_m _S_o_l_a_r_i_s You should now mount your NetBSD root and _/_u_s_r parti- tions under Solaris so that you can populate the file systems with NetBSD binaries. # //uussrr//ssbbiinn//mmoouunntt //ddeevv//ddsskk//cc00tt11dd00ss00 //mmnntt # mmkkddiirr //mmnntt//uussrr # //uussrr//ssbbiinn//mmoouunntt //ddeevv//ddsskk//cc00tt11dd00ss66 //mmnntt//uussrr Now extract the distribution file sets # ccdd ~~//nneettbbssdd//bbiinnaarryy//sseettss # gguunnzziipp **..ttaarr..ggzz # eecchhoo ~~//nneettbbssdd//bbiinnaarryy//sseettss//**..ttaarr || ((ccdd //mmnntt;; xxaarrggss --nn11 ppaaxx --rrppee --ff )) Now you should copy the NetBSD second stage bootloader into your new root partition and install the bootblocks using Solaris's installboot(1M) command. # ccpp ~~//nneettbbssdd//iinnssttaallllaattiioonn//mmiisscc//ooffwwbboooott //mmnntt # //uussrr//ssbbiinn//iinnssttaallllbboooott ~~//nneettbbssdd//iinnssttaallllaattiioonn//mmiisscc//bboooottbbllkk //ddeevv//rrddsskk//cc00tt11dd00ss00 ++oo _C_r_e_a_t_i_n_g _N_e_t_B_S_D _D_e_v_i_c_e _N_o_d_e_s _u_n_d_e_r _S_o_l_a_r_i_s This is not a necessary step. If your _/_d_e_v directory is empty, init(8) will create a RAM disk with all of the essential device nodes each time the system boots. If you want to create the device nodes on disk, you will need to use the Solaris mknod(1M) command. Look in _/_d_e_v_/_M_A_K_E_D_E_V for the correct names, major and minor num- bers, ownership, and permissions. ++oo _C_o_n_f_i_g_u_r_i_n_g _t_h_e _N_e_t_B_S_D _s_y_s_t_e_m _f_r_o_m _S_o_l_a_r_i_s To save effort, you may want to use your favorite Solaris editor to configure some of the files in _/_e_t_c before booting into NetBSD the first time. In particu- lar, you should look at _/_e_t_c_/_f_s_t_a_b, _/_e_t_c_/_r_c_._c_o_n_f, _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f, and _/_e_t_c_/_h_o_s_t_s. See the section below on _P_o_s_t _i_n_s_t_a_l_l_a_t_i_o_n _s_t_e_p_s before _B_o_o_t_i_n_g _N_e_t_B_S_D _f_o_r _t_h_e _f_i_r_s_t _t_i_m_e. BBoooottiinngg NNeettBBSSDD ffoorr tthhee ffiirrsstt ttiimmee Now it is time to boot NetBSD for the first time. You will boot from your disk using similar syntax as described above in _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e and _D_e_t_e_r_m_i_n_i_n_g _h_o_w _t_o _b_o_o_t _f_r_o_m _a_n _S_B_U_S _o_r _P_C_I _c_a_r_d. To boot from your first disk, type: ok bboooott ddiisskk 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 ssuunn for a local console, or whatever is appropriate for your serial console (some systems display garbage with a ssuunn termi- nal type, you may need to use ssuunn--ssss55) 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_hme0="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_hme0="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. Select the proper terminal devices If you are using a serial console, you will have to edit the _/_e_t_c_/_t_t_y_s file and change sun-ss5 to the appropriate terminal type, such as vt220. 4. 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. 5. 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. 6. 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: 7. 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 _s_p_a_r_c_6_4_/_1_0_._9_9_._1_2_/_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 bbaasshh ppeerrll aappaacchhee xxffccee44 ffiirreeffooxx ... 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): eexxppoorrtt PPKKGG__PPAATTHH==hhttttppss::////ccddnn..nneettbbssdd..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//$$((uunnaammee --pp))//$$((uunnaammee --rr | ccuutt --dd__ --ff11))//AAllll ppkkgg__aadddd ppkkggiinn ++oo 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 hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ssttaabbllee//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. 8. 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 10.99.12 is with bina- ries, and that is the method documented here. To do the upgrade, you must boot the install kernel using one of the methods described above. 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 addi- tional 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 10.99.12 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 10.99.12. Note that ssyyssiinnsstt will automatically invoke postinstall fix and thus all issues that are fixed by ppoossttiinnssttaallll by default will be handled. In NetBSD 9 and earlier, filesystems listed in _/_e_t_c_/_f_s_t_a_b would be mounted before non-legacy zzffss 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 _g_u_i_d_e_: hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ffeeaattuurreess//UUFFSS22eeaa// before booting the updated system multi-user for the first time. _N_o_t_e _t_h_a_t _y_o_u _d_o _n_o_t _n_e_e_d _t_o _d_o _a_n_y_t_h_i_n_g _s_p_e_c_i_a_l _i_f _y_o_u _n_e_v_e_r _d_i_d _r_u_n _a_n_y _a_f_f_e_c_t_e_d _k_e_r_n_e_l_, especially if you have never run NetBSD -current. A number of things have been removed from the NetBSD 10.99.12 release. See the ``Components removed from NetBSD'' section near the beginning of this document for a list. 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 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. TThhee EEnndd NetBSD/sparc64 10.99.12 Dec 21, 2024 NetBSD/sparc64 10.99.12