From owner-freebsd-current Sun May 3 04:15:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19271 for freebsd-current-outgoing; Sun, 3 May 1998 04:15:13 -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 EAA19235 for ; Sun, 3 May 1998 04:14:39 -0700 (PDT) (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 MAA26056; Sun, 3 May 1998 12:14:32 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <354C5194.8D8986B8@tdx.co.uk> Date: Sun, 03 May 1998 12:14:28 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Terry Lambert CC: current@FreeBSD.ORG Subject: Re: VM changes broke SYSVSHM? References: <199805031039.DAA26478@usr08.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > We need to be able to support -current, because for many people 2.2.X > > is too far in the past. 8-) But we need to avoid throwing marbles > > where bladers are skating. > > The problem is that -current is not yet released. Absolutely... - I've only been running current for about a month, but I had a very good idea of what I was getting into (i.e. this sort of problem) > You can not expect John to go off on a branch in order to let people > pretend that -current is -stable. Very true, but it's still amazing the amount of people I see who say "I'm running 3.0 on our [production] server...", very scary ;-) We have 6 production boxes running 2.2.2 through 2.2.6 (which run perfectly) and my own machine which runs 3.0, and runs perfectly - most the time, but enough not to make me go and install it on all the other 6... I think the best thing we can probably do is let John get on with it in peace... :-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message