Mark Post wrote:
There are a few rules, for lack of a better term, that will apply to the Wiki,
none of them particularly onerous:
1. Although technically not required, we would prefer that anyone
contributing to the wiki create an account before doing so.
You should insist on this.
Mark Post wrote:
Cross-posted to Linux-390, IBMVM, and IBM-Main
The idea of having a Wiki (http://dictionary.reference.com/browse/wiki) for mainframe
Linux and z/VM has been floating around for some time. It was thought that having a Wiki
with a fair amount of content already in it would
Mark Post wrote:
On 9/23/2009 at 1:36 AM, Douglas M. Wooster d...@isomedia.com wrote:
-snip-
I'm sure one could use a Wiki as a discussion
forum, but it really seems better suited to developing, storing, and
searching reference material.
I'm not sure how this meme got started, but nobody is
John Summerfield wrote:
David, Jack was referring to the discussion of the wiki itself when he
was talking about discussion on the wiki.
That's correct, and that's all I was saying.
--
Jack J. Woehr# «'I know what it means well enough, when I find
http://www.well.com/~jax # a
No, I understood what he meant. I was expressing a sincere dislike for
diluting the discussion here with Yet Another Place to check for
things that interest me.
Doing the discussion using the discussion tools in Mediawiki is a
significant step backward in function in that I have to use
We are setting up a encryption product that uses the in-kernel crypto
facility. IBM has said that this should use the Crypto processors when
going through the api. We are trying to verify that we are truly using
the Crypto processors. Has anyone done this and secondly how can we
verify that the
My vote on this topic is that the real time, day to day discussions stay
here on the lists (VM and zLinux). I like the fact that the information
comes to me, via e-mail, with no effort on my part.
I think a proper role for the Linux Wiki would be to take on part of the
functionally of the
On Friday, 09/25/2009 at 11:30 EDT, Thompson, Michael E
michael_thomp...@uhc.com wrote:
We are setting up a encryption product that uses the in-kernel crypto
facility. IBM has said that this should use the Crypto processors when
going through the api. We are trying to verify that we are truly
So it's not letting you use the -k (--keep_volser) option unless you also
specify -a? Because, at least looking at the man page, -k should work as
long as you're in non-interactive mode and -c puts you in non-interactive
mode.
As in:
`fdasd -k -c /fdasdb.conf /dev/dasdb`
Also, you might also
You could have a zos person clip the volser.
Ron
Sent from my iPhone
On Sep 25, 2009, at 1:46 PM, Christian Paro
christian.p...@gmail.com wrote:
So it's not letting you use the -k (--keep_volser) option unless you
also
specify -a? Because, at least looking at the man page, -k should
Is there a way to rename a volume? I'm testing a DR scenario. I've formatted a
volume under ZM as UPST01, attached it to Linux (Redhat 5) and did
lsdasd
0.0.0201(ECKD) at ( 94: 0) is dasda : active at blocksize 4096, 1802880
blocks, 7042 MB
0.0.2201(ECKD) at ( 94: 4) is dasdb : n/f
Is there a reason why you create 3 partitions on one dasd? I would define 3
minidisks to VM on that one DASD or different ones and format each disk
individually with one partition per disk. These can be freely moved to
other volumes without any care.
Aria
-Original Message-
From:
if you are running this under z/VM you can just do a cpfmtxa and just
change the volser
Bauer, Bobby (NIH/CIT) [E] wrote:
Is there a way to rename a volume? I'm testing a DR scenario. I've formatted a
volume under ZM as UPST01, attached it to Linux (Redhat 5) and did
lsdasd
0.0.0201(ECKD) at
On Sep 25, 2009, at 1:52 PM, Aria Bamdad wrote:
Is there a reason why you create 3 partitions on one dasd? I would
define 3
minidisks to VM on that one DASD or different ones and format each
disk
individually with one partition per disk. These can be freely moved
to
other volumes without any
That covers symmetric encryption. In addition, if you are looking to see
if the MAC or hash functions are used, you can TRACE I B93E and TRACE I
B93F for the hashing, or TRACE I B91E for MAC operations.
Eric Rossman, CISSP®
ICSF Cryptographic Security Development
z/OS Enabling Technologies
On
Martha McConaghy wrote:
Wow..I don't really know how this discussion got so far off-base.
For several years now, there has been a lot of discussion in the z/VM
community about the need to have a place to collect the wisdom of the
elders, i.e. the knowledge and experience of those of us who
16 matches
Mail list logo
