From: Daniel Jacobowitz <dan@debian.org>
To: Mariusz Mazur <mmazur@kernel.pl>
Cc: linux-kernel@vger.kernel.org, debian-glibc@lists.debian.org
Subject: Re: Userland headers available
Date: Fri, 23 Jan 2004 13:47:55 -0500 [thread overview]
Message-ID: <20040123184755.GA2138@nevyn.them.org> (raw)
In-Reply-To: <200401231907.17802.mmazur@kernel.pl>
On Fri, Jan 23, 2004 at 07:07:17PM +0100, Mariusz Mazur wrote:
> At http://ep09.pld-linux.org/~mmazur/glibc-kernel-headers/ there are userland
> headers for linux, derived from 2.6 kernels with lots of 2.4 compatibility
> fixes. CVS repo can be found at cvs.pld-linux.org/glibc-kernel-headers (anon
> and webcvs). These headers are currently used to compile a whole linux distro
> (ftp.pld-linux.org/dists/ac) for x86, sparc, amd64, alpha and ppc, but
> general fixes are applied to all archs since we never know if a new arch
> won't be added (amd64 was added just a month-two ago). #1 feature is that
> they are and will be maintained (currently three people are working on them)
> and bugs are mostly fixed instantly. Enjoy.
I've done precisely the same thing for Debian - if I find the time,
I'll compare...
I would really like to come up with an approach to maintain this
interface definition in the kernel source. I'm still trying to think
of a way to do it without breaking compatibility or kernel builds.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-23 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 18:07 Userland headers available Mariusz Mazur
2004-01-23 18:47 ` Daniel Jacobowitz [this message]
2004-01-23 19:04 ` Mariusz Mazur
2004-01-23 19:15 ` Chris Friesen
2004-01-23 19:39 ` Chris Friesen
2004-01-23 23:47 ` jw schultz
2004-01-24 1:38 ` H. Peter Anvin
2004-01-25 23:30 ` Daniel Jacobowitz
2004-01-26 0:09 ` H. Peter Anvin
2004-01-23 20:28 ` Sam Ravnborg
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=20040123184755.GA2138@nevyn.them.org \
--to=dan@debian.org \
--cc=debian-glibc@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmazur@kernel.pl \
/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.