FreeNAS Code

Build system, branding, and image size enhancements.

Overall:

- Use variables instead of hardcoded and relative path based assumptions.
- Change branding from FreeNAS to a (largely) build driven variable name to simplify muxing between FreeNAS and TrueNAS.
- Rename /etc/version.freenas to /etc/version .
- Change the version info to <sw-name>-<version>-<revision>-<arch>, e.g.
FreeNAS-8.1-r7817-amd64 .

build/do_build.sh:

- Simplify arguments for forcing builds again to -f (no args), based on feedback from jpaetzel.
- Use variables as necessary.
- Add alpha support for unionfs based builds. This doesn't work with UFS SU+J on 9.0-BETA1+, so caveat emptor.

build/functions.sh:

- Consolidate build-related functions into a single file for simplicity.

build/nano_env:

- Add a file which contains the master info for how a build is performed.

gui/...:

- Chase the changes done above, but try to simplify / improve how things are done, emitting more diagnostic info than before.

nanobsd/common:

1. Allow the end user to specify the number of CPUS in the environment if they want, instead of hardcoding $CPUS + 1.
2. Nuke .pyc files. They're created automatically by They'll get regenerated on the fly once they're read in again by the interpreter.
3. Nuke the headers (minus the pyconfig.h -- it's required at runtime) since we're not compiling binaries (cc, etc isn't included in the final image).
4. Nuke all of perl the right way if $DEBUG == 1.

Misc:
nanobsd/freenas-common:

- Start features based build tunables for

Improve/correct the top-level build script. In particular:
1. Fix the optimization which assumes that if the obj
directory is present then buildworld/buildkernel will
not need to be run. That is false if you provided the
-f option in the past, and as such would just generate
bogus images lacking new src features/patches.
2. Provide fine grained tuning of -f ports|all.
Rebuilding/not rebuilding ports has no effect today,
but it will in the future.
3. Print out a simple error message at the end if the
nanobsd build failed because nanobsd is extremely
quiet when things fail (except in terms of the exit
code).
4. Add a usage message and simple examples.
5. Update documentation.

Make forcing updates easier to grok and document them.

Add a hint pointing to the SF svn page for
those who may not be intimately familiar
with how SF looks/works.

A lot has changed in the last 8 months. Update the README
to reflect that.

Correct svn repo URL. Minor nit in advice fixed.

Upgrade build to 8.2-beta1

Document that i386 builds on amd64 work.

fix some typos, and update to include ISO.

We've moved! Yea!