FreeNAS Code

Mute the add_port noise and add something a bit more meaningful instead if make package-name fails.

Use make in this one spot so it doesn't inject -DNO_CLEAN if and when -n is specified on the CLI to nanobsd.sh ;).

Use NANO_PMAKE and more consistent design patterns without going overboard and rototilling things unnecessarily.

Readd telnet for debugging purposes.

Add an easy knob for adding/removing additional directories not iterated over via buildworld/installworld (NANO_LOCAL_DIRS).

Please use do_build.sh -f -- -k after changing this feature to rerun buildworld and installworld.

Where did my /var/db/pkg go... >.<?

Print out what we're running add_port against so if something
fails when running make package-name, etc.. it's easy to
identify what the culprit is without having to do do_build.sh
with set -x.

We autogenerate sshd_config from ix-sshd, so there's no reason why we need to generate it in nanobsd.

Add knobs for building more legitimate debug images.

Signed-off-by: Garrett Cooper <yanegomi@...>

1. Move all FreeNAS specific build items from nanobsd/common to nanobsd/freenas-common as the intended purpose (from what I gather and based on past experience working with imp@) is that all items in common should really be moved to nano
bsd.com in one form or another.
2. Remove redundant functions.
3. Add proper pretty printing for functions to have build logs that we can properly diagnose in the event of failure.
4. Properly strip binaries so that we get images that have debug symbols if DEBUG is defined in SW_FEATURES; in particular, debug symbols weren't being stripped from the libraries. Eventually it would be nice to move to a paradigm like the following:

objcopy --only-keep-debug bin_or_lib symbols
strip bin_or_lib

The way we won't need to differentiate between a debug and release image except in terms of what additional developer tools are included in the image.

Signed-off-by: Garrett Cooper <yanegomi@...>