linux-kernel - Re: 2.6.28 changes in-kernel name for UVC device ?

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:	Tue, 20 Jan 2009 15:19:44 +0200
From:	Ionut Leonte <ionut.leonte@...il.com>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28 changes in-kernel name for UVC device ?

On Tuesday 20 January 2009 15:07:21 you wrote:
> These rules are broken, and match also on firewire devices and not
> only video4linux devices.
>
> Such rules are not part of the standard udev setup and need to be
> fixed to work as intended. There is no change or fault at the kernel
> side. You may just disable the firefire drivers if you don't need
> them.
>
> Btw, swapping default kernel names to devfs names and create symlinks
> for the kernel names is not recommended at all.

Thanks for the clarifications. The rule is taken from the 'default' udev setup 
as presented to me by my distribution (Gentoo in my case). I'll be sure to 
file a bug report with them.

Cheers.
--
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/