Among other things, that same directory is the default location for
finding the proplist associated with the module when it is being loaded
from the filesystem.
See module_load_plist_vfs() in kern/kern_module_vfs.c ...
On Wed, 10 Aug 2011, Julio Merino wrote:
On 8/10/11 5:53 AM, Marc Balmer wrote:
Currently, we install kernel modules under the following path
/stand/<arch>/<release>/<name>/<name>.kmod
The duplication of the name probabably was meant to prevent escaping the
path when a module name like ../../../foo was given on the commandline.
IIRC, that name duplication was in the spirit of Mac OS X bundles: you have a
directory that defines the module, and inside you have the binary and
possibly any associated data files that may be required.
Have you asked the original author for his rationale? (I presume that was
ad@).
!DSPAM:4e429a292351973113738!
-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer | | pgoyette at netbsd.org |
-------------------------------------------------------------------------
