diff options
author | Theo de Raadt <deraadt@cvs.openbsd.org> | 1995-10-18 08:53:40 +0000 |
---|---|---|
committer | Theo de Raadt <deraadt@cvs.openbsd.org> | 1995-10-18 08:53:40 +0000 |
commit | d6583bb2a13f329cf0332ef2570eb8bb8fc0e39c (patch) | |
tree | ece253b876159b39c620e62b6c9b1174642e070e /distrib/notes/amiga |
initial import of NetBSD tree
Diffstat (limited to 'distrib/notes/amiga')
-rw-r--r-- | distrib/notes/amiga/contents | 141 | ||||
-rw-r--r-- | distrib/notes/amiga/hardware | 58 | ||||
-rw-r--r-- | distrib/notes/amiga/install | 314 | ||||
-rw-r--r-- | distrib/notes/amiga/legal | 7 | ||||
-rw-r--r-- | distrib/notes/amiga/prep | 80 | ||||
-rw-r--r-- | distrib/notes/amiga/upgrade | 163 | ||||
-rw-r--r-- | distrib/notes/amiga/whatis | 4 | ||||
-rw-r--r-- | distrib/notes/amiga/xfer | 128 |
8 files changed, 895 insertions, 0 deletions
diff --git a/distrib/notes/amiga/contents b/distrib/notes/amiga/contents new file mode 100644 index 00000000000..2c728e54e55 --- /dev/null +++ b/distrib/notes/amiga/contents @@ -0,0 +1,141 @@ +The amiga-specific portion of the NetBSD 1.1 release is found in the +"amiga" subdirectory of the distribution. That subdirectory is layed +out as follows: + +.../NetBSD-1.1/amiga/ + binary/ amiga binary distribution sets; + see below. + + floppies/ amiga installation and upgrade +>>> ^^^^^^^^ should this be miniroot/? + file system images; see below. + + security/ amiga security distribution; + see below; + + utils/ Miscellaneous amiga + installation utilities; see + installation section, below. + +There are two amiga file system images to be found in the "amiga/floppy" +>>> ^^^^^^ +subdirectory of the NetBSD 1.1 distribution. One of them is a upgrade +image and one is an installation image. They are described in more +detail below. There are gzipped versions of each available, for easier +downloading. (The gzipped version have the ".gz" extension added to +their names.) + +Installation file system: + + This file contains a BSD root file system setup to help + you install the rest of NetBSD. This includes formatting + and mounting your root and /usr partitions and getting + ready to extract (and possibly first fetching) the distribution + sets. There is enough on this file system to allow you to + make a slip or ppp connection, configure an ethernet, mount an + NFS file system or ftp. You can also load distribution sets from + a SCSI tape or from one of your existing AmigaDOS partitions. + + This file is named "inst-11.fs". + + +Upgrade file system: + + This file contains a BSD root file system setup to help + you upgrade a previous version of NetBSD. This includes + converting existing partitions + and mounting your root and /usr partitions and getting + ready to extract (and possibly first fetching) the distribution + sets. There is enough on this file system to allow you to + make a slip or ppp connection, configure an ethernet, mount an + NFS file system or ftp. You can also load distribution sets from + a SCSI tape, from one of your existing AmigaDOS partitions, or + from an existing NetBSD partition. + + This file is named "inst-11.fs". + +The NetBSD/amiga binary distribution sets contain the binaries which +comprise the NetBSD 1.1 release for the amiga. There are seven binary +distribution sets, and the "security" distribution set. The binary +distribution sets can be found in subdirectories of the "amiga/binary" +subdirectory of the NetBSD 1.1 distribution tree, and are as follows: + + base11 The NetBSD/amiga 1.1 base binary distribution. You + MUST install this distribution set. It contains the + base NetBSD utilities that are necessary for the + system to run and be minimally functional. It + includes shared library support, and excludes + everything described below. + [ 7M gzipped, 19M uncompressed ] +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + comp11 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 ] +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + etc11 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 ] +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + games11 This set includes the games and their manual pages. + [ 1M gzipped, 3M uncompressed ] +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + man11 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 ] +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + misc11 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 ] +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^ + + text11 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 "secr11" and can be found +in the "amiga/security" subdirectory of the NetBSD 1.1 distribution +tree. It contains crypt.c (the source file for the DES encryption +algorithm) and the binaries which depend on it. It can only be found +on those sites which carry the complete NetBSD distribution and that +can legally obtain it. (Remember, because of United States law, this +distribution set may not be exported to locations outside of the +United States and Canada.) [ 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. diff --git a/distrib/notes/amiga/hardware b/distrib/notes/amiga/hardware new file mode 100644 index 00000000000..513236ac7cd --- /dev/null +++ b/distrib/notes/amiga/hardware @@ -0,0 +1,58 @@ +NetBSD/amiga 1.1 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 +>>> adjust sizes? + +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/Bytesync. + 53c710 based boards: A4091, Magnum, Warp Engine and Zeus. + FAS216 based boards: FastLane Z3, Blizzard. + Video controllers: + ECS, AGA and A2024 built in on various amigas. + Retina Z2 and Retina Z3. + Picasso II. + GVP Spectrum. + Piccalo. + A2410. + Ethernet controllers: + A2065 Ethernet + Hydra Ethernet + ASDG Ethernet + A4066 Ethernet + Ariadne Ethernet + Arcnet controllers: + A2060 Arcnet + Tape drives: + Most SCSI tape drives, including + Archive Viper, Cipher SCSI-2 ST150. + CD-ROM drives: + Most SCSI CD-ROM drives + Serial cards: + MultiFaceCard II and III + A2232 + 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. diff --git a/distrib/notes/amiga/install b/distrib/notes/amiga/install new file mode 100644 index 00000000000..5b73f335e75 --- /dev/null +++ b/distrib/notes/amiga/install @@ -0,0 +1,314 @@ +Installing NetBSD is a relatively complex process, but, if you have +this document in hand and are careful to read and remember the +information which is presented to you by the install program, it +shouldn't be too much trouble. + +Before you begin, you must have already prepared your hard disk as +detailed in the section on preparing your system for install. + +The following is a walk-through of the steps necessary to get NetBSD +installed on your hard disk. If you wish to stop the installation, +you may hit Control-C at any prompt, but if you do, you'll have to +begin again from scratch. + +>>> transfer installation file system to the swap partition. +>>> Does this go here, or in the hard disk prep section? + +>>> Getting loadbsd, ixemul.library, and netbsd onto AmigaDOS +>>> partition. + Next you need to get yourself into NetBSD by loading the + kernel from AmigaDOS with loadbsd like so: + + loadbsd -b netbsd + + You should see the screen clear and some information about + your system as the kernel configures the hardware. Note which + hard disk device(s) are configured (sd0, sd1, etc). Then + you will be prompted for a root device. At this time type + 'sd0*'. +>>> Need to document what device number to actually use. + + The system should continue to boot. For now ignore WARNING: + messages about bad dates in clocks and swap space. 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 base11 + + and to extract the games distribution: + + Extract game11 + + 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 base11 + + and to extract the games distribution: + + Extract game11 + + 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 game11.?? + + 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. + +>>> Document using ppp or slip? + 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 +>>> Is this step still needed? - check on it! + +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. + +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!!!) + +>>> Missing the step to transfer the netbsd kernel to / diff --git a/distrib/notes/amiga/legal b/distrib/notes/amiga/legal new file mode 100644 index 00000000000..2a4b4e547b6 --- /dev/null +++ b/distrib/notes/amiga/legal @@ -0,0 +1,7 @@ + This product includes software developed by Christian E. Hopps. + + This product includes software developed by Timo Rossi + + This product includes software developed by Michael L. Hitch + +>>> any others? diff --git a/distrib/notes/amiga/prep b/distrib/notes/amiga/prep new file mode 100644 index 00000000000..7e7f8c2919d --- /dev/null +++ b/distrib/notes/amiga/prep @@ -0,0 +1,80 @@ +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. + +>>> Should the miniroot transfer to the swap partition instructions +>>> go here? diff --git a/distrib/notes/amiga/upgrade b/distrib/notes/amiga/upgrade new file mode 100644 index 00000000000..d6fc606e39f --- /dev/null +++ b/distrib/notes/amiga/upgrade @@ -0,0 +1,163 @@ +The upgrade to NetBSD 1.1 is a binary upgrade; it would be prohibitive +to make users upgrade by compiling and installing the 1.1 sources, and +it would be very difficult to even compile a set of instructions that +allowed them to do so. Because of the various changes to the system, +the largest being the 64-bit file size support and shared libraries, +>>> just what are the major differences between 1.0 and 1.1?? +it is impractical to upgrade by recompiling from the sources and +installing. + +>>> no kernel-copy! +To do the upgrade, you must have the appropriate kernel-copy floppy +image on a disk, and the upgr-11.fs floppy image on another. You must +>>> +also have at least the "base11" binary distribution set available, +so that you can upgrade with it, using one of the upgrade methods +described above. Finally, you must have sufficient disk space +available to install the new binaries. Since the old binaries are +being overwritten in place, you only need space for the new binaries, +which weren't previously on the system. If you have a few megabytes +free on each of your root and /usr partitions, you should have enough +space. + +Since upgrading involves replacing the kernel, and most of the system +binaries, it has the potential to cause data loss. You are strongly +advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the +NetBSD partition or on another operating system's partition, before +beginning the upgrade process. + +To upgrade your system, follow the following instructions: + +>>> transfer upgrade file system image to swap partition +>>> should this be in the hard disk prep section? + + Boot your machine using of the appropriate kernel-copy floppy. + When presented with the boot prompt (the prompt begins with + "Boot" and ends with ":-"), hit return. + + While booting, you will probably see several warnings. You + should be warned that no swap space is present, and that +>>> ^^^^^^^^^^^^^^^^^^^^^ + init(8) cannot find /etc/rc. Do not be alarmed, these are +>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + completely normal. When you reach the prompt asking you for a + shell name, just hit return. + + You will be presented with some information about the upgrade + process and a warning message, and will be asked if you wish + to proceed with the upgrade process. If you answer + negatively, the upgrade process will stop, and your disk will + not be modified. If you answer affirmatively, the upgrade + process will begin, and your disk will be modified. You may + hit Control-C to stop the upgrade process at any time. + However, if you hit it at an inopportune moment, your system + may be left in an inconsistent (and possibly unusable) state. + + You will be asked if you wish to upgrade your file systems to + the new file system format. If you do, reply affirmatively. + If you don't have your file systems upgraded now, you should + probably do it manually after the install process is complete, + by using "fsck -c 2". Read the fsck(8) manual page for more + details. +>>> Is this needed for 1.0 to 1.1 upgrade? Or mention that the upgrade +>>> should be done if it wasn't previously done? [It shouldn't hurt +>>> to run through the upgrade steps.] + + The upgrade program will then check your root file system, + and, if you approved, will upgrade it to the new file system + format. It will then mount your root file system on /mnt. + + If your file systems are being upgraded, the upgrade script + will copy the new fsck(8) program to your hard disk and + upgrade your remaining file systems. + + The upgrade program will then mount all of your file systems + under /mnt. (In other words, your root partition will be + mounted on /mnt, your /usr partition on /mnt/usr, etc.) + + If you don't already have the NetBSD distribution sets on your + disk, look in the installation section for information on how + to transfer them to your disk. +>>> NetBSD or AmigaDOS partitions... + + Once the distribution sets are transferred to your disk, + continue here. (Obviously, if the NetBSD distribution sets + are already on your disk, because you've transferred them + before starting the upgrade process, you don't need to + transfer them again now!) + + After the software has been transferred to the machine (or + mounted, in the case of upgrading via NFS), change into the + directory containing the "base11" distribution set. Once you + are there, run the "Set_tmp_dir" command, and hit return at + the prompt to select the default answer for the temporary + directory's path name. (It should be the path name of the + directory that you're in.) + + Run the command "Extract base11" to upgrade the base + distribution. + + Repeat the above two steps for all of the sets you wish to + upgrade. (For each, change into the directory containing the + set, run "Set_tmp_dir" and accept the default path name, then + run the "Extract <setname>" command.) + + If you were previously using the security distribution set, + you MUST upgrade to the new version, or you will not be able + to log in when the upgrade process is complete. Similarly, if + you were not previously using the security set, you must NOT + upgrade to the new version. + + When you are done upgrading all of the distribution sets you + wish to upgrade, issue the command "Cleanup". It will clean + up the installation, by remaking some system databases. When + it is complete, you should use "halt" to halt the system. + +>>> transfer new kernel to / + +Your system has now been upgraded to NetBSD 1.1. + +After a new kernel has been copied to your hard disk, your + machine is a complete NetBSD 1.1 system. However, that + doesn't mean that you're finished with the upgrade process. + There are several things that you should do, or might have to + do, to insure that the system works properly. + + First, if you did not upgrade your file systems to the new + file system format during the upgrade process, you may want to + do so now, with "fsck -c 2". If you are unsure about the + process, it's suggested that you read the fsck(8) manual page. + + Second, you will probably want to get the etc11 distribution, + extract it, and compare its contents with those in your /etc/ + directory. You will probably want to replace some of your + system configuration files, or incorporate some of the changes + in the new versions into yours. + + Third, you will probably want to update the set of device + nodes you have in /dev. If you've changed the contents of + /dev by hand, you will need to be careful about this, but if + not, you can just cd into /dev, and run the command "sh + MAKEDEV all". + + Fourth, you must deal with certain changes in the formats of + some of the configuration files. The most notable change is + that the "options" given to many of the file systems in + /etc/fstab or by hand have changed, and some of the file + systems have changed names. To find out what the new options + are, it's suggested that you read the manual page for the + file systems' mount commands, for example mount_nfs(8) for + NFS. (Note that the information for mounts of type "ufs", + i.e. Fast File Systems, are contained in the mount(8) man + page.) +>>> Is this needed for 1.0 -> 1.1 upgrade? + + Finally, you will want to delete old binaries that were part + of the version of NetBSD that you upgraded from and have since + been removed from the NetBSD distribution. You might also + want to recompile any locally-built binaries, to take + advantage of the shared libraries. (Note that any new + binaries that you build will be dynamically linked, and + therefore take advantage of the shared libraries, by default. + For information on how to make statically linked binaries, + see the cc(1) and ld(1) manual pages.) diff --git a/distrib/notes/amiga/whatis b/distrib/notes/amiga/whatis new file mode 100644 index 00000000000..bff5272d6c1 --- /dev/null +++ b/distrib/notes/amiga/whatis @@ -0,0 +1,4 @@ + +>>> What should go here? +This is the first public release of NetBSD for the Amiga line of +computers. diff --git a/distrib/notes/amiga/xfer b/distrib/notes/amiga/xfer new file mode 100644 index 00000000000..602b2bb18e1 --- /dev/null +++ b/distrib/notes/amiga/xfer @@ -0,0 +1,128 @@ +Installation is supported from several media types, including: + AmigaDOS HD partitions + Tape + NFS partitions + FTP + NetBSD partitions, if doing an upgrade. + +>>> Transfering install/upgrade file system image to swap partition +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-11.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-11.fs +>>> fix above to document file system transfer to swap paritition +>>> using xstreamtodev + +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. + +If you are upgrading NetBSD, you also have the option of installing +NetBSD by putting the new distribution sets somewhere in your existing +file system, and using them from there. To do that, you must do the +following: + + Place the distribution sets you wish to upgrade somewhere in + your current file system tree. At a bare minimum, you must + upgrade the "base" binary distribution, and so must put the + "base11" set somewhere in your file system. If you wish, + you can do the other sets, as well, but you should NOT upgrade + the "etc" distribution; the "etc" distribution contains system + configuration files that you should review and update by hand. + + Once you have done this, you can proceed to the next step in + the upgrade process, actually upgrading your system. |