FreeNAS Code

GUI bits for loader.conf entries

GUI part for sysctl stuff

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

Blast, args were backwards.

Produce a date representation that actually matches date(1) without any arguments supplied (in particular, add the timezone to remove any ambiguity related to time locale).

time.localtime() is not needed when calling time.asctime() since it's the
default when parameter is omitted.

Submitted by: gcooper

Use localtime() instead of gmtime().

let the browser show files as well for iscsi file extent

Add FreeNAS version when saving config.

The uploaded config file is actually still in memory at the time that the upload is being performed. Thus, we can't trust the file attribute to point to something sane.

So, we're back to writing to a temp file, then reading it back.