All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adam T. Bowen" <adamb@agitate.org.uk>
To: linux-admin@vger.kernel.org
Subject: Re: Problems and suggestions with hardware and Fedora Core 4
Date: Mon, 12 Sep 2005 10:21:26 +0100	[thread overview]
Message-ID: <43254896.6070403@agitate.org.uk> (raw)
In-Reply-To: <BAY7-F105A5A4E0ACB18B4CCBF61BA9B0@phx.gbl>

Hi,

Bargel Jazat wrote:
> Thanks for the suggestions about the problem on fc4.
[snip]
> - Adam: I ran chkrootkit and found no problems. I have not run any virus 
> check yet. Have
>  viruses for Linux been reported?

There are a few out there, they just don't propagate on *nix systems 
because of the pervasive security model.  I probably over reacted with 
that part of my advice, but whenever I hear a phrase like "a few binary 
files were different," I loose my head.

[snip]
>  Maybe fc4 is not stable enough (yet) for a production environment?
>  I want to run a server for a web application I am writing. Would you 
> suggest me to move
>  back to fc3 or fc2?
>  I have also considered moving to Debian (uses older versions of 
> packages and kernel and
>  should be more stable).

I would recommend against running any version of Fedora Core on a 
production system.  It is a bleeding edge distro used as "a proving 
ground for new technology."  If you like the redhat/fedora way of doing 
things, I can recommend CentOS:

       http://www.centos.org/

Cheers

Adam

> 
> Giorgio
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2005-09-12  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 14:27 Problems and suggestions with hardware and Fedora Core 4 Bargel Jazat
2005-09-12  9:21 ` Adam T. Bowen [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=43254896.6070403@agitate.org.uk \
    --to=adamb@agitate.org.uk \
    --cc=linux-admin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.