All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: Most "HAM" friendly distro ?
Date: Thu, 5 Jan 2006 10:46:31 +1100	[thread overview]
Message-ID: <20060104234631.GA20864@cloud.net.au> (raw)
In-Reply-To: <9923fd660601041255o4e45fd5dw572a79848c1781ff@mail.gmail.com>

On Wed, Jan 04, 2006 at 12:55:38PM -0800, Douglas Cole wrote:
> Well as most recent postings seem to indicate some distro's are less
> friendly than others for updating and changing kernels and other
> things.
> I too am using SuSE (version 10) for my desktop OS, but still have a
> separate pc running SuSE 8.2 for packet, since it is the one that
> works for me, and as has been posted on here many times, 2.6 kernel
> packet issues have been many.
> 
> So my question is, which distro' would one reccomend to someone who is
> used to using a distro' that does not require recompiling the kernel
> every time I turn around?
> 
> I was thinking maybe Kubuntu, or one of the Debian based distro's just
> for the sake of the ease with which APT makes updating/upgrading, but
> since I have not spent enough time with Debian based distro's I am not
> sure that is going to fit my needs.

How about Debian itself? 

Ham radio has been in Debian since the early days. Two past project
leaders have been hams (Bruce Perens K6BP and Bdale Garbee KB0G).

Our standard kernels include all the AX.25 drivers. We have a mailing
list debian-hams for discussion. Here's a list of radio packages
included in the 3.1 (sarge) release:

http://packages.debian.org/stable/hamradio/


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  parent reply	other threads:[~2006-01-04 23:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 20:55 Most "HAM" friendly distro ? Douglas Cole
2006-01-04 21:26 ` IT3 Stuart Blake Tener
2006-01-04 23:28   ` Alex Flinsch
2006-01-07 17:43   ` Ralf Baechle DL5RB
2006-01-04 23:09 ` Nate Bargmann
2006-01-04 23:19   ` Jeremy Utley
2006-01-05  1:31   ` Bob Nielsen
2006-01-05  2:14     ` Nate Bargmann
2006-01-04 23:46 ` Hamish Moffatt [this message]
2006-01-05  0:40   ` Douglas Cole
2006-01-06 13:15     ` Hamish Moffatt
2006-01-06 14:19       ` Margaret Leber
2006-01-06 14:26         ` Hamish Moffatt
2006-01-06 14:58       ` Douglas Cole
2006-01-06 17:11         ` K. David Prince
2006-01-06 17:58         ` Bob Nielsen
2006-01-05  0:27 ` Mike McCarthy, W1NR
2006-01-05  1:08   ` Douglas Cole
2006-01-05  1:29     ` Mike McCarthy, W1NR
2006-01-05  3:21       ` Douglas Cole
2006-01-05  4:36         ` Curt Mills
2006-01-05  7:07           ` Hamish Moffatt
2006-01-06 14:37             ` Curt, WE7U
2006-01-06 17:39               ` Bob Nielsen
2006-01-06 17:51                 ` Curt, WE7U
2006-01-07 15:03                   ` Most 'HAM' " w9ya
2006-01-06 23:27                 ` Most "HAM" " Hamish Moffatt
2006-01-07  2:10                   ` Bob Nielsen
2006-01-07  9:11                     ` Ian Haver
2006-01-07 14:10                       ` Nate Bargmann
2006-01-07 19:38                         ` Curt Mills
2006-01-07 19:19   ` Ralf Baechle DL5RB
2006-01-09 12:01 ` stephen
2006-01-09 12:41   ` Hamish Moffatt
2006-01-09 13:08   ` Nate Bargmann
  -- strict thread matches above, loose matches on Subject: below --
2006-01-05  2:26 Adam Vazquez Kb2jpd 

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=20060104234631.GA20864@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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.