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

  • Public

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

Embed Notice

HTML Code

Corresponding Notice

  1. Embed this notice
    vv221 (vv221@fediverse.dotslashplay.it)'s status on Tuesday, 18-Jun-2024 21:57:47 JSTvv221vv221
    in reply to
    • Nekko
    It’s because I like systemd that I want to point out what I see as a bad decision, if I disliked it in the first place I would not have bothered with a bug report ;)
    Scratch that, the despicable behaviour of the Debian maintainer for systemd convinced me that I am no longer going to rely on this system, no matter how much it helped me with my systems administration in the last years.

    I already started a plan to move away from it, cf. https://fediverse.dotslashplay.it/snac/vv221/p/1718493621.850738

    Sorry for the systemd upstream team, you are not the problem here. But I can’t bring myself to rely on a software maintained by someone reacting the way the current Debian maintainer does when faced with an honest bug report.

    CC: @NekkoDroid@mastodon.gamedev.place
    In conversationabout 8 months ago from fediverse.dotslashplay.itpermalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: fediverse.dotslashplay.it
      vv221 (@vv221@fediverse.dotslashplay.it)
      Following the decision of the Debian maintainer for systemd that it is OK for an init system to get the ability to randomly nuke /home and /srv, I started a migration away from systemd on my server. The first step is migrating my systemd-nspawn containers to LXC containers, and it is surprisingly much easier than I expected! Of course it helps that I can keep using the network bridges I had set up for the systemd-nspawn containers (I did not want to rely on systemd-networked at the time, and I am grateful today
  • 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.