From: "Philippe Lafoucrière" <lafou@wanadoo.fr>
To: Chris Gianelloni <wolf31o2@gentoo.org>
Cc: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)"
Date: 13 Aug 2003 16:20:11 +0200 [thread overview]
Message-ID: <1060784410.7503.29.camel@biproc> (raw)
In-Reply-To: <1060783729.4133.42.camel@vertigo>
> Proper testing would have yielded different results. Also, there is no
> way to duplicate the results since there is zero information on the
> setup. In any scientific circle, this data would IMMEDIATELY be thrown
> out since it cannot be reproduced. They also had no "control" group.
> It would also have been nice to have seen them test Gentoo (optimized)
> against Gentoo (non-optimized). Testing should have also been done on
> the SAME machine. Not "identical" machines, but the exact same one.
> The reason for this is there is the possibility that hardware could be
> causing a discrepancy in the results.
>
> The "Gentoo Approach" also is not limited to simply optimization, but
> also to the customization and control over your system that a Gentoo
> user gets.
>
> I have found that most Gentoo converts don't even bother to use much
> optimization, but rather enjoy the ease of use and control much more.
totally agree ! Btw, gnumeric speed is related to version apparently,
and they didn't use the official gentoo (patched) kernel ("The same
2.4.21 source was copied to all machines"). This sux !!
I don't use gentoo for optimization, but ease of use and management :)
I've tried to install a red hat 9. It's pretty fast for a i386 distro !
More faster to start openoffice for exemple. But redhat network updates
killed my nerves !
Gentoo roxor :)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-13 14:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 13:38 [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Philippe Lafoucrière
2003-08-13 14:07 ` brett holcomb
2003-08-13 15:03 ` Sven Vermeulen
2003-08-13 16:15 ` Alan
2003-08-13 20:30 ` Chris Gianelloni
2003-08-13 14:08 ` Chris Gianelloni
2003-08-13 14:12 ` Brad Laue
2003-08-13 14:20 ` Philippe Lafoucrière [this message]
2003-08-13 14:25 ` Philippe Lafoucrière
2003-08-13 14:32 ` Chris Gianelloni
2003-08-13 16:17 ` Alan
2003-08-13 16:22 ` Patrick Kursawe
2003-08-13 20:35 ` Chris Gianelloni
2003-08-13 20:32 ` Chris Gianelloni
2003-08-14 10:02 ` Paul de Vrieze
2003-08-13 21:15 ` FRLinux
2003-08-13 22:49 ` William Kenworthy
2003-08-14 2:04 ` Brian Jackson
2003-08-14 10:10 ` Paul de Vrieze
2003-08-14 12:30 ` Chris Gianelloni
2003-08-14 16:59 ` William Kenworthy
2003-08-14 17:38 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentooapproach)" matt c
2003-08-14 19:22 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" FRLinux
2003-08-14 23:01 ` William Kenworthy
2003-08-13 14:24 ` David Holm
2003-08-13 14:28 ` Philippe Lafoucrière
2003-08-13 16:16 ` Eric Olinger
2003-08-13 19:00 ` Jon Portnoy
2003-08-13 20:02 ` Mike Frysinger
2003-08-14 1:07 ` [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)' donnie berkholz
2003-08-14 1:13 ` Jon Portnoy
2003-08-14 11:01 ` Chris Gianelloni
2003-08-13 14:34 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Stuart Herbert
2003-08-13 14:34 ` Svyatogor
2003-08-13 17:46 ` Adam Porich
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=1060784410.7503.29.camel@biproc \
--to=lafou@wanadoo.fr \
--cc=gentoo-dev@gentoo.org \
--cc=wolf31o2@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