[Boards: 3 / a / aco / adv / an / asp / b / bant / biz / c / can / cgl / ck / cm / co / cock / d / diy / e / fa / fap / fit / fitlit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mlpol / mo / mtv / mu / n / news / o / out / outsoc / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / spa / t / tg / toy / trash / trv / tv / u / v / vg / vint / vip / vp / vr / w / wg / wsg / wsr / x / y ] [Search | Free Show | Home]

>use systemd and boot with systemd-boot >lightening fast

This is a blue board which means that it's for everybody (Safe For Work content only). If you see any adult content, please report it.

Thread replies: 387
Thread images: 24

File: systemd-logo.png (63KB, 480x277px) Image search: [Google]
systemd-logo.png
63KB, 480x277px
>use systemd and boot with systemd-boot
>lightening fast boot, everything works as it should and efficiently
>this is something we're supposed to avoid in Linux

Fuck the luddites, systemd is what'll bring about the year of desktop LInux.
>>
>>57094507
Systemd won. Is there anything really left to argue on?
>>
>>57094507
This post.
The pinnacle of your worthless life.
Admit it.
>>
I'm 100% sure there is a backdoor there
>>
>>57096640
ok thank you for your opinions

can you reference an audit or particular bug which supports your theory?
>>
>>57094507
>>lightening fast boot
sure thing pal
>>
>>57096662
I can't read code but the Gentoo forum people assure me systemd has an NSA backdoor in it.
>>
>>57096662
>Be NSA
>Try to backdoor linux kernel
>Fail
>Try to convince Linus to put a backdoor in the kernel
>Fail
>Give up on PID 0
>"PID 1 is good enough"
>"Hey, we know Redhat right"
>Ask them to put a backdoor
>???
>NSA approves systemd
>>
>>57094507
https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish
>>
>>57094519
NSA won
>>
>>57096711
>Embrace: Development of software substantially compatible with a competing product, or implementing a public standard.
>Extend: Addition and promotion of features not supported by the competing product or part of the standard, creating interoperability problems for customers who try to use the 'simple' standard.
>Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support the new extensions.

wow that sounds familiar, but Red Hat wouldn't have anything but the Linux community's best interests at heart right?
>>
>>57096740
Do you miss udev on Slackware? :)))
>>
>>57096835
Not him but i dont.
>>
>>57096905
Irony was where the Ironians live.
>>
https://muchweb.me/systemd-nsa-attempt

>Ignoring for the moment the various technical problems with systemd, I have my suspicions that its provenance and scope are cause for alarm.

>Systemd comes from Red Hat. Red Hat, in the Linux world, is the company with the largest ties to the US government and the various state security organizations around the world--including NSA. The US government (DoD) is Red Hat's number one customer. Red Hat also happens to be Lennart Poettering's employer.

>The Linux kernel, I believe, is clean. As long as Linus lives, you're not going to subvert the kernel. Let's just assume that is true for the sake of argument. If you can't get into the kernel, what is your next option? You need something low level (PID 1?), ubiquitous, and vast in scope and complexity.

>This describes systemd perfectly. It was almost like it was designed to touch as much of a Linux system as possible. It has hooks into some many different subsystems and APIs that it's almost impossible to build a modern distro with current software without pulling in systemd as a dependency. This happened almost overnight, and I think there are malicious forces at work here.

>We must remember Heart Bleed. Heart Bleed appeared to be an innocent mistake, and it was a tiny typo in one line of a C program. If it's possible to do that much damage with a tiny little error, imagine when you have an attack surface as wide as systemd, written in a language like C that is almost designed to produce security holes when not written absolutely perfectly--and humans are not absolutely perfect programmers.

>Systemd is dangerous. It's too big to be audited as quickly as its developed. It's complexity adds as much attack surface to a Linux system as the kernel itself. We can't get away from these facts. Shitfighting about init systems is a waste of our time. Sytemd is horrible because of where it comes from and how complex it is. Backdoors will be hidden in it.

Enough said.
>>
>>57097127
Then why does Linus approves systemd?
>>
>>57097204
>approves
afair hes not against it
>>
enjoy your botnet
>>
>>57094507
B O T N E T
O
T
N
E
T
>>
>>57096689
>anti-systemdfags in a nutshell
>>
>>57096689
That assurance is meaningless without a source. It's all open source so show me that code.
>>
>>57097777
quads of logical thought
>>
>>57096711
Systemd GPL3 software. You can't EEE GPL software because it's always possible for people to change anything they need at any time they want.
>>
>>57097127
>systemd comes from red hat
>the gubmint is a customer of red hat
>the gubmint is illuminati
>systemd is illuminati confirmed
>>
>>57097777

Bash, openssl. Both had the source out there but still backdoors for years.
>>
>>57097843
That's because people assumed it was fine. This is a normal assumption to make. If you want to prove that there are backdoors, the source is right there for you to find it and tell us. As soon as someone makes it public, it will be fixed ASAP.
>>
>>57094507
What about that bug that just came out that allows any user account to crash the entire system with a single command line? I'm going to stick to Slackware, it's stable, secure and fast.
>>
>>57098008
It only affected people using development versions of Systemd. There's no problem for the vast majority who use official releases.
>>
>>57097777
Show me that there's no backdoored code.
>>
>>57098028
I'm going to stick to a distro that is know for it's stability and security. Not one that runs something known for being insecure.
>>
the aggressive and constant shilling, which, despite the age of systemd, is a recent occurrence, makes me suspicious

furthermore few distros give you any choice in the matter, making shilling on the user end unnecessary, except, notably one: gentoo, a distro popular on this board

one more thing
having tried both, and having used systemd for over a year, I find openRC comparably fast in boot times and far more reliable
>>
>>57097343
do you even know what a botnet is you retarded autist?
>>
>>57098035
Prove to me you're not a child rapist.
>>
>>57098051
>the aggressive and constant shilling, which, despite the age of systemd, is a recent occurrence, makes me suspicious
I agree

>furthermore few distros give you any choice in the matter, making shilling on the user end unnecessary, except, notably one
Slackware doesn't use systemd.
>>
>>57098052
It's a shitposter. Please try to not dignify the shitposters with any response. If you can't help that, it's better to respond with shit of your own like "no u" or "faggot" or "smug anime girl.jpg"
>>
>>57098059
Not an argument.
>>
>>57098071
Slackware is considered a minor distro by virtue of its Distrowatch download numbers. Therefore, Slackware doesn't count as much as Gentoo.
>>
>>57098092
Slackware is the oldest standing linux distro. It's also well known despite it's smaller userbase so don't give me that crap.
>>
>>57098091
ditto
>>
> If it's possible to do that much damage with a tiny little error, imagine when you have an attack surface as wide as systemd, written in a language like C that is almost designed to produce security holes when not written absolutely perfectly--and humans are not absolutely perfect programmers.

Sounds like the problem is C.
>>
>>57098100
Says the NSA agent
>>
>write init system in C
>call it systemD
>C
>D

Lenerd you're a fucking idiot.
>>
>>57098098
Distrowatch lists it has a major distro you dumbshit.
http://distrowatch.com/dwres.php?resource=major
>>
>>57098098
Its age has no bearing for how major or minor it is. Things that matter are the direct community activity and the download numbers.
>>
>>57098156
Distrowatch disagrees see:
>>57098147
>>
>>57098156
How is a distro listed in the top 10 distributions small?
>>
>>57098147
no u

>>57098169
I guessed wrong
>>
>>57098178
no u
>>
>>57094507
So reading this thread it seems that the only thing wrong with systemd is conjecture?
>>
>>57098071
arch can also live without it with a few things from the aur
>>
>>57098230
Exactly. No one is stopping conspiracytards from using slackware or Gentoo
>>
>systemdoor
backdoor

prove me wrong
>protip
you can't
>>
>>57098230
Certain agencies have been pushing it real hard.
>>
>>57098327
There is no backdoor in systemd. Prove me wrong.
>>
>>57098374
links to said pushing?
>>
>>57096700

>pid 0
You don't really know what you meant with PID 0, do you?

>average g poster and the person you're talking to on here
>>
>>57097843

Where is or was the backdoor in Bash?
>>
>>57098141

D (100) is 1 better than C (99). You're also on /g/, so you probably prefer the D too.
>>
>>57098141
the d stands for daemon, fool
>>
>>57098446
*demon
>>
>>57098488
https://en.wikipedia.org/wiki/Daemon_(computing)
>>
>>57098501
your point being?
>>
>>57098509
That your spelling it wrong, retard.
>>
>>57098537
actually it appears that you are the retard here.
>>
>>57097127
Sorry, going to need something logical - like proof - rather than conjecture.
>>
Gnome3 OpenRC master race.
>>
>>57098092
Slackware is ranked much higher than Gentoo dumbass. It's very close to arch linux.
>gentoo is 33
>Slackware is 15
>arch linux is 10
>>
>>57098697
>ranking solely based on page views
now how exactly is that representative?
>>
>>57098752
More people are looking for arch linux and Slackware than Gentoo. Clearly it's more popular and more people know about it and want to install it.
>>
>>57097293
If he's not against it it means he doesn't think is bad
>>
There is incredibly high chance there is a backdoor in there. Just because it hasn't been found yet, doesn't mean it doesn't exist. If you want to go against the odds, then use it as you will.
>>
>>57094507
>tfw still using grub
my boot manager is something I'm NOT willing to replace for experimental code
>>
>>57099226
>newfag redditor can't even tripcode properly
>>
I hope these systemd shills enjoy when Lennard and his gang make GNU/Linux into something like Windows, by adding unecessary complexity.

The root problem on systemd is that they don't know what systemd really is. Every once in a while they throw more unecessary crap into the project. YES unecessary, there still some great code that worked in the 70's that still works perectly in the 2010's.
>>
>>57097843
The fact that I can link you to the source code of the Bash and OpenSSL vulnerabilities is enough to demonstrate that if it's vulnerable, you should be able to point out the vulnerable lines of code.
>>
>>57098008
If you copy/paste “:(){:|:&};:” into your terminal you can take down a system as any running user as well

Does this mean you should uninstall bash?
>>
>>57099412
You do realize there are alternatives right?
>>
>>57099412
Why would I install another compromised buggy pos just because another one is as well?
>>
>>57099369
>The root problem on systemd is that they don't know what systemd really is.
This. It reminds me of windows click-select functionality.
>>
>>57099412
I just tried it in Slackware and my system is still up.
>>
File: 1476513714088.webm (2MB, 1366x768px) Image search: [Google]
1476513714088.webm
2MB, 1366x768px
>>57098008
Fuck off
>>
>>57099479
Slackware is p. great
>>
>>57099484
Nah, I'm sticking to slackware. I like stable and secure distros
>>
>>57097127
>>We must remember Heart Bleed. Heart Bleed appeared to be an innocent mistake, and it was a tiny typo in one line of a C program. If it's possible to do that much damage with a tiny little error, imagine when you have an attack surface as wide as systemd, written in a language like C that is almost designed to produce security holes when not written absolutely perfectly--and humans are not absolutely perfect programmers.
So what you're saying is: "Nothing has changed."
>>
>>57099499
Slackware devs won't fix your gtk bugs, it's not a magic
>>
>>57098008
What I love about Slackware is that it's very vanilla. Other distros like Debian modify their packages and result in distro specific bugs like with this one Debian only ssl bug from a few years back.
>>
>>57099511
Why would I switch to something even more buggy and less secure just because it isn't perfect? It's not perfect but it's still one hell of a lot better. There will always be bugs and security issues. Just some don't have as many as distros with systemd.
>>
>>57099511
They just won't patch in unstable new shit that's known to be broken.
>>
>>57098420
Shellshock
>>
http://0pointer.de/blog/projects/the-biggest-myths.html
>>
>>57099526
I wish that Kali linux distro was built off of slackware instead of debian it would make so much more sense.
>>
>>57099529
>more buggy
How is it less buggy? Slackware is vanilla, they are out of devs

>>57099532
They won't patch anything
>>
>>57098446
Systemd confirmed for satanic ritual
>>
>>57099553
>I wish that Kali linux distro was built off of slackware instead of debian it would make so much more sense.

neo-/g/ everybody
>>
>>57099511
It's not Slackware's fault something is broken upstream and the gtk devs can't or won't do something about it.
>>
>>57099553
don't hax me bruh
>>
>>57099563
So you admit Slackware won't fix your bugs in packages
>>
>>57099573
>fix bugs
The don't even have enough devs to implement dependency resolve
>>
>>57099557
>How is it less buggy?
By having less bugs. Its know as the most stable and secure linux distro for a reason. They don't release shit until it's actually done.

>They won't patch anything
They just released a new version of slackware in july.
>>
>>57099557
if you need a patch you can make it yourself. the sbo community does this, AlienBOB does this (sometimes). but you shouldn't need patches for all your major software to make it compliant with your system.
>>
>>57099562
>>57099564
You do realize that it was make for professional pen testing which pays very well? One of the top pen testing cert providers requires you to use it but it's fucking pain in the ass.
>>
>>57099573
Slackware is supposed to be vanilla, as in completely unmodified packages. It's your choice to apply unofficial patches. But I'm warning you, modifying upstream can result in bugs and exploits that vanilla packages don't have.
>>
>>57099607
I haven't had any issues with the vanilla packages anyways. Everything I want to run on SlackWare just werks.
>>
>>57099590
>implying slackware users are too dumb resolve their own dependencies
>implying sqg and slapt-get don't exist
>>
>>57099590
Slackware doesn't want dependency resolve. Install a package manager like slapt-get if you want automatic dependency resolution.
>>
>>57099604
Yeah the guy complaining the Kali devs should switch to Slackware instead of Debian as a base is FOR SURE a pentester.
>>
>>57099594
>>57099607
The fuck are you talking about? Are you implying all these bugs don't apply for slackshit?

https://bugs.freedesktop.org/buglist.cgi?quicksearch=xorg

>>57099620
Do you need a special snowflake award?
>>
>>57099573
It's not a distros job to fix upstream bugs, it's to oh idk, distribute fucking software.
>>
Ponder this a moment:
Perhaps the anti-systemd shills are in fact pro-NSA. Now hear me out on this, I know it sounds crazy. When did the NSA start it's mass-surveilance program? That's right, pre-systemd. Now, if you had established backdoors in Linux, how would you feel about it if suddenly, practically overnight, you had those backdoors taken away? You get it? The fucking argument can go both ways!
>>
>>57099590
That's not from a lack of devs it's a development choice.
>>
>>57099623
>Slackware doesn't want dependency resolve
can't have, because they lack devs. It's their FIRST official excuse
>>
>>57099634
There's also like six different package managers you could use that have dep resolution. Fucking slapt-get has it. My own motherfucking homebrew autoslackbuild script has it.
>>
Also what dependencies are there to resolve when the DVD has pretty much everything you need?
>>
>>57099625
Not a single person is claiming it doesn't have bugs. Are you thick?

>>57099625
Kali is a buggy piece of shit that doesn't even install properly half the time. Slackware is frequently used as a base for other Distros. State your reasoning for him being wrong?
>>
>>57099640
Doesn't want.
>>
>>57099658
>frequently used
*was* frequently used anon, back in the day.

Though at work I saw our coffee machines reboot, and they were fucking running SLAX, I lol'd pretty hard.
>>
>>57099626
Those are upstream bugs, not Slackware specific.

>>57099640
It has nothing to do with lack of devs. They don't want nor do they need automatic dependency resolve. They like the simplicity of you resolving dependencies on your own. It's really not that hard.
>>
>>57099626
no, but I'm nominating you for a lifetime achievement in shitposting medal.
>>
>>57099668
Still is. There is even an ARM version of it now.
>>
>>57099668
I want a coffee machine that can run Slax :(
Also name another major distro that can run virtually unmodified on a toaster.
>>
>>57099667
>>57099670
First in the list, faggot
>Automatic dependency handling requires constant manual developer maintenance, and adds potential for dependency hell.

>>57099670
What the fuck was about Slackware being bug free and stable then?
>>
>>57099702
Them stating that doesn't mean it's the main reason.

>>57099702
>What the fuck was about Slackware being bug free and stable then?
Slackware does have less bugs. Those were also upstream bugs you linked to. Slackware has a well earned reputation for being the most stable and secure.
>>
File: 1476016365112.png (411KB, 500x503px) Image search: [Google]
1476016365112.png
411KB, 500x503px
>Slackware
LMFAO luckily I'm not a NEET to worry about that piece of crap
>>
>>57099717
It's a popular IT distro. What are you on about?
>>
>>57099711
>Them stating that doesn't mean it's the main reason.
It's their FIRST excuse for a reason, stay in denial if you want
>>
>>57099711
>Slackware has a well earned reputation for being the most stable and secure.
Stable? Sure, because it doesn't have a package manager so you basically can't update your system

Secure? No, because it doesn't have a package manager so you basically can't update your system
>>
>>57094507
It's 2016 and systemd has yet to make linux popular so can we go back to SysV now?
>>
>>57099728
No it isn't.

>>57099737
It has a package manager and you can update your system. Try again.
>>
>>57099702
>Automatic dependency handling requires constant manual developer maintenance, and adds potential for dependency hell.
They're saying it's easier for both developers and users to not have automatic dependency resolve. Fucking Debian has recommended packages as a dependency, resulting in many packages you don't really need being installed when you only need 2.

>What the fuck was about Slackware being bug free and stable then?
That was just one guy who was wrong. Nobody else here thinks Slackware is bug free, but it's definitely quite stable.
>>
>>57099226

Which distribution are you using?
>>
>>57099743
>N-No it isn't
Cry harder NEET
>>
>>57099745
>That was just one guy who was wrong
I didn't claim it was bug free he's just twisting my words.
>>
>>57098052
>>57098082
fuck off systemd shills
your botnet will not consume me
>>
File: 1475029071590.jpg (46KB, 496x478px) Image search: [Google]
1475029071590.jpg
46KB, 496x478px
>>57099745
>>57099755
>Doesn't have less bugs than other distros
>Doesn't fix any bugs
""""STABLE""""

hahaha fuck off
>>
>>57099369

>unecessary[sic] complexity
Getting things to work more easily and robustly is unnecessary complexity. Totally.

>The root problem on systemd is that they don't know what systemd really is.
It's funny, because you don't know what systemd really is. Are you really that dense to claim that the creators of it don't know what their creation is? Its goals are clearly defined. If you cannot comprehend that then you're an idiot.
>>
>>57099702
Slackware has very minimal and efficient system utilities. It also does not rush to incorporate the latest versions of everything. The job of a distro is a) choose which versions of which software to include; b) create basic system setup, configuration, and management utilities. For (a), only using stable and tested upstream releases ensures quality, not adding tons of patches to it ensures that no new bugs pop up. For (b), Slackware has a very clean installer, package management scripts, configuration scripts, etc. They have also remained virtually unchanged in decades -> stability.

>>57099737
# slackpkg update
# slackpkg install-new && slackpkg upgrade-all
>>
>>57099752
>adding in a stutter
Okay pal, it's clear who the NEET is. They have listed their reason for not adding it multiple times. A quick google search will show you the technical reasons for not having it.
>>
>>57099737
It has a special package manager that only updates the system.

Anything else you want to install you have to do it manually because there are no repositories. You basically just wget everything from the slackware site or find the source yourself and build it that way.
>>
>>57099775
>shit you pulled out of your ass
Nice try. Between the twisting of people's words and pulling shit straight out of your ass it's clear you have no intention of arguing in good faith.
>>
>>57099784
>Anything else you want to install you have to do it manually because there are no repositories. You basically just wget everything from the slackware site or find the source yourself and build it that way.
That sounds fantastically secure and stable
>>
>>57099542

You're really stupid, aren't you? I suggest you look up the definition of backdoor and compare it to a bug.
How do you feel no shame in spreading your idiocy on here? It's a technology related forum, surely you're smart enough to realize that other people are going to call you out on your stupidity. What do you get out of your attempts to pass off your wrong knowledge as the truth?
>>
>>57099658
>Slackware is frequently used as a base for other Distros.

Slackware-based distributions:
https://en.wikipedia.org/wiki/List_of_Linux_distributions#Slackware-based

The only Slackware-based distribution even worth mentioning is Slax, which isn't anything special nowadays. Slackware is dead and so are it's derivatives.

Meanwhile, here are Debian-based distributions:
https://en.wikipedia.org/wiki/List_of_Linux_distributions#Debian-based

>State your reasoning for him being wrong?

What he said:
>I wish that Kali linux distro was built off of slackware instead of debian it would make so much more sense.

Kali doesn't have a lot of resources, it makes much more sense to use a distribution that is known for offering a good base system, is well tested and is easy modify and distribute than using a distribution offers almost no benefits, such as Slackware.
>>
>>57099777
>It also does not rush to incorporate the latest versions of everything.
Debian stable

Remaining unchanged for a century and calling it stable is laughable

>>57099783
lmao NEET is mad
>>
>>57099752
It does have a package manager. Pkgtools for a downloaded package and slackpkg for installing from repo over a network. You can even use slackpkg+ and slapt-get for third party repos like alien bob or SBotools for anything off slackbuild.org
>>
ITT: systemd shills in full defense mode
>>
File: slackpkg+.png (11KB, 760x616px) Image search: [Google]
slackpkg+.png
11KB, 760x616px
>>57099784
>no repositories
>>
>>57094507
Go away lennart
>>
File: 73426-thorhammer.jpg (2MB, 4008x2220px) Image search: [Google]
73426-thorhammer.jpg
2MB, 4008x2220px
>>57099738
Or fuck, can we just go to Upstart, or anything else that doesn't try to be a sudo, a logging system, a boot manager, a baker, a potter, and a fucking candlestick maker?

Like

I want my init system to manage my processes, I don't want it giving me a fucking rimjob.
>>
I swear Lennart Poettering or some other systemd dev comes to /g/. There's a massive systemd shill here who is somewhat recognizable through his writing style that gets into arguments.in these threads all the time.
>>
>>57099784
>>57099801
There are repositories. Slackbuilds.org for example. There are others as well. I mostly use slackbuilds though.
>>
>>57099800
>twisting words
So are you saying it's ""stable"" with all those same bugs I'd have to experience with other distros?

0/10
>>
>>57099813
Theres not much in them though and isn't alien like a 3rd party repo?
>>
>>57099604

You sure like your epic sounding l33t words like "pentester" don't you?

>someone has such an advanced and niche job
>doesn't know how to install the tools he uses
>needs it to be provided for him

Only cringe-worthy idiots like you would believe that nonsense.
>>
>>57099831
More often than not, deviating from upstream results in bugs only your distro is vulnerable to.
>>
Slackware package managers, many of them!

https://github.com/dslackw/slpkg
https://github.com/megous/spkg
https://github.com/rg3/slackroll
https://github.com/brokenman/usm
https://github.com/MyRequiem/spman
https://github.com/wargarblgarbl/autoslack
>>
>>57094507
>this is something we're supposed to avoid in Linux

No one's saying that. The point is that some people want a choice between the old init system and systemd. systemd is quickly assimilating a lot more than just typical init processes - it's becoming a pervasive dependency that's required to do virtually anything with your Linux box.

The goal of the project is not simply to replace init with something more efficient, but to force the systemd standard on the entire Linux community, thereby limiting the scope of your freedoms.
>>
>>57099726

>IT distro
Nice buzzphrase. Does it scale?
>>
File: 1445876025075.jpg (274KB, 1414x965px) Image search: [Google]
1445876025075.jpg
274KB, 1414x965px
Daily reminder than systemd is NSA botnet trying to take over GNU/Linux
>>
>>57099852
Which is why you use one of the many vanilla distros
>>
>>57099807
There is Zenwalk, Salix, Porteus, and VectorLinux for desktop distros based off of slackware. Slackware also now has a lightweight arm distro that is great for embedded systems. Nice try though.

>sense to use a distribution that is known for offering a good base system, is well tested and is easy modify and distribute
Literally Slackware. What it is known for. Please give a good reason next.
>>
>>57094507
>desktop LInux.
Never happening.
>>
>>57099808
>lmao NEET is mad
You are getting extremely defensive.
>>
File: 1475283026205.jpg (71KB, 659x553px) Image search: [Google]
1475283026205.jpg
71KB, 659x553px
>>57099859
Get out tinfoil loser neckbeard
>>
>>57098035
Sure. The source is all available and there's obviously no back door there. Prove me wrong.
>>
>>57099858
But is it *webscale*?
>>
>>57099845
>One of the top pen testing cert providers requires you to use it
Only cringe-worthy idiots like you would spew shit without reading what he actually posted.
>>
File: 1456684279840.png (121KB, 1140x521px) Image search: [Google]
1456684279840.png
121KB, 1140x521px
>>57099885
enjoy no games
>>
>>57099884
Hit a nerve, didn't I?
>>
>>57099831
It is stable. It's known for it's stability as well. Software has bugs that's a fact of life. Most of the bug in slackware will only come from something that you do. And it still has less than any other distro.
>>
>>57099858
I work at an actual IT department and we use ubuntu on hundreds of servers and machines
>>
>>57099908
>KDE
Gas yourself.
>>
>>57099859
>Heart Bleed appeared to be an innocent mistake
Is he implying that it was deliberate?
>>
>>57099908
>his init system includes gaymezz

Are anti systemd hippies getting this much desperate?
>>
>>57099845
You should try reading what I wrote. It's required by one of the top pentesting certification companies, they issue some of the most highly respected pen testing certs. Secondly pentesting is what it is called, that is the actual name for it. Kali is a buggy piece of shit.
>>
File: 1450441684801.jpg (338KB, 984x1008px) Image search: [Google]
1450441684801.jpg
338KB, 984x1008px
SystemD is a botnet. Also it is extremely resource hungry. It is a fucking joke on anything embedded or small.

SystemD is what will drive the final nail into the Linux coffin.
>>
>>57099885
Nice try jewsa, not falling for your hebrew tricks.
>>
>>57099930
Steam runs just fine on non-systemd distros, the fuck you on about?
>>
>>57099926
lmao poorfag can't run KDE
>>
>>57099717
>LMFAO luckily I'm not a NEET to worry about that piece of crap

Slackware really isn't that tedious. Exactly what is anyone's gripe with it?

>manual dependency resolution
Unless you're compiling something with massive dependency bloat, it's not that big of a deal to resolve this on your own. The software's readme should provide you with a full list of dependencies. And Slackware does have a package manager that mirrors a number of common dependencies.

Also, Zenwalk's package manager goes above and beyond to resolve dependencies for you.

>no GUI install
Come on. If you guys can't even cfdisk, then why are you running anything but Windows or OS X?
>>
>>57099865
You mean like Slackware?
>>
>>57099950
Nah, slackware is garbage
>>
>>57099937
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.
>>
>>57099911
I would seem to have nailed yours.
>>
>>57099908
>>57099946
Steam runs on systemd distros as well, what's your point, mouth breather?
>>
>>57099908
>KDE
Christ, that's horrid. It looks like a web page opened up with noscript running.
>>
>>57099859
>>57099937
Confirmed.
SystemD is the next botnet!
>>
>>57099844
Well they are technically all 3rd party repos, but Eric Hameleers (AlienBOB) is kind of an unofficial dev who provides things like multilib, latest KDE packages, a "real" live USB, and other useful stuff. Slackonly is a repo that provides binaries of everything on SBo. Some of the others are Slackware-derived distros.

>not much in them though
In all the years I have been using Slackware, and in the recent years since slackpkg+ has been available, the only thingsI haven't found through slackpkg+/sbo were TDE and llpp, and I was able to find Slackware binaries for the former and a Slackbuild for the latter.
>>
>>57099949
Slackware does have a GUI installer. It uses ncurses scripts to install it. After you setup partitions and type the setup command, it's GUI from there on.
>>
File: 1475279426868.jpg (154KB, 1298x921px) Image search: [Google]
1475279426868.jpg
154KB, 1298x921px
>>57099937
>SystemD is a botnet.
>>
>>57099957
Care to back that up?
>>
>>57099936
>>57099890

How can they tell which distribution you used those tools on when you were studying for it?
>>
>>57099936
>It's required by one of the top pentesting certification companies
Your mom's whorehouse?
>>
>>57099985
Old as sin packages for one
>>
>>57099949
>cfdisk
>not fdisk
fucking pleb....
>>
>>57098044
>I'm going to stick to a distro that is know for it's stability and security.
Qubes OS?
>>
>>57099987
You have to take a 24 hour certification test. You also have to complete labs before that.

>>57099996
>Old as sin packages for one
Not anywhere close to old as sin just not the latest dev release that are still buggy.
>>
Just wanted to pop in and give everyone a friendly reminder that systemd is just the Win10 botnet for linux.

Also the NSA work closely with Red Hat and Lennart, in fact SELinux is another NSA/Red Hat exclusive product
>>
>>57099981
I love that alienbob also has qbittorrent, libreoffice, openjdk 7 and 8, virtualbox among many other packages.
>>
>>57099949
>it's not that big of a deal to resolve this on your own.


Employed person:
#apt install gimp
get the job done
optionally remove gimp

SlackNEET:
>lul I'm so spiacul, I don't even need dep resolving
>let me open up my 1337 terminal and look for my package versions
>install gimp 20 minutes later
>lol look mum I resolved gimp, it's my productivity of the day :-DDD
>>
Daily reminder that systemd is a botnet:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
>>
>>57100049
IIRC gimp comes by default in the base system in Slack.
>>
>>57100062
Doesn't everything come by default in the base system?
>>
>>57100030

>You have to take a 24 hour certification test. You also have to complete labs before that.
Good for them. But how does that imply that anyone whose job is in that field preferring to use a shitty, downstream, spin-off distribution instead of just installing a regular distribution and his tools of choice manually?
>>
>>57100062
You do realise that was supposed to be an example, right? Do you suffer from autism?
>>
>>57100049
>Install slackpkg+ or slapt-get
>type a few commands to get the packages I need
>use slackbuilds for any uncommon package repos don't have
>done
>>
>>57100077
>>Install slackpkg+ or slapt-get
>>type a few commands to get the packages I need
>>use slackbuilds for any uncommon package repos don't have
>>done
vs
>#apt install gimp

Guess which one has a job
>>
>>57100073
I never claimed that once you lair. It is required for the certification. Who the hell is going to risk getting failed on a couple thousand dollar cert because of what ever bullshit you are rambling about?
>>
>>57100075
How often do people actually install shit, I mean if you're not some minimal system ricer.

Cause your example is kinda shit, hth.
>>
>>57100073
I don't believe he ever made that claim, Sir. You should calm yourself down.
>>
>tfw just migrated to BSD first time today after being a long-time Linux user
Feels good to be away from the systemd botnet.
>>
>>57100094
Of course, chromium totally comes with slackware
>>
>>57100070
The fucking point, why install shit when it's already there.
>>
>>57100054
holy shit this thread is hilarious and sad at the same time

this is why I don't take debian seriously
>>
>>57099484
What the fuck does this webm mean
>>
>>57100105
Dumb BSDbabby with NO proof whatsoever
>>
>>57100086
Your example is shit because Slackware comes with gimp. If you can't spend a measly 10 minutes setting up slapt-get, you need to increase your ADHD medication.
>>
>>57100120
It means it was patched quickly and you even don't have to reboot
>>
>>57100112
What exactly are you trying to claim?
>>
>>57100109
The fuck do you need that shit tier browser for?
>>
>>57100125
see >>57100075
>>
>>57100033
More reasons to use OpenBSD every day.
>>
>>57100105
>Feels good to be away from the systemd botnet.
Your OS has more open backdoors than a Village People concert. Fuck off.
>>
>>57099866
>There is Zenwalk, Salix, Porteus, and VectorLinux for desktop distros based off of slackware. Slackware also now has a lightweight arm distro that is great for embedded systems. Nice try though.

What the fuck? None of those are used, are you trolling me?

>Literally Slackware. What it is known for. Please give a good reason next.
Slackware is known for offering a good base system? I wonder why it has a grand total of 24 distributions based on it, including Slax-based distributions and including all the dead ones.

There's a reason Kali chose Debian and even if they chose anything other than Debian they sure as shit wouldn't use Slackware as a base because there would be no benefit, there's no reason to base your distribution on Slackware, it offers nothing to the developers and it certainly doesn't offer anything to the users. If you want to use Slackware that's fine but implying that it's good for anything other than personal use is ludicrous, it's like saying Slackware is a good server distribution.
>>
>>57100138
Enjoy your FBI backdoors, my man
>>
>>57100109
google-chrome-stable has been in the /extra directory for years. chromium is available via SBO/slackpkg+
# slackpkg install chromium
done
>>
>>57100109
You just install the chromium.SlackBuild off of slackbuilds.org. It takes no longer than downloading and install anything other application on any other OS.
>>
>>57100146
Source?
>>
>>57100142
nice try lennart
>>
>>57100090

From here >>57099604
>You do realize that it was make for professional pen testing which pays very well?
... in response to prove that Kali Linux is a serious distribution and implying that well paid, professional and serious people use it. That fact is also backed up by this >>57099553 post, which implies that any of those people would care about that instead of just installing his preferred upstream distribution (not Kali) and the programs seperately.
>>
>>57100153
Ask that to every single anti systemd FUD spreading cancer ITT
>>
>>57100144
They chose debian because they're lazy /g/-level devs that wanted a supported base that they could bitch at upstream. Also because UBUNTUU
>>
>>57100151
>>57100148
Finally
>>
>>57100119
>>57100054

What does that have to do with systemd?
>>
>systemd being shoved down FOSS fag throats
>No real way to complain, it's literally shut up or go away
>Literally a fucking botnet written by the man whose software was the #1 reason to never migrate to Linux

So much for those freedumbs huh faggots, this shit is fucking hilarious. systemd tears are beautiful.
>>
>>57100171
>>Literally a fucking botnet
Spotted the 14 y/o
>>
>>57096717
You're welcome to point to the exact lines of code containing the NSA backdoors.
>>
>>57100144
>What the fuck? None of those are used, are you trolling me?
Yes they are.

>Slackware is known for offering a good base system?

>distributions
As well as embeded systems which it is great for.

>it offers nothing to the developers and it certainly doesn't offer anything to the users.
Yes it does, it even offers everything that you previous claimed as the reason for choosing debian.

>If you want to use Slackware that's fine but implying that it's good for anything other than personal use is ludicrous, it's like saying Slackware is a good server distribution

That's not true either. It's great for embedded systems and is used in them. Especial the small arm slackware.
>>
>Gpl licensed, free and open source
>"Just werks"
>Faster boot process
>Eliminates bloat/meme packages

There is NO reason why one should delete systemd from his system. There is nothing systemd can't do what other init systems can.

>Botnet
Source is open, show where

>Not Unix
Neither is linux

>pottering
So what packages did YOU make yesterday?
>>
>>57100157
>in response to prove that Kali Linux is a serious distribution and implying that well paid, professional and serious people use it.
No I said that it was made for it and was required for a cert. Now you are just putting words in my mouse. I never once claimed it was a serious distribution either. Keep trying though. I said nothing like what you are claiming.
>>
>>57096700
Anon, systemd is PID 0...
>>
>>57100203
>So what packages did YOU make yesterday?
I made your wife's son
>>
>>57100105
Why? Are you retarded? With so many angry autists looking for ANY sign of anything malicious, systemd is probably the safest way to go.
>>
>>57100181
spotted the nsa shill
>>
>>57100244
I am paid by the NSA and I am spying on your super sensitive data that you carry on your poorfag thinkpad
>>
>>57100244
You mean the jewsa, NSA is ran by Israel supporting jews.
>>
>>57100171

Why would someone listen to your complaints? If they were legit and reasonable, they'd get taken into account. Otherwise you're free to create your own alternative or even for the existing one and incorporating your "improvements".
>>
>>57100203
fuck off with your pasta Agent Johnson
>>
>>57096700
>>Try to convince Linus to put a backdoor in the kernel
[citation needed]
>>
>>57100260
Refute
>>
File: 1471846589207.jpg (35KB, 467x410px) Image search: [Google]
1471846589207.jpg
35KB, 467x410px
>>57100203
>Faster boot process
Not true
>Eliminates bloat/meme packages
Absolutely the opposite
>"Just werks"
It doesn't
>Source is open, show where
He thinks a source being means it's safe.
>Neither is linux [Not unix]
Irrelevant
>So what packages did YOU make yesterday?
Even less relevant

Quality post.
>>
>>57100260
Agen Johnson is busy fucking ur mum
>>
>>57100266
>r-refute it you dumb goy
>>>/nsa/
>>
>>57099806
I'm not the anon who claimed it was a backdoor, check your privilege.
>>
Main purpose of systemd is doing to Linux what OSX Lion did to OSX, making every device that uses the new version of the OS a part of the NSA botnet.
>>
>>57100282
I checked and it's still there, thanks for reminding me to check it. I almost forgot to.
>>
File: Zd3mf.png (30KB, 1023x657px) Image search: [Google]
Zd3mf.png
30KB, 1023x657px
>>57100275
>Not true
Even Linus admits the boot process improvements (2014, debconf)
>Absolutely the opposite
Say goodbye to udev, gconf, polkit and other unmaintained garbage
>It doesn't
It fucking does
>it's safe.
Show where the botnet is, they'll fix it. Just like your NOTIFY="" bug got fixed in 60 minutes
>>
>>57100277
Get the fuck off back to /b/ dipshit
>>
>>57100308
Go to sleep leonart
>>
>>57100171
I hope to god you're a windows user. Please don't spoil the hilarious mental imagery your post gave me.
>>
>>57100320
That's what your mum said last night :-DD
>>
>>57100323
I use OpenBSD
>>
>>57100327
Confirmed, pottering posts in /g/
>>
>>57100338
So ur mum told you about this as well. Sorry for ""your"" dad tho
>>
>>57100319
Right after you stop shilling your botnet, lennart
>>
File: Harry_James_Potter34.jpg (52KB, 425x599px) Image search: [Google]
Harry_James_Potter34.jpg
52KB, 425x599px
I always imagine Pottering looking like picrelated
>>
>>57100336
Enjoy your FBI backdoors my man
>>
>>57100336
Whoah! Even better!
>>
>>57100346
kek I don't give a fuck about a lonely basement dweller like you, if that makes it clearer for you
>>
>>57099776
>Are you really that dense to claim that the creators of it don't know what their creation is? Its goals are clearly defined
Yeah, goals that change everytime are clearly defined.

>Getting things to work more easily and robustly is unnecessary complexity. Totally.
Dumbing down things are unnecessary. Sure everything works out of the box, but then you need some control over your system, e.g. dbus, and then you need to figure out how systemd services binaries works, while in SysV, you write a simple, easily modifiable, shell script. And the price is the totally unaceptable 0.5 seconds more of boot time. (If put in initialization).
>>
>>57100282

Doesn't change the fact that you called the bug in Bash a backdoor and not a bug.
>>
Why is everything that poettering makes turns into a bloated piece of shit? Like PulseAudio became good only after they all but kicked lennart out and retooled it heavily.
>>
>>57096662

it's statistically true.
on average, you have about 1 bug for every 1k LOC.
how big is systems again? and who developed it?
>>
>>57100397

>Yeah, goals that change everytime are clearly defined.
They were defined. System management is a broad topic and as people come with new demands they add them.

>how systemd services binaries works
Service files are text files. For laymen who don't know shell scripting it's easier than shell scripts. For people who are smart enough to know how shell scripting works, surely they are smart enough to "learn" how to write a config file.

> And the price is the totally unaceptable 0.5 seconds more of boot time. (If put in initialization).
You're an idiot if you think that boot times are the only reason systemd exists. Holy shit I just realized that I'm talking to a meme spammer who has no idea what he's talking about, but is only regurgitating other people's opinions.
>>
>>57100413
Lennart started writin pulseaudio at the age of 14.

You are still unemployed
>>
People who hate systemd: have you ever even used systemd?
>>
>>57100447
nice deflection lennart
>>
>>57099631
This is mostly true. Since the change to Systemd, we've had to expend limitless human and monetary resources on finding a way back into the Linux kernel. Our partners in Isreal are equally determined, too.
>>
>>57100166
Yup, which implies it takes less work to base your distribution on Debian than it does on Slackware, which is exactly my argument.

>>57100189
>Yes they are.
So is Hurd, just not by a lot of people.

>As well as embeded systems which it is great for.
You're right, Slackware DOMINATES the embedded system market.

>Yes it does, it even offers everything that you previous claimed as the reason for choosing debian.
No it doesn't, which is why no relevant distribution uses it as a base.

When Canonical wanted to make a distribution they based it on Debian, when Valve wanted to make a distribution they based it on Debian and again had they not used Debian they would have used fucking Fedora before they used Slackware. You can either accept that or keep living in your fantasy land. I'm out.
>>
>>57100413

>software became better after time passed
STOP THE PRESSES
>>
>>57094507

Like it, love it, or hate it. There's no way back now.
>>
>>57100457
Nice deflection, NEET
>>
>>57098141

nigger do you even daemon?
>>
>>57096532
no
>>
>BOTNET BOTNET BOTNET

You kids are dumb as fuck.
>>
>>57100460
>Slackware DOMINATES the embedded system market.
Never claimed that either. Nice try.

>When Canonical wanted to make a distribution they based it on Debian, when Valve wanted to make a distribution they based it on Debian
Irrelevant.

>they would have used fucking Fedora before they used Slackware
Going to need a source.

>No it doesn't, which is why no relevant distribution uses it as a base.
Yes it does. Notice how you have to keep changing what you claim about it being used a base too since you keep getting proved wrong. Moving the goal posts is a good sign you are loosing an argument which you have done repeatedly.
>>
>>57099553

govt wouldn't know who the haxxors are then
>>
>>57100407
I didn't call it a backdoor, I just assumed that that's what the original anon meant when he said backdoor. Honestly not sure why you're being so anal about vocabulary on /g/, where everything's a botnet and everyone's a shill.
>>
>>57100509
>Never claimed that either. Nice try.
You keep mentioning Slackware ARM like it's a reason to base your distribution on Slackware, it's not.

>Irrelevant
How is it irrelevant? That's what makes Debian "know for being a good base system" which is my argument. Relevant distributions use it as a base, Ubuntu is relevant, VectorLinux or whatever isn't. Deal with it.

>Yes it does. Notice how you have to keep changing what you claim about it being used a base too since you keep getting proved wrong. Moving the goal posts is a good sign you are loosing an argument which you have done repeatedly.
What? OK, let's review this.

What was originally said stated:
>I wish that Kali linux distro was built off of slackware instead of debian it would make so much more sense.

How would using Slackware instead of Debian as a base for Kali Linux make "so much more sense". My case is that it wouldn't make more sense. You apparently disagree, can you provide reasons besides "yes it does"?
>>
>install PCLinuxOS
>no systemd
>boots in seconds

But sure, feed me some unstable, buggy, badly coded, badly documented, poorly designed, non-standards-following software to solve me a problem I don't have.

Sage, hide and report paid shill threads.
>>
>>57100731
>But sure, feed me some unstable, buggy, badly coded, badly documented, poorly designed, non-standards-following software
>install PCLinuxOS
Mission accomplished, chump.
>>
>>57097875
That's retarded

One person can't audit the code faster than modifications arrives which means it's impossible to prove or disprove

Nice try NSA
>>
>>57100726
>You keep mentioning Slackware ARM like it's a reason to base your distribution on Slackware, it's not.
I mentioned it as being useful for embeded systems. Nice try though.

>How is it irrelevant? That's what makes Debian "know for being a good base system"
Other companies having choosen debian does not mean that no other distro is a good base system. So, yes it's irrelevant. Especially since we are talking about kali linux which is made for a very specific job.

>My case is that it wouldn't make more sense. You apparently disagree, can you provide reasons besides "yes it does"?
I've provided multiple reasons on why it's a good base system. You just pulled bs out of your ass and couldn't handle it not being accepted. You have repeatedly claimed I said things I didn't, twisted my words, and just flat out lied.

Secondly claiming that good choices where made concerning the development of Kali is idiotic seeing as how poorly it turned out.
>>
I use Gentoo and OpenRC.
>>
>>57100773

Even if that was true, that's not the topic of the thread. Systemd is. So your reply is a red herring.

Not surprised that systemd shills have to appeal to logical fallacies.
>>
>>57100144
>None of those are used

Not the anon you're replying to, but I use both Zenwalk and Salix. Zenwalk is my primary desktop OS, and I have Salix on my laptop.

Slackware distributions don't collect any statistics on downloads, the number of computers actively running Slackware, etc. That doesn't mean no one is using Slackware or any of its derivatives, it's just not aggressively tracked or advertised like some of the more mainstream distributions are.
>>
>>57096532
this.
>>
>>57100830
same anon
systemd botnet has no place on my PC
>>
>systemd-based distro boots at least 4x slower than runit/openrc-based distro on same hardware
How do people live with this shit?
>>
>>57101744
my boot time halved when i switched from openrc to systemd desu
>>
File: apple programmers.jpg (19KB, 665x279px) Image search: [Google]
apple programmers.jpg
19KB, 665x279px
>>57094507
It WOULD be the future

Were it not developed by FOSS shitters.

A project of systemd's scale and important REQUIRES a large team of professional developers UNDER ONE ROOF. ZERO volunteers. No uncertified persons. People outright HIRED as a LIABILITY, with their work A LIABILITY, talking to each other IN PERSON, coordinating perfectly, with no email-only social dynamics so more dominant and sensible personalities can properly and rightfully "smash puny nerds" (like lennart) whos only decision making power comes from seniority. So you can hire a new manager when shit goes south and "smash puny nerds".

When you're systemd you can't say "woops, FOSS problems, shit happens with so many people only coordinating over email and a VCS, we fixed it lol". It's bad enough for that to happen with the fucking kernel, and we only have one angry autistic finn to keep that in line. Systemd doesn't have a single sensible person at the helm, and because it's FOSS, it doesn't have to. Large datacenters are relying on a ragtag group of autistic retards on two counts now. How is this not a problem?

Large complex FOSS = disaster waiting to happen.
>>
>loonix babbies actually defend their terrible shitware
use bsd already
>>
>>57098420
it was actually a complete non-issue because the unix shell is not meant for use by untrusted users or any situation where input may not be 100% trusted. you can call binaries by name, and get the first one that shows up while walking a list of directories. how wonderful, it would be a shame if a parsing bug showed up and let people sending DNS requests use that feature.

the real backdoor was people using a shitty algol-alike user interface language as a systems programming language.

>fuck fixing that
>fix bash!
>>
>>57100446
Go back to f u 1 1 chan faggot
>>
>>57094507
svchost, the thread.
Go back sucking poettering cock while I enjoy my riced gentoo with openrc.
>>
>>57101744
My Arch install with systemd and systemd-boot boots in less than 3 seconds
>>
>implying i trust open source devs to be able to maintain something as large as systemd

Mozilla can't even get firefox right
It took devs decades to realize using an X server as a compositor was a bad idea
Something the size of vim can't go a year without a parsing bug in vimscript, and emacs still has a very long list of bugs
gcc and glibc are major infrastructure and don't have enough people to fix every bug (check out the bug trackers for a sad laugh)
Pulseaudio wasn't even usable for years after its first "stable" release
OpenRC spent ages with a half-finished featureset

it took microsoft a few years of testing and QA to go from vista to 7/vista sp3. am i supposed to believe that volunteer developers can write a whole new init system that handles all userspace plumbing and get it right in just two years when the biggest part of their QA is random people randomly running into bugs, maybe reporting them, maybe abandoning systemd altogether? or when it's a sparsely commented 300k lines of code?

nuh uh.

-sent from void linux+dwm
>>
>>57101977
My Slackware desktop/server/toaster reboots no more than once every few months. My Slackware ThinkPad reboots whenever I forget and leave it unplugged (about once every few weeks on average). I guarantee that I spend less cumulative time booting my system than you, even if it takes me 45-60 seconds to boot
>>
>>57102033
>I have to use a meme distro because I can't remove systemd from Arch
is all I got from your pot
>>
My %distro% install with systemd and systemd-boot boots in less than %n% milliseconds.
>>
>>57102071
That's nice, for those of us who turn off our computers when we're not using it, individual boot time matters more than cumulative.
>>
>paid MS shills trying to discredit systemd because they know it's better than anything they've been able to do with their shitty OS
Every single fucking day, several times a day. When will 4chan finally block these paid MS shills?
>>
>>57100275
This
You systemd shilling lennart cock loving faggots just don't get it.
>just read the source
The source changes constantly and grows even larger everyday. It was at 135,000 LoC last I checked. It is by design impossible to audit. For those of us with valuable time, auditing Sysvinit and OpenRC or Runit is a billion times simpler and THEY ACTUALLY WORK. There is literally nothing systemd has done that other init systems/programs can't do.
>>
>>57102189
why would you ever turn off your computer? don't you want 8 digit uptime?
>>
>>57102253
No, I care more about saving energy. My laptop isn't a server.
>>
>>57096662
>>57096640
>>57096689
-the speed at which this cancer init moves
-the size of the codebase
-the increasing complexity of the codebase
-the heavy push of the init on any and every Linux system
-tangling in as many independent features as possible
-including as many system critical features in the init system as possible
Pretty obvious
>>57097777
this is what a delusional person that has never read a single loc believes. They believe an init system as complex, large, and fast moving as systemd can be easily dissected so bugs can be found. As if someone that intentionally plants bugs would not try their hardest to obfuscate their inserts.
>>
>>57102285
Just hibernate like normal people then. There's no real need to ever shut down your computer, whatever the use-case is.
>>
>>57102285
>what is suspend-to-ram and suspend-to-disk
>>
>>57102302

Two things Linux can't do on virtually all laptops.
>>
>>57102301
>>57102302
that's something systemd handles better too
>>
File: rms.jpg (144KB, 1395x1395px) Image search: [Google]
rms.jpg
144KB, 1395x1395px
>>57102321
I'd just like to interject for moment. What you're refering to as Linux, is in fact, GNU/Linux, or as I've recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.

Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called Linux, and many of its users are not aware that it is basically the GNU system, developed by the GNU Project.

There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine's resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called Linux distributions are really distributions of GNU/Linux!
>>
>>57102324
You say that as if it was a good thing. That's a massive red flag, why is your init system handling suspend?

That's not a feature, it's a bug. It's not init's business to deal with that!
>>
>>57102340
Or, as I've recently come to calling it, ((((GNU))))+Linux.
>>
>>57102285
this is the problem with Linux

it needs to morph from being a server and workstation OS to accommodate special snowflakes that need something way more obscure than OSX on their laptops
>>
>>57102354
Because it's not just an init system, it's a system daemon
>>
>>57102321
>>57102324
no issues with either using pm-utils on Slackware on many different laptops over the years (ThinkPads, jade/snsv, eeePC)
>>
>>57102380
I could have made my laptop into a Hackintosh but I rather be a "special snowflake"
>>
>>57102324

>hit suspend
>my laptop goes off
>hit the power button
>it rises back up

Wow, I'm eager to see how systemd improves on that!

>>57102391

There's no such a thing as a "system daemon". Either systemd does one thing well or it tries to do many things and fails. There's no in-between.
>>
>>57102418
>muh oonigs philosophy
>>
>>57102321
Slackware does that just fine on my laptop.
>>
>>57102462

It's not a "philosophy", it's a computer science postulate.

Computer science is math. At math, if you start throwing axioms out the window, suddenly you can't prove your theorems anymore.

Microsoft did that and look how it worked out for them.
>>
>>57102418
Linux is not Unix, sorry. You can do more than one thing well, you just need to be competent. All I know is that systemd is the future for Linux. Ever since I've started using systemd, I haven't had to edit config files to get basic shit like automatic volume mounting to work without a DE. There is a reason systemd is being widely adopted and that reason is that it's better and more efficient than the old tools.
>>
Systemd is a systematic destabilization of the GNU/Linux community. It does this by design.

Systemd is an malignant anomaly in community. There has never been anything intrusive like it and it should be treated with extreme caution. Take all these simple general facts into consideration and think for yourself before mindlessly jumping on the "muh new" bandwagon:


-LARGE, FAST MOVING, INCREASINGLY COMPLEX codebase makes a proper audit infeasible considering limited resources

-dragging of many independent projects into a dependency tangle to create dependence on systemd and ensure its the only supported init

-including critical previously independent features into the init system (there is no reason for this consolidation of critical features except to get them under one source of control)

-aggressive pushing of the init system into distros with a "you're either with us or against us" mentality of development
>>
File: 6tD3rVR.jpg (358KB, 2000x1087px) Image search: [Google]
6tD3rVR.jpg
358KB, 2000x1087px
>>57102518
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>You can do more than one thing well
>>You can do more than one thing well
>>
>>57102518

>I haven't had to edit config files to get basic shit like automatic volume mounting to work without a DE

Nigga, that had been working well for ages without systemd.

Not to mention why is your init system handling volume mounting? Yet another huge red flag. Not a feature, but a bug.
>>
>>57102539
I feel sorry for you, the only thing you can do well is masturbate. At least that explains your low quality shitposts.
>>
>>57102564
>If it works, its a bug
- anti-systemd retard

Also stop fucking lying
>>
>>57102564
>Not to mention why is your init system handling volume mounting?
Name an init system that doesn't
>>
>>57102611
>let's just stack shit on top of as long as it works
>complexity, interoperability, portability none of that matters as long as I get my special snowflake monolithic pile of shit desktop OS
>fuck any engineering principles or standards
>>
>>57102656
there's a difference between doing "mount -a" as part of your startup script and having pid 1 listen for and automatically mount volumes. not to mention that automatically mounting volumes is potentially a huge security vulnerability.
>>
>>57098008
>using a literal joke distro that doesn't have a package manager

Enjoy.
>>
>>57102730
>monolithic
>literally 69 individual binaries that each serve different tasks

kek
>>
>>57102756
>I don't know how to do things without a package manager
How many years did you spend pissing on the toilet seat before someone told you to put it up?

>>57102764
>systemd is made up of 69 binaries
Was that supposed to be a defence of systemd?
>>
>>57102764
>thinking muh binary count means anything
It's a bloated piece of shit that keeps tangling unnecessary features into itself

It should just become its own OS but it would never do that because it needs to leech of the Linux userbase like the cancer it is
>>
>>57102745
>there's a difference between doing "mount -a" as part of your startup script and having pid 1 listen for and automatically mount volumes.
All systemd is doing is executing any .mount units you have defined. There's not much difference between that and running `mount -a`, except that the former is more robust.

>not to mention that automatically mounting volumes is potentially a huge security vulnerability.
What do you do, type `mount /dev/sdX /path` 10 times after every boot?
>>
File: lmao.jpg (159KB, 1014x1300px) Image search: [Google]
lmao.jpg
159KB, 1014x1300px
>his init system doesn't generate QR codes
>>
>>57102756
I has a package manager and it isn't anywhere close to a joke distro. It just werks.
>>
>>57102838
>>
>>57102794
>>57102799
>It's monolithic!
>>Actually, it's broken up into individual binaries that do their own thing and do it well.
>SO IT'S BLOATED!!1

These fucking retards are trying to hold back Linux, I swear to God.
>>
>>57102794
Not knowing how to do something, and not wanting to are two different things.
>>
>>57102880
>replying to anti-systemd shills
do you reply to fundamentalist christians on a regular basis as well?
>>
>>57102874
And it's still not a joke distro. If you had any idea what you are talking about you would know that. It's been a long time since Slackware was created and a long time since it was just a side project.
>>
>>57102880
>>>Actually, it's broken up into individual binaries that do their own thing and do it well.
>loog, it's bruken up indu many binaries meaning it's not monolithic because of my generalized novice undersdanin of the term
you automatically think by breaking up your poorly designed piece of shit it will somehow not become monolithic? Nice meme.
>>
>>57102906
Gotta publically wreck their arguments before the impressionable young kids who start getting into Linux read their mental refuse on forums and adopt their beliefs.
>>
>>57102934
>before the impressionable young kids
on /g/?
>>
>>57102922
A package involving 69 individual binaries can hardly be called MONOlithic.
>>
>>57102961
Yes, I'm including /g/ as well.
>>
>>57102880

Being monolithic has nothing to do with quantity of binaries, it's about architecture.

And being bloated isn't about number of binaries either, it's about functionality centralization and the adding of unnecessary abstraction layers that make other software dependent, effectively locking people into systemd.
>>
>>57102827
no, I have most of my commonly used volumes in my fstab, either by nfs share, device (sdcard, ultrabay), or uuid (flash drives) and I just mount/umount them as needed. i hate it when overreaching DEs and other "convenience" things automatically stick them into some /run/var/media/by-UUID/32b9ef4d5aef2c39ceaf68 directory, so I have everything mapped to a specific mount point with a simple human-readable and human-writable path. it's a system that has worked for me for 15+ years and i don't feel like changing it.
>>
>>57102962
they're so tightly coupled together without any documentation for how they interact so that replacing any individual binary would be a large undertaking for someone who is just getting involved with the codebase. this is by design. systemd's supposed modularity is a surface level smokescreen
>>
>>57102986
stop trying
it's pointless
>>
>>57102962

Being monolithic has nothing to do with quantity of binaries, it's about architecture. It's about combining things that should be kept apart in a single codebase.
>>
>>57103008
>It's about combining things that should be kept apart in a single codebase

For what purpose?
>>
>>57103032

There's no good reason to do it. That's why monolithic architecture is considered bad architecture.
>>
>>57103049
No, for what purpose would you want to keep them separate? If you hate monolithic design that much, why are you even using Linux? The kernel itself is monolithic!
>>
>>57102992
>no, I have most of my commonly used volumes in my fstab
So your fstab entries don't get mounted automatically by your init?
>>
>>57103126
not if set them as noauto. why would i have a removable volume automatically mounted on system initialization?
>>
>>57103183
Why would you have removable volumes in your fstab at all?

I only put permanent volumes that I always mounted in my fstab. For everything else, I just type the adequate `mount` command when I need it; e.g.
mount /dev/sdh1 /mnt/usb
>>
>>57103231
>>57103183
Also, systemd-fstab-generator respects the “noauto” option. (It will only create an `automount` unit for fstab entries that don't have that option)

So if you're saying this contradicts your experience, that sounds like a bug. Have you reported it?
>>
>>57103270
>reporting bugs so they can be fixed
>ever
>>
File: fstab.png (2KB, 419x117px) Image search: [Google]
fstab.png
2KB, 419x117px
>>57103231
because i have names for all my volumes, whether they are network shares, internal hdd, external hdd, flash drives, etc. having them in my fstab by UUID means I can do shit like
# mount /mnt/mutant
and not have to worry about what the device name is
this is really basic shit, if you can't understand it, you are completely unqualified to have an opinion on whether or not systemd is good.
>>
>>57103270
It doesn't contradict my experience because I don't use systemd. I had arch on a netbook for a while and systemd routinely pissed me off for reasons other than mounting. it's simply not a Good system architecture, not Unix Way, reinventing the wheel in the worst possible way.
>>
File: 1314249474607.jpg (42KB, 466x478px) Image search: [Google]
1314249474607.jpg
42KB, 466x478px
>>57103392
>It doesn't contradict my experience because I don't use systemd.
So you're commenting on a bug that doesn't even exist?

I swear, it's always the same with anti-systemd shills..
>>
>>57103341
So why don't you add the noauto option to the partitions you don't want to have automatically mounted? That will prevent systemd, or any other init system for that matter, from automatically mounting it

This has nothing to do with systemd, this is linux 101..
>>
File: mpv-shot0004.jpg (59KB, 720x549px) Image search: [Google]
mpv-shot0004.jpg
59KB, 720x549px
>>57103432
now you're just being retarded
>>57103423
and putting words in my mouth
>>
>>57099226
Nothing wrong with it. GRUB supports encrypted boot.
>>
>>57103480
>systemd proponents LITERALLY feel comfortable having red hat/the nsa handle decryption of their partitions
>>
>>57103496

>le NSA meem XD

Fuck off, encryptard.
>>
File: 1476321358074.png (10KB, 679x427px) Image search: [Google]
1476321358074.png
10KB, 679x427px
>>57103526
>>
>>57103553
>mfw
http://www.youtube.com/watch?v=g3qD9UJnXnY
>>
>>57103453
Says the guy making baseless blanket statements about apparent bugs in software he doesn't even use

btw. I use systemd and it doesn't auto-mount partitions for me, except for those in fstab, so I have no idea what the fuck you are even going on about to begin with
>>
>>57099749
I'm using Gentoo Hardened

GRUB is irreplaceable for me because all of the alternatives I've found make it really hard to rescue a system that fails to boot.

GRUB gives me the command line I know and trust; and that's all I want and need. Anything that replaces it needs at least a similar thing.
>>
>>57103775
i never claimed that useless features i neither need or want are bugs, only that they are useless features.
>>
>>57103823
>waaaaaaah, all software should conform only to my exact use case and if somebody wants to do something that I don't they are wrong and stupid waaaaaaaaah
anti-systemd mantra
>>
>>57103797
>I'm using Gentoo Hardened

how well has this been working out for you? what wm/de do you use? how long did it take you to get grsec tuned just right?
>>
>>57103910
>how well has this been working out for you?
It's been a pretty fun ride

>what wm/de do you use?
xmonad

>how long did it take you to get grsec tuned just right?
grsec needed basically no tuning for the most part, but I never used its RBAC. I also had some issues with PaX and proprietary software (e.g. nvidia kernel drivers), but the the grsec pax_guy patches + some paxmarking where necessary have always resolved those for me.

The only time I ever ran into serious amounts of maintenance overhead was when using SELinux, which was basically a nightmare to maintain. You have to fix things constantly, and write your own policies for most things. Random shit will break, and trying to get a new (or proprietary) program to run is an exercise in futility. The documentation and tools are all out there, though. Can't complain in that department.

I eventually turned SELinux off again, mostly because I wanted to switch to systemd and at the time there was no existing SELinux policy for systemd. (There is one now, but I'm not exactly keen to try it out again - having it disabled again is so refreshing since everything just works)

I also stopped using grsecurity by now, because of a mix of:

1. interfering with debugging (can't attach gdb to an existing process, for example)
2. the whole spender controversy, the apparent lack of code quality in grsec; and the shitty “free trial business model”
3. slow to follow upstream kernel releases

So right now I'm using a stock gentoo-sources kernel with hardened toolchain, but no PaX or SELinux. I no longer have the time or energy to be maintaining those two constantly.
>>
File: 1459269025928.png (158KB, 663x487px) Image search: [Google]
1459269025928.png
158KB, 663x487px
>>57103869
yes. everyone who doesn't do things the way i do them is stupid. thank you for acknowledging this.
>>
>>57097204
because he's an idiot

he wrote the fucking thing in x86 assembly
Thread posts: 387
Thread images: 24


[Boards: 3 / a / aco / adv / an / asp / b / bant / biz / c / can / cgl / ck / cm / co / cock / d / diy / e / fa / fap / fit / fitlit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mlpol / mo / mtv / mu / n / news / o / out / outsoc / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / spa / t / tg / toy / trash / trv / tv / u / v / vg / vint / vip / vp / vr / w / wg / wsg / wsr / x / y] [Search | Top | Home]

I'm aware that Imgur.com will stop allowing adult images since 15th of May. I'm taking actions to backup as much data as possible.
Read more on this topic here - https://archived.moe/talk/thread/1694/


If you need a post removed click on it's [Report] button and follow the instruction.
DMCA Content Takedown via dmca.com
All images are hosted on imgur.com.
If you like this website please support us by donating with Bitcoins at 16mKtbZiwW52BLkibtCr8jUg2KVUMTxVQ5
All trademarks and copyrights on this page are owned by their respective parties.
Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the content originated from that site.
This means that RandomArchive shows their content, archived.
If you need information for a Poster - contact them.