|
Re: SLES9 on z/VM, autoyast and <dasd> section: msg#00033linux.suse.autoinstall
On Tuesday 11 April 2006 20:52, Kai Dusek wrote: > > Have you tried a custom rule? > > Custom rules doesn't help us since we cannot assume _any_ dasd channel id > - so (that is my understanding) we would have to provide 2^16 different > custom xml profiles (one for each dasd id 0000-FFFF). okay then you can configure a webserver in a way, that it holds a CGI script that analyses the URL that was called and creates such a dasd section on the fly. Of course you have to use http then for fetching the profile. But anyway, since you are already using a patched driverupdate (SP3 has no DASD support if I remember correctly, so you must be using a patch for the installation system I did a while ago for some other IBM guys). Could you test another patch for SLES9SP3? Then I'll try to fix that for SLES10 and SP4 of SLES9. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@xxxxxxx, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: SLES9 on z/VM, autoyast and <dasd> section: 00033, Kai Dusek |
|---|---|
| Next by Date: | Adding driver to repository: 00033, Johan Kielbaey |
| Previous by Thread: | Re: SLES9 on z/VM, autoyast and <dasd> sectioni: 00033, Kai Dusek |
| Next by Thread: | autoyast on suse 10.1 beta9 x86_84: 00033, Martin Vogt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |