that screws it up!

fixup /etc/fstab and anything else that might have hardwired DOS partition
information.  This is the piece of the puzzle needed for loading an image
into a partition other than the one in which it was created.  I never
installed it since there was no demand and it is one more piece on the disk
loading path that could break.

Just checking this in for the day when we might want it.  Note that it is
still not installed (i.e., I didn't change the Makefile to install it).

refill it from the server.

into a testbed boot CD in a mostly automated manner. There are still a
few things that need to be done by hand, which are described in the
cdboot/README file.

Add tmcd/freebsd/cdboot directory of little scripts and files that
need to onto the fixit disk.

The install target is cdboot-install (must be run as root) and if you
are brave enough to run it, you better give it a DESTDIR argument or
you will write a bunch of files onto the local node that will cause
mayhem and havoc at the next reboot.

the CDROM to read/write the magic config sector.

my windoze box cause my CD didn't work for some reason, but now it
does.

/usr/local/etc/emulab instead of /etc/testbed. Handle both cases.

on the new boot CDROM.

speaking the bootinfo protocol just like the pxeboot kernel does. This
is used when booting the CD-ROM to figure out what to do next (boot
partition, or continue booting into one of newnode, frisbee, freebsd
on the CDROM).

boss name in.

night, and process it into a file to stick into the testbed www
directory. This replaces the current approach of wishfully thinking
that people will remember to add their commit log messages to another
file and them install it. I'm one of the worst offenders these days ...

So, take the commit log, skip up to the first entry in 2004/01, then
take the rest of the file and reverse the entries. Copy the resulting
file over to the www directory.

This script is run from cron on our site only!

Note to Opera users; opera does not respect <XMP> properly, and so the
page is somewhat scrogged by HTML entities that are supposed to be
ignored when inside an XMP. Works okay on other browsers.

estimated bandwidth that will be used on the link/LAN. This can then
be passed to assign, to do less conservative bandwidth allocation.

onto the web download page for people to use on their own machine.

to convert this to plain html, but I wanted to make sure that BOSSNODE
was expanded! We need some mechanism for dynamic content contained
within .html files. Hmm, maybe use shtml for stuff like this?

addresses of the interfaces used so that its easier to set the
accesspoint using link_config and tevc. It would be nice if we did the
mapping for the user (from lan0-node1 to MAC) but that would require
changes to the scheduler to look inside events, and I do not want to
got there yet.

agent was created for each link,link-vnode in a link/lan only when
that link has a delay/linkdelay. Well, with the link-agent that will
be used on wireless lans, lets just stick those agents into the table
for all links/lans in the experiment; its harmless. Might revisit this
at some point.

something we are continually being asked to do! This script will only
operate in UNAPPROVED users; once a user is approved it becomes too
difficult to deal with cause of existing directories which might be
exported to active experiments. We can probably deal with this, but we
rarely do this to an approved user, so its not a big deal.

Obvious: This script can get out of sync with the DB, but of course.

with parsing assign's output.

the conglomerate link object, not the real link, for the reversed
flag.

makes link conglomerates.

we might be combining links that go in different directions. Keep
track of which direction a link points, and reverse the interfaces
when we print it out, if it's going the opposit direction than the
other links in the conglomerate.

see (or remember) any reason for this slot to be 20 chars, when the
name of every other vname slot is 32. I looked in the event scheduler
and there do not appear to be any problems there with bumping it. Note
that I choose 64 cause we tend to construct agent names that might be
longer then 32 since they are based on real vnames (lan0, node0, etc).

data.  Add hostkeys() to the node module so we can get the SSH host
keys from nodes.

new directive for your NS file: tb-use-physnaming(1) which means that
if you have a line like this:

	set pc6 [$ns node]

and pc6 is an actual name of a physical node, then do an implicit
"fixnode" to pc6. In other words, pc6 is the name of the node in your
NS file (virtual topo) *and* will be fixed to the real pc6. Needless
to say, if pc6 is allocated when you go to swapin, you lose.

Add a new function, factor_out_fixednodes, that takes a set of nodes
and a reference to another coarsening function. Seperately coarsens
the fixed nodes and passes the non-fixed nodes to the other coarsener.

Intended for debugging, and to use used with assign's pre-check
feature to catch experiments that will never be mappable.