Skip to content

First boot asks again for a refused user name, and a second apply is told to reboot - #174

Merged
DevomB merged 2 commits into
mainfrom
first-boot-name-retry
Oct 5, 2026
Merged

DevomB merged 2 commits into
mainfrom
first-boot-name-retry

Conversation

@DevomB

@DevomB DevomB commented Oct 2, 2026

Copy link
Copy Markdown
Owner

Two prompts sent a user the wrong way.

  • First boot. A user name the setup refused (a capital letter is enough) ended the setup: the machine went on to a login prompt with no account, and only the next boot asked again. new_user now 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.sh drives it with a stand-in useradd: a plain name, a refused name then a good one, three refused names, and no answer.
  • A second apply. While a trial is armed and not yet booted, kryptik-update apply said "reboot first, or run rollback". Rollback arms the other slot, which is the slot just armed, so the trial stays and apply still refuses. The message says to reboot.

firstboot.sh is an input of stage 04's services step and kryptik-update of updater: both are in the stage's tail, so no package is built again.

DevomB added 2 commits October 2, 2026 01:07
…etup ended on one, leaving no account until the next boot
@DevomB
DevomB merged commit 52d942b into main Oct 5, 2026
21 checks passed
@DevomB
DevomB deleted the first-boot-name-retry branch October 5, 2026 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant