From owner-freebsd-hackers Thu Jul 15 17:50:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from splode.eterna.com.au (splode.eterna.com.au [203.15.111.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D65B14F92 for ; Thu, 15 Jul 1999 17:50:04 -0700 (PDT) (envelope-from mrg@eterna.com.au) Received: from splode.eterna.com.au (localhost [127.0.0.1]) by splode.eterna.com.au (Postfix) with ESMTP id 6B7CE3CA7; Fri, 16 Jul 1999 10:49:06 +1000 (EST) To: Sheldon Hearn Cc: freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org subject: re: Swap overcommit (was Re: Replacement for grep(1) (part 2)) in-reply-to: your message of "Fri, 16 Jul 1999 01:56:49 +0200." <80862.932083009@axl.noc.iafrica.com> organisation: people's front against (bozotic) www (softwar foundation) x-other-organisation: The NetBSD Foundation. Date: Fri, 16 Jul 1999 10:49:05 +1000 Message-ID: <19866.932086145@splode.eterna.com.au> From: matthew green Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All I want for Christmas is a knob to disable overcommit. And what I'm pretty sure the majority of the readers on this list want is for those of you who really think it's necessary to do it yourselves. What? Nobody who wants to disable the policy knows how to do it? Hmmm, I wonder whether that's significant... that's an impressively bold statement to make. by my reconning, at least 4 people who have posted "wanting no overcommit" are more than capable of programming this for NetBSD. .mrg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message