public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Gregg" <gregg@sc.am>
To: <arutha@gmx.de>
Cc: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Upgrade, course of action.
Date: Sat, 24 Aug 2002 19:28:35 -0500 (CDT)	[thread overview]
Message-ID: <4018.66.247.109.90.1030235315.squirrel@sc.am> (raw)
In-Reply-To: <200208241359.39309.arutha@gmx.de>

Im glad to be testing it :)

Yes I know about production and testing systems.  I have a backup solution
already in place, nearly hot-swapable.  Ive been programming as a
consultant for 9 years.  I know what risks I am taking.  But I honestly
cant stand redhat, and mandrake is just to much bloat.  Stable debian is
just out of date.  Most of my users are rather intelligent people, half of
them linux users themselves.  They know what I am doing.

Gregg

> On Saturday 24 August 2002 07:24, Gregg wrote:
>> Everyone keeps telling me how brave I am.  I have to say, it doesnt
>> seem that way to me.
>
> Sure, backup solutions are bought after the first real big crash,
> security  measures are taken after one billion credit card numbers have
> been stolen  etc. you get the picture. I have absolutely no idea what
> kind of customers  you have but I wouldn't want to have my domain hosted
> on a system running on  gcc 3.1 and all the latest packages.
>
> It's great for me at home but for serious computing it's just not
> reliable  enough. I don't say it has to crash but I say I don't know
> enough working  examples and theres no vendor to blame.
>
> Sure you've had no real outage (due to gentoo), many ppl never had
> problems  with xfs, I lost part of my homedir. On the other hand I never
> had problems  with reiserfs even when it wasn't in the main kernel
> others lost everything.  It's all about the risk.
>
> Gcc 3.1 is not as tested as it should be (heck 3.1 is not even the
> "real" 3.x  release) and some software is behaving strangely especially
> with athlon  optimizations. Gentoo itself is known to have broken
> ebuilds etc. (I've yet  to emerge one of those myself so far everything
> has worked).
>
> That's why we say brave. It's really great to have someone testing all
> this  out but I just wouldn't test it on paying customers that don't
> know about all  this. You do know about "production", "integration" and
> "testing" systems? :)
>
>
> Alex
>
> --
> "They that can give up essential liberty to obtain a little temporary
> safety  deserve neither liberty nor safety."
> Benjamin Franklin
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev





  reply	other threads:[~2002-08-25  0:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  9:22 [gentoo-dev] Upgrade, course of action Gregg
2002-08-23 16:30 ` [gentoo-dev] Re: [gentoo-user] " Michael Monsen
2002-08-23 16:31 ` Michael Monsen
2002-08-23 18:20   ` Dominik Westner
2002-08-23 19:30 ` [gentoo-dev] " Alexander Gretencord
2002-08-23 20:45   ` Gregg
2002-08-24  1:25 ` Charles Lacour
2002-08-24  5:24   ` Gregg
2002-08-24  6:41     ` [gentoo-dev] " Paul
2002-08-24  8:03     ` [gentoo-dev] " Thomas M. Beaudry
2002-08-24 11:59     ` Alexander Gretencord
2002-08-25  0:28       ` Gregg [this message]
2002-08-25  4:58       ` Thomas M. Beaudry

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=4018.66.247.109.90.1030235315.squirrel@sc.am \
    --to=gregg@sc.am \
    --cc=arutha@gmx.de \
    --cc=gentoo-dev@gentoo.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