[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 8:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Dasd Issue on Linux Guest.
So you can add the devices dynamically, but how do you then make them go
away, if you are only bringing them in to prepare them for use on another
system? Seems to me
So you can add the devices dynamically, but how do you then make them go
away,
set device range=range off echo'd to /proc/dasd/devices
There's a real handy script, dasd, described in the Large Scale Deployment
redbook:
#!/bin/sh
# dasd - simple utility for dynamic DASD management
if [ $1 = add
Maybe someone can help me. I've been trying to setup new dasd as well as
create a LVM for the combination of two volumes. What am I missing?
Because when I reboot nothing stays. I have to start all over it seems. I
used Yast1 to create LVM after they were formatted. I also issued the mount
reason you're having problems. When you do re-IPL, the volumes are unknown
to the system.
Mark Post
-Original Message-
From: Ketchens, LeMarr T. (RyTull)
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 11, 2003 6:07 PM
To: [EMAIL PROTECTED]
Subject: Dasd Issue on Linux Guest.
Maybe
]]
Sent: Tuesday, February 11, 2003 5:25 PM
To: [EMAIL PROTECTED]
Subject: Re: Dasd Issue on Linux Guest.
After updating your parmfile, you need to re-run zipl. Note that IPLing is
_not_ needed for a 2.4 system. You can dynamically bring the volumes on
with a
echo add device range=xxx[-yyy
As I said, re-run zipl.
Mark Post
-Original Message-
From: Ketchens, LeMarr T. (RyTull)
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 11, 2003 6:48 PM
To: [EMAIL PROTECTED]
Subject: Re: Dasd Issue on Linux Guest.
Now, what will keep the changes alive. I've done that, but I want
