Re: End of hypocrisy, beginning of reason
On Tue, 5 Aug 2014 09:17:15 -0700
Don Armstrong <don@debian.org> wrote:
> On Tue, 05 Aug 2014, Slavko wrote:
> > To be precise, i often read about these things: monolitic, binary
> > files and boot speed. I don't like first two and i am not interested
> > in latest.
>
> These are just accessible reasons. The main reason that I personally
> voted for systemd over sysv is because systemd (and upstart) provide
> correct boot sequencing in complex boot situations.
>
> For example, if you're using iscsi, and need to start a daemon after
> the network is up, iscsi is connected, lvm has resynced, and the
> appropriate filesystems are mounted, this is trivial using systemd or
> upstart, but very difficult using sysv.[1]
>
> The other reason is we also get rid of thousands of lines of
> difficult-to-maintain boilerplate in init scripts.
>
> While sysv may be easier to debug in simple systems, there's a reason
> why none of the CTTE members (myself included) voted for it.
>
> 1: Not impossible, but you basically end up replicating a dependency
> boot system in shell, and necessarily introduce brittleness and
> delays.
Cool! Finally someone who knows it and is on the ground floor. I have
some questions...
When I switch to systemd, I'd like to have it as isolated as humanly
possible, just because I'm a modularity kind of guy.
I'm thinking of starting the minimum possible daemons with systemd, and
starting the rest with daemontools. Of course, I've never before had to
manage run order in daemontools, so that might be a little challenging,
but I think I can handle it, even if I have to pull off a kludge.
Another challenge will be to prevent systemd from starting the daemons
I want to launch with daemontools, even though the package installer
tells systemd to launch those programs. Is it pretty easy to tell
systemd not to launch specific daemons?
I will, as usual when I use Debian, start my desktop environment with
startx or xinit. I usually use Xfce, LXDE, Openbox, dwm or i9. Do you
think I'll have systemd dependencies with those de's started with
startx or xinit?
What other tips would you have for those of us who want to, to the
extent possible, keep systemd as nothing more than the first program to
be booted, and want to reduce as much as possible what other programs
need to know about systemd and what systemd needs to know about the
programs I run?
Thanks,
SteveT
Steve Litt * http://www.troubleshooters.com/
Troubleshooting Training * Human Performance
Reply to: