Age | Commit message (Collapse) | Author |
|
|
|
UDev follows the kernel given name, and re-uses the kernel created
device node. If the kernel and spcecified udev rules disagree, the
udev specified node node is created and the kernel-created on is
deleted.
|
|
|
|
|
|
https://bugs.launchpad.net/bugs/368109
|
|
|
|
|
|
I don't see any security implications, to be actually useful,
/dev/cpu/<n>/cpuid should be world readable. The cpuid instruction
can be called from userspace anyway, so there is nothing to hide.
The device does not support any write operation, so 0444 should
suffice.
Signed-off-by: Andre Przywara <andre.przywara@amd.com>
|
|
Some broken mobile phones offer a faked cdrom drive with a media
without any tracks.
|
|
|
|
Instead of of our own private monitor socket, we send the
processed event back to our netlink socket, to the multicast
group 2 -- so any number of users can listen to udev events,
just like they can listen to kernel emitted events on group 1.
|
|
|
|
|
|
|
|
|
|
The driver's name changed in the 2.6.28 timeframe.
|
|
Patch from Gerardo Exequiel Pozzi.
|
|
Some broken tools get confused following links to /sys, switch
to link targets carrying the devpath instead of the syspath, like
the queue links.
|
|
|
|
|
|
A failing IMPORT+ match would prevent the OPTIONS+= action
from being applied.
|
|
|
|
https://bugs.launchpad.net/bugs/317430
|
|
Thanks to Scott, who found that.
|
|
$env{ID_PATH} includes the "-nst" suffix anyway, so we shouldn't append
it a second time as part of the rule creating the device file symlink.
Signed-off-by: Lennart Poettering <lennart@poettering.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
On Fri, Dec 26, 2008 at 01:26, Karel Zak <kzak@redhat.com> wrote:
> On Fri, Dec 26, 2008 at 12:39:16AM +0100, Kay Sievers wrote:
>> On Fri, Dec 26, 2008 at 00:26, Karel Zak <kzak@redhat.com> wrote:
>> > The upstream raw(8) command supports /dev/rawctl and also
>> > /dev/raw/rawctl. I think it makes more sense to use raw/rawctl when
>> > you have all your raw devices in raw/ subdirectory (e.g. /dev/raw/raw<N>).
>>
>> The raw tool looks for /dev/rawctl first and the fallback to
>> /dev/raw/rawctl is named DEVFS_*. Should we turn that order around and
>> remove the devfs notion from the raw tool and let udev create a
>> dev/raw/rawctl node?
>
> Yeah. Fixed, committed and pushed.
>
> $ strace -e open ./raw
> open("/dev/raw/rawctl", O_RDWR) = -1 ENOENT (No such file or directory)
> open("/dev/rawctl", O_RDWR) = -1 ENOENT (No such file or directory)
>
> I have also removed the #ifdef OLD_RAW_DEVS (/dev/raw<N>) junk.
|
|
|
|
A note on /dev/raw1394's security implications:
1. You cannot access local memory through raw1394, except
for ROMs and CSRs that are exposed to other nodes any way.
2. It is extremely hard to manipulate data on attached
SBP-2 devices (FireWire storage devices).
3. You can disturb operation of the FireWire bus, e.g.
creating a DoS situation for audio/video applications, for
SBP-2 devices, or eth1394 network interfaces.
4. If another PC is attached to the FireWire bus, it may be
possible to read or overwrite the entire RAM of that remote PC.
This depends on the PC's configuration. Most FireWire controllers
support this feature (yes, it's not a bug, or at least wasn't
intended to be one...) but not all OSs enable the feature.
Actually, a cheap setup to achieve #1 by #4 is to have two
FireWire controllers in the PC and connect them.
https://bugs.launchpad.net/ubuntu/+source/kino/+bug/6290/comments/21
|
|
|
|
|
|
|
|
dv1394*: no kernel name symlink
lp*: no par* symlink
hwrng: no kernel name symlink
|
|
specialix_rioctl: no kernel name symlink
specialix_sxctl: no kernel name symlink
bus/usb: 0644 -> 0664
ppdev: lp
dri: 0666 -> 0660
js: no kernel name symlink
|
|
|
|
|
|
|
|
$ tree /dev/serial/
/dev/serial/
|-- by-id
| |-- usb-067b_2303-if00-port0 -> ../../ttyUSB0
| |-- usb-FTDI_FT232R_USB_UART_A7005uBP-if00-port0 -> ../../ttyUSB3
| |-- usb-HUAWEI_Technology_HUAWEI_Mobile-if00-port0 -> ../../ttyUSB1
| `-- usb-HUAWEI_Technology_HUAWEI_Mobile-if01-port0 -> ../../ttyUSB2
`-- by-path
|-- pci-0000:00:1d.0-usb-0:1:1.0-port0 -> ../../ttyUSB3
|-- pci-0000:00:1d.7-usb-0:2.2.2:1.0-port0 -> ../../ttyUSB0
|-- pci-0000:00:1d.7-usb-0:2.3:1.0-port0 -> ../../ttyUSB1
`-- pci-0000:00:1d.7-usb-0:2.3:1.1-port0 -> ../../ttyUSB2
$ tree /dev/serial/
/dev/serial/
|-- by-id
| |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB0
| |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB1
| |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB2
| |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB3
| |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port0 -> ../../ttyUSB8
| |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port1 -> ../../ttyUSB9
| |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port2 -> ../../ttyUSB10
| |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port3 -> ../../ttyUSB11
| `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
`-- by-path
|-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB7
|-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB4
|-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port1 -> ../../ttyUSB5
|-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port2 -> ../../ttyUSB6
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB0
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB1
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port2 -> ../../ttyUSB2
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port3 -> ../../ttyUSB3
|-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB8
|-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB9
|-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB10
`-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB11
|
|
|
|
|
|
|
|
/dev/X0R null symbolic Required by iBCS-2
Note: /dev/X0R is <letter X>-<digit 0>-<letter R>
|
|
|
|
/dev/v4l
|-- by-id
| |-- usb-046d_09a4_C4B15020-video-index0 -> ../../video0
| `-- usb-05a9_a511-video-index0 -> ../../video1
`-- by-path
|-- pci-0000:00:1d.0-usb-0:1:1.0-video-index0 -> ../../video1
`-- pci-0000:00:1d.7-usb-0:2:1.0-video-index0 -> ../../video0
|
|
|