version 1.17, 1996/05/15 12:32:40 |
version 1.18, 1996/05/20 23:17:30 |
|
|
<http> |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN"> |
|
<html> |
<head> |
<head> |
<title>OpenBSD</title> |
<title>OpenBSD</title> |
|
<base href=http://pain.hungry.com/open/www/> |
|
<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> |
</head> |
|
|
|
<body> |
|
|
<h2>OpenBSD</h2> |
<h2>OpenBSD</h2> |
|
|
<hr> |
<p> |
The OpenBSD project involves continuing development of a multiplatform |
The OpenBSD project involves continuing development of a multiplatform |
4.4BSD-based Unix-like operating system. |
4.4BSD-based Unix-like operating system. |
|
</p> |
|
|
<p> |
<p> |
OpenBSD looks a lot like NetBSD (which it is derived from, following |
OpenBSD looks a lot like NetBSD (which it is derived from, following |
the 4.4BSD roots), but is now being developed seperately. Good changes |
the 4.4BSD roots), but is now being developed seperately. Good changes |
from other free operating systems will be merged in (of course, depending |
from other free operating systems will be merged in (of course, depending |
on various factors like developer time for example.) |
on various factors like developer time for example.) |
|
</p> |
|
|
<p> |
<p> |
<ul> |
<ul> |
|
|
<li><a href=#devel>How we help developers and users</a> |
<li><a href=#devel>How we help developers and users</a> |
<li><a href=goals.html>OpenBSD project goals</a> |
<li><a href=goals.html>OpenBSD project goals</a> |
</ul> |
</ul> |
|
</p> |
|
|
<a name=curplat> |
<h3><hr><a name=curplat>Platforms currently supported.</a></h3> |
<h3><hr>Platforms currently supported.</h3> |
|
|
|
|
<p> |
Note: for some of these platforms, the platform-independent code may |
Note: for some of these platforms, the platform-independent code may |
be identical to that found in NetBSD because there isn't a specific |
be identical to that found in NetBSD because there isn't a specific |
OpenBSD developer. For other ports the differences are significant. |
OpenBSD developer. For other ports the differences are significant. |
If you find an empty page that means nothing of consequence that is |
If you find an empty page that means nothing of consequence that is |
directly port-specific has changed from NetBSD. (Of course there are |
directly port-specific has changed from NetBSD. (Of course there are |
differences, but they just aren't in the /sys/arch/XXXX directory). |
differences, but they just aren't in the /sys/arch/XXXX directory). |
|
</p> |
|
|
|
<p> |
<dl> |
<dl> |
<dt><a href=alpha.html>alpha</a> <dd> DEC Alpha-based machines. |
<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=amiga.html>amiga</a> <dd> Commodore Amiga. |
|
|
<dt><a href=sun3.html>sun3</a> <dd> Sun's sun3 models. |
<dt><a href=sun3.html>sun3</a> <dd> Sun's sun3 models. |
<dt><a href=vax.html>vax</a> <dd> DEC's VAX computers. |
<dt><a href=vax.html>vax</a> <dd> DEC's VAX computers. |
</dl> |
</dl> |
|
</p> |
|
|
<a name=futplat> |
<h3><hr><a name=futplat>New platforms under development.</a></h3> |
<h3><hr>New platforms under development.</h3> |
|
|
<p> |
<dl> |
<dl> |
<dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x 88K VME cards |
<dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x 88K VME cards |
</dl> |
</dl> |
|
</p> |
|
|
<p> |
<p> |
<h3>Platforms not being developed, but which should be</h3> |
<h3>Platforms not being developed, but which should be</h3> |
Either there is enough free code available to make porting to these |
Either there is enough free code available to make porting to these |
machines relatively easy, or it's a port which should be done. |
machines relatively easy, or it's a port which should be done. |
|
</p> |
|
|
|
<p> |
<dl> |
<dl> |
<dt><a href=hppa.html>hppa</a> <dd> Hewlett-Packard PA-RISC HP700/HP800 models. |
<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=iris.html>iris</a> <dd> SGI Iris machines. |
<dt><a href=ppc.html>ppc</a> <dd> IBM/Apple/Motorola PowerPC-based machines. |
<dt><a href=ppc.html>ppc</a> <dd> IBM/Apple/Motorola PowerPC-based machines. |
</dl> |
</dl> |
|
</p> |
|
|
<a name=snapshots> |
<hr> |
<h3><hr>Binary Snapshots.</h3> |
<h3><hr><a name=snapshots>Binary Snapshots.</a></h3> |
|
|
|
<p> |
Snapshots will be made available from time to time in the following |
Snapshots will be made available from time to time in the following |
directories:<p> |
directories: |
|
</p> |
|
|
|
<p> |
<ul> |
<ul> |
<li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots> |
<li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/snapshots> |
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots</a><br> |
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots</a><br> |
|
|
located in University of Missouri-Rolla, mid-western USA. |
located in University of Missouri-Rolla, mid-western USA. |
<!-- johns@cs.umr.edu --> |
<!-- johns@cs.umr.edu --> |
</ul> |
</ul> |
|
</p> |
|
|
|
<p> |
You should also read the <a href=snapshots.html> |
You should also read the <a href=snapshots.html> |
general description about OpenBSD snapshots</a>. |
general description about OpenBSD snapshots</a>. |
|
</p> |
|
|
<p> |
<p> |
The page for each platform (listed above) provides a link to the |
The page for each platform (listed above) provides a link to the |
specific snapshot ftp area, as well as other information you might |
specific snapshot ftp area, as well as other information you might |
find neccessary or handy. |
find neccessary or handy. |
|
</p> |
|
|
<a name=devel> |
<hr> |
<h3><hr>How we help developers and users.</h3> |
<h3><a name=devel>How we help developers and users.</a></h3> |
|
|
|
<p> |
We are moving quickly to setup `infrastructure'... as things get working |
We are moving quickly to setup `infrastructure'... as things get working |
this section will be updated. |
this section will be updated. |
|
</p> |
|
|
|
<p> |
<dl> |
<dl> |
<dt><h4>Mailing Lists:</h4> |
<dt><h4>Mailing Lists:</h4> |
<dd>Some mailing lists are used for the development and use of OpenBSD. |
<dd>Some mailing lists are used for the development and use of OpenBSD. |
In each case, send mail to |
In each case, send mail to |
<a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a> |
<a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a> |
with a message body of "<strong>subscribe mailing-list-name</strong>". |
with a message body of "<strong>subscribe mailing-list-name</strong>". |
<p> |
|
These are the mailing lists: |
These are the mailing lists: |
<dl> |
<dl> |
<dt><strong>announce</strong> |
<dt><strong>announce</strong> |
|
|
<dd>user questions and answers |
<dd>user questions and answers |
<dt><strong>source-changes</strong> |
<dt><strong>source-changes</strong> |
<dd>automated mailout of CVS source tree changes |
<dd>automated mailout of CVS source tree changes |
</ul> |
</dl> |
|
</dl> |
|
</p> |
|
|
<p> |
<p> |
For further assistance, send a message body of "<strong>help</strong>", |
For further assistance, send a message body of "<strong>help</strong>", |
and you will receive a reply outlining all your options. |
and you will receive a reply outlining all your options. |
|
</p> |
|
|
<dt><h4>FTP:</h4> |
<dl><h4>FTP:</h4> |
<dd>This is a list of currently known ftp servers:<p> |
<dd>This is a list of currently known ftp servers:<p> |
<ul> |
<ul> |
<li><a href=ftp://ftp.openbsd.org/pub/OpenBSD> |
<li><a href=ftp://ftp.openbsd.org/pub/OpenBSD> |
|
|
located in University of Missouri-Rolla, mid-western USA. |
located in University of Missouri-Rolla, mid-western USA. |
<!-- johns@cs.umr.edu --> |
<!-- johns@cs.umr.edu --> |
</ul> |
</ul> |
<p> |
|
|
|
|
<p> |
The file structure of the FTP servers is as follows: |
The file structure of the FTP servers is as follows: |
|
</p> |
|
|
<p> |
<p> |
<strong><dl> |
<strong> |
|
<dl> |
<dt>pub/OpenBSD/snapshots/ |
<dt>pub/OpenBSD/snapshots/ |
<dt>pub/OpenBSD/src/ |
<dt>pub/OpenBSD/src/ |
</dl> |
</dl> |
</strong> |
</strong> |
<p> |
</p> |
|
|
|
<p> |
If you add a new FTP mirror site, please contact |
If you add a new FTP mirror site, please contact |
<a href=mailto:deraadt@theos.com> the FTP maintainer</a>. |
<a href=mailto:deraadt@theos.com> the FTP maintainer</a>. |
|
</p> |
|
|
<dt><h4>SUP:</h4> |
<dt><h4>SUP:</h4> |
<dd>Sorry, SUP is not ready for use yet. |
<dd>Sorry, SUP is not ready for use yet. |
|
|
in the OpenBSD CVS repository. Additionally they can easily see the |
in the OpenBSD CVS repository. Additionally they can easily see the |
logs of, check out, or "diff" the source files in the OpenBSD source |
logs of, check out, or "diff" the source files in the OpenBSD source |
tree. |
tree. |
<p> |
|
|
|
|
<p> |
The latest version of CVS is available at |
The latest version of CVS is available at |
<a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>. |
<a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>. |
Versions earlier than 1.6 are not recommended, and may not work. |
Versions earlier than 1.6 are not recommended, and may not work. |
|
</p> |
|
|
<p> |
<p> |
|
There are two levels of source tree access: |
|
</p> |
|
|
There are two levels of source tree access:<p> |
|
|
|
<dl> |
<dl> |
<dt><strong>Read-write access for developers</strong> |
<dt><strong>Read-write access for developers</strong> |
<dd>Developers who need to commit changes to the source tree must have |
<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 |
an account on the OpenBSD machines. Getting this access will be a |
natural result of working on the sources with other OpenBSD developers. |
natural result of working on the sources with other OpenBSD developers. |
<p> |
</dl> |
|
</p> |
The OpenBSD cvs server is in Calgary, Alberta, Canada. |
The OpenBSD cvs server is in Calgary, Alberta, Canada. |
<p> |
<p> |
|
|
|
<dl> |
<dt><strong>Read-only access for everyone</strong> |
<dt><strong>Read-only access for everyone</strong> |
<dd>Anyone can access the read-only CVS repositories. These copies |
<dd>Anyone can access the read-only CVS repositories. These copies |
of the read-write CVS repository are mirrored often. To use one, |
of the read-write CVS repository are mirrored often. To use one, |
set your <strong>CVSROOT</strong> environment variable to one of |
set your <strong>CVSROOT</strong> environment variable to one of |
the following values: |
the following values: |
<p> |
|
<ul> |
<ul> |
<li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br> |
<li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br> |
Host also known as <strong>anoncvs.openbsd.org</strong> and |
Host also known as <strong>anoncvs.openbsd.org</strong> and |
|
|
updated every 12 hours. |
updated every 12 hours. |
</ul> |
</ul> |
</dl> |
</dl> |
|
</p> |
|
|
<p> |
<p> |
<strong>IMPORTANT NOTE:</strong> |
<strong>IMPORTANT NOTE:</strong> |
There are a few issues relating to cryptographic software that everyone |
There are a few issues relating to cryptographic software that everyone |
|
|
OpenBSD is looking for people willing to run an anoncvs server |
OpenBSD is looking for people willing to run an anoncvs server |
in Europe!</strong> |
in Europe!</strong> |
</ul> |
</ul> |
|
</p> |
|
|
<p> |
<p> |
A sample use of an anoncvs CVS server would be: |
A sample use of an anoncvs CVS server would be: |
<pre> |
<pre> |
|
|
% cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s |
% cvs diff -bc -r1.1 -r1.5 sparc/sparc/locore.s |
[shows the changes between revisions 1.1 and rev 1.5] |
[shows the changes between revisions 1.1 and rev 1.5] |
</pre> |
</pre> |
|
</p> |
|
|
|
<p> |
The CVS man page (included with the CVS sources) has much more |
The CVS man page (included with the CVS sources) has much more |
information about how CVS can be used.<p> |
information about how CVS can be used. |
|
</p> |
|
|
<p> |
<p> |
The anoncvs service gives fledgling developers a chance to learn CVS |
The anoncvs service gives fledgling developers a chance to learn CVS |
operation and get thoroughly involved in the development process |
operation and get thoroughly involved in the development process |
before getting "commit" access -- as a result of showing useful |
before getting "commit" access -- as a result of showing useful |
skills and high quality results they will naturally later be given |
skills and high quality results they will naturally later be given |
developer access. |
developer access. As well, people providing patches can create |
As well, people providing patches can create their "diff"s relative |
their "diff"s relative to the CVS tree, which will ease integration. |
to the CVS tree, which will ease integration.<p> |
</p> |
|
|
<p> |
<p> |
The CVS client uses rsh to talk to the CVS server. |
The CVS client uses rsh to talk to the CVS server. If some local |
If some local security measure like a firewall (or imperfect protocol |
security measure like a firewall (or imperfect protocol emulators |
emulators like slirp) prevents you from using rsh, you may be able |
like slirp) prevents you from using rsh, you may be able to use |
to use <a href=http://www.cs.hut.fi/ssh>ssh</a> instead (If you are |
<a href=http://www.cs.hut.fi/ssh>ssh</a> |
running Solaris, there is a kernel bug which causes problems -- contact |
instead (if you are running Solaris, there is a kernel bug which |
johns@cs.umr.edu for further details). In this case, one sets the |
causes problems -- contact |
environment variable <strong>CVS_RSH</strong> to point to ssh |
<a href=mailto:johns@cs.umr.edu>johns@cs.umr.edu</a> |
(typically <strong>/usr/local/bin/ssh</strong>). To reduce the |
for further details). In this case, one sets the environment |
performance hit the anoncvs server would take it is recommended |
variable <strong>CVS_RSH</strong> to point to ssh (typically |
(and requested) that you disable encryption. If your local site |
<strong>/usr/local/bin/ssh</strong>). To reduce the performance |
prevents you from connecting out to port 22 (which ssh defaults to |
hit the anoncvs server would take it is recommended (and requested) |
using) use port 2022. |
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> |
<p> |
Do not be tempted to turn on compression since CVS already compresses. |
Do not be tempted to turn on compression since CVS already compresses. |
Use something like the following in your <strong>$HOME/.ssh/config</strong> |
Use something like the following in your <strong>$HOME/.ssh/config</strong> |
file. |
file. |
|
</p> |
<pre> |
<pre> |
Host anoncvs.usa.openbsd.org |
Host anoncvs.usa.openbsd.org |
Cipher none |
Cipher none |
Port 2022 |
Port 2022 |
</pre> |
</pre> |
If you wish to be a new anoncvs mirror site, please contact |
|
<a href=mailto:deraadt@theos.com>the anoncvs maintainer</a>. |
<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 |
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 |
per anoncvs user (assuming the user does a large operation; while smaller |
operations use fewer resources, anoncvs still makes much more of an |
operations use fewer resources, anoncvs still makes much more of an |
impact than ftp or sup). Such anoncvs machines should have excellent |
impact than ftp or sup). Such anoncvs machines should have excellent |
network connectivity for the area they are expected to serve. |
network connectivity for the area they are expected to serve. A |
<a href=anoncvs.shar>A document which describes the setup of anoncvs |
<a href=anoncvs.shar>document</a> |
servers</a> is available. |
which describes the setup of anoncvs servers is available. |
<p> |
</p> |
|
|
</dl> |
</dl> |
|
|
<p> |
<p> |
A few places run OpenBSD... you can see them described in the |
A few places run OpenBSD... you can see them described in the |
<a href=gallery.html>Gallery</a>. |
<a href=gallery.html>Gallery</a>. |
|
</p> |
|
|
<hr> |
<hr> |
<a href=mailto:www@openbsd.org>www@openbsd.org</a> |
<a href=mailto:www@openbsd.org>www@openbsd.org</a> |
<br><small>$OpenBSD$</small> |
<br><small>$OpenBSD$</small> |
|
|
|
</body> |
|
</html> |