Hi All; 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? 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?) 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? regards Bilal
On Sat, Jun 6, 2009 at 5:33 AM, bilal ghayyad <bilmar_gh at yahoo.com> wrote:> 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.
bilal ghayyad schrieb:> To download, compile and install DAHDI, do I need to download the both (dahdi-kernel and dahdi-tools)Yes. You can either get http://downloads.asterisk.org/pub/telephony/dahdi-linux/ and http://downloads.asterisk.org/pub/telephony/dahdi-tools/ or use the combined tarball http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/> If yes, then do I need to do the compilation and installation command for each package?Yes if you download both tarballs separately. The "complete" tarball automates it for you.> What is the method to download, compile and install the both packages as one package?cd /usr/src wget dahdi-...tar.gz tar -xvzf dahdi-...tar.gz cd dahdi-...tar.gz less README* Philipp Kempgen -- AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -> http://www.amooma.de Gesch?ftsf?hrer: Stefan Wintermeyer, Handelsregister: Neuwied B14998 Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de Videos of the AMOOCON VoIP conference 2009 -> http://www.amoocon.de --
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.
bilal ghayyad schrieb:> 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.Both -kernel and -tools were in Zaptel as well. They were just not separated in 2 tarballs.> Why they separated them in Dahdi?Cleanliness?> 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?Because the Makefile in the "-complete" tarball automatically calls ./configure for you.> 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?Maybe only "make" works. Give it a try. If make is called without a target it tries to run the first target in the Makefile which usually happens to be "all". Philipp Kempgen -- AMOOMA GmbH - Bachstr. 126 - 56566 Neuwied -> http://www.amooma.de Gesch?ftsf?hrer: Stefan Wintermeyer, Handelsregister: Neuwied B14998 Asterisk: http://the-asterisk-book.com - http://das-asterisk-buch.de Videos of the AMOOCON VoIP conference 2009 -> http://www.amoocon.de --
On Sat, Jun 06, 2009 at 02:33:28AM -0700, bilal ghayyad wrote:> > 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 basic idea is that dahdi-linux is the linux-specific part whereas dahdi-tools should be os-independent. I'm not really sure that this is the case with the dahdi-perl scripts (that rely heavily on the procfs and sysfs interfaces) and the ppp module in dahdi tools.> > 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?As I regularily use DAHDI drivers on my 64bit laptop, I can say it works rather well :-) One limitation: if dahdi is built as a module for a 64bit kernel, it will not support 32bit userspace clients. This is normally not something that you do, though. https://issues.asterisk.org/view.php?id=14808 -- Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen at xorcom.com +972-50-7952406 mailto:tzafrir.cohen at xorcom.com http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir