As of 20191230 a work around is being used to get the correct port number (/dev/pts/?) when direwolf starts in Buster. This port number is required to pass to kissattach for use with Pat Winlink. The workaround involves writing data to a temp file and reading that file for the port number. This produces extras read/write cycles to the SD card that are unnecessary. Correct way to read the port number is with the command
ls -l /tmp/kisstnc | awk '{print $NF}'
after direwolf has started. The original workaround was used because the symlink created by direwolf on start (/tmp/kisstnc) doesn't work and we get a permission denied. This was tested (v0.59) and reminiscence of the test are commented out in the start-pat2m script. The test was unsuccessful so I reverted back to the workaround (v0.60) until the correct solution can be implemented.
km4ack
commented
4 years ago
As of 20191230 a work around is being used to get the correct port number (/dev/pts/?) when direwolf starts in Buster. This port number is required to pass to kissattach for use with Pat Winlink. The workaround involves writing data to a temp file and reading that file for the port number. This produces extras read/write cycles to the SD card that are unnecessary. Correct way to read the port number is with the command ls -l /tmp/kisstnc | awk '{print $NF}' after direwolf has started. The original workaround was used because the symlink created by direwolf on start (/tmp/kisstnc) doesn't work and we get a permission denied. This was tested (v0.59) and reminiscence of the test are commented out in the start-pat2m script. The test was unsuccessful so I reverted back to the workaround (v0.60) until the correct solution can be implemented.