INSTALLATION NOTES for NetBSD/atari 1.2 Be sure to read _ALL_ of this document before you try to install NetBSD/atari. 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. The Atari release stepped in in March 1995. The first official release was NetBSD1.1. The NetBSD1.2 release is yet another step along the NetBSD-road! It fixes a huge number of bugs in the handling of the serial-port, video, Falcon SCSI and others. Also, finally a parallel printer is supported. 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 Release Contents: ------ --- ------- -------- The NetBSD 1.2 release is organized in the following way: .../NetBSD-1.2/ 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 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 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: dsrc12 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 ] gsrc12 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 ] ksrc12 This set contains the sources to the NetBSD 1.2 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc12 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 ] src12 This set contains all of the NetBSD 1.2 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. The Atari-specific portion of the NetBSD 1.2 release is found in the "atari" subdirectory of the distribution. That subdirectory is layed out as follows: .../NetBSD-1.2/atari/ binary/ atari binary distribution sets; see below. floppies/ atari boot and installation floppies; see below. security/ atari security distribution; see below; utils.netbsd/ utils.tos/ Miscellaneous atari installation utilities; see installation section, below. There are three atari floppy images to be found in the "atari/floppies" subdirectory of the NetBSD 1.2 distribution. One of them is a bootable TOS kernel floppy and the other two are installation floppy's. 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.) Bootable Kernel floppy: This TOS disk contains the loadbsd and chg_part programs and the BOOT kernel. It is setup so that you can insert it int your floppy drive, and start the programs from GEM. This floppy is named boot-12.fs Installation floppy: This disk 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 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 TOS partitions. This floppy's are named "miniroot-12.fs.1" and "miniroot-12.fs.2". The NetBSD/atari binary distribution sets contain the binaries which comprise the NetBSD 1.2 release for the atari. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in subdirectories of the "atari/binary" subdirectory of the NetBSD 1.2 distribution tree, and are as follows: base12 The NetBSD/atari 1.2 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, 22M uncompressed ] comp12 The NetBSD/atari 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. [ 5M gzipped, 18M uncompressed ] etc12 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.) [ 70K gzipped, 360K uncompressed ] games12 This set includes the games and their manual pages. [ 3M gzipped, 7M uncompressed ] man12 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. [ 900K gzipped, 4M uncompressed ] misc12 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 ] text12 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 784K gzipped, 3M uncompressed ] The atari security distribution set is named "secr12" and can be found in the "atari/security" subdirectory of the NetBSD 1.2 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.) [ 119K gzipped, 300K uncompressed ] The atari 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 atari 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/atari 1.2 runs on a TT030 and a Falcon. An FPU is not required. The minimum amount of RAM required is 4Mb. Here is a table of recommended HD partition sizes for a full install: partition: advise, with X, needed, with X root (/) 15M 15M 10M 10M user (/usr) 65M 100M 45M 80M 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, BOOT is small and might not have all the features you want). Supported devices include: - The buildin SCSI host adapter - Should support most SCSI-drives. The drives that are currently tested are: MAXTOR 7245S, MAXTOR 7080S, SEAGATE ST157N - Should support most tape drives. The drives that are currently tested are: TANDBERG 3600 - Should support most CD-ROM drives. - Should support most ZIP/MO drives. - The buildin video controller - The building (720Kb/1.44Mb) floppydrive - The serial2/modem2 ports - The Falcon FX memory expansion - The atari mouse - A 3-button mouse - The parallel printer If its not on this list, there is probably no support for it in this release. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: * TOS HD partitions * Tape No matter what you do, however, you'll need to have three disks handy, on which you will put the install and boot floppy images. All the images are available from the directory "atari/floppies", under the root of the NetBSD tree at your favorite archive site. If you are using NetBSD/atari to make the floppies, you should use the command dd(1) to write the raw floppy images (.fs files) to the disk. To write onto fd0 use: dd if=miniroot-12.fs.1 of=/dev/rfd0b bs=9b If you are using TOS to make the floppies, grab the 'rawwrite' utility from the "atari/utils" directory and issue the command: rawwrite miniroot-12.fs This will create the boot-floppy on the floppy in drive a. The floppies should be pre-formatted on 720Kb for both the 'dd' and 'rawwrite' commands to work. Pre-formatting can be best done using the desktop format command. Some other utilities seem to be giving problems. 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 GEMDOS partition: To install NetBSD from an GEMDOS partition, you need to get the NetBSD distribution sets you wish to install on your system on to an GEMDOS partition. Rename the sets from xxx.tar.gz to xxx.tgz. Note where you placed 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. If you make the tape on a UN*X-like system, you can create it as follows: cd .../NetBSD-1.2/atari/binary T= mt -f $T rewind for f in base etc comp games man misc text dd if=$f.tar.gz of=$T conv=sync bs=5k done mt -f $T rewind where "" is the name of the (non-rewinding!) tape device that you're using (probably something like /dev/nrst0, but we make no guarantees 8-). If you can't figure it out, ask your system administrator. Once you have done this, you can proceed to the next step in the installation process, preparing your hard disk. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ Note you will be modifying your HD's if you mess something up here you could lose everything on all the drives that you mess with. It is therefore advised that you: Write down your current configurations. Do this by writing down all partition info (especially their sizes). Back up the partitions you are keeping. If NetBSD has to share the disk with another operating system, you must take care of partitioning your harddisk before installing NetBSD; creating space for at least root, swap and /usr partitions and possibly at least one more for /local if you have the space. Warning: The AHDI partioning function erases all partions on your harddisk even if they are not changed! I know this is rather stupid, but don't say I didn't warn you. If NetBSD has a disk of it's own, you can delay the partitioning until the installer requests you to do it. 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. 1. Booting the miniroot ======================= First you need to get yourself into NetBSD. This can be done in a couple ways, both of which currently require GEMDOS. You can insert the GEMDOS kernel floppy and select the loadbsd program. It will ask for parameters, supply: '-b netbsd'. You can, of course, also run it from the shell command-line in MiNT: loadbsd -b a:/netbsd You should see the screen clear and some information about your system as the kernel configures the hardware. Then you will be prompted for a root device. At this time remove the GEMDOS kernel boot floppy from the drive if present and insert the BSD install floppy 1. Now type `rd0' to tell the kernel to load the install filesystem into RAMdisk. While While the kernel is loading, it will show a '.' for each track loaded. After loading 80 tracks, it will ask you to insert the next floppy. At this time, inser the BSD install floppy 2 and hit any key. The kernel continous loading another 40 tracks before it continues to boot. The system should continue to boot. For now ignore WARNING: messages about bad dates in clocks. Eventually you will be be asked to enter the pathname of the shell, just hit return. After a short while, you will be asked to select the type of your keyboard. After you have entered a valid response here, the system asks you if you want to install or upgrade your system. Since you are reading the 'install' section, 'i' would be the proper response here... 2. Entering the installer ========================= The installer starts with a nice welcome messages. Read this message carefully, it also informs you of the risks involved in continueiNg! If you still want to go on, type 'y'. The installer now continues by trying to figure out your disk configuration. Ignore the error: kern_fs_get_rrootdev: no raw root device When it is done, you will be prompted to select a root device from the list of disks it has found. 3. Select your root device ========================== You should know at this point that the disks are NOT numbered according to their scsi-id! The NetBSD kernel numbers the scsi drives (and other devices on the scsi bus) sequentially as it finds them. The drive with the lowest scsi id will be called sd0, the next one sd1, etc. Where you end up after the selection of the root disk depends on the contents of your disk. If it is already partitioned using AHDI, start reading at item 4a, if this disk has no AHDI partitioning but is blank or used by another non-AHDI system, start at item 4b. YOU ARE NOW AT THE POINT OF NO RETURN! The programs in section 4 will modify your harddisk. Type Control-C NOW if you don't want this. 4a. Setting AHDI partition id's on your root disk (using edahdi) ================================================================ Because NetBSD imposes a special ordering in disk partitions it uses for root & swap. And because it wants to guard you against an unwanted demolition of partitions used by other systems, you have to tell it what partitions it is allowed to use. You have to mark the partition you want to use as swap 'NBS' or 'SWP' and the other partitions as 'NBD'. Note that all the changes you make to the id's are reversable as long as you remember the original value. In the partition-id editor, the partitions are shown in the order that AHDI created them. When you leave this editor and continue at item 4b, your changes to the id's do have consequences to the partition order! They will show up as follows: a -- the first NBD partition b -- the first NBS partition d (and up) -- the rest of the partitions in AHDI order 4b. Labeling your root disk (using edlabel) =========================================== You are now allowed to change the partitioning of your disk. If your disk is already partitioned with AHDI DON'T change anything unless you are absolutely sure what you are doing! If you are labeling an empty SCSI disk, you can make life easy for yourself by selecting 'standarize geometry'. This allows you to select a 'sectors per track' and 'tracks/cylinder' value and have the (fictious) SCSI geometry changed accordingly. So if you select 64 sect/track and 32 tracks/cylinder, each cilinder is exactly 1Mb in size. Well, go ahead and don't forget to save your work before quitting! NOTE: to make sure that NetBSD can create/mount filesystems on the partitions you defined, make sure the 'type' is entered correctly: 4.2BSD - filesystems created by NetBSD MSDOS - filesystems shared with GEM Just ignore it, it's harmless. 5. Label additional disks ========================= Now that your root-disk is labeled, you are given the opportunity to label any of the other disks in your system. The procedure is the same as with your root disk. 6. Setup the fstab ================== Since all disks you want to use with NetBSD are properly labeled, it is time to tell the installer which partition will be associated with the different filesystems. As mentioned above, it is wise to make at least a separate root and /usr filesystem. Depending on what you are planning to do with your system, you might also consider to make a separate /var, /local or /home. When you tell the installer that all of your filesystems are specified correctly, it starts creating them for you. 7. Configure your network ========================= Don't do this right now. As non of the network cards are supported, it doesn't make any sense. 8. Edit the fstab - again.... ============================= Since the network configuration might have lead to additional (nfs) filesystem entries, you get another chance to modify your fstab. 9. Installing the distribution sets =================================== Your are finally at the point where some real data will be put on your freshly made filesystems. Select the device type you whish to install from and off you go.... Some notes: - If you want to install from tape, please read the section about how to create such a tape. - If you want to install from a gemdos filesystem, you should rename the distribution sets because of the nameing limitations on gemdos. Move all 'xxx.tar.gz' sets to 'xxx.tgz'. The installer will handle the rest. - Install at least the base and etc sets. - If you have to specify a path relative to the mount-point and you need the mount-point itself, enter '.'. 10. Timezone selection and device-node building =============================================== The isn't much to say about this. Just select the timezone you are in. The installer will make the correct setup on your root filesystem. After the timezone-link is installed, the installer will proceed by creating the device nodes on your root filesystem. Be patient, this will take a while... 11. Installing the kernel ========================= Because the kernel didn't fit on the install-disks, the installer asks you about the disk you're kernel is on. You can specify the same disks as with the installation of the sets with the addition of 'fd0'. The latter can be used when you decide to install the kernel from the kernel-floppy. 12. Installing the bootstrap ============================ Finally, the installer ask you if you want to install the bootblock code on your root disk. This is a matter of personal choise and can also be done from a running NetBSD system. See the 'installboot(8)' manual page about how to do this. 13. You did it! =============== Congratulations, you just installed NetBSD successfully! If you also installed a bootblock, you only have to reboot your atari to enter your freshly build system. If you didn't, get back to section 1 (How to boot the miniroot). Just substitute 'rd0' by your NetBSD root disk. Some extra remarks: =================== If you don't want to use the bootloader. You could use the following setup: Reserve a small GEMDOS partition of about 4Mb. This is enough to put in a few kernels. Put the netbsd kernel into this partition. Also, edit your /etc/fstab to always mount this partition, say as /kernels. Now make a symlink from /netbsd to /kernels/netbsd. This sceme is particulary handy when you want to make your own kernel. When compilation is finished, you just copy your kernel to /kernels/netbsd and reboot. It's wise to make sure there is _always_ a 'known to work' kernel image present. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ Before updating, you probably would want to backup your original filesystems! The update procedure will not overwrite or remove any files not present in the sets you install. If you've replaced programs present in the distribution, you have to replace them again after you did the update. The etc-set needs special caution. You generally don't want to install this one when upgrading. It is recommended that you get a copy of this set and _carefully_ upgrade your configuration files by hand. 1. Starting the upgrade ======================= Ok, let's go. Insert the bootfloppy and follow the 'normal' installation procedure until it asks you if you wish to install or upgrade. At this time, select upgrade. You will now be greeted and reminded of the fact that this is a potential dangerous procedure and that you should not upgrade the etc-set. 2. Selecting your root disk =========================== When you decide to proceed, you will be prompted to enter your root disk. After you've done this, it will be checked automatically to make sure that the filesystem is in a sane state before making any modifications. After this is done, you will be asked if you want to configure your network. You can skip this section on NetBSD/Atari for now. 3. Editing the fstab ==================== You are now allowed to edit your fstab. Normally you don't have to. Note that the upgrade-kit uses it's own copy of the fstab. Whatever you do here *won't* affect your actual fstab. After you are satisfied with your fstab, the upgrade-kit will check all filesystems mentioned in it. When they're ok, they will be mounted. 4. The actual upgrade ===================== You will now be asked if your sets are stored on a normally mounted filesystem. You should answer 'y' to this question if you have the sets stored on a filesystem that was present in the fstab. The actions you should take for the set extraction are pretty logical (I think). You might want to read the notes in section 9 (Installing the distribution sets) of the installation section. 5. Finishing up =============== After you have extracted the sets, the upgrade kit will proceed with setting the timezone and installing the kernel and bootcode. This is all exactly the same as described in the installation section. 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 (1) 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 (1) 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 Gordon Ross This product includes software developed by Leo Weppelman. This product includes software developed by Markus Wild. This product includes software developed by Thomas Gerner This product includes software developed by Waldi Ravens.