Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: notesnews 0.1 (unido 12/05/84); site unido.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!unido!dfk From: dfk@unido.UUCP Newsgroups: net.unix-wizards Subject: Re: Extending the UNIX pathname syntax Message-ID: Date: Fri, 26-Apr-85 16:00:00 EDT Article-I.D.: unido.nf17100003 Posted: Fri Apr 26 16:00:00 1985 Date-Received: Sun, 28-Apr-85 07:06:12 EDT References: <10102@brl-tgr.UUCP> Sender: notes@unido.UUCP Lines: 28 Nf-ID: #R:brl-tgr:-1010200:unido:17100003:000:1029 Nf-From: unido!dfk Apr 26 19:00:00 1985 >/***** unido:net.unix-wizar / boring!jack / 7:19 pm Apr 24, 1985*/ > >Something like /dev/net/blablabla is something that I've wanted >to implement for a long long time now, only I haven't found >the time yet. Well it sure sounds nice. >Has anyone implemented something like this already? Anyone feels >like doing so? Any comments? If I remember it correctly, a similar idea was in the original proposal for networking from UCB. It was a special socket called a "portal". A process listening to such a socket would be passed the "blablabla" part of the pathname. I am not sure wether the automatic creation of the server was in the proposal too. It sounds like a very clean (UNIX like) way to assign names to many things we currently name in rather crude ways. Since nothing of the sort is in 4.2 this seems not to be that trivial to implement and I don't get the impression that people at Berkeley are still thinking about it. Does anybody have an idea why this is so ? -Daniel Karrenberg