It makes no sense, since it doesn't declare any avars, but is
obviously capable of having physical sharing.  This would only make
sense if we didn't *also* declare ascopes in individual system calls.

Renaming this "pte" more closely represents what's being shared.
Also, previously we were inconsistent about including the vmap or not;
now we use the same format everywhere.

E.g. make RUN="avar on; ls; avar off; halt"

QEMU copies the command line into the bss, which makes saving it a
slightly annoying process.

The only locking is "point-to-point" between condvar sleep in one proc
and condvar wakeup in another.

half-broken implementation of syscall/sysret; exec seems to work
fine with syscall/sysret now.

A change in any kernel source may change the syscall definitions, so
those need to be regenerated, but previously this would cause
everything else to be likewise regenerated.  Avoid this by only
updating the generated file if its contents actually change.

This also makes these rules better behaved when there are errors,
since previously they would leave partially-generated files that would
confuse the next make run.

These are no longer necessary because of how we generate the syscall
vector array and removing them discourages calling syscall entry
points from inside the kernel.

Avoid calling sys_halt from inside the kernel.

Now the only thing you need to do to create a new syscall is write the
kernel function and put "//SYSCALL" immediately before it.

There are only two places we depended on these #defines: forkt and
initcode.  We now declare symbolic constants for the syscall numbers
in sysstubs, which makes forkt just work (though it gets filled in at
link time instead of by the preprocessor).  For initcode, we now link
initcode against sysstubs so it can get these constants.