MichaIng

@pitsi We want to install all packages, required for the DietPi system tho run, first, and remove the non-required packages afterwards. This resolves potential issues like the one with ifupdown...

The Armbian repository is added via mirror director, so by chance that one is picked on a single connection or not. But actually, I can access it just fine here,...

Hmm, for `apt update` it probably makes sense, at least when it is an automated first run setup. However, it is likely that just trying two times after another would...

@kmplngj Many thanks for your report. Jep that is a known limitation with the kiosk mode, which is not 100% non-interactive. The app mode is indeed the solution but one...

@kmplngj Thanks for reporting. Using `--app=$URL` instead of `--kiosk` does not hide this? However instead of hiding it, it would be better to check why the update fails. If you...

@kmplngj Okay that is bad, then we need to go through the available options again: https://peter.sh/experiments/chromium-command-line-switches/

@docgalaxyblock Makes sense, there are quite many options available for different use cases. I'll see if I find some time for v6.30 to implement such, meanwhile anyone is welcome do...

@docgalaxyblock @kmplngj Many thanks for your info guys. As of my testing [here](https://github.com/MichaIng/DietPi/issues/2938#issuecomment-506393195) sadly the `--kiosk --noerrdialogs` does not make it 100% non-interactive, as there are other prompts possible that...

Okay so `--kiosk --noerrdialogs` as you tested before does not work, `--app --noerrdialogs` does not, I'm out of ideas how get it silenced. Also seems like each Chromium behaves a...

> --check-for-update-interval=31536000 Great to have a solution for that. Probably `--check-for-update-interval=0` might work as well to disable update checks? There is not really a Chromium version that DietPi uses, there...