Re: auto starting of ppp has stopped working
On Friday, August 1, 2014 1:10:02 PM UTC+5:30, Chris Bannister wrote:
> On Fri, Aug 01, 2014 at 12:13:43AM -0700, Rusi Mody wrote:
> > On Friday, August 1, 2014 12:20:02 PM UTC+5:30, Chris Bannister wrote:
> > > On Thu, Jul 31, 2014 at 09:32:08PM -0700, Rusi Mody wrote:
> > > > So now the question is:
> > > > What is the 'modern' way of automatically doing 'modprobe pppoe'
> > > > at boot/ifup time?
> > > > Evidently something has changed that has made that stop happening...
> > > Put it in /etc/modules. I hope that is still the place. BTW, a quick
> > > google should have helped with this ... was Google unhelpful in this
> > > instance?
> > A quick google tells me that there are all sorts of places:
> > /etc/{modules,modprobe.d,modules-load.d}
> So, did you try /etc/modules?
Of course if modprobe is working putting it into /etc/modules should also.
I thought I explained why I find that an unsavoury solution. Let me try again.
The kernel is the innermost core of the system
The user is the outermost peel of the onion
Networking is somewhere in between.
This part was working and has stopped is part of the networking subsystem.
A good solution should be in that same arena.
Ideal would be (something like):
"Install such-&-such package. It takes care of this"
Slightly less but still acceptable would be:
Add such-&-such line to /etc/networking (or one of the other networking
config files)
Since I cant seem to find any such solutions, I prefer the following user-level
bandaid to a kernel level one:
$ cat ~/bin/pon
sudo modprobe pppoe
sudo pon dsl-provider
> [...]
> > tl;dr:
> http://knowyourmeme.com/memes/tldr
> "too long; didn't read"? ... um ... what was?
My own post 'above' is what the 'tl;dr' referred to :-)
Reply to: