β² 777 βΌ Average systemd debate (lemmy.world) submitted 2 years ago* by renzev@lemmy.world to c/linuxmemes@lemmy.world 124 comments fedilink hide all child comments
[β] mogoh@lemmy.ml 101 points 2 years ago (6 children) The systemd debate is basically dead. There are very few against it, but many accept it by now. Just avoid phoronix forum and some other places. permalink fedilink source hideshow 12 child comments replies: [β] exu@feditown.com 59 points 2 years ago (2 children) Anytime I see a Phoronix article (very loosely) about systemd or Wayland I fill my insults bingo card. permalink fedilink source parent hideshow 4 child comments replies: [β] IsoSpandy@lemm.ee 10 points 2 years ago (6 children) What's wrong with Wayland? I get the hate for systemd, even though I love it dearly, but I get the hate. But what's wrong with Wayland? It's amazing as far as I have used it. I started using with when Fedora 40 shipped plasma 6. permalink fedilink source parent hideshow 12 child comments replies: [β] rtxn@lemmy.world 28 points 2 years ago* (last edited 2 years ago) I'll preface this by saying that I'm a Wayland user (Hyprland, then KDE Plasma, and I'll be giving Cosmic a fair shot), and don't see myself returning to X and having to choose between massive screen tearing and massive input lag. Wayland is missing many features that are required for some people or some applications. There's no way for a multi-window application to tell the compositor where to place the windows, for example to have one window snap to and follow the other. Color profiles were implemented very recently. Wayland's isolation of applications, while a significant improvement to security, has made remote input software and xdotool-like programs highly dependent on third-party interoperability solutions (specifically dbus and XDG Desktop Portal). The same isolation broke most accessibility tools like screen readers. Dockable windows, like the toolbars in QT Creator or QOwnNotes, are often difficult or impossible to dock back into the main window. Because Wayland compositors have to implement all protocols (as opposed to deferring to the X.Org server; which is why wlroots is such a big deal) or rely on XDG Desktop Portal (which has never worked right for me), feature parity between compositors is never guaranteed, and especially problematic with GNOME dragging its heels. Wayland is nowhere near feature parity with X11 today, and that is a legitimate prohibitive issue for many people. Wayland will never reach total feature parity with X11 in some areas, and that will always be prohibitive for some people. But the worst (in my opinion) is the development process of the Wayland protocols. The proposal discussion threads read like the best and/or worst sitcom you've ever seen. It took them several months of back-and-forth just short of ad hominem attacks to decide how a window should set its icon. Several months for a pissing WINDOW ICON! permalink fedilink source parent [β] exu@feditown.com 7 points 2 years ago (1 child) Various mildly understandable to braindead reasons "it doesn't work" "breaks my workflow" "Xorg is better" "Nvidia" "no reason to use it" "being pushed by IBM" "no SSH forwarding" "has taken too long to get to current state" "when I last tried it 5 years ago it didn't work" permalink fedilink source parent hideshow 2 child comments replies: [β] Blaster_M@lemmy.world 14 points 2 years ago* permalink fedilink source parent [β] jj4211@lemmy.world 5 points 2 years ago I still have weird glitches where applications don't seem to update on screen (chrome and firefox, both natively doing wayland). Lack of any solution for programmatic geometry interaction. This one has been afflicted with 'perfect is enemy of good', as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative. The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The 'share your screen' was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened. Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent. I've been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts. permalink fedilink source parent [β] SomethingBurger@jlai.lu 5 points 2 years ago It's missing a lot of features that Wayland "developers" (spec writers) don't want to add because they personally don't need them. For the few features they actually add, they leave it to WM developers to implement them, thus creating different incompatible implementations. permalink fedilink source parent [β] Verat@sh.itjust.works 4 points 2 years ago For one thing they were so obsessed with security as a concept devleoping it that they completely ignored the use case of screen-readers for the visually impaired and prevent apps from accessing text from other apps and as far as I know it is still an issue. permalink fedilink source parent [β] rikudou@lemmings.world 3 points 2 years ago Well, Fedora 40 here as well and it just doesn't work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though. permalink fedilink source parent [β] possiblylinux127@lemmy.zip 1 point 2 years ago Part of me wants to troll and come up with crazy statements permalink fedilink source parent [β] TimeSquirrel@kbin.melroy.org 46 points 2 years ago (2 children) The systemd debate is basically dead. But the Super Nintendo vs. Sega Genesis/Megadrive debate rages on. permalink fedilink source parent hideshow 4 child comments replies: [β] PlasticExistence@lemmy.world 25 points 2 years ago (2 children) Because Sega does what Nintendonβt permalink fedilink source parent hideshow 4 child comments replies: [β] Thorry84@feddit.nl 8 points 2 years ago It has Blast Processing! permalink fedilink source parent [β] rikudou@lemmings.world 3 points 2 years ago (1 child) Like trying to destroy people's lives so they can make a few dollars. permalink fedilink source parent hideshow 2 child comments replies: [β] TimeSquirrel@kbin.melroy.org 1 point 2 years ago (1 child) Whoa, did I happen to miss something 30 years ago? What did they do? permalink fedilink source parent hideshow 2 child comments replies: [β] rikudou@lemmings.world 2 points 2 years ago I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they're rich and can afford it. permalink fedilink source parent [β] DmMacniel@feddit.org 9 points 2 years ago* (1 child) Both have great games. permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 9 points 2 years ago (1 child) Mega Drive is clearly better because that's the one I had as a child. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 8 points 2 years ago (1 child) I had neither... permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 14 points 2 years ago (1 child) Skill issue. Try the following: be born into a different family that did have a Mega Drive time travel back in time and give yourself a Mega Drive travel to an alternate universe (or as I like to call it, time travel sideways) where Mega Drives are standard issue at birth Β Hope this helps. Git gud. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent [β] tortina_original@lemmy.world 19 points 2 years ago (3 children) "Just avoid places that sysadmins and security guys frequent and get your opinions on systemd from memes and people running arch on home machine". Great plan. Systemd is absolute and utter shit, especially from security perspective. Noone was asking security guys but package maintainers. My favorite systemd thing is booting up a box with 6 NICs where only 1 was configured during the initial setup. Second favorite is betting on whether it will hang on reboot/shutdown. Great tool, 10/10. permalink fedilink source parent hideshow 6 child comments replies: [β] qjkxbmwvz@startrek.website 23 points 2 years ago* (last edited 2 years ago) (1 child) My favorite was when the behavior of a USB drive in /etc/fstab went from "hmm it's not plugged in at boot, I'll let the user know" to "not plugged in? Abort! Abort! We can't boot!" This change over previous init behavior was especially fun on headless machines... permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -1 points 2 years ago (2 children) You could just use systemd mounts like a normal person. Fstab is for critical partitions permalink fedilink source parent hideshow 4 child comments replies: [β] renzev@lemmy.world [S] 20 points 2 years ago (1 child) Fstab is for critical partitions Hush everyone, don't tell this guy about noauto, it'll burst his bubble permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -2 points 2 years ago (1 child) I've never seen it used in the wild permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent [β] qjkxbmwvz@startrek.website 8 points 2 years ago* (1 child) This happened to me when Debian switched from SysV to systemd. I am not the only person who experienced this (e.g., https://bbs.archlinux.org/viewtopic.php?id=147478 ). This is not to say the systemd behavior is wrong, but it essentially changed the behavior of fstab. Whether this is Debian's fault, Arch's fault (per the above link), systemd's fault, or my fault is a fair question. But this committed that most egregious of sins per our Lord and Savior Torvalds it broke my userspace. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -4 points 2 years ago That was a really long time ago. (2015) I don't understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd. permalink fedilink source parent [β] renzev@lemmy.world [S] 13 points 2 years ago (3 children) I've gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I haven't heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. The only arguments I hear in favor of systemd, even from the its diehard defenders, are justifications why it's not that bad. Not once have I heard someone advocate for systemd with reasoning that goes likes "Systemd is superior to legacy init systems because you can do X much easier" or "systemd is more secure because it's resistant against Y attack vector". It's always "Linus says it's allright" or "binary logfiles aren't a problem, you can just get them from journald instead of reading the file", or "everyone already uses it". When it comes to online discourse, systemd doesn't have advocates, it has apologists. permalink fedilink source parent hideshow 6 child comments replies: [β] pmc@lemmy.blahaj.zone 24 points 2 years ago* (1 child) Well, I'll tell you that I prefer systemd because I can comprehend its declarative unit files and dependency-based system a lot better than the shell script DSLs and runlevels that I've had to mess with in other init systems. systemctl status has a quite nice output that can be really handy when debugging units. I like being able to pull up logs for just about any service on my system with a simple journalctl command instead of researching where the log file is. permalink fedilink source parent hideshow 2 child comments replies: [β] renzev@lemmy.world [S] 1 point 2 years ago Thank you for the detailed response, very informative. You make a really good point about centralized logging, I can see how that can be very helpful when you run A LOT of different server process on one machine. I get centralized logging as a bonus of running everything in Docker, but I can see how it is nice to have logging as part of the init system if you want to run a lot of services natively. permalink fedilink source parent [β] InverseParallax@lemmy.world 10 points 2 years ago Linus had an epic flame war with the systemd idiots for breaking Linux stupidly: https://igurublog.wordpress.com/2014/04/03/tso-and-linus-and-the-impotent-rage-against-systemd/ He didn't do anything because he made it clear he owned the kernel and userspace was someone else's problem, but also that the systemd guys were absolute morons who were a danger to themselves and everyone else. permalink fedilink source parent [β] s_s@lemm.ee 0 points 2 years ago Iβve gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I havenβt heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. "Hi I'm new to Linux, I switched from Windows to Alpine Linux and my laptop's battery life has gone from 6 hours to 30 minutes before needing a charge." permalink fedilink source parent [β] mogoh@lemmy.ml 3 points 2 years ago (1 child) βJust avoid places that sysadmins and security guys frequent and get your opinions on systemd from memes and people running arch on home machineβ. Great plan. So salty. Also twisting the things I said. I for sure like to visit phoronix, but I avoid the phoronix forum and advice was to avoid the forum. Noone was asking security guys but package maintainers. citation needed. Keep using Devuan if it makes you happy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world -2 points 2 years ago (3 children) Not really interested in debating with average "I run arch btw" user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do, so having such a smart advice coming from you is not a surprise at all. I could, after all, just roll out my own distro if I am not happy, amirite? I run systemd machines because I don't have a choice. It doesn't make it any less of a shit. Simple as that. But hey, tell me some more about systemd, I am really new to all this π€ permalink fedilink source parent hideshow 6 child comments replies: [β] wormer@lemmy.ml 5 points 2 years ago Buddy lay off the Rick and Morty and take a shower "I'm not in the same universe as you!!!!!!" Get a grip permalink fedilink source parent [β] mogoh@lemmy.ml 5 points 2 years ago (1 child) Not really interested in debating with average βI run arch btwβ user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do Sir, this is the Linux memes sublemmy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world 1 point 2 years ago Right. I am dumb ππ€ permalink fedilink source parent [β] renzev@lemmy.world [S] 5 points 2 years ago Out of curiosity, why exactly do you not have a choice in not running systemd? Is it company policy / are they clients' machines? permalink fedilink source parent [β] Blisterexe@lemmy.zip 7 points 2 years ago* Although there is an argument for not using it on (very) old systems permalink fedilink source parent [β] corsicanguppy@lemmy.ca 7 points 2 years ago The systemd debate is basically dead. Not until it isn't shite. permalink fedilink source parent [β] ExhibiCat@lemmynsfw.com 3 points 2 years ago I'm against it but I just found that BSD doesn't have it and I fits me better than Linux in many other ways too. So there's just no need left to debate :) permalink fedilink source parent
[β] exu@feditown.com 59 points 2 years ago (2 children) Anytime I see a Phoronix article (very loosely) about systemd or Wayland I fill my insults bingo card. permalink fedilink source parent hideshow 4 child comments replies: [β] IsoSpandy@lemm.ee 10 points 2 years ago (6 children) What's wrong with Wayland? I get the hate for systemd, even though I love it dearly, but I get the hate. But what's wrong with Wayland? It's amazing as far as I have used it. I started using with when Fedora 40 shipped plasma 6. permalink fedilink source parent hideshow 12 child comments replies: [β] rtxn@lemmy.world 28 points 2 years ago* (last edited 2 years ago) I'll preface this by saying that I'm a Wayland user (Hyprland, then KDE Plasma, and I'll be giving Cosmic a fair shot), and don't see myself returning to X and having to choose between massive screen tearing and massive input lag. Wayland is missing many features that are required for some people or some applications. There's no way for a multi-window application to tell the compositor where to place the windows, for example to have one window snap to and follow the other. Color profiles were implemented very recently. Wayland's isolation of applications, while a significant improvement to security, has made remote input software and xdotool-like programs highly dependent on third-party interoperability solutions (specifically dbus and XDG Desktop Portal). The same isolation broke most accessibility tools like screen readers. Dockable windows, like the toolbars in QT Creator or QOwnNotes, are often difficult or impossible to dock back into the main window. Because Wayland compositors have to implement all protocols (as opposed to deferring to the X.Org server; which is why wlroots is such a big deal) or rely on XDG Desktop Portal (which has never worked right for me), feature parity between compositors is never guaranteed, and especially problematic with GNOME dragging its heels. Wayland is nowhere near feature parity with X11 today, and that is a legitimate prohibitive issue for many people. Wayland will never reach total feature parity with X11 in some areas, and that will always be prohibitive for some people. But the worst (in my opinion) is the development process of the Wayland protocols. The proposal discussion threads read like the best and/or worst sitcom you've ever seen. It took them several months of back-and-forth just short of ad hominem attacks to decide how a window should set its icon. Several months for a pissing WINDOW ICON! permalink fedilink source parent [β] exu@feditown.com 7 points 2 years ago (1 child) Various mildly understandable to braindead reasons "it doesn't work" "breaks my workflow" "Xorg is better" "Nvidia" "no reason to use it" "being pushed by IBM" "no SSH forwarding" "has taken too long to get to current state" "when I last tried it 5 years ago it didn't work" permalink fedilink source parent hideshow 2 child comments replies: [β] Blaster_M@lemmy.world 14 points 2 years ago* permalink fedilink source parent [β] jj4211@lemmy.world 5 points 2 years ago I still have weird glitches where applications don't seem to update on screen (chrome and firefox, both natively doing wayland). Lack of any solution for programmatic geometry interaction. This one has been afflicted with 'perfect is enemy of good', as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative. The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The 'share your screen' was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened. Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent. I've been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts. permalink fedilink source parent [β] SomethingBurger@jlai.lu 5 points 2 years ago It's missing a lot of features that Wayland "developers" (spec writers) don't want to add because they personally don't need them. For the few features they actually add, they leave it to WM developers to implement them, thus creating different incompatible implementations. permalink fedilink source parent [β] Verat@sh.itjust.works 4 points 2 years ago For one thing they were so obsessed with security as a concept devleoping it that they completely ignored the use case of screen-readers for the visually impaired and prevent apps from accessing text from other apps and as far as I know it is still an issue. permalink fedilink source parent [β] rikudou@lemmings.world 3 points 2 years ago Well, Fedora 40 here as well and it just doesn't work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though. permalink fedilink source parent [β] possiblylinux127@lemmy.zip 1 point 2 years ago Part of me wants to troll and come up with crazy statements permalink fedilink source parent
[β] IsoSpandy@lemm.ee 10 points 2 years ago (6 children) What's wrong with Wayland? I get the hate for systemd, even though I love it dearly, but I get the hate. But what's wrong with Wayland? It's amazing as far as I have used it. I started using with when Fedora 40 shipped plasma 6. permalink fedilink source parent hideshow 12 child comments replies: [β] rtxn@lemmy.world 28 points 2 years ago* (last edited 2 years ago) I'll preface this by saying that I'm a Wayland user (Hyprland, then KDE Plasma, and I'll be giving Cosmic a fair shot), and don't see myself returning to X and having to choose between massive screen tearing and massive input lag. Wayland is missing many features that are required for some people or some applications. There's no way for a multi-window application to tell the compositor where to place the windows, for example to have one window snap to and follow the other. Color profiles were implemented very recently. Wayland's isolation of applications, while a significant improvement to security, has made remote input software and xdotool-like programs highly dependent on third-party interoperability solutions (specifically dbus and XDG Desktop Portal). The same isolation broke most accessibility tools like screen readers. Dockable windows, like the toolbars in QT Creator or QOwnNotes, are often difficult or impossible to dock back into the main window. Because Wayland compositors have to implement all protocols (as opposed to deferring to the X.Org server; which is why wlroots is such a big deal) or rely on XDG Desktop Portal (which has never worked right for me), feature parity between compositors is never guaranteed, and especially problematic with GNOME dragging its heels. Wayland is nowhere near feature parity with X11 today, and that is a legitimate prohibitive issue for many people. Wayland will never reach total feature parity with X11 in some areas, and that will always be prohibitive for some people. But the worst (in my opinion) is the development process of the Wayland protocols. The proposal discussion threads read like the best and/or worst sitcom you've ever seen. It took them several months of back-and-forth just short of ad hominem attacks to decide how a window should set its icon. Several months for a pissing WINDOW ICON! permalink fedilink source parent [β] exu@feditown.com 7 points 2 years ago (1 child) Various mildly understandable to braindead reasons "it doesn't work" "breaks my workflow" "Xorg is better" "Nvidia" "no reason to use it" "being pushed by IBM" "no SSH forwarding" "has taken too long to get to current state" "when I last tried it 5 years ago it didn't work" permalink fedilink source parent hideshow 2 child comments replies: [β] Blaster_M@lemmy.world 14 points 2 years ago* permalink fedilink source parent [β] jj4211@lemmy.world 5 points 2 years ago I still have weird glitches where applications don't seem to update on screen (chrome and firefox, both natively doing wayland). Lack of any solution for programmatic geometry interaction. This one has been afflicted with 'perfect is enemy of good', as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative. The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The 'share your screen' was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened. Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent. I've been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts. permalink fedilink source parent [β] SomethingBurger@jlai.lu 5 points 2 years ago It's missing a lot of features that Wayland "developers" (spec writers) don't want to add because they personally don't need them. For the few features they actually add, they leave it to WM developers to implement them, thus creating different incompatible implementations. permalink fedilink source parent [β] Verat@sh.itjust.works 4 points 2 years ago For one thing they were so obsessed with security as a concept devleoping it that they completely ignored the use case of screen-readers for the visually impaired and prevent apps from accessing text from other apps and as far as I know it is still an issue. permalink fedilink source parent [β] rikudou@lemmings.world 3 points 2 years ago Well, Fedora 40 here as well and it just doesn't work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though. permalink fedilink source parent
[β] rtxn@lemmy.world 28 points 2 years ago* (last edited 2 years ago) I'll preface this by saying that I'm a Wayland user (Hyprland, then KDE Plasma, and I'll be giving Cosmic a fair shot), and don't see myself returning to X and having to choose between massive screen tearing and massive input lag. Wayland is missing many features that are required for some people or some applications. There's no way for a multi-window application to tell the compositor where to place the windows, for example to have one window snap to and follow the other. Color profiles were implemented very recently. Wayland's isolation of applications, while a significant improvement to security, has made remote input software and xdotool-like programs highly dependent on third-party interoperability solutions (specifically dbus and XDG Desktop Portal). The same isolation broke most accessibility tools like screen readers. Dockable windows, like the toolbars in QT Creator or QOwnNotes, are often difficult or impossible to dock back into the main window. Because Wayland compositors have to implement all protocols (as opposed to deferring to the X.Org server; which is why wlroots is such a big deal) or rely on XDG Desktop Portal (which has never worked right for me), feature parity between compositors is never guaranteed, and especially problematic with GNOME dragging its heels. Wayland is nowhere near feature parity with X11 today, and that is a legitimate prohibitive issue for many people. Wayland will never reach total feature parity with X11 in some areas, and that will always be prohibitive for some people. But the worst (in my opinion) is the development process of the Wayland protocols. The proposal discussion threads read like the best and/or worst sitcom you've ever seen. It took them several months of back-and-forth just short of ad hominem attacks to decide how a window should set its icon. Several months for a pissing WINDOW ICON! permalink fedilink source parent
[β] exu@feditown.com 7 points 2 years ago (1 child) Various mildly understandable to braindead reasons "it doesn't work" "breaks my workflow" "Xorg is better" "Nvidia" "no reason to use it" "being pushed by IBM" "no SSH forwarding" "has taken too long to get to current state" "when I last tried it 5 years ago it didn't work" permalink fedilink source parent hideshow 2 child comments replies: [β] Blaster_M@lemmy.world 14 points 2 years ago* permalink fedilink source parent
[β] jj4211@lemmy.world 5 points 2 years ago I still have weird glitches where applications don't seem to update on screen (chrome and firefox, both natively doing wayland). Lack of any solution for programmatic geometry interaction. This one has been afflicted with 'perfect is enemy of good', as the X way of allowing manual coordinates be specified is seen as potentially too limiting (reconciling geometry with scaling, non-traditional displays), so they do nothing instead of proposing an alternative. The different security choices also curtail functionality. Great, better security for input, uh oh, less flexibility in input solutions. The 'share your screen' was a mess for a long time (and might be for some others still). Good the share your screen has a better security model, but frustrating when it happened. Inconsistent experience between Wayland implementations. Since Wayland is a reference rather than a singular server, Plasma, Gnome, and others can act a little different. Like one supporting server side decorations and another being so philosophically opposed to the concept that they refuse to cater to it. While a compositing window manager effectively owned much of the hard work even in X, the X behavior between compositors were fairly consistent. I've been using Plasma as a Wayland compositor after many failed attempts, and it still has papercuts. permalink fedilink source parent
[β] SomethingBurger@jlai.lu 5 points 2 years ago It's missing a lot of features that Wayland "developers" (spec writers) don't want to add because they personally don't need them. For the few features they actually add, they leave it to WM developers to implement them, thus creating different incompatible implementations. permalink fedilink source parent
[β] Verat@sh.itjust.works 4 points 2 years ago For one thing they were so obsessed with security as a concept devleoping it that they completely ignored the use case of screen-readers for the visually impaired and prevent apps from accessing text from other apps and as far as I know it is still an issue. permalink fedilink source parent
[β] rikudou@lemmings.world 3 points 2 years ago Well, Fedora 40 here as well and it just doesn't work on my computer. Sure, Nvidia, blah blah blah. X does work flawlessly on my machine, though. permalink fedilink source parent
[β] possiblylinux127@lemmy.zip 1 point 2 years ago Part of me wants to troll and come up with crazy statements permalink fedilink source parent
[β] TimeSquirrel@kbin.melroy.org 46 points 2 years ago (2 children) The systemd debate is basically dead. But the Super Nintendo vs. Sega Genesis/Megadrive debate rages on. permalink fedilink source parent hideshow 4 child comments replies: [β] PlasticExistence@lemmy.world 25 points 2 years ago (2 children) Because Sega does what Nintendonβt permalink fedilink source parent hideshow 4 child comments replies: [β] Thorry84@feddit.nl 8 points 2 years ago It has Blast Processing! permalink fedilink source parent [β] rikudou@lemmings.world 3 points 2 years ago (1 child) Like trying to destroy people's lives so they can make a few dollars. permalink fedilink source parent hideshow 2 child comments replies: [β] TimeSquirrel@kbin.melroy.org 1 point 2 years ago (1 child) Whoa, did I happen to miss something 30 years ago? What did they do? permalink fedilink source parent hideshow 2 child comments replies: [β] rikudou@lemmings.world 2 points 2 years ago I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they're rich and can afford it. permalink fedilink source parent [β] DmMacniel@feddit.org 9 points 2 years ago* (1 child) Both have great games. permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 9 points 2 years ago (1 child) Mega Drive is clearly better because that's the one I had as a child. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 8 points 2 years ago (1 child) I had neither... permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 14 points 2 years ago (1 child) Skill issue. Try the following: be born into a different family that did have a Mega Drive time travel back in time and give yourself a Mega Drive travel to an alternate universe (or as I like to call it, time travel sideways) where Mega Drives are standard issue at birth Β Hope this helps. Git gud. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent
[β] PlasticExistence@lemmy.world 25 points 2 years ago (2 children) Because Sega does what Nintendonβt permalink fedilink source parent hideshow 4 child comments replies: [β] Thorry84@feddit.nl 8 points 2 years ago It has Blast Processing! permalink fedilink source parent [β] rikudou@lemmings.world 3 points 2 years ago (1 child) Like trying to destroy people's lives so they can make a few dollars. permalink fedilink source parent hideshow 2 child comments replies: [β] TimeSquirrel@kbin.melroy.org 1 point 2 years ago (1 child) Whoa, did I happen to miss something 30 years ago? What did they do? permalink fedilink source parent hideshow 2 child comments replies: [β] rikudou@lemmings.world 2 points 2 years ago I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they're rich and can afford it. permalink fedilink source parent
[β] Thorry84@feddit.nl 8 points 2 years ago It has Blast Processing! permalink fedilink source parent
[β] rikudou@lemmings.world 3 points 2 years ago (1 child) Like trying to destroy people's lives so they can make a few dollars. permalink fedilink source parent hideshow 2 child comments replies: [β] TimeSquirrel@kbin.melroy.org 1 point 2 years ago (1 child) Whoa, did I happen to miss something 30 years ago? What did they do? permalink fedilink source parent hideshow 2 child comments replies: [β] rikudou@lemmings.world 2 points 2 years ago I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they're rich and can afford it. permalink fedilink source parent
[β] TimeSquirrel@kbin.melroy.org 1 point 2 years ago (1 child) Whoa, did I happen to miss something 30 years ago? What did they do? permalink fedilink source parent hideshow 2 child comments replies: [β] rikudou@lemmings.world 2 points 2 years ago I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they're rich and can afford it. permalink fedilink source parent
[β] rikudou@lemmings.world 2 points 2 years ago I was talking about Nintendo, they constantly sue people (and other companies) for obscure amounts of money just because they're rich and can afford it. permalink fedilink source parent
[β] DmMacniel@feddit.org 9 points 2 years ago* (1 child) Both have great games. permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 9 points 2 years ago (1 child) Mega Drive is clearly better because that's the one I had as a child. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 8 points 2 years ago (1 child) I had neither... permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 14 points 2 years ago (1 child) Skill issue. Try the following: be born into a different family that did have a Mega Drive time travel back in time and give yourself a Mega Drive travel to an alternate universe (or as I like to call it, time travel sideways) where Mega Drives are standard issue at birth Β Hope this helps. Git gud. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent
[β] abfarid@startrek.website 9 points 2 years ago (1 child) Mega Drive is clearly better because that's the one I had as a child. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 8 points 2 years ago (1 child) I had neither... permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 14 points 2 years ago (1 child) Skill issue. Try the following: be born into a different family that did have a Mega Drive time travel back in time and give yourself a Mega Drive travel to an alternate universe (or as I like to call it, time travel sideways) where Mega Drives are standard issue at birth Β Hope this helps. Git gud. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent
[β] DmMacniel@feddit.org 8 points 2 years ago (1 child) I had neither... permalink fedilink source parent hideshow 2 child comments replies: [β] abfarid@startrek.website 14 points 2 years ago (1 child) Skill issue. Try the following: be born into a different family that did have a Mega Drive time travel back in time and give yourself a Mega Drive travel to an alternate universe (or as I like to call it, time travel sideways) where Mega Drives are standard issue at birth Β Hope this helps. Git gud. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent
[β] abfarid@startrek.website 14 points 2 years ago (1 child) Skill issue. Try the following: be born into a different family that did have a Mega Drive time travel back in time and give yourself a Mega Drive travel to an alternate universe (or as I like to call it, time travel sideways) where Mega Drives are standard issue at birth Β Hope this helps. Git gud. permalink fedilink source parent hideshow 2 child comments replies: [β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent
[β] DmMacniel@feddit.org 7 points 2 years ago Thanks for the troubleshooting, I will consider those steps. permalink fedilink source parent
[β] tortina_original@lemmy.world 19 points 2 years ago (3 children) "Just avoid places that sysadmins and security guys frequent and get your opinions on systemd from memes and people running arch on home machine". Great plan. Systemd is absolute and utter shit, especially from security perspective. Noone was asking security guys but package maintainers. My favorite systemd thing is booting up a box with 6 NICs where only 1 was configured during the initial setup. Second favorite is betting on whether it will hang on reboot/shutdown. Great tool, 10/10. permalink fedilink source parent hideshow 6 child comments replies: [β] qjkxbmwvz@startrek.website 23 points 2 years ago* (last edited 2 years ago) (1 child) My favorite was when the behavior of a USB drive in /etc/fstab went from "hmm it's not plugged in at boot, I'll let the user know" to "not plugged in? Abort! Abort! We can't boot!" This change over previous init behavior was especially fun on headless machines... permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -1 points 2 years ago (2 children) You could just use systemd mounts like a normal person. Fstab is for critical partitions permalink fedilink source parent hideshow 4 child comments replies: [β] renzev@lemmy.world [S] 20 points 2 years ago (1 child) Fstab is for critical partitions Hush everyone, don't tell this guy about noauto, it'll burst his bubble permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -2 points 2 years ago (1 child) I've never seen it used in the wild permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent [β] qjkxbmwvz@startrek.website 8 points 2 years ago* (1 child) This happened to me when Debian switched from SysV to systemd. I am not the only person who experienced this (e.g., https://bbs.archlinux.org/viewtopic.php?id=147478 ). This is not to say the systemd behavior is wrong, but it essentially changed the behavior of fstab. Whether this is Debian's fault, Arch's fault (per the above link), systemd's fault, or my fault is a fair question. But this committed that most egregious of sins per our Lord and Savior Torvalds it broke my userspace. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -4 points 2 years ago That was a really long time ago. (2015) I don't understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd. permalink fedilink source parent [β] renzev@lemmy.world [S] 13 points 2 years ago (3 children) I've gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I haven't heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. The only arguments I hear in favor of systemd, even from the its diehard defenders, are justifications why it's not that bad. Not once have I heard someone advocate for systemd with reasoning that goes likes "Systemd is superior to legacy init systems because you can do X much easier" or "systemd is more secure because it's resistant against Y attack vector". It's always "Linus says it's allright" or "binary logfiles aren't a problem, you can just get them from journald instead of reading the file", or "everyone already uses it". When it comes to online discourse, systemd doesn't have advocates, it has apologists. permalink fedilink source parent hideshow 6 child comments replies: [β] pmc@lemmy.blahaj.zone 24 points 2 years ago* (1 child) Well, I'll tell you that I prefer systemd because I can comprehend its declarative unit files and dependency-based system a lot better than the shell script DSLs and runlevels that I've had to mess with in other init systems. systemctl status has a quite nice output that can be really handy when debugging units. I like being able to pull up logs for just about any service on my system with a simple journalctl command instead of researching where the log file is. permalink fedilink source parent hideshow 2 child comments replies: [β] renzev@lemmy.world [S] 1 point 2 years ago Thank you for the detailed response, very informative. You make a really good point about centralized logging, I can see how that can be very helpful when you run A LOT of different server process on one machine. I get centralized logging as a bonus of running everything in Docker, but I can see how it is nice to have logging as part of the init system if you want to run a lot of services natively. permalink fedilink source parent [β] InverseParallax@lemmy.world 10 points 2 years ago Linus had an epic flame war with the systemd idiots for breaking Linux stupidly: https://igurublog.wordpress.com/2014/04/03/tso-and-linus-and-the-impotent-rage-against-systemd/ He didn't do anything because he made it clear he owned the kernel and userspace was someone else's problem, but also that the systemd guys were absolute morons who were a danger to themselves and everyone else. permalink fedilink source parent [β] s_s@lemm.ee 0 points 2 years ago Iβve gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I havenβt heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. "Hi I'm new to Linux, I switched from Windows to Alpine Linux and my laptop's battery life has gone from 6 hours to 30 minutes before needing a charge." permalink fedilink source parent [β] mogoh@lemmy.ml 3 points 2 years ago (1 child) βJust avoid places that sysadmins and security guys frequent and get your opinions on systemd from memes and people running arch on home machineβ. Great plan. So salty. Also twisting the things I said. I for sure like to visit phoronix, but I avoid the phoronix forum and advice was to avoid the forum. Noone was asking security guys but package maintainers. citation needed. Keep using Devuan if it makes you happy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world -2 points 2 years ago (3 children) Not really interested in debating with average "I run arch btw" user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do, so having such a smart advice coming from you is not a surprise at all. I could, after all, just roll out my own distro if I am not happy, amirite? I run systemd machines because I don't have a choice. It doesn't make it any less of a shit. Simple as that. But hey, tell me some more about systemd, I am really new to all this π€ permalink fedilink source parent hideshow 6 child comments replies: [β] wormer@lemmy.ml 5 points 2 years ago Buddy lay off the Rick and Morty and take a shower "I'm not in the same universe as you!!!!!!" Get a grip permalink fedilink source parent [β] mogoh@lemmy.ml 5 points 2 years ago (1 child) Not really interested in debating with average βI run arch btwβ user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do Sir, this is the Linux memes sublemmy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world 1 point 2 years ago Right. I am dumb ππ€ permalink fedilink source parent [β] renzev@lemmy.world [S] 5 points 2 years ago Out of curiosity, why exactly do you not have a choice in not running systemd? Is it company policy / are they clients' machines? permalink fedilink source parent
[β] qjkxbmwvz@startrek.website 23 points 2 years ago* (last edited 2 years ago) (1 child) My favorite was when the behavior of a USB drive in /etc/fstab went from "hmm it's not plugged in at boot, I'll let the user know" to "not plugged in? Abort! Abort! We can't boot!" This change over previous init behavior was especially fun on headless machines... permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -1 points 2 years ago (2 children) You could just use systemd mounts like a normal person. Fstab is for critical partitions permalink fedilink source parent hideshow 4 child comments replies: [β] renzev@lemmy.world [S] 20 points 2 years ago (1 child) Fstab is for critical partitions Hush everyone, don't tell this guy about noauto, it'll burst his bubble permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -2 points 2 years ago (1 child) I've never seen it used in the wild permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent [β] qjkxbmwvz@startrek.website 8 points 2 years ago* (1 child) This happened to me when Debian switched from SysV to systemd. I am not the only person who experienced this (e.g., https://bbs.archlinux.org/viewtopic.php?id=147478 ). This is not to say the systemd behavior is wrong, but it essentially changed the behavior of fstab. Whether this is Debian's fault, Arch's fault (per the above link), systemd's fault, or my fault is a fair question. But this committed that most egregious of sins per our Lord and Savior Torvalds it broke my userspace. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -4 points 2 years ago That was a really long time ago. (2015) I don't understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd. permalink fedilink source parent
[β] possiblylinux127@lemmy.zip -1 points 2 years ago (2 children) You could just use systemd mounts like a normal person. Fstab is for critical partitions permalink fedilink source parent hideshow 4 child comments replies: [β] renzev@lemmy.world [S] 20 points 2 years ago (1 child) Fstab is for critical partitions Hush everyone, don't tell this guy about noauto, it'll burst his bubble permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -2 points 2 years ago (1 child) I've never seen it used in the wild permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent [β] qjkxbmwvz@startrek.website 8 points 2 years ago* (1 child) This happened to me when Debian switched from SysV to systemd. I am not the only person who experienced this (e.g., https://bbs.archlinux.org/viewtopic.php?id=147478 ). This is not to say the systemd behavior is wrong, but it essentially changed the behavior of fstab. Whether this is Debian's fault, Arch's fault (per the above link), systemd's fault, or my fault is a fair question. But this committed that most egregious of sins per our Lord and Savior Torvalds it broke my userspace. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -4 points 2 years ago That was a really long time ago. (2015) I don't understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd. permalink fedilink source parent
[β] renzev@lemmy.world [S] 20 points 2 years ago (1 child) Fstab is for critical partitions Hush everyone, don't tell this guy about noauto, it'll burst his bubble permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -2 points 2 years ago (1 child) I've never seen it used in the wild permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent
[β] possiblylinux127@lemmy.zip -2 points 2 years ago (1 child) I've never seen it used in the wild permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent
[β] InverseParallax@lemmy.world 8 points 2 years ago (1 child) Jesus, I mount everything manually from noauto, except root. If nfs isn't available, I don't want my system to hang, typing mount takes 2 seconds. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent
[β] possiblylinux127@lemmy.zip 0 points 2 years ago* (1 child) Wouldn't your NFS not mount in that case? Wouldn't you want it to retry periodically? Also, what happens to your service when NFS isn't available? Sounds like systemd mounts are better in this case (unless the device is non critical) permalink fedilink source parent hideshow 2 child comments replies: [β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent
[β] InverseParallax@lemmy.world 4 points 2 years ago I mount it manually when I'm sure everything is up. The issue is, I use this workstation to bring up the rest of my network and servers if they're down, can't have a hard dependency on nfs if it's job is to bring up nfs. permalink fedilink source parent
[β] qjkxbmwvz@startrek.website 8 points 2 years ago* (1 child) This happened to me when Debian switched from SysV to systemd. I am not the only person who experienced this (e.g., https://bbs.archlinux.org/viewtopic.php?id=147478 ). This is not to say the systemd behavior is wrong, but it essentially changed the behavior of fstab. Whether this is Debian's fault, Arch's fault (per the above link), systemd's fault, or my fault is a fair question. But this committed that most egregious of sins per our Lord and Savior Torvalds it broke my userspace. permalink fedilink source parent hideshow 2 child comments replies: [β] possiblylinux127@lemmy.zip -4 points 2 years ago That was a really long time ago. (2015) I don't understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd. permalink fedilink source parent
[β] possiblylinux127@lemmy.zip -4 points 2 years ago That was a really long time ago. (2015) I don't understand why you are holding a grudge for almost 10 years. Most people have never used a system without systemd. permalink fedilink source parent
[β] renzev@lemmy.world [S] 13 points 2 years ago (3 children) I've gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I haven't heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. The only arguments I hear in favor of systemd, even from the its diehard defenders, are justifications why it's not that bad. Not once have I heard someone advocate for systemd with reasoning that goes likes "Systemd is superior to legacy init systems because you can do X much easier" or "systemd is more secure because it's resistant against Y attack vector". It's always "Linus says it's allright" or "binary logfiles aren't a problem, you can just get them from journald instead of reading the file", or "everyone already uses it". When it comes to online discourse, systemd doesn't have advocates, it has apologists. permalink fedilink source parent hideshow 6 child comments replies: [β] pmc@lemmy.blahaj.zone 24 points 2 years ago* (1 child) Well, I'll tell you that I prefer systemd because I can comprehend its declarative unit files and dependency-based system a lot better than the shell script DSLs and runlevels that I've had to mess with in other init systems. systemctl status has a quite nice output that can be really handy when debugging units. I like being able to pull up logs for just about any service on my system with a simple journalctl command instead of researching where the log file is. permalink fedilink source parent hideshow 2 child comments replies: [β] renzev@lemmy.world [S] 1 point 2 years ago Thank you for the detailed response, very informative. You make a really good point about centralized logging, I can see how that can be very helpful when you run A LOT of different server process on one machine. I get centralized logging as a bonus of running everything in Docker, but I can see how it is nice to have logging as part of the init system if you want to run a lot of services natively. permalink fedilink source parent [β] InverseParallax@lemmy.world 10 points 2 years ago Linus had an epic flame war with the systemd idiots for breaking Linux stupidly: https://igurublog.wordpress.com/2014/04/03/tso-and-linus-and-the-impotent-rage-against-systemd/ He didn't do anything because he made it clear he owned the kernel and userspace was someone else's problem, but also that the systemd guys were absolute morons who were a danger to themselves and everyone else. permalink fedilink source parent [β] s_s@lemm.ee 0 points 2 years ago Iβve gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I havenβt heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. "Hi I'm new to Linux, I switched from Windows to Alpine Linux and my laptop's battery life has gone from 6 hours to 30 minutes before needing a charge." permalink fedilink source parent
[β] pmc@lemmy.blahaj.zone 24 points 2 years ago* (1 child) Well, I'll tell you that I prefer systemd because I can comprehend its declarative unit files and dependency-based system a lot better than the shell script DSLs and runlevels that I've had to mess with in other init systems. systemctl status has a quite nice output that can be really handy when debugging units. I like being able to pull up logs for just about any service on my system with a simple journalctl command instead of researching where the log file is. permalink fedilink source parent hideshow 2 child comments replies: [β] renzev@lemmy.world [S] 1 point 2 years ago Thank you for the detailed response, very informative. You make a really good point about centralized logging, I can see how that can be very helpful when you run A LOT of different server process on one machine. I get centralized logging as a bonus of running everything in Docker, but I can see how it is nice to have logging as part of the init system if you want to run a lot of services natively. permalink fedilink source parent
[β] renzev@lemmy.world [S] 1 point 2 years ago Thank you for the detailed response, very informative. You make a really good point about centralized logging, I can see how that can be very helpful when you run A LOT of different server process on one machine. I get centralized logging as a bonus of running everything in Docker, but I can see how it is nice to have logging as part of the init system if you want to run a lot of services natively. permalink fedilink source parent
[β] InverseParallax@lemmy.world 10 points 2 years ago Linus had an epic flame war with the systemd idiots for breaking Linux stupidly: https://igurublog.wordpress.com/2014/04/03/tso-and-linus-and-the-impotent-rage-against-systemd/ He didn't do anything because he made it clear he owned the kernel and userspace was someone else's problem, but also that the systemd guys were absolute morons who were a danger to themselves and everyone else. permalink fedilink source parent
[β] s_s@lemm.ee 0 points 2 years ago Iβve gotten into quite a lot of systemd-related flame wars so far, and what strikes me is that I havenβt heard a single reason why systemd is good and should be used in favor of openrc/sysvinit/whatever. "Hi I'm new to Linux, I switched from Windows to Alpine Linux and my laptop's battery life has gone from 6 hours to 30 minutes before needing a charge." permalink fedilink source parent
[β] mogoh@lemmy.ml 3 points 2 years ago (1 child) βJust avoid places that sysadmins and security guys frequent and get your opinions on systemd from memes and people running arch on home machineβ. Great plan. So salty. Also twisting the things I said. I for sure like to visit phoronix, but I avoid the phoronix forum and advice was to avoid the forum. Noone was asking security guys but package maintainers. citation needed. Keep using Devuan if it makes you happy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world -2 points 2 years ago (3 children) Not really interested in debating with average "I run arch btw" user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do, so having such a smart advice coming from you is not a surprise at all. I could, after all, just roll out my own distro if I am not happy, amirite? I run systemd machines because I don't have a choice. It doesn't make it any less of a shit. Simple as that. But hey, tell me some more about systemd, I am really new to all this π€ permalink fedilink source parent hideshow 6 child comments replies: [β] wormer@lemmy.ml 5 points 2 years ago Buddy lay off the Rick and Morty and take a shower "I'm not in the same universe as you!!!!!!" Get a grip permalink fedilink source parent [β] mogoh@lemmy.ml 5 points 2 years ago (1 child) Not really interested in debating with average βI run arch btwβ user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do Sir, this is the Linux memes sublemmy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world 1 point 2 years ago Right. I am dumb ππ€ permalink fedilink source parent [β] renzev@lemmy.world [S] 5 points 2 years ago Out of curiosity, why exactly do you not have a choice in not running systemd? Is it company policy / are they clients' machines? permalink fedilink source parent
[β] tortina_original@lemmy.world -2 points 2 years ago (3 children) Not really interested in debating with average "I run arch btw" user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do, so having such a smart advice coming from you is not a surprise at all. I could, after all, just roll out my own distro if I am not happy, amirite? I run systemd machines because I don't have a choice. It doesn't make it any less of a shit. Simple as that. But hey, tell me some more about systemd, I am really new to all this π€ permalink fedilink source parent hideshow 6 child comments replies: [β] wormer@lemmy.ml 5 points 2 years ago Buddy lay off the Rick and Morty and take a shower "I'm not in the same universe as you!!!!!!" Get a grip permalink fedilink source parent [β] mogoh@lemmy.ml 5 points 2 years ago (1 child) Not really interested in debating with average βI run arch btwβ user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do Sir, this is the Linux memes sublemmy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world 1 point 2 years ago Right. I am dumb ππ€ permalink fedilink source parent [β] renzev@lemmy.world [S] 5 points 2 years ago Out of curiosity, why exactly do you not have a choice in not running systemd? Is it company policy / are they clients' machines? permalink fedilink source parent
[β] wormer@lemmy.ml 5 points 2 years ago Buddy lay off the Rick and Morty and take a shower "I'm not in the same universe as you!!!!!!" Get a grip permalink fedilink source parent
[β] mogoh@lemmy.ml 5 points 2 years ago (1 child) Not really interested in debating with average βI run arch btwβ user. We are not in the same universe, things I have to audit and maintain are not in the same universe with things you do Sir, this is the Linux memes sublemmy. permalink fedilink source parent hideshow 2 child comments replies: [β] tortina_original@lemmy.world 1 point 2 years ago Right. I am dumb ππ€ permalink fedilink source parent
[β] tortina_original@lemmy.world 1 point 2 years ago Right. I am dumb ππ€ permalink fedilink source parent
[β] renzev@lemmy.world [S] 5 points 2 years ago Out of curiosity, why exactly do you not have a choice in not running systemd? Is it company policy / are they clients' machines? permalink fedilink source parent
[β] Blisterexe@lemmy.zip 7 points 2 years ago* Although there is an argument for not using it on (very) old systems permalink fedilink source parent
[β] corsicanguppy@lemmy.ca 7 points 2 years ago The systemd debate is basically dead. Not until it isn't shite. permalink fedilink source parent
[β] ExhibiCat@lemmynsfw.com 3 points 2 years ago I'm against it but I just found that BSD doesn't have it and I fits me better than Linux in many other ways too. So there's just no need left to debate :) permalink fedilink source parent