is there some reason why whether or not to overcommit can't be a kernel compile time option? Or that a process can signal its desire to not get SIGKILL by registering a non-default SIGDANGER (which we'd have to create) handler ala AIX? ] Train travel features AC outlets with no take-off restrictions| firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Replacement for grep(1) (... Matthew Dillon
- Re: Replacement for grep(1) (part... Valentin Nechayev
- Re: Replacement for grep(1) (... Matthew Dillon
- Re: Replacement for grep(1) (part 2) Daniel C. Sobral
- Re: Replacement for grep(1) (part 2) Valentin Nechayev
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Chris G. Demetriou
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Robert Elz
- Re: Replacement for grep(1) (part 2) Michael Richardson
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Neil A. Carson
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) David Brownlee
- Re: Replacement for grep(1) (part 2) Matthew Dillon
- Re: Replacement for grep(1) (part 2) Jason Thorpe
- Re: Replacement for grep(1) (part 2) Matthew Dillon