From: philw@plan9.att.com philw@plan9.att.com
Subject: Permissions on names served by the kernel
Date: Wed, 27 Dec 1995 12:24:44 -0500 [thread overview]
Message-ID: <19951227172444.SAld1mfarxU8FtxIz0P9xKgdtzDNEdm74LDOQ8R7ZKw@z> (raw)
devsrv and #s is what I pointed to. It is a means of
publishing services between namespaces. #s can pass
a channel to either a pipe or file system by posting
a name in a global place. The code to post a channel
is in srv.c but I meant look at the device driver.
8½ and other file servers make themselves available
using this mechanism. Files posted in srv can also
be opened and acessed remotely via srv. From a cpu
connection look at /mnt/term/srv. If you look at
/rc/bin/window you can see it work.
phil
next reply other threads:[~1995-12-27 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-27 17:24 philw [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-12-27 17:29 G.David
1995-12-27 5:04 G.David
1995-12-20 19:41 philw
1995-12-20 19:06 G.David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19951227172444.SAld1mfarxU8FtxIz0P9xKgdtzDNEdm74LDOQ8R7ZKw@z \
--to=philw@plan9.att.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).