On Thu, May 10, 2012 at 7:40 AM, David Zeuthen wrote:
> I think udisks2's UDisksMountMonitor is just making a couple of
> assumptions it probably shouldn't be making ... and you are probably
> the first to run into them since you are using bind mounts. It's
> easier to deal with this in bugzilla,
Hey,
On Wed, May 9, 2012 at 8:38 PM, Daniel Drake wrote:
> Could these behaviour points be adapted in the interest of finding a
> real solution here, or is this regarded as a corner case which I
> should use the well-documented udev override for?
I think udisks2's UDisksMountMonitor is just maki
Hi,
OLPC runs / as a bind-mount, because the "real" partition
(/dev/mmcblk0p2) holding our root fs can actually hold different
versions of the software (usually with a huge amount of shared data
via hard links). We use this to implement a completely safe atomic
system upgrade path, where a symlink
