Perhaps we're misunderstanding each other.
They're just programs that init happens to run when it feels like it.
That's a terrible way to describe dependencies. Eg, you can't run for example NFS mounts if you don't have network, and can't do network without local FS, etc.
You're missing a bit of context with that. That statement was in direct response to your request for me to explain why I singled out Ubuntu/Upstart. It was intended in contrast to how Ubuntu's/Upstart's daemons function, as sysv daemons can all run just fine in a chroot more or less irrelevant of host (provided the dependencies are met), but Ubuntu's daemons cannot (due to dependence on a specific init which the host may not use). I can go ahead and ensure Bedrock provides network before setting up NFS, but I cannot ensure Bedrock provides the specific upstart init. Moreover, you explicitly said
(and I'm not even talking about dependency booting...
The fact you pointing out with great emphasis that I failed to address dependency issues in response to a statement which explicitly excluded dependency issues leads me to believe we are misunderstanding each other. If the misunderstandings are on my end, I apologize. I admit I could be dense and simply misunderstanding you - in fact, that's most likely the case - but it seems you're a bit scattered in your direction with the questions/responses. If you give me something very concrete and specific to respond to I will be more likely to succeed.
So OF COURSE it wont be resolved anytime
, because Ubuntu guys don't care, they use Upstart.
Agreed, sadly. Ubuntu puts very little priority on things outside of their core interest - people who use chroots aren't exactly their target audience. None the less I have a functional workaround for the issue.
Now, Bedrock doesn't address these issues
I'm not sure exactly what issues you are referring to. While getting Ubuntu's daemons to work is not as clean as I would like, but works just fine. If you are referring to automatic dependency resolution for client daemons at boot, then no, the first alpha release does not provide any means for this quite yet. It is a relatively low priority at the moment (as specifying these things manually is absolutely trivial), and the project is yet quite young.
it's of very low interest to me
That's fine. Your particular needs could very well differ from mine, and if this does not benefit you, I certainly encourage you to stick with something which does. As I stated before, I agree that this a relatively niche project. However, I do not approve of the way you are misrepresenting what Bedrock Linux is and is capable of, as there are others like me who do have a use for such things who may be discouraged from trying the project out after reading your comment.
it's not better than managing chroot by hand, by myself.
If you truly believe this, then I have almost certainly failed in properly explaining it, and I am at a loss as to where I have lead you astray. While all of this is certainly possible manually, it is significantly more work for the particular usage cases for which I utilize it. At the risk of confusing the issue, I will make an analogy against package managers: What they do can very well be done manually, but if you wish for anything remotely complicated it is significantly easier to simply use a package manager. Stating that "apt-get remove [package]" is a waste when you can just run find against timestamps for when the package was installed and just rm the resulting files is either significantly lacking in imagination or disingenuous. Now, if you have no need for package managers as you don't add/remove things very often, well, that's fine. But that doesn't mean the project is sufficiently irrelevant to dismiss it out of hand and discourage others who could very well benefit from it.