From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: /etc/passwd thoughts
Date: Fri, 12 Jun 2009 23:21:19 +0200 [thread overview]
Message-ID: <4A32C6CF.9010802@bfh.ch> (raw)
In-Reply-To: <4A32B94E.10902-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Warren Togami wrote:
> On 06/12/2009 04:20 PM, Bill Nottingham wrote:
>> Warren Togami (wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org) said:
>>> [warren@newcaprica dracut]$ grep -r \/etc\/passwd *
>>> modules.d/95nfs/install:dracut_install /etc/netconfig /etc/passwd
>>> /etc/services
>>> modules.d/95nfs/install:#echo
>>> "rpc:x:32:32:Rpcbind:/var/lib/rpcbind:/bin/false">>
>>> "$initdir/etc/passwd"
>>> modules.d/90mdraid/install:inst /etc/passwd
>>>
>>> It seems that we want an /etc/passwd for certain things in the initrd
>>> image, but is it really necessary for it to copy whatever users are on
>>> the generating system into the image?
>>
>> If daemons we want/need to start want to drop privleges... yes.
>>
>
> But it is also pulling in user accounts.
>
> It seems the above modules.d/95nfs/install creates its own /etc/passwd
> entry that it expects to be there. Why can't we do this for all cases
> where something in the initrd needs an /etc/passwd entry?
Actually 95nfs doesn't create its own entry. The part is commented out.
But I agree we should do something about the passwd case.
Question: Who really needs passwd entries?
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-12 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 20:19 /etc/passwd thoughts Warren Togami
[not found] ` <4A32B84E.8090603-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-12 20:20 ` Bill Nottingham
[not found] ` <20090612202045.GA30968-Zdt1ptygihhQcNjhGXsBABcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2009-06-12 20:23 ` Warren Togami
[not found] ` <4A32B94E.10902-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-12 21:21 ` Seewer Philippe [this message]
[not found] ` <4A32C6CF.9010802-omB+W0Dpw2o@public.gmane.org>
2009-06-13 2:12 ` David Dillow
[not found] ` <1244859170.18551.9.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2009-06-13 4:04 ` Seewer Philippe
2009-06-16 18:42 ` Warren Togami
[not found] ` <4A38CABB.9070900@redhat.com>
[not found] ` <4A38CABB.9070900-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-17 17:08 ` Warren Togami
[not found] ` <4A39231E.8050700-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-18 17:14 ` 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=4A32C6CF.9010802@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wtogami-H+wXaHxf7aLQT0dZR+AlfA@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 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.