On Mon, 2006-10-23 at 23:44 +0800, Peter Memishian wrote: > > * The terminology "data link" is more precise than "link", as "link" is a > > term that is used in many contexts (file systems, locking, compilation, > > kernel modules, etc.). The term "link" is used quite a bit throughout > the > > document, and it might help to specify "data link" in many cases in order > > to train people's brains to think in those terms and to remove any > > potential confusion. > > The short-hand "link" runs deeper than just the docs, though -- e.g., > dladm show-link, or even the name of the IEEE802.3ad standard. Further, > the other contexts seem pretty different, so I'm not convinced there's a > problem with just using "link" most of the time.
That's true. My point was not to get all instances of "link" replaced with "data link", but to use the "data link" terminology in a few more places where it's warranted (like in the title of the document perhaps, or in the introduction section). > Regarding your examples, what does "link" mean in terms of locking, and > how is the "compilation" case different than the "kernel modules" case? I don't remember what I was thinking wrt locking. :-( For compilation, I was thinking about the function of the link editor and dynamic linker, and for kernel modules, I was thinking of the data structures we refer to as module linkage structures. There's not really any reason to confuse these with a data link in the context of a networking admin. guide, so point taken. :-) -Seb _______________________________________________ networking-discuss mailing list [email protected]
