From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: watch for heresay
Date: Sun, 14 Oct 2001 08:48:18 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0110140829260.32569-100000@ignatious> (raw)
In-Reply-To: <003501c153bd$424ab080$0300a8c0@elcjn1.sdca.home.com>
On Sat, 13 Oct 2001, Tony Baechler wrote:
> ... I have no experience at all
> with Red Hat but have read that various config tools require graphics, so
> I would stay away from it for now. ...
Sorry, but this is **not** a good thing to say. When you decide something
shouldn't be used because you read somewhere that something is
required. The truth (which hopefully is important) is that every needed
config tool is available in both console and X tools. And guess what?? The
console tool came first like so many other items in the Unix/Linux
world. The X programs are front ends. Perhaps you should ditch the system
because there is also a web front end for the major tool? Basically, we
should refrain from spreading hearsay.
The rest of the post was quite refreshingly honest in stating it was based
on personal experiance. While I don't discount the experiance, here is
another view. I have installed Debian, Redhat, and Slackware. The only
distrobution I have had any problems with was Slackware. Once I figured
out my mistake, Slackware was pretty easy.
If you are downloading, then Debian is the smallest distro to get. This is
hands down the truth. The initial download for Debian will always fit in
less then 10 floppys. Debian has tools to create iso images, but doesn't
make them. Their reason is simple: they want to minimize downloading and
every CD they have seen has many packages many people don't want or
need. Instead the software gets what is needed and nothing more.
For the complete novice, RedHat and Debian have the easiest
interfaces. I highly recomend RedHat's linuxconf for ease of use. With the
one program you can do most configuration needed. It comes standard on a
redhat install. It is available for debian and might be for slackware.
Slackware has the highest learning curve for admin. That being said, it is
the easiest to maniputlate on a basic leve. All Linux systems use text
files for their config. Slackware is the easiest to directly modify the
text file.
=======
Kirk Wood
Cpt.Kirk@1tree.net
"When I take action, I'm not going to fire a $2 million missle at
a $10 empty tent and hit a camel in the butt. It's going to be decisive."
- President George Bush
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
which linux to go for Danny Keogh
` Thomas Ward
` Buddy Brannan
` Shaun Oliver
` Kirk Wood
` Kirk Wood
` Tony Baechler
` Kirk Wood [this message]
` watch for heresay Shaun Oliver
` Thomas Ward
` Rodney Clowdus
` Raul A. Gallegos
` Shaun Oliver
` Tony Baechler
` Frank Carmickle
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=Pine.LNX.4.21.0110140829260.32569-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).