Hi Steffen, I now managed the desired behaviour via the setupcmd parameter. It calls a wrapper script which executes the setcsid `console` ... command and checks /etc/yast.inf in a while loop for the "Aborted" entry. If the entry exists a reboot -f ensures that no manual interaction can be done at console anymore. Thanks again for this nice hint. Now the only problem left is to induce yast/curl/aira2c to use client certificate based authentication. But this is another topic. Jochen

...

...

Steffen Winterfeldt 07/25/11 3:30 PM >>> Hi Jochen,

On Mon, 25 Jul 2011, Jochen Schaefer wrote:

Hi Steffen,

do you know where to find some documentation about yast.inf?

Old linuxrc versions used to have some bits about it: http://www.gitorious.org/opensuse/linuxrc/blobs/sl_10.1/README.linuxrc Newer yast variants write 'abort: 1' to differentiate between crash & user abort. One more things: yast exit code is 0 (install ok) vs. !=0 (crash, abort). Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org