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-next>] [day] [month] [year] [list]
Message-Id: <200901201349.33707.ionut.leonte@gmail.com>
Date:	Tue, 20 Jan 2009 13:49:33 +0200
From:	Ionut Leonte <ionut.leonte@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: 2.6.28 changes in-kernel name for UVC device ?

I have a Dell laptop with an integrated webcam which works with the 'uvcvideo' 
module. For kernel versions 2.6.27 and below the following udev rule:

   KERNEL=="video[0-9]*",  NAME="v4l/video%n", SYMLINK+="%k", GROUP="video"

would create '/dev/video0' as a link to '/dev/v4l/video0'. When switching to 
2.6.28 the rule creates '/dev/video1394-0' instead. Obviously most user-space 
apps were quite surprised by this (as was I). 

Is this change intended or is it the accidental result of some modification ?

(attached 'lsusb' information for the device)

View attachment "lsusb_webcam" of type "text/plain" (19547 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ