Addition to other comments, you can also try your chance by installing Steam as flatpak. Maybe that would work without you needing a second distro.
For DaVinci Resolve, you can try this: https://www.danieltufvesson.com/makeresolvedeb
Addition to other comments, you can also try your chance by installing Steam as flatpak. Maybe that would work without you needing a second distro.
For DaVinci Resolve, you can try this: https://www.danieltufvesson.com/makeresolvedeb
While this is possible, I wouldn't disturb LMDE's (or Debian's) harmony with adding Nvidia's repo. By doing this you add a posibility of a broken or a wonky system after a driver update. Gaming over flatpak would be a safer choice.
Keep the posts going! They grow so quickly :')
There are actually many but this is the first one that came to my mind:
SUTEKI DA NE (Final Fantasy X)
Edit for additions:
It's actually quite terrifying that we cannot say it's 100% satire.
Yeah, I agree systemd makes things easier for sysadmins, and with every components of it to be fair. It's quite a huge project at this point, does way more things than a mere init system, I guess that's the argument of it being not so Unix-like. It's made specifically for Linux so it probably doesn't work on BSDs, though I have no idea honestly. Wayland was suppose to be the same and it works on some BSDs now apparently. Anyway, if I imagine system administration on bigscale, I think I would go with systemd as well.
I guess their lawyer said "best I can do is $3".
Where my gangnam-rs bois?
Khajit has schnuggels if you're willing to give wet food.
Heh, there is a joke running as "systemdOS", they have too many optional utilities. :)
Thanks! I think I like simpler inits because I started using Linux before systemd (mostly OpenRC or SysVinit for me those days, but even though I used Ubuntu for quite some time I don't really know about Upstart).
If you mean by abilities, I agree. Most of the tuning that exist on systemd doesn't exist for runit, at least out of the box or to my knowledge. However what I meant is, with systemd I don't know what's going on on my system, with runit I know every single service because I put them there in the first place. Of course systemd covers most of the things nowadays, while I have to deal with power management, networking, display manager, login manager etc all separately. Doing the Unix way is simple, while systemd grew to be quite complex.
For my daily usage it suffices. For my home server, I still prefer Debian with systemd (though I'm checking Alpine nowadays) because I'm lazy for that case and systemd does everything for me.
To be fair, there is no reason for a standard user to not to use systemd. You can easily find tutorials when you need them, which won't be a lot for your daily usage.
I switched to a systemd-less distro because I want simplicity and want every service on my system to be in my control. I cannot use systemd without copy-paste commands. With runit everything is simple.
Note that, some programs specifically check for systemd and for those you might need to adjust things accordingly, if you want to use an init system other than systemd. So again, if you don't want to deal with init systems, systemd just works.
I use Void Linux. It has runit and it's simple. If you want things kinda old-school there are distros that use OpenRC. There are a lot of init systems in the wild and that is a good thing, though you might find some of them quite barebones.
So if you want more control, why not? Just be ready to learn more things because systemd has more than what an init system do.