A bit of analysis and movement.
So we are starting up zynthian using systemd.
Now that has been an area of considerable ‘robust’ debate from my searchings.
After looking into it I like it.
It does parallel start by separating out the dependences into individual start ups.
I grasp some of the implications ( it seems to make a set of binary (machine specific) files that run the startup. This has an element of magic and it’s probably better to be explicit on implicit but.)
The config files .service etc are pretty simple and there is a nod to windows at several stages in the write up. (That really will really offend the die hard unixists … )
It’s driven from it’s command line tool
Which of course does EVERYTHING you can imagine but nothing that exactly matches your own mental image of what the system is doing …
One glaring absence is a ‘decent’ xfce based gui config tool, (unless you know better)
if Multimidicast is started directly after jack2 the service won’t start under a systemd unit
failing with a access to the udp network.
As a solution I’ve moved it after the networking.service.
Do we need these ports to start up under jack or do we simply want the in and out ports that are selected from the Env ZYNTHIAN_MIDI_NETWORK_IN_CHANNEL & ZYNTHIAN_MIDI_NETWORK_OUT_CHANNEL? to be presented and would this be done in the ‘autoconnector’ ?
I’m not sure if making it reliant on Jack2 & networking would stop the start up of a zynthian if no networking is enabled.