> As said to the previous bug reporters, it is simply not my job to load > _kernel_ modules for some other package. It would just additional > complexity while there are other places where it must be fixed. I agree > that this bug looks very shameful for a fresh Debian release so it > should be release critical. Especially when there is such a simple fix.
I agree with you about the bug#263224 importance. I believe though that pppoeconfig might need to at least give a hint about the need to have the module preloaded - right now the behaviour during pppoeconfig is inconsistent with the behaviour after the fresh boot when just pppoe is being run. I agree that it is out of the scope of pppoe or pppd. But, ideally, pppoeconfing aiming to be a 1-2-3 setup wizard type of program, I think it should do everything including modconf-ing the module in forever if necessary, or at least offering this interactively as an option. > PS: I won't clone 265183, there are already enough bug reports to the > pppoe module problem. But what about the routing loop problem I had mentioned in the original 265183 report? It is something pretty confusing for a new user. Kind regards, Vassilii P.S. Sorry for a long silence - I was on vacation abroad, away from my home which is where all my ADSL hardware lives. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
