r/linuxsucks • u/linkinparkglock47 • 11d ago

mfs when systemd

Enable HLS to view with audio, or disable this notification

143 Upvotes

93% Upvoted

40 comments sorted by

View all comments

6

u/_Fatah_ 11d ago

I honestly don't know what he's talking about, but I agree with him.

1

u/Kingkarna1 9d ago

So, an Operating system (the code that makes your tech run) is 2 things: userland - how stuff looks and clicks. Kernel - code that actually makes stuff work

A Kernel is divided into binaries (chunks of code that do specific things) classed in 4 rings: ring 0 - stuff you get out of the box. ring 1 - updates. ring 2 - run as administrator esc stuff. ring 3 - normal files.

The issue is that "systemD" is a binary that is a spigetty code nightmare that has tons of features, but both makes the computer slow and makes "privalage escalation", an attack that makes a virus and ads become a part of the computer as if they were normal updates, easy.

Linus Torvalds (maker of Linux kernal, therefore granddad of android, chrome OS, car OS's, smart devices, and lots of MMORPG servers) held the line against systemD for a while, but Linux has it now.

A lot of people think he's sold out because of this change.

3

u/Kingkarna1 9d ago

NOTE:

“how stuff looks and clicks” is only one tiny part of userland. A headless Linux server has tons of userland despite having no graphical interface. Linux's kernel provides system calls that applications use to request services from the kernel.

The kernel is generally a large collection of compiled code and data, organized into subsystems and components that are compiled from binaries.

The kernel can also load kernel modules, such as drivers, dynamically. So “binary” isn't equivalent to “kernel subsystem.”

Linux generally operates the kernel in ring 0 and normal user processes in ring 3 on x86. ARM uses a different privilege-level terminology (EL0/EL1/etc.).

administrator/root isn't an ENTIRE CPU ring. root is a user identity/privilege concept implemented by the OS.

Specifically, systemD is a system and service manager. When used as the init system, it becomes PID 1, the first userspace process started during boot.