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,
harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 0/7 respin] network,nfs,fstab-sys stuff
Date: Thu, 02 Feb 2012 16:27:37 +0800 [thread overview]
Message-ID: <4F2A48F9.90201@gmail.com> (raw)
In-Reply-To: <20120202075944.GA12408-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
On 02/02/2012 03:59 PM, Dave Young wrote:
> This series deal with network startup without netroot and nfsmount
> in fstab-sys. Patch 1/7, 2/7 and 3/7 is same with previous ones,
> I just send them for easily tracking.
>
> [PATCH 1/7] allow ifup bring up network manually even without netroot
> [PATCH 2/7] auto setup network without netroot
> [PATCH 3/7] fix fstab-sys module check
> [PATCH 4/7] add nobody group for rpc.idmapd
> [PATCH 5/7] source dracut-lib.sh in nfs cleanup script
> [PATCH 6/7] split nfs rpc daemons startup script
> [PATCH 7/7] do not check dev node exist for fstab-sys mounting
3- 7 patches all look good to me now.
I still keep my opinion on 2/7, I think we'd better not add more cmdline
unless we have to, until now, you still don't prove "we have to do that". :)
>
> Changes from last version are:
> 4/7: new fix for nfs
> 5/7: new fix for nfs
> 6/7: start nfs-start-rpc.sh in pre-udev hook
> 7/7: remove fsck check for nfs due to fsck_able already do this for us.
It would be nicer to put these into per patch.
Thanks.
next prev parent reply other threads:[~2012-02-02 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 7:59 [PATCH 0/7 respin] network,nfs,fstab-sys stuff Dave Young
[not found] ` <20120202075944.GA12408-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2012-02-02 8:27 ` Cong Wang [this message]
[not found] ` <4F2A48F9.90201-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-02-02 8:36 ` Dave Young
2012-02-02 8:45 ` Dave Young
2012-02-02 8:44 ` 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=4F2A48F9.90201@gmail.com \
--to=xiyou.wangcong-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=harald-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