All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	Mike Waychison <Michael.Waychison@Sun.COM>,
	linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Thu, 16 Dec 2004 15:51:47 -0800	[thread overview]
Message-ID: <20041216235147.GC11330@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0412170033160.25628@alpha.polcom.net>

On Fri, Dec 17, 2004 at 12:39:00AM +0100, Grzegorz Kulewski wrote:
> On Thu, 16 Dec 2004, Greg KH wrote:
> 
> >On Thu, Dec 16, 2004 at 02:45:31PM -0800, Pete Zaitcev wrote:
> >>On Thu, 16 Dec 2004 14:18:43 -0800, Greg KH <greg@kroah.com> wrote:
> >>
> >>>Hm, what about /.debug ?  That's a compromise that I can live with (even
> >>>less key strokes to get to...)
> >>
> >>No way, Jan is out of his mind, adding obfuscations like that. Anything
> >>but that. I didn't even bother to reply, because it never occurred to me
> >>that you'd fall for something so retarded.
> >
> >Bah, fine :)
> >
> >>Otherwise, /dbg sounds good.
> >
> >Ok, I can live with that.
> 
> I agree that anything like /.* is broken and strange... But this is only 
> my little opinion. :-)
> 
> But why creating dir in /proc - like /proc/debug is bad? Its advantages:
> - it does not pollute namespace,
> - it can be created by kernel at startup even on systems where debugfs 
> will not be used (why not?),
> - /proc is mounted in all configurations and often it is the first thing 
> that startscripts do,
> - if somebody really needs to debug proc using debugfs he can always mount 
> it as /debug temporaily.

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...

thanks,

greg k-h

  reply	other threads:[~2004-12-16 23:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 19:00 debugfs in the namespace 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 [this message]
2004-12-17  0:08               ` Grzegorz Kulewski
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=20041216235147.GC11330@kroah.com \
    --to=greg@kroah.com \
    --cc=Michael.Waychison@Sun.COM \
    --cc=kangur@polcom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.