From owner-freebsd-current@FreeBSD.ORG Mon Jan 19 10:16:51 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6390B1065673 for ; Mon, 19 Jan 2009 10:16:51 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (hercules.mthelicon.com [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2AB9D8FC12 for ; Mon, 19 Jan 2009 10:16:51 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from PegaPegII (93-152-14-233.daisydsl.managedbroadband.co.uk [93.152.14.233]) (authenticated bits=0) by hercules.mthelicon.com (8.14.3/8.14.3) with ESMTP id n0JAGmWL060486; Mon, 19 Jan 2009 10:16:49 GMT (envelope-from ken@mthelicon.com) Message-ID: <70F6CB3B39D847A2B684D2EE9F5BDF3F@PegaPegII> From: "Pegasus Mc Cleaft" To: "Scot Hetzel" References: <15305.1232357842@critter.freebsd.dk> In-Reply-To: <15305.1232357842@critter.freebsd.dk> Date: Mon, 19 Jan 2009 10:16:48 -0000 Organization: Feathers MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6001.18000 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 X-Antivirus: avast! (VPS 090118-0, 18/01/2009), Outbound message X-Antivirus-Status: Clean Cc: Erich Dollansky , current@freebsd.org Subject: Re: NTFS in GENERIC: opt-in or opt-out? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pegasus Mc Cleaft List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2009 10:16:51 -0000 From: "Poul-Henning Kamp" > In message <790a9fff0901190108r4eb3232bqfc6a0c8af8cd7c71@mail.gmail.com>, > Scot > Hetzel writes: >>On Mon, Jan 19, 2009 at 2:35 AM, Maxim Sobolev >>wrote: >>> Erich Dollansky wrote: > >>> Any particular reason why not? Memory is cheap, 100-200KB of extra >>> kernel >>> code doesn't really matter today, while NTFS is probably the most >>> widespread >>> filesystem after MSDOS. Therefore supporting it in the GENERIC out of >>> the >>> box even in the read-only mode (our NTFS driver is read-only AFAIK) >>> could >>> benefit many users. > >>Since a buildkernel will install the ntfs.ko kernel module by default, >>their is no need to have the NTFS filesystem complied into GENERIC. > > Seconded, we should move towards a mode modular kernel, not less. What about making MINIMAL, TYPICAL, and KITCHENSINK kernel config file? To be honest, I dont know of a single machine that I have setup that actually runs on the generic kernel for any length of time aside from installing. If I had my drothers, I would like the generic kernel to be as fully packed as possible because I tend to use the probe messages on boot as a guide-line for what things I will keep from the generic config. I tend to copy the generic config and then start hacking it up from there. That said, NTFS is something I would not use during the install but for those users that do run there machine off the GENERIC kernel gotten through whatever way they installed, it may prove to be a bit annoying to not have all the bells and whistles in by default. Peg