SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-23-2008, 04:12 AM
| ||||
| ||||
 Re: pkill.c warn when "no such process" On Sat, Feb 23, 2008 at 11:48:32AM +1100, Ian McWilliam wrote: > 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 find it interesting that *BSD (not just OpenBSD) let the GNU crowd > dictate the future of how U*ix like operating system should behave. I noticed the lack of messages from pkill some time ago but forgot all about it when I saw it had good return values. I don't see that as worth arguing about, since it's trivial to find out what happened. As for keeping with the "old way" you shouldn't change things just for fun. There really ought to be a *good* reason. A few weeks ago someone wrote on another list about a little script they'd been using for many, many years across many different unix systems. It broke under Linux, you see. I tried it on OpenBSD and it worked fine. It turns out GNUisms have changed their sed so that it no longer works for some things. GNU's not UNIX, but OpenBSD is (less the trademark, anyway). ;-) -- Darrin Chandler | Phoenix BSD User Group | MetaBUG dwchandler@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation      |
 |
« Canada: 2008 Federal Government Employee File
|
=?windows-1251?B?0eDs++Ug6/P46OUg8ODx8fvr6ugg7vIg7vLl9+Xx8uLl7e3u4+4g7/Du6Ofi7uTo8uXr/yA6LSk=?= »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 09:39 AM.
