INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL -- Installation procedure for NetBSD/evbarm. CCOONNTTEENNTTSS About this Document What is NetBSD? Dedication Changes Between The NetBSD 9 and 10 Releases Features to be removed in a later release The NetBSD Foundation Sources of NetBSD NetBSD 10.0_RC4 Release Contents NetBSD/evbarm subdirectory structure Binary distribution sets NetBSD/evbarm System Requirements and Supported Devices 32-bit SoCs supported by GENERIC kernels (Armv7-A) 64-bit SoCs supported by GENERIC64 kernels Getting the NetBSD System on to Useful Media Preparing your System for NetBSD installation Installing the NetBSD System Installation for Armv7 and AArch64 devices with U-Boot Installing NetBSD/evbarm to a SATA hard disk 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.0_RC4 on the _e_v_b_a_r_m platform. It is available in four different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is one of _._p_s, _._h_t_m_l, _._m_o_r_e, or _._t_x_t: _._p_s PostScript. _._h_t_m_l Standard Internet HTML. _._m_o_r_e The enhanced text format used on UNIX-like systems by the more(1) and less(1) pager util- ity programs. This is the format in which the on-line _m_a_n pages are generally presented. _._t_x_t Plain old ASCII. You are reading the _m_o_r_e version. WWhhaatt iiss NNeettBBSSDD?? The NetBSD Operating System is a fully functional open- source operating system derived from the University of Cali- fornia, Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many different different system architectures (ports) across a variety of distinct CPU families, and is being ported to more. The NetBSD 10.0_RC4 release contains complete binary releases for most of these system architectures, with preliminary support for the others included in source form. Please see the NetBSD _w_e_b_s_i_t_e_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg// for information on them. NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD fea- tures a complete set of user utilities, compilers for sev- eral languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code. NetBSD is a creation of the members of the Internet commu- nity. Without the unique cooperation and coordination the net makes possible, NetBSD would not exist. DDeeddiiccaattiioonn NetBSD 10.0 is dedicated to the memory of Ryo SHIMIZU, who passed away in May 2023. Ryo's technical contributions are too many to list here in full. He was a long term contributor and worked on a lot of low-level code over various architectures, from x68k to aarch64. He also worked on various out-of-tree NetBSD items, like the IIJ git repository conversion. The project lost an excellent technical contributor and many of us a good friend. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 99 aanndd 1100 RReelleeaasseess The NetBSD 10.0_RC4 release provides many significant changes, including support for many new devices, hundreds of bug fixes, new and updated kernel subsystems, and numerous userland enhancements. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. One important new feature in this release is the support for extended attributes and access controll lists on FFS file systems. For new installations the installer will default to disable this features, so the file system is compatible with older NetBSD releases (before 10), and allow other operating sys- tems to mount this file systems at least in read-only mode. If you want a new installed file system to support extended attributes, change the file system type from ``FFSv2'' to ``FFSv2ea'' in the partitioning menu. You can also convert file systems later, using the fsck_ffs(8) utility. More details are available in _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.0_RC4 release. The complete list of changes can be found in the following files: _C_H_A_N_G_E_S_: hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--1100..00__RRCC44//CCHHAANNGGEESS _C_H_A_N_G_E_S_-_1_0_._0_: hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD--1100..00__RRCC44//CCHHAANNGGEESS--1100..00 files in the top level directory of the NetBSD 10.0 release tree. 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..00__RRCC44 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 10.0_RC4 release is orga- nized as follows: _._._._/_N_e_t_B_S_D_-_1_0_._0___R_C_4_/ CHANGES Changes between the 9.0 and 10.0 releases. CHANGES-10.0 Changes between the initial 10.0 branch and final release of 10.0. CHANGES.prev Changes in previous NetBSD releases. LAST_MINUTE Last minute changes and notes about the release. README.files README describing the distribution's contents. _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.0_RC4 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.0_RC4 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. ssyyssssrrcc This set contains the sources to the NetBSD 10.0_RC4 kernel for all architectures as well as the config(1) utility. xxssrrcc This set contains the sources to the X Window Sys- tem. All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the ppkkggssrrcc set, which is traditionally unpacked into _/_u_s_r_/_p_k_g_s_r_c, all sets may be unpacked into _/_u_s_r_/_s_r_c with the command: # ccdd // ;; ttaarr --zzxxppff sseett__nnaammee..ttggzz In each of the source distribution set directories, there are files which contain the checksums of the files in the directory: MD5 MD5 digests in the format produced by the com- mand: cckkssuumm --aa MMDD55 _f_i_l_e. SHA512 SHA512 digests in the format produced by the command: cckkssuumm --aa SSHHAA551122 _f_i_l_e. The SHA512 digest is safer, but MD5 checksums are provided so that a wider range of operating systems can check the integrity of the release files. _N_e_t_B_S_D_/_e_v_b_a_r_m _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The evbarm-specific portion of the NetBSD 10.0_RC4 release is found in the _e_v_b_a_r_m subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_0_._0___R_C_4_/_e_v_b_a_r_m_/. It contains the following files and directories: _I_N_S_T_A_L_L_._h_t_m_l _I_N_S_T_A_L_L_._p_s _I_N_S_T_A_L_L_._t_x_t _I_N_S_T_A_L_L_._m_o_r_e Installation notes in various file formats, including this file. The _._m_o_r_e file contains underlined text using the more(1) conventions for indicating italic and bold display. _b_i_n_a_r_y_/ _g_z_i_m_g_/ _a_r_m_v_7_._i_m_g_._g_z A gzipped writable image containing the complete NetBSD operat- ing system for a range of 32-bit devices (includes a GENERIC kernel). _a_r_m_6_4_._i_m_g_._g_z A gzipped writable image containing the complete NetBSD operat- ing system for a range of 64-bit devices (includes a GENERIC64 kernel). _r_p_i_._i_m_g_._g_z A gzipped writable image containing the complete 32-bit NetBSD operating system for Raspberry Pi variants only (includes RPI ker- nels). _k_e_r_n_e_l_/ _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z A gzipped Armv7 kernel which supports a range of 32-bit devices that do not need board-specific ker- nels. _n_e_t_b_s_d_-_G_E_N_E_R_I_C_6_4_._g_z A gzipped AArch64 kernel which supports a range of 64-bit devices that do not need board-specific ker- nels. _n_e_t_b_s_d_-_R_P_I_._g_z A gzipped Armv6 kernel which supports the Rasp- berry Pi 1 only. _n_e_t_b_s_d_-_R_P_I_2_._g_z A gzipped Armv6 kernel which supports the Rasp- berry Pi 2 only. _s_e_t_s_/ evbarm 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_/ evbarm kernel modules providing memory disk root file systems for expert usage. _m_i_s_c_/ _b_o_o_t_a_a_6_4_._e_f_i AArch64 EFI boot- loader _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD 10.0_RC4 release for evbarm is comprised of the fol- lowing binary sets, which can be found in the _e_v_b_a_r_m_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 10.0_RC4 distribution tree: bbaassee The NetBSD 10.0_RC4 evbarm bbaassee binary distribution. You _m_u_s_t install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. ccoommpp Things needed for compiling programs. This set includes the system include files (_/_u_s_r_/_i_n_c_l_u_d_e) and the various system libraries (except the shared libraries, which are included as part of the bbaassee set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. ddeebbuugg This distribution set contains debug information for all base system utilities. It is useful when reporting issues with binaries or during development. This set is huge, if the target disk is small, do not install it. ddttbb Devicetree hardware descriptions for specific boards. eettcc This distribution set contains the system configuration 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. ggppuuffww This set includes firmware for graphical drivers. kkeerrnn--GGEENNEERRIICC This set contains a NetBSD/evbarm 10.0_RC4 GENERIC ker- nel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. mmaann This set includes all of the manual pages for the bina- ries and other software contained in the bbaassee set. Note that it does not include any of the manual pages that are included in the other sets. mmiisscc This set includes the system dictionaries, the typeset- table document set, and other files from _/_u_s_r_/_s_h_a_r_e. mmoodduulleess This set includes kernel modules to add functionality to a running system. rreessccuuee This set includes the statically linked emergency recover binaries installed in _/_r_e_s_c_u_e. tteexxtt This set includes NetBSD's text processing tools, including groff(1), all related programs, and their man- ual pages. NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on 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 environ- ment. 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 modi- fied. xxsseerrvveerr The X server. This includes the modular X.Org server. The evbarm 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 rela- tive and therefore the files are extracted _b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y. Therefore, if you want to extract the binaries into your system, i.e., replace the system binaries with them, you have to run the ttaarr --xxzzppff command from the root directory ( _/ ) of your system. _N_o_t_e_: Each directory in the evbarm binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//eevvbbaarrmm SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess _3_2_-_b_i_t _S_o_C_s _s_u_p_p_o_r_t_e_d _b_y _G_E_N_E_R_I_C _k_e_r_n_e_l_s _(_A_r_m_v_7_-_A_) _Q_E_M_U_: hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ppoorrttss//eevvbbaarrmm//qqeemmuu__aarrmm// is also supported. ++oo Allwinner A10, A13, A20, A32, A80, A83T, H3 (e.g. Cubieboard, OLinuXino, LeMaker Banana Pi...) ++oo Amlogic S805 (e.g. ODROID-C1) ++oo Broadcom BCM2836 (e.g. Raspberry Pi 2) ++oo Freescale/NXP i.MX6 Dual/DualLite/Quad, i.MX7 Dual (e.g. Wandboard, UDOO, Hummingboard...) ++oo Samsung Exynos 5422 (e.g. ODROID-XU3/XU-4) ++oo Texas Instruments AM335x and OMAP3 (e.g. BeagleBoard, BeagleBone Black...) ++oo Xilinx Zynq (e.g. Zedboard, Parallella...) ++oo NVIDIA Tegra K1 For a full list of supported devicetree-based boards, see the contents of the _d_t_b_._t_g_z set. _6_4_-_b_i_t _S_o_C_s _s_u_p_p_o_r_t_e_d _b_y _G_E_N_E_R_I_C_6_4 _k_e_r_n_e_l_s Devices conforming to the Arm "ServerReady" (SBBR and SBSA) spec- ifications, and _Q_E_M_U_: hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ppoorrttss//eevvbbaarrmm//qqeemmuu__aarrmm// are also supported. ++oo Allwinner H5, H6, A64 (e.g. PINE64, Pinebook, NanoPi A64, OLinuXino...) ++oo Amlogic G12, S905, S805X, S905D, S905W, S905X (e.g. ODROID-N2+, Le Potato, NanoPi K2...) ++oo Broadcom BCM2837, BCM2711 (e.g. Raspberry Pi 3 and 4) ++oo Freescale/NXP i.MX8MQ (e.g. Hummingboard...) ++oo Rockchip RK3328, RK3328 (e.g. Pinebook Pro, RockPro64, Firefly...) ++oo NVIDIA Tegra X1 For a full list of supported devicetree-based boards, see the contents of the _d_t_b_._t_a_r_._x_z set. GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa Generally, NetBSD is installed on Arm devices by writing a live image (armv7.img, or arm64.img for 64-bit devices) to a SD card or USB device. For Armv6 Raspberry Pi 1s, this image is rpi.img.gz. The storage device should be at least 2GB. If you're on Windows rather than a Unix variant, you can use _r_a_w_r_i_t_e_3_2_: hhttttppss::////wwwwww..nneettbbssdd..oorrgg//~~mmaarrttiinn//rraawwrriittee3322//iinnddeexx..hhttmmll instead of dd(1) to write images, and _7_-_Z_i_p_: hhttttppss::////wwwwww..77--zziipp..oorrgg// to decompress .gz files. Arm devices generally also ship with a vendor-specific U-Boot bootloader, which may be replaced with a board-specific "main- line" U-Boot image from pkgsrc for an optimal NetBSD experience. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn After writing an SD card image, there are generally no specific preparation steps needed for Arm. Once the system is booted, the init system will resize the root partition to take up the entire disk. Afterwards, the system can be configured to your liking. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm _I_n_s_t_a_l_l_a_t_i_o_n _f_o_r _A_r_m_v_7 _a_n_d _A_A_r_c_h_6_4 _d_e_v_i_c_e_s _w_i_t_h _U_-_B_o_o_t ++oo Download or build armv7.img.gz (32-bit) or arm64.img.gz (64-bit). ++oo Decompress the .gz image, using gunzip(1) on Unix. ++oo Write the image to disk: # dd if=armv7.img of=/dev/rld0 bs=1m conv=sync progress=1 ++oo If you are using Microsoft Windows, you can use _r_a_w_r_i_t_e_3_2_: hhttttppss::////wwwwww..nneettbbssdd..oorrgg//~~mmaarrttiinn//rraawwrriittee3322// to write SD card images, which can handle decompression too. ++oo To replace the vendor U-Boot bootloader with a "main- line" U-Boot, obtain a board-specific image. Bootload- ers are provided by the _s_y_s_u_t_i_l_s_/_u_-_b_o_o_t_-_* packages in _p_k_g_s_r_c_: hhttttppss::////wwwwww..ppkkggssrrcc..oorrgg//. If you're using pkgsrc on an UNIX-like operating system that isn't NetBSD, you must bootstrap first (see the _R_E_A_D_M_E file in the root directory of pkgsrc). You can also extract the U-Boot image from u-boot-*.tgz archive in an existing _N_e_t_B_S_D _b_i_n_a_r_y _p_a_c_k_a_g_e _s_e_t_: hhttttppss::////ccddnn..nneettbbssdd..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD//aaaarrcchh6644//99..00//AAllll//. Install the board-specific U-Boot to the SD card, e.g. for Allwinner devices (PINE H64 in this case): # dd if=/usr/pkg/share/u-boot/pine-h64/u-boot-sunxi-with-spl.bin of=/dev/rld0 bs=1k seek=8 conv=sync progress=1 Or a Rockchip device (e.g. RockPro64): # dd if=/usr/pkg/share/u-boot/rockpro64/rksd_loader.img of=/dev/rld0 seek=64 conv=sync progress=1 _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D_/_e_v_b_a_r_m _t_o _a _S_A_T_A _h_a_r_d _d_i_s_k Some Arm boards offer a SATA interface, and you might want to install NetBSD to a hard disk after you've got it running from an SD card. You can do this using sysinst(8) from within NetBSD. There are instructions for using _s_y_s_i_n_s_t _o_n _A_r_m_: hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//ppoorrttss//eevvbbaarrmm//iinnssttaallll__uussiinngg__ssyyssiinnsstt// on the NetBSD wiki. The main difference from installing on other ports is that a FAT32 partition is required for /boot. 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 prop- erly 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 config- uration of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt normally will), the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (_/) mounted read-only. When the system asks you to choose a shell, simply press RETURN to get to a _/_b_i_n_/_s_h prompt. If you are asked for a terminal type, respond with vvtt222200 (or whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # 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 proceed. 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 documentation 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 continue 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_awge0="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_awge0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are feeling a little more adventurous) run named(8). See resolv.conf(5) or named(8) for more information. Instead of manually configuring networking, DHCP can be used by setting dhcpcd=YES in _/_e_t_c_/_r_c_._c_o_n_f. 3. Logging in After reboot, you can log in as root at the login prompt. If you didn't set a password in ssyyssiinnsstt, there is no initial password. You should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. By default, root login from the network is dis- abled (even via ssh(1)). One way to become root over the network is to log in as a different user that belongs to group ``wheel'' (see group(5)) and use su(1) to become root. 4. Adding accounts Use the useradd(8) command to add accounts to your system. Do not edit _/_e_t_c_/_p_a_s_s_w_d directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database. 5. The X Window System If you installed the X Window System, you may want to read the chapter about X in the _N_e_t_B_S_D _G_u_i_d_e_: hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//gguuiiddee//eenn//cchhaapp--xx..hhttmmll: 6. Installing third-party packages If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system, pkgsrc. pkgsrc automati- cally handles any changes necessary to make the software run on NetBSD. This includes the retrieval and installation of any other packages the software may depend upon. ++oo More information on the package system is available at hhttttppss::////wwwwww..NNeettBBSSDD..oorrgg//ddooccss//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll ++oo A list of available packages suitable for browsing is at hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ccuurrrreenntt//ppkkggssrrcc//RREEAADDMMEE..hhttmmll ++oo Precompiled binaries can be found at hhttttppss::////ccddnn..NNeettBBSSDD..oorrgg//ppuubb//ppkkggssrrcc//ppaacckkaaggeess//NNeettBBSSDD// usually in the _e_v_b_a_r_m_/_1_0_._0___R_C_4_/_A_l_l subdir. If you installed pkgin(1) in the ssyyssiinnsstt post-installation con- figuration 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 correctly con- figured, you can install them with the following com- mands: ## 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 compiling 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. 7. Misc ++oo Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. ++oo Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you use. ++oo Many of the _/_e_t_c files are documented in section 5 of the manual; so just invoking # mmaann 55 _f_i_l_e_n_a_m_e is likely to give you more information on these files. UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm The easiest way to upgrade to NetBSD evbarm 10.0_RC4 is by using the sysutils/sysupgrade package from pkgsrc. First, edit _/_u_s_r_/_p_k_g_/_e_t_c_/_s_y_s_u_p_g_r_a_d_e_._c_o_n_f. Make sure RELEASEDIR and ARCHIVE_EXTENSION are correct: # Replace evbarm-aarch64 with evbarm-earmv7hf on a 32-bit system, evbarm-earmv6hf on the original RPI RELEASEDIR="https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0_RC4/evbarm-aarch64/" ARCHIVE_EXTENSION=tar.xz Make sure _/_b_o_o_t is mounted, and copy the new board-specific _*_._d_t_s device tree file into place. Note that the device tree files are sorted into SoC-type subdirectories in _/_b_o_o_t_/_d_t_b, e.g. allwinner, amlogic, broadcom, freescale, nvidia, rockchip. For example, for the Allwinner-based PINE A64 LTS: $ ftp https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0_RC4/evbarm-aarch64/binary/sets/dtb.tar.xz $ unxz dtb.tar.xz # cp ./boot/dtb/allwinner/sun50i-a64-pine64-lts.dtb /boot/dtb/allwinner/ Also copy _b_o_o_t_a_a_6_4_._e_f_i if applicable: $ ftp https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.0_RC4/evbarm-aarch64/installation/misc/bootaa64.efi # cp bootaa64.efi /boot/EFI/BOOT/bootaa64.efi Finally: # sysupgrade fetch # sysupgrade kernel # sysupgrade modules # reboot # sysupgrade sets # sysupgrade etcupdate # sysupgrade postinstall # reboot This is the most careful possible path with sysupgrade that makes sure the kernel and userland are always fully compatible, by mak- ing sure the kernel and boot files are newer than the userland. It is also possible to: # sysupgrade auto # reboot 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.0_RC4. 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. The display drivers used for modern GPUs and the whole subsystem supporting it (DRM/KMS) have been updated to a newer version. Unfortunately not all issues with this have been resolved before the NetBSD 10.0 release. You can find a list of issues in the _O_p_e_n _i_s_s_u_e_s _w_i_t_h _n_e_w _D_R_M_/_K_M_S_: hhttttppss::////wwiikkii..nneettbbssdd..oorrgg//rreelleenngg//nneettbbssdd--1100// section of the release engineering wiki page. A number of things have been removed from the NetBSD 10.0_RC4 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 distribu- tion set. Traditionally, the ``man pages'' (documentation) 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 categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The _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 numbered section name will be displayed. For instance, after logging in, enter # mmaann ppaasssswwdd to read the documentation for passwd(1). To view the documenta- tion 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 possibly 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 interface 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 spe- cific 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 appropriate 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 encouragement. ++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 host- ing 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 prob- ably were not able to get in touch with you, to verify 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 January, 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 registered trademarks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: 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 Founda- tion. This product includes software developed by The NetBSD Founda- tion, 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 Tech- nology Division, US Naval Research Laboratory. This product includes software developed by Aaron Brown and Har- vard 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 Software 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. Simpson. This product includes software developed by Causality Limited. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Charles M. Hannum, by the University of Vermont and State Agricultural College and Gar- rett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its con- tributors. 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 Services at Carnegie Mellon University (http://www.cmu.edu/computing/). 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 Gor- don 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@min- com.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 University. This product includes software developed by Harvard University and its contributors. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch This product includes software developed by Henrik Vestergaard 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 Corporation and its contributors. This product includes software developed by Internet Initiative 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. Wittkoski. 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 Highfield. 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 Cal- ifornia, 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. Midden. 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 Fredette. 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 Hallqvist. This product includes software developed by Niklas Hallqvist, 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 Marques 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. Nelson. This product includes software developed by QUALCOMM Incorpo- rated. 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 contributors. 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 Navigation, 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 Strategies, 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 Univer- sity 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 kernel team This product includes software developed by the RiscBSD team. This product includes software developed by the SMCC Technology 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 contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berke- ley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by the Urbana-Champaign 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. "Similar oper- ating 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 University All Rights Reserved. Permission to use, copy, modify and distribute this soft- ware and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative 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 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.Distribu- tion@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 soft- ware and its documentation is hereby granted, provided that both the copyright notice and this permission notice appear in all copies of the software, derivative 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.Distribu- tion@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 soft- ware and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies. Stanford University makes no repre- sentations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. TThhee EEnndd NetBSD/evbarm 10.0_RC4 Feb 06, 2024 NetBSD/evbarm 10.0_RC4