GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    iced depresso (icedquinn@blob.cat)'s status on Saturday, 20-Sep-2025 06:52:29 JST iced depresso iced depresso
    if you still hate systemd, why?
    serious question
    In conversation about 4 months ago from blob.cat permalink
    • Johnny Peligro likes this.
    • Embed this notice
      Blurry Moon (sun@shitposter.world)'s status on Saturday, 20-Sep-2025 06:52:27 JST Blurry Moon Blurry Moon
      in reply to
      @icedquinn it works pretty good these days
      In conversation about 4 months ago permalink
      Johnny Peligro likes this.
    • Embed this notice
      fiat volvntas tva (scathach@stereophonic.space)'s status on Saturday, 20-Sep-2025 07:02:40 JST fiat volvntas tva fiat volvntas tva
      in reply to
      @icedquinn I love systemd as an init system and service manager but I really dislike how it's trying to replace userspace

      Wish there was an init system compatible with systemd units (especially including sandboxing) but that didn't try to be the Everything Daemon
      In conversation about 4 months ago permalink
      iced depresso likes this.
    • Embed this notice
      jesu (jesu@pl.kotobank.ch)'s status on Saturday, 20-Sep-2025 07:07:51 JST jesu jesu
      in reply to
      @icedquinn spontaneous freezes and lockups, insistence to make it required by everything, it's not easier to maintain, leaves services in failure state spontaneously, crashes services on its own, insecure defaults, unable to remove dnsresolver, sometimes systemd and associated programs modify their config on their own, dns 8888/8844 hardcoding, lack of modularity (made worse with dependency hell), Red hat crap, nsa/spy crap, everything poettering makes is crap, root should stay root, pid0 shenanigans, crond misfires, default insecurities, insecurities in general, cve list is enormous, NOTABUG WONTFIX crap, bloat bloat and more bloat, systemd and assorted poetteringware assumes and only supports one real configuration, making any attempt at modularity with linux a thing of the past, ssh insecurity and spyware... I'm sure there's more but I just remember dealing with this
      In conversation about 4 months ago permalink
      ✙ dcc :pedomustdie: :phear_slackware: likes this.
    • Embed this notice
      🌈ᚩ🌈 (bonifartius@noauthority.social)'s status on Saturday, 20-Sep-2025 07:09:16 JST 🌈ᚩ🌈 🌈ᚩ🌈
      in reply to

      @icedquinn
      a) systemd was forced down my throat
      b) systemd gave me enough bullshit issues over the years by reinventing wheels bady
      c) systemd has bad design decisions like auto-restarting things
      d) poettering

      In conversation about 4 months ago permalink
      ✙ dcc :pedomustdie: :phear_slackware: likes this.
    • Embed this notice
      iced depresso (icedquinn@blob.cat)'s status on Saturday, 20-Sep-2025 08:26:50 JST iced depresso iced depresso
      in reply to
      • \\
      @slash i don't feel like wayland came with much rapidity. wayland to me feels more like people really wanted to use it, and were held back by it sucking, and it just eventually didn't.

      systemd to me feels like it came on heavily by IBM fiat
      In conversation about 4 months ago permalink
    • Embed this notice
      \\ (slash@pl.starnix.network)'s status on Saturday, 20-Sep-2025 08:26:51 JST \\ \\
      in reply to

      @icedquinn I don't hate it, I even use it- but I am still wary of how fast it grew into the roles of other projects, enveloped their functions and made interoperability more of a headache. I feel that way about a lot of projects that behave this way- gnome, wayland, etc. I might still use them, but I don't like when there are too many of them it changes the nature of the ecosystem they're in. Sometimes those changes can be gamed by commercial interests as well, through the allocation and diversion of funding to nudge certain initiatives and starve others- and decisions like that can be made without input from or regard to the community too.

      In conversation about 4 months ago permalink
    • Embed this notice
      Blurry Moon (sun@shitposter.world)'s status on Saturday, 20-Sep-2025 08:41:29 JST Blurry Moon Blurry Moon
      in reply to
      @icedquinn I don't use a pid0 manager, I just start libreoffice from linux kernel parameters
      In conversation about 4 months ago permalink
      Johnny Peligro likes this.
    • Embed this notice
      iced depresso (icedquinn@blob.cat)'s status on Saturday, 20-Sep-2025 08:41:29 JST iced depresso iced depresso
      in reply to
      • Blurry Moon
      @sun as god intended
      In conversation about 4 months ago permalink
    • Embed this notice
      iced depresso (icedquinn@blob.cat)'s status on Saturday, 20-Sep-2025 08:41:30 JST iced depresso iced depresso
      in reply to
      • Blurry Moon
      @sun strange reason to hate something
      In conversation about 4 months ago permalink
    • Embed this notice
      iced depresso (icedquinn@blob.cat)'s status on Saturday, 20-Sep-2025 08:50:56 JST iced depresso iced depresso
      in reply to
      • \\
      @slash freedesktop's egoism is certainly a problem. the mask off from "people just don't want to work on that" to clearly expressing an active desire to tank a maintainer was... something.

      not real sad to see x go though. the BSDs haven't been anti-wayland per se either. its more the failure to provide a working event pipeline that has caused issues with porting that one
      In conversation about 4 months ago permalink
    • Embed this notice
      \\ (slash@pl.starnix.network)'s status on Saturday, 20-Sep-2025 08:50:57 JST \\ \\
      in reply to
      @icedquinn I agree with you- the way that wayland is similar is instead in the way that it's being used to starve X from continuing to exist- and that, too, is largely at the mercy of IBM, which is potentially a huge problem in the long term. Earlier this year when the Xlibre stuff started, it turned into a giant drama campaign suspiciously quickly, because it just started out as someone pointing out "my change commits to fix X code are being ignored, so I'll fork" which is totally ordinary behavior in open source. It very quickly snowballed into an attempt to stomp any continuation of X into the ground- and when you look at the plans to naturally drop X support, and how much time and effort is invested into Wayland, I get why.

      I think its hard to ignore that through that funding and effort, there are multiple biases to keep in check. There's economic- you draw a paycheck from this work, you've spent years on it, your career or perceived expertise is kinda staked on it, you don't want to admit if early decisions out of your hands might've gone the wrong direction, or if something needs more work and will cost more money to the boss. Then there's also just the personal bias where you've committed so much time and energy, that it's really unpleasant to admit that something just isn't working still. So there's both an economic bias with the power of a company behind it, supercharged by the emotional bias of anyone who has committed all their time to it and just doesn't want to see that work go to waste.

      That's kind of what I'm talking about- strong personalities deciding to do things another way and create solutions they haven't seen can be a great thing in open source, but at some point without care they can become a gear in an economic machine with attached interests that don't actually benefit the project it started as. When competition is healthy, and in particular when scope is narrowed and designed for interoperability with other projects, that is less likely to occur, so my bias is against projects seeking that level of influence/irreplaceability so quickly, or ever.
      In conversation about 4 months ago permalink
    • Embed this notice
      Taylan (Now 18% More Deranged) (taylan@fedi.feministwiki.org)'s status on Saturday, 20-Sep-2025 09:12:32 JST Taylan (Now 18% More Deranged) Taylan (Now 18% More Deranged)
      in reply to
      @icedquinn

      1. Binary logs.
      2. Binary logs.
      3. Binary logs.
      4. Bloating the system's attack surfaces like we saw with the weird xz backdoor.
      In conversation about 4 months ago permalink
      iced depresso likes this.
    • Embed this notice
      🌈ᚩ🌈 (bonifartius@noauthority.social)'s status on Tuesday, 23-Sep-2025 18:43:16 JST 🌈ᚩ🌈 🌈ᚩ🌈
      in reply to

      @icedquinn also: iirc the xz ssh exploit was enabled by systemd as well, and failure modes like descibed in https://mastodon.bsd.cafe/@stefano/115252432137723192 are due to the windows way of thinking by systemd

      In conversation about 4 months ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Stefano Marinelli (@stefano@bsd.cafe)
        from Stefano Marinelli
        Spent my morning figuring out why Nginx was dead on a server with many days of uptime. No reboot, no kernel panic. Just... down. Ubuntu 24.04. The cause? An automatic unattended-upgrade of libc6. This prompted systemd to work its magic, wisely deciding to restart every running service to apply the patch. Fine. The problem is, in the exact same minute, the systemd timer for certbot decided it was time to renew certificates. The result: - systemd stops Nginx. - Port 80 becomes free. - certbot, in standalone mode, immediately grabs it for validation. - systemd tries to restart Nginx, which fails with "Address already in use". The web server was knocked offline by its own certificate renewal script. I swear, this is the kind of cascading failure that has never happened to me in years of running *BSD. With a classic cron job, certbot would have failed, logged an error, and tried again the next day. The web server would have remained untouched. systemd was doing its job, but something failed because of the interactions. Sometimes, too much automation and too many interconnected parts just create more spectacular ways for things to break. #SysAdmin #Linux #SystemD #Rant #KISS
      ✙ dcc :pedomustdie: :phear_slackware: likes this.
    • Embed this notice
      iced depresso (icedquinn@blob.cat)'s status on Tuesday, 23-Sep-2025 21:52:06 JST iced depresso iced depresso
      in reply to
      • 🌈ᚩ🌈
      @bonifartius i meant to make a fishbone of that survey yesterday but freeplane wouldn't start
      In conversation about 4 months ago permalink
    • Embed this notice
      Johnny Peligro (mischievoustomato@tsundere.love)'s status on Tuesday, 23-Sep-2025 22:04:22 JST Johnny Peligro Johnny Peligro
      in reply to
      @icedquinn i never hated it, none of the reasons listed ever or even here convinced me
      In conversation about 4 months ago permalink
    • Embed this notice
      iced depresso (icedquinn@blob.cat)'s status on Tuesday, 23-Sep-2025 22:29:26 JST iced depresso iced depresso
      in reply to
      • 🌈ᚩ🌈
      @bonifartius its just a silly way to draw an outline really

      meant to take a list of issues and categorize them in to problem domains and problems/causes.
      In conversation about 4 months ago permalink
    • Embed this notice
      🌈ᚩ🌈 (bonifartius@noauthority.social)'s status on Tuesday, 23-Sep-2025 22:29:27 JST 🌈ᚩ🌈 🌈ᚩ🌈
      in reply to

      @icedquinn you always have another diagram type i have to look up, nice :)

      In conversation about 4 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.