linux-kernel - Re: [PATCH] SYSFS: Allow boot time switching between deprecated and modern sysfs layout v2

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: <20100908193910.2d27a33b@basil.nowhere.org>
Date:	Wed, 8 Sep 2010 19:39:10 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	greg@...ah.com, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...ux.intel.com>, axboe@...nel.dk
Subject: Re: [PATCH] SYSFS: Allow boot time switching between deprecated and
 modern sysfs layout v2

On Wed, 8 Sep 2010 17:27:37 +0200
Kay Sievers <kay.sievers@...y.org> wrote:

> On Wed, Sep 8, 2010 at 16:54, Andi Kleen <andi@...stfloor.org> wrote:
> > From: Andi Kleen <ak@...ux.intel.com>
> >
> > I have some systems which need legacy sysfs due to old udev
> > versions, and it's a big hazzle to compile separate kernels for
> > them.
> 
> It's not udev, it's other tools making wrong assumptions like that
> directories can not be a symlink to a directory, or that a device is
> always the same parent device. It's also not udev which fails on newer
> installations, it's the lack of information in the non-extensible
> deprecated layout which makes all sorts of tools fail. So please
> work-off the text from the old help text instead of blaming the wrong
> things here. :)

Ok. I can either send out a new patch or Greg can change the description
of v2 to dish out the blame in a Kay approved matter when he merges it.
What you guys prefer.

-Andi


-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/