Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Darkly)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Uncategorized
  3. Linux From Scratch Abandoning SysVinit Support

Linux From Scratch Abandoning SysVinit Support

Scheduled Pinned Locked Moved Uncategorized
9 Posts 4 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • PhoronixP This user is from outside of this forum
    PhoronixP This user is from outside of this forum
    Phoronix
    wrote last edited by
    #1

    Linux From Scratch Abandoning SysVinit Support

    Linux From Scratch was one of the holdouts continuing optional SysVinit init system support through 2026, but that's now ending. Linux From Scratch "LFS" and Beyond Linux From Scratch "BLFS" are ending their System V Init support moving forward...
    https://www.phoronix.com/news/LFS-Dropping-SysVinit

    Dr. Quadragon ❌D 1 Reply Last reply
    0
    • PhoronixP Phoronix

      Linux From Scratch Abandoning SysVinit Support

      Linux From Scratch was one of the holdouts continuing optional SysVinit init system support through 2026, but that's now ending. Linux From Scratch "LFS" and Beyond Linux From Scratch "BLFS" are ending their System V Init support moving forward...
      https://www.phoronix.com/news/LFS-Dropping-SysVinit

      Dr. Quadragon ❌D This user is from outside of this forum
      Dr. Quadragon ❌D This user is from outside of this forum
      Dr. Quadragon ❌
      wrote last edited by
      #2

      @phoronix whoa, this actually sucks.

      uwu1baA 1 Reply Last reply
      0
      • Dr. Quadragon ❌D Dr. Quadragon ❌

        @phoronix whoa, this actually sucks.

        uwu1baA This user is from outside of this forum
        uwu1baA This user is from outside of this forum
        uwu1ba
        wrote last edited by
        #3
        @drq @phoronix my (horrible) take is that there is no reason to support sysvinit because half of it is a legacy that doesn't make sense anymore and half of it is manual labor.

        If LFS is trying to teach you something, it's better to teach something that exists in real life. And that would be systemd almost in all cases and where it's not it's openrc.
        Dr. Quadragon ❌D 1 Reply Last reply
        0
        • uwu1baA uwu1ba
          @drq @phoronix my (horrible) take is that there is no reason to support sysvinit because half of it is a legacy that doesn't make sense anymore and half of it is manual labor.

          If LFS is trying to teach you something, it's better to teach something that exists in real life. And that would be systemd almost in all cases and where it's not it's openrc.
          Dr. Quadragon ❌D This user is from outside of this forum
          Dr. Quadragon ❌D This user is from outside of this forum
          Dr. Quadragon ❌
          wrote last edited by
          #4

          @a1ba That's fair, but still, I'd rather have LFS support it. If anything, it's a piece of history.

          @phoronix

          uwu1baA 1 Reply Last reply
          0
          • Dr. Quadragon ❌D Dr. Quadragon ❌

            @a1ba That's fair, but still, I'd rather have LFS support it. If anything, it's a piece of history.

            @phoronix

            uwu1baA This user is from outside of this forum
            uwu1baA This user is from outside of this forum
            uwu1ba
            wrote last edited by
            #5
            @drq @phoronix on that note, maybe we need system software museums.

            Documenting and preserving the engineering solutions we had back then, so we will never repeat the mistake again.

            Like sysvinit runlevels. Or cron syntax.
            :5492_EzPepe: XaetaCore :linux:X 2 Replies Last reply
            0
            • uwu1baA uwu1ba
              @drq @phoronix on that note, maybe we need system software museums.

              Documenting and preserving the engineering solutions we had back then, so we will never repeat the mistake again.

              Like sysvinit runlevels. Or cron syntax.
              :5492_EzPepe: XaetaCore :linux:X This user is from outside of this forum
              :5492_EzPepe: XaetaCore :linux:X This user is from outside of this forum
              :5492_EzPepe: XaetaCore :linux:
              wrote last edited by
              #6
              @a1ba@suya.place @drq@mastodon.ml @phoronix@masto.ai ​​ Chron is still relevant
              1 Reply Last reply
              1
              0
              • uwu1baA uwu1ba
                @drq @phoronix on that note, maybe we need system software museums.

                Documenting and preserving the engineering solutions we had back then, so we will never repeat the mistake again.

                Like sysvinit runlevels. Or cron syntax.
                :5492_EzPepe: XaetaCore :linux:X This user is from outside of this forum
                :5492_EzPepe: XaetaCore :linux:X This user is from outside of this forum
                :5492_EzPepe: XaetaCore :linux:
                wrote last edited by
                #7
                @a1ba@suya.place @drq@mastodon.ml @phoronix@masto.ai ​​ Cron is still relevant
                uwu1baA 1 Reply Last reply
                1
                0
                • R ActivityRelay shared this topic
                • :5492_EzPepe: XaetaCore :linux:X :5492_EzPepe: XaetaCore :linux:
                  @a1ba@suya.place @drq@mastodon.ml @phoronix@masto.ai ​​ Cron is still relevant
                  uwu1baA This user is from outside of this forum
                  uwu1baA This user is from outside of this forum
                  uwu1ba
                  wrote last edited by
                  #8
                  @xaetacore @phoronix @drq these days I use systemd timers.
                  :5492_EzPepe: XaetaCore :linux:X 1 Reply Last reply
                  0
                  • uwu1baA uwu1ba
                    @xaetacore @phoronix @drq these days I use systemd timers.
                    :5492_EzPepe: XaetaCore :linux:X This user is from outside of this forum
                    :5492_EzPepe: XaetaCore :linux:X This user is from outside of this forum
                    :5492_EzPepe: XaetaCore :linux:
                    wrote last edited by
                    #9
                    @a1ba@suya.place @phoronix@masto.ai @drq@mastodon.ml Those are fine but i still find crontab -e easier and quicker
                    1 Reply Last reply
                    1
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    Powered by NodeBB Contributors
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups