udev complains about BestCrypt

udev complains about BestCrypt

[Phil Hagen]

When starting the BestCrypt (http://www.jetico.com/bcrypt7.htm) service,
udev 039 on FC3 complains to syslog as follows:
Nov 17 21:10:42 localhost wait_for_sysfs[26455]: either wait_for_sysfs
(udev 039) needs an update to handle the device '/block/bcrypt14' properly
(no device symlink) or the sysfs-support of your device's driver needs to
be fixed, please report to <linux-hotplug-devel@list s.sourceforge.net>

This happens for each of /block/bcrypt[0-15].  BestCrypt appears to work
properly, and the bcrypt[0-15] nodes are created in /dev, but the syslog
complaints lead me to believe that it's only working due to a default
condition or setting that properly "catches" the situation.

The bcrypt nodes are major/minor 188/[0-15], respectively.

I'm rather new to udev, so I'm sorry that I don't know the information
that may be able to help remedy this, but please let me know what I can do
to help.

-Phil Hagen


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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: udev complains about BestCrypt

[Kay Sievers]

On Wed, 2004-11-17 at 21:18 -0500, Phil Hagen wrote:
> When starting the BestCrypt (http://www.jetico.com/bcrypt7.htm) service,
> udev 039 on FC3 complains to syslog as follows:
> Nov 17 21:10:42 localhost wait_for_sysfs[26455]: either wait_for_sysfs
> (udev 039) needs an update to handle the device '/block/bcrypt14' properly
> (no device symlink) or the sysfs-support of your device's driver needs to
> be fixed, please report to <linux-hotplug-devel@list s.sourceforge.net>
> 
> This happens for each of /block/bcrypt[0-15].  BestCrypt appears to work
> properly, and the bcrypt[0-15] nodes are created in /dev, but the syslog
> complaints lead me to believe that it's only working due to a default
> condition or setting that properly "catches" the situation.
> 
> The bcrypt nodes are major/minor 188/[0-15], respectively.
> 
> I'm rather new to udev, so I'm sorry that I don't know the information
> that may be able to help remedy this, but please let me know what I can do
> to help.

I will add that to the list.
Btw: With kernel 2.6.10 all of these issues will be solved, as the
kernel exports in the hotplug environment what we can expect to show up
in sysfs.

Thanks,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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: udev complains about BestCrypt

[Patrick Mansfield]

On Thu, Nov 18, 2004 at 02:55:59PM +0100, Kay Sievers wrote:
> Btw: With kernel 2.6.10 all of these issues will be solved, as the
> kernel exports in the hotplug environment what we can expect to show up
> in sysfs.
> 

Is that the PHYSDEVBUS code?

Why doesn't udev or libsysfs use PHYSDEVBUS to find the bus (I don't see
any udev code using the value of PHYSDEVBUS)?

-- Patrick Mansfield


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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: udev complains about BestCrypt

[Greg KH]

On Thu, Nov 18, 2004 at 09:51:32AM -0800, Patrick Mansfield wrote:
> On Thu, Nov 18, 2004 at 02:55:59PM +0100, Kay Sievers wrote:
> > Btw: With kernel 2.6.10 all of these issues will be solved, as the
> > kernel exports in the hotplug environment what we can expect to show up
> > in sysfs.
> > 
> 
> Is that the PHYSDEVBUS code?
> 
> Why doesn't udev or libsysfs use PHYSDEVBUS to find the bus (I don't see
> any udev code using the value of PHYSDEVBUS)?

Because we _just_ added that to the kernel.

Give Kay a few days at least :)

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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: udev complains about BestCrypt

[Kay Sievers]

On Thu, 2004-11-18 at 10:04 -0800, Greg KH wrote:
> On Thu, Nov 18, 2004 at 09:51:32AM -0800, Patrick Mansfield wrote:
> > On Thu, Nov 18, 2004 at 02:55:59PM +0100, Kay Sievers wrote:
> > > Btw: With kernel 2.6.10 all of these issues will be solved, as the
> > > kernel exports in the hotplug environment what we can expect to show up
> > > in sysfs.
> > > 
> > 
> > Is that the PHYSDEVBUS code?
> > 

Yes, it is. It is meant as a hint what is expected to show up in sysfs.

> > Why doesn't udev or libsysfs use PHYSDEVBUS to find the bus (I don't see
> > any udev code using the value of PHYSDEVBUS)?

We have that values only at event time, so libsysfs need to be able to
do the reverse lookup anyway.
We may give libsysfs a hint where to look first for the bus, but in the
most expensive use of it, the udevstart case we can't do this.

> Because we _just_ added that to the kernel.
> 
> Give Kay a few days at least :)

Yeah, it's already used in wait_for_sysfs. We don't lookup the
exception lists if we are on a recent kernel.

Thanks,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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