OpenBSD

OpenBSD


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

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.)


Platforms currently supported.

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).
alpha
DEC Alpha-based machines.
amiga
Commodore Amiga.
atari
Atari TT and Falcon models.
hp300
Hewlett-Packard HP300/HP400 machines.
i386
Your standard run-of-the-mill PC.
mac68k
Most MC680x0-based Apple Macintosh models.
mvme68k
Motorola MVME147/16x/17x MC680[346]0-based VME cards.
pc532
A rare NS32532-based computer.
pmax
DEC MIPS-based machines.
sparc
Sun's Sun4 and sun4c models (sun4m soon!).
sun3
Sun's sun3 models.
vax
DEC's VAX computers.


New platforms under development.

arm32
Acorn ARM6+ computers.
mvme88k
Motorola MVME18x/19x MC88xxx-based VME cards
pica
Acer PICA R4400

Platforms not being developed, but which should be

Either there is enough free code available to make porting to these machines relatively easy, or it's a port which should be done.
hppa
Hewlett-Packard PA-RISC HP700/HP800 models.
iris
SGI Iris machines.
ppc
various IBM, Apple, and Motorola PowerPC-based machines.


Binary Snapshots.

Snapshots will be made available from time to time in the following directories:

You should also read the general description about OpenBSD snapshots.

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.


How we help developers and users.

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

Mailing Lists:

Some mailing lists are used for the development and use of OpenBSD. In each case, send mail to majordomo@OpenBSD.org with a message body of "subscribe mailing-list-name".

These are the mailing lists:

announce
important announcements. Since this is a low volume list it is excellent for people who just want to follow important events.
tech
technical discussions
misc
user questions and answers
source-changes
automated mailout of CVS source tree changes

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

FTP:

This is a list of currently known ftp servers:

The file structure of the FTP servers is as follows:

pub/OpenBSD/snapshots/
pub/OpenBSD/src/

If you add a new FTP mirror site, please contact the FTP maintainer.

SUP:

Sorry, SUP is not ready for use yet.

CVS Access:

CVS is used to manage the OpenBSD source tree. This allows developers to edit source files on their local machines, but have the OpenBSD CVS repository track the changes. It is also easy for anyone to see the logs of, check out, or "diff" the source files in the OpenBSD source tree.

CVS is available at ftp://prep.ai.mit.edu/pub/gnu/cvs-1.6.tar.gz. Versions earlier than 1.6 are not recommended, and may not work.

There are two levels of source tree access:

Read-write access for developers
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.

The OpenBSD cvs server is in Calgary, Alberta, Canada.

Read-only access for everyone
Anyone can access the read-only CVS repository. This copy of the read-write CVS repository is mirrored six times daily. To use it, set your CVSROOT environment variable to one of the following values:

  • CVSROOT=anoncvs@anoncvs.openbsd.org:/cvs
    located at Washington University, St. Louis, mid-west USA.
    protocols: rsh, ssh, ssh port 2022.
  • CVSROOT=anoncvs@hal.cs.umr.edu:/cvs
    located at University of Missouri-Rolla, Rolla, MO, mid-west USA.
    protocols: ssh, ssh port 2022.

IMPORTANT NOTE: There are a few issues relating to cryptographic software that everyone should be aware of:

  • The OpenBSD sources are from Canada. It is legal to export crypto software from Canada to the world.
  • However, if you are outside the USA or Canada, you should not fetch the cryptographic sections of the OpenBSD sources from a cvs or anoncvs server located in the USA. The files in question are...
    • src/kerberosIV/*
    • src/lib/libc/crypt/crypt.c
    • src/lib/libc/crypt/morecrypt.c
    Because of the USA ITAR munitions list, crypto software may only be exported to Canada from the USA.
  • At the moment the only anoncvs server is in the USA. OpenBSD is looking for people willing to run an anoncvs server in Europe!

A sample use of the anoncvs CVS server would be:

% setenv CVSROOT anoncvs@anoncvs.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]
The CVS man page (included with the CVS sources) has much more information about how CVS can be used.

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.

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 ssh instead. In this case, one sets the environment variable CVS_RSH to point to ssh (typically /usr/local/bin/ssh). 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. Do not be tempted to turn on compression since CVS already compresses. Use something like the following in your $HOME/.ssh/config file.

	Host anoncvs.openbsd.org
	    Cipher none
	    Port 2022
If you wish to be a new anoncvs mirror site, please contact the anoncvs maintainer. Anoncvs mirrors require about 250MB of disk, and use up to 8MB 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 few places run OpenBSD... you can see them described in the Gallery.


www@openbsd.org