From owner-freebsd-current Thu Apr 16 12:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20851 for freebsd-current-outgoing; Thu, 16 Apr 1998 12:38:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20826 for ; Thu, 16 Apr 1998 19:38:14 GMT (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id UAA02441; Thu, 16 Apr 1998 20:37:59 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <35365E14.BD1F9D21@tdx.co.uk> Date: Thu, 16 Apr 1998 20:37:56 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: Should I run -CURRENT? SNAP? References: <199804161842.LAA00669@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > -current right now seems to be quite stable. Yes, I haven't seen too many complaints recently... (Did I say complaints? - I mean't 'bug information'... :-) > > If I find a SNAP that works well is it likely to stay 'working well' (I > > know, how longs a piece of string?) - or am I better off staying 'really' > > current? > > I tend to leapfrog; when I have a stable system I'll live with it until > either I need/want to play with a new feature, or it just feels "really > old" (usually 2-3 months). Sounds like a good strategy... I like the 'play' word in there... > > Oh for SMP-Stable... > > Testing and input from people like you is what it will take to achieve > just exactly that. I guess so... I've just freed up a wedge of space on another 1Gb drive - and I'm about to install it... Thanks for your advice (to both my postings! - memory mapped IO?) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message