Re: State of userland headers

[Rob Landley <rob@landley.net>]

On Sunday 26 March 2006 8:12 am, Mariusz Mazur wrote:
> On Friday 24 March 2006 00:04, Rob Landley wrote:
> > You also don't want to run a libc built with newer headers than the
> > kernel you're running on, or it'll try to use stuff that isn't there.
> >
> > You're saying that the new kernel headers wouldn't be versioned using the
> > kernel's release numbers.  How do we know what kernel version their
> > feature set matches then?  (I'm confused.  This happens easily...)
>
> That's a tradeoff. You either version the headers just like I did, meaning
> that a given version corresponds to a given kernel, but that means you
> can't release before all of the archs are fully updated (and not relying on
> a single person to do all of the updates is one of the points of the
> exercise; and with more people, one can have delays) or you're forced to
> figure out some other way to version the headers.

If somebody #includes <linux/version.h> from the new headers, and can 
determine what kernel version it goes with for their platform from that (even 
if the different platforms are out of sync), and said information also goes 
in a README or release notes or some such, I'll live.

Rob
-- 
Never bet against the cheap plastic solution.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/