What I meant by 'put your kernel where you want it' would be copying the
compiled kernel to the location of choice. In my case, that would be
/boot/vmlinuz-x.x.x-x... Where the x's are the various digits of the
kernel rev and patch rev.
'mkinitrd' is a little program/script that creates loop back files system
(a file with a filesystem layout within)... generally ext2 format. In
this file (called an Initial Ramdisk, hence initrd), we have a mini-root.
This mini-root will contain kernel modules necessary to later reach the
real root filesystem that may be on an FS or hardware requiring such
modules. ReiserFS and SCSI modules are commonly placed in initrd images
for such reasons. Once the script has created the loopback filesystem,
populated it with modules and a mini-root with /etc/modules.conf and the
like, it unmounts it and gzip's it. Your boot loader tells the kernel
where to find it by appending 'initrd=path' to kernel's invocation.
Clear as mud now? :)
*Brandon
On Mon, 18 Jun 2001, bananachunks wrote:
> 2 tiny questions, as long as the help is being offered =D
>
> What do you mean by "put your kernel where you want it..."?
> >From the man pages, and the web, I've still not been able to figure out the
> whole "mkinitrd" deal...?
>
> TIA
> geo
>
> On Sunday 17 June 2001 23:03, you wrote:
> > Congrats! For future reference, the way to make sure your kernel
> > compile is as clean as possible, do:
> >
> > make mrproper
> > make config (or xconfig, or menuconfig)
> > make dep
> > make clean
> > make bzImage
> > make modules
> >
> > put your kernel where you want it...
> > make modules_install
> >
> > If necessary, make your initial ramdisk (mkinitrd)...
> > edit your bootloader config file (lilo.conf for lilo -- menu.lst for grub)
> > install the bootloader ('lilo' or 'sh install.sh' for grub)
> >
> > Be aware that if you want to save your previous kernel selections from
> > the 'make config' stage... You need to have a backup copy. 'make
> > menuconfig or xconfig' give you an option to save to an alternate file,
> > very handy. This is because 'make mrproper' wipes the config file
> > normaly generated by the config stages.
> >
> > *TheDarb
> >
> > Joe Menola wrote:
> > > FYI...
> > > After printing the section on patching the kernel from Win4Lin's user
> > > manual and reading very carefully, I discovered what I hoped I was doing
> > > wrong. The instructions call for a "make clean" after "make dep" and
> > > before "make bzImage". I had never read that far because I've compiled
> > > the kernel many times before. This is the first I've read of doing the
> > > extra "make clean". The patched kernel compiled like a charm.
> > > My apologies for b*tching about the patch go out to Netraverse. I should
> > > have read more carefully.
> > >
> > > -jm
> > >
> > >
> > > _______________________________________________
> > > Win4Lin-users mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.netraverse.com/mailman/listinfo/win4lin-users
> >
> > _______________________________________________
> > Win4Lin-users mailing list
> > [EMAIL PROTECTED]
> > https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
> _______________________________________________
> Win4Lin-users mailing list
> [EMAIL PROTECTED]
> https://lists.netraverse.com/mailman/listinfo/win4lin-users
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
