I recently ran into the problem of modprobe trying to read backup files
from /etc/modprobe.d, and because of sorting (I guess) it was always using
the old (backup) settings instead of the settings in the original file, as in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295755
Modprobe started spitting out strange error messages after I had
changed a module parameter. I tried reverted the change and otherwise
debug the problem by going back to the orignal settings. Of course,
even deleting the backup file and then re-editing the base file to try
another combination of settings ended up with a continuous cascade of
on-again/off-again errors.
This was preventing my headless MythTV system from starting up correctly and
was not very fun to debug - I only noticed some months after I had changed
the original setting and did not reboot.
The backup file was created by vim with the ".orig" extension in the
/etc/modprobe.d directory, but I'd imagine similar problems would be
had with emacs and "~" extension files.
I'm using KnoppMyth R5E50 with the 3.3-pre3-1 module-init-tools (Debian 4.0).
Cheers, Andreas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
