linux-kernel - Re: Documentation for sysfs, hotplug, and firmware loading.

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]

Date:	Wed, 18 Jul 2007 16:40:20 -0700
From:	Greg KH <greg@...ah.com>
To:	Rob Landley <rob@...dley.net>
Cc:	Cornelia Huck <cornelia.huck@...ibm.com>,
	linux-kernel@...r.kernel.org, Michael-Luke Jones <mlj28@....ac.uk>,
	Krzysztof Halasa <khc@...waw.pl>,
	Rod Whitby <rod@...tby.id.au>,
	Russell King <rmk@....linux.org.uk>, david@...g.hm
Subject: Re: Documentation for sysfs, hotplug, and firmware loading.

On Wed, Jul 18, 2007 at 01:39:53PM -0400, Rob Landley wrote:
> PICK ONE!  JUST #*%(&#%& PICK ONE!  AAAAAAAAHHHHHHH!!!!!!!!!
> 
> I don't care where it is.  Just put it somewhere I can find it, and keep it 
> there.  All this gratuitous moving stuff around serves NO PURPOSE other than 
> to break userspace.  I'm trying to document this so that the next time you 
> go "oh wait, it should be at "/sys/tarantula/fruitbat" I can show that you're 
> breaking an existing documented userspace API.
> 
> There's a kernel config option to make symlinks from the old 
> location.  /sys/block makes as much sense as any other location, and it's 
> what's there now.

Read the sysfs documentation file we just added, it describes how this
is all documented and should be used.  So well that I do not think you
need to try to document it again.

thanks,

greg k-h
-
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/