From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: Linux MM <linux-mm@kvack.org>
Subject: glibc and kernel update
Date: Thu, 25 Jun 1998 15:58:12 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.3.96.980625155639.31988C-100000@mirkwood.dummy.home> (raw)
Hi,
I still haven't resolved the problems between glibc, the
2.1 kernel series and pppd :(
Now I got a new idea: Since most of the kernel interfaces
go through glibc, does this mean that I have to get the
glibc source and recompile the whole thing in order to get
working ppp with a 2.1 kernel?
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
next reply other threads:[~1998-06-25 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-25 13:58 Rik van Riel [this message]
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
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=Pine.LNX.3.96.980625155639.31988C-100000@mirkwood.dummy.home \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox