Welcome to SparkyLinux forumsZapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl
Started by way12go, August 12, 2014, 03:15:36 PM
Quote from: way12go on November 29, 2014, 09:44:43 AMI always wanted to use1. Custom ISO makerand2. 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.
mkdir -p /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live
cp /full-patch/WORKINGDIRECTORY/squashfs-root/boot/vmlinuz-VERSION /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/vmlinuz
cp /full-patch/WORKINGDIRECTORY/squashfs-root/boot/initrd.img-VERSION /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/initrd.img
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
mksquashfs /full-patch/WORKINGDIRECTORY/squashfs-root /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/filesystem.squashfs -no-duplicates -no-recovery -comp xz -always-use-fragments
mksquashfs /full-patch/WORKINGDIRECTORY/squashfs-root /full-patch/WORKINGDIRECTORY/ISOTEMP/ISOMOUNT/live/filesystem.squashfs -no-duplicates -no-recovery -always-use-fragments -b 1M
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/ISOMOUNT
isohybrid -u custom-linux-version-1.iso
md5sum custom-linux-version-1.iso > custom-linux-version-1.iso.md5
SQUASHFSOPTSFULL="-no-recovery -comp xz -always-use-fragments -b 1M"
Quote from: Chdslv on November 30, 2014, 10:04:36 AM...But, without the switch comp-xz, [...] building of the filesystem.squashfs was susccessful. Also, the processors were working at a lower rate....
#!/bin/bashwhile truedo uptime >> $HOME/uptime.log free >> $HOME/memory.log sensors >> $HOME/sensors.log sleep 1;done
16:18:51 up 10 min, 3 users, load average: 5.64, 3.52, 1.63
total used free shared buffers cachedMem: 2884688 2779960 104728 75744 152388 1744208-/+ buffers/cache: 883364 2001324Swap: 2654204 4 2654200
acpitz-virtual-0Adapter: Virtual devicetemp1: +84.0°C (crit = +86.0°C)temp2: +66.0°C (crit = +85.0°C)coretemp-isa-0000Adapter: ISA adapterCore 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)
Quote from: Chdslv on December 01, 2014, 04:59:19 PM...the laptop is overheating...
Quote from: Chdslv on December 01, 2014, 04:59:19 PMThe log files are massive...
Quote from: Chdslv on December 01, 2014, 04:59:19 PMCan'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.
Quote from: Chdslv on December 01, 2014, 06:56:54 PMThanks 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.
Quote from: Chdslv on December 01, 2014, 06:56:54 PMI 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!
cpufreq-set --governor ondemand
Quote from: Chdslv on December 01, 2014, 11:26:59 PMI set Code Select Expandcpufreq-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?
View the most recent posts on the forum