> ISO is meant to get you a running system. The idea is running yum to > install things after that, that are not critical to the operation of > the system is not difficult for users. Trying to keep the size <650MB > is getting harder and harder to do as sipXecs grows.
Right, that makes sense. That would indeed explain why some of these things would be missing. > if you have to call cpan to install modules, that's another story, > capturing anything other than rpms on the iso is very difficult, > simply because the OS on the ISO doesn't actually run until 2nd stage > of install. I don't know of any other way to add perl modules? In this case, I need DateTime::Format::ISO8601 in order to run regtimes. And in fact, I think that's just the first part of the missing modules once I get past that. I certainly would prefer running a system which is closer to what others on this list are running, so that I don't have to get stuck with installing so many additional things. Perhaps it would help in terms of being able to get to the tests which are suggested when I have problems. As it stands, many of the problems I've had lead to more problems to resolve before I can ever get to the tests being suggested. > there is a sipXiso project to build your own ISO with your own tools > preinstalled > http://wiki.sipfoundry.org/display/xecsdev/Building+Your+Own+CentOS+ISO I'm pretty sure I've always picked up my ISOs from http://sipxecssw.org/pub/sipXecs/ So, the above aren't the same? _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
