From: Hans Reiser <reiser@namesys.com>
To: Peter Staubach <staubach@redhat.com>
Cc: "Vlad C." <vladc6@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux On-Demand Network Access (LODNA)
Date: Wed, 13 Jul 2005 12:07:09 -0700 [thread overview]
Message-ID: <42D5665D.9070706@namesys.com> (raw)
In-Reply-To: <42D561AB.3060002@redhat.com>
Peter Staubach wrote:
> Hans Reiser wrote:
>
>> Peter, do you agree with his point that mounting should be something
>> ordinary users can do on mountpoints they have write permission for?
>>
>> Do you agree that a systematic review of user friendliness would help
>> NFS? Do you think that NFS should look at SFS and consider adopting
>> some of its features?
>>
>
> I think that connecting to required data could be more easily done than
> currently. I don't know about allowing file systems to be mounted without
> some form of control or resource utilization controls however.
>
> I do agree that the entire user experience associated with using and
> trying
> to administrate an NFS network could stand a good, long, hard look.
>
> Traditional tools such as the automounter were nice 15 years ago, but
> have
> not evolved with the world, nor have the rest of the system tools for
> monitoring and managing NFS clients and servers.
>
> I could definitely envision better ways to handle things. In the past,
> many of the arguments against making things better were security related.
> There has been strong (relative term) security available to NFS
> implementations
> since 1997, but many vendors have not implemented it and many
> customers found
> it difficult to deploy because the underlying tools were very
> difficult to
> deploy. Many of the vendors are now implementing the security
> framework, but
> more work is required on the underlying security mechanisms, making them
> easier to deploy.
>
> With proper security, usable monitoring and management tools, and
> flexible
> resource controls, then I wouldn't see why NFS mounts should be anything
> special.
>
> Thanx...
>
> ps
>
>
I would encourage you to look at SFS..... it fixes a lot, making adding
what Vlad asks for reasonable.
next prev parent reply other threads:[~2005-07-13 19:10 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
2005-07-13 18:24 ` Hans Reiser
2005-07-13 18:47 ` Peter Staubach
2005-07-13 19:07 ` Hans Reiser [this message]
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=42D5665D.9070706@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=staubach@redhat.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