From: "Paul Fulghum" <paulkf@microgate.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: SyncPPP Generic PPP merge
Date: Thu, 24 May 2001 14:27:48 -0600 [thread overview]
Message-ID: <002501c0e48f$ffed1e40$0c00a8c0@diemos> (raw)
In-Reply-To: <E152zbc-0005Oz-00@the-village.bc.nu>
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
> I had hoped for 2.4 to use generic ppp with it. That might be the more
> productive way to attack the problem.
Generic PPP requires the user mode pppd to handle
the LCP and NCPs, while syncppp implements these in
the kernel.
Instead of using ifconfig to bring an interface
up or down, the user must now work with pppd. And the net
device naming changes (allocated by ppp_generic.c instead
of using the net device allocated by low level driver).
I have no problem with this, but some people might
not be happy with the change.
Is the plan to *replace* the PPP code in syncppp
(hopefully in a way that is invisible to the
low level drivers)?
Or is it to *add* generic PPP support to syncppp,
leaving (at least temporarily) the existing PPP
capability in syncppp for compatibility?
(implying a new syncppp flag USE_GENERIC_PPP?)
Paul Fulghum paulkf@microgate.com
Microgate Corporation www.microgate.com
next prev parent reply other threads:[~2001-05-24 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 10:51 SyncPPP IPCP/LCP loop problem and patch rjd
2001-05-22 12:31 ` Paul Mackerras
2001-05-22 13:34 ` rjd
2001-05-22 16:11 ` Paul Fulghum
2001-05-24 15:11 ` SyncPPP IPCP/LCP loop problem and patch. Take 2 rjd
2001-05-22 18:13 ` SyncPPP IPCP/LCP loop problem and patch Paul Fulghum
2001-05-24 15:30 ` rjd
2001-05-24 16:56 ` Paul Fulghum
2001-05-24 18:13 ` Alan Cox
2001-05-24 20:27 ` Paul Fulghum [this message]
2001-05-24 22:18 ` SyncPPP Generic PPP merge Alan Cox
2001-05-24 22:53 ` Jeff Mcadams
2001-05-25 0:55 ` Paul Mackerras
2001-05-25 16:44 ` Jeff Mcadams
2001-05-24 23:27 ` Paul Fulghum
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='002501c0e48f$ffed1e40$0c00a8c0@diemos' \
--to=paulkf@microgate.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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