mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Abraham vd Merwe <abraham@2d3d.co.za>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Felix von Leitner <leitner@fefe.de>
Subject: Re: kernel headers & userland
Date: Mon, 6 Aug 2001 13:09:24 +0200	[thread overview]
Message-ID: <20010806130924.A14167@crystal.2d3d.co.za> (raw)
In-Reply-To: <20010806095638.A5638@crystal.2d3d.co.za> <m166c1wj66.fsf@frodo.biederman.org>
In-Reply-To: <m166c1wj66.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Mon, Aug 06, 2001 at 04:56:49 -0600

[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]

Hi Eric!

> > Apparently Linus told Felix von Leitner (the author of dietlibc - a small,
> > no nonsense glibc replacement C library) a while ago _not_ to include any
> > linux kernel headers in userland (i.e. the C library headers in this case).
> > 
> > This imho is obviously wrong since there are definitely a need for including
> > kernel headers on a linux platform.
> 
> ???  Necessity no.  Are there practical benefits yes.
> 
> The policy of the kernel developers in general is that if your apps
> includes kernel headers and it breaks, it is a kernel problem.
> 
> As for ioctl it is a giant mess that needs to be taken out and shot.
> 
> And yes there are places where even the mighty glibc is in the wrong.

Just acknowledging that it is a problem doesn't solve the problem though.
The question remains how you approach the kernel headers issue at the moment?

My guess is the only way is by including the kernel headers for now and
change it one day when someone decides to clean up the mess.

-- 

Regards
 Abraham

Every absurdity has a champion who will defend it.

__________________________________________________________
 Abraham vd Merwe - 2d3D, Inc.

 Device Driver Development, Outsourcing, Embedded Systems

  Cell: +27 82 565 4451         Snailmail:
   Tel: +27 21 761 7549            Block C, Antree Park
   Fax: +27 21 761 7648            Doncaster Road
 Email: abraham@2d3d.co.za         Kenilworth, 7700
  Http: http://www.2d3d.com        South Africa


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-08-06 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-06  7:56 Abraham vd Merwe
2001-08-06 10:56 ` Eric W. Biederman
2001-08-06 11:09   ` Abraham vd Merwe [this message]
2001-08-06 15:20     ` Eric W. Biederman
2001-08-06 12:41 ` Alan Cox

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=20010806130924.A14167@crystal.2d3d.co.za \
    --to=abraham@2d3d.co.za \
    --cc=ebiederm@xmission.com \
    --cc=leitner@fefe.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®