View | Details | Raw Unified | Return to bug 99326
Collapse All | Expand All

(-)projects.sgml (-111 / +112 lines)
Lines 66-88 Link Here
66
novices.  The aim is to provide a set of step-by-step guides to
66
novices.  The aim is to provide a set of step-by-step guides to
67
installing and configuring various ports.</li>
67
installing and configuring various ports.</li>
68
68
69
<li><A HREF="http://www.vmunix.com/fbsd-book/">A Comprehensive
70
Guide to FreeBSD</A>: An attempt at a more readable,
71
"book-like" tutorial explaining the FreeBSD Operating
72
System. Intended for people new to both FreeBSD and
73
UNIX. Currently a work in progress.</li>
74
75
<li><A HREF="http://flag.blackened.net/freebsd/">FreeBSD
76
How-To's for the Lazy and Hopeless</A>: Another somewhat more
77
light-hearted attempt to provide more readable "how-to" style
78
information on setting up and configuring FreeBSD.</li>
79
80
<li><A HREF="http://home.worldonline.dk/nkbj/Linux+FreeBSD/Linux+FreeBSD.html">The
81
Linux+FreeBSD mini-HOWTO</a>: Describes how to
82
use Linux and FreeBSD on the same system. It introduces FreeBSD
83
and discusses how the two operating systems can cooperate,
84
e.g. by sharing swap space.</li>
85
86
<li><a href="&url.books;/developers-handbook/index.html">
69
<li><a href="&url.books;/developers-handbook/index.html">
87
The FreeBSD Developers' Handbook</a></li>
70
The FreeBSD Developers' Handbook</a></li>
88
71
Lines 99-105 Link Here
99
like the Networker's Guide are obsoleted in a few years by changes in
82
like the Networker's Guide are obsoleted in a few years by changes in
100
the product they are written for.
83
the product they are written for.
101
</li>
84
</li>
85
<li><h3>Unmaintained Pages</h3>
86
<ul>
87
<li><A HREF="http://www.vmunix.com/fbsd-book/">A Comprehensive
88
Guide to FreeBSD</A>: An attempt at a more readable,
89
"book-like" tutorial explaining the FreeBSD Operating
90
System. Intended for people new to both FreeBSD and
91
UNIX. Currently a work in progress.</li>
102
92
93
<li><A HREF="http://flag.blackened.net/freebsd/">FreeBSD
94
How-To's for the Lazy and Hopeless</A>: Another somewhat more
95
light-hearted attempt to provide more readable "how-to" style
96
information on setting up and configuring FreeBSD.</li>
97
</ul>
98
</li>
103
</ul>
99
</ul>
104
100
105
<a name="applications"></a>
101
<a name="applications"></a>
Lines 157-172 Link Here
157
to the SMPng network stack locking work for FreeBSD 5.3.  This project is
153
to the SMPng network stack locking work for FreeBSD 5.3.  This project is
158
exploring and implementing optimizations strategies for a multi-threaded
154
exploring and implementing optimizations strategies for a multi-threaded
159
network stack.<li>
155
network stack.<li>
160
<li><a name="dingo" href="&base;/projects/dingo/index.html">Dingo</a>:
161
<em>FreeBSD Network Cleanup and Consolidation Project</em>, is a
162
collection of work that needs to be done to clean up and advance the
163
FreeBSD network stack.  The goal is to remove duplicated functionality
164
while also adding new features that will make FreeBSD simple to use,
165
both for the network engineer, experimenter and the first time user.</li>
166
<li><a name="altq"  href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html">ALTQ</a>: bandwidth management for applications.</li>
167
<li><a name="kame" href="http://www.kame.net/">KAME Project</a>: A free IPv6/IPsec stack for BSD.</li>
156
<li><a name="kame" href="http://www.kame.net/">KAME Project</a>: A free IPv6/IPsec stack for BSD.</li>
168
<li><a name="ppp" href="http://www.awfulhak.org/ppp.html">Point to Point Protocol (PPP)</a></li>
169
<li><a name="smn" href="http://www.cs.pdx.edu/research/SMN/">Secure MobileIP via IP</a></li>
170
<li><a name="SYSLOG-SECURE">SYSLOG-SECURE</a>:
157
<li><a name="SYSLOG-SECURE">SYSLOG-SECURE</a>:
171
In August 2001 a standard of syslog was made: RFC3164. This RFC
158
In August 2001 a standard of syslog was made: RFC3164. This RFC
172
describes some extensions to add security to syslog. The project
159
describes some extensions to add security to syslog. The project
Lines 175-188 Link Here
175
be modified. And optional some tools to verify/manage the security will
162
be modified. And optional some tools to verify/manage the security will
176
made.
163
made.
177
All help is welcome. Send an email to albert@ons-huis.net for info.</li>
164
All help is welcome. Send an email to albert@ons-huis.net for info.</li>
165
<li><h3>Unmaintained Pages</h3>
166
<ul>
167
<li><a name="dingo" href="&base;/projects/dingo/index.html">Dingo</a>:
168
<em>FreeBSD Network Cleanup and Consolidation Project</em>, is a
169
collection of work that needs to be done to clean up and advance the
170
FreeBSD network stack.  The goal is to remove duplicated functionality
171
while also adding new features that will make FreeBSD simple to use,
172
both for the network engineer, experimenter and the first time user.</li>
173
<li><a name="altq"  href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html">ALTQ</a>: bandwidth management for applications.</li>
174
<li><a name="ppp" href="http://www.awfulhak.org/ppp.html">Point to Point Protocol (PPP)</a></li>
175
<li><a name="smn" href="http://www.cs.pdx.edu/research/SMN/">Secure MobileIP via IP</a></li>
176
</ul>
177
</li>
178
</ul>
178
</ul>
179
179
180
<a name="storage"></a>
180
<a name="storage"></a>
181
<h3>Storage</h3>
181
<h3>Storage</h3>
182
<ul>
182
<ul>
183
<li><a href="http://people.FreeBSD.org/~yar/hfs/">HFS and HFS
184
Plus in FreeBSD</a>: This project is aimed at integrating
185
HFS support from Darwin into FreeBSD.</li>
186
183
187
<li><a name="afs" href="http://www.stacken.kth.se/projekt/arla/">Arla</a>:
184
<li><a name="afs" href="http://www.stacken.kth.se/projekt/arla/">Arla</a>:
188
A free AFS client implementation.  The main goal is to
185
A free AFS client implementation.  The main goal is to
Lines 199-226 Link Here
199
operation, good security model, server replication and persistent
196
operation, good security model, server replication and persistent
200
client side caching.</li>
197
client side caching.</li>
201
198
202
<li><a name="cryptfs" href="http://www.fsl.cs.sunysb.edu/docs/cryptfs/">Cryptfs</a>: Encrypts file names and data pages using Blowfish.</li>
203
204
<li><a name="journaling" href="http://www.ece.cmu.edu/~ganger/papers/">
199
<li><a name="journaling" href="http://www.ece.cmu.edu/~ganger/papers/">
205
Journaling versus Soft Updates</a>: Asynchronous Meta-data Protection in File Systems.</li>
200
Journaling versus Soft Updates</a>: Asynchronous Meta-data Protection in File Systems.</li>
206
201
207
<li><a href="http://people.FreeBSD.org/~terry/">Mode locking</a></li>
202
<li><a name="softupdate" href="http://www.mckusick.com/softdep/index.html"> Soft Updates:</a>
208
<li><a href="http://people.FreeBSD.org/~terry/">Make the namei interface reflexive</a></li>
209
<li><a href="http://people.FreeBSD.org/~terry/">NFS client and server locking</a></li>
210
211
<li><a name="dcd" href="http://www.usenix.org/events/usenix99/full_papers/nightingale/nightingale_html/">The Design and Implementation of a DCD Device Driver for Unix</a></li>
212
213
<li><a href="http://iclub.nsu.ru/~semen/ntfs/">NTFS Driver for FreeBSD</a>:
214
This driver allows Windows&reg; NTFS partitions to be mounted by FreeBSD.
215
Currently NTFS partitions can only be accessed in read-only mode, but
216
plans are in the works for read/write access.</li>
217
218
<li><a name="rio" href="http://www.eecs.umich.edu/Rio/">Rio (RAM
219
I/O)</a>: The Rio project is investigating how to implement and
220
use reliable memory.  Reliable memory enables dramatic
221
improvements in reliability and performance.</li>
222
223
<li><a name="softupdate" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/sys/ufs/ffs/README.softupdates"> Soft Updates:</a>
224
A Solution to the Metadata Update Problem in File Systems</li>
203
A Solution to the Metadata Update Problem in File Systems</li>
225
204
226
<li><a name="tcfs" href="http://www.tcfs.it/">TCFS</a>:
205
<li><a name="tcfs" href="http://www.tcfs.it/">TCFS</a>:
Lines 233-238 Link Here
233
the client machine and thus the encryption/decryption key never
212
the client machine and thus the encryption/decryption key never
234
travels on the network.</li>
213
travels on the network.</li>
235
214
215
<li><a name="PathConvert" href="http://www.tamacom.com/pathconvert/">
216
The PathConvert project</a>: A project to develop utilities which make
217
conversion between absolute path name and relative path name. It
218
brings benefits mainly to the users of NFS and WWW.</li>
219
<!--
220
<li><a name="WAFS" href="http://www.eecs.harvard.edu/~stein/wafs/">
221
WAFS</a> is a simple filesystem designed to act as a logging
222
service for kernel subsystems. Reads and writes are keyed
223
by log-sequence number (LSN). All writes to WAFS are
224
sequential. Kernel subsystems can use this LSN service to
225
enforce write-ahead logging and guarantee consistency.
226
</li>
227
-->
228
<li><h3>Unmaintained Pages</h3>
229
<ul>
230
<li><a href="http://people.FreeBSD.org/~yar/hfs/">HFS and HFS
231
Plus in FreeBSD</a>: This project is aimed at integrating
232
HFS support from Darwin into FreeBSD.</li>
233
<li><a name="cryptfs" href="http://www.fsl.cs.sunysb.edu/docs/cryptfs/">Cryptfs</a>: Encrypts file names and data pages using Blowfish.</li>
234
<li><a href="http://people.FreeBSD.org/~terry/">Mode locking</a></li>
235
<li><a href="http://people.FreeBSD.org/~terry/">Make the namei interface reflexive</a></li>
236
<li><a href="http://people.FreeBSD.org/~terry/">NFS client and server locking</a></li>
237
<li><a name="dcd" href="http://www.usenix.org/events/usenix99/full_papers/nightingale/nightingale_html/">The Design and Implementation of a DCD Device Driver for Unix</a></li>
238
<li><a href="http://iclub.nsu.ru/~semen/ntfs/">NTFS Driver for FreeBSD</a>:
239
This driver allows Windows&reg; NTFS partitions to be mounted by FreeBSD.
240
Currently NTFS partitions can only be accessed in read-only mode, but
241
plans are in the works for read/write access.</li>
242
<li><a name="rio" href="http://www.eecs.umich.edu/Rio/">Rio (RAM
243
I/O)</a>: The Rio project is investigating how to implement and
244
use reliable memory.  Reliable memory enables dramatic
245
improvements in reliability and performance.</li>
236
<li><a name="Tertiary" href="http://now.cs.berkeley.edu/Td/">Tertiary Disk</a>:
246
<li><a name="Tertiary" href="http://now.cs.berkeley.edu/Td/">Tertiary Disk</a>:
237
A storage system architecture to create large disk storage systems
247
A storage system architecture to create large disk storage systems
238
that avoid the disadvantages of custom built disk arrays. The
248
that avoid the disadvantages of custom built disk arrays. The
Lines 245-285 Link Here
245
switched network to host a large number of disks. Our prototype
255
switched network to host a large number of disks. Our prototype
246
consists of 20 200MHz PC PCs, which host 370 8GB disks. The PCs
256
consists of 20 200MHz PC PCs, which host 370 8GB disks. The PCs
247
are connected through a 100Mbps Ethernet switch.</li>
257
are connected through a 100Mbps Ethernet switch.</li>
248
249
<li><a name="vinum" href="http://www.vinumvm.org/">Vinum</a>:
258
<li><a name="vinum" href="http://www.vinumvm.org/">Vinum</a>:
250
A logical volume manager modeled after the VERITAS volume manager&trade;.
259
A logical volume manager modeled after the VERITAS volume manager&trade;.
251
However, it is not a clone of Veritas, and attempts to solve a
260
However, it is not a clone of Veritas, and attempts to solve a
252
number of problems more elegantly than Veritas.  It also offers
261
number of problems more elegantly than Veritas.  It also offers
253
features that Veritas does not have.</li>
262
features that Veritas does not have.</li>
254
263
</ul>
255
<li><a name="PathConvert" href="http://www.tamacom.com/pathconvert/">
256
The PathConvert project</a>: A project to develop utilities which make
257
conversion between absolute path name and relative path name. It
258
brings benefits mainly to the users of NFS and WWW.</li>
259
<!--
260
<li><a name="WAFS" href="http://www.eecs.harvard.edu/~stein/wafs/">
261
WAFS</a> is a simple filesystem designed to act as a logging
262
service for kernel subsystems. Reads and writes are keyed
263
by log-sequence number (LSN). All writes to WAFS are
264
sequential. Kernel subsystems can use this LSN service to
265
enforce write-ahead logging and guarantee consistency.
266
</li>
264
</li>
267
-->
268
</ul>
265
</ul>
269
266
270
<a name="kernelandsecurity"></a>
267
<a name="kernelandsecurity"></a>
271
<h3>Kernel, security</h3>
268
<h3>Kernel, security</h3>
272
<ul>
269
<ul>
273
<li><a name="drawbridge" href="http://drawbridge.tamu.edu/">Drawbridge</a>:
274
A firewall package that was developed at Texas A&amp;M University and
275
was designed with a large academic environment in mind.  It's greatest
276
strength is the ability to perform high speed packet filtering for
277
a larger number of individual hosts within an intranetwork.</li>
278
279
<li><a name="kse" href="../kse/index.html">Kernel Scheduler Entities</a>:
280
A project to enhance the threading support on FreeBSD, using a threading
281
system similar in design to Scheduler Activations.</li>
282
283
<li><a name="lotteryscheduling"
270
<li><a name="lotteryscheduling"
284
href="http://www.cs.cmu.edu/~dpetrou/research.html">
271
href="http://www.cs.cmu.edu/~dpetrou/research.html">
285
Lottery Scheduling Kernel</a>: This work is based on
272
Lottery Scheduling Kernel</a>: This work is based on
Lines 298-309 Link Here
298
<li><a name="SMP" href="&base;/smp/index.html">Symmetric MultiProcessor Support</a>:
285
<li><a name="SMP" href="&base;/smp/index.html">Symmetric MultiProcessor Support</a>:
299
Documentation and other information about taking advantage of multiple
286
Documentation and other information about taking advantage of multiple
300
processors under FreeBSD.</li>
287
processors under FreeBSD.</li>
301
<li><a href="http://people.FreeBSD.org/~terry/">A validation suite for testing for kernel memory leaks</a></li>
302
<li><a name="spy" href="http://people.FreeBSD.org/~abial/spy/">SPY</a>:
303
Allows you to monitor and/or selectively block syscalls on your
304
system. It could be used either as a safety monitoring device, policy
305
enforcement, or debugging tool.</li>
306
307
<li><a name="trustedbsd" href="http://www.TrustedBSD.org/">TrustedBSD</a>:
288
<li><a name="trustedbsd" href="http://www.TrustedBSD.org/">TrustedBSD</a>:
308
Provides a set of trusted operating system extensions to the FreeBSD operating
289
Provides a set of trusted operating system extensions to the FreeBSD operating
309
system.  This includes features such as fine-grained privileges (capabilities),
290
system.  This includes features such as fine-grained privileges (capabilities),
Lines 318-325 Link Here
318
  specific area of the kernel.  The key concept of this test suite is
299
  specific area of the kernel.  The key concept of this test suite is
319
  chaos. Each test sleeps for a random number of seconds before it
300
  chaos. Each test sleeps for a random number of seconds before it
320
  starts up in a random number of invocations.</li>
301
  starts up in a random number of invocations.</li>
302
<li><h3>Unmaintained Pages</h3>
303
<ul>
304
<li><a name="drawbridge" href="http://drawbridge.tamu.edu/">Drawbridge</a>:
305
A firewall package that was developed at Texas A&amp;M University and
306
was designed with a large academic environment in mind.  It's greatest
307
strength is the ability to perform high speed packet filtering for
308
a larger number of individual hosts within an intranetwork.</li>
309
<li><a name="kse" href="../kse/index.html">Kernel Scheduler Entities</a>:
310
A project to enhance the threading support on FreeBSD, using a threading
311
system similar in design to Scheduler Activations.</li>
312
<li><a href="http://people.FreeBSD.org/~terry/">A validation suite for testing for kernel memory leaks</a></li>
313
<li><a name="spy" href="http://people.FreeBSD.org/~abial/spy/">SPY</a>:
314
Allows you to monitor and/or selectively block syscalls on your
315
system. It could be used either as a safety monitoring device, policy
316
enforcement, or debugging tool.</li>
321
317
322
</ul>
318
</ul>
319
</li>
320
</ul>
323
321
324
<a name="devicedrivers"></a>
322
<a name="devicedrivers"></a>
325
<h3>Device drivers</h3>
323
<h3>Device drivers</h3>
Lines 333-341 Link Here
333
the portability of drivers between hardware architectures.  This page
331
the portability of drivers between hardware architectures.  This page
334
also tracks the progress of drivers towards being SMPng-safe.</li>
332
also tracks the progress of drivers towards being SMPng-safe.</li>
335
333
334
335
<li><a name="cam" href="http://people.FreeBSD.org/~gibbs/ARTICLE-0001.html">CAM: New SCSI layer for FreeBSD</a>:
336
Details about what the new CAM SCSI layer is, and how it works.</li>
337
338
<li><a name="raid">List of supported RAID Cards</a>: Mike Smith's <a
339
href="http://people.FreeBSD.org/~msmith/RAID/">list</a> of supported RAID
340
cards and their respective information.</li>
341
<li><h3>Unmaintained Pages</h3>
342
<ul>
336
<li><a name="deviceframework" href="http://people.FreeBSD.org/~dfr/devices.html">
343
<li><a name="deviceframework" href="http://people.FreeBSD.org/~dfr/devices.html">
337
A New Device Framework for FreeBSD</a></li>
344
A New Device Framework for FreeBSD</a></li>
338
339
<li><a name="atm" href="http://www.ccrc.wustl.edu/pub/chuck/tech/bsdatm/bsdatm.html"> BSD ATM: implementation of ATM internetworking under 4.4BSD</a>:
345
<li><a name="atm" href="http://www.ccrc.wustl.edu/pub/chuck/tech/bsdatm/bsdatm.html"> BSD ATM: implementation of ATM internetworking under 4.4BSD</a>:
340
New computer applications in areas such as multimedia, imaging,
346
New computer applications in areas such as multimedia, imaging,
341
and distributed computing demand high levels of performance from
347
and distributed computing demand high levels of performance from
Lines 352-384 Link Here
352
<li><a name="homeauto" href="http://people.FreeBSD.org/~fsmp/HomeAuto/HomeAuto.html">Home Automation</a>:
358
<li><a name="homeauto" href="http://people.FreeBSD.org/~fsmp/HomeAuto/HomeAuto.html">Home Automation</a>:
353
Using FreeBSD to run appliance controllers, infra-red controllers,
359
Using FreeBSD to run appliance controllers, infra-red controllers,
354
automated telephone systems, and more.</li>
360
automated telephone systems, and more.</li>
355
356
<li><a name="cam" href="http://people.FreeBSD.org/~gibbs/ARTICLE-0001.html">CAM: New SCSI layer for FreeBSD</a>:
357
Details about what the new CAM SCSI layer is, and how it works.</li>
358
359
<li><a name="tokenring" href="http://www.jurai.net/~winter/tr/">The FreeBSD Token-Ring Project</a>:
361
<li><a name="tokenring" href="http://www.jurai.net/~winter/tr/">The FreeBSD Token-Ring Project</a>:
360
Information, files, patches, and documentation about adding Token Ring
362
Information, files, patches, and documentation about adding Token Ring
361
support to FreeBSD.</li>
363
support to FreeBSD.</li>
362
363
<li><a name="xircomcem">Xircom CEM Ethernet Driver</a>: A mailing list exists for further
364
<li><a name="xircomcem">Xircom CEM Ethernet Driver</a>: A mailing list exists for further
364
development of Scott Mitchell's Xircom CEM ethernet driver.  Send
365
development of Scott Mitchell's Xircom CEM ethernet driver.  Send
365
<tt>subscribe freebsd-xircom</tt> to <a
366
<tt>subscribe freebsd-xircom</tt> to <a
366
  href="mailto:majordomo@lovett.com">majordomo@lovett.com</a> to
367
  href="mailto:majordomo@lovett.com">majordomo@lovett.com</a> to
367
join.</li>
368
join.</li>
368
369
369
<li><a name="raid">List of supported RAID Cards</a>: Mike Smith's <a
370
370
href="http://people.FreeBSD.org/~msmith/RAID/">list</a> of supported RAID
371
</ul>
371
cards and their respective information.</li>
372
</li>
372
</ul>
373
</ul>
373
374
374
<a name="architecture"></a>
375
<a name="architecture"></a>
375
<h3>Architecture</h3>
376
<h3>Architecture</h3>
376
<ul>
377
<ul>
377
<li><a name="alpha" href="../platforms/alpha.html">Porting FreeBSD to Alpha systems</a>:
378
Contains information on the FreeBSD Alpha port such as the status,
379
mailing list information, the hardware used, and other Alpha
380
projects.</li>
381
382
<li><a name="ia64" href="../platforms/ia64/index.html">
378
<li><a name="ia64" href="../platforms/ia64/index.html">
383
Porting FreeBSD to IA-64 systems</a>:
379
Porting FreeBSD to IA-64 systems</a>:
384
This project is responsible for porting FreeBSD to the IA-64
380
This project is responsible for porting FreeBSD to the IA-64
Lines 393-406 Link Here
393
Contains information on the FreeBSD SPARC port including a FAQ,
389
Contains information on the FreeBSD SPARC port including a FAQ,
394
some early boot code, information on SPARC processors and motherboards,
390
some early boot code, information on SPARC processors and motherboards,
395
and other SPARC projects.</li>
391
and other SPARC projects.</li>
396
392
<li><h3>Unmaintained Pages</h3>
393
<ul>
394
<li><a name="alpha" href="../platforms/alpha.html">Porting FreeBSD to Alpha systems</a>:
395
Contains information on the FreeBSD Alpha port such as the status,
396
mailing list information, the hardware used, and other Alpha
397
projects.</li>
397
<li><a name="sysvr4" href="http://slash.dotat.org/~newton/freebsd-svr4/">
398
<li><a name="sysvr4" href="http://slash.dotat.org/~newton/freebsd-svr4/">
398
SysVR4 Emulation</a>: This page describes an SysVR4 emulator for
399
SysVR4 Emulation</a>: This page describes an SysVR4 emulator for
399
FreeBSD. It is currently capable of running (or walking, in some
400
FreeBSD. It is currently capable of running (or walking, in some
400
cases) a wide-ish variety of SysV executables taken from Solaris&trade;/x86
401
cases) a wide-ish variety of SysV executables taken from Solaris&trade;/x86
401
2.5.1 and 2.6 systems. I have reason to believe that it will also run
402
2.5.1 and 2.6 systems. I have reason to believe that it will also run
402
SCO UnixWare and SCO OpenServer binaries.</li>
403
SCO UnixWare and SCO OpenServer binaries.</li>
403
404
<li><a name="oskit" href="http://www.cs.utah.edu/flux/oskit/">The OSKit</a>:
404
<li><a name="oskit" href="http://www.cs.utah.edu/flux/oskit/">The OSKit</a>:
405
The OSKit is a framework and a set of 31 component libraries oriented
405
The OSKit is a framework and a set of 31 component libraries oriented
406
to operating systems, together with extensive documentation. By
406
to operating systems, together with extensive documentation. By
Lines 414-427 Link Here
414
network services. The OSKit also works well for constructing OS-related
414
network services. The OSKit also works well for constructing OS-related
415
programs, such as boot loaders or OS-level servers atop a
415
programs, such as boot loaders or OS-level servers atop a
416
microkernel.</li>
416
microkernel.</li>
417
418
<li><a name="picobsd" href="http://people.FreeBSD.org/~picobsd/">Small and embedded FreeBSD (PicoBSD)</a>:
417
<li><a name="picobsd" href="http://people.FreeBSD.org/~picobsd/">Small and embedded FreeBSD (PicoBSD)</a>:
419
PicoBSD is a one floppy version of FreeBSD which in its different
418
PicoBSD is a one floppy version of FreeBSD which in its different
420
variations allows you to have secure dial-up access, small diskless
419
variations allows you to have secure dial-up access, small diskless
421
router, or even a dial-in server.  All of this on only one standard
420
router, or even a dial-in server.  All of this on only one standard
422
1.44MB floppy disk.  It runs on a minimum 386SX CPU with 8MB of RAM,
421
1.44MB floppy disk.  It runs on a minimum 386SX CPU with 8MB of RAM,
423
and no hard drive is required!</li>
422
and no hard drive is required!</li>
424
423
</ul>
424
</li>
425
</ul>
425
</ul>
426
426
427
<a name="misc"></a>
427
<a name="misc"></a>
Lines 449-459 Link Here
449
	the nvi editor, web browser, the emacs editor, and the elvis editor,
449
	the nvi editor, web browser, the emacs editor, and the elvis editor,
450
	and the supported languages are C, Yacc, and Java.</li>
450
	and the supported languages are C, Yacc, and Java.</li>
451
451
452
      <li><A name="freebsdtour" href="http://snapshots.jp.FreeBSD.org/tour/">FreeBSD source code tour</A>:
453
	A hypertext cross referenced presentation of the FreeBSD kernel
454
	source code. The versions indexed are -CURRENT and RELENG_4.</li>
455
456
      <li><A name="enterman" href="http://www.de.daemonnews.org/199908/enteruser.html">Enteruser</a>: A Replacement for adduser.</li>
457
452
458
      <li><A name="acpi"
453
      <li><A name="acpi"
459
	href="&base;/projects/acpi/">ACPI on FreeBSD</A>:
454
	href="&base;/projects/acpi/">ACPI on FreeBSD</A>:
Lines 471-481 Link Here
471
        diffs using a binary diff tool, which dramatically reduces
466
        diffs using a binary diff tool, which dramatically reduces
472
        the bandwidth used.</li>
467
        the bandwidth used.</li>
473
468
474
      <li><a name="c99" href="&base;/projects/c99/index.html">The
475
	FreeBSD C99 &amp; &posix; Conformance Project</a>: This project aims to
476
	implement all requirements of the ISO 9899:1999 (C99) and
477
	IEEE 1003.1-2001 (POSIX) standards.</li>
478
479
      <li><a name="cvsweb" href="cvsweb.html">CVSweb</a>: A WWW
469
      <li><a name="cvsweb" href="cvsweb.html">CVSweb</a>: A WWW
480
	interface for CVS repositories with which you can browse a file
470
	interface for CVS repositories with which you can browse a file
481
	hierarchy on your browser to view each file's revision history
471
	hierarchy on your browser to view each file's revision history
Lines 497-507 Link Here
497
	possible.  The Tinderbox source code is maintained in the
487
	possible.  The Tinderbox source code is maintained in the
498
	FreeBSD CVS repository in the directory <a
488
	FreeBSD CVS repository in the directory <a
499
	  href="http://cvsweb.FreeBSD.org/src/tools/tools/tinderbox/">src/tools/tools/tinderbox</a>.</li>
489
	  href="http://cvsweb.FreeBSD.org/src/tools/tools/tinderbox/">src/tools/tools/tinderbox</a>.</li>
500
490
      <li><h3>Unmaintained Pages</h3>
501
      <li><a name="gnats4" href="./gnats4/index.html">The FreeBSD
491
          <ul>
502
	GNATS Upgrade</a>: This page details the tasks, timeline and
492
              <li><A name="freebsdtour" href="http://snapshots.jp.FreeBSD.org/tour/">FreeBSD source code tour</A>:
503
	implementation involved in upgrading the FreeBSD bug
493
	      A hypertext cross referenced presentation of the FreeBSD kernel
504
	tracking system from GNATS 3 to GNATS 4.</li>
494
	      source code. The versions indexed are -CURRENT and RELENG_4.</li>
495
              <li><A name="enterman" href="http://www.de.daemonnews.org/199908/enteruser.html">Enteruser</a>: A Replacement for adduser.</li>
496
              <li><a name="c99" href="&base;/projects/c99/index.html">The
497
	      FreeBSD C99 &amp; &posix; Conformance Project</a>: This project 
498
	      aims to implement all requirements of the ISO 9899:1999 (C99) and
499
	      IEEE 1003.1-2001 (POSIX) standards.</li>
500
              <li><a name="gnats4" href="./gnats4/index.html">The FreeBSD
501
	      GNATS Upgrade</a>: This page details the tasks, timeline and
502
	      implementation involved in upgrading the FreeBSD bug
503
	      tracking system from GNATS 3 to GNATS 4.</li>
504
          </ul>
505
      </li>
505
</ul>
506
</ul>

Return to bug 99326