[TriLUG] kernel customizing question

[gregbrown at mindspring.com]

Okay.  I have one question left.  Where does the new .img file come from?  The
only thing I've copied so far is copy bzImage to my new kernel name in /boot. 
At which point is the new .img file created in boot and where did it come
from?  

Thanks to everyone for the help with this.

Greg

On Sun, 17 Nov 2002 20:40:17 -0500 Dan Chen <crimsun at email.unc.edu> wrote:

> [Sorry for the awful formatting, I'm having a
> heck of a time hopping
> between imap accounts :(]
> 
> On Sun, 17 Nov 2002 19:58:14 -0500,
> gregbrown at mindspring.com wrote:
> >Howdy all.  I have a quick question for you. 
> I have compiled a custom
> >kernel using the steps outlined on this
> website:
> >http://www.rhce2b.com/kernel.shtml
> >
> >Essentially, they are:
> >cd /usr/src/linux-2.4
> >(as root)
> >mkproper
> 
> (I think you meant 'make mrproper' ?)
> 
> >make oldconfig
> 
> I didn't see you mention copying an old .config
> over, so I'm not sure
> what this is for...
> 
> Btw, if you copy .config over and run either
> 'make menuconfig' or 'make
> xconfig', it's not necessary to run 'make
> oldconfig' first.
> 
> >make xconfig
> >(change some options)
> >(save changes)
> >make dep
> >make clean
> 
> ('make clean' isn't necessary here)
> 
> >edit makefile (added custom-greg to file name)
> 
> You mean to EXTRAVERSION? If you do that, then
> you should rerun 'make
> clean && make dep' before doing this next
> step...
> 
> >make bzImage
> >make modules
> >make modules_install
> >cp /usr/src/linux-2.4/arch/i386/boot/bzImage
> /boot/vmlinuz-2.4.18-3custom-greg
> >
> >I then changed the the /etc/lilo.conf file to
> reflect the changes
> >
> >prompt
> >timeout=50
> >default=linux
> >boot=/dev/hda
> >map=/boot/map
> >install=/boot/boot.b
> >message=/boot/message
> >linear
> >
> >image=/boot/vmlinuz-2.4.18-3custom-greg
> >        label=linux-2.4.18-3custom-greg
> >       
> initrd=/boot/initrd-2.4.18-3custom-greg.img
> >        read-only
> >        root=/dev/hda3
> >
> >So, after all this I reboot by doing a init 0
> then powering back up.
> 
> You don't seem to have rerun the mkinitrd
> command (not sure of the
> specific syntax, I don't use it myself...)
> 
> Also, did you rerun '/sbin/lilo -v' as the last
> step before you
> rebooted?
> 
> >uname -a shows the following:
> >Linux paloverde 2.4.18-3 #1 Thu Apr 18
> 07:32:41 EDT 2002 i686 unknown
> >
> >Bummer.  Didn't work.  If I look in /boot
> vmlinuz is still linked to the
> >old kernel.  The page at RHCE didn't say
> anything about linking up vmlinuz
> >to the new kernel though.
> 
> Sounds like the /sbin/lilo issue I (and others)
> have mentioned...
> 
> Take care,
> -Dan
> 
> -- 
> Dan Chen                 crimsun at email.unc.edu
> GPG key:   www.unc.edu/~crimsun/pubkey.gpg.asc
>