From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Patrick Shirkey <pshirkey@boosthardware.com>,
linux-kernel@vger.kernel.org
Subject: Re: Files not linking/replacing.
Date: Mon, 16 Apr 2001 02:43:40 -0400 [thread overview]
Message-ID: <3ADA949C.D10D8536@mandrakesoft.com> (raw)
In-Reply-To: <3ADA524A.7038A81C@boosthardware.com> <m1eluttkx2.fsf@frodo.biederman.org>
"Eric W. Biederman" wrote:
> Normally /usr/src/linux on a redhat system contains a kernel with a
> known good set of kernel headers. /usr/include/linux and
> /usr/include/asm are symlinks that point into the known good kernel
> headers. It looks like you removed your known good 2.2.14 known good
> kernel headers, or the symlinks to them.
Modern glibc systems have their own copies of headers for
/usr/include/{asm,linux}, and those locations should not be pointing to
kernel space...
--
Jeff Garzik | "Give a man a fish, and he eats for a day. Teach a
Building 1024 | man to fish, and a US Navy submarine will make sure
MandrakeSoft | he's never hungry again." -- Chris Neufeld
next prev parent reply other threads:[~2001-04-16 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-16 2:00 Files not linking/replacing Patrick Shirkey
2001-04-16 6:31 ` Eric W. Biederman
2001-04-16 6:43 ` Jeff Garzik [this message]
2001-04-17 5:27 ` Eric W. Biederman
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=3ADA949C.D10D8536@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pshirkey@boosthardware.com \
/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