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
    Serge Matveenko ♻️☮️Ⓐ (lig@fosstodon.org)'s status on Wednesday, 14-Sep-2022 03:19:08 JST Serge Matveenko ♻️☮️Ⓐ Serge Matveenko ♻️☮️Ⓐ

    It's in Gentoo mostly because of Gnome 3.

    Further reading https://nosystemd.org/

    In conversation Wednesday, 14-Sep-2022 03:19:08 JST from fosstodon.org permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: nosystemd.org
      No systemd
    • PublicLewdness likes this.
    • Embed this notice
      Serge Matveenko ♻️☮️Ⓐ (lig@fosstodon.org)'s status on Wednesday, 14-Sep-2022 03:19:02 JST Serge Matveenko ♻️☮️Ⓐ Serge Matveenko ♻️☮️Ⓐ
      in reply to
      • Hugo 雨果

      @whynothugo Most of Systemd alternatives doesn't lack any its feature apart from the bloat around it.
      OpenRC explicitly positions itself as a dependency-based.
      I highly recommend learning about Systemd alternatives before stating Systemd's superiority.

      In conversation Wednesday, 14-Sep-2022 03:19:02 JST permalink
      PublicLewdness likes this.
    • Embed this notice
      Hugo 雨果 (whynothugo@fosstodon.org)'s status on Wednesday, 14-Sep-2022 03:19:07 JST Hugo 雨果 Hugo 雨果
      in reply to

      @lig Do any of these start dependencies when starting a service? What about restarting services that exit non-zero?

      What about socket activated services?

      Systemd has issues, but it's naive to ignore it as "prior art" when writing an init system.

      In conversation Wednesday, 14-Sep-2022 03:19:07 JST permalink
    • Embed this notice
      Iron Bug (iron_bug@friendica.ironbug.org)'s status on Wednesday, 14-Sep-2022 20:15:19 JST Iron Bug Iron Bug
      in reply to
      • Chucho #TeamStallman :artix:
      • Hugo 雨果
      @jrballesteros05 @lig @whynothugo kernel is the OS. it does all the work with hardware and system resources. and useless-d is just plain coprorative bullshit that is bloated and buggy and is the single point of failure, in addition.
      In conversation Wednesday, 14-Sep-2022 20:15:19 JST permalink
      PublicLewdness likes this.
    • Embed this notice
      Chucho #TeamStallman :artix: (jrballesteros05@fosstodon.org)'s status on Wednesday, 14-Sep-2022 20:15:20 JST Chucho #TeamStallman :artix: Chucho #TeamStallman :artix:
      in reply to
      • Hugo 雨果

      @lig @whynothugo I had a big problem with systemd-resolved and I had to disable in order to make my solution works, with non-systemd distros and even systemd distros without systemd-resolved I don't have that problem. They came with many solutions nobody ask, adding bloat, more monolithic stuff (as if we don't have enough with Linux kernel), hard dependencies and more fragmentation to the ecosystem. Fuck systemd.

      In conversation Wednesday, 14-Sep-2022 20:15:20 JST permalink
      PublicLewdness likes this.
    • Embed this notice
      Serge Matveenko ♻️☮️Ⓐ (lig@fosstodon.org)'s status on Wednesday, 14-Sep-2022 20:21:35 JST Serge Matveenko ♻️☮️Ⓐ Serge Matveenko ♻️☮️Ⓐ
      in reply to
      • Hugo 雨果

      @whynothugo Because OpenRC ot any other init system shouldn't handle the logging. That's not their dumb business.

      In conversation Wednesday, 14-Sep-2022 20:21:35 JST permalink
      PublicLewdness likes this.
    • Embed this notice
      Hugo 雨果 (whynothugo@fosstodon.org)'s status on Wednesday, 14-Sep-2022 20:21:37 JST Hugo 雨果 Hugo 雨果
      in reply to

      @lig I wouldn't consider "bloat" a feature TBH. I do agree that anyone staying systemd is superior should learn about alternatives (the same is true in any context TBH).

      I don't see OpenRC handling any logging. Where does stdout/stderr for services end up?

      In conversation Wednesday, 14-Sep-2022 20:21:37 JST permalink
    • Embed this notice
      Serge Matveenko ♻️☮️Ⓐ (lig@fosstodon.org)'s status on Wednesday, 14-Sep-2022 21:39:14 JST Serge Matveenko ♻️☮️Ⓐ Serge Matveenko ♻️☮️Ⓐ
      in reply to
      • Hugo 雨果

      @whynothugo It is a good thing. And with non-systemd init one can use any logging capability. Moreover, it shouldn't be a duty of init to provide such a capability. Systemd has both in a single codebase. It isn't a good thing IMO.
      https://manpages.debian.org/testing/openrc/openrc-run.8.en.html
      See `output_log`, `error_log`, `output_logger`, `error_logger`.

      In conversation Wednesday, 14-Sep-2022 21:39:14 JST permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        openrc-run(8) — openrc — Debian testing — Debian Manpages
      PublicLewdness likes this.
    • Embed this notice
      Hugo 雨果 (whynothugo@fosstodon.org)'s status on Wednesday, 14-Sep-2022 21:39:15 JST Hugo 雨果 Hugo 雨果
      in reply to

      @lig I don't see any mention of how to do that in the docs in with a quick search, do you have a reference?

      Why would being forced to use a specific tool be a good thing? Isn't it best to be flexible for this?

      In conversation Wednesday, 14-Sep-2022 21:39:15 JST permalink
    • Embed this notice
      Serge Matveenko ♻️☮️Ⓐ (lig@fosstodon.org)'s status on Wednesday, 14-Sep-2022 21:39:16 JST Serge Matveenko ♻️☮️Ⓐ Serge Matveenko ♻️☮️Ⓐ
      in reply to
      • Hugo 雨果

      @whynothugo you still can define it in openrc script but no one forces you to use a specific tool or to use the same logging solution for all your services.

      In conversation Wednesday, 14-Sep-2022 21:39:16 JST permalink
    • Embed this notice
      Hugo 雨果 (whynothugo@fosstodon.org)'s status on Wednesday, 14-Sep-2022 21:39:17 JST Hugo 雨果 Hugo 雨果
      in reply to

      @lig This is more of a Unix thing though; it's the parent process who has to define where to pipe stdout and stderr. The init system is, inevitably, the one spawning your services.

      In conversation Wednesday, 14-Sep-2022 21:39:17 JST 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.