I thought I could try to post this question here since I have at times found excellent support here on A@H issues as well as pure/straight digium/asterisk issues. I am looking to finally build a permanent asterisk server and would prefer, if at all possible, to stick with the "new" A@H called trixbox. Does anyone know if the CentOS behind trixbox is a relatively complete CentOS system? I have various other gateway services I would liek to run and would like to consider it a full-blown CentOS system, where I could use any/all docs/guides/updates etc, as for a stand-alone CentOS install? Or, am I better off simply installing CentOS (latest), and do a bare-bones asterisk/hudlite etc, install? I have only installed asterisk through various version of A@H and would like to avoid a painfull, lengthy manual install and configuration, as well as managing updates. Trixbox now uses tidy, simple binary rpms for updates so this will go along ways to ensuring stable/simple/quick upgrades. Thanks for any suggestions :) --------------------------------------------- Johnny Stork Open Enterprise Solutions http://www.openenterprise.ca http://www.johnnystork.ca -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060606/2627e278/attachment.htm
Johnny Stork wrote:> CentOS behind trixbox is a relatively complete CentOS system?The installation of CentOS is sufficient to support TrixBox, but you can always add additional packages using yum. cYa, Avi -- National Manager - Special Projects < Sydney / Melbourne / Canberra / Hobart / London /> 2/340 Gore Street T: +61 (0) 3 9235 5400 Fitzroy, VIC F: +61 (0) 3 9235 5444 3065 W: http://www.squiz.net/ .....>> Open Source - Own it - Squiz.net ...../>
> The installation of CentOS is sufficient to support TrixBox, but youcan> always add additional packages using yum. >If you download the iso and view it then you can see which packages Trixbox loads by default. On the CD or in the iso file find this directory: /CentOS/RPMS/ In it are all of the packages that Trixbox installs during the CentOS installation. Afterward, the Trixbox install process runs the script install.sh - open it up and you'll see a line that says yum -y install alsa-utils audiofile-devel bison <etc.> That will give you the list of packages that Trixbox will start with. I would recommend starting with the Trixbox install and then adding what you need. It is much easier (IMO) and keeps things clean. One package that I add immediately is samba-client.i386 - I need to communicate with several Samba servers right after a new install, so I just do: yum install samba-client.i386 All done! If you know which packages you want to add you can manually yum them one at a time, or you could write a script with a line like the one in install.sh. Personally, I modified the install.sh script, added a few other goodies, created a new iso file and burned a brand new CD that installs Trixbox with my customizations. This is useful for creating a backup as well. I keep a copy of my *conf files on another server, and after the Trixbox install I have a script go grab them and put them in /etc/asterisk. Very convenient for those of us who'd rather write Perl and shell scripts than manually copy a bunch of files all over the place. HtH! -MC