TB_IMAGEID_READINFO - I was mistaken about the level of access implied
by TB_IMAGEID_ACCESS.

reloads for nodes in an experiment.
Change os_load to schedule a default image reload whenever a mereuser
loads an image that is not the default image for that node type.
Add some support stuff in libdb (TBSetSchedReload) and some constant
definitions for sched_reload and for nodelog.

	Usage: os_load [-s | -w] [-r] [-i <imageid>] <node> [node ...]
        Usage: sched_reload [-f | -p] [-r] [-i <imageid>] <node> [node ...]

The imageid is now an optional argument. After continually forgetting
what imageid to use, or just plain forgetting the argument, and having
it try to load imageid pc53 on pcXX, I decided this interface was
bogus. With now imageid, select the default imageid for each node
provided. This is actually convenient since you can load multiple
types of nodes in one shot.

1.13, but had somehow gone unnoticed until now.

to contain a list of reloads currently in processes. It is filled by
os_load, and is cleared out by the tmcd 'reset' command or by nfree.
The tmcd 'loadaddr' command now uses this table instead of the reloads table.

Also added Frisbee support to sched_reload, and changed the Frisbee command
line option to os_load to '-r' to avoid a conflict with sched_reload's '-f'
option.

switch to try it out. The main thing missing at this point is a way to tell
frisbee _which_ disk image to load - it will load whichever image there
happens to be a server running for.

Change occurrences of "@TESTMODE@" back to @TESTMODE@ like they were supposed to be in the first place...

Lots of small changes for turning our 'require lib*' lines into 'use lib*' lines. Proper modules declare themselves as a package, and use Exporter to export the names of the subroutines that should be visible from the outside world. Many of ours didn't do that, it was just a file with a bunch of subs in it. So now I've fixed many of them to be proper, and removed the requires and 'push(@INC,...)' hacks and changed it to the proper 'use lib @prefix@/lib/;' and use lib*.

groups (or 2 right now) and then wait for them to finish before moving
to the next group. This is to aid in issuing a mass reload, but not
causing the network to meltdown. Will all change with Frisbee of
course, but this will help Matt Dorsch out.

Added testmode. Won't update the database for netdisking, and won't reboot nodes. Will update partitions table as if the change had already happened.

Will be fixed later with addition of next_boot_osid.

repetition and clutter. Mostly a visual and convenience thing. I plan
to work through other scripts as time permits.

hopefully get bigger and reduce the amount of typing that we all
do. I hacked up sched_reload and os_load to use it. Pretty simple to
start with.

I'm not planning to go much further on this until we sync up with the
dbtoir branch since it will just create needless branch merge errors.

replaced by the "images" table. New os_info table is added. New web
pages to add and delete OSIDs to/from the os_info table, for use in
the NS file. tb-create-os is gone. handle_os no longer operates on the
tbcmds file, and no longer writes anything into the ir file. Moved the
setting up of os state (nodes table) from os_setup to handle_os, where
it should be. os_load and sched_reload now take a single argument, the
name of the imageid from the images table.

mere users. os_load and os_setup reworked to use node_reboot.

(or was it months)?

what names map to what IPs on what networks on what planets.

see something like either wd0 or wd0:s1 or wd0:s1a. This is to keep
the command line parsing simple in the face of allowing multiple loads
at a time on the command line.

the testbed list.

now, but don't actually do anything with the node. Leave that to
user to run the os_load script.