Joshua Daniel Franklin wrote:
On 4/30/07, Jarod Wilson <[EMAIL PROTECTED]> wrote:
The current firewire stack was evaluated by engineering, and the basic
conclusion was "no way do we want to have to support this ugly mess".
Note that for Fedora 7, we've started writing an entirely new firewire
stack[1]. The intention is that once that stack has been battle-tested a
bit, we'll port it to RHEL5. Initial hope was to have it ready for 5.1,
but I'm inclined to think it'll be more like 5.2.
Just let me make one thing crystal-clear: Red Hat hasn't committed to
any sort of schedule to include firewire support in RHEL5, and perhaps
it never comes. But we're working on this new stack, and would like to
bring it to RHEL5 if/when its deemed ready. The above was personal
beliefs that probably should not have been voiced on this list, lest
they be taken as an official statement.
[1] http://fedoraproject.org/wiki/Releases/FeatureFirewireJuJu
That's sort-of good news, but that decision really should have made it out
of your engineering meeting and out to the world. I already mentioned that
the educational reseller DLT was apparently under the impression Firewire
would be in EL5. It's been a hassle for us every time a researcher brings
in data on a Firewire drive; with EL4 I saved a particular kernel and used
Oracle's modules:
http://www.oracle.com/technology/pub/articles/hunter_rac10gr2.html#8
I actually installed EL5 on a machine with firewire to eval; it was no big
deal since I have a nice kickstart setup, but it was a complete waste of
my time which could have been avoided by a sentence or two in the
Release Notes.
We can't RelNote every feature we don't include support for. Especially
if there's no change from the prior release.
--
Jarod Wilson
[EMAIL PROTECTED]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
