-
-
Notifications
You must be signed in to change notification settings - Fork 504
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.25.1 #2940
Beta v6.25.1 #2940
Conversation
+ Add drive size to selection menu + Verify source image file existence and mount as loop directly + Add RootFS menu selection based partition detection + Automatically detect GPT partition, check for MBR otherwise, exit if non is matching, to not continue with unknown partition table for now + Mount image for edit, before shrinking file system, to have correct minimal size AFTER changes have been applied + So all drive manipulation/estimation on loop device + Use /root instead of $HOME since the script is forced to run as root user anyway
…itial v6.26 support
+ DietPi-Benchmark | RAM: Check if /tmp is mounted as tmpfs, otherwise skip RAM bench + DietPi-Benchmark | RAM: Allow to fill 50% of free RAM to increase accuracy and which should be sufficient to assure that nothing is swapped + DietPi-Benchmark | FS: Allow to use up to free space - 50 MiB, always use min/max value in case provided value is outside of range or invalid + DietPi-Benchmark | Consequently use MiB and fix calculations where 1000 was used + DietPi-Benchmark | Consequently quote input values for G_CHECK_VALIDINT in case they contain free spaces
+ DietPi-Software | Coding: G_WHIP_CHECKLIST() does not return $G_WHIP_RETURNED_VALUE as array, so no ${G_WHIP_RETURNED_VALUE[@]} loop required + DietPi-Software | Failsafe: Always double quote G_CHECK_VALIDINT() $1 argument + DietPi-Software | Failsafe: Always localise $i in functions when using it in for loops
+ DietPi-Globals | Coding: Replace "sed -n Xp" with "mawk 'NR==X {print}'" which is ~30% faster + DietPi-Globals | G_THREAD Environment cleanup: Do not declare $G_THREAD_COUNT and $G_THREAD_COMMAND variables in session, but on demand + sanity checks within G_THREAD_START(), and, unset after G_THREAD_WAIT(). + DietPi-Globals | G_THREAD_WAIT() Visual: Use G_DIETPI-NOTIFY -2 processing animation instead of printing new line every second + DietPi-Globals | G_THREAD_START() Coding: Instead of double subshell for threads, use command assembly, which initiates (including disown) in ~half time
+ DietPi-Config | Add RPi4 default sdram_freq based on official docs: https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md + DietPi-Config | Fix RPi2 default sdram_freq 450 => 400 + DietPi-Config | Minor coding
+ DietPi-Set_hardware | Consequently use $FP_RPI_CONFIG (non-RAMdisk support) if we define this already + DietPi-Set_hardware | Do not use G_CONFIG_INJECT() to comment settings, as this causes confusing output and adds the comment as well if the setting was not present before + DietPi-Set_hardware | Assume dietpi.txt to be case sensitive
For the first time, updating from 6.25.0 to 6.25.1 via |
Try dietpi-update 1 |
A bit nervous to do that which is why I commented here first this is unlike past updates before I try to jackhammer it in just wanted to verify if this is a known issue or not but otherwise I guess I'll just force it. |
@CollinChaffin @user349 Found the issue:
The update whiptail has leading dashes in its text, thus fails. Strange however is that we have this already since... let me see.. ah nope, I removed a leading blank line...
Resolved with: https://github.com/MichaIng/DietPi/blob/dev/dietpi/dietpi-update
Okay this means all current beta users must update with @CollinChaffin |
Wow that was fast! Thanks @MichaIng just ran it non-interactively via |
Beta v6.25.1
(29/06/19)
Changes / Improvements / Optimisations (since v6.25.0)
Bug Fixes (since v6.25.0)