Subject: Re: [GIT PATCH] driver core patches against 2.6.24
From: Jon Masters <jonathan@jonmasters.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, Greg KH <gregkh@suse.de>,
       Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
In-Reply-To: <479A3ED3.6020808@goop.org>
References: <20080125071127.GA4860@kroah.com>
	 <alpine.LFD.1.00.0801251035150.2979@hp.linux-foundation.org>
	 <20080125185213.GA23475@suse.de>
	 <alpine.LFD.1.00.0801251108480.2979@hp.linux-foundation.org>
	 <479A3ED3.6020808@goop.org>
Content-Type: text/plain
Organization: World Organi[sz]ation Of Broken Dreams
Date: Fri, 25 Jan 2008 16:20:27 -0500
Message-Id: <1201296027.32422.80.camel@perihelion>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1146
Lines: 26


On Fri, 2008-01-25 at 11:56 -0800, Jeremy Fitzhardinge wrote:
> Linus Torvalds wrote:
> > I'm too lazy to want to do my own initrd. I just use the prepackaged ones 
> > and rely on the fact that my private kernel will refuse to load modules 
> > that aren't meant for it anyway.

> initrds generally aren't prepackaged, but generated on install (at least 
> with Fedora).  You can regenerate them with "mkinitrd -f 
> /boot/initrd-2.6.24.img 2.6.24".  Also, I find that "make 
> modules_install install" does it automatically from a kernel build.

Right. I assumed that Linus was calling mkinitrd but was being bitten by
one of the occasional assumptions (I believe we make in that script)
that certain things are always modular. I just mailed the maintainer,
suggesting we screen against the one of the Modules.* files (perhaps
Modules.order might become a good candidate in due course...).

Jon.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/