antiX-26-rc1 available

Forum › Forums › News › Announcements › antiX-26-rc1 available

  • This topic has 658 replies, 44 voices, and was last updated Apr 3-3:29 pm by Brian Masinick.
Viewing 15 posts - 481 through 495 (of 659 total)
  • Author
    Posts
  • #197909
    ProwlerGr
    Member

      Thanks @masinick
      I think I can see the problem with Dinit ( @anticapitalista modules.sh script needs to be aligned with runit/s6-rc & potentially a new scripted service for kmod-static-nodes is required)

      For 66 I believe you just need to enable the modules for the boot@system module
      sudo 66 configure -e nano boot@system
      Change relevant line to:
      MODULE_KERNEL=!yes
      Then activate the change with command
      sudo 66 reconfigure boot@system

      #197910
      Brian Masinick
      Moderator

        Thank you @ProwlerGr!

        I’ll take care of it tomorrow.
        Hopefully the permanent fixes will make the release too. [Thumbs up 👍]

        --
        Brian Masinick
        Alternate "Search B":
        This search page

        #197911
        ProwlerGr
        Member

          Maybe test the attached on Dinit & report back if it works well for you.
          We will need to wait for @anticapitalista to get back before it is properly packaged for antiX

          #197914
          andfree
          Member

            Maybe test the attached on Dinit & report back if it works well for you.

            Thank you. I would like to test it on my regular installed system, but I purged dinit yesterday, after an “accident”. I thought that dinit had caused a problem to the whole system and that removing it could have solved it. It didn’t. I fixed my problem another way. Is there a simple way to reinstall dinit on the existing multi-init system? I tried
            sudo apt install dinit
            but it would reinstall only the specific package, not all the dinit related packages that have been removed.

            I also tried to test your attachment on my frugal (static) system with kernel 6.6 (using the parameter init=dinit), but the “fuse” line is already there in /etc/modules file and although I delete it, when I reboot it’s still there. I have no explanation for this.

            We had better luck on my frugal (static) system with kernel 5.10. I booted with init=dinit parameter and there was not a “fuse” line in /etc/modules file. It was a good start. Then I tried to execute the Ungoogled Chromium Appimage and got this message:

            fuse: device not found, try 'modprobe fuse' first
            
            Cannot mount AppImage, please check your FUSE setup.
            (...)

            After that, I installed your .deb file:
            sudo apt install /<pathway-to>/dinit-service-boot-module-antix_0.1.8experimental1_all.deb

            When the installation finished, I rebooted and now the Appimage is executed properly. Your fix worked.

            #197915
            ProwlerGr
            Member

              Is there a simple way to reinstall dinit on the existing multi-init system?

              Running the following should give you a functional graphic system
              sudo apt install dinit-init-antix dinit-service-boot-module-antix dinit-dialogbox-manager dinit-service-slimski dinit-service-connmand dinit-service-turnstiled

              Otherwise just boot an unaltered antiX-26-rc1 iso, take list of all the installed dinit related packages & install them all

              #197917
              andfree
              Member

                Running the following should give you a functional graphic system
                sudo apt install dinit-init-antix dinit-service-boot-module-antix dinit-dialogbox-manager dinit-service-slimski dinit-service-connmand dinit-service-turnstiled

                It has really done it. Thank you.
                Now I have the pleasure of being able to confirm that your fix for dinit has already worked on my regular installed system as well.

                • This reply was modified 6 months, 3 weeks ago by andfree.
                #197921
                andfree
                Member

                  For 66 I believe you just need to enable the modules for the boot@system module
                  sudo 66 configure -e nano boot@system
                  Change relevant line to:
                  MODULE_KERNEL=!yes
                  Then activate the change with command
                  sudo 66 reconfigure boot@system

                  It worked. Thank you.

                  I noticed an issue that I don’t know if it is already known and I have no time to search about it, so I just mention it.
                  I can’t “pass” directly from dinit to 66; rebooting fails. However, I can reboot without problem from dinit to runit and then from runit to 66.

                  #197926
                  Brian Masinick
                  Moderator

                    Maybe test the attached on Dinit & report back if it works well for you.
                    We will need to wait for @anticapitalista to get back before it is properly packaged for antiX

                    Tried this one first: it works!

                    I’ll go on to the 66 fix next; thanks!

                    --
                    Brian Masinick
                    Alternate "Search B":
                    This search page

                    #197929
                    Brian Masinick
                    Moderator

                      Thanks @masinick
                      I think I can see the problem with Dinit ( @anticapitalista modules.sh script needs to be aligned with runit/s6-rc & potentially a new scripted service for kmod-static-nodes is required)

                      For 66 I believe you just need to enable the modules for the boot@system module
                      sudo 66 configure -e nano boot@system
                      Change relevant line to:
                      MODULE_KERNEL=!yes
                      Then activate the change with command
                      sudo 66 reconfigure boot@system

                      I got this working too, and now that I know where this is, I adjusted a few other parameters to suit my system and interests too.
                      One parameter that I can’t seem to get right is the correct timezone; default lists UTC. I wanted US Eastern or America/New_York, but what I put in didn’t have any effect, so the syntax is clearly wrong for what I entered.

                      Looking in the database, /usr/share/zoneinfo/America/New_York is the complete filename.
                      For America/New_York, what should be the correct entry? I believe I tried America/New_York.

                      --
                      Brian Masinick
                      Alternate "Search B":
                      This search page

                      #197932
                      ProwlerGr
                      Member

                        For America/New_York, what should be the correct entry? I believe I tried America/New_York.

                        I believe the 2 entries you need to change are:

                        TZ=America/New_York
                        HARDWARECLOCK=localtime
                        #197933
                        032_hsn
                        Member

                          @ProwlerGr
                          DINIT works fine for me. After the last updates, however, when I boot the snapshot, I have to switch to DINIT from RUNIT. DINIT does not appear automaticaly (… @andfree).

                          #197935
                          Brian Masinick
                          Moderator

                            For America/New_York, what should be the correct entry? I believe I tried America/New_York.

                            I believe the 2 entries you need to change are:

                            TZ=America/New_York
                            HARDWARECLOCK=localtime

                            Thanks! I thought that I had both of them set; I’ll double check, then make sure to perform the entire sequence; otherwise, everything is working well!

                            --
                            Brian Masinick
                            Alternate "Search B":
                            This search page

                            #197937
                            Brian Masinick
                            Moderator

                              For America/New_York, what should be the correct entry? I believe I tried America/New_York.

                              I believe the 2 entries you need to change are:

                              TZ=America/New_York
                              HARDWARECLOCK=localtime

                              Thanks! I thought that I had both of them set; I’ll double check, then make sure to perform the entire sequence; otherwise, everything is working well!

                              Hmm, that IS what I have set; I’ll try it one more time; I made sure to do
                              sudo 66 reconfigure boot@system

                              --
                              Brian Masinick
                              Alternate "Search B":
                              This search page

                              #197938
                              Brian Masinick
                              Moderator

                                Hmm, that IS what I have set; I’ll try it one more time; I made sure to do
                                sudo 66 reconfigure boot@system

                                I did it again: MAYBE, to quote a line from the old movie, “My Cousin Vinnie” – for me, SIX times is a charm – it worked, and I didn’t change a single value; all I did was run the reconfigure step AGAIN; this time it worked!

                                With this resolution, I have all five init alternatives booting and running well, and the initial time is correct for my system too.

                                Wed Mar  4 09:34:31 AM EST 2026
                                ps ax | head -2
                                  PID TTY      STAT   TIME COMMAND
                                    1 ?        Ss     0:00 /usr/bin/s6-svscan -t 0 -L 256 /run/66/scandir/0

                                --
                                Brian Masinick
                                Alternate "Search B":
                                This search page

                                #197939
                                Brian Masinick
                                Moderator
                                  Wed Mar  4 09:37:25 AM EST 2026
                                  Info:
                                    Memory: total: 16 GiB note: est. available: 14.4 GiB
                                      used: 1.67 GiB (11.6%)
                                    Processes: 333 Power: uptime: 1m states: freeze,mem,disk
                                      suspend: s2idle wakeups: 0 hibernate: platform Init: Dinit
                                      v: 0.20.0 default: 5
                                    Packages: pm: dpkg pkgs: 2043 Compilers: gcc: 14.2.0
                                      Shell: Bash v: 5.2.37 running-in: roxterm pinxi: 3.3.40-1

                                  --
                                  Brian Masinick
                                  Alternate "Search B":
                                  This search page

                                Viewing 15 posts - 481 through 495 (of 659 total)
                                • You must be logged in to reply to this topic.