3 ms·
Wasn't it? Multics was the modular system, Unix was the one where they said "That's silly, let's stick everything in a single kernel and not bother with all the
by geofft 11y ago
Wasn't it? Multics was the modular system, Unix was the one where they said "That's silly, let's stick everything in a single kernel and not bother with all the flexibility because we don't need it."
People seem to ignore the kernel for some reason, but it is literally one giant program to rule them all, and it works very well. There have been many efforts to modularize it and move most of the complexity into independent units, and none have particularly worked out.
- cfallin 11y agoThe thing is that the kernel, while large, has one defined purpose -- to provide abstractions of hardware resources and arbitrate those resources between programs -- and thus conceptual simplicity, even if the source tree is huge. The POSIX syscall API is simple and the rest is just implementation. In contrast, systemd is conceptually complex -- its scope continues to expand to manage every little nook and cranny and configurable tidbit in the system. (I'm not arguing one way or another, just pointing out that the type of complexity is different.)
- chris_wot 11y agoReally? How is it complex conceptually? The main concepts you really need to understand is that of units, and for that I found a very well written piece by Digital Ocean on the topic: https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files https://www.digitalocean.com/community/tutorials/understandi... Aside from that, there are a number of services and utilities, but I'm not sure how they are conceptually harder to understand that any other similar program or utility on Linux...
- cfallin 11y agoThe core of systemd revolves around units, but the "systemd ecosystem" has expanded to logging (journalctl), bus management, a new way to set the hostname (hostnamectl), a login manager, fstab parsing and disk management, a new session/login management framework, networking (systemd-netword, or is it netctl now, or do people use NetworkManager? I'm on Arch and ended up choosing netctl but I still don't understand all the tradeoffs), and I'm probably missing something. Don't get me wrong -- I actually like some of the new thinking, appreciate parallelized bootups, and think service units are cleaner than the old /etc/rc.d mudball. I'd rather have things Just Work(tm) than play with wpa_supplicant and hibernate configurations on my laptop. But it's been a lot of new stuff to learn for someone used to the Old Ways, and it's kind of astonishing how fast systemd pieces have taken over different domains.
- chris_wot 11y agoYeah, it can make my head spin too sometimes. But I just don't think that rapid change makes things more inherently complex for a system per se, it just means folks like us have to do more reading (and more grousing, I quite enjoy doing that on occasion, I must admit). Oh boy, I've just realised - I'm growing older! Eep.
- bitwize 11y agowpa_supplicant Just Works. NetworkManager is more like NightmareManager.
- marcosdumay 11y agoModules worked. Fuse worked. DRI worked. In kernel space, the global lock is gone, there is a central API that everybody else uses with code that mostly don't touch each other. Linux is very modular. It is just not a microkernel, and that is probably more due to historical performance bottlenecks than to architectural concerns.
- chris_wot 11y agoIt occurs to me that there is quite a bit of confusion around the terms "monolithic", "microkernel" and "modularity". The misconception is that a monolithic kernel isn't modular, which is very far from the truth.
- geofft 11y agoModules are so closely tied to the base kernel that they require recompilation for about every stable release and code changes for about every actual release. Almost nobody uses FUSE in production. DRI sorta works, but it's so closely tied to the kernel that people have loud objections to out-of-tree non-GPL modules using even bits of it. Linux is pretty modular as an engineering project, in that there are ways for developers of one part of the code not to need to care about all the rest of it. But in the sense that systemd gets criticized for not being modular, Linux is also not modular. It is technically possible to implement either systemd's or Linux's APIs faithfully enough for things written to those APIs to work with your alternative implementation. systemd gets criticized because doing this is difficult in practice; it's far more difficult with Linux.