I'm the lead developer of Image Scan! for Linux and changed upon this
bug report when investigating the boot failure. While I haven't heard
anything yet through whatever channel you tried to contact us, I figured
that I'd short-circuit the corporate red tape and follow up directly.
Firstly, apologies for causing this "mess". From our current research
we believe it was triggered by upstream changes introduced in v129.
Second, heartfelt thanks to Michael for reopening this bug. It will
affect anyone who installed an iscan version between 2.16.0 and 2.19.1
and upgrades from udev-0.125 to any later version that does not strip
out our botched z60_iscan.rules file. That would include everyone
updating to Squeeze once it becomes stable, if not for you reopening!
Third, thanks for your willingness to go through the trouble of actively
ripping out our bad file. We much appreciate that because it has a much
better chance of reaching all systems that need a fix, courtesy of APT.
When I looked into how that file ended up in initrd I was a bit
surprised to see that udev included *all* of /etc/udev/. I had a look
through all the packages that put files there and there are only very
few that I think warrant inclusion in an initrd. As a preventive
measure, would it not be a good idea to get such packages to provide an
initramfs-tools hook to do so themselves instead of udev doing it for
them?
On the iscan side, we're considering adding a hook to keep our file out.
There's nothing in the initrd stage we can think of that would need it
anyway.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
