* Rainer Krienke <krienke@uni-koblenz.de> [Jun 12. 2002 09:14]:
This does not seem to be working with DHCP. I tried
option root-path=nfs://server_ip:/path_to_nfs_dir option root-path=server_ip:/path_to_nfs_dir
option root-path=/path_to_nfs_dir (assuming "nextserver" would possibly be evaluated)
This is the right syntax. Just tested it, i.e group { next-server 192.168.1.1; host cyber { hardware ethernet 00:50:ba:3f:b5:d5; fixed-address cyber; option T129 "autoyast=http://192.168.1.1/profiles/ install=nfs nosshd"; option root-path "/work/CDs/original-8.0"; filename "vmlinuz.nbi-8.1"; } } And it works as expected! Check on the server side what is linuxrc trying to mount!
but the message is always that yast was unable to find the installation source. The option nextserver and filename are set accordingly to "server_ip" and "path_to_nfs_dir". On the kernel command line I specified tftp as the method for retrieving the control file. Using additional the install= parameter on the kernel command line it worked as expected.
In principle this should not be a problem if the path to the control file, i.e. the URL I have to specify manually on the kernel commandline is retrieved from the DHCP-server?
See above how I do that. But I agree with you that a solution for all cases must be provided.
This is a feature of the next release. It is already implemented and should answer all your questions above.
This is fine. Will the next release be only available with the next SuSE-Linux release i.e. 8.1 or is it available independently of the suse-linux release?
autoyast is not independent and itheavily relies on YaST2 and development of YaST2. So the answer is no, autoyast with new features will only be availbe with new SuSE Linux releases, i.e. 8.1 Regards, Anas -- Anas Nashif <nashif@suse.com>, SuSE Linux AG Montreal (Laval), Canada