* First login: create docker group and add normal user to it
* Update packages/bsp/common/usr/lib/armbian/armbian-firstlogin
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
* armbian-install: set `rootfstype` when installing with MTD flash boot
* armbian-install: add check for btrfs-progs
* Ensure `rootfstype` is set in the MTD boot scenario
* Change exit code to 12 when the user denies installing btrfs-progs
* Check for `mkfs.btrfs` instead of `btrfs`
* run debian noninteractive
* Check for mkfs.btrfs even after running the apt-get commands
Currently, WLAN DHCP is only enabled when the value of
PRESET_NET_USE_STATIC is explicitly set to 0. It is not enabled when
this configuration is uncommented or omitted. This change adjusts the
behavior so that DHCP is enabled by default unless a static network
configuration is used.
Signed-off-by: Marcello Sylvester Bauer <marcello.bauer@9elements.com>
fix: /usr/lib/armbian/armbian-firstlogin: line 406:
break: only meaningful in a `for', `while', or `until' loop
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com>
While it is unusual to run both NetworkManager and systemd-networkd
simultaneiously and doing so can cause startup problems, there is
nothing inherently wrong with doing so: the services are not
incompatible and some people run both, each managing different
interfaces.
The Armbian build framework enables one or the other but not both.
Therefore, if both are enabled at first login, it is probably because
the user has manually modified the image. In this case, trust that the
user knows what they are doing and don't disable one of them.
NetworkManager and systemd-networkd should never both be enabled
at the same time. In this case, disable systemd-networkd, with
message to the user that this is being done.
Avoid waiting for the NetworkManager-wait-online or
systemd-networkd-wait-online service to complete in the midst of
prompting for root account password.
Scanning accesspoints requires an activated wifi device.
Networkd does not activate it (only NetworkManager does so).
As a result, firstlogin is not able to configure and use wifi on minimal
images, as only Server and Desktop images have NetworkManeger installed.
Activating the wifi device using "ip link set ${WIFI_DEVICE} up" before
scanning fixes this.
(And can safely be done - there is no problem activating it multiple
times, as it is the case with NetworkManager installed.)
* Add a list of BASH shell aliases and merge them with ohmyZSH aliases
* Add command armbian-upgrade to the BSP which executes update + upgrade
* Display armbian-upgrade only if there are upgrades
* Generate empty folder where will store data. This doesn't exists at early start
* Move armbian-install to /usr/bin and autoexecute sudo
