https://bugzilla.novell.com/show_bug.cgi?id=829265 https://bugzilla.novell.com/show_bug.cgi?id=829265#c5 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@suse.com AssignedTo|lslezak@suse.com |fehr@suse.com --- Comment #5 from Thomas Fehr <fehr@suse.com> 2013-07-15 15:42:02 UTC --- Of course one could simply fetch scripts via schemes http or ftp instead of nfs. But if one insists for some reasons to use nfs as source for his scripts it would be tricky. pre-scripts and post-partitioning scripts run too early. init-scripts run too late. On could add a chroot script with in placed code in xml file at start of chroot-scripts list like this: <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">false</chrooted> <source><![CDATA[ echo "/sbin/modprobe" > /proc/sys/kernel/modprobe ]]></source> </script> <script> other scripts using nfs as URL scheme </script> </chroot-scripts> This should fix module autoloading (did not try that yet) But since the problem exists since at least SLES11 lifetime and was not reported yet it either does not hit too many customers or they silently use ftp or http when having trouble with nfs. Note that if one installs via nfs or gets autoyast.xml via nfs, the problem does also not show up since before package install autoloading works and if modules are already loaded later nfs mount works too. While verifying the fix, I ran into another problem with nfs scripts in chroot environment that seems unrelated to nfs mount problem. I will have another look and reassign the bug back to me. -- 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.