Re: "udevadm info --attribute-walk --path=/block/sda" doesn't show parents

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

On 04/18/2012 03:42 PM, Chris Friesen wrote:
> I have a kernel with udev-161 (also tested with udevadm from udev-173).
> When I run "udevadm info --attribute-walk --path=/block/sda" it just shows the device
> itself, and doesn't walk the whole chain showing the parents.
> Is there anything I can do, or am I caught with a kernel that isn't properly supported?
> I'm not subscribed to the hotplug list, so cc'ing me would be appreciated.
> I don't know what's causing the problem, but I find it suspicious that /sys/block/sda
> is a directory rather than a symlink like it is on my laptop.  I'm poking
> around in the udevadm code now.

Looking at the udevadm code led me to the following:

On the problematic 2.6.34 machine:

root@typhoon-base-unit0:/root> ls -l /sys/dev/block/
lrwxrwxrwx 1 root root 0 Apr 18 14:34 8:0 -> ../../block/sda

On my 2.6.35 machine:

[cfriesen@blah udev-173]$ ls -l /sys/dev/block/
lrwxrwxrwx. 1 root root 0 Apr 18 15:54 8:0 -> ../../devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda

So where do I go from here?  Is there a simple kernel change to make my 2.6.34
kernel behave more like the more recent one?  Would an older version of udev be
able to parse my 2.6.34 /sys directory properly, or do I need to figure out a
way to parse /sys manually?


Chris Friesen
Software Developer
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Linux DVB]     [Video Technology]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Devices]     [Fedora Women]     [ALSA Devel]     [Linux USB]

Add to Google Powered by Linux