Ok, so readahead-fedora should conflicts: auditd, but not if upstart is
installed (but the conflicts mechanism can't handle that). Hmm.
Can it fire off a log message or something if readahead detects that
auditd may be clobbering it? Maybe by alerting if it doesn't find the
usual /etc/init.d/stop-readahead-fedora in the data. (Which I guess
should be a fairly clear indication that *something* went wrong.)
Mike Stone
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org