DAHDI RPMs
New RPMs for dahdi-linux and dahdi-tools are now released in the Zultron repository. They are based on the ATrpms RPMs, and contain some improvements:
- Kernel module RPMs can be built against any
kernel-develorkernel-xen-develRPM - OSLEC echo canceller
- No ATrpms proprietary macros, so the RPMs can be compiled outside the ATrpms environment
- RTC is disabled by default for kernel-xen RPM modules
Install the complete kit:
yum install dahdi-linux dahdi-tools dahdi-linux-kmdl-`uname -r`
How to rebuild the dahdi-linux RPMs
To rebuild a new dahdi-linux-kmdl RPM to match the currently running kernel, be sure to install the matching kernel-devel or kernel-xen-devel RPM. Then, simply:
rpmbuild -bb dahdi-linux.spec
You can build for a specified kernel-devel rpm:
rpmbuild -bb --without userland -D "krpm kernel-xen-devel-2.6.18-53.1.13.el5" dahdi-linux.spec
Other command-line switches:
--without userland: only build the dahdi-linux-kmdl RPM
--with rtc: re-enable the RTC for timing (only affects kernel-xen)
--without firmware: leave firmware out of dahdi-linux RPM
--without udev: don't build for udev
The OSLEC drivers
Compiling the OSLEC drivers into DAHDI requires a small portion of a post-version 2.6.28 kernel tree. One of the sources, get-kernel-staging.sh, is a script to grab just this directory for the RPM, so that the entire kernel source doesn't need to be packed up into the SRPM.
Thanks
Thanks to Axel Thimm for the DAHDI RPMs and for always keeping his RPMs up-to-date.
This is great. I have one issue. I run Linux-Vservers and the host system kernel is is not a standard CentOS version. But to run conferencing etc. in a Vserver guest I need to run DAHDI at the host level. Well that is what I’m told as I haven’t completed an install yet.
My question is can I rebuild DAHDI for my kernel with only the dahdi-linux and dahdi-tools packages?
TIA
Rod,
Not too familiar with Vserver, but:
When I build the dahdi-linux RPMs, I had it in mind that people wanting RPM-based installs would naturally have RPM-based kernels. In your use case, do you have a kernel-devel RPM? If so, just follow these instructions to build the dahdi-linux-kmdl RPM and install it on the host. If not, it wouldn’t be hard to change things around a little so that you could build against non-RPM kernel sources; let me know, and I might make the changes.
You will, of course, need the configured kernel sources for your kernel, whether the kernel-devel RPM, or the source tree you built the kernel out of.
Hi,
thanks for all your effort to create simple RPM for CentOS. Most users wanting RPMs (rather than compiling * from scratch) are new users and will not understand how to resolve all the dependancies (libpri etc.) when using the over simplified “yum install asterisk” command that is referenced on the RPM Repo web page. It would be most useful if you could provide a simple, step-by-step, How-To for use with your RPMs, otherwise all your hard work will be still be confusing for the new users (ironically, the users who would benefit the most from your RPM work).
Thanks again!
Hi Simon,
The command ‘yum install asterisk’ should work if you’ve enabled both the EPEL and Zultron repos. The repo page mentions this. Perhaps I should make the EPEL installation more explicit in my instructions.
The other group of users my RPMs target, aside from new users, are people like myself: systems engineers who use RPMs and RPM repos with the goal that scalable systems can be built/rebuilt automatically, with minimal interaction from an admin. Therefore I try to strike a balance between verbose, newbie-oriented HOWTOs and terse, ‘just give me the links’, experienced user-oriented instructions.
Thanks for the comment.
Hi John,
thanks for the rapid response :-)
Your work is awesome, everything installed cleanly (now I have used the line below to enable EPEL):
rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-3.noarch.rpm
Many thanks and keep up the great work!
Simon