...Concerning systemd, I do like the idea of a faster boot time (obviously), but I also like controlling the startup of the system with shell scripts that are readable, and I'm guessing that's what most Slackware users prefer too. I don't spend all day rebooting my machine, and having looked at systemd config files it seems to me a very foreign way of controlling a system to me, and attempting to control services, sockets, devices, mounts, etc., all within one daemon flies in the face of the UNIX concept of doing one thing and doing it well. To the typical end user, if this results in a faster boot then mission accomplished. With udev being phased out in favor of systemd performing those tasks we'll have to make the decision at some point between whether we want to try to maintain udev ourselves, have systemd replace just udev's functions, or if we want the whole kit and caboodle....
В gentoo не все так плохо, ну и lvs. Хотя, если debian оставят на выбор: sysvinit, systemd, openrc, upstart, то может не все так плохо. Хотя нет, плохо т.к. разработчики могут отказаться от своих проектов в силу того, что ментейнеры их заменяют на systemг.
Он же сказал, что при том, что системд имеет плюс в виде быстрой загрузки, все остальное выглядит странно и выбор поддерживать udev самим, ставить системд в качестве системы инициализации или ставить ее либы, щоп работал удев - большущий такой вопрос т.е. отношение у него неположительное (или условно-отрицательное)
but I also like controlling the startup of the system with shell scripts that are readable, and I'm guessing that's what most Slackware users prefer too. I don't spend all day rebooting my machine, and having looked at systemd config files it seems to me a very foreign way of controlling a system to me