Creating a modified iso

Forum Forums New users New Users and General Questions Creating a modified iso

  • This topic has 9 replies, 7 voices, and was last updated Dec 17-5:25 pm by Anonymous.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #47486
    Member
    naaan

      Hello . I am trying to create a modified iso on antix.
      I created a live-usb . Booted from it. Removed packages > use iso snapshot > but the created ISO was much bigger than the original! Starting with 750mb base iso I ended up with a 1gb modified ISO.
      Any help please ? Could this be due to different compression technique ? Intially I had neglected to remove certain cache files. But removing those didn’t appear to affect the iso size.

      Thanks!

      #47488
      Moderator
      christophe
        Helpful
        Up
        0
        ::

        Yes. Probably compression scheme is to blame. I ran into this, too. Read all options carefully. šŸ™‚
        The compression defaults to the largest size.

        • This reply was modified 2 years, 4 months ago by christophe.

        confirmed antiX frugaler, since 2019

        #47491
        Member
        Xecure
          Helpful
          Up
          0
          ::

          Hi.

          Any help please ? Could this be due to different compression technique ?

          On the second screen, there is an option that says “ISO compression scheme”. By default it uses lz4, but if you want a greater compressing please use xz compression.

          Edit: ninja’d by christophe

          • This reply was modified 2 years, 4 months ago by Xecure. Reason: I was too slow!

          antiX Live system enthusiast.
          General Live Boot Parameters for antiX.

          #47511
          Anonymous
            Helpful
            Up
            0
            ::

            FYI: a search of the forum (oldforum archive?) will find benchmarking tests in which we (multiple testers, various hardware) compared the cost/benefit from each of the various compression schemes.

            xz… is so CPU-intensive that it begs use of the option (tickbox) “do NOT use all cores, in parallel”. Otherwise, CPU may overheat and/or throttle the system. During the testing I witnessed, first-hand, a CoreIIDuo system poweroff (as a self-preservative response) in reaction to the extended load imposed by an “all cores, xz compression” snapshot operation.

            #47527
            Moderator
            BobC
              Helpful
              Up
              0
              ::

              I always plug in the cooler and hover the cpu monitor when doing this

              #47539
              Moderator
              Brian Masinick
                Helpful
                Up
                0
                ::

                FYI: a search of the forum (oldforum archive?) will find benchmarking tests in which we (multiple testers, various hardware) compared the cost/benefit from each of the various compression schemes.

                xz… is so CPU-intensive that it begs use of the option (tickbox) ā€œdo NOT use all cores, in parallelā€. Otherwise, CPU may overheat and/or throttle the system. During the testing I witnessed, first-hand, a CoreIIDuo system poweroff (as a self-preservative response) in reaction to the extended load imposed by an ā€œall cores, xz compressionā€ snapshot operation.

                Wow! I believe you, that high compression can consume considerable CPU.

                I often use xz compression to copy packages or a few directories but I never specify the use of all CPUs, but I have not explicitly restricted it either.

                Recently when using our images I’ve been using lz4 compression.

                Im any case thanks for highlighting this, even if it has been mentioned many times. I’ll try to be careful and if I ever notice this you have forewarned us again; thank you!

                • This reply was modified 2 years, 4 months ago by Brian Masinick.

                --
                Brian Masinick

                #47583
                Member
                naaan
                  Helpful
                  Up
                  0
                  ::

                  It was indeed the compression scheme that caused the large size.
                  Have another issue. Remastered iso won’t boot. Kernel Panic
                  First I thought I was removing too many packages. But even without removing a single package. I get an kernel panic, in a VM as well.

                  Screenshot: https://i.imgur.com/PGWYXBL.png
                  Also iso-snapshot app complains about a missing file which I fix by – ‘sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list’

                  • This reply was modified 2 years, 4 months ago by naaan.
                  #47588
                  Member
                  Xecure
                    Helpful
                    Up
                    0
                    ::

                    Also iso-snapshot app complains about a missing file which I fix by – ā€˜sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list’

                    Your issue is there. There are things that need to be excluded from the snapshot if you want the final iso to boot on other systems. If that file is missing, you need to recover it. reinstall iso-snapshot-antix
                    sudo apt update && sudo apt install --reinstall iso-snapshot-antix

                    antiX Live system enthusiast.
                    General Live Boot Parameters for antiX.

                    #47590
                    Forum Admin
                    anticapitalista
                      Helpful
                      Up
                      0
                      ::

                      https://antixlinux.com/antix-19-3-manolis-glezos-bug-fix-upgrade-isos-available/

                      See known issues

                      Philosophers have interpreted the world in many ways; the point is to change it.

                      antiX with runit - leaner and meaner.

                      #47600
                      Anonymous
                        Helpful
                        Up
                        0
                        ::

                        sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list

                        ouch.
                        OMG, no that wouldn’t lead to a happy ending…

                        There are things that need to be excluded from the snapshot if you want the final iso to boot on other systems.

                        and, in the absence of a suitable exclusions list, the operation would never reach completion, period. Instead, endless recursion would result, attempting to read (and create squashed copies of) “virtual” files from the vfs directories, e.g. /sys/ and /proc/ …ultimately leading to “kernel panic” once the recursive process has fully exhaused all available (memory, swap) resources.

                      Viewing 10 posts - 1 through 10 (of 10 total)
                      • You must be logged in to reply to this topic.