* udev warnings / not exactly sure what to do
@ 2006-10-25 14:25 Andreas Jellinghaus
2006-10-26 0:40 ` MUNEDA Takahiro
0 siblings, 1 reply; 2+ messages in thread
From: Andreas Jellinghaus @ 2006-10-25 14:25 UTC (permalink / raw)
To: linux-hotplug
Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid SUBSYSTEMS
operation
Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid rule
'/etc/udev/rules.d/z60_openct.rules:49'
Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid SUBSYSTEMS
operation
Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid rule
'/etc/udev/rules.d/z60openct.rules:49'
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug94610
the relevant lines are:
36 # udev pcmcia rules file for openct
37 #
38 BUS!="pcmcia", ACTION!="add", GOTO="openct_pcmcia_rules_end"
39 # omnikey cardman 4040
40 SUBSYSTEM="cardman_4040", RUN+="/lib/udev/openct_pcmcia"
41 # Gemplus PCMCIA Card
42 BUS="pcmcia", DRIVER="serial_cs", SYSFS{prod_id1}="Gemplus",
SYSFS{prod_id2}="SerialPort", SYSFS{prod_id3}="GemPC Card",
RUN+="/lib/udev/openct_serial"
43 LABEL="openct_pcmcia_rules_end"
no idea why the line counting is off, but line 40 is the only line with
SUBSYSTEM in it. not SUBSYSTEMS why this is confusing. line 42 has
BUS="pcmcia", maybe that is the problem? (should be BUS="pcmcia", I
know, or even remove at all, as the GOTO earlier made sure these lines
are only evaluated for pcmcia devices anyway.)
I tested a bit, and if I remove BUS="pcmcia", and replace DRIVER=
with DRIVERS= then it works - no more warnings or error messages.
is DRIVERS exactly like DRIVER or do I need to change something?
still I'm not 100% sure what the right thing to do is, so every
advice is very welcome. Thanks for your help.
Regards, Andreas
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: udev warnings / not exactly sure what to do
2006-10-25 14:25 udev warnings / not exactly sure what to do Andreas Jellinghaus
@ 2006-10-26 0:40 ` MUNEDA Takahiro
0 siblings, 0 replies; 2+ messages in thread
From: MUNEDA Takahiro @ 2006-10-26 0:40 UTC (permalink / raw)
To: linux-hotplug
At Wed, 25 Oct 2006 16:25:45 +0200,
Andreas Jellinghaus <aj@ciphirelabs.com> wrote:
>
> Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid SUBSYSTEMS
> operation
> Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid rule
> '/etc/udev/rules.d/z60_openct.rules:49'
> Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid SUBSYSTEMS
> operation
> Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid rule
> '/etc/udev/rules.d/z60openct.rules:49'
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug94610
>
> the relevant lines are:
>
> 36 # udev pcmcia rules file for openct
> 37 #
> 38 BUS!="pcmcia", ACTION!="add", GOTO="openct_pcmcia_rules_end"
>
> 39 # omnikey cardman 4040
> 40 SUBSYSTEM="cardman_4040", RUN+="/lib/udev/openct_pcmcia"
>
> 41 # Gemplus PCMCIA Card
> 42 BUS="pcmcia", DRIVER="serial_cs", SYSFS{prod_id1}="Gemplus",
> SYSFS{prod_id2}="SerialPort", SYSFS{prod_id3}="GemPC Card",
> RUN+="/lib/udev/openct_serial"
>
> 43 LABEL="openct_pcmcia_rules_end"
>
> no idea why the line counting is off, but line 40 is the only line with
> SUBSYSTEM in it. not SUBSYSTEMS why this is confusing. line 42 has
> BUS="pcmcia", maybe that is the problem? (should be BUS="pcmcia", I
> know, or even remove at all, as the GOTO earlier made sure these lines
> are only evaluated for pcmcia devices anyway.)
>
> I tested a bit, and if I remove BUS="pcmcia", and replace DRIVER=
> with DRIVERS= then it works - no more warnings or error messages.
> is DRIVERS exactly like DRIVER or do I need to change something?
>
> still I'm not 100% sure what the right thing to do is, so every
> advice is very welcome. Thanks for your help.
>
> Regards, Andreas
Hi, Andreas
I guess, this issue has already solved. (I see Bug#394610)
FYI, udev-103/TODO says:
These things will change in future udev versions:
o make DRIVER= to match only the event device
(DRIVERS must be used, we currently translate it to DRIVERS and print
a warning if DRIVER is used)
o warn if BUS, ID, SYSFS are used as keys
(they are SUBSYSTEMS, KERNELS, ATTRS now)
Thanks,
MUNE
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-10-26 0:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-25 14:25 udev warnings / not exactly sure what to do Andreas Jellinghaus
2006-10-26 0:40 ` MUNEDA Takahiro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).