3 ms·

> . If you still think of systemd as an init system, then your knowledge of it is outdated by at least a couple of years. a couple years ? here's the blog post

> . If you still think of systemd as an init system, then your knowledge of it is outdated by at least a couple of years. a couple years ? here's the blog post from 2011, a decade ago: http://0pointer.de/blog/projects/why.html http://0pointer.de/blog/projects/why.html There's been as much time between now and this blog post, than there has been between this blog post and the introduction of windows fucking XP ! > systemd is in the process of becoming a comprehensive, integrated and modular platform providing everything needed to bootstrap and maintain an operating system's userspace. It includes C rewrites of all basic early boot init scripts that are shipped with the various distributions. > systemd is also a big opportunity for Linux standardization. Since it standardizes many interfaces of the system that previously have been differing on every distribution, on every implementation, adopting it helps to work against the balkanization of the Linux interfaces. Choosing systemd means redefining more closely what the Linux platform is about. This improves the lifes of programmers, users and administrators alike. being more than an init system has been the goal of the project since pretty much the beginning

ryandrake 6y ago
I’m waiting for the day systemd includes a chat and e-mail client. Maybe a built-in version of emacs and a spreadsheet application too.
- benttoothpaste 6y ago
  I can probably live with systemd-emacsd, but once we reach the stage of systemd-electrond, I’ll definitely retire for good.
- marcosdumay 6y ago
  While they are at it, we could use some new take on Bash too, Dash doesn't break enough scripts to fill HN threads. And some new find, cp and ls with mostly the same options, but some having the same names of the GNU ones but that overwrite data at random. And I'm eager to discover what the systemd folks can do in a remake of tar!
jeroenhd 6y ago
I was trying to be conservative because I've only really dealt with systemd since about 2016, but damn, nearly a decade of systemd and people still fight systemd vs systemV like it's 2011. I'm not against systemd myself, to be clear. I think putting services like these into modules of the systemd environment makes sense, and as long as you can disable them if you don't want them, that's perfectly fine. I've had to disable one of them on one of my servers because _something_ was going wrong preventing resolved from caching repeated DNS responses, causing a huge load when a script started scraping a particular domain without any clear indication as to why in the logs. As long as I can do that, I'm perfectly fine with whatever the systemd folks want to integrate next!

ryandrake 6y ago

I’m waiting for the day systemd includes a chat and e-mail client. Maybe a built-in version of emacs and a spreadsheet application too.

benttoothpaste 6y ago
I can probably live with systemd-emacsd, but once we reach the stage of systemd-electrond, I’ll definitely retire for good.
marcosdumay 6y ago
While they are at it, we could use some new take on Bash too, Dash doesn't break enough scripts to fill HN threads. And some new find, cp and ls with mostly the same options, but some having the same names of the GNU ones but that overwrite data at random. And I'm eager to discover what the systemd folks can do in a remake of tar!

jeroenhd 6y ago

I was trying to be conservative because I've only really dealt with systemd since about 2016, but damn, nearly a decade of systemd and people still fight systemd vs systemV like it's 2011. I'm not against systemd myself, to be clear. I think putting services like these into modules of the systemd environment makes sense, and as long as you can disable them if you don't want them, that's perfectly fine. I've had to disable one of them on one of my servers because _something_ was going wrong preventing resolved from caching repeated DNS responses, causing a huge load when a script started scraping a particular domain without any clear indication as to why in the logs. As long as I can do that, I'm perfectly fine with whatever the systemd folks want to integrate next!