linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nate Bargmann <n0nb@networksplus.net>
To: linux-hams@vger.kernel.org
Subject: Re: Most "HAM" friendly distro ?
Date: Wed, 4 Jan 2006 17:09:36 -0600	[thread overview]
Message-ID: <20060104230936.GD12936@mail.networksplus.net> (raw)
In-Reply-To: <9923fd660601041255o4e45fd5dw572a79848c1781ff@mail.gmail.com>

* Douglas Cole <doug.n7bfs@gmail.com> [2006 Jan 04 15:21 -0600]:

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

Debian seems to have a very modular kernel with most, if not all, of
the ham radio support enabled.  A number of hams are active in Debian
which helps the ham radio support, IMO.

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

Unless the Kubuntu team builds a radically different kernel, it's ham
radio support should be about equal.

> But what 2.6 kernel-based distro' really shines for use Amateur radio
> opp's at the moment ?

Check out Harv's Ham Shack.  It seems to be a ham radio oriented
distribution.

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
  Amateur radio exams; ham radio; Linux info @  | free since January 1998.
             http://www.qsl.net/n0nb/           |  "Debian, the choice of
             My Kawasaki KZ-650 SR @            |     a GNU generation!"
        http://www.networksplus.net/n0nb/       |   http://www.debian.org

  parent reply	other threads:[~2006-01-04 23:09 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 [this message]
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
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=20060104230936.GD12936@mail.networksplus.net \
    --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;
as well as URLs for NNTP newsgroup(s).