From: Shane Deering <vk3bvp@qsl.net>
To: linux-hams@vger.kernel.org
Subject: Re: redhat 6.2 dies 3/31/2003 + AX25 2.4 kernel issues
Date: Thu, 26 Dec 2002 13:24:23 +1100 [thread overview]
Message-ID: <200212261324.23684.vk3bvp@qsl.net> (raw)
In-Reply-To: <3E099099.7070306@junglevision.com>
On Wed, 25 Dec 2002 22:03, Cathryn Mataga wrote:
> According to the Redhat website, Redhat 6.2 and 7.0
> both die on 3/31/2003. These are the only supported versions
> that run with the 2.2 kernel. But, I've also read messages
> here that the 2.4 kernel has race conditions and is prone
> to crash. So, the question is, what do I do with my ax25
> Linux system with RF modems on 3/31/2003?
I'm using 2.2.17-21mdk kernel with RH7.2 on my packet box.
It was compiled on a newer box running Mandrake 7.1 and copied to the redhad
box. It's a long story....
>
> 1. Somehow get the 2.4 kernel fixed by 3/31/2003? Is this
> possible? What exactly is the issue, and how bad is this?
> Is this likely to happen?
I found early 2.4 (before 2.4.18) kernels very unstable for ax25 stuff.
After 2.4.18 less unstable running on RH 7.2 and 7.3.
This computer (I'm typing on) has Mandrake 9.0 on it and the standard kernel
2.4.19 seems to work OK out of the box (using modules) for ax25 stuff. But
I've only ran the packet stuff for short periods with a single TNC. I don't
know how it would stand up to more, busier ports running long term.
--
Shane Deering vk3bvp@qsl.net vk3bvp@vk3bvp.#sev.vic.aus.oc
http://www.qsl.net/vk3bvp/ Up 1 hour and 56 minutes
Sent with KMail v1.4.1 on Thu Dec 26 13:07:03 EST 2002
next prev parent reply other threads:[~2002-12-26 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-25 11:03 redhat 6.2 dies 3/31/2003 + AX25 2.4 kernel issues Cathryn Mataga
2002-12-25 15:23 ` Chuck Gelm
2002-12-26 2:24 ` Shane Deering [this message]
[not found] ` <20021226162643.A31559@pull.privacy.nb.ca>
2002-12-27 3:44 ` Cathryn Mataga
2002-12-27 3:55 ` mvw
2002-12-27 16:52 ` Andrew Bates
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212261324.23684.vk3bvp@qsl.net \
--to=vk3bvp@qsl.net \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox