All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ranch <linux-hams@trinnet.net>
To: Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: Looking for any active Linpac (Linux based AX.25 Packet radio terminal) users
Date: Thu, 20 Sep 2012 23:37:42 -0700	[thread overview]
Message-ID: <505C0B36.1010904@trinnet.net> (raw)
In-Reply-To: <505ACB55.60705@kth.se>


Hello Bjorn,

Centos6 comes with a 2.6.32 kernel and I'm currently running a 3.5.2 
kernel.  I have a friend, KJ6YWD who is running Linpac with Soundmodem 
with great results.

No, soundmodem isn't integrated but in classic Linux fashion, it 
shouldn't be.


I  have BOTH versions compiling.  The only Ncurses-only 0.17pre3 works 
very well (though is has some minor bugs).  It's the 1.0pre3 server 
version either with the Ncurses or Java client that I'm currently having 
issues with.  I've captured the issue straces here:

    http://www.trinityos.com/SCRATCH/Linpac/


If you're interested if giving Linpac a try, use my previously mentioned 
patches though they assume the use of compatibility libraries: 
compat-gcc-34-c++

I understand that the vector.h errors should be avoidable w/o those 
compatibility libraries and one of my posted patch files is supposed to 
rectify the compile errors (commented out in the SPEC file). 
Unfortunately, my patches for all this must be incomplete.  I'd love to 
have someone set me strait so I can remove those compatibility libs.

--David

On 09/20/2012 12:52 AM, Bjorn Pehrson wrote:
> Hi,
> What about proceeding to the 2.6 kernel and integrating soundmodem or
> has that already happened?
> best wishes
> Bjorn/SA0BXI
>
> On 2012-09-20 07:46, David Ranch wrote:
>> Hello Everyone,
>>
>> I was curious if there are any active Linpac users here on the list. I
>> (somewhat) recently took over the project from the previous author and
>> have things working for my uses. I wanted to see what else active
>> packet users would like to see from this project. I'm also curious
>> what versions of code people are using if it's the Ncurses interface
>> or the Java interface.
>>
>> http://linpac.sourceforge.net/
>>
>> Linpac is a fantastic AX.25 terminal program and is very feature rich.
>> It supports multiple concurrent connections, easy Unproto (UI)
>> traffic, local email and FBB forwarding, etc. It's currently working
>> on Centos5/6 and Ubuntu so far and I'm looking for any and all help
>> from people who know aspects of:
>>
>> - C++, Autoconf/Automake, socket programming, Ncurses, Java
>> - testers
>> - documentation
>>
>>
>> Give it a look and I have patches and .spec files ready to go:
>>
>> Patches:
>> http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/
>> SPECS:
>> http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/linpac.spec
>>
>>
>> 73s
>>
>> --David
>> KI6ZHD
>> --
>> 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
>> .
>>

      reply	other threads:[~2012-09-21  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20  5:46 Looking for any active Linpac (Linux based AX.25 Packet radio terminal) users David Ranch
2012-09-20  7:52 ` Bjorn Pehrson
2012-09-21  6:37   ` David Ranch [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=505C0B36.1010904@trinnet.net \
    --to=linux-hams@trinnet.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 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.