by chat1410 » Mon Feb 11, 2013 3:29 pm
Per
this response:$this->bbcode_second_pass_quote('WarheadsSE', 'I')t's a matter of I have done work, but I am limited in what I actually know about the underlying hardware, even with the NDA. PLX is not interested in updating the kernel, and actually have sold the unit that produced the hardware family and wrote the kernel!
My efforts along with others have resulted in kernels that are supportive of systemd, however, they are NOT stable kernels, and have as-yet-untraced faults that cannot be deemed "acceptable". Right now, efforts are underway to get uboot partition & usb support all the way to 2013.01-rc's. We've yet to get USB working fully, and we've got a few issues with the sata read (yay! nasty hack by PLX). The reason this is important is it will remove the need to have the kernel in NAND, which is one of the many things I despise about the way the system support stands as it is now.
The problem is PLX not being as open regarding the processor as necessary to write a systemd compatible component. As a result WarheadsSE and gang are having to create a roundabout method of getting systemd stable. Please remember this is all being done on the devs free time
because ALARM is community donation supported. If you want OXNAS working next week, and you don't know the required assembly/architecture, please donate enough money for WarheadsSE and gang to make this their full-time job.
The dev team is not incompetent or lazy, please stop treating them as such. They understand our frustrations but this stuff can't happen overnight (they've been working on trying to implement systemd for almost a year).