Rudy Gevaert wrote:
Henning Glawe wrote:
On Wed, Sep 12, 2007 at 06:14:26PM +0200, Michael Tautschnig wrote:
[...]
I think it works the following way: put your code in a script
$NFSROOT/$FAI/hooks/confdir.DEFAULT, where $NFSROOT and $FAI are
set in
make-fai-nfsroot.conf and fai.conf, respectively.
I'll try this out tomorrow. I now have my FAI pulling the config
space from a svn repository.
Just to make sure we get this right: That hooks/ directory will later be
effectively overwritten by the SVN checkout and well, hmm, I'm not
even sure one
gets to see the hook at all as it must be made available within
tmpfs. @Thomas:
Could you maybe comment on this one?
I am using a quite ugly hack:
---- in /etc/fai/fai.conf ----
[...]
if [ -d "/etc/fai/hooks" ]; then
FAI=/etc/fai
fi
[...]
---- in /etc/fai/hooks/confdir.DEFAULT.source ----
[...]
get_the_config
FAI=the_real_fai_config_path
[...]
Thanks this seems to work.
In some old scripts I was still using /fai/files/...as location of my
config space. I first changed that to use FAI_CONFIGDIR but that is now
empty because I'm using a checkout.
I can't use FAI_CONFIG_SRC as that is svn+ssh://blablaba. I can reset
FAI_CONFIGDIR to the correct dir in my hook (see above).
However I do think that if using subversion FAI_CONFIGDIR should contain
the path to the checked out sources.
Is this a bug?
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert [EMAIL PROTECTED] tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep Systemen Systems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
