Odd that nobody responded to this, it sounds neat, but how come it takes over the kernel log? I think it'd be better if it didn't but thats no matter. In your mailing list posts you mention how to use it manually, but would adding it to the minirt24.gz root and starting it up inside that stuff be more useful? Is it even possible? I'm guessing just add this to linuxrc
Code:
cat /proc/kmsg > /ramdisk/accesslist.log &
echo $! > /ramdisk/cat.pid
modprobe monitor
also is this for 2.4 or 2.6 or both?

doing lots of pondering on the sorting of files right now and first access is better than latest access (also I'd need to make a partition for the express purpose of not having noatime in fstab and then hack the initrd to mount it and other stupid details) so I'll probably be giving this a shot in the next few days