See: http://www.nytimes.com/2004/04/28/technology/28blue.html
(Free subscription required)
IBM plans today to announce new server computers that behave more like
mainframes and are priced as low as $1,500. The servers will be able to run
as many as 10 operating systems on a single machine. One
Anyone know how to tell what this error is?
Even when mounting a filesystem ro, the filesystem tries to update some
things in case the block device is read+write (tried this with ext23).
We do not detect if a device is read-only, because we did not find a nice
way to do so (our best idea was read
Hello,
Our customer's mainframe application will migrate to Linux on zSeries is
using VTS. The application is storing some data to VTS and reading it from VTS.
Is there any solutions for using VTS or ATL under Linux on zSeries?
UTS Global has the product for STK SILO, but we have only VTS, ATL.
Thanks. The document I am using to build this environment says that if I
do that then I will not be able to access the R/W DASD even from the ID i
used to build them since all systems will not see the DASD as R/O. If
there a way around that?
dasd=1F0-200,201(ro),202-21F
However note that this
Please see the What's New page at:
http://www10.software.ibm.com/developerworks/opensource/linux390/whatsnew.shtml
for a change summary of the 2004-04-27 additions and changes to the
Linux for zSeries and S/390 developerWorks Web pages.
April 2004 stream:
o Recommended kernel 2.6.5 bug fixes
Jim and Mark,
I often hear that some name is copyrighted or trademarked, but when
searching don't find evidence of such claim.
Maybe making the claim is enough to scare off would-be users. I've been
dealing with another name (completely off-subject) which has been in use
for 75 or so years, but
I couldn't find zlinux in our trademark database, however z/linux was
originally applied for by turbolinux. There are two serial numbers
associated with it; 78343981, and 76272119.
Geoff
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mike Walter
Sent:
Hi,
Am new to the group. Hope to have some
good discussions.
We are using 64 bit SuSE Linux for zSeries.
Is it possible to run 64-bit linux developed
applications on a 31-bit Linux for zSeries ?
Do we need to make sure that the correct
libraries are used in the 64-bit Linux environment while
However note that this cannot be done from the guestvol
system, since the
boot device is R/O. And if this is done from the basevol
system you will
no longer be able to write to the boot device to maintain it in the
future.
If you don't mind custom patches, you might wanna try the patch
Thanks. The document I am using to build this environment says that if
I
do that then I will not be able to access the R/W DASD even from the
ID i
used to build them since all systems will not see the DASD as R/O. If
there a way around that?
Your R/W guest should not update the dasd that
See: http://www.nytimes.com/2004/04/28/technology/28blue.html
(Free subscription required)
For privacy-paranoid, a lot of news sites (like NYTimes) do not require
subscription info if your HTTP_REFERER is from google.com. If your
client doesn't support changing this you can always search for
You cannot run a 64 bit application on 31 bit Linux for zSeries. The 64 bit version
has compatibility modules for 31 bit applications.
I am not sure how one develops 31 bit apps. on a 64 bit system. I think you have to
use the cross development compilers by specifying the 31 bit architecture
1. Is it possible to run s390x software on s390 Linux?
Never. There is no 64-bit compatibility mode library or
kernel support.
2. Do your paths need to point to specific places to develop s390
software under s390x compatibility mode?
No. BUT ... you may need to apply one or more -m
How about the other way around? Can you run 31-bit applications on 64-bit Linux?
Nature and nature's laws lay hid in night:
God said, 'Let Newton Be!' and all was light. - Alexander Pope
It did not last; the Devil howling 'Ho!
Let Einstein Be!' restored the status quo.- John Collings Squire
I am running Linux SLES8 SP03 in a native LPAR. My root file system is
running out of space. I was going to create a separate file system for
directory /opt and move the data under this directory to the new file
system. I have obtained a new DASD UCB address 2536 and here is what I
plan to do.
Mark, et al,
I see the word mark is Z/LINUX. A capital Z, not a little z. Does that
matter? Just curious...
At 11:50 AM 4/28/2004, you wrote:
Well, it didn't take all that long to find this:
http://tess2.uspto.gov/bin/showfield?f=docstate=eut3tj.2.14
Mark Post
-Original Message-
From:
I believe so. I remember for Suse anyways a Compat package. BUT, there
where some that didn't. Like we were looking at WebSphere Business Edition
v5.5. It said it required 31 bit, but we tried the compat package and they
did NOT lie, it did not work.
At 11:59 AM 4/28/2004, you wrote:
How about the
Yes, as long as the 32-bit libraries are available (which they are for SLES8
anyway). The kernel has a code for 32-bit syscalls. gcc's spec file will
allow you to create 32 or 64-bit apps too I recall.
-Original Message-
How about the other way around? Can you run 31-bit applications on
Your guess is as good as mine.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brian
France
Sent: Wednesday, April 28, 2004 12:35 PM
To: [EMAIL PROTECTED]
Subject: Re: term zLinux copyrighted by whom?
Mark, et al,
I see the word mark is
Update /etc/fstab with the appropriate information. Also, read
http://linuxvm.org/Info/HOWTOs/movefs.html to double-check your thinking on
methodology.
The lsof command will identify who might be using stuff in /opt. You would
probably want to do a telinit 1 command first, so that you don't
Thank you for such a quick response. I picked /opt because the
installation of IBM?s HTTP server, Websphere and some other products are
consuming a major portion of the file system. However, my questions and
insecurities can apply to any of the directories.
Jim Sibley [EMAIL PROTECTED]
The USPTO won't let you trademark something that sounds like something that already
has a trademark, so since Z/LINUX is trademarked you can't trademark (or use) zLinux,
ZLINUX, z/Linux, etc.
-Original Message-
From: Brian France [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 28, 2004
I picked /opt because the installation of IBM?s HTTP
server, Websphere and some other products are
consuming a major portion of the file system.
You should be able to move just the IBM stuff to
another volume, then put a link in /opt.
1. mount a device as /mnt/vendor
2. copy the IBM directories
On Wednesday 28 April 2004 13:10, Peter E. Abresch Jr. - at Pepco wrote:
I am running Linux SLES8 SP03 in a native LPAR. My root file system is
running out of space. I was going to create a separate file system for
directory /opt and move the data under this directory to the new file
system.
Ok, I read the official Preview Announcement for the IBM Virtualization
Engine.
http://www-306.ibm.com/common/ssi/OIX.wss?DocURL=http://d03xhttpcl001g.bould
er.ibm.com/common/ssi/rep_ca/6/897/ENUS204-096/index.htmlInfoType=ANInfoSu
bType=CAInfoDesc=Announcement+Letterspanelurl=[EMAIL
Jim Tison wrote:
The gdb (debugger) I run on my s390x machine will not
recognize ELF32 modules ...
The recently released gdb 6.1 will allow 'bi-arch' debugging on s390,
i.e. debugging a 32-bit application from a 64-bit gdb.
You can download the sources from the gdb home page; they should
build
Scott wrote:
Is this simply an extension of LPAR technology, or is
it z/VM like hipervisor in the firmware? Is there
anything new here for z/Series? Again, z/OS is
mentioned, z/VM is not.
The virtualization is not the kind we're used in
VMWARE or z/VM or LPARs where a platform runs many
copies
On Wed, 2004-04-28 at 15:24, Jim Sibley wrote:
What this appears to be is a virtual layer between
the OS/hardware and the application.
You make this sound like a super BIOS, or perhaps a microkernel.
Speculating under tinfoil (which I always keep handy) I see this as a
potential big win for
Jim Sibley [EMAIL PROTECTED] wrote:
The official Big Blue legal position on the term
zLinux is that it is copyrighted by another
company and one should use the terms Linux for
zSeries or Linux for s/390.
Anyone know who the other company is?
As Mark Post noted, TurboLinux owns this. Although
At 11:51 AM 4/28/2004, Ledbetter, Scott E wrote:
Not to call anyone at IBM an idiot, but they obviously have some writers
very adept at using thousands of words to say Virtually (HA!) nothing.
Nothing new... Back when it used to be called vapor-ware
Is this simply an extension of LPAR
OK, I am already stumped and embarrassed. I tried to the first step as:
mainpepl:/dev # dasdfmt -v -n 2536 -d cdl -l LNX003 -b 4096 -p
dasdfmt: Unable to open device /dev/dasd/2536/device: No such file or
directory
mainpepl:/dev #
How do I get Linux to recognize the new DASD UCB 2536? Thanks.
Wolfe, Gordon W wrote:
How about the other way around? Can you run 31-bit applications on 64-bit Linux?
You can provided SuSE has included your favorite libraries in the single
s390x package that delivers these compatibility libraries. At best this
applies to packages that SuSE also support in
You make this sound like a super BIOS, or perhaps a microkernel.
It's an abstraction layer. Kind of like comparing UNIT=DISK vs
UNIT=3390; the system figures out the Right Thing to Do based on the
other parms fed to it.
Speculating under tinfoil (which I always keep handy) I see this as a
It sounds more like an emulation layer in the middle that's able to appear
as Intel, RS/6000, AS/400, and zSeries, and a hypervisor (probably more
like LPAR than VM). And I suspect the reference to z/OS really means any
zSeries OS. Think how much money they could save if all their platforms
On Wed, 2004-04-28 at 15:35, Peter E. Abresch Jr. - at Pepco wrote:
OK, I am already stumped and embarrassed. I tried to the first step as:
mainpepl:/dev # dasdfmt -v -n 2536 -d cdl -l LNX003 -b 4096 -p
dasdfmt: Unable to open device /dev/dasd/2536/device: No such file or
directory
On Wed, Apr 28, 2004 at 12:24:46PM -0700, Jim Sibley wrote:
Subject: Re: IBM Virtualization Engine
Scott wrote:
[...]
What this appears to be is a virtual layer between
the OS/hardware and the application. The applications
develop to the virtualization layer specs and
hardware/OS vendor
It is SuSE SLES8 SP03 running on a native LPAR. How can I tell if I am
using devfs?
Adam Thornton [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
04/28/2004 05:04 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject:
You're not. You need to use /dev/dasda?, /dev/dasdb?, etc.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter
E. Abresch Jr. - at Pepco
Sent: Wednesday, April 28, 2004 5:06 PM
To: [EMAIL PROTECTED]
Subject: Re: Adding Spaces to a
On Wed, 2004-04-28 at 16:06, Peter E. Abresch Jr. - at Pepco wrote:
It is SuSE SLES8 SP03 running on a native LPAR. How can I tell if I am
using devfs?
Do your dasd devices have names like
/dev/dasda, /dev/dasda1
or like
/dev/dasd/0150/device, /dev/dasd/0150/part1
?
If the former, you
I knew we were being to vague in this announcement (or technically
preview). Virtualization Engine (VE) is TWO things. First, it is a set
of VE Systems Technologies that include hypervisors. Second, it is a
set of VE Systems Services which are designed to make it easier to
manage these systems as
The virtualization is not the kind we're used in VMWARE or z/VM or
LPARs where a platform runs many copies of the different OS's.
What this appears to be is a virtual layer between the OS/hardware
and the application. The applications develop to the virtualization
layer specs and hardware/OS
Scott:
What really struck me was that z/OS, Linux, Windows, AIX, Solaris
and OS/400 were all mentioned, but z/VM was not. What the ?
z/VM is the hypervisor layer for VE on zSeries. I know it could have
been mentioned by name, but neither was LPAR.
Is this simply an extension of LPAR
On Wed, Apr 28, 2004 at 11:13:58AM -0400, Daniel Jarboe wrote:
Date: Wed, 28 Apr 2004 11:13:58 -0400
From: Daniel Jarboe [EMAIL PROTECTED]
Subject: Re: IBM Plans to Build Servers That Act Like Mainframes
To: [EMAIL PROTECTED]
See: http://www.nytimes.com/2004/04/28/technology/28blue.html
I was wondering whether anyone else had built a 2.6 kernel into an NSS
yet.
I used my old reliable SAVELX exec; the guts of it are this:
/* Figure out DEFSYS command... */
/* Requires Class E privileges */
/* First and fourth megabytes: RW, exclusive */
/* Second and third megabytes: RO, shared
I must not be running devfs. I performed the following:
echo add device range=devno-2536 /proc/dasd/devices
I then did
cat /proc/dasd/devices | grep 2536
to get
2536(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 601020
blocks, 2347 MB
from there I substitued dasdc as
Jim:
The official Big Blue legal position on the term zLinux is that it
is copyrighted by another company and one should use the terms
Linux for zSeries or Linux for s/390.
Not quite right. The official position is:
- 'Linux on zSeries' refers to the operating environment of running
the
46 matches
Mail list logo
