Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ucbvax.UUCP
Path: utzoo!linus!security!genrad!grkermit!masscomp!clyde!floyd!vax135!cornell!uw-beaver!tektronix!ucbcad!ucbvax!sam
From: sam@ucbvax.UUCP
Newsgroups: net.unix-wizards
Subject: Re: UNIX domain addressing for 4.2bsd IPC
Message-ID: <2@ucbvax.UUCP>
Date: Tue, 13-Dec-83 18:51:45 EST
Article-I.D.: ucbvax.2
Posted: Tue Dec 13 18:51:45 1983
Date-Received: Fri, 16-Dec-83 01:51:59 EST
References: <14477@sri-arpa.UUCP>
Organization: U.C. Berkeley
Lines: 13

I sure would like to see the "4 lines of code" which would fix the UNIX
domain addressing problems.  To be simple, naming in the UNIX domain
needs an extensive overhaul.  Because the sockets are tied to inodes
one can't simply record bound names and expect them to remain constant
across the lifetime of a socket (remember the socket could be be moved
elsewhere in the file system while it's in use).  Also, since socket
names are pathnames, each send requires a call to namei resulting in
abominable performance.  There's an obvious need to be able to "bind"
(not bind(2)) UNIX domain sockets to files in the UNIX file system, but
the way it's done now was as much for expediency as anything else.

P.S. You could probably fix the wandering name problem which
currently exists by putting pwd in the kernel...just kidding Rob.