diff --git a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
index df4987a13a..85e2115cbb 100644
--- a/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml
@@ -1,2064 +1,2064 @@
Resources on the InternetThe rapid pace of FreeBSD progress makes print media impractical as a
means of following the latest developments. Electronic resources are the
best, if not often the only, way stay informed of the latest advances.
Since FreeBSD is a volunteer effort, the user community itself also
generally serves as a technical support department of sorts,
with electronic mail and USENET news being the most effective way of
reaching that community.The most important points of contact with the FreeBSD user community
are outlined below. If you are aware of other resources not mentioned
here, please send them to the &a.doc; so that they may also be
included.Mailing ListsThough many of the FreeBSD development members read USENET, we
cannot always guarantee that we will get to your questions in a timely
fashion (or at all) if you post them only to one of the
comp.unix.bsd.freebsd.* groups. By addressing your
questions to the appropriate mailing list you will reach both us and a
concentrated FreeBSD audience, invariably assuring a better (or at least
faster) response.The charters for the various lists are given at the bottom of this
document. Please read the charter before joining or sending
mail to any list. Most of our list subscribers now receive
many hundreds of FreeBSD related messages every day, and by setting down
charters and rules for proper use we are striving to keep the
signal-to-noise ratio of the lists high. To do less would see the
mailing lists ultimately fail as an effective communications medium for
the project.Archives are kept for all of the mailing lists and can be searched
using the FreeBSD World
Wide Web server. The keyword searchable archive offers an
excellent way of finding answers to frequently asked questions and
should be consulted before posting a question.List SummaryGeneral lists: The following are general
lists which anyone is free (and encouraged) to join:ListPurposecvs-allChanges made to the FreeBSD source treefreebsd-advocacyFreeBSD Evangelismfreebsd-announceImportant events and project milestonesfreebsd-archArchitecture and design discussionsfreebsd-bugbustersDiscussions pertaining to the maintenance of the FreeBSD
problem report database and related toolsfreebsd-bugsBug reportsfreebsd-chatNon-technical items related to the FreeBSD
communityfreebsd-configDevelopment of FreeBSD installation and configuration toolsfreebsd-currentDiscussion concerning the use of
&os.current;freebsd-ispIssues for Internet Service Providers using
FreeBSDfreebsd-jobsFreeBSD employment and consulting
opportunitiesfreebsd-newbiesNew FreeBSD users activities and discussionsfreebsd-policyFreeBSD Core team policy decisions. Low volume, and
read-onlyfreebsd-questionsUser questions and technical supportfreebsd-security-notificationsSecurity notificationsfreebsd-stableDiscussion concerning the use of
&os.stable;freebsd-testWhere to send your test messages instead of one of
the actual listsTechnical lists: The following lists are for
technical discussion. You should read the charter for each list
carefully before joining or sending mail to one as there are firm
guidelines for their use and content.ListPurposefreebsd-afsPorting AFS to FreeBSDfreebsd-aic7xxxDeveloping drivers for the Adaptec AIC 7xxxfreebsd-alphaPorting FreeBSD to the Alphafreebsd-armPorting FreeBSD to ARM processorsfreebsd-atmUsing ATM networking with FreeBSDfreebsd-auditSource code audit projectfreebsd-binupDesign and development of the binary update systemfreebsd-clusterUsing FreeBSD in a clustered environmentfreebsd-cvsweb
- CVSWeb maintenance
+ CVSweb maintenancefreebsd-databaseDiscussing database use and development under
FreeBSDfreebsd-docCreating FreeBSD related documentsfreebsd-emulationEmulation of other systems such as
Linux/DOS/Windowsfreebsd-firewireFreeBSD Firewire (iLink, IEEE 1394) technical
discussionfreebsd-fsFile systemsfreebsd-gnomePorting GNOME and GNOME applicationsfreebsd-hackersGeneral technical discussionfreebsd-hardwareGeneral discussion of hardware for running
FreeBSDfreebsd-i18nFreeBSD Internationalizationfreebsd-ia32FreeBSD on the IA-32 (Intel x86) platformfreebsd-ia64Porting FreeBSD to Intel's upcoming IA64 systemsfreebsd-ipfwTechnical discussion concerning the redesign of the IP
firewall codefreebsd-isdnISDN developersfreebsd-javaJava developers and people porting JDKs to
FreeBSDfreebsd-lfsPorting LFS to FreeBSDfreebsd-libhThe second generation installation and package
systemfreebsd-mipsPorting FreeBSD to MIPSfreebsd-mobileDiscussions about mobile computingfreebsd-mozillaPorting Mozilla to FreeBSDfreebsd-multimediaMultimedia applicationsfreebsd-new-busTechnical discussions about bus architecturefreebsd-netNetworking discussion and TCP/IP source codefreebsd-openofficePorting OpenOffice.org and
StarOffice to FreeBSDfreebsd-performancePerformance tuning questions for high
performance/load installationsfreebsd-platformsConcerning ports to non-Intel architecture
platformsfreebsd-portsDiscussion of the ports collectionfreebsd-ppcPorting FreeBSD to the PowerPCfreebsd-qaDiscussion of Quality Assurance, usually pending a releasefreebsd-realtimeDevelopment of realtime extensions to FreeBSDfreebsd-scsiThe SCSI subsystemfreebsd-securitySecurity issues affecting FreeBSDfreebsd-smallUsing FreeBSD in embedded applicationsfreebsd-smpDesign discussions for [A]Symmetric
MultiProcessingfreebsd-sparcPorting FreeBSD to SPARC based systemsfreebsd-standardsFreeBSD's conformance to the C99 and the POSIX
standardsfreebsd-threadsThreading in FreeBSDfreebsd-testingFreeBSD Performance and Stability Testsfreebsd-tokenringSupport Token Ring in FreeBSDLimited lists: The following lists are for
more specialized (and demanding) audiences and are probably not of
interest to the general public. It is also a good idea to establish a
presence in the technical lists before joining one of these limited
lists so that you will understand the communications etiquette involved.ListPurposefreebsd-coreFreeBSD core teamfreebsd-hubsPeople running mirror sites (infrastructural
support)freebsd-installInstallation developmentfreebsd-user-groupsUser group coordinationfreebsd-vendorsVendors pre-release coordinationfreebsd-wwwMaintainers of www.FreeBSD.orgDigest lists: Many of the above lists are
also available as digests. New messages posted to the list are
collected and sent out as a single email when over 100 KB of
messages have been received. The lists available in digest form are:Listcvs-all-digestfreebsd-afs-digestfreebsd-alpha-digestfreebsd-arm-digestfreebsd-chat-digestfreebsd-current-digestfreebsd-database-digestfreebsd-hackers-digestfreebsd-ia32-digestfreebsd-ia64-digestfreebsd-isdn-digestfreebsd-java-digestfreebsd-questions-digestfreebsd-security-digestfreebsd-sparc-digestfreebsd-stable-digestfreebsd-test-digestCVS lists: The following lists are for people
interested in seeing the log messages for changes to various areas of
the source tree. They are Read-Only lists and
should not have mail sent to them.ListSource areaArea Description (source for)cvs-all/usr/srcAll changes to the tree (superset)How to SubscribeTo subscribe to a list, send mail to &a.majordomo; and include
subscribe <listname> [<optional address>]
in the body of your message. For example, to subscribe yourself to
freebsd-announce, you would do:&prompt.user; mail majordomo@FreeBSD.org
subscribe freebsd-announce
^DTo actually post to a given list you simply send mail to
<listname@FreeBSD.org>. It will then
be redistributed to mailing list members world-wide.
Please note that subscription requests go to
&a.majordomo;, not the lists themselves.If you want to subscribe yourself under a different name, or
submit a subscription request for a local mailing list (this is more
efficient if you have several interested parties at one site, and
highly appreciated by us!), you would do something like:&prompt.user; mail majordomo@FreeBSD.org
subscribe freebsd-announce local-announce@example.com
^DFinally, it is also possible to unsubscribe yourself from a list,
get a list of other list members or see the list of mailing lists
again by sending other types of control messages to majordomo. For a
complete list of available commands, do this:&prompt.user; mail majordomo@FreeBSD.org
help
^DAgain, we would like to request that you keep discussion in the
technical mailing lists on a technical track. If you are only
interested in important announcements then it is suggested that
you join freebsd-announce, which is intended only for infrequent
traffic.List ChartersAll FreeBSD mailing lists have certain basic
rules which must be adhered to by anyone using them. Failure to comply
with these guidelines will result in two (2) written warnings from the
FreeBSD Postmaster postmaster@FreeBSD.org, after which,
on a third offense, the poster will removed from all FreeBSD mailing
lists and filtered from further posting to them. We regret that such
rules and measures are necessary at all, but today's Internet is a
pretty harsh environment, it would seem, and many fail to appreciate
just how fragile some of its mechanisms are.Rules of the road:The topic of any posting should adhere to the basic charter of
the list it is posted to, e.g. if the list is about technical
issues then your posting should contain technical discussion.
Ongoing irrelevant chatter or flaming only detracts from the value
of the mailing list for everyone on it and will not be tolerated.
For free-form discussion on no particular topic, the &a.chat;
is freely available and should be used instead.No posting should be made to more than 2 mailing lists, and
only to 2 when a clear and obvious need to post to both lists
exists. For most lists, there is already a great deal of
subscriber overlap and except for the most esoteric mixes (say
-stable & -scsi), there really is no reason to post to more
than one list at a time. If a message is sent to you in such a
way that multiple mailing lists appear on the
Cc line then the Cc
line should also be trimmed before sending it out again.
You are still responsible for your
own cross-postings, no matter who the originator might have
been.Personal attacks and profanity (in the context of an argument)
are not allowed, and that includes users and developers alike.
Gross breaches of netiquette, like excerpting or reposting private
mail when permission to do so was not and would not be
forthcoming, are frowned upon but not specifically enforced.
However, there are also very few cases where
such content would fit within the charter of a list and it would
therefore probably rate a warning (or ban) on that basis
alone.Advertising of non-FreeBSD related products or services is
strictly prohibited and will result in an immediate ban if it is
clear that the offender is advertising by spam.Individual list charters:FREEBSD-AFSAndrew File SystemThis list is for discussion on porting and using AFS from
CMU/TransarcFREEBSD-ANNOUNCEImportant events / milestonesThis is the mailing list for people interested only in
occasional announcements of significant FreeBSD events. This
includes announcements about snapshots and other releases. It
contains announcements of new FreeBSD capabilities. It may
contain calls for volunteers etc. This is a low volume, strictly
moderated mailing list.FREEBSD-ARCHArchitecture and design
discussionsThis list is for discussion of the FreeBSD
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:How to re-vamp the build system to have several
customized builds running at the same time.What needs to be fixed with VFS to make Heidemann layers
work.How do we change the device driver interface to be able
to use the same drivers cleanly on many buses and
architectures.How to write a network driver.FREEBSD-AUDITSource code audit projectThis is the mailing list for the FreeBSD source code
audit project. Although this was originally intended for
security-related changes, its charter has been expanded to
review any code changes.This list is very heavy on patches, and is probably of no
interest to the average FreeBSD user. Security discussions
not related to a particular code change are held on
freebsd-security. Conversely, all developers are encouraged
to send their patches here for review, especially if they
touch a part of the system where a bug may adversely affect
the integrity of the system.FREEBSD-BINUPFreeBSD Binary Update ProjectThis list exists to provide discussion for the binary
update system, or binup.
Design issues, implementation details,
patches, bug reports, status reports, feature requests, commit
logs, and all other things related to
binup are fair game.FREEBSD-BUGBUSTERSCoordination of the Problem Report handling effortThe purpose of this list is to serve as a coordination and
discussion forum for the Bugmeister, his Bugbusters, and any other
parties who have a genuine interest in the PR database. This list
is not for discussions about specific bugs, patches or PRs.FREEBSD-BUGSBug reportsThis is the mailing list for reporting bugs in FreeBSD.
Whenever possible, bugs should be submitted using the
&man.send-pr.1;
command or the WEB
interface to it.FREEBSD-CHATNon technical items related to the FreeBSD
communityThis list contains the overflow from the other lists about
non-technical, social information. It includes discussion about
whether Jordan looks like a toon ferret or not, whether or not
to type in capitals, who is drinking too much coffee, where the
best beer is brewed, who is brewing beer in their basement, and
so on. Occasional announcements of important events (such as
upcoming parties, weddings, births, new jobs, etc) can be made
to the technical lists, but the follow ups should be directed to
this -chat list.FREEBSD-COREFreeBSD core teamThis is an internal mailing list for use by the core
members. Messages can be sent to it when a serious
FreeBSD-related matter requires arbitration or high-level
scrutiny.FREEBSD-CURRENTDiscussions about the use of
&os.current;This is the mailing list for users of &os.current;. It
includes warnings about new features coming out in -CURRENT that
will affect the users, and instructions on steps that must be
taken to remain -CURRENT. Anyone running CURRENT
must subscribe to this list. This is a technical mailing list
for which strictly technical content is expected.FREEBSD-CURRENT-DIGESTDiscussions about the use of
&os.current;This is the digest version of the freebsd-current mailing
list. The digest consists of all messages sent to
freebsd-current bundled together and mailed out as a single
message. This list is Read-Only and
should not be posted to.FREEBSD-CVSWEBFreeBSD CVSweb ProjectTechnical discussions about use, development and maintenance
of FreeBSD-CVSweb.FREEBSD-DOCDocumentation projectThis mailing list is for the discussion of issues and
projects related to the creation of documentation for FreeBSD.
The members of this mailing list are collectively referred to as
The FreeBSD Documentation Project. It is an open
list; feel free to join and contribute!FREEBSD-FIREWIREFirewire (iLink, IEEE 1394)This is a mailing list for discussion of the design
and implementation of a Firewire (aka IEEE 1394 aka
iLink) subsystem for FreeBSD. Relevant topics
specifically include the standards, bus devices and
their protocols, adapter boards/cards/chips sets, and
the architecture and implementation of code for their
proper support.FREEBSD-FSFile systemsDiscussions concerning FreeBSD file systems. This is a
technical mailing list for which strictly technical content is
expected.FREEBSD-GNOMEGNOMEDiscussions concerning The GNOME Desktop Environment for
FreeBSD systems. This is a technical mailing list for
which strictly technical content is expected.FREEBSD-IPFWIP FirewallThis is the forum for technical discussions concerning the
redesign of the IP firewall code in FreeBSD. This is a
technical mailing list for which strictly technical content is
expected.FREEBSD-IA64Porting FreeBSD to IA64This is a technical mailing list for individuals
actively working on porting FreeBSD to the IA-64 platform
from Intel, to bring up problems or discuss alternative
solutions. Individuals interested in following the
technical discussion are also welcome.FREEBSD-ISDNISDN CommunicationsThis is the mailing list for people discussing the
development of ISDN support for FreeBSD.FREEBSD-JAVAJava DevelopmentThis is the mailing list for people discussing the
development of significant Java applications for FreeBSD and the
porting and maintenance of JDKs.FREEBSD-HACKERSTechnical discussionsThis is a forum for technical discussions related to
FreeBSD. This is the primary technical mailing list. It is for
individuals actively working on FreeBSD, to bring up problems or
discuss alternative solutions. Individuals interested in
following the technical discussion are also welcome. This is a
technical mailing list for which strictly technical content is
expected.FREEBSD-HACKERS-DIGESTTechnical discussionsThis is the digest version of the freebsd-hackers mailing
list. The digest consists of all messages sent to
freebsd-hackers bundled together and mailed out as a single
message. This list is Read-Only
and should not be posted to.FREEBSD-HARDWAREGeneral discussion of FreeBSD
hardwareGeneral discussion about the types of hardware that FreeBSD
runs on, various problems and suggestions concerning what to buy
or avoid.FREEBSD-HUBSMirror sitesAnnouncements and discussion for people who run FreeBSD
mirror sites.FREEBSD-INSTALLInstallation discussionThis mailing list is for discussing FreeBSD installation
development for the future releases.FREEBSD-ISPIssues for Internet Service
ProvidersThis mailing list is for discussing topics relevant to
Internet Service Providers (ISPs) using FreeBSD. This is a
technical mailing list for which strictly technical content is
expected.FREEBSD-NEWBIESNewbies activities discussionWe cover any of the activities of newbies that are not
already dealt with elsewhere, including: independent learning
and problem solving techniques, finding and using resources and
asking for help elsewhere, how to use mailing lists and which
lists to use, general chat, making mistakes, boasting, sharing
ideas, stories, moral (but not technical) support, and taking an
active part in the FreeBSD community. We take our problems and
support questions to freebsd-questions, and use freebsd-newbies
to meet others who are doing the same things that we do as
newbies.FREEBSD-OPENOFFICEOpenOffice.orgDiscussions concerning the porting and maintenance
of OpenOffice.org and
StarOffice.FREEBSD-PERFORMANCEDiscussions about tuning or speeding up FreeBSDThis mailing list exists to provide a place for
hackers, administrators, and/or concerned parties to
discuss performance related topics pertaining to
FreeBSD. Acceptable topics includes talking about
FreeBSD installations that are either under high load,
are experiencing performance problems, or are pushing
the limits of FreeBSD. Concerned parties that are
willing to work toward improving the performance of
FreeBSD are highly encouraged to subscribe to this list.
This is a highly technical list ideally suited for
experienced FreeBSD users, hackers, or administrators
interested in keeping FreeBSD fast, robust, and
scalable. This list is not a question-and-answer list
that replaces reading through documentation, but it is a
place to make contributions or inquire about unanswered
performance related topics.FREEBSD-PLATFORMSPorting to Non-Intel platformsCross-platform FreeBSD issues, general discussion and
proposals for non-Intel FreeBSD ports. This is a technical
mailing list for which strictly technical content is
expected.FREEBSD-POLICYCore team policy decisionsThis is a low volume, read-only mailing list for FreeBSD
Core Team Policy decisions.FREEBSD-PORTSDiscussion of
portsDiscussions concerning FreeBSD's ports
collection (/usr/ports), proposed
ports, modifications to ports collection infrastructure and
general coordination efforts. This is a technical mailing list
for which strictly technical content is expected.FREEBSD-QUESTIONSUser questionsThis is the mailing list for questions about FreeBSD. You
should not send how to questions to the technical
lists unless you consider the question to be pretty
technical.FREEBSD-QUESTIONS-DIGESTUser questionsThis is the digest version of the freebsd-questions mailing
list. The digest consists of all messages sent to
freebsd-questions bundled together and mailed out as a single
message.FREEBSD-SCSISCSI subsystemThis is the mailing list for people working on the SCSI
subsystem for FreeBSD. This is a technical mailing list for
which strictly technical content is expected.FREEBSD-SECURITYSecurity issuesFreeBSD computer security issues (DES, Kerberos, known
security holes and fixes, etc). This is a technical mailing
list for which strictly technical discussion is expected. Note
that this is not a question-and-answer list, but that
contributions (BOTH question AND answer) to the FAQ are
welcome.FREEBSD-SECURITY-NOTIFICATIONSSecurity NotificationsNotifications of FreeBSD security problems and
fixes. This is not a discussion list. The discussion
list is FreeBSD-security.FREEBSD-SMALLUsing FreeBSD in embedded
applicationsThis list discusses topics related to unusually small and
embedded FreeBSD installations. This is a technical mailing
list for which strictly technical content is expected.FREEBSD-STABLEDiscussions about the use of
&os.stable;This is the mailing list for users of &os.stable;. It
includes warnings about new features coming out in -STABLE that
will affect the users, and instructions on steps that must be
taken to remain -STABLE. Anyone running STABLE
should subscribe to this list. This is a technical mailing list
for which strictly technical content is expected.FREEBSD-STANDARDSC99 & POSIX ConformanceThis is a forum for technical discussions related to
FreeBSD Conformance to the C99 and the POSIX standards.FREEBSD-USER-GROUPSUser Group Coordination ListThis is the mailing list for the coordinators from each of
the local area Users Groups to discuss matters with each other
and a designated individual from the Core Team. This mail list
should be limited to meeting synopsis and coordination of
projects that span User Groups.FREEBSD-VENDORSVendorsCoordination discussions between The FreeBSD Project and
Vendors of software and hardware for FreeBSD.Usenet NewsgroupsIn addition to two FreeBSD specific newsgroups, there are many
others in which FreeBSD is discussed or are otherwise relevant to
FreeBSD users. Keyword
searchable archives are available for some of these newsgroups
from courtesy of Warren Toomey wkt@cs.adfa.edu.au.BSD Specific Newsgroupscomp.unix.bsd.freebsd.announcecomp.unix.bsd.freebsd.miscde.comp.os.unix.bsd (German)fr.comp.os.bsd (French)Other Unix Newsgroups of Interestcomp.unixcomp.unix.questionscomp.unix.admincomp.unix.programmercomp.unix.shellcomp.unix.user-friendlycomp.security.unixcomp.sources.unixcomp.unix.advocacycomp.unix.misccomp.bugs.4bsdcomp.bugs.4bsd.ucb-fixescomp.unix.bsdX Window Systemcomp.windows.x.i386unixcomp.windows.xcomp.windows.x.appscomp.windows.x.announcecomp.windows.x.intrinsicscomp.windows.x.motifcomp.windows.x.pexcomp.emulators.ms-windows.wineWorld Wide Web Servershttp://www.FreeBSD.org/
— Central Server.http://www.ar.FreeBSD.org/ — Armenia.http://www.au.FreeBSD.org/ — Australia/1.http://www2.au.FreeBSD.org/ — Australia/2.http://www3.au.FreeBSD.org/ — Australia/3.http://www4.au.FreeBSD.org/ — Australia/4.http://www5.au.FreeBSD.org/ — Australia/5.http://www6.au.FreeBSD.org/ — Australia/6.http://freebsd.itworks.com.au/ — Australia/7.http://www.at.FreeBSD.org/ — Austria.http://www2.at.FreeBSD.org/ — Austria/2.http://freebsd.unixtech.be/ — Belgium.http://www.br.FreeBSD.org/www.freebsd.org/ — Brazil/1.http://www2.br.FreeBSD.org/www.freebsd.org/ — Brazil/2.http://www3.br.FreeBSD.org/ — Brazil/3.http://www.bg.FreeBSD.org/ — Bulgaria.http://www.ca.FreeBSD.org/ — Canada.http://www.cn.FreeBSD.org/ — China.http://www.cz.FreeBSD.org/ — Czech Republic.http://www.dk.FreeBSD.org/ — Denmark.http://www3.dk.FreeBSD.org/ — Denmark/3.http://www.ee.FreeBSD.org/ — Estonia.http://www.fi.FreeBSD.org/ — Finland.http://www2.fi.FreeBSD.org/ — Finland/2.http://www.fr.FreeBSD.org/ — France.http://www.de.FreeBSD.org/ — Germany/1.http://www1.de.FreeBSD.org/ — Germany/2.http://www2.de.FreeBSD.org/ — Germany/3.http://www.gr.FreeBSD.org/ — Greece.http://www.hk.FreeBSD.org/ — Hong Kong.http://www.hu.FreeBSD.org/ — Hungary.http://www2.hu.FreeBSD.org/ — Hungary/2.http://www.is.FreeBSD.org/ — Iceland.http://www.ie.FreeBSD.org/ — Ireland.http://www2.ie.FreeBSD.org/ — Ireland/2.http://www.it.FreeBSD.org/ — Italy.http://www.gufi.org/mirrors/www.freebsd.org/data/ — Italy/2.http://www.jp.FreeBSD.org/www.FreeBSD.org/ — Japan.http://www.kr.FreeBSD.org/ — Korea/1.http://www2.kr.FreeBSD.org/ — Korea/2.http://www3.kr.FreeBSD.org/ — Korea/3.http://www.lv.FreeBSD.org/ — Latvia.http://www.lt.FreeBSD.org/ — Lithuania.http://rama.asiapac.net/freebsd/ — Malaysia.http://www.nl.FreeBSD.org/ — Netherlands/1.http://www2.nl.FreeBSD.org/ — Netherlands/2.http://www.no.FreeBSD.org/ — Norway.http://www2.no.FreeBSD.org/ — Norway/2.http://www.nz.FreeBSD.org/ — New Zealand.http://www.FreeBSD.org.ph/ — Philippines.http://www.pl.FreeBSD.org/ — Poland/1.http://www2.pl.FreeBSD.org/ — Poland/2.http://www2.pt.FreeBSD.org/ — Portugal/2.http://www3.pt.FreeBSD.org/ — Portugal/3.http://www4.pt.FreeBSD.org/ — Portugal/4.http://www.ro.FreeBSD.org/ — Romania.http://www2.ro.FreeBSD.org/ — Romania/2.http://www3.ro.FreeBSD.org/ — Romania/3.http://www4.ro.FreeBSD.org/ — Romania/4.http://www.ru.FreeBSD.org/ — Russia/1.http://www2.ru.FreeBSD.org/ — Russia/2.http://www3.ru.FreeBSD.org/ — Russia/3.http://www4.ru.FreeBSD.org/ — Russia/4.http://www.sm.FreeBSD.org/ — San Marino.http://www2.sg.FreeBSD.org/ — Singapore.http://www.sk.FreeBSD.org/ — Slovak Republic.http://www2.sk.FreeBSD.org/ — Slovak Republic/2.http://www.si.FreeBSD.org/ — Slovenia.http://www2.si.FreeBSD.org/ — Slovenia/2.http://www.es.FreeBSD.org/ — Spain.http://www2.es.FreeBSD.org/ — Spain/2.http://www3.es.FreeBSD.org/ — Spain/3.http://www.za.FreeBSD.org/ — South Africa/1.http://www2.za.FreeBSD.org/ — South Africa/2.http://www.se.FreeBSD.org/ — Sweden.http://www2.se.FreeBSD.org/ — Sweden/2.http://www.ch.FreeBSD.org/ — Switzerland.http://www2.ch.FreeBSD.org/ — Switzerland/2.http://www.tw.FreeBSD.org/ — Taiwan.http://www2.tw.FreeBSD.org/ — Taiwan/2.http://www3.tw.FreeBSD.org/ — Taiwan/3.http://www4.tw.FreeBSD.org/ — Taiwan/4.http://www.tr.FreeBSD.org/ — Turkey.http://www2.tr.FreeBSD.org/ — Turkey/2.http://www.enderunix.org/freebsd/ — Turkey/3.http://www.ua.FreeBSD.org/www.freebsd.org/ — Ukraine/1.http://www2.ua.FreeBSD.org/ — Ukraine/2.http://www4.ua.FreeBSD.org/ — Ukraine/Crimea.http://www5.ua.FreeBSD.org/ — Ukraine/5.http://www.uk.FreeBSD.org/ — United Kingdom/1.http://www2.uk.FreeBSD.org/ — United Kingdom/2.http://www3.uk.FreeBSD.org/ — United Kingdom/3.http://www4.uk.FreeBSD.org/ — United Kingdom/4.http://www2.FreeBSD.org/ — USA/Texas.http://www3.FreeBSD.org/ — USA/3.http://www7.FreeBSD.org/ — USA/7.Email AddressesThe following user groups provide FreeBSD related email addresses
for their members. The listed administrator reserves the right to
revoke the address if it is abused in any way.DomainFacilitiesUser GroupAdministratorukug.uk.FreeBSD.orgForwarding onlyfreebsd-users@uk.FreeBSD.orgLee Johnston
lee@uk.FreeBSD.orgShell AccountsThe following user groups provide shell accounts for people who are
actively supporting the FreeBSD project. The listed administrator
reserves the right to cancel the account if it is abused in any
way.HostAccessFacilitiesAdministratorstorm.uk.FreeBSD.orgSSH onlyRead-only cvs, personal web space, email&a.brian;dogma.freebsd-uk.eu.orgTelnet/FTP/SSHEmail, Web space, Anonymous FTPLee Johnston
lee@uk.FreeBSD.org
diff --git a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
index d944c2347a..f0e461927d 100644
--- a/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
@@ -1,4782 +1,4782 @@
Obtaining FreeBSDCDROM and DVD PublishersRetail Boxed ProductsFreeBSD is available as a boxed product (FreeBSD CDs,
additional software, and printed documentation) from several
retailers:CompUSA
WWW: http://www.compusa.com/Frys Electronics
WWW: http://www.frys.com/CD and DVD SetsFreeBSD CD and DVD sets are available from many online
retailers:Daemon News Mall560 South State Street, Suite A2Orem, UT84058USA
Phone: +1 800 407-5170
Fax: +1 1 801 765-0877
Email: sales@bsdmall.com
WWW: http://www.bsdmall.com/FreeBSD Mall, Inc.3623 Sanford StreetConcord, CA94520-1405USA
Phone: +1 925 674-0783
Fax: +1 925 674-0821
Email: info@freebsdmall.com
WWW: http://www.freebsdmall.com/FreeBSD Services Ltd11 Lapwing CloseBicesterOX26 6XRUnited Kingdom
WWW: http://www.freebsd-services.com/Hinner EDVSt. Augustinus-Str. 10D-81825MünchenGermany
Phone: (089) 428 419
WWW: http://www.hinner.de/linux/freebsd.htmlIngram Micro1600 E. St. Andrew PlaceSanta Ana, CA92705-4926USA
Phone: 1 (800) 456-8000
WWW: http://www.ingrammicro.com/The Linux EmporiumHilliard House, Lester WayWallingfordOX10 9TAUnited Kingdom
Phone: +44 1491 837010
Fax: +44 1491 837016
WWW: http://www.linuxemporium.co.uk/bsd.htmlUNIXDVD.COM LTD57 Primrose AvenueSheffieldS5 6FSUnited Kingdom
WWW: http://www.unixdvd.com/DistributorsIf you are a reseller and want to carry FreeBSD CDROM products,
please contact a distributor:Cylogistics2672 Bayshore Parkway, Suite 610Mountain View, CA94043USA
Phone: +1 650 694-4949
Fax: +1 650 694-4953
Email: sales@cylogistics.com
WWW: http://www.cylogistics.com/FreeBSD Services Ltd11 Lapwing CloseBicesterOX26 6XRUnited Kingdom
WWW: http://www.freebsd-services.com/Kudzu, LLC7375 Washington Ave. S.Edina, MN55439USA
Phone: +1 952 947-0822
Fax: +1 952 947-0876
Email: sales@kudzuenterprises.comNavarre Corp7400 49th Ave SouthNew Hope, MN55428USA
Phone: +1 763 535-8333
Fax: +1 763 535-0341
WWW: http://www.navarre.com/FTP SitesThe official sources for FreeBSD are available via anonymous FTP
from:
ftp://ftp.FreeBSD.org/pub/FreeBSD/.
The FreeBSD mirror
sites database is more accurate than the mirror listing in the
Handbook, as it gets its information from the DNS rather than relying on
static lists of hosts.Additionally, FreeBSD is available via anonymous FTP from the
following mirror sites. If you choose to obtain FreeBSD via anonymous
FTP, please try to use a site near you.Argentina,
Australia,
Austria,
Brazil,
Bulgaria,
Canada,
China,
Czech Republic,
Denmark,
Estonia,
Finland,
France,
Germany,
Greece,
Hong Kong,
Hungary,
Iceland,
Ireland,
Italy,
Japan,
Korea,
Lithuania,
Netherlands,
New Zealand,
Norway,
Poland,
Portugal,
Romania,
Russia,
Saudi Arabia,
Singapore,
Slovak Republic,
Slovenia,
South Africa,
Spain,
Sweden,
Switzerland,
Taiwan,
Thailand,
UK,
Ukraine,
USA.ArgentinaIn case of problems, please contact the hostmaster
hostmaster@ar.FreeBSD.org for this domain.ftp://ftp.ar.FreeBSD.org/pub/FreeBSD/AustraliaIn case of problems, please contact the hostmaster
hostmaster@au.FreeBSD.org for this domain.ftp://ftp.au.FreeBSD.org/pub/FreeBSD/ftp://ftp2.au.FreeBSD.org/pub/FreeBSD/ftp://ftp3.au.FreeBSD.org/pub/FreeBSD/ftp://ftp4.au.FreeBSD.org/pub/FreeBSD/ftp://ftp5.au.FreeBSD.org/pub/FreeBSD/ftp://ftp6.au.FreeBSD.org/pub/FreeBSD/AustriaIn case of problems, please contact the hostmaster
hostmaster@at.FreeBSD.org for this domain.ftp://ftp.at.FreeBSD.org/pub/FreeBSD/ftp://ftp2.at.FreeBSD.org/pub/FreeBSD/BrazilIn case of problems, please contact the hostmaster
hostmaster@br.FreeBSD.org for this domain.ftp://ftp.br.FreeBSD.org/pub/FreeBSD/ftp://ftp2.br.FreeBSD.org/pub/FreeBSD/ftp://ftp3.br.FreeBSD.org/pub/FreeBSD/ftp://ftp4.br.FreeBSD.org/pub/FreeBSD/ftp://ftp5.br.FreeBSD.org/pub/FreeBSD/ftp://ftp6.br.FreeBSD.org/pub/FreeBSD/ftp://ftp7.br.FreeBSD.org/pub/FreeBSD/BulgariaIn case of problems, please contact the hostmaster
hostmaster@bg.FreeBSD.org for this domain.ftp://ftp.bg.FreeBSD.org/pub/FreeBSD/CanadaIn case of problems, please contact the hostmaster
hostmaster@ca.FreeBSD.org for this domain.ftp://ftp.ca.FreeBSD.org/pub/FreeBSD/ftp://ftp2.ca.FreeBSD.org/pub/FreeBSD/ChinaIn case of problems, please contact the hostmaster
phj@cn.FreeBSD.org for this domain.ftp://ftp.cn.FreeBSD.org/pub/FreeBSD/ftp://ftp2.cn.FreeBSD.org/pub/FreeBSD/ftp://ftp3.cn.FreeBSD.org/pub/FreeBSD/Czech RepublicIn case of problems, please contact the hostmaster
hostmaster@cz.FreeBSD.org for this domain.ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ Contact: calda@dzungle.ms.mff.cuni.czDenmarkIn case of problems, please contact the hostmaster
hostmaster@dk.FreeBSD.org for this domain.ftp://ftp.dk.FreeBSD.org/pub/FreeBSD/ftp://ftp2.dk.FreeBSD.org/pub/FreeBSD/EstoniaIn case of problems, please contact the hostmaster
hostmaster@ee.FreeBSD.org for this domain.ftp://ftp.ee.FreeBSD.org/pub/FreeBSD/FinlandIn case of problems, please contact the hostmaster
hostmaster@fi.FreeBSD.org for this domain.ftp://ftp.fi.FreeBSD.org/pub/FreeBSD/ftp://ftp3.fi.FreeBSD.org/pub/FreeBSD/FranceIn case of problems, please contact the hostmaster
hostmaster@fr.FreeBSD.org for this domain.ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ftp://ftp2.fr.FreeBSD.org/pub/FreeBSD/ftp://ftp3.fr.FreeBSD.org/pub/FreeBSD/ftp://ftp5.fr.FreeBSD.org/pub/FreeBSD/ftp://ftp6.fr.FreeBSD.org/pub/FreeBSD/ftp://ftp8.fr.FreeBSD.org/pub/FreeBSD/GermanyIn case of problems, please contact the mirror admins
de-bsd-hubs@de.FreeBSD.org for this domain.ftp://ftp.de.FreeBSD.org/pub/FreeBSD/ftp://ftp2.de.FreeBSD.org/pub/FreeBSD/ftp://ftp3.de.FreeBSD.org/pub/FreeBSD/ftp://ftp4.de.FreeBSD.org/pub/FreeBSD/ftp://ftp5.de.FreeBSD.org/pub/FreeBSD/ftp://ftp6.de.FreeBSD.org/pub/FreeBSD/ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/GreeceIn case of problems, please contact the hostmaster
hostmaster@gr.FreeBSD.org for this domain.ftp://ftp.gr.FreeBSD.org/pub/FreeBSD/ftp://ftp2.gr.FreeBSD.org/pub/FreeBSD/Hong Kongftp://ftp.hk.FreeBSD.org/pub/FreeBSD/HungaryIn case of problems, please contact the hostmaster
mohacsi@ik.bme.hu for this domain.ftp://ftp.hu.FreeBSD.org/pub/FreeBSD/IcelandIn case of problems, please contact the hostmaster
hostmaster@is.FreeBSD.org for this domain.ftp://ftp.is.FreeBSD.org/pub/FreeBSD/IrelandIn case of problems, please contact the hostmaster
hostmaster@ie.FreeBSD.org for this domain.ftp://ftp.ie.FreeBSD.org/pub/FreeBSD/ftp://ftp2.ie.FreeBSD.org/pub/FreeBSD/ftp://ftp3.ie.FreeBSD.org/pub/FreeBSD/ItalyIn case of problems, please contact the hostmaster
hostmaster@it.FreeBSD.org for this domain.ftp://ftp.it.FreeBSD.org/pub/FreeBSD/JapanIn case of problems, please contact the hostmaster
hostmaster@jp.FreeBSD.org for this domain.ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ftp://ftp2.jp.FreeBSD.org/pub/FreeBSD/ftp://ftp3.jp.FreeBSD.org/pub/FreeBSD/ftp://ftp4.jp.FreeBSD.org/pub/FreeBSD/ftp://ftp5.jp.FreeBSD.org/pub/FreeBSD/ftp://ftp6.jp.FreeBSD.org/pub/FreeBSD/ftp://ftp7.jp.FreeBSD.org/pub/FreeBSD/KoreaIn case of problems, please contact the hostmaster
hostmaster@kr.FreeBSD.org for this domain.ftp://ftp.kr.FreeBSD.org/pub/FreeBSD/ftp://ftp2.kr.FreeBSD.org/pub/FreeBSD/ftp://ftp3.kr.FreeBSD.org/pub/FreeBSD/ftp://ftp4.kr.FreeBSD.org/pub/FreeBSD/ftp://ftp5.kr.FreeBSD.org/pub/FreeBSD/ftp://ftp6.kr.FreeBSD.org/pub/FreeBSD/ftp://ftp7.kr.FreeBSD.org/pub/FreeBSD/LithuaniaIn case of problems, please contact the hostmaster
hostmaster@lt.FreeBSD.org for this domain.ftp://ftp.lt.FreeBSD.org/pub/FreeBSD/NetherlandsIn case of problems, please contact the hostmaster
hostmaster@nl.FreeBSD.org for this domain.ftp://ftp.nl.FreeBSD.org/pub/FreeBSD/ftp://ftp2.nl.FreeBSD.org/pub/FreeBSD/New ZealandIn case of problems, please contact the hostmaster
hostmaster@nz.FreeBSD.org for this domain.ftp://ftp.nz.FreeBSD.org/pub/FreeBSD/NorwayIn case of problems, please contact the hostmaster
hostmaster@no.FreeBSD.org for this domain.ftp://ftp.no.FreeBSD.org/pub/FreeBSD/ftp://ftp3.no.FreeBSD.org/pub/FreeBSD/PolandIn case of problems, please contact the hostmaster
hostmaster@pl.FreeBSD.org for this domain.ftp://ftp.pl.FreeBSD.org/pub/FreeBSD/ftp://ftp2.pl.FreeBSD.org/pub/FreeBSD/ftp://ftp3.pl.FreeBSD.org/pub/FreeBSD/PortugalIn case of problems, please contact the hostmaster
hostmaster@pt.FreeBSD.org for this domain.ftp://ftp2.pt.FreeBSD.org/pub/FreeBSD/ftp://ftp3.pt.FreeBSD.org/pub/FreeBSD/RomaniaIn case of problems, please contact the hostmaster
hostmaster@ro.FreeBSD.org for this domain.ftp://ftp.ro.FreeBSD.org/pub/FreeBSD/RussiaIn case of problems, please contact the hostmaster
hostmaster@ru.FreeBSD.org for this domain.ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/ftp://ftp3.ru.FreeBSD.org/pub/FreeBSD/ftp://ftp4.ru.FreeBSD.org/pub/FreeBSD/Saudi ArabiaIn case of problems, please contact
ftpadmin@isu.net.saftp://ftp.isu.net.sa/pub/mirrors/ftp.freebsd.org/SingaporeIn case of problems, please contact the hostmaster
hostmaster@sg.FreeBSD.org for this domain.ftp://ftp.sg.FreeBSD.org/pub/FreeBSD/South AfricaIn case of problems, please contact the hostmaster
hostmaster@za.FreeBSD.org for this domain.ftp://ftp.za.FreeBSD.org/pub/FreeBSD/ftp://ftp2.za.FreeBSD.org/pub/FreeBSD/ftp://ftp3.za.FreeBSD.org/pub/FreeBSD/ftp://ftp4.za.FreeBSD.org/pub/FreeBSD/Slovak RepublicIn case of problems, please contact the hostmaster
hostmaster@sk.FreeBSD.org for this domain.ftp://ftp.sk.FreeBSD.org/pub/FreeBSD/ftp://ftp2.sk.FreeBSD.org/pub/FreeBSD/SloveniaIn case of problems, please contact the hostmaster
hostmaster@si.FreeBSD.org for this domain.ftp://ftp2.si.FreeBSD.org/pub/FreeBSD/SpainIn case of problems, please contact the hostmaster
hostmaster@es.FreeBSD.org for this domain.ftp://ftp.es.FreeBSD.org/pub/FreeBSD/ftp://ftp2.es.FreeBSD.org/pub/FreeBSD/ftp://ftp3.es.FreeBSD.org/pub/FreeBSD/SwedenIn case of problems, please contact the hostmaster
hostmaster@se.FreeBSD.org for this domain.ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ftp://ftp2.se.FreeBSD.org/pub/FreeBSD/ftp://ftp3.se.FreeBSD.org/pub/FreeBSD/ftp://ftp5.se.FreeBSD.org/pub/FreeBSD/SwitzerlandIn case of problems, please contact the hostmaster
hostmaster@ch.FreeBSD.org for this domain.ftp://ftp.ch.FreeBSD.org/pub/FreeBSD/TaiwanIn case of problems, please contact the hostmaster
hostmaster@tw.FreeBSD.org for this domain.ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp3.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp4.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp5.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp6.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp7.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp8.tw.FreeBSD.org/pub/FreeBSD/ftp://ftp9.tw.FreeBSD.org/pub/FreeBSD/Thailandftp://ftp.nectec.or.th/pub/FreeBSD/ Contact: ftpadmin@ftp.nectec.or.th.Ukraineftp://ftp.ua.FreeBSD.org/pub/FreeBSD/ Contact: freebsd-mnt@lucky.net.ftp://ftp2.ua.FreeBSD.org/pub/FreeBSD/ftp://ftp3.ua.FreeBSD.org/pub/FreeBSD/ftp://ftp5.ua.FreeBSD.org/pub/FreeBSD/ftp://ftp6.ua.FreeBSD.org/pub/FreeBSD/ftp://ftp7.ua.FreeBSD.org/pub/FreeBSD/UKIn case of problems, please contact the hostmaster
hostmaster@uk.FreeBSD.org for this domain.ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD/ftp://ftp3.uk.FreeBSD.org/pub/FreeBSD/ftp://ftp4.uk.FreeBSD.org/pub/FreeBSD/ftp://ftp5.uk.FreeBSD.org/pub/FreeBSD/ftp://ftp6.uk.FreeBSD.org/pub/FreeBSD/USAIn case of problems, please contact the hostmaster
hostmaster@FreeBSD.org for this domain.ftp://ftp1.FreeBSD.org/pub/FreeBSD/ftp://ftp2.FreeBSD.org/pub/FreeBSD/ftp://ftp3.FreeBSD.org/pub/FreeBSD/ftp://ftp4.FreeBSD.org/pub/FreeBSD/ftp://ftp5.FreeBSD.org/pub/FreeBSD/ftp://ftp6.FreeBSD.org/pub/FreeBSD/ftp://ftp7.FreeBSD.org/pub/FreeBSD/ftp://ftp8.FreeBSD.org/pub/FreeBSD/ftp://ftp9.FreeBSD.org/pub/os/FreeBSD/ftp://ftp10.FreeBSD.org/pub/FreeBSD/ftp://ftp11.FreeBSD.org/pub/FreeBSD/ftp://ftp12.FreeBSD.org/pub/FreeBSD/ftp://ftp13.FreeBSD.org/pub/FreeBSD/ftp://ftp14.FreeBSD.org/pub/FreeBSD/Anonymous CVSIntroductionAnonymous CVS (or, as it is otherwise known,
anoncvs) is a feature provided by the CVS
utilities bundled with FreeBSD for synchronizing with a remote
CVS repository. Among other things, it allows users of FreeBSD
to perform, with no special privileges, read-only CVS operations
against one of the FreeBSD project's official anoncvs servers.
To use it, one simply sets the CVSROOT
environment variable to point at the appropriate anoncvs server,
provides the well-known password anoncvs with the
cvs login command, and then uses the
&man.cvs.1; command to access it like any local
repository.The cvs login command, stores the passwords
that are used for authenticating to the CVS server in a file
called .cvspass in your
HOME directory. If this file does not exist,
you might get an error when trying to use cvs
login for the first time. Just make an empty
.cvspass file, and retry to login.While it can also be said that the CVSup and anoncvs
services both perform essentially the same function, there are
various trade-offs which can influence the user's choice of
synchronization methods. In a nutshell,
CVSup is much more efficient in its
usage of network resources and is by far the most technically
sophisticated of the two, but at a price. To use
CVSup, a special client must first be
installed and configured before any bits can be grabbed, and
then only in the fairly large chunks which
CVSup calls
collections.Anoncvs, by contrast, can be used
to examine anything from an individual file to a specific
program (like ls or grep)
by referencing the CVS module name. Of course,
anoncvs is also only good for
read-only operations on the CVS repository, so if it is your
intention to support local development in one repository shared
with the FreeBSD project bits then
CVSup is really your only
option.Using Anonymous CVSConfiguring &man.cvs.1; to use an Anonymous CVS repository
is a simple matter of setting the CVSROOT
environment variable to point to one of the FreeBSD project's
anoncvs servers. At the time of this
writing, the following servers are available:USA:
:pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
(Use cvs login and enter the password
anoncvs when prompted.)Germany:
:pserver:anoncvs@anoncvs.de.FreeBSD.org:/home/ncvs
(Use cvs login and enter the password
anoncvs when prompted.)Germany:
:pserver:anoncvs@anoncvs2.de.FreeBSD.org:/home/ncvs
(rsh, pserver, ssh, ssh/2022)
Japan:
:pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
(Use cvs login and enter the password
anoncvs when prompted.)Since CVS allows one to check out virtually
any version of the FreeBSD sources that ever existed (or, in
some cases, will exist), you need to be
familiar with the revision () flag to
&man.cvs.1; and what some of the permissible values for it in
the FreeBSD Project repository are.There are two kinds of tags, revision tags and branch tags.
A revision tag refers to a specific revision. Its meaning stays
the same from day to day. A branch tag, on the other hand,
refers to the latest revision on a given line of development, at
any given time. Because a branch tag does not refer to a
specific revision, it may mean something different tomorrow than
it means today. contains revision tags that users
might be interested
in. Again, none of these are valid for the ports collection
since the ports collection does not have multiple
revisions.When you specify a branch tag, you normally receive the
latest versions of the files on that line of development. If
you wish to receive some past version, you can do so by
specifying a date with the flag.
See the &man.cvs.1; manual page for more details.ExamplesWhile it really is recommended that you read the manual page
for &man.cvs.1; thoroughly before doing anything, here are some
quick examples which essentially show how to use Anonymous
CVS:Checking Out Something from -CURRENT (&man.ls.1;) and
Deleting It Again:&prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
&prompt.user; cvs loginAt the prompt, enter the passwordanoncvs.
&prompt.user; cvs co ls
&prompt.user; cvs release -d ls
&prompt.user; cvs logoutChecking Out the Version of &man.ls.1; in the 3.X-STABLE
Branch:&prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
&prompt.user; cvs loginAt the prompt, enter the passwordanoncvs.
&prompt.user; cvs co -rRELENG_3 ls
&prompt.user; cvs release -d ls
&prompt.user; cvs logoutCreating a List of Changes (as unified diffs) to &man.ls.1;&prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
&prompt.user; cvs loginAt the prompt, enter the passwordanoncvs.
&prompt.user; cvs rdiff -u -rRELENG_3_0_0_RELEASE -rRELENG_3_4_0_RELEASE ls
&prompt.user; cvs logoutFinding Out What Other Module Names Can Be Used:&prompt.user; setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs
&prompt.user; cvs loginAt the prompt, enter the passwordanoncvs.
&prompt.user; cvs co modules
&prompt.user; more modules/modules
&prompt.user; cvs release -d modules
&prompt.user; cvs logoutOther ResourcesThe following additional resources may be helpful in learning
CVS:CVS Tutorial from Cal Poly.CVS Home,
the CVS development and support community.CVSWeb is
+ url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSweb is
the FreeBSD Project web interface for CVS.Using CTMCTM is a method for keeping a
remote directory tree in sync with a central one. It has been
developed for usage with FreeBSD's source trees, though other
people may find it useful for other purposes as time goes by.
Little, if any, documentation currently exists at this time on the
process of creating deltas, so talk to &a.phk; for more
information should you wish to use CTM
for other things.Why Should I Use CTM?CTM will give you a local copy of
the FreeBSD source trees. There are a number of
flavors of the tree available. Whether you wish
to track the entire CVS tree or just one of the branches,
CTM can provide you the information.
If you are an active developer on FreeBSD, but have lousy or
non-existent TCP/IP connectivity, or simply wish to have the
changes automatically sent to you,
CTM was made for you. You will need
to obtain up to three deltas per day for the most active
branches. However, you should consider having them sent by
automatic email. The sizes of the updates are always kept as
small as possible. This is typically less than 5K, with an
occasional (one in ten) being 10-50K and every now and then a
large 100K+ or more coming around.You will also need to make yourself aware of the various
caveats related to working directly from the development sources
rather than a pre-packaged release. This is particularly true
if you choose the current sources. It is
recommended that you read Staying
current with FreeBSD.What Do I Need to Use
CTM?You will need two things: The CTM
program, and the initial deltas to feed it (to get up to
current levels).The CTM program has been part of
FreeBSD ever since version 2.0 was released, and lives in
/usr/src/usr.sbin/ctm if you have a copy
of the source available.If you are running a pre-2.0 version of FreeBSD, you can
fetch the current CTM sources
directly from:ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/The deltas you feed
CTM can be had two ways, FTP or
email. If you have general FTP access to the Internet then the
following FTP sites support access to
CTM:ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/or see section mirrors.FTP the relevant directory and fetch the
README file, starting from there.If you wish to get your deltas via email:Send email to &a.majordomo; to subscribe to one of the
CTM distribution lists.
ctm-cvs-cur supports the entire CVS tree.
ctm-src-cur supports the head of the development
branch. ctm-src-2_2 supports the 2.2 release
branch, etc.. (If you do not know how to subscribe yourself
using majordomo, send a message first containing the word
help — it will send you back usage
instructions.)When you begin receiving your CTM
updates in the mail, you may use the
ctm_rmail program to unpack and apply them.
You can actually use the ctm_rmail program
directly from a entry in /etc/aliases if
you want to have the process run in a fully automated fashion.
Check the ctm_rmail manual page for more
details.No matter what method you use to get the
CTM deltas, you should subscribe to
the ctm-announce@FreeBSD.org mailing list. In
the future, this will be the only place where announcements
concerning the operations of the
CTM system will be posted. Send an
email to &a.majordomo; with a single line of
subscribe ctm-announce to get added to the
list.Using CTM for the First
TimeBefore you can start using CTM
deltas, you will need to get to a starting point for the deltas
produced subsequently to it.First you should determine what you already have. Everyone
can start from an empty directory. You must use
an initial Empty delta to start off your
CTM supported tree. At some point it
is intended that one of these started deltas be
distributed on the CD for your convenience, however, this does
not currently happen.Since the trees are many tens of megabytes, you should
prefer to start from something already at hand. If you have a
-RELEASE CD, you can copy or extract an initial source from it.
This will save a significant transfer of data.You can recognize these starter deltas by the
X appended to the number
(src-cur.3210XEmpty.gz for instance). The
designation following the X corresponds to
the origin of your initial seed.
Empty is an empty directory. As a rule a
base transition from Empty is produced
every 100 deltas. By the way, they are large! 70 to 80
Megabytes of gzip'd data is common for the
XEmpty deltas.Once you have picked a base delta to start from, you will also
need all deltas with higher numbers following it.Using CTM in Your Daily
LifeTo apply the deltas, simply say:&prompt.root; cd /where/ever/you/want/the/stuff
&prompt.root; ctm -v -v /where/you/store/your/deltas/src-xxx.*CTM understands deltas which have
been put through gzip, so you do not need to
gunzip them first, this saves disk space.Unless it feels very secure about the entire process,
CTM will not touch your tree. To
verify a delta you can also use the flag and
CTM will not actually touch your
tree; it will merely verify the integrity of the delta and see
if it would apply cleanly to your current tree.There are other options to CTM
as well, see the manual pages or look in the sources for more
information.That is really all there is to it. Every time you get a new
delta, just run it through CTM to
keep your sources up to date.Do not remove the deltas if they are hard to download again.
You just might want to keep them around in case something bad
happens. Even if you only have floppy disks, consider using
fdwrite to make a copy.Keeping Your Local ChangesAs a developer one would like to experiment with and change
files in the source tree. CTM
supports local modifications in a limited way: before checking
for the presence of a file foo, it first
looks for foo.ctm. If this file exists,
CTM will operate on it instead of
foo.This behavior gives us a simple way to maintain local
changes: simply copy the files you plan to modify to the
corresponding file names with a .ctm
suffix. Then you can freely hack the code, while CTM keeps the
.ctm file up-to-date.Other Interesting CTM OptionsFinding Out Exactly What Would Be Touched by an
UpdateYou can determine the list of changes that
CTM will make on your source
repository using the option to
CTM.This is useful if you would like to keep logs of the
changes, pre- or post- process the modified files in any
manner, or just are feeling a tad paranoid.Making Backups Before UpdatingSometimes you may want to backup all the files that would
be changed by a CTM update.Specifying the option
causes CTM to backup all files that
would be touched by a given CTM
delta to backup-file.Restricting the Files Touched by an UpdateSometimes you would be interested in restricting the scope
of a given CTM update, or may be
interested in extracting just a few files from a sequence of
deltas.You can control the list of files that
CTM would operate on by specifying
filtering regular expressions using the
and options.For example, to extract an up-to-date copy of
lib/libc/Makefile from your collection of
saved CTM deltas, run the commands:&prompt.root; cd /where/ever/you/want/to/extract/it/
&prompt.root; ctm -e '^lib/libc/Makefile' ~ctm/src-xxx.*For every file specified in a
CTM delta, the
and options are applied in the order given
on the command line. The file is processed by
CTM only if it is marked as
eligible after all the and
options are applied to it.Future Plans for CTMTons of them:Use some kind of authentication into the CTM system, so
as to allow detection of spoofed CTM updates.Clean up the options to CTM,
they became confusing and counter intuitive.Miscellaneous StuffThere is a sequence of deltas for the
ports collection too, but interest has not
been all that high yet.CTM MirrorsCTM/FreeBSD is available via anonymous
FTP from the following mirror sites. If you choose to obtain CTM via
anonymous FTP, please try to use a site near you.In case of problems, please contact &a.phk;.California, Bay Area, official sourceftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/South Africa, backup server for old deltasftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/Taiwan/R.O.C.ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/If you did not find a mirror near to you or the mirror is
incomplete, try to use a search engine such as
alltheweb.Using CVSupIntroductionCVSup is a software package for
distributing and updating source trees from a master CVS
repository on a remote server host. The FreeBSD sources are
maintained in a CVS repository on a central development machine
in California. With CVSup, FreeBSD
users can easily keep their own source trees up to date.CVSup uses the so-called
pull model of updating. Under the pull
model, each client asks the server for updates, if and when they
are wanted. The server waits passively for update requests from
its clients. Thus all updates are instigated by the client.
The server never sends unsolicited updates. Users must either
run the CVSup client manually to get
an update, or they must set up a cron job to
run it automatically on a regular basis.The term CVSup, capitalized just
so, refers to the entire software package. Its main components
are the client cvsup which runs on each
user's machine, and the server cvsupd which
runs at each of the FreeBSD mirror sites.As you read the FreeBSD documentation and mailing lists, you
may see references to sup.
Sup was the predecessor of
CVSup, and it served a similar
purpose. CVSup is used much in the
same way as sup and, in fact, uses configuration files which are
backward-compatible with sup's.
Sup is no longer used in the FreeBSD
project, because CVSup is both faster
and more flexible.InstallationThe easiest way to install CVSup
is to use the precompiled net/cvsup package
from the FreeBSD packages collection.
If you prefer to build CVSup from
source, you can use the net/cvsup
port instead. But be forewarned: the
net/cvsup port depends on the Modula-3
system, which takes a substantial amount of time and
disk space to download and build.If you are going to be using
CVSup on a machine which will not have
XFree86 installed, such as a server, be
sure to use the port which does not include the
CVSup GUI,
net/cvsup-without-gui.If you do not know anything about
CVSup at all and want a
single package which will install it, set up the configuration
file and start the transfer via a pointy-clicky type of
interface, then get the net/cvsupit
package. Just hand it to &man.pkg.add.1; and it will lead you
through the configuration process in a menu-oriented
fashion.CVSup ConfigurationCVSup's operation is controlled
by a configuration file called the supfile.
There are some sample supfiles in the
directory /usr/share/examples/cvsup/.The information in a supfile answers
the following questions for cvsup:Which files do you
want to receive?Which versions of them
do you want?Where do you want to
get them from?Where do you want to
put them on your own machine?Where do you want to
put your status files?In the following sections, we will construct a typical
supfile by answering each of these
questions in turn. First, we describe the overall structure of
a supfile.A supfile is a text file. Comments
begin with # and extend to the end of the
line. Lines that are blank and lines that contain only
comments are ignored.Each remaining line describes a set of files that the user
wishes to receive. The line begins with the name of a
collection, a logical grouping of files defined by
the server. The name of the collection tells the server which
files you want. After the collection name come zero or more
fields, separated by white space. These fields answer the
questions listed above. There are two types of fields: flag
fields and value fields. A flag field consists of a keyword
standing alone, e.g., delete or
compress. A value field also begins with a
keyword, but the keyword is followed without intervening white
space by = and a second word. For example,
release=cvs is a value field.A supfile typically specifies more than
one collection to receive. One way to structure a
supfile is to specify all of the relevant
fields explicitly for each collection. However, that tends to
make the supfile lines quite long, and it
is inconvenient because most fields are the same for all of the
collections in a supfile.
CVSup provides a defaulting mechanism
to avoid these problems. Lines beginning with the special
pseudo-collection name *default can be used
to set flags and values which will be used as defaults for the
subsequent collections in the supfile. A
default value can be overridden for an individual collection, by
specifying a different value with the collection itself.
Defaults can also be changed or augmented in mid-supfile by
additional *default lines.With this background, we will now proceed to construct a
supfile for receiving and updating the main
source tree of FreeBSD-CURRENT.Which files do you want
to receive?The files available via CVSup
are organized into named groups called
collections. The collections that are
available are described in the following section. In this
example, we
wish to receive the entire main source tree for the FreeBSD
system. There is a single large collection
src-all which will give us all of that.
As a first step toward constructing our
supfile, we
simply list the collections, one per line (in this case,
only one line):src-allWhich version(s) of them
do you want?With CVSup, you can receive
virtually any version of the sources that ever existed.
That is possible because the
cvsupd server works directly from
the CVS repository, which contains all of the versions. You
specify which one of them you want using the
tag= and value
fields.Be very careful to specify any tag=
fields correctly. Some tags are valid only for certain
collections of files. If you specify an incorrect or
misspelled tag, CVSup
will delete files which you probably
do not want deleted. In particular, use only
tag=. for the
ports-* collections.The tag= field names a symbolic tag
in the repository. There are two kinds of tags, revision
tags and branch tags. A revision tag refers to a specific
revision. Its meaning stays the same from day to day. A
branch tag, on the other hand, refers to the latest revision
on a given line of development, at any given time. Because
a branch tag does not refer to a specific revision, it may
mean something different tomorrow than it means
today. contains branch tags that
users might be interested in. When specifying a tag in
CVSup's configuration file, it
must be preceded with tag=
(RELENG_4 will become
tag=RELENG_4).
Keep in mind that only the tag=. is
relevant for the ports collection.Be very careful to type the tag name exactly as shown.
CVSup cannot distinguish
between valid and invalid tags. If you misspell the tag,
CVSup will behave as though you
had specified a valid tag which happens to refer to no
files at all. It will delete your existing sources in
that case.When you specify a branch tag, you normally receive the
latest versions of the files on that line of development.
If you wish to receive some past version, you can do so by
specifying a date with the value
field. The &man.cvsup.1; manual page explains how to do
that.For our example, we wish to receive FreeBSD-CURRENT. We
add this line at the beginning of our
supfile:*default tag=.There is an important special case that comes into play
if you specify neither a tag= field nor a
date= field. In that case, you receive
the actual RCS files directly from the server's CVS
repository, rather than receiving a particular version.
Developers generally prefer this mode of operation. By
maintaining a copy of the repository itself on their
systems, they gain the ability to browse the revision
histories and examine past versions of files. This gain is
achieved at a large cost in terms of disk space,
however.Where do you want to get
them from?We use the host= field to tell
cvsup where to obtain its updates. Any
of the CVSup mirror
sites will do, though you should try to select one
that is close to you in cyberspace. In this example we will
use a fictional FreeBSD distribution site,
cvsup666.FreeBSD.org:*default host=cvsup666.FreeBSD.orgYou will need to change the host to one that actually
exists before running CVSup.
On any particular run of
cvsup, you can override the host setting
on the command line, with .Where do you want to put
them on your own machine?The prefix= field tells
cvsup where to put the files it receives.
In this example, we will put the source files directly into
our main source tree, /usr/src. The
src directory is already implicit in
the collections we have chosen to receive, so this is the
correct specification:*default prefix=/usrWhere should
cvsup maintain its status files?The CVSup client maintains
certain status files in what
is called the base directory. These files
help CVSup to work more
efficiently, by keeping track of which updates you have
already received. We will use the standard base directory,
/usr/local/etc/cvsup:*default base=/usr/local/etc/cvsupThis setting is used by default if it is not specified
in the supfile, so we actually do not
need the above line.If your base directory does not already exist, now would
be a good time to create it. The cvsup
client will refuse to run if the base directory does not
exist.Miscellaneous supfile
settings:There is one more line of boiler plate that normally
needs to be present in the
supfile:*default release=cvs delete use-rel-suffix compressrelease=cvs indicates that the server
should get its information out of the main FreeBSD CVS
repository. This is virtually always the case, but there
are other possibilities which are beyond the scope of this
discussion.delete gives
CVSup permission to delete files.
You should always specify this, so that
CVSup can keep your source tree
fully up-to-date. CVSup is
careful to delete only those files for which it is
responsible. Any extra files you happen to have will be
left strictly alone.use-rel-suffix is ... arcane. If you
really want to know about it, see the &man.cvsup.1; manual
page. Otherwise, just specify it and do not worry about
it.compress enables the use of
gzip-style compression on the communication channel. If
your network link is T1 speed or faster, you probably should
not use compression. Otherwise, it helps
substantially.Putting it all together:Here is the entire supfile for our
example:*default tag=.
*default host=cvsup666.FreeBSD.org
*default prefix=/usr
*default base=/usr/local/etc/cvsup
*default release=cvs delete use-rel-suffix compress
src-allThe refuse FileAs mentioned above, CVSup uses
a pull method. Basically, this means that
you connect to the CVSup server, and
it says, Here is what you can download from
me..., and your client responds OK, I will take
this, this, this, and this. In the default
configuration, the CVSup client will
take every file associated with the collection and tag you
chose in the configuration file. However, this is not always
what you want, especially if you are synching the doc, ports, or
www trees — most people cannot read four or five
languages, and therefore they do not need to download the
language-specific files. If you are
CVSuping the ports collection, you
can get around this by specifying each collection individually
(e.g., ports-astrology,
ports-biology, etc instead of simply
saying ports-all). However, since the doc
and www trees do not have language-specific collections, you
must use one of CVSup's many nifty
features; the refuse file.The refuse file essentially tells
CVSup that it should not take every
single file from a collection; in other words, it tells the
client to refuse certain files from the
server. The refuse file can be found (or, if you do not yet
have one, should be placed) in
base/sup/refuse.
base is defined in your supfile; by
default, base is
/usr/local/etc/cvsup,
which means that by default the refuse file is in
/usr/local/etc/cvsup/sup/refuse.The refuse file has a very simple format; it simply
contains the names of files or directories that you do not wish
to download. For example, if you cannot speak any languages other
than English and some German, and you do not feel the need to use
the German applications (or applications for any other
languages, except for English), you can put the following in your
refuse file:ports/chinese
ports/french
ports/german
ports/hebrew
ports/japanese
ports/hungarian
ports/korean
ports/portuguese
ports/russian
ports/ukrainian
ports/vietnamese
doc/de_DE.ISO8859-1
doc/el_GR.ISO8859-7
doc/es_ES.ISO8859-1
doc/fr_FR.ISO8859-1
doc/it_IT.ISO8859-15
doc/ja_JP.eucJP
doc/nl_NL.ISO8859-1
doc/pt_BR.ISO8859-1
doc/ru_RU.KOI8-R
doc/sr_YU.ISO8859-2
doc/zh_TW.Big5and so forth for the other languages (you can find the
full list by browsing the FreeBSD
FTP server). Note that the name
of the repository is the first directory in the
refuse file.With this very useful feature, those users who are on
slow links or pay by the minute for their Internet connection
will be able to save valuable time as they will no longer need
to download files that they will never use. For more
information on refuse files and other neat
features of CVSup, please view its
manual page.Running CVSupYou are now ready to try an update. The command line for
doing this is quite simple:&prompt.root; cvsup supfilewhere supfile
is of course the name of the supfile you have just created.
Assuming you are running under X11, cvsup
will display a GUI window with some buttons to do the usual
things. Press the go button, and watch it
run.Since you are updating your actual
/usr/src tree in this example, you will
need to run the program as root so that
cvsup has the permissions it needs to update
your files. Having just created your configuration file, and
having never used this program before, that might
understandably make you nervous. There is an easy way to do a
trial run without touching your precious files. Just create an
empty directory somewhere convenient, and name it as an extra
argument on the command line:&prompt.root; mkdir /var/tmp/dest
&prompt.root; cvsup supfile /var/tmp/destThe directory you specify will be used as the destination
directory for all file updates.
CVSup will examine your usual files
in /usr/src, but it will not modify or
delete any of them. Any file updates will instead land in
/var/tmp/dest/usr/src.
CVSup will also leave its base
directory status files untouched when run this way. The new
versions of those files will be written into the specified
directory. As long as you have read access to
/usr/src, you do not even need to be
root to perform this kind of trial run.If you are not running X11 or if you just do not like GUIs,
you should add a couple of options to the command line when you
run cvsup:&prompt.root; cvsup -g -L 2 supfileThe tells
CVSup not to use its GUI. This is
automatic if you are not running X11, but otherwise you have to
specify it.The tells
CVSup to print out the
details of all the file updates it is doing. There are three
levels of verbosity, from to
. The default is 0, which means total
silence except for error messages.There are plenty of other options available. For a brief
list of them, type cvsup -H. For more
detailed descriptions, see the manual page.Once you are satisfied with the way updates are working, you
can arrange for regular runs of CVSup
using &man.cron.8;.
Obviously, you should not let CVSup
use its GUI when running it from &man.cron.8;.CVSup File CollectionsThe file collections available via
CVSup are organized hierarchically.
There are a few large collections, and they are divided into
smaller sub-collections. Receiving a large collection is
equivalent to receiving each of its sub-collections. The
hierarchical relationships among collections are reflected by
the use of indentation in the list below.The most commonly used collections are
src-all, and
ports-all. The other collections are used
only by small groups of people for specialized purposes, and
some mirror sites may not carry all of them.cvs-all release=cvsThe main FreeBSD CVS repository, including the
cryptography code.distrib release=cvsFiles related to the distribution and mirroring
of FreeBSD.doc-all release=cvsSources for the FreeBSD Handbook and other
documentation. This does not include files for
the FreeBSD web site.ports-all release=cvsThe FreeBSD Ports Collection.If you do not want to update the whole of
ports-all (the whole ports tree),
but use one of the subcollections listed below,
make sure that you always update
the ports-base subcollection!
Whenever something changes in the ports build
infrastructure represented by
ports-base, it is virtually certain
that those changes will be used by real
ports real soon. Thus, if you only update the
real ports and they use some of the new
features, there is a very high chance that their build
will fail with some mysterious error message. The
very first thing to do in this
case is to make sure that your
ports-base subcollection is up to
date.ports-archivers
release=cvsArchiving tools.ports-astro
release=cvsAstronomical ports.ports-audio
release=cvsSound support.ports-base
release=cvsThe Ports Collection build infrastructure -
various files located in the
Mk/ and
Tools/ subdirectories of
/usr/ports.Please see the important
warning above: you should
always update this
subcollection, whenever you update any part of
the FreeBSD Ports Collection!ports-benchmarks
release=cvsBenchmarks.ports-biology
release=cvsBiology.ports-cad
release=cvsComputer aided design tools.ports-chinese
release=cvsChinese language support.ports-comms
release=cvsCommunication software.ports-converters
release=cvscharacter code converters.ports-databases
release=cvsDatabases.ports-deskutils
release=cvsThings that used to be on the desktop
before computers were invented.ports-devel
release=cvsDevelopment utilities.ports-editors
release=cvsEditors.ports-emulators
release=cvsEmulators for other operating
systems.ports-finance
release=cvsMonetary, financial and related applications.ports-ftp
release=cvsFTP client and server utilities.ports-games
release=cvsGames.ports-german
release=cvsGerman language support.ports-graphics
release=cvsGraphics utilities.ports-hungarian
release=cvsHungarian language support.ports-irc
release=cvsInternet Relay Chat utilities.ports-japanese
release=cvsJapanese language support.ports-java
release=cvsJava utilities.ports-korean
release=cvsKorean language support.ports-lang
release=cvsProgramming languages.ports-mail
release=cvsMail software.ports-math
release=cvsNumerical computation software.ports-mbone
release=cvsMBone applications.ports-misc
release=cvsMiscellaneous utilities.ports-multimedia
release=cvsMultimedia software.ports-net
release=cvsNetworking software.ports-news
release=cvsUSENET news software.ports-palm
release=cvsSoftware support for Palm
series.ports-portuguese
release=cvsPortuguese language support.ports-print
release=cvsPrinting software.ports-russian
release=cvsRussian language support.ports-security
release=cvsSecurity utilities.ports-shells
release=cvsCommand line shells.ports-sysutils
release=cvsSystem utilities.ports-textproc
release=cvstext processing utilities (does not
include desktop publishing).ports-vietnamese
release=cvsVietnamese language support.ports-www
release=cvsSoftware related to the World Wide
Web.ports-x11
release=cvsPorts to support the X window
system.ports-x11-clocks
release=cvsX11 clocks.ports-x11-fm
release=cvsX11 file managers.ports-x11-fonts
release=cvsX11 fonts and font utilities.ports-x11-toolkits
release=cvsX11 toolkits.ports-x11-serversX11 servers.ports-x11-wmX11 window managers.src-all release=cvsThe main FreeBSD sources, including the
cryptography code.src-base
release=cvsMiscellaneous files at the top of
/usr/src.src-bin
release=cvsUser utilities that may be needed in
single-user mode
(/usr/src/bin).src-contrib
release=cvsUtilities and libraries from outside the
FreeBSD project, used relatively unmodified
(/usr/src/contrib).src-crypto release=cvsCryptography utilities and libraries from
outside the FreeBSD project, used relatively
unmodified
(/usr/src/crypto).src-eBones release=cvsKerberos and DES
(/usr/src/eBones). Not
used in current releases of FreeBSD.src-etc
release=cvsSystem configuration files
(/usr/src/etc).src-games
release=cvsGames
(/usr/src/games).src-gnu
release=cvsUtilities covered by the GNU Public
License (/usr/src/gnu).src-include
release=cvsHeader files
(/usr/src/include).src-kerberos5
release=cvsKerberos5 security package
(/usr/src/kerberos5).src-kerberosIV
release=cvsKerberosIV security package
(/usr/src/kerberosIV).src-lib
release=cvsLibraries
(/usr/src/lib).src-libexec
release=cvsSystem programs normally executed by other
programs
(/usr/src/libexec).src-release
release=cvsFiles required to produce a FreeBSD
release
(/usr/src/release).src-sbin release=cvsSystem utilities for single-user mode
(/usr/src/sbin).src-secure
release=cvsCryptographic libraries and commands
(/usr/src/secure).src-share
release=cvsFiles that can be shared across multiple
systems
(/usr/src/share).src-sys
release=cvsThe kernel
(/usr/src/sys).src-sys-crypto
release=cvsKernel cryptography code
(/usr/src/sys/crypto).src-tools
release=cvsVarious tools for the maintenance of
FreeBSD
(/usr/src/tools).src-usrbin
release=cvsUser utilities
(/usr/src/usr.bin).src-usrsbin
release=cvsSystem utilities
(/usr/src/usr.sbin).www release=cvsThe sources for the FreeBSD WWW site.distrib release=selfThe CVSup server's own
configuration files. Used by CVSup
mirror sites.gnats release=currentThe GNATS bug-tracking database.mail-archive release=currentFreeBSD mailing list archive.www release=currentThe pre-processed FreeBSD WWW site files (not the
source files). Used by WWW mirror sites.For More InformationFor the CVSup FAQ and other
information about CVSup, see
The
CVSup Home Page.Most FreeBSD-related discussion of
CVSup takes place on the
&a.hackers;. New versions of the software are announced there,
as well as on the &a.announce;.Questions and bug reports should be addressed to the author
of the program at cvsup-bugs@polstra.com.CVSup SitesCVSup servers for FreeBSD are running
at the following sites:Argentinacvsup.ar.FreeBSD.org (maintainer
msagre@cactus.fi.uba.ar)Australiacvsup.au.FreeBSD.org (maintainer
cvsup@ntt.net.au)cvsup2.au.FreeBSD.org (maintainer
cvsup@isp.net.au)cvsup3.au.FreeBSD.org (maintainer
cvsup@speednet.com.au)cvsup4.au.FreeBSD.org (maintainer
cvsup@ideal.net.au)cvsup5.au.FreeBSD.org (maintainer
cvsup@netlead.com.au)Austriacvsup.at.FreeBSD.org (maintainer
postmaster@wu-wien.ac.at)cvsup2.at.FreeBSD.org (maintainer
ftp-admin.zid@univie.ac.at)Brazilcvsup.br.FreeBSD.org (maintainer
cvsup@cvsup.br.FreeBSD.org)cvsup2.br.FreeBSD.org (maintainer
tps@ti.sk)cvsup3.br.FreeBSD.org (maintainer
camposr@matrix.com.br)cvsup4.br.FreeBSD.org (maintainer
cvsup@tcoip.com.br)cvsup5.br.FreeBSD.org (maintainer
hostmaster@br.FreeBSD.org)Bulgariacvsup.bg.FreeBSD.org (maintainer
hostmaster@bg.FreeBSD.org)Canadacvsup.ca.FreeBSD.org (maintainer
cvsup@ca.FreeBSD.org)Chinacvsup.cn.FreeBSD.org (maintainer
phj@cn.FreeBSD.org)Czech Republiccvsup.cz.FreeBSD.org (maintainer
cejkar@fit.vutbr.cz)Denmarkcvsup.dk.FreeBSD.org (maintainer
jesper@FreeBSD.org)Estoniacvsup.ee.FreeBSD.org (maintainer
taavi@uninet.ee)Finlandcvsup.fi.FreeBSD.org (maintainer
count@key.sms.fi)cvsup2.fi.FreeBSD.org (maintainer
count@key.sms.fi)Francecvsup.fr.FreeBSD.org (maintainer
hostmaster@fr.FreeBSD.org)cvsup2.fr.FreeBSD.org (maintainer
ftpmaint@uvsq.fr)cvsup3.fr.FreeBSD.org (maintainer
ftpmaint@enst.fr)cvsup4.fr.FreeBSD.org (maintainer
ftpmaster@t-online.fr)cvsup5.fr.FreeBSD.org (maintainer
freebsdcvsup@teaser.net)cvsup8.fr.FreeBSD.org (maintainer
ftpmaint@crc.u-strasbg.fr)Germanycvsup.de.FreeBSD.org (maintainer
cvsup@cosmo-project.de)cvsup2.de.FreeBSD.org (maintainer
cvsup@apfel.de)cvsup3.de.FreeBSD.org (maintainer
ag@leo.org)cvsup4.de.FreeBSD.org (maintainer
cvsup@cosmo-project.de)cvsup5.de.FreeBSD.org (maintainer
&a.rse;)cvsup6.de.FreeBSD.org (maintainer
adminmail@heitec.net)cvsup7.de.FreeBSD.org (maintainer
karsten@rohrbach.de)Greececvsup.gr.FreeBSD.org (maintainer
ftpadm@duth.gr)cvsup2.gr.FreeBSD.org (maintainer
paschos@cs.uoi.gr)Hungarycvsup.hu.FreeBSD.org (maintainer
janos.mohacsi@bsd.hu)Icelandcvsup.is.FreeBSD.org (maintainer
hostmaster@is.FreeBSD.org)Irelandcvsup.ie.FreeBSD.org (maintainer
dwmalone@maths.tcd.ie),
Trinity College, Dublin.Japancvsup.jp.FreeBSD.org (maintainer
cvsupadm@jp.FreeBSD.org)cvsup2.jp.FreeBSD.org (maintainer
&a.max;)cvsup3.jp.FreeBSD.org (maintainer
shige@cin.nihon-u.ac.jp)cvsup4.jp.FreeBSD.org (maintainer
cvsup-admin@ftp.media.kyoto-u.ac.jp)cvsup5.jp.FreeBSD.org (maintainer
cvsup@imasy.or.jp)cvsup6.jp.FreeBSD.org (maintainer
cvsupadm@jp.FreeBSD.org)Koreacvsup.kr.FreeBSD.org (maintainer
cjh@kr.FreeBSD.org)cvsup2.kr.FreeBSD.org (maintainer
holywar@mail.holywar.net)cvsup3.kr.FreeBSD.org (maintainer
leo@florida.sarang.net)Kuwaitcvsup1.kw.FreeBSD.org (maintainer
sysadmin@kems.net)Latviacvsup.lv.FreeBSD.org (maintainer
system@soft.lv)Lithuaniacvsup.lt.FreeBSD.org (maintainer
domas.mituzas@delfi.lt)cvsup2.lt.FreeBSD.org (maintainer
vaidas.damosevicius@if.lt)New Zealandcvsup.nz.FreeBSD.org (maintainer
cvsup@langille.org)Netherlandscvsup.nl.FreeBSD.org (maintainer
xaa@xaa.iae.nl)cvsup2.nl.FreeBSD.org (maintainer
cvsup@nl.uu.net)cvsup3.nl.FreeBSD.org (maintainer
cvsup@vuurwerk.nl)cvsup4.nl.FreeBSD.org (maintainer
hostmaster@cvsup4.nl.FreeBSD.org)Norwaycvsup.no.FreeBSD.org (maintainer
Per.Hove@math.ntnu.no)Polandcvsup.pl.FreeBSD.org (maintainer
Mariusz@kam.pl)cvsup2.pl.FreeBSD.org (maintainer
hostmaster@cvsup2.pl.FreeBSD.org)cvsup3.pl.FreeBSD.org (maintainer
hostmaster@cvsup3.pl.FreeBSD.org)Portugalcvsup.pt.FreeBSD.org (maintainer
jpedras@webvolution.net)Romaniacvsup.ro.FreeBSD.org (maintainer
razor@ldc.ro)cvsup2.ro.FreeBSD.org (maintainer
hostmaster@rofug.ro)cvsup3.ro.FreeBSD.org (maintainer
veedee@c7.campus.utcluj.ro)Russiacvsup.ru.FreeBSD.org (maintainer
ache@nagual.pp.ru)cvsup2.ru.FreeBSD.org (maintainer
dv@dv.ru)cvsup3.ru.FreeBSD.org (maintainer
fjoe@iclub.nsu.ru)cvsup4.ru.FreeBSD.org (maintainer
maxim@macomnet.ru)cvsup5.ru.FreeBSD.org (maintainer
maxim@macomnet.ru)cvsup6.ru.FreeBSD.org (maintainer
pvr@corbina.net)San Marinocvsup.sm.FreeBSD.org (maintainer
sysadmin@alexdupre.com)Singaporecvsup.sg.FreeBSD.org (maintainer
mirror-maintainer@mirror.averse.net)Slovak Republiccvsup.sk.FreeBSD.org (maintainer
scorp@scorp.sk)cvsup2.sk.FreeBSD.org (maintainer
scorp@scorp.sk)Sloveniacvsup.si.FreeBSD.org (maintainer
blaz@si.FreeBSD.org)cvsup2.si.FreeBSD.org (maintainer
cuk@cuk.nu)South Africacvsup.za.FreeBSD.org (maintainer
&a.markm;)cvsup2.za.FreeBSD.org (maintainer
&a.markm;)Spaincvsup.es.FreeBSD.org (maintainer
&a.jesusr;)cvsup2.es.FreeBSD.org (maintainer
&a.jesusr;)cvsup3.es.FreeBSD.org (maintainer
jose@we.lc.ehu.es)Swedencvsup.se.FreeBSD.org (maintainer
pantzer@ludd.luth.se)cvsup2.se.FreeBSD.org (maintainer
cvsup@dataphone.net)Taiwancvsup.tw.FreeBSD.org (maintainer
ijliao@FreeBSD.org)cvsup3.tw.FreeBSD.org (maintainer
foxfair@FreeBSD.org)cvsup4.tw.FreeBSD.org (maintainer
einstein@NHCTC.edu.tw)cvsup5.tw.FreeBSD.org (maintainer
einstein@NHCTC.edu.tw)cvsup6.tw.FreeBSD.org (maintainer
jason@tw.FreeBSD.org)cvsup7.tw.FreeBSD.org (maintainer
cvsup@abpe.org)cvsup8.tw.FreeBSD.org (maintainer
heboy@FreeBSD.tku.edu.tw)cvsup9.tw.FreeBSD.org (maintainer
cs871256@csie.ncu.edu.tw)cvsup10.tw.FreeBSD.org (maintainer
rafan@infor.org)cvsup11.tw.FreeBSD.org (maintainer
vanilla@FreeBSD.org)cvsup12.tw.FreeBSD.org (maintainer
GEO.bbs@birdnest.twbbs.org)cvsup13.tw.FreeBSD.org (maintainer
cdsheen@tw.FreeBSD.org)Turkeycvsup.tr.FreeBSD.org (maintainer
roots@enderunix.org)Ukrainecvsup2.ua.FreeBSD.org (maintainer
freebsd-mnt@lucky.net)cvsup3.ua.FreeBSD.org (maintainer
ftpmaster@ukr.net), Kievcvsup4.ua.FreeBSD.org (maintainer
phantom@cris.net)cvsup5.ua.FreeBSD.org (maintainer
never@nevermind.kiev.ua)cvsup6.ua.FreeBSD.org (maintainer
freebsd-cvs@colocall.net)cvsup7.ua.FreeBSD.org (maintainer
never@nevermind.kiev.ua)United Kingdomcvsup.uk.FreeBSD.org (maintainer
ftp-admin@plig.net)cvsup2.uk.FreeBSD.org (maintainer
&a.brian;)cvsup3.uk.FreeBSD.org (maintainer
ben.hughes@uk.easynet.net)cvsup4.uk.FreeBSD.org (maintainer
ejb@leguin.org.uk)cvsup5.uk.FreeBSD.org (maintainer
mirror@teleglobe.net)USAcvsup1.FreeBSD.org (maintainer
cwt@networks.cwu.edu), Washington
statecvsup2.FreeBSD.org (maintainers
djs@secure.net and &a.nectar;), Virginiacvsup3.FreeBSD.org (maintainer
&a.wollman;), Massachusettscvsup5.FreeBSD.org (maintainer
mjr@blackened.com), Arizonacvsup6.FreeBSD.org (maintainer
cvsup@cvsup.adelphiacom.net), Illinoiscvsup7.FreeBSD.org (maintainer
&a.jdp;), Washington statecvsup8.FreeBSD.org (maintainer
hostmaster@bigmirror.com), Washington
statecvsup9.FreeBSD.org (maintainer
&a.jdp;), Minnesotacvsup10.FreeBSD.org (maintainer
&a.jdp;), Californiacvsup11.FreeBSD.org (maintainer
cvsup@research.uu.net), Virginiacvsup12.FreeBSD.org (maintainer
&a.will;), Indianacvsup13.FreeBSD.org (maintainer
dima@valueclick.com), Californiacvsup14.FreeBSD.org (maintainer
freebsd-cvsup@mfnx.net), Californiacvsup15.FreeBSD.org (maintainer
cvsup@math.uic.edu), Illinoiscvsup16.FreeBSD.org (maintainer
pth3k@virginia.edu), Virginiacvsup17.FreeBSD.org (maintainer
cvsup@mirrortree.com), Washington stateCVS TagsWhen obtaining or updating sources from
cvs and
CVSup a revision tag (reference to a
date in time) must be specified. The following tags are
available, each specifying different branches of FreeBSD at
different points of time:The ports tree does not have any tag associated with it,
it is always CURRENT.The most common tags are:HEADSymbolic name for the main line, or FreeBSD-CURRENT.
Also the default when no revision is specified.In CVSup, this tag is represented
by a . (not punctuation, but a literal
. character).In CVS, this is the default when no revision tag is
specified. It is usually not
a good idea to checkout or update to CURRENT sources
on a STABLE machine, unless that is your intent.RELENG_5_0The release branch for FreeBSD-5.0, used only
for security advisories and other seriously critical fixes.RELENG_4The line of development for FreeBSD-4.X, also known
as FreeBSD-STABLE.RELENG_4_8The release branch for FreeBSD-4.8, used only
for security advisories and other seriously critical fixes.RELENG_4_7The release branch for FreeBSD-4.7, used only
for security advisories and other seriously critical fixes.RELENG_4_6The release branch for FreeBSD-4.6 and FreeBSD-4.6.2,
used only for security advisories and other seriously
critical fixes.RELENG_4_5The release branch for FreeBSD-4.5, used only
for security advisories and other seriously critical fixes.RELENG_4_4The release branch for FreeBSD-4.4, used only
for security advisories and other seriously critical fixes.RELENG_4_3The release branch for FreeBSD-4.3, used only
for security advisories and other seriously critical fixes.RELENG_3The line of development for FreeBSD-3.X, also known
as 3.X-STABLE.RELENG_2_2The line of development for FreeBSD-2.2.X, also known
as 2.2-STABLE. This branch is mostly obsolete.Other revision tags that are available include:RELENG_4_8_0_RELEASEFreeBSD 4.8RELENG_5_0_0_RELEASEFreeBSD 5.0RELENG_4_7_0_RELEASEFreeBSD 4.7RELENG_4_6_2_RELEASEFreeBSD 4.6.2RELENG_4_6_1_RELEASEFreeBSD 4.6.1RELENG_4_6_0_RELEASEFreeBSD 4.6RELENG_4_5_0_RELEASEFreeBSD 4.5.RELENG_4_4_0_RELEASEFreeBSD 4.4.RELENG_4_3_0_RELEASEFreeBSD 4.3.RELENG_4_2_0_RELEASEFreeBSD 4.2.RELENG_4_1_1_RELEASEFreeBSD 4.1.1.RELENG_4_1_0_RELEASEFreeBSD 4.1.RELENG_4_0_0_RELEASEFreeBSD 4.0.RELENG_3_5_0_RELEASEFreeBSD-3.5.RELENG_3_4_0_RELEASEFreeBSD-3.4.RELENG_3_3_0_RELEASEFreeBSD-3.3.RELENG_3_2_0_RELEASEFreeBSD-3.2.RELENG_3_1_0_RELEASEFreeBSD-3.1.RELENG_3_0_0_RELEASEFreeBSD-3.0.RELENG_2_2_8_RELEASEFreeBSD-2.2.8.RELENG_2_2_7_RELEASEFreeBSD-2.2.7.RELENG_2_2_6_RELEASEFreeBSD-2.2.6.RELENG_2_2_5_RELEASEFreeBSD-2.2.5.RELENG_2_2_2_RELEASEFreeBSD-2.2.2.RELENG_2_2_1_RELEASEFreeBSD-2.2.1.RELENG_2_2_0_RELEASEFreeBSD-2.2.0.AFS SitesAFS servers for FreeBSD are running at the following sites:SwedenThe path to the files are:
/afs/stacken.kth.se/ftp/pub/FreeBSD/stacken.kth.se # Stacken Computer Club, KTH, Sweden
130.237.234.43 #hot.stacken.kth.se
130.237.237.230 #fishburger.stacken.kth.se
130.237.234.3 #milko.stacken.kth.seMaintainer ftp@stacken.kth.sersync sitesThe following sites make FreeBSD available through the rsync
protocol. The rsync utility works in
much the same way as the rcp command,
but has more options and uses the rsync remote-update protocol
which transfers only the differences between two sets of files,
thus greatly speeding up the synchronization over the network.
This is most useful if you are a mirror site for the
FreeBSD FTP server, or the CVS repository. The
rsync suite is available for many
operating systems, on FreeBSD, see the
net/rsync
port or use the package.Czech Republicrsync://ftp.cz.FreeBSD.org/Available collections:ftp: A partial mirror of the FreeBSD FTP
server.FreeBSD: A full mirror of the FreeBSD FTP
server.Germanyrsync://grappa.unix-ag.uni-kl.de/Available collections:freebsd-cvs: The full FreeBSD CVS
repository.This machine also mirrors the CVS repositories of the
NetBSD and the OpenBSD projects, among others.Netherlandsrsync://ftp.nl.FreeBSD.org/Available collections:vol/3/freebsd-core: A full mirror of the
FreeBSD FTP server.United States of Americarsync://ftp-master.FreeBSD.org/This server may only be used by FreeBSD primary mirror
sites.Available collections:FreeBSD: The master archive of the FreeBSD
FTP server.acl: The FreeBSD master ACL
list.rsync://ftp13.FreeBSD.org/Available collections:FreeBSD: A full mirror of the FreeBSD FTP
server.