Date: Mon, 13 Oct 1997 19:06:25 +0900 From: itojun@itojun.org To: Julian Elischer <julian@whistle.com> Cc: hackers@FreeBSD.ORG Subject: Re: good name for a (in fact 2) new module(s) Message-ID: <25477.876737185@coconut.itojun.org> In-Reply-To: julian's message of Mon, 13 Oct 1997 00:32:38 MST. <Pine.BSF.3.95.971013000137.9123D-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>I have two new major kernel modules to add soon. >Part of all this is to think of good names for them before they >hit the light of day.. once they've been released, I can't easily >change the names and the CVS files will have been created etc. >They are: >A networking framework to allow the linking and operation of an arbitrary >graph (think of nodes and edges) of processing modules within the kernel. >e.g. a ppp framing modules, a frame-relay mux, a frame relay control >module, debug modules. etc. At the moment this is called "netgraph" in the >same line as netatalk, netinet, netipx, etc. This is scheduled to be made >public by whistle on Jan. 1. It kind-of fills the same ecological niche as >the sysV STREAMS, but is considerably different. I've discussed this with >many including Mike Karels. Many of you will have seen early versions of >this. Whistle's mpd (multilink PPP daemon) knows how to use this framework >to do fun things with ISDN and frame relay links etc. A bit off-topic, but I can't resist: will netinet/netatalk be heavily changed by the addition of netgraph, or they are just another (separate) protocol family? itojun
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25477.876737185>