On 2019-06-10, Gene Heskett <ghesk...@shentel.net> wrote: >> >> Maybe >> >> sudo systemctl stop serial-getty@ttyS0.service >> >> if you haven't already tried it. > > No, after a reboot, I don't need to. > > minicom is working, sorta. Theres enough diffs in the protocol to > call "working" by a rather fuzzy definition. But at least /dev/ttyS0 is > now available for MY use. That was the squawk. I still have not found > where the previous boot, to the same kernel/etc might have decided to > grab /dev/ttyS0 for its own use. The previous boot did send 7 or 8 bytes > of data that was just random line noise to the legacy machine on the > receiving end that cable. Other than that, I'm still clueless.
Well, Michael Stone's guess was a good one (though, apparently, wrong). Of course, you don't show any logs so it's anybody's guess. Here's another: modemmanager probing ttyS0 trying to identify a modem. Probably not, though. Anyway, it's working, which is enough for some of us in this crazy old world. > If I were to file a bug, it would be against java's current (stretch) > jre. It has no backward compatibility with the wheezy version and has > broken another utility we use so badly that the majority of it has now > been re-written in pypy. So we at least have the function, if not > the "purty" we had with the wheezy version of the jre. The purty will be > improved I am sure. The pypy effort is quite young yet. > >> >> > Thanks all; >> > >> > Cheers, Gene Heskett > > > Cheers, Gene Heskett -- “Decisions are never really made – at best they manage to emerge, from a chaos of peeves, whims, hallucinations and all around assholery.” – Thomas Pynchon