TIP: Click on subject to list as thread! ANSI
echo: mbse
to: RJ Clay
from: Andrew Leary
date: 2015-05-29 19:40:14
subject: MBSE 1.0.5 archive

Hello RJ!

28 May 15 10:09, you wrote to me:

 AL>> 1.0.5 is still a work in progress; that's why I haven't committed
 AL>> it to the Sourceforge Hg repository yet.

 RC>    Ah, I'd wondered;  I'm used to seeing a post about releases but I
 RC> thought perhaps I'd missed something...

When a release happens, it will be posted here and on SourceForge.

 AL>>   I gave a copy to Sean Dennis for his use in setting up his new
 AL>> BBS, and he shared it in his DropBox.

 RC>   So that's how Michael Ryan got ahold of it...

 AL>>   1.0.5 should be considered alpha/beta code, and not for
 AL>> production use.  Once I am finished with the work in progress, I
 AL>> will probably commit the changes as 1.0.6 to avoid confusion.

 RC>   That might be a good idea...

It should help avoid confusion, especially with the extra source code 
repository that was set up.

 AL>>   At that time, I will gladly send you the source archive for
 AL>> your Debian packaging efforts.

 RC>   I appreciate that but it's not entirely nececceary if a copy is
 RC> hatched out and/or put online at SF. (I don't recall who put the
 RC> v1.0.4 archive online at SF?)  Now that the Hg to Git import is
 RC> working well (using

I uploaded the archive to SourceForge when 1.0.4 was released.

 AL>> That being said, anyone who has downloaded 1.0.5 should not
 AL>> notice any issues as long as they don't attempt to specify a
 AL>> literal IPv6 address as the hostname for a node they connect to.
 AL>> mbcico currently only supports IPv6 connections to hosts that a
 AL>> DNS lookup returns an AAAA record for.

 RC>   I've also been wondering about that.  I'm planning to set up a new
 RC> system, in part for testing IPv6 (on Debian 8, where I've not been
 RC> able to get a manual compile to work yet...), so I've been thinking
 RC> about what I'll need to do for it's configuration and what I'll need
 RC> to add for DNS.

Are you running your own DNS servers, or are you using a provider?  Most 
providers at this point offer some degree of IPv6 support.  I'm currently 
using the free DNS offering at he.net with no issues.  DynDNS does offer IPv6 
support also, albeit only with a paid account.

Regards,

Andrew

--- GoldED+/LNX 1.1.5-b20130910
* Origin: Phoenix BBS * phoenix.bnbbbs.net:2323 (1:320/219)
SEEN-BY: 19/33 34/999 90/1 116/18 120/331 123/500 128/187 135/364 140/1
SEEN-BY: 218/700 226/0 160 230/150 240/1120 249/303 250/1 261/38 100 266/404
SEEN-BY: 267/155 280/464 282/1031 1056 292/907 908 320/119 340/400 393/68
SEEN-BY: 396/45 633/267 280 640/384 712/620 848 770/1 801/161
@PATH: 320/219 119 261/38 712/848 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.