From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Cc: John Burch <jburch@vincisystems.com>
Subject: Re: reach of jffs2 within image vs. partition
Date: Wed, 2 Apr 2003 16:03:04 +0200 [thread overview]
Message-ID: <20030402140304.GA752@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1049291095.2652.2.camel@passion.cambridge.redhat.com>
On Wed, 2 April 2003 14:44:56 +0100, David Woodhouse wrote:
> On Wed, 2003-04-02 at 14:41, John Burch wrote:
> > Is there any advantage or disadvantage to creating the jffs2 image file
> > with the exact same size (via padding) as the partition, as opposed to
> > creating the jffs2 image with some size that's less than the partition
> > size?
>
> Not generally, no.
>
> If you use the 'cleanmarker' option then it'll prevent the kernel from
> erasing the remaining blocks on the first mount, and with some
> bootloaders you can't define a partition while installing an image which
> is smaller than the total intended size of that partition -- so you had
> to pad with 0xFF to avoid writing crap to the end of it.
In my experience, better always use images of the same size as the
partition.
You don't *have* to, but then some will figure out how to not erase
the partition, write the image to it, remount the partition and find
some old data in the filesystem that was supposed to be erased.
Give people the option to shoot themselves in the foot and eventually
someone will do it - and blame you. ;)
Jörn
--
When you close your hand, you own nothing. When you open it up, you
own the whole world.
-- Li Mu Bai in Tiger & Dragon
next prev parent reply other threads:[~2003-04-02 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 13:06 reach of jffs2 within image vs. partition John Burch
2003-04-02 13:11 ` David Woodhouse
2003-04-02 13:41 ` John Burch
2003-04-02 13:44 ` David Woodhouse
2003-04-02 14:03 ` Jörn Engel [this message]
2003-04-02 14:04 ` David Woodhouse
2003-04-02 14:13 ` Thomas Gleixner
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=20030402140304.GA752@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dwmw2@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