https://bugzilla.novell.com/show_bug.cgi?id=843718
https://bugzilla.novell.com/show_bug.cgi?id=843718#c16
Marcus Schaefer changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|ms@suse.com |adrian@suse.com
--- Comment #16 from Marcus Schaefer 2013-11-07 10:00:52 UTC ---
in reply to comment #14
I agree to what Rudi said about the tools which should create the device nodes.
With regards to LVM the situation is that udev and the device-mapper creates
devices. The one from the device mapper appear all in /dev/mapper/... the one
udev creates are in /dev/...
the schema of both is different and from the use of the device mapper
created devices I was discouraged because people told me udev is the way to
go. That's the reason why kiwi uses the devices udev creates and those devices
are also used if I install a system with yast + lvm
I'm not sure but I think if you run tools which creates device nodes under
linux these days they mostly use udev and our entire distribution would fail if
we don't start udev as the very first task in the initrd
Thus we can complain about the use of udev and how much pain it still cause but
we also have decided that SUSE uses udev and I think with regards to this a
buildservice VM should also be able to cope with udev in the same way a
standard system would do it
I also would love if the bs worker kernel is not different from the distro
kernel
in the Studio project we use containment systems which are also simple JeOS
VM's building inside them does not outline any lvm device node issues.
I think I can't do much with this bug, thus assigning to the buildservice space
hope that's ok
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
