>> THANK YOU! > np, i'm not doing the hardest part :) you have been the first who actually *did* something to resolve the issue instead of just going on with bla-bla-bla.
>> - do you have /lib/dev-state/log file? > yes > $ ls /lib/dev-state/log -l > srw-rw-rwT 1 root root 0 jui 4 22:13 /lib/dev-state/log= Good, this was the immediate culprit. Remove it and you should be able to boot normally. It was expected to be removed by devfsd update but probably something did not work as expected. Anyway the whole story is so fragile that this is the minor problem. I will have to think about final solution. I do not like losing boot messages before syslogd start so reverting my last minilogd patch is not an option (at least, the last one to consider). This is *very* system dependent, in your case I presume the USB was the reason you experienced it (by adding more syslog users). please tell me if removing /lib/dev-state/log fixed it; else I need stack again, do not bother with ksymoops. Please, Cc me I do not receive cooker. -andrey
