Annotation of www/index.html, Revision 1.60
1.18 fn 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
1.1 deraadt 3: <head>
4: <title>OpenBSD</title>
1.19 fn 5: <base href=http://www.openbsd.org/>
1.18 fn 6: <link rev=made href=mailto:www@openbsd.org>
7: <meta name="resource-type" content="document">
8: <meta name="description" content="the main OpenBSD page">
9: <meta name="keywords" content="openbsd,main">
10: <meta name="distribution" content="global">
11: <meta name="copyright" content="This document copyright 1996 by OpenBSD, Inc.">
1.1 deraadt 12: </head>
1.18 fn 13:
14: <body>
15:
1.31 deraadt 16: <h1>OpenBSD</h1>
17: <br>
1.37 deraadt 18: <img src="head.gif">
1.30 deraadt 19: <br>
20: <small>The picture is Copyright (C) 1996 Shawn Mueller</small>
21: <br>
22: <h1>OpenBSD</h1>
1.1 deraadt 23:
1.18 fn 24: <p>
1.1 deraadt 25: The OpenBSD project involves continuing development of a multiplatform
26: 4.4BSD-based Unix-like operating system.
1.18 fn 27: </p>
1.1 deraadt 28:
29: <p>
1.22 deraadt 30: <ul>
31: <li><a href=#additions>Changes Relative to other *BSD's</a>
32: <li><a href=#curplat>Supported platforms</a>
33: <li><a href=#futplat>New platforms under development</a>
1.50 deraadt 34: <li><a href=#devel>How we help developers and users</a>
1.55 deraadt 35: <li><a href=#snapshots>Binary snapshots</a>
1.48 deraadt 36: <li><a href=#ftp>FTP mirrors</a>
1.50 deraadt 37: <li><a href=#maillist>Mailing Lists</a>
38: <li><a href=#gnats>Bug tracking</a>
39: <li><a href=#sup>Sup</a>
40: <li><a href=#anoncvs>AnonCVS</a>
1.22 deraadt 41: <li><a href=goals.html>OpenBSD project goals</a>
42: </ul>
43: </p>
44:
45: <h3><hr><a name=additions>Changes Relative to other *BSD's.</a></h3>
46:
47: <p>
1.1 deraadt 48: OpenBSD looks a lot like NetBSD (which it is derived from, following
49: the 4.4BSD roots), but is now being developed seperately. Good changes
50: from other free operating systems will be merged in (of course, depending
1.24 deraadt 51: on various factors like developer time for example.) OpenBSD tracks
52: NetBSD changes very closely; say anywhere between 2 days to 10 days
53: behind the state of NetBSD-current all the time. Hence you can truly
54: say that OpenBSD is NetBSD <b>PLUS MORE STUFF</b>.
1.18 fn 55: </p>
1.1 deraadt 56:
57: <p>
1.22 deraadt 58: Various additions have been made. This is only a small partial list of
1.25 deraadt 59: the major machine independent changes (ie. it is the most interesting
60: changes or what people ask about most often). Check the specific port
61: you are interested in for further details of that port -- many of them
62: have been extended too.
1.1 deraadt 63: <ul>
1.35 deraadt 64: <li>Many many NetBSD PR's fixed (which NetBSD has not yet fixed)
1.22 deraadt 65: <li>New curses library, including libform, libpanel and libmenu.
1.25 deraadt 66: <li>a termlib library which understands termcap.db, needed for new curses.
67: <li>The FreeBSD ports subsystem was integrated and is usable by you!
1.22 deraadt 68: <li>ipfilter for filtering dangerous packets
69: <li>better ELF support
1.25 deraadt 70: <li>nlist() that understands ELF, ECOFF, and a.out, allowing non-a.out ports
71: to use kvm utilies
1.22 deraadt 72: <li>Verbatim integration of the GNU tools (using a wrapper Makefile)
73: <li>All the pieces needed for cross compilation are in the source tree.
74: <li>Some LKM support in the tree.
75: <li>ATAPI support (should work on all ISA busses)
1.25 deraadt 76: <li>new scsi, md5, pkg_* commands
1.22 deraadt 77: <li>Numerous security related fixes
1.25 deraadt 78: <li>Kerberos and other crypto in the source tree that is exportable
79: <li>Solid YP master, server, and client capabilities.
1.22 deraadt 80: <li>/dev/rnd -- source of random data
1.23 deraadt 81: <li>In-kernel update(8) with an adaptive algorithm
1.25 deraadt 82: <li>Some ddb improvements and extensions
83: <li>Numerous scsi fixes
1.28 deraadt 84: <li>new system calls: rfork(), minherit(), poll().
85: <li>select() that can handle any amount of file descriptors.
1.29 deraadt 86: <li>kernfs extensions
87: <li>ATM support (support for one company's sparc & i386 cards available)
1.33 deraadt 88: <li>Boot kernels with "-c" to edit/enable/disable device configuration tables
1.38 deraadt 89: <li>pax as tar, gnutar is toast
1.42 deraadt 90: <li>using AT&T awk, gawk is toast
1.38 deraadt 91: <li>Even more security fixes.
1.47 deraadt 92: <li>Accepts FreeBSD MD5 passwords in password maps, soon will be able to
93: generate them too
1.40 deraadt 94: <li>Linux ext2fs and BSD4.4 LFS support being worked on.
1.47 deraadt 95: <li>Working ATAPI audio support.
1.51 deraadt 96: <li>terminfo database support.
1.53 deraadt 97: <li>Fortran in the tree.
98: <li>The most secure rdist support anywhere.
99: <li>randomized port allocation from bind() and bindresvport() -- security
100: via unpredictability.
101: <li>Protection from the udp spamming and ftp bounce attacks.
102: <li>Significantly improved ftp daemon.
103: <li>Numerous more security policy and implimentation improvements (OpenBSD
104: defaults to installing in a very secure mode)
105: <li>zlib (non-GPL'd gzip-compatible library)
106: <li>Newest version of ppp, vi,
1.54 deraadt 107: <li>_POSIX_SAVED_IDS behaviour with permitted BSD extensions.
1.60 ! deraadt 108: <li>Fixed long-standing vm swap-leak.
! 109: <li>FreeBSD malloc() that uses mmap() and is able to free unused memory.
! 110: <li>Numerous FreeBSD userland fixes and improvements incorporated.
1.1 deraadt 111: </ul>
1.18 fn 112: </p>
1.1 deraadt 113:
1.18 fn 114: <h3><hr><a name=curplat>Platforms currently supported.</a></h3>
1.1 deraadt 115:
1.18 fn 116: <p>
1.1 deraadt 117: Note: for some of these platforms, the platform-independent code may
118: be identical to that found in NetBSD because there isn't a specific
119: OpenBSD developer. For other ports the differences are significant.
120: If you find an empty page that means nothing of consequence that is
121: directly port-specific has changed from NetBSD. (Of course there are
122: differences, but they just aren't in the /sys/arch/XXXX directory).
1.18 fn 123: </p>
1.1 deraadt 124:
1.18 fn 125: <p>
1.1 deraadt 126: <dl>
1.41 deraadt 127: <dt><a href=alpha.html>Alpha</a> <dd> DEC Alpha-based machines.
128: <dt><a href=amiga.html>Amiga</a> <dd> Commodore Amiga.
129: <dt><a href=arc.html>ARC</a> <dd> ARC R4000/R4400 machines (including PICA)
130: <dt><a href=arm32.html>Arm32</a> <dd> Acorn ARM6+ computers.
131: <dt><a href=atari.html>Atari</a> <dd> Atari TT and Falcon models.
132: <dt><a href=hp300.html>HP300</a> <dd> Hewlett-Packard HP300/HP400 machines.
1.1 deraadt 133: <dt><a href=i386.html>i386</a> <dd> Your standard run-of-the-mill PC.
134: <dt><a href=mac68k.html>mac68k</a> <dd> Most MC680x0-based Apple Macintosh models.
1.41 deraadt 135: <dt><a href=mvme68k.html>MVME68K</a> <dd> Motorola MVME147/16x/17x 68K VME cards.
136: <dt><a href=pc532.html>PC532</a> <dd> A rare NS32532-based computer.
137: <dt><a href=pmax.html>Pmax</a> <dd> DEC MIPS-based machines.
138: <dt><a href=sparc.html>Sparc</a> <dd> Sun's Sun4 and sun4c models (sun4m soon!).
139: <dt><a href=sun3.html>Sun3</a> <dd> Sun's sun3 models.
140: <dt><a href=vax.html>Vax</a> <dd> DEC's VAX computers.
1.1 deraadt 141: </dl>
1.18 fn 142: </p>
143:
144: <h3><hr><a name=futplat>New platforms under development.</a></h3>
1.1 deraadt 145:
1.18 fn 146: <p>
1.1 deraadt 147: <dl>
1.10 deraadt 148: <dt><a href=mvme88k.html>mvme88k</a> <dd> Motorola MVME18x/19x 88K VME cards
1.25 deraadt 149: <dt><a href=ppc.html>ppc</a> <dd> IBM/Apple/Motorola PowerPC-based machines.
1.1 deraadt 150: </dl>
1.18 fn 151: </p>
1.1 deraadt 152:
153: <p>
154: <h3>Platforms not being developed, but which should be</h3>
1.36 deraadt 155: There is enough free code available to make porting to these
156: machines relatively easy.
1.18 fn 157: </p>
158:
159: <p>
1.1 deraadt 160: <dl>
161: <dt><a href=hppa.html>hppa</a> <dd> Hewlett-Packard PA-RISC HP700/HP800 models.
162: <dt><a href=iris.html>iris</a> <dd> SGI Iris machines.
163: </dl>
1.18 fn 164: </p>
1.1 deraadt 165:
1.26 deraadt 166:
1.49 deraadt 167: <hr><hr>
168: <h3><a name=devel>How we help developers and users.</a></h3>
169:
1.50 deraadt 170: <dl>
1.55 deraadt 171: <dt><h4><a name=snapshots>BINARY SNAPSHOTS:</a></h4>
172:
173: <p>
1.59 deraadt 174: <dd>Snapshots will be made available from time to time on the ftp mirrors.
175: The snapshots are available on each of the FTP servers listed below,
1.55 deraadt 176: typically in the directory <strong>OpenBSD/snapshots</strong>.
177: You should also read the <a href=snapshots.html>general description
178: about OpenBSD snapshots</a>.
179: </p>
180:
1.59 deraadt 181: <p>
182: NOTE: please do not fetch binaries directly from <string>cvs.openbsd.org
183: </string> but instead use one of the mirror sites.
184:
1.56 deraadt 185: </dl>
1.55 deraadt 186: <dl>
1.56 deraadt 187: <dt><h4><a name=ftp>FTP:</a></h4>
1.48 deraadt 188: <dd>This is a list of currently known ftp servers:<p>
189: <ul>
1.18 fn 190:
1.48 deraadt 191: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD>
192: ftp://ftp.openbsd.org/pub/OpenBSD</a><br>
193: located at Rutgers University, eastern USA.
194: <!-- deraadt@openbsd.org -->
1.18 fn 195:
1.48 deraadt 196: <li><a href=ftp://ftp.ibp.fr/pub/OpenBSD>
197: ftp://ftp.ibp.fr/pub/OpenBSD</a><br>
1.1 deraadt 198: located in France.
199: <!-- ftpmaint@ftp.ibp.fr -->
1.48 deraadt 200:
201: <li><a href=ftp://ftp.univ-evry.fr/pub/system/OpenBSD>
202: ftp://ftp.univ-evry.fr/pub/system/OpenBSD</a><br>
203: located in France.
204: <!-- mirror@ftp.univ-evry.fr -->
205:
1.52 deraadt 206: <li><a href=ftp://hal.heuris.com/pub/OpenBSD>
207: ftp://hal.heuris.com/pub/OpenBSD</a><br>
1.1 deraadt 208: located in University of Missouri-Rolla, mid-western USA.
209: <!-- johns@cs.umr.edu -->
1.48 deraadt 210:
211: <li><a href=ftp://ftp.tut.ac.jp/OpenBSD>
212: ftp://ftp.tut.ac.jp/OpenBSD</a><br>
213: located at Toyohashi University of Technology, Aichi, JAPAN
214: <!-- Keijiro Umehara ume@ftp.tut.ac.jp -->
215:
1.1 deraadt 216: </ul>
1.48 deraadt 217:
218: <p>
219: The file structure of each FTP server is as follows:
1.18 fn 220: </p>
221:
222: <p>
1.48 deraadt 223: <strong>
224: <dl>
225: <dt>OpenBSD/snapshots/
226: <dt>OpenBSD/X11/
227: <dt>OpenBSD/src/
228: </dl>
229: </strong>
1.18 fn 230: </p>
1.1 deraadt 231:
232: <p>
1.48 deraadt 233: If you add a new FTP mirror site, please contact
234: <a href=mailto:deraadt@theos.com> the FTP maintainer</a>.
235: </p>
1.50 deraadt 236: </dl>
1.48 deraadt 237:
1.50 deraadt 238: </dl>
1.1 deraadt 239: <dl>
1.50 deraadt 240: <dt><h4><a name=maillist>MAILING LISTS:</a></h4>
1.1 deraadt 241: <dd>Some mailing lists are used for the development and use of OpenBSD.
242: In each case, send mail to
243: <a href=mailto:majordomo@OpenBSD.org>majordomo@OpenBSD.org</a>
244: with a message body of "<strong>subscribe mailing-list-name</strong>".
1.18 fn 245:
1.27 deraadt 246: There is a only minimal set of mailing lists intentionally; among
247: other benefits such as more communication it reduces cross-posting.
1.26 deraadt 248: There are no private mailing lists.
249: <p>
1.1 deraadt 250: These are the mailing lists:
251: <dl>
252: <dt><strong>announce</strong>
253: <dd>important announcements. Since this is a low volume list
254: it is excellent for people who just want to follow important events.
255: <dt><strong>tech</strong>
256: <dd>technical discussions
257: <dt><strong>misc</strong>
258: <dd>user questions and answers
259: <dt><strong>source-changes</strong>
260: <dd>automated mailout of CVS source tree changes
1.18 fn 261: </dl>
262:
1.1 deraadt 263: <p>
264: For further assistance, send a message body of "<strong>help</strong>",
265: and you will receive a reply outlining all your options.
1.18 fn 266: </p>
1.1 deraadt 267:
1.26 deraadt 268: </dl>
1.50 deraadt 269: <dl><h4><a name=gnats>BUG TRACKING:</a></h4>
270: <dd>We run GNATS for tracking bugs:
271: <a href=/cgi-bin/wwwgnats.pl>Click here to enter the bug tracking system.</a>
1.26 deraadt 272:
1.39 deraadt 273: </dl>
1.50 deraadt 274: <dl>
275: <dt><h4><a name=sup>SUP:</a></h4>
1.21 deraadt 276: <dd>Sorry, unlike other *BSD projects, the SUP service is not
277: available. We do not believe the SUP service to be a good tool for
278: source code access. But read below for the description of the
279: <a href="#anoncvs"><strong>anoncvs</strong> service!</a>
1.1 deraadt 280:
1.50 deraadt 281: <dt><h4><a name=anoncvs>CVS Access:</a></h4>
1.7 david 282: <dd>CVS is used to manage the OpenBSD source tree. This allows
283: developers to work on a local source tree and commit their changes when
284: ready. Also <strong>anyone</strong> can edit source files on their
285: local machines, and automatically track and merge in any changes made
286: in the OpenBSD CVS repository. Additionally they can easily see the
287: logs of, check out, or "diff" the source files in the OpenBSD source
288: tree.
1.57 deraadt 289: </p>
290:
291: <p>
292: Most importantly, the <strong>anoncvs</strong> service does NOT
293: delete the changes you make in your local copy of the source tree --
294: read on for more details!
295: </p>
1.18 fn 296:
1.1 deraadt 297: <p>
1.17 deraadt 298: The latest version of CVS is available at
299: <a href=ftp://ftp.cyclic.com/pub/cvs/>Cyclic</a>.
300: Versions earlier than 1.6 are not recommended, and may not work.
1.57 deraadt 301: If you already have OpenBSD installed, CVS is included.
1.18 fn 302: </p>
303:
1.17 deraadt 304: <p>
1.18 fn 305: There are two levels of source tree access:
306: </p>
1.1 deraadt 307:
308: <dl>
1.58 deraadt 309: <dt><strong>Read-write access for developers:</strong>
1.1 deraadt 310: <dd>Developers who need to commit changes to the source tree must have
311: an account on the OpenBSD machines. Getting this access will be a
312: natural result of working on the sources with other OpenBSD developers.
1.58 deraadt 313: If someone does some good work and shows they can work with the team,
314: they will get an account.
1.18 fn 315: </dl>
316:
317: <dl>
1.58 deraadt 318: <dt><strong>Read-only access for everyone:</strong>
1.5 deraadt 319: <dd>Anyone can access the read-only CVS repositories. These copies
320: of the read-write CVS repository are mirrored often. To use one,
321: set your <strong>CVSROOT</strong> environment variable to one of
322: the following values:
1.1 deraadt 323: <ul>
1.21 deraadt 324: <p>
1.12 deraadt 325: <li><strong>CVSROOT=anoncvs@anoncvs.usa.openbsd.org:/cvs</strong><br>
326: Host also known as <strong>anoncvs.openbsd.org</strong> and
327: <strong>eap.ccrc.wustl.edu</strong>.<br>
1.4 deraadt 328: located at Washington University, St. Louis, mid-west USA.<br>
1.21 deraadt 329: maintained by <a href=mailto:chuck@maria.wustl.edu>Chuck Cranor</a>.<br>
1.5 deraadt 330: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 331: updated every 4 hours.<br>
332: <p>
1.12 deraadt 333: <li><strong>CVSROOT=anoncvs@anoncvs2.usa.openbsd.org:/cvs</strong><br>
1.52 deraadt 334: Host also known as <strong>hal.heuris.com</strong>.<br>
335: located in MO, mid-west USA.<br>
336: maintained by <a href=mailto:johns@heuris.com>John Stone</a>.<br>
337: protocols: rsh, ssh, ssh port 2022.<br>
1.21 deraadt 338: updated every 12 hours.<br>
339: <p>
340: <li><strong>CVSROOT=anoncvs@anoncvs.uk.openbsd.org:/cvs</strong><br>
341: Host also known as <strong>dumpty.wonderland.org</strong>.<br>
342: located in London, UK.<br>
343: maintained by <a href=mailto:peter@wonderland.org>Peter Galbavy</a>.<br>
344: protocols: rsh, ssh, ssh port 2022.<br>
345: updated every 12 hours.<br>
1.43 deraadt 346: <p>
347: <li><strong>CVSROOT=anoncvs@anoncvs.tw.openbsd.org:/cvs</strong><br>
348: Host also known as <strong>hercules.secc.fju.edu.tw</strong>.<br>
349: located in Taipei, Taiwan.<br>
350: maintained by <a href=mailto:shawn@openbsd.org>Shawn Hsiao</a>.<br>
351: protocols: rsh, ssh, ssh port 2022.<br>
352: updated every 12 hours.<br>
1.1 deraadt 353: </ul>
1.21 deraadt 354: <p>
355: You may want to use `traceroute' to find out which server is nearest you.
1.1 deraadt 356: </dl>
1.18 fn 357: </p>
358:
1.1 deraadt 359: <p>
360: <strong>IMPORTANT NOTE:</strong>
361: There are a few issues relating to cryptographic software that everyone
362: should be aware of:
363: <ul>
1.20 deraadt 364: <li>The OpenBSD sources are from Canada.
365: <a href=http://insight.mcmaster.ca/org/efc/pages/doc/crypto-export.html>It
366: is legal to export crypto software from Canada to the world.</a>
1.21 deraadt 367: <p>
1.1 deraadt 368: <li>However, if you are outside the USA or Canada, you should not
1.5 deraadt 369: fetch the cryptographic sections of the OpenBSD sources from an
370: anoncvs server located in the USA. The files in question are...
1.1 deraadt 371: <ul>
372: <li>src/kerberosIV/*
373: <li>src/lib/libc/crypt/crypt.c
374: <li>src/lib/libc/crypt/morecrypt.c
375: </ul>
376: Because of the USA ITAR munitions list,
377: crypto software may only be exported to Canada from the USA.
1.21 deraadt 378: <p>
1.58 deraadt 379: <li>The OpenBSD project is looking for more anoncvs servers -- read
380: on to find out how you can help.
1.1 deraadt 381: </ul>
1.18 fn 382: </p>
383:
1.1 deraadt 384: <p>
1.5 deraadt 385: A sample use of an anoncvs CVS server would be:
1.1 deraadt 386: <pre>
1.12 deraadt 387: % setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
1.1 deraadt 388: % cd /tmp
1.58 deraadt 389: % cvs get src/sys/arch/sparc
1.1 deraadt 390: [copies the files from the repository to your machine]
1.58 deraadt 391: % cvs log src/sys/arch/sparc/sparc/locore.s
1.1 deraadt 392: [shows the commit log for the chosen file ]
1.58 deraadt 393: % cvs diff -bc -r1.1 -r1.5 src/sys/arch/sparc/sparc/locore.s
1.1 deraadt 394: [shows the changes between revisions 1.1 and rev 1.5]
395: </pre>
1.18 fn 396: </p>
397:
398: <p>
1.44 deraadt 399: Here is how someone using anoncvs regularily would update his
400: source tree:
401: <pre>
402: # setenv CVSROOT anoncvs@anoncvs.usa.openbsd.org:/cvs
403: # cd /usr
404: # cvs -q get -PA src
405: </pre>
406: or similarily later on he might try
407: <pre>
408: # cd /usr/src
409: # cvs -q up -PAd
410: </pre>
1.58 deraadt 411: Everytime you ran this it would syncronize your /usr/src tree. It would
412: not destroy any of your local changes, rather it would attempt to merge
413: changes in. If you use obj directories (not obj symbolic links) you may
414: wish to append "-I obj" to the cvs command line, this will keep cvs from
415: spitting out a warning about all the obj directories it is going to
416: encounter which are not in the repository.
1.44 deraadt 417: </p>
418:
419: <p>
1.1 deraadt 420: The CVS man page (included with the CVS sources) has much more
1.18 fn 421: information about how CVS can be used.
422: </p>
423:
1.1 deraadt 424: <p>
425: The anoncvs service gives fledgling developers a chance to learn CVS
426: operation and get thoroughly involved in the development process
427: before getting "commit" access -- as a result of showing useful
428: skills and high quality results they will naturally later be given
1.18 fn 429: developer access. As well, people providing patches can create
430: their "diff"s relative to the CVS tree, which will ease integration.
431: </p>
432:
433: <p>
434: The CVS client uses rsh to talk to the CVS server. If some local
435: security measure like a firewall (or imperfect protocol emulators
436: like slirp) prevents you from using rsh, you may be able to use
1.58 deraadt 437: <a href=http://www.cs.hut.fi/ssh>ssh</a> instead. In this case,
438: one sets the environment variable <strong>CVS_RSH</strong> to point
439: to ssh (typically <strong>/usr/local/bin/ssh</strong>). To reduce the
440: performance hit the anoncvs server would take it is recommended (and
441: requested) that you disable encryption. If your local site prevents
442: you from connecting out to port 22 (which ssh defaults to using) use
443: port 2022.
1.18 fn 444: </p>
1.5 deraadt 445:
446: <p>
1.1 deraadt 447: Do not be tempted to turn on compression since CVS already compresses.
448: Use something like the following in your <strong>$HOME/.ssh/config</strong>
449: file.
1.18 fn 450: </p>
1.1 deraadt 451: <pre>
1.12 deraadt 452: Host anoncvs.usa.openbsd.org
1.1 deraadt 453: Cipher none
454: Port 2022
455: </pre>
1.18 fn 456:
457: <p>
458: If you wish to be a new anoncvs mirror site, please contact the anoncvs
459: <a href=mailto:deraadt@theos.com>maintainer</a>.
1.16 deraadt 460: Anoncvs mirrors require about 300MB of disk, and use up to 4MB of swap
1.1 deraadt 461: per anoncvs user (assuming the user does a large operation; while smaller
462: operations use fewer resources, anoncvs still makes much more of an
1.18 fn 463: impact than ftp or sup). Such anoncvs machines should have excellent
464: network connectivity for the area they are expected to serve. A
465: <a href=anoncvs.shar>document</a>
466: which describes the setup of anoncvs servers is available.
467: </p>
1.1 deraadt 468:
469: </dl>
470:
471: <hr>
472: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.60 ! deraadt 473: <br><small>$OpenBSD: index.html,v 1.59 1996/08/02 08:11:34 deraadt Exp $</small>
1.18 fn 474:
475: </body>
476: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to index.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www