Lennart Shills BTFO

youtube.com/watch?v=GNUGjFzenq4

SystemD(ick) is a botnet.
Free yourselves with a distro that respects
your freedom like Void or Gentoo.

We are going to make GNU/Linux great again.
We are going to ban gnome packages from entering our repos.
We are going to stop SystemD from crossing the RedHat border illegally into our distros.
We are going to build a wall across the RedHat border and Lennart is going to pay for it!
WE ARE GOING TO MAKE GNU/LINUX GREAT AGAIN!
And you Better believe it!
You are gonna be so proud of GNU/Linux because we're going to turn it around.
We're going to start winning
again we're gonna win so much we're gonna win at every level.
We're going to win with program support.
We're going to win with market share.
We're going to win with hardware compatibility.
We're gonna win with every single facet.
We're gonna win so much, you may even get tired of winning.
You’re going to say, ‘Please user, I have a headache. Please, don't win so much. This is getting terrible.’
And I'm going to say, ‘No, we have to make GNU/Linux great again.’
You're gonna say, ‘Please.’
I said, ‘Nope, nope. We're gonna keep winning.’
Make GNU/Linux great again!
Thank you everybody.

Other urls found in this thread:

without-systemd.org/wiki/index.php/Arguments_against_systemd
youtube.com/watch?v=GNUGjFzenq4
agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
github.com/systemd/systemd/issues/4234
plus.google.com/ LennartPoetteringTheOneAndOnly/posts/g1E6AxVKtyc
lists.freedesktop.org/archives/systemd-devel/2013-March/010062.html
0pointer.de/public/gnomeasia2014.pdf
comments.gmane.org/gmane.comp.sysutils.systemd.devel/9925
ewontfix.com/14/
youtube.com/watch?v=pxHUevaC2Zk
bugs.chromium.org/p/chromium/issues/detail?id=583671#c52
forums.debian.net/viewtopic.php?f=20&t=120652&p=570371
without-systemd.org/wiki/index.php/Main_Page
twitter.com/SFWRedditVideos

>shilling your own video

Systemd just works. It's robust and widely supported.

without-systemd.org/wiki/index.php/Arguments_against_systemd
Absurd Bugs and Responses section.

If it ain't broke, don't fix it. Init.d works fine even to this day, the only problem is that everyone abandoned it because it was "old". The linux kernel is 25 years old, yet no one abandons it because it is still getting updated regularly.

Sorry user, legacy init scripts are deprecated. Those 25 y/o scipts are really inefficient.

Just think about setting host name during boot process. Init would for a seperate process look for a bash script, execute the script, set the hostname back and the whole boot process resumes.

Systemd just replaces that with a couple of lines of fast C code.

This is professional development user

Not my video. But how can I prove it? What is asserted without evidence can be dismissed without evidence.

>What is asserted without evidence can be dismissed without evidence.
Just like your claim of systemd being an NSA botnet?
Great

Also, it's pretty amazing when you start researching the actual systemd technology. Redhat took what was good of Launchd, made it simple and cleverer and implemented it.

Socket activation is really amazing. You can also perform D-Bus activation in parallel.

Clever

Further more BSD style init scritps absolutely sucks, non-intuitive and inefficient.

I suggest you start studying, OP

for all of our sake, get back on your fucking medication

Well, that's what happens when Linux overtakes so much market share. They need to keep you in the botnet somehow. Don't let the fact that you are using open source software fool you into thinking you are free of the botnet.

Do you think it's a coincidence that the rapid SystemD adoption and the new super aggressive telemetry policies in Windows happened around the same time? They were just catching up with Apple in terms of spying their users.

That's it, I'm removing systemd from my life.

Just removed it from my Jessie install.

Feels good man.

You are wrong. PERIOD

guixsd

One universal OS, one global government... I don't where this is going.

Is this guy for fucking real?

>I just added a new module to systemd git, “libc”, and you are probably
wondering what that is about. Here’s a quick overview over what this is
and our plans with it.

>We figured to complete the systemd project we were still lacking an
email program[1]. In order to get this off the ground quickly we noticed
we’d need a libc first. We had the option of either merging glibc into
systemd, or write a new C library. Of course, we are pretty good at
rewriting existing programs (we are simply faster doing that, since we
don’t have to read so much code), so we opted for the latter. The new
module ‘libc’ is the result.

>Technically, this move makes perfectly sense, too. We are sick of
supporting unstable glibc APIs and ABIs, and we believe that we greatly
benefit from the fact that we now finally have everything the OS
userspace consists of in one single repository.

>Of course, this new libc is not available to Ubuntu and other Linux
distributions that have not yet adopted systemd. However, after
deliberately choosing a home-grown display server (Wayland) over the
generally accepted one (Mir) we decided creating an incompatible libc
would be the best approach to create a strong platform following a
strict release cadence.

I know it sounds like satire, but it's for real.

So... don't use it? Why are these threads necessary?

This is actually what makes SystemDicks hard.

systemd is supposed to be a standard system base, those are things that every system uses so it's not absurd at all, also they are completely optional.

Someone got triggered.

That's a joke email from Lennart you fucking mouth breathers.

lists.freedesktop.org/archives/systemd-devel/2013-March/010062.html

That doesn't look like a joke you piece of shit.

>Further more BSD style init scritps absolutely sucks, non-intuitive and inefficient.
Hi Lennart. You're wrong as always, BSD style init scripts are objectively superior to anything you faggots design.

It was an April fools joke you retard. comments.gmane.org/gmane.comp.sysutils.systemd.devel/9925

>For the sake of the archives, and since this apparently wasn't obvious
>to everybody: this was our attempt to being funny on April 1st.

>There is no truth in the original mail.

>Lennart

>mouth breathers
Hi SRS

Not an argument.

Except that if you look at the original link you posted, the date isn't April 1st. He's just saving face.

Keep sucking Potterin's dick.

Wow, anti-systemd shills grasping at straws at this point!

>March 31
>what are timezones

Did you even read the mailing list? You people are really fucking dumb.

gimme that photo systemd made of isis flag

They probably though it was real. If they can't read a man page they probably can't read a mailing list.

systemd is literally the best thing that's ever happened to open source, no wonder you have to be dumb to oppose it.

To inform the people their systems are being compromised.

But you would be okay with this, wouldn't you.

Slackware doesn't use SystemD either.

There are smart people that dislike systemd for valid reasons but then there's these children that literally have no idea what they are talking about. 90% of the shit people say in these threads is either false and/or come from a misunderstanding of systemd (which would be solved by reading which apparently these people can't do).

I no longer worry about systemd. I did at the beginning but now it is clear it will self-destruct on its own given time. Little by little the relevant true technical people that makes up what we consider the Linux ecosystem are realizing what a fucking huge mistake it was to allow Poettering to be in charge.
One thing is sure I won't have it on mt system.

>There are smart people that dislike systemd
Nope.

>for valid reasons
There's no valid reason to dislike systemd. There's no possible criticism of it.

>90% of the shit people say in these threads is either false and/or come from a misunderstanding of systemd
These threads should be a bannable offense.

>Little by little the relevant true technical people that makes up what we consider the Linux ecosystem are realizing what a fucking huge mistake it was to allow Poettering to be in charge.

Can to elaborate? Did I miss something?

Neither does PCLinuxOS.

You must have some kind of special retardation. I just don't understand it. If these people are not paying you and you aren't trolling, why would you stand for this fucking philosophy:

People as bitter and mislead as you make me really sad. Systemd It's against everything Linux has always been about.

If you don't have anything to hide you don't have a reason not to use systemd.

Haven't you heard? only terrorists and pedophiles uninstall systemd.

That's an April fools joke email from Lennart, maybe read the thread? Oh I forgot you people can't read.

No need to insult me on top of that. It won't make me install systemd any faster.

Do you think I care what you install on your system? The people that make these threads are the ones that seem to care about that stuff.

There is a huge movement right now on the Linux kernel community to start making security the central design consideration going forward. All that work is/will be for naught if the PID1 is developed by a guy who has stated publicly he only cares about performance. The whole kernel community at some point will force Lennart to fall in line.

North Korea best Korea!

But what "relevant true technical people" were you talking about?

...

The same guy that said this:
>I have to say, I don't really get the hatred of systemd. I think it improves a lot on the state of init, and no, I don't see myself getting into that whole area.

>Yeah, it may have a few odd corners here and there, and I'm sure you'll find things to despise. That happens in every project. I'm not a huge fan of the binary logging, for example. But that's just an example. I much prefer systemd's infrastructure for starting services over traditional init, and I think that's a much bigger design decision.

>Yeah, I've had some personality issues with some of the maintainers, but that's about how you handle bug reports and accept blame (or not) for when things go wrong. If people thought that meant that I dislike systemd, I will have to disappoint you guys.

Are there any arguments against systemd besides that it's new code? Binary logs by default is the only concern I can think of.

Yes.

ewontfix.com/14/

as much as i think systemd has many many wrong design decisions and the devs are kinda asses
but one stupid, one-line vulnerability is not what's wrong with systemd. see shellshock for instance, way more dangerous than this and bash wasnt crucified for it.

Not necessarily against systemd itself but against its fast adaptation in most Linux distros.

Systemd in its current state is a PMSing bitch breaking stuff with every update and totally unreliable for a production environment. That would be cool on arch, I guess, but on glacial distros like Debian it only raises suspicion.

But GNU software (including bash) has been getting crucified forever for being dogshit, user.

You are just too new a fish and haven't noticed the water you're swimming in yet.

Only the init part of systemd runs as PID 1. Everything besides that is optional user space.

Does systemd break things besides the killing all user processes part?

>sucks, non-intuitive and inefficient.
Maybe (You) are right, but they are rather easy to maintain. When i was a kid i used Slackware and OpenBSD and what i liked is it's simplicity in the etc. It's not like systemd users can't have this too, but they need a little learning if they come from sysv or BSD. The main issue is always from udev.

youtube.com/watch?v=pxHUevaC2Zk

>Does systemd break things besides the killing all user processes part?

That's actually just the documented stuff.

I have bad news OP.

Chrome OS is switching to systemd.
bugs.chromium.org/p/chromium/issues/detail?id=583671#c52

Only bad if you were counting on Chrome-OS.

It's only logical that a US based company is mandated to include NSA/systemd in it's distro.

Are you saying that ironically?

> Wants to get rid of systemd over violations of some imagined best practices.
> Does not require purely functional init based on a language with formally proven soundness.
Just arbitrary. Neither getshitdoneitworks nor the correct as possible approach. Just muh beliefs.

>Are there any arguments against systemd besides that it's new code?
There are many, many arguments against systemd, they just aren't ones that systemd fanatics will accept so there's no point bothering to repeat them any more. For example, it's very important (for various reasons and not just because of "the Unix way") that an 'init system' is strictly modular in a fully independent way. Systemd is assuredly not. However, in threads like these, systemd partisans will muddy the waters, argue about why independent modularity isn't important, mock their opponents, and then finally claim that systemd *is* modular which is the equivalent of just trolling. And *all* of their arguments are like this: once you *finally* reach the inescapable conclusion, once they *know* they've been proven wrong, they will claim up is down and coincidentally stop posting in the thread.

It's extremely tiring to repeat the same thread over and over again, stating the same arguments and only getting squirming, trolling, deflection and silence in response. Waste of time.

it's a shame because it feels like most people on here who argue for systemd are just playing devil's advocate "for the lulz" but don't really realize how fucking stupid people are on this board and how if they read some shit enough times that they'll start to parrot it as truth without any factual basis

the shady politicking of systemd's adoption should be enough for anyone who cares about the FOSS ecosystem to be slightly suspicious of corporate motives. red hat is the microsoft of linux, it's right there in front of you.

Except you've been proven to make up lies against systemd: All your credibility has gone down the toilet.

I never thought someone's good honest work for the benefit of free software would instigate so much jealousy!

we are already eating from the trash can all of the time

*schniff*

>mfw

I have arch with runit does that count?

>Not an argument
Thanks for acknowledging where you came from goon

For some reason i can't quite put my finger on, you seem like a complete asshole.
Do you have hair plugs and a micropenis?
I just get the image in my head of a loudmouth baboon when I read you're comment.

He has Gentoo.

Got ya, sempai

DELET THIS

Bonus

Why doesn't someone pull a systemd on systemd? Systemd had legacy support for the "old" interfaces, but tried to push over users to the new interfaces. Why can't someone make a set of systemd>sysvinit shims?

Because no critic of systemd has any technical skill, otherwise he wouldn't be a critic of systemd.

>what is suckless
>what are tox devs

Reminder that you can't cum with another dude's dick.

What?

But it is possible to cum with another dude's dick inside of you.

because linus torvalds is clearly a talentless hack with no technical skill

The best init system besides systemd is OpenRC which doesn't even have socket activation. It's sad that upstart was killed years ago and it is still better than OpenRC. I feel like systemd is here to stay.

See

Two things killed upstart:

- it was made by a literal fag
- it was GPL licensed and thus couldn't be adopted by many Linux distros and all BSDs

>it was GPL licensed and thus couldn't be adopted by many Linux distros and all BSDs

How is GPL a problem? Upstart had the same license as the Linux kernel (GPLv2). Canonical just gave up, they saw that everyone else (Debian was the final straw) was switching to systemd, they probably thought it wasn't worth it to keep developing upstart.

Remnant left Canonical.

systemd is LGPL and all others are BSD-licensed.

LGPL and GPLv2 are almost exactly the same. I didn't know about the main dev leaving but I'm sure they could have continued to develop upstart even without him if they wanted to.

>Except YOU have proven to make up lies against systemd
point number 2 in pic related. besides, systemd shills make up far more lies pro-systemd than the opposition ever did.
see forums.debian.net/viewtopic.php?f=20&t=120652&p=570371

Holy Shit thanks for posting my video mate.

No tripcode because I'm phone but hey, believe if yo u want to

THEN WHO WAS PHONE?!?!?!?

without-systemd.org/wiki/index.php/Main_Page

:^)

I don't have time for your shit thread and I'm posting from my job.

1. There's no proof that systemd is a botnet. And no, your tinfoil blogs don't count. Maybe spend some time researching the code instead of making laughable blogs will convince people.

2. If you don't like it go use BSD or something. The benifits of Systemd are clear. The init system is objectively smarter, easy to learn and the bootup optimizations are a real thing. Partly because parallel socket activations and getting rid of redundant scripts thrown everywhere. Unix inits are really not all that wonderful. Glad that Linux is finally getting some real and practical development that doesn't stick to old, unmaintained and deprecated relics from the past.

3. Going a bit technical and I hope Cred Forums kiddies understand:
For each process that is spawned, you may control: the environment, resource limits, working and root directory, umask, OOM killer adjustment, nice level, IO class and priority, CPU policy and priority, CPU affinity, timer slack, user id, group id, supplementary group ids, readable/writable/inaccessible directories, shared/private/slave mount flags, capabilities/bounding set, secure bits, CPU scheduler reset of fork, private /tmp name-space, cgroup control for various subsystems. Also, you can easily connect stdin/stdout/stderr of services to syslog, /dev/kmsg, arbitrary TTYs. If connected to a TTY for input systemd will make sure a process gets exclusive access, optionally waiting or enforcing it --I don't see any loss of control here

4. Thanks to systemd, DE devs can now create more powerful graphical tools that Linux has lacked for the past 25 years.

>Round up
Systemd is a well developed, future proof, customisation and efficient init system. There is a reason why all relevant distros like Debian, Ubuntu, and of course, Fedora based distros etc has adopted it.

Only lonely unemployed neckbeards that happen to be computer illiterate will cry over an init system being popular.

>customisation
*-friendly

>we are just an init system

Jesus fuck why do you care

Yea no one cares about Linux anymore, Fuchsia will be here next year.

You autists can do whatever you want with it for all we care, You can use Stallmans dirty feet as the init system if you want.

>no GUI
might as well run BSD kek

>optional features make me upset

Systemd can be just an init. It doesn't have to include all those things.

If i wanted a:
tmpfs
backlight
rfkill
bootchart
readahead
encrypted storage
efi/gpy boot
virtual machine/container
container management
hostname management
locale manager
ntp
webserver
dns cache
terminal muxer

I would install the programs that I WANT to do those features,i dont need my init/PID 1 to do these things for me.
If i wanted them i would install a program that does that.
I dont need any of that one my server
I dont need any of that on my desktop

I need an init system,that is ONLY an init system

But it does not act as just an init, It,by default loads everything that ISNT AN INIT SYSTEM

>Wants extra packages
>Installs extra packages one by one
vs
>Wants extra packages
>Just uses systemd

Guess which one has a job

PID 1 doesn't do all those moron, systemd is not one single process

>I don't need any of that in my server

>He doesn't need tmpfs
>He doesnt need ntp
>He fucking doesn't need container management
hahahaha

That's because most distributions choose to use most of the features Systemd provides. You can however build a system where Systemd is ONLY an init and nothing else, of course you likely wouldn't do that because if you care about an init being only an init there are other options besides Systemd that may be more appropriate for you.

>systemd is inefficient/bloated for what i need for said service
>systemd is not one single process
So you prove it?

You dont need tmpfs on server
You dont need ntp on a server, everything is locale anyway.When was the last time this millienia did you clock sway?
You dont need container, they are for incompetent sysadmins

>You dont need container, they are for incompetent sysadmins
Do I need to prove how this idiot kid is a NEET?

It's for def an NSA trojan.

No-one, no company, would willingly put up with Pottering and all his bullshit and monolithic PID 1 failtrains for free.

Red Hat and Ubuntu are getting paid/squeezed by the NSA to put in yet another bloated, unnessesary, riddled with backdoor bullshit into the kernel. People gave up on SELinux and they needed another vector. Expanding potterring NetworkManager program to include the entire... everything was a logical step for any government bureaucrat.

It's not needed. No-one want it. It keeps getting shilled and forced on everyone anyway. it's for def a botnet.

>docker
>im retarded sysadmin who cant make chroot/jails properly.

>kvm
>im a retarded sysadmin who cant decide what software i need nor can i manage a testing server prior to pushing to production

You don't think google will just lead it as a headless OS do you?

It's going to replace android and chrome OS soon.

>chroot is an alternative to containers
lmfao
Don't pretend to know what you are talking about, edgy faggot

chroot isnt a container
change root
CH-ROOT

OpenRC best RC

Check the date.

Everyone knows emacs is the superior init. There's really no need to use these fancy "sysvinit" or "system management" solutions when everything can be done in a few lines of elisp.

You do know latest systemd can hotpatch itself, right?

Another reason why systemd is so based

This sounds a lot like the "Master Control Program" (MCP) from the old Tron movie.

>tfw too intelligent to care about SystemD

Only old men and """"enlightened""" redditors believe this shit. KYS.

Kinda what he's trying to say...

>Only old men and """"enlightened""" redditors believe this shit. KYS.
I'm old and I use systemd on about 10 servers, 2 desktops and 1 laptop.

You're one of the good one's, user.

Only non-humans and faggots use systemd, the bright one like sysadmins don't use systemd.

The hivemind is strong with you all (but you're only a few fags and doing a forum slide).

It's better to get a distro without systemd because debian sometimes pulls systemd with packages that have it as a dependency.

Again, I don't care about the design of systemd, I care that it is controlled by RedHat, who services the NSA. Because of that there is a high probability that they put a backdoor in the OS disguised as a bug.

No problem, it's a great channel.

What are you, fucking retarded. I heard hitting shotgun shells with nails makes you smarter.

No logical argument and no evidence, please leave this thread if you are not going to contribute to the discussion.

Bullshit. Systemd already has one indirect dependency: journald

>Oh you wanna troubleshoot why alsa is shitting itself? Here's a blob you can't read without a service I expect you to be able to run

Fucking autistic faggot

This is why people hate linux and dont use it, its retarded fanbase deters everyone from it

AND, we're gonna have Microsoft pay for it.

Not an argument.

How is that possible?

Installed the arch-runit package from the aur and made a service for lightdm. I feel kind of bad about the service since it's just a shell script with "exec lightdm" which seems kind of low effort but I looked at systemd's service file for it and it looks like it does the same thing.

i was just looking at runit to replace sysvinit

do i have remove openrc as well?

Runit can only manage services or only act as init or both.