From: Greg KH <greg@kroah.com>
To: Mike Waychison <Michael.Waychison@Sun.COM>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Thu, 16 Dec 2004 14:18:43 -0800 [thread overview]
Message-ID: <20041216221843.GA10172@kroah.com> (raw)
In-Reply-To: <41C20356.4010900@sun.com>
On Thu, Dec 16, 2004 at 04:51:18PM -0500, Mike Waychison wrote:
> I thought debugfs was meant for just debugging. As there is no plans
> for standardizing its namespace, why are we allowing ourselves to rely
> on it being mounted at all?
>
> AFAICT, there should be no excuse for userspace to actually rely on any
> of the data within debugfs. Otherwise we end up with yet another
> filesystem whose role is: Chaotic hodgepodge of magic files created by
> drivers that couldn't bother to be well-organized.
>
> Please, let's not make debugfs part of userspace. Keep it for what it
> is, debugging purposes only.
I'm not saying we will ever make it "required" at all. It's just that
people are going to want to mount the thing, and are already asking me
where we should mount it at. If you pick a different place than me,
fine, I don't mind. It's the user who is asked to report some info that
happens to be in debugfs that is going to want to know where to put it,
as they have no idea even what it is. Distros are going to ask what to
put in their fstabs for where to mount the thing too.
So, let's pick a place and be done with it.
I like /dbg (3 characters total to get to, which is shorter than /debug
which takes at least 4, 3 chars and a tab). Pete likes /debug. Jan
Engelhardt want to hide the thing from people at /.debugfs.
Hm, what about /.debug ? That's a compromise that I can live with (even
less key strokes to get to...)
Or is their some restriction on putting hidden directories in the root
filesystem as specified by the LSB?
So, /.debug sound acceptable?
thanks,
greg k-h
next prev parent reply other threads:[~2004-12-16 22:20 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 [this message]
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=20041216221843.GA10172@kroah.com \
--to=greg@kroah.com \
--cc=Michael.Waychison@Sun.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