To-do list for vesta/release/12.pre13/7

All done!

Completed

RFE: Support for hard links in /vesta-work
Check in Debian sarge std_envs for supported platforms
- Standardize top-level model names
  - linux_arch_deb_sarge.main.ves (all supported Linux platforms)
  - linux_arch_deb_woody.main.ves (PowerPC and Sparc)
  - linux_arch_rh7.main.ves (i386 and Alpha)
  - linux_arch_fc4.main.ves (probably at some point)
  - linux_arch_suse10.main.ves (possibly at some point)
  - linux_arch.main.ves (will still be present for convenience and will simply import and evaluate the Debian sarge model)
  - all_linux_arch.main.ves (will evaluate all variants for this OS/CPU combination, useful for maintainers)
Add additional smarts in in vesta-setup.sh to prioritize the "native" top-level model name when setting [Evaluator]DefaultMain
Add a dependency on portmap to vesta-server to prevent the slow-mounting problem
Bug: Debian post-install falls over if repository in use
Bug: initscripts incompatible with Debian /lib/lsb/init-functions
Pull all installable package (.rpm/.deb) under a Vesta build to make it easier for others to make new packages
Check in fixes to /vesta/vestasys.org/vesta/extras/kits for minor problems discovered in the packages already built:
- Bogus dependency in RPMs (see Debian bug report)
- Missing dependency on vsrun on .debs
Test re-spun packages
Upload to Sourceforge files section, pub.vestasys.org apt source, and post to vesta-users mailing list

In testing on 10-14, mysterious failure suggests SRPC problem:
- Warning: failed to contact runtool server on host "remus.priv.xorian.net": Internal error (TCP): Error receiving data (Interrupted system call)
  This error can only be generated at one place: TCP_sock.C:1419. There's a loop above which should simply repeat the read system call in exactly the case which this error message indicates: TCP_sock.C:1388. So I'm at a loss to explain how this could ever happen.