Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Nate Bargmann <n0nb@networksplus.net>
To: linux-hams@vger.kernel.org
Subject: Re: AO-40 Transponder Operation
Date: Fri, 4 Oct 2002 21:50:48 -0500	[thread overview]
Message-ID: <20021005025048.GK13150@localhost> (raw)
In-Reply-To: <3D9E0F5F.9070700@earthlink.net>

* jeff <wd4nmq@earthlink.net> [2002 Oct 04 20:56 -0500]:
> Actually there are hams that use Linux.

Perhaps I was a bit too sour.  I didn't intend to imply that no hams use
Linux, I intended to convey that I hoped by the end of 2002 the count
would be somewhere around 30 to 40%.  Maybe I run in the wrong crowd as
my guestimate is the percentage of those using Linux as their primary
hamshack platform to be less than 5%.  Nothing scientific, just a seat
of the pants guess based on the hams in my area.

> 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.

Excellent!  I hope that I didn't come across blaming the Linux ham coders 
for what I perceive to be a problem.  Instead I'm blaming the hams that 
*won't* even give Linux a try even on a second hard drive for whatever 
reason.  I'm blaming the hams that develop some cool piece of 
hardware/software that can only be used with Doze, although I think 
this situation is improving.

> 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.

Say this sounds neat, have I missed it?  What's it called? URL?

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

I take it echolink is similar in concept to IRLP?

> So there are hams who use Linux.

No doubt.  Just not in large enough numbers to suit me.  I'm waiting for
the day when Linux apps are the dominant demonstrations at the booths at
Dayton.  It's coming, I'm just impatient!

In the mean time I shall continue to advocate what I believe are the
advantages to running a Linux system.  I shall continue to try to
convince those that have just spent 3 days or more cleaning up after the
latest virus that I've had no such issues in the past 4 and 1/2 years.
In the same vein I shall continue to appeal the average ham's sense of
frugality by emphasizing that a Linux system isn't as resource intensive
as later MS-ware thus shortening the upgrade cycle of the hamshack
computer.  When someone decides to take the plunge I'll do my best to
help.

BTW, thanks for your efforts and the source code.

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0nb@networksplus.net               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamomoto

  reply	other threads:[~2002-10-05  2:50 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
2002-10-05  2:50           ` Nate Bargmann [this message]
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=20021005025048.GK13150@localhost \
    --to=n0nb@networksplus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox