Thanks all , I will chat to the Capman and see what the plan might be.
regards
Gerard
-Original Message-
From: John Summerfield [mailto:[EMAIL PROTECTED]
Sent: 22 July, 2003 17:50
To: [EMAIL PROTECTED]
Subject: Re: Linux and VSAM
On Tue, 22 Jul 2003, Ceruti, Gerard G wrote:
Hi All
I
And a generous offer from Microsoft:
http://news.zdnet.co.uk/story/0,,t269-s2137959,00.html?rtag=zdnetukhompage
It's hardly generous, unless you were being ironic. It's perfectly normally for
suppliers
to indemnify customers, with the twin provisos that the customer notifies the supplier
Mark,
Thanks for the reply. For the first time, SuSE had a good response time.
The whole problem started with a mix up on the proper key to register. It
did not raise it's ugly head until we attempted a kernel upgrade for a
specific install. All is good again after registering the proper key
I built the Debian Linux 2.4.21 kernel with Leland's patch, and sar
and iostat are now reporting I/Os.
Thanks very much for your help.
--Robert
-Original Message-
From: Lucius, Leland [mailto:[EMAIL PROTECTED]
Sent: Friday, July 18, 2003 9:00 PM
To: [EMAIL PROTECTED]
Subject: Re:
OK I have reviewed the procedures and I have implemented them. The thing
that concerned me right away was the kernel version numbers. My current
redhat.img and initrd.img files are based on kernel 2.4.9-37. The
procedures are for 2.4.9-17. I went ahead and made the initrd_oso.img
file and
Go Aussies!
http://www.theregister.com/content/61/31910.html
In that splendid Australian way, OSV is inventive with the invective,
likening SCO's bid to make Linux users pay up as the IT industry equivalent
of a Nigerian scam or Internet extortion ploy.
Peter Webb
Technical Support
I built the Debian Linux 2.4.21 kernel with Leland's patch, and sar
and iostat are now reporting I/Os.
Cool, glad to be of help.
Leland
On Wed, 23 Jul 2003, Peter Webb, Toronto Transit Commission wrote:
Go Aussies!
http://www.theregister.com/content/61/31910.html
In that splendid Australian way, OSV is inventive with the invective,
likening SCO's bid to make Linux users pay up as the IT industry equivalent
of a
I really liked: http://www.osv.org.au/index.cgi?tid=29 in particular, the
paragraph:
quote
SCO's suggestion that these end users would somehow be at legal risk
through using Linux is a wholly disingenuous statement, and is akin to the
hypothetical situation of General Motors suing owners of
On Wed, 23 Jul 2003, McKown, John wrote:
I really liked: http://www.osv.org.au/index.cgi?tid=29 in particular, the
paragraph:
quote
SCO's suggestion that these end users would somehow be at legal risk
through using Linux is a wholly disingenuous statement, and is akin to the
hypothetical
Actually this kind of thing was common in the early days of the automobile industry.
There was even a patent granted on the car. GM and Chrysler paid royalties to someone
for years, but Henry Ford refused. The case went on for several years. The patent
holder died, and his family decided to
Have you noticed that most cars look like they were designed by the same guy?
Most cars move through the same air, using the same fuel, and carrying the same
passengers
with the same baggage.
Most computers are rectangular boxes.
Things are different under the covers, which is where the
On Mer, 2003-07-23 at 16:53, Fargusson.Alan wrote:
Actually this kind of thing was common in the early days of the automobile industry.
There was even a patent granted on the car. GM and Chrysler paid royalties to
someone for years, but Henry Ford refused. The case went on for several
Very interesting:
http://mozillaquest.com/Linux03/ScoSource-19-Injunction_Story01.html
Lionel B. Dyck, Systems Software Lead
Kaiser Permanente Information Technology
25 N. Via Monte Ave
Walnut Creek, Ca 94598
Phone: (925)
I compiled gcc 3.3 on my LCDS instance. When I ran the make check command
it failed on the gctest. This seems to be a test of the Boehm garbage
collector.
I then re-compiled gcc 3.3, using gcc 3.3 as the compiler. The same part of
make check failed. The error message is spectacularly
Eric,
If you're interested, I can set up an account on my LCDS system for you to
upload the initrd. I'll try taking a look at it to see what might be wrong.
Mark Post
-Original Message-
From: Eric Sammons [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 10:18 AM
To: [EMAIL
On Wednesday 23 July 2003 12:08, you wrote:
Have you noticed that most cars look like they were designed by the
same guy?
I think he's the same guy who designs all the sneakers, too.
Have you noticed that most cars look like they were designed by the
same guy?
I think he's the same guy who designs all the sneakers, too.
I thought my Chuck Converse's were starting to look an awfull lot like Nikes!
;-)
pct
Mark,
Thank you for the offer, I actually figured out the issue and resolved it.
First, as I was building my new initrd.img file and ftping it around I
forgot to set locsite fix 80 on the client (z/VM). Then I discovered that
if I look at the 2.4.9-37 oco tarball there is a ocord.img. If I
Here's a trivial update to zipl (s390-tools) to get it to write an audit
message to syslog to report all writes of the bootloader. It simply provides
some of the parameters used to invoke it. I wrote it to provide me with a
record of when the kernel/parameters may have changed.
---
On Wed, Jul 23, 2003 at 04:00:58PM -0400, Post, Mark K wrote:
...
Now I am attempting the install, It seems I may not have the FTP site laid
out correctly. Any advice on how best to set up the FTP directory
structure. I have /ftp/RedHat/CD1 and /ftp/RedHat/CD2, is there another
way to
Nilson, I have suse 7.2 running without problems in a G4 machine.
About 8.0, I4m looking for cd4s, since suse didn4t make it available to
download. :-(
Nilson Vieira escreveu:
Hi All
Does any one know if suse 8.0 for s390 runs on 9672 G4?
Whenever i try to tape ipl i get disable wait end the
!!!DO NOT DO THIS ON A PRODUCTION IMAGE!!!
This is probably a know issue, but thought some of you more sadistic types
that have never seen one, might like to see a pretty little kernel OOPs.
(This is a fairly lame one though...)
Just modprobe any of the dasd_*_mod disciplines and then rmmod it.
Leland,
Not for me. I issued the command, and it worked just fine. No errors in
dmesg or anything.
# cat /proc/s390dbf/dasd/sprintf
00 01055273287:534983 0 - 00 00212336 debug area created
00 01055273287:535076 1 - 00 002122f6 Registered successfully to major no
94
00 01055273287:535131 1 -
Ah, bummer! And I was having so much fun. I'm running a 2.4.19-4suse-SMP
kernel. You running a 2.4.21? I looked at the source for 2.4.21 and it
looked like it would have the same problem.
You did the rmmod before catting? Weird. Now, I'm gonna have to go and try
a stock IBM kernel to see
No, I'm running a 2.4.19. I did manage to miss the comment about doing an
rmmod on the module. Sorry.
Mark Post
-Original Message-
From: Lucius, Leland [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2003 6:02 PM
To: [EMAIL PROTECTED]
Subject: Re: Any of you not seen a kernel OOPs
No, I'm running a 2.4.19. I did manage to miss the comment
about doing an
rmmod on the module. Sorry.
Did you get the OOPs?
I have a nice collection of multi-colored AND multi-textured pocket lint for
the first person to figure out why it happens. :-)
Leland
Before anyone yells, I should note that this is NOT a MAJOR problem and
fairly obscure. But, depending on what route is taken, the fix could
require too many changes to make it worthwhile to pursue by IBM.
So, now that you know HOW to make it happen, the easiest fix is simply NOT
to do it. :-)
Here's a trivial update to zipl (s390-tools) to get it to write an audit
message to syslog to report all writes of the bootloader. ...
Fabulous, Neale! The wonderful thing about SYSLOG
is that it can be directed to a network sink, not just a file.
On CMS, one could watch the traffic with
On Wed, 23 Jul 2003, Alan Cox wrote:
On Mer, 2003-07-23 at 16:53, Fargusson.Alan wrote:
Actually this kind of thing was common in the early days of the automobile
industry. There was even a patent granted on the car. GM and Chrysler paid
royalties to someone for years, but Henry Ford
On Wed, 23 Jul 2003, Eric Sammons wrote:
Mark,
Thank you for the offer, I actually figured out the issue and resolved it.
First, as I was building my new initrd.img file and ftping it around I
forgot to set locsite fix 80 on the client (z/VM). Then I discovered that
if I look at the
You can make it happen other ways:
echo /proc/dasd/devices add range asdf
cat /proc/s390dbf/dasd/sprintf
or
echo /proc/chpids asdf
cat /proc/s390dbf/cio_msg/sprintf
Looks like the lcs driver may also be plagued by the problem as well.
The tape driver looks clean though.
Hi all, did somebody is using large volume support with linux 390? is it
recommended to use it with z/vm with volumes of 32760 cyl? how do i enable
it on z/vm 4.3?
thanks
--
Alejandro Leyva Rabinovich.
Jefe de la Unidad Departamental de Soporte Ticnico
(Administracisn de Mainframe).
Direccisn
33 matches
Mail list logo
