On Thursday 12 January 2006 11:31, Anthony Walker wrote:
>
> Perhaps it is related to the older udev in use. If the following output
> does confirm this theory I will have to see how I can upgrade udev and
> hopefully not break anything else in the process.
> ...
> 249 visdn-timer
> 250 visdn-timer
> 251 visdn-timer
> 252 visdn-timer
> 253 visdn-timer

All those reservations for visdn-timer are suspect. They remember me of a bug 
I solved quite some time ago. Are you sure you are running a recent snapshot?

Make sure there is no garbage in /lib/modules/.../extra/, the module_install 
target sometimes puts there garbage like your home directory, it's a bug I'm 
going to solve soon.

A reboot would be recommendable, anyway.

Bye,
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to