Conversation
mention that the others correspond to systemd commmands
mvidner
force-pushed
the
clarify-inst-finish-stop
branch
from
18f4f44 to
a55d389
Compare
|
This is a follow-up for #47 |
It will stop at the congratulation screen as it currently does allowing to reboot manually through the UI or the CLI
It will be available as well as the UI. Currently the only task is running is to save logs.
|
| Stop at the end of the installation | ||
| - `reboot`: | ||
| Stop the installation at its end, at the "Congratulations! [Reboot]" screen, | ||
| leaving the backend running |
There was a problem hiding this comment.
But now I am wondering... agama finish stop seems to be a no-op then? What am I missing?
There was a problem hiding this comment.
That is exactly the case, what about renaming it to agama.finish=no, probably someone would expect then also the agama.finish=yes but by default reboot will be applied in case not a valid option an called from unattended installation, in the CLI it will report an error
There was a problem hiding this comment.
I am not sure if we sould mention the UI at all, I mean what is shown in the UI is because the installer is in the installed phase but maybe @imobachgs or @dgdavid have an stronger opinion
3 participants
mention that the others correspond to systemd commands
(here my initial misconceptions and questions about `stop`)
TODO: as a user I would like to know some more info about `stop`. Presumably this is a debugging option when I am doing a test and want to inspect the system. I assume that the web service will stop and the web UI will no longer work? Agama CLI will not work? So I should log in at the console, that's my only option? To continue, I should tell systemd to `reboot`, `poweroff` or `halt`?We may also say that
stopis an intermediate state that we don't want to overspecify.