The Wayback Machine - https://web.archive.org/web/20190222064344/http://www.openbsd.org/21.html
Released sometime around June 1, 1997.
Copyright 1997, Theo de Raadt.
All applicable copyrights and credits are in the src.tar.gz,sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in thefiles fetched via ports.tar.gz.
Following this are the instructions if you had purchased a CDROM setinstead of attempting to doan alternate form of install. The instructions for doing an ftp (orother style of) install are very similar; the CDROM instructions areleft intact so that you can see how much easier it would have been ifyou had purchased a CDROM instead.
CD2:2.1/alpha/INSTALL.alpha
Quick installer information for people familiar with OpenBSD, and theuse of the new "disklabel -E" command. If you are at all confused wheninstalling OpenBSD, read the relevant INSTALL.* file as listed above!
Play with your BIOS options, and see if you can enable booting off aCD; try using CD1. If not, write CD1:2.1/i386/floppy21.fs to afloppy, then boot that. If you are mixing OpenBSD with anotheroperating system, you will surely need to read the INSTALL.i386document.
To make a floppy under MS-DOS, use /2.1/tools/rawrite.exe. UnderUnix, use "dd if=<file> of=/dev/<device> bs=32k" (where device couldbe "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfectfloppies with NO BAD BLOCKS or you will lose.
Using CD1, tell the BOOT ROM to load the file CD1:\2.1\arc\bsd.rd. Ifthat does not work, create a MS-DOS filesystem using your vendor's arcsetup program, copy CD1:2.1/arc/bsd.rd to there and attempt to bootit.
To boot off CD1, type "boot cdrom 2.1/sparc/bsd.rd", or"b sd(0,6,0)2.1/sparc/bsd.rd" depending on your ROM version.Alternatively, write CD1:2.1/sparc/floppy21.fs to a floppy and boot itusing "boot fd()" or "boot floppy" depending on your ROM version.Finally, a third alternative is to write CD1:2.1/sparc/kc.fs andCD1:2.1/sparc/inst.fs to two separate floppies. Then insert "kc.fs",and boot as described above. As soon as the floppy drive ejects afloppy, insert "inst.fs". Answer a bunch of questions. Reboot fromthe "kc.fs" floppy. This time, when the floppy is ejected simplyre-insert "kc.fs" again and answer a different set of questions.
Write the simpleroot21.fs onto the start of the disk using dd on anothermachine. After moving the disk drive, use "boot -f rz(0,0,0)/bsd"(2100/3100) or "boot 5/rz0a/bsd" (5000). Alternatively, install vianetwork as described in detail in INSTALL.pmax.
Create BSD partitions according to INSTALL.amiga's preparation section.Mount the CD2 under AmigaOS as device CD0: Next, execute the followingCLI command: "CD0:2.1/amiga/utils/loadbsd CD0:2.1/amiga/bsd.rd".
You can boot over the network by following the instructions inINSTALL.hp300.
Your alpha must use SRM firmware (not ARC). If you have a CDROM, youcan try "boot -fi 2.1/alpha/bsd.rd dkaX" (use "show device" to find yourCDROM drive identifier). Otherwise, write CD2:2.1/alpha/floppy.fs to afloppy and boot that by typing "boot dva0". If this fails, you can placebsd.rd on some other device and boot it, or use the provided simpleroot.
Boot MacOS as normal and partition your disk with the appropriate A/UXconfigurations. Then, extract the Macside utilities fromCD1:2.1/mac68k/utils onto your hard disk. Run Mkfs to create yourfilesystems on the A/UX partitions you just made. Then, use theBSD/Mac68k Installer to copy all the sets in CD1:2.1/mac68k/ onto yourpartitions. Finally, you will be ready to configure the BSD/Mac68kBooter with the location of your kernel and boot the system.
Theo has no real idea. In the rush to get everything else done, theinstall stuff for the mvme68k was never completed. Enough pieces areincluded so that a really skilled person could find a way to installit; perhaps using netbooting. Good luck!
src.tar.gz contains a source archive starting at /usr/src. This filecontains everything you need except for the kernel sources, which arein a separate archive. To extract:
# mkdir -p /usr/src# cd /usr/src# tar xvfz /tmp/src.tar.gz
srcsys.tar.gz contains a source archive starting at /usr/src/sys.This file contains all the kernel sources you need to rebuild kernels.To extract:
# mkdir -p /usr/src/sys# cd /usr/src# tar xvfz /tmp/srcsys.tar.gz
Both of these trees are a regular CVS checkout. Using these trees itis possible to get a head-start on using the anoncvs servers asdescribed athttp://www.OpenBSD.org/anoncvs.html.Using these filesresults in a much faster initial CVS update than you could expect froma fresh checkout of the full OpenBSD source tree.
A ports tree archive is also provided. To extract:
# cd /usr# tar xvfz /tmp/ports.tar.gz# cd ports# ls...
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Goreadhttp://www.OpenBSD.org/faq/faq15.htmlif you know nothing about portsat this point. This text is not a manual of how to use ports.Rather, it is a set of notes meant to kickstart the user on theOpenBSD ports system.
Certainly, the OpenBSD ports system is not complete. This is becausethe full integration of ports into the OpenBSD environment is a veryyoung project as of this release. We believe the ports that areprovided here are stable, but it is most important to realize thatports will continue to grow a great deal in functionality in thefuture.
As we said, ports will be growing a lot in the future. The ports/directory represents a CVS (see the manpage for cvs(1) if you aren'tfamiliar with CVS) checkout of our ports. As with our complete sourcetree, we will soon be making ports available via anoncvs. So, inorder to keep current with the, you must make the ports/ treeavailable on a read-write medium and update the tree with a commandlike:
# cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd
[Of course, you must replace the local directory and server name herewith the location of your ports collection and a nearby anoncvsserver.]
Again, it's important to see the webpage for specific instructions asthis is a very new service which hasn't yet been ironed outcompletely.
Finally, despite ports' youth, help is never far. If you'reinterested in seeing a port added, would like to help out, or justwould like to know more, the mailing list ports@openbsd.org is a goodplace to know.
[8]ページ先頭
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
