Rich,
for DS8100 the MIH default seems to be 00:40 (40 seconds).
That should be quite enough, shouldn't it ?
ciao Lutz
-
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
Hello,
Anyone having problems during installation of Debian/390 R3.1 with LCS
support?
Seems that network doesn't come up, so we can't continue install from ftp
site.
Any hint about?
TIA
Carlos Bodra
Sao Paulo - Brazil
--
For
Hi, gang.
I don't have any hands-on experience with the DS8100, but I would
suspect that 40 seconds would be a reasonable setting for MIH time out.
This sounds silly, I know, but is the device plugged into a wall socket,
powered up and correctly connected to the host?
Have a good one.
DJ
Lutz
Evidently my MITIME setting is being overridden to 40 seconds as well.
So, that must not be the problem.
Dave Jones wrote:
Hi, gang.
I don't have any hands-on experience with the DS8100, but I would
suspect that 40 seconds would be a reasonable setting for MIH time out.
This sounds silly, I
Need some guidance here
We issued the shutdown command for a Linux test image and after it
went down we IPL'ed the LPAR. In the boot process coming up we are
receiving a the message that /dev/opt/opt a LVM reiserfs file system
has problems. I can see from the log that FSCK has tried to fix
I have a SuSE SLES 9 system, that I have configured with a 256 M Virtual
Disk for Swap, as well as a secondary minidisk swap disk. Both show up
when I do a 'cat /proc/dasd/devices' after booting:
0.0.0301(ECKD) at ( 94:16) is dasde : active at blocksize: 4096,
18 blocks, 703 MB
On Jul 18, 2005, at 9:15 AM, John Kaba wrote:
I have a SuSE SLES 9 system, that I have configured with a 256 M
Virtual
Disk for Swap, as well as a secondary minidisk swap disk. Both
show up
when I do a 'cat /proc/dasd/devices' after booting:
0.0.0301(ECKD) at ( 94:16) is dasde :
Unless he's running a 64-bit system, in which case the DIAG driver is
not available.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Monday, July 18, 2005 10:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problem picking up
nope, I'm running it on a 9672 R16 under z/VM 4.4
Post, Mark K
[EMAIL PROTECTED]
m To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port
Hi,
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 15.07.2005 16:44:39:
But up to now we run into problems defining LVM2-groups including these
large Mdisks. After definition SLES9-guest comes not up properly,
only in S-mode (maintenance).
There shouldn't be a problem with the size of
I have finally ordered SLES9 for zseries.
I ordered media which I have received.
There are 6 CD's for SLES9 64-bit for zseries and
6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9.
Why did I think SLES9 was 64-bit only?
I'm not sure anyone can answer that question.
But
I'm just not able to perform an online update from
http://sdb.suse.de/download like I've always been able to do in the
past. I've been away for 2 weeks and thought maybe something had
changed.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Tom Driscoll
On Monday 18 July 2005 3:27 pm, Smith, Ann (ISD, IT) wrote:
Make a SLES 9 install server, The doc on this is on CD1 under the docu
directory.
-Cameron
I have finally ordered SLES9 for zseries.
I ordered media which I have received.
There are 6 CD's for SLES9 64-bit for zseries and
6 CD's for
On Mon, 18 Jul 2005, Smith, Ann (ISD, IT) wrote:
I have finally ordered SLES9 for zseries.
I ordered media which I have received.
There are 6 CD's for SLES9 64-bit for zseries and
6 CD's for 31-bit for s/390. I did not realize there was a 31-bit SLES9.
Why did I think SLES9 was 64-bit only?
What we did around here is the following (we don't have zVM but install
zLinux as LPAR)
mkdir /sles9
then we downloaded each iso into this location (each for your CD under the
same directory).
then we downloaded the sp1 iso's (two iso)
note: now you can get sp2 as well.
then downloaded
Than you for anwering, Stefan.
No, as far as I understood one of my zLinux-staff colleagues his boot
parameters
mark dasd-device addresses as ('all will be sensed and taken' ...).
After formating the phys. volumes, defining LVM's and appropr. group via
Yast we shutdown
and reboot SLES9.
Lance:
am I correct in saying that the mount point for the /dev/opt/opt (lvm) file
system is /opt?
The approach I follow when creating something like an /opt is to create an
/opt-bkup before proceeding (ie. copy recursive opt to opt-bkup).
Then I create the vgopt and lvopt (lvm) so I don't have
I can get to it for SLES9 updates but not SLES8. Any ideas? Maybe YAST
differences?
Thanks.
Wiggins, Mark [EMAIL PROTECTED]
Sent by: Linux on 390 Port LINUX-390@VM.MARIST.EDU
07/18/2005 01:11 PM
Please respond to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
To
LINUX-390@VM.MARIST.EDU
cc
Subject
I just tried it, and it works for me.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Wiggins, Mark
Sent: Monday, July 18, 2005 3:11 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Is sdb.suse.de down???
Is the sdb.suse.de site is down. I tried
Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that
didn't work either. Is there anywhere else that I can download updates
from? The address is pingable but not accessible...
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792
Hi List,
I'm trying to install the Slackware from the site at
http://ftp.ibiblio.org/pub/Linux/distributions/slack390/slack390-10.0/ and am
at the point where the VM reader install files are IPLed and ready to start
formatting DASD.
When I first did this, I did a dasdfmt and got a cannot open
21 matches
Mail list logo
