[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101215011904.GA24292@falooley.org>
Date: Tue, 14 Dec 2010 17:19:05 -0800
From: Jason Lunz <lunz@....org>
To: Rob Landley <rob@...dley.net>
Cc: dedekind1@...il.com,
richard -rw- weinberger <richard.weinberger@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
David Woodhouse <dwmw2@...radead.org>,
atom ota <atomota@...epyhammer.com>,
user-mode-linux-devel@...ts.sourceforge.net,
Jeff Dike <jdike@...toit.com>,
lkml <linux-kernel@...r.kernel.org>,
linux-mtd@...ts.infradead.org
Subject: Re: [PATCH] mtd: allow mtd and jffs2 when ARCH=um
On Tue, Dec 14, 2010 at 06:49:02PM -0600, Rob Landley wrote:
> The problem is that jffs2 is a filesystem, and thus something people would
> really like to be able to loopback mount, but it's hardwired to assume it's
> only ever stored on a certain type of hardware, and thus requies incestuous
> knowledge of the erase granularity of the flash layer in order to function.
I assume you can turn your jffs2 image file into a block dev using
losetup, then turn the corresponding loop device into an mtd device
using block2mtd, at which point you ought to be able to mount it with
jffs2. I've never tried it.
> What any of this has to do with UML is an open question. I don't want to
> require UML to loopback mount a jffs2 image, I want to be able to do it from my
> host. From my perspective, you're solving the wrong problem.
There's more than just loopback-mounting jffs2 images. I use this to
make entire uml+jffs2 virtual machines for testing purposes.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists