From owner-freebsd-chat Fri Apr 16 13:44:14 1999 Delivered-To: freebsd-chat@freebsd.org Received: from youknow.youwant.to (youknow.youwant.to [209.133.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 52A321598B for ; Fri, 16 Apr 1999 13:44:07 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever (whenever.youwant.to [209.133.29.2]) by youknow.youwant.to (8.8.7/8.8.7) with SMTP id NAA32170; Fri, 16 Apr 1999 13:41:44 -0700 From: "David Schwartz" To: "Daniel C. Sobral" Cc: Subject: RE: swap-related problems Date: Fri, 16 Apr 1999 13:41:44 -0700 Message-ID: <000001be8849$8a1c4050$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <37179B9E.D4434460@newsguy.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Feel free to submit patches. It's not important enough to me. I'm more than happy to simply not recommend FreeBSD for mission-critical processes on multi-user systems. I don't have an agenda, so I have no incentive to do so. Why is it that discussions of features always degenerate into "I think that's stupid, but if you want it, then you code it"? Is there something really wrong with saying, "That's a good idea, but there are no resources to code it"? If it really is a bad idea, what's the point in submitting patches? If it's a good idea, why not state so, so that perhaps people will work on it. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message