I have a gentoo system with /var separate from /. As of baselayout 1.8.6.8-r1, I'm having problems with booting due to the init scripts recording things in /var/lib/init.d/ and then mounting /var and not having access to the information that was already written. This also prevented booting until I created /var/lib/init.d under the / partition. ie. I now have two separate /var/lib/init.d directories so that I can at least boot the machine. Reproducible: Always Steps to Reproduce: 1. create a separate partition for /var 2. boot the machine Actual Results: Machine would not boot. Complained about missing /var/lib/init.d Expected Results: Mount /var before looking for /var/lib/init.d
Ok, that's a problem, however you can easily modify the svcdir variable in /etc/conf.d/rc to a local directory. I've used it on my servers (all with separate var ;) ) and works just fine. Bye
Thanks for the tip. That certainly makes the boot go more smoothly. There should probably be a warning on the baselayout pointing this out.
It runs the following in /etc/init.d/ before /var is touched: checkroot hostname modules checkfs localmount which in theory means /var should be mounted if in /etc/fstab and not marked as 'noauto'. Any idea why this fails for you ? If it does, it is a bug, and nothing that should be warned about (except maybe if some weird config). You could also edit /etc/conf.d/rc to use tmpfs like the older versions did ... I would however like to get thsi fixed. I know Seemant is running a setup like yours (/var on seperate partition at least), and working fine for him ...
yeah, I was puzzled by this bug report as well. My /var has always been on a separate partition, and I had no hiccups going to the new baselayout.
Since I have not dug through all the startup scripts yet, let me start by listing the systems as accurately as I can. After the baselayout update, I had trouble starting up some daemons on my test machines. I tracked the problem down to the move of of cache directory to /var/lib/init.d. I ran depscan.sh to create that directory and things looked good (though my next move shows that I probably could have made a better choice). I then tried to start up apache and the system immediately complained and dropped me into a shell to fix the problems. Not thinking, I hit ^D to get out of the shell and it rebooted (yes, if I was thinking, I would have been more careful). On the reboot, it dropped me into a shell again complaining that there was not /var/lib/init.d (which there was not, since /var was not mounted). After creating /var/lib/init.d (running depscan.sh again) and rebooting, I'm getting a complaint about the softlevel file not being there. It seems it is being written the /var/lib/init.d before /var is mounted. Let me know if you need more details.
I should have commented much sooner. It may be something that did not update properly. Could you move /var/cache/edb/config (or backup), then zero it, and remerge baselayout. Then check if anything needs updating in /etc/ and /etc/init.d/ or where ever else might be crusual. Afterwards you can move the backup of /var/cache/edb/config back.
This works for me at least.
