Hello Uwe, that's good news. For me it looks like the /etc/resolv.conf is indeed empty like Christopher mentioned (at least inside the chrooted system, did not check outside). If I manually add a nameserver, the chroot script can mount the NFS server. Still, the *next* chroot script is not correctly pulled from the NFS, I get the same original error there: "mount failed". I guess YaST runs outside the chroot, and there is a similar problem DNS there? Also, the (possibly related) problem that YaST hangs at the next step "Configuring lan" and the process list suggests that systemd is waiting for some kind of password/input (process name is: "/bin/systemd-tty-ask-password-agent --watch") persists after creating a valid resolv.conf. Best regards, Joschi Brauchle On 08/07/2012 11:30 AM, Uwe Gansert wrote:
On 06.08.2012 10:51, Joschi Brauchle wrote:
I just started testing 12.2RC2 and noticed to following. There are multiple custom user scripts in my XML file, all of which get pulled from an NFS server.
I started to reproduce your issue here and it looks like it's a bug triggered by a fix I've added to workaround problems with systemd. I hope I can fix that in time for 12.2 Thanks for the report
-- Dipl.-Ing. Joschi Brauchle, M.S. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle@tum.de Web: http://www.lnt.ei.tum.de/