From owner-freebsd-hackers Sat Oct 18 22:49:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA23285 for hackers-outgoing; Sat, 18 Oct 1997 22:49:13 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from plum.cyber.com.au (plum.cyber.com.au [203.7.155.24]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id WAA23280 for ; Sat, 18 Oct 1997 22:49:08 -0700 (PDT) (envelope-from darrenr@cyber.com.au) Received: (from darrenr@localhost) by plum.cyber.com.au (8.6.12/8.6.6) id PAA19493; Sun, 19 Oct 1997 15:48:32 +1000 From: Darren Reed Message-Id: <199710190548.PAA19493@plum.cyber.com.au> Subject: Re: Freebsd 3.0 current fails ipfilter 3.2b8 build (fwd) To: tlambert@primenet.com (Terry Lambert) Date: Sun, 19 Oct 1997 15:48:32 +1000 (EST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199710180147.SAA15414@usr06.primenet.com> from "Terry Lambert" at Oct 18, 97 01:47:39 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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