Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.internals
Subject: Re: Shared libraries
Message-ID: <1991May12.011253.35@kithrup.COM>
Date: 12 May 91 01:12:53 GMT
References: <163@titccy.cc.titech.ac.jp> <1991May8.173813.27064@batcomputer.tn.cornell.edu> <166@titccy.cc.titech.ac.jp>
Organization: Kithrup Enterprises, Ltd.
Lines: 25

In article <166@titccy.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) 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.

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?  It does increase the size, in case you weren't
aware of it.

If you have shared libraries, you can then just install the "DNS" version of
the network libraries, and *poof*, you can then get elsewhere.

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.

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

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.