© 1995-2013 by The FreeBSD Project. All rights reserved.URL: http://lists.de.freebsd.org
Christoph P. Kukulies writes:
>> Besteht Interesse an einem OpenBSD Mirror? Ich habe jetzt
>> wieder mehr Platz auf meinem FTP-Server.
>Erzaehl mal was ueber OpenBSD - wer sind die Leute?
Frustierte ehemalige NetBSD User, denen die Politik des
NetBSD-Core-Teams zu konservativ ist.
http://www.openbsd.org
OPENBSD
[INLINE]
The picture is Copyright (C) 1996 Shawn Mueller
OPENBSD
The OpenBSD project involves continuing development of a multiplatform
4.4BSD-based Unix-like operating system.
* Changes Relative to other *BSD's
* Supported platforms
* New platforms under development
* Binary snapshots
* How we help developers and users
* OpenBSD project goals
________________________________________________________________________
Changes Relative to other *BSD's.
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.) OpenBSD
tracks NetBSD changes very closely; say anywhere between 2 days to 10
days behind the state of NetBSD-current all the time. Hence you can
truly say that OpenBSD is NetBSD PLUS MORE STUFF.
Various additions have been made. This is only a small partial list of
the major machine independent changes (ie. it is the most interesting
changes or what people ask about most often). Check the specific port
you are interested in for further details of that port -- many of them
have been extended too.
* Many many NetBSD PR's fixed (which NetBSD has not yet fixed)
* New curses library, including libform, libpanel and libmenu.
* a termlib library which understands termcap.db, needed for new
curses.
* The FreeBSD ports subsystem was integrated and is usable by you!
* ipfilter for filtering dangerous packets
* better ELF support
* nlist() that understands ELF, ECOFF, and a.out, allowing non-a.out
ports to use kvm utilies
* Verbatim integration of the GNU tools (using a wrapper Makefile)
* All the pieces needed for cross compilation are in the source
tree.
* Some LKM support in the tree.
* ATAPI support (should work on all ISA busses)
* new scsi, md5, pkg_* commands
* Numerous security related fixes
* Kerberos and other crypto in the source tree that is exportable
* Solid YP master, server, and client capabilities.
* /dev/rnd -- source of random data
* In-kernel update(8) with an adaptive algorithm
* Some ddb improvements and extensions
* Numerous scsi fixes
* new system calls: rfork(), minherit(), poll().
* select() that can handle any amount of file descriptors.
* kernfs extensions
* ATM support (support for one company's sparc & i386 cards
available)
* Boot kernels with "-c" to edit/enable/disable device configuration
tables
* pax as tar, gnutar is toast
* Even more security fixes.
* Linux ext2fs support coming soon!
________________________________________________________________________
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.
arm32
Acorn ARM6+ computers.
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 68K VME cards.
pc532
A rare NS32532-based computer.
pica
Acer PICA R4400
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.
mvme88k
Motorola MVME18x/19x 88K VME cards
ppc
IBM/Apple/Motorola PowerPC-based machines.
Platforms not being developed, but which should be
There is enough free code available to make porting to these machines
relatively easy.
hppa
Hewlett-Packard PA-RISC HP700/HP800 models.
iris
SGI Iris machines.
________________________________________________________________________
________________________________________________________________________
Binary Snapshots.
Snapshots will be made available from time to time in the following
directories. Please do not fetch binaries directly from
cvs.openbsd.org, but instead use one of these mirrors.
* ftp://ftp.openbsd.org/pub/OpenBSD/snapshots
located at Rutgers University, eastern USA.
* ftp://ftp.ibp.fr/pub/OpenBSD/snapshots/
located in France.
* ftp://hal.cs.umr.edu/pub/OpenBSD/snapshots/
located in University of Missouri-Rolla, mid-western USA.
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.
Mailing Lists:
Some mailing lists are used for the development and use of
OpenBSD. In each case, send mail to majordomo(at)OpenBSD.org with
a message body of "subscribe mailing-list-name". There is a
only minimal set of mailing lists intentionally; among other
benefits such as more communication it reduces cross-posting.
There are no private mailing lists.
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.
Bug tracking:
We run GNATS for tracking bugs: Click here to enter the bug tracking
system.
FTP:
This is a list of currently known ftp servers:
+ ftp://ftp.openbsd.org/pub/OpenBSD
located at Rutgers University, eastern USA.
+ ftp://ftp.ibp.fr/pub/OpenBSD
located in France.
+ ftp://hal.cs.umr.edu/pub/OpenBSD
located in University of Missouri-Rolla, mid-western USA.
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, unlike other *BSD projects, the SUP service is not
available. We do not believe the SUP service to be a good tool
for source code access. But read below for the description of
the anoncvs service!
CVS Access:
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 anyone 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.
The latest version of CVS is available at Cyclic. 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 repositories. These
copies of the read-write CVS repository are mirrored
often. To use one, set your CVSROOT environment variable
to one of the following values:
o CVSROOT=anoncvs(at)anoncvs.usa.openbsd.org:/cvs
Host also known as anoncvs.openbsd.org and
eap.ccrc.wustl.edu.
located at Washington University, St. Louis, mid-west
USA.
maintained by Chuck Cranor.
protocols: rsh, ssh, ssh port 2022.
updated every 4 hours.
o CVSROOT=anoncvs(at)anoncvs2.usa.openbsd.org:/cvs
Host also known as hal.cs.umr.edu.
located at University of Missouri-Rolla, Rolla, MO,
mid-west USA.
maintained by John Stone.
protocols: ssh, ssh port 2022 (NO rsh).
updated every 12 hours.
o CVSROOT=anoncvs(at)anoncvs.uk.openbsd.org:/cvs
Host also known as dumpty.wonderland.org.
located in London, UK.
maintained by Peter Galbavy.
protocols: rsh, ssh, ssh port 2022.
updated every 12 hours.
You may want to use `traceroute' to find out which server
is nearest you.
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
an anoncvs server located in the USA. The files in question
are...
o src/kerberosIV/*
o src/lib/libc/crypt/crypt.c
o 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 most of the anoncvs servers are in the USA.
OpenBSD is looking for people willing to run an anoncvs
servers in Europe and other places in the world!
A sample use of an anoncvs CVS server would be:
% setenv CVSROOT anoncvs(at)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]
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 (if you are running Solaris, there is a
kernel bug which causes problems -- contact johns(at)cs.umr.edu
for further details). 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.usa.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 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
document which describes the setup of anoncvs servers is
available.
_________________________________________________________________
www(at)openbsd.org
$OpenBSD: index.html,v 1.39 1996/07/02 18:06:01 deraadt Exp $
Received on Wed 03 Jul 1996 - 19:43:42 CEST