diff --git a/handbook/development.sgml b/handbook/development.sgml index 5e60efedfc..c98a4910b9 100644 --- a/handbook/development.sgml +++ b/handbook/development.sgml @@ -1,109 +1,109 @@ - + The FreeBSD development model

Contributed by &a.asami;.

The development of FreeBSD is a very open and flexible process, FreeBSD being literally built from the contributions of hundreds of people around the world, as can be seen from our . We are constantly on the lookout for new developers and ideas, and those interested in becoming more closely involved with the project need simply contact us at the &a.hackers;. Those who prefer to work more independently are also accommodated, and they are free to use our FTP facilities at to distribute their own patches or work-in-progress sources. The &a.announce; is also available to those wishing to make other FreeBSD users aware of major areas of work. Useful things to know about the FreeBSD project and its development process, whether working independently or in close cooperation: The CVS repository

The central source tree for FreeBSD is maintained by (Concurrent Version System), a freely available source code control tool which comes bundled with FreeBSD. The primary +url="http://www.freebsd.org/cgi/cvsweb.cgi" name="CVS repository"> resides on a machine in Concord CA, USA from where it is replicated to numerous mirror machines throughout the world. The CVS tree, as well as the and trees which are checked out of it, can be easily replicated to your own machine as well. Please refer to the section for more information on doing this. The committers list

The are the people who have write access to the CVS tree, and are thus authorized to make modifications to the FreeBSD source (the term ``committer'' comes from the cvs(1) ``commit'' command, which is used to bring new changes into the CVS repository). The best way of making submissions for review by the committers list is to use the command, though if something appears to be jammed in the system then you may also reach them by sending mail to . The FreeBSD core team

The would be equivalent to the board of directors if the FreeBSD Project were a company. The primary task of the core team is to make sure the project, as a whole, is in good shape and is heading in the right directions. Inviting dedicated and responsible developers to join our group of committers is one of the functions of the core team, as is the recruitment of new core team members as others move on. Most current members of the core team started as committers who's addiction to the project got the better of them.

Some core team members also have specific , meaning that they are committed to ensuring that some large portion of the system works as advertised. Note that most members of the core team are volunteers when it comes to FreeBSD development and do not benefit from the project financially, so "commitment" should also not be misconstrued as meaning "guaranteed support." The ``board of directors'' analogy above is not actually very accurate, and it may be more suitable to say that these are the people who gave up their lives in favor of FreeBSD against their better judgement! ;) Outside contributors

Last, but definitely not least, the largest group of developers are the users themselves who provide feedback and bug-fixes to us on an almost constant basis. The primary way of keeping in touch with FreeBSD's more non-centralized development is to subscribe to the &a.hackers; (see ) where such things are discussed. of those who have contributed something which made its way into our source tree is a long and growing one, so why not join it by contributing something back to FreeBSD today? :-)

Providing code is not the only way of contributing to the project; for a more complete list of things that need doing, please refer to the section in this handbook. In summary, our development model is organized as a loose set of concentric circles. The centralized model is designed for the convenience of the users of FreeBSD, who are thereby provided with an easy way of tracking one central code base, not to keep potential contributors out! Our desire is to present a stable operating system with a large set of coherent that the users can easily install and use, and this model works very well in accomplishing that. All we ask of those who would join us as FreeBSD developers is some of the same dedication its current people have to its continued success! diff --git a/handbook/sup.sgml b/handbook/sup.sgml index a64f0ab4f8..3bc3fd0c8d 100644 --- a/handbook/sup.sgml +++ b/handbook/sup.sgml @@ -1,159 +1,159 @@ - + SUP

Contributed by &a.jkh; and &a.gclarkii;. SUP is a network based software update tool developed at CMU. The purpose of this document is get the beginner up and running with sup. Configuration

SUP gets the information it needs to run from a configuration file called a supfile. There are different example supfiles provided for different source releases of FreeBSD. The file, for example, contains sup information for the latest standard FreeBSD source distributions - it tells sup what collections it will be updating and/or installing and where they go. Someone using this particular supfile is said to be supping .

For ports, please have a look at .

If you are interested in obtaining the - files + files that make up the source tree, refer to .

If you would rather track changes to the -stable branch, refer to instead. If you are inside the United States, you may also uncomment the `secure' and `eBones' collection lines to grab the DES code. If you are outside the U.S., you should NOT sup this code from sup.FreeBSD.ORG as this will violate U.S. export restrictions. Instead you should use the in the sup examples directory. This will connect you to the international sup site that contains a secure distribution. Any distributions you do not wish to receive can be commented out with a # at the beginning of the distribution line. Please consult the file for a list of alternate sup servers. The default sup server (sup.FreeBSD.ORG) listed in the above example files is currently overloaded and any traffic that can be transfered to a different host will help relieve some of the strain. Once this is setup, you are ready to go. To start sup type: sup supfile If you wish to see what sup is doing "verbosely", give it the -v option, like so: sup -v supfile Thats all there is to it! Remember that if you are running current, which is what you will have if you sup with the standard-supfile, please join the &a.current . You should also be sure to read for important information on just what we can and cannot do for you as a -current user. If you are using the stable-supfile, please join the &a.stable and read . Distributions

For the main FreeBSD distribution using the standard-supfile: src-base: /usr/src/... misc files at the top of /usr/src src-bin: /usr/src/bin user and system binaries src-secure: /usr/src/secure DES Sources (US/Canada ONLY) src-eBones: /usr/src/eBones Kerberos and DES (US/Canada ONLY) src-etc: /usr/src/etc system files src-games: /usr/src/games games src-gnu: /usr/src/gnu sources under the GNU Public License src-include: /usr/src/include include files src-sys: /usr/src/sys kernel sources src-lib: /usr/src/lib libraries src-libexec: /usr/src/libexec system binaries src-release: /usr/src/release sources required to build a release src-share: /usr/src/share various shared resources src-sbin: /usr/src/sbin single user system binaries src-tools: /usr/src/tools various management tools src-usrbin: /usr/src/usr.bin user binaries src-usrsbin: /usr/src/usr.sbin system binaries

For the international FreeBSD distribution using the secure-supfile: src-secure: /usr/src/secure DES Sources src-eBones: /usr/src/eBones Kerberos and DES

There is also a collection including all of the above, except for either (domestic or international) versions of the export-restricted software (i.e., src-secure and src-eBones collections): src-all: /usr/src the whole operating system (almost)

And for the ports collection: ports-base: /usr/ports/... misc files at the top of /usr/ports ports-archivers: /usr/ports/archivers archiving tools ports-astro: /usr/ports/astro astronomical ports ports-audio: /usr/ports/audio sound support ports-benchmarks: /usr/ports/benchmarks benchmarks ports-cad: /usr/ports/cad CAD tools ports-chinese: /usr/ports/chinese Chinese support ports-comms: /usr/ports/comms communication software ports-databases: /usr/ports/databases databases ports-devel: /usr/ports/devel development utilities ports-editors: /usr/ports/editors editors ports-emulators: /usr/ports/emulators emulators for other OSes ports-games: /usr/ports/games games ports-graphics: /usr/ports/graphics various graphics utilities ports-japanese: /usr/ports/japanese Japanese support ports-lang: /usr/ports/lang programming languages ports-mail: /usr/ports/mail mail software ports-math: /usr/ports/math numerical computation software ports-mbone: /usr/ports/mbone MBone applications ports-misc: /usr/ports/misc miscellaneous utilities ports-net: /usr/ports/net networking software ports-news: /usr/ports/news USENET news software ports-plan9: /usr/ports/plan9 various programs from Plan9 ports-print: /usr/ports/print printing software ports-russian: /usr/ports/russian Russian support ports-security: /usr/ports/security ``security'' utilities, for better or for worse ports-shells: /usr/ports/shells various UN*X shells ports-sysutils: /usr/ports/sysutils system utilities ports-vietnamese: /usr/ports/vietnamese Vietnamese support ports-www: /usr/ports/www software related to the world wide web ports-x11: /usr/ports/x11 X11 software

There is also a collection including all of the above: ports-all: /usr/ports the whole ports tree