Osier Yang wrote:
Hi kaitlin. I tested on three machines.
===Machine A=== [root@dhcp-66-70-159 ~]# ls -laut /boot/ | grep vmlinuz -rw-r--r-- 1 root root 2045656 Jan 14 08:40 vmlinuz-2.6.18-183.el5xen -rw-r--r-- 1 root root 158 Jan 14 06:15 .vmlinuz-2.6.18-183.el5.hmac -rw-r--r-- 1 root root 1953468 Jan 8 14:28 vmlinuz-2.6.18-183.el5 -rw-r--r-- 1 root root 161 Dec 21 18:51 .vmlinuz-2.6.18-183.el5xen.hmac
[root@dhcp-66-70-159 ~]# find /boot/ | grep vmlinuz | egrep -v 'xen' | tail -n1 /boot/.vmlinuz-2.6.18-183.el5.hmac
==Machine B==== [root@dhcp-66-70-128 tmp]# ls -laut /boot/ | grep vmlinuz lrwxrwxrwx 1 root root 22 Jan 15 10:52 vmlinuz -> vmlinuz-2.6.18-160.el5 -rw-r--r-- 1 root root 1931964 Dec 23 13:44 vmlinuz-2.6.18-160.el5 -rw-r--r-- 1 root root 1931580 Aug 1 05:02 vmlinuz-2.6.18-158.el5 -rw-r--r-- 1 root root 2029233 Aug 1 05:02 vmlinuz-2.6.18-158.el5xen -rw-r--r-- 1 root root 158 Jul 28 05:41 .vmlinuz-2.6.18-160.el5.hmac -rw-r--r-- 1 root root 161 Jul 14 2009 .vmlinuz-2.6.18-158.el5xen.hmac -rw-r--r-- 1 root root 158 Jul 14 2009 .vmlinuz-2.6.18-158.el5.hmac
[root@dhcp-66-70-128 tmp]# find /boot/ | grep vmlinuz | egrep -v 'xen' | tail -n1 /boot/.vmlinuz-2.6.18-160.el5.hmac
======Machine C=============== [root@amd-4450b-4-1 ~]# ls -laut /boot/ | grep vmlinuz -rw-r--r-- 1 root root 1953468 Jan 12 21:29 vmlinuz-2.6.18-183.el5 -rw-r--r-- 1 root root 2045656 Jan 12 21:29 vmlinuz-2.6.18-183.el5xen -rw-r--r-- 1 root root 161 Dec 22 07:51 .vmlinuz-2.6.18-183.el5xen.hmac -rw-r--r-- 1 root root 158 Dec 22 07:43 .vmlinuz-2.6.18-183.el5.hmac
[root@amd-4450b-4-1 ~]# find /boot/ | grep vmlinuz | grep -v 'xen' | tail -n1 /boot/vmlinuz-2.6.18-183.el5
so, the result depends on the access time of ".vmlinuz-*.hmac".
Ah, good call! Thanks for tracking this down.
that means the patch is not useless. :)
Yep, agreed. I've applied your patch. Thanks!
Thanks and Regards osier
-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com