From: Larry Holden <kc5klm@valornet.com>
To: John Agar <dukewas3@shaw.ca>
Cc: linux-hams@vger.kernel.org
Subject: Re: Most useful/easy flavour of Linux for Ham Radio Applications
Date: Sat, 26 May 2007 19:15:27 -0500 [thread overview]
Message-ID: <4658CD9F.5070105@valornet.com> (raw)
In-Reply-To: <000001c79fd3$88056800$7802a8c0@ADMIN>
John Agar wrote:
> Hello all,
>
> It's been a long time since I checked in to this group.
>
> Have been unable to play with Linux for some time.
> As a result I'm way behind.
>
> Please - opinions on which is the best flavour of Linux for
> ham radio applications. Ease of configuration(good documentation)
> is my major concern.
>
> Thank you.
>
> 73 de John Agar
> VE4EI
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.467 / Virus Database: 269.8.0/817 - Release Date: 24/05/2007
> 4:01 PM
>
>
> -
> 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 use Slackware and compile my own packages with checkinstall.
Everything seems to work great! The list is as follows: GMFsk, Kpsk,
TWpsk, HF rtty, Qgrid, Gsat, Xlog, Grig, predict, Qsstv, TWclock,
Xastir, Xcall. Slackware is one of oldest around with plenty of
documentation. Hamshack live cd is a good way to try it. Go to
http://hamshack-hack.sourceforge.net/.
73, KC5KLM
next prev parent reply other threads:[~2007-05-27 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 20:22 Most useful/easy flavour of Linux for Ham Radio Applications John Agar
2007-05-26 21:55 ` Matti Aarnio
2007-05-27 0:32 ` Bob Nielsen
2007-05-27 3:24 ` jarmo
2007-05-27 4:45 ` Curt Mills
2007-05-27 0:15 ` Larry Holden [this message]
2007-05-27 5:22 ` w9ya
2007-05-27 11:27 ` Mike McCarthy, W1NR
2007-05-28 4:19 ` Adam Vazquez Kb2Jpd
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 19:40 John Agar
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=4658CD9F.5070105@valornet.com \
--to=kc5klm@valornet.com \
--cc=dukewas3@shaw.ca \
--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.