Delete all references to sup.
This commit is contained in:
parent
b204fc857e
commit
dae458199b
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=1833
6 changed files with 22 additions and 192 deletions
|
@ -1,4 +1,4 @@
|
|||
# $Id: Makefile,v 1.26 1997-05-17 04:00:26 brian Exp $
|
||||
# $Id: Makefile,v 1.27 1997-08-18 00:03:51 jdp Exp $
|
||||
|
||||
SGMLOPTS=-links
|
||||
SRCS= authors.sgml basics.sgml bibliography.sgml boothelp.sgml
|
||||
|
@ -13,7 +13,7 @@ SRCS+= mirrors.sgml nfs.sgml nutshell.sgml pgpkeys.sgml policies.sgml
|
|||
SRCS+= porting.sgml ports.sgml ppp.sgml printing.sgml
|
||||
SRCS+= quotas.sgml relnotes.sgml routing.sgml russian.sgml
|
||||
SRCS+= serial.sgml scsi.sgml sections.sgml sio.sgml skey.sgml slipc.sgml
|
||||
SRCS+= slips.sgml stable.sgml submitters.sgml sup.sgml synching.sgml
|
||||
SRCS+= slips.sgml stable.sgml submitters.sgml synching.sgml
|
||||
SRCS+= term.sgml userppp.sgml uart.sgml linuxemu.sgml
|
||||
|
||||
.include <bsd.sgml.mk>
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: cvsup.sgml,v 1.24 1997-07-31 09:35:49 asami Exp $ -->
|
||||
<!-- $Id: cvsup.sgml,v 1.25 1997-08-18 00:03:53 jdp Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect1><heading>CVSup<label id="cvsup"></heading>
|
||||
|
@ -13,7 +13,7 @@ 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.
|
||||
|
||||
<p>CVSup uses the so-called "pull" model of updating. Under the pull
|
||||
<p>CVSup uses the so-called <em>pull</em> 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
|
||||
|
@ -27,11 +27,11 @@ user's machine, and the server "cvsupd" which runs at each of the
|
|||
FreeBSD mirror sites.
|
||||
|
||||
<p>As you read the FreeBSD documentation and mailing lists, you may
|
||||
see references to <ref id="sup">. Sup was the predecessor to CVSup,
|
||||
see references to <em>sup</em>. Sup was the predecessor of CVSup,
|
||||
and it served a similar purpose. CVSup is in used in much 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, however, because CVSup is both faster and more flexible.
|
||||
project, because CVSup is both faster and more flexible.
|
||||
|
||||
<sect2><heading>Installation<label id="cvsup:install"></heading>
|
||||
|
||||
|
@ -164,7 +164,7 @@ name="FreeBSD-current">.
|
|||
<itemize>
|
||||
<item>Which files do you want to receive?<label id="cvsup:config:files">
|
||||
|
||||
<p>As with sup, the files available via CVSup are organized into named
|
||||
<p>The files available via CVSup are organized into named
|
||||
groups called "collections". The collections that are available are
|
||||
described <ref id="cvsup:collec" name="here">.
|
||||
In this example, we wish to receive the
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: firewalls.sgml,v 1.17 1997-02-22 12:58:30 peter Exp $ -->
|
||||
<!-- $Id: firewalls.sgml,v 1.18 1997-08-18 00:03:54 jdp Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Firewalls<label id="firewalls"></heading>
|
||||
|
@ -412,13 +412,6 @@ filtering:
|
|||
ipfw add deny from any to my.org/28 6000 setup
|
||||
</verb></tscreen>
|
||||
|
||||
To allow access to the SUP server on <bf>sup.FreeBSD.ORG</bf>, use the
|
||||
following command:
|
||||
|
||||
<tscreen><verb>
|
||||
ipfw add accept from any to sup.FreeBSD.ORG 871
|
||||
</verb></tscreen>
|
||||
|
||||
To see the accounting records:
|
||||
<tscreen><verb>
|
||||
ipfw -a list
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: sections.sgml,v 1.24 1997-05-02 02:20:25 ache Exp $ -->
|
||||
<!-- $Id: sections.sgml,v 1.25 1997-08-18 00:03:56 jdp Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!-- Entities containing all the pieces of the handbook are -->
|
||||
|
@ -56,7 +56,6 @@
|
|||
<!ENTITY slipc SYSTEM "slipc.sgml">
|
||||
<!ENTITY slips SYSTEM "slips.sgml">
|
||||
<!ENTITY submitters SYSTEM "submitters.sgml">
|
||||
<!ENTITY sup SYSTEM "sup.sgml">
|
||||
<!ENTITY synching SYSTEM "synching.sgml">
|
||||
<!ENTITY uart SYSTEM "uart.sgml">
|
||||
<!ENTITY userppp SYSTEM "userppp.sgml">
|
||||
|
|
|
@ -1,164 +0,0 @@
|
|||
<!-- $Id: sup.sgml,v 1.30 1997-07-31 09:35:52 asami Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
|
||||
<sect1><heading>SUP<label id="sup"></heading>
|
||||
|
||||
<p><em>Contributed by &a.jkh; and &a.gclarkii;.</em>
|
||||
|
||||
SUP is a network based software update tool developed at CMU. The
|
||||
purpose of this document is get the beginner up and running with sup.
|
||||
|
||||
<sect2><heading>Configuration<label id="sup:setup"></heading>
|
||||
|
||||
<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
|
||||
<url 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
|
||||
<url url="file:/usr/share/examples/sup/ports-supfile"
|
||||
name="/usr/share/examples/sup/ports-supfile">.<p>
|
||||
If you are interested in obtaining the
|
||||
<url url="http://www.freebsd.org/cgi/cvsweb.cgi" name="CVS"> files
|
||||
that make up the source tree, refer to
|
||||
<url 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
|
||||
<url 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
|
||||
<url 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
|
||||
<url 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
|
||||
the strain.
|
||||
|
||||
Once this is setup, you are ready to go. To start sup type:
|
||||
<verb>
|
||||
sup supfile
|
||||
</verb>
|
||||
If you wish to see what sup is doing "verbosely", give it the -v option,
|
||||
like so:
|
||||
<verb>
|
||||
sup -v supfile
|
||||
</verb>
|
||||
Thats all there is to it! Remember that if you are running current,
|
||||
which is what you will have if you sup with the standard-supfile, please
|
||||
join the &a.current . You should also be sure to read
|
||||
<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">.
|
||||
|
||||
<sect2><heading>Distributions<label id="sup:dists">
|
||||
</heading>
|
||||
|
||||
<p>For the main FreeBSD distribution using the standard-supfile:
|
||||
<verb>
|
||||
src-base: /usr/src/... misc files at the top of /usr/src
|
||||
src-bin: /usr/src/bin user and system binaries
|
||||
src-contrib: /usr/src/contrib contributed software
|
||||
src-secure: /usr/src/secure DES Sources (US/Canada ONLY)
|
||||
src-eBones: /usr/src/eBones Kerberos and DES (US/Canada ONLY)
|
||||
src-etc: /usr/src/etc system files
|
||||
src-games: /usr/src/games games
|
||||
src-gnu: /usr/src/gnu sources under the GNU Public License
|
||||
src-include: /usr/src/include include files
|
||||
src-sys: /usr/src/sys kernel sources
|
||||
src-lib: /usr/src/lib libraries
|
||||
src-libexec: /usr/src/libexec system binaries
|
||||
src-release: /usr/src/release sources required to build a release
|
||||
src-share: /usr/src/share various shared resources
|
||||
src-sbin: /usr/src/sbin single user system binaries
|
||||
src-tools: /usr/src/tools various management tools
|
||||
src-usrbin: /usr/src/usr.bin user binaries
|
||||
src-usrsbin: /usr/src/usr.sbin system binaries
|
||||
</verb>
|
||||
|
||||
<p>For the international FreeBSD distribution using the secure-supfile:
|
||||
<verb>
|
||||
src-secure: /usr/src/secure DES Sources
|
||||
src-eBones: /usr/src/eBones Kerberos and DES
|
||||
</verb>
|
||||
|
||||
<p>There is also a collection including all of the above, except for
|
||||
either (domestic or international) versions of the export-restricted
|
||||
software (i.e., <tt>src-secure</tt> and <tt>src-eBones</tt>
|
||||
collections):
|
||||
<verb>
|
||||
src-all: /usr/src the whole operating system (almost)
|
||||
</verb>
|
||||
|
||||
<p>And for the ports collection:
|
||||
<verb>
|
||||
ports-base: /usr/ports/... misc files at the top of /usr/ports
|
||||
ports-archivers: /usr/ports/archivers archiving tools
|
||||
ports-astro: /usr/ports/astro astronomical ports
|
||||
ports-audio: /usr/ports/audio sound support
|
||||
ports-benchmarks: /usr/ports/benchmarks benchmarks
|
||||
ports-cad: /usr/ports/cad CAD tools
|
||||
ports-chinese: /usr/ports/chinese Chinese support
|
||||
ports-comms: /usr/ports/comms communication software
|
||||
ports-converters: /usr/ports/converters character code converters
|
||||
ports-databases: /usr/ports/databases databases
|
||||
ports-devel: /usr/ports/devel development utilities
|
||||
ports-editors: /usr/ports/editors editors
|
||||
ports-emulators: /usr/ports/emulators emulators for other OSes
|
||||
ports-games: /usr/ports/games games
|
||||
ports-german: /usr/ports/german German support
|
||||
ports-graphics: /usr/ports/graphics various graphics utilities
|
||||
ports-japanese: /usr/ports/japanese Japanese support
|
||||
ports-korean: /usr/ports/korean Korean support
|
||||
ports-lang: /usr/ports/lang programming languages
|
||||
ports-mail: /usr/ports/mail mail software
|
||||
ports-math: /usr/ports/math numerical computation software
|
||||
ports-mbone: /usr/ports/mbone MBone applications
|
||||
ports-misc: /usr/ports/misc miscellaneous utilities
|
||||
ports-net: /usr/ports/net networking software
|
||||
ports-news: /usr/ports/news USENET news software
|
||||
ports-plan9: /usr/ports/plan9 various programs from Plan9
|
||||
ports-print: /usr/ports/print printing software
|
||||
ports-russian: /usr/ports/russian Russian support
|
||||
ports-security: /usr/ports/security ``security'' utilities, for better or for worse
|
||||
ports-shells: /usr/ports/shells various UN*X shells
|
||||
ports-sysutils: /usr/ports/sysutils system utilities
|
||||
ports-textproc: /usr/ports/textproc text processing utilities (does not include desktop publishing)
|
||||
ports-vietnamese: /usr/ports/vietnamese Vietnamese support
|
||||
ports-www: /usr/ports/www software related to the world wide web
|
||||
ports-x11: /usr/ports/x11 X11 software
|
||||
</verb>
|
||||
|
||||
<p>There is also a collection including all of the above:
|
||||
<verb>
|
||||
ports-all: /usr/ports the whole ports tree
|
||||
</verb>
|
||||
|
||||
<!-- The following is currently not available (and probably will never return)
|
||||
<p>If you want to keep updated on the original source of the ports,
|
||||
you can also add this to your supfile. But note that this collection
|
||||
is <em>enormous</em>, and unless you are an ftp site mirroring the
|
||||
entire FreeBSD tree (but cannot use ``mirror'' for some reason), you
|
||||
(and us) are much better off not using sup to collect these:
|
||||
<verb>
|
||||
ports-distfiles: /usr/ports/distfiles original tarballs
|
||||
</verb>
|
||||
-->
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $Id: synching.sgml,v 1.11 1997-08-12 09:18:29 asami Exp $ -->
|
||||
<!-- $Id: synching.sgml,v 1.12 1997-08-18 00:03:59 jdp Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>Synchronizing Source Trees over the Internet<label id="synching"></heading>
|
||||
|
@ -7,7 +7,7 @@
|
|||
|
||||
<!--
|
||||
|
||||
Last updated: $Date: 1997-08-12 09:18:29 $
|
||||
Last updated: $Date: 1997-08-18 00:03:59 $
|
||||
|
||||
This document tries to describe the various ways in which a user may
|
||||
use the internet to keep development sources in synch.
|
||||
|
@ -18,11 +18,14 @@ to stay up-to-date with any given area of the FreeBSD project sources,
|
|||
or all areas, depending on what interests you. The primary
|
||||
services we offer are CVSup and CTM.
|
||||
|
||||
<p><bf>CVSup</bf> is the new kid on the block, it does everything that sup
|
||||
did and more, doing it also far more efficiently in terms of its demands
|
||||
on server disk space and network resources. Because of this, CVSup has
|
||||
largely replaced <ref id="sup"> in the FreeBSD Project. Like sup, it also
|
||||
operates on a <em>pull</em> synchronization model.
|
||||
<p><bf>CVSup</bf> uses the <em>pull</em> model of updating. The
|
||||
user (or a cron script) invokes the <tt>cvsup</tt> program, and it
|
||||
interacts with a <tt>cvsupd</tt> server somewhere to bring your files
|
||||
up to date. The updates you receive are up-to-the-minute and you get
|
||||
them when, and only when, you want them. You can easily restrict your
|
||||
updates to the specific files or directories that are of interest to
|
||||
you. Updates are generated on the fly by the server, according to
|
||||
what you have and what you want to have.
|
||||
|
||||
<p><bf>CTM</bf>, on the other hand, does not interactively compare
|
||||
the sources you have with those on the master archive. Instead, a script
|
||||
|
@ -35,16 +38,15 @@ and apply the changes to the user's copy of the sources. This process is
|
|||
far more efficient than CVSup, and places less strain on our server resources
|
||||
since it is a <em>push</em> rather than a <em>pull</em> model.
|
||||
|
||||
<p>There are other trade-offs, of course. With CVSup, you can also
|
||||
inadvertently wipe out portions of your archive and CVSup will detect
|
||||
<p>There are other trade-offs, of course. If you
|
||||
inadvertently wipe out portions of your archive, CVSup will detect
|
||||
and rebuild the damaged portions for you. CTM won't do this, and if
|
||||
you wipe some portion of your source tree out (and don't have it backed
|
||||
up) then you will have to start from scratch (from the most recent CVS
|
||||
"base delta") and rebuild it all.
|
||||
|
||||
For more information on CTM, CVSup or the now largely-obsolete sup, please
|
||||
For more information on CTM and CVSup, please
|
||||
see one of the following sections:
|
||||
|
||||
&ctm;
|
||||
&cvsup;
|
||||
⊃
|
||||
|
|
Loading…
Reference in a new issue