[ATrpms-users] Dahdi w/ Oslec
Joseph L. Casale
jcasale at activenetwerx.com
Tue Mar 30 23:37:06 CEST 2010
>dahdi still needs manual intervention (copying over the echo dir from
>the kernel), so it is not turned on by default.
>But for CentOS there is also another issue: the kernel doesn't carry
>oslec at all, so it needs either a lucky backport or the old install
>method outlined at the oslec homepage. So for RHEL/CentOS we would
>need an oslec kmdl first and then patching dahdi.
Thanks for the post. So after further looking (I admit now I don't know
much about rpm building yet!) I see a few things:
I have only ever done it manually and as patch to rpms using this method:
It seems Tzafrir Cohen has a git repo with a bit of code that can make a nice
patch that actually creates the kernel echo files etc and writes them in the
dahdi source dir to build similarly to the rowetel link:
I am unclear about the need for the oslec kmdl, it can't be just included
in the dahdi rpm?
How is it intended that one deploys and uses the rpm you provide?
It doesn't have any deps or provides?
Does one handle getting the user space tools on his own, the digium ones
are rather tailored to their build methods.
lastly, the testing rpm for your latest build added and "extra" dir in the
module path under the kernel, was that by mistake?
More information about the atrpms-users