From: Chuck Gelm <nc8q@gelm.net>
To: linux-hams@vger.kernel.org
Subject: Re: Writing AX.25 Server Progie
Date: Tue, 31 Dec 2002 18:13:53 -0500 [thread overview]
Message-ID: <3E1224B1.EF59C889@gelm.net> (raw)
In-Reply-To: Pine.LNX.4.33.0212310828290.8587-100000@wapiti.tc.fluke.com
Howdy, Y'all:
IMHO, from what I can tell after subscribing to the Xastir list
for several weeks, is that
the code is development or prototype rather than
stable.
HTH, Chuck
"Curt Mills, WE7U" wrote:
>
> On Tue, 31 Dec 2002, M Taylor wrote:
>
> > On Sun, Dec 29, 2002 at 12:07:02AM -0600, Kelly Black wrote:
> > > I was wondering if anybody could point me to other sources of socket
> > > programming for AX.25 that are up to date as far as keeping pace with
> > > the libax25 and coding conventions.
> > >
> > > I have to admit that I have never written a C program that used sockets
> > > before, but wish to give it a go.
> > >
> > > Sketchy details of the end product:
> > > Replacement of ARES/Data program used for the Twin Cities Marathon in
> > > Minnesota. I would like to write a program to be more tailored to this
> >
> > I would look at some of the APRS software, I think there is some simple
> > clients/servers which should be less "strange" than the utilities
> > and low-level applications than come with the stock ax25-tools and ax25-apps.
>
> Like Xastir? That's the
(under development)
> APRS app that's written in C and runs on
> Unix/Linux/Mac OSX (so far). I think most of the socket stuff is in
> interface.c. I've been told that the way we do an AX.25 receive is
> not the most efficient, but it works. Something about that we can
> get all packets for all interfaces from the one call, but the way we
> do it we're separating the packets for each interface and throwing
> away the rest? Details are fuzzy.
>
> Anyway, it's
(under development)
> working code, and constantly being maintained.
>
> If your application is GPL'ed, you can use pieces of the code
> directly:
>
> http://www.xastir.org
>
> Go to Sourceforge project page/CVS/Browse CVS Repository to get to
> the individual files, or snag the whole thing via CVS or a file
> download. Stick to the development releases if you grab a file.
> They run MUCH better than the last "stable" release.
>
> --
> Curt Mills, WE7U hacker_NO_SPAM_@tc.fluke.com
> Senior Methods Engineer/SysAdmin
> "Lotto: A tax on people who are bad at math!"
> "Windows: Microsoft's tax on computer illiterates!" -- WE7U
> "The world DOES revolve around me: I picked the coordinate system!"
next prev parent reply other threads:[~2002-12-31 23:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 6:07 Writing AX.25 Server Progie Kelly Black
2002-12-31 2:31 ` M Taylor
2002-12-31 16:35 ` Curt Mills, WE7U
2002-12-31 19:02 ` Kelly Black
2002-12-31 23:13 ` Chuck Gelm [this message]
2002-12-31 23:43 ` Curt Mills, WE7U
2003-01-01 17:45 ` Chuck Gelm
2003-01-02 19:02 ` Curt Mills, WE7U
2003-01-02 19:13 ` John Ackermann N8UR
2003-01-02 19:33 ` Curt Mills, WE7U
2003-01-02 19:15 ` John Ackermann N8UR
2003-01-02 21:38 ` Xastir.lsm ?; was " Chuck Gelm
2003-01-02 21:59 ` Curt Mills, WE7U
2003-01-02 22:30 ` Xastir.lsm ? Chuck Gelm
2003-01-02 22:58 ` Curt Mills, WE7U
2003-01-01 7:30 ` Writing AX.25 Server Progie Wilbert Knol
2003-01-01 16:29 ` Kelly Black
2003-01-06 3:02 ` Dennis Boone
2003-01-06 3:39 ` Kelly Black
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=3E1224B1.EF59C889@gelm.net \
--to=nc8q@gelm.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