This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: support for calling Linux syscalls directly
- From: Rich Felker <dalias at aerifal dot cx>
- To: libc-alpha at sourceware dot org
- Date: Thu, 31 Jan 2013 19:11:28 -0500
- Subject: Re: support for calling Linux syscalls directly
- References: <201301242314.47793.vapier@gentoo.org><5109A662.7050101@zytor.com><20130131073057.GQ20323@brightrain.aerifal.cx><Pine.LNX.4.64.1301312309490.13481@digraph.polyomino.org.uk><510AFCF3.6080109@zytor.com><20130131233654.GR20323@brightrain.aerifal.cx><20130131234949.396B12C069@topped-with-meat.com>
On Thu, Jan 31, 2013 at 03:49:49PM -0800, Roland McGrath wrote:
> > The approach I proposed was to determine what's "glibc material". I
> > suspect everything that's not does not belong in a library at all. If
> > the syscall is specific to a single package (like modutils), then the
> > package (e.g. modutils) maintainers are going to be a lot more
> > competent dealing with the kernel interface than a third party trying
> > to maintain libinux.
>
> The plan is that libinux be maintained along with the kernel, which is by
> definition the place that knows the kernel interfaces best as they change.
I thought kernel interfaces were permanent and weren't allowed to
change... Making a library that's intended to be used to access them
with the idea that they "might change" sounds like a dangerous
precedent towards weakening the stability of the kernel API/ABI.
Rich