From: Chuck Hast <wchast@gmail.com>
To: Bill - WA7NWP <wa7nwp@jnos.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: YAPP File Transfer with Linux
Date: Tue, 12 Jul 2005 19:56:36 -0400 [thread overview]
Message-ID: <620c9057050712165657e8e0c8@mail.gmail.com> (raw)
In-Reply-To: <42D43E41.8060901@jnos.org>
On 7/12/05, Bill - WA7NWP <wa7nwp@jnos.org> wrote:
>
> > So what you seem to be looking for are tools that send and receive
> > files using just AX.25. 'ax25send filename ve3tix' and
> > 'ax25receive' running on the listening ("server") side.
> >
> > I don't know of anything, but it wouldn't be that hard to write.
>
> Exactly. Maybe a bit more then that if we have some scripting
> to navigate the connections through the nodes and digis. That
> wouldn't even be needed as we might be able to use Expect.
>
> YAPP and the files Curt found might be a good starting place. Tieing
> it through the AX25 system could be a bit tricky. Also hopefully
> it doesn't have any extraneous overhead.
>
> > Maybe if I find some free time.
>
> It would be appreciated. I'm in a good situation here for a while
> with access to a parallel Linux box across town. That makes it
> easy to experiment and test new techniques.
>
> > -ve3tix
Folks, I have not used it my self, but some of the fellows who maintain
our FPAC network in Florida use YAPP to update the files on the switches.
FPAC has YAPP built in, we use it with either one of the yapp programs
of automated uploading using f6fbb BBS.
The move to fpac Linux on our network brings up the question of using
other more efficient modes of sending files, so anything that will work
better is most certainly welcome.
--
Chuck Hast
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."
next prev parent reply other threads:[~2005-07-12 23:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 8:21 [PATCH] First cut of PR430 / extended 6pack driver Ralf Baechle DL5RB
2005-07-11 21:59 ` YAPP File Transfer with Linux Bill Vodall WA7NWP
2005-07-11 22:06 ` Curt, WE7U
2005-07-11 22:12 ` Curt, WE7U
2005-07-12 11:42 ` Rodolfo Brasnarof
2005-07-12 14:13 ` Bill Vodall
2005-07-12 14:21 ` Digi-ned output file and logrotate Bill Vodall
2005-07-12 15:24 ` Jim Bayer
2005-07-12 14:56 ` YAPP File Transfer with Linux Bob Nielsen
2005-07-12 14:55 ` Bill Vodall
2005-07-12 15:28 ` Bob Nielsen
2005-07-12 17:05 ` Bill Vodall
2005-07-12 18:07 ` Robert Eliassen
2005-07-12 18:51 ` Jeremy Utley
2005-07-12 19:11 ` Bill Vodall WA7NWP
2005-07-13 7:53 ` Robert Eliassen
2005-07-13 11:03 ` Tomi Manninen
2005-07-13 14:41 ` Chuck Hast
2005-07-13 17:51 ` Dave Platt
2005-07-14 0:19 ` Bob Nielsen
2005-07-12 20:51 ` Michael Taylor
2005-07-12 22:03 ` Bill - WA7NWP
2005-07-12 23:56 ` Chuck Hast [this message]
2005-07-12 15:13 ` Robert Eliassen
2005-07-12 15:22 ` SSH and the NONE option Bill Vodall
2005-07-12 16:55 ` Ralf Baechle DL5RB
2005-07-12 17:02 ` Bill Vodall
2005-07-12 18:04 ` Jonathan Lassoff
2005-07-12 19:08 ` Bill Vodall WA7NWP
2005-07-12 20:00 ` Jim Bayer
2005-07-12 20:43 ` Michael Taylor
2005-07-12 20:41 ` Michael Taylor
2005-07-12 21:57 ` Bill - WA7NWP
2005-07-12 22:19 ` Dennis Boone
2005-07-14 7:59 ` Ralf Baechle DL5RB
2005-07-14 9:47 ` Per Crusefalk
2005-07-14 14:53 ` Jim Bayer
2005-07-14 15:12 ` Andrew Bates
2005-07-14 17:01 ` Dave Platt
2005-07-14 15:27 ` Bob Snyder
2005-07-14 16:28 ` Jonathan Lassoff
2005-07-14 19:02 ` Bob Snyder
2005-07-14 19:28 ` Curt, WE7U
2005-07-14 20:43 ` Bob Snyder
2005-07-30 1:31 ` SSH and the NONE option - more Bill - WA7NWP
2005-07-30 8:19 ` Robert Snyder
2005-08-01 11:34 ` Ralf Baechle DL5RB
2005-08-02 13:20 ` Bill Vodall
2005-07-14 19:51 ` SSH and the NONE option Andrew Bates
2005-07-14 16:01 ` Ralf Baechle DL5RB
2005-07-16 9:28 ` Arno Verhoeven - PE1ICQ
2005-07-13 12:39 ` YAPP File Transfer with Linux Rodolfo Brasnarof
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=620c9057050712165657e8e0c8@mail.gmail.com \
--to=wchast@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=wa7nwp@jnos.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.