Date: Tue, 13 Jul 1999 16:29:50 -0700 From: Mike Smith <mike@smith.net.au> To: Jason Thorpe <thorpej@nas.nasa.gov> Cc: hackers@FreeBSD.ORG Subject: Re: Replacement for grep(1) (part 2) Message-ID: <199907132329.QAA01922@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 13 Jul 1999 16:27:11 PDT." <199907132327.QAA25268@lestat.nas.nasa.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 13 Jul 1999 16:16:07 -0700 > Mike Smith <mike@smith.net.au> wrote: > > > 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. > > That's just silly. If people want a no-overcommit system, they have it, > and if they don't, they have that, too. You're too tied up in what you think you're trying to say that you're missing what I'm telling you. Of course you can turn overcommit off and on (more or less) with a switch. But a system that doesn't overcommit doesn't behave like a system that does; the two are quite different animals in many respects. You can make the "overcommit or not overcommit" option a switch, but the consumers of the system (may) need to change their behaviour as well. -- \\ 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907132329.QAA01922>