[Rpm-maint] [PATCH] Use private environment on EINVAL error code for JFFS2

2012-04-24 Thread Daniel Drake
JFFS2 is an embedded filesystem used by the OLPC XO-1. It does not support writable mmap. When opening a non-private environment, libdb uses a writable disk-backed mmap, even if the DB_NOMMAP flag is passed. This fails with EINVAL on JFFS2. Detect the EINVAL condition and fall back to a private e

Re: [Rpm-maint] [PATCH] Use private environment on EINVAL error code for JFFS2

2012-05-03 Thread Panu Matilainen
On 04/24/2012 06:41 PM, Daniel Drake wrote: JFFS2 is an embedded filesystem used by the OLPC XO-1. It does not support writable mmap. When opening a non-private environment, libdb uses a writable disk-backed mmap, even if the DB_NOMMAP flag is passed. This fails with EINVAL on JFFS2. Detect the

Re: [Rpm-maint] [PATCH] Use private environment on EINVAL error code for JFFS2

2012-05-03 Thread Daniel Drake
On Thu, May 3, 2012 at 8:04 AM, Panu Matilainen wrote: > I applied a slightly different version that only falls back to DB_PRIVATE on > system level errors to differentiate from the BDB-level logical errors (like > invalid/incompatible flags): > > http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=58c