9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Greg Watson <gwatson@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] v9fs release
Date: Thu, 28 Nov 2002 12:39:07 -0700	[thread overview]
Message-ID: <p05111706ba0c1f4fa670@[10.0.0.2]> (raw)
In-Reply-To: <Pine.GSO.4.21.0211281305290.25057-100000@steklov.math.psu.edu>

Please don't bother. We are not proposing to merge this with any code
base, nor are we looking for a review of the design or code. This is
simply a work-in-progress that we wish to make available to those who
are interested. Constructive feedback is always appreciated.

It is entirely likely that this will morph into something that is of
no interest to the 9p folks, since we are primarily concerned with
developing for our local environment. Expect to see all sorts of
add-ons in the source tree.

Greg

>On Thu, 28 Nov 2002, Greg Watson wrote:
>
>>  ...and we are planning to mount users home directories, etc. using
>>  v9fs. There's an automounter that mounts the filesystems in a private
>>  namespace each time a process is executed on a node. When the process
>>  terminates the filesystems are auto unmounted.
>
>Umm...  Why the devil was that stuff mixed with 9P support, again?  Do one
>thing and do it well and all such...
>
>Frankly, after the look through the source...  Folks, it's unmergable.
>There are 4 or 5 unrelated patches trying to get out of that beast and
>as it is the combination will be vetoed.
>
>And please, please, use the sane coding style.  Either one described in
>Documentation/CodingStyle or the style common in Plan 9 kernel - they
>are close enough.
>
>I can post detailed review either on fsdevel or here tomorrow (probably
>the former - code and design review of that stuff doesn't look on-topic for
>9fans).  And no, it won't be pleasant - aside of very sloppy programming in
>a lot of places, there are outright races aplenty.
>
>/me sadly shakes head and ponders adding "Required reading: K&P" into the
>place where required versions of cc/binutils/etc. are described...



  reply	other threads:[~2002-11-28 19:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28  6:58 Russ Cox
2002-11-28 16:50 ` Ronald G. Minnich
2002-11-28 18:02   ` Greg Watson
2002-11-28 18:19     ` Alexander Viro
2002-11-28 19:39       ` Greg Watson [this message]
2002-11-29  1:00       ` Ronald G. Minnich
2002-11-29  2:31         ` Jim Choate
2002-11-29 13:37           ` matt
2002-11-29 14:08         ` Alexander Viro
2002-11-29 17:07           ` Ronald G. Minnich
  -- strict thread matches above, loose matches on Subject: below --
2002-11-28  3:17 okamoto
2002-11-28  6:50 ` Ronald G. Minnich
2002-11-27 22:44 Geoff Collyer
2002-11-27 21:34 Keith Nash
2002-11-27 22:28 ` Ronald G. Minnich

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='p05111706ba0c1f4fa670@[10.0.0.2]' \
    --to=gwatson@lanl.gov \
    --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).