The Datafile PD-CD 4

home *** CD-ROM | disk | FTP | other *** search

/ The Datafile PD-CD 4 / DATAFILE_PDCD4.iso / unix / riscbsd / datafile / beta_txt < prev next >

Wrap

Text File | 1996-10-12 | 36.3 KB | 1,155 lines

============================================================================= RiscBSD Beta Release ============================================================================= Notes on installing the RiscBSD Beta Release. Author: Mark Brinicombe Some small additions by Dirk.vanGulik@jrc.it, for the DataFile, Boston. $Id: beta.txt,v 1.2 1996/02/08 22:17:22 mark Exp $ Prerequisites: A large X on a brick wall to indicate where you bang your head. System Requirements 8Meg + of DRAM 1Meg + of VRAM 300Meg + of spare IDE disc space Software requirements 1. A SCSI/IDE Hard drive its re-formatter and partitioning tool, such as: !hform - HD formatter (available with your machine) (For IDE drives, as come with the RPC.) ScsiDM - As comes with most Acorn SCSI drives !hform / !scsiutils / !scsiformat As come with most third party SCSI drives. 2. One or more kernels, in the kernel direcotry. bsd-XXX.gz - boot kernel inst-X.X.fs - installation kernel 3. This file *PRINTED* out !! 4. bootloader + tools 5. faq.txt - RiscBSD FAQ 6. Distribution sets sets/as252.* - OPT - Binutils 2.5.2 as and ld sets/base.* - REQ - base distribution set sets/bash.* - OPT - Bash shell sets/bison.* - OPT - GNU bison set sets/cc263.* - OPT - GCC 2.6.3 sets/comp.* - OPT - compiler related distribution set sets/config.* - REC - experimental configuration scripts sets/cvs.* - OPT - Concurrent Versions System sets/dip.* - OPT - Dialup Internet Protocol distribution set sets/etc.* - REQ - /etc distribution set sets/games.* - OPT - text console based games sets/gmake.* - OPT - GNU make 3.74 set sets/gs.* - OPT - Ghostscript, postscript previewer set sets/gsfonts.* - OPT - Ghostscript extra fonts set sets/httpd.* - OPT - NCSA HTTPD set sets/joe.* - OPT - Text editor set sets/kern*.* - REQ - kernel distribution sets sets/local.* - REC - local binaries and scripts sets/man.* - OPT - manual pages set sets/misc.* - REQ - miscellaneous distribution set sets/perl.* - OPT - Perl sets/shells.* - REC - Extra shells set (tcsh, bash, zsh) sets/sup.* - OPT - Software Upgrade Protocol sets/tcl.* - OPT - Tcl sets/tcsh.* - REC - Tcsh shell sets/tk.* - OPT - Tk sets/text.* - OPT - text distribution set sets/zsh.* - OPT - zsh shell sets/x11r6.* - OPT - X11R6 base distribution sets/x11r6man.* - OPT - X11R6 manual distribution sets/xarm15.* - OPT - Xarm 8bpp Xserver sets/xarm15m.* - OPT - Xarm 1bpp Xserver sets/xarchie.* - OPT - X11 interface to archie sets/xcontrib.* - OPT - X11 contrib programs sets/xdm.* - OPT - Xdm configuration sets/xftp.* - OPT - X11 FTP tool sets/xpaint.* - OPT - X11 paint package sets/xpixmap.* - OPT - Xpm editor sets/xpm.* - OPT - Xpm library for X11 sets/xrn.* - OPT - X11 news reader sets/axe.* - OPT - X11 text editor sets/chimera.* - OPT - X11 WWW browser sets/fvwm.* - OPT - FVWM window manager for X11R6 sets/gview.* - OPT - Ghostview, X11 postscript previwer sets/knews.* - OPT - X11 Threaded news reader REQ - Required set OPT - Optional set REC - Optional but recommended Note the required set etc is only needed for new installations, not upgrades. Each set is a single compressed tar file that has been split into small chunks that will fit on 1.44Meg DOS floppies. This file will attempt to explain how you install a beta release of RiscBSD. (Note: It may not work, or these instructions may be wrong :-)) Ok, The first thing is to allocate disc space for RiscBSD. We (the Datafile) have found it to work on IDE (as supplied with the RPC) as well as Cumana and Powertech SCSI. RiscBSD will co-exist with ADFS on the same disc, so you do not need to allocate a complete disc to RiscBSD. However, RiscBSD *requires* its own partition. This partition lives after the ADFS part of the disc. The implication of this is that in order to share a disc with ADFS, the ADFS partition will not occupy the whole disc i.e. you will have to reinitialise the ADFS partition to leave room above it for RiscBSD. Alternatively, and highly recommended, you can use a whole disc for RiscBSD. This file will use an installation on a Conner CFS420 HD (826 cyls, 16 heads, 63 sects/track) connected as drive 5, with half the disc for ADFS as an example. Ok. so step 0 is... 0. Print this file out. Since you are going to be booting RiscBSD later etc. you will not be able to keep referring back to this file so make a paper copy now :-) Step 1... 1. Decide which disc to install on and how you are going to split the disc between ADFS and RiscBSD. You should seriously consider getting an extra drive completely devoted to RiscBSD ! Since alpha/beta release users are going to want to play and compile things I would suggest that they have a minimum of 200Meg. See Appendix A/B for details on the sizes of various directories. Step 2 ... Copy the 'bb-riscbsd' utility to a floppy or onto a location reachable *after* you have re-initailised the hard-disk. (You can use the copy on PDCD_4 so there is no need to copy this file) Backup your drive and then reinitialise the ADFS part with !Hform, specifying the new size for the ADFS section e.g. 413 cylinders (210Meg) on a CFS420A drive (which has 826 cylinders). i.e. half the disc. Or if you are using SCSI, use the appropriate tool; to re-format and partition. Do *write* down the cylinder numbers !. Unless you know what you are doing; the *first partition should be ADFS, the second is left for RiscBSD. Run bb-riscbsd from and check that it 'sees' the filecore at the beginning; and gives you the right size. Specify the offset onto the next partition for RiscBSD. (So in the above example you would use 413 as the offset; 0..412 being in use for ADFS/Filecore. Step 3 ... 3. Put all your backed up stuff back on the disc. (Actually this can wait.. and it might be best to do it *after* unix is installed because you might have to re-do this if you got some number/cylinder offset wrong.) Ok now we can install the RiscOS based bits (bootloader) and a kernel onto the ADFS/Filecore part of the HD (or any other HD). Step 4... 4. Create a RiscBSD directory on the ADFS partition and extract the file riscos.spark into it. Copy the kernel files into the directory and decompress them. Run the basic program bb_riscbsd in the misc subdirectory. This will prompt you for the type of filesystem, the drive and starting cylinder of the RiscBSD section. The program will tell you how big the ADFS part is before prompting, so for our example this would be 413. This means that the ADFS part occupies cyls 0-412, so RiscBSD will start at 413. Ok now we have part of the disc reserved for RiscBSD. Before we can boot we need a root floppy. Step 5... Locate the inst-11.fs file. Under RiscOS this can be written to a floppy with the flopwrite program. e.g. *format 0 DOS/Q *dir $.riscbsd *misc.flopwrite -t=1440 inst-11 Ok now we are now ready to rock and roll :-). The next stage is to boot RiscBSD and see what happens :-) Step 6... 6. Run the !BtRiscBSD application. An icon will be installed on the iconbar. Click select on the icon to open the configuration window. You should boot riscbsd via the ramdisc. This should be the default configuration for the bootloader but just in case this means that you need to set the root device to /dev/rd0a and set the ramdisc size to 1440K (This should happen automatically when you select /dev/rd0a) The swap device should be set to either wd0b or wd1b depending on which disc you are using for RiscBSD (for our example - wd1b). Also select single user mode. Insert the root floppy. Drag the kernel file you wish to boot into the window (It may be worth saving this configuration) and then click on boot. Ok, if all goes well the kernel will start to boot. The boot will start by report the memory located along with various information messages and a few debugging messages. This is the arm initiation code. The "real" startup point is when the copyright message is printed. After probing the CPU/FPA in cpu_startup() the kernel will attempt to configure the appropriate device drivers for the hardware it finds. Note: Whilst probing the IDE controller there may be a pause if you only have one drive attached. After probing the hardware and configuring the devices the kernel will attempt to mount the root filesystem and run init. NOTE: remember the cylinders/heads/sectors reported for the drive you wish to install on, you will need the later. (Our example will have reported 826 cyls, 16 heads and 63 sects/track) So if you install on IDE, the line to look for looks like wd0: 826 cylinders, 16 heads, 64 sect and 512 bytes/sector For SCSI, look for something like sd0: 826 cylinders, 16 heads, 64 sect and 512 bytes/sector Write these numbers down! If nessesarry repeat the above to get a second look/verification. If all has gone well RiscBSD has booted given you lots of information during bootup, found all your hardware and will be sitting with the prompt Enter pathname of shell or RETURN for sh: At this point things are looking good :-) Step 7... Pressing return will start the installation script Now we will have lots of questions to answer Step 8... 8. Ok at this point you should have some text on screen saying welcome to the NetBSD 1.1 installation program. and lower down Progress with installation? [n] Pressing return will abort the installation and drop you into a sh shell. To continue type y and press RETURN Now we will have to answer questions about the harddisc. Step 9... 9. Ok the next prompt should be What kind of disk will you be installing on ? [IDE] At this point you can just press return as currently only IDE drives are supported. Now select the device Step 10... 10. A list of possible devices you can install on will be printed. (For the moment this will just be wd0 and wd1) and you will have the prompt Which disk would you like to install on? [wd0] enter either wd0 or wd1 and press RETURN depending on which HD you are installing on. (for our example it will be wd1) Naming the disc Step 11... 11. Next prompt is What kind of disk is it? (one word please) [mywd] You should enter the name/type of the disc (no spaces allowed) for our example we could use cfs420a or my420slave or cfs420slave etc. Specifying the geometry Step 12... 12. We now enter the geometry of the HD. There will be 4 prompts for this. Number of bytes per disk sector? [512] This value is correct if the HD block size is 512 bytes so you can just press RETURN. Number of disk cylinders? Enter the total number of cylinders as reported during boot. For our example this will be 826. Number of disk tracks (heads) per disk cylinder? Enter the number of heads reported during boot. For our example this will be 16. Number of disk sectors per disk track? Enter the number of sectors reported during the boot. For our example this will be 63. You will them be told how many bytes there are per cylinder. (for the example this will be approximately 512K) Specifying the partitions. Step 13... 13. The next prompt will ask you how you want to specify the partition sizes. This can either be in cylinders or sectors. Cylinders is recommended as ideally all partitions should start and finish on cylinder boundries. What units would you like to use? [cylinders] Just press RETURN Step 14... 14. We now need to specify how much of the disk is NetBSD. Size of NetBSD portion of disk (in cylinders)? Ok this will be the total number of cylinders minus the number of cylinders used by ADFS. For example this will be 826 - 413 = 413 Offset of NetBSD portion of disk (in cylinders)? Ok this will be the starting cylinder of the NetBSD part. This will be the cylinder number you specified when running the bb_riscbsd program under RiscOS. For our example it will be 413. Specifying the root size Step 15... 15. You will be informed how many cylinders are left to be allocated. You will then be prompted for the size of the root partition. Root partition size (in cylinders)? Enter the number of cylinders you wish to use. For our example we will allocate about 30Meg for the root partition (we will include /var on the root partition). This will be about 60 cylinders. See appendix B for partition size information. Specifing the swap size Step 16... 16. You will be informed how many cylinders are left to be allocated. You will then be prompted for the size of the swap partition. Swap partition size (in cylinders)? Enter the number of cylinders you wish to use. For our example we will allocate about 24Meg for the swap partition. This will be about 50 cylinders. Specifying other partitions. Step 17... 17. You will be informed how many cylinders are left to be allocated. You will then be prompted for the size of the next partition. Next partition size (in cylinders)? Enter the number of cylinders you wish to use for the next partition. This will either be /var or /usr depending on whether you have allowed space for /var on the root partition. You will them be prompted for the mount point. Mount point ? Enter the required mount point for the partition. For our example we will allocate the rest of the NetBSD space to /usr so we will enter 303 cylinders and a mount point of /usr more partitions ? Step 18... 18. If you have not used up all the space you will be prompted for another partition (see Step 17) Now all the partitions have be specified it is time to write the disklabel. Step 19... 19. You will get the prompt THIS IS YOUR LAST CHANCE Are you sure you want NetBSD installed on your hard drive? (yes/no) Ok well thats a tough question :-) Entering no will abort the installation. For our example we will of course enter yes. The message will be Here we go... Step 20... 20. Start biting your nails :-) This will either work now or not :-) If not, start crying ;-) The install script should now start printing information about what it is doing. Firstly it will install a disklabel. Then it will attempt to newfs the partitions created. This may take a little while depending on the sizes of the partitions. During newfs the block numbers of all the superblock backups will be printed. After newfs it will copy the base binaries from the floppy to the root partition so that you can boot from the HD. Hopefully no errors will have occurred during this session. If everything is ok, some text will be printed before returning you to the shell. There should now be enough on the harddisc to allow you to boot from it. At the point we can test this :-) If you would rather go ahead and install the distribution sets before booting from the HD skip step 21. Step 21... 21. At the shell prompt type halt The kernel will halt and reboot RiscOS. Change the rootdevice in the bootload config window. You can also remove the ramdisc by setting it's size to zero. Boot again in single user mode. This time after pressing RETURN at the prompt Enter pathname of shell or RETURN for sh: All the created partitions will be checked by fsck and then the shell will be entered. That was the hard work done. Despite how complex it seems it should take less than 5 minutes to do :-) Now all you have to do is get all the sets onto the HD so you can install them :-) Ok assuming everything above worked you should now be in a shell having booted RiscBSD off the harddisc. The next stage is to make the sets available to RiscBSD for installation. If you did not do stage 21 and are still running with the ramdisc mounted as the root filesystem then the following should still apply. The set install proceedure for the beta release should detect this and take that into consideration. This text file will either consider installing the sets from floppies or from a CDROM. If you are going to install from floppies you need to put the set files onto a collection of 1.44MB floppy discs. Each distribution set has at least a .set file and a .00 file. In addition there may be .01 .02 etc. for sets that will not fit on a single floppy. If you are installing from CDROM you need to mount the CDROM. Check the instructions supplied with the CDROM for mounting details. Step 22... 22. If the backspace key is not working correctly on the command line then type stty erase ^H and press return. NOTE: This will enable the backspace key to work properly. Normally this sort of this would be taken care of during the login but in single user mode it may not have been. Making the sets available to the installer. If you are installing from CDROM goto step 27. Steps 23 to 26 Transfer the sets from floppies to the HD. Step 23 Start the installer 23. At the prompt type /usr/local/sbin/inst This will run the RiscBSD installer script. This installer can be used to transfer the set files from floppies to the HD and also handles installing the sets. Step 24 24. The installer will present a menu of 6 or more options. Select the menu option "Load distributions onto HD" (This will normally option 2) This will take you into another menu with 4 or 5 options. These options allow you to simply transfer files from floppies into a distribution directory on the HD from where they can be installed. Step 25 Set the distribution directory 25. Typically the distribution directory will be /usr/distrib on the HD. The installed menu option to set the distribution directory will show you the current setting. If you have booted off the harddisc then this should be /usr/distrib. If you booted off the floppy via the ramdisc then this should be /mnt/usr/distrib as the harddisc is mounted on /mnt when the bootstrap binaries are transferred from from the rootdisc to the harddisc. If the distribution directory is not set correct or you wish to change it do so now. Step 26 Actually copy the files 26. The installer gives you three methods of copying the files from floppies to the harddisc. Select the appropraite method depending on how you have copied the set files onto floppy disc. The normal way is to have copied them onto 1.44MB DOS floppies (option 2). The other 2 options support transferring the sets straight from tars files written to the floppies (avoiding the use of the DOS filesystem) Having selected an installation method you will be asked which floppy drive to use. Assuming a standard RiscPC is being use then this will be drive 0. You will then be asked to insert a floppy disc and press return. On pressing return the installer will copy all the files from the floppy to the distribution directory. You will then be prompted for the next floppy. Typing s at the prompt will terminate the process. If you have installed from floppies then skip step 27 and go directly to step 30. Step 27. Installing from CDROM 27. If you are installing from CDROM the first thing to do is to mount the CDROM. At the prompt type something like mount -r -t cd9660 /dev/scd0 /cdrom Check the mounting details supplied with the CDROM for the exact details. Step 28 Start the installer 28. At the prompt type /usr/local/sbin/inst This will run the RiscBSD installer script. Step 29 Set the distribution directory 29. Typically the distribution directory will be /usr/distrib on the HD. As we are installing from CDROM then we need to change the distribution directory to point to the distribution sets on the CDROM Use the set distrib directory (Option 1) on the installer menu to change the distribution directory to the CDROM distribution directory typically /cdrom/usr/distrib Check the instructions with the CDROM for exact details. Step 30 What have we got and are there any errors ... 30. Ok we now are now running the RiscBSD inst program and have either mounted and CDROM and set the distribution directory to point to it or we have loaded the sets from a collection of floppy discs into the distribution directory on the harddisc. Select the "Show distribution sets" option from the inst menu. This will list all the distribution sets found in the distribution directory. It will show the set name along with a brief discription of the set. If you have transferred the sets from floppy discs you may like to check that none of the set files are missing or corrupt. Select the option "Validate distribution sets". This will list the set names of all the available sets and will prompt you to enter a list. You can enter a space separated list of sets to validate or the set name "all" for all the sets. The installer will then check that all the parts of each of the specified sets are present and will check the checksums on each part. Any errors will be reported. The option "Verify distribution sets" can also be used but this is alot slower as tests the integrity of the compressed sets using gzip. This option should not normally be needed though. Step 31 Actually install something ... 31. Select the option "Install distribution sets" from the inst menu. The installer will list all the sets that are available for installation. You will then be prompted for a space separated list of sets to install. There are three special set names that can be used. The set name "req" can be used to install all the required sets. These are the sets "base etc misc text kern". The set name "std" can be used to install all the standard sets. These are the sets "base etc misc text kern man local" The set name all can be used to install all the available sets. NOTE: The sets will be installed in the order given at the prompt apart from the base set which will always be installed first. The optional sets do not have to be installed at this point. They can be installed at a future date using the inst program. Having installed the required set you may like to quit and find out how much disc space you have left before installing the option sets. How much space did I lose ? Step 31... 31. type at the shell prompt df -k installing the sets base, etc, text, misc and man should result in approx 9.5Meg used on / (/mnt) approx 61Meg used on /usr (/mnt/usr) The paths in brackets are the relevant ones if you booted of the root floppy. I've got bags of room left ;-) Step 32... 32. Other sets you may have pulled include all the X11R6 sets and the NetBSD source tree. If so you can install that now :-) Step 33... 33. Also the actual compiler and assembler have not yet been installed. The compiler and assembler distribution is split into three sets. The "comp" contains all the header files and libraries. The "as???" sets contain version ?.?.? of the assembler and linker The "cc???" sets contain version ?.?.? of the C and C++ compiler. Ekk I'm running out of space ! Step 34... 34. Once the distribution sets have been installed you can delete them from your HD. However if you installed from CDROM - oh dear, buy a new HD :-) Configuring the system Step 35... 35. Ok now everything has been install there are one or two things to configure. From the shell prompt type Configure and press return. Hostname config Step 36... 36. Ok the first prompt will be What is this machine's hostname? [unknown.host.domain] Enter the name of your machine. Step 37... 37. The next prompt will be What domain is this machine in ? Enter the domain name here. Step 38... 38. The next prompt will ask you if you have an ethernet interface. If you have ether1, ether3, ether5, etherb or etherh interface in your machine then you can configure it now. After responding yes to this question you will be prompted for some information about the interface. For reference, the following hardware corresponds with the following drivers. ether1 podule - ie ether3 podule - ea ether5 podule - ea etherB netslot - eb etherH netslot - eh After the network interface config the configure script will make all the special device files in /dev Then it's back to the prompt. Time zone configuration Step 39... 39. You may need to change the symbolic link /etc/localtime to point to your preferred timezone. Fix the bugs. Step 40... 40. The following commands will fix a few bugs in the beta release So far no bugs have been reported in the beta release... Try for a multiuser startup Step 41... 41. Type exit from the single user mode shell. init will then try for a multiuser mode startup. More configuration ? Step 42... 42. If you have installed the config set then you may like to try running the RiscBSD Configuration Manager. This provides options to configure timezones, network interfaces, nfs, resolver and users. The configuration manager can be run with the command /usr/local/sbin/rcm This is now the recommended configuration proceedure. In future RCM will be extended to support more configuration options. This section i.e. steps 43 to 7842 have not been written yet as my current research contract ends in a 3 months time and I have about 9 months of work left to do to finish it. Appendix A Package Compressed size Uncompress size as252 226702 552960 axe 1405776 3184640 base 19882724 45260800 bash 307400 788480 bison 123244 368640 cc263 2172029 5253120 chimera 604974 1464320 comp 2832589 10547200 config 12052 81920 cvs 349009 849920 dip 111448 276480 etc 60054 337920 fvwm 2000309 4577280 games 4763364 10813440 gmake 234611 665600 gs 786962 1925120 gsfonts 1714119 3409920 gview 533531 1198080 httpd 392081 1095680 joe 532992 1239040 knews 499240 1116160 local 200177 460800 man 827888 3287040 misc 1887975 6563840 perl 1501396 4833280 sup 303780 675840 tcl 394772 1648640 tcsh 273662 645120 text 1278299 3942400 tk 1315495 4341760 x11r6 18836638 49858560 x11r6man 715160 1300480 x11xv 970872 2334720 xarchie 597348 1382400 xarm15 829722 2170880 xarm15m 1054148 2775040 xcontrib 3880086 8724480 xdm 2778 20480 xemacs 10613054 38768640 ** Alpha2 set ** xftp 649660 1546240 xpaint 679017 1679360 xpixmap 581883 1351680 xpm 400376 911360 xrn 583260 1310720 zsh 224000 532480 Total 88114617 236072960 NOTE: The uncompresses size is the size for the uncompressed binaries and data files. It does not include filesystem overheads and block rounding. I did have a piece of paper with all the sizes of various directories written down. Anybody who has seen my desk will agree that it is probably lost forever now... Note these sizes are approximate and the for the src directories includes objects files as well. NOTE: These were the sizes for the alpha2 release so things may be a bit bigger now. Sizes are in blocks (512 bytes) /bin 5785 /sbin 8478 /etc 484 /var 4089 /usr/bin 45606 /usr/sbin 16997 /usr/libexec 6435 /usr/lib 2969 /usr/include 5961 /usr/src/bin 14629 /usr/src/include 712 /usr/src/lib 17885 /usr/src/sbin 15883 /usr/src/libexec 9007 /usr/src/usr.bin 54885 /usr/src/usr.sbin 28254 /usr/src/sys 34371 /usr/src/gnu 57369 /usr/share 9381 /usr/local /usr/local/NetBSD-current 51524 /usr/X11R6 /usr/X11R6/man Note: It is not difficult to fill up a 800 Meg partition :-) Appendix B - Suggested partition sizes / - 16Meg swap - 24Meg /var - 12Meg Sometimes simpler to put /var on / and make the root about 25-30Meg /usr - 200Meg+ If you want to even think about X then /usr - 300Meg+ If you want things like xemacs and TeX then /usr - 400Meg+ Appendix C - Useful commands ls -al - list all the files in a dir in long format df -k - list the mounted partitions and sizes in kilobytes (without -k sizes are in blocks) stty erase ^H - enable the backspace key in single user mode vmstat - general stats vmstat -i - interrupt stats vmstat -s - stats summary vmstat -m - memory stats ps -aux - process stats mount -t msdos /dev/fd0a /mnt - mount a msdos floppy on /mnt umount /mnt - unmount the device mounted at /mnt mount -r -t cd9660 /dev/scd0 /cdrom - mount a CDROM Appendix D - Miscellaneous Special keys / mouse buttons The left mouse button will slow down the speed at which text is printed The middle mouse button will freeze the console. ALT-Cursor up - scroll back through the VRAM ALT-Cursor up - scroll forward through the VRAM CTRL-ESC - force a kernel panic (Do no use this unless dire emergency) Floppies. Faster access times can be obtained if 1.44M floppies are formatted from a PC not from RiscOS (Note: the 486 card does not solve this as it uses RiscOS to format the floppies :-) Switching consoles ALT-F1 to ALT-F? will switch between any virtual consoles enabled. The X server is on console 9 so use ALT-F9 to switch to it. Appendix E - Help I am stuck !!! Have you checked the FAQ ? It may contain the answer you need. 1. Sometimes when halting / rebooting the kernel will freeze while syncing discs or will go mad reporting errors (again during the syncing/unmount phase. If this happens try pressing CTRL-ESC to attempt to scramble for the kshell (kernel debug shell) where you can try CTRL-D or reboot to reboot RiscOS. 2. You are getting weird errors from inetd etc. ermm kill inetd :-) unless you are using SLIP you probably will not be using networking stuff. This error occured on the alpha distribution and should not occur on the beta release. Appendix F - Using other kernels. The kernels directory in the beta release contains alternative kernels that you can use. Note, not all these kernel have the same device support. They may, however, provide better performance. To use a different kernel, just decompress it and drag the file into the bootloader config window. That kernel will them be used instead. Click the save button if you wish to save the new config. Once you have booted you may find that certain commands such as ps and vmstat will give errors or rubbish results. This is because they use the symbol table in the file /netbsd to get the addresses of any kernel variables they need. If you decide to stick with one of these other kernels you will need to copy it to /netbsd. Then after the next reboot the kernel in /netbsd will match with the kernel you booted. The recommended proceedure is that once you have completed the installation and have installed a kernel in /netbsd you should then use the native boot option in the boot loader. To enable this select the native boot option and specify the kernel filename of unixfs:$.netbsd Appendix G - The new installer inst is a new program to aid in the installation of the RiscBSD sets. it can be found in /usr/local/sbin/ It is aimed at replacing the installation method for the sets described above. Eventually it will be a general purpose installer/deinstaller. Currently it can not be used for the installation of the base set. Until the base and etc sets has been installed and the machine rebooted certain installer options (Validate) will not work. Once you have booted from the HD using the base set you can run the new installer i.e. /usr/local/sbin/inst This will give you a menu. 1. Set distrib directory (Currently ...) 2. Load distribution sets 3. Show distribution sets 4. Validate distribution sets (confirm checksums) 5. Verify distribution sets (integrity check) 6. Install distribution sets from ... Q. Quit Select 1 and specify the location of the distribution files. This will be the directory (probably /usr/distrib) where you copied the base set to. If you specify a directory that does not exist you will be prompted as to whether you want to create one. If you have not transferred all the sets to the HD yet, select option 2 This gives you a sub menu 1. Set distrib directory (Currently ...) 2. Load sets from msdos floppies 3. Load sets from tar floppies 4. Load sets from multi-volume tar floppies Q. Quit If you copies the sets onto msdos floppies select option 2. You will then be prompted to insert the floppies one at a time and they will be transferred to the hard disc. Once this has been completed you can return to the main menu. The other 2 options allow the sets to be transferred as either a single multivolume tar for or as a collection of floppy sized tar files. Once all the sets have be loaded onto the harddisc you can show the available sets by selecting option 3. This will produce a brief list of the sets and a description of their contents. Options 4 and 5 provide a means to check that the sets have been correctly transferred before you try to install them. If you are using inst to install the base set then option 4 will not be available. Both options will print out the available sets and will prompt for the names of the sets to check. Option 4 will then check that there are the correct number of parts to the set and that each part has the correct checksums. It will report passed or failed messages for each set. Option 5 will check the integrity of the sets using gzip. (This option is slower than just checksuming). Once you are happy that the sets are ok you can proceed to option 6. You will again be given a list of the loaded sets and prompted for the sets to install. Installation of those set will then proceed. Following installation you will return to the main menu where you could check and install other sets. Once the REQUIRED sets have been installed you don't have to install any other sets immediately. You can use the inst program at a later date to install other sets. Appendix H - The alpha2 install proceedure (Not really needed now) This install proceedure has been superceded by the inst program. 1. At the shell prompt type Set_tmp_dir and press RETURN. This runs a function in the shell script /.commonutils and will set the temporary directory for the files you will install. You will be prompted to enter a directory What directory should be used to find and/or store installation files ? [/usr/distrib] /usr/distrib is as good a place as any so just press return. Now type Load_fd and press RETURN. This is another shell util that will help with the process of copying from the floppies. You will be prompted for a drive. Ignore what it says about not being able to use the drive you booted from. (That only applies if you do this before reboot from the HD and even then if you use the ramdisc which is new (to NetBSD) (and exclusive to NetBSD/arm32 :-) it does not apply. Enter 0 at the prompt for the floppy drive to read from. You will them be prompted to insert a floppy and press return to copy it or CTRL-C to abort. When the contents of the msdos floppy have been copied you will be prompted to enter another floppy. Repeat this until all the files have been transferred from all the floppy discs. Install the files. Step 2... 2. Having transferred all the files and pressed CTRL-C at the insert floppy prompt from step 23 you should now be back at the shell. Type Tmp_dir and press RETURN to cd to the directory where all the files have been copied to. Typing ls <RETURN> will show you the files. I did not really need to mention that as anybody installing this version will know that already. Actually install something Step 2... 3. Type Extract base and press RETURN Again Extract is a shell function written for your convienience :-) You will be prompted as to whether you wish the files to be listed when they are installed. It is up to you whether you say yes or no but I also like to see lots of text going by :-) Assuming you typed yes, you will see the files being extracted from the base set and installed on your HD. Repeat the procedure with for comp text misc etc shells as cc and patch1. Note you do not need to install all these sets unless you want to. A list of which sets are required and which are optional is given at the beginning of the document. i.e. Extract comp Extract text Extract misc Extract etc Extract as Extract cc Extract config Extract local Extract kern???? where ???? is the alpha kernel version number Extract any other sets that were copied as well.