Customisation
From M L Vision Network Services Wiki
There are a number of ways to customise the resulting image. Most users are going to need to add extra extensions or plugins. There will often also be a need to change the device identification within plist files. I have provided the capability to do these easily.
The file and directory structure of the package is as follows:
| Root | Subfolder (If Applicable) | Description |
|---|---|---|
| files | extensions | Any extensions added to this directory will be added to the DVD. Permissions and ownership are not important as they will set correctly when they are copied. |
| extensions.disabled | Any extensions you don't want included can be stored here. This is useful when experimenting. | |
| plugins | Any plugin added to this directory will be added to the DVD. Make sure it is a valid plugin (the plist shows you the dependency order and often the first entry in OSBundleLibraries is the actual owning extensions). | |
| plugins.disabled | Any plugins you don't want included can be stored here. This is useful when experimenting. | |
| deviceid | Any extension or plugin that needs a PCI device id added to it needs a manifest file. There are 2 examples in the directory to help you create these. There are 4 variables that define how to edit the plist.
| |
| devideid.disabled | Any manifest files you don't want included can be stored here. This is useful when experimenting | |
| updates | Any Mac OS X update file (in DMG format) placed here will be added to the installer. There is appoximately 200MB of free space for updates so be careful not to exceed this or you will need to build an image with dual layer support. Multiple updates should be support but it is a better choice to use a single combo updater (Intel preferable for size reasons) | |
| updates.disabled | Any update file you don't want included can be stored here. This is useful when experimenting | |
| kernel | Custom kernels are stored here. They are delta files built with xdelta and only contain the differences between the stock kernel and the custom kernel. The version string in the main script controls which file is used | |
| boot | Boot files are stored here. The only file that might need to be changed is boot.pcefi (which is the EFI boot loader) and as new versions are released can be overwritten | |
| tools | Supporting tools are stored here. There should be no need to make changes to this directory | |
| images | The original DMG must be copied here for the script to run. The resulting ISO file will also be copied here. Intermediary images will also exist here but can be deleted if space is a premium | |
| slipstream | The core script file |
