From: Martin C.Atkins <martin@parvat.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Novice question - run as other
Date: Thu, 18 Mar 2004 09:51:16 +0530 [thread overview]
Message-ID: <20040318095116.673c3fcc.martin@parvat.com> (raw)
In-Reply-To: <200403171800.i2HI0jtq086906@adat.davidashen.net>
On Wed, 17 Mar 2004 22:00:45 +0400 (AMT) David Tolpin <dvd@davidashen.net> wrote:
> A more general conclusion is that for tasks where writing to
> or reading from files reflects or affects process space, and not
> name space, rc is not suitable and C code must be written.
Is it the process that writes to the device that gets altered,
or the process that opens the device?
I suspect the former, but why is it not the second? If it was the second,
then rc could probably be used, but what else wouldn't work, or would break?
Was the choice one of expediency, or is there a real semantic advantage
to the first choice?
Martin
--
Martin C. Atkins martin@parvat.com
Parvat Infotech Private Limited http://www.parvat.com{/,/martin}
next prev parent reply other threads:[~2004-03-18 4:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 12:43 David Presotto
2004-03-17 17:03 ` ron minnich
2004-03-17 17:13 ` rog
2004-03-17 17:13 ` David Presotto
2004-03-17 18:00 ` David Tolpin
2004-03-17 18:12 ` ron minnich
2004-03-17 18:14 ` David Presotto
2004-03-17 19:34 ` rog
2004-03-17 19:43 ` [9fans] unsuscribe Jose timofonic
2004-03-17 19:52 ` [9fans] Novice question - run as other Russ Cox
2004-03-17 19:58 ` rog
2004-03-18 4:21 ` Martin C.Atkins [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 18:29 plan9fans
[not found] <200403170948.i2H9mi3W084127@adat.davidashen.net>
2004-03-17 18:24 ` 9nut
2004-03-18 7:38 ` boyd, rounin
[not found] <200403161953.i2GJrNMv080779@adat.davidashen.net>
2004-03-16 22:54 ` 9nut
2004-03-17 7:18 ` David Tolpin
2004-03-17 8:10 ` Geoff Collyer
2004-03-17 8:24 ` David Tolpin
2004-03-17 8:55 ` Geoff Collyer
2004-03-17 9:04 ` David Tolpin
2004-03-17 9:19 ` Bruce Ellis
2004-03-17 10:31 ` boyd, rounin
2004-03-17 14:01 ` Dave Lukes
2004-03-17 9:33 ` 9nut
2004-03-17 8:54 ` David Tolpin
2004-03-17 8:56 ` Charles Forsyth
2004-03-17 9:07 ` David Tolpin
2004-03-17 9:17 ` Charles Forsyth
2004-03-17 9:28 ` David Tolpin
2004-03-17 10:08 ` 9nut
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=20040318095116.673c3fcc.martin@parvat.com \
--to=martin@parvat.com \
--cc=9fans@cse.psu.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).