From: Harold Hartley <vzeqqgj8@verizon.net>
To: vk4akm@bigpond.com
Cc: linux-hams@vger.kernel.org
Subject: Re: ax25-howto
Date: Sun, 04 Sep 2005 08:15:22 -0400 [thread overview]
Message-ID: <431AE55A.1080708@verizon.net> (raw)
In-Reply-To: <431A83F4.8060206@bigpond.com>
vk4akm wrote:
> G'day Folks
> This might be a real dumb question but how do I get ax25 to work on a
> Suse 9.3 PC.
> The AX25-Howto is a little confusing.
> I assumed with a late model Kernel the compiling a Kernel for ax25 is
> not required.
> So I stepped on to the next stage, downloaded and installed the
> appropriate rpms for libax25, ax25-tools, ax25-apps and soundmodem.
> What to do next?
>
> I have Gmfsk working fine on the PC so the soundcard radio link etc is
> working.
>
> Any help to push me in the right direction would be appreciated.
>
> 73's
> Ken
>
>
> -
> 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
>
I must agree as I have found it talks in some places about files that
are not relevent to most distro's now and in fact are very out of date.
Now with the newer files such as the ax25-config, ax25-tools and
ax25-apps, most of the how-to don't apply to the newer files and mainly
applies the the old ax25-utils and such...
I'm wondering if someone will evenually update the How-to in places that
does need some update to, but not all the How-to needs updating.
Harold
next prev parent reply other threads:[~2005-09-04 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-04 5:19 ax25-howto vk4akm
2005-09-04 12:15 ` Harold Hartley [this message]
2005-09-06 18:21 ` ax25-howto Ralf Baechle DL5RB
2005-09-07 15:14 ` ax25-howto Dave Stubbs
2005-09-07 15:13 ` ax25-howto Dave Stubbs
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=431AE55A.1080708@verizon.net \
--to=vzeqqgj8@verizon.net \
--cc=linux-hams@vger.kernel.org \
--cc=vk4akm@bigpond.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.