hiya
>> contents of /srv/fai/config/class/01-init.source
>> ---
>> #!/bin/bash
>>
>> TESTVAR="foobar"
>> export TESTVAR
>> ---
> So ... does that work? IMHO it should, but as Michael Goetze said, you
> probably cannot do more than this, like use $TESTVAR in some *.var files
> or somewhere later o
> hiya
> >> Is there a "correct" way to provide variables to scripts in class/ ?
> [...]
>
> > If you name your script 00foobar.source it will be executed first _and_
> > sourced, therefore all variable definitions from 00foobar.source will
> > also be visible in all other scripts. You might need
hiya
>> Is there a "correct" way to provide variables to scripts in class/ ?
[...]
> If you name your script 00foobar.source it will be executed first _and_
> sourced, therefore all variable definitions from 00foobar.source will
> also be visible in all other scripts. You might need to export the
> hiya
>
> > $kernelmodules is the right way to do this, but not in
> > FAIBASE.var. The variable is used in 20-hwdetect.source, which is
> > executed before FAIBASSE.var is sourced. You can just edit your
> > 20-hwdetect.source script and add modules there to $kernelmodules.
>
> Is there a "corr
hiya
> $kernelmodules is the right way to do this, but not in
> FAIBASE.var. The variable is used in 20-hwdetect.source, which is
> executed before FAIBASSE.var is sourced. You can just edit your
> 20-hwdetect.source script and add modules there to $kernelmodules.
Is there a "correct" way to prov
