From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 17 22:08:04 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2C881065670 for ; Fri, 17 Feb 2012 22:08:04 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id 738F78FC08 for ; Fri, 17 Feb 2012 22:08:04 +0000 (UTC) Received: by eaan10 with SMTP id n10so1653738eaa.13 for ; Fri, 17 Feb 2012 14:08:03 -0800 (PST) Received-SPF: pass (google.com: domain of rank1seeker@gmail.com designates 10.14.127.80 as permitted sender) client-ip=10.14.127.80; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rank1seeker@gmail.com designates 10.14.127.80 as permitted sender) smtp.mail=rank1seeker@gmail.com; dkim=pass header.i=rank1seeker@gmail.com Received: from mr.google.com ([10.14.127.80]) by 10.14.127.80 with SMTP id c56mr5673584eei.13.1329516483428 (num_hops = 1); Fri, 17 Feb 2012 14:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; bh=SppfNV/6fSitZlWTiMTBSfBSdPq5mhprH8kmoBntQ6E=; b=CEZ+ZaTA9UT18pq9BWPMl77gwnP3NH5QkZ+p9F5PAhO6mUnbXFACJ2/HgMCIDI3b9G D74t8YM4eKQ0w+SCcQBDSYI5qYznYf8qWqoaceBbmSd+JpUzWdKia6RKSTJr96tW9/qk 01XqlTiSJTTitb3a0YbFxmfTqDWWthjiSOmfY= Received: by 10.14.127.80 with SMTP id c56mr4603748eei.13.1329516483377; Fri, 17 Feb 2012 14:08:03 -0800 (PST) Received: from DOMYPC ([82.193.208.173]) by mx.google.com with ESMTPS id n17sm43436872eei.3.2012.02.17.14.08.01 (version=SSLv3 cipher=OTHER); Fri, 17 Feb 2012 14:08:02 -0800 (PST) Message-ID: <20120217.220802.988.2@DOMY-PC> From: rank1seeker@gmail.com To: hackers@freebsd.org Date: Fri, 17 Feb 2012 23:08:02 +0100 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <4F3E8225.9030501@FreeBSD.org> <4F3E8C26.3080900@FreeBSD.org> <4F3EA5F2.9070804@gmail.com> <4F3EAE5F.6070903@gmail.com> X-Mailer: POP Peeper (3.8.1.0) Cc: Subject: Re: 8 to 9: Kernel modularization -- did it change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 22:08:05 -0000 > For me as a user, that would be a much preferable approach, = instilled=0D=0A> long ago by Linux. I don't like unused stuff around, and = I like to=0D=0A> understand what I am using.=0D=0A> =0D=0A> Some build = kernel confutation parameters "minimum modules", "medium=0D=0A> modules", = "maximum modules" might be utilized. I would be using=0D=0A> "medium" or = most likely "maximum", leaving me with a minimal kernel.=0D=0A> =0D=0A> = -- Alex -- alex-goncharov@comcast.net --=0D=0A=0D=0ANO.=0D=0A=0D=0A> = Thinking bigger picture (beyond sound), would it make sense to = keep=0D=0A> GENERIC very minimal, but provide an extensive loader.conf = with a=0D=0A> default install...so most things worked, but were loaded as = modules?=0D=0A> =0D=0A> Matt=0D=0A=0D=0ANO.=0D=0A=0D=0A=0D=0AYou can't = base a "wish" on a solution for YOURS problems!=0D=0A=0D=0AGENERIC must = be as giantic as possible, to make as many machines as possible to BOOT = and enable all what can be enabled in/on them.=0D=0ATHEN ... individual = "strips" unhooked parts -> custom kernel, via wich you "specialize it", = for your hardware!=0D=0A=0D=0AThat is, unless individual is passive/bored = (lazy?) and prefer everything on a silver plate ...=0D=0AThere are many = paths in that case ...=0D=0AWindows are the easiest solution. THEY THINK = FOR YOU!=0D=0A;)=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6