Salix Forums

Hi all,

chances are, that in 2.6.38 xz compression for squashfs will be included.

The uncompression speed is ~30% higher than with legacy lzma patched squashfs.

My questions are:

1. will SalixOS use xz compressed squashfs?
2. if yes, what do the developers think about using .xzm for module naming?

I think by using .xzm we could achieve an easy way to be able to separate squashfs4 based modules from squashfs3-based ones.

Regards, Quax

For now Slackware current still has kernel version 2.6.35.10.

As stated by thenktor, Slackware current is still on 2.6.35.10 and Pat doesn't want to use 2.6.36 or 2.6.37 due to some to-be-verified-security concerns. So maybe if 2.6.38 will be ready before Salckware current becomes 13.2 and if Pat is ok with it, we could have it.

Btw, for Salix Live, we still need to patch the kernel (for aufs2), so if xz compression for sqaushfs is not included by default on the kernel running 13.2, Salix (I) will patch the kernel for include it. Squashfs-tools that is going to be push in salix-current can already generate squashfs filesystem with xz compression.

About the extension name, It really doesn't matter. Salix will use a new system of Live scripts for 13.2, and the modules (squashfs4+lzma or squashfs4+xz) will be named under this new system and will not be related to the underlying FS+compression.

For me, a good extension should be "sq4xz" if you really want to have one. xzm doesn't make sens, as it is a filesystem and it's only a module in a sens of a live CD. But as I stated earlier, I thing it doesn't matter.

JRD wrote:Salix will use a new system of Live scripts for 13.2

Am afraid ... And curious. May we have any info?

Find the Salix liveCDs so nice. Wondering if any improvement except updating of programs is possible? Trust you 'll keep the cheatcodes and features of the actual Live scripts.

Looking forward to receiving your reaction.

I'll keep you inform in the days (or weeks ?) to come. Don't be afraid, from the user experience, it will not change much.