GitLab

 allow boot from partitions other than 1
 allow "-new" versions of freebsd/frisbee MFS

These get redirected to a file nowadays, so they shouldn't cause problems.

trying to copy it via NFS.

Add code to restart the tmcc proxy, which appears to die off for no
apparent reason. I now waitpid for it while the jail is running, and
restart if it exits.

At Mike's suggestion temporarily wrap tmcc proxy in a ktrace to see if we
can debug this problem. The ktrace file (using -a option) is written as
/var/emulab/jails/nodeid/tmcc.ktrace.

interfaces when configuring veth interfaces. Instead, tmcd now returns
actual configuration information for those interfaces, albeit slightly
modified to make it apparent what their role is. See revision 1.232 of
tmcd/tmcd.c for more information.

See initial revision for tbsetup/gentopfile for more details. Note
that a gzipped version of the file is also created by gentopofile, and
we try to get that first to cut down on the amount of data copied over
(the topomap is highly compressable).

Needs to be backed out later.

the pnode rebooted, the file got multiple entries causing the generated
gated config to have syntax errors.

in the timestamps, and seeing what was taking so much time.

* Increase the overlap from two to four seconds (have vnodesetup exit
  earlier) so that the next jail can start sooner. Using getrusage it
  seemed pretty clear that there were plenty of cycles available to
  start the next jail going a little earlier. Instead of looking for
  the watchdog pid file to appear, I touch (in mkjail) a specific file
  in the jail directory , and have vnodesetup look for that file
  instead of the pid.

* Cut back the number of inodes in the filesystem! Sheesh, we ere
  creating 137,000 inodes for a 50MB vnode filesystem. Takes 1
  second to do that. Reduced to 30,000 and the time when to .1
  seconds. Could probably go even lower.

* Add -p option to fsck when restoring a jail from an existing
  filesystem. No need to force check the filesystem if its clean.

* Instead of running MAKDEV inside each jail filesystem (which was
  also taking .8 seconds to do), do it just once and stash a copy in
  /var/emulab/jails. Each jail does a "hier cp" of that master copy
  into the jail filesystem. Reduced the time to .05 seconds.

So, for the results:

Original time to boot a jail: 8.2 seconds, with the last two seconds
overlapped with the next one.

Original time to reinstate a jail after halting it (filesystem left
behind): 6.5 seconds, with the last 1.5 seconds overlapped with the next
one.

Original time to boot 16 jails on a pc850: 2 minutes and 12 seconds.

---------------------------------------------------------------------------

New time to boot a jail: 6.2 seconds, with the last 4 seconds overlapped
with the next one.

New time to reinstate a jail after halting it: 6 seconds, with the last 4
seconds overlapped with the next onw.

New time to boot 16 jails on a pc850: 88 seconds. Does this number ring any
bells? :-)

1. tbbootconfig: ensure block is zeroed on first init, fix cut/paste error
2. rc.frisbee: cleanup interface to slicefix
3. slicefix: cleanup, make it work correctly, init tbboot block for cd boot

Unrelated:
1. link-agent makefile: build link-agent when doing client-install

partition by bootinfo, there actually is such a partition. This avoids
one instance Mike ran into in which the node got into a reboot loop
cause bootinfo said something that was not possible. So, run fdisk and
make sure the MBR has such a slice defined. If not, stay on the CD.

add more potential root device unit numbers (4-7)

booting the rest of the MFS (just go multiuser without doing any
testbed setup).

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).

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.

around from the last boot, and we have more than one CPU: line.
Sometimes (such as at Wisc.), the first instance contains garbage. So,
instead of exiting after the first CPU: line, use a different method
of handling unknown CPU speeds, modeled after chipset.awk .

1. "make clean" will just remove stuff built in the process of a regular build
2. "make distclean" will also clean out configure generated files.

This is how it was always supposed to be, there was just some bitrot.

of their file server (aero)

Extend DISABLE_NAMED_SETUP: when set, we don't set a nodes hostname to
<name>.<eid>.<pid>.<domain> since that won't resolve.  Just stick with
pc<XXX>.<domain> in those cases.  The various sethostname* scripts are
now .in so that they get preprocessed to check for the option.

It didn't fix the problem and it makes nodes fail on startup sometimes.

filesystems.  Also add sysctl call to increase socketbuf size for NFS
sockets.

the top level.  This will build all the necessary binaries and then install
them.  This works on FBSD4 and RHL7.3.  It still doesn't work on FBSD5
(newer compiler that no longer supports a style of use of _FUNCTION_ in the
event lib) or RHL9 (event lib needs SSL lib which has a bad dependency
on Kerberos).  Notes:

- requires that elvin libraries be installed on nodes (they are) to build
  event agents, requires linuxthreads be installed on FBSD (it is now) to
  build imagezip (which is installed, but is not strictly necessary)

- installed event-agents and other binaries are stripped

- added a few missing files to the source tree for bsd (healthd.conf)
  and linux (healthd.conf, rc.local)

- the only thing that doesn't get rebuilt in /usr/local/etc/emulab is
  healthd, I couldn't quickly find how it gets built

- uses a scaled down version of libtb with no DB functions (since mysql
  isn't installed on nodes).  N.B. DO NOT DO A CLIENT INSTALL FROM YOUR
  REGULAR OBJ TREE OR ELSE YOU MAY WIND UP WITH A NEUTERED VERSION OF
  libtb.a!

The build-as-well-as-install semantics are counter to the regular install
targets, but this is what we gotta do for now.  Once the TB source builds
under Linux and newer BSDs, we could undo this and just require that people
do a regular "make" followed by "make client-install"  OTOH, there should
be no reason to require installation of mysql and other server-side packages
just to build clients (or make them sit through the compilation of assign),
so maybe we will keep the client build special.

no freebsd support.

The primary change is that tmcd now sends down a list of setting to
apply to each interface, and that list is turned into a hash table,
and provided to rc.config, which passes them along to the machine
dependent routine in liblocsetup.

Then in the linux version of liblocsetup there is a bunch of new code
to configure wireless links using iwconfig and iwpriv, using the
settings array.

All of this is bound to change once we get more experience with it.