diff options
| -rw-r--r-- | distrib/notes/atari/contents | 61 | ||||
| -rw-r--r-- | distrib/notes/atari/hardware | 33 | ||||
| -rw-r--r-- | distrib/notes/atari/install | 272 | ||||
| -rw-r--r-- | distrib/notes/atari/prep | 97 | ||||
| -rw-r--r-- | distrib/notes/atari/upgrade | 36 | ||||
| -rw-r--r-- | distrib/notes/atari/whatis | 2 | ||||
| -rw-r--r-- | distrib/notes/atari/xfer | 64 | ||||
| -rw-r--r-- | distrib/notes/pc532/contents | 51 | ||||
| -rw-r--r-- | distrib/notes/pc532/hardware | 21 | ||||
| -rw-r--r-- | distrib/notes/pc532/install | 208 | ||||
| -rw-r--r-- | distrib/notes/pc532/prep | 3 | ||||
| -rw-r--r-- | distrib/notes/pc532/upgrade | 43 | ||||
| -rw-r--r-- | distrib/notes/pc532/whatis | 11 | ||||
| -rw-r--r-- | distrib/notes/pc532/xfer | 19 |
14 files changed, 0 insertions, 921 deletions
diff --git a/distrib/notes/atari/contents b/distrib/notes/atari/contents deleted file mode 100644 index 1d2be25d7bd..00000000000 --- a/distrib/notes/atari/contents +++ /dev/null @@ -1,61 +0,0 @@ -TopPart - - bins/ atari binary distribution sets; - see below. - - floppies/ atari boot and installation - floppies; see below. - - utils.openbsd/ - utils.tos/ Miscellaneous atari - installation utilities; see - installation section, below. - -There are three atari floppy images to be found in the "atari/floppies" -subdirectory of the OpenBSD OSREV distribution. One of them is a -bootable TOS kernel floppy and the other two are installation floppy's. -They are described in more detail below. There are gzipped versions -of each available, for easier downloading. (The gzipped version -have the ".gz" extension added to their names.) - -Bootable Kernel floppy: - - This TOS disk contains the loadbsd and chg_part programs - and the GENERIC kernel. It is setup so that you can insert it - into your floppy drive, and start the programs from GEM. - - This floppy is named boot-OSrev.fs - -Installation floppy: - - This disk contains a BSD root file system setup to help - you install the rest of OpenBSD. This includes formatting - and mounting your root and /usr partitions and getting - ready to extract (and possibly first fetching) the distribution - sets. There is enough on this file system to allow you to - make a slip connection, configure an ethernet, mount an NFS - file system or ftp. You can also load distribution sets from - a SCSI tape or from one of your existing TOS partitions. - - This floppy's are named "inst-OSrev.fs.1" and "inst-OSrev.fs.2". - -DistributionDescription - -OpenBSDbase(7M,19M) - -OpenBSDcomp(4M,12M) - -OpenBSDetc(50K,280K) - -OpenBSDgame(1M, 3M) - -OpenBSDman(730K,3M) - -OpenBSDmisc(2M,6M) - -OpenBSDxbase - -OpenBSDxfont - -OpenBSDxserv - diff --git a/distrib/notes/atari/hardware b/distrib/notes/atari/hardware deleted file mode 100644 index 162d6c26a8e..00000000000 --- a/distrib/notes/atari/hardware +++ /dev/null @@ -1,33 +0,0 @@ -OpenBSD/MACHINE OSREV runs on a TT030 and a Falcon. Currently an FPU is -required, although this might change in the (near) future. The -minimum amount of RAM required is 4Mb. - -Here is a table of recommended HD partition sizes for a full install: - partition: advise, with X, needed, with X - root (/) 15M 15M 10M 10M - user (/usr) 65M 100M 45M 80M - swap ----- 2M for every M ram ----- - local (/local) up to you - -As you may note the recommended size of /usr is 20M greater than -needed. This is to leave room for a kernel source and compile tree -as you will probably want to compile your own kernel. (GENERIC is -large and bulky to accommodate all people, BOOT is small and might -not have all the features you want). - -Supported devices {:-include-:}: - - The built-in SCSI host adapter - - Should support most SCSI-drives. The drives that are - currently tested are: - MAXTOR 7245S, MAXTOR 7080S, SEAGATE ST157N - - Should support most tape drives. The drives that are - currently tested are: - TANDBERG 3600 - - Should support most CD-ROM drives. - - The buildin video controller - - The building (720Kb/1.44Mb) floppydrive - - The serial2/modem2 ports - - The Falcon FX memory expansion - - The atari mouse - -If its not on this list, there is no support for it in this release. diff --git a/distrib/notes/atari/install b/distrib/notes/atari/install deleted file mode 100644 index 7ccd4c2fe22..00000000000 --- a/distrib/notes/atari/install +++ /dev/null @@ -1,272 +0,0 @@ -OpenBSDInstallPrelude - -The following is a walk-through of the steps necessary to get OpenBSD -installed on your hard disk. If you wish to stop the installation, -you may hit Control-C at any prompt, but if you do, you'll have to -begin again from scratch. - - First you need to get yourself into OpenBSD. This can be - done in a couple ways, both of which currently require - GEMDOS. - - You can insert the GEMDOS kernel floppy and select - the loadbsd program. It will ask for parameters, - supply: '-b bsd'. You can, of course, also run it - from the shell command-line in MiNT: - - loadbsd -b a:/bsd - - You should see the screen clear and some information about - your system as the kernel configures the hardware. Then - you will be prompted for a root device. At this time remove - the GEMDOS kernel boot floppy from the drive if present and - insert the BSD install floppy 1. Now type `rd0' to tell the - kernel to load the install filesystem into RAMdisk. While - While the kernel is loading, it will show a '.' for each - track loaded. After loading 80 tracks, it will ask you - to insert the next floppy. At this time, insert the BSD - install floppy 2 and hit any key. The kernel continuous - loading another 40 tracks before it continues to boot. - - The system should continue to boot. For now ignore WARNING: - messages about bad dates in clocks. Eventually you will be - be asked to enter the pathname of the shell, just hit - return. After a short while you should see a welcome - message and a prompt, asking if you wish to proceed with the - installation. - - If you wish to proceed, enter "y" and then return. - - If you have configured your hard drive[s] correctly it - should find the drive and partition that you selected to - use as your root. - - YOU ARE NOW AT THE POINT OF NO RETURN. If you confirm that - you want to install OpenBSD, your hard drive will be modified, - and perhaps its contents scrambled at the whim of the install - program. - - If you are sure you want to proceed, enter "yes" at the - prompt. - - The install program will now make the root filesystem you - specified. There should be only one error in this section - of the installation. It will look like so: - - newfs: ioctl (WDINFO): Invalid argument - newfs: /dev/rsd0a: can't rewrite disk label - - If there are any others, restart from the the beginning of - the installation process. This error is ok as the Atari - does not write disklabels currently. You should expect - this error whenever using newfs. - - Next the install program will ask you which drive and - partition you wish to use as /usr. First it will list the - available drives. Choose one. Next it will give you a - list of the partitions on that disk along with their sizes, - types, etc.. Choose the letter that corresponds to the - partition you wish to use for /usr. To be able to make the - proper selection, you need to know, that OpenBSD assigns a - special meaning to some of the partition letters: - 'a' : root filesystem - 'b' : swap partition - 'c' : whole disk - You should choose a letter in the range 'd'-'p' for your - /usr filesystem. If you are doing a full install this should - be a partition that is at least 45M-50M large. If everything is - ok the install program will then format and mount your /usr. If - not then it will ask again for a drive and partition. - - When this completes your root partition will be mounted on - /mnt and your /usr partition on /mnt/usr. An fstab will - have been created and initialized to correctly mount these - two file systems. This fstab will be in /mnt/etc. - - What you do from this point on depends on which media you're - using to install OpenBSD. Follow the appropriate instructions, - given below. - - To install from an GEMDOS partition: - - You first need to mount the GEMDOS partition - using the mount_msdos command. If e.g. your GEMDOS - partition is the first partition on sd0 you could - type: - - mkdir /mnt/gemdos - mount_msdos /dev/sd0d /mnt/gemdos - - You can use `disklabel sd0' to find out what types - of partitions are on the disk `sd0'. - - Next goto the directory in which you stored the - distribution sets. If e.g. you stored them in the - root directory of the partition: - - cd /mnt/gemdos - - When there, run "Set_tmp_dir" and choose the default - temporary directory, by hitting return at the - prompt. - - Run the "Extract" command, giving it as its sole - argument the name of the distribution set you wish - to extract. For example, to extract the base - distribution, use the command: - - Extract base20 - - and to extract the games distribution: - - Extract game20 - - If the distribution sets are in different directories, - you will need to cd to each directory in turn, running - "Set_tmp_dir" and the appropriate "Extract" command(s). - - Continue this process until you've finished installing - all of the sets which you desire to have on your - hard disk. Once you have extracted all sets and - are at the "#" prompt again, proceed to the section - "Configuring Your System," below. - - To install from tape: - - The first thing you should do is pick a temporary - directory where the distribution files can be stored. - To do this, use the command "Set_tmp_dir" and enter - your choice. The default is /mnt/usr/distrib. - - After you have picked a temporary directory, - you should issue the load command: - - Load_tape - - Next, you will be told to insert the media into - the appropriate drive, and hit return. Continue - to follow instructions until you are returned to - the "#" prompt. - - Go to the directory which contains the first - distribution set you wish to install. This is - either the directory you specified above, or possibly - a subdirectory of that directory. - - When there, run "Set_tmp_dir" again, and choose - the default temporary directory, by hitting - return at the prompt. - - Run the "Extract" command, giving it as its sole - argument the name of the distribution set you - wish to extract. For example, to extract the base - distribution, use the command: - - Extract base20 - - and to extract the games distribution: - - Extract game20 - - After the extraction is complete, go to the location - of the next set you want to extract, "Set_tmp_dir" - again, and once again issue the appropriate - extract command. Continue this process until - you've finished installing all of the sets which you - desire to have on your hard disk. - - After each set is finished, if you know that you - are running low on space you can remove the - distribution files for that set by saying: - - rm set_name.?? - - For example, if you wish to remove the distribution - files for the game09 set, after the "Extract game09" - command has completed, issue the command: - - rm game20.?? - - Once you have extracted all sets and are at the "#" prompt - again, proceed to the section "Configuring Your System," - below. - -Configuring Your System: ------------ ---- ------ - -Once you have finished extracting all of the distribution sets that -you want on your hard drive and are back at the "#" prompt, -you are ready to configure your system. - -The configuration utility expects that you have installed the base -system. If you have not, you will not be able to run it successfully -(nor will you have a functional system regardless of configuration). - -To configure the newly installed operating system, run the -command "Configure". - -Configure will ask for the machine's hostname, domain name, and other -network configuration information. - -Once you have supplied `Configure' all that it requests, your machine -will be configured well enough that when you reboot it it will -almost be a completely functional OpenBSD system. Note you should -ignore the errors from `chown' they will be corrected shortly. - -Once you are done with `Configure', halt the system with the "halt" -command (wait for "halted" to be displayed) and reboot. Then again -boot OpenBSD this time with the command: - - loadbsd bsd - -You need to do your final tweaks now. First mount your file systems -like so: - - mount -av - -Next you need to re-make your devices to get the ownership correct: - - cd /dev - ./MAKEDEV all - -Your system is now complete but not completely configured; you -should adjust the /etc/sendmail.cf file as necessary to suit your -site and/or disable sendmail and other network related programs. -These things can be found in /etc/netstart. Use vi, if you installed -the man pages you can type `man vi' or `man ed' for instructions -on how to use these somewhat non-intuitive editors. - -As mentioned at the end of the `Configure' run, you should copy the -OpenBSD kernel onto the root partition as "/bsd". There is also -another option to this. As OpenBSD/Atari has to be booted from TOS, -you could do the following: - Reserve a small GEMDOS partition of about 4Mb. This is - enough to put in a few kernels. Put the bsd kernel - into this partition. Also, edit your /etc/fstab to always - mount this partition, say as /kernels. Now make a symlink - from /bsd to /kernels/bsd. - This scheme is particularly handy when you want to make your - own kernel. When compilation is finished, you just copy - your kernel to /kernels/bsd and reboot. It's wise to - make sure there is _always_ a 'know to work' kernel image - present. - -To get the proper timezone settings, link /etc/localtime to the -appropriate file in /usr/share/zoneinfo. The link provided is to -/usr/share/zoneinfo/US/Pacific. - -Once you are done with the rest of configuration unmount your file -systems and halt your system, then reboot: - - cd / - umount -av - halt - <reboot> - -Finally you can now boot your system and it will be completely -functional: - - loadbsd -a bsd - -When it boots off the hard drive, you will have a complete -OpenBSD system! CONGRATULATIONS! (You really deserve them!!!) diff --git a/distrib/notes/atari/prep b/distrib/notes/atari/prep deleted file mode 100644 index 80705768931..00000000000 --- a/distrib/notes/atari/prep +++ /dev/null @@ -1,97 +0,0 @@ -Note you will be modifying your HD's if you mess something up here you -could lose everything on all the drives that you mess with. It is -therefore advised that you: - - Write down your current configurations. Do this - by writing down all partition info (especially their sizes). - - Back up the partitions you are keeping. - -What you need to do is partition your drives; creating -space for at least root, swap and /usr partitions and possibly at -least one more for /local if you have the space. - -The partitioning can be done in two ways, the first method heavily -relies on the AHDI way of partitioning, the second method nearly -ignores the AHDI partitioning and gives you far more flexibility. -Currently, the second method can only be achieved from a working -OpenBSD/atari system. How this should be done is described in -"upgrading to OpenBSD-labeling". - -Using AHDI partitioning: - The partitioning can be done with the AHDI-disk that is - provided with your TT or Falcon. Note that the AHDI partitioning - function erases all partitions on your hard disk even if they are - not changed! - I know this is rather stupid, but don't say I didn't warn you. - - You will need the 'chg_part' program from the boot disk to - prepare your hard disk a bit more. This program will change the - partition-id so OpenBSD knows which partitions it can use. The - synopsis is: - chg_part <driveno> <partno> <new_id> - - The drive number corresponds with the drive's SCSI-id. The new - id can be selected from one of the following acronyms: - NBU - OpenBSD User partition - NBR - OpenBSD Root partition - NBS - OpenBSD Swap partition - Because OpenBSD cannot be bootloaded (yet) and thus must be - loaded through GEM, it is unwise to use drive 'C' - (drive 0/partition 1) as a OpenBSD partition. When a partition-id - is changed, GEMDOS won't be able to recognize your drive, so be - warned that the drive labels are shifted afterwards. The chg_part - program still recognizes them, take this into account when - re-labeling partitions. Also note that the chg_part process is - reversible. So don't panic if you made a mistake. Just run - chg_part again with the same drive/partition arguments but - supplied the original partition id. - -Upgrading to OpenBSD-labeling: - First of all the new disk label functions are fully backwards - compatible with the current (old) behavior, therefore you don't - have to rename partition identifiers if you don't want to. The only - limitation is that you won't be able to write a disklabel to your - harddisk ("Device not configured."). - - If you'd like to have the flexibility of the OpenBSD disk label, - the procedure is very simple: change the identifier of the AHDI - partition that contains your OpenBSD root filesystem from NBR to NBD. - Boot OpenBSD; run `disklabel -e sd?'; disklabel will start vi; - quit vi without changing anything; now the disklabel should be - written to the NBD partition. If at this point disklabel tells - you that one or more of your partitions extend past the end of - the unit, then you have an old version of disklabel. Get the - - If you like, you can now change the NBD partition id to RAW - (this would for example be necessary if the partition must be - shared with MiNT), but keep in mind that the partition id must - be either NBD or RAW, otherwise OpenBSD won't be able to find the - disklabel. The NBS id (used for a swap partition) is no longer - needed, you can change it to whatever you like (or leave it as - is, if that's what you like :-) ). The same is true for the - NBU id's. - - WARNINGS: - - the NBD partition does not necessarily have to be the - partition that contains the OpenBSD root filesystem, but - it *must* be a partition that contains a fast filesystem. - Do *not* try this with a partition that contains a gemdos, - minix or ext2 filesystem; if you do, you'll *loose* a - filesystem. - - Now that you have a real disklabel, you can modify it in - (almost) any way you want. However, if you make a mess of - the disk label, OpenBSD may (or may not) make a mess of - your disk! No freedom without responsibility. - OpenBSD will try to warn you for a possibly dangerous - partition table, but it's up to you to either take that - warning serious or ignore it (there may be good reasons - to ignore the warning, if you know what you're doing). - - So what do you do if you have a new disk, that will be exclusively - used by OpenBSD? Very simple: don't let it get `infected' by the - AHDI `virus'. ,-) Just connect the disk to your TT/Falcon; boot - OpenBSD; run `disklabel -e'; you'll see only one large partition `d' - (there won't be any filesystem on it yet); you can create partitions - in any way you want, as you're no longer limited by an AHDI partition - table. diff --git a/distrib/notes/atari/upgrade b/distrib/notes/atari/upgrade deleted file mode 100644 index f53c1a87a89..00000000000 --- a/distrib/notes/atari/upgrade +++ /dev/null @@ -1,36 +0,0 @@ -Before updating, you probably would want to backup your original -filesystems! - -The update procedure will not overwrite or remove any files not present -in the sets you install. If you've replaced programs present in the -distribution, you have to replace them again after you did the update. -The etc-set needs special caution. You generally don't want to install -this one when upgrading. It is recommended that you get a copy of this -set and _carefully_ upgrade your configuration files by hand. -Before starting the actual procedure, make a note of the partitions your -root- and usr-filesystems are on. You'll need to mount them by hand. - -Ok, let's go. Insert the bootfloppy and follow the 'normal' installation -procedure until it asks you if you wish to proceed with the installation. -Now enter 'n' and hit return. You will be left at the shell prompt. Now -mount your root and usr filesystems on /mnt. If your root-filesystem is -on sd1a and your usr-filesystem on sd1d this would require the following -actions: - mount_ffs /dev/sd1a /mnt - mount_ffs /dev/sd1d /mnt/usr - -At this point, you can follow the section "Installing the OpenBSD System" -to install the sets. There is one difference: When Extract asks you - "Are you installing a -current snapshot? [n]" -answer 'y'. - -Once you are done installing the upgrade sets, then reboot: - cd / - umount -av - halt - <reboot> - -Now you can boot your upgraded system as usually, but take the -new kernel! To finish up, you should rebuild your /dev-directory: - cd /dev - ./MAKEDEV all diff --git a/distrib/notes/atari/whatis b/distrib/notes/atari/whatis deleted file mode 100644 index de50ed1cae5..00000000000 --- a/distrib/notes/atari/whatis +++ /dev/null @@ -1,2 +0,0 @@ -The Atari release stepped in in March 1995. This means the OpenBSD 2.0 -is the first official release of OpenBSD/Atari. diff --git a/distrib/notes/atari/xfer b/distrib/notes/atari/xfer deleted file mode 100644 index b5bd75ac3b1..00000000000 --- a/distrib/notes/atari/xfer +++ /dev/null @@ -1,64 +0,0 @@ -Installation is supported from several media types, including: - TOS HD partitions - Tape - -No matter what you do, however, you'll need to have three disks handy, -on which you will put the install and boot floppy images. - -All the images are available from the directory "atari/floppies", -under the root of the OpenBSD tree at your favorite archive site. - -If you are using OpenBSD/atari to make the floppies, you should use -the command dd(1) to write the raw floppy images (.fs files) to -the disk. To write onto fd0 use: - - dd if=inst-10.fs.1 of=/dev/rfd0b bs=9b - -If you are using TOS to make the floppies, grab the 'rawrite' utility -from the "OSREV/tools" directory and issue the command: - rawrite boot-10.fs - -This will create the boot-floppy on the floppy in drive a. The floppies -should be pre-formatted on 720Kb for both the 'dd' and 'rawrite' commands -to work. Pre-formatting can be best done using the desktop format command. -Some other utilities seem to be giving problems. - -The steps necessary to prepare the distribution sets -for installation depend on which method of installation -you choose. The various methods are explained below. - -To prepare for installing via an GEMDOS partition: - - To install OpenBSD from an GEMDOS partition, you need to - get the OpenBSD distribution sets you wish to install - on your system on to an GEMDOS partition. All of the - set_name.xx pieces can be placed in a single directory - instead of separate ones for each distribution set. This - will also simplify the installation work later on. - - Note where you place the files you will need this later. - - Once you have done this, you can proceed to the next - step in the installation process, preparing your hard disk. - -To prepare for installing via a tape: - - To install OpenBSD from a tape, you need to somehow - get the OpenBSD filesets you wish to install on - your system on to the appropriate kind of tape, - in tar format. - - If you're making the tape on a UN*X system, the easiest - way to do so is: - - tar cvf <tape_device> <files> - - where "<tape_device>" is the name of the tape device - that describes the tape drive you're using (possibly - something like /dev/nrst0, but we make no guarantees 8-). - If you can't figure it out, ask your system administrator. - "<files>" are the names of the "set_name.nnn" files - which you want to be placed on the tape. - - Once you have done this, you can proceed to the next - step in the installation process, preparing your hard disk. diff --git a/distrib/notes/pc532/contents b/distrib/notes/pc532/contents deleted file mode 100644 index da2a8b0b717..00000000000 --- a/distrib/notes/pc532/contents +++ /dev/null @@ -1,51 +0,0 @@ -TopPart - -OpenBSDfloppy - -OpenBSDdistsets - - download.c.gz Source for a pc532 ROM compat download pgm - - bsd.default.gz Upgrade kernel - - -DistributionDescription - -OpenBSDbase(6.8M,?) - -OpenBSDcomp(4.7M,?) - -OpenBSDetc(63K,?) - -OpenBSDgame(2.8M,?) - -OpenBSDman(0.8M,?) - -OpenBSDmisc(1.9M,?) - -OpenBSDxbase - -OpenBSDxfont - -OpenBSDxserv - -The initial installation process on a pc532 without OpenBSD/pc532 -is supported by the following files: - - Initial file system used via SCSI floppy or downloaded into - memory: - - inst-OSrev.fs -- file system containing boot loader - and install kernel with 2MB - ram root file system. - - download.c -- source for the program to download - inst-OSrev.fs into memory via the - pc532 ROM monitor. - - -The upgrade process is supported by having a copy of a 2. kernel -available. This file is: - - bsd.default.gz -- a kernel produced from the DEFAULT - configuration file in pc532/conf. diff --git a/distrib/notes/pc532/hardware b/distrib/notes/pc532/hardware deleted file mode 100644 index 6a182e31c3a..00000000000 --- a/distrib/notes/pc532/hardware +++ /dev/null @@ -1,21 +0,0 @@ -OpenBSD/pc532 OSREV runs on a PC532 computer. It supports a subset of the -"standard" hardware to date. This is defined as: - - 4 - 32 Megs of memory - 8 serial lines done by 4 scn2681 chips - the NCR DP8490 SCSI chip (scsi only) - Most SCSI disks work (fixed and floppy) - A few SCSI tapes work - Some SCSI CD-ROM drives work - The Matthias Pfaller Parallel Port. - -OpenBSD/pc532 currently expects the ROM monitor to be the "autoboot -monitor" of Oct/Nov 1991. It includes support to set up auto booting -of OpenBSD, including a secondary boot program that the autoboot monitor -will load that in turn loads the OpenBSD kernel from a OpenBSD file system. - -Most of the pc532 specific development of OpenBSD/pc532 was done on a -machine with 8-Megs of memory. It should run with 4-Megs of memory -although it may be slower. - - diff --git a/distrib/notes/pc532/install b/distrib/notes/pc532/install deleted file mode 100644 index eb9ef919a18..00000000000 --- a/distrib/notes/pc532/install +++ /dev/null @@ -1,208 +0,0 @@ -(IF you already have OpenBSD/pc532 installed and you only want to update -your system, see the next section.) - -To install OpenBSD/pc532, there are several things you need to know. -First, OpenBSD "autoconfigs" the scsi devices. inst{:--:}OSrev.fs has only -support for disks configured into the kernel. Starting the search at -SCSI address 0, lun 0 and increasing, the first disk found will be sd0 -regardless of the address, the second will be sd1. KLONDIKE for example -has the following devices installed: - - sd0 -> ID 0 LUN 0: Quantum LP52S hard disk drive - sd1 -> ID 1 LUN 0: Micropolis 4110 hard disk drive - sd2 -> ID 2 LUN 0: Teac FC-1, 3.5" floppy disk drive - sd3 -> ID 2 LUN 1: Teac FC-1, 5.25" floppy disk drive - cd0 -> ID 3 LUN 0: Toshiba XM-4101TA CD-ROM drive - st0 -> ID 4 LUN 0: Tandberg TDC3600 QIC tape drive - -Only sd0-sd3 are supported by the inst{:--:}OSrev.fs kernel. - -Next you need to know what the install script wants to do. This install -is script on the ram disk root that can do most of the work of configuring -your disk. - - a) The script assumes your are using the first n sectors of your - disk, where you can specify n. It will allow you to create - up to 5 file system partitions, one swap partition and one - boot partition. - - b) You should know how many total sectors are on your disk. The - configure will report a head, track, and cylinder count, but - I have found that on my disks, it reports something that makes - a smaller disk than I really had. - - c) It is possible to have the install script make a partition - over your save area AND not make a new file system, thus - preserving what is there. Then, later you can make a new - file system after you no longer need the stuff there. You - will need to do only one boot to get things working from - the disk. - -The Install Procedure: - - a) Adjust your console device settings. - The inst{:--:}OSrev.fs kernel will come up with 9600 baud, 7 bits, - even parity and one stop bit. Adjust your terminal to match - these settings. The monitor's baud rate can be changed with - "baud d'9600". - - b) Get inst{:--:}OSrev.fs and boot the kernel. - - From Floppy: (and using the autoboot monitor) - If you have a 1.44 meg SCSI floppy drive, you can put inst{:--:}OSrev.fs - onto a 3.5" floppy disk. Insert the disk into your floppy - drive and use the monitor's boot command to boot the default - image from the floppy. The image booted will ask you for a - kernel to load. Answer - sdXa:/bsd - Replace X with your drive number. For KLONDIKE X would be "2". - - Tape: - You will need to load a copy of inst{:--:}OSrev.fs into RAM. - - load the inst{:--:}OSrev.fs at 0x288000 - - run at 0x3E8820 - The boot program will ask you now for a kernel to load. Answer - rd0a:/bsd - - Serial line: - Provided with the distribution is source for program called - download. (download.c) This program when used as - "download file" will read the contents of the file and - output to standard output a byte sequence used by the pc532 - ROM monitor to download a binary file into RAM. Using this - program on a computer connected to the pc532, one can - load a copy of inst{:--:}OSrev.fs into RAM at 0x288000. The boot - sequence is now the same as with tape. - - c) Choose a disk geometry. For me, the reported geometry left - some sectors "unallocated". That is, the autoconfig message - said the disk had 2428 cylinders, 9 heads, and 93 sectors/track. - This gives a total of 2032236 sectors, but I knew that I had - 2053880 sectors. - - To help in this process, there is a program "factor" that is - on the inst{:--:}OSrev.fs. The usage is "factor number" and it lists - the prime factors of number. - For example, with the 2053880 sector disk I got: - - ---->~/sd1 - - steelhead[3]$ factor 2053880 - 2053880: 2 2 2 5 51347 - - Not many to choose from, so I tried ... - - ---->~/sd1 - steelhead[4]$ factor 2053820 - 2053820: 2 2 5 103 997 - - Now I'd like to get about a meg per track: - steelhead[5]$ echo "2 * 997"|bc - 1994 - - Now I need the number of tracks (or cylinders): - steelhead[5]$ echo "2 * 5 * 103"|bc - 1030 - - So I ended up choosing 1030 cylinders, 1 head, 1994 sectors/track. - I "lost" only 60 sectors, but got a "reasonable geometry". - - d) run "install" -- it will ask you for the disk geometry and other - questions. It will ask you for the geometry and then ask you - how many of those sectors you want to use for OpenBSD. It also - wants to know the size of your boot partition (to be used with - the auto-boot monitor), your root partition, your swap partition, - and then any other partitions you may want. For the "other" - partitions, it will ask for a mount point. The mount point will - be "relative to /" and should not {:-include-:} the leading "/". Also, - IF you do not want the partition to have newfs run on it (that is - it might be the last one and have a copy of inst{:--:}.fs) enter "NO" - to the mount point and it will not run newfs on the partition. - It will enter the partition into the disklabel. - - e) look around, if you want ... and then halt OpenBSD. - - f) reboot the machine. Using the autoboot monitor, all you should have - to do is give the ROM monitor command "boot". The secondary - UFS boot program eventually times out and auto-loads /bsd. - You can get it to do it faster by hitting "return". - If you are NOT using the autoboot monitor, it's time to warm - up your eprom burner :-) - - g) Now it is time to load all the other files of the distribution: - You can do this via -- - - a) a TCP/IP link (slip, ppp or plip) - you have ifconfig, slattach, route, netstat, - hostname and ftp on the mini-root. You can even - use nfs... - Plip is only an option if you have installed a - centronics port in your pc532. - You do have access to vi to edit your network - files. (/etc/resolv.conf, ...) - - b) floppy disk - - c) tape - - d) cdrom (If you have a CD with OpenBSD/532 ...) - - e) Use the ROM compatible "download" program. The program - download is included in the initial installation and - can be used as the receive end of the download by - using it as "download -r file_to_write". If the CRC is - correct, the file is retained. If the CRC is not - correct, the file is deleted. - - f) some other method? (Let me know about it.) - - h) Load the tgz files. Choose a place to put them. I would make - a directory /gz.files and put them there. If you are "short - on space," you might want to load them and extract them one - at a time. A minimum installation is "base" and "etc". It - takes about 32 Megs installed + 15 Megs for the base{:--:}OSrev.tgz. - - i) Extract the tar files in /. For example, if your *.tgz were - in a directory /gz.files, to extract base{:--:}OSrev.tgz you would: - - - cd / - - tar -xpzf /gz.files/base{:--:}OSrev.tgz - - Add v to the flags if you want a verbose extract. - - j) Extract at least "base" and "etc" for a new installation. For - "update" extracts, don't extract "etc" directly unless you - have saved your current /etc tree. For "full" installations, - extract all files. - - k) Edit the information in /etc - - - hosts - host name and address information - - myname - your host name - - mygate - hostname of gateway (assuming you have one) - - resolv.conf - which nameserver to use - - hostname.{sl0,ppp0,plip0} - interface hostname - - netstart - configures the network and says if sendmail should - be started - - ttys - make sure the console entry has the correct speed - - gettytab - I find "ap" instead of "ep" in the default entry - works better for me. - - fstab - make sure it includes all partitions you want mounted - - localtime - this is usually a link into /usr/share/zoneinfo - - Now you can adjust the kernel's default baud rate to match your - monitor's default baud rate. Do the following: - gdb -w /bsd - set scndefaultrate = YOUR_BAUD_RATE - quit - where YOUR_BAUD_RATE is the actual value, 19200, 38400 or - something slower than 9600. - If you set scndefaultrate to something bogus, you'll probably - not be able to reboot... So be careful! - - - l) Reboot the machine and it should come up in multi-user mode *IF* - you got it configured correctly. - - m) Enjoy! And help fix bugs and improve OpenBSD/pc532! - diff --git a/distrib/notes/pc532/prep b/distrib/notes/pc532/prep deleted file mode 100644 index 73ad339805e..00000000000 --- a/distrib/notes/pc532/prep +++ /dev/null @@ -1,3 +0,0 @@ -The major preparation needed is to make sure you can recover any -current bits stored on your pc532. If you don't care about your -data on the disk, you don't need to do anything.
\ No newline at end of file diff --git a/distrib/notes/pc532/upgrade b/distrib/notes/pc532/upgrade deleted file mode 100644 index 252f74293af..00000000000 --- a/distrib/notes/pc532/upgrade +++ /dev/null @@ -1,43 +0,0 @@ -The upgrade to OpenBSD OSREV is a binary upgrade; it would be prohibitive -to make users upgrade by compiling and installing the OSREV sources, and -it would be very difficult to even compile a set of instructions that -allowed them to do so. - -To do the upgrade, you must have at least base{:--:}OSrev.tgz on disk and -a copy of the proper bsd.default. It will require quite a bit -of disk space to do the upgrade. - -Since upgrading involves replacing the kernel, and most of the system -binaries, it has the potential to cause data loss. You are strongly -advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the -OpenBSD partition or on another operating system's partition, before -beginning the upgrade process. - -To upgrade your system, follow the following instructions: - - Make sure your are root. Just in case the new binaries don't - run with the old kernel, make copies of several key binaries - from /bin, /sbin and /usr/bin in some directory. (Things like - sh, cp, ls, rm, tar, halt, and others.) - - Extract the tgz files. For example, to extract base{:--:}OSrev.tgz: - - cd / - tar -xpzf /gz.files/base{:--:}OSrev.tgz - - Extract all the tgz files you want. You should carefully - work at upgrading /etc. There may be changes to file formats - depending on what version of OpenBSD/pc532 you are running. - - BE CAREFUL IF YOU ARE NOT RUNNING WITH SECURITY. The - OSREV distribution does contain support for password encryption. - It would be reasonable to save a copy of master.passwd and - remove all passwords until after you upgrade. - - Place bsd.default in / as the file bsd. - - Reboot. (Remember, detbsd.default is a 9600 console line - kernel. Read the last part of the new installation part of - these notes to find out how to change your default speed.) - - After reboot, you should make sure you check your new file systems. diff --git a/distrib/notes/pc532/whatis b/distrib/notes/pc532/whatis deleted file mode 100644 index 28ba57ed5bd..00000000000 --- a/distrib/notes/pc532/whatis +++ /dev/null @@ -1,11 +0,0 @@ -For the pc532 port, there are a few known problems. They {:-include-:}: - - a) ppp reports a lot of input errors on some machines. - - b) Some tape drives do not work very well. Some have hung the system. - - c) The serial drivers do not have all the desired features. (ttyflags - is the most glaring.) - - d) The disk driver is polled, not interrupt driven. - diff --git a/distrib/notes/pc532/xfer b/distrib/notes/pc532/xfer deleted file mode 100644 index e08d975dc74..00000000000 --- a/distrib/notes/pc532/xfer +++ /dev/null @@ -1,19 +0,0 @@ -The "standard" method of getting OpenBSD/pc532 onto your pc532 is -via the console terminal and using the downloading parts of the -ROM monitor. As such, usually another computer has the distribution -on disk and is connected via a serial line to your pc532's console -port. A terminal connected to the attached host computer is used -to access the pc532 console via a terminal program. The source for -a program called download is part of this distribution. Download -sends data to the ROM monitor over the serial line. - -You may need to find and read the documentation about the ROM monitor -download command and other low level commands. - -Other methods of getting OpenBSD/pc532 on your pc532 may {:-include-:} -SCSI tape or SCSI floppy disk or cloning a disk on a system -already running OpenBSD/pc532. - -If you have some operating system already running on your pc532, -you can use that OS to get OpenBSD/pc532 on a hard disk much easier than -with the ROM monitor. |