From owner-freebsd-stable Thu Jan 28 01:40:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16885 for freebsd-stable-outgoing; Thu, 28 Jan 1999 01:40:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16878 for ; Thu, 28 Jan 1999 01:40:35 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id FAA18024; Thu, 28 Jan 1999 05:38:42 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 28 Jan 1999 05:38:42 -0400 (AST) From: The Hermit Hacker To: "Jordan K. Hubbard" cc: Michael Robinson , stable@FreeBSD.ORG Subject: Re: When to transition to 3.0-STABLE.. NOT NOW! In-Reply-To: <84058.917514364@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 Jan 1999, Jordan K. Hubbard wrote: > > Too, late, unfortunately. I guess I've been spoiled after all these years, > > and mistakenly assumed that when something had a "STABLE" label on it, it > > was, well, stable. > > Just to clarify this - it IS stable. If you took a brand new box > today and installed 3.0S on it, it would run just fine. There is > nothing wrong with the bits. > > It is UPGRADING from a.out systems which still presents a new problem, > one which we've never had to deal with before, and I think folks are > just not adequately taking this into account. Tonight, with much trepidation, I ran 'make upgrade NOCONFIRM=YES', and was most impressed...but I went from 3.0-RELEASE(aout) to 3.0-STABLE(elf), and already had all the da0 drive mappings done already... If you want a 'commercial' example of doing a system upgrade, try going from a Solaris 2.5.x and earlier system to Solaris 2.6 ... disk space requirements, for some reason, jumped when solaris 2.6 (minimums), but they distributed an option to 're-size' your file systems...that I've yet to get to work. So, instead, you back it all up, wipe everything out and re-install from scratch. Quite frankly, in light of everything that could have gone wrong...none of it did. I still have one last, outstanding, elf-related problem that I posted earlier, but, other then that, the 3.0S system appears to be purring along quite nicely... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message