Hi Artem,
Thanks for the taking the time to answer.
On Fri, Nov 30, 2012 at 8:08 AM, Artem Bityutskiy wrote:
>
>> I don't know how many ubi volumes a user typically creates, but I
>> expect not to be too many.
>
> I think I saw something like 8-10 in some peoples' reports.
>
Mmm, that's more th
On Wed, 2012-11-21 at 11:00 +0100, Thomas Petazzoni wrote:
> While I think the original ubiblk that was read-only made sense to
> allow the usage of read-only filesystems like squashfs, I am not sure
> a
> read/write ubiblock is useful.
>
> Using a standard block read/write filesystem on top of ub
Hi, without the reveiw, I can say that overall this sounds good, thanks!
On Tue, 2012-11-20 at 19:39 -0300, Ezequiel Garcia wrote:
> Also, I've decided to make block devices get automatically created for
> each ubi volume present.
> This has been done to match gluebi behavior of automatically crea
Hi Thomas,
On Wed, Nov 21, 2012 at 7:00 AM, Thomas Petazzoni
wrote:
> Dear Ezequiel Garcia,
>
> On Tue, 20 Nov 2012 19:39:38 -0300, Ezequiel Garcia wrote:
>
>> * Read/write support
>>
>> Yes, this implementation supports read/write access.
>
> While I think the original ubiblk that was read-only
Dear Ezequiel Garcia,
On Tue, 20 Nov 2012 19:39:38 -0300, Ezequiel Garcia wrote:
> * Read/write support
>
> Yes, this implementation supports read/write access.
While I think the original ubiblk that was read-only made sense to
allow the usage of read-only filesystems like squashfs, I am not su
Hi,
I'm happy to announce we finally have a read/write ubiblock implementation!
What follows are some historical notes and some implementation hints.
Feel free to comment on anything, ask questions or provide feedback.
You can even fire some flames if you like, my asbestos suite works just fine ;
6 matches
Mail list logo
