We are working on a new Distro Install Process as we speak.
The plan is to let you go through the normal Centos Setup screens with a full Centos ISO and than we will prompt you with a payload/version option for what version of the Distro you want to install and it would pull down the packages it needs for the Distro like Asterisk, Dahdi, FreePBX and such so the amount of time it spends pulling down packages from the Internet should be about 1/4 of what it currently is with the Net Install only option that we have.
Which brings be to this Blog.
We are trying to come up with a better version number for the Distro mainly because lots of people equate the 1.8.2.x-x with that we are either using Asterisk 1.8.2 or FreePBX 1.8.
What I am thinking of is as followed.
asteriskversion.freepbxversion.centosversion-minor release number.
So for example the next release would be
This would equate to a Asterisk 8.5 with FreePBX 2.9 and Centos 5.5
We will also have a
Which would equate to Asterisk 8.5 with FreePBX 2.9 and Centos 6.0.
I would love feedback from everyone on what they would like to see in regards to version numbering so we can polish off the new Full ISO builds for everyone this week.
This will also allow you to wget the setup script from our webserver and just execute the script on any stock Centos Machine to turn it into a full fledge FreePBX Distro system.
When you say “Asterisk 8.5”, I presume that you mean “Asterisk 1.8.5”. Is that correct?
In other words, the first three digits are the asterisk version, right?
I like the idea of installing CentOS and then using a script to make the needed modifications to become a FreePBX distro. I would recommend that you stick with only one version of CentOS at a time, though, as support becomes a pain due to the fact that you are no longer able to assume a number of things about a users’ system.
Also, it would make sense to have the user perform a specific type of CentOS install (minimal, or whichever) to begin.
I guess the main point is to avoid problems due to users having different underlying systems, whether due to different CentOS versions or different installed packages.
I don’t think so, because the upcoming version of Asterisk is version 10 so you can essentially see the current version as 8.5/8.6, because Digium communicated some time ago that the 1. prefix was meaningless and therefore discarded going forward.
I like the new concept and versioning scheme.
With CentOS 6.1 ready and synced to the mirrors beginning next week, and hopefully Asterisk 1.8.6 as well by that time, you’ll probably want to aim for a 188.8.131.52-1
What the the “1” in your versioning scheme stand for?
The 1 is just to start with a clean number versus 85. Maybe someday we will decide to use Fedora or some other Linux flavor so the 1 would become a 2 or something.
I am setting up a new network and want to use Free PBX and was wondering what the best hardware is to use for highest quality. Best Server, etc…
Please do not hijack a forum thread and start a new one with your questions.
Is there a beta/nightly build/… version available for testing?
Current 184.108.40.206 release doesn’t work for me.
Sorry we were pushing the new dahdi 2.5 to the yum servers and it was trying to grab those on install. All fixed now.
I would prefer to see the FreePbx version listed before the Asterisk version - since I would consider it to be the most significant when thinking of installing the FreePBXDistro.
I think you are likely to run in to issues with yum getting confused with the various component version numbers and thinking it can upgrade from one to another. It might be better to embed the target OS version number at least in the name, and possibly the Asterisk version number too - in a similar fashion to kernel versions, e.g. freepbx-distro6085-2.9-1 would be the FreePBX distro version 2.9 for CentOS 6.0 using Asterisk 8.5. Then an upgrade to say freepbx-distro6186 would only happen if it was explicitly requested.
Ok so the new version numbering at this point will be based on what I stated above. I have tested it thoroughly.
We are still fighting issues with Centos 6.0 but we will move in the mean time to the new version system and roll out a 220.127.116.11-1.
The big difference in this new version over the current 18.104.22.168 is it will include the latest dahdi 2.5 and asterisk 1.8.6. I hope to have it done this week still.
I propose including some text in the version numbers that makes clear what each number refers to. Also, using text would allow you to put the periods where they belong instead of between portions of the version number.
For example, using your latest example:
Alternatively, eliminate the text and use hyphens to separate the components, again so that you can put the periods where they belong, i.e.:
I personally do not like letters in my versions. It make it tough for updates since they are not true version numbers.
Okay, then eliminate the text and use hyphens to separate the components, again so that you can put the periods where they belong, i.e.:
“This will also allow you to wget the setup script from our webserver and just execute the script on any stock Centos Machine to turn it into a full fledge FreePBX Distro system.”
Is there any news about this feature. Where can I find link to the script.
It is being worked on and will come out in the future.