Am 29.09.2010 09:37, schrieb Bern VK2KAD:
I have hit a couple of obstacles using the Hercules images. Some
seem to
be related to me using a Windows Hercules rather than a Linux platform.
First was that the image expands into a full 3390-9 image which is
over 8GB
on NTFS.
After dasdcopy this came back down to <500MB so it is now manageable.
After just adding the volume to an existing Hercules config I found
that the
image must be on device 120 - I detected conflicts between Fedora and
other
distros I have in the same config file if the Fedora disk wasn't 120 !!.
The latest glitch for me is that I cannot logon as root (or anyone for
that
matter)
Here is a snip of the console log >>>>
Fedora release 14 (Laughlin)
Kernel 2.6.35.4-12.fc14.s390x on an s390x (console)
s390 login:
.root
root
c
Fedora release 14 (Laughlin)
Kernel 2.6.35.4-12.fc14.s390x on an s390x (console)
s390 login:
.install
install
c
Fedora release 14 (Laughlin)
Kernel 2.6.35.4-12.fc14.s390x on an s390x (console)
s390 login:
.
c
Fedora release 14 (Laughlin)
Kernel 2.6.35.4-12.fc14.s390x on an s390x (console)
s390 login:
Something not quite right ?? I wanted to logon via the s390 console
to get
the ifconfig to match my local network.
Sorry about the big DASD. We'll use a smaller one next time.
Phil tracked the login problems down to a selinux problem with the
console. You'll need to set it to permissive until we fix that.
Logins per ssh should work though, and you won't need to change selinux
mode if you intend to access the system via ssh only.
Karsten
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
