Re: [PLUG] new kernel bombs

[Kevin Brosius <kbrosius@kns.com>]

Until you're more familiar with initrd's, you're probably better off
removing the requirement for it.  Generally, it's only required when the
root fs driver is compiled as a module.  You can change the kernel
drivers for your root (and boot mounted) fs's from modules to built in,
that way you won't need an initrd.  It'll also prove whether or not the
initrd is part of the problem.

An initrd is only needed to load modules which the kernel cannot boot
without.  The root filesystem is the primary need here.  So, either
ext2, or reiserfs (etc...) needs to be built in (or in initrd) for a
successful boot.

This can be extended for less common setups.  For example if your root
filesystem is an nfs mount, you might need nfsd, ethernet, and other
supporting modules in initrd.

Kevin


"W. Chris Shank" wrote:
> 
> well, turns out i didn't have ramdisk or initrd enabled in the kernel (duh).
> but with a recompile and install, it still didn't work.
> 
> > On Tue, Jul 16, 2002 at 01:21:38PM -0600, W. Chris Shank wrote:
> >> what does make install end up doing? also, if you just type make
> >> instead of make bzIamge, what's your kernel?
> >
> > i believe 'make' does the same as make bzImage, but i could be wrong
> > there, and i think make install copies the necessary files over into
> > /boot, changes the appropriate symlinks, and does whatever it needs to
> > do with the bootloader.  funny, i don't know for certain, i've
> > always just done it that way :)
> >
> > --sean

______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug