On Thu, Jan 30, Joschi Brauchle wrote:
For some reason I did not get the DUD to work correctly. It may be my fault... Anyways, I unpacked the DUD and copied all files into my OSS repository on the NFS server, leading to the equivalent effect of the DUD.
Now, Autoyast stage 2 works perfectly again! Thanks!
I have a quick followup question: --------------------- <runlevel> <default>5</default> <services config:type="list"> <service>
rpcbind enable </service> </services> </runlevel> --------------------- does not work, i.e. rpcbind.service is disabled in the installed system.In y2log I see an error message saying something like "rpcbind service does not exist, creating it" (or something along these lines, dont have the log available currently). Same happens e.g. for "xinetd", but not for "sshd", "nfs" and many others.
Could be that with migration to systemd some services have been renamed. In theory these renames could be mapped to corresponding systemd names in Import/Export code of yast2-runlevel. So it would probably be worth a bug report. Unfortunately I cannot guarantee that anyone really fixes it. In general the "migration" (if one would call it that, usurpation would bet a much better term) to systemd is one of the worst nightmares since I work in linux area.
So why does AutoYast think that the rpcbind.service does not exist and why is it not enabled?
Tschuess, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr@suse.de GPG public key available. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org