From: Greg KH <greg@kroah.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: leemgs1@gmail.com, linux-kernel <linux-kernel@vger.kernel.org>,
mathieu.desnoyers@polymtl.ca,
Steven Rostedt <srostedt@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/5] debugfs - Fix mount directory of debugfs by default in events.txt
Date: Mon, 7 Sep 2009 14:30:47 -0700 [thread overview]
Message-ID: <20090907213047.GA28651@kroah.com> (raw)
In-Reply-To: <1252350914.7503.24.camel@twins>
On Mon, Sep 07, 2009 at 09:15:14PM +0200, Peter Zijlstra wrote:
> On Mon, 2009-09-07 at 11:55 -0700, Greg KH wrote:
> > On Mon, Sep 07, 2009 at 02:48:57PM +0200, Peter Zijlstra wrote:
> > > On Mon, 2009-09-07 at 21:37 +0900, GeunSik Lim wrote:
> > > >
> > > > >From 99e8ab48d783e619329c31e8f91e4384729a2e8b Mon Sep 17 00:00:00 2001
> > > > From: GeunSik,Lim <leemgs1@gmail.com>
> > > > Date: Mon, 7 Sep 2009 20:34:19 +0900
> > > > Subject: [PATCH 1/5] Fix mount directory of debugfs by default in events.txt
> > > >
> > > > We need common default directory of denbugfs for consistency.
> > > > (debugfs's default directory is /sys/kernel/debug/ by debugfs.)
> > >
> > > I'd rather we fix that brain-dead default.
> >
> > Um, why is that "brain-dead"? It was discussed many times when debugfs
> > first came out and this was what was decided on.
>
> From what people tell me it wasn't a clear consensus.
Specifics please.
> > So what is the problem?
>
> Its not related to sysfs in any way I can discover,
So, other filesystems are mounted in sysfs, and in /proc for many years.
> its not consistent with most of the other virtual fs',
What do you mean by this?
> and its way too much typing.
tab completion is your friend, as is environment variables. Don't
choose stuff just because you are lazy :)
> we don't mount /dev, /proc, /sys in weird places either, so why should
> we mount /debug in a cumbersome location.
Because it is a _kernel_ debug thing, not a system-level debug thing.
What would userspace developers think about /debug ? Why would they
care about such a thing?
As much as we tend to ignore it, kernel developers are not the primary,
or only, users of Linux :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-07 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 12:37 GeunSik Lim
2009-09-07 12:48 ` Peter Zijlstra
2009-09-07 18:55 ` Greg KH
2009-09-07 19:15 ` Peter Zijlstra
2009-09-07 21:30 ` Greg KH [this message]
2009-09-07 22:27 ` Steven Rostedt
2009-09-08 1:27 ` GeunSik Lim
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=20090907213047.GA28651@kroah.com \
--to=greg@kroah.com \
--cc=hch@infradead.org \
--cc=leemgs1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=peterz@infradead.org \
--cc=srostedt@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
all inboxes | Powered by JetHome®