From: Mike Waychison <Michael.Waychison@Sun.COM>
To: Greg KH <greg@kroah.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Thu, 16 Dec 2004 16:51:18 -0500 [thread overview]
Message-ID: <41C20356.4010900@sun.com> (raw)
In-Reply-To: <20041216190835.GE5654@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greg KH wrote:
> On Thu, Dec 16, 2004 at 11:00:02AM -0800, Pete Zaitcev wrote:
>
>>Hi Greg,
>>
>>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 :)
>
> 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 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.
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBwgNWdQs4kOxk3/MRAslqAJwPnra30/EBuZxuXkdpo67SZJXJUQCaAtC1
OeMH0Xiww/8xV9tIfqyzmE4=
=Aa8I
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-16 21:51 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 [this message]
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=41C20356.4010900@sun.com \
--to=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