529 lines
		
	
	
	
		
			25 KiB
		
	
	
	
		
			Text
		
	
	
	
	
	
			
		
		
	
	
			529 lines
		
	
	
	
		
			25 KiB
		
	
	
	
		
			Text
		
	
	
	
	
	
| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
 | |
| <!ENTITY base CDATA "..">
 | |
| <!ENTITY date "$FreeBSD: www/en/projects/projects.sgml,v 1.125 2002/04/13 10:29:47 murray Exp $">
 | |
| <!ENTITY title "FreeBSD Development Projects">
 | |
| <!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
 | |
| ]>
 | |
| 
 | |
| <html>
 | |
| &header;
 | |
| 
 | |
| <a name="development"></a>
 | |
| 
 | |
| <p>In addition to the mainstream development path of FreeBSD, a number
 | |
| of developer groups are working on the cutting edge to expand
 | |
| FreeBSD's range of applications in new directions.  Follow the links
 | |
| below to learn more about these exciting projects.</p>
 | |
| 
 | |
| If you miss a project please send the URL and a short
 | |
| description (3-10 lines) to
 | |
| <A HREF="../mailto.html">www@FreeBSD.ORG</A>
 | |
| 
 | |
| <p>In addition, some of these projects regularly submit status reports,
 | |
| which can be viewed on the <a href="../news/status/status.html">status
 | |
| reports page</a>.</p>
 | |
| 
 | |
| <ul>
 | |
|   <li><a href="#documentation">Documentation</a></li>
 | |
|   <li><a href="../advocacy/index.html">Advocacy</a></li>
 | |
|   <li><a href="#applications">Applications</a></li>
 | |
|   <li><a href="#networking">Networking</a></li>
 | |
|   <li><a href="#filesystem">Filesystem</a></li>
 | |
|   <li><a href="#kernelandsecurity">Kernel and Security</a></li>
 | |
|   <li><a href="#devicedrivers">Device drivers</a></li>
 | |
| <li><a href="#architecture">Architecture</a></li>
 | |
| <li><a href="#misc">Misc</a></li>
 | |
| </ul>
 | |
| 
 | |
| <a name="documentation"></a>
 | |
| <h3>Documentation</h3>
 | |
| <ul>
 | |
| <li><a href="../docproj/docproj.html">FreeBSD Documentation Project</a>
 | |
| The FreeBSD Documentation Project is a group of people who maintain
 | |
| and write the documentation (such as the Handbook and FAQ) for the
 | |
| FreeBSD	project.  If you want to help with the documentation project,
 | |
| subscribe to the freebsd-doc@FreeBSD.ORG
 | |
| mailing list and participate.</li>
 | |
| 
 | |
| <li><a name="newbies" href="newbies.html">FreeBSD Resources for Newbies</a>
 | |
| is a list of resources to help those new to FreeBSD and UNIX in
 | |
| general.  There is also a 
 | |
| freebsd-newbies@FreeBSD.ORG mailing list.</li>
 | |
| 
 | |
| <li><a name="retail" href="http://www.bafug.org/purchase/FbsdRetail.html">Retail Outlets for FreeBSD</a>
 | |
| is a list of worldwide retailers where FreeBSD can be purchased.</li>
 | |
| 
 | |
| <li><a name="securityhowto" href="http://people.FreeBSD.org/~jkb/howto.html">
 | |
| FreeBSD Security How-To</a>
 | |
| FreeBSD is a very secure operating system. Since source code
 | |
| is freely available, the OS is constantly going through the
 | |
| review and audit. While FreeBSD comes very secure OOB
 | |
| (Out-Of-Box), there are many features that can make it more
 | |
| secure for those of you who are "paranoid". This How-To will
 | |
| go over some steps which will help you increase overall
 | |
| security of your machine.</li>
 | |
| 
 | |
| <li><a name="BSDsites" href="http://www.freebsdmirrors.org/">
 | |
| RELEASE/SNAP finder for FreeBSD FTP servers</a>.
 | |
| A resource that would allow anyone to find a FTP server that contains
 | |
| particular releases and SNAP of FreeBSD. The database is updated daily
 | |
| at 3am Melbourne time (10 hours ahead of UTC).</li>
 | |
| 
 | |
| <li><a name="diary" href="http://www.freebsddiary.org/">The FreeBSD
 | |
| Diary</a> is a collection of how-to entries aimed at UNIX
 | |
| novices.  The aim is to provide a set of step-by-step guides to
 | |
| installing and configuring various ports.</li>
 | |
| 
 | |
| <li><A HREF="http://www.vmunix.com/fbsd-book/">A Comprehensive
 | |
| Guide to FreeBSD</A> - an attempt at a more readable,
 | |
| "book-like" tutorial explaining the FreeBSD Operating
 | |
| System. Intended for people new to both FreeBSD and
 | |
| UNIX. Currently a work in progress.</li>
 | |
| 
 | |
| <li><A HREF="http://flag.blackened.net/freebsd/">FreeBSD
 | |
| How-To's for the Lazy and Hopeless</A> is another somewhat more
 | |
| light-hearted attempt to provide more readable "how-to" style
 | |
| information on setting up and configuring FreeBSD.</li>
 | |
| 
 | |
| <li><A HREF="http://www.linuxdoc.org/HOWTO/mini/Linux+FreeBSD.html">The
 | |
| Linux+FreeBSD mini-HOWTO</a> describes how to
 | |
| use Linux and FreeBSD on the same system. It introduces FreeBSD
 | |
| and discusses how the two operating systems can cooperate,
 | |
| e.g. by sharing swap space.</li>
 | |
| 
 | |
| <li><a href="http://people.FreeBSD.org/~rpratt/227/index.html">
 | |
| Install Preview for FreeBSD 2.2.7</a>
 | |
| This is a guide illustrating the FreeBSD install program for 
 | |
| those new to unix and/or FreeBSD.</li>
 | |
| 
 | |
| <li><a href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/index.html"> 
 | |
| Programmer's Documentation Project</a></li>
 | |
| 
 | |
| <li><a name="cookbook" 
 | |
| href="http://home.austin.rr.com/aaweber/CookBook/cookbook.html">
 | |
| The FreeBSD Cook Book</a>
 | |
| Ok, you got FreeBSD installed, now what? Here are some suggested
 | |
| solutions to common problems you can implement with the knowledge
 | |
| you now have. This document is styled after the electronics cook
 | |
| books with some recipes for some common types of installations.
 | |
| Each "recipe" has some recommended minimum hardware, specific
 | |
| software to use, and most important the configuration information
 | |
| required to get the system running correctly.</li>
 | |
| 
 | |
| <li><a name="freebsd-corp-net-guide"
 | |
| href="http://www.freebsd-corp-net-guide.com/">
 | |
| The FreeBSD Corporate Networker's Guide</a>
 | |
| This Web site serves as a supplement to The FreeBSD Corporate
 | |
| Networker's Guide, with the principal goal of enhancing its
 | |
| usefulness. While books like fictional novels can be used and enjoyed
 | |
| for hundreds of years after initial publication, technical manuals
 | |
| like the Networker's Guide are obsoleted in a few years by changes in
 | |
| the product they are written for.
 | |
| </li>
 | |
| 
 | |
| </ul>
 | |
| 
 | |
| <a name="applications"></a>
 | |
| <h3>Applications</h3>
 | |
| <ul>
 | |
| <li><a name="java" href="../java/index.html">Java on FreeBSD</a>
 | |
| This contains information on where to obtain the latest JDK for
 | |
| FreeBSD, how to install and run it, and a list of java software that
 | |
| you may find interesting.  Please note that the JDK is unsupported on
 | |
| versions of FreeBSD prior to 2.2.</li>
 | |
| 
 | |
| <li><a name="gnome" href="../gnome/index.html">GNOME on FreeBSD</a>
 | |
| This contains information on where to obtain the latest GNOME for
 | |
| FreeBSD, how to install and run it, latest project news and
 | |
| updates, FAQ covering FreeBSD-specific GNOME issues, application
 | |
| porting guidelines and much more.</li>
 | |
| 
 | |
| <li><a name="multimedia" href="http://people.FreeBSD.org/~faulkner/multimedia/mm.html">MultiMedia</a>
 | |
| A resource of links to information and software pertaining to the world
 | |
| of multimedia in the UNIX world.</li>
 | |
| 
 | |
| <li><a href="../ports/index.html">FreeBSD Ports Collection</a>
 | |
| The FreeBSD Ports Collection provides an easy way to compile and
 | |
| install a wide range of applications with a minimum amount of effort.
 | |
| A list of current ports is available along with a search mechanism
 | |
| to see if a specific application exists in the Ports Collection.</li>
 | |
| 
 | |
| <li><a href="http://people.FreeBSD.org/~fenner/portsurvey/">FreeBSD Ports distfiles survey</a>
 | |
| is a list which checks the Ports Collection for unfetchable distfiles
 | |
| and provides a summary for each port.</li>
 | |
| 
 | |
| <li><a href="http://FreshPorts.org/">FreshPorts</a> provides the most up-to-date list of 
 | |
| ports and port changes.  Add your favourite ports to your watch list and receive email
 | |
| notification of any changes.</li>
 | |
| </ul>
 | |
| 
 | |
| <a name="networking"></a>
 | |
| <h3>Networking</h3>
 | |
| <ul>
 | |
| <li><a name="altq"  href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html">ALTQ</a>: bandwidth management for applications</li>
 | |
| <li><a name="kame" href="http://www.kame.net/">KAME Project</a>, a free IPv6/IPsec stack for BSD</li>
 | |
| <li><a name="ppp" href="http://www.awfulhak.org/ppp.html">Point to Point Protocol (PPP)</a></li>
 | |
| <li><a name="smn" href="http://www.cs.pdx.edu/research/SMN/">Secure MobileIP via IP</a></li>
 | |
| <li><a name="SYSLOG-SECURE">SYSLOG-SECURE</a>:
 | |
| In August 2001 a standard of syslog was made: RFC3164. This
 | |
| to describe some extensions tot syslog to add security. The project I
 | |
| started in 2002 is to adapt RFC3164 to FreeBSD version of syslog, and to add
 | |
| some security extensions. At least syslog-sign. Both libc and syslogd will
 | |
| be modified. And optional some tools to verify/manage the security will
 | |
| made.
 | |
| All help is welcome. Send an email to albert@ons-huis.net for info.
 | |
| </ul>
 | |
| 
 | |
| <a name="filesystem"></a>
 | |
| <h3>File system</h3>
 | |
| <ul>
 | |
| <li><a name="afs" href="http://www.stacken.kth.se/projekt/arla/">Arla</a>
 | |
| is a free AFS client implementation.  The main goal is to
 | |
| make a fully functional client with all capabilities of normal AFS.
 | |
| Other planned and implemented things are all the normal management
 | |
| tools and a server.</li>
 | |
| 
 | |
| <li><a name="coda" href="http://www.coda.cs.cmu.edu/">Coda</a> is
 | |
| a distributed filesystem.  Among its features are disconnected
 | |
| operation, good security model, server replication and persistent
 | |
| client side caching.</li>
 | |
| 
 | |
| <li><a name="crossfs" href="http://crossfs.bizland.com/cxvfs.html">
 | |
| crossFS Virtual File System</a>
 | |
| is based on FreeBSD Virtual File System and provides a
 | |
| framework for porting UNIX based filesystems to Windows NT systems.
 | |
| </li>
 | |
| 
 | |
| <li><a name="cruptfs" href="http://www.cs.columbia.edu/~ezk/research/software/">cryptfs</a> encrypts file names and data pages using Blowfish.</li>
 | |
| 
 | |
| <li><a name="elephant" href="http://www.cs.ubc.ca/~feeley/DSG%20Web/dsg_p_elephant.html">Elephant</a>: The File System that Never Forgets
 | |
| 
 | |
| <li><a name="journaling" href="http://www.ece.cmu.edu/~ganger/papers/">
 | |
| Journaling versus Soft Updates: Asynchronous Meta-data Protection in File Systems</a></li>
 | |
| 
 | |
| <li><a href="http://people.FreeBSD.org/~terry/">Mode locking</a></li>
 | |
| <li><a href="http://people.FreeBSD.org/~terry/">Make the namei interface reflexive</a></li>
 | |
| <li><a href="http://people.FreeBSD.org/~terry/">NFS client and server locking</a></li>
 | |
| 
 | |
| <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>
 | |
| 
 | |
| <li><a href="http://iclub.nsu.ru/~semen/ntfs/">NTFS Driver for FreeBSD</a>
 | |
| This driver allows Windows NTFS partitions to be mounted by FreeBSD.
 | |
| Currently NTFS partitions can only be accessed in read-only mode, but
 | |
| plans are in the works for read/write access.</li>
 | |
| 
 | |
| <li><a name="rio" href="http://www.eecs.umich.edu/Rio/">Rio (RAM
 | |
| I/O)</a>: The Rio project is investigating how to implement and
 | |
| use reliable memory.  Reliable memory enables dramatic
 | |
| improvements in reliability and performance.</li>
 | |
| 
 | |
| <li><a name="softupdate" href="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/sys/ufs/ffs/README.softupdates"> Soft Updates:</a>
 | |
| A Solution to the Metadata Update Problem in File Systems</li>
 | |
| 
 | |
| <li><a name="tcfs" href="http://tcfs.dia.unisa.it/">TCFS</a>
 | |
| is a Transparent Cryptographic File System that is a suitable
 | |
| solution to the problem of privacy for distributed filesystem. By a
 | |
| deeper integration between the encryption service and the filesystem,
 | |
| it results in a complete transparency of use to the user
 | |
| applications. Files are stored in encrypted form and are decrypted
 | |
| before they are read. The encryption/decryption process takes place on
 | |
| the client machine and thus the encryption/decryption key never
 | |
| travels on the network.</li>
 | |
| 
 | |
| <li><a name="Tertiary" href="http://now.cs.berkeley.edu/Td/">Tertiary Disk</a>
 | |
| is a storage system architecture to create large disk storage systems
 | |
| that avoid the disadvantages of custom built disk arrays. The
 | |
| name comes from twin goals: to have the cost per megabyte and
 | |
| capacity of tape libraries and the performance of magnetic
 | |
| disks. We use commodity, off the shelf components to develop a
 | |
| scalable, low cost, terabyte capacity disk system. Our target is
 | |
| to build a complete storage system with about 30-50% extra to
 | |
| the cost of the raw disk.  Tertiary Disk uses PCs connected by a
 | |
| switched network to host a large number of disks. Our prototype
 | |
| consists of 20 200MHz PC PCs, which host 370 8GB disks. The PCs
 | |
| are connected through a 100Mbps Ethernet switch.</li>
 | |
| 
 | |
| <li><a name="vinum" href="http://www.vinumvm.org/">Vinum</a>
 | |
| is a logical volume manager modeled after the VERITAS volume manager.
 | |
| However, it is not a clone of Veritas, and attempts to solve a
 | |
| number of problems more elegantly than Veritas.  It also offers
 | |
| features that Veritas does not have.</li>
 | |
| 
 | |
| <li><a name="PathConvert" href="http://www.tamacom.com/pathconvert/">
 | |
| The PathConvert project</a> is to develop utilities which make
 | |
| conversion between absolute path name and relative path name. It
 | |
| brings benefits mainly to the users of NFS and WWW.</li>
 | |
| 
 | |
| <li><a name="v9fs" href="http://www.acl.lanl.gov/~rminnich/">
 | |
| V9FS: Memory-based filesystem for FreeBSD</a> It will (we hope)
 | |
| become the basis of private name spaces for FreeBSD in the
 | |
| future. It provides a filesystem that uses only memory for
 | |
| directories, inodes, and data.  This is not at all like mfs,
 | |
| since mfs uses memory for "disk blocks", and essentially acts as
 | |
| the device for UFS. V9FS in contrast is a first-class citizen
 | |
| and is a full mountable filesystem. No writeup yet.</li>
 | |
| 
 | |
| <li><a name="WAFS" href="http://www.eecs.harvard.edu/~stein/wafs/">
 | |
| WAFS</a> is a simple filesystem designed to act as a logging
 | |
| service for kernel subsystems. Reads and writes are keyed
 | |
| by log-sequence number (LSN). All writes to WAFS are     
 | |
| sequential. Kernel subsystems can use this LSN service to
 | |
| enforce write-ahead logging and guarantee consistency. 
 | |
| </li>
 | |
| 
 | |
| </ul>
 | |
| 
 | |
| <a name="kernelandsecurity"></a>
 | |
| <h3>Kernel, security</h3>
 | |
| <ul>
 | |
| <li><a name="drawbridge" href="http://drawbridge.tamu.edu/">Drawbridge</a>
 | |
| is a firewall package that was developed at Texas A&M University and
 | |
| was designed with a large academic environment in mind.  It's greatest
 | |
| strength is the ability to perform high speed packet filtering for
 | |
| a larger number of individual hosts within an intranetwork.</li>
 | |
| 
 | |
| <li><a name="lotteryscheduling"
 | |
| href="http://www.csua.berkeley.edu/computing/software/lottery-sched.html">
 | |
| Lottery Scheduling Kernel</a>: This work is based on
 | |
| Waldspurger's lottery scheduling algorithm, which implements
 | |
| proportional-share resource management. The primary advantages
 | |
| are that users have strict control over the relative execution
 | |
| rates of their processes, and users are load-insulated from each
 | |
| other, preventing one user from dominating the CPU.</li>
 | |
| 
 | |
| 
 | |
| <li><a name="metacomputing" href="http://www.acl.lanl.gov/~rminnich/">Metacomputing</a></li>
 | |
| <li><a name="DHCP" href="http://home.san.rr.com/freebsd/dhcp.html">DHCP configuration</a>
 | |
| How to set up DHCP on FreeBSD systems for use with cable modems, etc.</li>
 | |
| 
 | |
| <li><a href="http://people.FreeBSD.org/~terry/">Working LDAP for FreeBSD</a></li>
 | |
| 
 | |
| <li><a name="SMP" href="http://people.FreeBSD.org/~fsmp/SMP/SMP.html">Symmetric MultiProcessor Support</a>
 | |
| Documentation and other information about taking advantage of multiple
 | |
| processors under FreeBSD.</li>
 | |
| <li><a href="http://people.FreeBSD.org/~terry/">A validation suite for testing for kernel memory leaks</a></li>
 | |
| <li><a name="spy" href="http://people.FreeBSD.org/~abial/spy/">SPY</a>
 | |
| allows you to monitor and/or selectively block syscalls on your
 | |
| system. It could be used either as a safety monitoring device, policy
 | |
| enforcement, or debugging tool.</li>
 | |
| 
 | |
| <li><a name="trustedbsd" href="http://www.TrustedBSD.org/">TrustedBSD</a>
 | |
| provides a set of trusted operating system extensions to the FreeBSD operating
 | |
| system.  This includes features such as fine-grained privileges (capabilities),
 | |
| Access Control Lists, and Mandatory Access Control.  These features are
 | |
| being integrated back into the base FreeBSD distribution, as well as being
 | |
| ported to other BSD-derived systems.</li>
 | |
| 
 | |
| </ul>
 | |
| 
 | |
| <a name="devicedrivers"></a>
 | |
| <h3>Device drivers</h3>
 | |
| <ul>
 | |
| <li><a name="fdd" href="http://www.posi.net/freebsd/drivers/">BSD Driver Database</a>
 | |
| Just because you don't have the time to write the driver
 | |
| yourself doesn't mean you can't still help. The idea behind
 | |
| the BSD Driver Database is to help individuals with
 | |
| hardware that needs supporting get in touch with driver
 | |
| developers with the knowledge to write the support for the
 | |
| hardware. This is a list of drivers currently under
 | |
| development that could stand to gain from time or resources
 | |
| you may have to offer.</li>
 | |
| 
 | |
| <li><a name="deviceframework" href="http://people.FreeBSD.org/~dfr/devices.html">
 | |
| A New Device Framework for FreeBSD</a></li>
 | |
| 
 | |
| <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>:
 | |
| New computer applications in areas such as multimedia, imaging,
 | |
| and distributed computing demand high levels of performance from
 | |
| computer networks. ATM-based networking solutions provide one
 | |
| possible alternative to meeting these performance needs.
 | |
| However, the complexity of ATM over traditional networks such as
 | |
| Ethernet has proven to be a barrier to its being used. In this
 | |
| paper we present the design and implementation of BSD ATM, a
 | |
| light-weight and efficient ATM software layer for BSD-based
 | |
| operating systems that requires minimal changes to the operating
 | |
| system. BSD ATM can be used both for IP-based networking traffic
 | |
| and for ``native'' ATM traffic.</li>
 | |
| 
 | |
| <li><a name="NVIDIA" href="http://nvidia.netexplorer.org/">
 | |
| The FreeBSD NVIDIA Driver
 | |
| Initiative</a> - An initiative aiming for NVIDIA supported 3D drivers for
 | |
| FreeBSD. This is to be accomplished with help from the FreeBSD developer
 | |
| community as well as NVIDIA. Please visit the web page for regular news
 | |
| updates and to find out how you can help.</li>
 | |
| 
 | |
| 
 | |
| <li><a name="timekeeping" href="http://phk.freebsd.dk/rover.html">High-precision timekeeping with FreeBSD</a>
 | |
| How to create a NTP stratum 1 server with state of the art
 | |
| performance.</li>
 | |
| 
 | |
| <li><a name="homeauto" href="http://people.FreeBSD.org/~fsmp/HomeAuto/HomeAuto.html">Home Automation</a>
 | |
| with FreeBSD such as appliance controllers, infra-red controllers,
 | |
| automated telephone systems, and more.</li>
 | |
| 
 | |
| <li><a name="isdn" href="http://www.freebsd-support.de/i4b/">i4b: ISDN for FreeBSD</a>
 | |
| ISDN4BSD (or i4b for short) is a package for interfacing a computer
 | |
| running FreeBSD, NetBSD, OpenBSD, or BSD/OS to ISDN.  The only ISDN
 | |
| protocol currently supported is the BRI protocol.  ISDN4BSD allows you
 | |
| to make IP network connections by using either IP packets sent in raw
 | |
| HDLC frames on the B channel, or by using sychronous PPP.  For
 | |
| telephony, ISDN4BSD can answer incoming phone calls like an answering
 | |
| machine.</li>
 | |
| 
 | |
| <li><a name="cam" href="http://people.FreeBSD.org/~gibbs/">CAM: New SCSI layer for FreeBSD</a>
 | |
| Details about what the new CAM SCSI layer is, and how it works.</li>
 | |
| 
 | |
| <li><a name="tokenring" href="http://www.jurai.net/~winter/tr/tr.html">The FreeBSD Token-Ring Project</a>
 | |
| Information, files, patches, and documentation about adding Token Ring
 | |
| support to FreeBSD.</li>
 | |
| 
 | |
| <li><a name="usb" href="http://www.etla.net/~n_hibma/usb/usb.pl"> FreeBSD USB driver development</a>
 | |
| The NetBSD USB stack has been ported to FreeBSD. Together with them we
 | |
| have started developing the drivers for many devices using the USB bus.
 | |
| Have a look on the webpage if you want to join the effort or you want to
 | |
| have a look on the devices that are being supported.</li>
 | |
| 
 | |
| <li><a name="awe64"
 | |
| href="http://www.r.dl.itc.u-tokyo.ac.jp/~tanimura/awepnp-freebsd.html">Setting
 | |
| up PnP (Plug-and-Play) and the AWE64, AWE32, or SB32 soundcards with FreeBSD.</a></li>
 | |
| 
 | |
| <li><a name="xircomcem"></a>A mailing list exists for further 
 | |
| development of Scott Mitchell's Xircom CEM ethernet driver.  Send
 | |
| <tt>subscribe freebsd-xircom</tt> to <a 
 | |
|   href="mailto:majordomo@lovett.com">majordomo@lovett.com</a> to 
 | |
| join.</li>
 | |
| 
 | |
| <li><a name="raid"></a>Mike Smith's <a
 | |
| href="http://people.FreeBSD.org/~msmith/RAID/">list</a> of supported RAID
 | |
| cards and their respective information.</li>
 | |
| </ul>
 | |
| 
 | |
| <a name="architecture"></a>
 | |
| <h3>Architecture</h3>
 | |
| <ul>
 | |
| <li><a name="alpha" href="../platforms/alpha.html">Porting FreeBSD to Alpha systems</a>
 | |
| Contains information on the FreeBSD Alpha port such as the status,
 | |
| mailing list information, the hardware used, and other Alpha
 | |
| projects.</li>
 | |
| 
 | |
| <li><a name="ia64" href="../platforms/ia64.html">
 | |
| Porting FreeBSD to IA-64 systems</a>
 | |
| This project is responsible for porting FreeBSD to the IA-64 
 | |
| architecture. Direct any questions specific to this project to the 
 | |
| freebsd-ia64@FreeBSD.org mailing list. </li>
 | |
| 
 | |
| <li><a name="ppc" href="../platforms/ppc.html">Porting FreeBSD to PowerPC systems.</a>
 | |
| Contains information on the FreeBSD PPC port, such as mailing list
 | |
| information and so on.</li>
 | |
| 
 | |
| <li><a name="sparc" href="../platforms/sparc.html">Porting FreeBSD to SPARC systems</a>
 | |
| Contains information on the FreeBSD SPARC port including a FAQ,
 | |
| some early boot code, information on SPARC processors and motherboards,
 | |
| and other SPARC projects.</li>
 | |
| 
 | |
| <li><a name="sysvr4" href="http://slash.dotat.org/~newton/freebsd-svr4/">
 | |
| The SysVR4 Emulation</a> page describes an SysVR4 emulator for
 | |
| FreeBSD. It is currently capable of running (or walking, in some
 | |
| cases) a wide-ish variety of SysV executables taken from Solaris/x86
 | |
| 2.5.1 and 2.6 systems. I have reason to believe that it will also run
 | |
| SCO UnixWare and SCO OpenServer binaries.</li>
 | |
| 
 | |
| <li><a name="oskit" href="http://www.cs.utah.edu/flux/oskit/">The OSKit</a>
 | |
| The OSKit is a framework and a set of 31 component libraries oriented
 | |
| to operating systems, together with extensive documentation. By
 | |
| providing in a modular way not only most of the infrastructure
 | |
| "grunge" needed by an OS, but also many higher-level components, the
 | |
| OSKit's goal is to lower the barrier to entry to OS R&D and to
 | |
| lower its costs. The OSKit makes it vastly easier to create a new OS,
 | |
| port an existing OS to the x86 (or in the future, to other
 | |
| architectures supported by the OSkit), or enhance an OS to support a
 | |
| wider range of devices, filesystem formats, executable formats, or
 | |
| network services. The OSKit also works well for constructing OS-related
 | |
| programs, such as boot loaders or OS-level servers atop a
 | |
| microkernel.</li>
 | |
| 
 | |
| <li><a name="picobsd" href="http://people.FreeBSD.org/~picobsd/">Small and embedded FreeBSD (PicoBSD)</a>
 | |
| PicoBSD is a one floppy version of FreeBSD which in its different
 | |
| variations allows you to have secure dial-up access, small diskless
 | |
| router, or even a dial-in server.  All of this on only one standard
 | |
| 1.44MB floppy disk.  It runs on a minimum 386SX CPU with 8MB of RAM,
 | |
| and no hard drive is required!</li>
 | |
| 
 | |
| <li><a name="buds" href="http://www.mozie.org/projects/buds/index.html">
 | |
| BUDS: BSD Unix Distributed Simple-ly</a>
 | |
| 
 | |
| Provide a general purpose clustering system for further
 | |
| development into parallel-multi-processors. This system is
 | |
| intended to be generic in nature, but powerful. It is not intend
 | |
| for computationally intensive applications, nor is it intended
 | |
| for highly complex interdependent applications.</li>
 | |
| 
 | |
| <li>The <a name="Eclipse"
 | |
| href="http://www.bell-labs.com/project/eclipse/release/">Eclipse</a>
 | |
| Operating System is a testbed for Quality of Service (QoS) that is
 | |
| being developed at Information Sciences Research Center in Bell-Labs,
 | |
| Lucent Technologies. 
 | |
| 
 | |
| Eclipse provides flexible and fine-grained QoS support for
 | |
| applications. Its design allows legacy or Eclipse-unaware applications
 | |
| to provide QoS without the need of modification or recompilation. A
 | |
| simple API is provided for (new) applications to take advantage of
 | |
| the fine-grained QoS support.
 | |
| 
 | |
| Currently, the Eclipse project targets QoS support for server
 | |
| applications, in particular, to differentiate the performance of
 | |
| different web sites hosted on the same platform (see the Apache
 | |
| examples).  </li>
 | |
| </ul>
 | |
| 
 | |
| <a name="misc"></a>
 | |
| <h3>Misc</h3>
 | |
|     <ul>
 | |
|       <li><a name="global" href="http://www.tamacom.com/global/">GLOBAL</a>
 | |
| 	is a common source code tag system that works the same way across
 | |
| 	diverse environments.  Currently, it supports the shell command line,
 | |
| 	the nvi editor, web browser, the emacs editor, and the elvis editor,
 | |
| 	and the supported languages are C, Yacc, and Java.</li>
 | |
| 
 | |
|       <li><a name="pao" href="http://www.jp.FreeBSD.org/PAO/">PAO: Mobile Computing page, laptops running FreeBSD</a>
 | |
| 	PAO enables FreeBSD to drive many PCMCIA (PC-card) cards and also
 | |
| 	provides you with PC-card "hotplug" on your laptop machines running
 | |
| 	FreeBSD.  It also contains some improvements and bug fixes for the
 | |
| 	APM BIOS driver.</li>
 | |
| 
 | |
|       <li><A name="freebsdxr" HREF="http://lxr.linux.no/freebsd/source">FreeBSD cross reference</A>.
 | |
| 	A hypertext cross referenced presentation of the FreeBSD kernel
 | |
| 	sourecode. The version indexed is -CURRENT, and it is updated every
 | |
| 	night.</li>
 | |
|       <li><A name="enterman" HREF="http://www.de.daemonnews.org/199908/enteruser.html">Enteruser: A Replacement for Adduser</A></li>
 | |
|       <li><A name="libh" HREF="libh.html">FreeBSD libh Project</A>.
 | |
|         Libh is a wrapper that allows tcl scripts to
 | |
| 	run in a sort of sandbox and interface to other libraries.
 | |
| 	Some of the stock libraries that come with libh that can be
 | |
| 	called from the Tcl scripts include a generic user interface library,
 | |
| 	which uses Turbo Vision for its console backend, and Qt for its X11
 | |
| 	backend.  Libh also includes a new package system that uses Zip
 | |
| 	archives and various per-package scripts among other things.  It also
 | |
| 	includes the beginnings of a new sysinstall.</li>
 | |
| 
 | |
|       <li><A name="binup" HREF="updater.html">Binary Updater
 | |
| 	(binup)</A>.  The FreeBSD Binary Updater Project aims to
 | |
| 	provide a secure mechanism for the distribution of binary
 | |
| 	updates for FreeBSD.  This system is a client / server
 | |
| 	mechanism that allows clients to install any known "profile"
 | |
| 	or release of FreeBSD over the network. Where a specific
 | |
| 	profile might contain a specific set of FreeBSD software to
 | |
| 	install, additional packages, and configuration actions that
 | |
| 	make it more ideal for a specific environment (ie FreeBSD 4.3
 | |
| 	Secure Web server profile).</li>
 | |
| 
 | |
|       <li><a name="c99" href="&base;/projects/c99/index.html">The
 | |
| 	FreeBSD C99 & POSIX Conformance Project</a> aims to
 | |
| 	implement all requirements of the ISO 9899:1999 (C99) and
 | |
| 	IEEE 1003.1-2001 (POSIX) standards.</li>
 | |
| </ul>
 | |
| 
 | |
| 
 | |
| &footer;
 | |
| </body>
 | |
| </html>
 |