From: Grzegorz Kulewski <kangur@polcom.net>
To: Greg KH <greg@kroah.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Mike Waychison <Michael.Waychison@Sun.COM>,
linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Fri, 17 Dec 2004 01:08:05 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.60.0412170101530.25628@alpha.polcom.net> (raw)
In-Reply-To: <20041216235147.GC11330@kroah.com>
On Thu, 16 Dec 2004, Greg KH wrote:
> Disadvantage:
> - it puts a non-process type thing into /proc which is what I am
> specifically trying to get away from doing.
>
> Only process related things _should_ be in /proc. Now if I can ever
> fully achieve that goal in my lifetime is something that is left to be
> seen...
Ok, probably - but who said this? IIRC there is no standard describing
what should be in proc and what should not. I do not think that after so
many years of storing everyting in /proc there is any chance that you will
remove all not [0-9]* dirs and files from /proc before the sun will stop
lighting... :-) Many, really _many_, binary only apps are using proc for
999999 different (often stupid) things - how you will change that? There
is way too late for such change, in my opinion.
And polluting / with proc, sys, dev, selinux, debug and who knows what
else is at least equally bad.
Thanks,
Grzegorz Kulewski
next prev parent reply other threads:[~2004-12-17 0:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 19:00 Pete Zaitcev
2004-12-16 19:08 ` Greg KH
2004-12-16 19:33 ` Pete Zaitcev
2004-12-16 19:42 ` Greg KH
2004-12-17 19:08 ` Pavel Machek
2004-12-18 17:49 ` Jörn Engel
2004-12-16 20:00 ` Jan Engelhardt
2004-12-16 21:51 ` Mike Waychison
2004-12-16 22:18 ` Greg KH
2004-12-16 22:45 ` Pete Zaitcev
2004-12-16 22:53 ` Greg KH
2004-12-16 23:39 ` Grzegorz Kulewski
2004-12-16 23:51 ` Greg KH
2004-12-17 0:08 ` Grzegorz Kulewski [this message]
2004-12-17 0:21 ` Greg KH
2004-12-17 1:15 ` Grzegorz Kulewski
2004-12-17 1:23 ` Greg KH
2004-12-17 7:48 ` Jan Engelhardt
2004-12-16 23:21 ` Bernd Eckenfels
2004-12-17 2:27 ` Phil Lougher
2004-12-17 7:23 ` Jan Engelhardt
2004-12-17 17:22 ` debugfs in the namespace [u] Martin Schlemmer [c]
2004-12-16 23:29 ` debugfs in the namespace Pedro Venda (SYSADM)
2004-12-18 22:24 ` Matt Mackall
2004-12-17 4:06 ` H. Peter Anvin
2004-12-17 18:39 ` John Levon
[not found] <fa.al1ango.pl0rak@ifi.uio.no>
[not found] ` <fa.ddml8me.1k46obg@ifi.uio.no>
2004-12-17 5:51 ` Bodo Eggert
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=Pine.LNX.4.60.0412170101530.25628@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=Michael.Waychison@Sun.COM \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®