From: James Cameron <james.cameron@hp.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP connect hangs at "getlogname (AUTO_PPP), read:"
Date: Tue, 13 Apr 2004 22:58:18 +0000 [thread overview]
Message-ID: <20040413225818.GA21157@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404130851580.8284@localhost.localdomain>
G'day, a different James here ...
Robert P. J. Day wrote:
> ppp async is compiled into the kernel. but i also just noticed that
> ppp sync is there as well, i'm hoping it's not a problem to have them
> both built into the kernel.
I don't think that both being built should be a problem.
The two PPTP projects regularly find users who have compiled the PPP
components into the kernel, yet they do not function for them unless
they are compiled as modules. We haven't got to the bottom of this. We
even have evidence of a few people finding it works fine built
statically.
So I would suggest building the PPP kernel components as modules, just
to see if it makes any difference. ;-)
--
James Cameron http://quozl.netrek.org/
HP Open Source, Volunteer http://opensource.hp.com/
PPTP Client Project, Release Engineer http://pptpclient.sourceforge.net/
next prev parent reply other threads:[~2004-04-13 22:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 13:02 PPP connect hangs at "getlogname (AUTO_PPP), read:" Robert P. J. Day
2004-04-13 13:30 ` James Carlson
2004-04-13 13:30 ` Robert P. J. Day
2004-04-13 15:05 ` Robert P. J. Day
2004-04-13 15:39 ` James Carlson
2004-04-13 16:04 ` Bill Unruh
2004-04-13 16:28 ` Robert P. J. Day
2004-04-13 16:44 ` James Carlson
2004-04-13 17:00 ` Robert P. J. Day
2004-04-13 17:07 ` James Carlson
2004-04-13 18:09 ` Robert P. J. Day
2004-04-13 18:23 ` James Carlson
2004-04-13 18:53 ` Robert P. J. Day
2004-04-13 22:58 ` James Cameron [this message]
2004-04-13 23:10 ` Robert P. J. Day
2004-04-13 23:18 ` James Cameron
2004-04-15 13:26 ` Robert P. J. Day
2004-04-15 23:28 ` James Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040413225818.GA21157@hp.com \
--to=james.cameron@hp.com \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).