[arch-dev-public] [signoff] module-init-tools 3.8-1
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d. Signoff both arches. Allan
Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
WARNING: this breaks mkiniticpio (resolve-modalias does not build due to updated glibc) so do a mkinitcpio until udev-141-3 hits testing soon... allanbrokeit
Allan McRae schrieb:
Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
WARNING: this breaks mkiniticpio (resolve-modalias does not build due to updated glibc) so do a mkinitcpio until udev-141-3 hits testing soon...
allanbrokeit
It does not only break mkinitcpio but also initscripts/load-modules, unless you have no modules in your rc.conf blacklist! I already fixed it before Allan even noticed, ha!
Thomas Bächler wrote:
Allan McRae schrieb:
Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
WARNING: this breaks mkiniticpio (resolve-modalias does not build due to updated glibc) so do a mkinitcpio until udev-141-3 hits testing soon...
allanbrokeit
It does not only break mkinitcpio but also initscripts/load-modules, unless you have no modules in your rc.conf blacklist!
I already fixed it before Allan even noticed, ha!
Many that to Thomas for fixing this. I was confusing myself about whether the udev fix was really enough... As an aside, it is the first time I have ever had to use a rescue CD on an Arch install! Allan
On Sun, Jun 7, 2009 at 16:18, Allan McRae<allan@archlinux.org> wrote:
Thomas Bächler wrote:
Allan McRae schrieb:
Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
WARNING: this breaks mkiniticpio (resolve-modalias does not build due to updated glibc) so do a mkinitcpio until udev-141-3 hits testing soon...
allanbrokeit
It does not only break mkinitcpio but also initscripts/load-modules, unless you have no modules in your rc.conf blacklist!
I already fixed it before Allan even noticed, ha!
Many that to Thomas for fixing this. I was confusing myself about whether the udev fix was really enough...
As an aside, it is the first time I have ever had to use a rescue CD on an Arch install!
Seems to work fine here (x86_64). I do not have any module blacklisted, but those in MODULES array of rc.conf load fine as well as those that are autodetected. So I guess I can sign this off. -- Roman Kyrylych (Роман Кирилич)
On Sun, Jun 7, 2009 at 12:44 PM, Roman Kyrylych<roman.kyrylych@gmail.com> wrote:
On Sun, Jun 7, 2009 at 16:18, Allan McRae<allan@archlinux.org> wrote:
Thomas Bächler wrote:
Allan McRae schrieb:
Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
WARNING: this breaks mkiniticpio (resolve-modalias does not build due to updated glibc) so do a mkinitcpio until udev-141-3 hits testing soon...
allanbrokeit
It does not only break mkinitcpio but also initscripts/load-modules, unless you have no modules in your rc.conf blacklist!
I already fixed it before Allan even noticed, ha!
Many that to Thomas for fixing this. I was confusing myself about whether the udev fix was really enough...
As an aside, it is the first time I have ever had to use a rescue CD on an Arch install!
Seems to work fine here (x86_64). I do not have any module blacklisted, but those in MODULES array of rc.conf load fine as well as those that are autodetected. So I guess I can sign this off.
Working here on x86_64, or at least I could boot following this and the mkinitcpio upgrade. -Dan
Allan McRae schrieb:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
Signoff both arches.
Allan
Didn't explicitly say this, but m-i-t, udev and filesystem from testing are working nicely.
On Sunday 07 June 2009 11:45:59 Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
Signoff both arches.
Allan
Maybe you could add an install script which moves modprobe.conf to the new location. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
Pierre Schmitz wrote:
On Sunday 07 June 2009 11:45:59 Allan McRae wrote:
Upstream update to module-init-tools-3.8. Main changes are that it expects all configuration files in /etc/modprode.d so /etc/modprobe.conf has move there. Also, all files in /etc/modprobe.d are expected to end with .conf so this required rebuilding udev, filesystem and v86d.
Signoff both arches.
Allan
Maybe you could add an install script which moves modprobe.conf to the new location.
I'm thinking no for the same reason we don't merge new configuration files or restart daemons. Allan
On Wed, Jun 10, 2009 at 20:24, Allan McRae<allan@archlinux.org> wrote:
Pierre Schmitz wrote:
Maybe you could add an install script which moves modprobe.conf to the new location.
I'm thinking no for the same reason we don't merge new configuration files or restart daemons.
Allan
Agreed. Don't automate such things IMO
On Thursday 11 June 2009 02:24:26 Allan McRae wrote:
Maybe you could add an install script which moves modprobe.conf to the new location.
I'm thinking no for the same reason we don't merge new configuration files or restart daemons.
Have a closer look and you'll see that this is completely different. But at least write an announcement which documents this change. We also need to update the installer to this; this also breaks ftp install (even though non-critical) -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
On Thu, Jun 11, 2009 at 12:50 AM, Pierre Schmitz<pierre@archlinux.de> wrote:
We also need to update the installer to this; this also breaks ftp install (even though non-critical)
Just the path to modprobe.conf, correct?
Am Freitag 12 Juni 2009 18:20:08 schrieb Aaron Griffin:
On Thu, Jun 11, 2009 at 12:50 AM, Pierre Schmitz<pierre@archlinux.de> wrote:
We also need to update the installer to this; this also breaks ftp install (even though non-critical)
Just the path to modprobe.conf, correct?
very likely. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de
participants (7)
-
Aaron Griffin
-
Allan McRae
-
Daenyth Blank
-
Dan McGee
-
Pierre Schmitz
-
Roman Kyrylych
-
Thomas Bächler