1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] A new init system; Simple, powerful, fast, and user-frien

    From Pramod V U@21:1/5 to All on Tue May 6 06:00:01 2025
    `66` is a new init system using `s6` under then hood. I've already written a mail or two long ago about it on this mailing list.
    I have already packaged it, the core boot services, and many other service definition frontend files, in my overlay.

    It supports a simple declarative INI format for declaring services, supports hard and soft dependencies, efficient and safe parallelism.

    Oh! Yes, it handles the logs of the daemons via stdout/stderr, via dedicated loggers. Logs of different daemons are different...

    Everything possible is pre-computed and pre-resolved. This makes 66 ***really*** fast!

    But, it *never* runs in the system, except for the few milliseconds you need it.
    It uses s6 under the hood, something powerful yet so lightweight that you don't understand it's even running; unless you explicitly check for it.

    Kindly request me if you want any detailed info on any component, or just the whole thing.

    Those who want to try out a good init system with advanced features but simplicity and speed, this is exactly for you.
    Those who are just fine with systemd or openrc, using it in a production system, this isn't for you *yet*...

    All packages are currently in a separate overlay...
    The repository:
    https://github.com/pramodvu1502/66-svmgr-gentoo-overlay

    The Gentoo Wiki Page (incomplete as of now): https://wiki.gentoo.org/wiki/66-init

    Kind regards,
    Pramod V U

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Tue May 6 15:46:02 2025
    On Tuesday, 6 May 2025 04:57:46 British Summer Time Pramod V U wrote:
    `66` is a new init system using `s6` under then hood. I've already written a mail or two long ago about it on this mailing list. I have already packaged it, the core boot services, and many other service definition frontend
    files, in my overlay.

    It supports a simple declarative INI format for declaring services, supports hard and soft dependencies, efficient and safe parallelism.

    Oh! Yes, it handles the logs of the daemons via stdout/stderr, via dedicated loggers. Logs of different daemons are different...

    Everything possible is pre-computed and pre-resolved. This makes 66 ***really*** fast!

    But, it *never* runs in the system, except for the few milliseconds you need it. It uses s6 under the hood, something powerful yet so lightweight that
    you don't understand it's even running; unless you explicitly check for it.

    Kindly request me if you want any detailed info on any component, or just
    the whole thing.

    Those who want to try out a good init system with advanced features but simplicity and speed, this is exactly for you. Those who are just fine with systemd or openrc, using it in a production system, this isn't for you *yet*...

    All packages are currently in a separate overlay...
    The repository:
    https://github.com/pramodvu1502/66-svmgr-gentoo-overlay

    The Gentoo Wiki Page (incomplete as of now): https://wiki.gentoo.org/wiki/66-init

    Kind regards,
    Pramod V U

    Just to say thank you for working on this and for updating us on progress. Hopefully one day it will be a good alternative to OpenRC and migration will not be too involved.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmgaIKoACgkQseqq9sKV Zxk2UBAAsWle54AqCDUyk42yT7WCx1c+79fRyJ2zuS0M4xGbjeZO43TeosjTJfJn BDcrdY8LwLZ+ALjvYg2QuKAHSs5PmGIp8Rvnfas91/2ho5gp4zGMEfo/KQ8snOsE Jmvxd3jRRdqbqYNANUIEv/7hFzl7Wz2jhSrVRPl6GkAf5zOeIda1Phu/2N9ySwSK 1w6iqXzaaashCEGNlMATMQIL6XrubKl/3ioOqhQ7k/PLQUI08dw/jWzI6fnth3Jv pG49IPZ8jDWGq2Nvk9WN5f/vBHeGCzDe9wHM9a37bHJ7eyEfBUDgfPg9OHrjhJIg qy1t+5ixthX4czEcDtf00w4sI28I9aXkq8gBwqMpeHQR3NOaJXCa/Oa6iISz9q5r f+Q0vdzBlnXUsHu/BP7IuvxClCUGpkO5+pxDReo03LYO0uMIw/g2xt8CRl1HQqz5 qb2pfBG5di2knaH6lG1AfRlQez85cpp42A6lIxYWCxWoMnxdrGwvehOYrO4tO0yv +A5pm1DPwcMfT0oPx8++gh2CAf/VtE/vI6rrEHvjVWFXQtjwPc71JgYqtBfBp6Du /Q37Za7cFx/FGlWPprqAbdtTaBhDePcJf4A+v5cudWuQISmkD0zGf8cnFG9qjw53 cadXML/q4iKB5b/nSQUQ/QwxA2NzkGJZBjjrLsEZh8FfOjDzIXA=
    =xTfQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Pramod V U@21:1/5 to Michael on Tue May 6 18:00:01 2025
    On Tuesday, May 6th, 2025 at 8:17 PM, Michael <[email protected]> wrote:

    Just to say thank you for working on this and for updating us on progress.

    Many more frontends and packages are being added at a rapid pace, to the repo. Kindly voice your opinion and requirement on what is priority and what is not.

    To prepare this new init system more effectively and faster, I will have to know what the potential users, and criticizers, have to say.

    Testers' help will be greatly appreciated. Just testing, I'll prepare it. Unfortunately I'm too busy to keep rebooting to test it.

    Hopefully one day it will be a good alternative to OpenRC and migration will not be too involved.

    Currently, `sys-apps/66-boot` is a package which contains the core boot services, upto udevd and the (age)ttys, including ZFS and crypttab (parsed by an internal awk script).

    This package pulls the 66 suite.

    And a package `66-frontend/66-service-meta` pulls other packages in the same category, based on useflags. (Yes, a new category)
    The other packages contain 66 service files.
    More are being added at a rapid pace.

    Unfortunately, 66 doesn't support the "firstboot" concept, unlike systemd and openrc.
    Eg. The `/etc/machine-id` file, `/var/lib/dbus/machine-id` symlink, `/etc/hostname` and many more things need to be done manually (or atleast by a previously used init like openrc).

    I'd like to, atleast for gentoo where I maintain it, keep the "firstboot" separate from the general everyday system.
    I am working on a handwritten script to do so, and will very soon put it into a repository in <https://git.obarun.org>. And an ebuild in my overlay.

    An irrelevant note: systemd systems can't run the poweroff binary is a random openssl library is missing. It is a symlink to a multicall-binary systemctl, which needs libsystemd which in turn needs the openssl library; A hard requirement for some reason.
    AND if you force it off, systemd fails on next boot due to same issue.

    But please remember, I am too busy, I can't frequently boot to it and test it. Help will be greatly appreciated. Just testing.

    Regards,
    Pramod

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)