lubuntu-wiki-docs team mailing list archive

[∅ <maps.backward@xxxxxxxxx>]

https://help.ubuntu.com/community/Lubuntu/Documentation/FAQ/Guides#Disable_Bluetooth
suggests blacklisting to unload Bluetooth. An interesting thing I found
is that if you then try to sudo modprobe bluetooth you get a notice
letting you know that this blacklisting file will be deprecated in the
future.

Another possible way of doing this is by modifying the S-scripts in run
levels 2-5. This can be easily done with the ncurses-based package
sysv-rc-conf but can also be done (with a little more skill/knowledge)
with update-rc.d. I guess you could also technically mess with the files
themselves but that's a pain IMHO.

To be sure they accomplished the same thing, I checked to see that lsmod
| grep bluetooth and ps aux | grep bluetooth both produced results,
which they did. Then I did the blacklisting and checked again. Neither
produced results. Then I removed the blacklisting, made sure that we
were back to the original behavior, and altered the S-scripts so that
the Bluetooth daemon wasn't loaded. Again, I checked the results of the
aforementioned commands and, again, nothing.

Anyways, it sounds like it may make sense to replace this section with a
section generally on unloading services, but use Bluetooth as an
example. My question is what you guys thing about giving the average
user the instruction to alter their run levels. This could mean totally
messing up their system if they don't do it right. Of course,
sysv-rc-conf is particularly easy, but still…I thought I'd ask before
forging forward.

wxl