Checkfs should depend on modules since they should be loaded to support the
devices on which the filesystems are. If you think that's esotheric, it
happened to me :)
This is the patch:
- need checkroot
+ need checkroot modules
Not too much :)
If it test ok, and dont bork anything else, sound logical enouth to do.
As round for testers, and if its fine with a few guys, give me the thumbs
I know it sounds bit silly, but usually the -r? update on baselayout was
due to a very small change that did not seem that important.
Hm, modifying this breaks all of my current startup scripts. Dunno why but
nothing won't work anymore. I don't even have the possibility to login as root.
The last exit was a hard reset of my box...
Ok, that's strange... It works perfectly for me :-/
Are you sure that it's related to this and not the crash?
What's the last startup step you see on the console? Or does it seem to work all
the way but then you can't login?
This works fine this side.
The new checkfs from baselayout 184.108.40.206 with checkfs now depending on modules
breaks my system startup:
I have a static kernel without module support and without any module
infrastructure installed. As far as I can tell, on startup, "modules" isn't
started properly, "checkfs" isn't executed because one of its dependencies is
missing, and anything depending on "checkfs" is not executed for the same reason.
Removing "modules" from the depends of "checkfs" makes everything working again.
However, I'm not yet sure what *exactly* causes the problem, because "modules"
*is* executed before "checkfs" (I do have "modules" in /etc/runlevels/boot), and
it *is* registered as started in /mnt/.init.d/started.
It just returns immediately because its first line is "[ -f /proc/modules ] ||
return", and a kernel built without module support doesn't have /proc/modules.
Why does this cause troubles with "checkfs"?
Try to change it to:
"[ -f /proc/modules ] || return 0"
And see if that fixes it ? Sometimes not specifying what to
return can have unpredictable results.
"return 0" solves the problem for me:
My system boots fine now with a kernel without module support, even if "checkfs"
depends on "modules".
Fixed in CVS, thanks.
The baselayout containing this fix is already in portage.