From owner-freebsd-stable@FreeBSD.ORG Sat Feb 11 08:41:06 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 760E2106564A for ; Sat, 11 Feb 2012 08:41:06 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 5304C8FC13 for ; Sat, 11 Feb 2012 08:41:06 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id q1B8f5fM056262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 11 Feb 2012 00:41:05 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id q1B8f5Ve056261; Sat, 11 Feb 2012 00:41:05 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA08891; Sat, 11 Feb 12 00:34:09 PST Date: Sat, 11 Feb 2012 07:33:08 -0800 From: perryh@pluto.rain.com To: bzeeb-lists@lists.zabbadoz.net Message-Id: <4f368a34.rIGc5BVL5Vu8OIjl%perryh@pluto.rain.com> References: <20120210145604.Horde.ewjpSpjmRSRPNSH0YRHxgAk@webmail.leidinger.net> <5B8B698D-6DC0-4334-8617-4EDEC7973D9D@lists.zabbadoz.net> In-Reply-To: <5B8B698D-6DC0-4334-8617-4EDEC7973D9D@lists.zabbadoz.net> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Alexander@Leidinger.net, stable@freebsd.org Subject: Re: Reducing the need to compile a custom kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2012 08:41:06 -0000 "Bjoern A. Zeeb" wrote: > various parts of the network stack being loadable, which is not > as easy as it sounds, especially making them unloadable again > currently ... Seems to me unloadability does not matter to the case under discussion, which is modularizing the kernel to reduce the number of cases in which a custom kernel is needed. How much real functional difference is there between "built in" and "loaded permanently at boot"?