From e968859def471580c1d8e5c71aeaf7b7c30e2f01 Mon Sep 17 00:00:00 2001 From: mark Date: Sat, 8 Nov 1997 02:55:06 +0000 Subject: [PATCH] Install notes for NetBSD/arm32. --- distrib/notes/arm32/contents | 113 +++++++ distrib/notes/arm32/hardware | 90 ++++++ distrib/notes/arm32/install | 391 ++++++++++++++++++++++ distrib/notes/arm32/legal | 13 + distrib/notes/arm32/prep | 16 + distrib/notes/arm32/prep.RISCOS | 558 ++++++++++++++++++++++++++++++++ distrib/notes/arm32/upgrade | 5 + distrib/notes/arm32/whatis | 9 + distrib/notes/arm32/xfer | 164 ++++++++++ 9 files changed, 1359 insertions(+) create mode 100644 distrib/notes/arm32/contents create mode 100644 distrib/notes/arm32/hardware create mode 100644 distrib/notes/arm32/install create mode 100644 distrib/notes/arm32/legal create mode 100644 distrib/notes/arm32/prep create mode 100644 distrib/notes/arm32/prep.RISCOS create mode 100644 distrib/notes/arm32/upgrade create mode 100644 distrib/notes/arm32/whatis create mode 100644 distrib/notes/arm32/xfer diff --git a/distrib/notes/arm32/contents b/distrib/notes/arm32/contents new file mode 100644 index 000000000000..67b6ba8ce4f5 --- /dev/null +++ b/distrib/notes/arm32/contents @@ -0,0 +1,113 @@ +The arm32-specific portion of the NetBSD _VER release is found in the +"arm32" subdirectory of the distribution. That subdirectory is laid +out as follows: + +.../NetBSD-_VER/arm32/ + INSTALL Installation notes; this file. + + binary/ arm32 binary distribution sets; + see below. + + kernels/ arm32 installation and other + kernels; see below. + + security/ arm32 security distribution; + see below; + + / Miscellaneous arm32 + installation utilities and + supplementary documentation for + ; see installation + section, below. + +There are a collection of arm32 kernels in the "arm32/kernels" +subdirectory of the NetBSD _VER distribution. Some of these kernels +contain a root file system image and should only be used for the +initial installation. Some of the kernels only support a particular +subset of the platforms that arm32 supports (See +"arm32/kernels/README" for more details.) + +The NetBSD/arm32 binary distribution sets contain the binaries which +comprise the NetBSD _VER release for the arm32. There are eight binary +distribution sets and the "security" distribution set. The binary +distribution sets can be found in subdirectories of the "arm32/binary" +subdirectory of the NetBSD _VER distribution tree, and are as follows: + + + base13 The NetBSD/arm32 _VER 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. + [ ~11M gzipped, 28M uncompressed ] + + comp13 The NetBSD/arm32 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. + [ 7.5M gzipped, 25M uncompressed ] + + etc13 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.) + [ 52K gzipped, 310K uncompressed ] + + games13 This set includes the games and their manual pages. + [ 3M gzipped, 7.4M uncompressed ] + + man13 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, 9.5M uncompressed ] + + misc13 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, 8M uncompressed ] + + text13 This set includes NetBSD's text processing tools, + including groff, all related programs, and their + manual pages. + [ 1M gzipped, 3.8M uncompressed ] + + +The arm32 security distribution set is named "secr13" and can be found +in the "arm32/security" subdirectory of the NetBSD _VER distribution +tree. It contains security related binaries which depend on +cryptographic source code. You do not need this distribution set to use +encrypted passwords in your password file; the "base13" distribution +includes a crypt library which can perform only the decryption function. +The security distribution includes a version of the Kerberos IV +network security system, and a Kerberized version of the "telnet" program. +The "secr13" distribution set can be found only on those sites which +carry the complete NetBSD distribution and which 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.) + [ 154K gzipped, 358K uncompressed ] + +The arm32 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 arm32 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 xfp" +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/arm32/hardware b/distrib/notes/arm32/hardware new file mode 100644 index 000000000000..a24cb36bc369 --- /dev/null +++ b/distrib/notes/arm32/hardware @@ -0,0 +1,90 @@ +NetBSD/arm32 _VER runs on several systems with ARM6 or above processors, +with or without FPU coprocessor. The minimal configuration is said to +require 8M of RAM and 50M of disk space, though we do not know of anyone +running with a system quite this minimal today. To install the entire +system requires much more disk space (the unpacked binary distribution, +without sources, requires at least 65M without counting space needed for +swap space, etc), and to run X or compile the system, more RAM is +recommended. (8M of RAM will actually allow you to run X and/or compile, +but it won't be speedy. Note that until you have around 16M of RAM, +getting more RAM is more important than getting a faster CPU.) + +Supported devices include (but is not limit to): + RiscPC/A7000(+) floppy controller. + IDE controllers: + Acorn motherboard IDE. + Simtec IDE controller. + RapIDE IDE controller. + ICS IDE controller. + + SCSI host adapters: + Cumana SCSI 2. + PowerTec SCSI 2. + MCS Connect32 SCSI 2. + Acorn SCSI. + Oak SCSI I. + Morley SCSI I (uncached only). + + VIDC20 video. + RiscPC Motherboard serial port. + RiscPC Motherboard parallel port. + Ethernet adapters: + Acorn Ether1. + Atomwide Ether3. + ANT Ether3. + ANT Ether5. + Atomwide EtherA. + ANT EtherB. + Acorn EtherH. + I-cubed EtherH. + ANT EtherM. + + Most SCSI tape drives. + CD-ROM drives: + Most SCSI CD-ROM drives. + Most ATAPI CD-ROM drives. + [ Note: Some low-priced IDE CDROM drives are known + for being not or not fully ATAPI compliant, and thus + requires some hack (generally an entry to a quirk + table) to work with NetBSD.] + + Mice: + RiscPC quadrature mouse. + A7000 PS/2 mouse. + + Processors: + ARM 610. + ARM 700. + ARM 700 + FPA11. + ARM 710. + ARM 7500. + ARM 7500FE. + ARM 810. [*] + SA110. + + Motherboards: + Acorn RiscPC. + Acorn A7000 (experimental). + Acorn A7000+ (experimental). + VLSI RC7500 (experimental). + + Other devices: + RiscPC keyboard. + A7000 keyboard. + RiscPC realtime clock. + VLSI RC7500 motherboard devices. + +Drivers for hardware marked with "[*]" are NOT present in installation +kernels. + +Support for some devices is limited to particular kernels. eg there is no +SA110 support in A7000 kernels. + +Hardware the we do NOT currently support, but get many questions +about: + Acorn/Aleph1 PC cards. + Any SCSI card using a PowerROM. + Podule based serial ports. + Castle SCSI/Ethernet cards. + +Drivers are planned for some of the above. diff --git a/distrib/notes/arm32/install b/distrib/notes/arm32/install new file mode 100644 index 000000000000..6071a47e9754 --- /dev/null +++ b/distrib/notes/arm32/install @@ -0,0 +1,391 @@ +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 should know the geometry of your hard disk, i.e. +the sector size (note that sector sizes other than 512 bytes are not +currently supported), the number of sectors per track, the number of +tracks per cylinder (also known as the number of heads), and the +number of cylinders on the disk. The NetBSD kernel will try to +discover these parameters on its own, and if it can it will print them +at boot time. If possible, you should use the parameters it prints. +(You might not be able to because you're sharing your disk with +another operating system, or because your disk is old enough that the +kernel can't figure out its geometry.) + +If NetBSD will be sharing the disk with RiscOS or another operating +system, you should have already completed the section of these notes +that instructed you on how to prepare your hard disk. You should know +the size of the NetBSD area of the disk and its offset from the +beginning of the disk. You will need this information when setting up +your NetBSD partitions. + +You should now be ready to install NetBSD. It might be handy for you +to have a pencil, some paper, and a calculator handy. + +The following is a walk-through of the steps you will take while +getting NetBSD installed on your hard disk. If any question has a +default answer, it will be displayed in brackets ("[]") after the +question. If you wish to stop the installation, you may hit Control-C +at any time, but if you do, you'll have to begin the installation +process again from scratch. + + Boot your machine using the installation kernel for your + platform (instructions for doing this on your platform can be + found in the preparation section of this document). + + If this doesn't work, ensure that you're using the correct + kernel for your hardware. + + Depending upon your platform and the method of loading the, + it may take a while to load the kernel. + + You will then be presented with the NetBSD kernel boot + messages. You will want to read them, to determine your + disk's name and geometry. Its name will be something like + "sd0" or "wd0" and the geometry will be printed on a line that + begins with its name. As mentioned above, you will need your + disk's geometry when creating NetBSD's partitions. You will + also need to know the name, to tell the install tools what + disk to install on. + + 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 asked if you wish to install or upgrade your + system or go to a shell prompt. Enter "install". + + You will be presented with a welcome message and a prompt, + asking if you wish to proceed with the installation process. + If you wish to proceed, enter "y" and hit return. + + You will be asked what type of disk driver you have. The + valid options are listed by the install program, to make sure + you get it right. + + The install program will then tell you which disks of that + type it can install on, and ask you which it should use. + Reply with the name of your disk. (The first disk of the type + you selected, either "wd0" for IDE disks, or "sd0" for SCSI + disks, is the default.) + + You will then be asked to name your disk's disklabel. The + default response is "mywd" or "mysd" depending on the type of + your disk, and for most purposes it will be OK. If you choose + to name it something different, make sure the name is a single + word and contains no special characters. You don't need to + remember this name. + + You will be prompted for your disk's geometry information, + i.e. the number of bytes per sector, cylinders on the disk, + tracks per cylinder (heads), and sectors per track. Enter + them when they are requested. If you make a mistake, hit + Control-C and when you get to the shell prompt, restart the + install process by running the "install" command. Once you + have entered this data, the install program will tell you the + total size of your disk, in both sectors, and cylinders. + Remember this number; if you're installing on the whole disk, + you'll need it again soon. + + When describing your partitions, you will have the option of + entering data about them in units of disk sectors or + cylinders. If you choose to enter the information in units of + sectors, remember that, for optimal performance, partitions + should begin and end on cylinder boundaries. You will be + asked about which units you wish to use, and you should reply + with "c" for cylinders, or "s" for sectors. + + You will be asked for the size of the NetBSD portion of the + disk. If you're installing on the whole disk, reply with the + size of the disk, as printed earlier by the install program. + If you're using only part of the disk, reply with the size + that you specified in the partition editor. (Don't forget to + enter the size in the units you specified in the last step!) + + If you are not installing on the whole disk, you will be asked + for the offset of the NetBSD partition from the beginning of + the disk. Reply with the appropriate offset (again, in + whichever units you specified), as determined by how you + set up your disk using the partition editor. + + You will be asked to enter the size of your NetBSD root + partition. It should be at least 13M, but if you are going to + be doing development, 14-16M is a more desirable size. This + size should be expressed in units of sectors or cylinders, + depending on which you said you wanted to use. + + Next, you will be asked for the size of your swap partition. + You should probably allocate twice as much swap space as you + have real memory. Systems that will be heavily used should + have more swap space allocated, and systems that will be + lightly used can get by with less. If you want the system to + be able to save crash dumps when it panics, you will need at + least as much swap space as you have RAM. Again, this number + should be expressed in units of sectors or cylinders, as + appropriate. + + The install program will then ask you for information about + the rest of the partitions you want on your disk. For most + purposes, you will want only one more partition, "/usr". + (Machines used as servers will probably also want /var as a + separate partition. That can be done with these installation + tools, but is not covered here.) The install program will + tell you how much space there is left to be allocated in the + NetBSD area of the disk, and, if you only want one more + partition ("/usr"), you should enter it at the prompt when the + installer asks you how large the next partition should be. + It will then ask you for the name of the mount point for that + partition. If you're doing a basic installation, that is + "/usr". + + YOU ARE NOW AT THE POINT OF NO RETURN. Nothing has been + written to your disk yet, but if you confirm that you want to + install NetBSD, your hard drive will be modified, and its + contents may be scrambled at the whim of the install program. + This is especially likely if you have given the install + program incorrect information. If you are sure you want to + proceed, enter "yes" at the prompt. + + The install program will now label your disk and make the file + systems you specified. The filesystems will be initialized to + contain NetBSD bootstrapping binaries and configuration files. + It will also create an /etc/fstab for your system, and mount + all of the file systems under /mnt. (In other words, your root + partition will be mounted on /mnt, your /usr partition on + /mnt/usr, and so on.) There should be no errors in this + section of the installation. If there are, restart from the + beginning of the installation process. + + You will be placed at a shell prompt ("#"). The task is to + install the distribution sets. The flow of installation + differs depending on your hardware resources, and on what + media the distribution sets reside. + + To install from floppy: + The first thing you should do is pick a temporary + directory where the distribution files can be stored. + To do this, enter the command "Set_tmp_dir", and enter + the name of the temporary directory. (Don't forget + that if your disk is still mounted under /mnt; you + should probably pick a directory under /mnt/usr.) + + After you have picked a temporary directory, enter the + "Load_fd" command, to load the distribution sets from + your floppies. + + You will be asked which floppy drive to use. Enter + "0" (zero) if you're using the first floppy drive, or + enter "1" if you're using the second. + + You will be prompted to insert a floppy into the drive, + to have its contents copied to your hard disk. Do so, + and hit return to begin copying. When that is done, + read the remainder of the floppies that contain the + distribution sets that you want to install, one by + one. When the last is read, and you are being + prompted for another, hit Control-C. + + Run the "Extract" command once for each distribution + set you wish to install. For instance, if you wish to + install the "base13" distribution set, followed by the + "text13" distribution set, and finally the "etc13" + distribution set, use the commands: + Extract base13 + Extract text13 + Extract etc13 + + For each extraction, it will ask you if the extraction + should be verbose. If you reply affirmatively, it + will print out the name of each file that's being + extracted. + + (Note: if you know that you will be running low on + disk space when installing NetBSD, you can load and + extract one distribution set at a time. To do this, + load only the floppies which contain the files for the + first distribution set, extract them, and then change + to the temporary directory and remove them with the + command "rm set_name.??".) + + Once you are finished extracting all of the sets that + you wish to install, you should proceed to the + instructions below (after the last install medium + type-specific instructions), that explain how you + should configure your system. + + 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, enter the command "Set_tmp_dir", and enter + the name of the temporary directory. (Don't forget + that your disk is mounted under /mnt; you should + probably pick a directory under /mnt/usr.) The + default is /mnt/usr/distrib. + + After you have picked a temporary directory, enter the + "Load_tape" command, to load the distribution sets from + tape. + + You will be asked which tape drive to use. The + default is "rst0", which is correct if you're using + the SCSI tape drive with the lowest SCSI ID number. + (For the SCSI tape drive with the next lowest SCSI ID + number, you should use "rst1", and so on.) + + You will be prompted to hit return when you have + inserted the tape into the tape drive. When you do, + the contents of the tape will be extracted into the + temporary directory, and the names of the files being + extracted will be printed. + + After the tape has been extracted, to go the directory + containing the first distribution set you wish to + install. (Depending on how you made the tape, it's + probably a subdirectory of the temporary directory you + specified above.) Once there, run the "Set_tmp_dir" + command again, and accept its default answer by + hitting return at the prompt. + + Use the "Extract" command to extract the distribution + set. For instance, if you're extracting the "base13" + set, use the command: + Extract base13 + You will be asked if you wish the extraction to be + verbose. If you reply affirmatively, the name of each + file being extracted will be printed. + + Repeat the previous two steps for each distribution + set you wish to install. Change to the set's + directory, run "Set_tmp_dir", and then run + "Extract " to extract the set. + + Once you are finished extracting all of the sets that + you wish to install, you should proceed to the + instructions below (after the last install medium + type-specific instructions), that explain how you + should configure your system. + + To install via FTP or NFS: + The first thing you should do is pick a temporary + directory where the distribution files can be stored. + To do this, enter the command "Set_tmp_dir", and enter + the name of the temporary directory. (Don't forget + that your disk is mounted under /mnt; you should + probably pick a directory under /mnt/usr.) The + default is /mnt/usr/distrib. + + Configure the appropriate ethernet interface (e.g. + ea0, eb0, etc.) up, with a command like: + + ifconfig [netmask ] + + where "" is the interface name, like those + listed above, and "" is the numeric IP address + of the interface. If the interface has a special + netmask, supply the word "netmask" at and that netmask + at the end of the command line. (The brackets + indicate that those arguments are optional.) For + instance, to configure interface ea0 with IP address + 129.133.10.10, use the command: + + ifconfig ea0 129.133.10.10 + + and to configure interface eb0 with IP address + 128.32.240.167 and a special netmask, 0xffffff00, use + the command: + + ifconfig eb0 128.32.240.167 netmask 0xffffff00 + + If the NFS server or FTP server is not on a directly- + connected network, you need to set up a route to it + using a command like: + + route add default + + where is your gateway's numeric IP + address. + + If you are NFS-mounting the distribution sets, mount + them on the temporary directory with a command like: + + mount -t nfs : + + where is the server's numeric IP address, + is the path to the distribution files on + the server, and is the name of the local + temporary directory. + + Once this is done, proceed as if you had loaded the + files from tape, changing to the appropriate + directories, running "Set_tmp_dir", and running + "Extract" as appropriate. + + If you are retrieving the distribution sets using ftp, + change into the temporary directory, and execute the + command: + + ftp + + where is once again the server's numeric + IP address. Get the files with FTP, taking care to + use binary mode when transferring the files. + + Once you have all of the files for the distribution + sets that you wish to install, you can proceed using + the instructions above, as if you had installed from a + floppy. (Note that as with the floppy install, if + you're short on disk space, you can transfer only one + set at a time, extract it, then delete it, to save + space.) + + To install from CDROM: + First create a mount point so that you can mount the + CDROM: + mkdir /mnt/cdrom + If you get an error here of "mkdir: /mnt/cdrom", don't + worry it just means that you didn't need to create the + directory. + + Then all you need to do is mount the CDROM. + For the first CDROM drive use: + mount -rt cd9660 /dev/cd0a /mnt/cdrom + Or, for the second use: + mount -rt cd9660 /dev/cd1a /mnt/cdrom + + Once this is done, extract the required sets as + described in the "To install from floppy" section, but + ensure that you set the temporary directory to the + location of the sets on the CDROM (usually + /cdrom/distrib, but check the release notes that + came with the CD). + +Completing your installation: + Once you have finished extracting all of the distribution sets + that you wish to install, and are back at the "#" prompt, you + are ready to configure your system. The configuration utility + expects that you have installed the "base13" and "etc13" + distribution sets. If you have not, you will not be able to + run it successfully (nor will you have a functional system, in + any case). To configure your newly-installed NetBSD system, + run the command "Configure". It will ask you for the system's + host name, domain name, and other network configuration + information. It will set up your configuration files and make + the device nodes for the newly-installed system. + + +Congratulations, you have successfully installed NetBSD _VER. When you +reboot into NetBSD, you should log in as "root" at the login prompt. +There is no initial password, but if you're using the machine in a +networked environment, you should create yourself an account and +protect it and the "root" account with good passwords. + +Some of the files in the NetBSD _VER distribution might need to be +tailored for your site. In particular, the /etc/sendmail.cf file will +almost definitely need to be adjusted, and other files in /etc will +probably need to be modified, as well. If you are unfamiliar with +UN*X-like system administration, it's recommended that you buy a book +that discusses it. diff --git a/distrib/notes/arm32/legal b/distrib/notes/arm32/legal new file mode 100644 index 000000000000..0c1f8ceee1a4 --- /dev/null +++ b/distrib/notes/arm32/legal @@ -0,0 +1,13 @@ + This product includes software developed by Mark Brinicombe. + + This product includes software developed by Neil Carson. + + This product includes software developed by Scott Stevens. + + This product includes software developed by Rob Black. + + This product includes software developed by Melvyn Tang-Richardson. + + This product includes software developed by Wolfgang Solfrank. + + This product includes software developed by Frank Lancaster. diff --git a/distrib/notes/arm32/prep b/distrib/notes/arm32/prep new file mode 100644 index 000000000000..9d4a5b48de12 --- /dev/null +++ b/distrib/notes/arm32/prep @@ -0,0 +1,16 @@ +First and foremost, before beginning the installation process, MAKE +SURE YOU HAVE A RELIABLE BACKUP of any data on your hard disk that you +wish to keep. Repartitioning your hard disk is an excellent way to +destroy important data. + +Second, read and perform the instructions in "arm32//prep" +specific to your platform for partitioning and booting (even if you're +dedicating a device to NetBSD). + +Finally, when you are happy with your NetBSD installation, do whatever +is necessary to restore order to the partition you took space away from. +This will most likely involve restoring files, but might involve some +other "house-work". + +Your hard disk is now prepared to have NetBSD installed on it, and +you should proceed with the installation instructions. diff --git a/distrib/notes/arm32/prep.RISCOS b/distrib/notes/arm32/prep.RISCOS new file mode 100644 index 000000000000..1796f22ac19a --- /dev/null +++ b/distrib/notes/arm32/prep.RISCOS @@ -0,0 +1,558 @@ +These instructions are specific to NetBSD/arm32 on Acorn RISCOS platforms +(RiscPC/A7000/A7000+) running RiscOS, but may be relevant to futures +Acorn hardware or other hardware running RiscOS. + +0 Before you start + +Read this document and any other accompanying documentation +completely before continuing. + +1 Requirements + +1.1 Hardware + +Refer to the NetBSD installation notes for a list of supported hardware. + +1.2 Software + +You will need the following RiscOS software: + + A program that will unpack sparchives. We recommend that you + get David Pilling's !SparkPlug. A selfextracting version of this + can be found on the Acorn ftp site (ftp://ftp.acorn.co.uk), and + also at David Pilling's W3 site + (http://www.pilling.demon.co.uk/soft.html). + + A program that can uncompress gzip files: + + SparkFS from David Pilling (commercial) (v1.28 for + SA-110). + + !Gzip from HENSA (micros.hensa.ac.uk). + + There is also a command line version of gzip available + that Laurent Domisse has patched to work on SA. This is + available from: + http://www.users.dircon.co.uk/~arcangel/files/index.html + + A program to report your disk's geometry: + + Not really needed you can simply boot the installation + kernel and look for the geometry in the boot messages. + + Sergio Monesi's fsck suite (a good thing to have around + anyway). Available from: + http://cdc8g5.cdc.polimi.it/~pel0015/fsck.html + + !Zap (The read disk facility). Available from HENSA. + + The partition software/formatter for your desired installation + target: + + IDE disks on motherboard interface: !HForm + IDE disks on Simtec interface: UNKNOWN + IDE disks on ICS interface: UNKNOWN + IDE disks on RapIDE interface: UNKNOWN + Acorn SCSI cards: ScsiDM + Power-tec SCSI cards: !PowerMgr + Cumana SCSI-2: !SCSIMgr + oak SCSI-1 card: UNKNOWN + MCS Connect32 SCSI: UNKNOWN + Morley SCSI: UNKNOWN + +Additionally you will require the following: + + An installation kernel for your platform: + + RiscPC: UNKNOWN + A7000(+): UNKNOWN + + The Bootloader and RiscOS tools: bootloader.arc (This should + be pre-extracted if you're installing from CDROM). + + The NetBSD/arm32 distribution sets (Will be on the CDROM, or + available from your nearest NetBSD ftp site). + + A hardcopy of this document, along with a hardcopy of the + NetBSD installation instructions "INSTALL"). + +2 Preparing your hard disk + +Terms: + +Device: The actual physical hard disk +Partition: A section of a device. +File system: A structured partition that is able to hold files. +Disc: A RiscOS file system in a partition. There can be + more than one Disc per Device. + +You will have to decide which device you wish to install NetBSD on. +You will also have to decide whether you want to split the device +between one or more RiscOS discs and NetBSD or dedicate a whole +device for NetBSD. + +In making this decision you should consider the possibility that if +NetBSD is incorrectly configured on a shared device then your shared +data is at risk. + +It is still recommended that if you decide to dedicate a device to +NetBSD that you set aside a small RISC OS partition at the beginning +of the device. This is a useful place to store the RiscOS side of +NetBSD, and will make the use of UnixFS easier to configure. If you +do decide to create a minimal RiscOS partition at the beginning of +the device, a size of 10-20 MB is recommended (some partitioning +software has problems with partitions smaller than this). + +The point is that you will have to repartition your device to make +room for a separate partition after the RISC OS one for NetBSD. This +means backing up your device, re-partitioning it and then copying all +the data back afterwards. We recommend that you only copy the needed +data back and put off installing the rest until you have NetBSD up +and running. This way you will save yourself a lot of work if +something goes wrong and you have to start all over again. + +2.1 Sharing your device + +2.1.1 Acorn IDE + +Use !HForm for this interface. This is a program that is delivered +with your computer and is located in the Utilities directory on your +harddisc. + +With this software you only have the possibility of using one +partition for RISC OS, so you have to set the rest aside for NetBSD. + +Use this procedure to set up your device: + + Start !HForm by double-clicking on it's icon. + + Choose the "custom" or "other" option when prompted (usually + the last). + + Use the default values for the geometry but do not enter the + full number of cylinders. Just enter the number you want to + use for RISC OS. Make a note of this number. + + Continue to accept the default answers until you're asked + whether you want to format or initialise, choose initialise. + + Go to the section about running bb_riscbsd. + +2.1.2 Cumana SCSI-2 card + +It is recommended that you use a newer version of !SCSIMgr (newer +than v1.55) since this will be easier to use when you want to leave +part of the device unused by RISC OS. You should check for the latest +version of this software at the following URL: +http://www.cumana.demon.co.uk + +You need to create one or more RISC OS partitions, and you do it in +in the following way: + Run !SCSIMgr by double-clicking on it. + + Select the device you wish to repartition. + + Click on the clear icon in the partitions subwindow. + + This will give you a dialogue box where you can specify the + size of the RISC OS partitions. Do not select all since you + want to use part of it for NetBSD. + + Enter the amount of the device you wish to reserve for + RiscOS. This will be the whole device size less the amount + you want to reserve for NetBSD. Make a note of this number. + + If you like, split the RISC OS portion of the device into + several partition (you should only "see" the RiscOS portion). + + Click on Execute when you are happy with the partions. This + will create your partitions, and wipe you device. + + Go to the section about running bb_riscbsd. + +2.1.3 Alsystems Power-tec SCSI-2 card + +You must use the !PowerMgr program to partition the device. + +The RISC OS partitions should be called RiscOs:, and the NetBSD one +should be called Empty:. + +Here is the procedure you should use: + Start !PowerMgr by double-clicking on its icon. + + Click on advanced in the main window + + Click on Define/create partitions + Click on the device you want to set up for NetBSD + + Set up the RISC OS partitions as RiscOs: and the + remaining one as Empty: + + Click on each figure and press return + + Click on partition drive + + Click on yes to warning as you really want to wipe + the device + + Click on yes to proceed, this will lead you to the + partition init. + + Partition init + Set a tick on all RiscOs: partitons, give them a name + and set LFAU to auto. + + Unset the tick on your Empty: partition. + + Click on Inititialize selected partitions. + + Click on yes to proceed init as you want to wipe the + selected partitions + + Click on yes to proceed to configure + + Configure + Here you should set up the RISC OS partitions as you + like them. Normally the default will be ok. + + Click on configure. This will configure your computer + and give you access to the Discs. + + You *Must Not* run bb_riscbsd + +2.1.4 Acorn SCSI card + +You can only have one RISC OS partition with this card. The rest has +to be set aside for NetBSD. + +This card does not have a friendly WIMP-based interface on the SCSI +management program, but the command line version is very good. You +should run this in a task window (hit CTRL-F12): + dir + + scsidm + +You will get the following prompt: +scsidm> + +Now you should enter the following commands: + probe (to see which devices are available) + + device (replace with the no of your device) + + section (to divide the device between RISC OS and + NetBSD) + Answer yes to the question: + Include RISCiX partitions? + + Enter the size of the RISC OS area in blocks + (sectors) + + SCSIDM will round this up to the nearest cylinder + boundary. + + Answer yes to the question: + Do you really want to section device ? + + This will section the device into two partitions. + + quit + + Go to the section on running bb_riscbsd + +2.1.5 Other interfaces + +It may not be possible to partition devices on other interface. If +you are using a different interface you have 2 options: + Try to work out how to partition devices on it + + Use the entire device for NetBSD + +2.2 Using a whole device for NetBSD + +As a safety precaution NetBSD/arm32 looks for a filecore bootblock +at the beginning of any device it labels. If it finds one and it +looks as though it is in use then NetBSD/arm32 will not touch it. + +Because of this, if you've ever used your device for RiscOS, you will +need to invalidate this bootblock. + +To do this you need to: + Be absolutely sure you want to do this + + run bb_trash and follow the instructions + +Ensure that this device is now not configured for RiscOS. + +You are now ready to boot NetBSD and continue the installation. + +3 Running bb_riscbsd + +When you run this program, you will first be asked whether you are +installing to an ADFS drive or a SCSI drive. You can just press A or +S respectively. (The bb_riscbsd program assumes that you are using a +non-Acorn SCSI card, so if you are using an Acorn card, then you may +have to edit this program and replace CSI_DiscOp with SCSIFS_DiscOp.) + +Then you will be asked which disc you want to install NetBSD on. This +*must* be the first disc on the device. bb_riscbsd will now +scrutinize the device and see how it has been laid out. + +It will then tell you how much of the device is occupied by RiscOS in +cylinders, and you will then be asked for the NetBSD starting +cylinder. Normally you should just enter the number given to you +since the RISC OS starting cylinder is 0 and therefore the last +cylinder in use is one less than the figure given. If no figure is +displayed, then your partitioning software failed to fill in the +bootblock completely (it doesn't have to do this for you but most do) +or you selected the wrong device. If you are convinced that this is +the correct device then you must calculated a cylinder offset using +the numbers noted down during partitioning (if it is not a whole +number *always* round up, you might waste a little of the device but +it'll all be safe). + +Make a note of this number. + +bb_riscbsd will make a backup of the original bootblock, but it +can be non-trivial to put it back. + +4 Booting + +Now that your device is ready for the installation you need to +unpack the bootloader archive (bootloader.arc, if you're installing +from CDROM then this should be unpacked already), copy it to your +harddisk and run the bootloader (!BtRiscBSD). + +4.1 Configuring !BtRiscBSD before installation + +!BtRiscBSD should come configured ready for installation. + +4.2 Running !BtRiscBSD + +Double click on the !BtRiscBSD icon and then on the iconbar icon to +open the Configuration window. + +Drag the kernel for your platform to the kernel name box and hit boot. + +NetBSD should now start to boot, install NetBSD as per the NetBSD +installation notes. + +4.3 Configuring !BtRiscBSD after installation + +Run !BtRiscBSD as before and bring up the configuration window. + +Set the kernel as UnixFS:$.netbsd and set the native boot option (if +the boot fails use a copy of the installed kernel (/netbsd) from +RiscOS. + +Set "Root device", "swap device" to the partitions you used for the +installation. + +Set multi user mode. + +Ensure the RAMDISK is set to 0. + +Click save. + +Click Boot. + +5 Advanced stuff + +5.1 Using UnixFS to copy the sets. + +Once the required sets are installed and you can boot from your +newly installed NetBSD setup, you can use UnixFS to copy the +remaining sets from RiscOS to NetBSD. + +In order to be able to use unixfs to transfer the sets you must have +a certain setup. + +1) You must have the RiscOS disc that corresponds to the NetBSD + device configured (eg *con. IDEdiscs 2) even if it has no RiscOS + section. +2) If you have RISC OS 3.5 without the new FileCore, then you must + also have the NetBSD filesystem *completely* below the 511MB + boundary of the device. +3) You must know the SWI base of the _DiscOp SWI. Here + is SCSIFS, SCSI or ADFS depending upon which controller + type you have you NetBSD device on. + Some common ones: + Power-tec SCSI-2 card: &40980 + RapIDE: &4BBC0 + + There are small obey files for some interfaces supplied with UnixFS. +4) Have given the directory you want to write into write permission for + everyone. This should have been done above. For example to make + /usr/distrib world writable type (as root): + chmod 1777 /usr/distrib + +To mount a Unix partition: + +1) Double-click on the unixfs_res module to load it. +2) Run a unixfs_mount command to mount the partition. +3) Open the root directory by double-clicking on the openroot file. +4) Open the distrib directory and just copy the sets to this. +5) Shut down unixfs by double-clicking on the kill_unixfs file. THIS + STEP IS VERY IMPORTANT as it works like dismount onMS-DOS floppies. + +The difficult step here is step number 2). If you are using an +ADFS IDE disc, then you can just double-click on one of the +following obey files (always choose the RiscOS disc number that +corresponds to the *first* disc on the NetBSD device): +- MountHD4a (ADFS::4 drive, not disc, root filesystem) +- MountHD4e (ADFS::4 drive, not disc, /usr filesystem) +- MountHD5a (ADFS::5 drive, not disc, root filesystem) +- MountHD5e (ADFS::5 drive, not disc, /usr filesystem) + +If you are not using an ADFS IDE device, you need to create such +an obey file yourself. We recommend that you copy one of the +above and change that. These files normally only contain a +unixfs_mount command. If you go to the command line (or a task +window), and you type *help unixfs_mount you will see that the +unixfs_mount command has a very incomprehensible syntax. + +The unixfs_mount command normally only takes one argument. That +is composed of the following: +(discop_swibase + (disc << 3) + partition) + +To mount the root partition of third Power-tec SCSI-2 disc the +following commands can be used in task window (hit CTRL-F12) to +find the argument to unixfs_mount: + *basic + PRINT ~(&40980 + (6 << 3) + 0) + QUIT + +The PRINT command calculates the value to use and will in this +context give the value 409B0 which also is in hexadecimal. The +interesting things above are: +- &40980 The SWI base for SCSIFS_DiscOp. +- 6 The disc number in RISC OS. +- 0 The RiscBSD partition no. with a=0, b=1 etc. +- ~ Tell the PRINT command to show the result in hexadecimal. +- << Shifts the first number with the second number + places left. + In this case, it shifts 6 with 3 places to the left. +- & Denotes that the number is in hexadecimal. +- ( and ) Used to group the sub-expressions. + +When you have calculated the figure to give to unixfs_mount you +just change it in the copy of the file you made above and run it by +double-clicking on it. + +When you have mounted the unixfs filesystem, you can open the +directory and copy the sets to it. +Don't forget to copy the file "checksums" too. As its name suggests, it +contains checksums to check if the files are OK. + +When you are finished with the transfer, run the file +kill_unixfs to dismount the unixfs filesystem. + +Appendix A - Device naming + + +The names of the devices in NetBSD are not at all like the ones +in RISC OS. We will here try to explain the naming scheme used +in NetBSD. This is pretty much the same in all UNIXes, but +there will be some differences. NetBSD is derived from BSD and +differs from the ones that are derived from System V. Most of +the dominant operating systems in the UNIX market today are +based on System V (Sun Solaris, SGI Irix, HP HP-UX 10.xx, Linux +etc.). Some of them are actually hybrids of both. + +The filesystem in UNIX use the slash character (/) as the +directory separator. The top (or bottom if you like) directory +is called the root and is denoted by only the slash (/). All +absolute filenames are adressed starting with the root, so the +temporary directory is called /tmp. + +The devices in UNIX are addressed as special files in the +filesystem, and they all start with /dev, so e.g. the quadrature +mouse is called /dev/quadmouse. + +Also some devices can be adressed in two different ways; as a +raw (character by character) or block device. This is especially +true with discs, and they therefore have two different names. +The raw device is called the same as the block device except +that it has an 'r' in front of the name. E.g. the first internal +hard drive is called /dev/wd0 as a block device, but /dev/rwd0 +as a raw device. See also later. + +For now, the only needed devices are the storage devices, so we +will hereby describe the naming convention used for these. +Please note that when you have different partitions on a device, +they will get the same number in NetBSD, but different letters, +whereas in RISC OS they will get different numbers. See the +examples at the end of this section. + +The (block) device names are mostly composed of 4 characters: +1. The type + - w Winchester drives (i.e. standard ADFS drives) + - s SCSI drives + - c CD-ROM drives + - r RAM drives (obsolete in newer kernels) + - m Memory drives (only in newer kernels) + - f Floppy drives +2. A 'd' indicating a disc device +3. The number of the device of that type starting with 0. + - For IDE drives, the master will be 0, and the slave 1. + - For SCSI drives, the target ID will be used to +determine the number. They start on 0 and increase with +each device found. The drive with the lowest target ID will get +0, the second lowest target ID will get 1 etc. +Also, if you have different controllers, all devices on controller +0 (lowest expansion slot) will be added first. + - The CD-ROM drives act the same way as SCSI drives. + - The floppy drive is numbered as in RISC OS. + - At present you can only have one RAM drive, so it is 0. +4. The name of the partition. There are eight of these (along with + common allocations): + - a The root partition + - b The swap partition + - c The whole disc + - d Scratch (what are these?) + - e The first additonal partition. + i.e. if you have only /usr, then this will be /usr + if you have both /var and /usr this will be /var + - f The section additional partition. + i.e. if you have /var and /usr, this will be /usr + - g ???? + - h Previously the /usr partition? + +If you only have one partition on the drive this can normally be +accessed with either partition a (root partition) or c (whole +disc). This has not been verified to work. + +A couple of examples of how to map RISC OS names to NetBSD ones +(the partition names have been left out): +ADFS::0 fd0 +ADFS::1 fd1 +ADFS::4 wd0 +ADFS::5 (same drive as :4) wd0 +ADFS::5 (other drive than :4) wd1 +SCSI::4 sd0 +SCSI::5 (same drive as :4) sd0 +SCSI::5 (other drive than :4) sd1 + +So, if you have one ADFS IDE drive, and want to install NetBSD +at the after ADFS::5, you should still use wd0. If on the other +hand, ADFS::5 is a second drive, then you will have to use wd1. + +Appendix B - Acknowledgements + +This document was based upon the document +"Installing RiscBSD 1.2-Release" +(C) 1996 The RiscBSD Documentation Project + +That has the following acknowledgement: + +This manual has been written from scratch based on version 1.2 +of the installation manual that Mark Brinicombe wrote. + +It was mainly written by Kjetil B. Thomassen +(mailto:kjetil.b.thomassen@eunet.no) with contributions from: +Neil Hoggarth (mailto:neil.hoggarth@physiol.ox.ac.uk) +Markus Baeurle (mailto:emw4maba@gp.fht-esslingen.de) +Jasper Wallace (mailto:jasper@ivision.co.uk) +Mark Brinicombe (mailto:amb@physig.ph.kcl.ac.uk) +Scott Stevens (mailto:s.k.stevens@ic.ac.uk) +and a lot more people posting to the RiscBSD mailing list. diff --git a/distrib/notes/arm32/upgrade b/distrib/notes/arm32/upgrade new file mode 100644 index 000000000000..10289b0501c9 --- /dev/null +++ b/distrib/notes/arm32/upgrade @@ -0,0 +1,5 @@ +Upgrading from a previous version of NetBSD isn't currently supported by +NetBSD/arm32. If you are currently running NetBSD/arm32 then make a +FULL BACKUP of your current installation, and install NetBSD _VER from +scratch. Obviously some of the steps can be skipped (in particular, +hard disk partitioning) as they will already be done. diff --git a/distrib/notes/arm32/whatis b/distrib/notes/arm32/whatis new file mode 100644 index 000000000000..b41c0a3c8a02 --- /dev/null +++ b/distrib/notes/arm32/whatis @@ -0,0 +1,9 @@ +NetBSD/arm32 _VER is the first official binary release of NetBSD for the +arm32 platform, although binary release have been available in the past +under a different name (RiscBSD). + +The _VER release brings with it two major enhancements; full shared +library support, and soft-float library support. + +Because of this some of your existing binaries will require +recompilation. But the up side is that they should run faster. diff --git a/distrib/notes/arm32/xfer b/distrib/notes/arm32/xfer new file mode 100644 index 000000000000..f3bac28d0a3b --- /dev/null +++ b/distrib/notes/arm32/xfer @@ -0,0 +1,164 @@ +Installation is supported from several media types, including: + + Remote NFS partition + FTP + CDROM + DOS Floppy + Tape + +No matter which installation medium you choose, you'll need to have an +installation kernel (and possibly a boot application, see +"arm32//prep" for details). + +Note that, if you are installing or upgrading from a writable media, +the media can be write-protected if you wish. These systems mount a +root image from inside the kernel, and will not need to write to the +media. + +Obviously, the steps necessary to prepare the distribution sets for +installation or upgrade depend on which installation medium you +choose. The steps for the various media are outlined below. + +To install or upgrade NetBSD using CDROM, you need to do the +following: + + Find out (probably from the release notes supplied with the + CDROM) where the sets files are on the CDROM. + + Proceed to the instruction on installation. + +To install or upgrade NetBSD using DOS floppies, you need to do the +following: + + Count the number of "set_name.xx" files that make up the + distribution sets you want to install or upgrade. You will + need that number of 1.44M floppies. + + Format all of the floppies with DOS. DO NOT make any of them + bootable DOS floppies. (If the floppies are bootable, then + the DOS system files that make them bootable will take up + some space, and you won't be able to fit the distribution set + parts on the disks.) If you're using floppies that are + formatted for DOS by their manufacturers, they probably + aren't bootable, and you can use them out of the box. + + Place all of the "set_name.xx" files on the DOS disks. + + Once you have the files on DOS disks, you can proceed to the + next step in the installation or upgrade process. If you're + installing NetBSD from scratch, go to the section on preparing + your hard disk, below. If you're upgrading an existing + installation, go directly to the section on upgrading. + +To install or upgrade NetBSD using a tape, you need to do the +following: + + To install NetBSD from a tape, you need to make a tape that + contains the distribution set files, in "tar" format. If + you're making the tape on a UN*X-like system, the easiest way + to do so is probably something like: + + tar cf + + where "" is the name of the tape device that + describes the tape drive you're using (possibly /dev/rst0, or + something similar, but it will vary from system to system. + (If you can't figure it out, ask your system administrator.) + In the above example, "" are the + distribution sets' directories, for the distribution sets you + wish to place on the tape. For instance, to put the + "misc13", "base13" and "etc13" distributions on tape (in + order to do the absolute minimum installation to a new disk), + you would do the following: + + cd .../NetBSD-_VER # the top of the tree + cd arm32/binary + tar cf misc13 etc13 kern13 + + (Note that you still need to fill in "" in the + example.) + + Once you have the files on the tape, you can proceed to the + next step in the installation or upgrade process. If you're + installing NetBSD from scratch, go to the section on preparing + your hard disk, below. If you're upgrading an existing + installation, go directly to the section on upgrading. + +To install or upgrade NetBSD using a remote partition, mounted via +NFS, you must do the following: + + NOTE: This method of installation is recommended only for + those already familiar with using BSD network + configuration and management commands. If you aren't, + this documentation should help, but is not intended to + be all-encompassing. + + Place the NetBSD distribution sets you wish to install into a + directory on an NFS server, and make that directory mountable + by the machine on which you are installing or upgrading NetBSD. + This will probably require modifying the /etc/exports file on + of the NFS server and resetting its mount daemon (mountd). + (Both of these actions will probably require superuser + privileges on the server.) + + You need to know the the numeric IP address of the NFS server, + and, if the server is not on a network directly connected to + the machine on which you're installing or upgrading NetBSD, + you need to know the numeric IP address of the router closest + to the NetBSD machine. Finally, you need to know the numeric + IP address of the NetBSD machine itself. + + Once the NFS server is set up properly and you have the + information mentioned above, you can proceed to the next step + in the installation or upgrade process. If you're installing + NetBSD from scratch, go to the section on preparing your hard + disk, below. If you're upgrading an existing installation, go + directly to the section on upgrading. + +To install or upgrade NetBSD by using FTP to get the installation +sets, you must do the following: + + NOTE: This method of installation is recommended only for + those already familiar with using BSD network + configuration and management commands. If you aren't, + this documentation should help, but is not intended to + be all-encompassing. + + The preparations for this installation/upgrade method are + easy; all you make sure that there's some FTP site from which + you can retrieve the NetBSD distribution when you're about to + install or upgrade. You need to know the numeric IP address + of that site, and, if it's not on a network directly connected + to the machine on which you're installing or upgrading NetBSD, + you need to know the numeric IP address of the router closest + to the NetBSD machine. Finally, you need to know the numeric + IP address of the NetBSD machine itself. + + Once you have this information, you can proceed to the next + step in the installation or upgrade process. If you're + installing NetBSD from scratch, go to the section on + preparing your hard disk, below. If you're upgrading an + existing installation, go directly to the section on + upgrading. + +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. Please note that the /dev on + the floppy used for upgrades only knows about wd0, wd1, sd0, + sd1 and sd2. If you have more than two IDE drives or more than + three SCSI drives, you should take care not to place the sets + on the high numbered drives. + + At a bare minimum, you must upgrade the "base" binary + distribution, and so must put the "base13" 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.