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: <20100930122928.19e5ee84@lxorguk.ukuu.org.uk>
Date:	Thu, 30 Sep 2010 12:29:28 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	"Marc - A. Dahlhaus" <mad@....de>, linux-kernel@...r.kernel.org,
	isdn@...ux-pingi.de
Subject: Re: [PATCH] Fix capi devicenames

> In any case devices.txt should be fixed, it has not much to do with
> the real world.

If some distros chose not to follow devices.txt that is their problem.

devices.txt is the specification, and its ABI.

It is fixed and the kernel behaviour is to follow it. Those who didn't
follow it, or who didn't propose a change back when it was specified in
the first place have only themselves to blame.

It isn't changing, and the ISDN code should follow the spec.

How you sort out your userspace is a problem for those who dug holes and
jumped down them.
--
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/