From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: making sysvinit optional
Date: Wed, 10 Jul 2019 20:17:06 -0400 [thread overview]
Message-ID: <b10dfd2b-1fe4-0f55-132e-83476db6c60a@gentoo.org> (raw)
In-Reply-To: <20190711000332.GA6104@whubbs1.dev.av1.gaikai.org>
On 7/10/19 8:03 PM, William Hubbs wrote:
>>
>> This logic, or maybe the name of the flag, sounds backwards to me. I
>> only get sysvinit when USE=sysvinit is NOT set?
>
> If you don't set sys-apps/openrc[sysvinit], you would have /sbin/init
> and /sbin/shutdown as they are now, from sys-apps/sysvinit.
>
> If you do set sys-apps/openrc[sysvinit], /sbin/init and /sbin/shutdown
> would become wrappers for /sbin/openrc-init and /sbin/openrc-shutdown.
Which way do muons spin?
>> Modulo my first comment, you'll want some USE flag (un)set for
>> sys-apps/openrc to ensure that /sbin/init is provided.
>
> I am willing to be convinced, but I'm not sure all providers of a virtual
> are required to provide the same binaries. A couple of examples off the
> top of my head are virtual/editor, virtual/logger and virtual/mta.
Will the system boot if you don't install sysvinit and if you don't
provide the /sbin/init wrapper for /sbin/openrc-init?
next prev parent reply other threads:[~2019-07-11 0:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 20:25 [gentoo-dev] rfc: making sysvinit optional William Hubbs
2019-07-10 21:48 ` William Hubbs
2019-07-10 23:16 ` William Hubbs
2019-07-10 23:30 ` Michael Orlitzky
2019-07-11 0:03 ` William Hubbs
2019-07-11 0:17 ` Michael Orlitzky [this message]
2019-07-11 3:14 ` William Hubbs
2019-07-11 13:01 ` Michael Orlitzky
2019-07-11 15:43 ` William Hubbs
2019-07-11 16:11 ` Michael Orlitzky
2019-07-11 17:03 ` William Hubbs
2019-07-11 0:17 ` Rich Freeman
2019-07-11 3:02 ` William Hubbs
2019-07-11 13:42 ` Rich Freeman
2019-07-11 15:56 ` William Hubbs
2019-07-11 16:46 ` Rich Freeman
2019-07-11 17:22 ` William Hubbs
2019-07-11 17:38 ` Rich Freeman
2019-07-11 15:39 ` Mike Gilbert
2019-07-11 16:43 ` William Hubbs
2019-07-11 0:19 ` William Hubbs
2019-07-13 17:51 ` William Hubbs
2019-07-14 13:54 ` Mike Gilbert
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=b10dfd2b-1fe4-0f55-132e-83476db6c60a@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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