[Asterisk-Users] Asterisk on FreeBSD 4.9?

Wed Jan 14 10:15:52 MST 2004

The way to get this work done is in steps.  Some of these
steps will help everyone.  This is good as the more people
a step helps the more likely it is to get done.

1) First priority.  Make a GNU "Autotools" build system for
   Asterisk.  Thiat is one that uses a ./configure script
   There is a patch or "asterisk versin that
   does this already.  Priority #1 is to get this tested
   and into CVS.  It is an absolute pain in the but to
   support multiple platforms with this.  And the work
   is already done, except for testing and CVS checkin

   This work will help people wanting a Sun SPARC/Solaris
   or a Mac OSX version too.

   The GNU/Autotools build system allows a user to define
   $PREFIX which is where the packe will go.  The default
   is /usr/local just where is needs to be

2) Write the device drivers.  But FIRST re-organize them
   so the "guts" of the hardware specific stuff is not mixed
   up with the interface to the OS.  Get this re-organization
   to work under Linux first.

   This work will help the Linux users as newer versions of
   for Linux kernel come out.  Linus has said that he does
   not care if new kernels break drivers, we will need to
   livewith this.  Being multi-OS will help with being
   multi-kernel-version

3) IS there any BSD-specific stuff left?

Actually I'd like to eee Asterisk on Solaris.  If you want
a "five nines" system Solaris is almost there if you buy
the "right" SPARC hardware.  And you could likely fit a
dozen or so Digium cards 4 port T1 cards in a big Sun server

--- John Todd <jtodd at loligo.com> wrote:
> >I'm about to post on bugs to offer a bounty for work on FreeBSD. 
> I'm
> >fairly certain that others will come along to increase that bounty.
> >
> >Before I do post it, I would like some input on what the
> requirements
> >should be.  Here's what I have so far:
> >
> >  - Must be completed before 6/30/04
> >  - Support for all Zaptel hardware
> >  - Commitment of the drivers to both
> >    4-STABLE and 5-CURRENT/STABLE
> >
> >I'm not completely conversant on how GPL software can be committed
> to
> >the kernel, but I believe it can be done under the contrib/
> directory.
> >
> >I do not want this work to exist as a series of
> >downloads/checkouts/patches/modules if it can be avoided.  I don't
> want
> >to patch my kernel or load modules.  I want to be able to do a cvsup
> on
> >/usr/src, add necessary device entries to my kernel config file and
> >build it.
> >
> >I'd like to see astersk and libpri installs follow the
> reccomendations
> >and requirements found in the FreeBSD hier(1) man page. 
> Specifically,
> >it should install completely to /usr/local/.  Preferrably, I'd like
> to
> >see a port created for both asterisk and libpri, even just a
> metaport
> >that uses CVS to fetch the source and any OS-specific patches.
> >
> >Any comments before I post the bounty?  I will recommend that those
> with
> >suggestions on the requirements and those that offer additional
> bounties
> >for this will sit in committee to determine when the requirements of
> the
> >bounty have been met.
> >
> >--
> >   Troy Settle
> >   Pulaski Networks
> >   http://www.psknet.com
> >   866.477.5638
> >
> [snip]
> 
> Troy -
>    While it is not 100% relevant to your requests, I'd like to see 
> continued support of NetBSD/OpenBSD in this same vein and added to 
> the bounty, since the additional work to get things correctly 
> functioning on those two systems seems to be fairly minor while the 
> "hood is open".  MacOS is a different animal, and (IMHO) lower on the
> 
> "must-have" list when it comes to Zap device support, though it would
> 
> still be cool.
> 
>    If OpenBSD (1st choice) and NetBSD (2nd choice) can be added for 
> Zap device support, count me in on the bounty.  Talk to me privately 
> if you want to get a dollar figure.  I've had * running on OpenBSD, 
> but of course no Zap hardware.  I'd move everything over to OpenBSD 
> if it supported Zap, since that's my primary OS for all the platforms
> 
> in my network.  While Linux in it's various flavors is great, it's 
> simply not what my network runs, and so my * boxes are the "odd man 
> out" systems, which makes me somewhat uncomfortable from a security 
> and management perspective.
> 
>    Additionally, if files are to be installed in /usr/local, then I'd
> 
> like to see the configs remain in /etc/asterisk since on my systems 
> (and many other people's) the /usr/ directories are for binaries 
> only; no configurations or "moving parts" so those directories can be
> 
> mounted read-only or mounted from a common server if necessary.  I'm 
> sure this is what you meant, but I've seen config directories 
> unwisely located in /usr/local before, and I wanted to make sure 
> everyone is of the same mind where that is concerned.
> 
> JT
> 
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

=====
Chris Albertson
  Home:   310-376-1029  chrisalbertson90278 at yahoo.com
  Cell:   310-990-7550
  Office: 310-336-5189  Christopher.J.Albertson at aero.org
  KG6OMK

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus