NFS virtual hosts /import/<host> -> <host>:/export/<host>
  debian.ethz.ch only as pure debian.org mirror, not for operation
  woody-phys.ethz.ch (and woody.phys.ethz.ch) for woody operation
    all /adm, /adm/etc /misc1 /pub are links to /import/woody-phys/*
  later sarge-phys (sarge.phys) for next upgrade round

install boot disk and RAM-disk with miniroot, ev 1 1.9M floppy
  per boot script ask IP or enter host, then NFS woody.phys mount
    rest of install, with NFS life sys and config
      + HTTP debian packages + HTTP own packages
    or FAI could give base for this, until macjine running
  as up to now enable hgost on servers, host then triggers its install
  classes for install selection as pseudo-packages, a la tasksel
    dphys-base, dphys-job-<job>, dphys-host-<host>_datum+tag
      should be split into <arch> and all, for div architektures
  host specific config as package dphys-host-<host>
    so should allow also servers without problems
    fileserver is WS with lots of disk, homes poniting there, backup, no logins
      partitioning and filesystems and mountpoints from install server
    other server are WS with speciel daemons, no logins
      all with host-specific package that installs all and configs
  create our packages with standard dpkg tools, files and scripts

managing as up to now dont send, but let hosts fetch
  every host does apt-get upgrade of its dphys-host-<host> package
    for that directories with full package-gen system, edit, pack, host fetch
    as only action when new-package, fetch frequency minutea, or by ssh "shove"
  NIS only for netgroup, or better not at all, instead expanded exports
    dito all other machine management from local files, in package
  LDAP only for user/password management, his reghts in completed system
    and NFS then his home
  generel: hosts statical by package, user dynamical by LDAP/NFS