Date: Sun, 19 Oct 1997 15:48:32 +1000 (EST) From: Darren Reed <darrenr@cyber.com.au> To: tlambert@primenet.com (Terry Lambert) Cc: hackers@FreeBSD.ORG Subject: Re: Freebsd 3.0 current fails ipfilter 3.2b8 build (fwd) Message-ID: <199710190548.PAA19493@plum.cyber.com.au> In-Reply-To: <199710180147.SAA15414@usr06.primenet.com> from "Terry Lambert" at Oct 18, 97 01:47:39 am
next in thread | previous in thread | raw e-mail | index | archive | help
In some mail I received from Terry Lambert, sie wrote > > > > > 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. > > If it's used lots of places, then the API is bad. Kernel internals > should not be treated as API. > > I count your build failures as *good* things. For FreeBSD specific > code, it means I can do a grep for an _var,h file, and end up with > a list of what I need to rebuild. That is a wonderful thing. What if I mention this: I was using "struct ifnet" _WITHOUT_ wanting to look at kernel memory. Why would you want to do that, you ask. So you can more easily build userland code which interfaces with the code used in the kernel and test it that way. Darren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710190548.PAA19493>