diff options
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ/applications.sgml | 18 | ||||
| -rw-r--r-- | FAQ/hackers.sgml | 17 | ||||
| -rw-r--r-- | FAQ/hardware.sgml | 8 | ||||
| -rw-r--r-- | FAQ/preface.sgml | 42 |
4 files changed, 46 insertions, 39 deletions
diff --git a/FAQ/applications.sgml b/FAQ/applications.sgml index 542fdb54c9..fca8aa6acf 100644 --- a/FAQ/applications.sgml +++ b/FAQ/applications.sgml @@ -1,4 +1,4 @@ -<!-- $Id: applications.sgml,v 1.8 1998-11-22 14:03:32 jkh Exp $ --> +<!-- $Id: applications.sgml,v 1.9 1999-01-21 01:49:12 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <sect> @@ -14,7 +14,7 @@ <ref id="mailing" name="mailing list"> for periodic updates on new entries. - <p>Most ports should be available for both the 2.2 and 3.0 + <p>Most ports should be available for the 2.2, 3.x and 4.0 branches, and many of them should work on 2.1.x systems as well. Each time a FreeBSD release is made, a snapshot of the ports tree at the time of release in also included in the @@ -37,13 +37,13 @@ of FreeBSD at the following locations: <descrip> - <tag>for 2.2.7-release/2.2-stable</tag> - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.2.7/" - name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-2.2.7/"> + <tag>for 2.2.8-release/2.2.8-stable</tag> + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-2.2.8/" + name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-2.2.8/"> - <tag>for 3.0-current</tag> - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-3.0/" - name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/packages-3.0/"> + <tag>for 4.0-current</tag> + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-3.0/" + name="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/ports/i386/packages-3.0/"> </descrip> <p>or your nearest local mirror site. @@ -57,7 +57,7 @@ <sect1> <heading>Where do I find libc.so.3.0?</heading> - <p>You are trying to run a package for 2.2/3.0 on a 2.1.x + <p>You are trying to run a package for 2.2/3.x/4.0 on a 2.1.x system. Please take a look at the previous section and get the correct port/package for your system. diff --git a/FAQ/hackers.sgml b/FAQ/hackers.sgml index 9394caff52..0d1bdd4417 100644 --- a/FAQ/hackers.sgml +++ b/FAQ/hackers.sgml @@ -1,4 +1,4 @@ -<!-- $Id: hackers.sgml,v 1.10 1999-01-18 20:12:22 des Exp $ --> +<!-- $Id: hackers.sgml,v 1.11 1999-01-21 01:49:12 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <sect> @@ -13,9 +13,9 @@ <url url="http://www.freebsd.org/cgi/cvsweb.cgi" name="CVS Repository">: <itemize> - <item><bf/RELENG_2_1_0/ AKA <bf/2.1-stable/ AKA <bf/"2.1 branch"/ <item><bf/RELENG_2_2/ AKA <bf/2.2-stable/ AKA <bf/"2.2 branch"/ - <item><bf/HEAD/ AKA <bf/-current/ AKA <bf/3.0-current/ + <item><bf/RELENG_3/ AKA <bf/3.x-stable/ AKA <bf/"3.0 branch"/ + <item><bf/HEAD/ AKA <bf/-current/ AKA <bf/4.0-current/ </itemize> <p><bf/HEAD/ is not an actual branch tag, like the other two, it's @@ -23,12 +23,15 @@ <em/"the current, non-branched development stream"/ which we simply refer to as <bf/-current/. - <p>Right now, <bf/-current/ is the 3.0 development stream and the - <bf/2.2-stable/ branch, <bf/RELENG_2_2/, forked off from - <bf/-current/ in November 1996. + <p>Right now, <bf/-current/ is the 4.0 development stream and the + <bf/3.0-stable/ branch, <bf/RELENG_3/, forked off from + <bf/-current/ in Jan 1999. + + <p>The <bf/2.2-stable/ branch, <bf/RELENG_2_2/, departed -current in + November 1996. <p>The <bf/2.1-stable/ branch, <bf/RELENG_2_1_0/, departed -current in - September of 1994. + September of 1994. This branch has been fully retired. <sect1> <heading> diff --git a/FAQ/hardware.sgml b/FAQ/hardware.sgml index 4f997716a3..851457b77a 100644 --- a/FAQ/hardware.sgml +++ b/FAQ/hardware.sgml @@ -1,4 +1,4 @@ -<!-- $Id: hardware.sgml,v 1.14 1998-12-06 05:14:56 jkh Exp $ --> +<!-- $Id: hardware.sgml,v 1.15 1999-01-21 01:49:12 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <sect> @@ -55,7 +55,7 @@ <p>ATAPI (IDE) Zip drives are supported in FreeBSD 2.2.6 and later releases. - <p>FreeBSD 3.0-CURRENT contains support for the parallel Zip + <p>FreeBSD 3.0-STABLE contains support for the parallel Zip However, you will need to build a new kernel with support for ppbus (Parallel Port Bus) in order to use the Zip. See the LINT configuration file for examples. @@ -340,7 +340,7 @@ </heading> <p>The newer AIC789x series Adaptec chips are supported under the CAM SCSI - framework making it's debut in 3.0. Patches against 3.0-CURRENT and 2.2-STABLE + framework which made it's debut in 3.0. Patches against 2.2-STABLE are in <url url="ftp://ftp.freebsd.org/pub/FreeBSD/development/cam/" name="ftp://ftp.freebsd.org/pub/FreeBSD/development/cam/">. A CAM-enhanced boot floppy is available at <url url="http://www.freebsd.org/~abial/cam-boot/" name="http://www.freebsd.org/~abial/cam-boot/">. In both cases read the README before @@ -402,7 +402,7 @@ <heading>Does FreeBSD support Symmetric Multiproccessing (SMP)? </heading> - <p>SMP is supported in 3.0-CURRENT only. + <p>SMP is supported in 3.0-STABLE and later releases only. </sect> diff --git a/FAQ/preface.sgml b/FAQ/preface.sgml index 4a66f9c339..40466d0e46 100644 --- a/FAQ/preface.sgml +++ b/FAQ/preface.sgml @@ -1,4 +1,4 @@ -<!-- $Id: preface.sgml,v 1.26 1999-01-19 04:53:51 jkh Exp $ --> +<!-- $Id: preface.sgml,v 1.27 1999-01-21 01:49:12 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <sect> @@ -98,19 +98,19 @@ versions are one and the same, but it shouldn't be long before the <bf>-current</bf> branch is polished enough for general release. - <p>This is not to say that a 3.0-current snapshot is unusable for + <p>This is not to say that a 3.0-STABLE release is unusable for business services, and many people who need some 3.0 specific feature (newer compiler technology, faster networking code, etc) have decided to take a chance with it with very good results. We simply do not - wish to "certify" 3.0 as mission-worthy until it's been better - shaken-out. + wish to "certify" 3.0 as mission-worthy until it's been released + as 3.1-RELEASE in February, 1999. <sect1> <heading>What is FreeBSD-current?<label id="current"></heading> <p><url url="../handbook/current.html" name="FreeBSD-current"> is the development version of the operating system, which will in due - course become 3.0.1-RELEASE. As such, it is really only of interest + course become 4.0-RELEASE. As such, it is really only of interest to developers working on the system and die-hard hobbyists. See the <url url="../handbook/current.html" name="relevant section"> in the <url url="../handbook/handbook.html" name="handbook"> for @@ -152,7 +152,7 @@ <p>Snapshot releases are directly available from <url url="ftp://current.freebsd.org/pub/FreeBSD/"> and are generated, - on the average, once a day for both the 3.0-current and 2.2-stable + on the average, once a day for both the 4.0-current and 3.0-stable branches. <sect1> @@ -166,7 +166,7 @@ and other commercial enterprises for whom sudden shifts or experimental features are quite undesirable). The other branch was <url url="../handbook/current.html" name="-current">, which - essentially has been one unbroken line leading towards 3.0-RELEASE + essentially has been one unbroken line leading towards 4.0-RELEASE (and beyond) since 2.0 was released. If a little ASCII art would help, this is how it looks: @@ -190,20 +190,19 @@ 3.0.0-RELEASE (Oct 1998) | | [3.0-stable] - *BRANCH* 3.0.1 (Feb 1999) -> ... future 3.0.x releases ... + *BRANCH* 3.1 (Feb 1999) -> ... future 3.x releases ... | | \|/ + - [3.1-current continues] + [4.0-current continues] </verb> - <p>The -current branch is slowly progressing towards 3.0.1 and beyond, + <p>The -current branch is slowly progressing towards 4.0 and beyond, the previous 2.2-stable branch having just retired with the release - of 2.2.8. 3.0-current will continue to be where the active development - takes place up until the actual release of 3.0.1 in early 1999. At that - point, 3.0 will become yet another branch and 3.1-current will become - the next "current branch". + of 2.2.8. 3.0-stable has now replaced it, the next release coming + up with 3.1 in early 1999. 4.0-current is now the "current branch", + with the first 4.0 releases appearing in Q1 2000. <sect1> <heading>When are FreeBSD releases made?</heading> @@ -259,12 +258,12 @@ name="FreeBSD FTP site">: <itemize> - <item>For the current 2.2-stable release, 2.2.8R see the - <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/2.2.8-RELEASE/" + <item>For the current 2.2-stable release, 2.2.8R, see the + <url url="ftp://ftp.FreeBSD.ORG/pub/FreeBSD/releases/2.2.8-RELEASE/" name="2.2.8-RELEASE"> directory. - <item>For the current 3.0-current release, 3.0-SNAP, see the - <url url="ftp://current.freebsd.org/pub/FreeBSD/" name="3.0"> directory. + <item>For the current 3.0-stable release, 3.0-RELEASE, see the + <url url="ftp://current.freebsd.org/pub/FreeBSD/releases/3.0-RELEASE/" name="3.0-RELEASE"> directory. <item><url url="ftp://releng22.freebsd.org/pub/FreeBSD/" name="2.2 Snapshot"> releases are made once a day along the @@ -274,8 +273,13 @@ those strictly necessary for security or reliability enhancements are now made. + <item><url url="ftp://releng30.freebsd.org/pub/FreeBSD/" + name="3.0 Snapshot"> releases are also made once a day along the + RELENG_3 branch (post 3.0-release) as it continues on its way + towards 3.1-RELEASE. + <item><url url="ftp://current.freebsd.org/pub/FreeBSD/" - name="3.0 Snapshot">releases are also made once a day for the + name="4.0 Snapshot">releases are made once a day for the <ref id="current" name="-current"> branch, these being of service purely to bleeding-edge testers and developers. </itemize> |