To whom it may concern.
As some issues lately discussed on both lists evidently show, there is not to much attention paid to REAL PURITY of all, or at lest some linux config files, in particular axports file.
It is CRUCIAL, that axports file: - CAN NOT contain ANY EMPTY line at all! If additional space is necessary between lines then usual spaceholder "#" is fine, - CAN NOT contain ^M (CR - in hex 0x0D) code at the end of any line!
NOT RESPECTING above two rules may result in unpredictable behavior of many AMPRNet software, not to mention FBB BBS, URONode.
Presence of ^M (CR) code can be viewed and corrected, for instance, in Midnight Commander, VI and well known Emacs editors.
From the other hand, simple and friendly editors
like nano and joe, apparently are useless...
There are few nifty tools that may one use for removing ^M characters, even from bunch of files without editing. Best known is dos2unix available for all linux like distros.
Best regards _____ Tom - SP2L (ex sp2lob) __________________________ Send from Sony Xperia Z1 http://aqua-mail.com
Being a ^M "offender" I can tell you that the ax.25 and Uronode and axMailFax software have no issues with said ^M characters in the axports file. The blank line issue has been well known for years but to my recollection, only for NetROM's nrports file. I (until yesterday) had a blank end line on my axports file to no detriment.
Tom thank you for following your hunch, and hopefully we can get that documented for the "fbb" script for us newby types.
Mitch