-
-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beta v6.17 | Autorun 2nd "dietpi-update" to apply v6.17 #2144
Comments
MichaIng
referenced
this issue
Oct 16, 2018
+ DietPi-Patch | Run 2nd dietpi-update during pre-v6.17 patch concurrently, since killing parental script causes issues: https://github.com/Fourdee/DietPi/issues/2144
|
Little error:
€: Fix + PR up: https://github.com/Fourdee/DietPi/pull/2145 |
This was referenced Oct 16, 2018
Works a charm, great work 👍 Will mark as completed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ref: https://github.com/Fourdee/DietPi/issues/2140#issuecomment-430005986
v6.17
update runs on first boot,dietpi-software
only applies update untilpatch_file
terminates for manual re-run. Since terminated,.update_stage
is not updated, thusdietpi-software
does not know about applied update and does not forcereboot
. Also it offers to configure system, install software and finish first run setup.dietpi-software
code, and/or many incremental patches are missing due to low DietPi version on image.dietpi-software
allows to/does install software.Without doing much hacks on
.update_stage
and or.install_stage
, somehow force an additionaldietpi-update
run during boot scripts or something, the easiest solution would be an automated update re-run.I experimented around with G_EXIT_CUSTOM trap to somehow call
dietpi-update 1
after terminating 1st dietpi-update instance and patch_file itself.The problem is, that scripts don't like, if you kill their (grant) parents. Input is broken, leading to ugly errors
_pSLsys_getkey: EIO error
, whiptails does not take input, terminal looks somehow ugly, screen a patchwork of whiptail in background, those error messages and input cursor somewhere in the middle of the screen.Simple test scripts to replicate this behaviour:
Testing now to simply allow concurrent
dietpi-update
run byrm -R /tmp/DietPi-Update /tmp/DietPi-Patchfile
first. Then afterdietpi-update 1
has finished insidepatch_file
,kill $PPID; exit
.Branch to test this: https://github.com/Fourdee/DietPi/blob/patch_test/dietpi/patch_file
The text was updated successfully, but these errors were encountered: