[asterisk-dev] Zaptel project being renamed to DAHDI

Jeffrey Ollie jeff at ocjtech.us
Tue May 20 23:55:46 CDT 2008

On Tue, May 20, 2008 at 5:59 PM, Tilghman Lesher
<tilghman at mail.jeffandtilghman.com> wrote:
> On Tuesday 20 May 2008 17:08:25 John Lange wrote:
>> It would be great to finally break the tie between specific versions of
>> Asterisk->Zaptel->Kernel so easier packaging could take place.
> That is unlikely to happen.  The main reason why the move towards
> integration with the kernel was rejected

I think that Kevin posted the real reason earlier - Digium wants to
retain the ability to dual-license the code. Hey, it's Digium's code
so they get to write the rules.  I'd prefer it if Digium chose
differently but I don't have the time/energy/skill to get the drivers
into shape for inclusion into the kernel myself.

> was a practical one: given the length of kernel release cycles

Uh, what?  The Linux kernel releases a new version every 3-4 months.
Between 2.6.24 and 2.6.25 there were over 750K lines of code changes:

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
$ cd linux-2.6
$ git diff --shortstat v2.6.24..v2.6.25
 9738 files changed, 777371 insertions(+), 404514 deletions(-)

I fail to see how that could be described as "lengthy".

> Along with the kernel API changes made in each minor release,

Yes, but when the kernel API changes the kernel developers update all
of the in-kernel drivers for you.  Yeah, you'd have to check that they
didn't break anything but you have to do that work anyway when a new
kernel version is released.


More information about the asterisk-dev mailing list