GitLab

into a single new script call modgroups. Usage:

	modgroups [-a pid:gid:trust[,pid:gid:trust]...]
                  [-m pid:gid:trust[,pid:gid:trust]...]
                  [-r pid:gid[,pid:gid]...] user

So, -a to add groups, -r to remove groups, and -m to modify the trust
value for a member of a group.

The reason for doing this is that previously, we had no idea in the
backend what group changes actually happened; we just knew what the
current groups are. This make it hard to add and remove users from
mailing lists, chat server buddy lists, etc. This is cleaner ...

Add rules to allow outbound http,https (for windows)

the multicast IP address. Mike sez it makes the firewall rules easier.

'connected-to-X' features for every other switch/node it's connected
to. This way, you can easily ask for nodes on cisco3, or whatever...

Add tiplines table to inner DB state so we get the nifty console icon.

to the inner DB (so that the console icon is displayed). Make sure
that we do not try to run console_setup inside by checking the server
and keydata fields (which is now cleared for the inner elab).

Major interface change; the default mode in the map is that click
on a node now *adds* to a highlight (used to be shift-click), and that
click over the floor area deselects everything.

Add a "Distances between highlighted node" menu item, that uses the
x,y,z coords of nodes to determine the distance between them. Okay
so there might be a small constant in there, say 14 feet, that just
happens to be the distance between floors in MEB.

Entailed new instructions for manual setup as well as integration into
elabinelab framework.  First, the manual path:

setup.txt, setup-boss.txt, setup-ops.txt and new setup-fs.txt:
    Updated to reflect potential for separate fs node.  The org here
    is a little dicey and could be confusing with ops+fs vs. ops and fs.
    Has not been field tested yet.

*/GNUmakefile.in: new fs-install target.

configure, configure.in, defs-*:
    Somewhat unrelated, make min uid/gid to use be a defs setting.
    Also add config of fs-install.in script.

boss-install.in, ops-install.in and new fs-install.in:
    Handle distinct fs node.  If you have one, fs-install is run before
    ops-install.  All scripts rely on the defs file settings of FSNODE
    and USERNODE to determine if the fs node is seperate.

utils/checkquota.in:
    Just return "ok" if quotas are not used (i.e., if defs file FS_WITH_QUOTA
    string is null.

install/ports/emulab-fs:
    Meta ...

Pass through some args.

shaping in dummynet.

"new" and explain why.  Temporarily make the papers menu item say "new"
(for about two weeks, I think).

Add SMP support caveat.

mcast addr problem, change the pick_address code so that it always
adds one to the last address picked. Store the last used index in the
emulab_indicies table (the table is seeded with the BASEADDR if there
is no existing address, so external emulabs will be okay). With the
lower three octets, it should be quite some time before we run out and
have to start over (currently it sends email if this happens).

guess the default path is different on new boss?

Fix sshd input checking, add RDP kbd/mouse event checking, and correct for nCPUs due to hyperthreading on the pc-3000's.

Also print name of moused over node on the mode line.

boss. Odd, indeed ...