This is a discussion on Re: pkill.c warn when "no such process" within the mailing.openbsd.tech forums, part of the OpenBSD category; --> On Fri, Feb 22, 2008 at 9:48 PM, Ian McWilliam <kaosagnt@tpg.com.au> wrote: > > On 23 Feb 2008, at ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Fri, Feb 22, 2008 at 9:48 PM, Ian McWilliam <kaosagnt@tpg.com.au> wrote: > > On 23 Feb 2008, at 6:09 AM, Unix Fan wrote: > > > Heinrich Rebehn wrote: > >> You are certainly right. But my point was, that in one case (rm) it > >> is > >> appropriate for the system to output an error message, if it cannot > >> perform an action that the user requested, and in the other case > >> (pkill) > >> it's not. > >> > >> -Heinrich > > > > pkill(1) and pgrep(1) were imported almost 9 releases ago... based > > on commands defined by another operating system. > > > > Why should the behaviour be changed now? > > > > It could break countless numbers of scripts.. > > > > > > > > -Nix Fan. > > > > > > > OpenBSD was imported over 12 years ago from a tree based upon another > operating system, whose tree was imported years earlier based upon > another operating system. With your argument, why bother to fix / > change anything from the original OS release OpenBSD is based upon. > > "It could break countless number of scripts.." > I agree this is not a reasonable reason in this case. > I find it interesting that *BSD (not just OpenBSD) let the GNU crowd > dictate the future of how U*ix like operating system should behave. > you don't seem no know unix, here is a good starting point http://harmful.cat-v.org/cat-v/unix_prog_design.pdf. iru |
| Thread Tools | |
| Display Modes | |
|
|