See notes around a third of the way down this GitHub page
squashfuse has been ported into FreeBSD ... see Thread 56767
So if you use packages you can install
squashfs-tools provides mksquashfs and unsquashfs commands that create (extract) compressed file system images. Say for instance you want to make a backup of your current running system then you might
which basically is saying make a copy of everything from / down storing that into a squashed filesystem file called backup.sfs. The -e parameter indicates to exclude the /tmp folder from being backed up ... as in this case that is where the backup.sfs file (squashed filesystem) is being created and not excluding that folder would enter into some kind of eternal loop of copying itself (backup.sfs file).
That backup.sfs squashed filesystem single file can be extracted using something like
that tells unsquashfs to force extract to the / folder the content of backup.sfs
I've only used the above purely as a example. Copying and restoring a live running system wouldn't be a wise choice as you'd start over-writing some system files with versions that were recorded in the backup ... that likely would crash the system. More usually you'd use mksquashfs and unsquashfs in a similar manner to using tar or zip on selected folders only, or perhaps to backup a whole system but having booted from the freebsd boot CD.
squashfuse provides a means to mount a single squashed filesystem file and browse around those files (read only). squashfuse requires the fuse module to be loaded i.e. edit /boot/loader.conf to include
and then after rebooting that will be active. You can then mount a file such as backup.sfs running (as root)
to create a mount point directory
after which you can cd to m and start browsing the contents. Afterwards umount that by changing directory to where the m folder is and
As the above linked GitHub entry suggests
If you have htop installed, fire that up whilst making a squashfs and you'll see that it uses all of the cores available i.e. multi cores will create a sfs quicker than a single core as it does things in parallel.
mksquashfs shows a nice progress bar as its running that provides a indication of how long its going to take to complete
squashfuse has been ported into FreeBSD ... see Thread 56767
So if you use packages you can install
pkg install squashfs-tools pkg install fusefs-squashfusesquashfs-tools provides mksquashfs and unsquashfs commands that create (extract) compressed file system images. Say for instance you want to make a backup of your current running system then you might
cd /tmp mksquashfs / backup.sfs -e tmpwhich basically is saying make a copy of everything from / down storing that into a squashed filesystem file called backup.sfs. The -e parameter indicates to exclude the /tmp folder from being backed up ... as in this case that is where the backup.sfs file (squashed filesystem) is being created and not excluding that folder would enter into some kind of eternal loop of copying itself (backup.sfs file).
That backup.sfs squashed filesystem single file can be extracted using something like
cd /tmp unsquashfs -f -d / backup.sfsthat tells unsquashfs to force extract to the / folder the content of backup.sfs
I've only used the above purely as a example. Copying and restoring a live running system wouldn't be a wise choice as you'd start over-writing some system files with versions that were recorded in the backup ... that likely would crash the system. More usually you'd use mksquashfs and unsquashfs in a similar manner to using tar or zip on selected folders only, or perhaps to backup a whole system but having booted from the freebsd boot CD.
squashfuse provides a means to mount a single squashed filesystem file and browse around those files (read only). squashfuse requires the fuse module to be loaded i.e. edit /boot/loader.conf to include
Code:
fuse_load="YES" mkdir mto create a mount point directory
squashfuse backup.sfs mafter which you can cd to m and start browsing the contents. Afterwards umount that by changing directory to where the m folder is and
umount mAs the above linked GitHub entry suggests
If you have htop installed, fire that up whilst making a squashfs and you'll see that it uses all of the cores available i.e. multi cores will create a sfs quicker than a single core as it does things in parallel.
mksquashfs shows a nice progress bar as its running that provides a indication of how long its going to take to complete
as speed improvements can be considerable. But then again in a world of 32GB common desktops, cached IO is near 100% of the base system anyway.