Date: Wed, 20 Jan 1999 23:17:41 -0500 From: Christian Kuhtz <ck@adsu.bellsouth.com> To: "David O'Brien" <obrien@NUXI.com> Cc: current@FreeBSD.ORG Subject: Re: KLD naming Message-ID: <19990120231741.Z25047@oreo.adsu.bellsouth.com> In-Reply-To: <19990120191915.B17471@relay.nuxi.com>; from David O'Brien on Wed, Jan 20, 1999 at 07:19:15PM -0800 References: <199901202046.MAA23549@bubba.whistle.com> <199901202336.PAA04090@dingo.cdrom.com> <19990120194556.B37565@znh.org> <19990120191915.B17471@relay.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 20, 1999 at 07:19:15PM -0800, David O'Brien wrote:
[..]
> etc? This is what the original poster suggested, and nobody has really
> given a good response what is wrong with the "grouping" being expressed
> in the modules' name. Mike Smith and Andrzej Bialecki have given good
> reasons why *not* to go to a subdirectory structure.
What would you name a network stack? For example:
net_mpls_tdp.ko
net_mpls_ldp.ko
net_mpls_core.ko
or
net_h323v2_yada.ko
net_h323v2_yadayada.ko
net_h323v2_barf.ko
or
codec_g711.ko
codec_g7231a.ko
codec_g729.ko
Is that acceptable? Anyone have better ideas?
Cheers,
Chris
--
"Logic is a little bird, sitting in a tree; that smells *awful*."
-- /usr/bin/fortune
[Disclaimer: I speak for myself and my views are my own and not in any way to
be construed as the views of BellSouth Corporation. ]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990120231741.Z25047>