Problem was:
Using a nfs source for the control.xml file didn't work as described.
** Doesn't work (as input to the boot prompt):
linux autoyast=nfs://ip-of-nfs1:/path/control.xml
install=nfs://ip-nfs2:/other-path/suse8.0
(one will be asked for a valid path to a control file, later)
** Doesn't work , either:
linux autoyast=nfs://ip-of-nfs1/path/control.xml
install=nfs://ip-nfs2:/other-path/suse8.0
(no colon after nfs-server1's ip in the autoyast statement)
Anas Nashif
Try without the : in the URL <snip>
So the URL should look like this: install=nfs://123.123.123.111/installs/suse8.0
Ah - the trick is to leave out *both* times the colon .. If one of these lines on the boot prompt, it works: ** Works: linux autoyast=nfs://ip-nfs1/path/control.xml install=nfs://ip-nfs2/other-path/suse8.0 ** Works, too: linux autoyast=http://ip-www/control.xml install=nfs://ip-nfs2:/other-path/suse8.0 (Here the colon after the nfs-server ip doesn't hurt in the install statement) Anis Nashif mentions further:
This is a known issue and it was fixed and an updated version will be available for nfs installs soon.
Is there a open list of "known issues" ? (I've got some more small issues, but if they are known, I don't want to bother the list with them.) And - soon is approximatly when? (Should I start to play with autoinstall boot CDs with the old version or is it worth to wait for the new version?) Regards, Hella