copyright

we need to make sure www/ is done before event/, because the latter
tries to install some web documentation.

their ports.

that requires some stuff in rc.local to enable them.

a disk image in case the image isn't stored on the boot CD
(needed to handle heterogenous boot CD media).  netbed-setup.pl
now tries this alternate location if the local disk image
is missing, old, or corrupt.

even if the disk is up to date.

Add a sliceNN_alt_image pointer to a web location for downloading
a disk image in case the image isn't stored on the boot CD
(needed to handle heterogenous boot CD media)

even if the disk is up to date.

place than the old one.

in later revisions. This caused OSPF routing to fail again when Jay
swapped in the 416 topo to test it.

port that has been split into a client and a server.

Update status of most testbeds.
Tweak language of most boxes.
(still needs reordering, make left-hand column consistent)

'-DBATCH' option so that no silly ports will try to ask interactive
questions.

troubleshooting entry.

table to the location_info table.

new_nodes table. Thought it would be easy, but ended up doing more
damage then I expected; oh well. New nodes show up in "gold" color
(not listed in the legend).

I added a link from the newnode_edit page. Rob will need to arrange
for a location_info entry to be created when a new node is made live
(but only if building/floor are not null).

table - this will allow us to place them on the map while they are still
in limbo.

 ALTER TABLE new_nodes ADD COLUMN (floor varchar(32) default NULL,
    building varchar(32) default NULL,
    loc_x int(10) unsigned NOT NULL default '0',
    loc_y int(10) unsigned NOT NULL default '0',
    contact tinytext,
    phone tinytext,
    room varchar(32) default NULL);

number in database-migrate.

that I added to the DB. See revision 1.251 of sql/database-create.sql.
I have removed all of the hardwired names of buildings, images, files,
etc. I have also added MEB floors 1 and 2, but they do not show up on
the status page unlesss there are actually nodes assigned to them.
When you go to set a node location, you do see the little thumbs of
all existing buildings/floors, so you can add nodes to floors that do
not currently have any.

Still needs some work to cleanly display multiple buildings, but thats
for another day.

sql/database-create.sql. The old ips slot of virt_nodes is left in
place while we transition over.

This is rather primitive still; We just need a place to define
buildings and floors in buildings, so that we do not hardwire them
into the code. This can get arbitrarily complicated, but not until we
need it.

	CREATE TABLE buildings (
	  building varchar(32) NOT NULL default '',
	  image_path tinytext,
	  title tinytext NOT NULL,
	  PRIMARY KEY  (building)
	) TYPE=MyISAM;

The image_path is optional for buildings. The title is a string to
print along with the images (Merril Engineering Building).

	CREATE TABLE floorimages (
	  building varchar(32) NOT NULL default '',
	  floor varchar(32) NOT NULL default '',
	  image_path tinytext,
	  thumb_path tinytext,
	  x1 int(6) NOT NULL default '0',
	  y1 int(6) NOT NULL default '0',
	  x2 int(6) NOT NULL default '0',
	  y2 int(6) NOT NULL default '0',
	  PRIMARY KEY  (building, floor)
	) TYPE=MyISAM;

The image_path is not optional; it is either an absolute path or a
filename in $TB/www. The thumb_path is for a tiny view of it. Floor is
something like 1, 2, 3 but could also be basement, lobby, penthouse,
etc. The x,y coordinates are intended to be bounding box coords of the
"interesting" part of the image so that it is easier to scale specific
entries from the location_info table. But, not really sure about this
yet; needs more thought and some investigation about appropriate ways
to store coordinate values like this.