From owner-freebsd-bugs Mon Feb 24 15:40:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA00260 for bugs-outgoing; Mon, 24 Feb 1997 15:40:09 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA00219; Mon, 24 Feb 1997 15:40:04 -0800 (PST) Resent-Date: Mon, 24 Feb 1997 15:40:04 -0800 (PST) Resent-Message-Id: <199702242340.PAA00219@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, nik@blueberry.co.uk Received: from coconut.blueberry.co.uk ([194.70.52.66]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA28979 for ; Mon, 24 Feb 1997 15:30:42 -0800 (PST) Received: (from nik@localhost) by coconut.blueberry.co.uk (8.8.5/8.8.5) id XAA23618; Mon, 24 Feb 1997 23:29:59 GMT Message-Id: <199702242329.XAA23618@coconut.blueberry.co.uk> Date: Mon, 24 Feb 1997 23:29:59 GMT From: Nik Clayton Reply-To: nik@blueberry.co.uk To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/2810: Tutorial submission: Upgrading FreeBSD from source Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 2810 >Category: docs >Synopsis: Tutorial submission detailing how to upgrade FBSD from source >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Feb 24 15:40:02 PST 1997 >Last-Modified: >Originator: Nik Clayton >Organization: Blueberry Design >Release: FreeBSD 2.1.7-RELEASE i386 >Environment: N/A >Description: As a penance for wasting a few folk's time with some of my recent SNAFU's when upgrading 2.1.5 to 2.1.7 (Hi Jordan), I've written up a document describing (hopefully accurately) the steps that need to be gone through when re-making the world, and the precise meaning of the phrase "You must merge in /etc by hand" that gets bandied about every now and then. I've placed this in and would welcome feedback from anyone who knows more about this subject than I do. At the moment, the document is plain text (I don't know LinuxDoc, would prefer not to (I'd rather spend the time learning DocBook, but don't know of a handy tutorial -- references appreciated)). I'm kind of hoping that with a bit of peer review it can become a candidate for the tutorials page, and ultimately spawn a new section of the handbook. As I say, feedback welcomed. Hope it's useful. This message also sent to doc@freebsd.org. >How-To-Repeat: N/A >Fix: N/A >Audit-Trail: >Unformatted: