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.
-
AuthorPosts
-
December 15, 2020 at 12:57 pm #47486Member
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!
December 15, 2020 at 1:24 pm #47488Moderator
christophe
::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.
Attachments:
confirmed antiX frugaler, since 2019
December 15, 2020 at 1:26 pm #47491Member
Xecure
::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.December 15, 2020 at 8:54 pm #47511Anonymous
::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.
December 16, 2020 at 5:54 am #47527ModeratorBobC
December 16, 2020 at 2:47 pm #47539Moderator
Brian Masinick
::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 MasinickDecember 17, 2020 at 9:45 am #47583Membernaaan
::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.
December 17, 2020 at 9:54 am #47588Member
Xecure
::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-antixantiX Live system enthusiast.
General Live Boot Parameters for antiX.December 17, 2020 at 11:53 am #47590Forum Admin
anticapitalista
::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.
December 17, 2020 at 5:25 pm #47600Anonymous
::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.
-
AuthorPosts
- You must be logged in to reply to this topic.