[arch-dev-public] blacklisting issue, perhaps initscripts or kernel 3.0 related
d at falconindy.com
Mon Aug 1 11:23:16 EDT 2011
On Mon, Aug 01, 2011 at 05:19:11PM +0200, Thomas Bächler wrote:
> Am 01.08.2011 16:48, schrieb Aaron Griffin:
> > On Mon, Aug 1, 2011 at 2:44 AM, Thomas Bächler <thomas at archlinux.org> wrote:
> >> Am 01.08.2011 09:30, schrieb Tobias Powalowski:
> >>> To explain it a bit better:
> >>> Arch always had the possibility to load modules in a certain order by
> >>> using the MODULES= array in rc.conf.
> >> Preservation of order has not been working for several initscripts releases.
> > Order preservation is doable via modprobe configs. See
> > /etc/modprobe.d/usb-load-ehci-first.conf for an example.
> Indeed, but it is not pretty.
It's also not recommended by upstream, as per modprobe.conf(5). We
shouldn't make any guarantees about module load order. What's the
problem we're trying to solve with this juggling? Is this bandaiding and
issue that should be taken upstream to the kernel folk? Or, is this some
pre-emptive attack against hardware being claimed by the wrong module,
in which case we should be leaving it up the user to figure out which
module they want to use...
More information about the arch-dev-public