Mike Smith <[EMAIL PROTECTED]> writes:
> > Terry Lambert <[EMAIL PROTECTED]> writes:
> > > There is so much "goo" around the module loading these days; there
> > > are incursions into "mount" and all sorts of other programs that
> > > should not know about module loading.
> >
> > The kldload(2) interface alone is enough to make me cringe. The way
> > in which it locates a module to load appears to be black magic.
>
> What part of searching a path for a matching file is "black magic"?
>
> Shells have been doing this for decades...
%%%
/*
* Load /boot/kernel/procfs.ko
* XXX: why does this work?
*/
chdir("/");
kldload("procfs");
/*
* Load /boot/kernel/procfs.ko
* XXX: why does this work?
*/
chdir("/");
kldload("procfs.ko");
/*
* Load /boot/kernel/procfs.ko
*/
kldload("/boot/kernel/procfs.ko"); /* Proper interface */
/*
* Move procfs.ko from /boot/kernel to /tmp, then load the copy in /tmp.
*/
system("/bin/mv /boot/kernel/procfs.ko /tmp");
chdir("/tmp");
kldload("procfs.ko"); /* XXX: this doesn't work. */
%%%
If that's not black magic, I'd like to know what is. I'd like to
refer you to the kldload(2) manual, but unfortunately it doesn't
document how kldload(2) works. :(
Best regards,
Mike Barcroft
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
