$sudo nano /etc/rc.conf
Houston, we found the problem!
]]>$ sudo sed -i '/MODULES=/s/)/ bluetooth&/' rc.conf
What a mess! Now I need to create a new file for every module in /etc/modules-load.d!?!?!
Well...
$ echo "bluetooth" | sudo tee /etc/modules-load.d/10-bluetooth.conf
I think this is much better than this:
$sudo nano /etc/rc.conf
↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓,↓
→,→,→,→,→,→,→,→,→,→,→,→,→,→,→,→,→,→,→,→
bluetooth
^O
^W
It is also much easier to write a little helper (like an rc.d that can activate and deactivate daemons).
]]>Ok, that is better. The man page says name the file after the module. So the name of the .conf file does not matter? So I can create modules.conf and list them each on a separate line? I can live with that.
Yes, that's right. As long as it ends in .conf it will be read.
]]>What a mess! Now I need to create a new file for every module in /etc/modules-load.d!?!?!
You can put a bunch of modules in one file in /etc/modules-load.d if you want. Put each one on a separate line.
]]>What a mess! Now I need to create a new file for every module in /etc/modules-load.d!?!?!
Also many, many wiki pages need to be updated as they still say to add modules to rc.conf.
I hope this makes it better, because it is not easier.
Only one file is needed, you can list one module per line.
Feel free to update the wiki. I did a bit, but obviously not all. The old syntax still works, do if someone uses that it is not under end of the world.
]]>^ What manpage? archlinux nor rc.conf has it, as far as I can see
Thanks for the quick reply, I'll delete them!
Hm, oops. In that case I will have to add that :-S
]]>USECOLOR="no"
Not sure where should it come to.
]]>Thanks for the quick reply, I'll delete them!
]]>So yesterday I came back from holiday and fully updated my system. Today I got around to merging all the changes with rc.conf and setting up the new config files - all working as it should. There are some leftover entries from my old rc.conf though, for which I did not find a new config file:
DAEMON_LOCALE="yes" USECOLOR="yes" USEBTRFS="no" broadcast= NETWORK_PERSIST="no"
What about these? Are they dropped, or should I keep them in rc.conf? I don't use the last three and all five of them are the default, but I'd still like to know.
Should be explained in the man page. You can delete then all.
]]>DAEMON_LOCALE="yes"
USECOLOR="yes"
USEBTRFS="no"
broadcast=
NETWORK_PERSIST="no"
What about these? Are they dropped, or should I keep them in rc.conf? I don't use the last three and all five of them are the default, but I'd still like to know.
]]>This is really just slowly becoming a headache. I have other work to get on with, without having to deal with spending so much time on just getting a PC to work.
Everything changes. You will face those changes sooner or later. You only can choose between dealing with changes one at a time (rolling release distro) or delaying changes until installing a new release (release distro). Some people feel that dealing with changes one at a time increases amount of work to "get a PC to work". I think this is just a perception. Nevertheless, they prefer release distros, so I recommend you moving to one.
]]>