Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: jeff <wd4nmq@earthlink.net>
To: Nate Bargmann <n0nb@networksplus.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: AO-40 Transponder Operation
Date: Fri, 04 Oct 2002 17:59:59 -0400	[thread overview]
Message-ID: <3D9E0F5F.9070700@earthlink.net> (raw)
In-Reply-To: 20021004175512.GH13150@localhost

Actually there are hams that use Linux. I have written a couple of radio 
control programs for Kenwoods that run under Linux. One is exclusive 
Linux and the other is written in Tcl/Tk that runs under Linux, Windows, 
Mac or any system that there is a Tcl/Tk package for, and there are a 
couple of dozen systems supported.

I also wrote a APRS app under Tcl/Tk that runs under Linux/Windows that 
uses the online Tiger mapping service to draw the map and place APRS 
stations on.

I also am putting the finishing touches on a Linux echolink/ilnk app 
called echoLinux. It is alpha right now.

So there are hams who use Linux.

Nate Bargmann wrote:
> * Margaret Leber <maggie@voicenet.com> [2002 Oct 04 12:13 -0500]:
> 
>>Nonetheless, it's still a Windows virus. I'm starting to see more and 
>>more  Klez-infected messages coming from people in the ham community.
> 
> 
> Sadly, I was hoping the trend would be the other way by now as more hams
> would be using the Free OSes.  It appears this hasn't been the case.
> 
> Linux is slowly gaining more mention in the mainstream ham press.
> Somehow it seems that as a group hams pretend to be on the cutting edge
> of technology.  Most, however, are content to wallow in their current 
> comfort zone.
> 
> I've advocated Linux for the past few years and have found very few
> takers.  Even with standing offers of help to other hams with getting 
> a Linux system going, I'm met with hams wanting help with their Doze 
> machine, which I won't do.
> 
> I've come to the conclusion that the only way a majority of hams will
> give Linux a try is for some cool new mode of communications ala PSK31
> would be available on Linux first and that a Doze version would be
> non-existant.  Unfortunately, it's been working the other way around.
> 
> I'm glad Jonathan took on developing a WSJ app for Linux.  This is a
> seriously cool mode, as I understand it, and a lack of a similar
> capability puts my hamming at a severe disadvantage if I want to run the
> latest ham tech.  The Gate's Tax is not welcome in my life and I will do
> without before installing his bits on my machines.
> 
> Sigh...Off my soapbox now.
> 
> 73, de Nate >>
> 



-- 
Jeff, wd4nmq
wd4nmq@earthlink.net
http://home.earthlink.net/~wd4nmq
iLink client node #10438, iLink sysop link node #14746


  reply	other threads:[~2002-10-04 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021004040843Z261464-8740+5907@vger.kernel.org>
2002-10-04  4:47 ` AO-40 Transponder Operation Brett Mueller
2002-10-04  6:58   ` Craig Small
2002-10-04  7:28     ` Jean-Paul ROUBELAT
2002-10-04 10:57       ` Virus Warning (was: Re: AO-40 Transponder Operation) Cees Tool
2002-10-04 12:16     ` AO-40 Transponder Operation Margaret Leber
2002-10-04 12:28       ` Margaret Leber
2002-10-04 17:55       ` Nate Bargmann
2002-10-04 21:59         ` jeff [this message]
2002-10-05  2:50           ` Nate Bargmann
2002-10-07 16:51             ` Curt Mills, WE7U
2002-10-07 21:41               ` Chuck Gelm
2002-10-08  1:57                 ` Nate Bargmann

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=3D9E0F5F.9070700@earthlink.net \
    --to=wd4nmq@earthlink.net \
    --cc=linux-hams@vger.kernel.org \
    --cc=n0nb@networksplus.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox