From owner-freebsd-current Thu Jan 21 03:14:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20506 for freebsd-current-outgoing; Thu, 21 Jan 1999 03:14:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from octopus.originative.co.uk (originat.demon.co.uk [158.152.220.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20492 for ; Thu, 21 Jan 1999 03:14:07 -0800 (PST) (envelope-from paul@originative.co.uk) From: paul@originative.co.uk Received: by OCTOPUS with Internet Mail Service (5.5.1960.3) id ; Thu, 21 Jan 1999 11:12:31 -0000 Message-ID: To: julian@whistle.com, mike@smith.net.au Cc: ck@adsu.bellsouth.com, obrien@NUXI.com, current@FreeBSD.ORG Subject: RE: KLD naming Date: Thu, 21 Jan 1999 11:12:27 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Julian Elischer [mailto:julian@whistle.com] > Sent: Thursday, January 21, 1999 7:58 AM > To: Mike Smith > Cc: Christian Kuhtz; David O'Brien; current@FreeBSD.ORG > Subject: Re: KLD naming > > > well you're about to get your first test.... > we are releasing the netgrpah code in full production form tonigh (if > the version we've put together for release passes all tests tonight) > The whole thing installs as KLD modules (or linked in of course) > > our present names are all predicated with ng_ > hence ng_socket ng_rfc1490, ng_frame_relay etc > the base module is 'netgraph'. > > now what would you suggest? > we can still cahnge it before we release and no-body knows > any better but > after is always harder to change than beefore.. Why not have a third party identifier on the front, e.g. whistle_ng_rfc1490 You can determine your own naming scheme then and if we make this standard then it will ensure that third party supplied modules don't result in name space conflicts. It's perfectly feasible in the future that different companies might produce competing modules for subsystems, sound for example, so we might as well deal with this possibility now. Makes it easier to identify the source of the modules as well. Perhaps we should adopt a FreeBSD prefix on core modules so you can see from ls what's part of the OS and what's been added in from elsewhere. Although I'm in favour of this naming scheme over directories you can reach the point where the names are holding too much metainformation that really should be directory structure. There wouldn't be need for directories at all if you put the structure in the filename :-) Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message