From owner-freebsd-doc Tue Apr 4 13:50:51 2000 Delivered-To: freebsd-doc@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 1F78637BB9B for ; Tue, 4 Apr 2000 13:50:47 -0700 (PDT) (envelope-from bandix@looksharp.net) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id QAA29387; Tue, 4 Apr 2000 16:49:44 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Tue, 4 Apr 2000 16:49:44 -0400 (EDT) From: "Brandon D. Valentine" To: J McKitrick Cc: doc@FreeBSD.ORG Subject: Re: rough doc patch In-Reply-To: <20000404142322.A7059@dogma.freebsd-uk.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 4 Apr 2000, J McKitrick wrote: >Just a thought for some documentation to be inserted somewhere in the >handbook to reduce some confusion. > >Note to new users: Do not be misled. While staying up to date via cvsup is >simple, upgrading across major revisions is not. Due to major changes >between revisions, the procedure may become decidedly more complex. The >suggestion is to monitor -stable a few weeks before performing the upgrade. >It might even be worth monitoring -current before the release becomes >official. However, be advised that upgrading from source is NOT for the >faint of heart. Upgrading in binary mode via sysinstall is the preferred >method for newcomers to FreeBSD. Otherwise, you may face complications, >and these may even require reinstalling your system from scratch. > >However, if you decide to perform the upgrade via source, it might be good >to watch -stable for a few weeks after the release, just to see what >glitches others have run into. PLEASE do this for your own good. It may >save you a great deal of grief farther down the line. > >NOTE: major upgrades often have special instructions which may even be >modified from time to time after the release is made. These are usually >found in /src/UPDATING, but revisions are often posted to -stable. They are >also VERY important, and could mean the difference between a seamless >upgrade and a nightmare of reinstalls and lost data. Proceed with caution. > >jm Very good, my only suggestion is s/farther/further/ since we're talking extent and not distance. ;-) Brandon D. Valentine -- "...and as for hackers, we note that all of those known to The Register are so strapped financially that seizing their property would be tantamount to squeezing blood from a stone." -- The Register, 02/17/2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message