From: Christian Heinz <christian.ch.heinz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] dracut: create ldconfig aux cache directory on the initrd
Date: Tue, 7 Dec 2010 12:11:33 +0100 [thread overview]
Message-ID: <20101207111133.GA32623@neptun> (raw)
In-Reply-To: <1291715126-sup-971@ittemni>
Hi,
> What is the benefit of "falling partially" over "falling completely".
> I'm wondering if there shouldn't be check if dracut is run by non-root
> and then exit immediately. Normal user cannot read some files (e.g.
> /bin/mount), so what's the point?
Not having read permission for /bin/mount as normal user looks weird to
me. I use dracut on Arch Linux, though I also just tested on a Fedora VM
and everything builds/runs just fine without root permissions. Are there
any compelling reasons to restrict image generation to root only? Am
I missing something fundamental?
Regards,
Christian
next prev parent reply other threads:[~2010-12-07 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 1:44 [PATCH 1/2] dracut: create ldconfig aux cache directory on the initrd Christian Heinz
[not found] ` <1291686260-32371-1-git-send-email-christian.ch.heinz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-12-07 1:44 ` [PATCH 2/2] dracut: don't print misleading dinfo after successful ldconfig run Christian Heinz
2010-12-07 9:49 ` [PATCH 1/2] dracut: create ldconfig aux cache directory on the initrd Amadeusz Żołnowski
2010-12-07 9:54 ` Amadeusz Żołnowski
2010-12-07 11:11 ` Christian Heinz [this message]
2010-12-07 11:55 ` Amadeusz Żołnowski
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=20101207111133.GA32623@neptun \
--to=christian.ch.heinz-re5jqeeqqe8avxtiumwx3w@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 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.