Does such exist.... Has anyone created..... can said code be easily separated / compiled separately.....
What I'm looking for is a "version" of nos that is devoid of any of it's networking functionality or well at least the bottom 3 layers of the OSI stack. The issue being that NOS has long been a standard and familiar interface for networked amateur radio BBS systems. I'm good with that. over the last 20+ years though we have moved to computers and operating systems that are much more capable, especially when it comes to processing speed, memory, and a decent built in network stack. I now no longer need my application (BBS) to handle the network layer stuff but simply need what amounts to a good BBS interface. can/has this functionality be/been gutted/separated out from the NOS code base such that I can end up with an application that simply is setup to listen on the proper port via init.d and present *ONLY* the familiar bbs interface while the OS handles all the networking stuff and the application not even being capable of such.
Eric
http://en.wikipedia.org/wiki/List_of_BBS_software#Unix_and_compatible
------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 http://k7ve.org/blog http://twitter.com/#!/john_hays http://www.facebook.com/john.d.hays
On Fri, Apr 11, 2014 at 10:52 PM, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Does such exist.... Has anyone created..... can said code be easily separated / compiled separately.....
What I'm looking for is a "version" of nos that is devoid of any of it's networking functionality or well at least the bottom 3 layers of the OSI stack. The issue being that NOS has long been a standard and familiar interface for networked amateur radio BBS systems. I'm good with that. over the last 20+ years though we have moved to computers and operating systems that are much more capable, especially when it comes to processing speed, memory, and a decent built in network stack. I now no longer need my application (BBS) to handle the network layer stuff but simply need what amounts to a good BBS interface. can/has this functionality be/been gutted/separated out from the NOS code base such that I can end up with an application that simply is setup to listen on the proper port via init.d and present *ONLY* the familiar bbs interface while the OS handles all the networking stuff and the application not even being capable of such.
Eric
Those are standard BBS software, not HAM related, and can not do FBB or RLI forwarding.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of K7VE - John Sent: Saturday, April 12, 2014 09:13 To: eric.fort@gmail.com; AMPRNet working group Subject: Re: [44net] NOS "versions"
(Please trim inclusions from previous messages) _______________________________________________ http://en.wikipedia.org/wiki/List_of_BBS_software#Unix_and_compatible
What I'm looking for is the familiar interface of NOS presented to the user which other packages won't do in that they provide their own ideas of how user interface ought be done and without the unneeded cruft and bloat of networking code compiled in. As for RLI & FBB BBS forwarding, are there not Daemons available that handle such functions similar to how NNTP, SMTP, & UUCP work together and function together for such tasks? For that matter other than reasons of maintaining interoperability with systems and protocols which to my knowlege are used no where else but amateur radio is support for these forwarding types so importaint? how about encouraging people to move to more widely adopted standards? Is there something that RLI/FBB do so much better?
Eric AF6EP
On Sat, Apr 12, 2014 at 7:27 AM, Marius Petrescu marius@yo2loj.ro wrote:
(Please trim inclusions from previous messages) _______________________________________________ Those are standard BBS software, not HAM related, and can not do FBB or RLI forwarding.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of K7VE
- John
Sent: Saturday, April 12, 2014 09:13 To: eric.fort@gmail.com; AMPRNet working group Subject: Re: [44net] NOS "versions"
(Please trim inclusions from previous messages) _______________________________________________ http://en.wikipedia.org/wiki/List_of_BBS_software#Unix_and_compatible
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Speaking of widely used standards: FBB forwarding IS the second most widely used standard for BBS message forwarding, since most other BBS systems have long dissappeared, their places being taken over by forums and social networks. The only surviving standard is, to my knowledge, FidoNet with about 2000 nodes. And running a citadel is a little overblown, taking in account that their interface is much more console oriented, a dumb terminal not being enough.
My opinion: If you need an AX25 connectivity, then you need something oriented towards it, like FBB, NOS or a PMS. If you want to go the fast lane set up a forum, a mail server and possibly an IRC server.
By the way: Anyone interested in reviving the old HamIRC network?
73s de Marius, YO2LOJ
On Sat, 2014-04-12 at 21:57 +0300, Marius Petrescu spake:
By the way: Anyone interested in reviving the old HamIRC network?
It'd be nice to see the original ping-pong convers system back as it was, which doesn't need any special software to use and is simple for ax25 purposes.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Brian Sent: Saturday, April 12, 2014 22:06
It'd be nice to see the original ping-pong convers system back as it was, which doesn't need any special software to use and is simple for ax25 purposes. ------------------------------
But that system is up and running. This is just a part of it:
*** Links at Hub_EU Host State Quality Software Since NextTry Tries Queue RX TX Hub_NA Connected 1s/1s saupp1.6 Apr 11 0 407K 1344K GrimstaSE Connected l 1s/1s htpp1.22 Apr 11 0 17K 1663K Timis_RO Connected l 1s/1s htpp1.22 Apr 11 356 17K 1663K CatHmA_UK Connected l 1s/1s saupp1.6 Apr 11 0 145K 1539K Krakow_PL Connected l 1s/1s saupp1.6 Apr 11 0 18K 1660K Hub_PL Connected l 1s/1s saupp1.6 Apr 11 0 94K 1592K HUB_DL Connected l 1s/1s saupp1.6 Apr 11 0 383K 1328K GDY_PL Connected l 1s/1s saupp1.6 Apr 11 0 18K 1663K Odense_DK Connected l 1s/1s saupp1.6 Apr 11 0 22K 1662K SJCCty_BR Connected l 1s/1s htpp1.26 Apr 11 0 14K 1357K DHR_NL Connected l 1s/1s saupp1.6 Apr 11 0 122K 1564K HUB_NL Connected l 1s/1s saupp1.6 Apr 11 0 179K 1510K TU_Ostrav Connected l 1s/1s saupp1.6 Apr 11 0 54K 1622K Brno_CZ Connected l 1s/1s htpp1.26 Apr 11 0 17K 1651K *** *** Links at Hub_NA Host State Quality Software Since NextTry Tries Queue RX TX SpamNet-1 Disconnected --- 18:35 21:34 970 P TACOMA Connected l 1s/1s htppu1.5 Mar 26 0 238K 22M SaltLk_US Connected l 1s/1s saupp1.6 Mar 13 0 1307K 41M Woodside Connected l 1s/1s jnos2.0j Mar 28 0 126K 19M Quebec,QC. Connected l 1s/1s tnos3.01 6:32 0 7K 681K GVCITY_US Connected l 1s/1s jnos2.0j 12:35 0 3K 353K ALWGW_US Connected l 1s/1s tnos2.42 Apr 11 0 28K 1958K Hub_EU Connected l 1s/1s saupp1.6 Apr 11 860 1344K 407K Pittsbrgh Connected l 1s/1s pp-3.12 Dec 13 0 1492K 163M bbgate_US Connected l 1s/1s jnos2.0j 12:37 0 3K 352K N2NOV Connected l 16s/1s jnos2.0j Mar 30 0 111K 17M LAXNET_US Connected l 1s/1s jnos2.0j Apr 2 0 85K 12M ***
Eric, You don't say whether you're interested in a Windows or a Linux based version but I believe the answer to both might be here: http://www.langelaar.net/projects/jnos2/
This appears to be the only "maintained" version of JNOS but I haven't looked at the code to see how deep into the stack he's getting but his dependence on winpcap indicates it still has some degree of coupling to layer 3.
Regards, Geoff Joy - ke6qh -
On Apr 11, 2014, at 22:52, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Does such exist.... Has anyone created..... can said code be easily separated / compiled separately.....
What I'm looking for is a "version" of nos that is devoid of any of it's networking functionality or well at least the bottom 3 layers of the OSI stack. The issue being that NOS has long been a standard and familiar interface for networked amateur radio BBS systems. I'm good with that. over the last 20+ years though we have moved to computers and operating systems that are much more capable, especially when it comes to processing speed, memory, and a decent built in network stack. I now no longer need my application (BBS) to handle the network layer stuff but simply need what amounts to a good BBS interface. can/has this functionality be/been gutted/separated out from the NOS code base such that I can end up with an application that simply is setup to listen on the proper port via init.d and present *ONLY* the familiar bbs interface while the OS handles all the networking stuff and the application not even being capable of such.
Eric
Probably linux/unix based but Basicly my point being that I'd like to seperate the NOS code into at least a couple different parts and compile/run only those parts necessary. the parts as I see it would be a bbs application, a mail/news gateway application that acts as a gateway between UUCP/NNTP/SMTP & FBB/RLI/MBX spools, and a network stack.
Eric
On Sat, Apr 12, 2014 at 7:59 PM, Geoff Joy geoff@windowmeister.com wrote:
Eric, You don't say whether you're interested in a Windows or a Linux based version but I believe the answer to both might be here: http://www.langelaar.net/projects/jnos2/
This appears to be the only "maintained" version of JNOS but I haven't looked at the code to see how deep into the stack he's getting but his dependence on winpcap indicates it still has some degree of coupling to layer 3.
Regards, Geoff Joy - ke6qh -
On Apr 11, 2014, at 22:52, Eric Fort eric.fort@gmail.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Does such exist.... Has anyone created..... can said code be easily separated / compiled separately.....
What I'm looking for is a "version" of nos that is devoid of any of it's networking functionality or well at least the bottom 3 layers of the OSI stack. The issue being that NOS has long been a standard and familiar interface for networked amateur radio BBS systems. I'm good with that. over the last 20+ years though we have moved to computers and operating systems that are much more capable, especially when it comes to
processing
speed, memory, and a decent built in network stack. I now no longer need my application (BBS) to handle the network layer stuff but simply need
what
amounts to a good BBS interface. can/has this functionality be/been gutted/separated out from the NOS code base such that I can end up with
an
application that simply is setup to listen on the proper port via init.d and present *ONLY* the familiar bbs interface while the OS handles all
the
networking stuff and the application not even being capable of such.
Eric
-
Brian -
Eric Fort -
Geoff Joy -
K7VE - John -
Marius Petrescu