#systemd
if #wayland had been called #X12, lol. (heard on https://www.youtube.com/watch?v=vEjsRil0jJ8 )
and so... if #systemd had been called #sysv6 to supercede #sysv5 ...
and if #pulseaudio had been called #alsa2 of #jack whatever,
#adoption [, #onboarding ] would have slipstreamed? n_n X3
... or... maybe that sounds like #embraceextendextinguish and shouldnt give monopolists and their usurper agents ideas. ;p
The Linux systemd Controversy: A Beginnerβs Guide to Understanding the Debate
In the world of Linux, few debates have stirred as much controversy as the battle between the traditional System V init system, often known as SysVinit, and the newer systemd.
systemd is a system and service manager, first introduced in 2010 to replace the traditional System V init system. It was designed to improve boot-up speeds and manage system services more efficiently. Today, systemd is the default init system for many popular Linux distributions, including Ubuntu, Fedora, and Red Hat Enterprise Linux. Despite the name, systemd is not a daemon. Instead, itβs a software suite that provides a number of system components for Linux. Its goal: to standardize service configuration and behavior across Linux distributions.
Personally, I have no preference at all. Itβs there, and I use it sometimes when I need to change or troubleshoot something. My take on it really is that Linux has many options and therefore there will always be differences of opinion, just like we also have for all the βbestβ Linux distros. When do you ever hear Windows users passionately debating for or against the Yellow and Blue version of Windows? You donβt, because they donβt have those options. And for macOS, of course, Steve knows bestβ¦
I think most newer Linux users have not really experienced the pre-systemd era, and also probably donβt delve much into where systemd is actually changed much. With modern Linux there is less and less reason to delve down into systemd unless you are in the habit of experimenting, learning, pulling things apart. But sometimes the topic flares up, so it is interesting to hear a bit about what and why.
See https://itsfoss.com/systemd-init/
#Blog, #linux, #systemd, #technology
#Redhat is doing another #systemD and doubling down on #Walyand by dropping #LibreOffice, because apparently editing images is more important than editing documents. #mywayorthehighway #debian is sure to follow again
https://lwn.net/Articles/933525/
https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277
Systemd-Entwickler arbeiten an Soft-Reboot
https://linuxnews.de/systemd-entwickler-arbeiten-an-soft-reboot/
#systemd #Linux #LinuxNews
I have to say that even if it does not bring many new features, I'm quite excited about the fact that #UbuntuTouch is now based on 20.04 and not 16.04. Sure, 20.04 still is old but it should now be much easier to change the base version now that the switch to #systemd is done. I already saw a phone running on 23.04 beta!
How to Create a Systemd Service in Linux
Systemd is a modern software suite that provides many components on a Linux system including a system and service manager. It is compatible with SysV and LSB init scripts and works as a replacement for sysvinit.
For easier management, units are categorized into several types: target, service, socket, device, mount, automount, swap, path, timer, snapshot, slice, scope, and busname.
A systemd service is defined in a unit file (a unit is a representation of a service and system resources such as devices, sockets, mount points, etc.). Custom service unit files should be stored in the /etc/systemd/system/ directory and must have an .service extension. For example, a custom test-app service uses /etc/systemd/system/test-app.service unit file.
A unit file is a plain text ini-style file that usually includes three common sections. The first section is usually the Unit section which carries generic information about the unit that is not dependent on the type of unit.
The next section is the unit type section, for a service, it is a Service section. And the final section is the Install section which carries installation information for the unit.
In this guide (linked below), they show how to create a new systemd service and manage the service using the systemctl command, in Linux. It is one of the more concise and easier-to-read guides that I have seen.
See https://www.tecmint.com/create-systemd-service-linux/
#Blog, #linux, #opensource, #systemd, #technology
systemd-analyze security
#systemd bietet mittlerweile interessante MΓΆglichkeiten fΓΌr die Optimierung der systemseitigen #it-security:
systemd-analyze security
Bislang konnte ich noch keine Probleme feststellen.
#GNU/Linux #sandboxing
systemd service sandboxing and security hardening 101 #systemd
As for the other OS, the culprit was clamav. Fortunately, they also provide clamav-lts, which doesn't need Rust to build, so I'm changing over to that.
And I've been messing around with SMT settings in my BIOS, thinking that was to blame. (I had it disabled on my last MB but it was enabled here so I disabled it for comparison. It made my CPU load look half as big, but of course that was just because I had twice as many virtual cores, so the monitor thought I was using less of the imagined double capacity!)
I have just discovered what a threat to Free software Rust is. It makes systemd look trivial.
I have come across its tentacles on another OS, where I have an automated build program which can build 144/145 packages in under half an hour, but one of them is written in Rust, so Rust must be built first, and rust takes over three hours. This will make maintenance of repos unmanageable if programs like that are allowed into the ecosystem. Free Software builders just won't be able to cope.
Clamav is the latest culprit. I have that on my mail servers to provide protection to my Windows-using clients, but I need to find an alternative fast now it's written in Rust.
Systemd supremo Lennart Poettering leaves Red Hat for Microsoft
To considerable amusement in the Linux community, the infamous lead developer of systemd has a new job β at Microsoft.
The news surfaced on a Fedora mailing list when someone found that they were unable to tag Poettering in a bug report because his Red Hat Bugzilla account was disabled, to which Poettering responded that he had created a personal account.
This has caused much merriment in comment threads on sites such as Phoronix, Hacker News, and Slashdot, from "Welcome home, Agent Poettering!" to "Good work!" to various quips about future combined Linux-plus-Windows operating systems.
Although near universally adopted in almost every mainstream Linux distribution, systemd remains highly controversial, as The Reg has covered at considerable length. Despite all the furor, systemd is merely one example of a trend towards richer systems-management tools on modern xNix systems, such as SMF in Solaris and its various open-source descendants or Apple's launchd. ...
From about a week ago, though I'd missed it at the time.
This has resonance for those engaged in the Linux community. I've long been strongly leery of systemd, in roughly equal parts based on its design, on Poettering's own exceptionally abrasive personality and disregard for valid technical complaints, and a remarkably (and unpleasantly) fanboi-ish cult which grew up around the system. It's all but entirely dominated Linux distributions, including Debian, which has considerably cooled my own enthusiasm (for both Linux and Debian) over the past few years.
https://www.theregister.com/2022/07/07/lennart_poettering_red_hat_microsoft/
Systemd Creator Lands At Microsoft
Yesterday's surprise was that Lennart Poettering quietly had left Red Hat following a decade and a half there leading PulseAudio among other projects and ultimately going on to start systemd that has fundamentally reshaped modern Linux distributions. It turns out he had joined Microsoft and continuing his work on systemd.
https://www.phoronix.com/scan.php?page=news_item&px=Systemd-Creator-Microsoft
So, the much-hated creator of the much-hated systemd joins the much-hated company Microsoft. How fitting.
"When you install a Linux system its just a bunch of RPM or DEB packages. For example of you install CentOS 7.8 Minimal variant you end up with several hundred RPM packages installed. After a week or month many of these packages will get updates sometimes making this CentOS system unusable or even unbootable (recent GRUB Boothole problem for example). On the contrary FreeBSD comes with a Base System concept. This means that when you install FreeBSD you install a minimal system as a whole. No packages or subsystems to be separately updated. Just whole Base System. That means that /boot /bin /sbin /usr /etc /lib /libexec /rescue directories are untouchable by any packages. When you decide to install packages (or build them using FreeBSD Ports) they will all fall into the /usr/local prefix. That means /usr/local/etc for configuration. The /usr/local/bin and /usr/local/sbin directories for binaries. The /usr/local/lib and /usr/local/libexec for libraries and so on. The FreeBSD Base System kernel modules are kept in the same dir along with the kernel in the /boot/kernel directory. To make things tidy all kernel modules that are provided by packages go into the /boot/modules dir. Everything has its place and its separated."
All this quickly became lost when #systemD from #Redhat aggressively took over...
LOL... " #systemd Native Integration"... is, ermmmmm... is that a feature? https://www.suse.com/c/handover-for-the-next-round-sap-on-suse-cluster-and-systemd-native-integration/
2021 hardcore list of linux distributions without #elogind and other #systemd parts ... Edited: February 28h 2022 (replacing older strict list) https://sysdfree.wordpress.com/2022/02/28/333/ #gnu #linux
#ibm #redhat is all about #systemd and nothing else exists or is being considered https://www.redhat.com/sysadmin/how-to-configure-firewalld
