Fix bogon with freebsd-stable mailing list entity.
Make the sup documentation a little more lively. Fix bogon in current docs.
This commit is contained in:
parent
293fcf5e41
commit
94a04fd972
@ -1,4 +1,4 @@
|
||||
<!-- $Id: current.sgml,v 1.12 1996/07/04 01:44:31 jkh Exp $ -->
|
||||
<!-- $Id: current.sgml,v 1.13 1996/07/09 07:29:13 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
|
||||
THE FREEBSD CURRENT POLICY
|
||||
|
||||
Last updated: $Date: 1996/07/04 01:44:31 $
|
||||
Last updated: $Date: 1996/07/09 07:29:13 $
|
||||
|
||||
This document attempts to explain the rationale behind
|
||||
FreeBSD-current, what you should expect should you decide to run it,
|
||||
@ -70,15 +70,13 @@ ask! It takes far too much time to do this as a general task.
|
||||
|
||||
We do our best to help people genuinely in one of the 3
|
||||
``legitimate'' FreeBSD-current categories, but we simply <em>do not
|
||||
have the time</em> to help every person who jumps into FreeBSD-current
|
||||
with more enthusiasm than knowledge of how to deal with
|
||||
experimental system software. This is not because we are mean and
|
||||
nasty people who do not like helping people out (we would not even be
|
||||
doing FreeBSD if we were), it is literally because we cannot answer
|
||||
400 messages a day <em>and</em> actually work on FreeBSD! I am sure
|
||||
that, if given the choice between having us answer lots of questions or
|
||||
continuing to improve FreeBSD, most of you would vote for us
|
||||
improving it.
|
||||
have the time</em> to provide tech support for it.
|
||||
This is not because we are mean and nasty people who do not like
|
||||
helping people out (we would not even be doing FreeBSD if we were),
|
||||
it is literally because we cannot answer 400 messages a day
|
||||
<em>and</em> actually work on FreeBSD! I am sure that, if given
|
||||
the choice between having us answer lots of questions or continuing to
|
||||
improve FreeBSD, most of you would vote for us improving it.
|
||||
</enum>
|
||||
|
||||
<sect><heading>Using FreeBSD-current</heading>
|
||||
@ -124,7 +122,7 @@ ask! It takes far too much time to do this as a general task.
|
||||
|
||||
<item> Use ftp. The source tree for FreeBSD-current is always
|
||||
"exported" on:
|
||||
<htmlurl url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-stable"
|
||||
<htmlurl url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current"
|
||||
name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/FreeBSD-current">
|
||||
We also use `wu-ftpd' which allows compressed/tar'd grabbing
|
||||
of whole trees. e.g. you see:
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: lists.sgml,v 1.1 1996/05/16 23:18:06 mpp Exp $ -->
|
||||
<!-- $Id: lists.sgml,v 1.2 1996/07/04 01:44:31 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -54,8 +54,8 @@ and double quotes.
|
||||
name='<freebsd-questions@FreeBSD.ORG>'></tt>">
|
||||
|
||||
<!ENTITY a.stable "FreeBSD-stable mailing list
|
||||
<tt><htmlurl url='mailto:freebsd-questions@FreeBSD.ORG'
|
||||
name='<freebsd-questions@FreeBSD.ORG>'></tt>">
|
||||
<tt><htmlurl url='mailto:freebsd-stable@FreeBSD.ORG'
|
||||
name='<freebsd-stable@FreeBSD.ORG>'></tt>">
|
||||
|
||||
<!ENTITY a.majordomo "<tt><htmlurl url='mailto:majordomo@FreeBSD.ORG'
|
||||
name='<majordomo@FreeBSD.ORG>'></tt>">
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: sup.sgml,v 1.15 1996/05/16 23:18:25 mpp Exp $ -->
|
||||
<!-- $Id: sup.sgml,v 1.16 1996/07/04 01:44:33 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
@ -11,35 +11,41 @@ purpose of this document is get the beginner up and running with sup.
|
||||
|
||||
<sect1><heading>Getting setup</heading>
|
||||
|
||||
<p>Starting with FreeBSD 2.1, sup is supplied as part of the base
|
||||
system and no separate installation is required.
|
||||
|
||||
SUP gets the information it needs to run from a configuration file
|
||||
called a supfile. This file should be found in
|
||||
<tt>/usr/share/examples/sup/standard-supfile</tt> for the standard
|
||||
distributions.
|
||||
This file tells sup what collections it will be updating
|
||||
and/or installing and where they go. This supfile will sup the current source
|
||||
collection. For ports please have a look at
|
||||
<tt>/usr/share/examples/sup/ports-supfile</tt>. If you are interested
|
||||
in obtaining the cvs files that make up the source tree, refer to
|
||||
<tt>/usr/share/examples/sup/cvs-supfile</tt>. If you would rather
|
||||
track changes to the -stable release, refer to
|
||||
<tt>/usr/share/examples/sup/stable-supfile</tt>
|
||||
instead.
|
||||
<p>SUP gets the information it needs to run from a configuration file
|
||||
called a supfile. There are different example supfiles provided
|
||||
for different source releases of FreeBSD. The
|
||||
<htmlurl url="file:/usr/share/examples/sup/standard-supfile"
|
||||
name="/usr/share/examples/sup/standard-supfile"> file, for example,
|
||||
contains sup information for the latest standard FreeBSD source
|
||||
distributions - it tells sup what collections it will be updating
|
||||
and/or installing and where they go. Someone using this particular
|
||||
supfile is said to be supping <ref id="current" name="-current">.
|
||||
<p>For ports, please have a look at
|
||||
<htmlurl url="file:/usr/share/examples/sup/ports-supfile"
|
||||
name="/usr/share/examples/sup/ports-supfile">.<p>
|
||||
If you are interested in obtaining the
|
||||
<htmlurl url="http://www.freebsd.org/cgi-bin/cvsweb" name="CVS"> files
|
||||
that make up the source tree, refer to
|
||||
<htmlurl url="file:/usr/share/examples/sup/cvs-supfile"
|
||||
name="/usr/share/examples/sup/cvs-supfile">.<p>
|
||||
If you would rather track changes to the -stable branch, refer to
|
||||
<htmlurl url="file:/usr/share/examples/sup/stable-supfile"
|
||||
name="/usr/share/examples/sup/stable-supfile"> instead.
|
||||
|
||||
If you are inside the United States, you may also uncomment
|
||||
the `secure' and `eBones' collection lines to grab the DES code.
|
||||
If you are outside the
|
||||
U.S., you should NOT sup this code from sup.FreeBSD.ORG as this will
|
||||
violate U.S. export restrictions. Instead you should use the
|
||||
<tt>secure-supfile</tt> found within the above directory. This will
|
||||
<htmlurl url="file:/usr/share/examples/sup/secure-supfile"
|
||||
name="secure-supfile"> in the sup examples directory. This will
|
||||
connect you to the international sup site that contains a secure distribution.
|
||||
Any distributions you do not wish to receive can be commented out
|
||||
with a # at the beginning of the distribution line.
|
||||
|
||||
Please consult the file
|
||||
<tt>/usr/share/examples/sup/README</tt>
|
||||
<htmlurl url="file:/usr/share/examples/sup/README"
|
||||
name="/usr/share/examples/sup/README">
|
||||
for a list of alternate sup servers. The default sup server (sup.FreeBSD.ORG)
|
||||
listed in the above example files is currently overloaded and any traffic
|
||||
that can be transfered to a different host will help relieve some of
|
||||
@ -60,8 +66,8 @@ join the &a.current . You should also be sure to read
|
||||
<ref id="current" name="Staying current with FreeBSD">
|
||||
for important information on just what we can and cannot do for you as
|
||||
a -current user. If you are using the stable-supfile, please
|
||||
join the &a.stable and read <ref id="stable" name="Staying stable with FreeBSD">
|
||||
.
|
||||
join the &a.stable and read
|
||||
<ref id="stable" name="Staying stable with FreeBSD">.
|
||||
|
||||
<sect1><heading>Description of FreeBSD SUP distributions</heading>
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user