[nos-bbs] rsync

kd6oat kd6oat at gmail.com
Sat Nov 30 01:10:01 EST 2013


Thank you Bob.


On Fri, Nov 29, 2013 at 9:35 PM, Bob Tenty <bobtenty at gmail.com> wrote:

>  That is also to answer KD6OAT's question
>
> This was a leftover previous the B1F forwarding changes Maiko issued a
> week ago or so.
>
> Read the comment under #ifdef DONT_COMPILE (line 167)  in mboxmail.c
> A session with FBB was terminated under certain circumstances as Jnos
> couldn't handle B1F forwarding
> yet and was terminated and you received a message about that in the
> log.(B1F not supported yet)
>
> But now Jnos is B1F capable on reception so that old code snipped may
> interfere.
>
> So yes, you should rsync.
>
> 73,
>
> Bob VE3TOK
>
>
> On 13-11-29 08:52 PM, Michael E. Fox - N6MEF wrote:
>
>  Bob,
>
>
>
> Under what conditions will this have any effect on us?  For example, only
> if we have “#define …”?
>
>
>
> Thanks,
>
> Michael
>
>
>
>
>
> *From:* nos-bbs-bounces at tapr.org [mailto:nos-bbs-bounces at tapr.org<nos-bbs-bounces at tapr.org>]
> *On Behalf Of *Bob Tenty
> *Sent:* Friday, November 29, 2013 1:48 PM
> *To:* TAPR xNOS Mailing List
> *Subject:* [nos-bbs] rsync
>
>
>
> Maiko has issued an updated "mboxmail.c" source file as it was missing an
> preprocessor directive with the effect that some left over code about B1F
> was still compiled in.
>
> rsync with:
>
> rsync -av www.langelaar.net::jnosX  <destination directory>
>
> Enjoy,
>
> Bob VE3TOK
>
>
> _______________________________________________
> nos-bbs mailing listnos-bbs at tapr.orghttp://www.tapr.org/mailman/listinfo/nos-bbs
>
>
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20131129/af5237c4/attachment.html>


More information about the nos-bbs mailing list