I am trying to build a Basevol/Guestvol Shared OS DASD system. It appears
that
the SuSE 9 system is different from SuSE 8. I have a bunch of SuSE 8
system
up sharing the OS. Is there anything special to make the SuSE 9 work?
I don't see why that would not work. Have'nt tried though. In case you're
On Mon, Aug 08, 2005 at 10:33:57AM -0400, Jon Brock wrote:
We are indeed using different userids and passwords for the different shares
Have you looked at Samba ACL support? ACLs (Access Control Lists) allow
you to create a more complex security environment than can be created
using simple Unix
As to /dev/3270/tub, believe me, devfs was the furthest thing from my
mind. Here's what I was talking about. Consider the device /dev/tty.
It exists to provide a path for the application to the current
controlling tty. What would the application have to do (absent
stdout/stderr) to
For those interested, the .iso CD images for SUSE Professional 9.3 are
now available from the mirror sites. And:
Novell announced the creation of the openSUSE project, a new initiative
sponsored by Novell aimed at promoting the adoption of Linux worldwide.
Hosted at http://www.opensuse.org,
While I agree that xip2 is (really) great thing, what everyone
recommending it's use is missing is this: Bill Scully went to great
effort to document just how to set up a workable basevol/guestvol
arrangement. No one has really done that for xip2. The documentation
you point to is very
Is anyone running TSM Server on zLinux? If so, are you having any issues?
Brad Brewer
Humana Inc.
Technical Services
System Software
(502)580-3086
The information transmitted is intended only for the person or entity to which
it is addressed and may contain CONFIDENTIAL material. If you
I am currently running on a IBM Z800 processor with an IFL processor.
The IFL processor has a SuSe Linux LPAR that has TSM running on it. I am
not currently having an problems.
[EMAIL PROTECTED] 8/10/2005 12:34:44 PM
Is anyone running TSM Server on zLinux? If so, are you having any
issues?
What are you using for backup media?
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Mike Lovins
Sent: Wednesday, August 10, 2005 1:41 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TSM
I am currently running on a IBM Z800 processor with an IFL processor.
The
I am using IBM 3590 B11 tape drives to backup the TSM database. I am
using Hatachi 7700E disk to store the data from the server and
workstations that I backup. The migration is using the IBM B11 tape
drives.
[EMAIL PROTECTED] 8/10/2005 12:42:07 PM
What are you using for backup media?
Bob,
I don't see much running and if I try and start yast
By chance, are you trying to start yast from a 3270 session?
What am I missing?
You probably want to use SSH sessions out of habit after the install. 3270
sessions are still handy for CP commands.
If you have a Windows desktop, most
I've been letting the blocksize default to 4096 for dasdfmt, but I'm getting
abuse from zOS types for not using half-track blocking, and the space I'm
losing to IRGs.
What are the possible values for the blocksize, and what are the pros and cons
of changing away from the default of 4096?
My understanding is that the block layer in Linux does not allow block sizes
larger then the page size of the system. Therefore on Intel and zSeries
hardware 4096 is the largest possible block size. I think this is the same for
pSeries as well.
If you could have a larger block size it would
Hi, Martin
Thanks for the patch.
A few problems remain. Minor number is not the same as tty-index
except in the (typical) case that driver-minor_start is 0; the index of
the first tty will always be 0. I've had success in initializing
driver-minor_start to 1 and the argument of
On Wednesday, 08/10/2005 at 06:42 MST, Richard Hitt [EMAIL PROTECTED]
wrote:
A few problems remain. Minor number is not the same as tty-index
except in the (typical) case that driver-minor_start is 0; the index of
the first tty will always be 0. I've had success in initializing
14 matches
Mail list logo
