lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49b7c2350905281517k4b518c9of6e991f50571d427@mail.gmail.com>
Date:	Fri, 29 May 2009 07:17:01 +0900
From:	GeunSik Lim <leemgs1@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Greg KH <greg@...ah.com>,
	Jaswinder Singh Rajput <jaswinder@...nel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, trivial@...nel.org,
	balagi@...tmail.de, bgamari@...il.com, Ingo Molnar <mingo@...e.hu>,
	inaky.perez-gonzalez@...el.com
Subject: Re: [RFC PATCH]debugfs:Fix terminology inconsistency of dir name to 
	mount debugfs filesystem.

On Thu, May 28, 2009 at 10:45 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> 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.
Thank you for the decision to update  debufs filesystem realted contents.
>
> 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
> =====
About typo in the above statements.
/sys/kernel/debugfs --> /sys/kenrel/debug
Default directory of debugfs filesystem is /sys/kernel/debug/ as you know.

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



-- 
Regards,
GeunSik Lim ( SAMSUNG ELECTRONICS)
Blog : http://blog.naver.com/invain/
e-Mail: geunsik.lim@...sung.com
           leemgs@...il.com , leemgs1@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ