From: Ray Wells <vk2tv@exemail.com.au>
To: "Curt, WE7U" <archer@eskimo.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Problems with ax25d/axspawn on OpenSuSE 11.0 32-bit
Date: Tue, 20 Jan 2009 09:41:54 +1100 [thread overview]
Message-ID: <497501B2.7060209@exemail.com.au> (raw)
In-Reply-To: <alpine.LNX.1.10.0901191336440.22828@wapiti2.we7u.net>
Curt, WE7U wrote:
> On Sun, 18 Jan 2009, Curt, WE7U wrote:
>
>> I saw several bugs in the AX.25 stuff yesterday/today.
>
> An update: I figured newer versions of the AX.25 bits in the SuSE
> ham repository but my update methods were not snagging them. The
> SuSE update methods need a bit of revision as neither "Online
> Update", nor "zypper ref; zypper up --type package" gets everything.
> The only method that does (thanks Ken!) is Software Management ->
> Package -> All Packages -> Update if newer version available.
>
> So... I need to repeat my on-air tests with Bob using the newer
> AX.25 modules and tools to see if any or all of the bugs reported
> are still evident. Stay tuned.
>
Are you guys familiar with the work being done by Bernard, F6BVP, on
kernel ax25 related stuff? Some of his patches have been included in
later kernels.
Bernard's source files for libax25, ax25-apps & ax25-tools are available
here
http://f6bvp.free.fr/logiciels/ax25/
Ray vk2tv
next prev parent reply other threads:[~2009-01-19 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 8:22 Problems with ax25d/axspawn on OpenSuSE 11.0 32-bit Curt, WE7U
2009-01-18 21:08 ` Ken Koster
2009-01-19 21:49 ` Curt, WE7U
2009-01-19 22:41 ` Ray Wells [this message]
2009-01-21 17:35 ` Curt, WE7U
2009-01-22 9:11 ` John Ronan
2009-01-22 16:51 ` Curt, WE7U
2009-01-23 18:19 ` Curt, WE7U
2009-01-25 6:02 ` Curt, WE7U
2009-01-25 22:33 ` Ken Koster
2009-01-26 16:51 ` Thomas Osterried
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=497501B2.7060209@exemail.com.au \
--to=vk2tv@exemail.com.au \
--cc=archer@eskimo.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 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.