[Replying to both, thanks for your feedback!] * Michael Tautschnig <[EMAIL PROTECTED]> [20070927 00:06]: > > Any suggestions what could be the best solution for this? Does a > > patch which would allow disabling need for FAI_CONFIG_SRC sound > > reasonable to you? Or would an option "chrootupdate" (which justs > > makes sure the packages inside the chroot are up2date and executes > > the according config/scripts/$CLASS/* stuff and so on) make more > > sense?
> AFAIK there was already some discussion in the IRC channel on this one, but I > still consider your request self-contradictory. How would you want to execute > config/scripts/$CLASS/* if there is no configuration, i.e., there _is no_ > config/ directory... * Henning Sprang <[EMAIL PROTECTED]> [20070927 00:11]: > Michael Prokop wrote: > > Any suggestions what could be the best solution for this? Does a > > patch which would allow disabling need for FAI_CONFIG_SRC sound > > reasonable to you? > Generally sounds desireable to make softupdate in a chroot, and in some > cases even without having to use nfs/svn/... > But you always need a configspace _somewhere_ - otherwise I don't see > how softupdate can run. > If (not sure if it already does) FAI_CONFIG_SRC supports a simple > file:// URL, you can bind-mount the configspace from the main system > into the chroot and run softupdate inside. > softupdate anyway places the configspace somewhere in the system to be > updated, so we maybe only need to skip the fetching in that case. > > Or would an option "chrootupdate" (which justs > > makes sure the packages inside the chroot are up2date and executes > > the according config/scripts/$CLASS/* stuff and so on) make more > > sense? > This could be a shortcut for something like > mount -o bind /srv/fai/config /path/to/chroot/var/lib/fai/config > (guess the latter is where the configspace is stored temporarily) > chroot /path/to/chroot fai -N softupdate As discussed on IRC FAI_CONFIG_SRC is pretty close to FAI_CONFIGDIR. I'll check this out in practice and will try to provide according documentation then. Thanks for your feedback. regards, -mika-
signature.asc
Description: Digital signature
