According to James Howles: While burning my CPU.
>
> Hi,
> I went to my /usr/src/linux-2.0.32 directory and did a make config, make
> dep, make clean, and make zImage. I added 2 other stanzas to lilo for the 2
> newly recompiled kernel I successfully recompiled.
Did you rerun 'lilo' ?? if you did not then no new kernels will be used.
> The problem is that I doubt about somethin:
> First kernel image was compiled to support a lot of things(networking,
> etc), and the second one is supposed to be compiled with a really minimal
> setting (no networking, really simple).
> I seem to load both with no problem, But ..Both look weirdly similar, with
> exactly same features and compiled options..
> So my question is: How to make sure that kernel image A is really kernel
> image A, and kernel image B is really what it is ??
Many ways 3 of them are.
dmesg | grep -e "Linux version"
cat /proc/version
cat /proc/cmdline
> To me, my second kernel image looks too much similar to the first..and
> despite the fact that recompile it appeared to be a piece of cake..it
> probably failed to be what it should be.
> Is there a way to know that this is kernel image A that is actually on..and
> this is B that is on..and so on..??
>
Anyway the best way to compile thesedays is to compile as much as possable
as modules, just say "m" is you see;
Loopback device support (CONFIG_BLK_DEV_LOOP) [Y/m/n/?] choose m here, the
only things you realy need to compile into the kernel are things like ext2 fs
Harddisk driver, things you need "ALL" the time.
The rest modules, hence less hassel with making a kernel for this and a
kernel for that..
Read /usr/doc/HOWTO/Module-HOWTO.gz
/Kernel-HOWTO.gz
--
Regards Richard.
[EMAIL PROTECTED]
