On Mon, 19 Mar 2001, Sonam Chauhan wrote:
> I run Redhat 7 on a P III. My previous kernel was '2.2.16-22' (uname)
> and my new kernel is 2.4.2 (compiled with the default config options)
default config? you mean you didn't change anything in the config?
That's not right. You have to customize it for you machine(s). That's the whole
point of compiling your own kernel.
> Here's one message my 2.2.16 kernel outputs at boot time:
> -------------
> raid5: MMX detected, trying high-speed MMX checksum routines
> pII_mmx : 1115.568 MB/sec
> p5_mmx : 1171.575 MB/sec
> 8regs : 860.679 MB/sec
> 32regs : 482.727 MB/sec
> using fastest function: p5_mmx (1171.575 MB/sec)
> -------------
> The 2.4.2 kernel I compiled generates no such message.
Well I guess the default config doesn't enable RAID 5. These aren't
optimizations. It's just the RAID-5 code finding the best checksum code at boot
time. If you don't use RAID-5, this won't make any difference.
> Can someone help with these questions:
> 1. Is there a a way to generate a /usr/src/linux-2.2.16/.config for my
> *2.2.16* kernel?
> This would tell me how my kernel varied from a default 2.2.16 kernel.
I think Redhat has config files somewhere on their FTP server. I wouldn't really
know: I'm a Debian user.
> 2. Does Redhat makes specific patches to their distro kernels that aren't
> in the mainstream kernel.
Yes, they do. I understand they add in various patches for projects plus
updates and bug fixes.
> Is it possible to apply those to the 2.4 kernel?
Probably not the same patch, but most projects that produce kernel patches will
likely have 2.4 patches by now. You'll have to hunt down each one that you
want/need. RedHat should document somewhere exactly what patches and changes
they've made to their source.
> 3. 'uname -a' informs me that my kernel is 2.2.16-22'
> while my current /usr/src/linux points to 'linux-2.2.16'
> Is the '-24' significant?
Distributions often append their own version number to the official/upstream
version number. That way you can tell if the official package has changed
version, or if the distributor has made changes. Distro changes are often little
things to do with the way it's packaged, but can sometimes include bug/security
fixes that haven't gone into the upstream version yet.
hope this helps,
bye
--
8<--------8<--------8<--------8<--------8<--------8<--------8<--------
Ian Tester *8)# \7\ LINUX: because geeks will find a way
[EMAIL PROTECTED] \7\ http://www.zipworld.com.au/~imroy
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
