https://bugzilla.novell.com/show_bug.cgi?id=683126 https://bugzilla.novell.com/show_bug.cgi?id=683126#c1 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |kasievers@novell.com --- Comment #1 from Marcus Schaefer 2011-03-28 20:43:37 UTC --- sorry kiwi doesn't create device nodes, I'm sure udev creates /dev/mem. Please check this with Kay -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=683126 https://bugzilla.novell.com/show_bug.cgi?id=683126#c3 --- Comment #3 from Vladimir Nadvornik 2011-03-29 11:26:55 UTC --- (In reply to comment #2)

There is no known problem with basic device nodes like this for years. I'm pretty confident that this is a problem with kiwi and not udev.

What kernel version is that?

Standard SLES11SP1 kernel, 2.6.32.29-0.3-default

What type of filesystem is mounted at /dev?

udev on /dev type tmpfs (rw,mode=0755)

Does: /sys/class/mem/mem/ exist?

yes

Does running: udevadm trigger create the node?

yes, manually calling udevadm trigger creates the node. udevadm trigger is however called immediately after udevd start, but this call apparently did not create it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=683126 https://bugzilla.novell.com/show_bug.cgi?id=683126#c5 Vladimir Nadvornik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Vladimir Nadvornik 2011-03-29 12:28:25 UTC --- I have re-tested it with kiwi 4.83 and it seems to work fine with this version. Some change between 4.81 and 4.83 apparently fixes it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=683126 https://bugzilla.novell.com/show_bug.cgi?id=683126#c7 --- Comment #7 from Kay Sievers 2011-03-29 15:03:13 UTC --- Nothing must ever use startproc to start any non-broken service. It's a completely broken concept to blindly fork any modern service in the background with that helper. We removed it from all usual services long ago. Services block their execution for a reason, and do their own double-forking, and do not return until they have successfully initialized their work. Dependend services can rely on a working and initialized daemon that way. Startproc breaks all this logic. Please get entirely rid of it. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=683126 https://bugzilla.novell.com/show_bug.cgi?id=683126#c9 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #9 from Marcus Schaefer 2011-03-29 16:26:14 UTC --- ok, done -- 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.