os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Make some items "hot" that should be, eliminate typos and macro expansion

Browse source 
bogons.
This commit is contained in:
Jordan K. Hubbard 1996-07-04 01:44:33 +00:00
parent 6abf6c3655
commit 624a400665
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=403
4 changed files with 24 additions and 21 deletions

18
handbook/current.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: current.sgml,v 1.11 1996-05-16 23:17:52 mpp Exp $ -->
<!-- $Id: current.sgml,v 1.12 1996-07-04 01:44:31 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
@ -10,7 +10,7 @@
THE FREEBSD CURRENT POLICY
Last updated: $Date: 1996-05-16 23:17:52 $
Last updated: $Date: 1996-07-04 01:44:31 $
This document attempts to explain the rationale behind
FreeBSD-current, what you should expect should you decide to run it,
@ -83,9 +83,9 @@ ask! It takes far too much time to do this as a general task.
<sect><heading>Using FreeBSD-current</heading>
<p><enum> <item> Join the freebsd-current and cvs-all
mailing lists. This is not just a good idea, it is
<em>essential</em>. If you are not on the &a.current, you
<p><enum> <item> Join the &a.current and the &a.cvsall .
This is not just a good idea, it is <em>essential</em>.
If you are not on the <em>FreeBSD-current</em> mailing list you
will not see the comments that people are making about the
current state of the system and thus will probably end up stumbling
over a lot of problems that others have already found and
@ -94,7 +94,7 @@ ask! It takes far too much time to do this as a general task.
Before you rebuild <tt>/usr/src</tt>, you <em>must</em>
rebuild the kernel or your system will crash horribly!").
The cvs-all mailing list will allow you to see the commit log
The <em>cvs-all</em> mailing list will allow you to see the commit log
entry for each change as it is made along with any pertinent
information on possible side-effects.
@ -111,12 +111,12 @@ ask! It takes far too much time to do this as a general task.
three ways:
<enum>
<item> Using the CTM facility described below. Unless you
<item> Use the <ref id="ctm" name="CTM"> facility. Unless you
have a good TCP/IP connection at a flat rate, this is
the way to do it.
<item> Use the CMU `sup' program (Software Update
Protocol), also described below.
<item> Use the CMU <ref id="sup"> program (Software Update
Protocol).
This is the second most recommended method, since it allows
you to grab the entire collection once and then only what has
changed from then on. Many people run sup from cron

6
handbook/lists.sgml
View file

@ -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 -->
<!--
@ -13,6 +13,10 @@ and double quotes.
<tt><htmlurl url='mailto:freebsd-announce@FreeBSD.ORG'
name='&lt;freebsd-announce@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.cvsall "FreeBSD CVS commit message mailing list
<tt><htmlurl url='mailto:cvs-all@FreeBSD.ORG'
name='&lt;cvs-all@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.doc "FreeBSD documentation project mailing list
<tt><htmlurl url='mailto:freebsd-doc@FreeBSD.ORG'
name='&lt;freebsd-doc@FreeBSD.ORG&gt;'></tt>">

14
handbook/stable.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: stable.sgml,v 1.2 1996-05-16 23:18:19 mpp Exp $ -->
<!-- $Id: stable.sgml,v 1.3 1996-07-04 01:44:32 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
@ -10,7 +10,7 @@
THE FREEBSD STABLE POLICY
Last updated: $Date: 1996-05-16 23:18:19 $
Last updated: $Date: 1996-07-04 01:44:32 $
This document attempts to explain the rationale behind
FreeBSD-stable, what you should expect should you decide to run it,
@ -45,7 +45,7 @@ next section).
<sect><heading>Using FreeBSD-stable</heading>
<p><enum><item> Join the freebsd-stable mailing list. This will
<p><enum><item> Join the &a.stable . This will
keep you informed of build-dependencies that may appear in
<em>stable</em> or any other issues requring special attention.
Developers will also make announcements in this mailing list when
@ -65,12 +65,12 @@ next section).
three ways:
<enum>
<item> Using the CTM facility described below. Unless you
<item> Use the <ref id="ctm" name="CTM"> facility. Unless you
have a good TCP/IP connection at a flat rate, this is
the way to do it.
<item> Use the CMU `sup' program (Software Update
Protocol), also described below.
<item> Use the CMU <ref id="sup"> program (Software Update
Protocol).
This is the second most recommended method, since it allows
you to grab the entire collection once and then only what has
changed from then on. Many people run sup from cron
@ -102,7 +102,7 @@ next section).
<item> Before compiling stable, read the Makefile in /usr/src
carefully. You should at least run a `make world' the first time
through as part of the upgrading process.
Reading freebsd-stable will keep you up-to-date on other bootstrapping
Reading the &a.stable will keep you up-to-date on other bootstrapping
procedures that sometimes become necessary as we move towards the next
release.
</enum>

7
handbook/sup.sgml
View file

@ -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 -->
@ -56,12 +56,11 @@ like so:
</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 mailing list. You should also be sure to read
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 mailing list 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>