Frank Swarbrick wrote:
Sounds like Linux needs an intermediate "byte-code" format, so you could
use gcc to compile to this byte-code and then have gcc on the
destination machine compile the byte-code in to it's natural machine
code.
Heh, just a random thought...
You can get gcc to produce prep
On Sep 27, 2005, at 7:19 PM, Frank Swarbrick wrote:
Sounds like Linux needs an intermediate "byte-code" format, so you
could
use gcc to compile to this byte-code and then have gcc on the
destination machine compile the byte-code in to it's natural machine
code.
Heh, just a random thought...
G
Sounds like Linux needs an intermediate "byte-code" format, so you could
use gcc to compile to this byte-code and then have gcc on the
destination machine compile the byte-code in to it's natural machine
code.
Heh, just a random thought...
---
Frank Swarbrick
Senior Developer/Analyst - Mainframe
Or try:
grep -c ^processor /proc/cpuinfo
Rick Troth wrote:
Try this:
cat /proc/cpuinfo | grep '^processor' | wc -l
Dunno about "inactive" -vs- "active".
-- R;
On Tue, 27 Sep 2005, Phil Tully wrote:
On linux how do you display the number of cpu's the kernel has
acti
Try this:
cat /proc/cpuinfo | grep '^processor' | wc -l
Dunno about "inactive" -vs- "active".
-- R;
On Tue, 27 Sep 2005, Phil Tully wrote:
> On linux how do you display the number of cpu's the kernel has
> active/inactive?
>
> Phil Tully
---
Phil Tully writes:
>On linux how do you display the number of cpu's the kernel has
>active/inactive?
The top command will show a line in the header for each CPU. Also, the
/proc/cpuinfo file contains detailed information about each processor. Do
either of those have what you're looking for?
On linux how do you display the number of cpu's the kernel has
active/inactive?
Phil Tully
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or v
It's a case of customer not understanding that the architecture is
different is why I raised the question. I said I would ask the learned
members of the list as I'd never heard it described as "ELF" Before.
Basically they have some software that they would like to see run on the
z/Series Linux but
On Sep 27, 2005, at 2:45 PM, James Melin wrote:
I've got a customer here that's all excited about ELF binaries.
They have a
product they'd like to see run on z/Series linux but there is no
declaration that z/Series is a supported platform. They do state
that their
binaries are 100% ELF compatibl
ALL Linux is ELF.
ELF is an execution (and linkage?) format for many platforms.
PC Linux has been "ELF" for several years ... nearly ten, I suppose.
Mainframe Linux has been "ELF" as long as it has been public.
(That is, prior executable formats had fallen out of use on Linux
before the advent o
James Melin writes:
>I've got a customer here that's all excited about ELF binaries. They have a
>product they'd like to see run on z/Series linux but there is no
>declaration that z/Series is a supported platform. They do state that their
>binaries are 100% ELF compatible. What exactly does that m
>
> I've got a customer here that's all excited about ELF binaries. They have a
> product they'd like to see run on z/Series linux but there is no
> declaration that z/Series is a supported platform. They do state that their
> binaries are 100% ELF compatible. What exactly does that mean for an int
I've got a customer here that's all excited about ELF binaries. They have a
product they'd like to see run on z/Series linux but there is no
declaration that z/Series is a supported platform. They do state that their
binaries are 100% ELF compatible. What exactly does that mean for an intel
based p
Trying to setup a test zFCP multipathed environment on a SLES9
z/VM instance and want to use the EVMS (2.3.3) that comes with
the distro. The supplied docs point to
http://evms.sourceforge.net/user_guide
for the user guide but that points to the current release's (2.5.3) guide.
It appears that th
It might be that simple, but it shouldn't be needed.
Because mksles9root creates a directory struction with the subdirectory
starting with s390 or s390x. If I'm in /data1, I should be able to run
mksles9root s390 and it would create /data1/s390/... and I should also
be able to run mksles9root s39
The key is: What directory are you running mksles9root in? i.e. where is it
trying to build the mksles9root directory? If you're trying to create it in the
same place, then it will complain; If you try to do it in another place, you
may have better luck.
--
Robert P. Nix Mayo Foundat
Mike,
It's been there for a while. I just haven't had a chance to update the
web page to point to it.
http://linuxvm.org/patches/s390/mksles9root.sh
Sorry, but I had to add the ".sh" so that ESAWEB would have a file type
to use for the mime type.
Mark Post
-Original Message-
From: Li
Then you're in luck. As both Marcy and I noted from attending Steve
Wehr's session in SF, that's the version that has support for
"profiles". That makes it very easy (and you still remain supported by
IBM!) to do what you want to do.
Mark Post
-Original Message-
From: Linux on 390 Port
We'll be going up on WebSphere 6 with this.
"Post, Mark K"
<[EMAIL PROTECTED]
m> To
Sent by: Linux on LINUX-390@VM.MARIST.EDU
390 Port
Tom,
> That didn't seem to work that a way.
Hmmm - are you sure you have the latest script? I swatted a couple of
bugs - the latest is on http://mikemacisaac.com/mksles9root
(Note: I may be giving up on this mikemacisaac.com experiment and thus am
hoping to have this script officially hosted on l
Yes, it is true that WebSphere records the hostname into its config files
upon installation. There is a helpful doc that explains which files you
need to modify if you plan on changing the hostname:
http://www-1.ibm.com/support/docview.wss?uid=swg27005391&aid=1
You can either modify each of the
If it's WAS5, you can use a script to change name and ip's that have
been imbedded. I have one if you need it.
For WAS6, you should get a copy of Steve Wehr's zExpo presention from
last week. The wasprofile concept can probably help you out here.
DB2connect doesn't seem to care about which IP/s
Not having a 2.6 system (of any flavor) running at the moment, I'm
tempted to say that the kernel-headers package won't be sufficient. I
believe that in order to be able to do a "make modules" command, you're
going to need the entire kernel source package. Trying to do that with
just the kernel h
That didn't seem to work that a way.
I have the iso images in /data1.
I CD to /data1.
I run ./mksles9root s390x.
It creates a /data1/s390x/ (just like you said)
(now I'm going the other way..)
I run ./mksles9root s390 and it gives me the:
Error: sles9root exists - must be removed first (rm -
For WebSphere, there was a presentation at zExpo that talks about doing
just that. It's only supported in the newer/newest version of
WebSphere, though. What version will you be installing?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Jame
Are you sure you don't have to:
mkinitrd
zipl
ANY time you make changes to volumes?
I do which yast would, at least, give you an informational message
telling you that you need to do those steps when you add/chg/delete
dasd. Sometimes I too quick to IPL and as I start the shutdown
process...Noo
Is that if you do your own or if you use mksles9root?
I'm using mksles9root. It makes the directories. I had the s390
versions out there. It wanted me to remove them so it could create the
s390x (not the author of the code, so I don't know why).
Since there didn't seem to be a command switch,
Thank you, Kurt.
Regards,
Marija
Kurt Verhofstadt <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
27.09.2005 13:53
Please respond to Linux on 390 Port
To: LINUX-390@VM.MARIST.EDU
cc:
Subject:Re: How to activate DASD in Linux
Oeps. That should be 'mkinitr
James Melin writes:
>My intent is to clone the SLES-9 image that we have running using the
>techniques spelled out in the 'LPAR to virtual servers in 2 days'
book. ...
I've automated this very thing for WebSphere, and you're right: it buries
the hostname, the IP address and your domain name in var
My intent is to clone the SLES-9 image that we have running using the
techniques spelled out in the 'LPAR to virtual servers in 2 days' book. My
specific situation is that I must take existing production systems, and
create them as SLES-9 64 bit. The problem being is that I am not going to
be allow
Adam,
thanks for the info. I'm still struggling with this.
I had the kernel headers installed so I put in a link from
/usr/src/kernel-headers-2.6.8-2 to /lib/modules/2.6.8-2-s390/build.
I not sure what I need to change in version.h and module.h
At the moment:
make -C /lib/modules/`uname -r`
Oeps. That should be 'mkinitrd' and 'zipl'.
run initrd and zipl.
regards,
Kurt.
- Confidentiality Notice -
This communication and the information it contains is intended (a) for the
person(s) or organization(s)
named above and for no other person or organization, and (b) may be
confide
run initrd and zipl.
regards,
Kurt.
- Confidentiality Notice -
This communication and the information it contains is intended (a) for the
person(s) or organization(s)
named above and for no other person or organization, and (b) may be
confidential, legally privileged and
protected by law. Unau
Hello,
can you say, what will add the dasd permanently?
I added one dasd (through Yast - ACTIVATE - SLES9).
After reboot, that dasd is not activated at the same time when others, so
it can't be mounted in /etc/fstab.
Regards,
Marija
Carsten Otte <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
Tom,
> That kind of implies that I can't have both 31 and 64 bit products on
> the installation server at the same time.
They can exist on the same server, just not in the same directory. I put
the 31-bit iso images in one directory, say /data/sles9 and the 64-bit iso
images in another, say /data/
Eddie Chen wrote:
>Does any one know which performs better, raid-level 0 or striping
> in LVM (z/linux system) ?
No difference. On 2.6.x. both LVM and EVMS are backed by device mapper
technology anyway, and one day md-raid is going to be as well.
--
Carsten Otte
IBM Linux technology cent
Uriel Carrasquilla wrote:
> We were told to ignore them.
> We have been running with those messages for about 4 months now without any
> problems in 4xLPAR's.
I see that the message causes some confusion. So here's my short explanation
on barriers:
- a journaling filesystem like ext3 needs to make
37 matches
Mail list logo
