On Wed, 1 Oct 2003, Thorsten Hock wrote:
> > > I did it too several times with the same results...
> > > But keep on complaining about it - perhaps one day...
> > > Thorsten Hock
> >
> > Especially now that a Linux laptop preload is available for IBM field
> use. I
> > think the WINE gadget they'r
When I tested an adrdssu backup of the CDL disk that I created for booting
linux, silly me, I restored it to a volume that once upon a time, may have
had an IPL record on it.
What I want to know is that if you do a full volume copy using adrdssu, and
then do a restore, are you going to get cyl 0,
Hello,
Ive got some troubles with my guest lan definition. Every linux guest
can work together thru that lan, but nobody can reach the guest TCPIP.
TCPIP is able to ping himself but nobody else thru that lan.
Any idea ? Thanks in advance.
TCPIP profile:
DEVICE HIPER1 HIPERS E000
On Fri, 2003-10-03 at 03:40, Monteleone wrote:
> Iʼve got some troubles with my guest lan definition. Every linux guest
> can work together thru that lan, but nobody can reach the guest TCPIP.
> TCPIP is able to ping himself but nobody else thru that lan.
> Any idea ? Thanks in advance.
> TCPIP
I am running within an LPAR on 3 disk units;
unit 123d on volser LIN3
unit 123e on volser LIN4
unit 132f on volser LIN5
Our dasd is a IBM shark model 2105-F20: emulating 3390-3 disk
drives. Our tape drives are on a IBM VTS model 3494-B10: emulating
3590 Magstar tape drives.
I have ident
< snip
ftp://ftp.ox.ac.uk/pub/linux/s390/offlindr This works great for moving
your data to another disk/installation/etc. As far as a "hot standby" it
would be a little more difficult to implement.
Dave Jeffs
State of Utah
You don't say what is failing, so I'm going to have to guess. Since you're
going to be coming up on different device numbers, you will need to update
your parmfile to point to the new device numbers, and re-run zipl to write
that information out to disk. Have you done that?
Since you're using DF
What's new in release 3.00
Release date: 2 October 2003
Dynamically loaded module support for devices, instructions, and
operator console panels (Jan Jaeger, David "Fish" Trout, Ivan
Warren)
Shared and remote DASD support (Greg Smith)
z/990 (ALS4)
Well, it does that when dumping an MVS sysres, so I see no reason why it
wouldn't do it for any other operating system.
Mark Post
-Original Message-
From: James Melin [mailto:[EMAIL PROTECTED]
Sent: Friday, October 03, 2003 10:59 AM
To: [EMAIL PROTECTED]
Subject: ADRDSSU bakup of disks,
Ok. Just wanted to make sure. I didn't have 'pure' empirical data.
LEt me run this scenario by you Mark, since you know VM
LPAR linux her, as you know. Going to recover on VM, so I can have VM map
the devices I'm restoring to, to the addresses the parmfile is going to
expect.
So 7873 becomes B21
> LPAR linux her, as you know. Going to recover on VM, so I can
> have VM map
> the devices I'm restoring to, to the addresses the parmfile
> is going to
> expect.
>
> So 7873 becomes B213, etc
>
> Will that work? Then I'll zipl to the correct disk layout and
> IPL native.
A full dump (if you
Jim,
Sure, that's one of the beauties of z/VM. Another option is that since you
have multiple volumes, you could write out the modified parmfile/kernel
information to a second disk drive, and just IPL once from that device
number. That's how I test out new kernels to make sure I didn't hose
some
12 matches
Mail list logo
