From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OQoBl-0000Qf-Sz for garchives@archives.gentoo.org; Mon, 21 Jun 2010 21:05:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 819BEE0CD8 for ; Mon, 21 Jun 2010 21:05:53 +0000 (UTC) Received: from mail-yw0-f188.google.com (mail-yw0-f188.google.com [209.85.211.188]) by pigeon.gentoo.org (Postfix) with ESMTP id DE440E0BE1 for ; Mon, 21 Jun 2010 20:23:12 +0000 (UTC) Received: by ywh26 with SMTP id 26so2850343ywh.10 for ; Mon, 21 Jun 2010 13:23:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=YkZ9r+itGSgO7xJR5wWyNI9zogJh0lX9FTkYA2+63SY=; b=PAtKjOYjhvzPF3DJF6f8bXAOe48IbZ9Kud1ACyRiP0+KBg8n8VelsVT5WU/h9rrW0U WoB9xyjkeJxHwTrK2LuQKK13Z0mPooPA5DYlJKDMW6hlQXhIC2jkuoDhuoHxjTnlzga3 wsdOXUck9pSCWwNUATsShUOcV4ezqy9OEP5vM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=fRmaTJLN1RuRDpMF+T0hYJcZzzKLvBUr2avtIEP/OX0z1pRdFJRGhzDyijRT5SrN8E QNm/xp4R053Jv0zrir4yjorkDqPGI5kZVOEZfO0PrdZZcqn6F27IWZIFqUqtUL23eVne ogeW1E3NnUD6d8Fa18qVa6z0wCSsx7ExEAZ+8= Received: by 10.100.245.35 with SMTP id s35mr4257183anh.71.1277151792544; Mon, 21 Jun 2010 13:23:12 -0700 (PDT) Received: from [192.168.1.2] (adsl-95-107-53.jan.bellsouth.net [98.95.107.53]) by mx.google.com with ESMTPS id a10sm250846anj.19.2010.06.21.13.23.10 (version=SSLv3 cipher=RC4-MD5); Mon, 21 Jun 2010 13:23:11 -0700 (PDT) Message-ID: <4C1FCA2D.1070207@gmail.com> Date: Mon, 21 Jun 2010 15:23:09 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100616 Gentoo/2.0.4-r2 SeaMonkey/2.0.4 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 MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Boot hangs after install, no error References: <4C1958B9.4000903@gmail.com> <4C1F7817.7020208@gmail.com> <4C1FA976.4020804@gmail.com> <201006212026.54478.wonko@wonkology.org> <4C1FB70F.4090505@gmail.com> <4C1FC51E.7030003@gmail.com> In-Reply-To: <4C1FC51E.7030003@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 7ff22446-c6d0-41d1-9c6b-3dbee326ebe4 X-Archives-Hash: c45da4777d5f0c1d3864a02b89248acd Bill Longman wrote: > On 06/21/2010 12:01 PM, Dale wrote: > >> Alex Schuster wrote: >> >>> Dale writes: >>> >>> >>> >>>> I don't use genkernel anymore. I just roll my own. That way, I know >>>> what is in there and what is not. Then if something doesn't work, I >>>> know if it is the kernel or something else. With genkernel, you won't >>>> have a clue what it is since you don't know much if anything about the >>>> kernel and how it is configured. >>>> >>>> >>> That's not necessarily true. When I create a new kernel, I copy >>> /usr/src/linux/.config into the new kernel directory, make oldconfig and >>> menuconfig just as I like my kernel to be, and recreate the linux symlink >>> to the new kernel directory. Then I do a genkernel --install --lvm --luks >>> all&& emerge -a @module-rebuild, and am done. >>> I never noticed genkernel changing anything in my configuration, .config, >>> /proc/config.gz and the stuff in /etc/kernels/ are identical. Until not >>> long ago, I did not even know that genkernel was intended to create a >>> working kernel from scratch. >>> >>> Wonko >>> >>> >>> >> I always do mine this way. I copy the .config from the old kernel to >> the new kernel, run make oldconfig then afterwards make all&& make >> modules_install and then copy the kernel to /boot with my own numbering >> system. That way I know which version and series the kernel is. After >> that, edit grub with the new kernel and I'm done. I have only had that >> fail once in the past six years or so and the kernel made some serious >> changes and I had to start from scratch that one time. They moved >> things around and oldconfig couldn't reorganize things on the new kernel. >> >> Point being, genkernal causes issues for people and they don't know how >> to fix it because they expect genkernel to do everything. Problem with >> that is that usually when someone has a kernel problem, they use >> genkernel. If they do their own, it just works. Now someone new to >> building a kernel may need some help but apparently genkernel needs some >> help anyway. May as well learn how to roll your own. This is Gentoo >> after all. >> > The only thing that genkernel would add is your initrd. The kernel is > exactly the same, whether you compile it with "make" or through > "genkernel". Do a test and you'll see. (I'm assuming we're both talking > about gentoo-sources, not vanilla-sources. Either way, they'd be the > same.) Some might be confused about what happens in the steps if they > haven't been down the "kernel compilation trail" more than once or > twice, but for folks who just want to compile their kernel and plop it > into place, along with a hands-off initrd, it's rather handy. > > But only if it works. When I compile my kernel, I KNOW for sure what is in there. When genkernel does one, especially on a new install, I have no idea what is in it or what is not. If something goes wrong, I don't know where to start. Is it a kernel problem or is it something else? Who knows. Then you have to go back and start from the bottom, usually the kernel, and work your way back up to find out what is broken. Genkernel may work for you but that doesn't mean it does for everyone else. Should I mention hal here? When someone comes for help, your looking for the failure not the successes. If it was sucessful, they wouldn't need help. Dale :-) :-)