From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 17 21:00:46 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F104106564A for ; Fri, 17 Feb 2012 21:00:46 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 2F2108FC12 for ; Fri, 17 Feb 2012 21:00:45 +0000 (UTC) Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta07.westchester.pa.mail.comcast.net with comcast id b8xW1i00527AodY5790lk5; Fri, 17 Feb 2012 21:00:45 +0000 Received: from hans3 ([66.30.197.229]) by omta19.westchester.pa.mail.comcast.net with comcast id b90l1i00F4xSlmi3f90lT3; Fri, 17 Feb 2012 21:00:45 +0000 Received: from algo by hans3 with local (Exim 4.77 (FreeBSD)) (envelope-from ) id 1RyUv6-000J5e-0E; Fri, 17 Feb 2012 16:00:44 -0500 From: Alex Goncharov To: matt In-reply-to: <4F3EAE5F.6070903@gmail.com> (message from matt on Fri, 17 Feb 2012 11:45:35 -0800) References: <4F3E8225.9030501@FreeBSD.org> <4F3E8C26.3080900@FreeBSD.org> <4F3EA5F2.9070804@gmail.com> <4F3EAE5F.6070903@gmail.com> Message-Id: Sender: Alex Goncharov Date: Fri, 17 Feb 2012 16:00:44 -0500 Cc: freebsd-hackers@freebsd.org, mav@FreeBSD.org Subject: Re: 8 to 9: Kernel modularization -- did it change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2012 21:00:46 -0000 ,--- You/matt (Fri, 17 Feb 2012 11:45:35 -0800) ----* | Given that there's apparently little penalty for module vs. kernel, | I can see not including it by default in GENERIC. I do have a | laptop that won't make console tones unless snd_hda is NOT loaded, | which is odd, but never worth debugging. | | Thinking bigger picture (beyond sound), would it make sense to keep | GENERIC very minimal, but provide an extensive loader.conf with a | default install...so most things worked, but were loaded as modules? For me as a user, that would be a much preferable approach, instilled long ago by Linux. I don't like unused stuff around, and I like to understand what I am using. Some build kernel confutation parameters "minimum modules", "medium modules", "maximum modules" might be utilized. I would be using "medium" or most likely "maximum", leaving me with a minimal kernel. -- Alex -- alex-goncharov@comcast.net --