INSTALLATION NOTES for NetBSD/amiga 1.2.1 Be sure to read _ALL_ of this document before you try to install NetBSD/amiga. What is NetBSD? ---- -- ------ The NetBSD Operating System is a fully functional UN*X-like system derrived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many architectures and is being ported to more. NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that this release wouldn't have come about. The current release has built upon the successful NetBSD 1.1 release by integrating many bug fixes, adding new and updated kernel subsystems, and adding various userland enhancements. The results of these improvements is a stable operating system fit for production use and ready for the next phase of development. Significant changes include: Continuing the multi-platform tradition, the integration of the DEC Alpha port has been completed, and new ports to ARM and x68k have been added. NetBSD/sparc now supports 4m machines. NetBSD/amiga now supports the DraCo. Standard C Prototypes have been added to the Kernel. Kernel NTP (Network Time Protocol) phased lock loop support has been added. See http://www.eecis.udel.edu/~ntp/ for more details. The PINT (PINT is not TWAIN) SCSI scanner driver interface has been integrated. See http://www.dol-esa.gov/~kstailey/pint for more details. A new SCSI medium changer driver and the `chio' program used to operate it has been added. The NFS subsystem now supports NFSv3. Several performance enhancements have been made to the networking subsystem. GCC, Libg++, and many other third party programs have been upgraded to more recent versions. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.2 also includes some refinement to the NetBSD binary emulation system (which includes FreeBSD, HP-UX, iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility), bringing NetBSD closer to the goal of making the emulation as accurate as possible. NetBSD 1.2.1 is an update of NetBSD 1.2. It fixes many bugs, but (with a few small exceptions) does not support any additional hardware or add new features. This is the third public release of NetBSD for the Amiga line of computers. Several additional graphics, network and SCSI boards are now supported, as well as the 68060 CPU. IBM encoded floppy disks can now be read and written (raw, Berkeley FFS and MSDOS file system; however, we still can't write the ADOS file system). This release should also work on early DraCo models, which still have a CIA timer. Note, however, that only onboard keyboard, onboard SCSI, the Altais graphics board, and non-DMA Zorro-II devices are supported on these machines; no parallel or serial port (especially no mouse) and no floppy drives yet. The Future of NetBSD: --- ------ -- ------ The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project. The NetBSD Foundation will help improve the quality of NetBSD by: * providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. * providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. * providing a better position from which to undertake promotional activities. * periodically organizing workshops for developers and other interested people to discuss ongoing work. We hope to have regular releases of the full binary and source trees, but these are difficult to coordinate, especially with all of the architectures which we now support! We hope to support even _more_ hardware in the future, and have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily basis. We intend to integrate free, positive changes from whatever sources will provide them, providing that they are well thought-out and increase the usability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD: ------- -- ------ NetBSD Mirror Site List The following sites mirror NetBSD as of Sep 30, 1996. Host name Services Provided ---- ---- -------- -------- ftp.netbsd.org Anonymous FTP FTP path: ftp://ftp.netbsd.org/pub/NetBSD sup.netbsd.org SUP SUP: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup ftp.iastate.edu Anonymous FTP, AFS FTP path: ftp://ftp.iastate.edu/pub/netbsd AFS path: /afs/iastate.edu/public/ftp/pub/netbsd ftp.eecs.umich.edu Anonymous FTP FTP path: ftp://ftp.eecs.umich.edu/BSD/NetBSD ftp.cs.umn.edu Anonymous FTP, SUP FTP path: ftp://ftp.cs.umn.edu/packages/NetBSD SUP: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG ftp.cslab.vt.edu Anonymous FTP FTP path: ftp://ftp.cslab.vt.edu/pub/NetBSD ftp.op.net Anonymous FTP FTP path: ftp://ftp.op.net/pub/NetBSD ftp.cetlink.net Anonymous FTP, SUP FTP path: ftp://ftp.cetlink.net/pub/NetBSD SUP: sup.cetlink.net hostbase=/a/anon_ftp/pub netbsd.rmit.edu.au Anonymous FTP, SUP FTP path: ftp://netbsd.rmit.edu.au/pub/NetBSD SUP: ftp://netbsd.rmit.edu.au/README.sup ftp.coppe.ufrj.br Anonymous FTP FTP path: ftp://ftp.coppe.ufrj.br/mirror/netbsd ftp.cevis.uni-Bremen.de Anonymous FTP FTP path: ftp://ftp.cevis.uni-Bremen.de/pub/comp/os/NetBSD netbsd.wifo.uni-mannheim.de Anonymous FTP, SUP FTP path: ftp://netbsd.wifo.uni-mannheim.de/pub/NetBSD SUP: See ftp://netbsd.wifo.uni-mannheim.de/pub/NetBSD/sup/cfg-files/normal ftp.uni-regensburg.de Anonymous FTP FTP path: ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD/ ftp.uni-trier.de Anonymous FTP, SUP FTP path: ftp://ftp.uni-trier.de/pub/unix/systems/NetBSD SUP: use host=sup.uni-trier.de, hostbase=/ftp/pub/unix/systems/NetBSD collections are the same as on sup.NetBSD.ORG netbsd.tohoku.ac.jp Anonymous FTP FTP path: ftp://netbsd.tohoku.ac.jp/NetBSD ftp.cs.uit.no Anonymous FTP, SUP FTP path: ftp://ftp.cs.uit.no/pub/NetBSD SUP: Get the file README.sup via anonymous ftp, and read it. ftp.ntnu.no Anonymous FTP FTP path: ftp://ftp.ntnu.no/pub/NetBSD/ skarven.itea.ntnu.no SUP SUP: Use this line as your sup file to get /usr/README.supinfo-skarven: current release=supinfo host=skarven.itea.ntnu.no use-rel-suffix backup delete old base=/usr prefix=/usr hostbase=/supmirror ftp.stacken.kth.se Anonymous FTP FTP path: ftp://ftp.stacken.kth.se/pub/OS/NetBSD ftp.sunet.se Anonymous FTP FTP path: ftp://ftp.sunet.se/pub/os/NetBSD If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. NetBSD 1.2.1 Release Contents: ------ ----- ------- -------- The NetBSD 1.2.1 release is organized in the following way: .../NetBSD-1.2.1/ BUGS Known bugs list (incomplete and out of date). CHANGES Changes since NetBSD's last release (and before). LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.2.1 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures that NetBSD 1.2.1 has a binary distribution for. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (e.g. those containing crypt(3)) that should not be exported from the United States, and that if you do export them, it's your fault, not ours. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: dsrc121 This set contains the "domestic" sources. These sources contain export-restricted encryption code and should not be exported from the U.S. [ 140K gzipped, 655K uncompressed ] gsrc121 This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 7.1M gzipped, 30.4M uncompressed ] ksrc121 This set contains the sources to the NetBSD 1.2.1 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc121 This set contains the "share" sources, which include the sources for the man pages not associated with any particular program, the sources for the typesettable document set, the dictionaries, and more. [ 2.4M gzipped, 8.9M uncompressed ] src121 This set contains all of the NetBSD 1.2.1 sources which are not mentioned above. [ 9.3M gzipped, 41.6M uncompressed ] It is worth noting that unless all of the source distribution sets are installed (except the domestic set), you can't rebuild and install the system from scratch, straight out of the box. However, all that is required to rebuild the system in that case is a trivial modification to one Makefile. The source distribution sets are distributed as groups of files named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) Catted together, the files belonging to a source distribution set comprise a gzipped tar file. If you want to look at list of the files contained in the set, you could use the command: cat set_name.?? | gunzip | tar tvf - or to actually extract the files contained in the set: cat set_name.?? | gunzip | tar xfp - In each of the source distribution set directories, there is a file named "CKSUMS" which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the integrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. [ XXX file sizes need to be upgraded in this section ] The amiga-specific portion of the NetBSD 1.2.1 release is found in the "amiga" subdirectory of the distribution. That subdirectory is layed out as follows: .../NetBSD-1.2.1/amiga/ binary/ amiga binary distribution sets; see below. miniroot/ amiga installation and upgrade file system images; see below. security/ amiga security distribution; see below; utils/ Miscellaneous amiga installation utilities; see installation section, below. There are two amiga file system images to be found in the "amiga/miniroot" subdirectory of the NetBSD 1.2.1 distribution. One of them is a upgrade image and one is an installation image. They are described in more detail below. There are gzipped versions of each available, for easier downloading. (The gzipped version have the ".gz" extension added to their names.) Installation file system: This file contains a BSD root file system setup to help you install the rest of NetBSD. This includes formatting and mounting your root and /usr partitions and getting ready to extract (and possibly first fetching) the distribution sets. There is enough on this file system to allow you to make a slip or ppp connection, configure an ethernet, mount an NFS file system or ftp. You can also load distribution sets from a SCSI tape or from one of your existing AmigaDOS partitions. This file is named "inst-121.fs". Upgrade file system: This file contains a BSD root file system setup to help you upgrade a previous version of NetBSD. This includes converting existing partitions and mounting your root and /usr partitions and getting ready to extract (and possibly first fetching) the distribution sets. There is enough on this file system to allow you to make a slip or ppp connection, configure an ethernet, mount an NFS file system or ftp. You can also load distribution sets from a SCSI tape, from one of your existing AmigaDOS partitions, or from an existing NetBSD partition. This file is named "upgr-121.fs". The NetBSD/amiga binary distribution sets contain the binaries which comprise the NetBSD 1.2.1 release for the amiga. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in subdirectories of the "amiga/binary" subdirectory of the NetBSD 1.2.1 distribution tree, and are as follows: base121 The NetBSD/amiga 1.2.1 base binary distribution. You MUST install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. [ 8M gzipped, 20M uncompressed ] comp121 The NetBSD/amiga Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!). This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 6M gzipped, 15M uncompressed ] etc121 This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand.) [ 77K gzipped, 340K uncompressed ] games121 This set includes the games and their manual pages. [ 3M gzipped, 7M uncompressed ] man121 This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. [ 1M gzipped, 3M uncompressed ] misc121 This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. [ 2M gzipped, 7M uncompressed ] text121 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 900K gzipped, 3M uncompressed ] The amiga security distribution set is named "secr121" and can be found in the "amiga/security" subdirectory of the NetBSD 1.2.1 distribution tree. It contains crypt.c (the source file for the DES encryption algorithm) and the binaries which depend on it. It can only be found on those sites which carry the complete NetBSD distribution and that can legally obtain it. (Remember, because of United States law, this distribution set may not be exported to locations outside of the United States and Canada.) [ 128K gzipped, 307K uncompressed ] The amiga binary distribution sets are distributed in the same form as the source distribution sets; catted together, the members of a set form a gzipped tar file. Each amiga binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. 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 files are extracted "below" the current directory. That is, if you want to extract the binaries "into" your system, i.e. replace the system binaries with them, you have to run the "tar xvfp" from /. Also note that if you upgrade or install this way, those programs that you are using at the time will NOT be replaced. If you follow the normal installation or upgrade procedures, this will be taken care of for you. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/amiga 1.2 runs on any Amiga that has a 68020 or better CPU with some form of FPU and MMU, and on DraCos which still have a CIA. The minimal configuration requires 4M of RAM and about 65M 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. (4M of RAM will actually allow you to compile, however it won't be speedy. X really isn't usable on a 4M system.) Here is a table of recommended HD partition sizes for a full install: partition: advise, with X, needed, with X root (/) 20M 20M 15M 15M user (/usr) 65M 100M 55M 90M swap ----- 2M for every M ram ----- local (/local) up to you As you may note the recommended size of /usr is 20M greater than needed. This is to leave room for a kernel source and compile tree as you will probably want to compile your own kernel. (GENERIC is large and bulky to accommodate all people). If you only have 4M of fast memory, you should make your swap partition larger, as your system will be doing much more swapping. Supported devices include: A4000/A1200 IDE controller. SCSI host adapters: 33c93 based boards: A2091, A3000 builtin and GVP series II. 53c80 based boards: 12 Gauge, IVS, Wordsync/Bytesync and Emplant.*) 53c710 based boards: A4091, Magnum, Warp Engine, Zeus and DraCo builtin. FAS216 based SCSI boards: FastLane Z3, Blizzard I and II**) Video controllers: ECS, AGA and A2024 built in on various Amigas. Retina Z2, Retina Z3 and Altais. Picasso II. GVP Spectrum. Piccolo. Piccolo SD64. A2410. Cybervision 64. Domino. Merlin (Zorro 2 only). Omnibus. Ethernet controllers: A2065 Ethernet Hydra Ethernet ASDG Ethernet A4066 Ethernet Ariadne Ethernet Quicknet Ethernet Arcnet controllers: A2060 Arcnet Tape drives: Most SCSI tape drives, including Archive Viper, Cipher SCSI-2 ST150. Scanners: SCSI-2 scanners behaving as SCSI-2 scanner devices, HP Scanjet II, Mustek SCSI scanner.***) CD-ROM drives: Most SCSI CD-ROM drives Serial cards: MultiFaceCard II and III A2232 Amiga floppy drives with Amiga (880/1760kB) and IBM (720/1440kB) encoding. ****) Amiga parallel port. Amiga serial port. Amiga mouse. If its not on the above lists, there is no support for it in this release. Especially (but this is an incomplete list), there is no driver for: Cyberstorm SCSI option, Blizzard IV SCSI, Blizzard 2060 SCSI, Ferret SCSI, Oktagon SCSI. Known problems with some hardware: *) the Emplant SCSI adapter has been reported by a party to hang after doing part of the installation without problems. **) Fastlane SCSI is reported to show data errors and hangs at least when used with multiple devices on the bus. This might be a problem with any FAS board. ***) SCSI scanner support is machine independend, so it should work, but hasn't been tested yet on most Amiga configurations. There are reports that it Mustek and HP Scanjet hang if accessed from the A3000. This might apply to other 33C93-Adapters, too. ****) Our floppy driver doesn't notice when mounted floppies are write-protected at the moment. Your floppy will stay unchanged, but you might not notice that you didn't write anything due to the buffer cache. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: AmigaDOS HD partitions Tape NFS partitions FTP NetBSD partitions, if doing an upgrade. The install or upgrade miniroot filesystem needs to be transferred to the NetBSD swap partition. This can be done from AmigaDOS in the case of a new install or upgrade, or from NetBSD when doing an upgrade. See the "Preparing your System for NetBSD Installation" section for details. The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. To prepare for installing via an AmigaDOS partition: To install NetBSD from an AmigaDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an AmigaDOS partition. All of the set_name.xx pieces can be placed in a single directory instead of separate ones for each distribution set. This will also simplify the installation work later on. Note where you place the files you will need this later. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via a tape: To install NetBSD from a tape, you need to somehow get the NetBSD filesets you wish to install on your system on to the appropriate kind of tape, in tar format. If you're making the tape on a UN*X system, the easiest way to do so is: tar cvf where "" is the name of the tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). If you can't figure it out, ask your system administrator. "" are the names of the "set_name.nnn" files which you want to be placed on the tape. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via an NFS partition: NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the NetBSD software you wish to install into a directory on an NFS server, and make that directory mountable by the machine which you will be installing NetBSD on. This will probably require modifying the /etc/exports file of the NFS server and resetting mountd, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of the router closest to the the new NetBSD machine, if the NFS server is not on a network which is directly attached to the NetBSD machine. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. To prepare for installing via FTP: NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. The preparations for this method of installation are easy: all you have to do is make sure that there's some FTP site from which you can retrieve the NetBSD installation when it's time to do the install. You should know the numeric IP address of that site, the numeric IP address of your nearest router if one is necessary Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. If you are upgrading NetBSD, you also have the option of installing NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base11" set somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ You will need an AmigaDOS hard drive prep tool to prepare you hard drives for use with NetBSD/amiga. HDToolBox is provided with the system software and on floppy installation disks since Release 2.0 of AmigaDOS so we will provide instructions for its use. Preparing you hard disk with HDToolBox: A full explanation of HDToolBox can be found with your AmigaDOS manuals and is beyond the scope of this document. Note you will be modifying your HD's if you mess something up here you could lose everything on all the drives that you configure. It is therefore advised that you: Write down your current configurations. Do this by examining each partition on the drive and the drives parameters (from Change drive type.) Back up the partitions you are keeping. What you need to do is partition your drives; creating at least root, swap and /usr partitions and possibly at least one more for /local if you have the space. (The root and swap partitions must be on the same drive for your initial installation. You can use other configurations after building a customized kernel once your system is running.) This should be done as the HDToolBox manual describes. One thing to note is that if you are not using a Commodore controller you will need to specify the device your SCSI controller uses e.g. if you have a Warp Engine you would: from cli, hdtoolbox warpdrive.device from wb set the tooltype, SCSI_DEVICE_NAME=warpdrive.device The important things you need to do above and beyond normal partitioning includes (from Partition Drive section): Marking all NetBSD partitions as non-bootable. Changing the file system parameters of the partitions to NetBSD ones. This must be done from the partitioning section and `Advanced options' must be enabled. To Make the needed changes: - Click the `Adv. Options' button - Click the `Change filesystem' button - Choose `Custom File System' - Turn off `Automount' if on. - Set the dostype to one of these three choices: root partition : 0x4e425207 swap partition : 0x4e425301 other partitions: 0x4e425507 Here `other' refers to other partitions you will format for reading and writing under NetBSD (e.g. /usr) Make sure you hit the return key to enter this value as some versions of HDToolBox will forget your entry if you don't. - Turn custom boot code off - Set Reserved Blocks start and end to 0. - Click Ok. Mask and maxtransfer are not used with NetBSD. Until you compile your own kernel your swap partition must exist on the drive that also holds your root partition. Once this is done NetBSD/amiga will be able to recognize your disks and which partitions it should use. Transferring the miniroot filesystem: The NetBSD/amiga installation or upgrade now uses a "miniroot" fileystem which is installed on the partition used by NetBSD for swapping. This removes the requirement of using a floppy disk for the filesystem used by the installation or upgrade process. It also allows more utilities to be present on the filesystem than would be available when using an 880K floppy disk. Once the hard disk has been prepared for NetBSD, the appropriate miniroot filesystem (inst-121.fs for a new install or upgr-121.fs for an upgrade) is transferred to the swap partition configured during the hard disk prep (or the existing swap parition in the case of an upgrade). The xstreamtodev utility provided in the "amiga/utilities" directory can be used on AmigaDOS to transfer the filesystem for either a new installation or an upgrade. The filesystem can also be transferred on an existing NetBSD system for an update by using dd. This should only be done after booting NetBSD into single-user state. It may also be possible to shutdown to single-user, providing that the single-user state processes are not using the swap partition. On AmigaDOS, the command: xstreamtodev --input=inst-121.fs --rdb-name= where is the name you gave to the NetBSD partition to be used for swapping. Use upgr-121.fs if you are going to do an upgrade of an existing NetBSD system. If xstreamtodev is unable to determine the SCSI driver device name or the unit number of the specified partition, you may also need to include the option "--device=" and/or "--unit=". To transfer the miniroot using NetBSD, you should be booted up in single user state on the current NetBSD system, or use the "shutdown now" command to shutdown to single-uyser state. Then copy the miniroot using dd: dd if=upgr-121.fs of=/dev/rsd0b where /dev/rsd0b should be the device path of the swap partition your system is configured to use. Once the file is copied, reboot back to AmigaDOS to boot the upgrade kernel. NOTE: the release kernel is a "generic" kernel, and requires that the swap partition be on the same device as the root partition. Installing the NetBSD System: ---------- --- ------ ------ Installing NetBSD is a relatively complex process, but, if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you must have already prepared your hard disk as detailed in the section on preparing your system for install. The following is a walk-through of the steps necessary to get NetBSD installed on your hard disk. If you wish to stop the installation, you may hit Control-C at any prompt, but if you do, you'll have to begin again from scratch. Transfer the install miniroot filesystem onto the hard disk partition used by NetBSD for swapping, as described in the "Preparing your System for NetBSD Installation" section above. You then need to have "ixemul.library" in your LIBS: directory on AmigaDOS. You also need to have the "loadbsd" program in your command path. If AmigaDOS complains about loadbsd not being an executable file, be sure that the "Execute" protection bit is set. If not, set it with the command: Protect loadbsd add e Next you need to get yourself into NetBSD by loading the kernel from AmigaDOS with loadbsd like so: loadbsd -b netbsd If you have an AGA machine, and your monitor will handle the dblNTSC mode, you may also include the "-A" option to enable the dblNTSC display mode. If your machine has a fragmented physical memory space, as, e.g., DraCo machines, you should add the "-n2" option to enable the use of all memory segments. You should see the screen clear and some information about your system as the kernel configures the hardware. Note which hard disk device(s) are configured (sd0, sd1, etc). Then you will be prompted for a root device. At this time type 'sd0*', where '0' is the device which contains the swap partition you created during the hard disk preparation. If the system should hang after entering the root device, try again with loadbsd -I ff -b netbsd This disables synchronous transfer on all SCSI devices. The system should continue to boot. For now ignore WARNING: messages about bad dates in clocks. Eventually you will be asked to enter the pathname of the shell, just hit return. After a short while you should see a welcome message and a prompt, asking if you wish to proceed with the installation. If you wish to proceed, enter "y" and then return. If you have configured your hard drive[s] correctly it should find the drive and partition that you selected to use as your root. You will be prompted for which device you want to use for your root. If you have multiple disks present with root partitions defined, you will need to be sure you enter the device name of the correct partition you want to install NetBSD on. YOU ARE NOW AT THE POINT OF NO RETURN. If you confirm that you want to install NetBSD, your hard drive will be modified, and perhaps its contents scrambled at the whim of the install program. If you are sure you want to proceed, enter "yes" at the prompt. The install program will now make the root filesystem you specified. There should be only one error in this section of the installation. It will look like so: newfs: ioctl (WDINFO): Invalid argument newfs: /dev/rsd0a: can't rewrite disk label If there are any others, restart from the the beginning of the installation process. This error is ok as the Amiga does not write disklabels currently. You should expect this error whenever using newfs. Next the install program will ask you which drive and partition you wish to use as /usr. First it will list the available drives. Choose one. Next it will give you a list of the partitions on that disk along with their sizes, types, etc.. Choose the letter that corresponds to the partition you wish to use for /usr. If you are doing a full install this should be at the very least 45M-50M large. If everything is ok the install program will then format and mount your /usr. If not then it will ask again for a drive and partition. When this completes your root partition will be mounted on /mnt and your /usr partition on /mnt/usr. An fstab will have been created and initialized to correctly mount these two file systems. This fstab will be in /mnt/etc. What you do from this point on depends on which media you're using to install NetBSD. Follow the appropriate instructions, given below. To install from an AmigaDOS partition: You first need to mount the AmigaDOS partition using the mount_ados command. If e.g. your AmigaDOS partition is the first partition on sd0 you could type: mkdir /mnt/ados mount_ados -o ro /dev/sd0d /mnt/ados You can use `disklabel sd0' to find out what types of partitions are on the disk `sd0'. Next goto the directory in which you stored the distribution sets. If e.g. you stored them in the root directory of the partition: cd /mnt/ados When there, run "Set_tmp_dir" and choose the default temporary directory, by hitting return at the prompt. Run the "Extract" command, giving it as its sole argument the name of the distribution set you wish to extract. For example, to extract the base distribution, use the command: Extract base121 and to extract the games distribution: Extract game12 If the distribution sets are in different directories, you will need to cd to each directory in turn, runing "Set_tmp_dir" and the appropriate "Extract" command(s). Continue this process until you've finished installing all of the sets which you desire to have on your hard disk. Once you have extracted all sets and are at the "#" prompt again, proceed to the section "Configuring Your System," below. To install from tape: The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, use the command "Set_tmp_dir" and enter your choice. The default is /mnt/usr/distrib. After you have picked a temporary directory, you should issue the load command: Load_tape Next, you will be told to insert the media into the appropriate drive, and hit return. Continue to follow instructions until you are returned to the "#" prompt. Go to the directory which contains the first distribution set you wish to install. This is either the directory you specified above, or possibly a subdirectory of that directory. When there, run "Set_tmp_dir" again, and choose the default temporary directory, by hitting return at the prompt. Run the "Extract" command, giving it as its sole argument the name of the distribution set you wish to extract. For example, to extract the base distribution, use the command: Extract base121 and to extract the games distribution: Extract game12 After the extraction is complete, go to the location of the next set you want to extract, "Set_tmp_dir" again, and once again issue the appropriate extract command. Continue this process until you've finished installing all of the sets which you desire to have on your hard disk. After each set is finished, if you know that you are running low on space you can remove the distribution files for that set by saying: rm set_name.?? For example, if you wish to remove the distribution files for the game09 set, after the "Extract game09" command has completed, issue the command: rm game12.?? Once you have extracted all sets and are at the "#" prompt again, proceed to the section "Configuring Your System," below. To install via FTP or NFS: First, use Set_tmp_dir to pick a temporary directory for the installation files. /mnt/usr/distrib is suggested. Configure the appropriate ethernet interface i.e. le0 if you have a 2065 or ed0 if you have a AMIGNET from Hydra Systems. ifconfig [netmask ] where is the interface name (e.g. ed0, etc.), and is the numeric IP address of the interface. If the interface has a special netmask, supply the word "netmask" and that netmask at the end of the command line. For instance, without a special netmask: ifconfig ed0 129.133.10.10 or with a special netmask ifconfig ed0 128.32.240.167 netmask 0xffffff00 You should also be able to use SLIP or PPP as the network connection. [XXX instructions for ppp or slip would be usefull perhaps the next release] If the NFS server or FTP server is not on a directly- connected network, you should set up a route to it with the command: route add default where is your gateway's numeric IP address. If you are NFS-mounting the distribution sets, mount them on the temporary directory with the command: mount -t nfs : where is the server's numeric IP address, is the path to the distribution files on the server, and is the name of the local temporary directory. Once this is done, proceed as if you had loaded the files from tape, "cd"ing to the appropriate directories and running "Set_tmp_dir" and "Extract" as appropriate. If you are retrieving the distribution sets using ftp, cd into the temp directory, and execute the command: ftp where is once again the server's numeric IP address. Get the files with FTP, taking care to use binary mode to transfer all files. Once you have all of the files for the distribution sets you wish to install, you can proceed using the instructions above as if you had installed the files from a tape. Configuring Your System: ----------- ---- ------ Once you have finished extracting all of the distribution sets that you want on your hard drive and are back at the "#" prompt, you are ready to configure your system. The configuration utility expects that you have installed the base system. If you have not, you will not be able to run it successfully (nor will you have a functional system regardless of configuration). To configure the newly installed operating system, run the command "Configure". Configure will ask for the machine's hostname, domain name, and other network configuration information. Once you have supplied `Configure' all that it requests, your machine will be configured well enough that when you reboot it it will almost be a completely functional NetBSD system. >>> Copy the kernel from the miniroot filesystem at this point <<< Once you are done with `Configure', halt the system with the "halt" command (wait for "halted" to be displayed) and reboot. Then again boot NetBSD this time with the command: loadbsd netbsd You need to do your final tweeks now. First mount your file systems like so: mount -av Your system is now complete but not completely configured; you should adjust the /etc/sendmail.cf file as necessary to suit your site and/or disable sendmail and other network related programs. These things can be found in /etc/netstart. Use vi, if you installed the man pages you can type `man vi' or `man ed' for instructions on how to use these somewhat non-intuitive editors. You should also put a copy of the netbsd kernel in your root partition. This can be done easily by mounting the AmigaDOS partition containing the kernel you used to start NetBSD and copying the "netbsd" file to the root: mount -r -t ados /dev/sd0d /mnt cp /mnt/netbsd / (where /dev/sd0d is the AmigaDOS partition where you have netbsd, and /mnt/netbsd is the appropriate path of the netbsd file). Once you are done with the rest of configuration unmount your file systems and halt your system, then reboot: cd / umount -av halt Finally you can now boot your system and it will be completely functional: loadbsd -a netbsd When it boots off of the hard drive, you will have a complete NetBSD system! CONGRATULATIONS! (You really deserve them!!!) Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ The upgrade to NetBSD 1.2.1 is a binary upgrade; it would be prohibitive to make users upgrade by compiling and installing the 1.2.1 sources, and it would be very difficult to even compile a set of instructions that allowed them to do so. Because of the various changes to the system, it is impractical to upgrade by recompiling from the sources and installing. To do the upgrade, you must have the NetBSD kernel on AmigaDOS and you must transfer the upgrade filesystem upgr-121.fs onto the swap partition of the NetBSD hard disk. You must also have at least the "base121" binary distribution set available, so that you can upgrade with it, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previously on the system. If you have a few megabytes free on each of your root and /usr partitions, you should have enough space. Since upgrading involves replacing the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process. To upgrade your system, follow the following instructions: Transfer the upgrade miniroot filesystem onto the hard disk partition used by NetBSD for swapping, as described in the "Preparing your System for NetBSD Installation" section above. Now boot up NetBSD using the 1.2.1 kernel using the loadbsd command: loadbsd -b netbsd If you machine has a splitted memory space, like, e.g., DraCo machines, use this instead: loadbsd -bn2 netbsd You should see the screen clear and some information about your system as the kernel configures the hardware. Note which hard disk device is configured that contains your root and swap partition. When prompted for the root device, type 'sd0*' (replacing 0 with the disk number that NetBSD used for your root/swap device). The '*' character indicates that the root filesystem is contained on the swap partition. When you reach the prompt asking you for a shell name, just hit return. You will be presented with some information about the upgrade process and a warning message, and will be asked if you wish to proceed with the upgrade process. If you answer negatively, the upgrade process will stop, and your disk will not be modified. If you answer affirmatively, the upgrade process will begin, and your disk will be modified. You may hit Control-C to stop the upgrade process at any time. However, if you hit it at an inopportune moment, your system may be left in an inconsistent (and possibly unusable) state. You will be asked if you wish to upgrade your file systems to the new file system format. If you do, reply affirmatively. If you don't have your file systems upgraded now, you should probably do it manually after the install process is complete, by using "fsck -c 2". Read the fsck(8) manual page for more details. The upgrade program will then check your root file system, and, if you approved, will upgrade it to the new file system format. It will then mount your root file system on /mnt. If your file systems are being upgraded, the upgrade script will copy the new fsck(8) program to your hard disk and upgrade your remaining file systems. The upgrade program will then mount all of your file systems under /mnt. (In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, etc.) If you don't already have the NetBSD distribution sets on your disk, look in the installation section for information on how to transfer them to your disk. Once the distribution sets are transferred to your disk, continue here. (Obviously, if the NetBSD distribution sets are already on your disk, because you've transferred them before starting the upgrade process, you don't need to transfer them again now!) After the software has been transferred to the machine (or mounted, in the case of upgrading via NFS), change into the directory containing the "base121" distribution set. Once you are there, run the "Set_tmp_dir" command, and hit return at the prompt to select the default answer for the temporary directory's path name. (It should be the path name of the directory that you're in.) Run the command "Extract base121" to upgrade the base distribution. Repeat the above two steps for all of the sets you wish to upgrade. (For each, change into the directory containing the set, run "Set_tmp_dir" and accept the default path name, then run the "Extract " command.) If you were previously using the security distribution set, you MUST upgrade to the new version, or you will not be able to log in when the upgrade process is complete. Similarly, if you were not previously using the security set, you must NOT upgrade to the new version. When you are done upgrading all of the distribution sets you wish to upgrade, issue the command "Cleanup". It will clean up the installation, by remaking some system databases. When it is complete, you should use "halt" to halt the system. You will probably also want to copy the release "netbsd" kernel image to your root at some point. Your system has now been upgraded to NetBSD 1.2.1. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.2.1 system. However, that doesn't mean that you're finished with the upgrade process. There are several things that you should do, or might have to do, to insure that the system works properly. First, if you did not upgrade your file systems to the new file system format during the upgrade process, you may want to do so now, with "fsck -c 2". If you are unsure about the process, it's suggested that you read the fsck(8) manual page. Second, you will probably want to get the etc121 distribution, extract it, and compare its contents with those in your /etc/ directory. You will probably want to replace some of your system configuration files, or incorporate some of the changes in the new versions into yours. Third, you will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this, but if not, you can just cd into /dev, and run the command "sh MAKEDEV all". Fourth, you must deal with certain changes in the formats of some of the configuration files. The most notable change is that the "options" given to many of the file systems in /etc/fstab or by hand have changed, and some of the file systems have changed names. To find out what the new options are, it's suggested that you read the manual page for the file systems' mount commands, for example mount_nfs(8) for NFS. (Note that the information for mounts of type "ffs", i.e. Fast File Systems, are contained in the mount_ffs(8) man page.) Finally, you will want to delete old binaries that were part of the version of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. If upgrading from a NetBSD version older than 1.0, you might also want to recompile any locally-built binaries, to take advantage of the shared libraries. (Note that any new binaries that you build will be dynamically linked, and therefore take advantage of the shared libraries, by default. For information on how to make statically linked binaries, see the cc(1) and ld(1) manual pages.) Using online NetBSD documentation ----- ------ ------ ------------- Documentation is available if you first install the manual distribution set. Traditionally, the "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropros(1), passwd(1), and 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 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Administrivia: ------------- Registration? What's that? 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 . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.ORG To report bugs, use the 'send-pr' command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: netbsd-bugs@NetBSD.ORG Use of 'send-pr' is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses. 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 this effort, and have an idea as to how you could be useful, send mail and/or subscribe to: netbsd-help@NetBSD.ORG As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to: ------ -- -- Members and 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 ongoing work on BSD systems, support, and encouragement. Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. Best Internet Communications for hosting the NetBSD FTP and SUP server. Cygnus Support for hosting the NetBSD Mail server. 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. Alistair G. Crooks has been producing tar file snapshot reports for NetBSD-current users, a very valuable service. Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. The following people (in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: Bay Area Internet Solutions Jason Brazile Dave Burgess Canada Connect Corporation James Chacon Bill Coldwell Charles Conn Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Easynet, UK Free Hardware Foundation Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow MS Macro System GmbH, Germany Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Jason R. Thorpe Steve Wadlow (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) 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 mentioned, tell us!) We are: -- --- (in alphabetical order) The NetBSD core group: J.T. Conklin Charles Hannum Paul Kranenburg Jason Thorpe Christos Zoulas The port-masters (and their ports): Allen Briggs (mac68k) Mark Brinicombe (arm32) Chuck Cranor (mvme68k) Chris G. Demetriou (alpha) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Anders Magnusson (vax) Phil Nelson (pc532) Masaru Oki (x68k) Gordon Ross (sun3) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (i386) Leo Weppelman (atari) Supporting cast: Steve Allen John Brezak Aaron Brown Dave Burgess Bill Coldwell Bernd Ernesti Hubert Feyrer Brian R. Gaeke Adam Glass Michael Graff Brad Grantham Matthew Green Michael L. Hitch Lawrence Kesteloot John Kohl Ted Lemon Paul Mackerras Neil J. McRae Perry Metzger Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Scott Reynolds Karl Schilke (rAT) Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Ignatios Souvatzis Kevin Sullivan Legal Mumbo-jumbo: ----- ----- ----- The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by John Kohl. This product includes software developed by Paul Kranenburg. This product includes software developed by Terrence R. Lambert. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl for the NetBSD Project. This product includes software developed by Chris Provenzano. This product includes software developed by Theo de Raadt. This product includes software developed by the David Muir Sharnoff. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/ This product includes software developed by TooLs GmbH. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed by Christos Zoulas. This product includes software developed by Klaus Burkert. This product includes software developed by Michael van Elst. This product includes software developed by Bernd Ernesti. This product includes software developed by Michael L. Hitch. This product includes software developed by Christian E. Hopps. This product includes software developed by Mika Kortelainen. This product includes software developed by Jukka Marin. This product includes software developed by Kari Mettinen. This product includes software developed by Brad Pepers. This product includes software developed by Ignatios Souvatzis. This product includes software developed by Ezra Story. This product includes software developed by Lutz Vieweg. This product includes software developed by Daniel Widenfalk. This product includes software developed by Markus Wild.