On 2014-09-18, Rich Freeman <[email protected]> wrote:
> On Thu, Sep 18, 2014 at 3:18 PM, Grant Edwards
><[email protected]> wrote:
>> The only Linux systems where I care about boot time are embedded
>> systems which are never going to have the resources needed to run
>> systemd.
>
> How about containers? When I launch mariadb I'd prefer that it
> happen in milliseconds, not tens of seconds. That includes setting
> up interfaces, populating /dev, getting an ip, launching ssh, syslog,
> etc, and so on, oh, and mariadb.
OK, that makes sense. I've never used containers and only have a
vague understanding of what they are -- I occasionally use a VM or
two, but startup speed doesn't matter for them in my applications. I
assumed there must be _some_ application where boot up speed is
important, but I just didn't know what it would be.
>> The other thing I keep hearing from systemd proponents is stuff about
>> how it allows you to parallelize startup. I don't _want_ stuff
>> starting up in parallel -- that just makes it all the more difficult
>> to troubleshoot problems. I want things to start up one at a time, in
>> a determined order.
>
> I hope you aren't running openrc then. It doesn't launch in a
> predetermined order.
I'm am running openrc (with parallel startup disabled) on my "regular"
Gentoo systems. On my systems, the startup order seems to be
deterministic. [I also have a bunch of "other" systems I boot on
occasion for testing apps/drivers -- they're running various distros
using whatever init system they default to.]
> I will agree that you get far more race conditions than you do with
> openrc even with parallel startup, since processes start much more
> quickly.
--
Grant Edwards grant.b.edwards Yow! It's the RINSE CYCLE!!
at They've ALL IGNORED the
gmail.com RINSE CYCLE!!
