From: serge@euler.Berkeley.EDU serge@euler.Berkeley.EDU
Subject: Plan 9 devices
Date: Wed, 26 Apr 1995 16:13:40 -0400 [thread overview]
Message-ID: <19950426201340.0pomXbY6CK8i_rlqU000RdsYV2RQXuWbsiqnZG8h8dc@z> (raw)
>I was just wondering if it's possible to replace '#name' with,
>e.g. /dri(ver[s])/name (/wet/name? :-)
Some of the other possibilities would be /# (a bit of backwards
compatibility) or /local (for 'local' devices/drivers). The (additional)
advantages would be one less hack ... er, excuse me syntactic
escape/special case, more uniformity, etc. :-) You could even
conceivably bind /cpu/dri/xxx to /dev/xxx to access cpu server's drivers?
next reply other threads:[~1995-04-26 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-26 20:13 serge [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-26 0:52 serge
1995-04-20 8:59 Hans-Peter
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=19950426201340.0pomXbY6CK8i_rlqU000RdsYV2RQXuWbsiqnZG8h8dc@z \
--to=serge@euler.berkeley.edu \
/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).