diff options
| author | Miod Vallat <miod@cvs.openbsd.org> | 2010-03-16 17:23:10 +0000 |
|---|---|---|
| committer | Miod Vallat <miod@cvs.openbsd.org> | 2010-03-16 17:23:10 +0000 |
| commit | 6588e4f22e3472c3d54c68e5f84dea9c206a0f87 (patch) | |
| tree | 04ff2c15a0dc4631c5a3e8f22cf5e199209f3fcb /distrib | |
| parent | e5607f886b5f9d19e6348d4ed71a19dabe5eb63c (diff) | |
Jumbo commit for 4.7 installation instructions:
- do not mention tape as an installation media on systems where it is very
unlikely that a tape drive can be connected to (i.e. anything with only
USB as expansion capabilities)
- do not mention that fetching the installation sets from a partition is
``for upgrades only''. You may do this for installation, but of course
you can not use a partition which will be newfs'ed for that purpose.
- mention ext2fs partitions as possible installation sets source only on
platforms where the installation media actually can mount an ext2fs
filesystem.
- stress the fact that the sparc miniroot image is a GENERIC kernel with
a little on-disk filesystem, and not a RAMDISK kernel with a little
in-memory filesystem, and thus must not be overwritten during installation
(i.e. be careful if you repartition the disk the miniroot has been put on).
- more conv=sync -> conv=osync for tape setup instructions.
- model-specific layout changes on armish, loongson and socppc instructions.
- fix various typos and grammar mistaeks.
"sure" deraadt@ (without eyeballing)
Diffstat (limited to 'distrib')
49 files changed, 744 insertions, 775 deletions
diff --git a/distrib/notes/alpha/install b/distrib/notes/alpha/install index dfe7f58fbf4..2c65619c597 100644 --- a/distrib/notes/alpha/install +++ b/distrib/notes/alpha/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.34 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.35 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way is @@ -111,7 +111,7 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall diff --git a/distrib/notes/alpha/xfer b/distrib/notes/alpha/xfer index 8206ed3dda1..a6ef52cf078 100644 --- a/distrib/notes/alpha/xfer +++ b/distrib/notes/alpha/xfer @@ -1,8 +1,8 @@ -dnl $OpenBSD: xfer,v 1.28 2005/03/18 13:30:51 miod Exp $ +dnl $OpenBSD: xfer,v 1.29 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM (NOT supported if booting from floppy) - FFS partitions (for upgrades only) + FFS partitions Tape FTP HTTP @@ -44,7 +44,6 @@ If you neither have a floppy drive nor a CD-ROM drive on your alpha: OpenBSDXferShortPrelude - OpenBSDXferBareTape(xbase xetc xfont xserv xshare) OpenBSDXferFFS diff --git a/distrib/notes/amd64/install b/distrib/notes/amd64/install index 5ef3922e2b5..f797f560c58 100644 --- a/distrib/notes/amd64/install +++ b/distrib/notes/amd64/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.13 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.14 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude If OpenBSD will be sharing the disk with another operating system, @@ -54,7 +54,7 @@ OpenBSDInstallPart5({:- If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'i', 'j' and so on.-:}) -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall diff --git a/distrib/notes/amd64/xfer b/distrib/notes/amd64/xfer index 947bd0ecb46..08863acc536 100644 --- a/distrib/notes/amd64/xfer +++ b/distrib/notes/amd64/xfer @@ -1,10 +1,10 @@ -dnl $OpenBSD: xfer,v 1.9 2007/08/02 17:33:12 david Exp $ +dnl $OpenBSD: xfer,v 1.10 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) - DOS (FAT) partitions (for upgrades only) - EXT2 partitions (for upgrades only) + FFS partitions + DOS (FAT) partitions +dnl EXT2 partitions Tape dnl Remote NFS partition FTP @@ -41,7 +41,6 @@ Creating a PXE network bootable setup using OpenBSD or other Un*x-like system: OpenBSDXferShortPrelude - OpenBSDXferBareTape(xbase xetc xfont xserv xshare) dnl OpenBSDXferNFS diff --git a/distrib/notes/armish/prep b/distrib/notes/armish/prep index 1f28d84cf6c..0cb437580e7 100644 --- a/distrib/notes/armish/prep +++ b/distrib/notes/armish/prep @@ -1,321 +1,310 @@ -dnl $OpenBSD: prep,v 1.15 2010/03/04 10:56:03 jasper Exp $ -To be able to boot the OpenBSD/MACHINE installation program, you will -need to learn a bit about RedBoot, the low-level process that controls -the microprocessor after hardware initialization. -dnl -dnl XXX bootable partitions +dnl $OpenBSD: prep,v 1.16 2010/03/16 17:23:09 miod Exp $ +To be able to boot the OpenBSD/MACHINE installation program, you will need +to learn a bit about RedBoot, the low-level process that controls the +microprocessor after hardware initialization. The enabled features between IOData HDL-G and Thecus N2100 vary, so different methods will be needed on both machines. -All these machines use RedBoot as their firmware and boot loader -interface, with varying limitations. Thecus systems cannot load a -file from disk, but can load an image from flash or network. IOData -systems are more restricted, and can only load an image from ext2fs -partitions on disk, while the commands to load from flash are not -available and network booting does not appear to work. +All these machines use RedBoot as their firmware and boot loader interface, +with varying limitations. Thecus systems cannot load a file from disk, but +can load an image from flash or network. IOData systems however are more +restricted, and can only load an image from ext2fs partitions on disk, while +the commands to load from flash are not available, and network booting does +not appear to work. -Talking to the Thecus +Thecus N2100 setup: -The Thecus N2100 needs a serial cable. On the back of the disk drive -circuit board, there is either a 10-pin header (with one pin removed), -or 9 holes for you to solder in your own header. The ribbon cable -that connects from there to your serial cable or the serial port on -your computer is of the same type as used on older i386 PCs, but -be aware that there are two different types of 10-pin IDC to DB-9M -ribbon cable in use, which look identical (the differences are hidden -inside the DB-9 connector). The cable you need is wired using the -"AT-Everex" or "Asus" pinout, as described here: + Talking to the Thecus - http://www.pccables.com/07120.htm + The Thecus N2100 needs a serial cable. On the back of the disk drive + circuit board, there is either a 10-pin header (with one pin removed), + or 9 holes for you to solder in your own header. The ribbon cable + that connects from there to your serial cable or the serial port on + your computer is of the same type as used on older i386 PCs, but + be aware that there are two different types of 10-pin IDC to DB-9M + ribbon cable in use, which look identical (the differences are hidden + inside the DB-9 connector). The cable you need is wired using the + "AT-Everex" or "Asus" pinout, as described here: -and *not* the more straightforward to solder "crossed" type: - - http://www.pccables.com/07121.htm. - -If you wish to check a cable, or make your own, the pinouts are: - - DB9 IDC10 - === ===== - 1 2 3 4 5 1 3 5 7 9 - 6 7 8 9 2 4 6 8 10 - -Wire pin 1 to 1, 2 to 2 etc, with 10 not connected. - -On the Thecus N2100, it is necessary to move jumper J3 to J4 to properly -route the serial port interrupt to allow serial to work under OpenBSD. -This jumper is under the disk drives, so you may wish to ensure its -correct setting while you are installing the disk(s). For instructions -on assembling/disassembling your N2100, see the N2100 Manual at - - http://www.thecus.com/download/manual/N2100%20UM%20EN.pdf - - -Booting Thecus N2100 - -When you have connected your computer, a command like "tip -115200 tty00" -(assuming you're using the first serial port on your machine) should -connect you to the Thecus console. Now apply power to the Thecus -and start it. - -After some device probe information, you should see this prompt: - - == Executing boot script in 3.000 seconds - enter ^C to abort - -To enter interactive RedBoot, it is necessary to press ^C within the given -number of seconds of the prompt. It will typically accept the ^C if typed -during the diagnostics that precede this prompt. - -The recommended way to boot OpenBSD on Thecus is to configure networking and -load bsd.rd from a tftp server or http server. First networking must be -configured using the fconfig or ip_address commands. - -Update the IP address, netmask and server address with the commands -listed below to allow booting from the network. TFTP and HTTP are -supported. (BOOTP configuration _may_ not work) - -Using ip_address only allows you to set the local IP address and -the IP address of the server where bsd.rd is located. This command -takes effect immediately but will not persist across a reboot. - - RedBoot> ip_address -l 10.0.0.21 -h 10.0.0.7 - IP: 10.0.0.21/255.255.255.0, Gateway: 0.0.0.0 - Default server: 10.0.0.7, DNS server IP: 0.0.0.0 - -Once you have done this, and have set up your TFTP server on -the gateway machine (10.0.0.7 in the above example), you can -boot manually. - - RedBoot> load /bsd.rd - Using default protocol (TFTP) - Entry point: 0x00200000, address range: 0x00200000-0x0066a49c - RedBoot> go - -OpenBSD/armish booting ... -initarm: Configuring system ... -physmemory: 32768 pages at 0xa0000000 -> 0xa7ffffff -[ no symbol table formats found ] -Copyright (c) 1982, 1986, 1989, 1991, 1993 - The Regents of the University of California. All rights reserved. -Copyright (c) 1995-2010 OpenBSD. All rights reserved. http://www.OpenBSD.org - -OpenBSD 4.7-beta (RAMDISK) #84: Tue Mar 2 18:21:39 MST 2010 - deraadt@armish.openbsd.org:/usr/src/sys/arch/armish/compile/RAMDISK -real mem = 134217728 (128MB) -avail mem = 121610240 (115MB) -... -Install(I), Upgrade(U) or Shell(S)? - -If you then install to your hard disk, in future you can -load /boot the same way and just hit "return" to boot OpenBSD. - - -Automatic Booting - -However, for easier booting, you may wish to modify the flash -memory so that the Thecus will boot automatically into OpenBSD -when it is powered up. Doing so disables the devices' built-in -Linux kernel, however, and makes it difficult or impossible to -apply future RedBoot firmware upgrades. There are two general -approaches: -1) Just change the boot configuration (using 'fconfig') to automate the - above booting (your TFTP or HTTP boot server will still be needed); -2) Remove a file from the flash and replace it with OpenBSD's /boot; - this configuration can be booted standalone. - -Thecus RedBoot provides the 'fconfig' (not ifconfig) command to -change the boot configuration of the device. Also 'fis' is provided -to perform flash operations. - -Due to a change made by Thecus to the firmware, fconfig does not -work with Thecus firmware version "1.93 (Feb 2007)" or later, and -*it is thus not possible to make the Thecus auto-boot into OpenBSD* -(worse, it will let you enter the "script" commands below, but -ignore them on boot). To correct this, you must "upgrade" your -thecus down to version "1.93 Nov 29 2005" using the file -n2100-downgrade-reboot.rom *before* you remove any files from flash. -You can get this file from Thecus; they have given permission for -it to be mirrored at http://www.darwinsys.com/openbsd/. However, -if you have removed files from flash before running this downgrade, -it is not believed to be possible to get your machine to auto-boot. - -Once the downgrade is done, if your TFTP machine will always be around, -you can autoboot just by changing the boot script with fconfig, -as follows: (in this example, 192.168.1.254 is both the default -IP gateway and also the TFTP server): - - RedBoot> fconfig - Run script at boot: true - Boot script: - .. load /boot.armish - .. go - Enter script, terminate with empty line - >> load /boot.armish - >> go - >> - Boot script timeout (1000ms resolution): 3 - Use BOOTP for network configuration: false - Gateway IP address: 192.168.1.254 - Local IP address: 192.168.1.253 - Local IP address mask: 255.255.255.0 - Default server IP address: 192.168.1.254 - Console baud rate: 115200 - DNS server IP address: - GDB connection port: 9000 - HW Status: 0 - Force console for special debug messages: false - MAC address: 0x00:0x14:0xFD:0x30:0x25:0x14 - MAC address 2: 0x00:0x14:0xFD:0x30:0x25:0x15 - Network debug at boot time: false - Reset default: Normal - Serial number: N2100 V2.1.06 - ... Unlock from 0xf0fc0000-0xf0fc1000: . - ... Erase from 0xf0fc0000-0xf0fc1000: . - ... Program from 0x07fd2000-0x07fd3000 at 0xf0fc0000: . - ... Lock from 0xf0fc0000-0xf0fc1000: . - RedBoot> - -This configuration can easily be set back to the default, as the -Linux system does not get erased from the flash memory. To set it -back, just change the boot script with fconfig back to what it was, -for example: - - thecus_setip - fis load ramdisk - fis load kernel - exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=128M@0xa0000000" - -You could also remove the boot script altogether by not re-entering -it, so you would be dropped to the RedBoot shell by default. - -Recheck the new values and use the 'reset' command. - - -For the standalone booting option, you will have to load /boot into -the flash memory... - -To overwrite the Thecus ROM and boot from the load device, it is necessary -to delete a 'rom file' and load the openbsd bootloader image there. With -networking configured (as above) remove a region and load the 'boot' program. - -Initially the machine will contain much like the following: - - RedBoot> fis list - Name FLASH addr Mem addr Length Entry point - RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 - RedBoot config 0xF0FC0000 0xF0FC0000 0x00001000 0x00000000 - FIS directory 0xF0FE0000 0xF0FE0000 0x00020000 0x00000000 - ramdisk 0xF0040000 0x00800000 0x00D00000 0x00800000 - kernel 0xF0D40000 0x00200000 0x00160000 0x00200000 - user 0xF0EA0000 0xF0EA0000 0x00120000 0x00200000 - -There is no free space in the rom for the 'boot' program, so something must -be removed. -WARNING: this will make the machine unbootable into the original -Thecus server mode and it is quite difficult to restore to the -original software. -EXTREME WARNING: Do not touch the RedBoot, RedBoot config, or FIS -directory regions, as doing so will probably brick the device. - -Remove (with confirmation) a region to make space, eg 'user' (the -non-root files needed to run Linux from Flash Memory). - - RedBoot> fis delete user - Delete image 'user' - continue (y/n)? y - ... Erase from 0xf0ea0000-0xf0fc0000: ......... - ... Unlock from 0xf0fe0000-0xf1000000: . - ... Erase from 0xf0fe0000-0xf1000000: . - ... Program from 0x07fdf000-0x07fff000 at 0xf0fe0000: . - ... Lock from 0xf0fe0000-0xf1000000: . - -Load the Armish OpenBSD bootloader 'boot' via tftp or http: - - RedBoot> load -m http /boot - Entry point: 0x00100000, address range: 0x00100000-0x001067e0 - -Save that loaded file to flash: - - RedBoot> fis create boot - ... Erase from 0xf0ea0000-0xf0ec0000: . - ... Program from 0x00100000-0x001067e0 at 0xf0ea0000: . - ... Unlock from 0xf0fe0000-0xf1000000: . - ... Erase from 0xf0fe0000-0xf1000000: . - ... Program from 0x07fdf000-0x07fff000 at 0xf0fe0000: . - ... Lock from 0xf0fe0000-0xf1000000: . - -Confirm its addition: - - RedBoot> fis list - Name FLASH addr Mem addr Length Entry point - RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 - RedBoot config 0xF0FC0000 0xF0FC0000 0x00001000 0x00000000 - FIS directory 0xF0FE0000 0xF0FE0000 0x00020000 0x00000000 - ramdisk 0xF0040000 0x00800000 0x00D00000 0x00800000 - kernel 0xF0D40000 0x00200000 0x00160000 0x00200000 - boot 0xF0EA0000 0x00100000 0x00020000 0x00100000 - -Now that the bootloader is in place, update fconfig to autoboot OpenBSD: - - RedBoot> fconfig - Run script at boot: true - Boot script: - .. fis load ramdisk - .. fis load kernel - .. exec ... - Enter script, terminate with empty line - >> fis load boot - >> go - >> - Boot script timeout (1000ms resolution): 1 - ... - Update RedBoot non-volatile configuration - continue (y/n)? y - ... Unlock from 0xf0fc0000-0xf0fc1000: . - ... Erase from 0xf0fc0000-0xf0fc1000: . - ... Program from 0x0ffd2000-0x0ffd3000 at 0xf0fc0000: . - ... Lock from 0xf0fc0000-0xf0fc1000: . - -The important part is that 'Run script' is true and that the commands are -'fis load boot' and 'go' ('boot' is the file created by 'fis create boot' -earlier). Confirm the update and type 'reset' to auto boot. - -The bootloader is command driven with timeout like many other OpenBSD -architectures. - - -How to boot/install IOData HDL-G: - -The hda1 partition is the boot partition for Linux; it contains -zImage and initrd. Since RedBoot only can boot from the ext2fs partition -it is very important that this partition be present and not be reformatted. -If this partition is destroyed, it will be necessary to remove the HD and -recreate the partition on another machine. Note: RedBoot should be able -to boot from the network, however that has been unsuccessful on IODATA HDL-G -so far. - -To install OpenBSD, boot linux, and copy 'boot' and 'bsd.rd' into the -partition mounted on /dev/hda1, after that has been done, it is possible -to reboot into OpenBSD and install the device. Installation can proceed -as on other machines, however care must be take to not remove wd0i/hda1 -partition (fdisk partition 0). DO NOT chose the 'full disk installation' -option. - -Unfortunately, since IODATA did not provide the 'fconfig' command it -is not possible to change the boot commands run when RedBoot starts, -thus it not possible to autoboot OpenBSD; the OpenBSD/MACHINE bootloader -is currently unable to work when loaded as `zImage'. Futhermore, to -disable autobooting into Linux, at least one of the zImage and initrd files -need to be renamed or removed. This can be done from the shell in bsd.rd. - -To load the ramdisk kernel to install use the commands - - RedBoot> load -m disk hda1:/bsd.rd - RedBoot> go - -to boot normally, load the bootloader which will give options to boot other -kernels. - - RedBoot> load -m disk hda1:/boot - RedBoot> go - -Since this bootloader is able to boot any kernel from the OpenBSD root -partition, it is not necessary to keep bsd.rd on the hda1 partition after -OpenBSD is installed. + http://www.pccables.com/07120.htm + + and *not* the more straightforward to solder "crossed" type: + + http://www.pccables.com/07121.htm. + + If you wish to check a cable, or make your own, the pinouts are: + + DB9 IDC10 + === ===== + 1 2 3 4 5 1 3 5 7 9 + 6 7 8 9 2 4 6 8 10 + + Wire pin 1 to 1, 2 to 2 etc, with 10 not connected. + + On the Thecus N2100, it is also necessary to move jumper J3 to J4 to + properly route the serial port interrupt to allow serial to work under + OpenBSD. This jumper is located under the disk drives, so you may wish + to ensure its correct setting while you are installing the disk(s). + For instructions on assembling/disassembling your N2100, see the N2100 + Manual at + http://www.thecus.com/download/manual/N2100%20UM%20EN.pdf + + + Booting Thecus N2100 + + When you have connected your computer, a command such as + "tip -115200 tty00" (assuming tty00 is your serial port device) + should connect you to the Thecus console. Now apply power to the + Thecus and start it. + + After some device probe information, you should see this prompt: + + == Executing boot script in 3.000 seconds - enter ^C to abort + + To enter interactive RedBoot, it is necessary to press ^C within the + given number of seconds of the prompt. It will typically accept the + ^C if typed during the diagnostics that precede this prompt. + + The recommended way to boot OpenBSD on Thecus is to configure + networking and load bsd.rd from a TFTP server or HTTP server. + + Update the IP address, netmask and server address with the commands + listed below to allow booting from the network. TFTP and HTTP are + supported. (BOOTP configuration _may_ not work) + + Using ip_address only allows you to set the local IP address and + the IP address of the server where bsd.rd is located. This command + takes effect immediately but will not persist across a reboot. + + RedBoot> ip_address -l 10.0.0.21 -h 10.0.0.7 + IP: 10.0.0.21/255.255.255.0, Gateway: 0.0.0.0 + Default server: 10.0.0.7, DNS server IP: 0.0.0.0 + + Once you have done this, and have set up your TFTP server on + the gateway machine (10.0.0.7 in the above example), you can + boot manually. + + RedBoot> load /bsd.rd + Using default protocol (TFTP) + Entry point: 0x00200000, address range: 0x00200000-0x0066a49c + RedBoot> go + + Once OpenBSD is installed on the hard disk, you will only need to + load the OpenBSD/MACHINE boot loader (/boot) the same way, and just + hit "return" to boot OpenBSD. + + + Automatic Booting + + However, for easier booting, you may wish to store the OpenBSD boot + loader in the flash memory, so that the Thecus will boot automatically + into OpenBSD when it is powered up. + Doing so disables the devices' built-in Linux kernel, however, and + makes it difficult or impossible to apply future RedBoot firmware + upgrades. There are two general approaches: + 1) Just change the boot configuration (using 'fconfig') to automate + the above booting (your TFTP or HTTP boot server will still be + needed). + 2) Remove a file from the flash and replace it with OpenBSD's /boot; + this configuration can then be booted standalone. + + Thecus RedBoot provides the 'fconfig' (not ifconfig) command to + change the boot configuration of the device. Also 'fis' is provided + to perform flash operations. + + Due to a change made by Thecus to the firmware, fconfig does not + work with Thecus firmware version "1.93 (Feb 2007)" or later, and + *it is thus not possible to make the Thecus auto-boot into OpenBSD* + (worse, it will let you enter the "script" commands below, but + ignore them on boot). To correct this, you must "upgrade" your + Thecus down to firmware version "1.93 Nov 29 2005" using the file + n2100-downgrade-reboot.rom *before* you remove any files from flash. + You can get this file from Thecus; they have given permission for + it to be mirrored at + http://www.darwinsys.com/openbsd/thecus.html + However, if you have removed files from flash before running this + downgrade, it is not believed to be possible to get your machine + to auto-boot. + + Once the downgrade is done, if your TFTP machine will always be + around, you can autoboot just by changing the boot script with + fconfig, as follows: (in this example, 192.168.1.254 is both the + default IP gateway and also the TFTP server): + + RedBoot> fconfig + Run script at boot: true + Boot script: + .. load /boot.armish + .. go + Enter script, terminate with empty line + >> load /boot.armish + >> go + >> + Boot script timeout (1000ms resolution): 3 + Use BOOTP for network configuration: false + Gateway IP address: 192.168.1.254 + Local IP address: 192.168.1.253 + Local IP address mask: 255.255.255.0 + Default server IP address: 192.168.1.254 + Console baud rate: 115200 + DNS server IP address: + GDB connection port: 9000 + HW Status: 0 + Force console for special debug messages: false + MAC address: 0x00:0x14:0xFD:0x30:0x25:0x14 + MAC address 2: 0x00:0x14:0xFD:0x30:0x25:0x15 + Network debug at boot time: false + Reset default: Normal + Serial number: N2100 V2.1.06 + ... Unlock from 0xf0fc0000-0xf0fc1000: . + ... Erase from 0xf0fc0000-0xf0fc1000: . + ... Program from 0x07fd2000-0x07fd3000 at 0xf0fc0000: . + ... Lock from 0xf0fc0000-0xf0fc1000: . + RedBoot> + + This configuration can easily be set back to the default, as the + Linux system does not get erased from the flash memory. To set it + back, just change the boot script with fconfig back to what it was, + for example: + + thecus_setip + fis load ramdisk + fis load kernel + exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=128M@0xa0000000" + + You could also remove the boot script altogether by not re-entering + it, so you would be dropped to the RedBoot shell by default. + + Recheck the new values and issue the 'reset' command. + + For the standalone booting option, you will have to load /boot into + the flash memory. To overwrite the Thecus ROM behaviour, it is + necessary to delete a 'rom file' and load the OpenBSD bootloader image + there. With networking configured (as above), remove a region and + load the 'boot' program. + + Initially the machine will contain much like the following: + + RedBoot> fis list + Name FLASH addr Mem addr Length Entry point + RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 + RedBoot config 0xF0FC0000 0xF0FC0000 0x00001000 0x00000000 + FIS directory 0xF0FE0000 0xF0FE0000 0x00020000 0x00000000 + ramdisk 0xF0040000 0x00800000 0x00D00000 0x00800000 + kernel 0xF0D40000 0x00200000 0x00160000 0x00200000 + user 0xF0EA0000 0xF0EA0000 0x00120000 0x00200000 + + There is no free space in the rom for the 'boot' program, so something + must be removed. + WARNING: this will make the machine unbootable into the original + Thecus server mode and it is quite difficult to restore to the + original software. + EXTREME WARNING: Do not touch the RedBoot, RedBoot config, or FIS + directory regions, as doing so will probably brick the device. + + Remove (with confirmation) a region to make space, eg 'user' (the + non-root files needed to run Linux from Flash Memory). + + RedBoot> fis delete user + Delete image 'user' - continue (y/n)? y + ... Erase from 0xf0ea0000-0xf0fc0000: ......... + ... Unlock from 0xf0fe0000-0xf1000000: . + ... Erase from 0xf0fe0000-0xf1000000: . + ... Program from 0x07fdf000-0x07fff000 at 0xf0fe0000: . + ... Lock from 0xf0fe0000-0xf1000000: . + + Load the OpenBSD/MACHINE bootloader 'boot' via TFTP or HTTP: + + RedBoot> load -m http /boot + Entry point: 0x00100000, address range: 0x00100000-0x001067e0 + + Save that loaded file to flash: + + RedBoot> fis create boot + ... Erase from 0xf0ea0000-0xf0ec0000: . + ... Program from 0x00100000-0x001067e0 at 0xf0ea0000: . + ... Unlock from 0xf0fe0000-0xf1000000: . + ... Erase from 0xf0fe0000-0xf1000000: . + ... Program from 0x07fdf000-0x07fff000 at 0xf0fe0000: . + ... Lock from 0xf0fe0000-0xf1000000: . + + Confirm its addition: + + RedBoot> fis list + Name FLASH addr Mem addr Length Entry point + RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 + RedBoot config 0xF0FC0000 0xF0FC0000 0x00001000 0x00000000 + FIS directory 0xF0FE0000 0xF0FE0000 0x00020000 0x00000000 + ramdisk 0xF0040000 0x00800000 0x00D00000 0x00800000 + kernel 0xF0D40000 0x00200000 0x00160000 0x00200000 + boot 0xF0EA0000 0x00100000 0x00020000 0x00100000 + + Now that the bootloader is in place, update fconfig to autoboot + OpenBSD: + + RedBoot> fconfig + Run script at boot: true + Boot script: + .. fis load ramdisk + .. fis load kernel + .. exec ... + Enter script, terminate with empty line + >> fis load boot + >> go + >> + Boot script timeout (1000ms resolution): 1 + ... + Update RedBoot non-volatile configuration - continue (y/n)? y + ... Unlock from 0xf0fc0000-0xf0fc1000: . + ... Erase from 0xf0fc0000-0xf0fc1000: . + ... Program from 0x0ffd2000-0x0ffd3000 at 0xf0fc0000: . + ... Lock from 0xf0fc0000-0xf0fc1000: . + + The important part is that 'Run script' is true and that the commands + are 'fis load boot' followed with 'go' ('boot' being the file created + by 'fis create boot' earlier). Confirm the update and type 'reset' + to auto boot. + + The bootloader is command driven with timeout like many other OpenBSD + architectures. + + +IOData HDL-G setup: + + The hda1 partition is the boot partition for Linux; it contains + zImage and initrd. Since RedBoot on this machine can only boot from + the ext2fs partition, it is very important that this partition be + preserved and not be reformatted. If this partition is destroyed, it + will be necessary to remove the disk drive and recreate the partition + on another machine. (RedBoot should be able to boot from the network, + however that has been unsuccessful on IODATA HDL-G so far) + + To install OpenBSD, boot linux, and copy 'boot' and 'bsd.rd' into the + partition mounted on /dev/hda1. After that has been done, it is + possible to reboot into OpenBSD and install the device. Installation + can then proceed as on other machines, however care must be take to + not remove wd0i/hda1 partition (fdisk partition 0). DO NOT chose the + 'full disk installation' option. + + Unfortunately, since IODATA did not provide the 'fconfig' command, it + is not possible to change the boot commands run when RedBoot starts, + thus it not possible to autoboot OpenBSD; the OpenBSD/MACHINE + bootloader is currently unable to work when loaded as `zImage'. + Futhermore, to disable autobooting into Linux, at least one of the + zImage and initrd files need to be renamed or removed. This can be + done from the shell in bsd.rd. + + To load the ramdisk kernel to install use the commands + + RedBoot> load -m disk hda1:/bsd.rd + RedBoot> go + + to boot normally, load the bootloader which will give options to boot + other kernels. + + RedBoot> load -m disk hda1:/boot + RedBoot> go + + Since this bootloader is able to boot any kernel from the OpenBSD + root partition, it is not necessary to keep bsd.rd on the hda + partition after OpenBSD is installed. diff --git a/distrib/notes/armish/xfer b/distrib/notes/armish/xfer index d4b7ad62282..41de6908e2e 100644 --- a/distrib/notes/armish/xfer +++ b/distrib/notes/armish/xfer @@ -1,8 +1,8 @@ -dnl $OpenBSD: xfer,v 1.2 2006/10/14 18:40:32 krw Exp $ +dnl $OpenBSD: xfer,v 1.3 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions DOS (FAT) partitions EXT2 partitions FTP diff --git a/distrib/notes/hp300/install b/distrib/notes/hp300/install index 438082cf957..aff718684ea 100644 --- a/distrib/notes/hp300/install +++ b/distrib/notes/hp300/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.36 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.37 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude({:-HP-IB disks-:}) The ramdisk kernel may be loaded from the network, from CD-ROM, or other @@ -103,7 +103,7 @@ OpenBSDInstallPart5 plan to install a bootblock on this disk, you can reclaim this space with the 'b' command. -OpenBSDInstallPart6({:-CD-ROM, NFS, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS, -:}) OpenBSDURLInstall diff --git a/distrib/notes/hp300/xfer b/distrib/notes/hp300/xfer index 31e3c536372..ad9cc468a95 100644 --- a/distrib/notes/hp300/xfer +++ b/distrib/notes/hp300/xfer @@ -1,15 +1,14 @@ -dnl $OpenBSD: xfer,v 1.15 2005/03/18 13:30:52 miod Exp $ +dnl $OpenBSD: xfer,v 1.16 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape Remote NFS partition FTP HTTP -OpenBSDXferShortPrelude - +OpenBSDXferPrelude OpenBSDXferBareTape(xbase xetc xfont xserv xshare) diff --git a/distrib/notes/hppa/install b/distrib/notes/hppa/install index 58e1648bb75..4e12668996a 100644 --- a/distrib/notes/hppa/install +++ b/distrib/notes/hppa/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.19 2009/10/25 20:56:24 miod Exp $ +dnl $OpenBSD: install,v 1.20 2010/03/16 17:23:09 miod Exp $ dnl lots of texts coming from {mac68k,mvme68k,vax}/install initially OpenBSDInstallPrelude @@ -134,7 +134,7 @@ OpenBSDInstallPart5(,{:- plan to install a bootblock on this disk, you can reclaim this space with the 'b' command. -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall diff --git a/distrib/notes/hppa/xfer b/distrib/notes/hppa/xfer index e53aaf89cbf..6e21bae6e76 100644 --- a/distrib/notes/hppa/xfer +++ b/distrib/notes/hppa/xfer @@ -1,16 +1,17 @@ -dnl $OpenBSD: xfer,v 1.9 2005/08/24 15:14:01 kettenis Exp $ +dnl $OpenBSD: xfer,v 1.10 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape + Remote NFS partition FTP HTTP +OpenBSDXferPrelude -OpenBSDXferShortPrelude +OpenBSDXferBootTape(xbase xetc xfont xserv xshare,lif{:--:}OSrev.fs obs=2k conv=osync) - -OpenBSDXferBootTape(xbase xetc xfont xserv xshare,lif{:--:}OSrev.fs obs=2k conv=sync) +OpenBSDXferNFS OpenBSDXferFFS diff --git a/distrib/notes/i386/install b/distrib/notes/i386/install index ad647a1b88b..003e88e3698 100644 --- a/distrib/notes/i386/install +++ b/distrib/notes/i386/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.45 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.46 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude If OpenBSD will be sharing the disk with DOS or another operating @@ -57,7 +57,7 @@ OpenBSDInstallPart5({:- If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'i', 'j' and so on.-:}) -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall diff --git a/distrib/notes/i386/xfer b/distrib/notes/i386/xfer index d43632a5e81..5119705f6d6 100644 --- a/distrib/notes/i386/xfer +++ b/distrib/notes/i386/xfer @@ -1,10 +1,10 @@ -dnl $OpenBSD: xfer,v 1.28 2007/08/02 17:33:12 david Exp $ +dnl $OpenBSD: xfer,v 1.29 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) - DOS (FAT) partitions (for upgrades only) - EXT2 partitions (for upgrades only) + FFS partitions + DOS (FAT) partitions + EXT2 partitions (NOT supported if booting from floppy) Tape dnl Remote NFS partition FTP @@ -41,7 +41,6 @@ Creating a PXE network bootable setup using OpenBSD or other Un*x-like system: OpenBSDXferShortPrelude - OpenBSDXferBareTape(xbase xetc xfont xserv xshare) dnl OpenBSDXferNFS diff --git a/distrib/notes/landisk/install b/distrib/notes/landisk/install index 59616d2e0b6..64358ddcf51 100644 --- a/distrib/notes/landisk/install +++ b/distrib/notes/landisk/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.7 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.8 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude OpenBSDInstallPart2 @@ -16,13 +16,13 @@ OpenBSDInstallMBRPart2(that's the way things are) OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall OpenBSDCDROMInstall -OpenBSDDISKInstall({:-"wdN" or -:},{:-only-:}) +OpenBSDDISKInstall({:-"wdN" or -:},,{:-, Linux (ext2) or MS-DOS-:}) OpenBSDCommonInstall diff --git a/distrib/notes/landisk/prep b/distrib/notes/landisk/prep index 7eea1b4e324..ed4e16adab3 100644 --- a/distrib/notes/landisk/prep +++ b/distrib/notes/landisk/prep @@ -1,4 +1,4 @@ -dnl $OpenBSD: prep,v 1.3 2007/02/28 22:30:05 miod Exp $ +dnl $OpenBSD: prep,v 1.4 2010/03/16 17:23:09 miod Exp $ The default configuration of the MACHINE systems comes with a Linux installation on the disk (either an IDE hard drive, or a CompactFlash card). At the moment, there is no known way to log in this installation @@ -26,7 +26,6 @@ If the machine has a hard drive, and you had to change jumpers on it to change its ``master'' status, do not forget to configure it back to ``master'' or ``single drive'', as slave drives are not bootable. - dnl I need to write a comprehensive text, also explaining that Rx/Tx dnl are swapped between the CF and HD models. In addition to the disk preparation, you will need to connect a serial diff --git a/distrib/notes/landisk/xfer b/distrib/notes/landisk/xfer index ecb27b4b223..efe67d90058 100644 --- a/distrib/notes/landisk/xfer +++ b/distrib/notes/landisk/xfer @@ -1,10 +1,10 @@ -dnl $OpenBSD: xfer,v 1.3 2007/03/01 19:18:10 miod Exp $ +dnl $OpenBSD: xfer,v 1.4 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) -dnl DOS (FAT) partitions -dnl EXT2 partitions + FFS partitions + DOS (FAT) partitions + EXT2 partitions dnl Tape FTP HTTP @@ -14,7 +14,7 @@ from one of the FTP mirrors over the internet, you may wish to transfer the sets to a local FTP server, or copy them to a partition on the target system's disk (for upgrades only). -OpenBSDXferPrelude +OpenBSDXferShortPrelude dnl OpenBSDXferBareTape(xbase xetc xfont xshare) dnl diff --git a/distrib/notes/loongson/install b/distrib/notes/loongson/install index 265ed43eaa6..76262579709 100644 --- a/distrib/notes/loongson/install +++ b/distrib/notes/loongson/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.11 2010/03/06 20:11:40 otto Exp $ +dnl $OpenBSD: install,v 1.12 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude Booting the installation media: @@ -73,6 +73,8 @@ OpenBSDURLInstall OpenBSDCDROMInstall +OpenBSDNFSInstall + OpenBSDDISKInstall({:-"wdN" or -:},,{:-, Linux (ext2) or MS-DOS-:}) OpenBSDCommonInstall @@ -82,122 +84,109 @@ dnl OpenBSDTAPEInstall dnl OpenBSDInstallWrapup - Lemote systems final steps: +Lemote systems final steps: - Lemote systems ship with a boot menu. After an installation - preserving the Linux partitions is complete, you can add an - OpenBSD entry to the boot menu to be able to boot OpenBSD - more easily. + Lemote systems ship with a boot menu. After an installation + preserving the Linux partitions is complete, you can add an OpenBSD + entry to the boot menu to be able to boot OpenBSD more easily. - The boot menu contents are found in /boot/boot.cfg on the Linux - partition. To add an OpenBSD entry, simply add a new entry in - the file, such as: + The boot menu contents are found in /boot/boot.cfg on the Linux + partition. To add an OpenBSD entry, simply add a new entry in the + file, such as: title OpenBSD kernel /dev/fs/ext2@wd0/boot/boot args "" - In the example above, /dev/fs/ext2@wd0/boot/boot is the PMON - path to the OpenBSD bootloader, which is copied to - that location by the install script. + In the example above, /dev/fs/ext2@wd0/boot/boot is the PMON path + to the OpenBSD bootloader, which is copied to that location by the + install script. - You may make OpenBSD the default option by changing the - ``default'' line near the top of the file. The value on this - line is the index of the default entry, starting at zero. So - if you added the OpenBSD entry as the fourth entry in the - file, it would become the default choice with: + You may make OpenBSD the default option by changing the ``default'' + line near the top of the file. The value on this line is the index + of the default entry, starting at zero. So if you added the OpenBSD + entry as the fourth entry in the file, it would become the default + choice with: default 3 - The timeout until the default choice is selected, in seconds, - can be modified on the ``timeout'' line. - - However, due to side effects of PMON operation, automatic - loading of OpenBSD binaries (bootloader or kernel) causes - a register dump to be silently displayed by PMON; while - it won't be visible on screen, PMON will gladly wait for - user input to continue if it believes it has written too - much output. - - To overcome this annoyance, simply change the `moresz' - environment variable to a large value (30 or larger will - do): - - PMON> set moresz 30 - - The bootloader will attempt to load the kernel file set in - the `bsd' environment variable. Should this fail, it will - wait for user commands. The value of `bsd' should be a - path within the OpenBSD root filesystem on the disk, such - as: - - PMON> set bsd /bsd - - If you have removed the Linux installation or if you do not - want to use the boot menu, you may simply disable it in the - environment, and set the `al' variable - to point to the bootloader path: - - PMON> set ShowBootMenu no - PMON> set al /dev/fs/ext2@wd0/boot/boot - - Alternatively, you might want to create a /boot/boot.cfg - file in the small Linux partition created by the installation. - - On the Fuloong 2F, getting PMON to use the serial console - is tricky, due to PMON bugs and design decisions made by - Lemote. - PMON's default serial speed is 115200, and OpenBSD will - also use that speed. By default, it is possible to use - serial input if no USB keyboard is attached. PMON will - nevertheless display its output on the VGA display. - To get full serial access, the first step is to boot - into PMON> with both serial console and VGA display but - no USB keyboard attached. - You can type on the serial console, but output will be shown - on the VGA display. Next enter the following - commands: - - PMON> set novga 1 - PMON> set nokbd 1 - PMON> set al "" - PMON> set ShowBootMenu no - - If you have a dual boot setup, mount the Linux boot partition - and rename /boot/boot.cfg so that it does not get found by - PMON. This will enable full serial access to PMON on - the Fuloong 2F. - - Gdium systems final steps: - - Gdium systems do not have a boot menu, and directly boot the - system (Linux, by default). Unfortunately, the OpenBSD - bootloader operation is very limited on this machine, as - it can not access USB devices (which means no keyboard - input as well). - - To overcome this and be able to boot OpenBSD nevertheless, - the bootloader relies upon PMON's ability to load a Linux - so-called ``initrd'' image. By making PMON load the kernel - as the ``initrd'' image, and then run the bootloader, - the bootloader will be able to ``load'' the OpenBSD kernel - correctly. - - The path to the file booted by default is set in the `al' - environment variable, and the path to the initrd image is - set in the `rd' environment variable. - - To boot the bsd kernel on the G-Key by default, assuming it - has been copied to /boot/bsd on the first ext3 partition, and - the bootloader has been copied to /boot/boot on the same - filesystem, the settings are: - - PMON> set al /dev/fs/ext2@usbg0/boot/boot - PMON> set rd /dev/fs/ext2@usbg0/boot/bsd - - Alternatively, you can disable autoboot by removing this - variable: - - PMON> unset al + The timeout until the default choice is selected, in seconds, can + be modified on the ``timeout'' line. + + However, due to side effects of PMON operation, automatic loading + of OpenBSD binaries (bootloader or kernel) causes a register dump + to be silently displayed by PMON; while it won't be visible on + screen, PMON will gladly wait for user input to continue if it + believes it has written too much output. + + To overcome this annoyance, simply change the `moresz' environment + variable to a large value (30 or larger will do): + + PMON> set moresz 30 + + The bootloader will attempt to load the kernel file set in the `bsd' + environment variable. Should this fail, it will wait for user + commands. The value of `bsd' should be a path within the OpenBSD + root filesystem on the disk, such as: + + PMON> set bsd /bsd + + If you have removed the Linux installation or if you do not want to + use the boot menu, you may simply disable it in the environment, and + set the `al' variable to point to the bootloader path: + + PMON> set ShowBootMenu no + PMON> set al /dev/fs/ext2@wd0/boot/boot + + Alternatively, you might want to create a /boot/boot.cfg file in the + small Linux partition created by the installation. + + On the Fuloong 2F, getting PMON to use the serial console is tricky, + due to PMON bugs and design decisions made by Lemote. PMON's default + serial speed is 115200, and OpenBSD will also use that speed. By + default, it is only possible to use serial input if no USB keyboard is + attached. PMON will nevertheless display its output on the VGA display. + To get full serial access, the first step is to boot into PMON> with + both serial console and VGA display but no USB keyboard attached. + You can type on the serial console, but output will be shown on the + VGA display. Next enter the following commands: + + PMON> set novga 1 + PMON> set nokbd 1 + PMON> set al "" + PMON> set ShowBootMenu no + + If you have a dual boot setup, mount the Linux boot partition and + rename /boot/boot.cfg so that it does not get found by PMON. This + will enable full serial access to PMON on the Fuloong 2F. + +Gdium systems final steps: + + Gdium systems do not have a boot menu, and directly boot the system + (Linux, by default). Unfortunately, the OpenBSD bootloader operation + is very limited on this machine, as it can not access USB devices + (which means no keyboard input as well). + + To overcome this and be able to boot OpenBSD nevertheless, the + bootloader relies upon PMON's ability to load a Linux so-called + ``initrd'' image. By making PMON load the kernel as the ``initrd''i + image, and then run the bootloader, the bootloader will be able to + ``load'' the OpenBSD kernel correctly. + + The path to the file booted by default is set in the `al' environment + variable, and the path to the initrd image is set in the `rd' + environment variable. + + To boot the bsd kernel on the G-Key by default, assuming it has been + copied to /boot/bsd on the first ext3 partition, and the bootloader + has been copied to /boot/boot on the same filesystem, the settings + are: + + PMON> set al /dev/fs/ext2@usbg0/boot/boot + PMON> set rd /dev/fs/ext2@usbg0/boot/bsd + + Alternatively, you can disable autoboot by removing this variable: + + PMON> unset al OpenBSDCongratulations diff --git a/distrib/notes/loongson/xfer b/distrib/notes/loongson/xfer index 79512365fb0..afaf85ec759 100644 --- a/distrib/notes/loongson/xfer +++ b/distrib/notes/loongson/xfer @@ -1,16 +1,20 @@ -dnl $OpenBSD: xfer,v 1.1 2010/02/03 17:10:44 miod Exp $ +dnl $OpenBSD: xfer,v 1.2 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions DOS (FAT) partitions EXT2 partitions +dnl Tape + Remote NFS partition FTP HTTP -OpenBSDXferShortPrelude +OpenBSDXferPrelude dnl usb tape drives anyone? dnl OpenBSDXferBareTape(xbase xetc xfont xserv xshare) dnl +OpenBSDXferNFS + OpenBSDXferFFS diff --git a/distrib/notes/luna88k/install b/distrib/notes/luna88k/install index a88b01f2e27..bb6aa53b353 100644 --- a/distrib/notes/luna88k/install +++ b/distrib/notes/luna88k/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.8 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.9 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -81,7 +81,7 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, NFS, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS, -:}) OpenBSDURLInstall diff --git a/distrib/notes/luna88k/xfer b/distrib/notes/luna88k/xfer index 7151bb25611..032480ced95 100644 --- a/distrib/notes/luna88k/xfer +++ b/distrib/notes/luna88k/xfer @@ -1,18 +1,17 @@ -dnl $OpenBSD: xfer,v 1.4 2008/08/06 18:23:56 miod Exp $ +dnl $OpenBSD: xfer,v 1.5 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape - Remote NFS partitions + Remote NFS partition FTP HTTP OpenBSDXferPrelude - -dnl OpenBSDXferBootTape(xbase xetc xfont xshare,bsd.rd obs=8k conv=sync) -OpenBSDXferBootTape(,bsd.rd obs=8k conv=sync) +dnl OpenBSDXferBootTape(xbase xetc xfont xshare,bsd.rd obs=8k conv=osync) +OpenBSDXferBootTape(,bsd.rd obs=8k conv=osync) OpenBSDXferNFS diff --git a/distrib/notes/m4.common b/distrib/notes/m4.common index 49115cf03cb..1c2b3db64e5 100644 --- a/distrib/notes/m4.common +++ b/distrib/notes/m4.common @@ -1,5 +1,5 @@ dnl -dnl $OpenBSD: m4.common,v 1.90 2010/03/09 20:38:43 otto Exp $ +dnl $OpenBSD: m4.common,v 1.91 2010/03/16 17:23:05 miod Exp $ dnl dnl Copyright (c) 2004 Todd T. Fries <todd@OpenBSD.org> dnl @@ -571,8 +571,8 @@ define({:-OpenBSDInstallPart6-:}, After these preparatory steps have been completed, you will be able to extract the distribution sets onto your system. There - are several install methods supported; FTP, HTTP, tape, - $1or a local disk partition.-:})dnl + are several install methods supported: + FTP, HTTP, $1or a local disk partition.-:})dnl dnl dnl Notes for various installation methods. dnl @@ -693,10 +693,11 @@ define({:-OpenBSDDISKInstall-:}, {:- To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution - sets. This is normally $1"sdN", where N is a number - 0 through 9. Next you will have to identify the partition - within that disk that holds the distribution; this is a - single letter between 'a' and 'p'. + sets. + This is normally $1"sdN", where N is a number. + Next you will have to identify the partition within that disk + that holds the distribution; this is a single letter between + 'a' and 'p'. You will also have to identify the type of file system residing in the partition identified. Currently, you can @@ -894,7 +895,8 @@ define({:-OpenBSDXferFloppyFromDOS-:}, (i.e. read-only).-:})dnl dnl define({:-OpenBSDXferFloppyFromUNIX-:}, -{:-Creating a bootable floppy disk using SunOS, Solaris or other Un*x-like system: +{:-Creating a bootable floppy disk using SunOS, Solaris or other Un*x-like +system: First, you will need obtain a local copy of the bootable filesystem image as described above. If possible use the sha1(1) command to @@ -977,7 +979,7 @@ dnl OpenBSDXferBootTape describes how to set up a non-bootable distribution dnl tape, and takes as first argument, the list of X11 sets which may be put dnl on the tape. Then at least one, and up to three arguments list the first dnl files to be put on the tape to make it bootable. Each filename can be -dnl followed by dd(1) arguments (such as conv=sync). +dnl followed by dd(1) arguments (such as conv=osync). define({:-OpenBSDXferBootTape-:}, {:-Creating an (optionally bootable) installation tape: @@ -1005,7 +1007,7 @@ ifelse(X$4,X,,{:- dd of=${TAPE} if=$4 fi for file in base etc comp game man misc $1 do - dd if=${file}OSrev.tgz of=${TAPE} obs=8k conv=sync + dd if=${file}OSrev.tgz of=${TAPE} obs=8k conv=osync done tar cf ${TAPE} bsd mt -f ${TAPE} offline diff --git a/distrib/notes/mac68k/hardware b/distrib/notes/mac68k/hardware index d6a993f390b..5b997381402 100644 --- a/distrib/notes/mac68k/hardware +++ b/distrib/notes/mac68k/hardware @@ -1,4 +1,4 @@ -dnl $OpenBSD: hardware,v 1.26 2005/09/18 23:42:03 martin Exp $ +dnl $OpenBSD: hardware,v 1.27 2010/03/16 17:23:09 miod Exp $ OpenBSD/MACHINE OSREV runs on several of the older Macintosh computers. 8MB of RAM should be sufficient to boot and a minimal system can probably be squeezed onto a 120MB partition by installing just the minimum sets. @@ -17,8 +17,8 @@ should work on: * 68040 (not including the 68LC040) The following Macintosh models are supported and tested. This means that at -least the SCSI controller, serial console and on-board ethernet will function on -these models. On some of these machines, a full 68040 CPU is required to +least the SCSI controller, serial console and on-board ethernet will function +on these models. On some of these machines, a full 68040 CPU is required to replace the default 68LC040 CPU. * LC family: LC 475, Performa 475, Performa 476 * Centris family: 610, 650 diff --git a/distrib/notes/mac68k/install b/distrib/notes/mac68k/install index 718147511f3..91aa2114738 100644 --- a/distrib/notes/mac68k/install +++ b/distrib/notes/mac68k/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.39 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.40 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude OpenBSDInstallPart2 @@ -77,15 +77,15 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:CD-ROM, NFS, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS, -:}) OpenBSDURLInstall OpenBSDCDROMInstall OpenBSDNFSInstall -dnl Not supported -dnl OpenBSDDISKInstall(,{:-only -:}) + +OpenBSDDISKInstall(,{:-only -:}) OpenBSDCommonInstall diff --git a/distrib/notes/mac68k/xfer b/distrib/notes/mac68k/xfer index 27be02ad80a..6a89174bcbe 100644 --- a/distrib/notes/mac68k/xfer +++ b/distrib/notes/mac68k/xfer @@ -1,14 +1,14 @@ -dnl $OpenBSD: xfer,v 1.19 2005/03/18 13:30:53 miod Exp $ +dnl $OpenBSD: xfer,v 1.20 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape Remote NFS partition FTP HTTP -OpenBSDXferShortPrelude +OpenBSDXferPrelude OpenBSDXferBareTape(xbase xetc xfont xserv xshare) diff --git a/distrib/notes/macppc/contents b/distrib/notes/macppc/contents index dd4f5a79bcf..b885be2ab2b 100644 --- a/distrib/notes/macppc/contents +++ b/distrib/notes/macppc/contents @@ -1,10 +1,12 @@ -dnl $OpenBSD: contents,v 1.26 2010/03/07 14:07:07 miod Exp $ +dnl $OpenBSD: contents,v 1.27 2010/03/16 17:23:09 miod Exp $ TopPart OpenBSDdistsets OpenBSDbsd +OpenBSDbsdmp + OpenBSDrd OpenBSDinstalliso diff --git a/distrib/notes/macppc/install b/distrib/notes/macppc/install index 7d1a2991d1a..3d8654d81ea 100644 --- a/distrib/notes/macppc/install +++ b/distrib/notes/macppc/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.30 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.31 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude Before you begin, you should decide if OpenBSD is to be installed @@ -140,12 +140,14 @@ OpenBSDInstallPart5({:- automatically installed if you setup a small (a few MB) MSDOS partition as position `i' in the label. -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall OpenBSDCDROMInstall +OpenBSDNFSInstall + OpenBSDDISKInstall(,,{:- or MS-DOS-:}) OpenBSDCommonInstall diff --git a/distrib/notes/macppc/whatis b/distrib/notes/macppc/whatis index 0c43545444d..098f7a22748 100644 --- a/distrib/notes/macppc/whatis +++ b/distrib/notes/macppc/whatis @@ -1,4 +1,4 @@ -dnl $OpenBSD: whatis,v 1.5 2005/03/18 13:29:46 miod Exp $ +dnl $OpenBSD: whatis,v 1.6 2010/03/16 17:23:09 miod Exp $ -OpenBSD/MACHINE runs on the ``New World'' 32 bit PowerPC-based Apple +OpenBSD/MACHINE runs on the ``New World'' PowerPC-based Apple Macintosh systems (i.e. from the iMac onwards). diff --git a/distrib/notes/macppc/xfer b/distrib/notes/macppc/xfer index afd85363153..31957f9101a 100644 --- a/distrib/notes/macppc/xfer +++ b/distrib/notes/macppc/xfer @@ -1,24 +1,26 @@ -dnl $OpenBSD: xfer,v 1.12 2005/03/18 13:30:53 miod Exp $ +dnl $OpenBSD: xfer,v 1.13 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions HFS partitions (bootloader/kernel only, using another media for d/l) Tape + Remote NFS partition FTP HTTP -OpenBSDXferShortPrelude +OpenBSDXferPrelude OpenBSD can now be booted from a CD-ROM by holding down the 'c' key during reboot. If ofwboot and bsd.rd are copied to an HFS partition, it is possible to boot from those files. Then install the rest of the files from any of the above sources. -Note: Once an OpenBSD partition exists, it is not possible to load the +Note: once an OpenBSD partition exists, it is not possible to load the kernel (bsd.rd) from an HFS partition on that disk. - OpenBSDXferBareTape(xbase xetc xfont xserv xshare) +OpenBSDXferNFS + OpenBSDXferFFS diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install index d57beca0c0b..e937101c87f 100644 --- a/distrib/notes/mvme68k/install +++ b/distrib/notes/mvme68k/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.36 2009/06/28 13:37:41 sthen Exp $ +dnl $OpenBSD: install,v 1.37 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -257,7 +257,7 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, NFS, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS, -:}) OpenBSDURLInstall diff --git a/distrib/notes/mvme68k/xfer b/distrib/notes/mvme68k/xfer index c8beffabe8e..1194f961924 100644 --- a/distrib/notes/mvme68k/xfer +++ b/distrib/notes/mvme68k/xfer @@ -1,17 +1,16 @@ -dnl $OpenBSD: xfer,v 1.7 2005/03/18 13:30:53 miod Exp $ +dnl $OpenBSD: xfer,v 1.8 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape - Remote NFS partitions + Remote NFS partition FTP HTTP OpenBSDXferPrelude - -OpenBSDXferBootTape(xbase xetc xfont xshare,stboot obs=512,bootst obs=512,bsd.rd obs=8k conv=sync) +OpenBSDXferBootTape(xbase xetc xfont xshare,stboot obs=512,bootst obs=512,bsd.rd obs=8k conv=osync) OpenBSDXferNFS diff --git a/distrib/notes/mvme88k/install b/distrib/notes/mvme88k/install index 9389d30e23e..ea45b935bd2 100644 --- a/distrib/notes/mvme88k/install +++ b/distrib/notes/mvme88k/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.27 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.28 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -230,7 +230,7 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, NFS, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS, -:}) OpenBSDURLInstall diff --git a/distrib/notes/mvme88k/xfer b/distrib/notes/mvme88k/xfer index 7eb29cf8a98..118ec8b05a0 100644 --- a/distrib/notes/mvme88k/xfer +++ b/distrib/notes/mvme88k/xfer @@ -1,17 +1,16 @@ -dnl $OpenBSD: xfer,v 1.6 2008/08/06 18:23:56 miod Exp $ +dnl $OpenBSD: xfer,v 1.7 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape - Remote NFS partitions + Remote NFS partition FTP HTTP OpenBSDXferPrelude - -OpenBSDXferBootTape(xbase xetc xfont xserv xshare,stboot obs=512,bootst obs=512,bsd.rd obs=8k conv=sync) +OpenBSDXferBootTape(xbase xetc xfont xserv xshare,stboot obs=512,bootst obs=512,bsd.rd obs=8k conv=osync) OpenBSDXferNFS diff --git a/distrib/notes/palm/install b/distrib/notes/palm/install index 721d7b539a1..f487b93e7f5 100644 --- a/distrib/notes/palm/install +++ b/distrib/notes/palm/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.2 2009/10/02 07:47:44 jasper Exp $ +dnl $OpenBSD: install,v 1.3 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude An OpenBSD/palm installation will use the PalmOS to bootstrap itself. @@ -23,7 +23,7 @@ OpenBSDInstallMBRPart2(indeed) OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall diff --git a/distrib/notes/palm/xfer b/distrib/notes/palm/xfer index 598b78e79b3..88cc7d70dc0 100644 --- a/distrib/notes/palm/xfer +++ b/distrib/notes/palm/xfer @@ -1,15 +1,13 @@ -dnl $OpenBSD: xfer,v 1.1 2009/10/02 07:26:15 jasper Exp $ +dnl $OpenBSD: xfer,v 1.2 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM + FFS partitions DOS (FAT) partitions - FFS partitions (for upgrades only) - Remote NFS partition + EXT2 partitions FTP HTTP OpenBSDXferShortPrelude -OpenBSDXferNFS - OpenBSDXferFFS diff --git a/distrib/notes/sgi/contents b/distrib/notes/sgi/contents index 8088a8813ba..4d202009dc7 100644 --- a/distrib/notes/sgi/contents +++ b/distrib/notes/sgi/contents @@ -1,12 +1,12 @@ -dnl $OpenBSD: contents,v 1.13 2010/03/07 14:54:23 miod Exp $ +dnl $OpenBSD: contents,v 1.14 2010/03/16 17:23:09 miod Exp $ TopPart OpenBSDdistsets dnl three flavours of OpenBSDbsd bsd.IP27 A stock GENERIC-IP27 MACHINE kernel for IP27 and IP35 - class machines, which will be installed on such systems - during the install. + class machines, which will be installed on such + systems during the install. bsd.IP30 A stock GENERIC-IP30 MACHINE kernel for IP30 class machines, which will be installed on such systems @@ -38,7 +38,11 @@ dnl three flavours of OpenBSDrd Used for simple installation from a pre-existing system. -OpenBSDcd +dnl can't use OpenBSDcd because of the multiple bsd.rd + cd{:--:}OSrev.iso A miniroot filesystem image suitable to be used + as a bootable CD-ROM image, but will require the base + and X sets be found via another media or network; + otherwise similar to the bsd.rd* images above. DistributionDescription(eleven) diff --git a/distrib/notes/sgi/install b/distrib/notes/sgi/install index f21b98a12ef..4768ef7b32a 100644 --- a/distrib/notes/sgi/install +++ b/distrib/notes/sgi/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.18 2009/10/10 19:20:28 miod Exp $ +dnl $OpenBSD: install,v 1.19 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -84,7 +84,7 @@ OpenBSDInstallPart5 dnl XXX Note that this is a #$%@ boot blocks limitation which should be fixed dnl XXX by reading the real label in the boot blocks. -OpenBSDInstallPart6({:-CD-ROM, NFS -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS -:}) OpenBSDURLInstall @@ -92,6 +92,8 @@ OpenBSDCDROMInstall OpenBSDNFSInstall +OpenBSDDISKInstall(,{:-only -:}) + OpenBSDCommonInstall OpenBSDTAPEInstall diff --git a/distrib/notes/sgi/prep b/distrib/notes/sgi/prep index 4722237e8be..eabe422af35 100644 --- a/distrib/notes/sgi/prep +++ b/distrib/notes/sgi/prep @@ -1,4 +1,4 @@ -dnl $OpenBSD: prep,v 1.18 2010/03/07 21:26:22 miod Exp $ +dnl $OpenBSD: prep,v 1.19 2010/03/16 17:23:09 miod Exp $ Before you install your system, you should identify your system family and familiarize yourself with the ARCBios setup and how to run programs from the Command monitor prompt. @@ -72,7 +72,8 @@ Switching from serial to graphics console and vice versa: As of OpenBSD OSREV, supported graphics console devices are: - the onboard frame buffer on IP32 systems (gbe) - - ImpactSR (Mardigras) frame buffer on IP30 (I-Series and E-Series) (impact) + - ImpactSR (Mardigras) frame buffer on IP30 (I-Series and E-Series) + (impact) - VPro family frame buffers on IP27, IP30 and IP35 systems (odyssey) And the following graphics devices are not supported yet: @@ -113,11 +114,12 @@ Setting the environment: When setting up the system to boot from disk, the ``OSLoader'' environment variable will need to be changed. - Its default value is ``sash'', which is IRIX's standalone + Its default value is ``sash'' or ``sash64'', which is IRIX's standalone shell and loader. Set it to ``boot'', the OpenBSD boot loader. - Also, by default it tries to boot a kernel named ``/unix''. To - make it boot OpenBSD, set ``OSLoadFilename'' to ``/bsd''. + The kernel image loaded by default is specified in the ``OSLoadFilename'' + variable, which defaults to ``/unix''. To boot OpenBSD, set it to + ``/bsd''. To enable automatic booting of OpenBSD once the machine has passed its diagnostic tests, change the value of ``AutoLoad'' to ``Yes''. diff --git a/distrib/notes/sgi/xfer b/distrib/notes/sgi/xfer index e79f4c9b888..3c98e06da2a 100644 --- a/distrib/notes/sgi/xfer +++ b/distrib/notes/sgi/xfer @@ -1,14 +1,14 @@ -dnl $OpenBSD: xfer,v 1.5 2008/08/06 18:23:56 miod Exp $ +dnl $OpenBSD: xfer,v 1.6 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape Remote NFS partition FTP HTTP -OpenBSDXferShortPrelude +OpenBSDXferPrelude OpenBSDXferBareTape(xbase xetc xfont xserv xshare) diff --git a/distrib/notes/socppc/contents b/distrib/notes/socppc/contents index 8f506e904d5..3091204e3f1 100644 --- a/distrib/notes/socppc/contents +++ b/distrib/notes/socppc/contents @@ -1,4 +1,4 @@ -dnl $OpenBSD: contents,v 1.9 2010/03/07 14:07:08 miod Exp $ +dnl $OpenBSD: contents,v 1.10 2010/03/16 17:23:09 miod Exp $ TopPart OpenBSDdistsets @@ -8,7 +8,8 @@ OpenBSDbsd OpenBSDrd bsd.bin A RAMDISK kernel that can be loaded directly - by the U-Boot firmware. Used for installation. + by the U-Boot firmware. Used for installation + on Thecus N1200. boot The OpenBSD/MACHINE secondary boot loader in U-Boot format. diff --git a/distrib/notes/socppc/install b/distrib/notes/socppc/install index 5d245341e30..94fd960b5b0 100644 --- a/distrib/notes/socppc/install +++ b/distrib/notes/socppc/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.5 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.6 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude OpenBSDInstallPart2 @@ -21,7 +21,7 @@ OpenBSDURLInstall OpenBSDCDROMInstall -OpenBSDDISKInstall({:-"wdN" or -:},,{:-, Linux (ext2) or MS-DOS-:}) +OpenBSDDISKInstall({:-"wdN" or -:},,{:- or MS-DOS-:}) OpenBSDCommonInstall diff --git a/distrib/notes/socppc/prep b/distrib/notes/socppc/prep index c35b5425723..3529cad47bc 100644 --- a/distrib/notes/socppc/prep +++ b/distrib/notes/socppc/prep @@ -1,214 +1,205 @@ -dnl $OpenBSD: prep,v 1.8 2010/02/17 21:16:23 kettenis Exp $ -To be able to boot the OpenBSD/MACHINE installation program on the -Thecus N1200, you will need to learn a bit about Das U-Boot, the -low-level process that controls the microprocessor after hardware -initialization. On the RouterBOARD RB600A, that task is handled by -RouterBOOT. +dnl $OpenBSD: prep,v 1.9 2010/03/16 17:23:09 miod Exp $ +To be able to boot the OpenBSD/MACHINE installation program on the Thecus +N1200, you will need to learn a bit about Das U-Boot, the low-level process +that controls the microprocessor after hardware initialization. -Talking to the Thecus +On the RouterBOARD RB600A, that task is handled by RouterBOOT. -The Thecus N1200 needs a serial cable. On the back of the disk drive -circuit board, there is either a 10-pin header (with one pin removed), -or 9 holes for you to solder in your own header. The ribbon cable -that connects from there to your serial cable or the serial port on -your computer is of the same type as used on older i386 PCs, but -be aware that there are two different types of 10-pin IDC to DB-9M -ribbon cable in use, which look identical (the differences are hidden -inside the DB-9 connector). The cable you need is wired using the -"AT-Everex" or "Asus" pinout, as described here: +Thecus N1200 setup: - http://www.pccables.com/07120.htm + Talking to the Thecus N1200 -and *not* the more straightforward to solder "crossed" type: + The Thecus N1200 needs a serial cable. On the back of the disk drive + circuit board, there is either a 10-pin header (with one pin removed), + or 9 holes for you to solder in your own header. The ribbon cable + that connects from there to your serial cable or the serial port on + your computer is of the same type as used on older i386 PCs, but + be aware that there are two different types of 10-pin IDC to DB-9M + ribbon cable in use, which look identical (the differences are hidden + inside the DB-9 connector). The cable you need is wired using the + "AT-Everex" or "Asus" pinout, as described here: - http://www.pccables.com/07121.htm. + http://www.pccables.com/07120.htm -If you wish to check a cable, or make your own, the pinouts are: + and *not* the more straightforward to solder "crossed" type: - DB9 IDC10 - === ===== - 1 2 3 4 5 1 3 5 7 9 - 6 7 8 9 2 4 6 8 10 + http://www.pccables.com/07121.htm. -Wire pin 1 to 1, 2 to 2 etc, with 10 not connected. + If you wish to check a cable, or make your own, the pinouts are: + DB9 IDC10 + === ===== + 1 2 3 4 5 1 3 5 7 9 + 6 7 8 9 2 4 6 8 10 -Booting Thecus N1200 + Wire pin 1 to 1, 2 to 2 etc, with 10 not connected. -When you have connected your computer, a command like "tip -115200 tty00" -(assuming you're using the first serial port on your machine) should -connect you to the Thecus console. Now apply power to the Thecus -and start it. -After some device probe information, you should see this prompt: + Booting the Thecus N1200 - Hit any key to stop autoboot: 1 + When you have connected your computer, a command such as + "tip -115200 tty00" (assuming tty00 is your serial port device) + should connect you to the Thecus console. Now apply power to the + Thecus and start it. -You have exactly one second to press a key and enter interactive -U-Boot. Fortunately it will typically accept a key typed during the -diagnostics that precede this prompt. + After some device probe information, you should see this prompt: -The recommended way to boot OpenBSD on Thecus is to configure networking and -load bsd.bin from a TFTP server. First networking must be configured -using the setenv command. + Hit any key to stop autoboot: 1 - => setenv ipaddr 10.0.0.21 - => setenv serverip 10.0.0.7 - => setenv gatewayip 10.0.0.7 + You have exactly one second to press a key and enter interactive + U-Boot. Fortunately it will typically accept a key typed during the + diagnostics that precede this prompt. -Once you have done this, and have set up your TFTP server on -the gateway machine (10.0.0.7 in the above example), you can -boot manually. + The recommended way to boot OpenBSD on Thecus is to configure + networking and load bsd.bin from a TFTP server. First networking must + be configured using the setenv command. - => tftpboot 200000 bsd.bin - Speed: 1000, full duplex - Using Freescale TSEC0 device - TFTP from server 10.0.0.7; our IP address is 10.0.0.21 - Filename 'bsd.bin'. - Load address: 0x200000 - Loading: ########################################################## - ############################################################# - ... - ###### - done - Bytes transferred = 295148 (480ec hex) - => go 200000 + => setenv ipaddr 10.0.0.21 + => setenv serverip 10.0.0.7 + => setenv gatewayip 10.0.0.7 -Copyright (c) 1982, 1986, 1989, 1991, 1993 - The Regents of the University of California. All rights reserved. -Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org + Once you have done this, and have set up your TFTP server on the + gateway machine (10.0.0.7 in the above example), you can boot + manually. -OpenBSD 4.3 (RAMDISK) #175: Tue Mar 4 21:54:34 MST 2008 - deraadt@socppc.openbsd.org:/usr/src/sys/arch/socppc/compile/RAMDISK -real mem = 134217728 (128MB) -avail mem = 122384384 (116MB) -... -Install(I), Upgrade(U) or Shell(S)? + => tftpboot 200000 bsd.bin + Speed: 1000, full duplex + Using Freescale TSEC0 device + TFTP from server 10.0.0.7; our IP address is 10.0.0.21 + Filename 'bsd.bin'. + Load address: 0x200000 + Loading: ########################################################## + ############################################################# + ... + ###### + done + Bytes transferred = 295148 (480ec hex) + => go 200000 -If you then install to your hard disk, in future you can -load the OpenBSD/socppc boot loader + Once OpenBSD is installed on the hard disk, you will only need to + load the OpenBSD/MACHINE boot loader: - => tftpboot 200000 boot - => bootm + => tftpboot 200000 boot + => bootm -and just hit "return" to boot OpenBSD. + and just hit "return" to boot OpenBSD. -Automatic Booting + Automatic Booting -However, for easier booting, you may wish to modify the flash -memory so that the Thecus will boot automatically into OpenBSD -when it is powered up. + However, for easier booting, you may wish to store the OpenBSD boot + loader in the flash memory, so that the Thecus will boot automatically + into OpenBSD when it is powered up. - => erase fe780000 fe800000 + => erase fe780000 fe800000 - .... done - Erased 4 sectors - => tftpboot 200000 boot - Speed: 1000, full duplex - Using Freescale TSEC0 device - TFTP from server 10.0.0.7; our IP address is 10.0.0.21 - Filename 'boot'. - Load address: 0x200000 - Loading: ########################################################## - done - Bytes transferred = 295148 (480ec hex) - => cp 200000 fe780000 20000 - Copy to Flash... - 512 KBdone - => setenv bootcmd bootm FE780000 - => saveenv - Saving Environment to Flash... - Un-Protected 2 sectors - Erasing Flash... - .. done - Erased 2 sectors - Writing to Flash... - 256 KBdone - Protected 2 sectors - => reset - -This configuration can easily be set back to the default, as the -Linux system does not get erased from the flash memory. To set it -back, just change the boot script with fconfig back to what it was, -for example: - - => setenv bootcmd flashboot - => saveenv - -The bootloader is command driven with timeout like many other OpenBSD -architectures. - -It may be needed to increase the 'bootdelay' variable in order to give -the SATA-chip a chance to initialize. Having a too short delay could cause -OpenBSD/socppc to not find it's root device (and thus kernel image). -In some cases as much as ten seconds are needed for the delay, although -five seconds will do in most cases: - - => setenv bootdelay 5 - => saveenv - - -Booting the RouterBOARD RB600A - -The RouterBOARD RB600A comes with a standard DB9 serial port, so no -special cables are needed. Like the Thecus, the default baudrate is -115200, so a command like "tip -115200 tty00" should connect you to -the RouterBOARD console. As soon as you apply power to the -RouterBOARD, it will start booting. - -Shortly after RouterBOOT starts, you will see a message like: - - Press any key within 2 seconds to enter setup. - -Since board initailization is very fast, it is rather easy to miss -this message, in which case the board will load its RouterOS (which is -just Linux) from flash. - -The recommended way to install OpenBSD on the RouterBOARD is to copy -the miniroot "miniroot{:--:}OSrev.fs" image to CompactFlash on another -machine and place in the first (J301) CompactFlash slot on the board. - -Use the dd(1) utility to copy the miniroot to CompactFlash. -The command would likely be, under OpenBSD: - dd if=miniroot{:--:}OSrev.fs of=/dev/rsd1c -Replace ``rsd1c'' with the appropriate device name for the raw device -on the system used to do the copy. - -You will need to configure your RouterBOARD to boot from CompactFlash. -To do this, enter the RouterBOOT setup by pressing a key when the -message show above appears on the serial console. This should present -you with the following menu: - - RouterBOOT-2.20 - What do you want to configure? - d - boot delay - k - boot key - s - serial console - o - boot device - f - cpu frequency - r - reset booter configuration - e - format nand - g - upgrade firmware - i - board info - p - boot protocol - t - do memory testing - x - exit setup - your choice: - -Choose 'o' to enter the boot device menu: - - Select boot device: - e - boot over Ethernet - * n - boot from NAND, if fail then Ethernet - c - boot from CompactFlash only - 1 - boot Ethernet once, then NAND - 2 - boot Ethernet once, then CompactFlash - o - boot from NAND only - b - boot chosen device -your choice: - -Choose 'c' to select CompactFlash and then, at the main menu, choose -'x' to save the setting. The board will reset, and immediately -attempt to boot from CompactFlash, straight into the OpenBSD -installer. + .... done + Erased 4 sectors + => tftpboot 200000 boot + Speed: 1000, full duplex + Using Freescale TSEC0 device + TFTP from server 10.0.0.7; our IP address is 10.0.0.21 + Filename 'boot'. + Load address: 0x200000 + Loading: ########################################################## + done + Bytes transferred = 295148 (480ec hex) + => cp 200000 fe780000 20000 + Copy to Flash... + 512 KBdone + => setenv bootcmd bootm FE780000 + => saveenv + Saving Environment to Flash... + Un-Protected 2 sectors + Erasing Flash... + .. done + Erased 2 sectors + Writing to Flash... + 256 KBdone + Protected 2 sectors + => reset + + This configuration can easily be set back to the default, as the + existing Linux system does not get erased from the flash memory. + To set it back, just change the boot command back to what it was, + for example: + + => setenv bootcmd flashboot + => saveenv + + The bootloader is command driven with timeout like many other OpenBSD + architectures. + + It may be needed to increase the 'bootdelay' variable in order to give + the SATA-chip a chance to initialize. Having a too short delay could + cause OpenBSD/MACHINE to not find its root device (and thus kernel + image). Although sometimes as much as ten seconds of delay are + necessary, five seconds will do in most cases: + + => setenv bootdelay 5 + => saveenv + + +RouterBOARD RB600A setup: + + The RouterBOARD RB600A comes with a standard DB9 serial port, so no + special cables are needed. Like the Thecus, the default baudrate is + 115200, so a command like "tip -115200 tty00" should connect you to + the RouterBOARD console. As soon as you apply power to the + RouterBOARD, it will start booting. + + Shortly after RouterBOOT starts, you will see a message like: + + Press any key within 2 seconds to enter setup. + + Since board initailization is very fast, it is rather easy to miss + this message, in which case the board will load its RouterOS (which + is just Linux) from flash. + + The recommended way to install OpenBSD on the RouterBOARD is to copy + the miniroot "miniroot{:--:}OSrev.fs" image to CompactFlash on another machine + and place in the first (J301) CompactFlash slot on the board. + + Use the dd(1) utility to copy the miniroot to CompactFlash. + The command would likely be, under OpenBSD: + dd if=miniroot{:--:}OSrev.fs of=/dev/rsd1c + Replace ``rsd1c'' with the appropriate device name for the raw device + on the system used to do the copy. + + You will need to configure your RouterBOARD to boot from CompactFlash. + To do this, enter the RouterBOOT setup by pressing a key when the + message shown above appears on the serial console. This should present + you with the following menu: + + RouterBOOT-2.20 + What do you want to configure? + d - boot delay + k - boot key + s - serial console + o - boot device + f - cpu frequency + r - reset booter configuration + e - format nand + g - upgrade firmware + i - board info + p - boot protocol + t - do memory testing + x - exit setup + your choice: + + Choose 'o' to enter the boot device menu: + + Select boot device: + e - boot over Ethernet + * n - boot from NAND, if fail then Ethernet + c - boot from CompactFlash only + 1 - boot Ethernet once, then NAND + 2 - boot Ethernet once, then CompactFlash + o - boot from NAND only + b - boot chosen device + your choice: + + Choose 'c' to select CompactFlash and then, at the main menu, choose + 'x' to save the setting. The board will reset, and immediately + attempt to boot from CompactFlash, straight into the OpenBSD + installer. diff --git a/distrib/notes/socppc/xfer b/distrib/notes/socppc/xfer index c5f8704736c..a15798cf77e 100644 --- a/distrib/notes/socppc/xfer +++ b/distrib/notes/socppc/xfer @@ -1,18 +1,13 @@ -dnl $OpenBSD: xfer,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +dnl $OpenBSD: xfer,v 1.2 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) -dnl DOS (FAT) partitions + FFS partitions + DOS (FAT) partitions dnl EXT2 partitions FTP HTTP -Although you can access the distribution sets directly from the CD-ROM or -from one of the FTP mirrors over the internet, you may wish to transfer -the sets to a local FTP server, or copy them to a partition on the target -system's disk (for upgrades only). - OpenBSDXferShortPrelude OpenBSDXferFFS diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index 25d41bf09ce..99663bce385 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -1,11 +1,13 @@ -dnl $OpenBSD: install,v 1.69 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.70 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude({:-SMD disks-:}) -There are several ways to install OpenBSD onto a disk. The easiest way -in terms of preliminary setup is to use the OpenBSD miniroot that can -be booted off your local disk's swap partition. The normal way is to -use the OpenBSD CD-ROM, or the bootable CD-ROM mini image, or an +There are several ways to install OpenBSD onto a disk. The normal way +is to use the OpenBSD CD-ROM, or the bootable CD-ROM mini image, or an installation floppy, or an installation tape, depending on your hardware. +Alternatively, if you already have an operating system installed and +do not wish to change the existing partition layout, it is simpler to +use the OpenBSD miniroot that can be booted off your local disk's swap +partition. If your SPARC is hooked up to a network, try and find a server to arrange for a diskless setup. This is a convenient way to install on a @@ -180,13 +182,13 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall OpenBSDCDROMInstall -OpenBSDDISKInstall(,{:-only -:}) +OpenBSDDISKInstall({:-"xdN", "xyN" or -:},{:-only -:}) OpenBSDCommonInstall @@ -436,9 +438,9 @@ Here's an example to illustrate this whole mess: else server# set SKIP=0 server# set KARCH=SUN4C - server# dd if=boot of=/tftpboot/boot.MACHINE.OpenBSD.$KARCH skip=$SKIP bs=32 + server{:-#-:} dd if=boot of=/tftpboot/boot.MACHINE.OpenBSD.$KARCH skip=$SKIP bs=32 server# cd /tftpboot - server# ln -s boot.MACHINE.OpenBSD.$KARCH 8273900B.$KARCH + server{:-#-:} ln -s boot.MACHINE.OpenBSD.$KARCH 8273900B.$KARCH After the boot program has been loaded into memory and given control by diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer index 008eed379a1..33dff301711 100644 --- a/distrib/notes/sparc/xfer +++ b/distrib/notes/sparc/xfer @@ -1,8 +1,8 @@ -dnl $OpenBSD: xfer,v 1.44 2007/03/01 19:17:27 miod Exp $ +dnl $OpenBSD: xfer,v 1.45 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape FTP HTTP @@ -11,9 +11,9 @@ Not all methods are supported on all SPARC Systems and some of them work only with the floppy or the miniroot installation. If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be -able to boot from it, or from the supplied bootable CD-ROM mini image. However, -not all SPARC systems support booting from CD-ROM, and the current boot -image is only known to work on sun4c and sun4m architecture workstations. +able to boot from it, or from the supplied bootable CD-ROM mini image. +However, not all SPARC systems support booting from CD-ROM, and the current +boot image is only known to work on sun4c and sun4m architecture workstations. If you can boot from the CD-ROM, you are home free and can proceed to the installation steps. If not, you will need to do some setup work to prepare a bootable image: either a floppy, hard drive, tape, or compatible net boot @@ -77,7 +77,7 @@ Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system: a partition that will be overwritten during the install process, since it actually runs off a ram-disk image in the kernel. In contrast the miniroot is a normal unix root filesystem and you - must place it in a partition that will not be overwritten until + must place it in a partition that WILL NOT BE OVERWRITTEN until you've completed the installation process. To copy the floppy image to the whole disk, overwriting labels: @@ -127,10 +127,8 @@ Creating a network bootable setup using SunOS or other Un*x-like system: as required by the netboot setup. - OpenBSDXferPrelude - -OpenBSDXferBootTape(xbase xetc xfont xserv xshare,bsd.rd obs=8k conv=sync,boot obs=8k conv=sync) +OpenBSDXferBootTape(xbase xetc xfont xserv xshare,bsd.rd obs=8k conv=osync,boot obs=8k conv=osync) OpenBSDXferFFS diff --git a/distrib/notes/sparc64/install b/distrib/notes/sparc64/install index b62c64ccee9..3361a7abc92 100644 --- a/distrib/notes/sparc64/install +++ b/distrib/notes/sparc64/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.43 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.44 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude There are several ways to install OpenBSD onto a disk. The easiest way @@ -104,7 +104,7 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, -:}) OpenBSDURLInstall diff --git a/distrib/notes/sparc64/xfer b/distrib/notes/sparc64/xfer index ea75830718f..affb76839fb 100644 --- a/distrib/notes/sparc64/xfer +++ b/distrib/notes/sparc64/xfer @@ -1,8 +1,8 @@ -dnl $OpenBSD: xfer,v 1.27 2010/03/06 13:20:40 eric Exp $ +dnl $OpenBSD: xfer,v 1.28 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM (NOT supported if booting from floppy) - FFS partitions (for upgrades only) + FFS partitions Tape FTP HTTP @@ -80,7 +80,6 @@ Creating a network bootable setup using SunOS or other Un*x-like system: OpenBSDXferPrelude - OpenBSDXferBareTape(xbase xetc xfont xserv xshare) OpenBSDXferFFS diff --git a/distrib/notes/vax/install b/distrib/notes/vax/install index 8b820c12cc7..294b5c1dd70 100644 --- a/distrib/notes/vax/install +++ b/distrib/notes/vax/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.23 2009/05/13 18:38:29 miod Exp $ +dnl $OpenBSD: install,v 1.24 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude({:-MSCP or other non-SCSI disks-:}) For most systems, the easiest way to install OpenBSD/MACHINE OSREV is via @@ -98,7 +98,7 @@ OpenBSDInstallPart4 OpenBSDInstallPart5 -OpenBSDInstallPart6({:-CD-ROM, NFS, -:}) +OpenBSDInstallPart6({:-CD-ROM, tape, NFS, -:}) OpenBSDURLInstall diff --git a/distrib/notes/vax/xfer b/distrib/notes/vax/xfer index 6b24046f96e..07272b49981 100644 --- a/distrib/notes/vax/xfer +++ b/distrib/notes/vax/xfer @@ -1,8 +1,8 @@ -dnl $OpenBSD: xfer,v 1.10 2008/08/06 18:23:56 miod Exp $ +dnl $OpenBSD: xfer,v 1.11 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions Tape Remote NFS partition FTP @@ -10,7 +10,6 @@ Installation is supported from several media types, including: OpenBSDXferPrelude - dnl Put back xserv when it is back dnl OpenBSDXferBareTape(xbase xetc xfont xserv xshare) OpenBSDXferBareTape(xbase xetc xfont xshare) diff --git a/distrib/notes/zaurus/install b/distrib/notes/zaurus/install index 75a7a01b016..a6c6149c936 100644 --- a/distrib/notes/zaurus/install +++ b/distrib/notes/zaurus/install @@ -1,4 +1,4 @@ -dnl $OpenBSD: install,v 1.26 2010/02/03 17:13:52 miod Exp $ +dnl $OpenBSD: install,v 1.27 2010/03/16 17:23:09 miod Exp $ OpenBSDInstallPrelude OpenBSD is installed on the Zaurus by effectively converting @@ -117,8 +117,6 @@ OpenBSDDISKInstall({:-"wdN" or -:},,{:-, Linux (ext2) or MS-DOS-:}) OpenBSDCommonInstall -OpenBSDTAPEInstall - OpenBSDInstallWrapup OpenBSDCongratulations diff --git a/distrib/notes/zaurus/xfer b/distrib/notes/zaurus/xfer index 3efa25c193b..b51d1dabdae 100644 --- a/distrib/notes/zaurus/xfer +++ b/distrib/notes/zaurus/xfer @@ -1,8 +1,8 @@ -dnl $OpenBSD: xfer,v 1.3 2005/03/18 13:30:53 miod Exp $ +dnl $OpenBSD: xfer,v 1.4 2010/03/16 17:23:09 miod Exp $ Installation is supported from several media types, including: CD-ROM - FFS partitions (for upgrades only) + FFS partitions DOS (FAT) partitions EXT2 partitions FTP @@ -10,7 +10,4 @@ Installation is supported from several media types, including: OpenBSDXferShortPrelude - -OpenBSDXferBareTape(xbase xetc xfont xserv xshare) - OpenBSDXferFFS |