Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!winchester!djl
From: djl@mips.COM (Dan Levin)
Newsgroups: comp.sys.mips
Subject: Re: VIS and hesiod.
Summary: Hesiod front end not available
Message-ID: <40405@mips.mips.COM>
Date: 25 Jul 90 22:55:45 GMT
References: <23880@boulder.Colorado.EDU>
Sender: news@mips.COM
Lines: 20

In article <23880@boulder.Colorado.EDU>, hartzell@boulder.colorado.edu (George Hartzell) writes:
> 
> Does anyone know if MIPS has any plans to incorporate/supply/support
> Hesiod in RISC/os?

At the time VIS and RISC/OS 4.50 were frozen, MIT had not released the client
code to build a standard UNIX libc that supports Hesiod.  We evaluated the
possibility of doing that work ourselves, and decided that the resource was
better spent elsewhere.

The server side work is trivial, given BIND source and the Hesiod distribution.

Clearly, the intent of VIS was to allow just such technologies to be integrated
into RISC/OS.  MIPS will continue to consider other distributed naming
schemes for addition into RISC/OS.

-- 
			***dan

{decwrl,pyramid,ames}!mips!djl         djl@mips.com (No, Really! Trust Me.)