As to your second question: I think Mark would probably donate a T100P and/or X100P to the cause, even if only temporarily, and I can certainly do the same as I have some hardware resources at the moment (though no PRI's to loan out, I have the cards and spare systems.)
JT
At 10:11 AM -0500 1/14/04, Troy Settle wrote:
John,
I thought you might be interested. I don't know the particulars about driver portability between the BSD's, but it seems that at least on x86 hardware, it should be fairly easy. I'll include those 2 in the bounty.
I'm not sure what hier(1) has on the other BSDs, but in FreeBSD it is completely acceptable and desirable to have /usr/local/etc/ for local configurations. /, /usr are only for the base OS.
Of course, these are simple build-time configuration options to have. Each OS (even each linux distro) has it's own heir(1) scheme, perhaps the work to get a clean and proper installation of asterisk on FreeBSD will prompt the developers to also have asterisk install itself properly on other platforms obeying their respective hierarchies.
John, Do you think you could talk Mark into making some hardware available for test/development platforms if we end up with a non-digium person attacking this?
-- Troy Settle Pulaski Networks http://www.psknet.com 540.994.4254 ~ 866.477.5638 Pulaski Chamber 2002 Small Business Of The Year
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Todd Sent: Wednesday, January 14, 2004 9:22 AM To: [EMAIL PROTECTED] Subject: RE: [Asterisk-Users] Asterisk on FreeBSD 4.9?
>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> "hood is open". MacOS is a different animal, and (IMHO) lower on the> [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"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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
