From: Jeff Garzik <garzik@havoc.gtf.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: DervishD <raul@viadomus.com>,
ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: Why 'linux/fs.h' cannot be included? I *can*...
Date: Tue, 29 Jan 2002 09:42:44 -0500 [thread overview]
Message-ID: <20020129094244.F10404@havoc.gtf.org> (raw)
In-Reply-To: <20020129093024.E10404@havoc.gtf.org> <E16VZbr-00046x-00@the-village.bc.nu>
In-Reply-To: <E16VZbr-00046x-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Jan 29, 2002 at 02:51:43PM +0000
On Tue, Jan 29, 2002 at 02:51:43PM +0000, Alan Cox wrote:
> > Your libc should provide a "sanitized" version of the kernel headers,
> > which is completely separate from any kernel sources.
> >
> > dietlibc does this... it's completely independent of kernel header changes.
> >
> > RedHat will be doing this with glibc in the future.
>
> We already do. Red Hat shipped since about 7.0 has a seperate set of
> kernel based headers that glibc uses for its own internal use, and the set
> in the kernel sources.
To clarify, Arjan said the headers were going to be further sanitized,
and less just simple copies of selected kernel headers... <cheer>
That's what I wanted to say, but -ENOCAFFEINE :)
Jeff
next prev parent reply other threads:[~2002-01-29 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 10:20 DervishD
2002-01-29 14:30 ` Jeff Garzik
2002-01-29 14:51 ` Alan Cox
2002-01-29 14:42 ` Jeff Garzik [this message]
[not found] <mailman.1012391761.28301.linux-kernel2news@redhat.com>
2002-01-30 18:24 ` Pete Zaitcev
2002-01-30 23:33 ` Keith Owens
2002-01-31 1:17 ` Jeff Garzik
2002-01-31 1:51 ` Keith Owens
2002-01-31 1:57 ` Jeff Garzik
2002-01-31 2:06 ` Keith Owens
2002-01-31 2:35 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 12:07 DervishD
2002-01-30 14:27 ` Eric W. Biederman
2002-01-30 16:12 ` Jeff Garzik
2002-01-28 19:31 DervishD
2002-01-28 19:44 ` 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=20020129094244.F10404@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@viadomus.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
Powered by JetHome