From owner-freebsd-hackers Thu Jun 8 0:44:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 04BCB37BAEB for ; Thu, 8 Jun 2000 00:44:35 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA18724; Thu, 8 Jun 2000 03:43:38 -0400 Date: Thu, 8 Jun 2000 03:43:38 -0400 (EDT) From: Mike Nowlin To: Matthew Dillon Cc: Bjoern Fischer , hackers@FreeBSD.ORG Subject: Re: kerneld for FreeBSD In-Reply-To: <200006070728.AAA97354@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. > Not to mention "how much memory do you really gain by unloading modules"? Considering the price of RAM these days (although not as low as it was, but I won't be spending $650 US for 16M any time soon again), the few K that unloading a bunch of modules saves won't EVER really be noticed by the 83Tb chunk that Nutscrape allocates. Excuse me, I must now think back to the dumbness achieved by people re-compiling Linux completely statically in hopes that it'll speed up their systems by not dynamically loading the libraries.... These were the same guys who wanted to unload modules to save kernel RAM... --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message