public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: "Vlad C." <vladc6@yahoo.com>
Cc: Hans Reiser <reiser@namesys.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux On-Demand Network Access (LODNA)
Date: Wed, 13 Jul 2005 11:32:26 -0400	[thread overview]
Message-ID: <42D5340A.7060002@redhat.com> (raw)
In-Reply-To: <20050712234425.55899.qmail@web54409.mail.yahoo.com>

Vlad C. wrote:

>--- Hans Reiser <reiser@namesys.com> wrote:
>  
>
>>Please treat at greater length how your proposal
>>differs from NFS.
>>    
>>
>
>I think NFS is not flexible enough because:
>
>1) NFS requires synchronization of passwd files or
>NIS/LDAP to authenticate users (which themselves
>require root access on both server and client to
>install)
>2) NFS by definition understands only its own network
>protocol.
>3) NFS requires root privileges on the client to
>mount. I'm not aware of a way to let normal users
>mount an NFS partition other than listing it in the
>client's fstab and adding the 'users' option... but
>then changing fstab still requires root access.
>4) Users have to contact their sysadmin every time
>they want to mount a different partition, a different
>subdirectory of the same partition, or if they want to
>change the local mountpoint, all because the partition
>and mountpoint are hard-coded in fstab.
>
>On the other hand, I envision the following:
>

Please keep in mind that these are restrictions of the current NFS
implementation and are not inherent in an NFS solution.

The implied need for flexibility is being addressed by NFSv4 and the
ability to understand multiple versions of protocols and multiple
protocols is already resident in the system.  We could do some work
to make it more transparent if desired, but it already works.

    Thanx...

       ps

  parent reply	other threads:[~2005-07-13 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 16:07 Linux On-Demand Network Access (LODNA) Vlad C.
2005-07-12 18:48 ` Hans Reiser
2005-07-12 19:32   ` Jeremy Maitin-Shepard
2005-07-12 23:44   ` Vlad C.
2005-07-13  1:18     ` Hans Reiser
2005-07-14 19:32       ` Vlad C.
2005-07-13 15:32     ` Peter Staubach [this message]
2005-07-13 18:24       ` Hans Reiser
2005-07-13 18:47         ` Peter Staubach
2005-07-13 19:07           ` Hans Reiser
2005-07-14 18:43       ` Vlad C.
2005-07-14 15:57 ` Alan Cox

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=42D5340A.7060002@redhat.com \
    --to=staubach@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=vladc6@yahoo.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