7 ms·
Nice article, but at this point it's game, set, match -- systemd has won. The Linux community overwhelmingly supports it, and its advantages clearly outweigh it
by bitwize 13y ago
Nice article, but at this point it's game, set, match -- systemd has won. The Linux community overwhelmingly supports it, and its advantages clearly outweigh its perceived disadvantages.
"It's not Unix" is no longer a valid critique. The old Unix design philosophy is dead. People want systems of components that function as an integrated whole. They do NOT want pieces that are generally unaware of each other (this is touted as the virtue of "loose coupling").
Yes, pid 1 does a lot. That's by necessity. It's not your grandpap's Unix anymore. Do you want to control all the system services, including the "badly behaved" ones? That functionality needs to be in pid 1. Do you want to bring the system up safely and sanely, accounting for things like hotplugged disks in /etc/fstab? That functionality needs to be in pid 1. Systemd is the correct design for modern Linux. It also brings the advantage of better integration and greater commonality across distros.
- icebraining 13y agoWhy do those things need to be on pid 1? Just asserting it is not really convincing.
- sandGorgon 13y agoAny init system needs to be pid 1 [1] This blog post does not identify the subtle argument that upstart maintainers made against systemd at pid -1 : it also brings along with all the other services (like logind) that frameworks like Gnome depend on. So, if Gnome wants to depend on logind and logind depends on systemd (post systemd rev-205), this means that Gnome is irrevocably coupled to systemd which must run as PID-1 [2]. This means it becomes hard for upstart to be used with Gnome. There has been no doubt whatsover that an init system needs to run as PID-1. [1] http://en.wikipedia.org/wiki/Process_identifier#Unix-like http://en.wikipedia.org/wiki/Process_identifier#Unix-like [2] I must add here that Gnome does include a fallback path to not depend on systemd components.
- vidarh 13y agoA part of any init system needs to be pid 1. The question is how much of it, and whether or not Systemd piles too much stuff into pid 1 that could instead be farmed out to separate processes, handled by separate binaries, that could be more easily upgraded or replaced. (I don't know; I've not looked at Systemd enough to have an opinion)
- sandGorgon 13y agothey are separate binaries - however all of them depend on systemd (post rev 205) and cannot be run independently. this is because all of systemd's services rely strongly on cgroups for resource control and upstream kernel wants a single reader/writer for the cgroups API (the current filesystem model is going away). systemd is just following lockstep with what kernel wants and is becoming that API. There has been a lot of FUD around the "PID 1" disaster, but invariably every init system will have to have a single point cgroup writer. Systemd is just ahead of the curve.
- ithkuil 13y agohttp://lists.freedesktop.org/archives/systemd-devel/2013-June/011521.html http://lists.freedesktop.org/archives/systemd-devel/2013-Jun... Anyone has more information about this from the kernel perspective ? Will systemd be the only API ? Sounds strange.
- sandGorgon 13y agoThis is a reasonable evaluation of the status - https://lwn.net/Articles/575672/ https://lwn.net/Articles/575672/ Basically, if you use systemd as the init system, then yes - it is the only API [1] . If you dont want to use systemd then there are alternate implementations of the cgroup API (e.g. cgmanager - http://cgmanager.linuxcontainers.org/ http://cgmanager.linuxcontainers.org/ ). IMHO, they are both incompatible with each other. Lennart has a reasonable justification of why systemd is implementing it's own API [2] [1] https://lwn.net/Articles/557111/ https://lwn.net/Articles/557111/ [2] https://lwn.net/Articles/557140/ https://lwn.net/Articles/557140/
- abofh 13y agoPID1 also comes with powers over capabilities and (in some cases) cgroups. You can do much of that with FSCaps, etc - but to control the bounding set, you have to be pid1. So - if you want init to be able to limit what processes can do, you will be pid1.
- deleted 13y ago[deleted]
- stormbrew 13y agoI'm not so sure this is entirely true, especially with pid namespaces becoming a real thing. The true pid1 could be greatly simplified for the sake of system stability while providing sub-pid1s that handle actual service, device, and application management.
- adobriyan 13y agoEveryhing in pidns is destroyed when pidns init dies.
- stormbrew 13y agoI'm not sure what you're getting at here. Yes, that is obviously true. As is the case with the true pid1 init. Care to expand?
- adobriyan 13y agoI mean if you protecting yourself from panic by moving stuff from real PID 1 into pidns root, you're doing it wrong. pidns root will segfault and kernel will SIGKILL everything inside which is equivalent to good old panic.
- d0 13y agodaemontools doesn't run as pid 1 and achieves all of this. http://cr.yp.to/daemontools.html http://cr.yp.to/daemontools.html
- FooBarWidget 13y agoIt does not. Not even close. https://news.ycombinator.com/item?id=7210308 https://news.ycombinator.com/item?id=7210308
- Fasebook 13y agoThat comment is insane. Why would log files need journaling? They should be serialized. How is adding a line to a run script "duplicating logic badly"? Coupling is clearly bad, as evidenced by ... 30+ years of software design, but is a necessary evil. I don't see any reason why it's necessary in such a low level system component. "this is not rocket science" you don't impose dependencies on something you want to be reliable. Daemontools is clearly the most mature solution, from a perspective of stability. It's probably why nobody wants to use it, there's nothing to play with or exploit for profit because it already works.
- bitwize 13y agoThat comment is insane. Why would log files need journaling? They should be serialized. systemd-journald provides tampering-attestation features that plain-text logs do not, and cannot, provide. It's fundamentally more secure.
- peterwwillis 13y agoFallacy: having owned the user that writes logs, I cannot fuck with your logs if journaled. Reality: if I owned the user writing logs, I can do anything I want with the logs, no matter how they're stored.
- hdevalence 13y ago
- repsilat 13y agoPeople want systems of components that function as an integrated whole. They do NOT want pieces that are generally unaware of each other (this is touted as the virtue of "loose coupling"). This may be true of "mainstream" users' applications, but is it really true of system software? And should we really attribute the cultural shift toward monolithic systems to shifting preferences rather than leap-first "design"?
- stefantalpalaru 13y ago> systemd has won Not in the Gentoo ecosystem where we have OpenRC: https://en.wikipedia.org/wiki/OpenRC https://en.wikipedia.org/wiki/OpenRC
- nailer 13y agoGentoo is still popular as it's the basis for ChromeOS and CoreOS, but CoreOS uses systemd and I'm not sure re: ChromeOS.
- edwintorok 13y agoAlso Debian is still on sysvinit, and there is a vote being held to decide what init system to use for jessie as default.
- akerl_ 13y agoThat vote has almost total agreement that systemd will be the new init system. At this point, they're stuck in a quagmire of other bureaucratic nonsense and debates over related issues like whether packages will be allowed to require a particular init system.
- asdfaoeu 13y agoEven on systemd that stuff isn't all handled in pid 1. There are 6 systemd service processes running on my machine handling different components. Snipped out the irrelevant processes. % systemd-cgls ├─user.slice │ └─user-1000.slice │ └─user@1000.service │ ├─6612 /usr/lib/systemd/systemd --user │ └─6616 (sd-pam) └─system.slice ├─1 /sbin/init ├─systemd-udevd.service │ └─151 /usr/lib/systemd/systemd-udevd ├─systemd-logind.service │ └─345 /usr/lib/systemd/systemd-logind └─systemd-journald.service └─125 /usr/lib/systemd/systemd-journald
- justincormack 13y agoLinux has always supported userspace diversity, so nothing wins completely. We are at a point where containers are going to change what people want in a Linux distro and not sure that monolithic will win.
- sitkack 13y agoContainerization will make this entire kerfuffle pointless. Running single image big machines with lots of services is a 90s and early 2000s architecture aesthetic that will fade into the background as individual services migrate to a PaaS model for enhanced modularity and mobility. I haven't looked deeply into systemd, but from how the conversation around it is going, it would seem to be solving complexity with more complexity. I'd like to see a mashup of CoreOS plus NixOS integrated with a cluster container management system.
- njharman 13y ago"is a 90s and early 2000s architecture aesthetic" I hope you realize "containers" are so similar (identical compared to "single image big machines") to how mainframes worked in 70's. Just saying nothing is new, cycles are the norm and don't be so high and superior cause your new hotness is gonna be the "old, broken shit" in a couple decades.
- sitkack 13y agoAnd mobile is the new desktop because there is enough computational power there. Soon, we will see containerization on mobile because of too much complexity and not enough security. Containerization has always been a good idea. http://en.wikipedia.org/wiki/FreeBSD_jail http://en.wikipedia.org/wiki/FreeBSD_jail has been around for almost 14 years. I am aware that full system virtualization dates back to the 1960s, in no way do I think that old eq bad.
- justincormack 13y agoCoreOS is of course systemd based...
- asdasf 13y agoThis is precisely it. Linux is not unix. It only vaguely and superficially resembles unix. Those of us who like unix aren't using linux anyways. If you want to use unix, do so. But suggesting linux distros need to be a certain way because unix is that way makes no sense.
- ChuckMcM 13y agoLinux was never UNIX. Influenced yes, but not UNIX. That said, in the FOSS world it is never 'game, set, match' it is 'game, set, fork' :-). For what its worth though, these sorts of debates have happened forever, MOTIF vs CDE, Streams vs Sockets, Signals vs Events, TCP vs OSI, Etc.
- Fasebook 13y agoIf this were true, why would you bother saying it.
- bitwize 13y agoBecause the holdouts in the init wars debate are whiners who are trying to obstruct useful progress being made on the Linux platform, e.g., Ian Jackson.