From owner-freebsd-arch@FreeBSD.ORG Sat Mar 27 02:41:12 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A09416A4CE; Sat, 27 Mar 2004 02:41:12 -0800 (PST) Received: from huva.hittite.isp.9tel.net (huva.hittite.isp.9tel.net [62.62.156.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id D855843D31; Sat, 27 Mar 2004 02:41:11 -0800 (PST) (envelope-from cyrille.lefevre@laposte.net) Received: from pc2k (unknown [81.185.204.209]) by huva.hittite.isp.9tel.net (Postfix) with SMTP id 79DCF9BC67; Sat, 27 Mar 2004 11:41:56 +0100 (CET) Message-ID: <1c0901c413e8$04a466c0$7890a8c0@dyndns.org> From: "Cyrille Lefevre" To: "Garance A Drosihn" References: <20040325070120.GA67497@VARK.homeunix.com> <1a9c01c41359$b3da45e0$7890a8c0@dyndns.org> Date: Sat, 27 Mar 2004 11:41:09 +0100 Organization: ACME MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: "Jacques A. Vidrine" cc: arch@freebsd.org cc: David Schultz cc: Albert Cahalan Subject: Re: posix ps (was Re: Adding `pgrep' and `pkill' to /usr/bin) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Mar 2004 10:41:12 -0000 "Garance A Drosihn" wrote: > At 6:40 PM +0100 3/26/04, Cyrille Lefevre wrote: > > > >two years ago, I've added posix syntax and so to my locally > >ps(1). For instance, I'm currently adding the notion of > >dynamic personalities (the term comes from linux) instead > >of static #define such as... say : > > > >$ ps -X help > > any bsd bsd43reno bsd44 default extended freebsd hpux > > irix netbsd none openbsd pedantic posix relaxed solaris > > sunos susv3 tru64 > ...etc... > > >When finished, I'll probably submit these changes as a port, > >... since I suppose -arch will reject these important changes > >to a native command. > > I (personally) think that is overkill for a base-system command. > I do think that it is important for us to improve on what we > have for `ps, but that does not mean we immediately have to > rush out and re-implement every version of `ps' on the planet. not every version, but at least, the one w/ interesting options. my patch will follow w/o the enhanced personality part. could you take an eye on it before to commit your changes ? as I read your proposed changes, we could merge them w/o any problem. well, in fact, I already merge some of them (the or part instead of and). original ps : 26668 (no posix compliant) yours : 31072 (partly posix compliant) mine : 35684 (fully posix compliant) > You are suggesting that we go from being the least feature-full > and most-oddball `ps', to trying to match every `ps' along with > every subtle formatting-nuance of every system. With the changes at the beginning, it was not, but ... > that I just did, I went through a fair amount of trouble to make > sure that I was not increasing the size of `ps'. There are some > FreeBSD users who need to squeeze the OS onto very small file > systems, and I think that is a reasonable thing for our users > to want. I (personally) think that the size and complexity of > some all-encompassing `ps' is not worth the effort, and not worth > the PR's we will get over every feature does not *EXACTLY* match > how it behaves on the "original OS". > > I can see your `ps' being a very good option to have as a port, > and I might even install it in some situations, but I do not > think we want something that elaborate for a base-system command. > > >here are some sample outputs : > > > >$ PERSONALITY=freebsd ps -? > > Secondly, I personally am not fond of commands which COMPLETELY > change their behavior based on environment variables. Different > options, different formats, different rules. that's what other system does to avoid conflicts and for clarity. > If nothing else, writing the man page for that would be a real > nightmare, and I am no good at writing man pages... :-) not necesseraly, take a look on the tru64 manual pages. [snip] > I was going to write those up in reply to this message, but I > have a steady-stream of "emergency interruptions" (here at work) > today, and I'm supposed to be somewhere else right now, so I > guess my thoughts will wait until a later date. see you Cyrille Lefevre. -- home: mailto:cyrille.lefevre@laposte.net