On Mon, 18 Dec 2017 07:19:02 -0500
Sam Varshavchik <mrsam(a)courier-mta.com> wrote:
When we had initiscripts, I forget which one it was, but there was
one that read all the config files, and enabled those interfaces. And
stuff that depended on the network being up ran after that. Simple.
Easy. So, again: is it unreasonable to be able to start things that
require the statically- assigned IP addresses after they actually are
assigned to their network ports? Did something change, in the world
we live in, where this is not possible any more? And what exactly did
change, that made this a logically impossible, herculean task?
I think you are talking about the days before we had multi-threaded
boot, and boot was deterministic. Boot went to multi-threaded, and so
became non-deterministic, in order to shorten boot time. Maybe
part of the solution is a kernel (or systemd) switch that says, "I
don't care if boot takes 10 or 20 seconds (or a minute) longer, I want
it to be deterministic." If that switch was set, then things would
always run sequentially in a fixed order, unlike now.