hvedemelsbof

@c0rneliues very nice, i had a boot loop when usb hdd was connected, that was solved by your build. The related bananapim5 has a "patch of the patch": https://github.com/armbian/build/blob/main/patch/u-boot/v2022.10/board_bananapim5/meson64-boot-nvme-scsi-first.patch shouldn't the base patch just be changed to not prioritize USB? Am i not right, that at least for the N2+, usb boot can be achieved via SPI? Being completely new to u-boot, i also don't understand the difference between the boot.scr environment called boot_targets ( https://docs.u-boot.org/en/latest/develop/bootstd/overview.html#boot-targets ) and how that relates to what's being patched directly into the u-boot build shipped with armbian. I tried to override the boot targets to not include usb by setting the u-boot environment (in boot.cmd and then remaking the .scr file), but that had no effect. It seems like something should be fixed in the armbian release, but i'm not really sure what - would down-prioritizing usb in the armbian patch break usb booting for some?

I found this default setting in `/etc/apt/apt.conf.d/02-armbian-periodic` for apt in my armbian image for my odroid HC2: ```APT::Periodic::Enable: "0"``` I suspect many credit-card servers just chug along with default settings for years without manual upgrades (myself included until i reinstalled a fresh image the other day). Should't that be enabled by default so people can stay up to date with security updates etc.?