From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 51487138350 for ; Thu, 23 Apr 2020 19:46:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AFF57E0A5C; Thu, 23 Apr 2020 19:46:49 +0000 (UTC) Received: from mta2.recol.net (mta2.recol.net [64.207.103.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 59C26E09D4 for ; Thu, 23 Apr 2020 19:46:49 +0000 (UTC) Received: from wrkhors.com (99-105-125-193.uvs.stlsmo.sbcglobal.net [99.105.125.193]) by mta2.recol.net (Postfix) with ESMTPSA id 625B4399321; Thu, 23 Apr 2020 15:46:48 -0400 (EDT) Date: Thu, 23 Apr 2020 14:46:45 -0500 From: Steven Lembark To: gentoo-user@lists.gentoo.org Cc: lembark@wrkhors.com Subject: Re: [gentoo-user] Is Gentoo dead? Message-ID: <20200423144645.1ced910f.lembark@wrkhors.com> In-Reply-To: <20200421183317.GC187193@redacted> References: <20200421165803.GB187193@redacted> <20200421183317.GC187193@redacted> Organization: Workhorse Computing X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; x86_64-pc-linux-gnu) X-Workhorse: Quite Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 8f9bb477-76e4-4ebb-8155-b3b9198cbc45 X-Archives-Hash: ff76e77b1bfb9b4a4124372708a1efb0 > Still you have to manually configure things. And I know that Gentoo is > about choice, but configuring kernel is hard. Actually, it's less difficult than finding out half-way through a three-day execution cycle that you have the wrong kernel config. "make menuconfig" is blindingly simple on its own. Discovering which hardware your machine actally has is difficult, which drivers are appropriate can be a True Pain (tm); but actually configuring the kernel is blindingly easy -- if admittedly rahter boring [I've found a moderate quantity of decent beer helps the process along quite nicely]. Q: What is it about configuring a kernel that you are finding most difficult? I may be able to provide some poitners to simplify it. -- Steven Lembark 5725 Aylesboro Ave Workhorse Computing Pittsburgh PA 15217 lembark@wrkhors.com +1 888 359 3508