Add a systemd generator that automatically launches IS if trigger file is found #12
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.
The first patch adds the initial-setup-reconfiguration.service which starts initial-setup.service if /.unconfigured exists.
The IS-side machinery then runs it in the reconfig mode due to the /.unconfigured trigger file being found. It also takes care of enabling of cleaning up the trigger file once done.
The second patch is just some cleanups and logging improvements I did when working on the first patch.
BTW, for this to work the initial-setep-reconfiguration.service needs to be always enabled.That effectively means the service needs to be added to the systemd presets file to assure it is automatically enabled when the initial-setup package is installed.