>>> Aza Tek 04/16/11 5:56 PM >>> >>Yes it's a purpose built application, but it can be extended with other >>functionality on a single machine. >>Personal Experience: I used CentOS, Ubuntu Server and Debian, and have found >>Ubuntu Server/Debian environments to be a bit more reliable.
While I'm not a Ubuntu user, I do see value in supporting multiple distros. Each distro has a number of difference that a particular users may begin to rely on. The location of conf files for networking, dns etc vary between distros..and can be a learning curve even for moderate experinced linux users. If your a linux admin and supporting 10 other ubuntu servers, uniformity makes the platform easier to manage. Furthermore distro specific tools might want to be leveraged. For example we maintain our own Suse SLE builds of SipX. We use several tools that integrate with SLE like Lifecycle Manager, which allows customer appliances to check-in, get security patches and push new version upgrades all while tracking support contracts etc.....its a tool we love. Also because our other appliances run SLE that means our tech support staff can begin basic diagnostics on any system whether its sipx or not. And we also get Novell Tech supported as a "certified" SLE appliance when issues arise. With all that said, it is certainly not eZuce or any other corp sponsors responsibility to maintain a distro they do not deploy. Should the project community want it, then we the community should build it and house it just like the Suse builds. The developer community and sponsors are always eager to help with build questions. So there is nothing stopping any Ubuntu user to take this charge and maintain that part of the repo. I think we would all welcome greater involvement. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
