> 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. \\ [EMAIL PROTECTED] \\ -- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Ted Faber
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Ted Faber
- Re: Replacement for grep(1) (part 2) Kris Kennaway
- Re: Replacement for grep(1) (part 2) Gregory Sutter
- Re: Replacement for grep(1) (part 2) Mike Smith
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Noriyuki Soda
- Re: Replacement for grep(1) (part 2) Brian F. Feldman
- Re: Replacement for grep(1) (part 2) Valentin Nechayev
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Valentin Nechayev

