| View previous topic :: View next topic |
| Author |
Message |
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
 Posted: Sun Jul 30, 2017 8:41 pm Post subject: |
 |
|
| steveL wrote: | Gentoo has never automagically enabled anything just because it is installed.
The closest parallel is with daemons; just because they're installed, does not mean the admin is ready to deal with them being started automatically, nor even wants that. |
in this case, a daemon called modules-load starts automagically to load stuff from systemd locations (ref op). i can't disable that service as it's not enabled, nor listed on any runlevels.
it was a surprise to me, as it's not documented anywhere.
| steveL wrote: | If a bindist wants to, that's their choice, and sod-all to do with what is best for Gentoo users.
And yes, what you're discussing here is again from the point of view of an upstream developer; and sorry, no you don't always know best: that's why we have distros.
Gentoo is not an idiot-box distribution; if an admin wants to set up autoload for their users, they can do it themselves.
The alternative breaks the principle of least-surprise, for no good reason, especially so given the context. |
and that's why we have docs. those who come to gentoo do so for very specific reasons, least of all plug-and-pray!
Last edited by josephg on Tue Aug 01, 2017 1:28 am; edited 3 times in total |
|
| Back to top |
|
 |
steveL
Watchman
Joined: 13 Sep 2006
Posts: 5153
Location: The Peanut Gallery
|
| Posted: Mon Jul 31, 2017 3:16 pm Post subject: |
|
|
| josephg wrote: | | Those who come to gentoo do so for very specific reasons, least of all plug-and-pray! |
Heh; ++ |
|
| Back to top |
|
|
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
| Posted: Wed Aug 02, 2017 7:00 am Post subject: |
|
|
i just had a brainwave, and decided to test it.. all working fine and a non-destructive fix.
simple solution: disable this daemon modules-load
| Code: | | # chmod -x /etc/init.d/modules-load |
_________________
"Growth for the sake of growth is the ideology of the cancer cell." Edward Abbey |
|
| Back to top |
|
|
i4dnf
Apprentice
Joined: 18 Sep 2005
Posts: 271
Location: Bucharest, Romania
|
| Posted: Wed Aug 02, 2017 7:12 am Post subject: |
|
|
I think that fix will be "unfixed" the next time you update openrc, especially if it contains an updated /etc/init.d/modules-load file. (I don't think the tools dealing with CONFIG_PROTECT mechanism get "activated" on file permissions only.)
Modifying the /etc/init.d/modules file and commenting out the modules-load dependecy prevents modules-load from autoloading and also, in case an update openrc contains a modified file you'll be able to inspect the changes via dispatch-conf, or whatever your prefered method.
_________________
"The only difference between me and a madman is that I am not MAD" (SALVATOR DALI) |
|
| Back to top |
|
|
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
| Posted: Wed Aug 02, 2017 7:31 am Post subject: |
|
|
| i4dnf wrote: | | I think that fix will be "unfixed" the next time you update openrc, especially if it contains an updated /etc/init.d/modules-load file. (I don't think the tools dealing with CONFIG_PROTECT mechanism get "activated" on file permissions only.) |
hmm.. and you are right! i tested this, and indeed the next emerge resets the permission bits, no relevant messages.
| i4dnf wrote: | | Modifying the /etc/init.d/modules file and commenting out the modules-load dependecy prevents modules-load from autoloading and also, in case an update openrc contains a modified file you'll be able to inspect the changes via dispatch-conf, or whatever your prefered method. |
i'm loathe to edit /etc/init.d, and imho preferable to edit /etc/conf.d
i know i can add depends in /etc/conf.d, but can i disable/negate depends want in /etc/conf.d/modules?
Last edited by josephg on Wed Aug 02, 2017 9:54 am; edited 1 time in total |
|
| Back to top |
|
|
i4dnf
Apprentice
Joined: 18 Sep 2005
Posts: 271
Location: Bucharest, Romania
|
| Posted: Wed Aug 02, 2017 7:42 am Post subject: |
|
|
Hmm, openrc manual (man openrc-run) says the !modules-load should work.
i.e in /etc/conf.d/modules
| Code: | | rc_want="!modules-load" |
_________________
"The only difference between me and a madman is that I am not MAD" (SALVATOR DALI) |
|
| Back to top |
|
|
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
| Posted: Wed Aug 02, 2017 9:49 am Post subject: |
|
|
i couldn't find rc_want in man openrc-run, but i have tested this and it works. i think this workaround is better than the previous ones as /etc/init.d/ remains pristine.
| Code: | $ cat /etc/conf.d/modules
rc_want="!modules-load" |
i4dnf, thank you! this is perfect  fits in with the gentoo policy of modifying /etc/conf.d/ rather than /etc/init.d/
also keeps this change across emerge/updates
personally i think gentoo/openrc should remove this "want modules-load" from /etc/init.d/modules, and allow user/sysadmin to add modules-load to any runlevel (just like any other service) if this is wanted. for eg
| Code: | | # rc-update add modules-load boot |
this also means those who don't want this systemd behaviour can remove modules-load service from any runlevels. |
|
| Back to top |
|
|
i4dnf
Apprentice
Joined: 18 Sep 2005
Posts: 271
Location: Bucharest, Romania
|
| Posted: Wed Aug 02, 2017 7:45 pm Post subject: |
|
|
| josephg wrote: | | i couldn't find rc_want in man openrc-run, but i have tested this and it works. |
| man openrc-run wrote: | | With the exception of /etc/rc.conf, the configuration files can also influence the dependencies of the service through variables. Simply prefix the name of the dependency with rc_. |
In openrc-run speak dependencies are any of: need, use, want, after, before, provide, config, keyword
_________________
"The only difference between me and a madman is that I am not MAD" (SALVATOR DALI) |
|
| Back to top |
|
|
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
| Posted: Wed Aug 02, 2017 11:49 pm Post subject: |
|
|
thanks again i4dnf
and another distro which suggests openrc has this to say about modules-load.d:
_________________
"Growth for the sake of growth is the ideology of the cancer cell." Edward Abbey
Last edited by josephg on Mon Aug 07, 2017 8:09 am; edited 3 times in total |
|
| Back to top |
|
|
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20067
|
| Posted: Thu Aug 03, 2017 6:18 pm Post subject: |
|
|
Locking this thread for the time being.
As it is solved, I'll see about extracting the unrelated content later.
@steveL & mv: I've replied to the report post and separated it to its own thread. Please see that thread.
[split]steveL & mv
In the meantime, please stop engaging each other.
EDIT: Unlocked and split off some of the posts by steveL and mv.
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
| Posted: Wed Sep 26, 2018 10:34 am Post subject: |
|
|
reopened: latest version of openrc loads modules from systemd locations and does not respect rc_wants workaround which solved the OP issue.
_________________
"Growth for the sake of growth is the ideology of the cancer cell." Edward Abbey |
|
| Back to top |
|
|
josephg
l33t
Joined: 10 Jan 2016
Posts: 783
Location: usually offline
|
| Posted: Wed Sep 26, 2018 10:44 am Post subject: |
|
|
digging further… previous versions of openrc had a modules-load service to replicate systemd behaviour of automagically loading modules from systemd locations. modules-load was automatically called by modules service. the workaround blocked modules-load service.
this workaround does not work anymore, because the latest openrc removed that modules-load service and subsumed it inside the modules service. so now we can't block modules-load because it doesn't exist. do we now entirely block modules service? i feel a bit wary.
_________________
"Growth for the sake of growth is the ideology of the cancer cell." Edward Abbey
Last edited by josephg on Thu Oct 18, 2018 8:58 pm; edited 1 time in total |
|
| Back to top |
|
|
Naib
Watchman
Joined: 21 May 2004
Posts: 6051
Location: Removed by Neddy
|
| Posted: Thu Oct 18, 2018 7:35 pm Post subject: |
|
|
/etc/init.d/modules
| Code: |
find_modfiles()
{
local dirs="/usr/lib/modules-load.d /run/modules-load.d /etc/modules-load.d"
|
1) Why the hell /usr/lib ... if an administrator now needs to disable something they need to edit part of a lib and NOT in etc (where such things are controlled from)
2) WHY THE HELL /run a tmpfs directory mounted at boot...
http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#etcHostspecificSystemConfiguration
| Quote: | /etc : Host-specific system configuration
3.7.1. Purpose
The /etc hierarchy contains configuration files. A "configuration file" is a local file used to control the operation of a program; it must be static and cannot be an executable binary. [2] |
| Quote: |
/usr/lib : Libraries for programming and packages
4.6.1. Purpose
/usr/lib includes object files and libraries. [21] On some systems, it may also include internal binaries that are not intended to be executed directly by users or shell scripts. [22]
Applications may use a single subdirectory under /usr/lib. If an application uses a subdirectory, all architecture-dependent data exclusively used by the application must be placed within that subdirectory. [23]
|
Fair enough storing the actual modules in /usr/lib/* but the control of this should be via /etc
_________________
| Quote: | | Removed by Chiitoo |
|
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Thu Oct 18, 2018 8:34 pm Post subject: |
|
|
A program is not a library. /usr/bin is more appropriate than /usr/lib
Concur regarding /etc for configuration. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Thu Oct 18, 2018 8:51 pm Post subject: |
|
|
| Naib wrote: | | if an administrator now needs to disable something they need to edit part of a lib and NOT in etc |
No, it is always sufficient to edit in etc (see below).
| Naib wrote: | | storing the actual modules in /usr/lib/* but the control of this should be via /etc |
That's how the mechanism is meant to be used: /usr/lib contains only the defaults. You can override these with /etc: If a file with the same name exists in /etc that one will be used, and the corresponding file from /usr/lib will be ignored in that case. In particular, to "remove" a file from /usr/lib you can just create an empty file (or a symlink to /dev/null) in /etc with the corresponding name.
The advantage of this is that the defaults as well as your local changes are both always accessible without using any backup or special features of a package manager. Another advantage is that in /etc really only local changes are stored which simplifies things if you want to see what you modified locally (e.g. to initialize another machine, or for backup purposes). Yet another advantage is that a package update can simply update the defaults. A disadvantage is that it is less obvious when this happens. |
|
| Back to top |
|
|
|
Kernel & Hardware
