linux-kernel - Re: [PATCH] Fix capi devicenames

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: <20100930103010.1a6a7785@lxorguk.ukuu.org.uk>
Date:	Thu, 30 Sep 2010 10:30:10 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Marc - A. Dahlhaus" <mad@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix capi devicenames

On Wed, 29 Sep 2010 21:21:23 +0200
"Marc - A. Dahlhaus" <mad@....de> wrote:

> capi device names should get changed to what userspace expects.

If userspace isn't following the spec (which has been the spec for many
years) then thats not our problem.

> Without this change recent udev versions can't produce working device
> nodes as the capi control device node name "capi" collides with the
> "capi" directory under which userspace expects to get the application
> device nodes. This also fixes the Documentation.

The documentation isn't broken, the documentation *is* the reference.

NAK. Fix udev.

We have a spec for a reason, if some distro didn't follow it then that's
up to them but they can sort out their own udev.

Alan
--
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/