| SQUASHFS CHANGE LOG |
| |
| 1.0 23 OCT 2002 Initial release |
| |
| 1.0c 14 NOV 2002 Bug fix release |
| |
| Fixed bugs with initrds and device nodes |
| |
| 1.1 8 JAN 2003 Added features |
| |
| 1. Kernel squashfs can now mount different byte order filesystems. |
| 2. Additional features added to mksquashfs. Mksquashfs now supports |
| exclude files and multiple source files/directories can be |
| specified. A nopad option has also been added, which |
| informs mksquashfs not to pad filesystems to a multiple of 4K. |
| See README for mksquashfs usage changes. |
| 3. Greater than 2GB filesystems bug fix. Filesystems greater than 2GB |
| can now be created. |
| 4. Patch for 2.4.20 kernels. |
| |
| 1.1b 16 JAN 2003 Bug fix release |
| |
| Fixed readpage deadlock bug. This was a rare deadlock bug that |
| happened when pushing pages into the page cache when using greater |
| than 4K blocks. I never got this bug when I tested the filesystem, |
| but two people emailed me on the same day about the problem! |
| I fixed it by using a page cache function that wasn't there when |
| I originally did the work, which was nice :-) |
| |
| 1.2 13 MAR 2003 Append feature and new mksquashfs options added |
| |
| Mksquashfs can now add to existing squashfs filesystems. Three extra |
| options "-noappend", "-keep-as-directory", and "root-becomes" |
| have been added. |
| |
| The append option with file duplicate detection, means squashfs can be |
| used as a simple versioning archiving filesystem. A squashfs |
| filesystem can be created with for example the linux-2.4.19 source. |
| Appending the linux-2.4.20 source will create a filesystem with the |
| two source trees, but only the changed files will take extra room, |
| the unchanged files will be detected as duplicates. |
| |
| See the README file for usage changes. |
| |
| 1.3 29 JUL 2003 FIFO/Socket support added plus optimisations and |
| improvements |
| |
| 1. FIFOs and Socket inodes are now supported, |
| 2. Mksquashfs can now compress files larger than available |
| memory, |
| 3. File duplicate check routine optimised, |
| 4. Exit codes fixed in Mksquashfs, |
| 5. Patch for Linux 2.4.21, |
| 6. Patch for Linux 2.6.0-test1. Hopefully, this will work for |
| the next few releases of 2.6.0-testx, otherwise, I'll be |
| releasing a lot of updates to the 2.6.0 patch... |
| |
| 1.3r2 14 OCT 2003 Second release of 1.3, bug fixes and extra patches for |
| new kernels |
| |
| 1. Bug fix in routine that adds files to the filesystem being |
| generated in mksquashfs. This bug was introduced in 1.3 |
| (not enough testing...) when I rewrote it to handle files larger |
| than available memory. This bug caused a SEGV, so if you've ever |
| got that, it is now fixed, |
| 2. Long running bug where ls -s and du reported wrong block size |
| fixed. I'm pretty sure this used to work many kernel versions ago |
| (2.4.7) but it broke somewhere along the line since then, |
| 3. New patch for Linux 2.4.22, |
| 4. New patch for 2.6.0-test7, this replaces the patch for 2.6.0-test1. |
| |
| 1.3r3 18 JAN 2004 Third release of 1.3, this adds a new mksquashfs option, |
| some bug fixes, and extra patches for new kernels |
| |
| 1. New mksquashfs -ef exclude option. This option reads the exclude |
| dirs/files from an exclude file, one exclude dir/file per line. This |
| avoids the command line size limit when using the -e exclude option, |
| 2. When appending to existing filesystems, if mksquashfs experiences a |
| fatal error (e.g. out of space when adding to the destination), the |
| original filesystem is restored, |
| 3. Mksquashfs now builds standalone, without the kernel needing to be |
| patched. |
| 4. Bug fix in the kernel squashfs filesystem, where the pages being |
| filled were not kmapped. This seems to only have caused problems |
| on an Apple G5, |
| 5. New patch for Linux 2.4.24, |
| 6. New patch for Linux 2.6.1, this replaces the patch for 2.6.0-test7. |
| |
| 2.0-ALPHA 21 MAY 2004 Filesystem changes and compression improvements |
| |
| 1. Squashfs 2.0 has added the concept of fragment blocks. |
| Files smaller than the file block size and optionally the |
| remainder of files that do not fit fully into a block (i.e. the |
| last 32K in a 96K file) are packed into shared fragments and |
| compressed together. This achieves on average 5 - 20% better |
| compression than Squashfs 1.x. |
| 2. The maximum block size has been increased to 64K (in the ALPHA |
| version of Squashfs 2.0). |
| 3. The maximum number of UIDs has been increased to 256 (from 48 in |
| 1.x). |
| 4. The maximum number of GIDs has been increased to 256 (from 15 in |
| 1.x). |
| 5. Removal of sleep_on() function call in 2.6.x patch, to allow Squashfs |
| to work on the Fedora rc2 kernel. |
| 6. Numerous small bug fixes have been made. |
| |
| 2.0 13 JULY 2004 A couple of new options, and some bug fixes |
| |
| 1. New mksquashfs -all-root, -root-owned, -force-uid, and -force-gid |
| options. These allow the uids/gids of files in the generated |
| filesystem to be specified, overriding the uids/gids in the |
| source filesystem. |
| 2. Initrds are now supported for kernels 2.6.x. |
| 3. amd64 bug fixes. If you use an amd64, please read the README-AMD64 |
| file. |
| 4. Check-data and gid bug fixes. With 2.0-alpha when mounting 1.x |
| filesystems in certain cases file gids were corrupted. |
| 5. New patch for Linux 2.6.7. |
| |
| 2.0r2 29 AUG 2004 Workaround for kernel bug in kernels 2.6.8 and newer |
| added |
| |
| 1. New patch for kernel 2.6.8.1. This includes a workaround for a |
| kernel bug introduced in 2.6.7bk14, which is present in all later |
| versions of the kernel. |
| |
| If you're using a 2.6.8 kernel or later then you must use this |
| 2.6.8.1 patch. If you've experienced hangs or oopses using Squashfs |
| with a 2.6.8 or later kernel then you've hit this bug, and this |
| patch will fix it. |
| |
| It is worth mentioning that this kernel bug potentially affects |
| other filesystems. If you receive odd results with other |
| filesystems you may be experiencing this bug with that filesystem. |
| I submitted a patch but this has not yet gone into the |
| kernel, hopefully the bug will be fixed in later kernels. |