From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Random segfaults with kernel 2.6.27
Date: Fri, 21 Nov 2008 07:50:11 +0200 [thread overview]
Message-ID: <gg5i76$ej$1@ger.gmane.org> (raw)
In-Reply-To: <350fc7cf0811202122t6eab1543u3c524b784cb8aed2@mail.gmail.com>
Andrey Falko wrote:
> [...]
> I agree. Even if this is a bug, no open source developer could be
> qualified to fix it because fgrlx is closed source. If you can, report
> this to ATI, otherwise, you will have to live with the problem or use
> open source drivers.
That is not true. If it's in portage, you have to accept bugs against
it. If a bug is serious, then that means the package has to stay masked
if there's no workaround for it in form of a patch. And sometimes there
are patches for non-OSS software too. (This bug is not serious because
I'm the only one who can confirm it. But you're talking generally, so
this specific bug is not the point of this reply.)
ATI doesn't support Gentoo, btw. Only Ubuntu, openSUSE and some other
high-profile distros are "supported." In quotes because it's broken
even on those ;)
prev parent reply other threads:[~2008-11-21 5:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 0:52 [gentoo-user] Random segfaults with kernel 2.6.27 Nikos Chantziaras
2008-11-21 1:07 ` Andrey Falko
2008-11-21 1:24 ` [gentoo-user] " Nikos Chantziaras
2008-11-21 1:58 ` Dale
2008-11-21 2:27 ` Nikos Chantziaras
2008-11-21 5:39 ` Dale
2008-11-21 2:20 ` Andrey Falko
2008-11-21 2:36 ` Nikos Chantziaras
2008-11-21 3:16 ` Nikos Chantziaras
2008-11-21 3:51 ` Mike
2008-11-21 3:59 ` Mike
2008-11-21 3:53 ` Iain Buchanan
2008-11-21 4:39 ` Nikos Chantziaras
2008-11-21 5:03 ` Iain Buchanan
2008-11-21 5:20 ` Nikos Chantziaras
2008-11-21 5:22 ` Andrey Falko
2008-11-21 5:50 ` Nikos Chantziaras [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='gg5i76$ej$1@ger.gmane.org' \
--to=realnc@arcor.de \
--cc=gentoo-user@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