Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc.cso.uiuc.edu!garcon!mrcnext.cso.uiuc.edu!carlson
From: carlson@mrcnext.cso.uiuc.edu
Newsgroups: comp.sys.next
Subject: Re: Loading the /etc/services file into
Message-ID: <800009@mrcnext.cso.uiuc.edu>
Date: 24 Jun 89 21:06:00 GMT
References: <3539@cps3xx.UUCP>
Lines: 23
Nf-ID: #R:cps3xx.UUCP:3539:mrcnext.cso.uiuc.edu:800009:000:1000
Nf-From: mrcnext.cso.uiuc.edu!carlson    Jun 24 16:06:00 1989


Obviously, NetInfo can only store one entry for a key ("isis").
Do you really need all 3 entries? Or just keep the tcp one?
You might try to add suffixes to isis, like isis_tcp,
although you will then have to patch the isis code.

This does seem like a real pain, I admit. 
(Though so far we haven't noticed any problems.)
Maybe the /services table should have a sub-table for each protocol,
i.e. /services/tcp & /services/udp.

Now that I think about it, it might be very useful to apply this
idea elsewhere.  Then we could devide /users into groups (we already
segregate their home directories),
and everything under /machines (hosts) could be organized
the same way as the domain-based host naming system.
Of course, this would require re-writing the get* routines (again),
and may or may not increase search times.
Anybody at NeXT care to comment?

--------------------
Brad Carlson  <carlson@mrcnext.cso.uiuc.edu> or <b-carlson@uiuc.edu>
University of Illinos--Micro Resource Center--NeXT guru