Hi Mike,
Our VM is pretty easy. We have the z/VM base and added DIRMAINT and
Performance toolkit.
The z/VM base has all you need to run zLinux. Dirmaint makes your life a
lot easier and it can do some password expiration. RACF is a bit too
much for our system as we only have a few z/VM users.
I tried using the suggested compiler option CFLAGS=m31 but make fails with a
segmentation exception on rexx.img
http://www.ibm.com/developerworks/linux/linux390/perf/tuning_rec_compileoptions.html#opt31
Out former VM programmers have gotten pretty attached to ooRexx. Any help on
how to build
I would add VM:Tape and VM:Backup from CA to provide enhanced data
backuprestore capabilities. IBM offers Tape Manager and Backup Manager
(I think that is the name, Tracy Dean can correct me, please).
VM:Operator or Operations Manager can be added to help automate the
OPERATOR console for some
The best place to fix this is in the system you're using as a source for
the clone. What good is cloning, if, after every clone, you have to go in
and make hand modifications?
Change your source system to use by-path. Then you won't have a problem with
any of the clones. And, since you're just
On 12/8/2008 at 7:39 PM, Bruce Furber [EMAIL PROTECTED] wrote:
I tried using the suggested compiler option CFLAGS=m31 but make fails with a
segmentation exception on rexx.img
http://www.ibm.com/developerworks/linux/linux390/perf/tuning_rec_compileopti
ons.html#opt31
Out former VM
Adam
After reading thru the script, I'm wondering
And now I know that I shouldn't be taking the by-id as defaulted and I should
be using by-path when I setup the disk in yast
What is the difference between using the script and going back into yast,
Expert Partitioner
Editing each
On Tuesday, 12/09/2008 at 03:46 EST, Mike Eves [EMAIL PROTECTED]
wrote:
I am trying to establish a z/VM software stack to support zLinux and
would be
grateful for any advice or recommendations. I want to be able to run a
robust
and secure z/VM environment using traditional mainframe support
On Dec 9, 2008, at 3:21 PM, Tom Duerbusch wrote:
Adam
After reading thru the script, I'm wondering
And now I know that I shouldn't be taking the by-id as defaulted and
I should be using by-path when I setup the disk in yast
What is the difference between using the script and going
On Dec 9, 2008, at 3:45 PM, Adam Thornton wrote:
Plus, I just don't like yast.
I guess I'd better explain lest I ruffle too many feathers.
YaST is fine if you're administering one guest.
It becomes less useful in an environment where you have lots of
penguins, because it is not trivially
Hi,
* Short story *
Is it possible to relocate /etc/passwd, /etc/shadow and /etc/group files ?
* Long story *
I am building a system based on SLES10-SP2 with a read only root fs. My
work is based on the Redpaper REDP-4322-00, Sharing and maintaining Linux
under z/VM. Very inspiring work.
Sym-links should work initially. But consider bind mounting /etc from
a R/W point such as /local/etc (for example).
Changing passwords locally requires other files under /etc, so simply
sym-linking does not solve all your problems, but a bind mount /etc
goes much further.
On 12/9/08,
I do agree with that.
It is much easier from a documentation perspective as well as maintenance (when
dealing with lots), to have command line procedures and then code them into
scripts.
I only have a few images that have by-id used. And now, my
installation/generation procedures have been
On Tuesday 09 December 2008 16:50, Dominic Coulombe wrote:
* Short story *
Is it possible to relocate /etc/passwd, /etc/shadow and /etc/group files ?
You're right: you can't change the location of those files without rebuilding
pwutils with a different pathname. I forget where the code for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You may find some of the documents in this google search helpful:
http://www.google.com/search?hl=enclient=firefox-arls=org.mozilla%3Aen-US%3Aofficialhs=k7q=nfs+shared+root+filesystembtnG=Search
In particular, the second hit on that page Shared,
The software stack that we are running, so far successfully, is:
Dirmaint
RACF/VM
IBM Operations Manager for z/VM
Mainstar Provisioning Expert for Linux (the best provisioning tool imho)
Velocity Softwares ESALPS and zTune (again the best in the market imho)
FDR/UpStream (for the Linux client to
Hi,
Bind mounting the whole /etc directory does work fine. So does mounting a
disk containing only the /etc fs.
Thanks for your input.
On Tue, Dec 9, 2008 at 17:09, Richard Troth [EMAIL PROTECTED] wrote:
Sym-links should work initially. But consider bind mounting /etc from
a R/W point
On Tue, Dec 9, 2008 at 17:16, Edmund R. MacKenty
[EMAIL PROTECTED] wrote:
[...]
I do things almost this way in some filesystem layouts of my Provisioning
Expert product: I put /etc on a writable filesystem and populate it with
symlinks to a read-only filesystem. But for certain files,
On 12/9/08, Dominic Coulombe [EMAIL PROTECTED] wrote:
Would it be a better solution to have a local, read write /etc disk with
some symbolic links pointing to the secured files I want to be identical
between two clones ? I am open to other suggestions as well.
Unionfs.
18 matches
Mail list logo
