Personally I have no issue with systemd.. I dont see what all the fuss is about. It boots considerably faster than sysv init.

Politics? Philosophy? I guess... There are some many points where systemd breaks the basic UNIX philosophy, that practically created GNU. The logs are binary and not that easy to recover when the system goes down. The other thing is that systemd is taking the Microsoft approach: "monolitic everything". This goes agains Linux, which by definition should me "modular everything". Some people don't have a problem with it. Other do. I myself was wondering if there should be an attempt to modernize sysinitv, to make use of modern coding techniques and standards.

Logged

There isn't a single thing that's impossible. Just the things that we don't yet know how to deal with.

Now that you mention logs. I notice there is no 'journal' (/var/log/journal/) folder and file generated in Sparky.? That must be by design, as I find them in my Manjaro and Arch (both also systemd) installs.

Now that you mention longs. I notice there is no 'journal' (/var/log/journal/) folder and file generated in Sparky.? That must be by design, as I find them in my Manjaro and Arch (both also systemd) installs.

If it's by design, then it's by Debian design. As far as I know we didn't modify anything regarging systemd.

Logged

There isn't a single thing that's impossible. Just the things that we don't yet know how to deal with.

Journal size limitIf the journal is persistent (non-volatile), its size limit is set to a default value of 10% of the size of the respective file system. For example, with /var/log/journal located on a 50 GiB root partition this would lead to 5 GiB of journal data. The maximum size of the persistent journal can be controlled by SystemMaxUse in /etc/systemd/journald.conf, so to limit it for example to 50 MiB uncomment and edit the corresponding line to:

I dont see what all the fuss is about. It boots considerably faster than sysv init.

That's funny. My system does not boot any faster than LMDE with sysvinit I used before. But shutdown is considerably faster (maybe 3 seconds using Sparky and systemd vs. 20 seconds using LMDE with sysvinit).I don't see what the fuss is about either, but I am no programmer, so maybe I lack the insight

One last thing with Debian is to set up peristent logging with systemd's logging component called journal. By default journal will log to /run which is ephemeral meaning the logs will disappear after reboot. The process of making the logs persistent (if you choose to do so) is documented here: /usr/share/doc/systemd/README.Debian ..............It's worth noting that you don't have to use journal if you don't want to, it's designed to co-exist with syslog, that's already running on your system, so you can continue to use that. I personally find journal awesome and would recommend that you at least check it out and see what it brings to the table.

That explains why no journal log for me on Sparky.. I don't miss it. The other 'syslogs' are actually more helpful. As for boot times, et. I believe a lot depends on individual hardware and configs.

And YES, it does appear that internal debian politics account for a lot of the fuss....

The commentary on DistroWatch generally opposes systemd for the reasons mentioned: A loss of modularity and therefore, control.

I upgraded an openSUSE xfce installation from 13.1 to 13.2 via zypper dup last night and that installed systemd. On rebooting the process was noticeably faster but someone else posted that the opposite was true, on his machine.

The question here is whether a Debuan version of Sparky is contemplated? The only way to know for sure is to try them both.