From: Ed Tanous <ed@tanous.net>
To: Anton Kachalov <rnouse@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: /etc/migration.d
Date: Thu, 22 Oct 2020 12:51:35 -0700 [thread overview]
Message-ID: <CACWQX82gk1BAyPfXgXh_9bWu4nbaGh5MA1xHAgdaFRT+nzy9bw@mail.gmail.com> (raw)
In-Reply-To: <CADVsX8_M4qcgYoVq1AC5WgMO598mWT6gfeyqrzScQQrt==uwoA@mail.gmail.com>
On Thu, Oct 22, 2020 at 9:21 AM Anton Kachalov <rnouse@google.com> wrote:
>
> Hello,
>
> any objections about distro feature flag to cover root Vs. non-root configs & code?
My only concern is whether or not it's needed. If a particular daemon
runs and functions as non-root, is there a reason why anyone would opt
out of that? Presumably as an intermediate step we could make it a
distro flag, but in the long term, ideally, that could just be the
default, right?
Are there use cases where certain builds need daemons to run as root?
next prev parent reply other threads:[~2020-10-22 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 18:47 /etc/migration.d Anton Kachalov
2020-10-16 16:50 ` /etc/migration.d Ed Tanous
2020-10-16 17:10 ` /etc/migration.d Anton Kachalov
2020-10-16 20:25 ` /etc/migration.d Patrick Williams
2020-10-16 21:01 ` /etc/migration.d Anton Kachalov
2020-10-20 11:22 ` /etc/migration.d Anton Kachalov
2020-10-22 16:19 ` /etc/migration.d Anton Kachalov
2020-10-22 19:51 ` Ed Tanous [this message]
[not found] ` <CAH2-KxA9cX49Kfp4SbRPdY1wRt3u8T7o-hUfkBORZNZ9yUXoSg@mail.gmail.com>
2020-10-22 20:39 ` [gbmc-team] /etc/migration.d Anton Kachalov
2020-10-22 20:45 ` Ed Tanous
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=CACWQX82gk1BAyPfXgXh_9bWu4nbaGh5MA1xHAgdaFRT+nzy9bw@mail.gmail.com \
--to=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=rnouse@google.com \
/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;
as well as URLs for NNTP newsgroup(s).