[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
misc/38724: Kernel modules installed in inappropriate directory tree
>Synopsis: Kernel modules installed in inappropriate directory tree
>Arrival-Date: Wed May 21 20:25:00 +0000 2008
>Originator: Havard Eidnes
>Release: NetBSD-current (4.99.63 as of today)
Host System: NetBSD quattro.urc.uninett.no 3.1_STABLE NetBSD 3.1_STABLE
(QUATTRO) #1: Tue Nov 21 02:34:49 CET 2006
The new kernel modules are installed in
directory tree, i.e. below /stand/.
I claim that this is an inappropriate place to store these
files. The justification for my claim is hier(7):
/stand/ programs used in a standalone environment
I interpret this to mean that files in /stand/ are programs
suitable to be executed on the "bare metal" of the machine
(possibly in the firmware environment), but at least *not*
within an OS kernel. "stand" implies "standalone", which
again implies "no OS kernel". If I understand correctly, the
new kernel modules do not fit into this category.
Admittedly, as far as I know, we don't currently install any
such programs in /stand/, but the argument still stands.
So, what remains is to come up with a better suggestion for
the file tree to store these in.
/kernel/ Could be annoying due to tab-expansion and the
existence of /kern.
/kmod/ One possible alternative? One more entry in
the toplevel directory, though.
/lib/modules/ They're really not libraries...
I'm not married to either idea; more suggestions are welcome.
However, the abuse of /stand/ has to stop. 1/2 :-)
Inspect the result of a fresh build.
Set lists and bsd.kmodule.mk needs updating when we agree on
the new name.
Main Index |
Thread Index |