"Daniel B. Haun" wrote:
>
> Hi Michael,
>
> For us really green newbies, those that have never recompiled a kernel.
> What would be your best stepxstep? You seem to have a pretty good handle on
> this stuff....:) I have LM 7.2 installed, just the stock one, I guess.
>
> Daniel in Nj... :)
>
> On Saturday 10 February 2001 12:04, you wrote:
> > On 10 Feb 2001 05:11:13 -0800, wrote:
> > > When you re-compile you'll need to 'make mrproper' before 'make
> > > xconfig' and edit the Makefile to at least uncomment the line
> > > export INSTALL_PATH=/boot
> >
> > No, you don't have to do "make mrproper" before you re-compile a kernel.
> > This will also remove your previously chosen options, so you'll have to
> > choose them all over again.
> >
> > > > % make xconfig
> > > > and then:
> > > > % make dep
> > > > % make clean
> > > > % make bzImage
> > >
> > > you didn't do a 'make install' here
> >
> > "Make install" is not required, especially if you want to run multiple
> > versions of the kernel. All it means is that you have to do the next
> > steps (copying, symlinking, running lilo, etc) yourself.
> >
> > > > then I moved and renamed both bzImage and System.map
> > > > % mv /arch/i386/boot/bzImage /boot/vmlinuz-2.4.1
> > > > % mv System.map /boot/System.map-2.4.1
> > > > and finally deleted the existing symlinks for System.map and vmlinuz
> > > > and made new ones linked to those new files:
> > > > % rm System.map
> > > > % rm vmlinuz
> > > > % ln -s System.map-2.4.1
> > > > % ls -s vmlinuz-2.4.1 vmlinuz
> > >
> > > all that would be unnecessary. I usually clean up uneeded links
> > > and files in /boot, after I get the new kernel to boot successfully.
> >
> > Doing it this way makes it easier to run multiple versions of the
> > kernel.
> >
> > > If you need/want ramdisk support, you do need a initrd if you want a
> > > to be able to boot the kernel. 'man initrd' if so, after 'make
> > > modules_install' the next step is
> > >
> > > mkinitrd /boot/initrd-2.4.1.img 2.4.1
> >
> > I compile ramdisk support in, but do NOT do the mkinitrd command. Works
> > fine.
Mine didn't boot at all either last night when I attempted to boot from
the boot floppy after I was finished compiling. It just kept reading the
floppy and outputting to the screen. I don't even know what it was
saying...just random lines on the screen. Weirdest boot attempt I've
ever seen.
--
Mark
"If you don't share your concepts and ideals, they end up being
worthless,"
"Sharing is what makes them powerful."
