Thomas Bächler wrote:
Tom K schrieb:
SImplest, most Arch-like solution is to load the modules in the
required order in the rc.conf MODULES array.
I hope that's what you mean by "manually". :)
With the asynchronous "trigger && load MODULES=() && settle", there is
no way anymore to ensure module loading order! You need to fix this
using persistent naming schemes, which is easy for network interfaces.
It is also easy on alsa devices (index= option) and hard drives (uuid,
label symlinks).
OK... guess I'll dig through arch-dev-public to find the upside to that. :P
