* Hella.Breitkopf@varetis.de [May 01. 2002 00:20]:

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)

Are you sure this one does not work? It looks exactly likethe one you describe next..

Anas Nashif gave the tip:

...

Try without the : in the URL <snip>

So the URL should look like this: install=nfs://123.123.123.111/installs/suse8.0

Ok, this was my mistake, it should say autoyast=...

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)

No, the 'install' keyword is evaluated by linuxrc. 'autoyast' is evaluated by linuxrc as well, but it passed as is to YaST2 and the problem was with parsing the url. a colon only make sense if you intend to add a port number. This has been fixed and as said a fixed version of the RPM will be available on the FTP server as soon as it is test enough.

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" ?

So far, this is the only major bug that was reported. Alot of non-bug issues were posted to me, mostly feature requests and improvement suggestions which we will be very glad to receive.

(I've got some more small issues, but if they are known, I don't want to bother the list with them.)

It would be great if you can post them. I will create a list of 'known bugs and issues' on http://www.suse.de/~nashif/autoinstall/. Major bugs with solutions will be added to the support data base after verification and successful testing.

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?)

I will be posting some more information about this bug and how it can be fixed shortly. Regards, Anas

Regards,

Hella

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com

-- Anas Nashif , SuSE Linux AG Montreal (Laval), Canada