1 Persons are tagged with #systemd

#systemd

danie10@squeet.me
Danie

The Linux systemd Controversy: A Beginner’s Guide to Understanding the Debate

Linux startup screen showing the text lines as various modules are loading at boot time
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

8 Likes
14 Comments
fla@diaspora-fr.org
Fla

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!

3 Likes
1 Comments
danie10@squeet.me
Danie

How to Create a Systemd Service in Linux

Bild/Foto
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

3 Likes
5 Comments
camelhigh@sysad.org
camelhigh

#linux #rust #systemd #clamav

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!)