All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cathryn Mataga <cathrynm@junglevision.com>
To: linux-hams <linux-hams@vger.kernel.org>
Subject: redhat 6.2 dies 3/31/2003 + AX25 2.4 kernel issues
Date: Wed, 25 Dec 2002 03:03:53 -0800	[thread overview]
Message-ID: <3E099099.7070306@junglevision.com> (raw)

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?

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?

2.  Just live with the crashing.  Cycle the power on the
machine every other day with a timer or some other horrible solution.
Maybe it won't be that that bad.

3.  Maybe someone other than Redhat will continue to do security patches
for 6.2?  I can't believe I'm the only one running 6.2.  Right?

4.  Upgrade to a new Redhat, but somehow install a 2.2 kernel in
a distribution designed for 2.4.  Will this work?  (I'm scared.)

5.  Switch to some other distribution that will continue to support
2.2 after 3/31/2003.

6.  Continue with 6.2 and keep an eye out for vulnerabilities and
maybe strip out a few services that I use otherwise.


             reply	other threads:[~2002-12-25 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-25 11:03 Cathryn Mataga [this message]
2002-12-25 15:23 ` redhat 6.2 dies 3/31/2003 + AX25 2.4 kernel issues Chuck Gelm
2002-12-26  2:24 ` Shane Deering
     [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=3E099099.7070306@junglevision.com \
    --to=cathrynm@junglevision.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.