GitLab

So, the scripts are now in clientside/tmcc/linux since they're the same
for any systemd-based Linux, and the centos7 and ubuntu15 makefiles
install those files.

Also had to improve fixup-fstab-swaps to handle the case where the / is
something like /dev/disk/by-uuid/<UUID> which is a symlink to the real
dev.  So try readlink -f to handle that.

include unreferenced target: sysetc-onceonly-install
	modified:   selinux-config
add emulab-fstab-fixup.service
add sysconfig/network
add sudoers
	modified:   sudoers
include verbage from dist sudoers, keeping our local changes

This commit is intended to makes the license status of Emulab and
ProtoGENI source files more clear.  It replaces license symbols like
"EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
blocks that contain actual license statements.

This change was driven by the fact that today, most people acquire and
track Emulab and ProtoGENI sources via git.

Before the Emulab source code was kept in git, the Flux Research Group
at the University of Utah would roll distributions by making tar
files.  As part of that process, the Flux Group would replace the
license symbols in the source files with actual license statements.

When the Flux Group moved to git, people outside of the group started
to see the source files with the "unexpanded" symbols.  This meant
that people acquired source files without actual license statements in
them.  All the relevant files had Utah *copyright* statements in them,
but without the expanded *license* statements, the licensing status of
the source files was unclear.

This commit is intended to clear up that confusion.

Most Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the Affero GNU General Public License, version 3
(AGPLv3).

Most Utah-copyrighted files related to ProtoGENI are distributed under
the terms of the GENI Public License, which is a BSD-like open-source
license.

Some Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the GNU Lesser General Public License, version 2.1
(LGPL).

In some cases systemd doesn't like our behavior of starting emulab services
from rc.local and killing them from the testbed service.  There's really no
reason to be doing it this way under systemd anyway, so make the testbed
service do both.

Need this when I create a client-side tarball, which does a client-install
with DESTDIR set.

directory.

Somewhere around fedora10, our ntp.conf file was causing ntp1.emulab.net
to no longer be able to update the clock on nodes.  Needed to un-restrict
access from that server.

Also, we were not going through our ntpd startup for f10 nodes.

broken.

rc.linux isn't fedora-specific in any way, so I moved it to the linux/ directory instead.

ala freebsd7/rc.freebsd.  We need this currently for the new remote nodes
where we have to load partition images and not a whole disk image (because
we download a copy of the image to the hard drive and we cannot have that
mounted and reload the entire disk).  Anyway, with a single partition image
the swap partition will not be "loaded", aka initialized, and we are left
without swap.  Now the rc.linux script takes care of that on first boot.

(linux), which is probably ok, but not optimal.

   No longer rely on looking at kernel boot time messages and extracting
   a hardware signature to determine the nodetype to then determine the
   control net.  Now we just DHCP on all interfaces and decree that the
   interface that answers is our control net interface.

   An extraordinary number of sleezy tricks were needed to get FBSD4,
   FBSD5, and RHL to DHCP on all interfaces without changing any standard
   scripts.

   For now, the nodetype/cpuspeed/chipset scripts still exist for the
   benefit of healthd, which uses the output of nodetype to determine
   what kernel module to load.  We should fix this.

   Side-effect: pump, the old RHL DHCP client, is history!  For older
   RHL releases, you will need a version of dhclient.

   Side-effect: in Linux, all non-control net interfaces are left up
   but without a legit IP address.  This is a consequence of dhclient.
   In FBSD, it was trivial to clean this up, RHL will take a little
   more work.  Up or down, it shouldn't matter.

2. Add an mfs-install make target, a scaled-down version of the client
   install.  Added a mandatory DESTDIR check so you don't accidentally
   install in the wrong place on boss.

touching a standard script

possible to:

	gmake client
	sudo gmake client-install

on a FBSD4, FBSD5, RHL7.3, and RHL9.0 client node.

There are still some dependencies that are not explicit and which would
prevent a build/install from working on a "clean" OS.  Two that I know of are:
you must install our version of the elvin libraries and you must install boost.