>sytemd is bloated and shit, ok, but MUH BOOT TIMES!!11
Well... youtube.com
Install Gentoo.
Sytemd is bloated and shit, ok, but MUH BOOT TIMES!!11
Jeremiah Kelly
Christopher Perry
Why girls are so dumb?g
Gentoo is a meme, though.
Brandon Kelly
Gentooniggers are really desperate
Startup finished in 1.767s (kernel) + 1.750s (userspace) = 3.518s
graphical.target reached after 909ms in userspace
Jonathan Thompson
Just suspend your box freetards
Nolan Morris
Christian Smith
>having a Unix or Unix-like OS
>powering it off ever
i shiggy diggy
Samuel Robinson
i need me some sauce
Jose Adams
you can make it even faster by disabling every process that's garbage and launching them at user space after you login in, basically while your DE loads the background process have enough time to load to.
Brandon Miller
Poettring shills BTFO.
Aiden Thomas
Just RC_PARALLEL that shit
Mason Hill
I don't get this faggotry. tried open-rc and it JUST WERKS. systemd being faster is a meme.
Angel Bell
It's FUD over and over.
99% of Linux users will probably never need to write an init script themselves. The default init system should be small and simple.
Leave systemd to sysadmins who actually understand its pros and cons, and need to exploit every feature.
Cameron Wilson
systemd just werks as well, so I don't care either
Samuel Jones
But comes with additional bloat you'll never use, not to mention way more security issues.
Xavier Taylor
> them binary logs my niggers
reeks of a co-ordinated attempt to obfuscate shit so bad that it drives people away from shit distros
Justin Green
The justifications they give for them are amazing, too.
>"with binary logs, you can verify they weren't modified!"
>what are fucking hashes
Ayden Mitchell
me on the right
Michael Fisher
Nice thighs, user.
Jack Ward
literally just google reverse image search
Gabriel Rivera
>>what are fucking hashes
not saying its a valid excuse but isn't there in theory intentional hash collision?
Jace Gomez
Technically, there *is* a tiny chance of collisions, but most widely used hash algorithms have the so called "avalanche property", which means that a small change in the input (such as a single character) will usually produce a huge change in the output (usually, a completely different result). Therefore, should plaintext logs get modified by hand, the hash value is nearly guaranteed to be totally different. This means that, in practice, plain text logs are no harder to authenticate than binary logs.
Not to mention that, since the de-serialization algorithm of systemd's binary logs is known, there is nothing preventing someone from de-serializing those logs, modifying them and re-serializing them again in place of the original ones. This means that binary logs should be authenticated in some way anyway, which defies the "easier to verify" excuse of binary logs.
Nathan Robinson
Implying Linux waking up from suspend is something that happens. Uptime threads are a cope.
Nathan Thompson
>ywn be molested by two onee-sans with big milkers