Date: Wed, 20 Jan 1999 10:58:13 -0000 From: paul@originative.co.uk To: archie@whistle.com, dfr@nlsystems.com Cc: gelderen@mediaport.org, current@FreeBSD.ORG Subject: RE: KLD naming Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FDBA@OCTOPUS>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Archie Cobbs [mailto:archie@whistle.com] > Sent: Wednesday, January 20, 1999 6:13 AM > To: dfr@nlsystems.com > Cc: gelderen@mediaport.org; current@FreeBSD.ORG > Subject: Re: KLD naming > > > Doug Rabson writes: > > > 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 > > ... > > ... > > I like this idea (subdirectories) better.. it will last longer :-) > Witness the explosion of the ports tree. > > You should then be able to load a module "isa/if_ed.ko" etc > and have it work (no leading slash). I don't think subdirectories based on bus type is a good idea, it doesn't really fit the granularity we're probably heading towards. Some thinks don't really fit at all, filesystems, screen savers etc and even for drivers we're heading towards less bus specific devices so an ethernet driver, say, would be the same for any bus, only the startup code would be different and possibly(probably) in a different module. A functional structure is probably better /modules /devices /ethernet /storage /display /network /filesystems /screensavers etc. Not a specific proposal for actual directories but perhaps a better direction. I think we should start thinking more in terms of function, rather than bus, in a lot of what we do with devices as we abstract out the bus code more effectively. Paul. 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?A6D02246E1ABD2119F5200C0F0303D10FDBA>