Because they can.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
For the good of all of us
Except the ones who are dead
But there's no sense crying after every mistake.
You just keep on trying 'til you run out of cake.
Me using runit, I agree
- OpenRC just feels nice
- Runit is simple
- S6 is really fucking fast
- Some distros (e.g. Guix, Void, Gentoo) come with non-systemd init systems by default, but I use them for other reasons
As for why I sometimes use musl, I like BSD. Also, Alpine Linux uses it by default, and most glibc software I've tried works just fine with gcompat.
I had to debug dns issues with a wm. Was disgusted what Systemd all does what it shouldn't.
Musl was fine until i had to install the one blob most people hate and love, Steam.
I like how simple and fast runit is. And the added security is nice.
For a while I had an Asus laptop, and no matter what, it seemed to not want to work properly with systemd-based distros. It would hang on-boot about 95+% of the time, I'd hard shut-off, restart, repeat.
On a whim, I tried Void Linux (runit) on it. And for whatever reason, it worked.
I use distros with systemd but damn, pretty soon it's not gnu/linux anymore, it'll be systemd/linux. systemd already manages services, bootloader, dns and networking. Maybe they'll replace coreutils next and the transition is completed.
Linux is becoming more akin to BSD with the introduction of systemd.
Gentoo comes with OpenRC as default so I roll with it. And it's simple and it works.
Plus the idea of having to randomly wait for some obscure stuff to block for a minute the boot/shutdown is not my thing.
The cool thing with Gentoo is that you can just decide one day to switch to systemd and it's about as easy as changing your profile and updating your system (and maybe recompiling your kernel)
People that complain about people not running systemd. Why does it bother you so much? :P
The developer of SystemD was mildly rude to some people back in 2009
That means everything he makes is pure evil by definition and explanations as to why it's bad will be invented post-hoc to make it make sense.
Linux developers are famous for how civil they handle their arguments. Especially that Linus Torvalds guy.
Especially that Linus Torvalds guy.
Wait until you learn about the beloved OpenBSD leader Theo De Raadt.
Imagine being so hard no other but frigging Linus Tolvards says you're "difficult".
SysV init works more reliably, is smaller, does just one job and is much, much better architected.
SystemD tends to fail if you do anything out of the ordinary, is massively bloated, has it's claws into far too many parts of the system, is IMHO poorly architected, the many of the individual components are poorly designed and the whole thing is a huge, and utterly unnecessary, attack surface.
SystemD is probably adaquate if you just want to use your machine in the most basic way, but as soon as you try to do anything beyond that you start running into the rough edges and bad design decisions that it's plagued with.
Could you elaborate on this? As someone who uses SystemD extensively on workstations and servers for spawning and managing both system-level and user-level services, I do find minimal issues overall with SystemD minus some certain functionalities such as socket spawning/respawning.
Of course some of default SystemD's housekeeping services do suck and I replace them with others. I would like to see the ability to just remove those services outright from my systems as separate packages since they do remain useless, but it isn't that big of an issue.
I also use systemd a lot and it baffles me people can claim sysvinit was more reliable with a straight face.
Half the time I restarted MySQL in the sysvinit days (pre-upstart as well), it would fail to stop it then try to start a new instance of it with the old one still running and the only way to fix it was to manually stop the other instance.
Process management is like the one thing systemd really does well thanks to cgroups, it's impossible for it to lose track of processes because the process lied about its pidfile.
Hate to be that guy, but all those articles are 5 years or older. Have people had more recent complaints about systemd or did that movement that complains about it kinda move on?
People don't need more recent complaints when those complaints are still relevant today.
I can actually configure and understand everything the UNIX way, which is actually important to me, because I do some wacky shit with my system + I'm a developer, I physically need to understand my system so I can debug it when it starts to eat shit
Although, seriously, if you're not a developer and don't intend on doing something specific with your system, just pick a mainstream distro and roll. I install Mint MATE or Ubuntu on my secondary systems too.
At this point i don't care anymore if my system has systemd or whatever, as long it's works i don't have complaint
Maybe back when I'm still young i will agree with majority linux enthusiasm that systemd is bloat, GUI is bloat, or whatever. But now as long it's work & can do job properly i don't care or even care
Life is bloat.
Jokes aside, GUI really is bloat. Especially when it's made by a corporate company with absolute dogshit development practices.
On a more serious note, systemd is bloat. With all of you new kids coming over to this side, start with the right way: the runit way. Also compile Gentoo whilst you're at it.
Obligatory /s if anyone is offended, you bunch of snowflakes
Most of them think that theyβre making a point about an argument their side lost almost a decade ago.
To which the other side replies with points outdated since the first other init/service manager aside from SysV and Systemd was invented.
More Code in Kernel-space = less secure
Systemd = a lot of Code in Kernel-space
By importance, descending:
First, I don't like people promoting systemd. I don't need it more than other init systems. It's about picking the right group.
Second, I want a simple distribution so I use Void, which famously uses runit. It's about being lazy.
Third, I don't like the idea of it sprouting dependencies which it shouldn't. It's about paranoia. See recent news with a backdoor which wouldn't work if not for this.
Does Alpine Linux count as "running"?
SystemD just isn't necessary for every Linux install.
Linux has thousands of uses that aren't "running on bare metal on my customized gaming rig at my computer desk to play steam games and pretend to look like Mr. Robot"
Staying lean in my init is a hobby
My initial experience with Linux was without systemD and I didn't like it when Debian switched to it. Void is comfy enough.
Dunno...
Wanna ask my OpenWRT router that?
Also, is Android not Linux anymore?
Give this systemd lecture a watch it explains the why https://www.youtube.com/watch?v=o_AIw9bGogo
I like being able to see my logs without waiting 20 minutes, knowing who started what without playing cat and mouse with random processes and being able to change something without going through multiple levels of merged configurations files from three different sources.
I also enjoy tools that were developed over decades and not rewritten from scratch reintroducing long-solved issues.
Its just easier for me to dualboot windows. Im too dumb to find how to do it with systemd :p
Aren't you talking about systemd-boot which is optional anyway? systemd covers the Linux init process which should have nothing to do with dual booting, no?
That is systemd-boot, which is separate. You should use refind anyways