Release Notes for Alpine 3.12.0: Difference between revisions
Line 26: | Line 26: | ||
Note that /etc/modules cannot be overridden and only exists because of historical precedent. | Note that /etc/modules cannot be overridden and only exists because of historical precedent. | ||
==== Telegram Desktop is now available in the community repo ==== | |||
See the commit (TODO: add commit when merged) for explanation. |
Revision as of 03:56, 14 February 2020
Notable changes
OpenRC now has a sane ordering of directories when loading kernel modules
Loading kernel modules during boot is done with the modules OpenRC service, which reads configuration files in certain locations and loads kernel modules with the modprobe utility from either busybox or util-linux.
Before the changes the files were loading in the following order, files in modules-load.d directories were decided by how the shell picked it by globbing.
- /etc/modules
- /etc/modules-load.d/*.conf
- /run/modules-load.d/*.conf
- /usr/lib/modules-load.d/*.conf
- /lib/modules-load.d/*.conf
That means the changes that were done in /etc/modules or /etc/modules-load.d by the local administrator ended up being overridden by modules installed by packages in /usr/lib/modules-load.d and /lib/modules-load.d.
With the changes to the modules service the new ordering of directories is:
- /lib/modules-load.d/*.conf
- /usr/lib/modules-load.d/*.conf
- /etc/modules
- /etc/modules-load.d/*.conf
- /run/modules-load.d/*.conf
Now admins can override files installed by packages (/lib/modules-load.d and /usr/lib/modules-load.d) by having files with the same name in /etc/modules-load.d, and both can be overridden by files in /run/modules-load.d.
Note that /etc/modules cannot be overridden and only exists because of historical precedent.
Telegram Desktop is now available in the community repo
See the commit (TODO: add commit when merged) for explanation.