diff --git a/en/commercial/commercial.sgml b/en/commercial/commercial.sgml index fcf6976970..5c440e9c5c 100644 --- a/en/commercial/commercial.sgml +++ b/en/commercial/commercial.sgml @@ -1,47 +1,47 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Please note that the inclusion of vendors in our list does not signify our endorsement of their products or services.

&footer; diff --git a/en/commercial/consulting.sgml b/en/commercial/consulting.sgml index 1022d74382..0ada5560d1 100644 --- a/en/commercial/consulting.sgml +++ b/en/commercial/consulting.sgml @@ -1,28 +1,28 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Consulting Services

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&consulting;

Commercial Vendors Home &footer; diff --git a/en/commercial/consulting_bycat.sgml b/en/commercial/consulting_bycat.sgml index d6dd7b5fdc..170871eaf6 100644 --- a/en/commercial/consulting_bycat.sgml +++ b/en/commercial/consulting_bycat.sgml @@ -1,28 +1,28 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Consulting Services

This file has been divided into sub-categories for your convenience. Please use the following shortcuts to assist you to the proper gallery entries.

&consultingbycat;

Commercial Vendors Home &footer; diff --git a/en/commercial/hardware.sgml b/en/commercial/hardware.sgml index 00868a461a..0a8eb9b672 100644 --- a/en/commercial/hardware.sgml +++ b/en/commercial/hardware.sgml @@ -1,28 +1,28 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Hardware Vendors

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&hardware;

Commercial Vendors Home &footer; diff --git a/en/commercial/misc.sgml b/en/commercial/misc.sgml index 9f91fc063c..2ca9aeb821 100644 --- a/en/commercial/misc.sgml +++ b/en/commercial/misc.sgml @@ -1,28 +1,28 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Miscellaneous Vendors

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&misc;

Commercial Vendors Home &footer; diff --git a/en/commercial/software.sgml b/en/commercial/software.sgml index d065b53665..d148d6beb9 100644 --- a/en/commercial/software.sgml +++ b/en/commercial/software.sgml @@ -1,28 +1,28 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Software Vendors

This file has been indexed by alphabetic order for easy navigating. Should you wish to find a specific entry, please use the shortcuts below for quick access.

&software;

Commercial Vendors Home &footer; diff --git a/en/commercial/software_bycat.sgml b/en/commercial/software_bycat.sgml index 96fc581db2..c0957714a8 100644 --- a/en/commercial/software_bycat.sgml +++ b/en/commercial/software_bycat.sgml @@ -1,28 +1,28 @@ - - + %includes; %vendorincludes; ]> &header; &vendorintroduction;

Software Vendors

This file has been divided into sub-categories for your convenience. Please use the following shortcuts to assist you to the proper gallery entries.

&softwarebycat;

Commercial Vendors Home &footer; diff --git a/en/docproj/current.sgml b/en/docproj/current.sgml index 092d2b1086..7062b1378c 100644 --- a/en/docproj/current.sgml +++ b/en/docproj/current.sgml @@ -1,190 +1,190 @@ - - + %includes; ]> &header;

Here are the projects currently under way (or being actively contemplated on the freebsd-doc mailing list). I have also included some that have not really been talked about, but would probably be a good idea. Each project lists the contact person for that project (if I know who it is).

If you think you can contribute to any of these, please do not hesitate to stand up and be counted. You should talk to the person responsible for that particular project, who can then bring you up to speed on what is happening.

Any omissions in this list are entirely my fault (Nik Clayton, <nik@FreeBSD.ORG>), sorry in advance to anyone whose project I have missed.

Open documentation problem reports

Current FreeBSD problems reports are tracked using the GNATS database. You can view the open documentation problem reports.

FreeBSD Handbook 2nd Edition

Responsible: Murray Stokely <murray@FreeBSD.org>

Synopsis: This project is complete. The 2nd Edition FreeBSD Handbook is available now from The FreeBSD Mall. The final manuscript is 653 pages, and the ISBN number is 1571763031. Thanks to everyone who contributed. Read the full announcement here.

The task list that we used during the development of this book is still archived here for posterity.

FreeBSD for Linux users

Responsible: Annelise Anderson < andrsn@andrsn.stanford.edu>

Synopsis: Linux users coming to FreeBSD can be confused by some of the differences between the systems (the different default shells, how boot time configuration is performed, and so on). Annelise is coordinating the development of a tutorial/FAQ section that will address these points.

The list of current questions is at http://andrsn.stanford.edu/FreeBSD/linux.html.

Write a section in the Handbook and/or FAQ

Responsible: No one

Synopsis: Chunks of the FAQ and Handbook have empty sections in them. They need filling. If you have just had to use one of these documents to complete a task, and found them lacking, please find the time to write up your experiences as a possible replacement.

Alternatively, if you have just had to do something that had no entry in the FAQ and/or Handbook, please consider writing a new section. Then submit it as outlined above.

Write some new Papers

The New SCSI layer for FreeBSD (CAM)

Responsible: <doc@FreeBSD.org>, <scsi@FreeBSD.org>

Synopsis: See The Design and Implementation of the FreeBSD SCSI Subsystem for a first snapshot.

Write some new Tutorials

Responsible: <doc@FreeBSD.org>

Synopsis:

Write Manpages for the kernel

Responsible: <doc@FreeBSD.org>

Synopsis: Document kernel functions, section 9

CGI Scripts

Responsible: <doc@FreeBSD.org>, Wolfram Schneider <wosch@FreeBSD.org>

Synopsis: Modify the CGI scripts url.cgi, ports.cgi, pds.cgi and the script portindex to use the Perl FreeBSD::Ports modules. These modules also need thorough testing.

Multilingual Web scripts

Responsible: <doc@FreeBSD.org>

Synopsis:

Our main Web pages are written in (American) English. The FreeBSD Translations Projects translate the web pages, Handbook and FAQ to other languages.

We must translate the cgi scripts and web build scripts too. The scripts should support multiple languages, not only one. Most scripts are written in perl.

Translations of the FreeBSD Documentation

Responsible: <doc@FreeBSD.org>

Translate the FreeBSD documentation (Web pages, FAQ, handbook, manpages) into other languages. See the FreeBSD translations projects

Search engine enhancements

Responsible: <doc@FreeBSD.org>

When searching the website, the output from the search engine includes the filename that was found, which might be something like FAQ34.html.

It would be more useful if the results included the question text, allowing the user to see whether or not the result was relevant.

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/doc-set.sgml b/en/docproj/doc-set.sgml index d93bd33e57..752ee55522 100644 --- a/en/docproj/doc-set.sgml +++ b/en/docproj/doc-set.sgml @@ -1,44 +1,44 @@ - - + %includes; ]> &header;

FreeBSD's documentation falls into three basic categories;

  1. The manual pages

    The Project does not really concern itself with these, since they are a part of the base system. The exception to this is the Japanese team, who are translating them. There is no reason other volunteers could not step in to translate the manual pages to other languages as well.

    That is not to say that the manual pages are unimportant, far from it. It is just that they are intimately tied to specific systems of FreeBSD, and most of the time the best person to write the manual page is the person that wrote that part of FreeBSD.

  2. The Books

    The project has a large amount of documentation that is "book length", or becoming that way. These include the FreeBSD FAQ and the FreeBSD Handbook.

  3. The Articles

    FreeBSD has a wealth of information available in shorter, article form -- similar to the tutorials or HOWTO documentation of other projects.

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/sgml.sgml b/en/docproj/sgml.sgml index 2af064b0dd..e313bba68b 100644 --- a/en/docproj/sgml.sgml +++ b/en/docproj/sgml.sgml @@ -1,166 +1,166 @@ - - + %includes; ]> &header;

The Documentation Project is trying to use SGML as the standard method of representing the documentation.

SGML is the Standard Generalised Markup Language.

In a nutshell (and apologies to any SGML purists in the audience that are offended) SGML is a language for writing other languages.

You have probably already used SGML, but you did not know it. HTML, the language that web pages are written in, has a formal description. That description is written in SGML. When you are writing HTML you are not writing SGML (per se), but you are using a language that is defined using SGML.

There are many, many markup languages that are defined using SGML. HTML is one of them. Another is called "LinuxDoc". As you can probably guess, it was originally created by the Linux documentation group to write their documentation, and the FreeBSD Documentation Project adopted it as well.

Another markup language defined using SGML is called "DocBook". This is a language designed specifically for writing technical documentation, and as such it has many tags (the things inside the <...>) to describe technical documentation related things.

For example, this is how you might write a brief paragraph in HTML (do not worry about the content, just look at the tags):

The system's passwords are stored in /etc/passwd. To edit
       this file you should use vipw. However, if you just
       want to add a new user you can use adduser.

 ]]>

The same paragraph, marked up using DocBook, looks like

The system's passwords are stored in
       /etc/passwd. To edit this file you should use
       vipw. However, if you just want to add a new user
       you can use adduser.
 ]]>

As you can see, DocBook is much more 'expressive' than HTML. In the HTML example the filename is marked up as being displayed in a 'typewriter' font. In the DocBook example the filename is marked up as being a 'filename', the presentation of the filename is not described.

There are a number of advantages to this more expressive form of markup:

If you are familiar with them, this is a bit like Microsoft Word stylesheets, only vastly more powerful.

Of course, with this power comes a price;

Right now, the Project is still using LinuxDoc for the Handbook and the FAQ. That's changing, and in particular there's a project underway to convert the documentation to DocBook.

What if you don't know LinuxDoc/DocBook? Can you still contribute?

Yes you can. Quite definitely. Any documentation is better than no documentation. If you've got some documentation to contribute and it's not marked up in LinuxDoc or DocBook, don't worry.

Submit the documentation as normal. Someone else on the Project will grab your committed documentation, mark it up for you, and commit it. With a bit of luck they'll then send you the marked up text back. This is handy because you can do a "before and after" shot of the plain documentation and the marked up stuff, and hopefully learn a bit more about the markup in the process.

Obviously, this slows down the committing process, since your submitted documentation needs to be marked up, which may take an evening or too. But it will get committed.

More information about SGML and DocBook?

You should first read the Documentation Project Primer. This aims to be a comprehensive explanation of everything you need to know in order to work with the FreeBSD documentation.

This is a long document, split in to many smaller files. You can also view it as one large file.

http://www.oasis-open.org/cover/sgml-xml.html

The SGML/XML web page. Includes countless pointers to more information about SGML.

http://www-tei.uic.edu/orgs/tei/sgml/teip3sg/index.html

The "Gentle Introduction to SGML". Recommended reading for anyone who wants to learn more about SGML from a beginners perspective.

http://www.oasis-open.org/docbook/

The DocBook DTD is maintained by OASIS. These pages are aimed users who are already comfortable with SGML, and who want to learn DocBook.

FreeBSD Documentation Project Home &footer; diff --git a/en/docproj/submitting.sgml b/en/docproj/submitting.sgml index 9a07e128df..f6f555c519 100644 --- a/en/docproj/submitting.sgml +++ b/en/docproj/submitting.sgml @@ -1,134 +1,134 @@ - - + %includes; ]> &header;

I have written some documentation. How do I submit it?

First, thank you for taking the time to do this.

You should make your documentation available for review. If you can, put it on an FTP site or a website.

Then post a message to the -doc mailing list, with a brief outline of the documentation and the pointer to its location, and solicit feedback.

If, for some reason, you can not put the documentation up for FTP or on a web site somewhere you can send it directly to the -doc mailing list. If you do this, please only send plain text documents.

You should probably cc: this request for comments to other appropriate mailing lists. For example, something that relates to how to use CVSup to keep your source tree up to date would be of interest to the subscribers of the FreeBSD-current and FreeBSD-stable mailing lists.

After people have looked over your documentation, and you have had the chance to incorporate any of their suggestions, you are ready to submit it.

To do this, wrap it up into a tar file. If your documentation consists of three files, 

     % tar cf doc.tar one two three

which does just that. Then compress the tar file,

     % gzip -9 doc.tar

which will produce doc.tar.gz.

Finally, encode the file so that it will not be mangled by any e-mail programs.

     % uuencode doc.tar.gz doc.tar.gz > doc.uue

You should then let the Documentation Project know about it. The correct way to do this is to use a command called send-pr, which should be installed on your machine.

You do this so that your submission can be tracked. When you submit a PR (Problem Report) it is assigned a unique number. One of the committers can then assign the PR to themselves, and liase with you on committing the new documentation.

send-pr itself is pretty simple. All it does is send an e-mail with some special formatting to a particular address. When you run send-pr you will be put into your editor (probably vi or emacs) with a template to fill out, and some instructions on how to fill it out.

Make sure the "Category" is set to "docs" and that the "Class" is set to one of "change-request". You should include the .uue file you created earlier in to the PR.

When you come out of the editor the PR will be sent as an e-mail to the right place. You will get a notification message shortly afterwards telling you what number your PR has been given, and this number can be used to track its progress.

Alternatively, you can use the web interface at http://www.FreeBSD.org/send-pr.html.

I have made some changes to existing documentation, how do I submit them?

Again, thank you for taking the time to do this.

First off, you need to produce a special file, called a diff. This diff shows just the changes that you have made. This makes it easier for the person doing the committing to see what you have changed, and means you do not need to spend lots of time explaining what you have changed (although you should still explain why you think the change should be made).

To make a 'diff', you should;

  1. Make a copy of the file you are going to change. If you are changing 

         % cp foo.sgml foo.sgml.old

  2. Then, make your changes to foo.sgml

         % vi foo.sgml
     ... tap tap tap ...
 
     ... test the changes, read them for typos and so on ...

  3. Make the diff. The command to do this is

         % diff -c foo.sgml.old foo.sgml > foo.diff

    This looks at the difference between the two files, and writes them to the file

You can then send

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/translations.sgml b/en/docproj/translations.sgml index 0cfad6243b..721a652103 100644 --- a/en/docproj/translations.sgml +++ b/en/docproj/translations.sgml @@ -1,182 +1,182 @@ - - + %includes; ]> &header;

The FreeBSD Brazilian Portuguese Documentation Project

E-Mail: lioux@FreeBSD.org
Documents currently being worked on
Handbook

The FreeBSD Chinese Documentation Project

Web: -
E-Mail: foxfair@FreeBSD.org
Mailing list available
Send a mail to majordomo@freebsd.sinica.edu.tw with the words "subscribe freebsd-chinese-doc" in the body of the message.
Posting is allowed for the members at freebsd-chinese-doc@freebsd.sinica.edu.tw
Documents available
FAQ
Documents currently being worked on
Handbook

The FreeBSD Dutch Documentation Project

E-Mail: asmodai@FreeBSD.org
Documents currently being worked on
Handbook

The FreeBSD Estonian Documentation Project

Web: http://www.bsd.ee/tolge.php
Documents available
FreeBSD handbook

The FreeBSD French Documentation Project

Web: http://www.freebsd-fr.org
Mailing lists available
Send a mail to listserver@freebsd-fr.org with the words "SUB freebsd-questions" in the body of the message for subscribing to the questions mailing list in French.
Send a mail to listserver@freebsd-fr.org with the words "SUB annonces" in the body of the message for subscribing to the announce mailing list in French.
Documents available
FAQ
Some tutorials
Really Quick Newsletters
PicoBSD
Documents currently being worked on
Handbook
CVS repository
CVS web
Send a mail to listserver@freebsd-fr.org with the words "SUB cvs" in the body of the message for subscribing to the French CVS update mailing list in French.

The FreeBSD German Documentation Project

Web: http://www.de.FreeBSD.org/de/uebersetzung.html
E-Mail: de-bsd-translators@de.FreeBSD.org
Documents currently being worked on
Handbook, FAQ, Web

The FreeBSD Italian Documentation Project

Web: http://www.gufi.org/
E-Mail: info@gufi.org
Documents currently being worked on
Handbook

The FreeBSD Japanese Documentation Project

Web: http://www.jp.FreeBSD.org/doc-jp/
E-Mail: doc-jp@jp.FreeBSD.org
Documents available
Handbook, FAQ, Web, FreeBSD NewsLetter Issue #2
Documents currently being worked on
FreeBSD Tutorials

The FreeBSD Korean Documentation Project

Web: http://www.kr.FreeBSD.org/projects/doc-kr/
E-Mail: doc@kr.FreeBSD.org
Documents currently being worked on
Handbook

The FreeBSD Russian Documentation Project

Web: http://www.FreeBSD.org.ua
E-Mail: ru-freebsd-doc@FreeBSD.ru
Documents available
FAQ
WWW
Q&A
Porter's handbook
Documents currently being worked on
Handbook

The FreeBSD Spanish Documentation Project

Web: http://www.es.FreeBSD.org/es/
E-Mail: jesusr@es.FreeBSD.org
Documents available
FAQ
Documents currently being worked on
Handbook

FreeBSD Documentation Project Home &footer diff --git a/en/docproj/who.sgml b/en/docproj/who.sgml index e7cd6ee901..0d9cde8509 100644 --- a/en/docproj/who.sgml +++ b/en/docproj/who.sgml @@ -1,38 +1,38 @@ - - + %includes; ]> &header;

The project is a fairly loosely knit group of people, and the only thing we have got in common is that we are subscribed to the mailing list FreeBSD-doc@FreeBSD.ORG.

Some of us can commit changes directly to the FreeBSD documentation tree. You can view a complete list of all FreeBSD developers with commit privileges, as well as a list of the principal committers for the FreeBSD Documentation Project.

Others do not have commit privileges, but they write and submit documentation nonetheless. Once the documentation has been submitted according to the Submit Documentation page, one of the committers will then review it and include it in the documentation set.

If you want to help out with the documentation project (and I fervently hope you do) all you have to do is subscribe to the mailing list and participate. As soon as you have done that, you're a member of the project.

FreeBSD Documentation Project Home

&footer; diff --git a/en/internal/about.sgml b/en/internal/about.sgml index bd4acb6e68..3e0f39b581 100644 --- a/en/internal/about.sgml +++ b/en/internal/about.sgml @@ -1,90 +1,90 @@ - - + %includes; ]> &header;

The Machine

The machine www.FreeBSD.org, otherwise known as freefall.FreeBSD.org, is 800MHz Pentium III set up with 1024 megabytes of RAM and about 50 gigabytes of disk space. The mail duties for the domain are handled by hub.FreeBSD.org, a 400 MHz Pentium II with 256 megabytes RAM and about 16 gigabytes disk space.

Naturally, these systems all run FreeBSD. The hardware and network connection have been generously provided by BSDi, Yahoo!, and other contributors to the FreeBSD project.

A complete list of all host names in the FreeBSD.org domain is available at the The FreeBSD.org Network page.

The Software

These pages are served up by the versatile and efficient Apache http server. In addition, there are a few locally crafted CGI scripts. Indexing of these pages and the mailing list archive are provided by freewais-sf, a derivative of the CNIDR freewais.

The Urchin web statistics package is used to provide these statistics on web server usage.

The Pages

These Web pages have been put together by John Fieber <jfieber@FreeBSD.org> with input from the FreeBSD community and you. The Webmaster is <wosch@FreeBSD.org>. The FreeBSD pages are HTML 3.2 compliant and best viewed with your browser.

See also the FreeBSD Documentation Project

Page Design

Original page design by Megan McCormack

Building and updating the FreeBSD Web Pages

&webbuild;

Update of the FreeBSD Web Pages

The FreeBSD Web Pages are updated daily at 0800 and 2000 UTC.

Mirroring the FreeBSD Web Pages

You can (and are encouraged to) mirror the FreeBSD web pages on www.FreeBSD.org.

Usage statistics for this server are updated daily.

FreeBSD Internal Home &footer; diff --git a/en/internal/bylaws.sgml b/en/internal/bylaws.sgml index 2f582b9622..d7e800baf5 100644 --- a/en/internal/bylaws.sgml +++ b/en/internal/bylaws.sgml @@ -1,62 +1,62 @@ - - + %includes; ]> &header;

These bylaws were approved by a vote of active committers on August 28, 2000.

  • Active committers have made a commit to the tree in the last 12 months.
  • Core consists of 9 elected active committers.
  • Core elections are held every 2 years, first time September 2000.
  • Core members and committers may be ejected by a 2/3 vote of core.
  • If the size of core falls below 7, an early election is held.
  • A petition of 1/3 of active committers can trigger an early election.
  • All elections will be run as follows:
    • Core appoints and announces someone to run the election.
    • 1 week to tally active committers wishing to run for core.
    • 4 weeks for the actual vote
    • 1 week to tally and post the results.
    • Each active committer may vote once in support of up to nine nominees.
    • New core team becomes effective 1 week after the results are posted.
    • Voting ties decided by unambiguously elected new core members.
  • These rules can be changed by a 2/3 majority of committers if at least 50% of active committers cast their vote.

The last core election was held in September of 2000. The next core election will be held in September of 2002.

Resources for FreeBSD Committers Home &footer; diff --git a/en/internal/developer.sgml b/en/internal/developer.sgml index 0a5447269d..ee80a0ca2e 100644 --- a/en/internal/developer.sgml +++ b/en/internal/developer.sgml @@ -1,62 +1,62 @@ - - + %includes; ]> &header;

Committers Guide

Almost everything a new committer to the FreeBSD Project needs to know (see the Ports Guide and FDP Primer for more info).

New Account Creation Procedure

Core Bylaws

Build the FreeBSD Web Pages

&webbuild;

FreeBSD Documentation Project Primer for New Contributors

This primer covers everything you will need to know in order to start contributing to the FreeBSD Documentation Project, from the tools and software you will be using (both mandatory and recommended) to the philosophy behind the Documentation Project.

FreeBSD Porter's Handbook

A Guide for FreeBSD Ports Committers

FreeBSD Projects

Other Resources

FreeBSD Internal Home &footer; diff --git a/en/internal/internal.sgml b/en/internal/internal.sgml index 904f18d12f..a20bf973fe 100644 --- a/en/internal/internal.sgml +++ b/en/internal/internal.sgml @@ -1,66 +1,66 @@ - - + %includes; ]> &header;

The FreeBSD.org Network

This page documents, for those with accounts on the FreeBSD.org network, just what machine resources are currently available and the sorts of jobs they are being provided for.

Resources for FreeBSD Committers

This page documents resources for FreeBSD committers.

About the FreeBSD WWW Server

The Machine, the software, mirroring the FreeBSD Web Pages, Usage statistics.

FreeBSD Project Staff

The FreeBSD Project is managed and operated by the following groups of people: FreeBSD Core Team, FreeBSD Developers; who is responsible for what.

Photos from Social Events

Personal Homepages

A list of private home pages hosted on people.FreeBSD.org.

FreeBSD Projects

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.

FreeBSD Release Engineering Process

This page documents the release engineering process for official FreeBSD releases.

FreeBSD 4.5 Release Schedule

A schedule for the official release of FreeBSD 4.5.

Contacting FreeBSD

FreeBSD Copyright

The FreeBSD Copyrights.

Search the FreeBSD Site

FreeBSD Search Services.

FreeBSD Statistics

Web statistic, FTP traffic, Release usage.

&footer; diff --git a/en/internal/mirror.sgml b/en/internal/mirror.sgml index 0f6c3e5716..b0f89c8c6f 100644 --- a/en/internal/mirror.sgml +++ b/en/internal/mirror.sgml @@ -1,61 +1,61 @@ - - + %includes; ]> &header;

You can (and are encouraged to) mirror the FreeBSD web pages www.FreeBSD.org. To do this, you need to obtain and install a program called cvsup on your web server. CVSup is a software package for distributing and updating collections of files across a network.

Installing CVSup

To build and install it, do the following:

  # cd /usr/ports/net/cvsup-bin
  # make all install clean

Running CVSup

If you keep your mirrored FreeBSD web pages in the directory /usr/FreeBSD-mirror and are owned by the user `fred', then run the following command as user `fred':

      $ cvsup supfile-www
The file supfile-www contain: 
        *default host=cvsup.FreeBSD.org
        *default prefix=/usr/FreeBSD-mirror
        *default base=/usr/local/etc/cvsup
        www release=current delete use-rel-suffix compress

This will mirror the FreeBSD web pages into /usr/FreeBSD-mirror. You can install this into fred's crontab, so that it runs once a day. The pages on www.FreeBSD.org are updated daily at about 4:30am California time.

More Information on CVSup

See the CVSup introduction in the handbook.

FreeBSD Internal Home &footer; diff --git a/en/internal/new-account.sgml b/en/internal/new-account.sgml index 2c7333e760..6e946af111 100644 --- a/en/internal/new-account.sgml +++ b/en/internal/new-account.sgml @@ -1,60 +1,60 @@ - - + %includes; ]> &header;

Authorizing A New Account

Someone from the list below sends a PGP-signed email to admins@FreeBSD.org, the person assigned as the mentor to the new committer, and copied to core@FreeBSD.org confirming the approval of the new account. This email should include a link to this document so the mentor/mentee know what is expected of them.

New account approvals are only valid from these PGP entities:

  • core-secretary

  • portmgr

  • nik

NOTE: New account requests from anyone other than these entities or requests signed with PGP keys other than from these entities will not be acted upon. No exceptions.

Information Needed From New Committer

The person assigned as the new committers' mentor needs to collect and send the following information to admins@FreeBSD.org:

  • master.passwd line containing preferred username, shell, and GECOS info (no password is needed)

  • ssh V2 public key (version 2 ONLY)

  • PGP key for new committer (used for account recovery or other needs that require positive identification of the committer)

admins@FreeBSD.org Creates New Account

admins@FreeBSD.org creates the new account with the above information on the FreeBSD.org cluster and notifies the mentor and the new committer.

Mentor Activates New Committer's Commit Bit

After the new committer confirms that his account works, the mentor activates the new committer's commit bit and guides them through the rest of the initial process.

&footer; diff --git a/en/internal/photos.sgml b/en/internal/photos.sgml index 0104a9fe03..245c9348c7 100644 --- a/en/internal/photos.sgml +++ b/en/internal/photos.sgml @@ -1,88 +1,88 @@ - - + %includes; ]> &header;

BSDCon Europe 2001, Brighton, Nov 2001

Pictures

BSDCon 2000, Monterey, October 2000

Photos by Will

LinuxWorld 2000, February 2000

Photos by jkh.

BSD Social Event Berlin, October 1999

Oxford (UK) FreeBSD meeting, November 1998

Photos and text by Nik. Organised by Paul Richards.

Dutch FreeBSD meeting, October 1998

Photos by Jordan and Wilko

BSD Social Event Hamburg, June 1998

Aled Morris, Andre Oppermann, Andreas Klemm, Andrew Gordon, Christoph Badura, Dirk Meyer, Frank Nobis, Harald Klatte, Joerg Wunsch, Jonathan Laventhol, Lars Gerhard Kuehl, Martin Cracauer, Stefan Bethke, Stefan Esser, Stefan Huerter, Stefan Zehl, Stephan Forth, Thomas Gellekum

AUUG Spring conference, Sydney, September 1998

Richard Stallman, Peter Wemm, Mark White, Andrew McRae, Greg Rose, many unidentified.

Summer 1998 USENIX, New Orleans

Branson, David Greenman, David O'Brien, Greg Lehey, Guido van Rooij, John Polstra, Jonathan Bresler, Jordan Hubbard, Justin Gibbs, Luigi Rizzo, Mark Murray, Mike Smith, Monique van Rooij, Ollivier Robert, Philippe Regnauld, Poul-Henning Kamp, Sharon, Steve Mann

FreeBSD Social Event Aachen, 1995

Aled Morris, Christoph Kukulies, Guido van Rooij, Jonathan Leventhol, Jörg Wunsch, Martin Welk, Michael Reifenberger, Patrick Hausen, Paul Richard, Paul Richards, Poul-Henning Kamp, René de Vries, Stefan Esser, Ulf Kieber, Wilko Bulte

FreeBSD People

Aled Morris, Andrey Chernov, Christoph Kukulies, Gary Jennejohn, Gary Palmer, Guido Van Rooij, Guy Helmer, Hellmuth Michaelis, James Robinson, Joerg Wunsch, John Fieber, Jon Loeliger, Jonathan Leventhol, Jordan Hubbard, Julian Stacey, Mark Murray, Martin Welk, Michael Reifenberger, Mike Smith, Ollivier Robert, Patrick Hausen, Paul Richards, Paul Traina, Poul-Henning Kamp, Rene de Vries, Stefan Esser, Thomas Gellekum, Timo Rinne, Ulf Kieber, Wilko Bulte, Wolfram Schneider

FreeBSD Internal Home &footer; diff --git a/en/internal/releng.sgml b/en/internal/releng.sgml index dec6d2ad36..86c68cdf2b 100644 --- a/en/internal/releng.sgml +++ b/en/internal/releng.sgml @@ -1,25 +1,25 @@ - - + %includes; ]> &header;

Moved!

This document has moved.

The FreeBSD Release Engineering document has been expanded and is now available as part of the FreeBSD Documentation set. You will find it here.

&footer; diff --git a/en/internal/releng45.sgml b/en/internal/releng45.sgml index 263ef55241..7584fbc561 100644 --- a/en/internal/releng45.sgml +++ b/en/internal/releng45.sgml @@ -1,25 +1,25 @@ - - + %includes; ]> &header;

Moved!

This document has moved.

The FreeBSD 4.5 Release Engineering schedule is available here.

The FreeBSD 4.6 Release Engineering schedule (in progress) is available here.

&footer; diff --git a/en/internal/statistic.sgml b/en/internal/statistic.sgml index 07cc617d45..2e6a0fd62c 100644 --- a/en/internal/statistic.sgml +++ b/en/internal/statistic.sgml @@ -1,66 +1,66 @@ - - + %includes; ]> &header;

Web Statistic

Analog

The Web usage statistics for this server are updated daily with the analog(1) tool.

Urchin

Urchin Logo

The Urchin web statistics package is used to provide these statistics on web server usage.

FreeBSD Release Usage Statistic

A snapshot of the current FreeBSD release usage is available at http://www.FreeBSD.org/statistic/release_usage/images/.

The FreeBSD Counter Page

The FreeBSD Counter Page page is the start of a project which will attempt to determine the world-wide installed base of FreeBSD users. The FreeBSD development community currently has only the vaguest idea as to how large our user base is, and this makes it all the more difficult to persuade hardware and software vendors to take it seriously.

FTP traffic at ftp.FreeBSD.org

We set a new traffic record for TerraSolutions and Lightning Internet Services at 29-Sep-2000, over 2TB.
Previous record was set for wcarchive at 23-May-1999, 1.39TB.

FreeBSD Internal Home &footer;