From: Ian Haver <g6vey@btinternet.com>
To: linux-hams@vger.kernel.org
Subject: Re: Most "HAM" friendly distro ?
Date: Sat, 07 Jan 2006 09:11:58 +0000 [thread overview]
Message-ID: <43BF85DE.1040806@btinternet.com> (raw)
In-Reply-To: <3FEF9BDB-83F9-4B61-97E3-ED546A92A02B@oz.net>
Hi all.
If i can just add my two pennies worth on the distro wars.
I originally run RedHat 4.0 many years back with just a console and jnos.
If was fast and fab. Then I wanted to write a letter, errm wheres the
equivillent of
M$ Word. there isnt one. It also become more apparent that this linux i
had found in mid 90`s
was quite a tool. Anyway to cut a long story short i dont go for a ham
distro because most
distro`s run ham apps with very little mods/tweeking. Instead i went for
the more glossy
workstation/desktop type and then have the fun and excitement of getting
the ham bits to work
on it.
Theres enough of us so called experienced linux operators out there to
guide the newbies
now, so theres not really a massive problem anymore. Lets face it its
not hard to install any of the
recent distributions now. Maybe getting a few hardware issues can be a
heart ache but by
enlarge linux goes onto pc hardware pretty well these days.
In my experience, listening to a few newbies in my BBS area they are
trying to install SUSE10 or
Mandrakes latest on a Pentium I clocked at 166Mhz wich had been running
dos/win95.
It isnt going to work properly. I try to explain that they wouldnt run
XP on it so it will struggle with
the later kernels and resources needed to make the system run smoothly
in linux. The sooner these
linux vendors stop selling Linux spec as in 386/486 upwards the better.
It should really be X86
architechture with min 1G proccessor and at least 256M Ram for those who
require good desktop
applications.
Forthose who just want a console with no GUI then thats a different matter.
Although i was caught out there as well. One of my ham friends wanted a
basic console mode ax25
interface between his lan machines and his packet. What better, run
linux with all the ax25 bits and then with
his windoze based lan machines he can access the outside world. He did
this on a P I 166 with 32M RAM.
It worked very well for him until one day he rung me and told me it had
all gone very slow, when i got there
i found out he had worked out how to install packages and had installed
the entire KDE suite. He also
managed to change the run level to 5. so hey he had a GUI as well but it
was really slow and as a result his
retry rates had doubled in his packet setup.
So with all the woffle above i can only recommend from experience. Run a
good fast machine with plenty of
Ram. Pick a Distibution which fruits with apps, you dont need to install
them, but at least you can later.
Run Linux for at least a week if not two and learn how the linux
operates especially its file structure and
permissions. Then have a play with ham radio. Because hopefully by then,
you would have learned how to edit
and manipulate files. You would have learned how to delete or rename
files and more so how to restart parts
of linux without rebooting the whole machine. I find in the ham world
with Linux, give them a few days to
learn or they will soon be going back to windows with a grumpy face
slagging off Linux at every convenience.
Best Regards All
Ian
G6VEY
SYSOP GB7YFS
Author Xarpm_plus
http://radiolinux.co.uk
next prev parent reply other threads:[~2006-01-07 9:11 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 [this message]
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=43BF85DE.1040806@btinternet.com \
--to=g6vey@btinternet.com \
--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).