> > 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.
TBH, unloading an idle module is basically a waste of time. Modules are,
on the whole, so small that the savings are entirely outweighed by the
unnecessary complexity.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
- Re: kerneld for FreeB... Coleman Kane
- Re: kerneld for FreeB... Alfred Perlstein
- Re: kerneld for FreeBSD Bill Fumerola
- Re: kerneld for FreeBSD Chris Costello
- RE: kerneld for FreeBSD Yevmenkin, Maksim N, CSCIO
- RE: kerneld for FreeBSD Yevmenkin, Maksim N, CSCIO
- Re: kerneld for FreeBSD Mike Smith
- Re: kerneld for FreeBSD Jeroen C. van Gelderen
- Re: kerneld for FreeBSD Mike Smith
- Re: kerneld for FreeBSD Jeroen C. van Gelderen
- Re: kerneld for FreeBSD Mike Smith
- Re: kerneld for FreeB... Jeroen C. van Gelderen
- Re: kerneld for FreeB... Bjoern Fischer
- Re: kerneld for FreeB... Matthew Dillon
- Re: kerneld for FreeB... Robert Watson
- Re: kerneld for FreeB... Daniel C. Sobral
- Re: kerneld for FreeB... Warner Losh
- Re: kerneld for FreeB... Peter Wemm
- Re: kerneld for FreeB... Warner Losh
- Re: kerneld for FreeB... Nate Williams
- Re: kerneld for FreeB... Mike Nowlin

