bedna, see - i tried your way on a raspi 3B+ with the last minimal armbian and it worked like your case like a charm - on my Win11 with putty. If you look a bit back to my post with the attached "ssh_debian.txt" - that is what I get when I use a debian as ssh client! ssh client and the odroid ssh server cannot agree on how to connect UNLESS I dumb it down as seen in the command line - and then "1234" is not accepted.. So - armbian "odroid XU4" does not behave like "raspi"!

So I need to know what I have to do to get MIDI messages into my music app that I'm working on. I developed a cli synth app on Manjaro using SDL3 and Jack. Jack I used to connect to MIDI aka 'MIDI-Bridge' or MIDI Through and an external program to produce MIDI messages sent to MIDI Through. I am currently trying to do the same on the actual device I wish to use which is the OrangePi 4 LTS I have spare with just bare bones Armbian Server, no desktop. I have audio working through Pipewire. I am used to Jack just being available because Pipewire intercepts and handles the calls behind the scenes. I noticed that on Armbian I think I have to use the 'pw-jack' program or jack-play goes into an eternal and uninterruptible error loop (I have to kill it through another terminal). Note: I am developing this program in Zig. Am I doing all of this the wrong way? Is there some system process I have to start? Or something I haven't installed?

On the other hand, openSUSE Leap 16, KDE, it is not impossible:

Armbian config is just a wrapper to system tools that are dealing with this. We only change hardware related packages, the rest is stock Debian / Ubuntu. Is this problem solved somehow in Ubuntu? Probably the core of issue is originating from here: https://www.iana.org/ "Time zone of Iceland in Africa?" https://lists.iana.org/hyperkitty/list/tz@iana.org/message/QKQ27H23CTLFGJAQXJ24IVLRLQXHRLUA/ Interesting problem ...

Thank you for the resources, and you're right, I should probably be asking a lawyer. That said, the thing that's been throwing me off is that the GPL FAQ specifically states that and uses GCC as an example. Using GCC to build a binary does not make the binary subject to GPL. It seems like there's a similarity here to armbian/build which is a tool that produces an artifact and the code within customize-image.sh is my own code. This question really came up for me when I was modifying a DTS file to disable a peripheral on my device and was investigating whether that change would need to be open sourced. I found that the parent DTS file that I was patching was licensed under GPL 2.0 OR MIT, so if I'm reading everything correctly, it seems like neither the customize-image.sh script nor my DTS patches need to published and licensed under GPL 2.0. But I'm posing here in case I've egregiously misunderstood something. If there's nuance and subtlety here, where my assumptions above might be correct, or might not be depending on other factors, then I may need to get an attorney involved.