med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

339
active users

#sysvinit

1 post1 participant1 post today
Replied in thread

@mrmasterkeyboard @cesarpose I mean, #Xorg - like #SysVinit - both have severe issues that just ain't gonna be addressable under reasonable expectations re: hardware support, compatibility and software support.

  • But there's a reason "Big Distros" and the community in general came to the conclusion that #Wayland and #SystemD are at worst 'necessary evils' and for the most part deliver a lot of quality-of-life features.

youtube.com/watch?v=o_AIw9bGogo

There is no "#conspiracy" of #BigTech wanting to kill #X11 or even sabotage #Xlibre for that matter. It's just that some folks have trouble letting go and acknowledge that #Xserver is kept on "life support" as #Xwayland so people can run their 25+ year old #Windows games in #Wine without going apeshit.

  • I mean, ask @fuchsiii about that effort, where she's basically "workarounding" wine devs by literally pulling a "#Steam compatibility layer" kind of trick and swapping "good known working" Wine versions in just before launching a game because that works for setups where you have one user playing one game at a time on one machine and where shuffling around files/symlinks is possible.
Replied in thread

@fabiscafe @okapi espechally in the form of an interactive desktop...

  • I could see it valid for multiple shell sessions, but #tmux & #screen cover that pretty well.

  • If one has to login into different machines then chances are #aithentification is centralized anyway.

Needless to say #modernizations like #SystemD don't happen because people like #Poettering are "hobbyless", but because the preexisting status-quo (#SysVinit) was slow, inflexible and error-prone by strict linearity and non-parallelization.

  • With a literal /etc/init file one can literally get a system to hang due to a mistake (i.e. certain call doesn't get invoked correctly), whereas on #SystemD (and competing solutions like #LaunchD on #macOS and #SMF on #Solaris) your desktop / laptop will continue to noot even if it doesn't have a network connection.

Not to mention as Benno Rice explained: 'Shit just gotmore dynamic!': We don't have that one big ass maingrame and serial terminals, instead we have laptops that may he carried around a campus or traveled with all day and that constantly switch between wireless and wired networks and have VPN tunnels open and whatnot...

Replied in thread

@halva +9001%

I've used @ubuntu 7.04 and @opensuse 10.2 and noone wants to go back to those ages when we had #WiFi problems, had to fiddle with #nVidia drivers and #AMD was just not an option!

  • Same with #SystemD: #SysVinit is shit and everyone who thinks it's reasonable amto wait 5-15+ mins for a desktop to boot is even mire delusional than #Xorg fans wanting to cancel #Wayland!

youtube.com/watch?v=o_AIw9bGogo

Replied in thread

@tauon @radmin not really tho.

Have you ever had to deal with #SysVinit?

youtube.com/watch?v=o_AIw9bGogo

I do so myself in my free time...

I have been a linux user for more than 20 years, and a Debian user for a good 15 years now. For the first time, I feel like something is off. systemd feels like a Frankenstein that does not belong. It makes the system feel brittle and vulnerable.

Perhaps some more reading is in order. But I am also starting to look into things like Devuan.

Thoughts? Interesting takes and links?

Replied in thread

@gettie @waifu I just think that's due to old programs refusing to change/noone fixing them to run on #Wayland.

  • #Xorg is #EoL / dead and the quicker we get things transitioned over the better.

This isn't even a matter of convenience and speed like with #SystemD vs. #SysVinit but a matter of #deprecated APIs & ABIs…

  • Just like #i386 support for #Linux got axed because it was way too painful to maintain and noone wanted to keep maintaining it!

Ok fam, after about a week of being a complete and utter newbie ingesting tutorials about #Linux I think I am finally understanding two things: what distros are, and that for some reason my brain will correlate ANY technical topic with food.

Linux is ice cream
Linux families are particular flavors of ice cream
And like ice cream, there’s basically certain core flavors, many specific flavors, and always the potential to invent new flavors. The ice cream landscape seems to break out something like this to a newbie:

Vanilla - Debian; French Vanilla - Ubuntu; Vanilla Bean - LMDE
Chocolate - Red Hat; Chocolate Chip - Fedora; Chocolate chocolate chip - Alma;
Fruit, Strawberry - Arch; Fruit, Peach or Cherry or pretty much any other fruit - any other Arch
Caramel - Gentoo; Vanilla Caramel Swirl - Redcore
Neapolitan and Spumoni - When you do super custom stuff like make Ubuntu have rolling release distro using Arch’s package system with Gentoo’s OpenRC for the init system
Exotic, like cucumber or ranch or avocado - Everything else that isn’t one of the other big buckets like SUSE, Solus, Quirky, LFS, Zeroshell, Vine, etc.
Nuts - Slackware (I mean this in an affectionate way, butter pecan is my fav!)
Gelato - BSD
Chocolate Gelato - Solaris

Like ice cream, Linux can have toppings too:
Sauce - init systems; and some people hate chocolate sauce - systemd
Whipped cream. Yeah sure there’s different brands and differences in texture or flavor a bit, but they’re basically all doing the same stuff - Packaging
Cherry - the GUI. It’s only there for looks, you could absolutely eat the ice cream without it, but most diners expect it on their sundae

Distros - An ice cream sundae. All the things (flavor, toppings, what it’s served in) are presented to you at once. Oooor some of the more lean ones are more like an ice cream cone
Eating a pint of ice cream right outta the freezer container - CLI