Repository navigation
First boot asks again for a refused user name, and a second apply is told to reboot - #174
Merged
Merged
Conversation
…etup ended on one, leaving no account until the next boot
…ready holds, so it never cleared the way
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Two prompts sent a user the wrong way.
new_usernow says why the name was refused and asks again, three times at most, as the password question does; after that, or with no answer in ten minutes, the next boot asks.tools/tests/firstboot.shdrives it with a stand-inuseradd: a plain name, a refused name then a good one, three refused names, and no answer.apply. While a trial is armed and not yet booted,kryptik-update applysaid "reboot first, or run rollback". Rollback arms the other slot, which is the slot just armed, so the trial stays andapplystill refuses. The message says to reboot.firstboot.shis an input of stage 04'sservicesstep andkryptik-updateofupdater: both are in the stage's tail, so no package is built again.