Bug#345067: [Yaird-devel] Re: Bug#345067: ide-generic on poweprc

[Jonas Smedegaard]

On Thu, 9 Mar 2006 10:55:12 +0100
Sven Luther <sven.luther at wanadoo.fr> wrote:

> the design of both yaird and the kernel ide layer make it very hard
> to believe such a bug existed. It could be, but would be a bug in the
> kernel to be solved ASAP, not something to work around in the ramdisk
> tools, and i believe the hacky workarounds, by hiding the problem,
> where even more nefast than they helped in any way.

Why did you not help back then, forcing us ramdisk generator
maintainers to invent ugly workarounds?

Why don't you fix ide-pmac to work modular now, so powerpc kernels kan
be all modular like other architectures?

And why don't you simply have the powerpc-kernels build ide-generic as a
module (rather than not building it at all), to allow the all too
concerned yaird to load it even if for the wrong reasons and known
unnecessary for your specific hardware (Pegasos builtin VIA chipset)?


> > I'll continue working on the wiki, but let's debate through email as
> 
> I would appreciate if you could clean the wiki, remove all my
> ranting, and your wrong assumptions, and put my analysis to the
> forefront.

I am uncertain as to what you consider valuable info and what you
consider ranting, so would appreciate it if you remove your own stuff
yourself.

I do not agree with shifting the context of the wiki page from tracking
the chain of problems/workarounds to focusing solely on the core
(non-existing?) kernel bug, so will not participate in emphasizing your
current analysis as being central to the page.


> You probably noticed that i modified the mention of the ide-core
> thingy after having examined the symbols in the modules (i asked for
> an x86 modules.dep for 2.6.8, 2.6.12 and 2.6.15, but nobody provided
> it to me yet, maybe you can), and did so in a non-controversial way i
> hope.

Why don't you just grab a kernel package from the archive and extract
the files you need from there?


> you have to accept your part, and admit you have been wrong, or we
> will not be able to be constructive on this issue if you stubornly
> continue to try to prove you where right.

Wrong where?

I hereby (stubbornly) repeat that I strongly suspect a kernel bug exist
to be worked around in yaird.

Please note that I do not say that the bug has not been fixed in most
recent kernels - on the contrary I suspect it was fixed in 2.6.14. What
I say is that the bug is relevant for yaird to deal with to work
reliably even with 2.6.8. Working with official Debian kernels is not
the target of yaird. As an example, developers of embedded distros
(some of which are tied to specific kernel versions due to the use of
non-free drivers) may favor yaird for their non-Debian ramdisks.


> Are you ready to move that responsability to the kernel team, or a
> common yaird team ? I would gladly help out, as it seems clear that i
> understand how things work either in yaird or the kernel itself
> better than you, but i don't speak perl, so we need a real perl
> native to join the project. This could be the solution, with you
> doing the day-to-day maintainership, me investigating the problem,
> and someone else doing the actual perl implementation, at least at
> first until i become familiar with perl, or Erik surfaces again ? 

I welcome help.

I strongly oppose close cooperation between the two of us, given our
experiences working together so far.

And no, I do not agree with you that your judgement is far superior to
mine. Let's just agree to disagree on that point, shall we :-)


 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/yaird-devel/attachments/20060309/93fd1f5c/attachment.pgp