From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] some shell scripts
Date: Thu, 14 Oct 2004 20:28:51 -0400 [thread overview]
Message-ID: <ee9e417a04101417281dbec140@mail.gmail.com> (raw)
In-Reply-To: <51866f86da16fb592ccf52a3223ef4de@collyer.net>
> I don't think the need kernel mods for this.
I think it makes a lot more sense to do it on the file server though.
Have some sort of changes file that you can block reading.
Any local solution fails to account for changes by others.
Russ
next prev parent reply other threads:[~2004-10-15 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:38 Russ Cox
2004-10-14 5:29 ` Martin C.Atkins
2004-10-14 6:50 ` geoff
2004-10-14 9:56 ` Martin C.Atkins
2004-10-14 15:29 ` Nigel Roles
2004-10-15 0:25 ` geoff
2004-10-15 0:28 ` Russ Cox [this message]
2004-10-15 0:38 ` geoff
2004-10-14 9:22 ` Fco. J. Ballesteros
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=ee9e417a04101417281dbec140@mail.gmail.com \
--to=russcox@gmail.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).