[asterisk-users] DAHDI, and 64 bit machine

[bilal ghayyad]

Hi David;

But why in Dahdi there is a kernel package and tool package while in zaptel there were not such thing, we were download zaptel only. Why they separated them in Dahdi?

Now, regarding to compilation and installation:
1) Why when using the complete package, I do not need to do the ./configure while I need to do this if I am trying to compile and install the dahdi-tools?

2) Why I need to write make all when I am trying to compile and install the dahdi-linux-complete? In other words, why to use make all and does not use make only?

Regards
Bilal

-----------------
> > To download, compile and install DAHDI, do I need to
> download the both (dahdi-kernel and dahdi-tools) If yes,
> then do I need to do the compilation and installation
> command for each package? What is the method to download,
> compile and install the both packages as one package?
> 
> depends on your OS. You may be able to find compatible
> pre-compiled
> packages for your distribution. But compiling will work
> too. When you
> download the packages there are instructions inside in
> conveniently
> named files like README.
> 
> > By the way: Why there is dahdi-kernel and dahdi-tools?
> In other words, for what the kernel is used and for what the
> tools is used? And why they called the dahdi-kernel in that
> name (related it to the kernel? to which kernel?)
> 
> the kernel package contains the kernel drivers source
> code.
> the tools package contains the tools source code.
> Drivers make the hardware talk to the kernel.
> Tools make the drivers tell the hardware what you want them
> to do,
> query status, etc.
> 
> > About the 64 bit machine:
> > If my machine is 64 bit, does that effect on selecting
> the DAHDI and the Asterisk version? Or All work for 64 and
> 32? I know that in codecs, there is a difference in the
> machine is 64 or 32, but what in the Asterisk and DAHDI?
> 
> No. The compilation process auto-detects your system
> settings and
> builds correctly.