home *** CD-ROM | disk | FTP | other *** search
Text File | 1995-03-08 | 37.3 KB | 1,085 lines |
- INSTALLATION NOTES for NetBSD/amiga 1.0
-
-
-
- Be sure to read _ALL_ of this document before you try to install
- NetBSD/amiga.
-
-
-
- What is NetBSD?
- ---- -- ------
-
- NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite
- -derived system. It is a fully functional UN*X-like system which runs
- on several architectures and is being ported to more. NetBSD, as the
- name implies, is a creation of the members of the network community
- and without the net it's likely that this release wouldn't have come
- about.
-
- NetBSD 1.0 is a milestone release. The hardest part of the 4.4BSD-Lite
- integration, the kernel, has been completed and has been running in
- "production use" for quite some time. Also, NetBSD 1.0 is the first
- true multi-architecture release of NetBSD. At the time of NetBSD 0.9,
- the i386 port was considered 'production quality' and the hp300 port was
- barely working. The NetBSD 1.0 source supports nine architectures, and
- complete binary releases for most of them will be made available.
-
- NetBSD 1.0 supports many new and improved features, the most important
- relating to file systems. New and improved versions of both the
- Berkeley Fast File System and the free implementation of the NFS
- protocol were provided, as part of the 4.4-Lite release. The new
- versions include such improvements as support for 64-bit file sizes,
- for local files, and "lease" support for NFS, to improve performance.
- In addition to the file system improvements, many other parts of the
- system have been improved considerably. For instance, the virtual
- memory code has substantially improved performance, and many of the
- kernel's interfaces have been cleaned up.
-
- Many new user programs have been added in NetBSD 1.0, as well,
- bringing it closer to our goal of supplying a complete UN*X-like
- environment. Additionally, support for shared libraries has been
- added, for most architectures, allowing a significant savings in both
- RAM consumption and disk space.
-
- This is the first public release of NetBSD for the Amiga line of
- computers.
-
-
-
- The Future of NetBSD:
- --- ------ -- ------
-
- 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 or nearly-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. This includes integrating the remainder of
- the 4.4BSD-Lite tape, as quickly as we can ensure that everything works
- properly.
-
- 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:
- ------- -- ------
-
- Host name Services Provided
- ---- ---- -------- --------
- ftp.iastate.edu Anonymous FTP, AFS
-
- Anon-FTP path: pub/netbsd/NetBSD-1.0
- AFS path: /afs/iastate.edu/public/ftp/pub/netbsd/NetBSD-1.0
-
- ftp.eecs.umich.edu Anonymous FTP
-
- Anon-FTP path: BSD/NetBSD/NetBSD-1.0
-
- gatekeeper.dec.com Anonymous FTP
-
- Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0
-
- wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP
-
- Anon-FTP path: pub/NetBSD/NetBSD-1.0
- SUP: get the file pub/misc/sup/supfile.example via
- anonymous FTP and read it as an example.
-
- ftp.demon.co.uk Anonymous FTP, possibly SUP
-
- Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0
- SUP: contact peter@demon.net for SUP server status/information
-
- ftp.uni-regensburg.de Anonymous FTP
-
- Anon-FTP path: pub/NetBSD/NetBSD-1.0
-
- ftp.unit.no Anonymous FTP
-
- Anon-FTP path: pub/NetBSD/NetBSD-1.0
-
- ftp.stacken.kth.se Anonymous FTP
-
- Anon-FTP path: pub/OS/NetBSD/NetBSD-1.0
-
- flick.lerc.nasa.gov Anonymous FTP
-
- Anon-FTP path: pub/NetBSD/NetBSD-1.0
-
- coombs.anu.edu.au Anonymous FTP
-
- Anon-FTP path: pub/NetBSD/NetBSD-1.0
-
- ftp.netbsd.org Anonymous FTP, SUP
-
- Anon-FTP path: pub/NetBSD/NetBSD-1.0
- SUP: get the file pub/sup/README.sup via anonymous FTP from
- ftp.netbsd.org, and read it for instructions.
-
- If you wish to become a distribution site for NetBSD, contact Chris
- Demetriou <cgd@NetBSD.ORG>.
-
-
- NetBSD 1.0 Release Contents:
- ------ --- ------- --------
-
- The NetBSD 1.0 release is organized in the following way:
-
- .../NetBSD-1.0/
- 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.0 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.0 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, excluding those portions which should
- not be exported from the U.S. (Those are contained in each
- architecture's "security" binary distribution set.) The source
- distribution sets are as follows:
-
- gsrc10 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.7M gzipped, 32.0M uncompressed ]
-
- ksrc10 This set contains the sources to the NetBSD 1.0
- kernel, config(8), config.new(8) and dbsym(8).
- [ 4.5M gzipped, 20.8M uncompressed ]
-
- ssrc10 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.3M gzipped, 8.5M uncompressed ]
-
- src10 This set contains all of the NetBSD 1.0 sources which
- are not mentioned above.
- [ 7.1M gzipped, 33.4M uncompressed ]
-
- It is worth noting that unless all of the source distribution sets
- are installed, 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) command. 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 amiga-specific portion of the NetBSD 1.0 release is found in the
- "amiga" subdirectory of the distribution. That subdirectory is layed
- out as follows:
-
- .../NetBSD-1.0/amiga/
- binary/ amiga binary distribution sets;
- see below.
-
- floppies/ amiga boot and installation
- floppies; see below.
-
- security/ amiga security distribution;
- see below;
-
- utils/ Miscellaneous amiga
- installation utilities; see
- installation section, below.
-
- There are two amiga floppy images to be found in the "amiga/floppy"
- subdirectory of the NetBSD 1.0 distribution. One of them is a
- bootable AmigaDOS kernel floppy and one is an installation floppy.
- 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 AmigaDOS disk contains the loadbsd boot program and
- the GENERIC kernel. It is setup so that you can insert it
- int your floppy drive, reboot the system and boot netbsd.
-
- This floppy is named boot-10.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 AmigaDOS partitions.
-
- This floppy is named "inst-10.fs".
-
- The NetBSD/amiga binary distribution sets contain the binaries which
- comprise the NetBSD 1.0 release for the amiga. There are seven binary
- distribution sets, and the "security" distribution set. The binary
- distribution sets can be found in subdirectories of the "amiga/binary"
- subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
-
- base10 The NetBSD/amiga 1.0 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.
- [ 7M gzipped, 19M uncompressed ]
-
- comp10 The NetBSD/amiga Compiler tools. All of the tools
- relating to C, C++, and FORTRAN (yes, there are two!).
- This set includes the system include files
- (/usr/include), the linker, the compiler tool chain,
- and the various system libraries (except the shared
- libraries, which are included as part of the base
- set). This set also includes the manual pages for all
- of the utilities it contains, as well as the system
- call and library manual pages.
- [ 4M gzipped, 12M uncompressed ]
-
- etc10 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.)
- [ 50K gzipped, 280K uncompressed ]
-
- games10 This set includes the games and their manual pages.
- [ 1M gzipped, 3M uncompressed ]
-
- man10 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.
- [ 730K gzipped, 3M uncompressed ]
-
- misc10 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, 6M uncompressed ]
-
- text10 This set includes NetBSD's text processing tools,
- including groff, all related programs, and their
- manual pages.
- [ 784K gzipped, 3M uncompressed ]
-
- The amiga security distribution set is named "secr10" and can be found
- in the "amiga/security" subdirectory of the NetBSD 1.0 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 amiga binary distribution sets are distributed in the same form as
- the source distribution sets; catted together, the members of a set
- form a gzipped tar file. Each amiga binary distribution set also has
- its own "CKSUMS" file, just as the source distribution sets do.
-
- The instructions given for extracting the source sets work equally
- well for the binary sets, but it is worth noting that if you use that
- method, the files are extracted "below" the current directory. That
- is, if you want to extract the binaries "into" your system, i.e.
- replace the system binaries with them, you have to run the "tar xvfp"
- from /. Also note that if you upgrade or install this way, those
- programs that you are using at the time will NOT be replaced. If you
- follow the normal installation or upgrade procedures, this will be
- taken care of for you.
-
-
-
- NetBSD System Requirements and Supported Devices:
- ------ ------ ------------ --- --------- -------
-
- NetBSD/amiga 1.0 runs on any amiga that has a 68020 or better CPU
- with some form of FPU and MMU. The minimal configuration requires
- 4M of RAM and about 65M of disk space. To install the entire system
- requires much more disk space, and to run X or compile the system,
- more RAM is recommended. (4M of RAM will actually allow you to
- compile, however it won't be speedy. X really isn't usable on a
- 4M system)
-
- Here is a table of recommended HD partition sizes for a full install:
- partition: advise, with X, needed, with X
- root (/) 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).
-
- Supported devices include:
- A4000/A1200 IDE controller.
- SCSI host adapters:
- 33c93 based boards: A2091, A3000 and GVP series II.
- 53c80 based boards: 12 Gauge, IVS and Wordsync.
- 53c710 based boards: A4091, Magnum, Warp Engine and Zeus.
- Video controllers:
- ECS, AGA and A2024 built in on various amigas.
- Retina Z2 and Retina Z3.
- Ethernet controllers:
- A2065 Ethernet
- Hydra Ethernet
- Tape drives:
- Most SCSI tape drives, including
- Archive Viper, Cipher SCSI-2 ST150.
- CD-ROM drives:
- Most SCSI CD-ROM drives
- Amiga floppy drives.
- Amiga parallel port.
- Amiga serial port.
- Amiga mouse.
-
- If its 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:
- AmigaDOS HD partitions
- Tape
- NFS partitions
- FTP
-
- No matter what you do, however, you'll need to have one disk handy,
- on which you will put the install floppy image.
-
- All the images are available from the directory "amiga/floppies",
- under the root of the NetBSD tree at your favorite archive site.
-
- If you are using NetBSD/amiga 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=inst-10.fs of=/dev/rfd0a bs=11b
-
- If you are using AmigaDOS to make the floppies, you should
- use the rawwrite utility, provided in the directory
- "amiga/utilities" in the distribution. To write the image to
- the floppy in df0 use (from cli):
-
- rawwrite 0 inst-10.fs
-
- The steps necessary to prepare the distribution sets
- for installation depend on which method of installation
- you choose. The various methods are explained below.
-
- To prepare for installing via an AmigaDOS partition:
-
- To install NetBSD from an AmigaDOS partition, you need to
- get the NetBSD distribution sets you wish to install
- on your system on to an AmigaDOS partition. All of the
- set_name.xx pieces can be placed in a single directory
- instead of separate ones for each distribution set. This
- will also simplify the installation work later on.
-
- Note where you place the files you will need this later.
-
- Once you have done this, you can proceed to the next
- step in the installation process, preparing your hard disk.
-
- To prepare for installing via a tape:
-
- To install NetBSD from a tape, you need to somehow
- get the NetBSD filesets you wish to install on
- your system on to the appropriate kind of tape,
- in tar format.
-
- If you're making the tape on a UN*X system, the easiest
- way to do so is:
-
- tar cvf <tape_device> <files>
-
- where "<tape_device>" is the name of the tape device
- that describes the tape drive you're using (possibly
- something like /dev/nrst0, but we make no guarantees 8-).
- If you can't figure it out, ask your system administrator.
- "<files>" are the names of the "set_name.nnn" files
- which you want to be placed on the tape.
-
- Once you have done this, you can proceed to the next
- step in the installation process, preparing your hard disk.
-
- To prepare for installing via an NFS partition:
-
- NOTE: this method of installation is recommended
- only for those already familiar with using
- the BSD network-manipulation commands and
- interfaces. If you aren't, this documentation
- should help, but is not intended to be
- all-encompassing.
-
- Place the NetBSD software you wish to install into
- a directory on an NFS server, and make that directory
- mountable by the machine which you will be installing
- NetBSD on. This will probably require modifying the
- /etc/exports file of the NFS server and resetting
- mountd, acts which will require superuser privileges.
- Note the numeric IP address of the NFS server and of
- the router closest to the the new NetBSD machine,
- if the NFS server is not on a network which is
- directly attached to the NetBSD machine.
-
- Once you have done this, you can proceed to the next
- step in the installation process, preparing your hard disk.
-
- To prepare for installing via FTP:
-
- NOTE: this method of installation is recommended
- only for those already familiar with using
- the BSD network-manipulation commands and
- interfaces. If you aren't, this documentation
- should help, but is not intended to be
- all-encompassing.
-
- The preparations for this method of installation
- are easy: all you have to do is make sure that
- there's some FTP site from which you can retrieve
- the NetBSD installation when it's time to do
- the install. You should know the numeric IP
- address of that site, the numeric IP address of
- your nearest router if one is necessary
-
- Once you have done this, you can proceed to the next
- step in the installation process, preparing your hard disk.
-
-
-
- Preparing your System for NetBSD Installation:
- --------- ---- ------ --- ------ ------------
-
- You will need an AmigaDOS hard drive prep tool to prepare you hard
- drives for use with NetBSD/amiga. HDToolBox is provided with the
- system software and on floppy installation disks since Release 2.0
- of AmigaDOS so we will provide instructions for its use.
-
- Preparing you hard disk with HDToolBox:
-
- A full explanation of HDToolBox can be found with your
- AmigaDOS manuals and is beyond the scope of this document.
-
- Note you will be modifying your HD's if you mess something
- up here you could lose everything on all the drives that
- you configure. It is therefore advised that you:
-
- Write down your current configurations. Do this
- by examining each partition on the drive and the
- drives parameters (from Change drive type.)
-
- Back up the partitions you are keeping.
-
- What you need to do is partition your drives; creating
- at least root, swap and /usr partitions and possibly at least
- one more for /local if you have the space.
-
- This should be done as the HDToolBox manual describes. One thing
- to note is that if you are not using a Commodore controller you
- will need to specify the device your SCSI controller uses e.g.
- if you have a Warp Engine you would:
-
- from cli,
- hdtoolbox warpdrive.device
-
- from wb set the tooltype,
- SCSI_DEVICE_NAME=warpdrive.device
-
- The important things you need to do above and beyond normal
- partitioning includes (from Partition Drive section):
-
- Marking all NetBSD partitions as non-bootable.
-
- Changing the file system parameters of the partitions
- to NetBSD ones. This must be done from the
- partitioning section and `Advanced options' must
- be enabled. To Make the needed changes:
-
- - Click the `Adv. Options' button
- - Click the `Change filesystem' button
-
- - Choose `Custom File System'
- - Turn off `Automount' if on.
- - Set the dostype to one of these three choices:
-
- root partition : 0x4e425207
- swap partition : 0x4e425301
- other partitions: 0x4e425507
-
- Here `other' refers to other partitions you will
- format for reading and writing under NetBSD (e.g.
- /usr)
-
- Make sure you hit the return key to enter this value
- as some versions of HDToolBox will forget your entry
- if you don't.
-
- - Turn custom boot code off
- - Set Reserved Blocks start and end to 0.
- - Click Ok.
-
- Mask and maxtransfer are not used with NetBSD.
-
- Until you compile your own kernel your swap partition
- must exist on the drive that also holds your root
- partition.
-
-
- Once this is done NetBSD/amiga will be able to recognize your
- disks and which partitions it should use.
-
-
-
- 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.
-
- First you need to get yourself into NetBSD. This can be
- done in a couple ways, both of which currently require
- AmigaDOS.
-
- You can insert the AmigaDOS kernel boot floppy and reboot
- or if you have downloaded a kernel to an AmigaDOS partition
- along with loadbsd you can run it from the CLI like so:
-
- loadbsd -b 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 AmigaDOS kernel boot floppy from the drive if present and
- insert the BSD install floppy. Now type `fd0' to boot off of
- your floppy drive 0.
-
- The system should continue to boot. For now ignore WARNING:
- messages about bad dates in clocks and swap space and about
- a missing /etc/spwd.db (it didn't fit, *shrug*). Eventually
- you will be asked to enter the pathname of the shell, just
- hit return. After a short while you should see a welcome
- message and a prompt, asking if you wish to proceed with the
- installation.
-
- If you wish to proceed, enter "y" and then return.
-
- If you have configured your hard drive[s] correctly it
- should find the drive and partition that you selected to
- use as your root.
-
- YOU ARE NOW AT THE POINT OF NO RETURN. If you confirm that
- you want to install NetBSD, your hard drive will be modified,
- and perhaps its contents scrambled at the whim of the install
- program.
-
- If you are sure you want to proceed, enter "yes" at the
- prompt.
-
- The install program will now make the root filesystem you
- specified. There should be only one error in this section
- of the installation. It will look like so:
-
- newfs: ioctl (WDINFO): Invalid argument
- newfs: /dev/rsd0a: can't rewrite disk label
-
- If there are any others, restart from the the beginning of
- the installation process. This error is ok as the Amiga
- does not write disklabels currently. You should expect
- this error whenever using newfs.
-
- Next the install program will ask you which drive and
- partition you wish to use as /usr. First it will list the
- available drives. Choose one. Next it will give you a
- list of the partitions on that disk along with their sizes,
- types, etc.. Choose the letter that corresponds to the
- partition you wish to use for /usr. If you are doing a
- full install this should be at the very least 45M-50M large.
- If everything is ok the install program will then format
- and mount your /usr. If not then it will ask again for a
- drive and partition.
-
- When this completes your root partition will be mounted on
- /mnt and your /usr partition on /mnt/usr. An fstab will
- have been created and initialized to correctly mount these
- two file systems. This fstab will be in /mnt/etc.
-
- What you do from this point on depends on which media you're
- using to install NetBSD. Follow the appropriate instructions,
- given below.
-
- To install from an AmigaDOS partition:
-
- You first need to mount the AmigaDOS partition
- using the mount_ados command. If e.g. your AmigaDOS
- partition is the first partition on sd0 you could
- type:
-
- mkdir /mnt/ados
- mount_ados /dev/sd0d /mnt/ados
-
- You can use `disklabel sd0' to find out what types
- of partitions are on the disk `sd0'.
-
- Next goto the directory in which you stored the
- distribution sets. If e.g. you stored them in the
- root directory of the partition:
-
- cd /mnt/ados
-
- When there, run "Set_tmp_dir" and choose the default
- temporary directory, by hitting return at the
- prompt.
-
- Run the "Extract" command, giving it as its sole
- argument the name of the distribution set you wish
- to extract. For example, to extract the base
- distribution, use the command:
-
- Extract base10
-
- and to extract the games distribution:
-
- Extract game10
-
- If the distribution sets are in different directories,
- you will need to cd to each directory in turn, runing
- "Set_tmp_dir" and the appropriate "Extract" command(s).
-
- Continue this process until you've finished installing
- all of the sets which you desire to have on your
- hard disk. Once you have extracted all sets and
- are at the "#" prompt again, proceed to the section
- "Configuring Your System," below.
-
- To install from tape:
-
- The first thing you should do is pick a temporary
- directory where the distribution files can be stored.
- To do this, use the command "Set_tmp_dir" and enter
- your choice. The default is /mnt/usr/distrib.
-
- After you have picked a temporary directory,
- you should issue the load command:
-
- Load_tape
-
- Next, you will be told to insert the media into
- the appropriate drive, and hit return. Continue
- to follow instructions until you are returned to
- the "#" prompt.
-
- Go to the directory which contains the first
- distribution set you wish to install. This is
- either the directory you specified above, or possibly
- a subdirectory of that directory.
-
- When there, run "Set_tmp_dir" again, and choose
- the default temporary directory, by hitting
- return at the prompt.
-
- Run the "Extract" command, giving it as its sole
- argument the name of the distribution set you
- wish to extract. For example, to extract the base
- distribution, use the command:
-
- Extract base10
-
- and to extract the games distribution:
-
- Extract game10
-
- After the extraction is complete, go to the location
- of the next set you want to extract, "Set_tmp_dir"
- again, and once again issue the appropriate
- extract command. Continue this process until
- you've finished installing all of the sets which you
- desire to have on your hard disk.
-
- After each set is finished, if you know that you
- are running low on space you can remove the
- distribution files for that set by saying:
-
- rm set_name.??
-
- For example, if you wish to remove the distribution
- files for the game09 set, after the "Extract game09"
- command has completed, issue the command:
-
- rm game10.??
-
- Once you have extracted all sets and are at the "#" prompt
- again, proceed to the section "Configuring Your System,"
- below.
-
- To install via FTP or NFS:
-
- First, use Set_tmp_dir to pick a temporary directory
- for the installation files. /mnt/usr/distrib is
- suggested.
-
- Configure the appropriate ethernet interface i.e. le0
- if you have a 2065 or ed0 if you have a AMIGNET from
- Hydra Systems.
-
- ifconfig <ifname> <ipaddr> [netmask <netmask>]
-
- where <ifname> is the interface name (e.g. ed0, etc.),
- and <ipaddr> is the numeric IP address of the interface.
- If the interface has a special netmask, supply
- the word "netmask" and that netmask at the end of the
- command line. For instance, without a special netmask:
-
- ifconfig ed0 129.133.10.10
-
- or with a special netmask
-
- ifconfig ed0 128.32.240.167 netmask 0xffffff00
-
- If the NFS server or FTP server is not on a directly-
- connected network, you should set up a route to it
- with the command:
-
- route add default <gate_ipaddr>
-
- where <gate_ipaddr> is your gateway's numeric IP address.
-
- If you are NFS-mounting the distribution sets,
- mount them on the temporary directory with the command:
-
- mount -t nfs <serv_ipaddr>:<dist_dir> <tmp_dir>
-
- where <serv_ipaddr> is the server's numeric IP address,
- <dist_dir> is the path to the distribution files on
- the server, and <tmp_dir> is the name of the local
- temporary directory.
-
- Once this is done, proceed as if you had loaded the
- files from tape, "cd"ing to the appropriate directories
- and running "Set_tmp_dir" and "Extract" as appropriate.
-
- If you are retrieving the distribution sets using ftp,
- cd into the temp directory, and execute the command:
-
- ftp <serv_ipaddr>
-
- where <serv_ipaddr> is once again the server's
- numeric IP address. Get the files with FTP,
- taking care to use binary mode to transfer
- all files.
-
- Once you have all of the files for the distribution sets
- you wish to install, you can proceed using the instructions
- above as if you had installed the files from a tape.
-
-
- Configuring Your System:
- ----------- ---- ------
-
- Once you have finished extracting all of the distribution sets that
- you want on your hard drive and are back at the "#" prompt,
- you are ready to configure your system.
-
- The configuration utility expects that you have installed the base
- system. If you have not, you will not be able to run it successfully
- (nor will you have a functional system regardless of configuration).
-
- To configure the newly installed operating system, run the
- command "Configure".
-
- Configure will ask for the machine's hostname, domain name, and other
- network configuration information.
-
- Once you have supplied `Configure' all that it requests, your machine
- will be configured well enough that when you reboot it it will
- almost be a completely functional NetBSD system. Note you should
- ignore the errors from `chown' they will be corrected shortly.
-
- Once you are done with `Configure', halt the system with the "halt"
- command (wait for "halted" to be displayed) and reboot. Then again
- boot NetBSD this time with the command:
-
- loadbsd netbsd
-
- You need to do your final tweeks now. First mount your file systems
- like so:
-
- mount -av
-
- Next you need to re-make your devices to get the ownership correct:
-
- cd /dev
- MAKEDEV all
-
- Your system is now complete but not completely configured; you
- should adjust the /etc/sendmail.cf file as necessary to suit your
- site and/or disable sendmail and other network related programs.
- These things can be found in /etc/netstart. Use vi, if you installed
- the man pages you can type `man vi' or `man ed' for instructions
- on how to use these somewhat non-intuitive editors.
-
- As mentioned at the end of the `Configure' run, you should copy the
- NetBSD kernel onto the root partition as "/netbsd".
-
- To get the proper timezone settings, link /etc/localtime to the
- appropriate file in /usr/share/zoneinfo. The link provided is to
- /usr/share/zoneinfo/US/Pacific.
-
- If you do not have a special graphics card like the Retina, you
- should edit the /etc/ttys file to turn off getty on the Retina
- console. Do this by editing the entry for /dev/ttye1, changing
- the "on" to "off".
-
- Once you are done with the rest of configuration unmount your file
- systems and halt your system, then reboot:
-
- cd /
- umount -av
- halt
- <reboot>
-
- Finally you can now boot your system and it will be completely
- functional:
-
- loadbsd -a netbsd
-
- When it boots off of the hard drive, you will have a complete
- NetBSD system! CONGRATULATIONS! (You really deserve them!!!)
-
-
-
- Upgrading a previously-installed NetBSD System:
- --------- - ---------- --------- ------ ------
-
- There is no previous release of NetBSD/amiga to upgrade.
-
-
-
- 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 <majordomo@NetBSD.ORG>. 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 has provided a home for
- sun-lamp, 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.
-
- 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.
-
- 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:
- Brian Carlstrom
- Demon Internet, UK
- Michael L. Hitch
- Herb Peyerl
- Mike Price
- Thor Lancelot Simon
- Bill Sommerfeld
- 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.)
-
- Dave Burgess <burgess@cynjut.infonet.net> has been maintaining the
- 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be
- recognized for it.
-
- 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 team:
- Chris G. Demetriou <cgd@sun-lamp.cs.berkeley.edu>
- Theo de Raadt <deraadt@sun-lamp.cs.berkeley.edu>
- Adam Glass <glass@sun-lamp.cs.berkeley.edu>
- Charles Hannum <mycroft@sun-lamp.cs.berkeley.edu>
-
- The port-masters (and their ports):
- Allen Briggs <briggs@mail.vt.edu> (mac68k)
- (and the rest of the 'Alice' group)
- Theo de Raadt <deraadt@sun-lamp.cs.berkeley.edu> (sparc)
- Charles Hannum <mycroft@sun-lamp.cs.berkeley.edu> (i386, hp300)
- Chris Hopps <chopps@sun-lamp.cs.berkeley.edu> (amiga)
- Adam Glass <glass@sun-lamp.cs.berkeley.edu> (pmax)
- Paul Mackerras <paulus@sun-lamp.cs.berkeley.edu> (da30)
- Anders Magnusson <ragge@sun-lamp.cs.berkeley.edu> (vax)
- Phil Nelson <phil@sun-lamp.cs.berkeley.edu> (pc532)
- Gordon Ross <gwr@sun-lamp.cs.berkeley.edu> (sun3)
-
- Supporting cast:
- Steve Allen <wormey@eskimo.com>
- John Brezak <brezak@sun-lamp.cs.berkeley.edu>
- Dave Burgess <burgess@cynjut.infonet.net>
- J.T. Conklin <jtc@sun-lamp.cs.berkeley.edu>
- Hubert Feyrer <hubert.feyrer@rz.uni-regensburg.de>
- Brad Grantham <grantham@tenon.com>
- Lawrence Kesteloot <kesteloo@cs.unc.edu>
- Paul Kranenburg <pk@sun-lamp.cs.berkeley.edu>
- Herb Peyerl <hpeyerl@novatel.ca>
- Matthias Pfaller <leo@marco.de>
- Chris Provenzano <proven@sun-lamp.cs.berkeley.edu>
- Wolfgang Solfrank <ws@tools.de>
-
-
- 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 Paul Kranenburg.
-
-
- This product includes software developed by Christian E. Hopps.
-
- This product includes software developed by Timo Rossi
-
-