This is the second such type of error of Gentoo depending on /usr being on the root partition I've noticed (the first one was catastropic and fixed quickly - by me). If you have emu10k1 emerged look at /etc/modules.d/emu10k1 you'll notice it calls /usr/bin/emu10k1-script. I don't think this is a bug, but others may disagree. I believe the correct solution would be to call /etc/init.d/modules twice with a check for a mounted /usr, and then make it group the modules according to whether they call anything on /usr. This is one method of ensuring users who need modules to mount /usr can continue. Reproducible: Always Steps to Reproduce: 1. Find a system with /usr on a separate partition 2. emerge emu10k1 3. boot up and watch for error message about failed to load emu10k1 (it does load but fails to run the post-install command. 4. Check the post-install command works by running it from the shell when logged in. Actual Results: emu10k1 reported as failed to load by boot script (not entirely accurate) emu10k1 was configured alright from the shell after login. Expected Results: Not required user interaction.
I *think* it will be too much complexity to do it as you suggests. The better way will be to move the scripts in /usr/bin to /bin. BTW, why is these scripts not rather put in sbin ? Daniel, Mike .. what do you think ? Could we move it to /bin (or /sbin rather) ?
i dont think it would be a good idea to move said script into /bin or /sbin ... those dirs really should be reserved for needed system files ... files that you need to recover from a failure of some sort ... a different solution might be to categorize modules the same way we have /sbin and /usr/sbin ... some modules are needed for proper bootup of a system while others are just nice to have (like emu10k1) ...
This is the sort of complexity I wanted to avoid.
welp if emu10k1 is the *only* module that does this ... you'd have to move most of its binaries/scripts ... i still dont like it but you're right, it would lead to a lot of complexity ...
Erm, does /usr/bin/emu10k1-script call any other scripts ? If not, then only it could be moved ?
And?
Why not just package an init-script with emu10k1 that loads its module? Don't put emu10k1 in modules.autoload and we should be golden, right?
emu10k1 has been long time obsolete and removed one year ago... About time to close this irrelevant bug.
this bug is not "irrelevant", it's just a pain i'm content with saying "dont make modules utilize /usr" for now
