_display_info prints the status and related information about the virtual disk created.

Fixed the query for server name, ip, and mac so that it works with
multiple subbosses.  Previously the query would fail due to the
subquery returning multiple rows.

Since the default FORWARD policy is to DROP, only send packets to the
INSIDE chain if:

A) they come in on the vlan interface and
B) they have src IPs in the control net (or brodcast IP)

Packets that match the first but not the second will fall through and
be dropped.

to avoid NFS mountd issues during install.

but causes elabinelab reboot to fail (when doing a XEN elabinelab).

reload MFSs to generate an ISUP cause that will screw up the reload by
clearing it. How do we prevent checkGenISUP() from generating an ISUP?
Well, by adding an osfeature to the MFSs that say they generate
ISUP. Sheesh.

virtual nodes. We now create an interfaces table entry so that we do
not special code to find the control network interface. This entry is
delated along with the node entries when the experiment is swapped
out.

Of course, we still have existing nodes with jailip entries, so not
much code was removed, but this saves me from having to add more
special cases for XEN elabinelab, and at some point we can remove the
deprecated code.

running.

control network, so that we can use routable IPs.

Create a swap volume for the guest. This addition is reflected in
rc.frisbee but not the linux version; looks for a disk with a dos
partition labeled as linux swap.

Look in the node attributes for additonal disk specifications and
create those disks (logical volumes). This is currently used in the
XEN elabinelab to add more disks for inner boss and ops, and look
like:

  $myboss add-attribute XEN_EXTRADISKS "disk1:10G,disk2:10G,disk3:10G"
  $myops  add-attribute XEN_EXTRADISKS "disk1:4G,disk2:10G"

It is up to the guest to do something with these, we do not partition
or label the volumes.

at.

character from , to ; (yes, very important change, I know).

directives in the node attributes, and use those to create the
additional file systems. This is not actually XEN specific, but just
where it currently gets used.

possible for Xen to give the guest a disk device to use for swap.
This code could be a lot better!

an assigned routable IP. Checks no longer necessary since we are open
source now.

Made the following changes to the clientside code to support Linux
firewalls:

- Made os_fwconfig_line() actually do something.
- getfwconfig() adds an 'IPS' hash to the fwinfo hash.  This contains
  the IP address for each host, much like how the 'MACS' hash contains
  the MAC address for each host.  This is needed because ebtables (which
  is needed for ARP proxying) doesn't resolve hostnames.

Rules are stored in firewall/iptables-fw-rules.  Syntax is similar to
fw-rules, but without the rule number (since iptables doesn't use rule
numbers).  These should be equivalent to our ipfw-based rules, but I
haven't tested every case yet to confirm this.  I'm sure some changes
will be necessary.