Hi Thomas,
I think Mark already pointed out a significant problem (the chandev
parameter line inside /etc/chandev.conf). You can find out how much the
channel device layer actually understood from your configuration file by
showing the /proc/chandev output (cat /proc/chandev). You should see a
t
I would have thought that there was a real osa somewhere for vm to get
to the network
but i am pretty new at this so
Post, Mark K wrote:
Thing is, there's not an actual OSA card in use here. It's all virtual
stuff.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL
Thing is, there's not an actual OSA card in use here. It's all virtual
stuff.
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Scorch
Burnet
Sent: Wednesday, March 31, 2004 5:52 PM
To: [EMAIL PROTECTED]
Subject: Re: Adding QDIO guest lan to ser
I believe that there can be only one portname per osa card and taht name
is case sensitive...
I defined the portname when i set up vm. since i only have one osa car
(albeit, with 16 addresses) all my linux images including the ones on
the vswitch point to that portname
Kern, Thomas wrote:
I did s
Ok, now what does "Q LAN DETAILS" give you?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kern,
Thomas
Sent: Wednesday, March 31, 2004 5:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Adding QDIO guest lan to server
I did switch the second NIC to
I did switch the second NIC to being E04-E06 and I get the same messages.
This is an old TurboLinux distribution and the /etc/chandev.conf was
provided by someone from TurboLinux to get it to talk to the 3172. I do have
plans to migrate to a newer but still unsupported copy of RedHat, but I must
w
I see a couple of problems here. The virtual NICs need to have a starting
address that is on an even boundary. So, "qeth2,0xe03,0xe04,0xe05,0,0" is
invalid.
"chandev=" is something you would put in your parmfile, not in
/etc/chandev.conf.
How did you define the virtual NICs? If you don't expli
> It looks like that messages is generated around line 837 in the
mkinird,
> before your change.
Ugh, my find had wrapped back to the beginning without me realizing.
Okay, on line 844
tar -C $root_dir -cf - $x 2>/dev/null | tar -C $tmp_mnt -xpf -
2>/dev/null
you're getting a rc 127. It's as if
Peter E. Abresch Jr. - at Pepco wrote:
file /usr/sbin/zebra from install of quagga-0.96.4-3 conflicts with file
from package zebra-0.93b-83
One of the things your package probably should say is 'Conflicts:
zebra' so that RPM will force you to take zebra out before you install
quagga.
Rob
--
I replaced ucc-snmp with ucdsnmp and replaced initscripts with aaa_base
and rebuilt. As Mark pointed out, this was in the original src.rpm for
Zebra. I ran the "rpm -ihv --test quagga-0.96.4-3.s390.rpm" and it failed
with many conflicts such as the following:
file /usr/sbin/zebra from install o
Try taking the redirection to /dev/null off lines ~710-712:
dd if=/dev/zero of=$tmp_initrd bs=1k count=$image_blocks 2>/dev/null
mke2fs -q -F -b 1024 -m 0 -N $image_inodes $tmp_initrd 2>/dev/null 1>&2
tune2fs -i 0 $tmp_initrd >/dev/null 2>&1
Then, do a "df /var/tmp/" command to see how
I am trying to add a QDIO guest lan to replace the IUCV connection between a
firewall server and a web server. The firewall server has a 3172 connection
to the real network. I tried to mimic the configuration from another server
I have that has a claw device to the network and a guest lan to our VM
Peter E. Abresch Jr. - at Pepco wrote:
error: failed dependencies:
ucd-snmp is needed by quagga-0.96.4-3
initscripts >= 5.60 is needed by quagga-0.96.4-3
I think this is because your Red Hat spec file specifies pre-required
package names that are used for Red Hat packages, and no
Well, i tried upping the initial size, I quadrupled it, to no avail. It looks like
that messages is generated around line 837 in the mkinird, before your change.
Here is the results of the bash on mkinitrd:
bash -x mkinitrd
+ kernels_default=vmlinuz vmlinuz.shipped
Rod wrte:
>>However, I could not
>>recommend ext2 as a filesystem because it is too
>>easily damanaged (sic)
>How so?
The Linux file systems are heavily cached and allow
"dirty" writes of the data - i.e., the data in memory
is not immediately synced with the hardware copy. This
is controlled by
>> At line at 1061 which is:
>>
>> dd if=/dev/zero of=$tmp_initrd_small bs=1k count=$img_size
2>/dev/null
>>
>> Can you remove the "2>/dev/null" portion of that, run mkinitrd again
and
>> see if you get any "No space left on device" errors?
>
> I did as you suggested, but I don't get any additional
>However, I could not
>recommend ext2 as a filesystem because it is too
>easily damanaged (sic)
How so?
Rod
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INF
I did as you suggested, but I don't get any additional messages, it's the exact same
thing.
>>> [EMAIL PROTECTED] 03/31/04 12:04PM >>>
> creating initrd "/boot/initrd" for kernel "/boot/kernel/image"
> (version 2.4.21-83-default) (s390)
>
> dasd_mod: failed to add module "/lib/modules/2.4.21-83
Before the zipl, did you do a mkinitrd? The dasd
drivers are in the initrd module and not in the kernel.
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
"Computer are useless.They can only give answers." Pablo Picasso
__
Do you Yahoo!?
Yahoo! Finance Tax Ce
In reply to Ron:
>The best skewed distribution could be your own, so we
>may get the horsedead by this: "Given this 4K
>filesystem, would I save space when I made it 1K
>blocks?"
Agreed. I looked at /etc, which has "a lot of small
files" and the average files size was 5900 bytes - not
a goot cand
Cool. Feeling like that is one reason why I like working with Linux.
Changing the prereq for ucdsnmp should get you past that hurdle. The
initscripts prereq is the same thing, just another package on the system.
When I do a "rpm -ql initscripts" on a Red Hat system, I get a list of
files, some o
> creating initrd "/boot/initrd" for kernel "/boot/kernel/image"
> (version 2.4.21-83-default) (s390)
>
> dasd_mod: failed to add module "/lib/modules/2.4.21-83-
> default/kernel/drivers/s3
> 90/block/dasd_mod.o"
> initrd too small
>
> Run zipl now to update the IPL record!
>
> how do I make it big
OK, I am getting excited now. I just built my first rpm and it looks good,
at least to a Linux newbe like myself. I think I am ready to install it,
but?.
The following command reveals "rpm -ihv --test quagga-0.96.4-3.s390.rpm"
error: failed dependencies:
ucd-snmp is needed by quagga-0
IANAL and all that, but very interesting article. Also, very long!
http://www.groklaw.net/article.php?story=20040330184527522
--
John McKown
Senior Systems Programmer
UICI Insurance Center
Applications & Solutions Team
This message (including any attachments) contains confidential information
i
If you want to have the output come to your terminal _and_ sent to a file,
use the "tee" command:
rpm -bb quagga-0.96.4.spec | tee /path/to/output/file
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter
E. Abresch Jr. - at Pepco
Sent: Wednes
My zipl.conf does have that statement, but I didn't run the mkinitrd.
I just tried, but I get this error:
using "/dev/dasda1" as root device (mounted on "/" as "ext2")
Found ECKD dasd, adding das
> I am ready to do the "rpm ?bb quagga-0.96.4.spec". There was a method
to
> redirect the output to the terminal and to a file so I can review it.
It
> was a redirection command and for the life of me, I cannot get my
syntax
> correct. Can someone provide me the syntax?
Something like "rpm -bb qua
Did you run mkinitrd before you did the zipl ?
Installing a new kernel also installs new drivers, and you have to make a
new initrd to hold those drivers at IPL time since SuSE does not compile
the dasd drivers into the kernel. ( Neither does RedHat - for that matter )
Jay Brenneman
Linux Test a
I am getting all so close, I have completed my .spec file and successfully
tested it. Some last minute questions.
I am ready to do the "rpm ?bb quagga-0.96.4.spec". There was a method to
redirect the output to the terminal and to a file so I can review it. It
was a redirection command and for t
> Yes, I checked the zipl.conf and then ran zipl.
Does your zipl.conf have a line like "ramdisk=/boot/initrd" ?
If not, you should probably add it (run mkinitrd if you haven't), and
then run zipl again.
> > Loading module dasd_mod dasd=$dasd ...
> > insmod: dasd_mod: no module by that name found
Yes, I checked the zipl.conf and then ran zipl.
Yes the Kernel reports the new version which is: Linux version 2.4.21-83-default
I'm stumped.
Thanks
Gene
>>> [EMAIL PROTECTED] 03/31/04 08:17AM >>>
> I just put on SuSE SP3. When I IPL'd, it gives me these messages:
>
> Loading module dasd_mod d
> I just put on SuSE SP3. When I IPL'd, it gives me these messages:
>
> Loading module dasd_mod dasd=$dasd ...
> insmod: dasd_mod: no module by that name found
> Loading module dasd_eckd_mod ...
> insmod: dasd_eckd_mod: no module by that name found
> kmod: failed to exec /sbin/modprobe -s -k b
Hi Everyone,
I just put on SuSE SP3. When I IPL'd, it gives me these messages:
Loading module dasd_mod dasd=$dasd ...
insmod: dasd_mod: no module by that name found
Loading module dasd_eckd_mod ...
On Wednesday 31 March 2004 01:36, Jim Sibley wrote:
> But, in general, I would say that the 4k blocksize is
> preferable in the majority of cases. The space lost to
> eckd overhead is probably worse than any advantages
> you might get with small blocksizes.
Right. Of course one might just use Reis
Jim Sibley wrote:
- I'm sure other more skewed distributions would give
different results.
The best skewed distribution could be your own, so we may get the horse
dead by this:
"Given this 4K filesystem, would I save space when I made it 1K blocks?"
I think running a few find -size commands woul
Thanks Rob
This puts my heart at rest , just when I was thinking the learning curve was
slowing the thought of trying a DeveloperWorks install had me going .
Thanks
-Original Message-
From: Rob van der Heij [mailto:[EMAIL PROTECTED]
Sent: 31 March 2004 12:01 PM
To: [EMAIL PROTECTED]
Subj
Ceruti, Gerard G wrote:
Hi All
Please excuse the dumb question,
Is there doco on how to install the developerworks code, I am waiting for
the powers that be to approve a POC, but I would like to get started with
some self education before.
The audience for this code is the distributors and a few
Hi All
Please excuse the dumb question,
Is there doco on how to install the developerworks code, I am waiting for
the powers that be to approve a POC, but I would like to get started with
some self education before.
Thanks
Gerard Ceruti
-Original Message-
From: Gerhard Hiller [mailto:[EM
38 matches
Mail list logo
