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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46F806AB.1050509@oracle.com>
Date:	Mon, 24 Sep 2007 11:49:15 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Christoph Hellwig <hch@...radead.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: [patch 6/7] Linux Kernel Markers - Documentation

Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 11:23:35AM -0700, Randy Dunlap wrote:
>> That might be OK for this case, but sometimes it makes sense to have
>> README etc. about how to use the software.  So you would want this
>> in the Documentation/ tree?  That makes it harder on users.
> 
> If it's so complex that we can't describe it in a few dozens lines
> it shouldn't be anywhere but the place it belongs and better have a
> real use and not just be a sample.  And in the trace case I must
> admit that I'd prefer a real use like some simple syscall-trace
> over this hack anyway..

I think that samples are perfectly fine for documentation and
that the trace example is a good example.  I think that most people
who need something like that would need to customize it for their
specific needs anyway.

We don't seem to be making progress...


-- 
~Randy
Phaedrus says that Quality is about caring.
-
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