Feel free to update the FAQ to use the .conf file! The other point raised is that of FAQ's for different expertise. I've given my views in a previous email, but things for run-level should really be in the intermediate / advanced section of tweaks to do with lubuntu :)
Regards, Phill. On 31 January 2012 17:40, Bhaskar Kandiyal <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > On Monday 30 January 2012 09:53 AM, ∅ wrote: > > > 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. > > That notice is for /etc/modprobe.d/blacklist, the message states that > every file in this directory should be a .conf file, so we can safely > replace /etc/modprobe.d/blacklist with /etc/modprobe.d/blacklist.conf > (both files exist as of now) to get the same results. I might make the > change to the FAQ. > > > 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 > > > > I don't think letting a user mess with the runlevels and their > services is a good idea :) > As you said, it can mess up the system, so we should take the easy way > out and tell the user the method that's less error prone or the one > that doesn't need advanced know-how. > > Regards, > Bhaskar Kandiyal > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iEYEARECAAYFAk8oJ40ACgkQc3l9wn9I2OeyrACfW8UcLd4I4UJ5RYU9PB/1ujD3 > JKYAnjNzdk7jIKmW6ChpO9eVpb7WZ0Sq > =hOF1 > -----END PGP SIGNATURE----- > > -- > Mailing list: https://launchpad.net/~lubuntu-wiki-docs > Post to : [email protected] > Unsubscribe : https://launchpad.net/~lubuntu-wiki-docs > More help : https://help.launchpad.net/ListHelp > -- https://wiki.ubuntu.com/phillw
-- Mailing list: https://launchpad.net/~lubuntu-wiki-docs Post to : [email protected] Unsubscribe : https://launchpad.net/~lubuntu-wiki-docs More help : https://help.launchpad.net/ListHelp
