There were a couple more changes that needed to be made to a couple of sed
commands as well, I discovered. I'm including a patch file that should fix
what needs fixing. I don't know if it will get through the mailing list
server or not, so I'm also sending a copy to Steve directly. I am also
going to cut and paste it into this email, but there are tab characters and
line-wraps that are going to look like blanks and newlines to most people,
so beware of that.
Mark Post
--- sbin/rhsetup Wed Oct 24 11:15:13 2001
+++ sbin/rhsetup Wed Oct 31 12:58:27 2001
@@ -91,10 +91,10 @@
get_all_dasds()
{
unset online_dasds
- TMP="`grep ':active' < /proc/dasd/devices | grep -v
'\(^019\|none\)'`"
+ TMP="`grep 'active' < /proc/dasd/devices | grep -v
'\(^019\|none\)'`"
for i in "$TMP"; do
online_dasds="`echo "$i" |
- sed -e 's/.* \(.*\):.*:.*/\/dev\/\1/'`
$online_dasds"
+ sed -e 's/.* is \(dasd.\).*/\/dev\/\1/'`
$online_dasds"
done
if [ -z "$online_dasds" ]; then
echo "No DASD devices found. Please check your setup."
@@ -102,7 +102,7 @@
else
echo "DASD devices "
echo "$online_dasds found."
- eval `cat /proc/dasd/devices | sed '/unknown/D;s/^.*[(]\([
0-9]*\)[:]\([ 0-9]*\)[)].*\(dasd[a-z]*\)[:].*$/\1 \2 \3/g' | awk ' $1 {
printf "mknod /dev/%s b %d %d; mknod /dev/%s1 b %d %d; mknod /dev/%s2 b %d
%d; mknod /dev/%s3 b %d %d",$3,$1,$2,$3,$1,$2+1,$3,$1,$2+2,$3,$1,$2+3; }'`
+ eval `cat /proc/dasd/devices | sed '/unknown/D;s/^.*[(]\([
0-9]*\)[:]\([ 0-9]*\)[)].*\(dasd[a-z]*\)[: ].*$/\1 \2 \3/g' | awk ' $1 {
printf "mknod /dev/%s b %d %d; mknod /dev/%s1 b %d %d; mknod /dev/%s2 b %d
%d; mknod /dev/%s3 b %d %d;",$3,$1,$2,$3,$1,$2+1,$3,$1,$2+2,$3,$1,$2+3; }'`
return 0
fi
}
-----Original Message-----
From: sstock@mail.unomaha.edu [mailto:sstock@mail.unomaha.edu]
Sent: Wednesday, October 31, 2001 11:48 AM
To: redhat-s390-list@redhat.com
Subject: RE: [Redhat-s390-list] rhsetup and loader errors
Does anyone know a good way to fix this issue? We tried to change the
file so that grep was looking for ": active" versus ":active" using sed and
then going ahead with rhsetup, but we continue to get the same error
mentioned below. Any help on what would be a better way to fix the rhsetup
file would be most appreciated.
Steve Stock
Senior Technology Research Fellow
University of Nebraska at Omaha
----- Forwarded by Steven Stock/FACSTAFF/UNO/UNEBR on 10/31/2001 10:42 AM
-----
"Post, Mark K"
<mark.post@eds.com> To: "'redhat390'"
<redhat-s390-list@redhat.com>
Sent by: cc:
redhat-s390-list-admin@ Subject: RE:
[Redhat-s390-list] rhsetup and loader errors
redhat.com
10/30/2001 02:05 PM
The first problem is due to the fact that the format of /proc/dasd/devices
changed sometime between 2.4.7 and 2.4.9:
# uname -a
Linux linux.eds.com 2.4.7-10.dbgBOOT #1 SMP Thu Sep 27 13:15:51 CEST 2001
s390 unknown
# cat /proc/dasd/devices
0301(ECKD) at ( 94: 0) is dasda:active at blocksize: 4096, 90000 blocks,
351 MB
0300(ECKD) at ( 94: 4) is dasdb:active at blocksize: 4096, 126000
blocks,
492 MB
0302(ECKD) at ( 94: 8) is dasdc:active at blocksize: 4096, 36000 blocks,
140 MB
0303(none) at ( 94: 12) is dasdd: unknown
0304(none) at ( 94: 16) is dasde: unknown
# uname -a
Linux linux.eds.com 2.4.9-7BOOT #1 SMP Wed Oct 24 13:51:03 CEST 2001 s390
unknown
# cat /proc/dasd/devices
0301(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 90000
blocks, 351 MB
0300(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 126000
blocks, 492 MB
0302(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 36000
blocks, 140 MB
0303(none) at ( 94: 12) is dasdd : unknown
0304(none) at ( 94: 16) is dasde : unknown
The rhsetup script is doing a grep on ':active' and not finding it now that
it is ': active' instead. I don't experience the same problem you do when
I
execute loader. I am able to start retrieving files from my FTP server.
Mark Post
-----Original Message-----
From: Jean-Francois Jiguet [mailto:jjiguet@fr.ibm.com]
Sent: Tuesday, October 30, 2001 10:53 AM
To: redhat-s390-list@redhat.com
Subject: [Redhat-s390-list] rhsetup and loader errors
On a 9672 with VM/ESA 240, the installation of the RedHat linux for S/390
beta version never complete.
Using 'rhsetup', I received :
# rhsetup
DASD devices found.
/bin/rhsetup: syntax error: `(' unexpected
get_all_dasds
Stopped installation. No cleanup is done!
#
Using 'loader', I received on the VM console of Linux userid the following
messages :
# loop: loaded (max 8 devices)
User process fault: interruption code 0x10
failing address: 0
CPU: 0
Process loaderbin (pid: 47, stackpage=07579000)
User PSW: 070de000 80462cd2 Not tainted
task: 07578000 ksp: 07579d08 pt_regs: 07579f68
User GPRS:
00000000 00000000 004c9bd0 7ffff674
80496a34 7ffffe91 7ffff580 7ffff584
004c0bac 00000000 7ffff580 00000000
0043f578 80462c84 80462cb8 7ffff520
User ACRS:
00000000 00000000 00000000 00000000
00000001 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
User Code:
43 20 b0 00 bf 2e d0 04 89 20 00 01 5a 20 80 00 a7 18 00 08
Error happens after choosing the ftp option on the first panel (ftp
,http,nfs). Message received was " Memory fault "
I start 'loader' with different memory size (32meg, 128meg,
256meg) but I received every time the task abend.
Timestamp for initrd.img and kernel.img is 2001/10/24.
Any idea's
Jean François
_______________________________________________
Redhat-s390-list mailing list
Redhat-s390-list@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-s390-list
_______________________________________________
Redhat-s390-list mailing list
Redhat-s390-list@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-s390-list
_______________________________________________
Redhat-s390-list mailing list
Redhat-s390-list@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-s390-list
Attachment:
rhsetup.diff
Description: Binary data
