INSTALLATION NOTES for NetBSD/atari 1.3 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 derived 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 NetBSD 1.3 release is a landmark. Building upon the successful NetBSD 1.2 release, we have provided numerous and significant functional enhancements, including support for many new devices, integration of many bug fixes, new and updated kernel subsystems, and many userland enhancements. The results of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to summarize the 18 months of development that went into the NetBSD 1.3 release. Some of the significant changes include: Support for machine independent device drivers has been radically improved with the addition of the "bus.h" interface, providing a high quality abstraction for machine and architecture independent device access. The bus_dma interface has also been integrated, providing a machine-independent abstraction for DMA mapping. This permits many good things, including (among many) clean multi-platform bounce buffer support. Framework support for ISA "Plug and Play" has been added, as well as support for numerous "Plug and Play" devices. APM support has been added to NetBSD/i386. An initial cut of multi-platform PCMCIA support has been added. Support for ATAPI devices (initially just ATAPI CD-ROM drives) has been added. Support for Sun 3/80s (sun3x architecture) has been added. Support for R4000 DECstations has been added. Integration/merger of 4.4BSD Lite-2 sources into userland programs has nearly been completed. Most of userland now compiles with high levels of gcc warnings turned on, which has lead to the discovery and elimination of many bugs. The i386 boot blocks have been completely replaced with a new, libsa based two stage boot system. This has permitted integration of compressed boot support (see below). Many ports now support booting of compressed kernels, and feature new "Single Floppy" install systems that boot compressed install kernels and ramdisks. We intend to do substantial work on improving ease of installation in the future. "ypserv" has been added, thus completing our support for the "yp" network information system suite. Support for the Linux "ext2fs" filesystem and for FAT32 "msdosfs" filesystems has been added. TCP now has a SYN "compressed state engine" which provides increased robustness under high levels of received SYNs (as in the case of "SYN flood" attacks.) (Much of this code was derived from sources provided by BSDI.) An initial implementation of Path MTU discovery has been integrated (though it is not turned on by default). An initial kernel based random number generator pseudodevice has been added. Several major fixes have been integrated for the VM subsystem, including the fix of a notorious VM leak, improved synchronization between mmap()ed and open()ed files, and massively improved performance in low real memory conditions. A new swap subsystem has radically improved configuration and management of swap devices and adds swapping to files. Userland ntp support, including xntpd, has been integrated. The audio subsystems have been substantially debugged and improved, and now offer substantial emulation of the OSS audio interface, thus providing the ability to cleanly run emulated Linux and FreeBSD versions of sound intensive programs. A "packages" system has been adapted from FreeBSD and will provide binary package installations for third party applications. The XFree86 X source tree has been made a supported part of the NetBSD distribution, and X servers (if built for this port), libraries and utilities are now shipped with our releases. The ftp(1) program has been made astoundingly overfunctional. It supports command line editing, tab completion, status bars, automatic download of URLs specified on the command line, firewall support and many other features. All ports now use "new" config. Old config has been laid to rest. The ARP subsystem and API has been rewritten to make it less ethernet-centric. A new if_media subsystem has been added which allows network interfaces to be configured using media type names rather than device-specific mode bits. Many kernel interface manual pages have been added to manual section 9. Several ports support much more hardware. Many updates to bring NetBSD closer to standards compliance. Most third party packages have been updated to the latest stable release. As has been noted, there have also been innumerable bug fixes. 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.3 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. In the near future, we hope to integrate a fully rewritten Virtual Memory subsystem, kernel threads, and SMP support. The Atari release stepped in in March 1995. The first official release was NetBSD1.1. About a year later, NetBSD1.2 was released for the Atari. This release fixed a large number of bugs and made the Atari-port a stable member of the NetBSD family. And now, finally, a NetBSD1.3 release is available! This release adds support for a brand new atari-compatible platform: The Hades. Both the 040 and 060 flavours are supported, unfortunately only the et4000-PCI console is currently supported. Also new in this release is the ethernet support for the TT030 by means of a Riebl driver and the IDE support for the Falcon. 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 22, 1997 If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. FTP mirrors ----------- Australia * ftp://ftp.au.netbsd.org/pub/NetBSD Brazil * ftp://ftp.ravel.ufrj.br/pub/NetBSD Germany * ftp://ftp.de.netbsd.org/pub/NetBSD * ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD Japan * ftp://netbsd.tohoku.ac.jp/NetBSD Netherlands * ftp://ftp.nl.netbsd.org/pub/comp/NetBSD Norway * ftp://ftp.ntnu.no/pub/NetBSD * ftp://skarven.itea.ntnu.no/pub/NetBSD Sweden * ftp://ftp.stacken.kth.se/pub/OS/NetBSD * ftp://ftp.sunet.se/pub/os/NetBSD UK * ftp://ftp.DOMINO.ORG/pub/NetBSD USA * ftp://ftp.netbsd.org/pub/NetBSD * ftp://ftp.cs.umn.edu/pub/NetBSD * ftp://ftp.cslab.vt.edu/pub/NetBSD * ftp://ftp.eecs.umich.edu/pub/NetBSD * ftp://ftp.iastate.edu/pub/netbsd * ftp://ftp.op.net/pub/NetBSD SUP mirrors ----------- Australia * ftp.au.netbsd.org Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup Germany * ftp.de.netbsd.org Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example Norway * skarven.itea.ntnu.no Instructions: 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 UK * ftp.domino.org Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup USA * sup.netbsd.org Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup * ftp.cs.umn.edu Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG AFS mirrors ----------- USA * ftp.iastate.edu AFS path: /afs/iastate.edu/public/ftp/pub/netbsd NetBSD 1.3 Release Contents: ------ --- ------- -------- The NetBSD 1.3 release is organized in the following way: .../NetBSD-1.3/ 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.3 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 for which NetBSD 1.3 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. 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: secrsrc.tgz: This set contains the "domestic" sources. These sources may be subject to United States export regulations. [ 412K gzipped, 1.8M uncompressed ] gnusrc.tgz: This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 15.6M gzipped, 66.4M uncompressed ] syssrc.tgz: This set contains the sources to the NetBSD 1.3 kernel, config(8), and dbsym(8). [ 10.7M gzipped, 50.0M uncompressed ] sharesrc.tgz: 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.9M gzipped, 11.1M uncompressed ] src.tgz: This set contains all of the NetBSD 1.3 sources which are not mentioned above. [ 13.9M gzipped, 60.7M 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. Most of the above source sets are located in the source/sets subdirectory of the distribution tree. The secrsrc.tgz set is contained in the source/security subdirectory. This set, which is available only to users in the United States and Canada, contains the sources normally found in /usr/src/domestic -- primarily kerberos and other cryptographic security related software. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada.) The source sets are distributed as compressed tar files. They may be unpacked into /usr/src with the command: cat set_name.tgz | gunzip | (cd /; tar xpf - ) The sets/Split/ and security/Split/ subdirectories contain split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are are 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.) The split distributions may be reassembled and extracted with "cat" as follows: cat set_name.?? | gunzip | (cd /; tar xpf - ) 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. Checksums based on other algorithms may also be present -- see the release(7) man page for details. The Atari-specific portion of the NetBSD 1.3 release is found in the "atari" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.3/atari/ SOURCE_DATE the date, in the default format produced by the date(1) command, of the source that the release was built from INSTALL these installation notes binary/ atari system binaries; see below. installation/ installation helper items The NetBSD/atari system binaries include the NetBSD/atari binary distribution sets, additional kernels, and security-related system binaries. The NetBSD 1.3 release for the atari port comprises those files found in the "atari/binary/sets" subdirectory of the NetBSD 1.3 distribution tree. There are seven system distribution sets, two kernel distribution sets, and four X distribution sets. The files in the "sets" subdirectory are as follows: base.tgz The NetBSD/atari 1.3 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. [ 8.6M gzipped, 25.1M uncompressed ] comp.tgz The NetBSD/atari Compiler tools; all of the tools relating to C and C++. 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. [ 6.2M gzipped, 21.6M uncompressed ] etc.tgz 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.) [ 49K gzipped, 288K uncompressed ] games.tgz This set includes the games and their manual pages. [ 2.8M gzipped, 7.2M uncompressed ] kern.tgz The NetBSD/atari 1.3 kernel binary. You should kern_hades.tgz install the appropriate kernel for your system. kern_x.tgz [ 472K gzipped, 1.01M uncompressed ] man.tgz 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. [ 2.2M gzipped, 8.8M uncompressed ] misc.tgz 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. [ 2.1M gzipped, 7.6M uncompressed ] text.tgz This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1.0M gzipped, 3.7M uncompressed ] xbase.tgz X clients, shared libraries, and related man pages. Also includes bitmaps and miscellaneous configuration files. [ 2.34 M gzipped, 7.46M uncompressed ] xcomp.tgz Static libraries, include files (except bitmaps), X config files (for xmkmf), and related man pages. [ 1.57M gzipped, 6.38M uncompressed ] xcontrib.tgz User-contributed X binaries (e.g. xev, xload) built from the X11 "contrib" sources with man pages and default config files. [ 178K gzipped, 661K uncompressed ] xfont.tgz X11 fonts. [ 5.66M gzipped, 6.99M uncompressed ] [* Note: an X server distribution set is currently not available.] The NetBSD/atari security distribution set is named "secr.tgz" and can be found in the "atari/binary/security" subdirectory of the NetBSD 1.3 distribution tree. It contains the crypt libraries (for the DES encryption algorithm) and the binaries built from the "src/domestic" portion of the NetBSD source tree 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, it may not be legal to distribute this set to locations outside of the United States and Canada.) [ 779K gzipped, 2.5M uncompressed ] The atari binary distribution sets are distributed as full .tar.gz files (with the extension .tgz because the software used to download the sets may incorrectly auto-unpack files ending in .gz and to accomodate systems which only support 3 character extensions to file names). 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 xvpf" 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. Additional kernels to those included in the distribution sets may be found in the "atari/binary/kernel" subdirectory of the NetBSD 1.3 distribution tree. These kernels are generally named something like "netbsd.BOOT.gz" or some other suitable name. Please note that these kernels are simply gzipped and are not in tar archives. There are three atari floppy images to be found in the "atari/installation/floppies" subdirectory of the NetBSD 1.3 distribution. One of them is a bootable TOS kernel floppy and the other two are installation floppies. 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_pid programs and a kernel. It is setup so that you can insert it int your floppy drive, and start the programs from GEM. For the TT030 and Falcon, the floppy is named boot-13.fs and the kernel supplied is 'BOOT'. For the Hades, you need the hades-boot-13.fs floppy. The kernel is 'HADES'. 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 GEMDOS partitions. These floppies are named "miniroot.fs.1" and "miniroot.fs.2". There are also TOS utilities in the "atari/installation/misc" subdirectory, which you will need to get NetBSD/Atari 'up-and-running'. The "gzip.ttp" program allows you to uncompress .gz images. The usage is "gzip.ttp -d filename.gz". The "rawwrite.ttp" program allows you to create the installation floppy disks from the files in the "atari/floppies" directory. The "aptck.ttp" program reads the partition tables present on a given disk and tries to interpret then the same way the NetBSD kernel does. If you have a disk on which GEMDOS and NetBSD are to co-exist, It is a good idea to run this before you begin the NetBSD/Atari installation just to check that the kernel's view of the partition tables agree with GEMDOS's view. If you have more than 3 partitions defined on a disk you will notice that the NetBSD/Atari partition starts one sector after the GEMDOS partition. This is to allow space for the auxilliary root for the 4th and subsequent partitions. The "loadbsd.ttp" program loads the NetBSD/Atari kernel from TOS (or MiNT, MultiTOS, etc.). Note: Each directory in the atari binary distribution also has its ----- own checksum files, just as the source distribution does: All BSDSUM files are historic BSD checksums for the various files in that directory, in the format produced by the command: cksum -o 1 . All CKSUM files are POSIX checksums for the various files in that directory, in the format produced by the command: cksum . All MD5 files are MD5 digests for the various files in that directory, in the format produced by the command: cksum -m . All SYSVSUM files are historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command: cksum -o 2 . The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/atari 1.3 runs on a TT030, Falcon and Hades. An FPU is not required. The minimum amount of RAM required is 4Mb. On the Hades, only the et4000-PCI card is supported in the 1.3 release. When another video card is present, you can use NetBSD only with a serial console. 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) 95M 125M 75M 105M swap ----- 2M for every M ram ----- local (/local) up to you In addition of the rule of thumb for the swap size mentioned below, you probably want to make sure that the size of the swap partition does not drop below 20Mb (30Mb for systems with X). 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 builtin 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, TANDBERG 3800 - Should support most CD-ROM drives. - Should support most ZIP/MO drives. - The builtin video controller - The builtin (720Kb/1.44Mb) floppydrive - The serial2/modem2 ports - The Falcon FX memory expansion - The atari mouse - A 3-button mouse - The parallel printer - Riebl (and possibly PAM) ethernet cards on the VME bus. - IDE interface on both Falcon and Hades - The serial interface on the first 68901 UART (modem1) - ET4000-PCI (VGA) on the Hades. If it's not on this list, there is 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 "installation/floppies" under the root of the NetBSD/atari 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. As an example, to write the first part of the miniroot filesystem onto a 720KB floppy in fd0 use: dd if=miniroot.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.fs This will create the boot-floppy on the floppy in drive a. The floppies should be pre-formatted on 720Kb/1.44Mb 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. Since the 1.3 release, it is also possible to use HD-floppies. You should than use the floppy device '/dev/rfd0c' or add the '-H' flag to 'rawwrite'. 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. 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.3/atari/binary/sets T= mt -f $T rewind for f in base etc comp games man misc text dd if=$f.tgz 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 a disk of it's own, you can delay the partitioning until the installer requests you to do it. This means that you can safely skip the rest of this section. 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 you want to use an AHDI partitioning sceme and you want to be able to boot directly into NetBSD, there are some constraints on the partition layout. As you might know; every hard disk has a "root sector" that contains information about the size of the hard disk and the partitions on the hard disk. The root sector can only contain the neccessary data for four partitions. Nobody thought that this limitation would cause any problems. After all, 640 KByte should be enough. As hard disk grew, it was neccessary to define more than four partitions. In order to be more or less compatible with the old format, a new type of partition entry was defined: XGM partions. An XGM partition is a "look over there" sign: Another root sector can be found at the start of the XGM partition. This root sector contains the remaining real partitions. And this is the big mystery: Partitions defined in the root sector of the hard disk are called "primary partitions", partitions defined in the root sector of an XGM partition are called "extended partitions". The bootblock will only work if the first NBD partition is a primary partition. This is not a limitation of NetBSD but a limitation of TOS/AHDI: You can only boot from primary partitions. If you are creating your partitions with HDX, you'll have to be very careful to fulfill this rule. HDX has some very strange ideas when it comes to extended partitions. Fortunately, you can edit this stuff: The "Edit partition scheme of the unit" dialog box has a button label "expert". This button is inactive unless you have defined more than four partitions. Click on it *after* you have defined the sizes of the partitions. A new dialog box appears on the screen. The left side contains two blocks of partitions: The upper block always contains the first four partitions, the lower block contains the last three partitions. If you have defined less than 7 partitions, some fields of the lower block will contain the string "unused". Some of the partitions will be displayed in reverse video: These are the extended partitions. The right side contains six possible ranges for the extended partitions. It is not possible to define your own range, you will have to use one of the schemes offered by HDX. To quote from Ghostbusters: Choose and die. The default scheme used by HDX is the first scheme: Extended partitions start with the second partition and end with the second to last partition. If you have defined 7 partitions, partitions #2 to #5 will be extended partitions, while partitions #1, #6 and #7 will be primary partitions. You can move the extended partition range by clicking on one of the buttons on the right side of the dalog box. Try to find one where your first NetBSD partition is a primary partition. Golden rules: * If the disk contains no GEMDOS partitions, don't use AHDI. Let NetBSD handle it alone. * If the disk contains one GEMDOS partition, make it partition #1 and start the extended partition range at partition #3. This allows you to boot from both the GEMDOS and the NetBSD partitions. * If the disk contains two GEMDOS partitions, use partitions #1 and #2 for GEMDOS, partition #3 for NetBSD-root. Start the extended partition range with partition #4. * If your disks contains three or more GEMDOS partitions, you are in trouble. Try using partitions #1 and #2 as the first two GEMDOS partitions. Use partition #3 as the first NetBSD partition. Start the extended partition range with partition #4. Put the other NetBSD extended partition range. Good luck, you'll need 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 need either the bootfloppy provided in the distribution or you can copy the loadbsd.ttp program and kernel to a boot floppy disk (1.4M needed) or put them on a TOS partition. Select the loadbsd program and it will ask for parameters, supply: '-b netbsd' (or whatever name you copied the kernel to). 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 `md0a' 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. Note: If you are using 1.44Mb floppies, you should select 'md1a' instead of 'md0a'. 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 continuing! If you still want to go on, type 'y'. The installer now continues by trying to figure out your disk configuration. 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 =================================== You 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. The tape device name will be "nrst0" for the first tape drive, "nrst1" for the second, etc. - 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 '.'. - For previous NetBSD users: If you want to install from a GEMDOS filesystem, you don't need to rename the distribution sets as you may have done in previous versions of NetBSD. 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 your kernel is on. You can specify the floppy with disk 'fd0' and partition 'b' for 720K disks and partition 'c' for 1.4M disks, or one of the hard disk partitions. 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 'md0a' 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. Compatibility Issues With Previous NetBSD Releases: ------------- ------ ---- -------- ------ -------- Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.3: * Swap configuration Description: All swap partitions are now configured by the swapctl(8) program. The kernel no longer configures a "default" swap partition. Because of this, all swap partitions (even the old "default") must be listed in /etc/fstab. Many users of previous releases relied on the kernel configuring a "default" swap partition and did not list any swap space in /etc/fstab at all -- such users will now have no swap space configured unless they list swap partitions in /etc/fstab! Common symptoms of of this problem include machine crashes during builds, and similar memory intensive activities. Fix: The most common position for a swap partition is the `b' partition of the drive the root file system is on. For diskless systems, check the new swapctl(8) manual for more detail on how this is done. Example fstab entries: /dev/sd0b none swap sw,priority=0 /dev/sd1b none swap sw,priority=5 * NFS daemons and other programs in /sbin moved Description: The NFS daemons (nfsd, nfsiod, mountd) have been moved from the /sbin to the /usr/sbin directory. When new binaries are loaded over old ones during upgrade, most programs get overlaid and replaced, but unless these binaries are explicitly removed they will not disappear. The installation subsystems on some NetBSD architectures will not properly remove these binaries. Due to changes in the NFS subsystem, the old NFS daemon binaries will not work correctly, and will cause serious problems. Unfortunately, the default startup script (/etc/rc) will run the old binaries in /sbin if they are present instead of the new ones in /usr/sbin. Some other programs (dumpfs, dumplfs and quotacheck) have also been moved from /sbin to /usr/sbin, and old versions may be left behind by accident. They, too, may cause difficulties. Fix: Remove the old daemon binaries (/sbin/nfsiod, /sbin/nfsd, /sbin/mountd, etc.) after your upgrade has finished. You may wish to do an "ls -lt /sbin | more" to help determine which binaries were not replaced/removed during your upgrade. * AMANDA, The Advanced Maryland Automatic Network Disk Archiver, from http://www.amanda.org Description: Due to a change in the output of dump(8) to ensure consistency in the messages, AMANDA's dump output parser breaks. Error messages such as the following may be an indication that this problem is present: FAILURE AND STRANGE DUMP SUMMARY: hostname wd0e lev 1 FAILED [no backup size line] Versions affected: 2.3.0.4, and most likely earlier versions Workaround/Fix: One of: * Apply the patch found at: ftp://ftp.netbsd.org/pub/NetBSD/misc/patches/amanda-pre-2.4.patch * Upgrade to AMANDA 2.4.0 or newer. The side effect of this is that the network protocol is incompatible with earlier versions. 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: ------------- 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. 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 David Brownlee Simon Burge Dave Burgess Ralph Campbell Canada Connect Corporation Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Demon Internet, UK Easynet, UK Scott Ellis Free Hardware Foundation Greg Gingerich Michael L. Hitch Innovation Development Enterprises of America Scott Kaplan Chris Legrow Neil J. McRae Perry E. Metzger MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center 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): Mark Brinicombe (arm32) Jeremy Cooper (sun3x) Chuck Cranor (mvme68k) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Anders Magnusson (vax) Phil Nelson (pc532) Masaru Oki (x68k) Scott Reynolds (mac68k) Gordon Ross (sun3, sun3x) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (i386) Leo Weppelman (atari) The NetBSD 1.3 Release Engineering team: Ted Lemon Perry Metzger Jason Thorpe Supporting cast: Steve Allen Lennart Augustsson Christoph Badura John Birrell Manuel Bouyer John Brezak Allen Briggs Aaron Brown David Brownlee Simon Burge Dave Burgess Dave Carrel Bill Coldwell Alistair Crooks Rob Deker Chris G. Demetriou Matthias Drochner Bernd Ernesti Erik Fair Hubert Feyrer Brian R. Gaeke Justin Gibbs Adam Glass Michael Graff Brad Grantham Matthew Green Juergen Hannken-Illjes Michael L. Hitch Marc Horowitz Matthew Jacob Lonhyn T. Jasinskyj Lawrence Kesteloot Klaus Klein John Kohl Kevin Lahey Ted Lemon Mike Long Paul Mackerras SAITOH Masanobu Neil J. McRae Perry Metzger Luke Mewburn der Mouse Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Darren Reed Kazuki Sakamoto Curt Sampson Wilfredo Sanchez Karl Schilke (rAT) Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Bill Sommerfeld Ignatios Souvatzis Bill Studenmund Kevin Sullivan Matt Thomas Enami Tsugutomo Todd Vierling Paul Vixie Colin Wood Steve Woodford Dedication: ---------- The Release Engineering team would like to dedicate the NetBSD 1.3 release to the memory of the late Koji Imada, who was killed in a motorcycle accident in August, 1997 at the age of 28. A doctoral student in Mathematical Science at Nagoya University, he was a user of NetBSD and a contributor to the project since 1993. Well remembered by his friends, he was also known as a connoisseur of gins, teas, and the motorcycles he loved to ride. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace. 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 Adam Glass and Charles Hannum. This product includes software developed by Adam Glass. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Charles D. Cranor and Washington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Weppelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Herb Peyerl. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Mark Brinicombe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by the Center for Software Science at the University of Utah. This product includes software developed by the University of Calgary Department of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Consortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. 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.