From 03c00df3ce76dc9b9273850e972c4e222649bc75 Mon Sep 17 00:00:00 2001 From: "Bruce A. Mah" Date: Fri, 5 Oct 2001 22:03:35 +0000 Subject: [PATCH] Add an abstract for this document, flesh out the introduction a bit, and fix up the upgrading section. While I'm here, delete some of the SGML comments that were left-over from merging the source files. MFC after: 1 day --- .../doc/en_US.ISO8859-1/relnotes/article.sgml | 66 +++++++++++-------- .../en_US.ISO8859-1/relnotes/common/new.sgml | 66 +++++++++++-------- 2 files changed, 78 insertions(+), 54 deletions(-) diff --git a/release/doc/en_US.ISO8859-1/relnotes/article.sgml b/release/doc/en_US.ISO8859-1/relnotes/article.sgml index d6380070ce86..ece5039ddaf1 100644 --- a/release/doc/en_US.ISO8859-1/relnotes/article.sgml +++ b/release/doc/en_US.ISO8859-1/relnotes/article.sgml @@ -12,17 +12,21 @@ - + + The release notes for &os; &release.current; contain a summary + of the changes made in the &os; base system since &release.prev;. + Both changes for kernel and userland are listed, as well as + applicable security advisories that were issued since the last + release. Some brief remarks on upgrading are also presented. + Introduction This document contains the release notes for &os; &release.current; on the &arch; hardware platform. It describes new features of &os; - that have been added (or changed) since &release.prev;. + that have been added (or changed) since &release.prev;. It also + provides some notes on upgrading from previous versions of &os;. - - What's New This section describes the most user-visible new or changed - features in &os; since &release.prev;. All changes + features in &os; since &release.prev;. Typical release note items + document new drivers or hardware support, new commands or options, + major bugfixes, or contributed software upgrades. Security + advisories issued after &release.prev; are also listed. In general, changes described here are unique to the &release.branch; branch unless specifically marked as &merged; features. @@ -2383,26 +2381,35 @@ - - Upgrading from previous releases of &os; - If you're upgrading from a previous release of &os;, - most likely it's 4.X and there may be some issues affecting you, - depending of course on your chosen method of upgrading. There - are two popular ways of upgrading &os; distributions: + If you're upgrading from a previous release of &os;, you + generally will have three options: - - Using sources, via /usr/src + Using the binary upgrade option of &man.sysinstall.8;. + This option is perhaps the quickest, although it presumes + that your installation of &os; uses no special compilation + options. - Using the binary upgrade option of &man.sysinstall.8;. + Performing a complete reinstall of &os;. Technically, + this is not an upgrading method, and in any case is usually less + convenient than a binary upgrade, in that it requires you to + manually backup and restore the contents of + /etc. However, it may be useful in + cases where you want (or need) to change the partitioning of + your disks. + + + From source code in /usr/src. This + route is more flexible, but requires more disk space, time, + and more technical expertise. Upgrading from very old + versions of &os; may be problematic; in cases like this, it + is usually more effective to perform a binary upgrade or a + complete reinstall. @@ -2420,5 +2427,10 @@ url="http://www.FreeBSD.org/handbook/">FreeBSD Handbook. + + Upgrading &os; should, of course, only be attempted after + backing up all data and configuration + files. + diff --git a/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml b/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml index d6380070ce86..ece5039ddaf1 100644 --- a/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml +++ b/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml @@ -12,17 +12,21 @@ - + + The release notes for &os; &release.current; contain a summary + of the changes made in the &os; base system since &release.prev;. + Both changes for kernel and userland are listed, as well as + applicable security advisories that were issued since the last + release. Some brief remarks on upgrading are also presented. + Introduction This document contains the release notes for &os; &release.current; on the &arch; hardware platform. It describes new features of &os; - that have been added (or changed) since &release.prev;. + that have been added (or changed) since &release.prev;. It also + provides some notes on upgrading from previous versions of &os;. - - What's New This section describes the most user-visible new or changed - features in &os; since &release.prev;. All changes + features in &os; since &release.prev;. Typical release note items + document new drivers or hardware support, new commands or options, + major bugfixes, or contributed software upgrades. Security + advisories issued after &release.prev; are also listed. In general, changes described here are unique to the &release.branch; branch unless specifically marked as &merged; features. @@ -2383,26 +2381,35 @@ - - Upgrading from previous releases of &os; - If you're upgrading from a previous release of &os;, - most likely it's 4.X and there may be some issues affecting you, - depending of course on your chosen method of upgrading. There - are two popular ways of upgrading &os; distributions: + If you're upgrading from a previous release of &os;, you + generally will have three options: - - Using sources, via /usr/src + Using the binary upgrade option of &man.sysinstall.8;. + This option is perhaps the quickest, although it presumes + that your installation of &os; uses no special compilation + options. - Using the binary upgrade option of &man.sysinstall.8;. + Performing a complete reinstall of &os;. Technically, + this is not an upgrading method, and in any case is usually less + convenient than a binary upgrade, in that it requires you to + manually backup and restore the contents of + /etc. However, it may be useful in + cases where you want (or need) to change the partitioning of + your disks. + + + From source code in /usr/src. This + route is more flexible, but requires more disk space, time, + and more technical expertise. Upgrading from very old + versions of &os; may be problematic; in cases like this, it + is usually more effective to perform a binary upgrade or a + complete reinstall. @@ -2420,5 +2427,10 @@ url="http://www.FreeBSD.org/handbook/">FreeBSD Handbook. + + Upgrading &os; should, of course, only be attempted after + backing up all data and configuration + files. +