All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias DiPasquale <codeslinger@gmail.com>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Jim Gifford <maillist@jg555.com>,
	Netfilter Developer <netfilter-devel@lists.netfilter.org>
Subject: Re: Use of Kernel Headers
Date: Sat, 21 Aug 2004 10:53:57 -0400	[thread overview]
Message-ID: <876ef97a0408210753109a2fc4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408211114310.16646@filer.marasystems.com>

On Sat, 21 Aug 2004 11:30:36 +0200 (CEST), Henrik Nordstrom
<hno@marasystems.com> wrote:
> 
> 
> On Fri, 20 Aug 2004, Jim Gifford wrote:
> 
> > This all goes back to having true separation between the kernel and
> > userspace, I'm starting to think iptables is different in it's situation and
> > true separation will never be possible
> 
> Separation is possible, it is mainly a matter of how the userspace headers
> should be maintained and how to ensure kernel compatibility to a
> reasonable manner (i.e. mostly an adminstrative issue). Today a lot of the
> kernel release compatibility depends on using the kernel headers. There is
> also a one or two extensions which have more complex dependencies but I
> think all of these is in pom extra.

Perhaps a special macro could be used to demarcate the sections of
kernel headers that are for userspace use (opposite of what __KERNEL__
does now). Then, when you wanted a set of headers for userspace apps
to use when they needed to interface with the kernel, a script could
be run to strip out all sections of the headers that were not
demarcated for use by userspace, and only those headers would be
copied into /usr/include/linux? Would that be a workable solution? Or
is it more complicated than that?

-- 
[ Tobias DiPasquale ]
0x636f6465736c696e67657240676d61696c2e636f6d

  reply	other threads:[~2004-08-21 14:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 21:10 Use of Kernel Headers Jim Gifford
2004-08-17 23:32 ` Henrik Nordstrom
2004-08-18  5:36   ` Jim Gifford
2004-08-18 19:00     ` Henrik Nordstrom
2004-08-18 19:25       ` Jim Gifford
2004-08-18 20:03         ` Henrik Nordstrom
2004-08-18 20:48           ` Jim Gifford
2004-08-18 20:51             ` Henrik Nordstrom
2004-08-18 21:01               ` Jim Gifford
2004-08-18 22:30   ` Jozsef Kadlecsik
2004-08-21  6:47     ` Jim Gifford
2004-08-21  9:30       ` Henrik Nordstrom
2004-08-21 14:53         ` Tobias DiPasquale [this message]
2004-08-21 15:13           ` Henrik Nordstrom
  -- strict thread matches above, loose matches on Subject: below --
2004-08-17 20:40 Jim Gifford
2004-08-17 21:00 ` Antony Stone
2004-08-17 21:09   ` Jim Gifford

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=876ef97a0408210753109a2fc4@mail.gmail.com \
    --to=codeslinger@gmail.com \
    --cc=hno@marasystems.com \
    --cc=maillist@jg555.com \
    --cc=netfilter-devel@lists.netfilter.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 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.