> 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 suspect that bit can be fixed if need be. Its nice to keep a constant
naming between cisco/ppp modes. cisco/ppp autodetect is also possible and would
be rather nice to support
> 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?)
Assuming this is a 'when 2.5 starts' discussion I'd like initially to keep the
syncppp api is but the pppd code going via generic ppp - and yes it would
break configs.
Clearly thats not 2.4 acceptable
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 31 2001 - 21:00:20 EST