On Tue, Jul 01, 2003 at 11:52:47PM -0500, Richard Troth wrote:
At home I've been hit by the you're on a dial-up type bounce.
Not true, but I'm small enough to have no means to fight it.
Eventually I will have to get an msn.net account to do e-mail.
It seems right and just: we should all
Greetings; (Posted to VMESA-L and VSE-L and LINUX-390)
- - Now in its sixth year! - - Includes VSE and linux/390!
I have set up a public service web page at
http://www.eskimo.com/~wix/vm/
for posting positions available and wanted for VM, VSE and linux/390.
Please visit the web
On Wed, 2 Jul 2003, Tzafrir Cohen wrote:
On Tue, Jul 01, 2003 at 04:38:51PM -0500, Richard Troth wrote:
FYI, for those who care about such things,
this list is being tracked by http://www.mail-archive.com/.
Sorry for the duplicate info if this was mentioned before.
Why should you
On Wed, 2 Jul 2003, Lionel Dyck wrote:
Another good article on SCO's water torture of the Linux community
http://www.businessweek.com/magazine/content/03_27/b3840089.htm
Is the authour prejudging this
True, SCO should be free to protect its software, in this case core
pieces of the Unix
On Wed, 2 Jul 2003, Lionel Dyck wrote:
Another good article on SCO's water torture of the Linux community
http://www.businessweek.com/magazine/content/03_27/b3840089.htm
Notice the date?
JULY 7, 2003
--
Cheers
John.
Join the Linux Support by Small Businesses list at
On Wed, 2 Jul 2003, Lionel Dyck wrote:
Another good article on SCO's water torture of the Linux community
http://www.businessweek.com/magazine/content/03_27/b3840089.htm
Is the authour prejudging this
True, SCO should be free to protect its software, in this case core
pieces of the
I wanted to get an idea of what others are doing in the way of cloning and
then upgrading their z/VM - z/Linux guests. I am running SuSE Linux 7.x
and will soon be upgrading to SuSE 8. In our Proof of Concept their is a
great desire to share binaries. I; however, can not figure a practical
way
Hello all,
does anyone have an installation checklist and / or caveats
do's dont's on installing a SuSE SLES X under z/VM?. The intended use
for the Linux solution is to host a Web server(s).
Regards,
J. Cassidy
See:
http://biz.yahoo.com/iw/030702/055118.html
Dave Jones
http://www.sinenomine.net/
Houston, TX
281.578.7544 (voice)
I only got a few responses to this note (and I'll follow up with those) --
not a big problem, since I've got contacts/references/resources to use.
But I'd hoped for in the trenches information, good/bad news about using
VM for d/r, comparisons with alternatives, lessons learned, evaluations of
On Thu, 2003-07-03 at 08:05, Eric Sammons wrote:
I wanted to get an idea of what others are doing in the way of cloning and
then upgrading their z/VM - z/Linux guests. I am running SuSE Linux 7.x
and will soon be upgrading to SuSE 8. In our Proof of Concept their is a
great desire to share
John,
The Distributions Redbook chapter on SuSE is still reasonably accurate as a
starting point. There are some differences in how YaST steps through the
installation, but nothing terribly drastic.
Mark Post
-Original Message-
From: John Cassidy [mailto:[EMAIL PROTECTED]
Sent:
On Thu, Jul 03, 2003 at 08:52:22PM +0800, John Summerfield wrote:
On Wed, 2 Jul 2003, Tzafrir Cohen wrote:
On Tue, Jul 01, 2003 at 04:38:51PM -0500, Richard Troth wrote:
FYI, for those who care about such things,
this list is being tracked by http://www.mail-archive.com/.
Sorry for
There is a redbook at the z/vm site that may help you. It discusses the
use of a basevol (containing shared r/o code) and mounting a guestvol
(server unique code r/w over the r/o basevol directories). For example,
the basevol is initially built and it has an /etc. The clone will link r/o
to
On Thu, 2003-07-03 at 09:49, Richard Masuda wrote:
There is a redbook at the z/vm site that may help you. It discusses the
use of a basevol (containing shared r/o code) and mounting a guestvol
(server unique code r/w over the r/o basevol directories). For example,
the basevol is initially
It depends on your setup. I had a hard time going from SLES7 to SLES8.
1. I was using SMB from a Win/95 machine to install SLES7. SLES8
requires Win/98 or above to use SMB for installs.
2. The old copy of PUTTY used port 23 for installation. SLES8 has a
new PUTTY which also seams to
That's true, bind mounts are scary at first but not so bad after some use.
I would not use the technique unless I had quite a number of clones and as
you say, very strict policies. I am like the original poster and wondering
how cloing in the VM environment is being done (while also sharing as
On Thu, 3 Jul 2003, Tzafrir Cohen wrote:
On Thu, Jul 03, 2003 at 08:52:22PM +0800, John Summerfield wrote:
On Wed, 2 Jul 2003, Tzafrir Cohen wrote:
On Tue, Jul 01, 2003 at 04:38:51PM -0500, Richard Troth wrote:
FYI, for those who care about such things,
this list is being tracked
They have no legal force whatsoever on the recipient. Therefore they do
not protect the sender from HIPAA regulations. You are still fully
liable under HIPAA for any confidential information you include in an email.
[EMAIL PROTECTED] wrote:
Probably legally required, like the one at the end of
On Iau, 2003-07-03 at 21:51, Stephen Frazier wrote:
They have no legal force whatsoever on the recipient. Therefore they do
not protect the sender from HIPAA regulations. You are still fully
liable under HIPAA for any confidential information you include in an email.
Does save having to argue
And, thinking about it, probably means that *I* will be held legally
responsible for any mis-use of information instead of the company. Yet
another way to sc**w the worker.
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Applications Solutions Team
+1.817.255.3225
This message
On Thursday, 07/03/2003 at 03:47 EST, McKown, John
[EMAIL PROTECTED] wrote:
And, thinking about it, probably means that *I* will be held legally
responsible for any mis-use of information instead of the company. Yet
another way to sc**w the worker.
What's kind of funny is that the disclaimer
If you include any confidential information in an email and someone
misuses it then you are legally responsible. Your company hopes that
maybe by including the message they might not be held responsible also.
However, if someone wants to sue because of a disclosure they will sue
both you and your
I recently had an inquiry about installing Debian natively on a P/390.
Turns out that building an OMA tape with a TDF just doesn't work, or at
least, didn't for me. So
GETTING DEBIAN RUNNING ON THE P/390
This *should* be a simple matter of crafting a TDF file from the kernel,
parmline,
24 matches
Mail list logo
