Hi,
I'm looking for a workarround to implement the pathlist feature for sles10. pathlist is available since code 11 only. Until now I have to configure 3 ask secttions to retrieve the same password for 3 different pathes.
I'm wondering at which point in time ask popups arrive in stage 1. If I could change modified.xml with the script feature within ask then it would be a working approach. But if ask popups come into place after yast reads modified.xml this approach will fail.
Thanks for any hints,
Jochen
on Monday 23 August 2010 Jochen Schaefer wrote:
I'm looking for a workarround to implement the pathlist feature for sles10. pathlist is available since code 11 only. Until now I have to configure 3 ask secttions to retrieve the same password for 3 different pathes.
I'm wondering at which point in time ask popups arrive in stage 1. If I could change modified.xml with the script feature within ask then it would be a working approach. But if ask popups come into place after yast reads modified.xml this approach will fail.
it's even worse. First of all, the ask-dialogs on SLES10 raise AFTER modified.xml has been read and second of all, SLES10 ask-dialogs don't have a script feature. For SLES10 I have a driverupdate that you could use and that will provide you with scripts and pathlist. If that is an option.
autoinstall@lists.opensuse.org