Make cluido wait for ipv4 to become available #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quite simple stuff. This means that you can have
cluido
start beforeipv4
, and still havecluido
be able to locate theipv4
server - which I find nice. It would be easiest to just putcluido
last in the list of things to start, but the virtual consoles seems to get a bit messed up if doing that, so let's not do it like that for now at least...(Eventually, the boot server should be completed and the responsibility for starting up cluido should be handed over to it. I'm not 100% sure that the building blocks - be able to start ELF binaries from user processes, etc - are in place, but they should be since we do have an execute command in cluido... Worth checking out at some point, it is.)