bind-mounting files in mock

[Jeremy Katz]

On Friday, March 27 2009, Jesse Keating said:
> On Fri, 2009-03-27 at 10:37 -0500, Clark Williams wrote:
> > It's not described in the man page, so I'm a bit leery about depending
> > on that behavior. That being said, it's not a normal use-case for mock
> > builds, so it'll probably only bite the livecd creation stuff it the
> > bind-mount behavior changes. 
> > 
> > Ok, I'll pull it in for the next release.
> 
> I need that functionality too when building install images.  Rather than
> see more and different code paths when chroot generating, I think there
> would be some value in using the same code path regardless of how the
> chroot is used.  I think the bind mounting of dev/ is only there for the
> loop entries, I don't know of any other mock consumers that require a
> real /dev/ tree.  We might consider just always file bind mounting a few
> loop entries in and only having one code path.

You can't really just do a few as you may need however many there are on
the real system.  If the idea is to make them by default it's probably
better to just make n of them based on the host.  But then the chroot
does have a way of affecting outside of it :/

Jeremy