From owner-freebsd-current Tue Jan 19 11:58:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00461 for freebsd-current-outgoing; Tue, 19 Jan 1999 11:58:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00441 for ; Tue, 19 Jan 1999 11:58:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id TAA47674; Tue, 19 Jan 1999 19:59:16 GMT Date: Tue, 19 Jan 1999 19:59:16 +0000 (GMT) From: Doug Rabson To: "Jeroen C. van Gelderen" cc: current@FreeBSD.ORG Subject: Re: KLD naming In-Reply-To: <011b01be43a1$323851e0$0d79eb0a@deskfix.local> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Jan 1999, Jeroen C. van Gelderen wrote: > Hi, > > Might it be a good idea to choose a consistent naming scheme for the > modules? I'd think so because it would help blind loading at the boot > prompt. If you choose names it the following format: > > type_name > saver_warp > saver_daemon > > the modules of one type will sort together in a directory listing. This is a > change that will make FreeBSD more user friendly I think. When I first started writing KLD, I had a vague notion that there would be a simple directory structure under /modules, e.g.: /modules pci/ ncr.ko ... isa/ if_ed.ko ... ... Including the type in the filename instead might be a better idea though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message