no, it's simply because htop doesn't show the kernel as PID 0 like it does on BSDs for some reason
if you boot with init=/bin/bash and run htop, bash and htop will be the only two processes shown
RedHat/GNOME/Freedesktop/systemd/Linux
Thomas Brown
Jeremiah Clark
that can't be 800M, htop doesn't know how to calculate memory usage on *BSD properly
on linux, it would show 200M at most for the same set of processes
Jose Ross
That's a quirk of Linux. All other UNIX likes and real UNIXes have the kernel in PID 0.
Ian Moore
This entire post is ZOG botnet. Don’t trust it
Lucas Brown
oh, look at the (((kike))) (((redhat))) shill attempting to patrol today.
Dominic Sanchez
lmao check it out I even have bloat botnet dbus running
Adrian Martin
You do know there are different methods to determine "used" memory right?
Xavier Watson
lol I'm not surprised
Luis Watson
The only real argument against systemd in my opinion is that it has heavily out played it's welcome and branched into domains that other projects were made to handle.
The "botnet" argument never made sense to me, it being a huge project made in C doesn't mean it's ebil. GNU is a large overblown project made in C that doesn't need to be big and bloated and everyone always sings it's praises.
Linux is a big overblown project made in C with many MANY exploits and bugs, remember that recent one where you could just use tcp to perform a privilege escalation just in the kernel?
For this reason i don't believe gnu/linux was ever made with the intention of following Unix standards/phillosophy. It's main goal from the start has been to rapidly gain functionality by any means possible and has been growing at a extreme rate to beat out windows (something they will only be able to achive with mass marketing at this point)
It's a test bed of many hacked together projects and if something gives them the means to take advantage of or make something faster, then they'll use it no matter what... That's what systemd has become.
It has in a way become the standard for bootprocess and process handling(handshake, w/e) It's what everything interfaces with not because it's good, but it's easy and widespread.. that's the whole point.
The problem with systemd is clear, it has intentionally driven itself deep into the ecosystem and made things hard depend on it specifically, rather then through a layer of abstraction as a true Unix-like/posix system would.
Stop using linux, gnu and systemd all together, their very existance goes counter to Unix/posix.
Use something with actual integrety like BSD, and not a shitty halfbreed BSD like freebsd that attempts to jerk off with Linux.. an actual BSD like openBSD.
Joshua Hernandez
You're confused. The GNU OS exists for its own purpose, it doesn't exist for the purpose of "beating out Windows". The GNU OS exists because before the GNU OS, there was no other OS that was dedicated for the purpose of being completely free software. Its purpose is to be a "full featured general purpose and free operating system". This means implementing features that some users would find useful.
As a free and full featured OS, it's expected that if you want your copy of GNU to function differently, you are expected to modify it to your wishes. If you find there are features you don't need for yourself, then you have to go ahead and remove those features from your copy of GNU.