Bug#354344: [Buildd-tools-devel] Bug#354344: Fix in 354344 breaks plain chroots

[Roger Leigh]

"Steve M. Robbins" <steven.robbins at videotron.ca> writes:

> The new "directory" type completely satisfies my need.
> Thanks very much indeed for this.

Great.

> On Sun, Jul 09, 2006 at 09:51:08PM +0100, Roger Leigh wrote:
>
>> Something like:
>> 
>> setup-options=check,mount,network,chrootname,sbuild
>> exec-options=check
>> 
>> would enable all the standard scripts, and be extensible for
>> additional scripts.  However, I would like it to be easier to disable
>> individual scripts, e.g.
>> 
>> setup-options=no-network
>> 
>> to allow all but the networking setup.
>> 
>> Any suggestions or thoughts here would be great.
>
> This sounds like a good idea.  
>
> Thinking about this reminds me that I never did understand the
> distinction being made between "setup" and "exec" scripts.  The man
> page schroot.conf does not enlighten me, and schroot ships with only
> one exec script (00check) that just logs info and looks basically like
> a debugging aid (it looks like it was derived from setup.d/00check, or
> vice-versa).

Yes.  What happens is that the setup scripts are run during chroot
setup and cleanup, and exec scripts are run before and after each
command you execute in the chroot.  There are currently no exec
scripts in existence; I created them in anticipation of having e.g. a
Xen chroot type, which might require setting up an SSH connection to
access the chroot, for example.  In this case the setup scripts would
create and boot a Xen host, and then shut down and destroy it, and the
exec scripts would disconnect and reconnect to the running instance.
That's the idea, anyway--until Xen runs on 32-bit powerpc, and is in
the mainline kernel, I'm not able to add support for it.

Both the setup and exec scripts are also intended to be used by users
for whatever purpose they like, so while there's no exec scripts "out
of the box", it's trivial to add your own should you wish to.

> Earlier in the thread, I mooted an option to toggle mounting:
>
>> >> > So: rather than a new chroot type, why not introduce a new option, say
>> >> > "auto-mount", for this?
>
> This seems to me completely unnecessary if "setup-options" is
> implemented.

It is as long as each script remains single-purpose.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please sign and encrypt your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20060727/b72d81bb/attachment.pgp