[BACK]Return to index.html CVS log [TXT][DIR] Up to [local] / www
File: [local] / www / index.html (download) (as text)

Revision 1.19, Mon May 20 23:38:50 1996 UTC (28 years ago) by fn
Branch: MAIN
Changes since 1.18: +1 -1 lines 

wrong base href.  fixed.

<!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">
<html>
<head>
<title>OpenBSD</title>
<base href=http://www.openbsd.org/>
<link rev=made href=mailto:www@openbsd.org>
<meta name="resource-type" content="document">
<meta name="description" content="the main OpenBSD page">
<meta name="keywords" content="openbsd,main">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 1996 by OpenBSD, Inc.">
</head>

<body>

<h2>OpenBSD</h2>

<p>
The OpenBSD project involves continuing development of a multiplatform
4.4BSD-based Unix-like operating system.
</p>

<p>
OpenBSD looks a lot like NetBSD (which it is derived from, following
the 4.4BSD roots), but is now being developed seperately.  Good changes
from other free operating systems will be merged in (of course, depending
on various factors like developer time for example.)
</p>

<p>
<ul>
<li><a href=#curplat>Supported platforms</a>
<li><a href=#futplat>New platforms under development</a>
<li><a href=#snapshots>Binary snapshots</a>
<li><a href=#devel>How we help developers and users</a>
<li><a href=goals.html>OpenBSD project goals</a>
</ul>
</p>

<h3><hr><a name=curplat>Platforms currently supported.</a></h3>

<p>
Note: for some of these platforms, the platform-independent code may
be identical to that found in NetBSD because there isn't a specific
OpenBSD developer. For other ports the differences are significant.
If you find an empty page that means nothing of consequence that is
directly port-specific has changed from NetBSD. (Of course there are
differences, but they just aren't in the /sys/arch/XXXX directory).
</p>

<p>
<dl>
<dt><a href=alpha.html>alpha</a>	<dd> DEC Alpha-based machines.
<dt><a href=amiga.html>amiga</a>	<dd> Commodore Amiga.
<dt><a href=arm32.html>arm32</a>	<dd> Acorn ARM6+ computers.
<dt><a href=atari.html>atari</a>	<dd> Atari TT and Falcon models.
<dt><a href=hp300.html>hp300</a>	<dd> Hewlett-Packard HP300/HP400 machines.
<dt><a href=i386.html>i386</a>		<dd> Your standard run-of-the-mill PC.
<dt><a href=mac68k.html>mac68k</a>	<dd> Most MC680x0-based Apple Macintosh models.
<dt><a href=mvme68k.html>mvme68k</a>	<dd> Motorola MVME147/16x/17x 68K VME cards.
<dt><a href=pc532.html>pc532</a>	<dd> A rare NS32532-based computer.
<dt><a href=pica.html>pica</a>		<dd> Acer PICA R4400
<dt><a href=pmax.html>pmax</a>		<dd> DEC MIPS-based machines.
<dt><a href=sparc.html>sparc</a>	<dd> Sun's Sun4 and sun4c models (sun4m soon!).
<dt><a href=sun3.html>sun3</a>		<dd> Sun's sun3 models.
<dt><a href=vax.html>vax</a>		<dd> DEC's VAX computers.
</dl>
</p>

<h3><hr><a name=futplat>New platforms under development.</a></h3>

<p>
<dl>
<dt><a href=mvme88k.html>mvme88k</a>	<dd> Motorola MVME18x/19x 88K VME cards
</dl>
</p>

<p>
<h3>Platforms not being developed, but which should be</h3>
Either there is enough free code available to make porting to these
machines relatively easy, or it's a port which should be done.
</p>

<p>
<dl>
<dt><a href=hppa.html>hppa</a>		<dd> Hewlett-Packard PA-RISC HP700/HP800 models.
<dt><a href=iris.html>iris</a>		<dd> SGI Iris machines.
<dt><a href=ppc.html>ppc</a>		<dd> IBM/Apple/Motorola PowerPC-based machines.
</dl>
</p>

<hr>
<h3><hr><a name=snapshots>Binary Snapshots.</a></h3>

<p>
Snapshots will be made available from time to time in the following
directories:
</p>

<p>
<ul>
<li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots>
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots</a><br>
located at Rutgers University, eastern USA.
<!-- davem@openbsd.org -->
<li><a href=ftp://ftp.ibp.fr/pub/OpenBSD/snapshots>
ftp://ftp.ibp.fr/pub/OpenBSD/snapshots/</a><br>
located in France.
<!-- ftpmaint@ftp.ibp.fr -->
<li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots>
ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots/</a><br>
located in University of Missouri-Rolla, mid-western USA.
<!-- johns@cs.umr.edu -->
</ul>
</p>

<p>
You should also read the <a href=snapshots.html>
general description about OpenBSD snapshots</a>.
</p>

<p>
The page for each platform (listed above) provides a link to the
specific snapshot ftp area, as well as other information you might
find neccessary or handy.
</p>

<hr>
<h3><a name=devel>How we help developers and users.</a></h3>

<p>
We are moving quickly to setup `infrastructure'... as things get working
this section will be updated.
</p>

<p>
<dl>
<dt><h4>Mailing Lists:</h4>
<dd>Some mailing lists are used for the development and use of OpenBSD.
In each case, send mail to
<a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
with a message body of "<strong>subscribe mailing-list-name</strong>".

These are the mailing lists:
<dl>
<dt><strong>announce</strong>
<dd>important announcements. Since this is a low volume list
it is excellent for people who just want to follow important events.
<dt><strong>tech</strong>
<dd>technical discussions
<dt><strong>misc</strong>
<dd>user questions and answers
<dt><strong>source-changes</strong>
<dd>automated mailout of CVS source tree changes
</dl>
</dl>
</p>

<p>
For further assistance, send a message body of "<strong>help</strong>",
and you will receive a reply outlining all your options.
</p>

<dl><h4>FTP:</h4>
<dd>This is a list of currently known ftp servers:<p>
<ul>
<li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
located at Rutgers University, eastern USA.
<!-- davem@openbsd.org -->
<li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
located in France.
<!-- ftpmaint@ftp.ibp.fr -->
<li><a href=ftp://hal.cs.umr.edu/pub/OpenBSD>
ftp://hal.cs.umr.edu/pub/OpenBSD</a><br>
located in University of Missouri-Rolla, mid-western USA.
<!-- johns@cs.umr.edu -->
</ul>

<p>
The file structure of the FTP servers is as follows:
</p>

<p>
<strong>
<dl>
<dt>pub/OpenBSD/snapshots/
<dt>pub/OpenBSD/src/
</dl>
</strong>
</p>

<p>
If you add a new FTP mirror site, please contact
<a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
</p>

<dt><h4>SUP:</h4>
<dd>Sorry, SUP is not ready for use yet.

<dt><h4>CVS Access:</h4>
<dd>CVS is used to manage the OpenBSD source tree. This allows
developers to work on a local source tree and commit their changes when
ready.  Also <strong>anyone</strong> can edit source files on their
local machines, and automatically track and merge in any changes made
in the OpenBSD CVS repository. Additionally they can easily see the
logs of, check out, or "diff" the source files in the OpenBSD source
tree.

<p>
The latest version of CVS is available at
<a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
Versions earlier than 1.6 are not recommended, and may not work.
</p>

<p>
There are two levels of source tree access:
</p>

<dl>
<dt><strong>Read-write access for developers</strong>
<dd>Developers who need to commit changes to the source tree must have
an account on the OpenBSD machines.  Getting this access will be a
natural result of working on the sources with other OpenBSD developers.
</dl>
</p>
The OpenBSD cvs server is in Calgary, Alberta, Canada. 
<p>

<dl>
<dt><strong>Read-only access for everyone</strong>
<dd>Anyone can access the read-only CVS repositories. These copies
of the read-write CVS repository are mirrored often. To use one,
set your <strong>CVSROOT</strong> environment variable to one of
the following values:
<ul>
<li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
Host also known as <strong>anoncvs.openbsd.org</strong> and
<strong>eap.ccrc.wustl.edu</strong>.<br>
located at Washington University, St. Louis, mid-west USA.<br>
protocols: rsh, ssh, ssh port 2022.<br>
updated every 4 hours.
<li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
Host also known as <strong>hal.cs.umr.edu</strong>.<br>
located at University of Missouri-Rolla, Rolla, MO, mid-west USA.<br>
protocols: ssh, ssh port 2022 (<strong>NO rsh</strong>).<br>
updated every 12 hours.
</ul>
</dl>
</p>

<p>
<strong>IMPORTANT NOTE:</strong>
There are a few issues relating to cryptographic software that everyone
should be aware of:
<ul>
<li>The OpenBSD sources are from Canada. It is legal to export crypto
software from Canada to the world.
<li>However, if you are outside the USA or Canada, you should not
fetch the cryptographic sections of the OpenBSD sources from an
anoncvs server located in the USA. The files in question are...
<ul>
<li>src/kerberosIV/*
<li>src/lib/libc/crypt/crypt.c
<li>src/lib/libc/crypt/morecrypt.c
</ul>
Because of the USA ITAR munitions list,
crypto software may only be exported to Canada from the USA.
<li><strong>At the moment all the anoncvs servers are in the USA.
OpenBSD is looking for people willing to run an anoncvs server
in Europe!</strong>
</ul>
</p>

<p>
A sample use of an anoncvs CVS server would be:
<pre>
% setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
% cd /tmp
% cvs get sparc
[copies the files from the repository to your machine]
% cvs log sparc/sparc/locore.s
[shows the commit log for the chosen file ]
% cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s
[shows the changes between revisions 1.1 and rev 1.5]
</pre>
</p>

<p>
The CVS man page (included with the CVS sources) has much more
information about how CVS can be used.
</p>

<p>
The anoncvs service gives fledgling developers a chance to learn CVS
operation and get thoroughly involved in the development process
before getting "commit" access -- as a result of showing useful
skills and high quality results they will naturally later be given
developer access.  As well, people providing patches can create
their "diff"s relative to the CVS tree, which will ease integration.
</p>

<p>
The CVS client uses rsh to talk to the CVS server.  If some local
security measure like a firewall (or imperfect protocol emulators
like slirp) prevents you from using rsh, you may be able to use
<a href=http://www.cs.hut.fi/ssh>ssh</a>
instead (if you are running Solaris, there is a kernel bug which
causes problems -- contact 
<a href=mailto:johns@cs.umr.edu>johns@cs.umr.edu</a>
for further details).  In this case, one sets the environment
variable <strong>CVS_RSH</strong> to point to ssh (typically
<strong>/usr/local/bin/ssh</strong>). To reduce the performance
hit the anoncvs server would take it is recommended (and requested)
that you disable encryption.  If your local site prevents you from
connecting out to port 22 (which ssh defaults to using) use port 2022.
</p>

<p>
Do not be tempted to turn on compression since CVS already compresses.
Use something like the following in your <strong>$HOME/.ssh/config</strong>
file.
</p>
<pre>
	Host anoncvs.usa.openbsd.org
	    Cipher none
	    Port 2022
</pre>

<p>
If you wish to be a new anoncvs mirror site, please contact the anoncvs
<a href=mailto:deraadt@theos.com>maintainer</a>.
Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
per anoncvs user (assuming the user does a large operation; while smaller
operations use fewer resources, anoncvs still makes much more of an
impact than ftp or sup).  Such anoncvs machines should have excellent
network connectivity for the area they are expected to serve.  A
<a href=anoncvs.shar>document</a>
which describes the setup of anoncvs servers is available.
</p>

</dl>

<p>
A few places run OpenBSD... you can see them described in the
<a href=gallery.html>Gallery</a>.
</p>

<hr>
<a href=mailto:www@openbsd.org>www@openbsd.org</a>
<br><small>$OpenBSD: index.html,v 1.19 1996/05/20 23:38:50 fn Exp $</small>

</body>
</html>