udevtest: man page unclear

udevtest: man page unclear

[Andreas Jellinghaus]

in udev 079 the man page reads:
NAME
       udevtest - simulate a udev run and print the action to the console

SYNOPSIS
       udevtest device-path subsystem

DESCRIPTION
       udevtest simulates a udev run for the given device and prints out the
       name of the node udev would have created, or the name of the network
       interface, that would have been renamend.

well, to my knowledge I can use udev as hotplug, i.e. to run something
if hardware is added. the manpage does not tell me if it can help in that
scenario. 

also what is device path? what is subsystem? an example would be nice. 
for example: how to run a test for a usb token?

udevtest /class/usb_device/usbdev3.3 usb
should be fine I think? is that correct?

Andreas



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: udevtest: man page unclear

[Kay Sievers]

On Sun, Mar 19, 2006 at 09:21:23PM +0100, Andreas Jellinghaus wrote:
> in udev 079 the man page reads:
> NAME
>        udevtest - simulate a udev run and print the action to the console
> 
> SYNOPSIS
>        udevtest device-path subsystem
> 
> DESCRIPTION
>        udevtest simulates a udev run for the given device and prints out the
>        name of the node udev would have created, or the name of the network
>        interface, that would have been renamend.
> 
> well, to my knowledge I can use udev as hotplug, i.e. to run something
> if hardware is added. the manpage does not tell me if it can help in that
> scenario. 

From the udev man page:
  The following keys can get values assigned:
  ...
  RUN    Add a program to the list of programs to be executed for a
         specific device.

> also what is device path? what is subsystem? an example would be nice. 
> for example: how to run a test for a usb token?

It's the kernel provided path the device in sysfs, the device location
without /sys.

> udevtest /class/usb_device/usbdev3.3 usb
> should be fine I think? is that correct?

If you wan to see what rules are executed for that device, what udev
would do if this event is sent by the kernel, sure.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel