From: Cong Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] deal with nfs in fstab-sys
Date: Mon, 30 Jan 2012 17:12:01 +0800 [thread overview]
Message-ID: <4F265EE1.7010505@gmail.com> (raw)
In-Reply-To: <4F265CAA.2080804-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 01/30/2012 05:02 PM, Dave Young wrote:
> On 01/30/2012 04:43 PM, Cong Wang wrote:
>
>> On 01/30/2012 04:41 PM, Dave Young wrote:
>>> On 01/30/2012 04:20 PM, Cong Wang wrote:
>>>
>>>> On Mon, 30 Jan 2012 at 06:44 GMT, Dave Young<dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>>>>> If we need to mount nonroot nfs in fstab we also need to launch rpc
>>>>> processes
>>>>> Add nfs-start-rpc code, also do not check and fsck $_dev in this case
>>>>
>>>> Isn't it nfs module's responsibility to call nfs-start-rpc code?
>>>> Why do you put it in fs-systab?
>>>
>>>
>>> nfs know nothing about fstab mount, it only deal with nfsroot thing. So
>>> I have to do this in fstab-sys
>>
>> Sure, but nfs module knows it needs to start rpc before mounting NFS.
>>
>> So, what's the problem if we call nfs-start-rpc script in pre-pivot hook
>> of nfs module (before mount-sys.sh, of course)?
>
>
> Actually nfs-start-rpc need to know the fs is nfs or nfs4, If add it as
> a hook, how does it accept the argument?
I think you can start rpc daemons unconditionally, no matter if it is
nfs4 or nfs.
next prev parent reply other threads:[~2012-01-30 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 6:44 [PATCH] deal with nfs in fstab-sys Dave Young
2012-01-30 8:20 ` Cong Wang
2012-01-30 8:41 ` Dave Young
[not found] ` <4F2657B4.3030200-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30 8:43 ` Cong Wang
[not found] ` <4F26581B.4040305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30 9:02 ` Dave Young
[not found] ` <4F265CAA.2080804-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30 9:12 ` Cong Wang [this message]
[not found] ` <4F265EE1.7010505-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30 9:20 ` Dave Young
[not found] ` <4F2660DB.8030105-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-01-30 9:27 ` Cong Wang
[not found] ` <4F266282.8040204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-31 9:56 ` Dave Young
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=4F265EE1.7010505@gmail.com \
--to=xiyou.wangcong-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox