From: f6bvp <f6bvp@free.fr>
To: linux-hams <linux-hams@vger.kernel.org>
Subject: New F6FBB BBS version 7.05c05
Date: Sat, 25 Jun 2011 15:16:18 +0200 [thread overview]
Message-ID: <4E05DFA2.50800@free.fr> (raw)
In-Reply-To: <4E04175A.4000401@bigpond.net.au>
Hi,
Here is a new version of F6FBB BBS with a few changes described in
CHANGES file :
7.05c5 (F6BVP)
- Charley K4GBB asked "With todays RTC clocks and NTP servers is there
still a need to freeze the Housekeeping
process because the last check failed ?". Corrected. epurmess no more
checks the date of epurmess.res.
- "Official libax25" introduced a new feature in ax25_ntoa() function
removing SSID 0 in callsigns when present.
This has been a major source of AX.25 application programs dysfunctions.
A new local function _ax25_ntoa() is used by FBB to avoid such issues.
KNOWN BUGS under investigation
- Barry VK2AAB reported that he has a 300bd HF partner who does not want
7+ files.
However he found that "J 0" in forward file does not work. 7+ files
should not be sent.
Meanwhile sysops are encouraged to use "J 2" parameter that will limit
7+ file forward to personal data.
http://f6bvp.free.fr/logiciels/BBS-f6fbb/xd705c05-src.tar.bz2
73 de Bernard, f6bvp
Le 24/06/2011 06:49, Barry a écrit :
> Hello Paul,
> Yes 5c04 is OK I am runnig it now.
>
> Barry VK2AAB
>
> Paul Brown wrote:
>> Hello Bernard,
>>
>> I was going to set up another computer with xdfbb, but I see the
>> source for xd705b is no longer available. Is xd705c04 the best source
>> to use right now?
>>
>> Thank you
>>
>> 73, Paul - N6RME
>>
>> ----- "f6bvp" <f6bvp@free.fr> wrote:
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2011-06-25 13:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4E04175A.4000401@bigpond.net.au>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E05DFA2.50800@free.fr \
--to=f6bvp@free.fr \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox