From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Best Desktop Patchset for kernel
Date: Wed, 5 Oct 2005 22:24:47 +0200 [thread overview]
Message-ID: <200510052224.47235.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <1128535313.18002.43.camel@cocagne.max-t.internal>
On Wednesday 05 October 2005 20:01, Olivier Crete wrote:
> On Wed, 2005-05-10 at 19:26 +0200, Hemmann, Volker Armin wrote:
> > Hi,
> >
> > ok, coaranm aside - have you EVER seen a dev recommending love- or
> > nitro-sources?
> >
> > [...]
> >
> > If you want the 'latency enhancement' of nitro, go directly to ck - Con
> > Kolivas knows what he does.
>
> The official party line from Gentoo/AMD64 is that if you use anything
> else than gentoo-sources, you are on your own and your bug reports will
> be ignored. vanilla-sources may be tolerated since gregkh&co seem to be
> doing a good job on the 2.6.x.y series.
>
> Using nitro or ck or love kernel may very well break your system and the
> breakage may not be fixed by simply switching back to gentoo-sources
> since it may break anything you have compiled or the content of your
> hard disk. If you want to try any of those highly experimental features,
> you are on your own. I would personally advise you pick only the
> specific features you want and apply them to gentoo sources so you can
> track down fast what breaks if you want to help debugging.
you are telling that the wrong guy - I always use gentoo - or vanilla-sources,
because I remember very well the problems of people using nitro/love sources
bach in 04.
Oh, and back in 2003/2004 I tried a lot of different kernels - and believe it
or not: at the end, the less patched, the better were the kernels. So I
stayed with gentoo or vanilla, because the rest was not better or faster,
only more instabil.
I am pretty much healed from straying around ;)
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-05 20:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 0:37 [gentoo-amd64] Best Desktop Patchset for kernel Karol Krizka
2005-10-05 1:04 ` Hemmann, Volker Armin
2005-10-05 1:04 ` Mark Knecht
2005-10-05 1:37 ` Jared Lindsay
2005-10-05 2:35 ` Hemmann, Volker Armin
2005-10-05 2:40 ` Mark Knecht
2005-10-05 3:40 ` Jared Lindsay
2005-10-05 3:50 ` Taka John Brunkhorst
2005-10-05 4:28 ` Hemmann, Volker Armin
2005-10-05 13:42 ` [gentoo-amd64] " Duncan
2005-10-05 17:26 ` Hemmann, Volker Armin
2005-10-05 18:01 ` Olivier Crete
2005-10-05 20:24 ` Hemmann, Volker Armin [this message]
2005-10-05 18:24 ` [gentoo-amd64] " Duncan
2005-10-05 21:54 ` [gentoo-amd64] " Jared Lindsay
2005-10-06 5:19 ` [gentoo-amd64] " Duncan
2005-10-06 6:53 ` Hemmann, Volker Armin
2005-10-06 15:59 ` [gentoo-amd64] " Duncan
2005-10-06 16:35 ` Marco Matthies
2005-10-06 21:27 ` [gentoo-amd64] " Duncan
2005-10-06 20:59 ` [gentoo-amd64] " Jared Lindsay
2005-10-06 21:42 ` [gentoo-amd64] " Duncan
2005-10-06 21:47 ` [gentoo-amd64] " Tres Melton
2005-10-11 22:12 ` [gentoo-amd64] " Billy Holmes
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=200510052224.47235.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--cc=gentoo-amd64@lists.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