From: "J.A. Magallon" <jamagallon@able.es>
To: Andries.Brouwer@cwi.nl
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] linuxabi
Date: Wed, 1 Oct 2003 12:20:01 +0200 [thread overview]
Message-ID: <20031001102001.GA3495@werewolf.able.es> (raw)
In-Reply-To: <UTC200310010001.h9101NU17078.aeb@smtp.cwi.nl> (from Andries.Brouwer@cwi.nl on Wed, Oct 01, 2003 at 02:01:23 +0200)
On 10.01, Andries.Brouwer@cwi.nl wrote:
> Hi Linus,
>
> Something we have talked about for a long time is
> separating out from the kernel headers the parts
> fit for inclusion in user space.
>
> This is a very large project, and it will take a long
> time, especially if we want the user space headers to
> be a pleasure to look at, instead of just a cut-n-paste
> copy of whatever we find in the current headers.
>
> Some start is required, and the very first step is
> making sure that you agree with the project.
> Immediately following is the choice of directory names.
>
> Below
> (i) a small textfile "linuxabi" describing the naming
> (subdirectories linuxabi and linuxabi-alpha etc of include),
Why not just 'abi' ? Simpler, and allows glibc to include
just 'abi/xxxx' in other systems if they follow the same convention (BSD?) ?
Where would this live in userspace, /usr/include/abi or /usr/include/linux/abi ?
How would this relate to current /usr/include/linux
(symlink /usr/include/linux to /usr/include/abi) ?
Just curious.
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.23-pre5-jam1 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-2mdk))
next prev parent reply other threads:[~2003-10-01 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 0:01 [PATCH] linuxabi Andries.Brouwer
2003-10-01 2:05 ` Bernd Eckenfels
2003-10-01 3:34 ` viro
2003-10-01 4:52 ` H. Peter Anvin
2003-10-01 5:22 ` Philippe Troin
2003-10-01 5:50 ` Miles Bader
2003-10-01 14:33 ` Daniel Jacobowitz
2003-10-01 10:20 ` J.A. Magallon [this message]
2003-10-02 14:39 ` Eric W. Biederman
2003-10-02 15:33 ` Andries Brouwer
2003-10-03 7:36 ` Eric W. Biederman
2003-10-04 3:37 ` Rob Landley
2003-10-04 6:31 ` Erik Andersen
[not found] ` <fa.e2g5r6g.u3igb4@ifi.uio.no>
2003-10-03 16:49 ` Kai Henningsen
2003-10-03 17:32 ` Sam Ravnborg
[not found] <BCSP.62t.7@gated-at.bofh.it>
[not found] ` <CcWl.7kh.9@gated-at.bofh.it>
[not found] ` <CdIL.8ts.13@gated-at.bofh.it>
2003-10-03 14:02 ` Ihar 'Philips' Filipau
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=20031001102001.GA3495@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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