Grrr... modprobe.conf

[Tom Horsley]

On Mon, 20 Sep 2010 13:49:30 +0100
Adam Williamson wrote:

> What's the last-touched date of your /etc/modprobe.conf ? Do you know
> when that is in relation to the lifetime of the install?

Just poking around, I get the impression that it may have
happened near the first round of updates after I did the
initial install of f14 alpha (from dvd):

[root at zooty ~]# ls -lc --full-time /spare/etc/modprobe.conf
-rw-r--r-- 1 root root 0 2010-08-25 19:44:57.000000000 -0400 /spare/etc/modprobe.conf
[root at zooty ~]# ls -lt --full-time /spare/etc/modprobe.conf
-rw-r--r-- 1 root root 0 2010-08-25 19:44:57.000000000 -0400 /spare/etc/modprobe.conf
[root at zooty ~]# ls -lt --full-time /spare/root/install.log
-rw-r--r--. 1 root root 103892 2010-08-25 18:42:33.000000000 -0400 /spare/root/install.log

Interesting that on my system at least, the file isn't world
writable. I hadn't noticed that before. Maybe there are multiple
ways it can get created, or maybe some process is inheriting
a umask that might be different? (The /spare partition is where I
have f14 installed).

In the yum.log I see the time on modprobe.conf occurs
in a gap in the yum updates:

Aug 25 19:37:56 Updated: xorg-x11-drv-aiptek-1.3.1-1.fc14.x86_64
Aug 25 20:02:56 Updated: libgcc-4.5.1-1.fc14.x86_64