Lines Matching refs:that

10 as the only devices that register themselves are the floppy,
15 There is a tree of nodes that describe the layout of the DEVFS as seen by
17 for reasons that will become obvious in a second. Think of it as a
19 a "devnode" struct, that holds information about the device
21 with that node. The back node itself can be considered to be 
23 and a link to the directory that holds it. It is sometimes refered
27 multiple places), a front layer is created that contains a tree of 'front'
35 The back plane has a mount structure and all that stuff, but it is in
43 the nodes can be moved around within that plane (or deleted).
48 Front nodes that refer to devices, use the same "devnode" struct that is used 
49 by their associated backing node, so that multiple front nodes that
51 that, the same vnode, ops, modification times, flags, owner and group.
61 Information that is to be shared between these mounts is stored
62 in the 'backing' node for that object.  Once you have erased 'front'
65 for the node with the correct major/minor/type, I don't see that
67 (I hope) devices that go direct from the backing node to the driver
86 of that directory and do not refer to their original backing node
93 code follows the links to all the front nodes linked to that backing
98 into its own back node, the new front node will appear in that front
99 directory, even though it's been moved, because the directory that
103 plane that controls to the mount being updated.. that would have the
104 effect of 're-propogating' through any backing nodes that find they
105 have no front nodes in that plane.