Re: [arch-general] [arch-dev-public] [announcement draft] New module-init-tools changes modprobe configuration file location
On Fri, Jun 19, 2009 at 2:07 AM, Thomas Bächler <thomas@archlinux.org>wrote:
Allan McRae schrieb:
Thomas Bächler wrote:
The new module-init-tools 3.8 package changes the location of the configuration file: /etc/modprobe.conf is no longer read, instead /etc/modprobe.d/modprobe.conf is used. Files without a .conf suffix in /etc/modprobe.d are ignored now.
I think that they are not ignored this release, but a warning gets printed about them every time a module gets loaded. So how about:
Warnings are now printed about files without a .conf suffix in /etc/modprobe.d as these will no longer work with the next release. This will generate a lot of output on bootup if .pacsave files are left in this folder.
Too long, how about "Files in /etc/modprobe.d without a .conf suffix will be ignored in the future."
I noticed the warnings too, so will anyone else.
Just out of curiosity, why was that change made? Isnt it a bit incosistent to all other *.d's? pacman.conf isnt in pacman.d, logrotate.conf isnt in logrotate.d, rc.conf isnt in rc.d etc. Are there plans to move those too? -- Greg
Grigorios Bouzakis wrote:
On Fri, Jun 19, 2009 at 2:07 AM, Thomas Bächler <thomas@archlinux.org>wrote:
Allan McRae schrieb:
Thomas Bächler wrote:
The new module-init-tools 3.8 package changes the location of the configuration file: /etc/modprobe.conf is no longer read, instead /etc/modprobe.d/modprobe.conf is used. Files without a .conf suffix in /etc/modprobe.d are ignored now.
I think that they are not ignored this release, but a warning gets printed about them every time a module gets loaded. So how about:
Warnings are now printed about files without a .conf suffix in /etc/modprobe.d as these will no longer work with the next release. This will generate a lot of output on bootup if .pacsave files are left in this folder.
Too long, how about "Files in /etc/modprobe.d without a .conf suffix will be ignored in the future."
I noticed the warnings too, so will anyone else.
Just out of curiosity, why was that change made? Isnt it a bit incosistent to all other *.d's? pacman.conf isnt in pacman.d, logrotate.conf isnt in logrotate.d, rc.conf isnt in rc.d etc. Are there plans to move those too?
Upstream decision Allan
On Thu, Jun 18, 2009 at 6:18 PM, Allan McRae<allan@archlinux.org> wrote:
Grigorios Bouzakis wrote:
Just out of curiosity, why was that change made? Isnt it a bit incosistent to all other *.d's? pacman.conf isnt in pacman.d, logrotate.conf isnt in logrotate.d, rc.conf isnt in rc.d etc. Are there plans to move those too?
Upstream decision
A better way to put it: modprobe.conf is utterly gone and destroyed. Only /etc/modprobe.d/*.conf is parsed now. If one of those files just so happens to be the old modprobe.conf, then everything works as before.
Grigorios Bouzakis schrieb:
Just out of curiosity, why was that change made? Isnt it a bit incosistent to all other *.d's? pacman.conf isnt in pacman.d, logrotate.conf isnt in logrotate.d, rc.conf isnt in rc.d etc. Are there plans to move those too?
In the past, they ignored /etc/modprobe.d when /etc/modprobe.conf was present. Then we patched it to always read both - and that was accepted upstream. I guess they were annoyed by it and thus made the config file locations consistent.
I suppose that the location of this file isn't really important for the system, as long as the system can put his hand on it. And from my point of view, it's better to have a consistent system, in other word all apps.conf file in /etc, side by side with the apps.d my 2 cents
participants (5)
-
Aaron Griffin
-
Allan McRae
-
Grigorios Bouzakis
-
ludovic coues
-
Thomas Bächler