From: Paul Mackerras <paulus@linuxcare.com.au>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: l_indien@magic.fr, jma@netgem.com, jfree@sovereign.org,
linux-kernel@vger.kernel.org
Subject: Re: Bug in ppp_async.c
Date: Wed, 24 Jan 2001 20:45:33 +1100 (EST) [thread overview]
Message-ID: <14958.42045.576523.62083@argo.linuxcare.com.au> (raw)
In-Reply-To: <200101240701.f0O71OE110437@saturn.cs.uml.edu>
In-Reply-To: <14958.25201.508164.388346@diego.linuxcare.com.au> <200101240701.f0O71OE110437@saturn.cs.uml.edu>
Albert D. Cahalan writes:
> Even Red Hat 7 only has the 2.3.11 version.
>
> The 2.4.xx series is supposed to be stable. If there is any way
> you could add a compatibility hack, please do so.
Stable != backwards compatible to the year dot. ppp-2.4.0 has been
out for over 5 months now. Adding the compatibility stuff back in
would make the PPP subsystem much more complicated and less robust.
And pppd is not the only thing you would have to upgrade if you are
using a 2.4.0 with Red Hat 7.0 - I would expect that you would also at
least have to upgrade modutils, and switch over from ipchains to
iptables if you use the netfilter stuff.
Paul.
--
Paul Mackerras, Open Source Research Fellow, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 3:37 Bug in ppp_async.c Jo l'Indien
2001-01-24 5:04 ` Paul Mackerras
2001-01-24 7:01 ` Albert D. Cahalan
2001-01-24 8:42 ` David Woodhouse
2001-01-24 9:45 ` Paul Mackerras [this message]
2001-01-24 18:03 ` Dan Egli
2001-01-26 5:17 ` Albert D. Cahalan
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=14958.42045.576523.62083@argo.linuxcare.com.au \
--to=paulus@linuxcare.com.au \
--cc=acahalan@cs.uml.edu \
--cc=jfree@sovereign.org \
--cc=jma@netgem.com \
--cc=l_indien@magic.fr \
--cc=linux-kernel@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