From 8b5a68d83b0545607b1efeea476cb49b3941f315 Mon Sep 17 00:00:00 2001 From: lukem Date: Sat, 29 Jun 2002 09:38:44 +0000 Subject: [PATCH] remove obsolete arm32 docco --- distrib/notes/arm32/Makefile | 5 - distrib/notes/arm32/hardware | 295 ---------------- distrib/notes/arm32/install | 574 -------------------------------- distrib/notes/arm32/legal | 10 - distrib/notes/arm32/prep | 25 -- distrib/notes/arm32/prep.RISCOS | 560 ------------------------------- distrib/notes/arm32/upgrade | 3 - distrib/notes/arm32/whatis | 13 - distrib/notes/arm32/xfer | 3 - 9 files changed, 1488 deletions(-) delete mode 100644 distrib/notes/arm32/Makefile delete mode 100644 distrib/notes/arm32/hardware delete mode 100644 distrib/notes/arm32/install delete mode 100644 distrib/notes/arm32/legal delete mode 100644 distrib/notes/arm32/prep delete mode 100644 distrib/notes/arm32/prep.RISCOS delete mode 100644 distrib/notes/arm32/upgrade delete mode 100644 distrib/notes/arm32/whatis delete mode 100644 distrib/notes/arm32/xfer diff --git a/distrib/notes/arm32/Makefile b/distrib/notes/arm32/Makefile deleted file mode 100644 index 811cf8d0da60..000000000000 --- a/distrib/notes/arm32/Makefile +++ /dev/null @@ -1,5 +0,0 @@ -# $NetBSD: Makefile,v 1.3 2001/01/14 21:37:56 mycroft Exp $ - -MERGED_SRCS+=${.CURDIR}/../common/upgrade - -.include diff --git a/distrib/notes/arm32/hardware b/distrib/notes/arm32/hardware deleted file mode 100644 index ac26a7878ea1..000000000000 --- a/distrib/notes/arm32/hardware +++ /dev/null @@ -1,295 +0,0 @@ -.\" $NetBSD: hardware,v 1.7 2000/10/29 14:08:05 lukem Exp $ -. -.Nx*M -\*V runs on a number of systems with -.Tn ARM6 -or later processors, -with or without FPU coprocessor. The minimal configuration is said to -require 8 MB of RAM and 50 MB 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 65 MB without counting space needed for -swap space, etc), and to run X or compile the system, more RAM is -recommended. (8 MB of RAM will actually allow you to run X and/or compile, -but it won't be speedy. Note that until you have around 16 MB of RAM, -getting more RAM is more important than getting a faster CPU.) -. -.Ss2 Supported devices -.(bullet -offset indent -RiscPC/A7000(+) floppy controller -.It -IDE controllers -.(bullet -compact -Acorn motherboard IDE -.It -Simtec IDE controller -.It -RapIDE Issue 2 IDE controller -.It -ICS V5 & V6 IDE controller -.bullet) -.It -SCSI host adapters -.(bullet -compact -Cumana SCSI 2 -.It -PowerTec SCSI 2 -.It -MCS Connect32 SCSI 2 -.It -Acorn SCSI -.It -Oak SCSI I -.It -Morley SCSI I (uncached only) -.bullet) -.It -VIDC20 video -.It -RiscPC Motherboard serial port -.It -RiscPC Motherboard parallel port -.It -Ethernet adapters -.(bullet -compact -Acorn Ether1 -.It -Atomwide Ether3 -.It -ANT Ether3 -.It -ANT Ether5 -.It -Atomwide EtherA -.It -ANT EtherB -.It -Acorn EtherH -.It -I-cubed EtherH -.It -ANT EtherM -.bullet) -.It -Most SCSI disk drives -.It -Most SCSI tape drives -.It -CD-ROM drives -.(bullet -compact -Most SCSI CD-ROM drives -.It -Most ATAPI CD-ROM drives -.(Note -Some low-priced IDE CD-ROM 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 -.Nx . -.Note) -.bullet) -.It -Mice -.(bullet -compact -RiscPC quadrature mouse -.It -A7000 PS/2 mouse -.bullet) -.It -Processors -.(bullet -compact -ARM 610 -.It -ARM 700 -.It -ARM 700 + FPA11 -.It -ARM 710 -.It -ARM 7500 -.It -ARM 7500FE -.It -ARM 810. [*] -.It -SA110 -.bullet) -.It -Motherboards -.(bullet -compact -Acorn RiscPC -.It -Acorn A7000 -.It -Acorn A7000+ -.It -VLSI RC7500 -.It -Digital DNARD -.It -Intel EBSA285 -.It -Chalice CATS -.bullet) -.It -Other devices -.(bullet -compact -RiscPC keyboard -.It -A7000 keyboard -.It -RiscPC realtime clock -.It -VLSI RC7500 motherboard devices -.bullet) -.bullet) -. -.Ss2 Supported Digital DNARD devices -.(bullet -offset indent -compact -IDE -.It -Keyboard -.It -Mouse -.It -Ethernet -.It -Smartcard -.It -Audio -.It -Joystick -.bullet) -. -.Ss2 Supported Chalice CATS devices -.(bullet -offset indent -compact -ALI M1543 southbridge inc PS/2 keyboard & mouse, ide, serial -.It -Parallel, USB and ISA bus -.It -RTC -.bullet) -. -.Ss2 Supported Intel EBSA285 & Chalice CATS PCI devices -.(bullet -offset indent -PCI - PCI bridges -.(bullet -compact -DC21150 -.It -DC21152 -.It -DC21153 -.It -DC21154 -.It -Hint HB1 -.bullet) -.It -Digital DC21x4x-based PCI Ethernet adapters -.(bullet -compact -Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX) -.It -Cogent EM964 [b] -.It -Cogent EM4XX [b] -.It -Compex Readylink PCI -.It -DANPEX EN-9400P3 -.It -Digital Celebris GL, GLST on-board ethernet -.It -.Tn DEC -.Pq Tn Digital -PCI Ethernet/Fast Ethernet adapters (all) -.It -JCIS Condor JC1260 -.It -Linksys PCI Fast Ethernet -.It -SMC EtherPower 10, 10/100 (PCI only!) -.It -SMC EtherPower -.It -SVEC -.It -PN0455 -.It -SVEC FD1000-TP -.It -Znyx ZX34X -.bullet) -.It -Qlogic ISP [12]0x0 SCSI/FibreChannel boards -.It -Adaptec AHA-2910, 2915, 2920, and 2930C adapters -.It -Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs using the AIC-7770, -AIC-7850, AIC-7860, AIC-7870, AIC-7880 and AIC-789x chipsets -.It -Adaptec AHA-394x[U][W] cards [b] -.It -Adaptec AHA-3950U2 cards -.It -Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters -.It -NE2000 PCI ethernet adapters -.It -Universal Serial Bus -.(bullet -compact -UHCI host controllers -.It -OHCI host controllers -.It -Hubs -.It -Keyboards using the boot protocol -.It -Mice -.It -Printers -.It -Generic support for HID devices -.bullet) -.It -Video cards -.(bullet -compact -Diamond Stealth 3D 2000 Pro -.It -ATI Charger 4MB -.It -STB Velocity 128 -.It -Cirrus Logic 5446 -.It -IGS 2010 -.It -IGS 5000 -.It -S3 based interfaces -.bullet) -.bullet) -.Pp -Drivers for hardware marked with -.Dq [*] -are -.Em not -present in installation kernels. -.Pp -Other PCI devices may be supported by Intel EBSA285 & Chalice CATS but -have not been tested. -.Pp -Support for some devices is limited to particular kernels. eg there is no -SA110 support in A7000 kernels. -. -.Ss2 Unsupported devices -.(bullet -offset indent -compact -Acorn/Aleph1 PC cards -.It -Any SCSI card using a PowerROM -.It -Podule based serial ports -.It -Castle SCSI/Ethernet cards -.bullet) -.Pp -Drivers are planned for some of the above devices. diff --git a/distrib/notes/arm32/install b/distrib/notes/arm32/install deleted file mode 100644 index 8bd81c69ee71..000000000000 --- a/distrib/notes/arm32/install +++ /dev/null @@ -1,574 +0,0 @@ -.\" $NetBSD: install,v 1.7 2000/10/29 14:08:05 lukem Exp $ -.\" -.\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc. -.\" All rights reserved. -.\" -.\" Redistribution and use in source and binary forms, with or without -.\" modification, are permitted provided that the following conditions -.\" are met: -.\" 1. Redistributions of source code must retain the above copyright -.\" notice, this list of conditions and the following disclaimer. -.\" 2. Redistributions in binary form must reproduce the above copyright -.\" notice, this list of conditions and the following disclaimer in the -.\" documentation and/or other materials provided with the distribution. -.\" 3. All advertising materials mentioning features or use of this software -.\" must display the following acknowledgement: -.\" This product includes software developed by the NetBSD -.\" Foundation, Inc. and its contributors. -.\" 4. Neither the name of The NetBSD Foundation nor the names of its -.\" contributors may be used to endorse or promote products derived -.\" from this software without specific prior written permission. -.\" -.\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS -.\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED -.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR -.\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS -.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR -.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF -.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS -.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN -.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) -.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE -.\" POSSIBILITY OF SUCH DAMAGE. -.\" -Installing -.Nx -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. -.Pp -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 -.Nx -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.) -.Pp -If -.Nx -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 -.Nx -area of the disk and its offset from the -beginning of the disk. You will need this information when setting up -your -.Nx -partitions. -.Pp -You should now be ready to install -.Nx . -It might be handy for you -to have a pencil, some paper, and a calculator handy. -.Pp -The following is a walk-through of the steps you will take while -getting -.Nx -installed on your hard disk. If any question has a -default answer, it will be displayed in brackets -.Pq Dq [] -after the -question. If you wish to stop the installation, you may press -.Key CONTROL-C -at any time, but if you do, you'll have to begin the installation -process again from scratch. -.Pp -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.) -.Pp -If this doesn't work, ensure that you're using the correct -kernel for your hardware. -.Pp -Depending upon your platform and the method of loading the, -it may take a while to load the kernel. -.Pp -You will then be presented with the -.Nx -kernel boot -messages. You will want to read them, to determine your -disk's name and geometry. Its name will be something like -.Li sd0 -or -.Li 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 -.Nx 's -partitions. You will -also need to know the name, to tell the install tools what -disk to install on. -.Pp -While booting, you will probably see several warnings. You -should be warned that no swap space is present, and that -.Xr init 8 -cannot find -.Pa /etc/rc. -Do not be alarmed, these are -completely normal. When you reach the prompt asking you for a -shell name, just press -.Key RETURN . -.Pp -You will be asked if you wish to install or upgrade your -system or go to a shell prompt. Enter -.Ic install . -.Pp -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 -.Sq Ic y -and press -.Key RETURN . -.Pp -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. -.Pp -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 -.Li wd0 -for IDE disks, or -.Li sd0 -for SCSI -disks, is the default.) -.Pp -You will then be asked to name your disk's disklabel. The -default response is -.Sq Ic mywd -or -.Sq Ic 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. -.Pp -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, press -.Key CONTROL-C -and when you get to the shell prompt, restart the -install process by running the -.Ic 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. -.Pp -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 -.Sq Ic c -for cylinders, or -.Sq Ic s -for sectors. -.Pp -You will be asked for the size of the -.Nx -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!) -.Pp -If you are not installing on the whole disk, you will be asked -for the offset of the -.Nx -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. -.Pp -You will be asked to enter the size of your -.Nx -root partition -.Pq Pa / . -It should be at least 13 MB, but if you are going to -be doing development, 14-16 MB 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. -.Pp -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. -.Pp -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, -.Pa /usr . -(Machines used as servers will probably also want -.Pa /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 -.Pq Pa /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 -.Pa /usr . -.Pp -.Em 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 -.Nx , -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 -.Ic yes -at the prompt. -.Pp -The install program will now label your disk and make the file -systems you specified. The file systems will be initialized to -contain -.Nx -bootstrapping binaries and configuration files. -It will also create an -.Pa /etc/fstab -for your system, and mount -all of the file systems under -.Pa /mnt . -(In other words, your -.Pa / -(root) partition will be mounted on -.Pa /mnt , -your -.Pa /usr -partition on -.Pa /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. -.Pp -You will be placed at a shell prompt ( -.Sq Li # ) . -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. -. -.Ss2 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 -.Ic Set_tmp_dir , -and enter -the name of the temporary directory. (Don't forget -that if your disk is still mounted under -.Pa /mnt ; -you should probably pick a directory under -.Pa /mnt/usr . ) -.Pp -After you have picked a temporary directory, enter the -.Ic Load_fd -command, to load the distribution sets from -your floppies. -.Pp -You will be asked which floppy drive to use. Enter -.Sq Ic 0 -(zero) if you're using the first floppy drive, or -enter -.Sq Ic 1 -if you're using the second. -.Pp -You will be prompted to insert a floppy into the drive, -to have its contents copied to your hard disk. Do so, -and press -.Key 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, press -.Key CONTROL-C . -.Pp -Run the -.Ic Extract -command once for each distribution -set you wish to install. For instance, if you wish to -install the -.Sy base -distribution set, followed by the -.Sy text -distribution set, and finally the -.Sy etc -distribution set, use the commands: -.Pp -.Dl # Ic "Extract base" -.Dl # Ic "Extract text" -.Dl # Ic "Extract etc" -.Pp -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 -.Nx , -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 -.Ic rm set_name.?? -.Note) -.Pp -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. -. -.Ss2 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 -.Ic Set_tmp_dir , -and enter -the name of the temporary directory. (Don't forget -that your disk is mounted under -.Pa /mnt ; -you should -probably pick a directory under -.Pa /mnt/usr . ) -The default is -.Pa /mnt/usr/distrib . -.Pp -After you have picked a temporary directory, enter the -.Sy Load_tape -command, to load the distribution sets from -tape. -.Pp -You will be asked which tape drive to use. The -default is -.Li 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 -.Li rst1 , -and so on.) -.Pp -You will be prompted to press -.Key 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. -.Pp -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 -.Ic Set_tmp_dir -command again, and accept its default answer by -pressing return at the prompt. -.Pp -Use the -.Ic Extract -command to extract the distribution -set. For instance, if you're extracting the -.Sy base -set, use the command: -.Pp -.Dl # Ic "Extract base" -.Pp -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. -.Pp -Repeat the previous two steps for each distribution -set you wish to install. Change to the set's -directory, run -.Ic Set_tmp_dir , -and then run -.Ic Extract Ar set_name -to extract the set. -.Pp -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. -.Pp -.Ss2 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 -.Ic Set_tmp_dir , -and enter the name of the temporary directory. (Don't forget -that your disk is mounted under -.Pa /mnt ; -you should probably pick a directory under -.Pa /mnt/usr . ) -The default is -.Pa /mnt/usr/distrib . -.Pp -Configure the appropriate ethernet interface (e.g. -ea0, eb0, etc.) up, with a command like: -.Pp -.Ic ifconfig Ar ifname ipaddr -.Op Ic netmask Ar netmask -.Pp -where -.Ar ifname No is the interface name, like those -listed above, and -.Ar ipaddr No is the numeric IP address -of the interface. If the interface has a special -netmask, supply the word -.Ic netmask No and that netmask -at the end of the command line. (The brackets -indicate that those arguments are optional.) For -instance, to configure interface -.Em ea0 -with IP address -.Li 129.133.10.10 , -use the command: -.Pp -.Dl # Ic "ifconfig ea0 129.133.10.10" -.Pp -and to configure interface -.Em eb0 -with IP address -.Li 128.32.240.167 -and a special netmask, -.Li 0xffffff00 , -use the command: -.Pp -.Dl # Ic "ifconfig eb0 128.32.240.167 netmask 0xffffff00" -.Pp -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: -.sp -.Ic route add default Ar gate_ipaddr -.sp -.No where Ar gate_ipaddr -is your gateway's numeric IP address. -.Pp -If you are NFS-mounting the distribution sets, mount -them on the temporary directory with a command like: -.sp -.Ic mount -t nfs Ar serv_ipaddr:dist_dir\ tmp_dir -.Pp -where -.Ar serv_ipaddr -is the server's numeric IP address, -.Ar dist_dir -is the path to the distribution files on the server, and -.Ar tmp_dir -is the name of the local temporary directory. -.Pp -Once this is done, proceed as if you had loaded the -files from tape, changing to the appropriate -directories, running -.Ic Set_tmp_dir , -and running -.Ic Extract -as appropriate. -.Pp -If you are retrieving the distribution sets using ftp, -change into the temporary directory, and execute the -command: -.Pp -.Ic ftp Ar serv_ipaddr -.Pp -where -.Ar serv_ipaddr -is once again the server's numeric -IP address. Get the files with FTP, taking care to -use binary mode when transferring the files. -.Pp -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.) -.Pp -.Ss2 To install from CD-ROM -First create a mount point so that you can mount the -CD-ROM: -.Pp -.Dl # Ic "mkdir /mnt/cdrom" -.Pp -If you get an error here of -.Dq "mkdir: /mnt/cdrom", -don't worry it just means that you didn't need to create the -directory. -.Pp -Then all you need to do is mount the CD-ROM. -For the first CD-ROM drive use: -.Pp -.Dl # Ic "mount -rt cd9660 /dev/cd0a /mnt/cdrom" -.Pp -Or, for the second use: -.Pp -.Dl # Ic "mount -rt cd9660 /dev/cd1a /mnt/cdrom" -.Pp -Once this is done, extract the required sets as -described in the -.Sx "To install from floppy" -section, but -ensure that you set the temporary directory to the -location of the sets on the CD-ROM (usually -.Pa /cdrom/distrib , -but check the release notes that came with the CD). -.Pp -.Ss2 Completing your installation -Once you have finished extracting all of the distribution sets -that you wish to install, and are back at the -.Sq Li # -prompt, you -are ready to configure your system. The configuration utility -expects that you have installed the -.Sy base -and -.Sy etc -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 -.Nx -system, -run the command -.Ic 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. -.Pp -.Em Congratulations, you have successfully installed -.Nx \*V . diff --git a/distrib/notes/arm32/legal b/distrib/notes/arm32/legal deleted file mode 100644 index e6cad9419617..000000000000 --- a/distrib/notes/arm32/legal +++ /dev/null @@ -1,10 +0,0 @@ -.\" $NetBSD: legal,v 1.8 2002/05/20 23:48:43 itojun Exp $ -. -.It -This product includes software developed by Advanced Risc Machines Ltd. -.It -This product includes software developed by Neil Carson. -.It -This product includes software developed by the RiscBSD kernel team. -.It -This product includes software developed by Scott Stevens. diff --git a/distrib/notes/arm32/prep b/distrib/notes/arm32/prep deleted file mode 100644 index 9bb0fedad4a7..000000000000 --- a/distrib/notes/arm32/prep +++ /dev/null @@ -1,25 +0,0 @@ -.\" $NetBSD: prep,v 1.5 2000/10/29 14:08:05 lukem Exp $ -. -First and foremost, before beginning the installation process, -.Em 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. -.Pp -Second, read and perform the instructions in -.Pa \*M/ Ns Ar platform Ns Pa /prep -that are specific to your platform for partitioning and booting (even if you're -dedicating a device to -.Nx ) . -.Pp -Finally, when you are happy with your -.Nx -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 -.Dq house-work . -.Pp -Your hard disk is now prepared to have -.Nx -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 deleted file mode 100644 index 9f5c3a9789d9..000000000000 --- a/distrib/notes/arm32/prep.RISCOS +++ /dev/null @@ -1,560 +0,0 @@ - $NetBSD: prep.RISCOS,v 1.7 2001/07/26 22:47:34 wiz Exp $ - -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 CD-ROM). - - The NetBSD/arm32 distribution sets (Will be on the CD-ROM, 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: partitions, 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 (press 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 CD-ROM 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 file system *completely* below the 511 MB - 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 on MS-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 file system) -- MountHD4e (ADFS::4 drive, not disc, /usr file system) -- MountHD5a (ADFS::5 drive, not disc, root file system) -- MountHD5e (ADFS::5 drive, not disc, /usr file system) - -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 (press 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 file system, 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 file system. - -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 file system 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 -file system, 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@thomassen.priv.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 deleted file mode 100644 index b29c72eec2f8..000000000000 --- a/distrib/notes/arm32/upgrade +++ /dev/null @@ -1,3 +0,0 @@ -.\" $NetBSD: upgrade,v 1.5 2000/10/10 12:55:17 lukem Exp $ -. -.so ../common/upgrade diff --git a/distrib/notes/arm32/whatis b/distrib/notes/arm32/whatis deleted file mode 100644 index 25a6fefb9005..000000000000 --- a/distrib/notes/arm32/whatis +++ /dev/null @@ -1,13 +0,0 @@ -.\" $NetBSD: whatis,v 1.7 2000/10/29 14:08:05 lukem Exp $ -. -.Nx \*V -on \*M is, as usual, also fully backward compatible with old -.Nx -\*M binaries, so you don't need to recompile all your local programs -provided you set the appropriate binary compatibility options in your -kernel configuration. -.Pp -New port-specific features include: -.(bullet -Addition of Xarm32VIDC Xserver for RiscPC and ARM7500 based systems. -.bullet) diff --git a/distrib/notes/arm32/xfer b/distrib/notes/arm32/xfer deleted file mode 100644 index c9bf9f9e5320..000000000000 --- a/distrib/notes/arm32/xfer +++ /dev/null @@ -1,3 +0,0 @@ -.\" $NetBSD: xfer,v 1.4 2000/10/10 12:55:17 lukem Exp $ -. -.so ../common/xfer