This is both a simple test case of .deb to .tcz importing and a replacement for the lshw-B.02.15 included in TCL4, which doesn't play nice with TCL5-alpha4.
MCollective was running as an external service. It used a static configuration accessible to anyone who accessed the source, and which could connect to an external master. This was considered a security threat in the security evaluation. This commit removes MCollective completely. The impact of doing this should be zero since it wasn't currently used.
…s.tar.gz gzipped tarfile and added these files to the Razor-Microkernel project instead. Also added a third file (etc/shadow-nologin) to the project. This third file is used for production systems (where we want to disable login by any user, even at the console). Finally, made changes to the build-dependency-files.sh script to copy over the appropriate pair of files (etc/passwd and etc/shadow for development systems; etc/passwd and etc/shadow-nologin for production systems) into what will be the /etc/passwd and /etc/shadow files on the ISO we are building.
…ract from the util-linux.tcz extension
…u' and 'sfdisk' commands for the ISO directly from a downloaded version of the util-linux.tcz extension, for example, instead of bundling these two executables in a separate gzipped tarfile). Also added a set of flags to the build-dependency-files.sh script (using the getopt built-in under BASH) that give the user the ability to point to their own built-list and mirror-list (instead of having these values 'hardwired' into the build-dependency-files.sh script). Finally, added a couple of flags that allow the user to specify if they going to be building a production or development ISO. In the case of a production ISO, the name of the file created by the rebuild_iso.sh script is changed to include 'prod' instead of 'dev' in its name, the openssh.tcz extension is skipped (along with it's configuration files), and passwd/shadow files are also skipped. These last two changes effectively remove the ability to access the Microkernel, either remotely via SSH or via the console, which is a key feature in a production system.
…build a separate overlay for the extensions that need to be installed at boot, nor is there a separate overlay for the MCollective install. All of the components are now dynamically downloaded by the 'build-dependency-files.sh' script (unless the user specifies that the previous downloads should be used via the '--reuse-prev-dl' flag). The only remaining dependencies that are not automatically included by this script are the configuration files for the openssh and mcollective installs, the lscpu and sfdisk executables, and the open_vm_tools extension we built for the Microkernel. These dependencies are all pulled into the image from the 'additional-build-files' directory (which is at the top-level of this project).