<div>Thank you Fredrik. Now i have understood your advice. But, why isn't the hook called updatebase.SQUEEZE_X86 instead</div>
<div>of updatebase.DEFAULT?<br><br></div>
<div class="gmail_quote">2010/11/27 mamadou diop <span dir="ltr"><<a href="mailto:diopmodou8@gmail.com">diopmodou8@gmail.com</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>Hi Thomas,</div>
<div> </div>
<div>I haven't done any interaction with my email. It is sent automatically. Please, tell me what to do</div>
<div>if i don't want to cite the whole email.<br><br></div>
<div class="gmail_quote">2010/11/26 Fredrik Eriksson <span dir="ltr"><<a href="mailto:fredrik.eriksson@axis.com" target="_blank">fredrik.eriksson@axis.com</a>></span>
<div>
<div></div>
<div class="h5"><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>mamadou diop wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Hi Frederik,<br> In the FAI guide, it is said to adjust the sources.list file after placing the base.tgz in the basefiles/ directory.<br>
There are two sources.list files : one in the /etc/fai/apt and another in the base.tgz. Which one of them needs<br>to be adjusted.<br></blockquote></div>What exactly are you trying to do?<br><br>As I understand it you want to be able to "simultaneously" install clients with different (Debian?) releasees, without having to reconfigure anything at the FAI server every time you want to install another release that is.<br>
If this is the case it is very possible indeed. We install both 32bit and 64bit Lenny and Squeeze.<br><br>To be able to do this we have two different fai-nfsroots, one for Lenny and one for Squeeze (both 64bit since all our machines have 64bit CPUs). They have two separate /etc configdirs with apt/sources.list corresponding to each release, you use the -C flag with make-fai-nfsroot(8) to define your configdir and the -B flag to define the name (and location) och your base.tar.gz.<br>
We have four base files, one for each flavour - 32bit or 64bit Lenny or Squeeze. As a side note we now build them with pbuilder --create and maintain them with a pbuilder --update cronjob. This makes them larger than the ones we used to build with fai-make-nfsroot, but thats fine since we keep them updated and our network is fast. It actually speeds up the installation process. It is a fine tool, pbuilder.<br>
<br>To get the right sources.list for each installation we use the method i described in the previous message.<br><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">2010/11/23 Fredrik Eriksson <<a href="mailto:fredrik.eriksson@axis.com" target="_blank">fredrik.eriksson@axis.com</a> <mailto:<a href="mailto:fredrik.eriksson@axis.com" target="_blank">fredrik.eriksson@axis.com</a>>>
<div><br><br> mamadou diop wrote:<br><br> Because of the sources.list file which only points to a Debian<br> release at a given time, it seems to me<br> that it is impossible to install simultaneously Debian clients<br>
with differents releases. Is my opinion true?<br><br> We actually have this in our current testing environment.<br> What you typically want is to have two files in your fai/config/<br> tree, a sources.list file and a hook script (at least this is how<br>
we solve it). The sources.list file should be named after a class,<br> where you for example define what distribution to run, and be put<br> in fai/config/files/etc/apt/sources.list/, i.e<br> fai/config/files/etc/apt/sources.list/LENNY_AMD64.<br>
As for the hook script ours is called<br> fai/config/hooks/updatebase.DEFAULT and is a small shell script to<br> say the least:<br><br> #! /bin/bash<br><br> fcopy -Bi /etc/apt/sources.list<br><br> What it does is that it takes the file based on your defined<br>
class, for example<br> fai/config/files/etc/apt/sources.list/SQUEEZE_X86, and copy it to<br> /etc/apt/sources.list on your target system. Thus you can have<br> multiple sources.list files aimed at different releases (and<br>
distributions or architectures if needed).<br><br></div></blockquote><br>Regards<br>--<br><font color="#888888">Fredrik<br></font></blockquote></div></div></div><br></blockquote></div><br>