From owner-freebsd-hackers Tue Jul 13 16:21:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id DA5241534F for ; Tue, 13 Jul 1999 16:21:40 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA01841; Tue, 13 Jul 1999 16:16:07 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907132316.QAA01841@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ted Faber Cc: Matthew Dillon , hackers@freebsd.org Subject: Re: Replacement for grep(1) (part 2) In-reply-to: Your message of "Tue, 13 Jul 1999 16:09:48 PDT." <199907132309.QAA01587@boreas.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Jul 1999 16:16:07 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, Matt, I understand that you think that the folks who are want to > turn off overcommit are looking to hang themselves, but how much does > it cost to sell them the rope? The issue here is that "turning off overcommit" isn't just a switch. There are a lot of other things that you're likely to want to do, depending on your application, in addition to turning it off. Matt's point, which he's not making by virtue of talking too much, is that you can't make a "no overcommit" system behave like an "overcommit" system, and most people are used to the sort of things that the latter makes practical. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message