[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [MiNT] expanded /proc vs new /kern



> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Jo-Even.Skarstein@gjensidige.no
> Sent: Monday, December 06, 1999 8:52 AM
> To: mint@fishpool.com
> Subject: RE: [MiNT] expanded /proc vs new /kern
>
>
> > -----Original Message-----
> > From: Martin-Eric Racine [mailto:q-funk@pp.fishpool.fi]
> > Sent: Monday, December 06, 1999 1:50 AM
> > To: MiNT List
> > Subject: [MiNT] expanded /proc vs new /kern
> >
> > Given that most of those I can think of live in the Unix domain,
> > not as commercial GEM applications, I cannot think of any reason
> > why they couldn't be patched and recompiled.
>
> You are making the mistake to assume that everything that's not commercial
> is open-source. It's not. I can't speak for the rest of the community, but
> atleast two of my own programs (Taskbar and Connexion(2)) depends on the
> *documented fact* that /proc is a 8+3 filesystem. There are also other,
> closed-source programs/apps that use /proc (although I don't know if they
> will break with long filenames), MultiStrip, Hideaway, SpeedUp, Paral and
> ps.cpx to name a few.
>
> I suggest that if the full name is really needed, then a new ioctl on
> /proc/.[pid] would suffice. Guido already suggested an ioctl to
> retrieve the
> argument-vector which also will return the complete filename of
> the process.

The latter is called PLOADINFO and has been around in MiNT for several years
now.