Re: Strange error w/ fai-mirror
[...] /srv/fai/mirror/dists/etch/main/binary-i386/Packages /srv/fai/mirror/dists/etch/main/binary-amd64/Packages I use this machine to do fai installations for both 32bit and 64bit machines. Originally I set things up on original machines and copied them over. I was hoping to make things work on a single machine without having to set things up on two different machines. For a workaround i'll continue to do things on separate machines (a 32bit and a 64bit) and copy the results over to my server unless anyone has a better suggestion? Hmm, for the fix: It probably suffices to choose different mirror directories rather than different machines, but that's up to you. To really fix it please file a bug with the Debian BTS to get this issue solved as soon as possible, it probably doesn't even take too much effort. Best, Michael pgpR2NpVvjgcS.pgp Description: PGP signature
Re: Strange error w/ fai-mirror
Michael Tautschnig wrote: [snip] Hmm, for the fix: It probably suffices to choose different mirror directories rather than different machines, but that's up to you. Well, its funny you mention that. I do have two different mirror directories. I have a /srv/fai/mirror and a /srv/fai/mirror64. I'm honestly not sure how /srv/fai/mirror ended up containing both arches in it. Before when i had done things, I had noticed that various fai scripts would detect my architecture and download accordingly. For example, I can't make an nfsroot for a 32bit machine on the 64 bit machine, at least I don't know how. What I had tried this time was to fake it out using debian's linux32 package and running the command: #linux32 fai-mirror /srv/fai/mirror Where /srv/fai/mirror is a completely empty directory (i run an rm -rf /srv/fai/mirror/* before hand). Granted my package_config/DEFAULT contains packages for both i386 and amd64, I assumed (or hoped) that it would detect the architecture and build the appropriate mirror. It appears to have attempted to build mirrors for both archs and then failed right at the end, but I haven't read into the script enough to really understand what's going on, which would be my next step. To really fix it please file a bug with the Debian BTS to get this issue solved as soon as possible, it probably doesn't even take too much effort. For this bug I would report that fai-mirror fails when detecting two archs in a mirror? That seems like one bug (i.e. better error message). I also think I'm going to read into this a little more (when i have time) to see if I can figure out why fai-mirror is populating /srv/fai/mirror with more than one arch or would that type of investigation be generally discouraged? (I'm a bit new to open source and contributing to projects, but would like to help more if i could) Thanks for your help, Carl -- Carl J. Van Arsdall [EMAIL PROTECTED] Build and Release MontaVista Software
Re: Define FAI_CONFIG_SRC from dhcp info
Thomas Lange a écrit : On Tue, 06 Feb 2007 19:52:25 +0100, Nicolas Courtel [EMAIL PROTECTED] said: My FAI server (version 3.1.6 for Etch) is connected to several networks, and has a different name on each network. I have configured the DHCP server so that it sends the appropriate name on each interface, and would like to do the same thing for the FAI_CONFIG_SRC variable : I'm looking for an FAI variable which would be set using the server-name dhcp variable, and could be used as the NFS server in FAI_CONFIG_SRC. Have a look at dhclient-perl. There you see that the DHCP vendor option 170 are mapped to FAI_CONFIG_SRC. option_170 FAI_CONFIG_SRC So you should use this in dhcpd.conf option option-170 nfs://faiserver/usr/local/share/fai; # FAI_CONFIG_SRC But I never tested this. Well, it works fine, almost out of the box. As dhclient-perl also defines an fai_config_src variable, I have declared it both in dhcpd.conf and dhclient-fai.conf, and FAI_CONFIG_SRC is now set to the appropriate value after a PXE boot. In dhcpd.conf, in general options: option fai_config_src code 170 = text; and then for each subnet: option fai_config_src nfs://subnet-faiserver/usr/local/share/fai/config; # FAI_CONFIG_SRC In dhclient-fai.conf: option fai_config_src code 170 = text; and add fai_config_src to the request list And in dhclient-perl, also added fai_config_src to @list. BTW. Maybe you like to update your FAI questionnaire from 2004 and sent it back to me. Surprisingly enough, my 2 year-old questionnaire is out-of-date :-) ; I will do so pretty soon. Thanks for your help, -- Nicolas
