Date: Sun, 14 Dec 1997 23:09:50 +0100 (MET) From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org Subject: Re: New option model (was Re: cvs commit: src/sys/kern kern_exit.c) Message-ID: <199712142209.XAA01033@uriah.heep.sax.de> References: <199712071816.KAA21840@freefall.freebsd.org> <19971208091729.40125@uriah.heep.sax.de> <863ek4p1tx.fsf_-_@bitbox.follo.net> <199712100013.BAA04827@uriah.heep.sax.de> <863ek1xtsl.fsf@bitbox.follo.net> <199712141816.TAA29536@uriah.heep.sax.de> <86zpm3pw53.fsf@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund <perhaps@yes.no> wrote: >> Well, if you were going to spell _KERNEL correctly, by all means, go >> ahead! ;) > > Won't this break many patches people are keeping externally? FreeBSD 3.0 will break almost anything anyway, so it's a good time to do this. :) > <DIVERSION>I also dislike using structs to communicate kernel <-> > userland - e.g. for ipfw. I'd like this to use something like the > tags system on the Amiga.</DIVERSION> For ioctls, they are rather safe in the BSD model, since the struct size is crunched into the ioctl command. So if you extend a struct later, just rename the old one in the kernel header file, as well as the old ioctl cmd value, and you can easily support both in parallel. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712142209.XAA01033>