public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: shaun_oliver@optusnet.com.au
To: speakup@braille.uwo.ca
Subject: Re: slackware vs redhat
Date: Fri, 27 Sep 2002 17:06:59 +1000	[thread overview]
Message-ID: <20020927070659.GA1519@borg> (raw)
In-Reply-To: <002a01c265f3$47d07fa0$bf393c44@flint01.mi.comcast.net>

1. redhat is out of date
afaik, red hat ain't out of date, andthe only reason I can think of your
friend would tell you this is because of misinformation or the fact that
distributers choose their packages carefully. they use the packages they
consider to be stable enough for release in their distributions..

2. redhat takes too many resources and is slower by over 50%
that's just an outright crock. Red hat as far as I can tell, ain't any
slower than any other distribution. the version I used a year ago or
there abouts was slow on boot up mainly  because it had a lot to load at
startup. however, you can configure that to suit your needs.
so that point is a load of rubbish.

3. doesnt take as much disk space and is easier to install.
Each distribution takes up as much disk space as you want it to.
the standard for slack 8.0 is around 2 GB if you choose a full install.
How much disk space GNU/Linux takes up is entirely up to you.

4. redhat updates every few months or so......
So what if it does, is this a problem?
all I can suggest is you use what you're comfortable with. if it's red
hat then use red hat if it's debian or slackware or something else, use
that one. Don't always trust what someone else tells you. use what you
feel the most comfortable using. and more importantly, check your facts.


-- 
Shaun Oliver


In a world without fences
          and walls who needs Windows and Gates?

EMAIL: shaun_oliver@optusnet.com.au
ICQ: 76958435


  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Sunfire
 ` shaun_oliver [this message]
   ` Sunfire
 ` Aaron Howell
   ` Sunfire
 ` Mitchell Smith
   ` Sunfire
 ` Steve Holmes

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=20020927070659.GA1519@borg \
    --to=shaun_oliver@optusnet.com.au \
    --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).