From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Woody Suwalski <woodys@xandros.com>
Cc: Matthias Kaehlcke <matthias@kaehlcke.net>, linux-kernel@vger.kernel.org
Subject: Re: [BUG?] SQUASHFS error: Major/Minor mismatch
Date: Tue, 13 Jan 2009 09:00:54 +0000 [thread overview]
Message-ID: <496C5846.3050809@lougher.demon.co.uk> (raw)
In-Reply-To: <496BC02A.2020402@xandros.com>
Woody Suwalski wrote:
> Phillip Lougher wrote:
>>
>> You have to use the latest version of Mksquashfs in CVS available
>> from http://squashfs.org.
>>
>> git-cvsimport -v -d
>> :pserver:anonymous@squashfs.cvs.sourceforge.net:/cvsroot/squashfs
>> squashfs
>>
>> Phillip
>>
> Does not look good! I have squashfs images which work OK in 3.3 and 3.4,
> but now I try to boot 2.6.29-rc1 and it can not mount my squashfs root
> partition!
> Does it mean that squashfs4 is not backward-compatible? If so - I can
> not use it - all my images are generated on 3.3 .. 3.4...
>
Backwards compatibility was dropped as part of the original review
complaints against mainlining. The new 4.0 layout was necessary to address
some issues again relating to the original review complaints. The 4.0
layout is designed to hopefully not require any further modification in the
future.
Ultimately this does mean the Squashfs mainline code will never be able to
read older filesystems. But, unsquashfs will always be able to read all
filesystem versions, and I'll maintain out-of-tree patches that add
backwards compatibility to the kernel code for those that need it. This
should be finished in the near future.
Philllip
prev parent reply other threads:[~2009-01-13 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 14:08 [BUG?] SQUASHFS error: Major/Minor mismatch Matthias Kaehlcke
2009-01-12 14:49 ` Geert Uytterhoeven
2009-01-12 15:06 ` Matthias Kaehlcke
2009-01-12 14:53 ` Phillip Lougher
2009-01-12 22:11 ` Woody Suwalski
2009-01-13 9:00 ` Phillip Lougher [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496C5846.3050809@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias@kaehlcke.net \
--cc=woodys@xandros.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox