linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Pavel Machek <pavel@suse.cz>
Cc: Alexander Viro <viro@math.psu.edu>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Simon Richter <Simon.Richter@phobos.fachschaften.tu-muenchen.de>,
	Jonathan Barker <jbarker@ebi.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: VFS mediator?
Date: 18 Mar 2002 23:18:07 +0100	[thread overview]
Message-ID: <shs1yeha5b4.fsf@charged.uio.no> (raw)
In-Reply-To: <E16lej0-0002FE-00@the-village.bc.nu> <Pine.GSO.4.21.0203141825070.329-100000@weyl.math.psu.edu> <20020318192502.GD194@elf.ucw.cz>

>>>>> " " == Pavel Machek <pavel@suse.cz> writes:

    >> * NFS (v2,v3): Portable.  And that's the only good thing to say
    >> about it - it's stateless, it has messy semantics all over the
    >> place and implementing userland server requires a lot of glue.

     > Does not work... If you mount nfs server on localhost, you can
     > deadlock.

Huh? Examples please? A hell of a lot of work has gone into ensuring
that this cannot happen. I do most of my NFS client work on this sort
of setup, so it had bloody well better work...

Cheers,
  Trond

  reply	other threads:[~2002-03-18 22:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 14:52 VFS mediator? Jonathan Barker
2002-03-14 23:09 ` Simon Richter
2002-03-14 23:33   ` Alan Cox
2002-03-15  0:00     ` Alexander Viro
2002-03-15 11:50       ` Simon Richter
2002-03-18 19:25       ` Pavel Machek
2002-03-18 22:18         ` Trond Myklebust [this message]
2002-03-18 22:38           ` Pavel Machek
2002-03-18 22:48             ` Trond Myklebust
2002-03-18 22:54               ` Pavel Machek
2002-03-18 23:05                 ` Trond Myklebust
2002-03-19  0:15           ` Alan Cox
2002-03-18 22:29         ` Alexander Viro
2002-03-18 22:36           ` Pavel Machek
2002-03-15 14:28 ` Jonathan Barker
2002-03-19 13:45 Jesse Pollard
2002-03-19 21:24 ` Pavel Machek

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=shs1yeha5b4.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jbarker@ebi.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=viro@math.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).