From: Kelly Black <kelly.black@penguinpackets.com>
To: Linux Hams mailing list <linux-hams@vger.kernel.org>
Subject: Re: Linux AX.25 Socket programming
Date: 01 Jan 2003 20:12:39 -0600 [thread overview]
Message-ID: <1041473560.10921.9.camel@edith> (raw)
In-Reply-To: <3E13731B.C965C3A7@omeganetserv.com>
On Wed, 2003-01-01 at 17:00, Andrew Bates wrote:
> > Excellent!!! Does anybody know where I can find an example of a script
> > that is doing just this read from stdin and write to stdout.
> >
>
> Here is a very simply perl script that reads and writes to the stdin/stdout:
>
SNIP---
O.K. Thanks for the tip. Can you get the callsign or other environment
info from the environment ( $ENV ?) as well like a CGI script does.
I will probably still write the program in C though as I was impressed
at how well I was able to view a curses based application via TCP/IP
over AX.25, and was floored by its responsiveness.
One of my reasons for re-writing the existing application is to make
user training simple by providing a simple interface option instead of
just the terse command line option that exists now.
Kelly
KB0GBJ
P.S. The application I am trying to re-create will be a sub-set of
ARES-DATA. I will tailor it for tracking runners in a marathon race.
next prev parent reply other threads:[~2003-01-02 2:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 18:59 Linux AX.25 Socket programming Jonathan Naylor
2003-01-01 22:48 ` Kelly Black
2003-01-01 23:00 ` Andrew Bates
2003-01-02 2:12 ` Kelly Black [this message]
2003-01-03 0:44 ` Curt Mills, WE7U
2003-01-02 4:37 ` Tomi Manninen
2003-01-02 5:13 ` Kelly Black
2003-01-03 6:32 ` Wilbert Knol
2003-01-03 17:17 ` Tomi Manninen OH2BNS
2003-01-03 20:47 ` Wilbert Knol
2003-01-03 20:58 ` Kelly Black
2003-01-03 21:02 ` M Taylor
2003-01-03 22:26 ` Wilbert Knol
2003-01-06 9:28 ` Wilbert Knol
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=1041473560.10921.9.camel@edith \
--to=kelly.black@penguinpackets.com \
--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