One approach would be the use pbzip2, another to split up the whole operation in n tasks and let grep -c "^processor" /proc/cpuinfo of them be processed in parallel. Problem is that SBC are pretty slow when it's about compression and that most tools fail to compress multi-threaded when input is stdin (pipe from dd). On Fast Ethernet equipped boards the best mode would be a special mini distro they can boot with that hands out the eMMC in USB mass storage gadget mode (explained here to prepare correctly sized DD images), on GbE equipped boards IMO the best variant is to send the eMMC's contents over network to a beefy box where it gets compressed there (in fact I do this for quick cloning, using dd on the devices I test with, send the stream through netcat and create an archive at the target location (if it's OS X it's done mostly on the GPU cores using ditto -c -k -sequesterRsrc -keepParent)īut we're searching for a way to clone to network shares or external disks too. Doing SD card clones is easy (and save, a running OS can not be cloned 100 percent consitently without taking special precautions) but people struggle with eMMC equipped board. We'd love to hear more about the "device backups with metadata" use case too, as backups are on the etcher roadmap, if a bit down the line.įrom time to time I do some research on this as it's something Armbian users are constantly asking for. Reply to this email directly or view it on GitHub: You are receiving this because you were assigned. But I'm not the average user :)īTW: Regarding application size: Did you try to apply HFS+ transparent file compression to your application bundle already using afsctool? Only drawback (at least for me using OS X): decompression happens on the CPU cores and not on the GPU as with. In the meantime we only use -mx=3 instead of -mx=9 since we build +100 OS images with every update, size differences are only small but time savings huge. LZMA with maximum compression applied to a clean image (made from scratch) is way more effizient than. (~10MB), but its definitely an improvement. Very nice, thank you very much for the suggestion. More well-known to image consumers, plus we have support for it inīTW: Regarding application size: Did you try to apply HFS+ transparentįile compression to your application bundle already using xz? It also uses the LZMA compression algorithm and its LZMA with maximum compression applied toĪ clean image (made from scratch) is way more effizient than.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |