If you’ve ever navigated any form of forum or online community focused on #Linux, you probably saw someone mentioning #SystemD as either an advantage, or, more likely, a problem. While it’s used by virtually every major Linux distro, it seems like there’s a strong core of people who dislike this system,so I thought I’d give a look at what systemd is, and at why some people seem to really hate it:
I’m thinking that I might install the latest #Devuan in its place and skip religiously-inspired choices like replacing proven DNS clients with one that is integrated into the ever-famished, all-devouring System Daemon.
Interact with end users on technical problems. Tier 1, 2 and 3 support for #CentOS and related open source products. Drive resolution of those problems, which include: Open source software issues. Questions around open source software usage. Questions around use and best practices. Review of the architecture and design where software is implemented. Conduct professional services and training engagements. Research, understand, and advocate open source software. Interact with various open source communities. Drive early resolution of issues. Make strategic contributions to the CentOS core and surrounding ecosystem, provide bug fixes ahead of the community where needed Be a part of the on-call rotation. Present knowledge via articles, blogs, and conference presentations.
Requirements:
Technical knowledge, skills and expertise in complex infrastructure, web-based software and enterprise software Strong knowledge of the Linux #kernel and system architecture. Understanding of software best practices; #SDLC, #SCM and #Agile development principles. Ability to develop with #C / #C++ in a UNIX environment. Utilization of common #Linux C/C++ build tools such as #gcc. Solid understanding of CentOS 6.x and 7.x and included frameworks like #firewalld, #systemd, etc. Strong #RHEL/CentOS background required #Debian / #Ubuntu, #SUSE / #openSUSE / #SLES, other distro background a bonus C, shell scripting, #perl, etc Virtual Machine experience with #qemu / #kvm, #Azure, #AWS, #VirtualBox, #Vagrant General experience such as: radius/Kerberos, lda, ipa/idm, monitoring, vpn, containers, centralized systems management, automation (ansible, chef, puppet, etc), version control (git, etc) or security hardening (CIS, STIGS, PCI-DSS, etc) Excellent written, verbal, and presentation skills Knowledge of open source packages Database administration; #postgresql / #mysql / #mariadb experience very desirable Experience with Linux distro package building (#rpm, #deb, #ipkg, etc) preferred Existing contributions to the CentOS community a major plus
@geniusmusing That one sounds promising. I might try it out soon.
Also, are you aware of any #Red-Hat derivatives that are #SystemD free? Or are such distributions only available in #Debian and #Gentoo families of Linux distros?
Alfheim Linux ALOBE Antergos ArchBox ArchEX ArchLabs Arch Linux 32 Arch Linux ARM ArchStrike Arch XFerience Artix Linux Astian OS Audiophile Linux BBQLinux BlackArch Linux Bluestar Linux Chakra Condres OS Ctlos Linux DidJiX Hyperbola KaOS LinHES MagpieOS Manjaro Linux MorpheusArch MSYS2 Namib Netrunner Rolling Ninja OS Obarun PacBSD Parabola PuppyRus-A RaspArch Revenge OS Sonar TalkingArch TeLiSc OS UBOS Velt OS
Don't like #systemd? Want to avoid #FreeBSD/#OpenBSD and commercial OS?
Fork your own distro. Seriously.
Every successful Linux distribution started with some person deciding to fork. That person invested time or money in community, and built their distro into success.
Red Hat is not magic. They've just been at this a long time.
If you do fork a non-systemd Linux based on my recommendation--if I've inspired you--feel free to call it Lucix.
@guy@gnusocial.no My main concern with #systemd is the complexity. Yes, startup scripts may be shorter and easier to read, but putting so much functionality in one component seems like a poor choice for an OS designed around the philosophy of "Do only one thing, and do it well". That said, I've never had a problem on any of my computers attributable to systemd (I have !Debian and !Ubuntu servers and desktops, and one !Devuan box I'm trying out).
I'm not sure !Devuan yet has the legendary stability of !Debian, nor a full suite of non- #SystemD applications in its repositories. But I'll be working my computers over to Devuan when it's a good fit.
@hobbsc I believe @munin comes from a security orientation: PID 1 should do very few things: start your system, launch processes, kill processes, shut down your system, and a couple of others. Systemd is just too invasive for that role.
I'm personally uncomfortable with this, and with the way it suddenly conquered nearly every distro. I'm not otherwise against it, but I do intend to swap the family's VPS fleet to Devuan instead of Debian (have not found a non-systemd replacement for CentOS yet) pending consultation with the kids.
OTOH, whenever I've had #systemd on a computer or VPS from the beginning, I haven't had much of a problem. Switching from #sysvinit ("upgrades" by the distro), however has always failed, requiring a from-scratch reinstall to make the computer operational again.