Douglas R. Reno wrote:
On Nov 27, 2016 5:10 PM, "Bruce Dubbs" <[email protected]> wrote:
akhiezer wrote:
D-Bus next to be 'integrated' into sysd? :
----
https://lwn.net/Articles/705479/
--
Nov. 2016
--
"D-Bus is incompatible with a chroot() environment because there is
a need to drop policy files into the host filesystem. For now, that
is an unsolved problem, but the goal is to move D-Bus functionality
into systemd itself. That is something the project should have done a
long time ago, Poettering said. The systemd D-Bus server would then
use a different policy mechanism that doesn't require access to the
host filesystem."
----
Why do they NEED to do this? The short answer is that they don't. It's
about politics and control.
https://devuan.org/
Have you ever heard of Containers? They use these VM snapshots all over in
modern IT. Each container is running on a host running systemd and one of
Xen, Docker, KVM, etc. And the Containers can all start off the same image
with the exception of a few volatile filesystems. Companies such as
CapitalOne and Abbot Laboratories use this all the time. They do this to
cut energy usage and bring the TCO down. This is why systemd was invented.
It is NOT about Politics and Control. There is a practical reason for it.
And what percentage of Linux users uses this capability? One size fits
all? And at the expense of complexity. There is a problem with dhcp --
updated systemd. There is a problem with ntp -- update systemd. There is
a problem with udev -- update systemd.
The bigger a software package becomes, the harder it is to ensure security
and otherwise manage.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
