It says create a file in /boot/efi called ssh. I did this, but it did not enable ssh.
I then found some docs saying that the file should actually go in /boot. I tried this, this didn’t work either.
Finally, I saw the post at the end of that thread that said to create /boot/custom.toml with the configuration needed to create a user and enable ssh. I tried this also, and this didn’t work.
For each attempt, I confirmed that the system responds to ping but port 22 isn’t open.
How do I actually enable sshd on boot? I have spent several days on this and apparently nothing works.
My only thought is to connect a monitor and keyboard in order to install ssh on the Debian image. Apparently the ROC-3328 doesn’t have a console TTY enabled by default, which would be my own first choice. But it comes to the same thing in the end.
Which is so obvious that my curiousity makes me ask: why haven’t you done this already? There has to be a story here…
The issue of course is that I need an automated process for this, since I am doing this for a lot of systems at the same time. What changes can I make to the mounted filesystem after writing the image to the card to enable ssh?
Ah. Yes, you wouldn’t want to tweak them by hand even if there were a serial console. Or maybe automation talking over the serial console would work? IIRC there’s a DT overlay that enables serial console, and you could patch that in, but…
Right, patch that in to the image before churning out copies for a lot of boards. Or install sshd on the image before copying (but that leaves all the many machines with the same host keys, but that can be changed by the automated scripts and might even make running the scripts over ssh slightly simpler…).
Hah, found it. This Slipstream thing lets you run in the image through the wonders of emulation. The slipstream-examples repo is still empty. ¯_(ツ)_/¯
But it comes to the same thing in the end.