Geez, calm down. You catch more flies with honey than with vinegar.
Also, isn't the warning pretty self-explanatory?
"man ioctl" shows that sys/ioctl.h is expected to be used in userland.
And, unlike userland, it's not like the kernel has any obligation to be the
same across Unices, so I'm wondering on what you base the supposition that
God decreed the One True And Correct Way for this to work?
On Thursday 11 April 2002 09:40 am, you wrote:
| Ok, why on earth is there a #warning for including <sys/ioctl.h> for
| kernel stuff ?
|
| By definition, /usr/include/sys _IS_ kernel include files.
|
| Has some crack monkey been playing with include files again ?
|
| If the current <sys/ioctl.h> isn't for use in the kernel, will someone
| please replace it with one that is or just delete it ?
|
| Yes, I'm aware that deleting it will cause all hell to break loose in
| terms of compatibility, but for christ sake, whoever's messing around
| with this stuff should *really* get their act together.
|
| Next you'll have files in /usr/include for including into the kernel
| and not userspace!
|
|
| To Unsubscribe: send mail to [EMAIL PROTECTED]
| with "unsubscribe freebsd-stable" in the body of the message
--
Brian T. Schellenberger . . . . . . . [EMAIL PROTECTED] (work)
Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal)
ME --> http://www.babbleon.org
http://www.eff.org <-- GOOD GUYS --> http://www.programming-freedom.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
