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: 19 Mar 2002 00:05:36 +0100 [thread overview]
Message-ID: <shs8z8p5ven.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> <shs1yeha5b4.fsf@charged.uio.no> <20020318223827.GD1740@atrey.karlin.mff.cuni.cz> <15510.28326.558485.955067@charged.uio.no> <20020318225403.GE1740@atrey.karlin.mff.cuni.cz>
>>>>> " " == Pavel Machek <pavel@suse.cz> writes:
> Sorry, this thread was about userland filesystems, and NFS is
> just not usefull there (for read/write case).
Nope. The point made in Alan's mail early on in the thread was that of
platform independence: the latter has nothing to do with userland
implementation or not. In fact, several of the filesystems Al
mentioned had no (known) userland implementation.
Cheers,
Trond
next prev parent reply other threads:[~2002-03-18 23:10 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=shs8z8p5ven.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