From owner-freebsd-hackers  Mon Oct 13 02:41:49 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id CAA06769
          for hackers-outgoing; Mon, 13 Oct 1997 02:41:49 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA06764
          for <hackers@freebsd.org>; Mon, 13 Oct 1997 02:41:44 -0700 (PDT)
          (envelope-from mike@word.smith.net.au)
Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1])
	by word.smith.net.au (8.8.7/8.8.5) with ESMTP id TAA01200;
	Mon, 13 Oct 1997 19:08:50 +0930 (CST)
Message-Id: <199710130938.TAA01200@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Julian Elischer <julian@whistle.com>
cc: hackers@freebsd.org
Subject: Re: good name for a (in fact 2) new module(s) 
In-reply-to: Your message of "Mon, 13 Oct 1997 00:32:38 MST."
             <Pine.BSF.3.95.971013000137.9123D-100000@current1.whistle.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 13 Oct 1997 19:08:46 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> A networking framework to allow the linking and operation of an arbitrary
> graph (think of nodes and edges) of processing modules within the kernel.

"PLGS" (think plugs & sockets, or Pluggable Link Grouping System.
Or maybe "tubes" (for the oldies) for Transport Unification Block 
Extension Scheme.

> The second module is a disk layering framework that works in conjunction
> with DEVFS. 

How about "DSTAC" for Direct STorage ACcumulation?

Apologies for the synthetic acronyms. 8)

> The present name for this module is the SLICE module, but I'm not sure
> that this is generic enough. I've been thinking of DASD (IBM's name for
> disk (Direct Access Storage Device) or DAS (similar). I'd have to do some
> 'bulk find and replace' operations but I'd rather do it now than later.

DASD would be OK as long as the legacy attachments weren't seen as a 
problem; you're reusing an older term for something quite different and 
will undoubtably confuse some people.

> Any thoughts about these names would be gratefully appreciated..
> failing violent objections, we might look forward to seeing a
> /sys/dev/slice or /sys/dev/das (no, not DAAS for those .au members).

Damn.  I was going to suggest that you could call the network module
"Gough".  (Heh, figure _that_ one out...)

mike