On 2010-01-25 at 05:58:04 +0100, Franz Pop wrote:
If there still is an issue affecting current kernels, you will probably get
much more response reporting it to the upstream kernel developers than
with a Debian bug report.
I'm just trying to follow the rules.
From
Given that, what are the guidelines for when to file the initial bug
report directly with upstream vs. when to file a bug report with Debian?
It's mostly a question of what's most effective.
The kernel team is already drowned in bug reports and has very little
manpower to deal with relatively
On Mon, Sep 22, 2008 at 04:10:01PM -0400, [EMAIL PROTECTED] wrote:
This works just fine in Etch, but fails in Lenny. A device cannot be taken
offline dynamically.
I fail to see what s390-tools or the chccwdev tools have to do with this
problem.
Package: s390-tools
Version: 1.6.2-1
This works just fine in Etch, but fails in Lenny. A device cannot be taken
offline dynamically. In my case, I have a separate dasd device for use as
a boot partition. The device number is 0201, which Linux references as
0.0.0201. The device node name for
4 matches
Mail list logo
