public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Xymoron <oxymoron@waste.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Dax Kelson <dax@gurulabs.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Will NFSv4 be accepted?
Date: Fri, 16 Aug 2002 09:54:34 -0500	[thread overview]
Message-ID: <20020816145434.GD5418@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0208151027510.3130-100000@home.transmeta.com>

On Thu, Aug 15, 2002 at 10:35:40AM -0700, Linus Torvalds wrote:
> 
> I personally doubt that NFS would be the thing driving this. Judging by 
> past performance, NFS security issues don't seem to bother people. I'd 
> personally assume that the thing that would be important enough to people 
> for vendors to add it is VPN or encrypted (local) disks.

I would have thought that there'd be a big push for merging IPSEC in as it
creates one of those "network effects" but it's still stalled by
politics. I think they're waiting for a written invitation or something.

Is loopback solid enough currently to make crypto over loopback
worthwhile? It's occurred to me that it might be better to move the
translation hooks down to the generic block layer proper so that
things like LVM and iSCSI and brain-damaged bit-swapped IDE could take
advantage of them without the deadlock-prone layering issues of
loopback. Thoughts?

-- 
 "Love the dolphins," she advised him. "Write by W.A.S.T.E.." 

  parent reply	other threads:[~2002-08-16 14:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-13 23:01 patch 14/38: CLIENT: add ->setup_read() nfs_rpc_op for async read, part 1 Kendrick M. Smith
2002-08-14 20:49 ` Will NFSv4 be accepted? Dax Kelson
2002-08-14 22:17   ` Trond Myklebust
2002-08-14 22:34     ` [NFS] " Brian Pawlowski
2002-08-14 23:21       ` Alexander Viro
2002-08-15  1:10       ` Alan Cox
2002-08-15  6:18         ` marius aamodt eriksen
2002-08-15 11:08           ` Alan Cox
2002-08-15  6:23       ` marius aamodt eriksen
2002-08-15 14:19         ` Trond Myklebust
2002-08-15  1:09   ` Alan Cox
2002-08-15  1:27     ` Dax Kelson
2002-08-15  1:35       ` Alan Cox
2002-08-15  1:51         ` Dax Kelson
2002-08-15  4:07           ` J. Bruce Fields
2002-08-15 17:35           ` Linus Torvalds
2002-08-15 18:20             ` Dax Kelson
2002-08-15 19:52             ` Roger Luethi
2002-08-15 23:07             ` Trond Myklebust
2002-08-16 14:54             ` Oliver Xymoron [this message]
2002-08-16 19:44               ` Linus Torvalds

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=20020816145434.GD5418@waste.org \
    --to=oxymoron@waste.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dax@gurulabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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