From owner-freebsd-hackers Mon Oct 13 03:06:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA08308 for hackers-outgoing; Mon, 13 Oct 1997 03:06:58 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from coconut.itojun.org (root@coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA08297 for ; Mon, 13 Oct 1997 03:06:51 -0700 (PDT) (envelope-from itojun@itojun.org) From: itojun@itojun.org Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.5/3.6Wbeta6) with ESMTP id TAA25481; Mon, 13 Oct 1997 19:06:25 +0900 (JST) To: Julian Elischer cc: hackers@FreeBSD.ORG In-reply-to: julian's message of Mon, 13 Oct 1997 00:32:38 MST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: good name for a (in fact 2) new module(s) Date: Mon, 13 Oct 1997 19:06:25 +0900 Message-ID: <25477.876737185@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >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