From: Robert Homann <homann@bury.com>
To: linux-mtd@lists.infradead.org
Cc: dedekind1@gmail.com
Subject: Re: Resizing of an existing UBIFS
Date: Fri, 25 May 2012 09:49:01 +0200 [thread overview]
Message-ID: <4FBF396D.4070000@bury.com> (raw)
In-Reply-To: <4FBF2DF7.8030809@intel.com>
On 05/25/2012 09:00 AM, Adrian Hunter wrote:
Hi!
> Before writing a tool you should check how much overhead there is in simply
> making max-leb-cnt as big as you might ever want.
It is definitely a lot simpler to just set this parameter to some big value
and generate new images from scratch since the overhead in space consumption
is not an issue in this case. But let's say, in my case the purpose of using
such a resizing tool is not space optimization, but fixing a former
decision...
I still need to think about whether or not it is worth the effort to write a
resizing tool. Should I decide to make it, I'll first ask around on this list
to provide some suggestions about the features that could and should be
supported while at it. Don't hold your breath, though. :)
Best regards,
Robert Homann
next prev parent reply other threads:[~2012-05-25 7:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 6:41 Resizing of an existing UBIFS Robert Homann
2012-05-22 6:53 ` Artem Bityutskiy
2012-05-22 7:21 ` Robert Homann
2012-05-22 8:10 ` Artem Bityutskiy
2012-05-22 9:25 ` Robert Homann
2012-05-22 9:40 ` Ricard Wanderlof
2012-05-22 10:19 ` Artem Bityutskiy
2012-05-22 11:11 ` Robert Homann
2012-05-22 11:24 ` Artem Bityutskiy
2012-05-25 7:00 ` Adrian Hunter
2012-05-25 7:49 ` Robert Homann [this message]
2012-05-25 8:00 ` Ricard Wanderlof
2012-05-28 9:09 ` Adrian Hunter
2012-06-01 10:10 ` Ricard Wanderlof
2012-06-01 11:48 ` Adrian Hunter
2012-06-01 19:47 ` Ricard Wanderlof
2012-06-04 7:58 ` Adrian Hunter
2012-06-04 9:35 ` Ricard Wanderlof
2012-06-04 9:47 ` Artem Bityutskiy
2012-05-25 10:12 ` Norbert van Bolhuis
2012-05-26 14:00 ` Artem Bityutskiy
2012-05-27 20:24 ` Norbert van Bolhuis
2012-05-28 5:46 ` 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=4FBF396D.4070000@bury.com \
--to=homann@bury.com \
--cc=dedekind1@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.