From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>
Cc: 'Douglas Cole' <doug.n7bfs@gmail.com>, linux-hams@vger.kernel.org
Subject: Re: Most "HAM" friendly distro ?
Date: Sat, 7 Jan 2006 20:19:51 +0100 [thread overview]
Message-ID: <20060107191951.GB756@linux-mips.org> (raw)
In-Reply-To: <000b01c6118e$e1b128f0$3849a8c0@lan.w1nr.net>
On Wed, Jan 04, 2006 at 07:27:59PM -0500, Mike McCarthy, W1NR wrote:
> I still see SuSE as very ham friendly. The problem with the AX25 drivers is
> the 2.6.13 kernel across ALL distros. SuSE 10.0 just happens to have the
> broken one and unless the maintainer gets the fixes into the global 2.6.13
> update, all distros using it will remain broken. 10.1 should "hopefully"
> fix the problem with the 2.6.15 kernel.
>
> Since 9.3, SuSE has started removing some software from the CD's. The ham
> software was one of the packages they decided to take out. That does not
> mean they are not available. Just point an installation source at any of
> the mirrors that have the "projects/ham" directory and you get all of the
> ham radio packages. If you want java, extra perl libraries and much of what
> used to fit on a single DVD but doesn't any more, the ftp mirrors have the
> packages available and can be installed and maintained through YaST by
> adding installation sources. AX25 is still compiled into the kernel as a
> module, so kernel recompilation is not needed.
But for how much longer? Part of the proboem is that AX.25 is relativly
intrusive protocol. Just enabling it as a module that is never load will
increase - the amount of memory for every packet. It's also not bullet-
proof but the code is slowly getting there. I can only encourage
everybody to contribute again. There are man drivers waiting to be
written, many bug waiting to be fixed, many features waiting to be
implemented.
Ralf
next prev parent reply other threads:[~2006-01-07 19:19 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
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 [this message]
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=20060107191951.GB756@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=doug.n7bfs@gmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=lists@w1nr.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 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.