From: ebiederm+eric@npwt.net (Eric W. Biederman)
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: glibc and kernel update
Date: 26 Jun 1998 09:43:57 -0500 [thread overview]
Message-ID: <m1iulofck2.fsf@flinx.npwt.net> (raw)
In-Reply-To: Rik van Riel's message of Fri, 26 Jun 1998 06:34:41 +0200 (CEST)
>>>>> "RR" == Rik van Riel <H.H.vanRiel@phys.uu.nl> writes:
RR> On 25 Jun 1998, Eric W. Biederman wrote:
RR> I still haven't resolved the problems between glibc, the
RR> 2.1 kernel series and pppd :(
>>
RR> Now I got a new idea: Since most of the kernel interfaces
RR> go through glibc, does this mean that I have to get the
RR> glibc source and recompile the whole thing in order to get
RR> working ppp with a 2.1 kernel?
>>
>> Just what problem are you having?
RR> Pppd dies with "This kernel doesn't support PPP", while it
RR> most certainly _does_. I traced it back to a socket operation
RR> which isn't exported properly through glibc...
>> I just got 2.3.5 to compile with glibc, but I haven't had a chance to
>> test it yet..
RR> It compiles perfectly. It just doesn't run ;(
I just did a second test.
pppd-2.3.5 with glibc-2.0.6 on kernel-2.1.101 (with a few patches)
pppd works here.
The only thing I can imagine is do your /usr/include/linux & /usr/include/asm
point to ``safe'' kernel headers or the real thing. Mine point to the real thing.
Eric
next prev parent reply other threads:[~1998-06-26 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-25 13:58 glibc and kernel update Rik van Riel
1998-06-25 15:46 ` Eric W. Biederman
1998-06-25 21:25 ` Eric W. Biederman
1998-06-26 4:34 ` Rik van Riel
1998-06-26 14:43 ` Eric W. Biederman [this message]
1998-06-25 16:34 ` Stephen C. Tweedie
1998-06-26 4:32 ` Rik van Riel
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=m1iulofck2.fsf@flinx.npwt.net \
--to=ebiederm+eric@npwt.net \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.