Re: [RFC PATCH]debugfs:Fix terminology inconsistency of dir name tomount debugfs filesystem.

From: Steven Rostedt
Date: Thu May 28 2009 - 09:46:02 EST

On Wed, 27 May 2009, Greg KH wrote:
> > > >
> > > > ( Note: it is more common to mount at /sys/kernel/debug, but for
> > > > simplicity this document will use /debug)
> > > > ===

> >
> > I really don't want to do that. Then I would need to show
> >
> > # echo function_graph > /sys/kernel/debug/current_trace
> >
> > Which I really do not like. I state that the common place to mount it is
> > in /sys/kernel/debug, But my examples are much easier to understand if
> > I just do: # echo function_graph > /debug/current_trace
> It's not just the "common" place, it is the DOCUMENTED PLACE.

I can change the wording to be "documented" or "distro mounted".

> I'm sorry you have to type a long path, perhaps you wish to invest in a
> tab key for auto-completion :)
> Again, distros already mount debugfs at this location, please don't
> confuse people just because you are annoyed at the length of the path.

Have you found which packages do that?

The point is that the document is more interested in showing the files
that are being used, and if I add /sys/kernel/debug/ in front of every
file, that just distracts from the eye. As stated:

"but for simplicity this document will use /debug"

I'll update ftrace.txt to explain it better.

Something like:

Debugfs is mounted by some packages at /sys/kernel/debugfs. If it is not
you can mount it by adding

debugfs /sys/kernel/debug debugfs defaults 0 0

to your /etc/fstab, or by manually mounting it:

# mount -t debugfs nodev /sys/kernel/debugfs

For simplicity, this document will assume that you also added the
following symbolic link:

# ln -s /sys/kernel/debugfs /debug

Then I can keep the document simplistic and still have the "DOCUMENTED"
locating specified.

-- Steve

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at