Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Neil Brown <neilb@suse.de>,
	linux-nfs@vger.kernel.org, chuck.lever@oracle.com,
	steved@redhat.com
Subject: Re: [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet
Date: Sun, 29 Aug 2010 15:37:17 -0400	[thread overview]
Message-ID: <20100829193717.GB1627@fieldses.org> (raw)
In-Reply-To: <20100828222450.7ca62e49@corrin.poochiereds.net>

On Sat, Aug 28, 2010 at 10:24:50PM -0400, Jeff Layton wrote:
> On Sun, 29 Aug 2010 08:38:53 +1000
> Neil Brown <neilb@suse.de> wrote:
> > I don't think it is all that bad.  It is a shame you have to use system()
> > rather than just calling mount() directly but I guess we need that to
> > update /etc/mtab.
> > 
> 
> Yeah, that's the main reason I went with system(). It's worthwhile to
> note that I'm using the exact same command that's in modprobe.conf on
> fedora/RHEL.
> 
> > Suggestions:
> > 
> >  - just don't do that.  Use /etc/init.d/nfsserver start (or whatever the
> >    distro uses).
> 
> I don't think we should count on that. Most people will use that, but
> it seems like we shouldn't require that for this to work as expected...
> 
> >  - Make /proc/fs/nfsd and auto-mount point.  That sounds like the systemd
> >    approach.
> 
> Yes, I think systemd will take care of this eventually, but I think we
> need something for existing distros that aren't using it yet.

I thought Neil was saying that this would be a "systemd-like" approach,
not that it would actually require systemd.  Am I missing something?

I can't come up with an immediate objection.  I'm also not opposed to
your patch as it stands.

--b.

  parent reply	other threads:[~2010-08-29 19:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 11:35 [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet Jeff Layton
2010-08-28 22:29 ` Neil Brown
2010-08-28 22:38 ` Neil Brown
2010-08-29  2:24   ` Jeff Layton
2010-08-29 19:31     ` J. Bruce Fields
2010-08-29 19:37     ` J. Bruce Fields [this message]
2010-08-29 22:12       ` Neil Brown
2010-08-30 15:51 ` Steve Dickson
2010-08-30 16:16   ` Jeff Layton
2010-08-30 16:53     ` Steve Dickson
2010-08-30 17:04       ` J. Bruce Fields
2010-08-30 17:22         ` Jeff Layton
2010-08-31 12:14         ` Steve Dickson
2010-08-30 17:48       ` Jeff Layton
2010-08-31 12:24         ` Steve Dickson
2010-08-31 12:43           ` Jeff Layton
2010-08-31 14:49             ` Steve Dickson
2010-08-31 15:10               ` Jeff Layton
2010-08-31 15:13                 ` J. Bruce Fields
2010-08-31 15:18                   ` Steve Dickson
2010-08-31 15:51                     ` J. Bruce Fields
2010-08-31 16:13                       ` Steve Dickson
2010-08-31 16:15                         ` J. Bruce Fields
2010-08-31 17:18                           ` Steve Dickson
2010-08-31 18:07                             ` J. Bruce Fields
2010-08-31 18:59                               ` Steve Dickson
2010-08-31 19:02                                 ` Jeff Layton

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=20100829193717.GB1627@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=steved@redhat.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