Comment 18 for bug 19171

On Jul 14, Joost Kooij <joost@213-84-68-67.adsl.xs4all.nl> wrote:

> Anyway, the problem turned out to be a broken udev_db setting in udev.conf
> My udev.conf had it set to "/dev/.udevdb", but because /etc/init.d/udev-mtab
> doesn't bind mount that (anymore?), it is not there. After changing it to
> "/dev/.static/dev/.udevdb", things were all merry again.
No, this is meaningless. /etc/init.d/udev-mtab has nothing to do with
this, the directory is supposed to be created by udevstart and using
/dev/.static/dev/.udevdb is definitely wrong because the file system
will be read only.
Let's try a different approach. What happens if you restore the correct
udev.conf and add "mkdir /dev/.udevdb" to /etc/init.d/udev after the
"warn_if_interactive" line?

--
ciao,
Marco