This is not merely a documentation string! Also, who says that
a module built for 2.4.9 won't work with 2.4.9-4GB? What patches
are these that warrant changing the label??
The good thing with the dash-level in the kernel IMHO is that you keep
the old set of kernel modules, and you can
Mark,
Thanks for the response. I guess even a Redhat Admin course
(on Intel) should still be of considerable value to me.
Thanks,
SG
-Original Message-
From: Post, Mark K [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 27, 2001 5:09 PM
To: [EMAIL PROTECTED]
Subject: Re: redhat s/390
Hi..
Thanks.. Now, I can't find the download for gcc-2.95.3.tar.gz anywhere.
Could you help pls.?
Vinod.
-Original Message-
From: Alex Bykov [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, December 27, 2001 6:50 PM
To: [EMAIL PROTECTED]
Subject: Re: Oracle Installation Problem
Let's say you ran a large, profitable company like IBM.
Software revenues around $12 billion.
You're risking a lot in supporting something like Linux.
OTOH - IBM achieved its utter dominance of the industry in the late
1960s using a public domain operating system.
Contrary to popular
Rather, QDIO is a hardware feature, for which IBM does not publish
the
programming interface. The interface is unique to IBM S/390. And it
is used
by more OS's than just Linux. Publishing the interface for Linux
also
publishes the interface for all other OS.
ISTR Amdahl paid a great deal of
Hello
How do I parse the identification field in /proc/cpuinfo? The other ones
I understand. The one I have access to says processor 0: version = FF,
identification = 035667, machine = 9672
I am trying to estimate the performance of our application on different
S390/zSeries systems, and for
How do I parse the identification field in /proc/cpuinfo? The
other ones
I understand. The one I have access to says processor 0:
version = FF,
Probably this indicates you're running under VM or VIF. The Linux guest is
seeing a virtual CPU (on bare metal, this would be the actual physical id
Thank you David!
One new question:
Are there any performance counters such as other processors have (cache
hit/miss, tlb hit/miss, branch predict misses, insns retired etc.)
available from Linux?
On Fri, 2001-12-28 at 20:08, David Boyes wrote:
How do I parse the identification field in
IBM Journal of RD occasionally publishes some interesting
articles in this
vein.
Thanks, that paid off immediately, if someone wonders the URL is:
http://www.research.ibm.com/journal/rd
And they have many nice articles online.
Vol. 43, Nos. 5/6, 1999 are particularly interesting for
Mark,
I thought IBM's OCO modules were only for OSA card support,
and were not needed for the MP3000, which uses plain
OS/2 TCP/IP using standard PC Ethernet cards.
Are you sure about that? I didn't need to add anything
for SuSE 7.0, SLES1 and SLES7 to work.
Is there a URL to get the IBM OCO
Thanks for your help, Mark.
The problem actually was with the window manager I was using.
When I used the MixServer from MicroImages, the tkCVS application came up
but none of the letters were legible. Once I tried with CYGWIN X-windows and
Linux/390's twm, I am getting the tkCVS windows clearly.
On Fri, 2001-12-28 at 22:01, David Boyes wrote:
Are there any performance counters such as other processors
have (cache
hit/miss, tlb hit/miss, branch predict misses, insns retired etc.)
available from Linux?
Hmm. If gcc generates the code to collect them (or gprof), then they should
Jim,
Absolutely. You can define virtual CTCs or IUCV links between your new
guest and either the VM TCP/IP stack, or the SuSE guest. You'll need to be
careful about assigning IP addresses and the associated routing. There's
been a ton of discussion on the mailing list about that, and both
Are there any performance counters such as other processors
have (cache
hit/miss, tlb hit/miss, branch predict misses, insns retired etc.)
available from Linux?
Hmm. If gcc generates the code to collect them (or gprof), then they should
be available in the same ways as on the other
Mark,
I'm not giving up on the OCO modules, but there is not enough
time left this year to obtain the GA Red Hat, obtain a PC and
install x86 Red Hat 7.2, download the required new 2.4.9-17 kernel,
follow the PDF installation procedure to merge in the OCO,
and, finally, complete the MP3000
Jim,
Getting the Red Hat GA isn't much. There are some files that are different
from the RC2, but you can figure those out and only download them. You
don't need an x86 Linux, you have your SuSE system on the same box. Use
that instead. The 2.4.9-17 kernel is part of the GA code, so that's
16 matches
Mail list logo
