GitLab

Use cygrunsrv -i on sshd to "allow the service to interact with the desktop."
Now that the sshd daemon has a desktop session context that is inherited by
the client shell, remote home directories can work.  They start with a blank
Windows mount context, but once a single Samba connection is made during
login, it enables all UNC //machine/path mounts to work.  Hence the home
directories are now CygWin mount points (no longer symlinks) to UNC paths, set
up by rc.mounts and then shared through CygWin to all of the user logins.

Get rid of the previous horrible (and fragile) hack to set up an auto-login by
the swapin user which then automatically started a user sshd on port 2222.

tmcd.c - Arrange for tmcd to provide the public key data when a special argument is
given as "tmcc accounts pubkeys".

rc.accounts - Due to permissions problems with remote-mounted authorized_keys
files, sshd_config now uses "AuthorizedKeysFile /sshkeys/%u/authorized_keys",
which is where rc.accounts puts the public key data.

Since root, Administrator, and even SYSTEM can be locked out by permissions on
NT, WINDOWS() variant logic to set ownership and modes on authorized_keys
files had to be added to rc.accounts.  There is also a bug in the sshd
"privilege separation" setreuid() dance that requires the authorized_keys
files to be owned by SYSTEM (or be mode 644, which is slightly worse.)

cygwinxp/liblocsetup.pm - Pay attention to the users' shell preferences in
generating /etc/passwd.  Make warnings more uniform.

openssl.

Cross compilation fixes for the stargates, 'gmake client' should now
build, link, and install properly.  Haven't really tried to run stuff though.

	* GNUmakerules: Add target for stripping executables, used instead
	of "install -s" since that doesn't work for cross-compiling.

	* Makeconf.in: Add ELVIN_CONFIG variable that refers to
	'elvin-config'.

	* configure, configure.in: Detect and save the elvin-config path
	since we need a different one for cross-compiling.

	* event/lib/GNUmakefile.in, event/link-agent/GNUmakefile.in,
	event/linktest/GNUmakefile.in, event/program-agent/GNUmakefile.in,
	event/proxy/GNUmakefile.in, event/tbgen/GNUmakefile.in,
	event/trafgen/GNUmakefile.in, os/dijkstra/GNUmakefile.in,
	os/syncd/GNUmakefile.in, sensors/slothd/GNUmakefile.in,
	tmcd/GNUmakefile.in, tmcd/linux/GNUmakefile.in: Cross compilation
	fixes, don't statically link on arm, create "foo-debug"
	executables with debugging info and install separately stripped
	ones instead of passing "-s" to install.

Pass camera config to vmcd in the config_vmc packet and add support
for using unix-domain sockets when talking to emcd instead of
unsecured tcp sockets.

	* robots/emc/emcd.c: Add support for camera configs in the config
	file and add support for listening on a unix-domain socket.

	* robots/emc/test_emcd.config, robots/emc/test_emcd.sh.in: Update
	for changes to emcd.

	* robots/mtp/mtp.h, robots/mtp/mtp.c, robots/mtp/mtp.x,
	robots/mtp/mtp_send.c: Add camera config to the config_vmc packet
	and add support for unix-domain sockets.

	* robots/primotion/GNUmakefile.in: Add empty install target.

	* robots/rmcd/rmcd.c, robots/rmcd/test_emcd.config: Add support
	for unix-domain sockets.

	* robots/vmcd/vmcd.c: Add support for unix-domain sockets and read
	the camera config from the config_vmc packet.

	* robots/vmcd/test_vmc*.sh: Fix tests changed by my last checkin.

	* robots/vmcd/test_emcd*.config: Update for changes to the emcd
	config file format.

The web interface could use some work...

Each switch has a 'primary' stack that it belongs to if it's specified
with the '-i' parameter. Otherwise, it can be considered to be a part
of any of the stacks of which it's a member.

The main point of this is so that we can have switches that are on
both the control and experimental networks.

Note: Having a VLAN with the same name on two overlapping stacks is
like crossing the streams: that would be bad. Not "all life as you
know it stopping instantaneously" bad, but snmpit might get confused.

table that will prevent an experiment from being swapped/modified. The
toggle is on the showexp page, and the toggle is *not* admin
over-ridable; you must turn the toggle off (and of course, you must be
an admin to do that).

out of the reserved table. Mostly this happens in nfree and nalloc,
but there a couple of other moves, in libdb and in the reload daemon.
The uid and experiment are stored, long with a timestamp.

out of the reserved table. Mostly this happens in nfree and nalloc,
but there a couple of other moves, in libdb and in the reload daemon.
The uid and experiment are stored, long with a timestamp.

Fix some robot related stuff that I broke with the last checkin and add in
some other tweaks.

	* robots/primotion/garcia-pilot.cc,
	robots/primotion/pilotClient.hh, robots/primotion/pilotClient.cc:
	Broadcast any goto/stop commands to clients observing the robot.

	* robots/rmcd/rmcd.c: Change the behavior to reorient the robot as
	the last step in a goto, so we avoid doing unnecessary pivots.
	Need to send an init packet to the robot so it knows who is
	talking to it.

	* robots/vmcd/vmc-client.c: Oops, supposed to use M_PI_2, not
	M_PI, when translating from camera coords to world.

	* www/telemetry.php3: Make the size of the applet a little bigger.

	* www/garcia-telemetry/GarciaTelemetry.java,
	www/garcia-telemetry/UpdateThread.java,
	www/garcia-telemetry/main.xml: Display a log of goto/stop commands
	sent to the robot.

that is both in the experimental and control nets.

rules (fw-rules), a script to populate the DB from those rules, and a
script to initialize the firewall variables.

This is not part of any standard make, it is used in a one-time fashion
either at install or during the next update.  Still need to write the
instructions for this.

Also, reflect new way of populating default_firewall_rules
(not done here anymore, done in the new firewall subdirectory)

them up!

* New database table to store obstacles, in the usual coord system;
  x1,y1, is the upper left corner.

* New web page to dump the entire obstacle list

	https://www.emulab.net/obstacle_list.php3

* New web page to dump a single obstacle, referenced by the above list
  page, and by the floormap generator.

* Hack up the floormap code to add obstacles to the areamap, so that
  when you mouse over them, you get a ballon showing the description,
  and a link to the above mentioned page.

* Add new DB table "webcams" which hold the id of the webcam, the
  server it is attached to, and the last update time.

* Add new sitevars webcam/anyone_can_view and webcam/admins_can_view.
  Should be obvious what they mean.

* Add trivial script grabwebcams (invoked from cron) to grab the images
  from the servers and stash in /usr/testbed/webcams. The images are
  grabbed with scp, protected by a 5 second timeout. Fine for a couple
  of cameras.

* Add web page stuff to display webcams, linked from the robot mape page.

Permission to view the webcams is currently admin, or in a project that is
allowed to use a robot. We can tighten this up later as needed.

that text will get emailed with the "postpone" menu selection.

The checkpoint driver can return a list of blocks that have been modified
since its startup.  If you use "imagezip -C /dev/shd0 -s 1 /dev/ad0 foo.ndz"
imagezip will make an ioctl call on the shd device to get the modified
blocks it needs to save (rather than parsing the filesystem).  It then
creates an image using those blocks.

The end result should be an "incremental" image that can be put down on
the disk by frisbee after the original image has been loaded.

This is all a theory right now (including the ioctl :-) but should get
tested RSN.

to override from the NS file. In your NS file:

	namespace eval TBCOMPAT {
		set elabinelab_fixnodes("boss") pc171
	        set elabinelab_hardware("boss") pc2000
	        set elabinelab_hardware("ops")  pc2000
	}

environment.

A bunch of engineering on the robot code.  I'm sure I've broken something,
but the majority of it is done and I wanted to get a checkpoint in.

	* GNUmakerules: Add rpcgen rules.

	* Makeconf.in: Add PATH and host_cpu variables so
	cross-compilation works properly.  Add JAVAC and JAR for java
	compilation.  Add BRAINSTEM_DIR that refers to a brainstem build
	directory to be used for the robot build.

	* configure, configure.in: Prepend the arm cross-compile dir to
	PATH.  Detect java for building applets.  Add --with-brainstem to
	specify the brainstem build dir.  Add --enable-mezzanine to turn
	on the mezzanine build.

	* robots/GNUmakefile.in: Add client target that builds the
	subdirs.

	* robots/emc/GNUmakefile.in, robots/emc/emcd.h, robots/emc/emcd.c,
	test_emcd.sh.in, robots/rmcd/GNUmakefile.in, robots/rmcd/rmcd.c,
	robots/rmcd/test_rmcd.sh.in, robots/vmcd/test_vmc-client.sh.in,
	robots/vmcd/test_vmcd.sh.in, robots/vmcd/test_vmcd2.sh,
	robots/vmcd/test_vmcd3.sh, robots/vmcd/test_vmcd4.sh,
	robots/vmcd/vmc-client.c, robots/vmcd/vmcd.c: Updates for the mtp
	switch to using rpcgen.

	* robots/emc/test_emcd.config: Restore missing config line.

	* robots/mtp/GNUmakefile.in, robots/mtp/global_bound.java,
	robots/mtp/mtp.h, robots/mtp/mtp.c, robots/mtp/mtp.java,
	robots/mtp/mtp.x, robots/mtp/mtp_command_goto.java,
	robots/mtp/mtp_command_stop.java, robots/mtp/mtp_config_rmc.java,
	robots/mtp/mtp_config_vmc.java, robots/mtp/mtp_control.java,
	robots/mtp/mtp_dump.c, robots/mtp/mtp_garcia_telemetry.java,
	robots/mtp/mtp_opcode_t.java, robots/mtp/mtp_packet.java,
	robots/mtp/mtp_payload.java, robots/mtp/mtp_recv.c,
	robots/mtp/mtp_request_id.java,
	robots/mtp/mtp_request_position.java,
	robots/mtp/mtp_robot_type_t.java, robots/mtp/mtp_role_t.java,
	robots/mtp/mtp_send.c, robots/mtp/mtp_status_t.java,
	robots/mtp/mtp_telemetry.java, robots/mtp/mtp_update_id.java,
	robots/mtp/mtp_update_position.java, robots/mtp/robot_config.java,
	robots/mtp/robot_position.java, robots/mtp/test_mtp.sh: Replace
	hand-generated stubs with xdr stubs for C and java.  Java stubs
	were generated by "remotetea's" jrpcgen.

	* robots/primotion/GNUmakefile.in,
	robots/primotion/buttonManager.hh,
	robots/primotion/buttonManager.cc, robots/primotion/dashboard.hh,
	robots/primotion/dashboard.cc, robots/primotion/flash-user-led.cc,
	robots/primotion/garcia-pilot.cc, robots/primotion/garciaUtil.hh,
	robots/primotion/garciaUtil.cc, robots/primotion/ledManager.hh,
	robots/primotion/ledManager.cc,
	robots/primotion/pilotButtonCallback.hh,
	robots/primotion/pilotButtonCallback.cc,
	robots/primotion/pilotClient.hh, robots/primotion/pilotClient.cc,
	robots/primotion/watch-user-button.cc,
	robots/primotion/wheelManager.hh,
	robots/primotion/wheelManager.cc: Replace gorobot with
	garcia-pilot, a beefed up daemon for controlling the robots.
	Improvements include: making use of the user LED and button to
	give some feedback and let the wrangler run a test sequence,
	reboot, and shutdown the robot; Logging of the battery level, how
	often the robot has moved and for how long, and the distance
	traveled; telemetry is sent back to emulab clients; movements are
	now just pivot-move instead of pivot-move-pivot, since the second
	pivot ends up being extra work most of the time; the robot will
	move backwards to cut down on the amount of rotation; and just
	generic cleanups to the code.

	* robots/primotion/garcia.config: The configuration file currently
	used on the garcias.

	* www/GNUmakefile.in: Add garcia-telemetry subdir to the build.

	* www/dbdefs.php3.in: Add TBNodeClass and TBNodeStatus functions.

	* www/garcia-telemetry/Base64.java,
	www/garcia-telemetry/GNUmakefile.in,
	www/garcia-telemetry/GarciaTelemetry.java,
	www/garcia-telemetry/UpdateThread.java,
	www/garcia-telemetry/main.xml: A telemetry applet for the garcia,
	it displays readouts for the various sensors and other bits of data
	gathered by the garcia-pilot daemon.  Hopefully, it will make a
	handy debugging tool.

	* www/garcia-telemetry.jar, www/mtp.jar, www/oncrpc.jar,
	www/thinlet.jar: Java jars used by the robot telemetry applet.

	* www/servicepipe.php3: A slightly enhanced version of
	ledpipe.php3 that can be used for other services, like robot
	telemetry.

	* www/shownode.php3: Add "Show Telemetry" menu item to robot
	nodes.

	* www/telemetry.php3: Telemetry page for the garcia-telemetry
	applet.

boss node, which were coming from my home dir. Take them from the source
tree instead in /proj.