Hi Shawn, On 02/25/2009 09:26 PM, Shawn Wells wrote: > I'm trying to use the RHEL5 EAL4 IBM kickstart for s390x, and having > issues during the installation. When the process begins I get prompted > to validate my installation media source. Regardless of my input > (enter, white space, full value) the script only processes the first > character of my input.
> Has anyone been able to use the common criteria kickstarts? Never tried. As Scott has already spotted, there seems to be an error in the kickstart script on handling the user input for Installation source: > + echo_user -n Installation source > Ã�http://192.168.5.216/kickstart/dist/ks-rhel- > s390x-server-5-u3/¨ ? > + echo -n Installation source > Ã�http://192.168.5.216/kickstart/dist/ks-rhel-s390x > -server-5-u3/¨ ? > + read res > > [ HIT ENTER ] > > + Ã� -z ¨ > + Ã� . = .! ¨ For all other parameters it would show something like this: + Ã� -z ¨ + res=http://192.168.5.216/kickstart/dist/ks-rhel-s390x-server-5-u3/ + Ã� .http://192.168.5.216/kickstart/dist/ks-rhel-s390x-server-5-u3/ = .! ¨ However, the assignment of res is missing here, so it continues and thinks you entered "!" and drops you to the interactive shell. > + echo > + INSTSRC= > + echo_user > + echo > + echo_user Available destination disks: > + echo Available destination disks: > + echo_user dasda 2347.734375 > dasdb 2347.734375 > + echo dasda 2347.734375 > dasdb 2347.734375 > + sed s/\(Ã�0-9¨*\)\.Ã�0-9¨*$/(\1 MB)/ > + ask Install on which disk(s), comma separated dasda > + echo_user > + echo > + echo_user -n Install on which disk(s), comma separated Ã�dasda¨ ? > + echo -n Install on which disk(s), comma separated Ã�dasda¨ ? > + read res > + Ã� -z ¨ > + res=dasda > + Ã� .dasda = .! ¨ > + echo dasda > + DISKS_INST=dasda > + echo dasda > + sed s/,/ /g > + echo dasda > dasdb > + grep -q ^dasda$ > + ask Hostname (fully qualified) z219.z900.redhat.com If you don't want to fix the script code, you could to avoid the interactive mode and hope it won't reset INSTSRC as shown above. > + cmdline_val method cdrom > + cat /proc/cmdline > + sed -n s/.*method=\(Ã�^ ¨*\).*/\1/p > + Res=http://192.168.5.216/kickstart/dist/ks-rhel-s390x-server-5-u3/ > + Ã� -z http://192.168.5.216/kickstart/dist/ks-rhel-s390x-server-5-u3/ ¨ > + echo http://192.168.5.216/kickstart/dist/ks-rhel-s390x-server-5-u3/ > + INSTSRC=http://192.168.5.216/kickstart/dist/ks-rhel-s390x-server-5-u3/ > + Interactive= > + cmdline_val instdisk > + cat /proc/cmdline > + sed -n s/.*instdisk=\(Ã�^ ¨*\).*/\1/p > + Res= > + Ã� -z ¨ > + echo > + DISKS_INST= > + Ã� -z ¨ > + echo dasda > dasdb > + head -1 > + DISKS_INST=dasda > + Interactive=y This suggests to also specify instdisk=dasda in your parmfile to not drop into interactive mode. Maybe that helps. > My full log is attached. If helpful, a screen capture of me going > through all this is available at For general kickstart installs, I add the following to my parmfile to activate kickstart on s390x: cmdline RUNKS=1 ks=http://a.b.c.d/ks/anaconda-ks.cfg Without RUNKS=1 the loader won't start automatically but only after you login through the network which I wouldn't consider unattended. cmdline helps to keep the output readable on the 3270 console since otherwise you would get all the curses escape sequences of the newt-based TUI of anaconda. Both options aren't required though and ks=... should do it. Maybe you even want the network login for having a full screen terminal with the interactive part of common criteria configuration kickstart. But then again you might want to try cmdline, since then you'd see the interleaving of shell trace output from the kickstart script (on the console) and your user input (also in the same 3270 console). http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.3/html/Installation_Guide/s1-s390-steps-vm.html Since RHEL 5.3 you may want to consider adding PORTNO="0" to your CMS conf file (or parmfile if you don't have a conf file) in order not to get asked interactively by linuxrc.s390 for the OSA port number. Under z/VM you may want to consider to automatically get a full console log. This save you copy&paste of multiple screens full of console output. Just add the following line (preferably at the beginning of your REXX script rhel5.exec after the comment line): 'cp spool con start *' This will enable the logging of the console into the spooler, if not enabled already. Also add the following REXX script "constop.exec" to your CMS A disk: /* stop potential console logging to get the output with rdrlist */ 'cp spool con stop' 'cp spool con close' When you're done with testing something and want to get the log, IPL into CMS, call constop and then use rdrlist to retrieve the log from the VM reader. After this, you can send it to other machines in ascii mode using the CMS FTP client (or using cmsfscat from a Linux guest or anything else having access to your CMS A disk DASD). Steffen Linux on System z Development IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
