public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs version 1 compatibility
Date: Thu, 26 Mar 2009 23:04:31 +1100	[thread overview]
Message-ID: <20090326120431.GA13745@cloud.net.au> (raw)
In-Reply-To: <1238061023.3321.67.camel@localhost.localdomain>

On Thu, Mar 26, 2009 at 11:50:23AM +0200, Artem Bityutskiy wrote:
> On Thu, 2009-03-26 at 18:44 +1100, Hamish Moffatt wrote:
> makes it very difficult to turn old image into new one. This will
> basically mean we need:
> 
> 1. extract files from the old image
> 2. feed them to mkfs.ubifs.
> 
> > Maybe before upgrade we could run mkfs.ubifs using the contents of the
> > existing volume to create the new format, unmount it and ubiupdatevol it..
> 
> The easiest way to do this is to boot the old kernel,
> e.g. in vmware, extract the files using the nandsim technique:
> http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_nandsim
> 
> then feed them to mkfs.ubifs.

Well I have these files on embedded devices out in the real world. The
volume is storing user data, so I need to do this change in-place.

> But yes, a user-space utility to extract files from an image would be
> of course nicer, but again it is something which is not easy to do.

OK I will investigate having the system build a new file system with
a new mkfs.ubifs while running the old kernel.. Alternatively I may be
able to stash the data somewhere else and copy it back when the new
kernel first boots.. I probably have some space in NOR for a small JFFS2
volume. Or I'll tar directly to an mtdblock device or something :)


thanks
Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2009-03-26 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  5:15 ubifs version 1 compatibility Hamish Moffatt
2009-03-26  6:02 ` Artem Bityutskiy
2009-03-26  6:34 ` Artem Bityutskiy
2009-03-26  7:44   ` Hamish Moffatt
2009-03-26  9:50     ` Artem Bityutskiy
2009-03-26 12:04       ` Hamish Moffatt [this message]
2009-03-26 12:12         ` Artem Bityutskiy
2009-03-26 13:15           ` Hamish Moffatt
2009-03-31  6:23             ` Artem Bityutskiy

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=20090326120431.GA13745@cloud.net.au \
    --to=hamish@cloud.net.au \
    --cc=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    /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