Re: Fedora vs Tao vs CentOs as servers

From: Scot L. Harris (webid_at_cfl.rr.com)
Date: 12/23/04

  • Next message: morpheus: "Re: HTML Editor / Bluefish"
    To: Fedora List <fedora-list@redhat.com>
    Date: Thu, 23 Dec 2004 17:14:50 -0500
    
    

    On Mon, 2004-12-20 at 02:47, Ow Mun Heng wrote:
    > I know this has been discussed, but it was more toward, is FC stable
    > enought for use as a production server etc.
    >
    > I'm looking more towards the limited life_span of FC compared to it's
    > RHEL counterpart. (which is where tao linux/CentOs etc... comes into the
    > picture)

    I don't understand the angst many people have over this question. For a
    production site there are several approaches you can take.

    1. buy support from a vendor (RH, SUSE, SUN)

    2. Run a "free" OS that provides updates and upgrade when they EOL your
    version.

    3. Run a "free" OS and update until they EOL it but keep it in
    production as long as you can as is with the last updates.

    4. Run a "free" OS but build your critical packages (apache, postgresql,
    php, sendmail, spamassassin, etc) from sources. Monitor the lists for
    those packages and apply patches that are relevant to your particular
    needs.

    In all cases above run a good updated firewall between your systems and
    the Internet. This limits what is exposed on your systems. Naturally
    harden the systems as much as you can by disabling any un-needed
    services and use a system firewall as well. Implement tripwire to
    monitor for changes. Production systems once in place should not change
    much except for log files and database files. Monitor log files and
    system resources. Setup snort to monitor network traffic looking for
    non-characteristic traffic patterns.

    Any of these options will work. Personally I believe option 4 for a
    production system is the way to go. You don't have rpm support for many
    packages you might run but you can easily upgrade to new versions or
    apply patches as needed. You could generate your own rpms which I don't
    think is that much more difficult.

    The key here is to run good firewalls and intrusion detection tools so
    you know quickly if/when there is a problem. Limiting what is exposed
    means you don't have to worry about a large number of potential
    exploits.

    Many sites run systems with ancient OSes with no problems. Is that
    optimum, probably not. But you can make it work while minimizing the
    risk.

    So pick a version and use it. Don't get caught up in the update daily
    rat race that many people seem to get stuck in.

      

    -- 
    Scot L. Harris
    webid@cfl.rr.com
    No animal should ever jump on the dining room furniture unless
    absolutely certain he can hold his own in conversation.
    		-- Fran Lebowitz 
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: morpheus: "Re: HTML Editor / Bluefish"

    Relevant Pages

    • Re: OS recommendations/Aging software issues
      ... > Now I am about to deploy a linux server and I am trying to figure out ... Keep a spare machine (preferably identical to the production one) up to ... each batch of updates causes no trouble, apply them to the production box. ...
      (Fedora)
    • Re: infrastructure modest proposal
      ... which verifies the updates can be applied successfuly to at least one ... there's "testing" where the developers get to play to their ... hearts content and, hopefully, get a product to "production" level. ... I understand that Fedora is a bunch of folks doing the ...
      (Fedora)
    • Re: Incomplete code in older DMD Pins
      ... Probably every game out the door. ... Other manufacturers made a run, ... Initial updates during production to correct a few things was ...
      (rec.games.pinball)
    • RE: Release engineering confusion
      ... > Cc: 'FreeBSD Questions' ... > Yes, production servers should track -STABLE, since it's, ... This is why I am confused, because as per the handbook: ... the sec/bug updates from my understanding so far. ...
      (freebsd-questions)
    • Re: Dell 2405FPW
      ... >>>Its well known that ONLY the early production runs had the pinkish problem. ... >>>I looked for the problem on the monitor before buying it. ... Alan Baker ...
      (comp.sys.mac.advocacy)