public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Lougher <phil.lougher@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: debugfs in the namespace
Date: Fri, 17 Dec 2004 02:27:44 +0000	[thread overview]
Message-ID: <cce9e37e04121618275ad611bc@mail.gmail.com> (raw)
In-Reply-To: <E1Cf4wA-0008U5-00@calista.eckenfels.6bone.ka-ip.net>

On Fri, 17 Dec 2004 00:21:34 +0100, Bernd Eckenfels
<ecki-news2004-05@lina.inka.de> wrote:
> In article <20041216144531.3a8d988c@lembas.zaitcev.lan> you wrote:
> > Otherwise, /dbg sounds good.
>
> I dont think that a root level directory, especially with an unreadable name
> is a good idea. Why dont we at least try to keep the  namespace clean?

Are you suggesting we should rename "etc", "mnt" etc? :-)  I like
"/dbg" it follows the gdb, kgdb naming convention and it was the Unix
way to name things like this.  Though perhaps debugfs should have been
named dbgfs in this case...

I don't like "/.debug", hiding it in way this implies that you don't
think it should be there (and so you've hidden it).  A properly
decided upon mount point shouldn't have these connotations?  If you're
using debugfs I think you should want to have the mount point visible.

Phillip

  reply	other threads:[~2004-12-17  2:28 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
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 [this message]
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=cce9e37e04121618275ad611bc@mail.gmail.com \
    --to=phil.lougher@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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