Date: Thu, 16 Oct 1997 22:40:46 +1000 (EST) From: Darren Reed <darrenr@cyber.com.au> To: julian@whistle.com (Julian Elischer) Cc: hackers@freebsd.org Subject: Re: Freebsd 3.0 current fails ipfilter 3.2b8 build (fwd) Message-ID: <199710161240.WAA00879@plum.cyber.com.au> In-Reply-To: <Pine.BSF.3.95.971015233553.12735A-100000@current1.whistle.com> from "Julian Elischer" at Oct 15, 97 11:37:25 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In some mail I received from Julian Elischer, sie wrote > > > > On Thu, 16 Oct 1997, Darren Reed wrote: > > > In some mail I received from Julian Elischer, sie wrote > > > > > > All the "_var.h" files contain variables who'se scope is within the > > > kernel only. > > > > Yup, I think that's a reasonable approach to take. > > > But these are structures that are not exported, and > which ARE changing. I don't see that as a reason for moving it into if_var.h > > I don't think it should extend, however, to structure definitions. > > > > > The only exception is LKMs which should define KERNEL. > > > I don't know who did this, (I see in the logs it was garrett) > > > but the idea is simply to make it more obvios when you are > > > doing the WRONG thing > > > and including kernel private variables (that are subject to change, > > > and not part of the API) . > > > > There is an API ? > What do you want that struct for? well, ifconfig, netstat, etc. all need it. if you're writing your own LKM for a network driver, you need it. if you're writing firewalling packet filtering code, you need it. "struct ifnet" is used in _lots_ of places. if you want to simulate kernel code, then you also need it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710161240.WAA00879>