linux-kernel - Squashfs 4.0 tools (for 2.6.29) released

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 06 Apr 2009 00:41:53 +0100
From:	Phillip Lougher <phillip@...gher.demon.co.uk>
To:	squashfs-devel@...ts.sourceforge.net,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	Linux Embedded Maillist <linux-embedded@...r.kernel.org>
Subject: Squashfs 4.0 tools (for 2.6.29) released

Hi,

I'm pleased to announce the first release of the squashfs 4.0 tools.
These are needed by any Squashfs users using linux 2.6.29.  They are available
from http://sourceforge.net/projects/squashfs

The changes from the change-log are:

1. Unsquashfs improvements:

1.1 Support for 4.0 filesystems added.
1.2 Swapping macros rewritten.
1.3 Unsquashfs code restructured and split into separate files.

2. Mksquashfs improvements:

2.1 Swapping macros rewritten.  Fixed little-endian layout allows
     code to be optimised and only added at compile time for
     big endian systems.
2.2 Support for pseudo files added.

New Mksquashfs options

Mksquashfs now supports pseudo files, these allow fake directories, character
and block devices to be specified and added to the Squashfs filesystem being
built, rather than requiring them to be present in the source directories.
This, for example, allows device nodes to be added to the filesystem without
requiring root access.

Phillip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/