Why not YP, er, NIS
July 27, 2011
A commentator on the last entry asked:
The answer for NIS is relatively easy. Shorn of various bits and pieces, NIS is just a file distribution mechanism. Well we have one of those, and ours is simpler, far more flexible, more powerful, and much more transparent and thus easier to understand and reason about. There is nothing particularly unique about our mechanism; these days there are a great many ways to distribute files around (and then do things on the remote end).
(Many of these ways are better than what we have.)
The only advantage NIS has in a modern environment is that things can update slightly faster. In exchange you have to live with a pile of complexity, fragility, and opaqueness. This tradeoff is almost never worth it.
NIS itself is a creation of an era when almost none of this was true.
Back in those days there were no good tools for file replication,
networks were drastically slower, central servers were so wimpy
that distributing files to a bunch of clients at once would do bad
things, and things like
(I assume that NIS lives on because it is the canned solution for file 'replication' for various important system files.)
Written on 27 July 2011.
* * *