cvs commit: src/lib/libc/sys syslink.2

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxxxxx>]

dillon      2007/04/02 20:09:28 PDT

DragonFly src repository

  Modified files:
    lib/libc/sys         syslink.2 
  Log:
  Update the syslink documentation.  This is still a work in progress.  The
  main change is that I got stuck in a hole and diverged from my original
  concept of having a self-identifying network.  These changes reformulate
  the algorithms such that we are back to the self-identifying network concept.
  That is, the idea that you can just connect into a cluster at any point and
  everything will be worked out automatically.
  
  One big issue still needs to be resolved, and that is how to figure out
  an optimal physical route from point A to point C without having to go
  through point B, where point B is the registration node used as a rendezvous
  for A and C.  It is always possible for A to issue a cluster-wide broadcast
  to 'forge' a route to C, or vise-versa, and we will probably implement things
  this way initially (and always have it available for emergencies), but it
  would not scale as the cluster grows despite the fairly rough granularity
  in the resources being advertised (e.g. filesystems rather then files).
  
  Revision  Changes    Path
  1.4       +175 -160  src/lib/libc/sys/syslink.2


http://www.dragonflybsd.org/cvsweb/src/lib/libc/sys/syslink.2.diff?r1=1.3&r2=1.4&f=u