On Fri, 2008-01-25 at 13:58 -0800, Jeremy Fitzhardinge wrote: > Linus Torvalds wrote: > > On Fri, 25 Jan 2008, Jon Masters wrote: > > > >> 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) > >> > > > > No. I really am not. My /etc/grub.conf looks like this: > > > > title Linux > > root (hd0,0) > > kernel /vmlinuz ro root=/dev/VolGroup00/LogVol00 rhgb quiet > > initrd /initrd-2.6.23.14-107.fc8.img > > > > ie I literally run the fedora initrd. > > > > I switch kernels, not initrd's. I don't even want to know if the initrd > > contains some distro-specific setup... > > The distro mkinird can reconstruct it containing your freshly built > modules (if any) and any other distro goo which needs to go in there. > /initrd-2.6.23.14-107.fc8.img doesn't come out of an rpm; its built by > an installer script when you install the kernel, and you can run the > same script on your kernels. > > Does you use "make modules_install install" when you build the kernel? > It just does the right thing for me under F8, including rebuilding > initrd and updating grub.conf.
My wish is that distros would just boot without requiring an initrd. I know how to make them for redhat and debian based distros, but the fact that you can't (easily) cross-build them makes it a very tedious construct. I can butcher the distros into booting and ignore the errors on bootup that whine that modules are missing, but really. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
