> 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. This is great for your multi-user desktop/workstation systems, but it kind of really sucks for my laptop, which has device drivers coming/going on a regular basis as I insert/remove cards on the fly. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- 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
- Re: kerneld for FreeB... Wes Peters
- Re: kerneld for FreeB... Nate Williams
- Re: kerneld for FreeB... Mike Smith
- RE: kerneld for FreeBSD Yevmenkin, Maksim N, CSCIO
- RE: kerneld for FreeBSD Yevmenkin, Maksim N, CSCIO
- RE: kerneld for FreeBSD Yevmenkin, Maksim N, CSCIO