EncapPackages | EncapReadme | EncapPlatforms | EncapInstall | EncapHowto


The encap packages are not currently being maintained. This page is still here mostly for historical interest. The previous maintainer no longer has to support a large number of platforms, but would be happy to mentor a new maintainer; just mail the mailing list? if interested.


bcfg2 encap packages

As an alternative to the distribution-specific bcfg2 binary packages which exist for some platforms, or building from scratch from source,  encap profiles of bcfg2 and all of the software it depends on are available, and are known to compile on many versions of AIX, BSD, GNU/Linux, Solaris, and Solaris/x86. Additional platforms should be trivial to add.

The encap_profile(5)s use mkencap(1) to compile to binary  encap packages.

For convenience  GNU Makefiles are supplied to automate most of this process, so all you have to do is make sure GNU make, gcc, and epkg are installed, and then type "make" (or "gmake" on non-GNU platforms).

You can install the server components manually with epkg(1) (a tool like dpkg/rpm/pkgadd that works the same way on all platforms).

A complete client install methodology, which lets you install, with one command, a new bcfg2 client configured for your environment, is included. All of the client encap packages and a local site configuration encap package are bundled into a single executable file with a setup script with  makeself. Installing a new client becomes a matter of just executing that file on the target machine.

It is recommended to compile from source, however if you have issues open a ticket and assign to "dclark", and he'll try to help you out (either with your compile or by supplying binary encap packages for your platforms).

Details on this process (which you should read in their entirety) are supplied in EncapReadme and EncapInstall. A list of successfully bootstrapped platforms is in EncapPlatforms.

Source Code

Current State