public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: caszonyi@rdslink.ro
To: "S. Barret Dolph" <wheds8@ms66.hinet.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: New linux box
Date: Mon, 26 Jan 2004 23:08:17 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.53.0401262305330.996@grinch.ro> (raw)
In-Reply-To: <200401262213.43388.wheds8@ms66.hinet.net>

On Mon, 26 Jan 2004, S. Barret Dolph wrote:

> Well, my problems have much to do with hardware and it is time to get a new
> box. My old box ran for 6 years with Mandrake and never crashed. (X-windows
> crashed when setting up Matrox 450 though.) My question is what hardware is
> good to avoid. I only use my computer for work, no games, but I am on it at
> least 6 hours or more a day. I care mostly about stability and don't really
> care too much about speed. So more to the point are any of you aware of
> hardware that is a nightmare to install. Or a site which can help.
>

If you want stability don't use the latest and greatest hardware (Video
card and motherboard chipset).

It is ussually good to avoid Nvidia because they have usually binary only
drivers and they are not stable.



> Cordially,
> S. Barret Dolph
> Taipei Taiwan
> -

Calin

--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
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

      parent reply	other threads:[~2004-01-26 21:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 14:13 New linux box S. Barret Dolph
2004-01-26 14:24 ` Peter Garrett
2004-01-26 15:57 ` Ken Moffat
2004-01-26 19:53   ` Theo. Sean Schulze
2004-01-26 20:56     ` Ken Moffat
2004-01-26 21:08 ` caszonyi [this message]

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.53.0401262305330.996@grinch.ro \
    --to=caszonyi@rdslink.ro \
    --cc=linux-newbie@vger.kernel.org \
    --cc=wheds8@ms66.hinet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox