http://bugzilla.opensuse.org/show_bug.cgi?id=1076779 http://bugzilla.opensuse.org/show_bug.cgi?id=1076779#c35 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com Flags| |needinfo?(jsrain@suse.com) --- Comment #35 from Michael Chang <mchang@suse.com> --- (In reply to Franck Bui from comment #32)
I'm not sure it's the right thing to do though. I don't think udev is supposed to fully work in a chroot (or even in a container).
I'm just curious about why it did work for us in the past. Is it an accident/delusion ?
To answer your question the database is located in /run/udev so this directory can be bind mounted from the host to the chroot. But again it seems a hack and even if it works in your case, relying on udev in a chroot seems fragile.
I tested bind mount /run/udev to the chroot environment and it works. Does that justify an installer bug (in the bootstrap process) ? @Jiri, Would you have any comment? -- You are receiving this mail because: You are on the CC list for the bug.