I corrected gateway (good catch, thank you) but
problem is still the same. Could you email me parmfile
which works for you and doesn't ask for hostname ?
Thanks
Marian
--- Post, Mark K [EMAIL PROTECTED] wrote:
If you cut and pasted this, as opposed to typing it
in, I see a problem.
Your
Hmmm, it looks like Hostname from parmfile is not used
at all. In documentation they mention it only once
where they explain how to code parameters, but later
where all possible parameters are listed, Hostname is
missing.
When I tried to setup without parameter file, I was
not asked for hostname
3590s come in SCSI and channel-attached varieties -- they can be one or the
other but not both. There is a physically different controller card installed
on the drive to differentiate the two variations.
If you configure the drive as SCSI, then the traditional IBM operating systems
can't use
On Friday 27 October 2006 22:53, Rich Smrcina wrote:
The author asks that I get the Valgrind tool to attempt to debug this.
The web site (http://www.valgrind.org) indicates that the tool runs on
certain platforms (s390/s390x is not mentioned).
No, Valgrind is currently not ported to the s390
At this time, I can't. I'm waiting for some z/VM maintenance to go on
so I can even IPL SLES10.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Marian Gasparovic
Sent: Sunday, October 29, 2006 7:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re:
Lee Stewart wrote:
Depends on when you want to check it...
After it's activated, look at /proc/dasd/devices
0.0.0200(ECKD) at ( 94: 0) is dasda : active at blocksize:
4096, 600840 blocks, 2347 MB
0.0.0190(ECKD) at ( 94:24) is dasdg (ro): active at blocksize:
4096, 19260 blocks,
Mark Perry wrote:
Filesystems live in LVs and LVs in VGs which are made up from PVs(=Disks)
1) It is the LV that is striped and not the Filesystem.
2) A striped LV can be expanded providing it uses the same PVs in its
VG. (This implies you did not fully utilize the PVs to begin with of
course!
