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

[Nuno Antunes]

On 4/3/07, Matthew Dillon <dillon at apollo.backplane.com> wrote:
    Also a big piece of this is that I am being very careful to separate
    the issue of finding a good routing path from the issue of actually
    routing the message, and I am creating degenerate cases (e.g. all 0's,
    all 1's) that provide for link layer communications and broadcast
    communications regardless of the state of the mesh's route discovery.
    This means, for example, that link layer communications work right off
    the bat.  If you connect to a syslink node, you can address that node
    (all 0's) regardless of the state of the rest of the mesh, and the
    same goes for broadcasts.  Hence the seed nodes and registration nodes
    can immediately start broadcasting the instant they connect to the
    mesh, forming the basis for creating useful rendezvous within the
    mesh.
Hi.

I'm trying to understand what this message routing is all about. A
cluster can work on a single ethernet segment, right? Can something
like VPLS over MPLS help in this case or am I way off here?
Thanks,
Nuno