> In OO you are _always_ composing stuff from at least two sets of data > and functions: the data and functions of parent, and the data and > functions of the new child you are creating. In Plan 9, the standard / > net might represent the parent, and /my/net that you bind on top of it > represents the new data and new functions you create, in purpose of > modifying the parent.
i think you're missing some important bits, and i think you misunderstand the culture. you might want to read ip(3) for information on how /net is really structured. even supposing that each process had it's own network stack (which they do not), it's doubtful that /my/net would be the choice. namespace(6) describes how /lib/namespace is interpreted to build an initial namespace. - erik
