Now that the dust has settled, why did so many distros fall for this rugpull pump & dump?
 Nothing Ever Happens Shirt $21.68 |
 DMT Has Friends For Me Shirt $21.68 |
Nothing Ever Happens Shirt $21.68 |
Now that the dust has settled, why did so many distros fall for this rugpull pump & dump?
the CIA is just that powerful
It's less work for them. As simple as that really.
What do you mean by "work" here? Forgive my stupid question.
Is init system something that should be tailored specifically to distros?
Also what do you mean by service files? I use Artix OpenRC and I can enable/disable a service just like systemd does.
It varies a little bit, but in general most init systems don't come with much besides the bare minimum you need to boot the system. If you want an actual usable system, you have to write a lot of essential scripts/services for startup (e.g. mounting filesystems, starting udev, etc.). Systemd, on the other hand, comes with everything you need out of the box from upstream itself. Distros didn't need to maintain their own set of startup scripts anymore; they could just use systemd. That's one reason why it's less work.
>Also what do you mean by service files?
A service file is just systemd's format for defining services on the machine (i.e. daemons and shit you run with systemd). All init systems have their own format of some sort.
>Artix
Artix is an unusual case because their developers actually don't mind writing a frickload of scripts all by hand (most distros don't do this). When they started, they borrowed scripts from gentoo (and later void for runit), but later they added more exotic init systems whose scripts are completely handwritten. And later they went back and modified all their openrc scripts as well. In the case of openrc, you are using init scripts that were written by Artix devs. For systemd, it is relatively common for the upstream developer to provide the service file so distros don't even have to write their own (hence, less work). Occasionally, you'll find some handwritten systemd service files though.
This was always the wrong question. Distros had to write their own initscripts before, but not systemd units because the app developers provided them. The distros made the rational choice.
The real question is, why did app developers only start providing service files when systemd happened???
because it's easier, better, more uniform, safer, less error-prone
不名誉なプログラムシステムディー CVE-2012-1174 Delete Any Files コンピューターが破壊された CVE-2015-7510, CVE-2018-15688 Arbitrary State Insertion 状態注入 CVE-2017-9217 Buffer Overflow バッファオーバーフロー CVE-2017-9445 systemd-resolvd Remote Code Execution プログラムをリモートで実行する CVE-2017-15908 Denial of Service サービス拒否 CVE-2017-1000082 0-Day (ゼロデイ) Root Exploit コンピュータを好きなように実行させます CVE-2018-15686 Root Privilege Elevation (10.0 Critical Exploit!!) ルートアカウントの不適切なアクセス CVE-2020-13776 Root Privilege Elevation Again 特権の昇格 CVE-2019-6454 Kernel Panic カーネルパニック CVE-2020-1712 Arbitrary Code Execution 任意のコードの実行 CVE-2021-33910 Stack Exhaustion スタックのスペースが不足しました
cope, call me when your init scripts have syscall filters with a single line.
call me when your stop job finishes
i don't use shit distros that can't configure a service right
But I thought according to
its the app developers that are providing them?
often they aren't. if they were, then systemd wouldn't need to support like five different service models (self forking, self nohup, etc..). Coincidentally, ones that don't provide their own are the ones that usually have fricked up ones made by bad distros.
>10.0 critical exploit
It's 7.8 at most idiot
oh and let's not forget that just this year ANOTHER arbitrary code execution CVE was found, CVE-2022-21944
my fricking sides, systemd is a joke
There is a new CVE in Linux kernel every 2 days on average
t. lennart
116 CVEs in 6 months in Linux Kernel. My bad, it's not every 2 days, it's one every ~1.5 day.
>b.. b-but the kernel!
have a nice day Lennart, nobody wants your shitware
>nobody
tell that to 99% of distributions that hopped to systemd as soon as possible
most people running Linux are running Chrome OS or an Android, neither of which use systemD, because systemd is pure poison for a smooth
experience.
You are not "most people." Don't be so full of yourself. Only 1% of Linux users are still running on non-systemd systems.
I'm sorry but it's more like 0.1% of Linux users run anything OTHER than Chrome OS or Android.
Some statistics: 2.5 biillon Android users worldwide. 50 million Chromebooks sold a year.
That's why when you go out in public, you see lots of people with Androids and Chromebooks, but virtually none running Fedora Core Linux or whatever irrelevancy you run.
Sorry, do you not like being attacked for being in a minority? Now you've got a taste of what you dish out.
>Sorry, do you not like being attacked for being in a minority? Now you've got a taste of what you dish out.
If systemd is only 0.1% of the market, then why are you mad about it?
Also, there could be 100000x more android phones then there are today and it still wouldn't change anything.
I've never seen a Chromebook in the wild
Maybe go outside once in a while
People don't use computers outside. Laptops are just shittier desktops that move from docking station to docking station.
Those aren't GNU/Linux, this is irrelevant.
dangerously based
Now list all the CVEs in every init script across every pre-systemd distro
Are you actually running Android's init on your desktop Linux pc with ubuntu? No? didn't think so
>bash scripts
>CVEs
are you mentally disabled. A CVE in that case would be a CVE in whatever program is being called (or possibly bash itself) not the actual init script.
I don't care where the CVE is filed, you need to list them
I wouldn't want to write sysvinit scripts either tbh
>An init system for an OS.
>Rugpull pump-n-dump.
Do you ever think before you speak?
I wonder who is behind this...
https://www.redhat.com/en/blog/red-hats-decade-of-collaboration-with-government-and-the-open-source-community
Systemd was made by a god of programming himself, you have to be moronic to use anything else in 2022.
Because it's actually better than the alternatives.
It was better at the time because none of the init systems could do asynchronous service bringup. Now it appeals to the sysadmins by providing useful tools and syntax similarity between systems. Other than that, not much.
There was a great need for something like that and the freetards didn't bother to code anything. Frick, all I need is parallelism, dependency resolving, process supervision and logging in one nice package.
But yeah sure, systemd has some massive bloat such as systemd-network and the mounter thingy.
>the freetards didn't bother to code anything
I don't know of you're aware of this, but systemd is free software.
Skarnetis working on making s6-rc a drop-in replacement if anyone wants to know. YWNBAW tho
It's a works program for troons
write the systemd in text, that i can filter you automatically, Black person
Because they maintaining distros, and not parroting baseless FUD on an anime website like a brainless useful idiot.