[gentoo-admin] Making changes to a statically build driver

[gentoo-admin] Making changes to a statically build driver

[Ezra Taylor]

[-- Attachment #1: Type: text/plain, Size: 349 bytes --]

Hello all:
               I made some changes to the e1000 kernel driver.  I then
recompiled the kernel without any issue.  How can I tell if the change
actually went through?  Again, this driver has been statically built into
the kernel.  Is there a way to test that a change went through without have
to setup a test environment?

-- 
Ezra Taylor

[-- Attachment #2: Type: text/html, Size: 380 bytes --]

RE: [gentoo-admin] Making changes to a statically build driver

[Two_Tone]

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

You could md5 hash the old and new kernel.  If the hash is different then changes were made.

-----Original Message-----
From: Ezra Taylor <ezra.taylor@gmail.com>
Sent: Thursday, Mar 5 2009 6:16 PM
To: gentoo-user@lists.gentoo.org; gentoo-admin@lists.gentoo.org
Subject: [gentoo-admin] Making changes to a statically build driver

Hello all:
               I made some changes to the e1000 kernel driver.  I then recompiled the kernel without any issue.  How can I tell if the change actually went through?  Again, this driver has been statically built into the kernel.  Is there a way to test that a change went through without have to setup a test environment?

-- 
Ezra Taylor

[-- Attachment #2: Type: text/html, Size: 1513 bytes --]

Re: [gentoo-admin] Making changes to a statically build driver

[Thilo Bangert]

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

>                I made some changes to the e1000 kernel driver.  I then
> recompiled the kernel without any issue.  How can I tell if the change
> actually went through?  Again, this driver has been statically built
> into the kernel.  Is there a way to test that a change went through
> without have to setup a test environment?

the e1000 driver probably prints version info to dmesg that you could 
tamper with...

also, check uname - it includes a buildversion (#1) and builddate of the 
currently running kernel:
bangert@marsupilami ~ $ uname -a
Linux marsupilami 2.6.28-gentoo-r2 #1 SMP Tue Mar 3 17:14:06 CET 2009 i686 
Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz GenuineIntel GNU/Linux


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]