Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!elroy.jpl.nasa.gov!usc!rpi!batcomputer!theory.tn.cornell.edu!shore
From: shore@theory.tn.cornell.edu (Melinda Shore)
Newsgroups: comp.unix.internals
Subject: Re: Shared libraries
Message-ID: <1991May8.173813.27064@batcomputer.tn.cornell.edu>
Date: 8 May 91 17:38:13 GMT
References: <161@titccy.cc.titech.ac.jp> <1991May7.145228.423@batcomputer.tn.cornell.edu> <163@titccy.cc.titech.ac.jp>
Sender: news@batcomputer.tn.cornell.edu
Organization: Cornell Theory Center
Lines: 21
Nntp-Posting-Host: theory.tn.cornell.edu

In article <163@titccy.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes:
>But hosts with muptiple IP addresses become common with the introduction
>of DNS.

Again, it has *absolutely* *nothing* to do with name service.  All that
dns provides is a mechanism for looking up hostname/ip address mappings.
Because of the growth of the internet there has been an increase in the
number of gateways, but I wouldn't say that the ratio of gateways to
leaf nodes has changed much.  At most you've got an entirely spurious
correlation.  

>>In the musty, dusty days before name service I had to fix the routing
>>code in a hyperchannel driver for just this reason.

>"fix the routing code"? Routing code has nothing to do with the problem.

No, but the routing code in this particular driver used ip addresses
as hash keys.  Duh.
-- 
                    Software longa, hardware brevis
Melinda Shore - Cornell Information Technologies - shore@theory.tn.cornell.edu