My home server was upgraded yesterday with the new baselayout 1.12.4-r2. When it was rebooted today, portmat and the nfs server were not started, with a message about missing eth0. When checking, eth0 was well present and httpd and sshd were running, but not nfs. The problem seems to come from the RC_NET_STRICT_CHECKING variable in /etc/conf.d/rc. When changed from "no" to "yes", all the net services are well started, including nfs. Comment: maybe a more appropriate checking between net, portmap and nfs would be a better solution (a.e. portmat could provide a "portmap" status, and nfs should need it)
the point of RC_NET_STRICT_CHECKING=no is that the services get to assume your interfaces are all setup properly that means services can start in any order they feel, so having portmap/nfs start before the net service is legit the "nfs" init.d already depends on the "portmap" service
you are right: after verification, the following messages appears: 1. portmap is not started because missing net.eth0 2. nfs is not started because missing portmap In any case, after downgrading baselayout to 1.11.15-r3, I could have a nfs service starting normally. I have verify later than switching from baselayout 1.11 to 1.12 has an effect on portmap and nfs starting or not starting. I left the RC_NET_STRICT_CHECKING variable with her default "no" value.
so the behavior you are seeing is correct
With baselayout 1.12.4-r2 and -r3, the behaviour was _not_ correct: the services portmap and nfs were not started. Now I have upgrade to baselayout 1.12.4-r6, and the portmap and nfs services are now correctly started. I did not analyze where the difference could come.
