All of lore.kernel.org
 help / color / mirror / Atom feed
From: steve <steve@steve-ss.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Don Riden <don@riden.org.uk>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: where can I ask user qns about nfs4?
Date: Sat, 11 Feb 2012 00:20:16 +0100	[thread overview]
Message-ID: <4F35A630.4000205@steve-ss.com> (raw)
In-Reply-To: <20120210191448.GD5781@fieldses.org>

On 02/10/2012 08:14 PM, J. Bruce Fields wrote:
> On Fri, Feb 10, 2012 at 08:13:16PM +0100, steve wrote:
>> On 02/10/2012 07:40 PM, J. Bruce Fields wrote:
>>> On Fri, Feb 10, 2012 at 09:19:38AM +0100, steve wrote:
>>>>>> I'm happy to provide more details of the domain joining process
>>>>>> offlist or summarise in another
>>>>>> email if there is interest.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I'm surprised by the lack of documentation available on using
>>>>>> Kerberised NFS with AD. I would have thought that it would be a
>>>>>> fairly common configuration?
>>>> Hi
>>>> This stuff really does need documenting. I've put together a rough
>>>> guide of most of the common misunderstandings here:
>>>> http://linuxcostablanca.blogspot.com/2012/02/nfsv4-myths-and-legends.html
>>> Could you get some of this material into the linux-nfs wiki?
>>>
>>> The NFS w/ AD stuff, for example, would probably be worth a page of its
>>> own and a top-level link under "Documentation" (and the link to Mike
>>> Eisler's blog entry could be moved to the page, if it still looks like
>>> it's current).
>>>
>>> --b.
>> Unfortunately, I am unable to write technical English in the style
>> that is required by the wiki.
> Just say it however it makes sense to you, ping me, and I can do any
> wordsmithing if it seems necessary.
>
> --b.
>
>> I am however happy for the link to be
>> placed there. As there is no user nfs mailing list I'm also happy
>> for folk to sign up to the article and use _it_ as a mailing list.
OK. I've requested a login. Linux has never been too good with 
documentation. At nfs level, unless you are capable of reading the code, 
you are stuck with misinformation. What I feel is that admins are stuck 
in the middle. It's a dilemma. You don't want to want to have to burden 
the devs with what to them is trivia. As admin, you have your own 
trivia: 'I saved it in My Documents but now only Sharon can open it'. 
You also need to be able to move forward without guessing: 'What's the 
official syntax for /etc/exports with krb5'. Your users get their 
answers. From you. Where are we expected to get our answers from!
Cheers,
Steve

  reply	other threads:[~2012-02-10 23:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02  6:39 where can I ask user qns about nfs4? steve
2012-02-02 10:58 ` Tigran Mkrtchyan
2012-02-02 11:33   ` nfs4 keytabs [was:Re: where can I ask user qns about nfs4]? steve
2012-02-02 13:05     ` Tigran Mkrtchyan
2012-02-02 13:29       ` steve
2012-02-02 14:56         ` steve
2012-02-02 18:57           ` Tigran Mkrtchyan
2012-02-03 17:22             ` steve
2012-02-06 13:31               ` steve
2012-02-04 20:50   ` where can I ask user qns about nfs4? Liam Gretton
2012-02-05  9:26     ` steve
2012-02-05 14:16       ` Jim Rees
2012-02-05 16:55         ` Liam Gretton
2012-02-05 17:37           ` Jim Rees
2012-02-06 16:39             ` J. Bruce Fields
2012-02-06 18:54               ` steve
2012-02-09 18:57           ` Don Riden
2012-02-09 19:33             ` steve
2012-02-10  8:19               ` steve
2012-02-10 18:40                 ` J. Bruce Fields
2012-02-10 19:13                   ` steve
2012-02-10 19:14                     ` J. Bruce Fields
2012-02-10 23:20                       ` steve [this message]
2012-02-10 20:47             ` Liam Gretton

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=4F35A630.4000205@steve-ss.com \
    --to=steve@steve-ss.com \
    --cc=bfields@fieldses.org \
    --cc=don@riden.org.uk \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.