On Mon, Jul 03, 2006 at 11:10:46PM +0100, Roger Leigh wrote: > "Steve M. Robbins" <[EMAIL PROTECTED]> writes:
> > In short, you disabled mounting /home when using a plain type > > of chroot. Clearly this is deliberate. How may I obtain the > > original behaviour? > > The "plain" type was never intended to do all the automatic mounts; > that was a workaround for the missing --rbind support. Now --rbind is > supported, you can just mount them under the chroot location (e.g. in > /etc/fstab) and --rbind will rebind them all under the session mount > location when you start a session. Ah. I didn't realise that. > Because the automatic mounting is being used by a few people, and it > is a convenient way to do things, I'm going to introduce a new chroot > type which will be "plain+mounts". Doesn't that leave you open to someone requesting both "file" and "file+mounts" chroot types? At the risk of displaying my ignorance of schroot: I'm having a hard time understanding why automatic mounting is deemed always useful for "non-plain" chroots and (currently) deemed not useful for "plain" chroots. As I understand it, the chroot type describes the source of the chroot filesystem. To me, that seems orthogonal to the question of whether you want "/home" mounted. So: rather than a new chroot type, why not introduce a new option, say "auto-mount", for this? Personally, I'd default it to true; but you're the boss. Cheers, -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
