vicidial.org

Hi
I have been following Vicidial pretty closely over a few years now. I am trying to understand everything about it and I have also been using it. I was curious about how the Installer .ISO is created? Like which tools do you guys use and how you go about the process?
I don't want generic ISO creation pointers, as I know about remastersys and the like. I was looking for your specific method.
Thanks guys for the great product and expecting an insight into my question...
Cheers & Merry Christmas!!

You will note that the .iso actually states the software that was used to create it.

Suse Studio.

The ISO is built using susestudio.com

The yast installer and behaviour is modified through various yast2 control.xml files.

The rest is a custom-written perl script that tries to patch all the various installation methods together.

We tried doing it the hard way, by building a distro tree and feeding it into an ISO build and etc, but susestudio just took away the headache. It's very easy as long as you like SuSE.

Is it possible to download the configurations and stuff used in the vicibox iso?
because right now I'm using virtualbox to look at the install scripts and stuff, and for some reason the network wont work so i cant get the file off virtualbox.

I've tried to extract the files directly from the iso, but the filesystem is clicfs which only SuSE uses so it wont work on any other distro,
tried compiling it (http://gitorious.org/+opensuse-develope ... use/clicfs) but failed.
tried the filesystem in openSuSE but that failed too...

and is there any svn-like environment I can look at the files and changes?

DomeDan wrote:Is it possible to download the configurations and stuff used in the vicibox iso?
because right now I'm using virtualbox to look at the install scripts and stuff, and for some reason the network wont work so i cant get the file off virtualbox.

I use VirtualBox for all facets of testing ViciBox except the preload ISO and it works fine. Try putting the network adapter into bridged mode with the onboard NIC and see if that works. You should be able to simply transfer the files you want use FileZilla and SFTP. If you can SSH to the instance then you can SFTP to it.

I don't really have any plans of making my SuseStudio build available for cloning. With the exception of a few files in the OS, all the additional files are in /usr/src/astguiclient. The notable exceptions are things in /usr/local/bin and the control.xml files for the installer, php.ini and some things like ntp.conf etc. I guess I could look into making an SVN repo for check-out but i'm not quite sure how I would organize it at this point. Would have to think about that a bit.

Tried the same virtual machine and just changed the iso to 4.0.2 and then the network interface is found when vicibox is booted, strange but whatever.. it works!
I see you added vim-data that's great, now I don't even need to get the files off the iso ^^