From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: How to pick a distro?
Date: Wed, 06 Apr 2005 13:44:44 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20050406133253.0202be68@celine> (raw)
In-Reply-To: <425440DE.4000403@gmail.com>
At 01:34 AM 4/7/2005 +0530, NNK wrote:
>I was wondering what I should be looking at in the different distros
>before picking one to use.
>
>Being a total novice, I don't have much experience on Linux, so I'm
>wondering what I should be asking.
>
>Any advice?
This is a difficult question to answer with anything other than personal
prejudice. I will give it a try, though.
1. As a beginner, you want to use a full-strength distribution, one that is
likely to support the full range of activities you might want to use Linux
for. Experienced users often can benefit from using more specialized,
semi-embedded distros that are geared to particular tasks ... e.g., distros
designed to work as routers or as dedicated vidcap hosts ... but you're
better off waiting until you know more before you go that route. Same goes
for source-based distros ... not the best place for a novice to start.
2. You want a distro that has a good packaging system and good support for
security and other updates. Examples that meet this are Debian (the distro
I use) and most of the big RPM-based distros. The best-known distro that
does NOT meet this standard (or at least I believe it does not) is
Slackware ... though if I'm wrong, I'd welcome correction from a Slackware
user.
3. You want someplace you can ask questions with the hope that you will get
prompt and accurate answers. Many distros have their own help lists, and if
you are considering one, you might look at the archives of its support list
to see if it meets this standard. Or, for distro-agnostic lists like this
one, notice what distros are discussed the most ... that is, notice what
the people who *answer* questions know the answers *to*. If you have a
friend who will be helping you, use what he or she uses ... that's way more
important than a quest for the elusive "best" distro.
4. This all assumes you are planning to use reasonablty modern desktop
equipment. Really old equipment ... 486- and even 386-based systems, and
other oddball hardware ... and laptops present specialized problems that
might dictate selection of a particular distro that handles that equipment
well. Most of the RPM-based distros are better at hardware detection than
Debian is, so you might think about how much that matters to your install too.
5. Finally, think about the range of applications you want to run.
Especially GUI-based ones. Different distros come out in different places
in the GUI wars (between KDE and Gnome, mainly, though there is more) and
your life will be easier if you pick a distro that fits what you want or
need in that regard.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-04-06 20:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 20:04 How to pick a distro? NNK
2005-04-06 20:44 ` Ray Olszewski [this message]
2005-04-06 21:21 ` James Miller
2005-04-07 9:29 ` Ulrich Fürst
2005-04-07 6:50 ` Yawar Amin
2005-04-07 16:52 ` Ray Olszewski
2005-04-07 19:57 ` Mouse going nuts in RH Linux Enterprise 3 (Taroon) Eve Atley
2005-04-07 20:10 ` caszonyi
2005-04-07 20:37 ` Ray Olszewski
2005-04-08 5:01 ` Rajendra Mishra
2005-04-08 13:16 ` Richard Adams
2005-04-07 20:44 ` Eve Atley
2005-04-09 8:32 ` How to pick a distro? Yawar Amin
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 2:03 Peter
2005-04-07 19:45 ` Jeremy Abbott
2005-04-08 5:55 ` Ray Olszewski
2005-04-08 16:18 ` Jeremy Abbott
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=5.1.0.14.1.20050406133253.0202be68@celine \
--to=ray@comarre.com \
--cc=linux-newbie@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