From: Matthew Reppert <repp0017@tc.umn.edu>
To: weeteck@linux.net
Cc: Mark Hahn <hahn@physics.mcmaster.ca>, linux-kernel@vger.kernel.org
Subject: Re: Kernel include file
Date: Mon, 08 Dec 2003 21:07:17 -0600 [thread overview]
Message-ID: <1070939237.24409.5.camel@minerva> (raw)
In-Reply-To: <20031207161929.7E0953951@sitemail.everyone.net>
On Sun, 2003-12-07 at 10:19, Neo Wee Teck wrote:
> Hmm... wrong idea...
>
> <new kernel>/include/linux
>
> update to..
>
> /usr/include/linux
>
> Should I?
No.
The headers in /usr/include/linux "belong to" glibc and should never be
changed, as it may cause newly compiled programs to break in nasty and
subtle ways.
kernelnewbies.org has a nice FAQ item on this.
Matt
next prev parent reply other threads:[~2003-12-09 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 16:19 Kernel include file Neo Wee Teck
2003-12-09 3:07 ` Matthew Reppert [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-07 15:54 Neo Wee Teck
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=1070939237.24409.5.camel@minerva \
--to=repp0017@tc.umn.edu \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=weeteck@linux.net \
/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