From: Ray Wells <vk2tv@exemail.com.au>
To: Michael Taylor <mctaylor@mctaylor.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: ax25-tools and apps
Date: Mon, 26 Jan 2009 17:02:21 +1100 [thread overview]
Message-ID: <497D51ED.40909@exemail.com.au> (raw)
In-Reply-To: <20090126001955.GA78660@mctaylor.blacknosugar.com>
Michael Taylor wrote:
> On Sun, Jan 18, 2009 at 01:50:34PM -0800, Ken Koster wrote:
>
>> So just where are the official sources for ax25-tools and ax25-apps?
>>
>
> As a previous developer (that is a minor contributor) for the linux
> ax25 software, I am sorry that the issue has been more confusing than
> it ought to be. I have not been running any AX.25 software since about
> 2003 and don't have an active station to test and evaluate development
> and patch submissions.
>
> Hopefully we can all contribute to moving the linux-ax25 software and
> community forward in a productive manner.
>
> Michael, VE3TIX (ex-VE1MCT)
> --
> 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
>
>
If I may be permitted to make a comment or two as a long time ax25 user.
My bbs has been using ax25 continuously since 1999. I still have six
ax25 radio ports, use axudp links, and handle telnet, rose, netrom and
garden variety ax25 on a system that has a bbs, node, and aprs HF and
VHF Igate. By today's packet standards it is a big system.
As a user rather than a programmer or developer, I consider myself
unqualified to lodge bug reports because my in-depth knowledge of the
"inner workings" is insufficient for me to reach a logical conclusion.
What may appear as a bug may be operator error. I always compile kernel
ax25, but I know my limitations, even though I push them.
As a user of ax25, however, I am not alone, being one of a considerable
number of bbs stations in France, the United States and Australia. There
may be others outside of "my" circle. Every bbs with which I forward
uses ax25. We all use fpacnode (from f6fbb) which is based on Linuxnode,
but containing considerable improvements for handling Rose protocol.
fpacnode also handles Netrom in an almost identical manner to Linuxnode.
What started out as an fpac mailing list seems to have collapsed to just
four of us exchanging emails.
Bernard f6bvp has taken over ongoing maintenance of xfbb (minor fixes)
and fpac (good improvements and fixes). Bernard has also released
patches for kernel ax25 and kernel Rose. The email group of four
previously mentioned, tend to be beta testers for Bernard's work.
I wonder how many ax25 users (and potential users) there are who aren't
in the know, and who plod away with broken code, or just give up?
As old as ax25 is, I remain optimistic that it will still be in use for
many years to come, and I would like to see a return to a coordinated
approach to maintaining the code.
Am I of any value as a beta tester beyond my current circle for those
developers who don't have test facilities? I don't know, but I do run a
number of Linux systems with kernel ax25, so setting up for testing
something I currently don't use ( axspawn, e.g.) is totally possible, if
it's of any use and it advances the cause.
Ray vk2tv
prev parent reply other threads:[~2009-01-26 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 21:50 ax25-tools and apps Ken Koster
2009-01-20 14:59 ` Pidoux
2009-01-20 18:17 ` Curt, WE7U
2009-01-20 18:24 ` Nate Bargmann
2009-01-20 19:08 ` Curt, WE7U
2009-01-28 16:10 ` Robert Steinhäußer
2009-01-26 0:19 ` Michael Taylor
2009-01-26 6:02 ` Ray Wells [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=497D51ED.40909@exemail.com.au \
--to=vk2tv@exemail.com.au \
--cc=linux-hams@vger.kernel.org \
--cc=mctaylor@mctaylor.com \
/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.