From: Damien Gardner Jnr <rendrag@rendrag.net>
To: "Wesley J. Landaker" <wjl@icecavern.net>
Cc: debian-hams@lists.debian.org,
Patrick Ouellette <pat@flying-gecko.net>,
linux-hams@vger.kernel.org
Subject: Re: AX25 and related software's future in Debian
Date: Thu, 24 May 2012 08:48:46 +1000 [thread overview]
Message-ID: <4FBD694E.3040903@rendrag.net> (raw)
In-Reply-To: <201205231215.27327.wjl@icecavern.net>
On 24/05/2012 4:15 AM, Wesley J. Landaker wrote:
> About ham radio software in general, I do use a lot of other ham radio
> software packaged in Debian. In general I'm surprised that there isn't
> more overlap between the ham radio and free/open-source software
> communities. - W5OSS
While I live and breath Debian, and have spent probably 90% of the time
since I was introduced to Debian in 1998, with it on the desktop, my
most recent personal machine runs Win 7. I used to have a macbook pro
17" running debian as my 'work' machine, and a little portege running
debian as my 'ham machine' when I was out and about..
But now that I'm married with kids, when I finally manage to get out, I
don't want to have to make sure batteries are charged, that the latest
apt-get upgrade hasn't killed my favourite apps, and that the firmware
for my wireless card hasn't been removed from the repository and killed
my ability to get on the 'net, or any other mucking about.. - I want to
just open up my go-bag, plug in the USB cable to the hub, fire up HRD,
and spend my hour chatting to folk on psk31, not messing with my OS :)
Cheers,
DG
--
Damien Gardner Jnr
VK2TDG. Dip EE. GradIEAust
rendrag@rendrag.net - http://www.rendrag.net/
--
We rode on the winds of the rising storm,
We ran to the sounds of thunder.
We danced among the lightning bolts,
and tore the world asunder
next prev parent reply other threads:[~2012-05-23 22:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 1:32 AX25 and related software's future in Debian Patrick Ouellette
2012-05-04 1:46 ` Dave Platt
2012-05-04 2:10 ` Patrick Ouellette
2012-05-04 1:53 ` Kamal Mostafa
2012-05-04 2:03 ` Charles Suprin
2012-05-04 2:17 ` Patrick Ouellette
2012-05-04 2:20 ` Alejandro Santos
2012-05-04 5:20 ` Kim, VK5FJ
2012-05-04 14:34 ` Patrick Ouellette
2012-05-04 14:06 ` Dan Smith
2012-05-04 15:14 ` Patrick Ouellette
2012-05-04 15:35 ` Dan Smith
2012-05-04 16:28 ` Steve Kostecke
2012-05-04 16:57 ` Patrick Ouellette
2012-05-04 17:50 ` Bill Vodall
2012-05-04 18:06 ` Patrick Ouellette
2012-05-04 18:32 ` Dan Smith
2012-05-04 18:49 ` Patrick Ouellette
2012-05-04 19:01 ` Dan Smith
2012-05-04 19:31 ` Patrick Ouellette
2012-05-04 22:52 ` Damien Gardner Jnr
[not found] ` <CAPSBm51zYFpfPa0Rqvjemv4KGh-NQfFmFTcW07B8KzpTK_E8bw@mail.gmail.com>
2012-05-05 3:00 ` Kris Kirby
2012-05-05 13:33 ` Thomas Osterried
2012-05-23 18:15 ` Wesley J. Landaker
2012-05-23 20:38 ` Nate Bargmann
2012-05-23 22:48 ` Damien Gardner Jnr [this message]
2012-05-24 12:18 ` C.J. Adams-Collier
2012-05-24 12:33 ` IT1 Stuart Blake Tener, USNR
2012-05-24 23:05 ` Marius Petrescu
2012-05-24 23:29 ` IT1 Stuart Blake Tener, USNR
2012-05-25 0:02 ` Marius Petrescu
2012-05-25 0:04 ` Marius Petrescu
2012-05-25 0:56 ` Bob Nielsen
2012-05-25 1:46 ` Nate Bargmann
[not found] <S1754044Ab2EQTsl/20120517194841Z+66@vger.kernel.org>
2012-05-17 20:03 ` Charles Boling (AD7UF)
2012-05-17 20:25 ` John Goerzen
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=4FBD694E.3040903@rendrag.net \
--to=rendrag@rendrag.net \
--cc=debian-hams@lists.debian.org \
--cc=linux-hams@vger.kernel.org \
--cc=pat@flying-gecko.net \
--cc=wjl@icecavern.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