kernel compilation

i went through an article about creating a floppy version of linux. it was  somthing that i was looking for . i have  a few doubts before i try that out . i have already a runnig version of slackware version 2.0.X and i had once compiled the kernel for including sound support . so after such a compile , i already have zimage or vmlinuz in that particular directory..

my doubht is now if i compile  wont i lose the earleir one
my questions are :
1. can i keep compling and make different kernels .. and keep it in a personal directory
2. and where should i put the kernel i need to use then ..

after the make config ...etc steps  we would end up with an image in /usr/src/linux/arch/i386/boot right ? i.e repeatedly can i make different kernels and move them from /usr/src/linux/arch/i386/boot  to a private directory and use them when i need by moving them back to /usr/src/linux/arch/i386/boot  at my own will ?

or does compling the source code of kernel not only leave us with a new kernel but also change all our OS settings ?

in a nut shell what all factors come into play when one compiles a new kernel .. is it just the compiler that compiles a big c program giving us an executable which we need to put in the root directory or boot floopy

please , would love toget a clear picture before i venture out . please dont direct me to read some HOWTO . they are really dull
Who is Participating?

Improve company productivity with a Business Account.Sign Up

swwelshConnect With a Mentor Commented:
Yes, you can have as many kernels as you want. Usually the active kernel image is moved to /vmlinuz after a compile so the next compile doesn't trash a good kernel, but you can put them anywhere you want. Just add a section to your lilo.conf file referring to the new kernel, then you can use it when the lilo prompt comes up by hitting shift-tab. This will list all the bootable files in lilo.conf. Remember to rerun lilo after every change to lilo.conf. I usually just move the kernels to / and rename them to oldkernel, scsikernel, or whatever you like. Use dd if=/oldkernel of=/dev/fd0 to make boot disks.

As far as making a floppy version of linux, I have heare there are such things, but you can do most of the same things with a boot/root disk combo. Look on your slakware cdrom for the rescue floppy image. This has a copy of vi on the root disk so you can mount your filesystem and make changes to configuration files
rajkinAuthor Commented:
thank you, before i accept your answer i would appreciate if you could give me some commands to make boot disks from linux env etc . i always fail to copy images to floppy disks after compilation. rawwrite works only for dos right ..
in linux i tried
mcopy  zimage a:\
cp zimage /dev/fd0     never works

the only command that worked was
make zdisk

what are the other commands to copy a bootableimage to the disk  ?

hope to receive an answer soon

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.