From owner-freebsd-net  Sat Apr 22 23:30: 4 2000
Delivered-To: freebsd-net@freebsd.org
Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43])
	by hub.freebsd.org (Postfix) with ESMTP id EBB7B37B631
	for <net@freebsd.org>; Sat, 22 Apr 2000 23:30:00 -0700 (PDT)
	(envelope-from nnd@wint.itfs.nsk.su)
Received: (from nnd@localhost)
	by wint.itfs.nsk.su (8.9.3/8.9.3) id NAA70599;
	Sun, 23 Apr 2000 13:29:57 +0700 (NOVST)
	(envelope-from nnd)
Date: Sun, 23 Apr 2000 13:29:57 +0700 (NOVST)
Message-Id: <200004230629.NAA70599@wint.itfs.nsk.su>
From: Nickolay Dudorov <nnd@mail.nsk.ru>
To: net@freebsd.org
Subject: Re: NETGRAPH in GENERIC?
In-Reply-To: <200004230144.SAA17203@bubba.whistle.com>
User-Agent: tin/1.4.2-20000123 ("Polish") (UNIX) (FreeBSD/5.0-CURRENT (i386))
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In <200004230144.SAA17203@bubba.whistle.com> Archie Cobbs <archie@whistle.com> wrote:
> There are two possible resolutions to this situation..
> 
> 1. Extract the netgraph code out of net/if_ethersubr.c and build a
>    separate ng_ether.ko netgraph KLD.  Add hooks in net/if_ethersubr.c
>    to call the netgraph stuff through function pointers that get
>    set by the KLD when it loads.. similar to the way ipfw.ko works.
> 
> 2. Always compile the base netgraph.ko module into the kernel
> 
> Option #1 would be best because option #2, even though the base
> netgraph code is small, would be bad for things like PicoBSD.
> Maybe I'll work on #1.. it shouldn't be too hard.

	It seems to me that the best solution will be #2 plus
kernel config option to DISABLE compiling netgraph in.

	N.Dudorov 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message