From: <w9ya@arrl.net>
To: linux-hams@vger.kernel.org
Subject: Re: YAPP server pgm - Packet File Transfer
Date: Fri, 15 Jul 2005 02:54:20 -0500 (EST) [thread overview]
Message-ID: <32962.192.168.1.116.1121414060.squirrel@gateway> (raw)
In-Reply-To: <42D6E7EA.7010000@jnos.org>
Hey Bill and the gang;
In the bad ol' days. i.e. in the first years after AX.25 made it's
appearance, I had a file server on the "duplex (ham 2m es 440) packet
network" in LA. We used a variation on the binary to ascii-text conversion
to prefilter for transfers. Worked pretty well too.
Vy 73;
Bob
w9ya
>
>> I am not sure if these programs I wrote are what the
>> original requestor wanted or not.
>
> that was me...
>
>> Here is what they do:
>> They sit on an unattended AX.25 capable file server, and users connect
>> to them and download files. If I had the upload half of
>> the program finished, they could upload files to the server also.
>
> It sounds like you are very close with the core functionality of
> what I'm looking for.
>
> My objective here is to transfer a binary file between two systems with
> packet radio.
>
> The file will be highly compressed standard Email and NNTP posts - the
> old UUCP way of doing things. I believe the existing tools allow
> setting the size of the outgoing file bundle so we'll be able to limit
> it to something like 50K which would probably be fine for most of the
> exchanges.
>
> I'd like the transfer to be very fast, aggressive and efficient. To get
> the job done as quick as possible and get out of the way. No doubt
> that FTP/TCP would be better for larger and more robust transfers but in
> this case the overhead of TCP is unacceptable.
>
> I'm attempting to keep this scheme as standard as possible by minimizing
> the value added tools. A single specialized "ax25" file copy program
> that works through the AX25 tools would be a good solution.
>
> While this is basically Linux, I'm considering the issues and
> possibilities of running this on the other OS's. (UUPC anyone?)
>
> There's sure been some interesting info presented here in the past
> couple days...
>
> 73,
> Bill - WA7NWP
>
> -
> 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
prev parent reply other threads:[~2005-07-15 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 20:10 YAPP server pgm Bob Morgan
2005-07-14 20:47 ` Tomi Manninen
2005-07-14 22:32 ` YAPP server pgm - Packet File Transfer Bill Vodall WA7NWP
2005-07-14 23:01 ` Dave Platt
2005-07-14 23:50 ` Bill Vodall WA7NWP
2005-07-15 7:54 ` w9ya [this message]
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=32962.192.168.1.116.1121414060.squirrel@gateway \
--to=w9ya@arrl.net \
--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