From owner-freebsd-stable Mon Jan 10 4:47:14 2000 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 1AF8A1502C for ; Mon, 10 Jan 2000 04:47:03 -0800 (PST) (envelope-from jon@phoenix.welearn.com.au) Received: (from jon@localhost) by phoenix.welearn.com.au (8.9.3/8.9.3) id XAA22005; Mon, 10 Jan 2000 23:46:39 +1100 (EST) (envelope-from jon) Date: Mon, 10 Jan 2000 23:46:37 +1100 From: Jonathan Michaels To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: When does the 4.x branch go stable? Message-ID: <20000110234635.A21865@phoenix.welearn.com.au> Mail-Followup-To: Brad Knowles , freebsd-stable@FreeBSD.ORG References: <20000109235744.01C49A54EE@netcom1.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Brad Knowles on Mon, Jan 10, 2000 at 10:48:07AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG all, please excuse my slightly longish post, i'm looking at two issues here. i've finally come to terms with what "tracking -stable" actually is and what it means for me. i'm almost ready to cutover to springing for the cvsup version of kernel updating as opposed to the get the new -release cdrom and copy the new stuff over ... grin. On Mon, Jan 10, 2000 at 10:48:07AM +0100, Brad Knowles wrote: > At 3:57 PM -0800 on 2000/1/9, Mike Harding wrote: > > > mmm - I guess I am ready to go to 4.x in general, just wondering when > > it would be 'safe'. This is for my home system and I would prefer to > > do a source code update in place... how safe would a -release 'upgrade' be ? then a migration to a -stable track a bit further down the line ? i've found the best way to upgrade was to take the hot backup server, clean off the hard disk media do a fresh install of the newer operating system, reconfigure the various bits, add the required packages and then let it sit freewheeling for a few days or about a week. after no hiccups i cut over the services one at a time, till i have it all cutover and working .. then i take a dump onto tape and restore this to the former 'hot' server, which now becomes the new hot backup server. i'm lucky in that i only need one a pair of hosts to take my entire workload. just to digress a little, after i take on the tracking of -stable, this hot baackup server could serve as an installation server and the 'official' -stable tracker from which i could roll my as required freebsd editions. or am i needlessly complicating my working environemnt so that i could just track -stable .. i'm only wanting to track the kernal sources and some of the base systems toolkits as supplied with the basic 'kernel builders' installation option from the sysinstall menu. > I've been watching the -current mailing list for a while now, and > what I currently see is that -CURRENT has a few niggling outstanding > problems (especially on older hardware), and a few pretty major > outstanding problems. what sort of hardware problems, please ? not architectural, or as regards old i386dx style, or i486dx style motherboards and thier atendant isa buss structures. my couple are running very well with 2.2.7-release, but sooner or latter i wll need to get on board a more recent freebsd, if for no other reason than for teh inherant security weakness that have been fixed over the last year or so. also, i have a few adaptec aha1542b's that are running very well, some of teh newer stuff is .... those small and fragile pci buss cards tend to get damaged quickly if not handled correctly, my hands are not a agile as they used to be is what i'm getting at here. anway cheers warm regards jonathan -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message