https://bugzilla.novell.com/show_bug.cgi?id=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c wei wang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wewang@novell.com AssignedTo|bnc-team-screening@forge.pr |coolo@novell.com |ovo.novell.com | -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c2 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Stefan Seyfried 2011-01-12 16:38:02 CET --- In stock 11.3, "modprobe loop" is called by boot.localfs, so I guess you must have changed something. Actually the same is true for factory, so systemd is probably not running boot.localfs and thus not loading the loop module. Maybe adding it as a default to "MODULES_LOADED_AT_BOOT" would be a good idea? -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c4 --- Comment #4 from Kay Sievers 2011-01-13 10:08:17 UTC --- systemd has it's own config for force-loading modules: man modules-load.d which should be uses instead of anything in /etc/sysconfig/. The loopdev logic in the kernel is just utterly broken and needs to be fixed to have a control device (like /dev/mapper/control) for loop devices, instead of requiring an arbitrary number of pre-created loop devices, which might, or might be not be used, or might be too many or to few, later. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c6 --- Comment #6 from Kay Sievers 2011-01-21 16:27:06 UTC --- (In reply to comment #5)

patch an alias devname:loop0 into the loop module

This could not go upstream as is the wrong solution and papers over the real problem that loop in the kernel is just a broken concept regarding the device management. It would need a proper control device, like /dev/mapper/control is, or something similar.

or package /lib/udev/devices/loop0.

Enabling autoloading only loop0 access might work for the common case, but is still a hack. I guess loading loop.ko unconditionally from /etc/modules-load.d/ (and make sysv read that too) might be the best current option. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c7 Ludwig Nussel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #7 from Ludwig Nussel 2011-01-25 10:55:11 CET --- I'd rather give the the /lib/udev/devices/ solution a try. Unconditionally loading the module is what we already have so it's hanging around even if not needed. -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c9 --- Comment #9 from Dirk Mueller 2011-05-16 23:05:10 CEST --- the easiest solution is probably to not package the device node, but just generate it in %post - and silently ignore the failure if it doesn't work. but why was this ugly hack added to aaa_base in the first place and not udev? -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c11 --- Comment #11 from Bernhard Wiedemann 2011-05-17 16:00:16 CEST --- This is an autogenerated message for OBS integration: This bug (661715) was mentioned in https://build.opensuse.org/request/show/70460 Factory / aaa_base -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c13 Christian Dengler changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED CC| |cdengler@novell.com InfoProvider|maintenance@opensuse.org | --- Comment #13 from Christian Dengler 2011-05-17 14:38:51 UTC --- okay, update started: SwampID 40961 -- 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=661715 https://bugzilla.novell.com/show_bug.cgi?id=661715#c15 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.4:41009 --- Comment #15 from Swamp Workflow Management 2011-05-31 13:39:07 UTC --- Update released for: aaa_base, aaa_base-debuginfo, aaa_base-debugsource, aaa_base-extras Products: openSUSE 11.4 (debug, i586, x86_64) -- 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.