On 10/11/05, Rick Troth [EMAIL PROTECTED] wrote:
These are what come to my eccentric mind.
IMHO you're way of the top with this. The interface for each of the
diagnose calls is completely different, i.e. different size control
blocks are passed back and forth between Linux and CP. There is not
Spin ... if the open() fails because of EBUSY,
then wait some fraction of a second and try again.
Or fail immediately with a the hypervisor is busy.
If after a wait and re-try it fails again, then fail
with the busy error message, or wait a second interval.
This is not rocket science.
Alan (Cox), Martin is right. The DIAG interface is complicated
and varies from one DIAG code to the next and requires guest real
addressing, which for Linux is kernel space. (And since CMS
has a flat addressing model, it can use pretty much any DIAG
function without pointer pains like
Is it possible to force z/OS USS NFS client to use only restricted ports?
I have to mount some NFS exports from z/Linux and I'd like to avoid using
insecure flag in /etc/exports and I don't want to have nfsd message
(connect from unprivileged port) whenever a client connects.
Thanks:
István
A couple of months back we had a network outage in New Zealand. It turned out
that someone in the capital had dug through one set of TelecomNZ's cables
with a hole digger, and a rat had eaten the backup. Since TelecomNZ owns
about 85 % of the NZ telecom capacity, that was most of the nation
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
Behalf Of John Summerfied
Sent: Wednesday, October 12, 2005 12:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: IP Networks survive disasters?
We have no public IP addresses on our side of the gateways,
so we
John Summerfied wrote:
The nice thing about /proc and (apparently) /sys is that one can, at a
pinch, control many functions by simply reading with cat and writing
with echo. There are several things particular to my Toshiba laptop that
I can control in this way, and if I can do that then I
Adam Thornton wrote:
I don't know if this would be considered an abuse of sysfs, but,
presuming that you'd have something like
/sys/devices/diagnose
Then for this you could just
cat /sys/devices/diagnose/8/status
In the same directory, you could have buffer_size, command, and so
forth.
McKown, John wrote:
This is likely a foolish question, but could the /sys/devices/diagnose
be set up like the /dev/fd ? E.g. for pid 12345, there exists an entire
tree /sys/devices/diagnose/12345. Then have self as a symlink to the
current pid so that for any particular pid, it could reference
Rick Troth wrote:
Lock the file.
Or have the device driver enforce single access.
But why lock? CP can handle multiple parralel diag8
calls from different processors just fine, and if
the Linux userspace interface is done proper there
is no race-issue at all.
File locking is limited to super
John Summerfied wrote:
Rick Troth wrote:
218 == real CPU ID info (for licensing, if nothing else)
In my ignorance, I'd expect to see that in /proc/cpuinfo
Isn't that what cpuinfo displays today? If no, how does it
differ?
--
Carsten Otte
IBM Linux technology center
ARCH=s390
John Summerfied wrote:
--w--- 1 root root 4096 Oct 12 08:02
class/pcmcia_socket/pcmcia_socket0/card_eject
PCMCIA socket is an excellent example for what /sys is useful: once you
plug your card, you'll see it connected to that socket there just as you
do see a qeth card connected to 3
China Awards 140k Desktop Linux Rollout
http://www.outsourcingpipeline.com/news/171204321
--
Dave Jones
V/Soft Software, Inc.
Houston
281.578.7544
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email
Please refer to:
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html
for the 2005-10-12 change summary:
New OCOs for Red Hat:
- tape_3590 for Red Hat Enterprise Linux 4 Update 2
(31-bit and 64-bit) kernel 2.6.9-22.EL (2005-10-05)
Happy downloading!
An excellent CMS based problem tracking and reporting tool is Cornell
University's PROBLEM system. It was developed in the early 1990s by
Andrew Hanushevsky and has a ton of sophisticated features. There's a
web interface available as well.
Drop me a note off-list if you'd like a copy. Support is
I agree with Martin that its not feasible to support a diag
pass-through.
There seems to be a clear customer requirement for making access to DIAG
function available.
The question we're debating is how, not why. The why is a foregone
conclusion.
Making a generic /dev/diag is not practical.
On Wednesday, 10/12/2005 at 01:56 ZE2, Carsten Otte [EMAIL PROTECTED]
wrote:
C8 == CP set language function
Afaics that can be done via diag8 as well!?
Actually, no. There is no CP SET LANGUAGE command. The diagnose is
useful so that the user's CP responses can be set to match the language
Ok. Thanks. I thought the chccwdev thing was all I really needed but wasn't
100% certain. I went forward using that as the replacement to echoing a
command request ala sles 8 and it all was fine. Must say the device
detection/allocation is much improved in SLES 9.
Post, Mark K
David Boyes wrote:
There seems to be a clear customer requirement for making access to DIAG
function available.
The question we're debating is how, not why. The why is a foregone
conclusion.
Maybe I missed that part of the thread, but would you mind showing me the
requirement? I mean, couple
David Boyes wrote:
I agree with Martin that its not feasible to support a diag
pass-through.
There seems to be a clear customer requirement for making access to DIAG
function available.
The question we're debating is how, not why. The why is a foregone
conclusion.
Making a generic
Alan Altmark wrote:
On Wednesday, 10/12/2005 at 01:56 ZE2, Carsten Otte [EMAIL PROTECTED]
wrote:
C8 == CP set language function
Afaics that can be done via diag8 as well!?
Actually, no. There is no CP SET LANGUAGE command. The diagnose is
useful so that the user's CP responses can be
On Oct 12, 2005, at 8:50 AM, Alan Altmark wrote:
14 == VM spool file manipulation
B8 == spool file XAB manipulation
These should be accessed via the reader/printer/punch device drivers
Malcolm write a few years ago, not as diagnose calls.
Two objections here:
1) Those drivers are not
- IUCV network protocol family
Why the need to make IUCV a network device? IUCV is not just a
point-to-point beastie, it's a single-application-to-single-application
protocol. The fact that it was used to create a network protocol for VM
and Linux is because an extra layer to mux and demux
Finishing last sentence...
- IUCV network protocol family
Why the need to make IUCV a network device? IUCV is not just a
point-to-point beastie, it's a single-application-to-single-application
protocol. The fact that it was used to create a network protocol for VM
and Linux is because an extra
Carsten Otte wrote:
David Boyes wrote:
There seems to be a clear customer requirement for making access to DIAG
function available.
The question we're debating is how, not why. The why is a foregone
conclusion.
Maybe I missed that part of the thread, but would you mind showing me the
Dumb quick question.
I'm trying to add SP2 to my 64 bit install process.
In mksles9root, the service packs are listed as:
SLES-9-SP-2-s390x-GM-CD1.iso
SLES-9-SP-2-s390x-GM-CD2.iso
SLES-9-SP-2-s390x-GM-CD3.iso
However, as just downloaded from Novell/Suse...where ever, the images
are:
Carsten Otte wrote:
Alan Altmark wrote:
[snip]
4 == examine real storage (CP memory, ie: hack VM from Linux!)
/dev/mem does that.
/dev/mem examines guest memory, not CP. IMO: Dangerous Idea. The ability
to read CP memory comes with the ability to change it.
Oh, CP memory not
On Oct 12, 2005, at 8:50 AM, Alan Altmark wrote:
88 == minidisk password validation
It is actually a proxy-LINK function for multi-client SVMs. It
also has
logon password and LOGON-BY validation. This could have some value.
Logon password and logonby validation would be very useful for
Tom,
Yes, you can just rename the files so mksles9root is happy.
I'm not really sure of the differences. We get our ISO images from a
common FTP server within IBM. Here are the details of mine:
# ls -l *SP-2*
-rw--- 1 root root 612798464 Jul 25 09:15
SLES-9-SP-2-s390x-GM-CD1.iso
Dave Jones wrote:
And as Adm T. has mentioned, put them someplace where everybody can
easily find them, and add functionality so a user space application
could be notified (async.) when a file appears on the rdr queue.
For the filesystem approach the notification comes for free
Adam Thornton wrote:
On Oct 12, 2005, at 8:50 AM, Alan Altmark wrote:
88 == minidisk password validation
It is actually a proxy-LINK function for multi-client SVMs. It
also has
logon password and LOGON-BY validation. This could have some value.
Logon password and logonby validation
On Wednesday, 10/12/2005 at 09:48 EST, Adam Thornton
[EMAIL PROTECTED] wrote:
Two objections here:
1) Those drivers are not easy to find. They're buried in a
supplementary rpm to a fairly obscure redbook, and you have to pick
apart the rpm by hand in order to rebuild the ur stuff.
Who said
Yep, the md5sub values are the same.
I updated the iso names in my copy of mksles9root and tried it out. No
errors.
So, it looks like I'm good to go.
Thanks for the conformation.
Tom Duerbusch
THD Consulting
[EMAIL PROTECTED] 10/12/05 10:21 AM
Tom,
Yes, you can just rename the files so
On Wednesday, 10/12/2005 at 05:24 ZE2, Carsten Otte [EMAIL PROTECTED]
wrote:
Adam Thornton wrote:
On Oct 12, 2005, at 8:50 AM, Alan Altmark wrote:
88 == minidisk password validation
It is actually a proxy-LINK function for multi-client SVMs. It
also has
logon password and
Neale Ferguson wrote:
Why the need to make IUCV a network device? IUCV is not just a
point-to-point beastie, it's a single-application-to-single-application
protocol. The fact that it was used to create a network protocol for VM
and Linux is because an extra layer to mux and demux application
Alan Altmark wrote:
Using VM for Linux authentication and access control purposes is an area
of intense interest to me.
Good. That extends my personal good ideas list to:
- reader/punch/printer device driver
- set language support
- IUCV network protocol family
- PAM support for CP
If we are to no longer receive management (or any) function
added to
CMS, we need the ability to perform the tasks CMS has traditionally
performed within the Linux environment. The fundamental
problem is to
enable all the existing architected communication paths between the
guest OS
Individual DIAGs can have their own variables in /sysfs/zvm/diag/nn as
appropriate. The lock mechanism is simple to implement in arbitrary
languages (works trivially in Fortran -- my favorite test), and is general
enough to accommodate arbitrary DIAGs.
Once that basic structure is in place,
On Wednesday, 10/12/2005 at 01:20 AST, David Boyes [EMAIL PROTECTED]
wrote:
As Rob van der Heij comments in another post, we don't need
the ability in Linux to be able to write a CP directory
management product...
Why not? Why shouldn't I write a directory management product as a
Where I thought it was something that would be fixed with a service
pack, it turns out, it was a novice type error.
In IPLing the text decks in CMS to start the Suse installation process,
I was punching out the 31 bit text decks and not the 64 bit text decks.
The install seemed to go normally,
RC is short for Release Candidate, while GM means Golden Master.
Usually, the last RC is declared to be the GM.
Mit freundlichen Grüßen / with kind regards
Martin Peschke
IBM Deutschland Entwicklung GmbH
Linux for zSeries Development
Phone: +49-(0)7031-16-2349
In my daily review of the linuxvm.org web server logs, I discovered that
someone at Microsoft mirrored the entire web site. H.
Mark Post
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
Hi,
If good IUCV support was available, *SPL would be rather cool. It's better
than DIAG14 because it is a defined asynchronous interface.
DIAG D8 might also be a fun addition to Linux.
Cheers,
Arty
--
For LINUX-390
On Wednesday, 10/12/2005 at 07:01 CET, Alan Cox [EMAIL PROTECTED]
wrote:
Which basically is the same as generic DIAG, the only difference being
that you are wrapping it in something. The more I follow this thread the
more generic diag seems right, even if it has a bitmask of not
supported
Hello from Gregg C Levine
An expression said by Pogo comes to mind. We have met the enemy. And
he is us.
---
Gregg C Levine [EMAIL PROTECTED]
---
Remember the Force will be with you. Always. Obi-Wan Kenobi
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf
Carsten Otte wrote:
John Summerfied wrote:
The nice thing about /proc and (apparently) /sys is that one can, at a
pinch, control many functions by simply reading with cat and writing
with echo. There are several things particular to my Toshiba laptop that
I can control in this way, and if I
On Oct 12, 2005, at 6:38 PM, John Summerfied wrote:
Rick's serialisation process, while it may lead to some head-
scratching
and syrup-taking, would at least alert to a race problem.
Taking? I prefer quaffing.
Adam
--
For
Carsten Otte wrote:
McKown, John wrote:
This is likely a foolish question, but could the /sys/devices/diagnose
be set up like the /dev/fd ? E.g. for pid 12345, there exists an entire
tree /sys/devices/diagnose/12345. Then have self as a symlink to the
current pid so that for any particular
I am under the impression that Linus does not want any more stuff like this in
/proc. I think he has requested that some of the stuff in /proc be moved
elseware.
The procfs filesystem was originally only for process related stuff. It was
kind of lazy to put other things in it.
-Original
Post, Mark K wrote:
In my daily review of the linuxvm.org web server logs, I discovered that
someone at Microsoft mirrored the entire web site. H.
One day a while ago I created the website mentioned below; there's a
wildcard DNS so I can and did just invent a name and configure Apache to
David Boyes wrote:
If process acquires lock on /sysfs/zvm/diag/8/lock (ie flock succeeds), then
write CP command into cmdstring to prepare for call. Once parameters are
loaded, open of /dev/diag8 and write a 1 to /dev/diag8 to execute the
I don't understand why you would use a device for
Carsten Otte wrote:
David Boyes wrote:
Suggestion, using DIAG 8 as an example:
Implemented in all DIAG drivers:
/sysfs/zvm/diag/nn/lock - semaphore to use as a
reserve/release flag. Processes
attempt to flock() this file.
Success
Carsten Otte wrote:
John Summerfied wrote:
--w--- 1 root root 4096 Oct 12 08:02
class/pcmcia_socket/pcmcia_socket0/card_eject
PCMCIA socket is an excellent example for what /sys is useful: once you
plug your card, you'll see it connected to that socket there just as you
do see a qeth
Carsten Otte wrote:
Rick Troth wrote:
Lock the file.
Or have the device driver enforce single access.
But why lock? CP can handle multiple parralel diag8
As I recall someone asserted there's a problem getting the proper cp
feedback at present. VM return codes don't map to *x return codes,
On Thursday, 10/13/2005 at 09:11 ZE8, John Summerfied
[EMAIL PROTECTED] wrote:
But why lock? CP can handle multiple parralel diag8
As I recall someone asserted there's a problem getting the proper cp
feedback at present. VM return codes don't map to *x return codes, so
another action is
Alan Altmark wrote:
On Thursday, 10/13/2005 at 09:11 ZE8, John Summerfied
[EMAIL PROTECTED] wrote:
But why lock? CP can handle multiple parralel diag8
As I recall someone asserted there's a problem getting the proper cp
feedback at present. VM return codes don't map to *x return codes, so
56 matches
Mail list logo
