Greg KH wrote:
> On Tue, Mar 23, 2004 at 01:51:01PM -0800, Daniel Stekloff wrote:
> 
>>
>>Hi Greg,
>>
>>I think this is what you want for udevinfo. Patched against the latest BK
>>tree. I tested it and it seemed to work.

It seems to have a bug:

carldani@4100xcdt:~/work/udev-023-orig> ./udevinfo -a -p /sys/block

udevinfo starts with the device the node belongs to and then walks up the
[...]
to match the device for which the node will be created.

  looking at class device '/sys/block':
couldn't open class device directory

carldani@4100xcdt:~/work/udev-023-orig> ./udevinfo -a -p /sys/block/

udevinfo starts with the device the node belongs to and then walks up the
[...]
to match the device for which the node will be created.

device '/sys/block' has major:minor 1:9
  looking at class device '/sys/block':
couldn't open class device directory


How can /sys/block have a major/minor number which changes everytime I
recompile udevinfo?


> Thanks, I've applied this.

Could you also apply the attached patch to clean up a bit?


Thanks,
Carl-Daniel