...
Additional Information
Customizing
You don't have Reasons to customize your CD, If you the ISO
- ISO makes a lot of assumptions about your system. US locale for example, size of the disk for auto-formatting is greater than 13GB, the default size of the partitons, etc. To change these, you must customize the ISO
- If you want to brand the ISO with your company logos, colors or welcome messages
- If you want to include extra RPMs by default
If you don't you'll produce the standard SIPfoundry ISO and may be all that you desire. If you do decide to customize, then to create you're own spash screen or kickstart file, create a separate directory with these to hold your custom files and configure your build to use this directory. For example ./configure ... OEM_DIR=~/work/ezuce
Contents of ~/work/ezuce
iso.mak.in - override various make variables used to create the ISO. See Makefile.in for a list of all the variables you could override. Here is an example
| No Format |
|---|
SPLASH_FILE = <at:var at:name="OEM_DIR" />/splash.lss ISO_LABEL ?= ezuce VOLUME_LABEL ?= "ezuce <at:var at:name="PACKAGE_VERSION" />" APPLICATION_LABEL ?= "ezuce <at:var at:name="PACKAGE_VERSION" />" PUBLISHER_ID ?= dhubler@ezuce.com PREPARERER_ID ?= dhubler@ezuce.com |
oem.m4 - Contains M4 macros that you can use to extend the kickstart file. Look in ks.m4 for an idea of the hooks that are currently in place you can alter. Here is an example
| No Format |
|---|
define(`sipx_packages', sipx_packages() ezuce ) define(`welcome_message', Welcome to eZuce ============================= First time logon: user = root password = setup ) define(`repo_contents', [ezuce] name=ezuce CentOS \$releasever - \$basearch baseurl=http://download.example.com/ezuce/PACKAGE_VERSION()/CentOS_\$releasever/ enabled=1 gpgcheck=0 ) |
splash.lss - this is a graphic that is the initial splash screen and is in a format that is not well supported, but google around for how to edit this file on your OS.