From: Davidlohr Bueso <dave@gnu.org>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] [PATCH procfs] Add process age
Date: Fri, 30 Jul 2010 10:58:27 -0400 [thread overview]
Message-ID: <1280501907.1929.5.camel@cowboy> (raw)
In-Reply-To: <20100728065640.GD5161@cr0.nay.redhat.com>
On Wed, 2010-07-28 at 14:56 +0800, Américo Wang wrote:
> On Mon, Jul 26, 2010 at 11:10:29AM -0400, Davidlohr Bueso wrote:
> >On Mon, 2010-07-26 at 16:48 +0200, Andi Kleen wrote:
> >> > True, but there are also many other no-so-useful files under /proc that
> >> > can also be replaced by userspace apps.
> >>
> >> Example?
> >
> >Off the top of my head:
> >
> >/proc/cmdline
>
> Are you kidding?
>
> /proc/cmdlines contains lots of info, it is not only used by the kernel,
> but also used by initramfs (this depends on your distribution).
>
Silly me, I meant /proc/#/cmdline, in the sense that you can get the
command name from the PID in userland.
Davidlohr
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-07-30 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 17:47 [RFC] [PATCH procfs] Add process age Davidlohr Bueso
2010-07-23 18:35 ` Alexey Dobriyan
2010-07-23 18:47 ` Davidlohr Bueso
2010-07-23 23:16 ` Sergey V.
2010-07-26 7:47 ` Andi Kleen
2010-07-26 13:57 ` Davidlohr Bueso
2010-07-26 14:48 ` Andi Kleen
2010-07-26 15:10 ` Davidlohr Bueso
2010-07-28 6:56 ` Américo Wang
2010-07-30 14:58 ` Davidlohr Bueso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1280501907.1929.5.camel@cowboy \
--to=dave@gnu.org \
--cc=adobriyan@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).