Hi Patrick, > Package: fai-client > Version: 4.0~beta2+experimental26 > > Hi, > > currently FAI uses a fixed/hard-coded location for the base tarball. > This is unfortunate in multi-distribution or multi-arch setups for example. > Currently such setups involve duplication of the fai configuration > directory and the nfsroot, which shouldn't be neccessary (at least > not in all cases). > > So I suggest to add support for new variable FAI_BASEFILE: > This should be as simple as changing task_extrbase in > /usr/lib/fai/subroutines. > Instead of using a hard-coded local basefile and extracting it, if it exists, > and using debootstrap otherwise do something like this: > > - Check if FAI_BASEFILE is defined. In this case check weither it exists > and if yes, use it as basefile. If it is defined but the tarball does > not exist print a warning to STDERR. > - If basefile exists extract it to /target > - If basefile does not exist call debootstrap >
If this is really only about the basefile, then you seem to have missed the bit of the FAI Guide that talks about the config/basebfiles directory. That is, you can create an archive to be unpacked using ftar, name it like the class that you intend to use it for, and put it in your config space in the basefiles/ directory. Does that fix any/all the issues you were facing? Best, Michael
pgpojjSzjSqfs.pgp
Description: PGP signature
