Jesse, Thanks for the help. I tried this over the weekend and amazingly enough it works great. I was seriously expecting some kind of boot error by leaving that initrd line out. I will note however, RH7.x used a root=/dev/<partition> notation for it's Lilo/Grub config files. RH8 seems to have moved to a root=LABEL=/ notation which might be the cause of the initial ramdisk showing up during the kernel build. The kernel I built for some reason doesn't understand the newer notation, but changing it back to the old form makes the kernel boot perfectly. ------------------------------------------------------------------ Mark Hoover District Network Engineer Norfolk Public Schools 628-3810 x3045 >>> psyche-list-request@redhat.com 02/07/03 02:52PM >>> Message: 5 From: Jesse Keating <hosting@j2solutions.net> Organization: j2Solutions To: psyche-list@redhat.com Subject: Re: Kernel Compile Question Date: Fri, 7 Feb 2003 10:06:13 -0800 Reply-To: psyche-list@redhat.com On Friday 07 February 2003 09:58, Mark Hoover wrote: > I recently installed RH8 on a 486 system that I want to use as a > gateway/router machine. When I compile the 2.4.20 kernel, I for some > reason end up with a initrd-2.4.20.img file. I specifically told > menuconfig that I did *not* want to use a ramdisk as I don't compile > anything as a module, I have the whole kernel configured to build > everything into the kernel. > > If I take the same config file and move it to a Pentium 100 with 48MB ram, > it'll compile without this initial ramdisk. The "make install" section may hit mkinitrd. Try booting w/out the initrd, will it boot? If so, just rm it. -- Jesse Keating RHCE MCSE For Web Services and Linux Consulting, Visit --> j2Solutions.net Mondo DevTeam (www.mondorescue.org) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
