lkml.org 
[lkml]   [1998]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: OFFTOPIC: e2fsprogs and +2Gb partitions


On 17 Jun 1998, Andi Kleen wrote:
>
> Most of this can be simply solved by a few #ifdef __KERNEL__. Is that really
> that difficult?

Yes. I've had _years_ of headaches. I've gone through this.

The point is that there is _NO_ point in not just copying over the header
files, and using the copies.

"#ifdef __KERNEL__" does not help. It's one small thing that needs to be
done if you don't do the sane thing, but it doesn't solve the placement
issue.

Furthermore, the whole point is that I'm doing the KERNEL. Nothing more. I
don't _want_ to know what one million user programs expect from their
headers. Have you ever looked into a user-level header? It's a disgusting
maze of

#if (defined(__ANSI__) && !defined(__POSIX__)) || defined(__MY_PET_POODLE__)
...
#elif defined(__BSD_EXTENSIONS__)
...
#elif defined(__OTHER_CRAP__) || defined(__USE_ALL)
..

and while some people have successfully bullied me into accepting a
limited form of that into the kernel, I just don't want to have anything
to do with anything like this. It's not something that the kernel header
files should care about, because the kernel developers don't care about
it.

I think that kernel header files should be used for building the kernel.
Nothing else.

Linus


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.978 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site