Replacing NIS [was:NIS - "Could not read ypservers map" during "make"]

[pll at lanminds.com]

>>>>> On Wed, 18 Jun 2003, "mark" == Mark Komarinski wrote:

  mark> All you've done is reimplement NIS - poorly.

Well, that was basically the gist of the conversation, how to 
implementt NIS without the flaws of NIS.  I don't think I did it 
poorly, and I readily admitted that there were some inherent flaws in 
that would need to be worked out.

   mark> Already implemented in yppasswd

Yes, but yppasswd isn't much good if you're not running NIS, and 
there have already been several reasons mentioned why you wouldn't 
want to run NIS.

  mark> Sounds like a lot of logic behind it.

There is, but you can't tell me there isn't a lot of logic behind NIS.
Sure, I'm re-implementing NIS, however, consider for a moment that 
I'm doing so in the UNIX tradition of taking already existing tools, 
each of which do one thing and do it really well, then combining 
them into something far greater than each one.  

Had the web, ssh, rsync, and rdist been around in 1983 when NIS was 
released to the wild, I honestly believe they would have done things 
a lot better and a lot more elegantly this NIS is now.


-- 

Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!