All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Thu, 16 Dec 2004 11:42:24 -0800	[thread overview]
Message-ID: <20041216194224.GA6640@kroah.com> (raw)
In-Reply-To: <20041216113357.4c2714bb@lembas.zaitcev.lan>

On Thu, Dec 16, 2004 at 11:33:57AM -0800, Pete Zaitcev wrote:
> On Thu, 16 Dec 2004 11:08:35 -0800, Greg KH <greg@kroah.com> wrote:
> 
> > On Thu, Dec 16, 2004 at 11:00:02AM -0800, Pete Zaitcev wrote:
> > > what is the canonic place to mount debugfs: /debug, /debugfs, or anything
> > > else? The reason I'm asking is that USBMon has to find it somewhere and
> > > I'd really hate to see it varying from distro to distro.
> > 
> > Hm, in my testing I've been putting it in /dbg, but I don't like vowels :)
> 
> Oh, that's right: usr and creat. How could I forget.
> 
> > Anyway, I don't really know.  /dev/debug/ ?  /proc/debug ?  /debug ?
> > 
> > What do people want?  I guess it's time to write up a LSB proposal :(
> 
> I use /debug but it's not too late to change. Fedora does not ship it yet,
> so I don't think we have an institutional opinion about it.
> 
> Personally, I'm against the doubles to prevent issues with the mounting
> order on boot, but that's rather weak. The /dev can be specially managed
> and I'm concerned with people running find(1) on it. The /proc sounds
> better, but mounting anything under /proc requires a kernel component
> to create a directory, does it not?

Yes it does, but debugfs could create the mount point, if people agree
that this is a good place to put it (like usbfs does.)

Personally, I don't want to put it there, but that's just because I hate
proc stuff :)

So, /debug sounds good to me.  Any objections?

thanks,

greg k-h

  reply	other threads:[~2004-12-16 19:42 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 [this message]
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
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=20041216194224.GA6640@kroah.com \
    --to=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 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.