[Yaird-devel] Bug#584565: Bug#584565: Bug#584565: [PATCH] enable yaird for kernel.org 2.6.33.4

[Nils Radtke]

  Hi Jonas,

# Ah, no.  My problem was different: http://bugs.debian.org/519866 -
# which lead to wrongly closed) http://bugs.debian.org/523828
# explaining that "depmod -m" needs to be run explicitly now.
See the touch thingie below.. ;)

# Is it perhaps similar to http://bugs.debian.org/516465 ?
Once (years ago) it could have been that one. Right now, it's 
yaird not even recognising a luks setup at all..
 
# >previous patches.
# It works for me too (now that I've generated that PCI module list.
A simple

  touch /lib/modules/2.6.33.4/modules.{pci,usb}map 
  
did work for me..

# But I am a bit suspicious about the devices that you ignore - could
# you perhaps elaborate more on that, to help ensure that they are
# universally sane to ignore?
Hm, I'd say, I just ignore path endings that aren't (at least for me) 
any devices.. As I said, no warranty that my patches will work w/o 
flaws for anyone else..

# last year I had a closer look at the problems with newer kernels,
# and tried to change how symlinks was resolved more generically
# (which I suspect is what you try to cover up with your ignore
That's what it sounds alike. And I think it's more or less what
the loop w/ the topological traversal is for: finding devices and
ignoring the rest. Whether that's a brilliant or helpless approach 
I cannot foresay so..
 
# >Right now, I'm a bit out of time and start thinking about hacking
# >one of my previously used ramfs images w/ the new lvm stuff.
# >Probably the faster solution, but then.. it's a hack.. :|
# If you can be persuaded, then I would be happy to have you help work
# directly on yaird.
Ha! That's not what I meant when I said "I'm a bit out of time".. ;)
I provided the patches w/ the believ they might eventually help someone
else.. If so I'm glad if not, pity.. ;)

# If "fumbling around" then you could do that on a separate branch,
Yeah, one could call it that way.. Though, after all, it's maybe only 
my impression and it's working out quite well for others..

# and when certain that you've narrowed down some flaw and found a
# sensible fix then you can apply that with a clear commit message to
# the main branch.
# Insterested?  Are you familiar with Git?  With Alioth?
git: not yet reaally familiar, svn/cvs: yep.

alioth: I know what is it and what it's for. Never used before.

Interested?
Partly: maybe your branch-approach isn't such a bad idea, though I'd say
once I fixed yaird locally and maybe sent the patches upstream (or to
the debian bts, as upstream (sf.net) honestly seems quite dead (as well as 
debian yaird-devel, btw)) I won't touch yaird again for another couple 
of years.. Last time I used it (and had to fix it) was probably 1 or 2 years 
ago..

    Cheers,

          Nils