Linked by Thom Holwerda on Wed 3rd Nov 2010 22:49 UTC, submitted by poundsmack
Fedora Core Fedora 14 has been released. "The Fedora Project today announced the availability of Fedora 14, the latest version of its free open source operating system distribution. The Fedora Projects leads the advancement of free and open source software with a new distribution released approximately every six months."
Thread beginning with comment 448537
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Is it possible to get a listing of which order things will start at boot, with systemd?

This is my biggest frustration with upstart: you have no way to tell which order things will start at boot. And every boot can use a different order.

Managing SysV init scripts and runlevels is a pain. But trying to get any semblance of order out of upstart is just as bad.

RC on FreeBSD is dependency-based as well, but at least there you can get the general order that things will start via a simple "rcorder /etc/rc.d/* /usr/local/etc/rc.d/*"

What's the equivalent for upstart/systemd?

Reply Parent Score: 2

brion Member since:

I'm not sure there's really an applicable concept of "what order things will load in".

By definition they're trying to get everything that's needed started up as fast as possible; this may include starting multiple things at the same time which don't depend on each other, and when other things that do depend on them get started will depend on how long those previous things took to start, and whether they're actually needed or in use.

It would be similarly difficult to ask what order the user will start programs or visit web sites in after logging in; the order will depend on what the user has to or wants to do, what messages came into their inboxes, what links they receive in email and chat, etc.

More generally, I really hate to rely on assuming that things are going to start up in a particular order; unless you're doing cold boots constantly, you may have services starting and stopping at runtime, say as software is updated or new services get activated. To be reliable, the control systems for these should be explicitly set up to ensure that things load each other when needed rather than just hoping everything comes up in the right order... otherwise you tend to get surprised when that next cold boot comes, and the simple manual ordering wasn't right after all.

Accept your new non-deterministic overlords! ;)

Reply Parent Score: 1

phoenix Member since:

IOW, it's impossible to get a standard, ASCII representation of the dependencies, thus making the boot process "yet another black box". ;)

Knowing the exact order things will start isn't an absolute requirement. But being able to get a dependency graph out of the process most certainly is.

Reply Parent Score: 2