Mike Smith wrote:
>
> > > and if a module wants to unload itself due to
> > > "unuse", it can already do so.
> >
> > You wouldn't have control over that process if the modules decides
> > for itself. It's a sysadmin decision to unload modules, not the
> > module's decision.
>
> So why introduce a third party? ("kerneld") If the admin wants to
> remove a module, great.
That was the point I was trying to make. If the admin wants to
remove modules manually he can do so. If he wants to have it
happen periodically he can set up a cron job to do it. You would
just need to add an option to kldunload that unloads all unused
modules. You didn't read very well, I never promoted "kerneld".
This last comment referred to
> and if a module wants to unload itself due to
> "unuse", it can already do so.
because modules should not unload themselves, it's up to the
admin to decide.
Cheers,
Jeroen
--
Jeroen C. van Gelderen o _ _ _
[EMAIL PROTECTED] _o /\_ _ \\o (_)\__/o (_)
_< \_ _>(_) (_)/<_ \_| \ _|/' \/
(_)>(_) (_) (_) (_) (_)' _\o_
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
