Systemd, nightmare or opportunity?
"Rob Meijer" <rmeijer-qWit8jRvyhVmR6Xm/[email protected]>
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <[email protected]> |
As those of you who use Linux may know, more and more Linux distributions are moving away from their init systems, and are moving to systemd. A consortium of interdependent system programs that replace not only init/startup, but a whole range of other functionality that were previously handled by independent software in the unix line (do one thing, do one thing good) that I feel loosely forms the philosophy that also underlies capability discipline. On one side, it would seem that a move away from this philosophy would be a move away from anything POLA related. On the other side however, this also might provide an opportunity/challenge for people concerned with least authority on the language level. If we could come up with a drop-in least authority rewrite of systemd in a capability secure language (David-Sarah might have a clue about what language to pick ;-) ), this could definetely become the basis for a much more robust version of Linux, that could easily be addapted by all those distro's now moving towards this horrible systemd architecture. Any thoughts?