Hi, On Sun, Apr 27, 2008 at 03:14:19PM +0900, Osamu Aoki wrote: > > I agree that it could be the best /e/n/i. > > Before changing it, I must ensure: > > - to have a perfect transition from etch and from sarge, > > - to have a valid comportement with kernel_pppoe =1 and =0, > > - not to have conflicts with current network configuration (your > > proposition uses eth0 for PPPoE interface, but it's not easy to > > disable current eth0 configuration as I said above). > > If you want to do this, adding warinig when finding current eth0 > configuration in /e/n/i. > > > I'm waiting your comments before hacking... > > I personally think, it is best comment out current /e/n/i contents as > comment and add fresh pppoe only configuration. Whoever mkes any more > complicated configuration should know how to edit it. (Possibly with > message displayed to the user.) > > We need to rotect newbie hitting problem.
IMHO it's too "violent" to comment out /e/n/i even with a fat warning. It's a shame /e/n/i could not be easily parsed... Anyway, due to lack of time, I don't change anything for lenny (pppoeconf is well-known for "just working" then I don't want break it). I start a branch named "experimental" to apply your recommandation: http://git.debian.org/?p=collab-maint/pppoeconf.git;a=shortlog;h=refs/heads/experimental Comments or patches welcome. Regards, -- Gregory Colpart <[EMAIL PROTECTED]> GnuPG:1024D/C1027A0E Evolix - Informatique et Logiciels Libres http://www.evolix.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
