Dev1 Galaxy Forum / how to tell dpkg to stay away from kernel module blacklist? [SOLVED]

Re: how to tell dpkg to stay away from kernel module blacklist? [SOLVED]

dummy@example.com (GNUser) — Fri, 13 Apr 2018 17:16:42 +0000

LOL

Good one!

Re: how to tell dpkg to stay away from kernel module blacklist? [SOLVED]

dummy@example.com (fsmithred) — Fri, 13 Apr 2018 17:13:09 +0000

Normally, dpkg will ask you what you want to do when it detects a config file that's been altered from the default. My understanding is that the *.d directories are there for the local admin to add custom configs that won't be touched by dpkg. I guess that understanding is not correct or complete. Maybe put it in a file named myfsckingblacklist.conf and see if that works.

Re: how to tell dpkg to stay away from kernel module blacklist? [SOLVED]

dummy@example.com (GNUser) — Fri, 13 Apr 2018 17:12:34 +0000

I'm going with this for now: # chattr +i /etc/modprobe.d/blacklist.conf

how to tell dpkg to stay away from kernel module blacklist? [SOLVED]

dummy@example.com (GNUser) — Fri, 13 Apr 2018 16:55:21 +0000

I was surprised and angry when I discovered that some application renamed my /etc/modprobe.d/blacklist.conf to /etc/modprobe.d/blacklist.conf.dpkg-bak. I'm guessing from the name that the culprit was dpkg, but I can't be sure.

This is upsetting because one of the blacklisted kernel modules is uvcvideo, which was blacklisted to disable my webcam for privacy reasons. (I have black tape over the webcam, but I also want that sucker's kernel module blacklisted just to be paranoid.) Running lsmod | grep uvcvideo confirms that the module is loaded (i.e., renaming blacklist.conf disables the blacklist).

Please, how do I make sure that dpkg (assuming it was the culprit) never ever does this again?