It's Happening! systemDick is kill!

>>56840623
systemd retards will defend this

OSX doesn't have this problem

>>56840623
OpenRC bby

>retards still telling lies about systemd/linux

>>56840623
Linux losers will defend this

>>56841060
i am a linux winner and cannot defend this

must be fixed

>>56840623
lmfao systemdicks

File: rekt-gif-.gif (136KB, 500x200px) Image search: [Google]

136KB, 500x200px

>>56840623
>fixed issue
OP GOT ABSOLUTELY REKT and BTFO AT THE SAME TIME. KEKEKEKEK

HOW WILL OP RECOVER

File: 1475115311649.webm (1008KB, 1920x1080px) Image search: [Google]

1008KB, 1920x1080px

OP, update you fucking bait


0/10

Doesn't even do anything...

Is this one of those MS paid troll threads?
Just report and continue

>>56841135
>must be fixed
It was... an hour after being reported.

File: 566-evp6cgB.jpg (28KB, 499x500px) Image search: [Google]

28KB, 499x500px

OP is full of shit.
Just did it here and nothing happened.

>>56841656
Because systemd is not some hobby NEET project. It is ACTIVELY maintained by paid professionals.


Kill yourself OP

File: hibye.png (81KB, 400x225px) Image search: [Google]

81KB, 400x225px

freebsd:/                                                                                       # NOTIFY_SOCKET=/run/systemd/notify systemd-notify ""
NOTIFY_SOCKET=/run/systemd/notify: Command not found.

Feels good man.

>>56841586
what terminal/settings is this

>>56841586
Nice Rem background

>>56841586
Emilia best girl

File: a430x.jpg (33KB, 500x443px) Image search: [Google]

33KB, 500x443px

>>56840623
>NOT using Debian with SysVInit
FUCKING KEK

>>56841755
I'm thinking of changing to FreeBSD. Can you think any drawbacks? Any particular DM/WM you recommend?

>>56842851
>Any particular DM/WM you recommend?
Not really, like the majority of *BSD users I don't use it as a desktop OS, it's actually worse than GNU/Linux in that use case
I run Windows on my PC and have a Macbook whilst all servers under my control are FreeBSD, not an uncommon combo for FreeBSD users.

>>56840623
Slackware doesn't have this problem

>systemd-notify: command not found
Go figure...

>>56840964
Hell yeah, motherfucker

SECURITY UPDATE: zero-length notify message triggers abort/denial of
service
- systemd-dont_assert_on_zero_length_message-lp1628687.patch: change
assert to simple return + log (LP: #1628687)
- Thanks to Jorge Niedbalski <[email protected]> for
the patch.

Windows 10 doesnt have this problem

>>56844095
Windows 10 doesn't have any customizable init either. BTFO wincuck

>>56841586
Fuck off beawesome

File: headcrab.jpg (146KB, 410x522px) Image search: [Google]

146KB, 410x522px

>>56842818
>not using Devuan

>>56840623
I just ran this and nothing happened

File: AbsolutelyDisgusting_Scooby.jpg (31KB, 240x389px) Image search: [Google]

31KB, 240x389px

OpenBSD does not have this problem.

>>56844066
>>56841693
>>56841586
>>56841563
>>56841003
>missing the point
Here, the author knew how dumb systemd apologists are and explained it quite thoroughly
> The immediate question raised by this bug is what kind of quality assurance process would allow such a simple bug to exist for over two years (it was introduced in systemd 209). Isn't the empty string an obvious test case? One would hope that PID 1, the most important userspace process, would have better quality assurance than this. Unfortunately, it seems that crashes of PID 1 are not unusual, as a quick glance through the systemd commit log reveals commit messages such as:
>coredump: turn off coredump collection only when PID 1 crashes, not when journald crashes
>coredump: make sure to handle crashes of PID 1 and journald special
>coredump: turn off coredump collection entirely after journald or PID 1 crashed

>>56841651
Hi there self-parody systemd shill! HIIIIIIII! How's it going? Ya still shilling shitty redhat shit?

>>56842818
>sysvinit
>not runit
Get with the times, grandpa.

>>56842851
Far worse hardware support compared to Linux. If your hardware is a desktop or server and it's at least 4-5 years old, FreeBSD will *PROBABLY* support a majority of it's hardware. Anything newer is a crapshoot. Peripherals... good luck.

File: Lennart_professionalism.jpg (23KB, 646x164px) Image search: [Google]

23KB, 646x164px

>>56845856
This

If you run systemd in your system better make sure you either work at Red Hat or your name is Lennart Poettering or Kay Sievers because YOLO pic related.

>>56846626
Guess I'll switch to debi- fuck.

>>56840964
yeeeas

>>56841650
Wow that's awesome.

>>56841656
>>56841693
Not all systems affected will be patched within an hour and this proves how seriously flawed systemd is. It is a security nightmare, and impossible to properly audit.

I have managed to remove it from Raspbian.

File: image_18.jpg (256KB, 1280x960px) Image search: [Google]

256KB, 1280x960px

>>56840623
Have you tried not running the command?

>>56848658
>mfw millions of rhel servers are now fucked and wont get pushed content for years

>>56848727
and think of all the embedded boxes that serve a serial console

the possibilities are fucking amazing and this vulnerability will bite them in the ass into the far, far future

Linux peaked on embedded anyway, it's far too fucking fat these days

>Nothing happens
What the fuck are you on about, fucktard OP?

>>56841651
>>56841003
>>56841563
>>56841586
>>56841656
>>56841693
>>56844066
>>56845306
>>56846800
>>56848751
>>56848763
Install gentoo

don't worry goyim the nsa isn't poking around in dbus

they want your system to be safe after all

>systemd uses Javascript in configuration files
just fuck my shit up lads

>>56848658
And since it's PID 1 you also require rebooting your whole system to update it.

>>56849001
systemd swallowed polkit?

>>56849087
Yep, it's a complete and utter waste of resources, too. On something small like a CHIP it's using a solid 5-10% of system resources at any given time doing who knows what the fuck.

>>56848968
>fucking dbus

What was wrong with 9p?

>>56849103
The CHIP obviously needs all the import systemd features like multi-user session management.
Thank you Lennart for forcing all that stuff on every Linux system.

File: Screen Shot 2016-09-29 at 11.37.43 PM.jpg (34KB, 384x293px) Image search: [Google]

34KB, 384x293px

>>56849107
It's not 9p and Linux isn't Plan 9.

>>56849136
exactly, and it was a wonder that we had multi-user session management on Linux before systemd isn't it?

>>56849136
your retarded distro did it because "muh guhnome"

just use a different distro like void

>>56849107
Red Hat didn't create it.

>>56849152
There was ConsoleKit but it is crap too.
But at least it didn't infect non-desktop system components.

>>56849153
I removed systemd from Raspbian but it wasn't easy.

>>56849153
I don't have a CHIP but I believe the official distro is Debian-based.

Using anything else will probably be quite a hassle.
These SBC with Chinese chips tend to be a nightmare to set up yourself.

>>56840623
ATTENTION: THIS IS ANOTHER ANTI-LINUX THREAD BY NSA SHILLS.

Nothing to see here, move along.

>>56849210
>NSA shills
>anti-Linux

Linux, Red Hat specifically, is the NSA's favorite OS.

>>56845856
> Isn't this security / stability critical thing bug free and fully tested?
Just about always: No.

And when it perhaps is, just about nobody uses it.

>>56849222
Pretty sure Windows is the NSA's favorite operating system.

>>56849236
NSA uses RHEL a lot.
They even develop software for it and publish guides for it.

File: Screen Shot 2016-09-30 at 12.02.18 AM.jpg (37KB, 380x300px) Image search: [Google]

37KB, 380x300px

>>56849153
see:
>>56849208
yes just like with a pi, you miss out on a while bunch of shit and it's barely worth the hassle because you give up GPIO and shit like that

>>56849222
>Red Hat specifically, is the NSA's favorite OS
this and checked

>>56849229
As if any group of people could audit systemd fast enough to keep up with the wildly fluctuating codebase anyhow.

And the codebases of its many supporting programs including databases, xml parsers, javascript parsers, kek the list goes on

Something worth considering:

Any time there is something posted on the internet critical of systemd, the shills that come out of the woodwork never address any technical issues directly. They are clearly not even familiar with init, let alone its much more complicated "replacement" systemd. At best they can lamely link or copypasta. Does this betray a certain low-dollar shillop? Certainly if they really wished to be taken seriously they could offer better technical banter, shit even their name calling is atrocious and wouldn't even be considered offensive on Reddit. !

File: 1472462670120.webm (589KB, 426x284px) Image search: [Google]

589KB, 426x284px

>>56840623

>gif

They killed the Debian guy to make sure systemd had full penetration.

>>56849890
No no it was a false-flag operation by the KGB.

>>56848887
install gentoo with systemd profile

>>56849890
Ian left the project long ago.

Holy fuck you have to be mainlining the Kool-Aid straight into your cock vein to defend this one.

Notify chokes on an empty string? Are you serious?

How long has this been around for?

>>56851008
Over two years

>>56845856
It's good that the bug was fixed so quickly. But it shows a lack of thought that nobody considered the case of handling empty messages. And the other points the author of that post brought up still remain. Setting umask(0) was already known as a bad idea when I started learning unix programming in 1992, even for a simple program. With such a large subsystem, defaulting to world writable and trusting code that others write to call the right macro is asking for trouble.

>>56840623
>not using devuan

just switch back to nsa/windows

>>56841586
That's nice but I love Emilia.

>>56851018
That settles it then: This non-bug never affected anyone besides anti-systemd shills.

>>56848763
Things appear normal, unless you try to start or stop any services. Things already running will continue working for the meanwhile.

When I tried it in a test vm, just running it once hung pid 1. Trying to reboot did nothing, even reboot --force since it needs to poke systemd.

Only way to bring the system back to working status was to power cycle the vm.

>Testing inputs of empty strings, excessively large data structures, and other invalid permutations is the realm of fuzz testing, which is a recent project even for the Linux kernel.
>Testing inputs of empty strings, excessively large data structures, and other invalid permutations is the realm of fuzz testing
>Testing inputs of empty strings
What an absolute fucking retarded faggot

Millennial shitgrammers are why trash like systemdicks will kill computers forever

>>56851057
>bugs are only bugs when publicly known
hello NSA

>>56851102
>local DoS
>NSA
nice buzzwords

>>56851122
>what is a network

>>56851143
>what is Natriumchloride