[Redhat-s390-list] Roswell Beta Installation Success (Almost)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well, the "manifest read" errors weren't due to virtual memory problems.
They were due to missing RPM packages.  Apparently my over-night wget
session had intermittent network problems.  An RPM here and an RPM there
were missing out of the list of 1164.  Still, I experienced a problem at the
very end of the install:

sh-2.05# /sbin/zilo
Testlevel is set to 0
IPL device is: '/dev/dasda'
bootsector is: '/boot/ipleckd.boot'...ok...
bootmap is set to: '/boot/boot.map'...ok...
Kernel image is: '/boot/image-2.2.19-0.12vrdr'...ok...
original parameterfile is: '/boot/parmfile'tempfile is
/boot/param.2.2.19-0.12vrdr
...ok...final parameterfile is: '/boot/param.2.2.19-0.12vrdr'...ok...
ix 0: offset: 0130a9 count: 0c address: 0x00000000
ix 1: offset: 0130b6 count: 80 address: 0x0000c000
ix 2: offset: 013136 count: 80 address: 0x0008c000
ix 3: offset: 0131b6 count: 6f address: 0x0010c000
ix 4: offset: 0103f1 count: 01 address: 0x00008000
Bootmap is in block no: 0x000103f2
sh-2.05# /usr/sbin/authconfig --kickstart --nostart --enableshadow
--enablemd5
cannot determine current run level

GLib-CRITICAL **: file gstrfuncs.c: line 1348 (g_strsplit): assertion
`string != NULL' failed.


I'm not sure what this command was trying to do, but the IPL from DASD
afterwards was successful, and I was able to login as root.

Mark Post



[Index of Archives]     [Fedora General Discussion]     [LKML]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Linux s390]     [Gimp]     [Yosemite News]

  Powered by Linux