The behavior of Slinky can be automatically customized in several ways. This allows system builders to develop their custom version of low-resource optimized Fedora Core with the smallest possible effort. This guide explains how to do it. Right now, the most complete and updated description of how Slinky works, listing all phases and components can be configured to achieve automated custom installs, is the right half of the Slinky block diagram by F. Zahaurek. Eventually, this page will contain a detailed description of each single section of that diagram. In the meantime the initial description of Slinky internals by M. Fratoni is still available here and useful, even if outdated. It also describes the pivot-root part of the process.
Related Resources and examples
Slinky has already been successfully customized to build the vum BOX for some Congo Schools. In that occasion, Ingo Lantschner and others produced a VUM Manual describing how they did it. That manual is still very useful as a reference, both as-is or to (re)write this Guide. There is also an Html compressed version. F. Zahaurek has already published a first version of this Guide that will be copied here soon. In this way all RULE members will be able to contribute to it. In the meantime, everybody interested in building Slinky can read how to do it on Franz’s page and ask questions, post patches and so on, directly on the RULE mailing list.