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
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.
Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.
If you use Debian 6 Squeeze and you are tired of looking at the childish graphical GDM login screen that is used by default, here's an easy way to change it.
If you've already tried to change it you've probably discovered that none of the old met…
Exception Handling is in the core of any application that is able to dignify its name.
In this article, I'll guide you through the process of writing a DRY (Don't Repeat Yourself) Exception Handling mechanism, using Aspect Oriented Programming.