Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!kddlab!cs.titech!titccy.cc.titech!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.unix.internals
Subject: Re: Shared libraries
Message-ID: <183@titccy.cc.titech.ac.jp>
Date: 13 May 91 08:04:12 GMT
References: <163@titccy.cc.titech.ac.jp> <1991May8.173813.27064@batcomputer.tn.cornell.edu> <166@titccy.cc.titech.ac.jp> <1991May12.011253.35@kithrup.COM>
Sender: news@titccy.cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 36

In article <1991May12.011253.35@kithrup.COM>
	sef@kithrup.COM (Sean Eric Fagan) writes:

>>And shared libraries dose *NOT* help the transition from /etc/hosts to DNS.

>Uhm, yes, it does.  For the original transition, no, you're right, it
>doesn't help, as you have to change the code in the application.

So, my claim is confirmed.

>But afterwards, when the applications will deal with multiple addresses,
>then consider this:  if you're not going to run a nameserver, just get
>addresses out of /etc/hosts, then you don't *need* the nameserver code in
>your application(s), do you?

My claim (and the current subject) is

>>And shared libraries dose *NOT* help the transition from /etc/hosts to DNS.
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are talking about the reverse transition.

And still,

>The alternative is to have both in every program that tries to use
>networking, and this is a waste of both system memory and disk space.

I showed in my old posting with measurement that the consumed area
is negligibly small. So, it should be noted that the measured system
(SONY NEWSOS 4.0R) supports both /etc/hosts, DNS and NIS.

>But I guess, as usual, you don't care about that.

Based on the measurement, I don't care.

						Masataka Ohta