Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Did ArchLinux Embrace Systemd? (2016)

reddit.com

Post reply on HN
Print view View original

131–132 of 132 posts

Re: Why Did ArchLinux Embrace Systemd? (2016)

#131

Post by Redoubts »

qtplatypus wrote: post #124
Redoubts wrote: post #114

Earlier quoted context omitted.

Could you elaborate more? My use case is very similar between the two, and I don't mean workstation operation.

I'm thinking that Linux is primarily a server OS and MacOS is primarily a workstation. And yes people do use Linux on the desktop and visa versa.

> I'm thinking that Linux is primarily a server OS and MacOS is primarily a workstation.

Good for you.

> And yes people do use Linux on the desktop

Good for them.

But the fact remains that this post still ignores why binary logs are bad for the server use case. They seem great for me in that role.

Re: Why Did ArchLinux Embrace Systemd? (2016)

#132

Post by School-Cotton »

Someone wrote: post #107
geggam wrote: post #58

Earlier quoted context omitted.

You know, everyone says this but every server I worked on (several thousands) which used sysvinit I cant remember any issues with startups that couldn't easily be scripted around. I still dont understand what issues are fixed with systemd and I am aware of many it has created.

I am not convinced every sysadmin could ‘easily’ script around init issues on the servers they manage, but I’ll give you that. The real issue isn’t with servers, it’s with desktop systems and laptops. When users plug in a USB sound card or plug their laptop into a dock, they don’t want to (and likely couldn’t) “easily script around” that; they expect an audio device, network connection, video card to be created witho…

Desktops and laptops are a tiny and insignificant minority of Linux installations, and almost completely related to why Linux is popular and important.
Post reply on HN