Mark, I use the ^ = x'5F' from a real 3279 terminal, I have traced it in linux where ^c is translated to a x'03' so I'm almost sure that it is the right character ( the same character also works if I use the original boot procedure)
After you told me that ctrl-c works for you I tested it in an old SuSE 2.4.7 and there it also works. We now run kernel 2.4.19 with updates from the IBM May stream and most other packages from RedHat. So the problem is probably in some package. I tried login from suse but that didn't help. Mats Westlund -----Original Message----- Mats, I just tried this with bootshell on a Linux/390 2.4.19 system, and it works for me: bash-2.04# sleep 20 && echo Time ran out sleep 20 && echo Time ran out ^c bash-2.04# What character are you using for the CTRL code? It should be a carat (^). Mark Post -----Original Message----- From: Mats Westlund (GIS) [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2003 2:43 AM To: [EMAIL PROTECTED] Subject: CTRL-C and bootshell on 3215 console window If we use the standard login program CTRL-C works fine when we enter it from the VM 3215 console window. If we change the /etc/inittab to use the bootshell written by Mike Kershaw or to the script below that was published on this newsgroup the CTRL-C don't work. We would like to have the features this kind of bootshell gives us but we also would like the CTRL-C to work. Could someone tell us how to fix that or explain why it don't work Boot shell #!/bin/bash CONSOLE="$1" if [ -z "$CONSOLE" ] ; then \ CONSOLE=/dev/console ; fi PS1=`hostname` #PS1="$PS1 # " PS1="$PS1 \\\$ " export PS1 SHELL=/bin/sh if [ -x /sbin/sh ] ; then SHELL=/sbin/sh ; fi exec $SHELL -i 0<$CONSOLE 1>$CONSOLE 2>$CONSOLE Thanks, Mats Westlund
