From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Cong Wang <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/5 branch usrmove v2] deal common part of etc passwd in 99base
Date: Thu, 29 Dec 2011 18:00:14 +0800 [thread overview]
Message-ID: <4EFC3A2E.6020606@redhat.com> (raw)
In-Reply-To: <CAM_iQpX6kWGPB_mGUWOaywQgxeWEC+Og6WjOZmknS+FPGuA0xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 12/29/2011 05:48 PM, Cong Wang wrote:
> On Thu, Dec 29, 2011 at 5:45 PM, Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> On 12/29/2011 05:27 PM, Cong Wang wrote:
>>> The nfs module still uses "/" as home of root, while ssh module uses
>>> "/root". With you patches, you changed to "/root" for both nfs and
>>> ssh, which *maybe* a problem for nfs module since you didn't test it.
>>
>>
>> I tested nfs boot as well, it works ok with $HOME=/root
>
> Ok, will change to "/root" too.
>
>>
>> Also if you add both ssh-client and nfs, what's the result of /etc/passwd?
>
> If the line "root:" exists before,
>
> egrep -q '^root:' "$initdir/etc/passwd" 2>/dev/null || echo
> 'root:x:0:0::/:/bin/sh' >> "$initdir/etc/passwd"
>
> egrep will succeed and echo will not be executed...
Yes, but who knows which module will be added firstly, maybe there's
other module do this in future.
But if nfs also use /root as HOME it will be ok currently
--
Thanks
Dave
next prev parent reply other threads:[~2011-12-29 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 6:29 [PATCH 1/5 branch usrmove v2] deal common part of etc passwd in 99base Dave Young
2011-12-27 11:44 ` Cong Wang
2011-12-29 3:03 ` Dave Young
2011-12-29 9:27 ` Cong Wang
2011-12-29 9:40 ` Cong Wang
2011-12-29 9:45 ` Dave Young
[not found] ` <4EFC36CD.8040205-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-12-29 9:48 ` Cong Wang
[not found] ` <CAM_iQpX6kWGPB_mGUWOaywQgxeWEC+Og6WjOZmknS+FPGuA0xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-12-29 10:00 ` Dave Young [this message]
[not found] ` <4EFC3A2E.6020606-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-12-29 10:04 ` Cong Wang
[not found] ` <20111226062910.GA3141-4/PLUo9XfK+sDdueE5tM26fLeoKvNuZc@public.gmane.org>
2012-01-23 11:03 ` Harald Hoyer
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=4EFC3A2E.6020606@redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@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