Russel,
I had already done this, and it didn't work. I encountered a similar
issue before, and worked out with rgooch that it was a devfsd bug. That
was awhile back, so this may be a different issue entirely, but I'm
waiting for his reply on this one.
Agreed, though, that devfs (and esp. devfsd) need work in the
documentation department.
Further discussion off-list ... we're way offtopic now :)
-ed
On 05 Apr 2001 10:28:47 -0600, Russel Ingram suggested:
> The one mentioned here can actually be resolved by watching
> the /var/log/messages for the name of the resource the kernel is looking
> for when it loads that module, then use that resource name as an alias to
> the proper module in /etc/modules.conf. That much will make the module
> load properly. Past that it's just a matter of telling devfsd to make
> the correct symbolic link to the device file that your software is looking
> for at the same time it makes the new format device file.
|