6 ms·
I thought the big concern is that it isn't hard yet.
by taeric 12y ago
I thought the big concern is that it isn't hard yet.
- Alupis 12y agoit will only get "hard" if software projects bake in hard-dependencies to systemd, like the gnome project has (because they thought/think it provides a lot of benefits, and imho it does). Even so, there are plenty of shims being built that provide the small amount of api compatibility necessary to make things like gnome work on non-systemd systems (FreeBSD for example).
- taeric 12y agoSo, it is going to get hard, is what you are saying? I mean, it could be that the shims are nice and easy, but it seems to be the expectation that this will not be the case, right? Especially since systemd seems to be on a very aggressive expansion of responsibilities campaign.
- Alupis 12y agosystemd is 69 individual components (and binaries) last time I checked. You can opt to build some, or all when you compile it. Yes they work together, but they have an open and now-more-or-less standardized api. So nothing prevents another developer from writing against the api, be it a shim to reduce/remove systemd but provide compatible calls into another system (init, logging, etc), or a complete replacement for a specific component of systemd. I see it only getting easier actually. Folks in the BSD projects for example have their own init system but still want software like gnome, so shims are used to provide the api abstraction. This can be applied elsewhere in the Linux world as well. Again, this is only for software where the developers have explicitly decided to hard-code in dependencies to systemd, which is not likely going to be everyone.
- deong 12y ago> Again, this is only for software where the developers have explicitly decided to hard-code in dependencies to systemd, which is not likely going to be everyone. I'd put good money on this getting harder and harder going forward though. At some point it will be everyone, or at least practically everyone, because every Linux distribution with any mindshare will have been using systemd for years, and hard-coding systemd will be not a lot different than hard-coding calls to the C standard library. Also, shims? How god-awfully inelegant can we be? "You don't like systemd? Cool. You can run something else (as long as it looks, feels, and behaves exactly like systemd)." Look, I'm not a religious zealot. Systemd is what they want me to run; systemd is what I'm running. I can live with ugly software. It's not the end of the world. But oh dear god is it ugly.
- makomk 12y agoI know the systemd developers are now planning on making udev depend on systemd in the near future, and that's pretty essential for desktop/server Linux.
- Alupis 12y agoMaybe not such a large hurdle though. udev was written by Kay mostly and he is on the systemd team. Before udev there was devfsd and hotplug[1], so it's feasible udev could be forked and/or an alternative introduced if it really becomes a burden for distros. [1] http://en.wikipedia.org/wiki/Udev http://en.wikipedia.org/wiki/Udev
- digi_owl 12y agoUdev is already forked, in the form of eudev. And Poettering is already having fun taunting them in systemd release notes, with lines like "This is your wakeup call". Frankly i am reminded of the stuff we would see Jobs pull on stage. Like "Redmond, ready your copying machines"...
- dingaling 12y ago> I thought the big concern is that it isn't hard yet. And once it is a hard dependency then Red Hat will be in control of strategy for the dominant init system. That's what concerns me, not the immediate technical challenges which can overcome. But those who are busy now patching the broken bits won't have influence over the direction of systemd in the future. We'll all go where one billion-dollar enterprise-oriented vendor leads us.
- digi_owl 12y agoThis came to mind: http://arstechnica.com/information-technology/2013/02/linus-torvalds-i-will-not-change-linux-to-deep-throat-microsoft/ http://arstechnica.com/information-technology/2013/02/linus-... The reason is that RH right now is deep in two camps, cloud and military/government contracts. http://www.bizjournals.com/triangle/blog/techflash/2014/09/u-s-department-of-defense-inks-contract-for-up-to.html http://www.bizjournals.com/triangle/blog/techflash/2014/09/u... and systemd has two parts as best i can tell. One part is aimed at cloud via containers and sandboxes (soon to come to desktop as well via Gnome). The other is aimed at securing "seats" via logind. This because the earlier consolekit had a limited reach because it didn't have a partner sitting as pid 1. And the military is after all the origin of the concept "trusted computing". I am not saying that there is a willed conspiracy. But with Red Hat being a for profit organization, anything that bring in the cash in the short run will be given priority...