Date: Sun, 03 May 1998 12:14:28 +0100 From: Karl Pielorz <kpielorz@tdx.co.uk> To: Terry Lambert <tlambert@primenet.com> Cc: current@FreeBSD.ORG Subject: Re: VM changes broke SYSVSHM? Message-ID: <354C5194.8D8986B8@tdx.co.uk> References: <199805031039.DAA26478@usr08.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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... <g> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?354C5194.8D8986B8>