Systemd is for ________ Last episode: >>59322473

File: Bacooomb.jpg (41KB, 449x337px) Image search: [Google]

41KB, 449x337px

Fags

>>59339615
fagoots

>>59339615
Baby Linux user here, what is systemd? I use manjaro btw.

improving linux and destroying the obsolete unix worse is better dogma to replace it with something practical and modern

>>59339615
cucks, shills, normies, and the CIA.

File: FührerBeats.gif (204KB, 226x280px) Image search: [Google]

204KB, 226x280px

>>59339664
>improving
You mis-spelled "making brittle, insecure, undocumented, and error prone."

File: RomanClothes.jpg (12KB, 205x243px) Image search: [Google]

12KB, 205x243px

>>59339615

...patricians.

File: IllumosLogo.png (136KB, 1583x2057px) Image search: [Google]

136KB, 1583x2057px

Us /tech/ will retreat to the Dæmon Peaks and Phoenix Ridge to regroup, and when the masses realize what has happened to their prized GNU we will strike with our superior UNIX and UNIX philosophy to slay the communist.

>>59339615

CIA NIGGERS

>>59339649
It's a thing that initializes things but also does things that other things once did so it's the new
>botnet

File: gooby.png (191KB, 812x716px) Image search: [Google]

191KB, 812x716px

>>59339804
oh FUCK, but I was using Linux to escape the botnet!

File: 4c5303f80165f623d83e0af57f2f1b84cfccfbcbd5cd9c57c01cde7597839aee.png (55KB, 920x720px) Image search: [Google]

55KB, 920x720px

systemd was created by an SWJ faggot who works for RedHat, a company that is basically a CIA front. It was forced on all distributions almost overnight.

The arguments against systemd and why it's bad have been posted over and over, yet systemd shills continuously pop up saying no one has provided any arguments against systemd and that Lennart Poettering's cock is small so it doesn't stretch your asshole or hurt too bad while he's fucking you over with a CIA trojan that runs at PID 1.

The systemd developers are making it harder and harder to not run on systemd. Even if Debian supports not using systemd, the rest of the Linux ecosystem is moving to systemd so it will become increasingly infeasible as time runs on.

By merging in other crucial projects and taking over certain functionality, they are making it more difficult for other init systems to exist. For example, udev is part of systemd now. People are worried that in a little while, udev won’t work without systemd. Kinda hard to sell other init systems that don’t have dynamic device detection.

The concern isn’t that systemd itself isn’t following the UNIX philosophy. What’s troubling is that the systemd team is dragging in other projects or functionality, and aggressively integrating them. When those projects or functions become only available through systemd, it doesn’t matter if you can install other init systems, because they will be trash without those features.

An example, suppose a project ships with systemd timer files to handle some periodic activity. You now need systemd or some shim, or to port those periodic events to cron. Insert any other systemd unit file in this example, and it’s a problem.

File: systemdcomponents-svg.png (228KB, 770x433px) Image search: [Google]

228KB, 770x433px

>>59339885
Systemd is now your OS. Linux is like an appendix, it's almost vestigial at this point.

File: 1474228758387.jpg (384KB, 1437x1296px) Image search: [Google]

384KB, 1437x1296px

There are 3 main groups of systemd haters, and they all have valid critcisms:

People who don't like the fact that systemd has massive scope creep. Specifically that it tries to reimplement many existing services instead of improving / integrating existing ones. For example user switching, network management, logging, etc.

People who don't like the idea of everything relying on systemd interfaces to work at all. For example gnome started to rely on logind and other services even though it technically didn't need to.

People who don't like the management of the project. Lennart can be a dick to people with different opinions. He also created many interesting projects which were both a bit complex and pushed before they were ready. (like pulseaudio, packagekit) Since they were forced on people via popular distros, pulseaudio became "the thing that's always broken" for a year or so. And since Lennart was the author, he became a person who breaks the system.

>in b4 a CIA shill replies with "no one will post a single valid criticism of systemd"

>>59339951
>>59339986
>redditfrog

Thanks for saving from wasting time reading anything you posted.

File: 1451791957901.jpg (2MB, 4086x5898px) Image search: [Google]

2MB, 4086x5898px

>>59339964
oh my FUCKING god, you've gotta be fucking kidding me. Should I just switch back to windows, or go to mac? Jesus christ this is bull shit.

File: 9e0423b2933b38af58eabfcd45dae719dbfd775e50532e231354c7401a06af54.png (212KB, 1000x1000px) Image search: [Google]

212KB, 1000x1000px

The only people the systemd developers had to convince to get it widely adopted were the distro maintainers and the developers of a few key software projects. The distro maintainers made systemd at least an optional (if not outright default) init system, since it (1) promised to eliminate a series of init-related problems, and (2) other critical pieces of low-level userspace functionality like udev were getting merged into systemd's codebase anyway. In theory, systemd would reduce their maintenance burden, giving them an incentive to encourage their users to adopt it.

Making it an optional or default init system wasn't enough to spur its rapid adoption, however. What helped solidify systemd's hold was a few key developers making their software depend on it to work. For example, you can't run GNOME without systemd these days, and KDE is not far behind. Other previously-unrelated daemons like upower now require systemd to work correctly. So, users who want a working desktop pretty much have to use systemd now, even if they don't have an opinion on it, or even if they want a desktop more than they want to steer clear of it.

This has created a lot of frustration within the user community. There are plenty of users who do not want systemd, but now have to either (1) go without a working desktop to do so, or (2) fork the relevant parts of the ecosystem that depend on systemd and make them so that they don't. This is exacerbated by author of systemd openly advocating that GNOME depend on it (helping to create this dilemma), having a reputation for breaking the Linux sound system (making people wonder if the same will happen to init), having a reputation for not taking criticism well, and increasingly having a reputation of being deceitful about his intentions for systemd's role in the ecosystem.

File: 09d68ea6f406eec2962d456ebaa61e0d61b9053c52fcfbe9a807996b67a6183b.jpg (135KB, 1024x811px) Image search: [Google]

135KB, 1024x811px

>>59340012
contd.

Systemd's design has also created a lot of frustration with power users and developers. While it is all well and good that every developer should maintain his/her code in the way he/she sees fit, there are two important design decisions in systemd that have questionable technical merit but have non-trivial social and political consequences for the ecosystem. First, the author of systemd has repeatedly stated that systemd will not be portable, and will reject patches from those who would make it work. This effectively locks people into Linux if they need to use software that depends on systemd, even if the software doesn't otherwise require Linux-specific features. Second, the author of systemd has publicly stated that the interfaces between the systemd components will remain unstable and undocumented for the foreseeable future. This makes the creation of alternatives to systemd components difficult, since developers have to first study the large systemd codebase to even figure out how to begin, and will need to ensure their alternatives are compatible with every version of systemd if they are to gain adoption.

>>59339615

^W currently running.

    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Sun 2017-01-08 01:14:21 EST; 2 months 0 days ago

File: 9frontsystem02.png (361KB, 500x326px) Image search: [Google]

361KB, 500x326px

>>59340005
At this point you have a couple options. If you don't want the botnet, move to a non-systemd Linux distribution, use a BSD, or switch to an even more exotic OS like Haiky or 9front.

If you don't care about the botnet but hate ads in your OS, switch to the Mac. If you don't mind maddening pop-up ads all over your shit at all times, just run Windows.

File: 1480084473646.jpg (63KB, 1280x720px) Image search: [Google]

63KB, 1280x720px

>>59340030
contd.

Combined, these two design decisions ensure that it will be very costly and time-consuming for developers to implement alternatives, short of rewriting the whole systemd from scratch. Any work they do to address their problems with systemd can be easily undermined by the systemd author (who doesn't particularly care for alternatives). What is particularly demoralizing about this situation is that there isn't a clear technical reason why systemd had to be designed this way--it could have been written in a portable fashion (or, people would step up and make it portable if the author would accept their work), and its components could have been designed to have stable internal interfaces, so replacing parts of systemd piecemeal would be feasible. The only perceived gains from these design decisions is that the systemd author can artificially make it too costly to compete against it, leading to frustration and controversy.

>>59339615
It's pretty good honestly, sysvinit's handling of hotplugging devices is wonky as fuck

I don't really care if Poettering is a SJW, but it seems like people take issue with his politics more than any actual technical issues with systemd

>>59339951
Prove you aren't a CIA shill.

>>59340193
I'm arguing against systemd, you didn't even read my post. If I was a CIA shill I'd be arguing FOR systemd.

File: 1476636504807.jpg (62KB, 840x544px) Image search: [Google]

62KB, 840x544px

Very real disadvantages of systemd:

1. systemd is tied to a specific kernel and a specific libc and specific device manager and specific journaling daemon, basically, having systemd means you're locked in to a whole lot of other things.
2. systemd is renowned for locking up during startup and boot when you have network filesystems.
3. systemd hardcodes quite a lot of the booting and shutdown process in C which other systems place in easily editable scripts.
4. systemd in practice requires quite a lot of things: ACLs, PAM, dbus, polkit, these are not hard requirements but without this the above advantages are lost so all distributions enable them at compile time.
5. logind starting to do retarded shit like user sessions and having retarded power management, in theory you can disable logind, but no distribution again does this.
6. systemd is very monolithic and comes in one configuration compared to being able to piece your system together yourself.

>in b4 i don't care, lennart's dick just tastes soooo good. plz lennart, cum on my face

Nobody would give a shit about systemd if Poettering wasn't an outspoken leftist, it would just be another Kernel-related project.

/pol/ needs to fuck off with their reverse SJWism

File: 1477544183194.png (262KB, 785x757px) Image search: [Google]

262KB, 785x757px

>>59340274
7. systemd appropriates the cgroup tree and takes control of it and completely messes with any other user of the cgroup tree and really wants them all to go through systemd, systemd was wirtten basically on the assumption that nothing but systemd would be using cgroups and they even tried to lobby to make cgroups a private prioperty of systemd in the kernel but that went no-where.

8. systemd's usage of cgroups for process tracking is a fundamentally broken concept, cgroups were never meant for this and it's a good way to fuck resource usage up.

9. systemd has a hard dependency on glibc for really no good reason.

10. systemd relies on DBus for IPC, as the name 'Desktop bus' implies DBus was never written with this in mind and it shows. DBus was written to facilitate IPC within a single desktop session, not as a transport during early boot. This is why systemd wanted to push kdbus heavily beause kdbus solved some of the problems inherent to DBus being used as IPC during early boot.

11. systemd's security and general code quality practices are less than stellar, a lot of security bugs pop up in systemd due to its insistence of putting quite a bit of code in pid1 and quickly adding new features and quickly changing things.

>in be4 "not one single valid criticism" please let me jack you off lennart

>>59340252
That is exactly something a CIA shill would say to deflect.

Do you have any actual evidence you're not a CIA shill?

File: 1474164949171.png (393KB, 785x757px) Image search: [Google]

393KB, 785x757px

>>59340288
13. systemd creates dependencies and is a dependency of things for political reasons in order to encourage people to pick these things. This is not conjecture, Lennart has admitted multiple times that he creates dependencies to 'gently push' everyone to the same configuration

14. systemd is monolithic for its own sake. It's basically product tying to encourage people to pick an all-or-none deal to again gently push towards this consistency.

15. Lennart Poettering, the face of systemd and its lead dev is the biggest primadonna FOSS has ever known who continues to shift blame and demand that entire world adapt to his designs.

>in b4 "lennart's is dick is sooo comfy in my ass"

>>59339951
>>59339986
>>59340044
>>59340274
>>59340288
>>59340012
>>59340305
>>59340030
Who pays you to shill this hard?

File: 5136eaac84b4ceaa5ee3bd888068d9b251dbf1127255ce4506e1a7ac15a2b0c6.jpg (31KB, 442x500px) Image search: [Google]

31KB, 442x500px

Systemd-tards and CIAniggers haven't posted one single argument in favor of systemd or why I should use it.

Here's some more reasons not to use it:

1. it's unauditable, at hundreds of thousands of lines of code
2. it's a large attack surface.
3. system logging is fundamentally flawed, almost broken
4. it has become an underlying dependency for top-level software layers; to forgo shitd is to forgo that software that depends on it
5. it places way too many potential failure cases into what is probably the most critical program in the system
6. what problem is it solving again?
7. bluring userspace with kernel land. MS tried this between 99-03 with kernel32.exe and IIS, and look how that turned out for them
8. because top software layers depend on it, and because it won't work anywhere else but Linux, it effectively shifts entire projects (and desktops) to linux-only, co-opting development for a specific environment
9. why was this needed when there were existing solutions?

>>59340005
Use Manjaro with OpenRC, or use Void Linux.
Systemd is shit, but it's not a shit as Mac or Windows.

>>59340332
>it's unauditable, at hundreds of thousands of lines of code
You're retarded, you're implying that the Linux kernel is unauditable by your same measure.

Gas yourself

>>59339885
This entire thread is an attempt by the feds to make you scared of Linux so you will use a compromised operating system. It's almost entirely just a couple paid anti-systemd shills who completely ignore any rebuttal to their 2 bad arguments.

>>59340328
I'd say your the shill here

>>59340328
Who pays you to shill for a backdoor?

Do you have a single valid reason why anyone should run system-backdoord?

>>59340355
Sorry but you are trying very hard and going to a lot of effort to shill why people shouldn't use a piece of software you don't like

Makes me a little suspicious of why you are so invested in this. If you're not a shill, why don't you prove it?

>>59340352
Not true, I'm not trying to scare anyone away from Linux. You most definitely should continue using Linux, just a distro that doesn't have systemd (backdoor) as the init.

Devuan, for example, is basically Debian without systemd. You can also use Arch or Manjaro with OpenRC.

>>59340274
logind also SIGKILLs your processes by default when you log out..

File: 1421621795916.png (37KB, 1234x815px) Image search: [Google]

37KB, 1234x815px

>>59340358
>systemd is a backdoor
Do you have even a shred of evidence for your claim?

File: proofs.png (68KB, 820x399px) Image search: [Google]

68KB, 820x399px

>>59340374
Well for one that was one of 3 of my posts.
I wouldn't have to hate systemd if didn't literally infect every thing it touches.
It actively tries to suppress competition. That's not a good thing in an open source project.
Plus the developers are incompetent narcissists.
More importantly though, why should I use it?
What's the benefit over Runit or OpenRC?
(hint: there isn't one)

>>59340398
>logind also SIGKILLs your processes by default when you log out..
as it should. It's the desktop environments responsibility to make sure things are gracefully closed before making the call to systemd to logout. If there are still processes hanging at that point, then kill them. That is absolutely the correct thing to do.

>>59340469
>why should I use it
Then don't, but the way you are very vocally spamming this thread over and over again makes me think you are pushing an agenda or you have a vested interest in people only using FOSS software that _you_ promote and evangelize.

It's very suspicious and you still haven't proved that you're not a paid shill.

sexual

>>59340518
And know I know you are retarded.
You NEVER EVER EVER SIGKILL anything. Period.
That absolutely should not be default behaviour.
Send a SIGTERM at the most. Most software responds to SIGTERM and gracefully shuts down. Any software that doesn't is broken.
If you fucking SIGKILL every leftover process you are going to have a lot of memory issues down the road.
>making the call to systemd to logout
This is why systemd is retarded.
You do not need a library call to logout.

>>59340332

- systemctl is much more uniformly informative than the equivalent shell scripts tend to be
- It's incredibly convenient to create services files for simple daemons.
- It's flexible enough to handle weird programs that handle their own daemonization somehow. Usually it's just a couple more lines of a service file.
- Users get their own systemd --user instance, so you can run per-user daemons without having to su into root.
- Comes with log maintenance and rotation by default, and journalctl is incredibly flexible at showing you relevant data
- Sets up cgroups for you automatically
- Seems to transparently handle old-style shell script service files

That's what I can think of off the top of my head.

File: 1473029505746.jpg (136KB, 640x977px) Image search: [Google]

136KB, 640x977px

>>59340352
The thing that pisses me off the most about this post is how plausible it is. There is so much conflict of interest between Linux and big dicked companies like M$ and the NSA/CIA that it would be reasonable to assume these organizations would subvert linux. The idea being that it's better to cut it by the root now than wait til it becomes bigger later and reducing the power that these agencies have over operating systems & individual user's hardware.

Fuck this world, I can't find peace in the physical or the cyber world anymore. Where is there left for me to escape?

>>59340332
>1. it's unauditable, at hundreds of thousands of lines of code
That doesn't come close to making it unauditable. This point is completely invalid.

>large attack surface
Explain exactly the different ways you would attack it.

>system logging is fundamentally flawed, almost broken
Explain what the flaws are

>it has become an underlying dependency for top-level software layers; to forgo shitd is to forgo that software that depends on it
Give me a specific example of how this affects me negatively

>it places way too many potential failure cases into what is probably the most critical program in the system
Systemd is not a single program

>what problem is it solving again?
>why was this needed when there were existing solutions?
I can't speak for the development team, but I like systemd because the previous state of Linux was that I had to learn a dozen different tools because the different Linux distros couldn't agree on a standard. Depending on which Linux distro I was working with, I had to remember how to use it's respective selection for init services as well as other components which systemd now handles. As a person who interacts with a variety of different linux distros regularly, it has made my life easier.

>bluring userspace with kernel land
Please elaborate. I'm genuinely curious about this.

>because top software layers depend on it
Please elaborate. I'm genuinely curious about this.

>because it won't work anywhere else but Linux
Literally do not care.

>it effectively shifts entire projects (and desktops) to linux-only
Literally do not care.

>>59340529
>vocally spamming
Try again fucko.
See the pic. Unfortunately that's the best you are going to get from me. There isn't much else I could do to prove I am not a (((shill))).
>pushing an agenda
Otherwise known as stating my opinion.
>__you__ promote
What was I promoting?
I don't care what init people uses.
I wouldn't care if people used systemd if it didn't threaten my ability to use other init systems.

For the anons that possess reading comprehension and aren't afraid to do a little reading:

http://ewontfix.com/14/

http://blog.darknedgy.net/technology/2015/10/11/0/

>>59340681
tl;dr

Please summarize the main points

>>59340681
Which one do I read first?

>>59340654
There was never peace in the cyber world, you're just paying better attention.

>>59340672
You've spammed the exact same copypasta in this thread for like the 4th time in 2 days.

I'm starting to think you have a 0day for OpenRC or something and that's why you're shilling so hard.

Nice try though.

>>59340727
>I'm starting to think you have a 0day for OpenRC or something and that's why you're shilling so hard.
I was just thinking the same thing

>>59340668
Heartbleed was the most innocent looking code possible. It is really easy to miss something in C.
That's why making projects that are hundreds of lines of code for no reason is pragmatically speaking, asking for it.
>different ways to attack it
Remember the DOS attack using the world writable systemd message socket? That's just one example.
Or the fact that every single file created by systemd is world writable by default?
The developers are shooting themselves in the foot for no reason.
Any large program that does a lot of different things has a big attack surface.
>how is it fundamentally flawed
Look around this thread.
>systemd is not a single program xDD
No but they are so closely related that a failure in one translates to failure is others.
>many standards
Yeah that is a problem, but systemd is NOT the solution. It's a problem with open source more than anything.
>please elaborate
Well I am not sure about the kernel one, but many user mode programs that have no reason to be dependent on systemd are hooking into it.
See GNOME.
>literally do not care
Well that's just, like, your opinion man.

Is systemd svchost: linux edition

>>59340727
What copypasta?
Nice try, but I don't use OpenRC :^)

>>59340812
>Nice try, but I don't use OpenRC :^)
Of course not. You probably use systemd and just want us to use openrc so you can exploit our systems.

>>59340812
You spammed the copypasta referred to in >>59340328 in a previous thread.

Seriously, why are you shilling so hard?

>>59340826
I use Runit. I can screenshot if you want.
>>59340833
Those were not me.
I know I won't convince you, but maybe someone who isn't retarded will see the truth.

>>59340866
>Those were not me.
Prove it, shill.

>>59340883
Screenshot in >>59340469 is the best you can get.
What other ways would prove it to you?

>>59340927
Proves nothing because everyone on /g/ knows what inspect element is

Gonna have to up your shill game if you want to convince people, gotta earn those shekels.

>>59339633
fpbpdp

>>59340927
I am aware it's not bullet proof.
What would do it though?
I have asked this at least 3 times now.

>>59340961
Meant for >>59340946

>>59340961
No proof in the world would ever be good enough for shills. Just quit responding to the obvious systemd CIAniggers.

>>59340961
>asking for help with hiding your shilling better
Why would anyone help you establish credibility? That's on you

>>59340989
I don't know what I expected. Proof is subjective, so I asked. That is exactly what a shill would say though, it seems >>59340988 is right

To all those with sense, don't use systemd, for the multitude of reasons discussed in this thread. Literally anything is better.

File: 1486430884555.jpg (287KB, 786x1068px) Image search: [Google]

287KB, 786x1068px

>>59339615
*he is Lennart Poettering: http://0pointer.de/lennart/

https://www.youtube.com/watch?v=i4CACB7paLc (((Embed)))
The systemd Journal has been introduced with F18. In this talk I want to discuss the why?, the what? and the how?

https://github.com/systemd/systemd/issues?q=is%3Aissue+is%3Aclosed
>Issues?

https://plus.google.com/+LennartPoetteringTheOneAndOnly
'" I think the Microsoft hatred is a disease. '" --- LENNART POETTERING

https://plus.google.com/+LennartPoetteringTheOneAndOnly/posts/J2TZrTvu7vd
'" The Linux community is dominated by western, white, straight, males in their 30s and 40s these days. '"

>Oy
>y

>Vey
>e
>y

File: this post.jpg (52KB, 600x600px) Image search: [Google]

52KB, 600x600px

>>59341015
>hehe yes goy be sure to run some of my unaudited init daemons instead, don't trust systemd, it's trying to trick you!

>>59339615
normalfags

>CIA Niggers
>Shills
>Lennart Poettering

Beta Cucks can use whatever flavour OS they want.
Homosexual Pedophiles can choose whatever init system they want.

sYSTEM d has been deeply inserted into so many distros in sao little time that only Beta Homosexual Pedophile Cucks are happy to run that shit.

Are (((You))), may I ask, an
>Homosexual
>Beta
>Pedophile
>Cuck

??
?

>>59339615
Smart, productive, hard-working people.

>>59341110
>Beta Homosexual Pedophile Cucks
literally nothing wrong with any of those things. Stay mad you cis-gendered white male.

File: tumblr_oeh1lo9rNw1vva2lso1_400.gif (2MB, 320x180px) Image search: [Google]

2MB, 320x180px

>>59340654
Sauce on trap ?
I agree with you that there is subversion going on, and a lot of it. Look at the state of this board with the AMD/Intel circlejerk and how SJW's are infecting FOSS, etc. There's definite psyops happenings all around us aimed to put us apart and fall into the ruts theyve dug out for us.

SystemD is just part of that IMO. That twink who founded it is probably just a faggot trying to push his warez, but the reason it gained so much steam and clout is due to the hidden influences of the State(s). It really was like waking up to a new init system overnight. I remember the Arch forums were pissed that we were losing our simple init config.

>>59341178
>constant psyops
Glad I am not the only one that notices this.

>>59341163
millenial-d spotted

File: PepePissCoke.png (77KB, 515x369px) Image search: [Google]

77KB, 515x369px

>>59340005
illumos is your only hope senpai

NSA

File: insidejob.JPG.jpg (51KB, 631x591px) Image search: [Google]

51KB, 631x591px

>>59341216
Makes me feel like Terry having to wade through all this noise.

Daily reminder that there is literally not a single valid criticism of systemd in this thread.

File: Kektastrophe.png (179KB, 400x350px) Image search: [Google]

179KB, 400x350px

>>59340350
Where's the standard by which it's written against?

Where's the design structure? Where's the API documentation?

Can you do anything other than be a total CIA nigger?

>>59341452
>it has hundrds of thousands of lines of code therefore an audit isn't possible
It's a retarded argument dude, you implied that it's unauditable because of the size of the codebase which would imply that the Linux kernel is unauditable too

>>59341427
a-are you for real?

>>59341473
every time this shit.

are you real?

>>59341452
Did you even look? It seriously took me less than a minute to find this: https://www.freedesktop.org/wiki/Software/systemd/
It contains tons of links, including user documentation, developer documentation, debugging guides, the white paper for the project, and more.

>>59341513
Because you keep parroting the same retarded arguments

>>59341473
it's inauditable because it is intertwied as fuck
also binary blobs

>>59341557
>it's inauditable because it is intertwied as fuck
Provide an example to demonstrate how it is intertwined. It seems pretty modular by design to me.

>binary blobs
I'm interested. Tell me more.

File: ThatsAButthurt.jpg (24KB, 330x250px) Image search: [Google]

24KB, 330x250px

systemd shills btfo

File: iWKad22.jpg (90KB, 1440x1080px) Image search: [Google]

90KB, 1440x1080px

>>59341473
Large codebases aren't audited by single people or Joe Blow. It's not possible for either you or me to audit the entire codebase of the Linux kernel or systemd. We can use the Heartbleed vulnerability in OpenSSL for example. The vulnerability existed for ten years and thousands of people reviewed the code, yet no one found the vulnerability.

The reason people trust the codebase of the Linux kernel is because it's been independently audited by security teams at multiple security companies. These audits are expensive and take a long time to complete. It took almost a year for QuarksLab to audit the much much smaller VeraCrypt codebase.

No independent security teams have audited systemd. Also, implying that a single person can audit a code base with hundreds of thousands of lines of code is a fallacy, and you need to quit repeating it, it's not reality. Just because something is open source doesn't mean it's audit-able. Especially if the devs refuse to document the components as Poettering refuses to do for systemd.

File: wojakpepe.jpg (27KB, 499x499px) Image search: [Google]

27KB, 499x499px

>>59341345
Yeah, at least others are waking up to it.
Eventually God will killall -9 CIA niggers
>>59341427
>at least 20 posts pointing out flaws, or valid criticisms
>not a single valid criticism
Are you real?

>>59341599
https://www.freedesktop.org/wiki/Software/systemd/
Stop spreading the meme that they don't document their project. It's not true. There is a fuck ton of documentation if you pull your head out of the sand

File: LP_CIA.png (441KB, 752x941px) Image search: [Google]

441KB, 752x941px

>>59339615

File: HappyHelper.png (24KB, 657x527px) Image search: [Google]

24KB, 657x527px

>>59341515
A bunch of disparate pages which half are out of date.

Wonderful. I wouldn't expect any less.

>>59341603
>completely ignoring all the rebuttals to your stupid arguments

>>59341599
>mplying that a single person can audit a code base with hundreds of thousands of lines of code is a fallacy
I never said one person could audit it you fucking retard, I was addressing your claim that "it's inauditable because it has hundreds of thousands LOC!!!" which is retarded on its face because you are implying that large-scale code reviews don't exist for bigger projects (like the kernel)

What the fuck do you think the LKML is?

Fucking idiots man

File: 64c299dd261e66b0eb4ebe932327364268b3227c.png (68KB, 606x539px) Image search: [Google]

68KB, 606x539px

>>59341634
It spreads because it's true. Systemd does not document!

>>59341634
I see you've never checked out the repo for systemd and looked at the code since you have no idea what you're talking about.

Documentation for running the commands is not the same as documentation for the code. They do not document entire hundred line blocks of code and it's almost impossible to figure out what it's doing at times.

>>59341599
This is a dumb argument because the combined code of all the software you would have to run without systemd is likely around the same number of lines. systemd is not just an init system. Comparing number of lines to a straight init system like sysv or openrc is not a valid comparison.

>>59341657
You CIA niggers are really bad at this.
>rebuttals
You mean autistically screeching "not a single valid criticism"?
Wow I am really convinced now :^)

>>59341685
>They do not document entire hundred line blocks of code and it's almost impossible to figure out what it's doing at times.
Give me an example of this. Show me the 100 line block of code which is almost impossible to figure out.

>>59341719
Heartbleed was literally 3 lines.
3 fucking lines out of a couple hundred thousand.
Good luck m8

>>59341719
>hold my hand because i'm babby and don't know how git works

File: NO!.jpg (20KB, 500x426px) Image search: [Google]

20KB, 500x426px

>>59341719
>Give me an example of this. Show me the 100 line block of code which is almost impossible to figure out.

>>59341745
I have systemd cloned to my machine already. Tell me where to look. Point me to the line number with a github link. So far, every part of the code I've looked at has been pretty straightforward. I have no evidence to believe any of your claims unless you provide it. The burden of evidence is on you.

>>59341740
By your logic no project is auditable. Might as well stop using computers.

this things is so controversial
why is life so controversial everywhere

>>59341740
>openssl is only 3 lines of code

>>59341777
Yes some large projects are inevitably going to have zero days because, they are too large to audit correctly as fast as they are changing.
The solution however, is to stop making large projects without a VERY good reason for doing so.
Systemd did not have a good enough reason to justify it's existence.
Everything systemd has """"implemented"""" already existed. That includes cgroups, containers, socket activation. All of those can be done on sysviinit, and openrc and runit can do them too.
>>59341797
What? I think you need to retake English class Rajeesh.

>>59341719
>He thinks auditing means making sense of a piece of code, not going through the entire thing and almost mathematically proving that it works as intended.

It's IMPOSSIBLE to audit something without specs, documentation. Both of which are lacking in systemd.

It's also impossible to audit a moving target.

>>59341842
>The solution however, is to stop making large projects without a VERY good reason for doing so.
From a code auditing perspective, having a large project with modular design is functionally the equivalent to having many smaller projects to perform the same function. In the end it's still the same ballpark for number of lines of code.

>>59339615
>mfw I'm not crazy about systemd but also couldn't give a shit and most of people's complaints could have been fixed if they spent as much time contributing to systemd as they did trashing it
But fuck Poettering though. Fuck that nigger.

>>59341875
I already provided you a link with more than enough documentation. You are just too busy with your head buried in the sand to acknowledge.

>>59341875
So what you are saying is that you are unable to provide an example to backup the assertion you made. Got it.

File: jiFfM.jpg (78KB, 750x600px) Image search: [Google]

78KB, 750x600px

>>59341898
>"Tips and Tricks" documentation is equal to code documentation.

Nigger, how do you even possess the skills to turn your computer on?

>>59339615
sexual

>>59341948
>only 1 link is tips and tricks
>dozens of pages of developer documentation
>being this delusional
Just admit you are wrong. It's okay.

File: 7c3e0cef-8a08-4ef1-ab8f-d036bbaa165e.jpg.png (343KB, 600x258px) Image search: [Google]

343KB, 600x258px

>>59341965
Documentation for Developers

> Backports
> Presets
> systemd Optimizations
> Interface Stability Promise
> Interface Portability and Stability Chart
> Writing Password Agents
> PID1's Bus APIs
> On hostnamed
> On timedated
> On localed
> On logind
> On machined
> On importd
> On resolved
> Multi-Seat on Linux
> Writing Display Managers
> Writing Desktop Environments
> Writing VM and Container Managers
> Writing Network Configuration Managers
> Writing Resolver Clients
> Inhibitor Locks
> New Control Group Interfaces
> Cooperating in the cgroupfs trees (obsolete)
> Control Groups vs. Control Groups
> Writing syslog Daemons Which Cooperate Nicely With systemd
> systemd and Storage Daemons for the Root File System
> The Case for the /usr Merge
> The Container Interface of systemd
> The initrd Interface of systemd
> The Boot Loader Interface of systemd
> Implementing Offline System Updates
> Generators
> Minimal Builds
> Journal Export Format
> Journal JSON Format
> Journal File Format
> On /etc/os-release
> Journal Message Catalogs
> Testing systemd during Development in Virtualization
> systemd File Hierarchy Requirements
> systemd-boot EFI Boot Manager

All of the above is not code documentation. KYS, you don't even have a room temp IQ.

>>59341878
Maybe in theory. That doesn't account for different implementations.
Take cron for example.
We have the standard crond (vixie-cron), fcron, dcron and bcron.
dcron is probably the simplest, and fcron the most complicated.
Most people only need the functionality of dcron.
Some people need fcron.
Some people might even want bcron, for it's security features.
The key theme here is choice.
Systemd timers fail because either they are not good enough, and thus cannot be used (But you can't really disable them), or they do too much, and are a waste of disk space.
Dcron is remarkably easy to audit, because it stands on it's own, and it's small.
To audit systemd timers you have to look at more, because while they are """"modular"""" they are intimately connected with systemd core logic.

>>59342010
All the code I've looked at so far has enough comments for me to make sense of it. Maybe you are mentally challenged.

What's funny is that before all these threads I had very little opinion on systemd. But as I asked you to substantiate your claims and found you were unable to do so, I have started to grow to like systemd more. I have been forced to learn more about systemd in order to debunk all your invalid claims and as a result I have started to realize that it is actually pretty well designed.

File: 1459299919241.gif (500KB, 500x200px) Image search: [Google]

500KB, 500x200px

>>59342105
>anything from Lennart Poettering being well designed

File: notamused.jpg (20KB, 300x300px) Image search: [Google]

20KB, 300x300px

>>59342105
>it's another systemd shill saying "not a single valid criticism" episode

>>59342135
Every time you make this post without pointing to a specific valid criticism it just makes your case look bad.

>>59342151
Fair enough, here are some:
>>59339951
>>59339986
>>59340012
>>59340030
>>59340044
>>59340274
>>59340288
>>59340305
>>59340332
>>59340469
>>59340576
>>59340789
>>59341053

>>59342010
>he needs documentation to understand a code base
Hi brainlet!

>>59339951
>systemd was created by an SWJ faggot who works for RedHat
Literally do not care. Fuck off back to /pol/
>a company that is basically a CIA front
evidence please
>it was forced on all distributions almost overnight
please elaborate and explain what forced the maintainers of various linux distros to switch to systemd.
>PID 1
You have no evidence that running systemd makes it easier for a trojan to take over PID 1 compared to other init services. All init services run on PID 1 and you have the opportunity to separate the bulk of systemds functionality from PID 1 as has been stated repeatedly.
>systemd developers are making it harder and harder to not run on systemd
i dont care unless you convince me that systemd is bad first.
>making it more difficult for other init systems to exist
Other init systems felt very archaic and rough around the edges anyways. I don't know why you would prefer them
>
An example, suppose a project ships with systemd timer files to handle some periodic activity. You now need systemd or some shim, or to port those periodic events to cron. Insert any other systemd unit file in this example, and it’s a problem.
So far everything I've looked at has been modular enough that I believe you would be able to simply disable the components you do not want.

>>59339964
systemd doesn't really talk to the hardware like an OS

>>59339664
c struct > xml > plaintext > xml > c struct

>better

>>59339986
>People who don't like the fact that systemd has massive scope creep
Don't care. That's a purely subjective point and I don't even know if I fully agree with it.
>Lennart can be a dick
Don't care. I don't have conversations with the guy

If the init service is PID 1, what's PID 0?

>>59340012
This entire argument is irrelevant because you can run a different init system on PID 1 and keep the other parts of systemd that Gnome depends on.

>>59340030
I'm a power user and a developer and I haven't been negatively effected at all. Unless you have some actual data to provide, this is a dismissable argument

File: 41HMOpkLA2L._SX258_BO1,204,203,200_.jpg (15KB, 260x337px) Image search: [Google]

15KB, 260x337px

>>59339664
>destroying the obsolete unix
>obsolete
an hero please

>>59340043
>maddening popups

Where were you in the last 10 years?

File: not_valid.jpg (34KB, 380x508px) Image search: [Google]

34KB, 380x508px

>>59342325
>Werks for me
Not a valid argument

>>59342328
Posting a book from 35 years ago doesn't exactly help your case anon

>>59339615
modern gnu/linox

>>59342344
Neither is yours unless you provide data to support your claim

>>59342259
>fuck off to /pol/
You don't need to be a Nazi to see why SJWs are bad.
Even people like Eric. S. Raymond hate them.
>evidence
Vault7
>all init services run on PID1
Yep. That's why it's important for PID1 to be simple, and stupid. Systemd is NOT that, however.
>i dont care
Well at least you are not denying that.
>other init systems felt archaic
Examples? I can maybe see OpenRC, but the commands to interface with it are actually simpler than systemd.
With runit, the commands to interface with it are even simpler than OpenRC, and the service files are easier to write than systemd.
>you can disable the components
For systemd? No. For other projects? Depends on them. They have a tendency to bite the bullet and go with systemd, see KDE in a few years max.

>>59342284
>i don't care XDDD
Well good to know.
I do however. I am not the only one, as can be seen all around the internet.
You don't get to sink the ship because you feel like drowning yourself.

File: jackie-chan1.jpg (74KB, 630x370px) Image search: [Google]

74KB, 630x370px

>2017
>Falling for the anti-systemd fud.

>>59342371
>You don't need to be a Nazi to see why SJWs are bad.
That's not what I'm arguing. I'm arguing that your opinion that he is an SJW is both subjective and irrelevant. That does not affect me as an end user. I literally do not give a fuck what his political beliefs are. Again, fuck off back to /pol/
>vault 7
Point me to the specific evidence. The fact that you repeatedly pull this shit when I ask you for evidence only demonstrates that you have nothing.
>PID1
As has been stated repeatedly, you can choose to run another init system on PID 1 and keep the rest of systemds functionality on a different PID.

It's pretty obvious you're just ignoring whatever I say and spouting the same nonsense repeatedly so I'm actually going to exit now. Have fun shilling CIA nigger

>>59342387
>caring about the personal politics of people who contribute to open source software

>>59342371
>evidence
>vault7
Can you point out the specific document in Vault7 that exposes Redhat as a CIA front?

>>59342433
>irrelevant
Okay then.
>fuck off to /pol/
I am not from /pol/
>specific evidence
DanceFloor.
They can remotely compromise any Linux system.
We do not know exactly what DanceFloor is or how it works, but it is most likely the kernel itself, or systemd.
The fact that systemd has had shoddy security practices and was created by a company that sucks the NSA and CIA collective deep state cock, doesn't help its case.
When more vault7 is released, we will know more.
These are things people have suspected about systemd for a while now.
>run another init system on PID1
Yeah I'm gonna need a source on that.
Why would you want to anyways? Features like logind and journald need systemd on PID1 to work at any capacity.
>ignoring what I say
Yeah kind of like how I addressed all your points, where as you addressed half of mine.
Really makes you think.
>im leaving bye xddd
Okay then. One less CIA nigger and one more score for the good guys.

>>59342477
It wouldn't be that much of an issue if their politics did not affect open source, but they do.
They consitantly try to change and ruin the very things that made open source great, see "The Dehumanizing Myth of the Meritocracy".
Lennart isn't really a SJW in that sense however.
>>59342486
It's circumstantial at the moment. However it really makes you think.
Every single OS that was compromised for HIVE, was backed by a huge company with ties to the NSA.
>windows
Microsoft
>macos
Apple
>linux
RedHat

It's not that unreasonable to suspect RedHat as being a CIA front.

>>59342514
>Yeah I'm gonna need a source on that.

SYSTEMD(1)                                                                                                                      systemd                                                                                                                      SYSTEMD(1)

NAME
       systemd, init - systemd system and service manager

SYNOPSIS
       systemd [OPTIONS...]

       init [OPTIONS...] {COMMAND}

DESCRIPTION
       systemd is a system and service manager for Linux operating systems. When run as first process on boot (as PID 1), it acts as init system that brings up and maintains userspace services.

       For compatibility with SysV, if systemd is called as init and a PID that is not 1, it will execute telinit and pass all command line arguments unmodified. That means init and telinit are mostly equivalent when invoked from normal login sessions. See
       telinit(8) for more information.

       When run as a system instance, systemd interprets the configuration file system.conf and the files in system.conf.d directories; when run as a user instance, systemd interprets the configuration file user.conf and the files in user.conf.d directories. See
       systemd-system.conf(5) for more information.

>>59342514
>we don't know what DanceFloor is but or how it works but here's my baseless speculation on how it uses systemd as an attack vector
Thanks for admitting you're full of shit and have no idea what you're talking about

>>59342433
>That's not what I'm arguing. I'm arguing that your opinion that he is an SJW is both subjective and irrelevant
Totally, the leader of a co-optive project being an SJW has no bearing on the user at all. No like there's a hidden agenda to usurp the Linux kernel into corporate control or anything.

File: still_not_valid.jpg (40KB, 378x508px) Image search: [Google]

40KB, 378x508px

>>59342358
No that's the thing, systemd fucked up my day. I don't have to provide any data. That's a FACT.
Happened to a lot of people two.

You have two options:
a) We are all lying
b) You and your minority of SJW-systemd shills are lying

>>59342563
Huh, neat I guess?
It still runs as root for it's use case though, so it's not that much better.
Why would you want to run systemd without running it as PID1 if it's attack surface is still mostly the same minus causing a panic by crashing PID1? I don't see how that is useful.

>>59342560
>it's circumstantial at the moment
i.e. you're pulling speculative bullshit from your ass

>It's not that unreasonable to suspect RedHat as being a CIA front.
You don't even know what the word 'front' means you fucking tard. Unless Red Hat Incorporated was founded by CIA agents with the express purpose of backdooring Linux systems, it's not a front.

>>59342596
>moving goalposts

>>59342596
>expecting people to take you seriously when this is clearly your first time seeing any part of the man page for systemd

>>59342564
Nice strawman.
I know your a CIA nigger, but at least address my post fairly. It only shows people your true colors.
We know what DanceFloor does. It remotely compromises most Linux machines.
Now gee, I wonder what kind of software has the privileges needed to do that?

>>59342642
Dumbass, DanceFloor was established as a rootkit/exfiltration system, not a remote exploit.

You just keep showing that you don't really know what you're talking about

>>59339986
I'm in group 1 and 2.

>>59342601
I am not sure you understand how deep the governments involvement with the telecommunications industry is.
But in case you want to nitpick my word choice. I'll reword the statement.
It's not unreasonable to suspect RedHat as being involved with the CIA.
>>59342621
>>59342637
Well atleast answer the question. How else am I going to be convinced to use systemd :^)

>>59342753
>It's not unreasonable to suspect
Any specific evidence in the Vault 7 leaks hat you mentioned or were you just bullshitting?

>>59342753
>Well atleast answer the question. How else am I going to be convinced to use systemd :^)
I don't think anyone cares what you use

>>59340668
>That doesn't come close to making it unauditable. This point is completely invalid.

>>large attack surface
>Explain exactly the different ways you would attack it.
There has already been a single local exploit that brought the local system to its knees....long after it was "stable enough for production use".

>Explain what the flaws are
In the event of log corruption, systemd silently rotates the log out and your systemd-provided log tool will not decode it.

>Give me a specific example of how this affects me negatively
I would like to port this over to Windows please...wait, we can't anymore because it relies on a component of systemd.

>Systemd is not a single program
your reply is not even remotely related to the original point - which is, there is too much functionality packed into the portion of systemd that runs as PID 1. From this perspective, I don't care that it is multiple programs, I care that it has the least number of potential failure vectors in the code path.

>Depending on which Linux distro I was working with, I had to remember how to use it's respective selection for init services as well as other components which systemd now handles.
Before the shitstorm that was upstart appeared, there was only rc scripts. How the fuck could you screw that up?

>As a person who interacts with a variety of different linux distros regularly, it has made my life easier.
And yet, prior to all this shit, there was only one standard, and one way to light up a service. Which means your point is moot.

>>bluring userspace with kernel land
>Please elaborate. I'm genuinely curious about this.
Why do we need replacements for DHCP, networking, etc. etc. etc.

>>because top software layers depend on it
>Please elaborate. I'm genuinely curious about this.
Gnome is now building software specific to systemd. What does this mean for non-Linux installs?

>>59341693
Horseshit.
>what is s6 and s6-rc
>what is runit

>>59342807
Lennart does.
He wants it to be systemd.

>>59341777
Careful there, we don't want to around letting people know the truth...

>>59341777
>>By your logic no project is auditable
>what is the halting problem

>>59342795
Well apparently RedHat people were at the CIA, in a private talk session. Along with the "NSA's breifing on Windows 8"
Hmm. I wonder what they could be talking about.
Some topics mentioned:
Key Logger implementation considerations
Listening post communication protocols
Configuration files
Implant configuration & deployment mechanisms
Patchers
>wikileaks.org/ciav7p1/cms/page_14588038.html
We don't even have all of vault7 so a lot of things are still missing.

>>59342932
>confusing auditable and decidable
0/10

>>59342935
You are being dishonest, the page you linked specifically mentions 'Red Hat VMWare Briefing' and there's several other groups that gave talks, including some of the CIA's own internal divisions.

Not really any evidence that Red Hat were the ones giving talks on those subjects or that those subjects even pertained to Linux platform.

Stop with the FUD, faggot.

File: what is that.jpg (70KB, 625x369px) Image search: [Google]

70KB, 625x369px

>>59342010
>> On hostnamed
>> On timedated
>> On localed
>> On logind
>> On machined
>> On importd
>> On resolved
Jesus fuck what is that shit?

>>59342259
>So far everything I've looked at has been modular enough that I believe you would be able to simply disable the components you do not want.
Can I build only the components I want and ditch the rest?

No. Otherwise, udev would be stand-alone still.

Saying you can "disable what you don't want" isn't an argument for being modular; you're still locked into the same environment. This is a red herring.

>>59342935
NSA operation ORCHESTRA Annual Status Report

Most of /g/ is filled with shills.../g/ died around '14 or so...

>>59339951
yes !

fuck systemd, redhat, and the cia

good ol gentoo still ships with openrc, and you can run openrc natively pretty much on any distro, just replace sysd and config a few files in /etc/, and you are now officially closer to freedom and a step ahead in the game

fuck the system

>>59342972
Oh yes because the title of the talk is the only important thing:

>Red Hat VMWare Briefing (Norman St. Laurent [email protected]) Red Hat

RedHat is CIA connected and now they control init on Linux. If that doesn't scare you, I don't know what will.

>>59343342
>I don't know what will.
Some verifiable evidence that they have done anything to compromise the security of Linux

ITT: People who lack the knowledge to use a system with systemd troll.

>>59343370
>Some verifiable evidence
Suspicion is enough you fucking shill. This isn't a court room. People are making decisions that can affect their privacy. A CHANCE of failure is enough to avoid some things.

>>59343413
>Suspicion is enough you fucking shill.
Only for retards who can't into the scientific method

>>59343424
Scientific method only applies to scientific experiments/theories, not for human/technological interaction you fucking autistic retard.

>>59343446
Incorrect. The scientific method applies whenever making the decision of whether or not to believe an assertion.
You are proposing a hypothesis. Unless you can demonstrate that it is a theory rather than a hypothesis, it is illogical to believe it is true.

Fucking retards in this thread...

File: 1488928322407.jpg (130KB, 1024x891px) Image search: [Google]

130KB, 1024x891px

>>59340654
>>59340352
>hating systemd has become a meme
>a very dangerous meme
I've got 2 words for you: meme warfare
http://www.dtic.mil/dtic/tr/fulltext/u2/a507172.pdf

File: 1489095010775.jpg (24KB, 810x456px) Image search: [Google]

24KB, 810x456px

>>59342335
>the current state of Windows

>>59340005
You can avoid systemd altogether if you use Gentoo.

>>59340012
>you can't run GNOME without systemd these days
This is why I use Cinnamon.

>>59343463
Yeah no, why would I take a chance with my privacy? It's my choice. I don't need to have 100% proof that they are in bed with the government to not trust them and even if I did you shills would find some way to tell me I'm wrong.
The worrying thing is that my choice to not take a chance with my privacy is somehow wrong and that I should just trust RedHat.
Really makes you think.

>>59340654
>>59340352
>it's another shills projecting episode
No one is advocating to use Windows or Mac.
Why should I use systemd? Why is it so asinine of an idea to want to use a different init?
There are many valid reasons to not want to use systemd.
You faggots are either arch babbies who can't into UNIX, paid RedHat shils, or CIA niggers.
Fuck off, everyone sees through your shit.

>>59343550
This. The null hypothesis is always 'you don't have all the proof you need to act' with these shills.

It just makes them terribly obvious. Their shilling needs to be more subtle to work, but they're not likely to change.

File: 1489026793365.png (735KB, 750x850px) Image search: [Google]

735KB, 750x850px

>>59343463
>Incorrect. The scientific method applies whenever making the decision of whether or not to believe an assertion.
Oh you're totally right, that's why the scientific method is used in the court room to determine if someone is a murderer.

WRONG.

Fucking autistic RETARD kill yourself NOW.

>>59340274
>>59340288
B I N A R Y L O G S
I
N
A
R
Y

L
O
G
S

>>59343620
Court cases absolutely do require verifiable evidence you fucking retard

>>59343550
By this reasoning you should distrust literally all software unless you have personally verified that it is trustworthy. Obviously this is a dumbshit position to take, as nobody has the time to scour the source code of literally all software they use.

>>59343744
binary logs make indexing and searching faster.

>>59339615
So, I still use systemd but I had Manjaro kde installed on my laptop and after being on for awhile it would crash. Turns out what was happening was, kde's Baloo was trying to index files but it reached a limit, and spammed like 5000+ errors to Journald within a second causing Journald to crash which caused systemd itself to crash, which of course froze the laptop and had to be hard shut down.

This happened everyday for a week while I was trying to figure it out.

File: c3ea5fc32f2ced5f2be65d2a2069251fde4e0197a263668c367204d71f82cfbb.jpg (40KB, 1280x720px) Image search: [Google]

40KB, 1280x720px

BEHEAD THOSE WHO SPREAD SYSTEMD

>>59343936
I bet you uncovered one of the CIA's buffer overflow exploits to get root access through journald

>>59343870
>verifiable evidence
Not the scientific method you insufferable moron.

>>59343936
This same thing happened to a friend of mine as well. System totally froze, was close to impossible to get a meaningful backtrace.

>>59343879
If you care about privacy, yeah you should probably do this in principle. Pragmatically speaking, you should distrust software that you have reason to distrust. I have no reason to suspect the GNU coreutils as being involved with the CIA.
RedHat software however...
>>59343887
And then what happens when it's corrupted?
The very marginal difference in performance is not worth the loss of flexibility and robustness of simple text files. If it's absolutely imperative, a better solution is to use some sort of markup for the log files to make searching easier.

>>59344031
It literally is just the scientific method minus any steps where experiments are performed. The equivalent of experiements in this scenario would be any pre-trial investigation/gathering of evidence to be used in the trial
At the end of the day you are making a bullshit argument to get out of providing verifiable evidence of your claim.

>>59344063
>And then what happens when it's corrupted?
The same thing that happens if any log gets corrupted. Are you brain damaged?

>>59344083
Its a binary format. Depending on how bad it is, journald has to discard more of the file. I don't think you understand how that works. If a text file is corrupted it can only fuck up the specific part that was corrupted, the rest of the file would be fine.

>>59344043
>>59343936
>>59343744
>>59343620
samefag

>>59344119
That is also true with the binary logs. There are a number of command line tools you can use to analyze binary log files even when they are partially corrupt.

File: Screenshot_20170311_003825.png (10KB, 342x132px) Image search: [Google]

10KB, 342x132px

>>59344123
>regular fag

>>59344136
I am not so sure about that. The order of the binary data is much more important in the journald logs. It's easier to fuck up.
Why would I want to have to use tools to analyze binary log files when I could just use a text editor on normal logs?

>>59340005
Alpine Linux, Void Linux, Devuan, Slackware, Funtoo, Gentoo.

>>59344083
>It literally is just the scientific method minus any steps
You clearly have no idea what the scientific method is.

The scientific method doesn't prove anything is right, it can only prove if something is wrong. Go read some Karl Popper once you pull the systemdildo out of your ass.

>>59344270
>Alpine

>>59344290
>systemd

>>59344341
>implying I'm somehow shilling for systemd
busybox is for cucks

>>59344288
>The scientific method doesn't prove anything is right
I never said it does (and also you are wrong, because once you eliminate all possible explanations except for one, you have proven that explanation). Any man of science will require that their beliefs be the known theories with the most verifiable evidence supporting them. Anything less is literal stupidity.

>>59344359
Care to elaborate friend?

>>59344517
using busybox is like letting your wife get dicked by tyrone

>>59344544
And the GNU coreutils is like letting your girlfriend (male) peg you

File: 1487216994010.jpg (90KB, 526x701px) Image search: [Google]

90KB, 526x701px

>>59343887
If only there was some way we could have easy to read plaintext logs and a way to index them quickly. If only we had some kind of index file or something.

>>59344083
>It literally is just the scientific method minus any steps where experiments are performed.
...which isn't the scientific method. You sound like an obnoxious internet atheist. Some places we don't use the scientific method; math, court systems, design of large systems, philosophy, medicine. We'll develop tools and test components of these systems, but we don't actually use the scientific method for the final decisions. Your doctor isn't prescribing you Viagra because he cloned you and checked that it would make your dick hard. Those engineers don't built a to scale test bridge first before building the real bridge. The court system isn't recreating the situations that caused the crime so they can observe it again.

File: vlcsnap-2016-10-05-02h24m18s226.png (434KB, 1280x720px) Image search: [Google]

434KB, 1280x720px

>>59344288
Woah, Karl Popper?! Did he the guy who done self substantiation?

>>59344544
you're an urban retard

Is it a shill tactic where they take some irrelevant part of your post and nitpick it to death, meanwhile ignoring the actually relevant parts?
Really activates the almonds.

Install Gentoo and be free.

https://sharpencryptedpig.noblogs.org/post/2014/05/29/how-to-install-gentoo-hardened-with-encrypted-root-and-swapexpress-procedure/

>>59345156
Page 500s on me.

>>59345186
use the internet archive you dumb cow

what are some good distros for an old pc?

>>59344393
>because once you eliminate all possible explanations except for one, you have proven that explanation
Except it doesn't work that way in real life only in an abstract world.

t. Physicist

btw systemd sucks and you guys should kill yourselves for supporting it. I had to switch our systems from CentOS to Slackware just to retain all the init modifications we need to do real work. Fuck you a million times.

>>59346884
>to retain all the init modifications we need to do real work
like what?

>228 / 50 / 38

Makes me think.

>>59345107
I'm half-convinced Poettering makes these threads himself just to shill

>>59347128
>implying he cares about the useless shitheads ranting about software

>>59346723
http://cdimage.ubuntu.com/netboot/16.10/

sudo apt install openbox tint2 pcmanfm gpicview lxappearance lxterminal xorg-xinit

>>59347257
thanks

>>59347148
Yeah cause that's why he got so butt hurt about people saying mean things to him.

systemd is 4chan

>>59347041
When you're running custom hardware nothing autists at redhat can anticipate the kind of driver loading/reloading you need to do on startup and on the fly.

We just don't need systemd's kitchen sink philosophy where we work. Scripts are useful for a reason.

I fucking hate how children are running the show in Linux now. Will likely have to move to FreeBSD once they can get CUDA working on it.

>>59346884
Systemd is backwards compatible. You can use your init scripts.

>>59349339
>>>59346884
>Systemd is backwards compatible. You can use your init scripts.
How because the cleanning sda shit message at every startup is annoying

>>59349445
I think you install systemd-sysvand then use sysv commands.

>>59339964
>>59339649
I don't understand. It's bad because it does all the things? At the very least that just makes it especially critical to keep secure but what's the problem here?

>>59349855
Systemd has such a large and new code base, it theoretically has more vulnerabilities than what it replaced.

>Not locking your units down to absolute minimal privileges with ProtectSystem PrivateTmp, PrivateNetwork, PrivateDevices and all their suboptions
Way too ez.

I bet most of your hacked together init scripts run shit as root.

>>59339615
intellectuals

Can someone give me a quick run down on who OP's pic is?

>>59352116
The reason this thread exists

>>59352116
Sjw cuck that helped shove systemd up all our arses so the cia has an easier go of it when attacking our the systems

File: ainsley.jpg (10KB, 200x226px) Image search: [Google]

10KB, 200x226px

>>59341178
>Sauce on trap ?
redditor

>>59341178
>he reason it gained so much steam and clout is due to the hidden influences of the State(s).
CIA-RedHat connection is now demonstrated thanks to Vault7.