I personally consider leaving the kernel module loadable intact after boot to be a huge, huge security hole. Loadable modules... fine, but once the machine goes multi-user I want to up the securelevel and that disables any further kld operations. If one of the biggest advantages of FreeBSD is its robustness and reliability, then one generally does not want to go loading and unloading modules all the time. A 'kerneld' like gizmo for FreeBSD would be a waste of time. The scheme we have now -- having the utility programs load the modules on the fly (ifconfig, vnconfig, etc...) works wonderfully. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- 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
- Re: kerneld for FreeB... Julian Elischer
- Re: kerneld for FreeB... Mike Smith
- Re: kerneld for FreeB... Coleman Kane