public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	linux-kernel@vger.kernel.org,
	squashfs-devel@lists.sourceforge.net
Subject: Re: Squashfs 4.0 tools
Date: Tue, 24 Mar 2009 08:15:34 +0300	[thread overview]
Message-ID: <49C86C76.70006@msgid.tls.msk.ru> (raw)
In-Reply-To: <49C847C6.4030904@lougher.demon.co.uk>

Phillip Lougher wrote:
> Stephen Hemminger wrote:
>> It is great that squashfs is finally in mainline kernel. But the
>> squashfs tools are tightly bound to the version of the squashfs 
>> filesystem.
[]
> I have been working on the 4.0 squashfs tools for the last couple of
> months making them (mksquashfs and unsquashfs) ready for a supported
> release.  Now that Linux 2.6.29 has been released (3 hours ago), I
> need to make this release ASAP, which as everything is almost finished,
> should be sometime this week.

By the way, with this on-disk format change, is there a way to get
4.0 fs code working with 2.6.27 (long-time-stable) kernel?  I tried
to compile it on 2.6.27 but it fails due to some API changes and I'm
not that deep into kernel to fix it...

Thanks!

  reply	other threads:[~2009-03-24  5:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  1:08 Squashfs 4.0 tools Stephen Hemminger
2009-03-24  2:39 ` Phillip Lougher
2009-03-24  5:15   ` Michael Tokarev [this message]
2009-03-31  6:01     ` [Squashfs-devel] " Phillip Lougher
2009-03-28 22:27   ` Rob Landley
2009-03-29  9:02     ` Geert Uytterhoeven
2009-03-31  0:55       ` Stephen Hemminger
2009-03-31  5:51         ` Phillip Lougher
2009-03-31 19:31         ` Rob Landley
2009-04-01  1:05           ` Phillip Lougher
2009-04-01 11:40             ` [Squashfs-devel] " Peter Korsgaard
2009-04-05 23:27             ` Phillip Lougher
2009-04-06  8:55               ` Rob Landley

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=49C86C76.70006@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    --cc=shemminger@vyatta.com \
    --cc=squashfs-devel@lists.sourceforge.net \
    /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