From owner-freebsd-stable Thu Jan 28 01:05:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11667 for freebsd-stable-outgoing; Thu, 28 Jan 1999 01:05:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11662 for ; Thu, 28 Jan 1999 01:05:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id BAA84062; Thu, 28 Jan 1999 01:06:05 -0800 (PST) To: Michael Robinson cc: stable@FreeBSD.ORG Subject: Re: When to transition to 3.0-STABLE.. NOT NOW! In-reply-to: Your message of "Thu, 28 Jan 1999 15:05:09 GMT." <199901281505.PAA06688@netrinsics.com> Date: Thu, 28 Jan 1999 01:06:04 -0800 Message-ID: <84058.917514364@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message