If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Announcement

Collapse

No announcement yet.

Systemd-Free Debian "Devuan" Planning Their First Developer Gathering This Spring

Until now all I've seen of your knowledge is calling others " idiots" with very little else. Because once I see such statement I simply skip rest of your post and when your insults go too childish, just flag it for admin. Sure as hell I won't bother reading past childish raving.

Until now all I've seen of your knowledge is calling others " idiots" with very little else. Because once I see such statement I simply skip rest of your post and when your insults go too childish, just flag it for admin. Sure as hell I won't bother reading past childish raving.

Comment

You haven't pointed out a single technical problem with systemd (not one!), only misconceptions and personal opinion. And sorry, your basic code snippets does not give you any authority in claims like "Wrong approach to development." regarding a major open source system and service manager.

It's hilarious, the keywords "binary logs" and "monolithic" is repeated in every clueless person's ramblings about systemd. I'm not even going to bother explaining why, as I've seen your handle in other systemd discussions and I'm sure you've seen the answer to that. Basically, you don't know what you're talking about.

last "code snippet" I made for money involved 50k LOC and I've written longer things. Just plain lacking time after I got kid. Protestant cultures prefer not to brag. About authority - haven't seen a thing you two have written, besides flaming here.

Attack surface - pretty logical. For example I remember not just one but three CVE's from January 2019. I'ts various components have had plenty of CVE's over the years, some being exploitable for a long time (year+) before getting fixed.

About systemd affecting various software projects its functionalities it has annexed - it does not need "proving",it's self-evident.

Comment

About systemd affecting various software projects its functionalities it has annexed - it does not need "proving",it's self-evident.

Look at this guy, who uses words like "annexed"... Do you sniff your own farts while you come up with this stuff?

At the end of the day, you simply have no clue about open source and how the players within work. Systemd has been chosen because it's technically superior. It's simply more effective than the projects it's "annexed". Every distribution could choose to not use systemd or just use parts of it. This notion that Redhat is somehow forcing it on people is completely absurd.

50k LOC..... Do you even github? Do you have a single line of public code? Have you participated in any open source projects?

Oh and btw, I'm not raging I am writing this with a perfect 40 beats per minute pulse and a smile on my face sipping my coffee.

Comment

As if the attack surface is any smaller if you use other apps in place of systemd components. Where's the hard numbers saying Linux with systemd is more exploited or has more exploits in general? Just another idiotic argument. Systemd haters should simply be told to shut up or provide better code. We've heard all your ramblings before, nobody gives a shit you are just noise.

Comment

As if the attack surface is any smaller if you use other apps in place of systemd components. Where's the hard numbers saying Linux with systemd is more exploited or has more exploits in general?

there are none!

the difference is when you have 3 security issues in 3 different components not from the same project that the fools argue that way only face one of them at time with no common context and no common project name to point with their dirty fingers - these fools have a complete biased view of the world

here some issues in initscripts (10 seconds google and there are for sure enough similar nobody is aware of) which would have been not be possible with systemd units

my "mysqld" was not vulnerable becasue i switched away from mysqld_safe to systemd-unit with "Restart=always" which is the whole point of the vulerable wrapper years ago

given the amount of hardening options in systemd-units which we use excessive fact is that systemd closed more potential security issues than it ever opened because it closes a whole group of attacks completly and forever instead race conditions and copy&paste boilerplate bullshit in initscripts all over the planet