On Sun, 2009-01-25 at 19:40 -0500, Darren Albers wrote:
> On Sun, Jan 25, 2009 at 6:38 PM, Chris Frey <cdf...@foursquare.net> wrote:
> > On Sun, Jan 25, 2009 at 06:27:06AM -0500, Rick Scott wrote:
> >> I suspect the problem comes down to the fact that you never know what
> >> pty you are going to get. A kernel module would get rid of this problem.
> >
> > That could be.  But when tethering over a Blackberry is as simple
> > as 'pppd call provider' from the command line, a GUI that makes it
> > even harder to use seems broken in my estimation.
> >
> > But I guess I'm a little hard-headed like that.  There's got to be a way! 
> > :-)
> >
> > I'd like to see both pppob and your kernel module working for this.
> > Have you gotten kernel+modem+NetworkManager working?
> >
> > - Chris
> >
> >
> 
> The reason for the way Network Manager does it now is so that
> everything is autodetected.   The device is inserted, udev and HAL
> make the device available to NetworkManager and tell it the serial
> port to talk to.   This way the user doesn't have to do anything, the
> device just works.   I did post on the NM Mailing list to see if Dan
> or anyone know of a way to make it work but I don't think there is at
> this time (The new Modem Manager being written for .8 might be able to
> handle this).
> 
> What Rich wrote looks to be the best option in the near-term, I just
> need to get XLT to build or to build the Kernel module without the
> GUI.

Just cd to the kernel directory and type make.

> 
> Is it possible to run pppob so that it exports the serial interface
> rather than over stdin/stdout?

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel

Reply via email to