smartos-live | please join the SmartOS discussion list

The first step when building is to set up a build environment. The SmartOS build requires building on SmartOS. This can be done in VMware, on an existing SmartOS machine, or other virtualization. You must build inside of a non-global zone.
While you can build as the root user, we recommend that you create a user to do your day to day work as. If you do create that user there are two things that you should do:.
Make sure that the user has the 'Primary Administrator' privilege. There are occasional parts of the build that require administrator privileges and these will use pfexec to do so. To add a user to the primary administrator role, as the root user in the zone, you should run:
Make sure that the user's shell is set to /bin/bash. There have occasionally been build issues when using different shells. Ultimately, those are bugs. If you do use another shell and encounter issues, please tell us.
Once the build zone has been configured, you can kick off a build in a few easy steps:.
By default, running gmake live produces a directory and a tarball in the output directory. This can be used in Triton with the sdcadm commands and can be used to boot through ipxe or other network boot loaders.
When you kick off a smartos-live build (running gmake live), it will build components in the following order:. If you run gmake world instead of gmake live, then the build will stop after all of the components have been built.
illumos-extra bootstrap phase against the build system
illumos-joyent
illumos-extra main phase against the proto area
smartos-live src against the proto area
local projects against the proto area
assemble packaging manifests
assemble the platform tgz
world: Builds all the components
live: Assembles the live image from the built components
check: Runs various style and lint tools on code in smartos-live
clean: Removes built artifacts and intermediate objects
update: Updates all of the repositories to the latest
iso: Builds a CD-ROM ISO image, defaulting to the VGA console
usb: Builds a FAT 32 USB image, defaulting to the VGA console
This section is likely to only interest users who perform release builds of SmartOS, or the Triton Platform Image.
common-release: depends on check, live and pkgsrc targets and needs to be run before a subsequent make invocation of any of the -release targets below
smartos-release: builds, publishes and uploads SmartOS artifacts
triton-release: builds, publishes and uploads a Triton platform image
triton-and-smartos-release: all of the above
*-publish: stage bits from the output directory, preparing for upload
*-bits-upload: upload bits to either Manta, a remote filesystem and optionally, a Triton imgapi instance, defaulting to updates.joyent.com
*-bits-upload-latest: as above, except attempt to re-upload the latest built bits, useful in case of interrupted uploads
ENGBLD_DEST_OUT_PATH: The path where we wish to upload bits. This is assumed to be relative to $MANTA_USER if using a Manta path. Otherwise this can be set to a local (or NFS) path where we wish to upload build arifacts.
ENGBLD_BITS_UPLOAD_LOCAL: If set to true, this causes us to simply cp(1) bits to $ENGBLD_DEST_OUT_PATH rather than upload using Manta tools.
ENGBLD_BITS_UPLOAD_IMGAPI: If set to true, this causes the build to also attempt to upload any Triton images found in the output/bits directory to an imgapi instance, which defaults to updates.joyent.com.
MANTA_USER
MANTA_KEY_ID
MANTA_URL
UPDATES_IMGADM_URL
UPDATES_IMGADM_IDENTITY
UPDATES_IMGADM_CHANNEL
UPDATES_IMGADM_USER
Several variables can also be set in a shell script at the top of the smartos-live repository called configure-build and are sourced by configure if this file exists. This allows you to override configure script defaults, or include additional pre-build customization.