On Wed, Oct 31, 2007 at 09:24:43AM -0600, Richi Plana wrote: > On Wed, 2007-10-31 at 09:28 -0400, Doug McLain wrote: > > I am running 7.92, and I see that the new firewire stack is in place. > > There is a page at the linux1394 wiki that suggests that kernel > > packagers build the old stack into the kernel for the time being: > > > > http://wiki.linux1394.org/JujuMigration > > > > Any chance of this happenign for Fedora 8? > > Axel Thimms (of ATRPMS fame) is distributing an ieee1394-kmdl package > which, I think, is compiled to use the old stack. They are doing it > because MythTV is incompatible (read: doesn't work) with the new > firewire stack. The only unfortunate thing is that he is distributing a > "libraw1394" package (which collides with a package on Fedora) in order > to provide support for the kernel module. I have suggested using a > different name for the package and placing the library in a different > directory (to be loaded by mythtv with LD_LIBRARY_PATH), and hopefully > that will fix any conflicts with Fedora. But mythtv is not the only app affected by this - every ffmeg using or derived project is affected, so half a multimedia system's packages would have to be special treated for not really any gain. Even upstream classifies the current state of the stack as "not end user deployable". So the reasons some advocates of "no replacement" policies are reversed - the replacement is *less* experimental than the original and is know to work. This raises the question about the target audience of Fedora: Early adoptors means that they are willing to break their systems and aid in unbreaking them. Unfortunately the true audience is less willing to see their systems break for a year waiting for a solution. Is ATrpms damaging Fedora's core cause? Perhaps, as these users are not building and pressure to get things fixed (same could be said about the nvidia drivers). But since the main motors of juju are at Red Hat they don't need and further motivation by screaming end users, so actually it's good thing for everyone. ;) > (I just checked and they don't seem to be doing it for F8 but you could > probably grab the src.rpm and compile it and update it for your kernel.) Actually you need to swap out the tarball with sources matching F8's kernel, just rebuilding will most probably not work. Alternatively Fedora could ship a kernel with both modules and blacklist the old ones. So users would just need to adjust the blacklisting config and I would have less work to do :) -- Axel.Thimm at ATrpms.net
Attachment:
pgpJRMAKylJg2.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
