RE: [MiNT] Was: /proc, will be: /sys

["Julian Reschke" <reschke@muenster.de>]

> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Thomas Binder
> Sent: Friday, November 12, 1999 3:24 PM
> To: MiNT mailing list
> Subject: Re: [MiNT] Was: /proc, will be: /sys
>
>
> Hi!
>
> On Fri, Nov 12, 1999 at 10:58:41AM +0100, Julian Reschke wrote:
> > Do Unix/POSIX/Linux systems actually differentiate between a process
> > name and the file name from which the process was created?
>
> Yes. IRIX and Solaris (or more generally, SysV-style systems) have the
> option `-f' for ps, which will cause it to print the full path and the

So does my ps.ttp.

> command line arguments, if possible (actually, you get the contents of
> argv[0] of the process, e.g. `-bash' for login shells). Without it, you
> get what was passed to exec() as the command name, path stripped.

So maybe I should change the default for my ps.ttp to use the name from
PLOADINFO with the path stripped. However, for those who use extensions, the
process names now would contain the extensions as well. I'm not convinced
that this is what people want...

> Under Linux (which currently has a BSD-style ps in most distributions),
> simple ps will behave like SysV-ps with the option `-f', while `ps c'
> will cause it to behave like SysV-ps without options.
>
> Reproducing this behaviour with MiNT would require Pexec() to check for
> argv[0] in the environment passed, as it's not directly passed as a
> parameter.

And this would only work if ARGV parameter passing was actually used...