Update to reflect current affairs.

This commit is contained in:
Jordan K. Hubbard 1997-10-12 16:21:36 +00:00
parent b09dc169b7
commit 90a93ec643
3 changed files with 18 additions and 16 deletions

View file

@ -50,11 +50,12 @@ from "John Smith <jsm@bar.com>" in the simple, no-frills registration
case. If you do not have an email address, some sort of postal
address will serve the same purpose.
If you also wish to receive the upcoming FreeBSD Newsletter (soon to
published and distributed free of charge by Walnut Creek CDROM) in
printed form, then you must specify some sort of postal address.
Likewise, if you elect to receive the email version then you should
specify a valid Email address.
If you also wish to receive the FreeBSD Newsletter, published and
distributed free of charge by Walnut Creek CDROM in printed form,
then you must specify some sort of postal address. Likewise, if you
elect to receive notification on the email version then you should
specify a valid Email address. Back-issues of the FreeBSD newsletter
are available at http://ftp.freebsd.org/pub/FreeBSD/newsletter/
Should you wish to unsubscribe to the FreeBSD Newsletter or otherwise
de-register yourself at a later time, you can simply send mail to

View file

@ -1,24 +1,24 @@
Welcome to the 2.1.x (or 2.0.5) -> 2.1.7 upgrade procedure!
Welcome to the 2.2.5 upgrade procedure!
It must first be said that this upgrade DOES NOT take a particularly
sophisticated approach to the upgrade problem, it being more a
question of providing what seemed "good enough" at the time. A truly
polished upgrade that deals properly with the broad spectrum of
installed 2.0.5 / 2.1.x systems would be nice to have, but until that
gets written what you get is this - the brute-force approach!
installed 2.x systems would be nice to have, but until that gets
written what you get is this - the brute-force approach!
What this upgrade will attempt to do is best summarized thusly:
1. fsck and mount all file systems chosen in the label editor.
2. Ask for a location to preserve your /etc directory into and do so.
2. Ask for a location to preserve your /etc directory into.
3. Extract all selected distributions on top of your existing system.
4. Copy certain obvious files back from the preserved /etc, leaving the
rest of the /etc file merge up to the user.
5. Drop user in a shell so that they may perform that merge before
rebooting into the new system.
And that's it! This "upgrade" is not going to hold your hand in all
major respects, it's simply provided to make one PART of the upgrade
And that's it! This "upgrade" is not going to hold your hand to any
major degree, it's simply provided to make one PART of the upgrade
easier.
IMPORTANT NOTE: What this upgrade procedure may also do, in fact, is

View file

@ -50,11 +50,12 @@ from "John Smith <jsm@bar.com>" in the simple, no-frills registration
case. If you do not have an email address, some sort of postal
address will serve the same purpose.
If you also wish to receive the upcoming FreeBSD Newsletter (soon to
published and distributed free of charge by Walnut Creek CDROM) in
printed form, then you must specify some sort of postal address.
Likewise, if you elect to receive the email version then you should
specify a valid Email address.
If you also wish to receive the FreeBSD Newsletter, published and
distributed free of charge by Walnut Creek CDROM in printed form,
then you must specify some sort of postal address. Likewise, if you
elect to receive notification on the email version then you should
specify a valid Email address. Back-issues of the FreeBSD newsletter
are available at http://ftp.freebsd.org/pub/FreeBSD/newsletter/
Should you wish to unsubscribe to the FreeBSD Newsletter or otherwise
de-register yourself at a later time, you can simply send mail to