You may have run out of memory space on your RAM disk while you
were doing the full backup (Or something like that ;)
This could have caused the package to go corrupted. My experience of kernel
panic in leaf is often due to some lack of memory.
This is what I would investigate if I were you.
I have not had luck with Bering uclibc -- some of my nics are natsemi,
and I could not get a working natsemi.o.
Is this really an issue? I've got several 1.2 boxes that I was planning on
eventually moving to uclibc but this would be a showstopper.
- Bob Coffman
Hi!
-Original Message-
From: Robert K Coffman Jr - Info From Data Corporation
[mailto:[EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 2:31 PM
To: [EMAIL PROTECTED]
Subject: [leaf-user] Natsemi.o
I have not had luck with Bering uclibc -- some of my nics
are natsemi,
and
Hi Bob,
Robert K Coffman Jr - Info From Data Corporation wrote:
I have not had luck with Bering uclibc -- some of my nics are natsemi,
and I could not get a working natsemi.o.
Is this really an issue? I've got several 1.2 boxes that I was planning on
eventually moving to uclibc but this would be
I think I tried it on uclibc 2.0.2 or whatnot.
Maybe 2.2 is working.
Didn't mean to spread FUD!
Rick.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin Hejl
Sent: Thursday, November 11, 2004 1:20 PM
To: [EMAIL PROTECTED]
Subject: Re: [leaf-user]
OK, the verdict seems to be that Charles' suggestion worked (for pings
-- we are only testing the connection with pings) --- so I doubt that
ping tests the CLAMPMSS parm. A large file transfer would probably need
it so I put CLAMPMSS=yes in shorwall.conf.
We are now able to ping across campus.
