From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758838AbYEEOiq (ORCPT ); Mon, 5 May 2008 10:38:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756139AbYEEOij (ORCPT ); Mon, 5 May 2008 10:38:39 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:43933 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756016AbYEEOii (ORCPT ); Mon, 5 May 2008 10:38:38 -0400 Date: Mon, 5 May 2008 07:37:59 -0700 (PDT) From: Linus Torvalds To: Jan Engelhardt cc: Rusty Russell , linux-kernel@vger.kernel.org, Jon Masters , Sam Ravnborg Subject: Re: changeset: Make forced module loading optional In-Reply-To: Message-ID: References: <200805051455.02723.rusty@rustcorp.com.au> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 5 May 2008, Jan Engelhardt wrote: > > That's not good procedure IMO. You always want to keep a known good > (=booting) kernel, and the distro-provided one might just be that. Yes, I've always had a known-good fallback. So I actually do duplicate the lines and leave unchanged versions in /etc/grub.conf for when things go wrong. But my point is, I really want to change just the kernel. I don't want to care what the initrd does, and I don't want to build my own. It's all "user space" to me - and thus beneath my notice. And the module loading bug was just that - a kernel bug. Linus