But that's not what the OP asked about. He asked about a shared read-only
root file system. He wasn't asking about sharing the other parts of the
file system. Your root file system only needs to be about 15MB, not 100MB
or 1GB. Trying to share that specifically isn't worth the effort. Sharing
Sorta off topic (different platform)
http://news.com.com/2100-7344-5182158.html
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
"Computer are useless.They can only give answers." Pablo Picasso
__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveawa
On Friday, 04/02/2004 at 02:58 EST, "Kern, Thomas"
<[EMAIL PROTECTED]> wrote:
> On an MP3000-H50, which chpid is used by the virtual QDIO nic that I
define
> for a virtual machine?
Unless you override it with the CHPID xx option, the virtual chpid is
selected from the set of chpids NOT present
On an MP3000-H50, which chpid is used by the virtual QDIO nic that I define
for a virtual machine?
I have 3 persistant LANs defined, VMLAN00, VMLAN01, VMLAN02.
VMLAN00 is meant as a backbone connection between VM, OS/390, and 2 separate
linux firewall servers. Each firewall server will then conne
I haven't posted this in a while, and now seems like a good time to do so
again.
Alan Altmark
Sr. Software Engineer
IBM z/VM Development
In November of 2003, an OSA-Express microcode update for the IBM zSeries
z800 and z900 machines became available that makes the portname optional
for the OSA-Ex
I modified the /etc/chandev.conf to be explicit about lcs0 and qeth1 to
match the /etc/modules.conf aliases that are set up for eth0 -> lcs and eth1
-> qeth. After reipling, I get the same IDX TERMINATE cause code 0x22 error.
This is a RHEL 3 system, but through trial and error, I know that the
ch
On Fri, 2 Apr 2004, Daniel Jarboe wrote:
> > And finally, the pain involved isnt so great, we just installed a
> linux
> > vm, compiled and installed the packages that we need (postgres 7.4,
> apache
> > 1.3.29, perl 5.8, etc), then copied the non-standard directories (etc,
>
> Do the "extra" soft
On Friday, 04/02/2004 at 12:15 EST, "Kern, Thomas"
<[EMAIL PROTECTED]> wrote:
> Can someone in IBM or someone with the source code for QETH, please tell
me
> what IDX TERMINATE and cause code 0x22 mean?
Everyone has access to the source code. One of my favorite URLs is
http://lxr.linux.no/source/
On Friday, 04/02/2004 at 12:27 EST, "Post, Mark K" <[EMAIL PROTECTED]>
wrote:
> I believe that the order of the cards in /etc/chandev.conf is
significant.
> I've always seen it coded this way:
> # cat /etc/chandev.conf
> qeth0,0x0f10,0x0f11,0x0f12
> add_parms,0x010,0x0f10,0x0f12,portname:LINUXSRV
>
> And finally, the pain involved isnt so great, we just installed a
linux
> vm, compiled and installed the packages that we need (postgres 7.4,
apache
> 1.3.29, perl 5.8, etc), then copied the non-standard directories (etc,
Do the "extra" software packages not included in the base get
compiled/ins
Could it be a syntax problem
you have:
lcs-1,0x3ad0,0x3ad1,0,3
qeth-1,0x0e04,0xe05,0x0e06,0,0
lcs1 and qeth1 without the dash.
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
"Computer are useless.They can only give answers." Pablo Picasso
__
Do you Yahoo
On Friday, 04/02/2004 at 11:55 CST, Rich Smrcina <[EMAIL PROTECTED]>
wrote:
> For what it's worth here's the pertinent entry in my chandev.conf:
>
>
noauto;qeth0,0x0800,0x0801,0x0802;add_parms,0x10,0x0800,0x0802,portname:GL1
>
> If this is the first machine to use the Guest Lan it will be able to s
I thought about SCSI/FCP, but I wasn't sure if you can boot from it. But thinking
about it, we're really talking about needing the driver for the root filesystem, which
COULD be on FCP. Hate those
maps though.
Maybe the logic was to be able to replace the normal drivers with the DIAG ones?
>
On Fri, 2004-04-02 at 11:37, Hall, Ken (IDS ECCS) wrote:
> Using the modular driver for the disk makes sense on Intel, where there are so many
> possible variations, but why bother for Z? How many different disk devices do we
> have? Two? (ECKD, and FBA)
Four.
For local disks, DIAG also. It
This virtual machine is LNXRHFW. It is authorized to connect its virtual NIC
E04 to guest lan VMLAN01. During these tests it is the ONLY server
connecting to VMLAN01. The virtual NIC is currently defined and coupled in
the PROFILE EXEC, eventually to be done in the user directory. The eventual
use
We are developing this. This week we have plans to take into production.
Right now, the benefits we have seen justify the pain involved. We reduced
the size of a linux vm from 500 mb or 1 gb to 100 mb, the time used to
create a linux vm is significantly reduced too. The administration is
really sim
Using the modular driver for the disk makes sense on Intel, where there are so many
possible variations, but why bother for Z? How many different disk devices do we
have? Two? (ECKD, and FBA)
Seems like a pointless complication, even if it's hidden from most users.
> -Original Message---
For what it's worth here's the pertinent entry in my chandev.conf:
noauto;qeth0,0x0800,0x0801,0x0802;add_parms,0x10,0x0800,0x0802,portname:GL1
If this is the first machine to use the Guest Lan it will be able to set
the name, so what you use really doesn't matter. All of the other
machines will
Swapping the order of qeth-1 and add_parms doesn't change it.
cat /etc/chandev.conf
chandev=noauto
lcs-1,0x3ad0,0x3ad1,0,3
qeth-1,0x0e04,0xe05,0x0e06,0,0
add_parms,0x10,0x0e04,0x0e06,portname:VMLAN01
Q NIC DETAILS
Adapter 0E04 Type: QDIO Name: UNASSIGNED Devices: 3
Port 0 MAC: 00-04-AC-0
I think that applies to both of us. :)
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Post, Mark K
> Sent: Friday, April 02, 2004 12:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [LINUX-390] new disk for linux (CORRECTION)
>
>
> I think I'm getting my d
Apologies from me also for getting it so wrong the first time. It was early in the
morning, and my brain hadn't kicked in yet. I figured zipl had to store hard pointers
to avoid reading the
filesystem.
I was puzzled at first about how SLES7 worked without an initrd, so I went and checked
and
I believe that the order of the cards in /etc/chandev.conf is significant.
I've always seen it coded this way:
# cat /etc/chandev.conf
qeth0,0x0f10,0x0f11,0x0f12
add_parms,0x010,0x0f10,0x0f12,portname:LINUXSRV
The "qeth" statement first, followed by the add_parms for that device.
Mark Post
Well, sort of. When zipl is run, it stores pointers to the boot sector,
kernel and the contents of the parmfile in a specific place on the disk.
Strictly speaking, there is no access to the file system on the disk. This
is why if you write over those files with new contents, your next boot is
lik
It indicates that the portname is wrong. Verify the port name with Q
LAN DETAILS.
On Fri, 2004-04-02 at 11:15, Kern, Thomas wrote:
> Can someone in IBM or someone with the source code for QETH, please tell me
> what IDX TERMINATE and cause code 0x22 mean?
>
> This is a RHEL system build during th
Can someone in IBM or someone with the source code for QETH, please tell me
what IDX TERMINATE and cause code 0x22 mean?
This is a RHEL system build during the Taroon beta.
/Thomas Kern
/301-903-2211
ifconfig eth1 10.0.1.1
qdio: loading QDIO base support version 2 ($Revision: 1.145 $/$Revision:
I think I'm getting my distributions confused again. I think I've been
arguing my point for SLES8 when it really applies to RHEL3. Sigh. Time for
some more sleep than I've been allowing myself lately.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Be
I think you need to spend some time rooting around in the initrd. You'll
see that the script in the initrd does the insmod of the DASD driver, _and_
specifies the device numbers to be used by it. After so many people
reported problems updating their parmfile and re-running zipl but still not
seei
Ken Hall wrote:
>Basically, you need an initrd if the boot-device
drivers >aren't built into the kernel. (You get this
choice >during the kernel configure process.) With
the variety >of hardware on that platform, ifyou tried
to include all >possible drivers in the actual kernel,
it
>would be hug
At 09:49 AM 4/2/2004, John Campbell wrote:
Here's some more trival, this time from the Ancient Burroughs 6700, which
had symmetric multiprocessing a LONG time ago (and, no, I don't think
trying to port Linux to such a machine would be much fun): the Processor
Operator instruction "Interrupt Oth
You want silly?
I spent some years on UNIVAC 1100 systems, which had a Meta-Assembler named
"MASM". (Meta-Assemblers, BTW, smoke Macro Assemblers any day of the
week... though, really, "C" is just a meta-assembler for the PDP-11.)
Anyway, on with my story.
In what was (I suspect) a response to
I keep seeing references to the new product offering, but have not
actually SEEN the new product offering... so whomever made the offering,
PLEASE contact me off list. Not saying we're in the market (don' know what
it is) but it may be helpful to us as we're just building the
infrastructure to go
It must be a sign of getting old, but about 2 minutes after I sent that previous note,
I remembered that a good part of it was wrong.
The DASD list comes from the boot filesystem, built by zipl from /etc/zipl.conf. The
script inside the initrd that does the load uses a variable "$dasd" to pick
On Fri, Apr 02, 2004 at 04:54:12PM +0200, Phil Payne wrote:
> >> Now that's the way to make a commercial announcement on a mailing
> >> list. Well done.
> _Relevant_ SPAM?
I wouldn't even term Dave's note as spam. It was a useful piece of
information presented factually without hype or personal
a
>>> [.. short, hype-free, informative message on new product offering ..]
>> Now that's the way to make a commercial announcement on a mailing
>> list. Well done.
_Relevant_ SPAM?
What a novelty. What next - the co-ordinates of the Holy Grail or the Ark of the
Covenant?
World Peace?
I, too, t
>
> On Thu, Apr 01, 2004 at 04:10:23PM -0500, Thomas David Rivers wrote:
> > [.. short, hype-free, informative message on new product offering ..]
>
> Now that's the way to make a commercial announcement on a mailing
> list. Well done.
>
> -- db
>
Hi David!
Thanks it's always sooo hard to
On Thu, Apr 01, 2004 at 03:38:26PM -0600, McKown, John wrote:
> Is that more or less than "oodles"? I.e. how many oodles per gob?
1.414 milliparsec-barns per gob. You can look it up anywhere in the
western spiral arm.
(is this silly, or what?)
On Thu, Apr 01, 2004 at 04:10:23PM -0500, Thomas David Rivers wrote:
> [.. short, hype-free, informative message on new product offering ..]
Now that's the way to make a commercial announcement on a mailing
list. Well done.
-- db
--
> > for i in `rpm -qa`; do rpm -V $i; done |grep missing
> rpm: only one major mode may be specified
Those are backticks around rpm -qa (on my keyboard, upper left, shared
by ~).
~ Daniel
---
This message is the proper
The kernel modules (dasd_mod.o and dasd_eckd_mod) are in the initrd, but the DASD parm
is picked up from the BOOT filesystem. That's updated by running zipl, copied from
/etc/zipl.conf. You don't
boot from the initrd, that's mounted AFTER the kernel loads from the boot filesystem.
If you need
Hi Daniel,
As you can probably tell, I'm real fluent with a lot of the Linux commands, so I
really appreciate your help.
I tried that command, and here is what I got:
rpm: only one major mode may be specified
>>> [EMAIL PROTECTED] 04/01/04 09:14AM >>>
> It's funny, this is the one I use to cl
40 matches
Mail list logo
