prep.RISCOS revision 1.18.2.2
1 1.18.2.2 pavel $NetBSD: prep.RISCOS,v 1.18.2.2 2007/12/14 21:15:53 pavel Exp $ 2 1.18.2.2 pavel 3 1.18.2.2 pavel These instructions are specific to NetBSD/acorn32 on Acorn RISCOS platforms 4 1.18.2.2 pavel (RiscPC/A7000/A7000+/NC's). 5 1.18.2.2 pavel 6 1.18.2.2 pavel Last updated for the BtNetBSD bootloader version 0.99a at 10 July 2002 by 7 1.18.2.2 pavel Reinoud Zandijk (reinoud (a] NetBSD.org), portmaster of NetBSD/acorn32. 8 1.18.2.2 pavel 9 1.18.2.2 pavel For a more detailed acknowledgement and list of contributers see Appendix B 10 1.18.2.2 pavel at the bottom. 11 1.18.2.2 pavel 12 1.18.2.2 pavel 13 1.18.2.2 pavel 14 1.18.2.2 pavel 0 Before you start 15 1.18.2.2 pavel 16 1.18.2.2 pavel Read this document and one of the INSTALL documents accompanying this 17 1.18.2.2 pavel document completely before continuing. There might be some things mentioned 18 1.18.2.2 pavel double but this document ought to help with the RISCOS installation 19 1.18.2.2 pavel specifically. 20 1.18.2.2 pavel 21 1.18.2.2 pavel 22 1.18.2.2 pavel 23 1.18.2.2 pavel 1 Requirements 24 1.18.2.2 pavel 25 1.18.2.2 pavel 26 1.18.2.2 pavel 1.1 Hardware 27 1.18.2.2 pavel 28 1.18.2.2 pavel Refer to the NetBSD installation notes and/or the web site 29 1.18.2.2 pavel http://www.NetBSD.org/ports/acorn32/ for a list of supported hardware. 30 1.18.2.2 pavel 31 1.18.2.2 pavel 32 1.18.2.2 pavel 1.2 Software 33 1.18.2.2 pavel 34 1.18.2.2 pavel You will need the following RiscOS software: 35 1.18.2.2 pavel 36 1.18.2.2 pavel A program that will unpack sparchives. We recommend that you 37 1.18.2.2 pavel get David Pilling's !SparkPlug. A self-extracting version of this 38 1.18.2.2 pavel can be found at David Pilling's W3 site 39 1.18.2.2 pavel (http://pilling.users.netlink.co.uk/free.html). 40 1.18.2.2 pavel 41 1.18.2.2 pavel A program to report your disk's geometry: 42 1.18.2.2 pavel 43 1.18.2.2 pavel Not really needed, you can simply boot the installation 44 1.18.2.2 pavel kernel and look for the geometry in the boot messages. 45 1.18.2.2 pavel 46 1.18.2.2 pavel Sergio Monesi's fsck suite (a good thing to have around 47 1.18.2.2 pavel anyway). Available from: 48 1.18.2.2 pavel http://cdc8g5.cdc.polimi.it/~pel0015/fsck.html 49 1.18.2.2 pavel 50 1.18.2.2 pavel !Zap (The read disk facility). Available from HENSA. 51 1.18.2.2 pavel 52 1.18.2.2 pavel The partition software/formatter for your desired installation 53 1.18.2.2 pavel target: 54 1.18.2.2 pavel 55 1.18.2.2 pavel IDE disks on motherboard interface: !HForm 56 1.18.2.2 pavel IDE disks on Simtec interface: UNKNOWN 57 1.18.2.2 pavel IDE disks on ICS interface: UNKNOWN 58 1.18.2.2 pavel IDE disks on RapIDE interface: UNKNOWN 59 1.18.2.2 pavel Acorn SCSI cards: ScsiDM 60 1.18.2.2 pavel Power-tec SCSI cards: !PowerMgr 61 1.18.2.2 pavel Cumana SCSI-2: !SCSIMgr 62 1.18.2.2 pavel oak SCSI-1 card: UNKNOWN 63 1.18.2.2 pavel MCS Connect32 SCSI: UNKNOWN 64 1.18.2.2 pavel Morley SCSI: UNKNOWN 65 1.18.2.2 pavel 66 1.18.2.2 pavel Additionally you will require the following : 67 1.18.2.2 pavel 68 1.18.2.2 pavel The Bootloader and RiscOS tools: BtNetBSD.tar.Z as found in 69 1.18.2.2 pavel the installation/misc directory. This archive which can be 70 1.18.2.2 pavel unpacked with !SparcPlug *includes the installation-kernel* 71 1.18.2.2 pavel so you don't have to download it separately. 72 1.18.2.2 pavel 73 1.18.2.2 pavel The NetBSD/acorn32 distribution sets (Will be on the CD-ROM, or 74 1.18.2.2 pavel available from your nearest NetBSD ftp site). 75 1.18.2.2 pavel 76 1.18.2.2 pavel A hardcopy of this document, along with a hardcopy of the 77 1.18.2.2 pavel NetBSD installation instructions "INSTALL"). 78 1.18.2.2 pavel 79 1.18.2.2 pavel 1.3 Preliminary steps : 80 1.18.2.2 pavel 81 1.18.2.2 pavel Unpack your BtNetBSD archive in whatever way, set the type of 82 1.18.2.2 pavel the `Settype' file in the BtNetBSD directory to `Obey' and run 83 1.18.2.2 pavel it. This will make the files RISC OS typed correctly. this is 84 1.18.2.2 pavel also explained in a bit more detail in the enclosed README file. 85 1.18.2.2 pavel It will also type the `InstKern' file that is the installation 86 1.18.2.2 pavel kernel itself complete with embedded ramdisc. 87 1.18.2.2 pavel 88 1.18.2.2 pavel 2 Preparing your hard disk 89 1.18.2.2 pavel 90 1.18.2.2 pavel Terms: 91 1.18.2.2 pavel 92 1.18.2.2 pavel Device: The actual physical hard disk 93 1.18.2.2 pavel Partition: A section of a device. 94 1.18.2.2 pavel File system: A structured partition that is able to hold files. 95 1.18.2.2 pavel Disc: A RiscOS file system in a partition. There can be 96 1.18.2.2 pavel more than one Disc per Device. 97 1.18.2.2 pavel 98 1.18.2.2 pavel You will have to decide which device you wish to install NetBSD on. 99 1.18.2.2 pavel You will also have to decide whether you want to split the device 100 1.18.2.2 pavel between one or more RiscOS discs and NetBSD or dedicate a whole 101 1.18.2.2 pavel Device for NetBSD. 102 1.18.2.2 pavel 103 1.18.2.2 pavel In making this decision you should consider the possibility that if 104 1.18.2.2 pavel NetBSD is incorrectly configured on a shared device then your shared 105 1.18.2.2 pavel data is at risk. 106 1.18.2.2 pavel 107 1.18.2.2 pavel It is still recommended that if you decide to dedicate a device to 108 1.18.2.2 pavel NetBSD that you set aside a small RISC OS partition at the beginning 109 1.18.2.2 pavel of the device. This is a useful place to store the RiscOS side of 110 1.18.2.2 pavel NetBSD, and will make the use of UnixFS easier to configure. If you 111 1.18.2.2 pavel do decide to create a minimal RiscOS partition at the beginning of 112 1.18.2.2 pavel the device, a size of 10-20 MB is recommended (some partitioning 113 1.18.2.2 pavel software has problems with partitions smaller than this). 114 1.18.2.2 pavel 115 1.18.2.2 pavel The point is that you will have to repartition your device to make 116 1.18.2.2 pavel room for a separate partition after the RISC OS one for NetBSD. This 117 1.18.2.2 pavel means backing up your device, re-partitioning it and then copying all 118 1.18.2.2 pavel the data back afterwards. We recommend that you only copy the needed 119 1.18.2.2 pavel data back and put off installing the rest until you have NetBSD up 120 1.18.2.2 pavel and running. This way you will save yourself a lot of work if 121 1.18.2.2 pavel something goes wrong and you have to start all over again. 122 1.18.2.2 pavel 123 1.18.2.2 pavel 124 1.18.2.2 pavel 2.1 Sharing your device 125 1.18.2.2 pavel 126 1.18.2.2 pavel 127 1.18.2.2 pavel 2.1.1 Acorn IDE 128 1.18.2.2 pavel 129 1.18.2.2 pavel Use !HForm for this interface. This is a program that is delivered 130 1.18.2.2 pavel with your computer and is located in the Utilities directory on your 131 1.18.2.2 pavel hard disk. 132 1.18.2.2 pavel 133 1.18.2.2 pavel With this software you only have the possibility of using one 134 1.18.2.2 pavel partition for RISC OS, so you have to set the rest aside for NetBSD. 135 1.18.2.2 pavel 136 1.18.2.2 pavel Use this procedure to set up your device: 137 1.18.2.2 pavel 138 1.18.2.2 pavel Start !HForm by double-clicking on its icon. 139 1.18.2.2 pavel 140 1.18.2.2 pavel Choose the "custom" or "other" option when prompted (usually 141 1.18.2.2 pavel the last). 142 1.18.2.2 pavel 143 1.18.2.2 pavel Use the default values for the geometry but do not enter the 144 1.18.2.2 pavel full number of cylinders. Just enter the number you want to 145 1.18.2.2 pavel use for RISC OS. Make a note of this number. 146 1.18.2.2 pavel 147 1.18.2.2 pavel Continue to accept the default answers until you're asked 148 1.18.2.2 pavel whether you want to format or initialize, choose initialize. 149 1.18.2.2 pavel 150 1.18.2.2 pavel Go to the section about running bb_riscbsd. 151 1.18.2.2 pavel 152 1.18.2.2 pavel 153 1.18.2.2 pavel 2.1.2 Cumana SCSI-2 card 154 1.18.2.2 pavel 155 1.18.2.2 pavel It is recommended that you use a newer version of !SCSIMgr (newer 156 1.18.2.2 pavel than v1.55) since this will be easier to use when you want to leave 157 1.18.2.2 pavel part of the device unused by RISC OS. You should check for the latest 158 1.18.2.2 pavel version of this software at the following URL: 159 1.18.2.2 pavel http://www.cumana.demon.co.uk 160 1.18.2.2 pavel 161 1.18.2.2 pavel You need to create one or more RISC OS partitions, and you do it in 162 1.18.2.2 pavel in the following way: 163 1.18.2.2 pavel Run !SCSIMgr by double-clicking on it. 164 1.18.2.2 pavel 165 1.18.2.2 pavel Select the device you wish to repartition. 166 1.18.2.2 pavel 167 1.18.2.2 pavel Click on the clear icon in the partitions subwindow. 168 1.18.2.2 pavel 169 1.18.2.2 pavel This will give you a dialogue box where you can specify the 170 1.18.2.2 pavel size of the RISC OS partitions. Do not select all since you 171 1.18.2.2 pavel want to use part of it for NetBSD. 172 1.18.2.2 pavel 173 1.18.2.2 pavel Enter the amount of the device you wish to reserve for 174 1.18.2.2 pavel RiscOS. This will be the whole device size less the amount 175 1.18.2.2 pavel you want to reserve for NetBSD. Make a note of this number. 176 1.18.2.2 pavel 177 1.18.2.2 pavel If you like, split the RISC OS portion of the device into 178 1.18.2.2 pavel several partition (you should only "see" the RiscOS portion). 179 1.18.2.2 pavel 180 1.18.2.2 pavel Click on Execute when you are happy with the partitions. This 181 1.18.2.2 pavel will create your partitions, and wipe your device. 182 1.18.2.2 pavel 183 1.18.2.2 pavel Go to the section about running bb_riscbsd. 184 1.18.2.2 pavel 185 1.18.2.2 pavel 186 1.18.2.2 pavel 2.1.3 Alsystems Power-tec SCSI-2 card 187 1.18.2.2 pavel 188 1.18.2.2 pavel You must use the !PowerMgr program to partition the device. 189 1.18.2.2 pavel 190 1.18.2.2 pavel The RISC OS partitions should be called RiscOs:, and the NetBSD one 191 1.18.2.2 pavel should be called Empty:. 192 1.18.2.2 pavel 193 1.18.2.2 pavel Here is the procedure you should use: 194 1.18.2.2 pavel Start !PowerMgr by double-clicking on its icon. 195 1.18.2.2 pavel 196 1.18.2.2 pavel Click on advanced in the main window 197 1.18.2.2 pavel 198 1.18.2.2 pavel Click on Define/create partitions 199 1.18.2.2 pavel Click on the device you want to set up for NetBSD. 200 1.18.2.2 pavel 201 1.18.2.2 pavel Set up the RISC OS partitions as "RiscOs:" and the 202 1.18.2.2 pavel remaining one as "Empty:". 203 1.18.2.2 pavel 204 1.18.2.2 pavel Click on each figure and press RETURN. 205 1.18.2.2 pavel 206 1.18.2.2 pavel Click on partition drive. 207 1.18.2.2 pavel 208 1.18.2.2 pavel Click on yes to warning as you really want to wipe 209 1.18.2.2 pavel the device. 210 1.18.2.2 pavel 211 1.18.2.2 pavel Click on yes to proceed, this will lead you to the 212 1.18.2.2 pavel partition init. 213 1.18.2.2 pavel 214 1.18.2.2 pavel Partition init 215 1.18.2.2 pavel Set a tick on all RiscOs: partitions, give them a name 216 1.18.2.2 pavel and set LFAU to auto. 217 1.18.2.2 pavel 218 1.18.2.2 pavel Unset the tick on your Empty: partition. 219 1.18.2.2 pavel 220 1.18.2.2 pavel Click on Inititialize selected partitions. 221 1.18.2.2 pavel 222 1.18.2.2 pavel Click on yes to proceed init as you want to wipe the 223 1.18.2.2 pavel selected partitions. 224 1.18.2.2 pavel 225 1.18.2.2 pavel Click on yes to proceed to configure. 226 1.18.2.2 pavel 227 1.18.2.2 pavel Configure 228 1.18.2.2 pavel Here you should set up the RISC OS partitions as you 229 1.18.2.2 pavel like them. Normally the default will be ok. 230 1.18.2.2 pavel 231 1.18.2.2 pavel Click on configure. This will configure your computer 232 1.18.2.2 pavel and give you access to the Discs. 233 1.18.2.2 pavel 234 1.18.2.2 pavel You *Must Not* run bb_riscbsd. 235 1.18.2.2 pavel 236 1.18.2.2 pavel 237 1.18.2.2 pavel 238 1.18.2.2 pavel 2.1.4 Acorn SCSI card 239 1.18.2.2 pavel 240 1.18.2.2 pavel You can only have one RISC OS partition with this card. The rest has 241 1.18.2.2 pavel to be set aside for NetBSD. 242 1.18.2.2 pavel 243 1.18.2.2 pavel This card does not have a friendly WIMP-based interface on the SCSI 244 1.18.2.2 pavel management program, but the command line version is very good. You 245 1.18.2.2 pavel should run this in a task window (press CTRL-F12): 246 1.18.2.2 pavel dir <location_of_scsidm> 247 1.18.2.2 pavel 248 1.18.2.2 pavel scsidm 249 1.18.2.2 pavel 250 1.18.2.2 pavel You will get the following prompt: 251 1.18.2.2 pavel scsidm> 252 1.18.2.2 pavel 253 1.18.2.2 pavel Now you should enter the following commands: 254 1.18.2.2 pavel probe (to see which devices are available) 255 1.18.2.2 pavel 256 1.18.2.2 pavel device <no> (replace <no> with the no of your device) 257 1.18.2.2 pavel 258 1.18.2.2 pavel section (to divide the device between RISC OS and 259 1.18.2.2 pavel NetBSD) 260 1.18.2.2 pavel Answer yes to the question: 261 1.18.2.2 pavel Include RISCiX partitions? 262 1.18.2.2 pavel 263 1.18.2.2 pavel Enter the size of the RISC OS area in blocks 264 1.18.2.2 pavel (sectors) 265 1.18.2.2 pavel 266 1.18.2.2 pavel SCSIDM will round this up to the nearest cylinder 267 1.18.2.2 pavel boundary. 268 1.18.2.2 pavel 269 1.18.2.2 pavel Answer yes to the question: 270 1.18.2.2 pavel Do you really want to section device <no>? 271 1.18.2.2 pavel 272 1.18.2.2 pavel This will section the device into two partitions. 273 1.18.2.2 pavel 274 1.18.2.2 pavel quit 275 1.18.2.2 pavel 276 1.18.2.2 pavel Go to the section on running bb_riscbsd. 277 1.18.2.2 pavel 278 1.18.2.2 pavel 279 1.18.2.2 pavel 280 1.18.2.2 pavel 2.1.5 Other interfaces 281 1.18.2.2 pavel 282 1.18.2.2 pavel It may not be possible to partition devices on other interface. If 283 1.18.2.2 pavel you are using a different interface you have 2 options: 284 1.18.2.2 pavel 285 1.18.2.2 pavel Try to work out how to partition devices on it 286 1.18.2.2 pavel 287 1.18.2.2 pavel Use the entire device for NetBSD 288 1.18.2.2 pavel 289 1.18.2.2 pavel 290 1.18.2.2 pavel 2.2 Using a whole device for NetBSD 291 1.18.2.2 pavel 292 1.18.2.2 pavel As a safety precaution NetBSD/acorn32 looks for a filecore bootblock 293 1.18.2.2 pavel at the beginning of any device it labels. If it finds one and it 294 1.18.2.2 pavel looks as though it is in use then NetBSD/acorn32 will not touch it. 295 1.18.2.2 pavel 296 1.18.2.2 pavel Because of this, if you've ever used your device for RiscOS, you will 297 1.18.2.2 pavel need to invalidate this bootblock. 298 1.18.2.2 pavel 299 1.18.2.2 pavel To do this you need to: 300 1.18.2.2 pavel 301 1.18.2.2 pavel Be absolutely sure you want to do this. 302 1.18.2.2 pavel 303 1.18.2.2 pavel Run bb_trash and follow the instructions. 304 1.18.2.2 pavel 305 1.18.2.2 pavel Ensure that this device is now not configured for RiscOS. 306 1.18.2.2 pavel 307 1.18.2.2 pavel You are now ready to boot NetBSD and continue the installation. 308 1.18.2.2 pavel 309 1.18.2.2 pavel 310 1.18.2.2 pavel 311 1.18.2.2 pavel 3 Running bb_riscbsd 312 1.18.2.2 pavel 313 1.18.2.2 pavel When you run this program, you will first be asked whether you are 314 1.18.2.2 pavel installing to an ADFS drive or a SCSI drive. You can just press A or 315 1.18.2.2 pavel S respectively. (The bb_riscbsd program assumes that you are using a 316 1.18.2.2 pavel non-Acorn SCSI card, so if you are using an Acorn card, then you may 317 1.18.2.2 pavel have to edit this program and replace SCSI_DiscOp with SCSIFS_DiscOp.) 318 1.18.2.2 pavel 319 1.18.2.2 pavel Then you will be asked which disc you want to install NetBSD on. This 320 1.18.2.2 pavel *must* be the first disc on the device. bb_riscbsd will now 321 1.18.2.2 pavel scrutinize the device and see how it has been laid out. 322 1.18.2.2 pavel 323 1.18.2.2 pavel It will then tell you how much of the device is occupied by RiscOS in 324 1.18.2.2 pavel cylinders, and you will then be asked for the NetBSD starting 325 1.18.2.2 pavel cylinder. Normally you should just enter the number given to you 326 1.18.2.2 pavel since the RISC OS starting cylinder is 0 and therefore the last 327 1.18.2.2 pavel cylinder in use is one less than the figure given. If no figure is 328 1.18.2.2 pavel displayed, then your partitioning software failed to fill in the 329 1.18.2.2 pavel bootblock completely (it doesn't have to do this for you but most do) 330 1.18.2.2 pavel or you selected the wrong device. If you are convinced that this is 331 1.18.2.2 pavel the correct device then you must calculate a cylinder offset using 332 1.18.2.2 pavel the numbers noted down during partitioning (if it is not a whole 333 1.18.2.2 pavel number *always* round up, you might waste a little of the device but 334 1.18.2.2 pavel it'll be safer). 335 1.18.2.2 pavel 336 1.18.2.2 pavel Make a note of this number. 337 1.18.2.2 pavel 338 1.18.2.2 pavel bb_riscbsd will make a backup of the original bootblock, but it 339 1.18.2.2 pavel can be non-trivial to put it back. 340 1.18.2.2 pavel 341 1.18.2.2 pavel 342 1.18.2.2 pavel 343 1.18.2.2 pavel 4 Booting 344 1.18.2.2 pavel 345 1.18.2.2 pavel Now that your device is ready for the installation you need to 346 1.18.2.2 pavel unpack the bootloader archive. 347 1.18.2.2 pavel 348 1.18.2.2 pavel In the archive you'll find the tools mentioned in this document as well as 349 1.18.2.2 pavel the bootloader !BtNetBSD itself and accompanied a file called `InstKern' 350 1.18.2.2 pavel which is the actual installation kernel with embedded ramdisc containing the 351 1.18.2.2 pavel NetBSD userland nessisary for installation. 352 1.18.2.2 pavel 353 1.18.2.2 pavel 354 1.18.2.2 pavel 4.1 [Optional] Configuring the !BtNetBSD bootloader before installation 355 1.18.2.2 pavel 356 1.18.2.2 pavel Open the !BtNetBSD application and edit the `fastboot' file to specify 357 1.18.2.2 pavel a known kernel location; an example is already given. 358 1.18.2.2 pavel 359 1.18.2.2 pavel You can also set other details like tweaking with the amount of memory in 360 1.18.2.2 pavel the WimpSlot of the bootloader when this is too much. Remember however that 361 1.18.2.2 pavel this shouldn't be set too low for it can crash the bootloader. 362 1.18.2.2 pavel 363 1.18.2.2 pavel When you think you've filled in the proper details save the file again 364 1.18.2.2 pavel and proceed. 365 1.18.2.2 pavel 366 1.18.2.2 pavel 367 1.18.2.2 pavel 4.2 Starting the installation! 368 1.18.2.2 pavel 369 1.18.2.2 pavel To start the installation just double click on the InstKern file. This will 370 1.18.2.2 pavel startup !BtNetBSD with the proper kernel argument and start its installation. 371 1.18.2.2 pavel 372 1.18.2.2 pavel NetBSD should now start to boot, install NetBSD as per the NetBSD 373 1.18.2.2 pavel installation notes. 374 1.18.2.2 pavel 375 1.18.2.2 pavel When you finish the installation you can restarted the computer as 376 1.18.2.2 pavel instructed. 377 1.18.2.2 pavel 378 1.18.2.2 pavel 379 1.18.2.2 pavel 4.3 [Optional] Configuring !BtNetBSD after installation 380 1.18.2.2 pavel 381 1.18.2.2 pavel Open the !BtNetBSD application again and edit the `fastboot' file again 382 1.18.2.2 pavel to custimise details like the mode defition file you want to use. 383 1.18.2.2 pavel 384 1.18.2.2 pavel Save the file and run !BtNetBSD again (see above). 385 1.18.2.2 pavel 386 1.18.2.2 pavel 387 1.18.2.2 pavel 388 1.18.2.2 pavel 5 Advanced stuff 389 1.18.2.2 pavel 390 1.18.2.2 pavel 391 1.18.2.2 pavel 5.1 Using UnixFS to copy the sets. 392 1.18.2.2 pavel 393 1.18.2.2 pavel Once the required sets are installed and you can boot from your 394 1.18.2.2 pavel newly installed NetBSD setup, you can use UnixFS to copy the 395 1.18.2.2 pavel remaining sets from RiscOS to NetBSD. 396 1.18.2.2 pavel 397 1.18.2.2 pavel In order to be able to use unixfs to transfer the sets you must have 398 1.18.2.2 pavel a certain setup. 399 1.18.2.2 pavel 400 1.18.2.2 pavel 1) You must have the RiscOS disc that corresponds to the NetBSD 401 1.18.2.2 pavel device configured (e.g., *con. IDEdiscs 2) even if it has no RiscOS 402 1.18.2.2 pavel section. 403 1.18.2.2 pavel 2) If you have RISC OS 3.5 without the new FileCore, then you must 404 1.18.2.2 pavel also have the NetBSD file system *completely* below the 511 MB 405 1.18.2.2 pavel boundary of the device. 406 1.18.2.2 pavel 3) You must know the SWI base of the <filesys>_DiscOp SWI. Here 407 1.18.2.2 pavel <filesys> is SCSIFS, SCSI or ADFS depending upon which controller 408 1.18.2.2 pavel type you have you NetBSD device on. 409 1.18.2.2 pavel Some common ones: 410 1.18.2.2 pavel Power-tec SCSI-2 card: &40980 411 1.18.2.2 pavel RapIDE: &4BBC0 412 1.18.2.2 pavel 413 1.18.2.2 pavel There are small obey files for some interfaces supplied with UnixFS. 414 1.18.2.2 pavel 4) Have given the directory you want to write into write permission for 415 1.18.2.2 pavel everyone. This should have been done above. For example to make 416 1.18.2.2 pavel /usr/distrib world writable type (as root): 417 1.18.2.2 pavel chmod 1777 /usr/distrib 418 1.18.2.2 pavel 419 1.18.2.2 pavel To mount a Unix partition: 420 1.18.2.2 pavel 421 1.18.2.2 pavel 1) Double-click on the unixfs_res module to load it. 422 1.18.2.2 pavel 2) Run a unixfs_mount command to mount the partition. 423 1.18.2.2 pavel 3) Open the root directory by double-clicking on the openroot file. 424 1.18.2.2 pavel 4) Open the distrib directory and just copy the sets to this. 425 1.18.2.2 pavel 5) Shut down unixfs by double-clicking on the kill_unixfs file. 426 1.18.2.2 pavel THIS STEP IS VERY IMPORTANT as it works like dismount on MS-DOS floppies. 427 1.18.2.2 pavel 428 1.18.2.2 pavel The difficult step here is step number 2). If you are using an 429 1.18.2.2 pavel ADFS IDE disc, then you can just double-click on one of the 430 1.18.2.2 pavel following obey files (always choose the RiscOS disc number that 431 1.18.2.2 pavel corresponds to the *first* disc on the NetBSD device): 432 1.18.2.2 pavel - wd0a (ADFS::4 drive, not disc, root file system) 433 1.18.2.2 pavel - wd0e (ADFS::4 drive, not disc, /usr file system) 434 1.18.2.2 pavel - wd1a (ADFS::5 drive, not disc, root file system) 435 1.18.2.2 pavel - wd1e (ADFS::5 drive, not disc, /usr file system) 436 1.18.2.2 pavel 437 1.18.2.2 pavel If you are not using an ADFS IDE device, you need to create such 438 1.18.2.2 pavel an obey file yourself. We recommend that you copy one of the 439 1.18.2.2 pavel above and change that. These files normally only contain a 440 1.18.2.2 pavel unixfs_mount command. If you go to the command line (or a task 441 1.18.2.2 pavel window), and you type *help unixfs_mount you will see that the 442 1.18.2.2 pavel unixfs_mount command has a very incomprehensible syntax. 443 1.18.2.2 pavel 444 1.18.2.2 pavel The unixfs_mount command normally only takes one argument. That 445 1.18.2.2 pavel is composed of the following: 446 1.18.2.2 pavel (discop_swibase + (disc << 3) + partition) 447 1.18.2.2 pavel 448 1.18.2.2 pavel To mount the root partition of third Power-tec SCSI-2 disc the 449 1.18.2.2 pavel following commands can be used in task window (press CTRL-F12) to 450 1.18.2.2 pavel find the argument to unixfs_mount: 451 1.18.2.2 pavel *basic 452 1.18.2.2 pavel PRINT ~(&40980 + (6 << 3) + 0) 453 1.18.2.2 pavel QUIT 454 1.18.2.2 pavel 455 1.18.2.2 pavel The PRINT command calculates the value to use and will in this 456 1.18.2.2 pavel context give the value 409B0 which also is in hexadecimal. The 457 1.18.2.2 pavel interesting things above are: 458 1.18.2.2 pavel - &40980 The SWI base for SCSIFS_DiscOp. 459 1.18.2.2 pavel - 6 The disc number in RISC OS. 460 1.18.2.2 pavel - 0 The RiscBSD partition no. with a=0, b=1 etc. 461 1.18.2.2 pavel - ~ Tell the PRINT command to show the result in hexadecimal. 462 1.18.2.2 pavel - << Shifts the first number with the second number 463 1.18.2.2 pavel places left. 464 1.18.2.2 pavel In this case, it shifts 6 with 3 places to the left. 465 1.18.2.2 pavel - & Denotes that the number is in hexadecimal. 466 1.18.2.2 pavel - ( and ) Used to group the sub-expressions. 467 1.18.2.2 pavel 468 1.18.2.2 pavel When you have calculated the figure to give to unixfs_mount you 469 1.18.2.2 pavel just change it in the copy of the file you made above and run it by 470 1.18.2.2 pavel double-clicking on it. 471 1.18.2.2 pavel 472 1.18.2.2 pavel When you have mounted the unixfs file system, you can open the 473 1.18.2.2 pavel directory and copy the sets to it. 474 1.18.2.2 pavel Don't forget to copy the file "checksums" too. As its name suggests, it 475 1.18.2.2 pavel contains checksums to check if the files are OK. 476 1.18.2.2 pavel 477 1.18.2.2 pavel When you are finished with the transfer, run the file 478 1.18.2.2 pavel kill_unixfs to dismount the unixfs file system. 479 1.18.2.2 pavel 480 1.18.2.2 pavel 481 1.18.2.2 pavel 482 1.18.2.2 pavel Appendix A - Device naming 483 1.18.2.2 pavel 484 1.18.2.2 pavel The names of the devices in NetBSD are not at all like the ones 485 1.18.2.2 pavel in RISC OS. We will here try to explain the naming scheme used 486 1.18.2.2 pavel in NetBSD. This is pretty much the same in all UNIXes, but 487 1.18.2.2 pavel there will be some differences. NetBSD is derived from BSD and 488 1.18.2.2 pavel differs from the ones that are derived from System V. Most of 489 1.18.2.2 pavel the dominant operating systems in the UNIX market today are 490 1.18.2.2 pavel based on System V (Sun Solaris, SGI Irix, HP HP-UX 10.xx, Linux 491 1.18.2.2 pavel etc.). Some of them are actually hybrids of both. 492 1.18.2.2 pavel 493 1.18.2.2 pavel The file systems in UNIX use the slash character (/) as the 494 1.18.2.2 pavel directory separator. The top (or bottom if you like) directory 495 1.18.2.2 pavel is called the root and is denoted by a single slash (/). All 496 1.18.2.2 pavel absolute filenames are addressed starting with the root, so the 497 1.18.2.2 pavel temporary directory is called /tmp. 498 1.18.2.2 pavel 499 1.18.2.2 pavel The devices in UNIX are addressed as special files in the 500 1.18.2.2 pavel file system, and they all start with /dev, so e.g. the quadrature 501 1.18.2.2 pavel mouse is called /dev/quadmouse. 502 1.18.2.2 pavel 503 1.18.2.2 pavel Also some devices can be addressed in two different ways; as a 504 1.18.2.2 pavel raw (character by character) or block device. This is especially 505 1.18.2.2 pavel true with discs, and they therefore have two different names. 506 1.18.2.2 pavel The raw device is called the same as the block device except 507 1.18.2.2 pavel that it has an 'r' in front of the name. E.g. the first internal 508 1.18.2.2 pavel hard drive is called /dev/wd0 as a block device, but /dev/rwd0 509 1.18.2.2 pavel as a raw device. See also later. 510 1.18.2.2 pavel 511 1.18.2.2 pavel For now, the only needed devices are the storage devices, so we 512 1.18.2.2 pavel will hereby describe the naming convention used for these. 513 1.18.2.2 pavel Please note that when you have different partitions on a device, 514 1.18.2.2 pavel they will get the same number in NetBSD, but different letters, 515 1.18.2.2 pavel whereas in RISC OS they will get different numbers. See the 516 1.18.2.2 pavel examples at the end of this section. 517 1.18.2.2 pavel 518 1.18.2.2 pavel The (block) device names are mostly composed of 4 characters: 519 1.18.2.2 pavel 1. The type 520 1.18.2.2 pavel - w Winchester drives (i.e. standard ADFS drives) 521 1.18.2.2 pavel - s SCSI drives 522 1.18.2.2 pavel - c CD-ROM drives 523 1.18.2.2 pavel - r RAM drives (obsolete in newer kernels) 524 1.18.2.2 pavel - m Memory drives (only in newer kernels) 525 1.18.2.2 pavel - f Floppy drives 526 1.18.2.2 pavel 2. A 'd' indicating a disc device 527 1.18.2.2 pavel 3. The number of the device of that type starting with 0. 528 1.18.2.2 pavel - For IDE drives, the master will be 0, and the slave 1. 529 1.18.2.2 pavel - For SCSI drives, the target ID will be used to 530 1.18.2.2 pavel determine the number. They start on 0 and increase with 531 1.18.2.2 pavel each device found. The drive with the lowest target ID will get 532 1.18.2.2 pavel 0, the second lowest target ID will get 1 etc. 533 1.18.2.2 pavel Also, if you have different controllers, all devices on controller 534 1.18.2.2 pavel 0 (lowest expansion slot) will be added first. 535 1.18.2.2 pavel - The CD-ROM drives act the same way as SCSI drives. 536 1.18.2.2 pavel - The floppy drive is numbered as in RISC OS. 537 1.18.2.2 pavel - At present you can only have one RAM drive, so it is 0. 538 1.18.2.2 pavel 4. The name of the partition. There are eight of these (along with 539 1.18.2.2 pavel common allocations): 540 1.18.2.2 pavel - a The root partition 541 1.18.2.2 pavel - b The swap partition 542 1.18.2.2 pavel - c The complete and whole disc ; all OS's and partitions 543 1.18.2.2 pavel - d Part of the disc that is not used by NetBSD; normally RiscOS 544 1.18.2.2 pavel - e The first additional partition. 545 1.18.2.2 pavel i.e. if you have only /usr, then this will be /usr 546 1.18.2.2 pavel if you have both /var and /usr this will be /var 547 1.18.2.2 pavel - f The second additional partition. 548 1.18.2.2 pavel i.e. if you have /var and /usr, this will be /usr 549 1.18.2.2 pavel - g The third ... 550 1.18.2.2 pavel - h The fourth ... 551 1.18.2.2 pavel 552 1.18.2.2 pavel If you only have one partition on the drive this can normally be 553 1.18.2.2 pavel accessed with either partition a (root partition) or c (whole 554 1.18.2.2 pavel disc). This has not been verified to work. 555 1.18.2.2 pavel 556 1.18.2.2 pavel A couple of examples of how to map RISC OS names to NetBSD ones 557 1.18.2.2 pavel (the partition names have been left out): 558 1.18.2.2 pavel ADFS::0 fd0 559 1.18.2.2 pavel ADFS::1 fd1 560 1.18.2.2 pavel ADFS::4 wd0 561 1.18.2.2 pavel ADFS::5 (same drive as :4) wd0 562 1.18.2.2 pavel ADFS::5 (other drive than :4) wd1 563 1.18.2.2 pavel SCSI::4 sd0 564 1.18.2.2 pavel SCSI::5 (same drive as :4) sd0 565 1.18.2.2 pavel SCSI::5 (other drive than :4) sd1 566 1.18.2.2 pavel 567 1.18.2.2 pavel So, if you have one ADFS IDE drive, and want to install NetBSD 568 1.18.2.2 pavel at the after ADFS::5, you should still use wd0. If on the other 569 1.18.2.2 pavel hand, ADFS::5 is a second drive, then you will have to use wd1. 570 1.18.2.2 pavel 571 1.18.2.2 pavel 572 1.18.2.2 pavel Appendix B - Acknowledgments 573 1.18.2.2 pavel 574 1.18.2.2 pavel This document was based upon the document 575 1.18.2.2 pavel "Installing RiscBSD 1.2-Release" 576 1.18.2.2 pavel (C) 1996 The RiscBSD Documentation Project 577 1.18.2.2 pavel 578 1.18.2.2 pavel That has the following acknowledgement: 579 1.18.2.2 pavel 580 1.18.2.2 pavel This manual has been written from scratch based on version 1.2 581 1.18.2.2 pavel of the installation manual that Mark Brinicombe wrote. 582 1.18.2.2 pavel 583 1.18.2.2 pavel It was mainly written by Kjetil B. Thomassen 584 1.18.2.2 pavel (kjetil (a] thomassen.priv.no) with contributions from: 585 1.18.2.2 pavel Neil Hoggarth (neil.hoggarth (a] physiol.ox.ac.uk) 586 1.18.2.2 pavel Markus Baeurle (emw4maba (a] gp.fht-esslingen.de) 587 1.18.2.2 pavel Jasper Wallace (jasper (a] ivision.co.uk) 588 1.18.2.2 pavel Mark Brinicombe (amb (a] physig.ph.kcl.ac.uk) 589 1.18.2.2 pavel Scott Stevens (s.k.stevens (a] ic.ac.uk) 590 1.18.2.2 pavel and a lot more people posting to the original RiscBSD mailing list. 591 1.18.2.2 pavel 592
Indexes created Mon Sep 29 21:09:56 GMT 2025