From owner-freebsd-questions@FreeBSD.ORG Sat Dec 7 05:55:55 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86E46AC0 for ; Sat, 7 Dec 2013 05:55:55 +0000 (UTC) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by mx1.freebsd.org (Postfix) with ESMTP id 0B03114FF for ; Sat, 7 Dec 2013 05:55:54 +0000 (UTC) Received: from ppp121-45-108-103.lns20.adl6.internode.on.net (HELO leader.local) ([121.45.108.103]) by ipmail06.adl2.internode.on.net with ESMTP; 07 Dec 2013 16:25:53 +1030 Message-ID: <52A2B867.50102@ShaneWare.Biz> Date: Sat, 07 Dec 2013 16:25:51 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "firmdog@gmail.com" , Fleuriot Damien Subject: Re: do I have to compile a new kernel? or just add options somehow? References: <1A249B2C-B341-4270-B343-627901FD9562@my.gd> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Dec 2013 05:55:55 -0000 On 06/12/2013 07:11, firmdog@gmail.com wrote: > I ran #kldload crypto. Did you see that? Then I ran kldstat and it > shows the module loaded. > > Why do I have to recompile the kernel if I can run kldload or use > loader.conf to load the module at boot time? > The various kernel modules can either be compiled into the kernel or loaded dynamically. There may be one or two exceptions that only work compiled in and some devices are obviously needed to boot the system. The modules that aren't compiled into the kernel will be available as loadable modules. An option compiled into the kernel is permanently available, consuming ram etc. A loadable module can be unloaded if not in use. The main reason for configuring and building your own kernel has been to remove things you don't want, therefore reducing minimum ram usage - less important for current systems with plenty of ram. You can configure the crypto module to be automatically loaded during startup by adding crypto_load="YES" to /boot/loader.conf