Anti-systemd fags btfo

youtu.be/o_AIw9bGogo

This guy is a real coder unlike most of Jow Forums and is a freeBSD dev.

During 40min he demonstrates that systemD is actually a piece of art and destroys EVERY anti-systemd argument.

So what's your reason not to embrace the D ?

Attached: IMG_20181208_162511.jpg (4608x2304, 3.74M)

Other urls found in this thread:

judecnelson.blogspot.com/2014/09/systemd-biggest-fallacies.html
twitter.com/NSFWRedditImage

This is also a work of art, but that doesn't mean it's any good, and it certainly doesn't mean it should be used by everyone.

Attached: 689px-Marcel_Duchamp,_1917,_Fountain,_photograph_by_Alfred_Stieglitz.jpg (689x899, 112K)

i launch my services inside .xinitrc
Works fine
I would disable most of the systemd features bug i cant, they are all hard coded.

You trust the guy that CoC'd FreeBSD?

As said in the presentation : every software has bugs
He might be cucked but at least he can code unlike you

I don't want to deal with journald

he only pointed out that Unix service management has already changed over time and that some services (the cancerous ones) may benefit from more change

its a typo idiots, i meant to say but

My bad I tried to infer what you meant

Why's that? journald seems to try to get out of your way a fair bit.

It's (probably) the biggest piece of shit in systemd.

very constructive reason, thank you

Could you elaborate why ?

He develops FreeBSD but feels compelled to post a 40 minute blog about systemd?

Yeah I won't be watching it.

Developping on FreeBSD doesn't mean one should go full austismo and not look what others do

You demonstrate the marvelous openmindness of anti-systemd fags

>mounts your efi rw
>rm -rf / --no-preserve-root
heh, nothin personnel kid

Yes actually.The design is done in a way that all logging from the system needs to pass through it and it cannot be disabled.
This leads to massive performance problems because if you've got a lot of services or just a spammy process, it's going to use up a lot of CPU time just to service them. Especially since there's only one journal file that it writes to.
The binary log format serves no purpose as far as I can tell, except to make logs less accessible through tools. It's been known to corrupt itself and become unreadable.

>freeBSD dev
*hugs*

I would recommand you to watch the video at 34:00

>OLD BAD
>NEW GOOD

Attached: ea9e130fd86e9e23394611f337bceea4--sad-anime-girl-manga-girl.jpg (700x988, 78K)

>You demonstrate the marvelous openmindness of anti-systemd fags

I'm not ashamed to admit that I don't give a rats ass about some random BSD dev's fucking literal blog post. I already know anti systemd faggots are idiots without some commie dipshits bipartisan blurb.

systemd is based, anti-systemd fags mindlessly rehearse what others say.
[Unit]
Description=My Service
After=my-other.service
[Service]
ExecStart=/usr/bin/scriptfags-btfo
[Install]
WantedBy=multi-user.target
scriptfags on suicide watch

Attached: serveimage (3).jpg (225x225, 7K)

I've watched the video before.
>Binary logging is not a bad thing, as long as you have the tools to pry them apart.
Opinion discarded, because there's one tool that's not particularly good. It will usually die if there's one byte wrong in the log file's metadata.
>Append only logging.
The default on every *nix system?
>Easily shipped logs
Hasn't this been easily done with existing tools for decades?

Nobody denies that systemd is useful, it's the implementation which is bad. Millions of lines of horrific quality C, running as PID 1. It's a massive vulnerability,

>feels the need to "correct" himself when he makes a grandfather joke by changing it to grandmother
Closed the video right there.

Let me guess, he only compares systemd to the ancient sysv init like any other systemd shills.

sorry not watching it. the systemd shills don't get that I actually have a choice not to use it. openrc works just fine and I don't feel comfortable using an init with the most shit surronding it and the most bugs

he also mentions openrc and upstart

You don't have to use it, buy why stay ignorant about why it was made and the design decisions?

>[spoiler]imagine liking something and having to convince others that its THE BEST all the time[/spoiler]

you must be exhausted OP

Thing is most people have a very manichaean vision of things so to appeal them I need to dumb down ideas. Seeing this video might make them think and develop a more nuanced opinion about systemd among other things.

I mean if you watch the video the bottom line is that systemd is not that great but we have nothing better yet

Its not good though. I also think seeking reassurance (clearly evident by your comments) for your choices like this means you've experienced cons to this that you're trying to diminish.

>in regards to the constant bugs....
>all software has bugs xD
why did I even bother to watch shit from someone that looks like an obvious pedophile

That's pure ad hominem. I would recommand you to find argument against systemD instead

>ponytail feminist tells me to install botnet

Attached: choerrysmile.jpg (400x400, 32K)

I don't need to you're presenting enough by yourself to paint a negative picture. Someone doesn't like it, see it the way you do, why does it weigh so heavily on you.

I have no issue what so ever with people not using systemd.

The thread comments show otherwise.

Why do you think this video is a valid argument? He's just saying this thing that appears closer to what I'm used to seems familiar. Which its comforting.

Binary logs that seem to be randomly corrupted

Someone send him this:
judecnelson.blogspot.com/2014/09/systemd-biggest-fallacies.html

dont get me started

erm this is the "him" to which you referr

Attached: I eat rat shit.jpg (220x391, 19K)

cute trip and good post

ya

Attached: nothing_to_see.png (764x131, 15K)

anything is better than shell scripts

Systemd is useful, and needed. The problem is that it was written by a bunch of wankers who, having ignored the last 40 years of lowlevel software development in C, are constantly rediscovering it in the worst posaible ways.
Redhat should have hired people who knew their stuff, instead of the caitiffs they put on the case