SparkyLinux Forums

Development => Remastering => Topic started by: way12go on August 12, 2014, 03:15:36 pm

Title: SparkyLinux Custom ISO Builder
Post by: way12go on August 12, 2014, 03:15:36 pm
I wish there is a tutorial for "SparkyLinux Custom ISO Builder".
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on August 12, 2014, 04:21:10 pm
It will be soon, it's on my working list.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on August 14, 2014, 02:33:29 pm
The part 1 is ready now: http://sparkylinux.org/custom-iso-builder-howto-part-1/
Title: Re: SparkyLinux Custom ISO Builder
Post by: configX on October 26, 2014, 02:27:23 pm
Thanks, pavroo! That's a nifty tool you have there. I was considering using it to make a pekwm Sparky remix.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on October 26, 2014, 03:27:33 pm
Why not? Feel free to customize Sparky.
Don't forget to past a download link when ready :)
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 26, 2014, 09:20:39 pm
Tried everything as in the tutorial, but the building iso process stops after about 12% and the computer restarts. I tried both methods, rebuild and the custom-build, but the result is the same. I did this again, without changing any app, except the iso name, but the result is the same.  Could you check the files, please?
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on November 26, 2014, 11:18:41 pm
1. Just let me know, to make sure: it stopped when xorriso was working?
2. Can you check what is the size of the new filesystem.squashfs file (in MB)
3. What iso image you try to rebuild? It's not compatible with all Debian based distros.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 27, 2014, 05:24:49 pm
1. Just let me know, to make sure: it stopped when xorriso was working?
2. Can you check what is the size of the new filesystem.squashfs file (in MB)
3. What iso image you try to rebuild? It's not compatible with all Debian based distros.

1. Yes, xorriso was working.
2. It was 313.8 MB, when it stopped.
3. Sparkylinux-3.5-x86_64-xfce.iso
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on November 27, 2014, 08:45:01 pm
I have checked the app and the iso image - it still works fine.
I think the problem is on your side.
Code: [Select]
It was 313.8 MBThe squashfs is too small. Normal one is about 1.5GB, if you added more packages it has to be even bigger.
As small as 300MB can be CLI edition iso only.
So I think there is not a problem with xorriso:
(http://sparkylinux.org/images/cib/thumbs/cib12.png)
but with building the new squashfs file (which is creating before iso image by xorriso):
(http://sparkylinux.org/images/cib/thumbs/cib23.png)
So it looks like, in my way that making the new filesystem.squashfs file you have used all available disk space.
That's why it stopped working.
To unpack sparky full edition iso you need at least 5GB, to build a new iso you need another 2-5 GB extra space.
If you have added much more extra applications to the new iso, and for example you'd like to build 4GB iso image, you need about 15-20 GB of the space.
Let me know some more about your space you had when the app stopped working.
Anyway if it still is a bug, it can help me fix it, if now it will help you build a new iso image.
Title: Re: SparkyLinux Custom ISO Builder
Post by: MoroS on November 27, 2014, 10:24:55 pm
So it looks like, in my way that making the new filesystem.squashfs file you have used all available disk space.
I wonder. I never heard of reboots caused by using up all the free space. The process should stop with an error, but no reason to reboot. If that was to be the symptom, then the system would never boot again (after restart there would still be no free space). I would suspect overheating here. That's a much more plausible cause for a reboot. Try monitoring your sensors and free disk space (just in case if I'm wrong on the disk space issue) while building the ISO.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on November 27, 2014, 10:39:22 pm
It can stop working if all the space is used.
I missed the rebooting, but it true.
My old laptop shuts down or reboots many times when the temperature was too hight.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 28, 2014, 12:03:37 am
You asked me about the filesystem.squashfs, which was the amount I mentioned. The squashfs-root was 5.2GB. I had more than 7.8 GB free after the rebooting. There is no overheating. I am going to try again.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 28, 2014, 07:27:19 pm
I tried again in a 22GB partition for the remaster folder. The working base is Sparkylinux-3.5-x86_64-xfce.iso and the iso to rebuild was the same. the squashfs-root is 4.9GB. Around 10-11% the building process stopped and the laptop powered off. The filesystem.squashfs is 316.1MB. The laptop never got over heated.

To check this matter, I remastered Ubuntu 14.10 within the partition, where Ubuntu was installed. The whole partition was 21GB, and the remaster was built within it. It used all 4 processors and the remaster was done within few minutes. I burnt it to a USB and installed it to make a full check.

I watched the speed of the remastering process in both and I see that Custom Iso Builder is quite slow. Most probably, it is not using all 4 processors.

EDIT: This happens when I try to use the Build_New method. The filesystem.squashfs should at least be 1.5GB
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on November 28, 2014, 10:19:55 pm
Yes, it should be, but your machine shuts down for a reason I don't know yet.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 29, 2014, 07:41:47 am
I made what's supposed to be done by the Build_New in a roundabout way and created a full remaster using the same machine. It was done in few minutes, using all 4 processors. I did that as a try, and I'd try to polish the files and redo it later. By the way, have anyone fully remastered SparkyLinux using the Custom-Iso-Builder?
Title: Re: SparkyLinux Custom ISO Builder
Post by: way12go on November 29, 2014, 09:44:43 am
I always wanted to use

1. Custom ISO maker

and

2. Backup current system into ISO ( Same effect I guess )

And I never tried 1 and when ever I tried 2 I had one recurring problem the ISO is large or it wouldn't boot from USB.

Any way I'm very happy with Sparkylinux install once and forget it, just dist-upgrade.

Time to time my fickle mind want to mess up with current install.

I shall never try something like that again and, that is, mess up with current system. I'm happy with Joe's Window Manager.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 29, 2014, 11:10:09 am
I always wanted to use

1. Custom ISO maker

and

2. Backup current system into ISO ( Same effect I guess )

And I never tried 1 and when ever I tried 2 I had one recurring problem the ISO is large or it wouldn't boot from USB.

Well pal, the idea is to try, and try, and try...until you get a result, even if the result is a negative one, and somehow you find a way out. I'd like to know the experience of others, who had tried to remaster SparkyLinux or Debian.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on November 29, 2014, 03:43:10 pm
It looks like the process of creating squashfs stops itself.
Make a test, so we can try to detect a problem.
1. Use Buld_New option to unpack an iso image.
2. Make changes - upgrade, install new apps, etc.

Close the Custom ISO Builder and open a terminal emulator in your working directory (as root).
1. Create live dir:
Code: [Select]
mkdir -p /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live2. Copy initrd and vmlinuz:
Code: [Select]
cp /full-patch/WORKINGDIRECTORY/squashfs-root/boot/vmlinuz-VERSION /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/vmlinuz
Code: [Select]
cp /full-patch/WORKINGDIRECTORY/squashfs-root/boot/initrd.img-VERSION /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/initrd.img
3. Still being in your WORKINGDIRECTORY create the new squashfs:
Code: [Select]
mksquashfs /full-patch/WORKINGDIRECTORY/squashfs-root /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/filesystem.squashfs -no-duplicates -no-recovery -comp xz -always-use-fragments -b 1MChange /full-patch/WORKINGDIRECTORY and VERSION number as you have.

Watch what is going on for any error message.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 30, 2014, 10:04:36 am
Using
Code: [Select]
mksquashfs /full-patch/WORKINGDIRECTORY/squashfs-root /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/filesystem.squashfs -no-duplicates -no-recovery -comp xz -always-use-fragments -b 1M building filesystem.squashfs stopped at 313MB, and with
Code: [Select]
mksquashfs /full-patch/WORKINGDIRECTORY/squashfs-root /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/filesystem.squashfs -no-duplicates -no-recovery -comp xz -always-use-fragments filesystem.squashfs stopped at 817.2MB.

But, without the switch comp-xz, i.e,
Code: [Select]
mksquashfs /full-patch/WORKINGDIRECTORY/squashfs-root /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/filesystem.squashfs -no-duplicates -no-recovery -always-use-fragments -b 1M building of the filesystem.squashfs was susccessful. Also, the processors were working at a lower rate.
Regards!

 
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on November 30, 2014, 02:12:39 pm
Now go to: /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT directory and build iso image:
Code: [Select]
xorriso -as mkisofs -rock -omit-version-number -disable-deep-relocation -joliet -allow-leading-dots -volid "ISO-NAME" -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -eltorito-alt-boot -e boot/grub/efi.img -no-emul-boot -o "/full-patch/WORKINGDIRECTORY/custom-linux-version-1.iso" "/full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNTIf the iso is made go to: /full-patch/WORKINGDIRECTORY and run:
Code: [Select]
isohybrid -u custom-linux-version-1.isoCreate md5sum if needed:
Code: [Select]
md5sum custom-linux-version-1.iso > custom-linux-version-1.iso.md5Change:
- ISO-NAME
- custom-linux-version-1

If some options are useless for you, edit CONFIG file and remove what you don't need from the line:
Code: [Select]
SQUASHFSOPTSFULL="-no-recovery -comp xz -always-use-fragments -b 1M"
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on November 30, 2014, 03:12:16 pm
Thanks Paweł!
I did all that earlier. I posted about remastering an iso in a roundabout way. It was (and still is) a nice learning experience going through your work.
Kind regards!
 
Title: Re: SparkyLinux Custom ISO Builder
Post by: MoroS on December 01, 2014, 11:07:27 am
...
But, without the switch comp-xz, [...] building of the filesystem.squashfs was susccessful. Also, the processors were working at a lower rate.
...

By ommiting the -comp parameter you switched from XZ compression to GZip compression, which is less resource intensive. That might really mean either overheating or RAM problems. Overheating won't be visible in log files. Memory failure might be visible (in /var/log/dmesg, /var/log/messages, /var/log/kernel if they still exist, because the SystemD transition made logging a bit more complicated :/ ). Memory issues should also occur when running a lot of things that will load up your memory, but you also might use memtest to check your memory, if you have some time to spare.

If you're into experiments you can try to monitor the temperature, CPU load and memory usage with a simple script that will write those values into 3 separate files. You can then post them so we can see what's happening:
Code: [Select]
#!/bin/bash
while true
do
    uptime >> $HOME/uptime.log
    free >> $HOME/memory.log
    sensors >> $HOME/sensors.log
    sleep 1;
done
This requires that you have lm_sensors installed (you probably have already, try executing the "sensors" command in the terminal). I was writing this script out of my head (don't have any Linux to test it at work :/ ), but it should work. Just launch the script in a separate terminal before building the SquashFS file. The files should be in your home directory.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on December 01, 2014, 04:59:19 pm
MoroS,
Thank you for the script. You are right, the laptop is overheating. The log files are massive to be copied here. I am pasting the last lines.
The laptop powers off  in 10 minutes,
Code: [Select]
16:18:51 up 10 min,  3 users,  load average: 5.64, 3.52, 1.63
It doesn't appear to use swap.
Code: [Select]
             total       used       free     shared    buffers     cached
Mem:       2884688    2779960     104728      75744     152388    1744208
-/+ buffers/cache:     883364    2001324
Swap:      2654204          4    2654200

The temperature, when it powers off,
Code: [Select]
acpitz-virtual-0
Adapter: Virtual device
temp1:        +84.0°C  (crit = +86.0°C)
temp2:        +66.0°C  (crit = +85.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +84.0°C  (high = +80.0°C, crit = +90.0°C)
Core 2:       +87.0°C  (high = +80.0°C, crit = +90.0°C)


Can't buy a new laptop yet, so I might have to use Gzip, rather than XZ. Actually, there is a newer laptop at home, but neither SparkyLinux (any Debian) or Xubuntu connects to WiFi.   
Title: Re: SparkyLinux Custom ISO Builder
Post by: MoroS on December 01, 2014, 05:57:28 pm
...the laptop is overheating...
Overheating is a common problem for laptops, especially when they're used near the maximum of their capabilities (most manufacturers today still treat them like typing machines and don't expect users to actually do power-usage). The thermal heatsink might also be clogged with dust, which causes higher than average temperatures (typically noticable after a year of hardware usage). On the other end there are also software solutions to prevent overheating on long and intensive tasks. One example would be CPUFreq, which manages the CPU scaling (governor and frequency). You might want to set a less demanding governor like "ondemand" or "powersave" prior to building the ISO (this keeps the frequencies low, thus giving lower temperatures, but at the cost of the whole process taking more time to complete).

The log files are massive...
I should've used a bigger (than 1 second) value for the sleep command. ;)

Can't buy a new laptop yet, so I might have to use Gzip, rather than XZ. Actually, there is a newer laptop at home, but neither SparkyLinux (any Debian) or Xubuntu connects to WiFi.
GZip should be fine most of the time (it should also be a bit faster when running the live image). As for the Wifi problems you might want to create a post about it on the forum and include your laptop model and the output of lspci and/or lsusb command (whether the former or latter contains information about your wifi model). Most of the problems are solvable by installing specific wifi driver-related packages.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on December 01, 2014, 06:56:54 pm
Thanks for the tips. I'll try cpufreq ondemand next time. What would be the command to set it and reset it to normal after? I have cpufrequtils installed.

I tried Custom Iso Builder on Ubuntu 14.10 as the base to rebuild SparkyLinux. I let it go for more than 10 mins and checked the sensor log, and the temperature had gone about 67°C few times in that 10 mins, but fallen to around 45°C. Is it something to do with the Debian base? Anyway, if I can get the work done with Gzip, that's perfectly okay with me.
Regards!
Title: Re: SparkyLinux Custom ISO Builder
Post by: MoroS on December 01, 2014, 10:19:04 pm
Thanks for the tips. I'll try cpufreq ondemand next time. What would be the command to set it and reset it to normal after? I have cpufrequtils installed.
You've got cpufreq-info to check which is currently used. Then use cpufreq-set to set it.

I tried Custom Iso Builder on Ubuntu 14.10 as the base to rebuild SparkyLinux. I let it go for more than 10 mins and checked the sensor log, and the temperature had gone about 67°C few times in that 10 mins, but fallen to around 45°C. Is it something to do with the Debian base? Anyway, if I can get the work done with Gzip, that's perfectly okay with me.
Regards!
I wonder. Maybe Ubuntu had the "ondemand" governor set by default. That would explain lower temperatures.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on December 01, 2014, 11:26:59 pm
I set
Code: [Select]
cpufreq-set --governor ondemand on Sparky and set Iso-builder to build the squashfs and it kept on going past 20% while checking the sensors log. The temperature went above 83°C few times, but went on building. It was slow, though. Would the ondemand command be always there after reboot?
Title: Re: SparkyLinux Custom ISO Builder
Post by: MoroS on December 04, 2014, 05:26:20 pm
I set
Code: [Select]
cpufreq-set --governor ondemand on Sparky and set Iso-builder to build the squashfs and it kept on going past 20% while checking the sensors log. The temperature went above 83°C few times, but went on building. It was slow, though. Would the ondemand command be always there after reboot?

Setting the governor via command line is only temporary. The settings reset with reboot. You can set it permanently via the /etc/default/cpufrequtils settings file.
Title: Re: SparkyLinux Custom ISO Builder
Post by: tems on December 09, 2014, 04:17:19 am
Hi team!

Congratulations for this spetacular  distro.
I have a project to create a fork to use in my religious community.
I wanted to work with the updated packages, but, when i use the ISO MASTER, in option building a new, and upgrade, when I run the last option it does not generate the iso.

Please, help.  I'm a still not as intermediate linux user. :(

Thanks, thanks!

Please, forgive me my poor English  :(
 
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on December 09, 2014, 12:25:04 pm
Hi
Have you read the guides already?
It looks like you don't choose right directory - it's very important.
http://sparkylinux.org/custom-iso-builder-howto-part-2/
Title: Re: SparkyLinux Custom ISO Builder
Post by: tems on December 10, 2014, 03:26:43 am
Thanks, Pavroo
Hi
Have you read the guides already?
It looks like you don't choose right directory - it's very important.
http://sparkylinux.org/custom-iso-builder-howto-part-2/

No, i had chosen the directory correct. it takes to process various minutes, but in the end does not generate iso.
i think because upgrade...

Please, please, i will like a tutorial for upgrade the 3.5xfce, change locale (language) and generate new iso.

Thanks an advance.

Tomaz Edson
Piaui - Brazil
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on December 10, 2014, 12:39:17 pm
Can you try again with the new iso of sparky 3.6 xfce?
Title: Re: SparkyLinux Custom ISO Builder
Post by: tems on December 11, 2014, 12:45:01 am
Can you try again with the new iso of sparky 3.6 xfce?

My distro is 3.5 xfce updated, but now o chroot not work. it can't find the bash (more or less). My version is 0.1.2

i managed with sudo chroot /mydirectory/squashfs-root/

I would like to know how to change the language for the live pr_BR.UTF-8. I did dpkg-reconfigure locales but does not seem to be enough.

Help!!!

Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on December 11, 2014, 01:20:58 pm
1. Reconfigure locales - what you did already.
2. Edit /etc/rc.local and add configuration for pr_BR locale.
2. Edit /etc/remastersys/isolinux/live.cfg and add entry for pr_BR as the first.

But...
The latest live installer 20141204-1 doesn't work well with different localization than en_US. That's why I removed all the locales from iso 3.6 (excluding en_US).
But...
There still is the old installer in the live system so if you set new iso locale to pr_BR you can use the old installer if you'd like.
But...
The old installer works on BIOS machines only, doesn't support EFI machines.

Don't call "Help", please.
What we do here is helping anyway.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on December 11, 2014, 07:43:31 pm
1. Reconfigure locales - what you did already.
2. Edit /etc/rc.local and add configuration for pr_BR locale.
3. Edit /etc/remastersys/isolinux/live.cfg and add entry for pr_BR as the first.

#2. /etc/rc.local is usually empty.
#3. There is no /etc/remastersys/isolinux/live.cfg in either 3.5 or 3.6 releases, after installing, but its there in squashfs-root, and can be changed, but doesn't work with Custom Iso Builder. One has to change /YourDirectory/ISOTEMP/ISOMOUNT/isolinux/live.cfg.

Either we have to use Custom Iso Builder or Remastersys.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on December 11, 2014, 08:08:28 pm
Quote
#2. /etc/rc.local is usually empty.
No, it's not.
Up to sparky version 3.5 there is configuration for all locales used in live system.
Check: /WORKINGDIRECTORY/squashfs-root/etc/rc.local
Quote
There is no /etc/remastersys/isolinux/live.cfg in either 3.5 or 3.6 releases
No, there is not.
Custom Iso Builder can be used to remaster iso image NOT installed system.
live.cfg file is in: /WORKINGDIRECTORY/squashfs-root/etc/remastersys/isolinux/live.cfg
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on December 11, 2014, 09:30:44 pm
Quote
#2. /etc/rc.local is usually empty.
No, it's not.
Up to sparky version 3.5 there is configuration for all locales used in live system.
Check: /WORKINGDIRECTORY/squashfs-root/etc/rc.local
Quote
There is no /etc/remastersys/isolinux/live.cfg in either 3.5 or 3.6 releases
No, there is not.
Custom Iso Builder can be used to remaster iso image NOT installed system.
live.cfg file is in: /WORKINGDIRECTORY/squashfs-root/etc/remastersys/isolinux/live.cfg

#1. Yes, it is not empty in 3.5, but empty in 3.6. I'm not 100% sure, whether to stay with 3.5, or move to 3.6, as once dist-upgrade, you get the new kernel.

#2. This live.cfg in /WORKINGDIRECTORY/squashfs-root/etc/remastersys/isolinux/live.cfg has nothing to do with remastering with Custom Iso Builder, when trying to remaster the iso image, does it? You have to change the live.cfg in /WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/isolinux/live.cfg, if you have to get something done with remastering the iso image, right? I am not talking about remastering the installed system here, but the iso image.

By the way, when using Build_New, it doesn't always copy the initrd.img to /WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/isolinux/live, and goes on to build the iso without the initrd.img, so I had to copy it manually into the newly built iso. It would be nice to stop the process to look in, before it starts to create the isohybrid. 
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on December 11, 2014, 09:53:40 pm
Quote
Yes, it is not empty in 3.5, but empty in 3.6.
That's right, I mentioned it before.
If you have 3.5 upgraded already, you don't need to use 3.6.
The file: /WORKINGDIRECTORY/squashfs-root/etc/remastersys/isolinux/live.cfg will be used to choose and run live system in your locale.
Quote
By the way, when using Build_New, it doesn't always copy the initrd.img
If you upgraded the chrooted system and the upgrading installed a new kernel,  try to rebuild the initrd:
Code: [Select]
update-initrd -uThen uninstall the old kernel.
Check is the initrd.img linking to the newest initrd-number.img in /WORKINGDIRECTORY/squashfs-root/boot/ directory.
Maybe it helps.
Title: Re: SparkyLinux Custom ISO Builder
Post by: tems on December 13, 2014, 03:08:56 am
Thanks, Pavroo
Excuse-me for the "help!", i"m sure you are here to help everyone.

After i post test results.

Title: Re: SparkyLinux Custom ISO Builder
Post by: tems on December 14, 2014, 03:18:27 am
Hi, team,

I need to do something before update packages? (in chroot)

What is the dbus-uuidgen > /var/lib/dbus/machine-id? Its necessary?

Thanks an advance.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on December 14, 2014, 02:10:09 pm
Quote
I need to do something before update packages?
I don't think so.
Quote
What is the dbus-uuidgen
http://dbus.freedesktop.org/doc/dbus-uuidgen.1.html
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on April 15, 2015, 11:03:12 am
Pavroo, Custom Iso Builder usually increases the size of the custom built iso by about 30% in Build-new, even when no new application is installed. Is there a way to change this? 
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on April 15, 2015, 01:08:36 pm
Even you haven't installed new packages, have you upgraded all of the existing ones?
If yes clean the cache:
Code: [Select]
apt-get autoremove && apt-get cleanand try again.
Let me know about results.
Title: Re: SparkyLinux Custom ISO Builder
Post by: MoroS on April 15, 2015, 01:21:28 pm
Code: [Select]
apt-get autoremove && apt-get clean
Maybe we should include this step in CIB and SBS? Since someone wants to build an ISO from his system, he should clean up a bit. That's not always the case, so we might ask the user if he wants to clean up the packages prior to making the ISO.
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on April 15, 2015, 02:14:51 pm
It's good idea, I will add it.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on April 15, 2015, 04:21:32 pm
Even without upgrading any apps, the resulting iso is more than 30% larger. It must be something to do with Remastersys?
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on April 15, 2015, 07:24:23 pm
It looks like the tool doesn't use xz compression.
Check do you have 'xz-utils' package installed in your host system.
Check are they any 'deb' packages still exist in /var/cache/apt/archives directory of the chrooted file system.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on April 15, 2015, 07:54:56 pm
xz-utils is installed.
No 'deb' packages still exist in /var/cache/apt/archives directory.
What might be the problem? Is Remastersys adding up something?
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on April 15, 2015, 09:04:03 pm
There is nothing about remastersys.
Looks like custom-iso-builder doesn't use xz compression on your system, that's why the iso image is bigger.
In my way it uses standard gz compression instead of xz.
I made a test with 4.0rc LXDE iso image.
Before: 1.541.124B
After: 1.540.576B
It's even smaller then the original one.
Sorry but I don't know by now why it makes bigger on your machine.
Title: Re: SparkyLinux Custom ISO Builder
Post by: Chdslv on July 14, 2015, 08:45:45 am
Is CIB taken off the repos?
Title: Re: SparkyLinux Custom ISO Builder
Post by: pavroo on July 14, 2015, 02:03:52 pm
No, it's still there - v0.1.5-1
Title: Re: SparkyLinux Custom ISO Builder
Post by: godstand2 on March 06, 2017, 12:43:46 am
Do not place much stuff in the /etc/skel directory. It breaks the live system and it won't start. How much is much stuff can i put the stuff from my home/(username) folder in there?
Title: Re: SparkyLinux Custom ISO Builder
Post by: godstand2 on March 13, 2017, 03:56:21 am
I really love SparkyLinux the most of all distros for it is sooooo fast on all computers Old and new(by the way the 32bit is what I use even on 64bit computers). I was wondering after I have already set up my sparky how can I make a backup disk with all my settings and apps and not just a hybrid iso like sparkybackup dist does and keep it for an emergencies to install it to say another computer, Like I can with Systemback does.It also gives you the option to install for a new user. I had installed System back on Sparkylink test machines and tried to use the copy user data and settings box checked and it said that it could not read Live image even when i tried to install the same thing happened, from the ISO I had made of the system using Systemback. I could run the live cd but not copy or install even with out box checked for user data and settings always "Could not read Live image error." I have made an ISO from Sparkybackup dist and it runns with all the the stuff i put in root folder including wine,games and programs as long as I installed them in root folder running as root also settings for root like themes and cursors the live disk ran with out a hitch even installed on another hdd but not with users setting or data was the image made so i would have to start all over again to set up slimjet browser for the user that is only browser I use as well have to setup appearance,screensavers,cursors and so on.All this work time and energy makes johnny boy here tired. It would be so nice to copy my system to my other computers with all settings and data intact and also from same disk install for new user with the little bit of the extras I have installed in root.The Sparkybackup ISO was 1.9GB size when I got done making it using the xz setting.