Date: Sat, 30 Jun 2007 00:59:08 -0500 From: "Scot Hetzel" <swhetzel@gmail.com> To: "Kostik Belousov" <kostikbel@gmail.com> Cc: ports@freebsd.org, Edwin Groothuis <edwin@mavetju.org> Subject: Re: How to get a list of all kernel modules Message-ID: <790a9fff0706292259g25d5ea1ck2b39de0acc385716@mail.gmail.com> In-Reply-To: <20070630040509.GD2268@deviant.kiev.zoral.com.ua> References: <20070617.011324.406004472.imp@bsdimp.com> <4674E05F.4060705@gmx.de> <20070617072945.GE1325@k7.mavetju> <20070617.013640.-131645657.imp@bsdimp.com> <20070618003329.GF1325@k7.mavetju> <20070625222609.GD1558@k7.mavetju> <20070630004536.GE1558@k7.mavetju> <20070630040509.GD2268@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/29/07, Kostik Belousov <kostikbel@gmail.com> wrote: > It would be very convenient to have unified location for ports kernel > modules. May be, even hier(7) compliant ? > > For instance, some random set of ports installed kernel modules to: > > sysutils/devcpu: /boot/modules/cpu.ko > net/ng_car: /boot/kernel/ng_car.ko > (this means that ng_car.ko module will be trashed on next kernel update) > audio/oss: /usr/local/lib/oss/modules > I would propose that kernel module ports should install their KLD(s)into /boot/modules, as that would allow the kernel module to be loaded without specifing a path to the module: kldload <module name> instead of: kldload /path/to/module/<module name>.ko And allow the KLD to be loaded from /boot/loader.conf. Another option would be to allow only specific types of modules to be placed into /boot/modules (network, filesystem, ...) and then have the remaining modules installed into PREFIX/libexec/kernel_modules (audio, ...). A rc script for the module would then be used to load/unload the module. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0706292259g25d5ea1ck2b39de0acc385716>