On Mon, Jun 07, 2010 at 04:24:32PM +0200, Nils Radtke wrote:
# 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.. ;)
# 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..
Hmm, interesting. Perhaps then simply loosening up the code to skip
parsing that file if unavailable is the way to go. Need to investigate
closer to ensure not loosing stabiliy or features by such approach.
# 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..
Fair enough. I will then investigate closer before applying to official
yaird, to ensure not risking stability.
# >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.. ;)
I sure appreciate your sharing your hacks, even if that's all you want.
Trying to enroll you in the greater task of maintaining yaird in general
is clearly abuse of your friendly and limited filing a bugreport - hope
you dont mind that :-)
# 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.
I would be happy to guide you with both git and Alioth. If interested,
please subscribe to the mailinglist at
http://lists.alioth.debian.org/mailman/listinfo/yaird-devel and let's
discuss further there.
That goes for anyone else reading this email conversation too :-)
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..
I am patient. Even with years between your contributions, I would still
prefer that you work in the main VCS than passing the results as diffs
to the BTS.
TTBOMK Sourceforge have not been used as upstream home for quite some
years. After I started packaging yaird for Debian, Erik van
Konijnenburg, the original author, agreed to move upstream development
to Alioth: http://yaird.alioth.debian.org/ (he put up that web page back
then, not me, so I suspect the timestamp of the front page is actually
the date he moved it there).
Sadly I lost contact with Erik van Konijnenburg some years ago. In july
2008 I decided to claim ownership of the project.
I have made little progress since then, but do not consider it dead.
YMMV.
Kind regards,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
