sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: mike@mystix.cs.uoregon.edu
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: 9fans?
Date: Sat, 27 Mar 1993 19:53:27 -0500	[thread overview]
Message-ID: <9303280053.AA01929@mystix.cs.uoregon.edu> (raw)

I'd be interested in such a mailing list.

I at least have had some, er, "exciting" times setting up Plan 9.
The CS department cannot afford to dedicate a machine as a full time
Plan 9 file server.  Thus I've been running the terminal kernels off
the Unix based file server u9fs.  The version of u9fs that was distributed
has lots of deficiencies (it doesn't even fully implement Plan 9 file
system semantics), which I've been gradually correcting.  In the long
run I'm either going to have to write a completely new file server, or
talk the department into dedicating a couple of machines to run the
Plan 9 file server and CPU server kernels.  Right now I can use Plan 9
quite comfortably, but non-experts would quickly get hopelessly stuck.

I would be very interested in hearing about other peoples' experiences.

Rob, if you're reading this, two simple improvements to u9fs that
you can easily make are:
1) set the Qid version from the file's mtime
   this makes executable caching do the right thing when
   you recompile something
2) honor the ORCLOSE open flag
   then temp files created by, e.g., sam, go away properly.


             reply	other threads:[~1993-03-28  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-03-28  0:53 mike [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-03-27 22:12 9fans? Scott Schwartz

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=9303280053.AA01929@mystix.cs.uoregon.edu \
    --to=mike@mystix.cs.uoregon.edu \
    --cc=sam-fans@hawkwind.utcs.toronto.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).