<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
You are right on target Bill - not a purely NOS issue.<BR>
<BR>
On Thu, 2006-06-29 at 18:19 -0500, Bill Vodall wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">> > I guess I'll go on record with the BBS "Download" and "Upload" command</FONT>
<FONT COLOR="#000000">A related issue and not purely NOS but I'll throw it out here for</FONT>
<FONT COLOR="#000000">folks to consider and any possible comments... I discussed it</FONT>
<FONT COLOR="#000000">a bit on other lists last fall and haven't yet gotten back to it.</FONT>
<FONT COLOR="#000000">A "ax25cp" command to copy files between AX25 stations would be very</FONT>
<FONT COLOR="#000000">useful. The best part is that it would open up the potential of highly</FONT>
<FONT COLOR="#000000">efficient UUCP style Email on amateur systems and packet networks. </FONT>
</PRE>
</BLOCKQUOTE>
This is very much like my original "step 2" and "step 3" proposals to what I submitted as a "bug".<BR>
In talking it thru later, my opinion changed slightly away from a nos solution into a generic BBS solution.<BR>
<BR>
If many of the other bbs software supported file transfer in some form - then nos needs to get on board with them.<BR>
The file transfer is truly useful as you point out.<BR>
In the AX.25-BBS world that remains more or less "healthy", many of the (local to me) users are TNC-only equipped and without a transfer capability except to the screen as a "listing" or to/from a spool as Jay points out.<BR>
However BBS-to-BBS file transfer brings the material local and more easily shared in the neighborhood.<BR>
The issue then becomes NOS is a small proportion of all BBS servers and inter-operability is important.<BR>
<BR>
How to pull this off?<BR>
Networking?<BR>
BBS software developers would need to be on the same page - Is that a manageable issue?<BR>
<BR>
I certainly support your idea as a reasonable direction for development of AX.25.<BR>
It remains to be seen that there is enough impetus to do the work - given the alternative solutions.
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">It would also enable basic NOS-to-NOS file exchange without the overhead</FONT>
<FONT COLOR="#000000">of TCP/IP.</FONT>
<FONT COLOR="#000000">If you do have a TCP path, the FTP functionality in NOS can be</FONT>
<FONT COLOR="#000000">configured for automatic timed file transfers with the built in</FONT>
<FONT COLOR="#000000">Cron and .net (?) configuration file. It's obscure but it</FONT>
<FONT COLOR="#000000">really works well once it's set up.</FONT>
<FONT COLOR="#000000">73</FONT>
<FONT COLOR="#000000">Bill - WA7NWP</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de Skip k8rra k<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>