From: jerome lacoste <jerome.lacoste@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Bradley Reed <bradreed1@gmail.com>, linux-kernel@vger.kernel.org
Subject: [OT] Re: MPlayer broken under 2.6.15-rc7-rt1?
Date: Mon, 2 Jan 2006 10:57:52 +0100 [thread overview]
Message-ID: <5a2cf1f60601020157w1ca252e0s1fe8fa3e839e54d4@mail.gmail.com> (raw)
In-Reply-To: <1136118354.17830.21.camel@laptopd505.fenrus.org>
On 1/1/06, Arjan van de Ven <arjan@infradead.org> wrote:
>
> > Although I like the idea of making the vendors of binary modules
> > really aware of the costs they introduce with regard to debug issues
> > on tainted system, if I was them, the first thing I would say is
> > "contact the vendor of the part of the system that changed", i.e. the
> > kernel.
>
> the good ones don't, and investigate. The bad ones... do you really want
> their code in your kernel??
I should have emphasized the "system that changed" part over the
"contact the vendor" one.
I believe most of us have to deal with time as a limited constraint.
And the issue investigation heuristic that considers that an issue
most likely results from the latest change in your configuration gives
a good result most of the time. Software, hardware, we all do it.
So maybe it's a bad vendor practise to *redirect* people somewhere
else, but it's I think a good engineering practise to work by
*isolating changes*. Kernel people work by isolating binary from
non-binary code. Vendor probably work by isolating unknown
configurations from preferred known working configurations. Everyone
just tries to do what best suit their development environment and
constraints.
Cheers,
Jerome
(and Happy Linux Year 2006)
next prev parent reply other threads:[~2006-01-02 9:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 18:29 Bradley Reed
2005-12-31 18:47 ` Alistair John Strachan
2005-12-31 18:59 ` Bradley Reed
2005-12-31 19:14 ` Alistair John Strachan
2005-12-31 19:51 ` Steven Rostedt
2005-12-31 20:07 ` Bradley Reed
2005-12-31 20:33 ` Steven Rostedt
2005-12-31 20:58 ` Jan Engelhardt
2005-12-31 22:46 ` RTC broken under 2.6.15-rc7-rt1 (was: Re: MPlayer broken under 2.6.15-rc7-rt1?) Steven Rostedt
2005-12-31 23:22 ` Bradley Reed
2006-01-01 0:04 ` Steven Rostedt
2006-01-01 9:14 ` MPlayer broken under 2.6.15-rc7-rt1? Arjan van de Ven
2006-01-01 9:51 ` Bradley Reed
2006-01-01 11:26 ` Arjan van de Ven
2006-01-01 12:12 ` jerome lacoste
2006-01-01 12:25 ` Arjan van de Ven
2006-01-02 9:57 ` jerome lacoste [this message]
2006-01-01 13:28 ` Arjan van de Ven
2006-01-01 14:21 ` Alexander E. Patrakov
2006-01-01 17:50 ` Prakash Punnoor
2006-01-01 11:50 ` Adrian Bunk
[not found] ` <20060101145402.0c6292bb@galactus.example.org>
2006-01-01 13:16 ` Adrian Bunk
2006-01-01 13:25 ` Arjan van de Ven
2006-01-01 13:41 ` Steven Rostedt
2006-01-01 15:21 ` Jan Engelhardt
2006-01-01 15:24 ` Jan Engelhardt
2006-01-01 14:31 ` Alistair John Strachan
2006-01-01 18:57 ` Lee Revell
2006-01-01 21:33 ` Keith Owens
2006-01-01 22:57 ` Alistair John Strachan
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=5a2cf1f60601020157w1ca252e0s1fe8fa3e839e54d4@mail.gmail.com \
--to=jerome.lacoste@gmail.com \
--cc=arjan@infradead.org \
--cc=bradreed1@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®