FAI 2.4 upgrade problems

[Felix Kühling]

Great news! I finally managed to finish an installation with FAI 2.4 and
boot the installed computer. More details below.

Once I had solved my previous problems I got a new one. The installed
system rebooted instead of loading a kernel. To make it short, as of FAI
2.4 you have to add class MBR if you use the classes BOOT and LILO and
want to boot from the master boot record. This should be added to the
changelog.

On Thu, 27 Feb 2003 11:29:27 +0100
Felix Kühling <fxkuehl at gmx.de> wrote:

> On Wed, 26 Feb 2003 14:12:19 -0600
> Justin Doiel <jdoiel at engr.uark.edu> wrote:
> 
[snip]
> > > 3. The logfiles cannot be saved on the install server. I get two error
> > > messages about rcmd problems. Sorry, I forgot the exact words. Maybe
> > > this is related to the next one.

It was. After solving problem 4 I got logfiles as usual.

[snip]
> > > 4. The DHCP information doesn't make it into environment variables. I
> > > tried the dhclient -lf /dev/null command line as in get-boot-info
> > > manually in the shell, but it didn't output anything to stdout. If I
> > > understand get-boot-info correctly dhclient is *supposed* to output
> > > variable definitions for all DHCP parameters. They are redirected to
> > > /tmp/fai/bootlog and sourced later by task_confdir.
> > > 
> > 
> > dont have that problem here. :P
> 
> Do you use DHCP or BOOTP? After reading a few scripts and manpages I
> have an idea what the problem could be. I saw a dhclient-perl script in
> .../nfsroot/sbin which seems to translate dhcp options into shell
> variables. It gets called by dhclient through /sbin/dhclient-script. But
> there is this line which makes me worry:
> 
> # exit if no data is available
> exit 0 unless $ENV{new_option_170};
> 
> As suggested in the new documentation I had removed the option_17x
> options from my dhcpd.conf and used the new FAI_LOCATION variable in
> fai.conf and class/LAST.var for setting FAI_ACTION. But here it looks as
> if at least option_170 is still needed. Is this a bug in the script or
> the documentation?
> 
> I havn't tested this theory yet. Maybe later today. I'll let you know
> what I find.

Ok. After adding option-170 back to dhcpd.conf it works. But this
definitely contradicts the changelog that was sent to this list:
<quote>
    - FAI_LOCATION is now defined in fai.conf, FAI_ACTION is defined
      in LAST.var, do not use T170 and T171 via a BOOTP or DHCP server
      ( but it;s still possible)
</quote>

I'd say it's still necessary :-P

Best regards,
  Felix

               __\|/__    ___     ___     ___
__Tschüß_______\_6 6_/___/__ \___/__ \___/___\___You can do anything,___
_____Felix_______\Ä/\ \_____\ \_____\ \______U___just not everything____
  fxkuehl at gmx.de    >o<__/   \___/   \___/        at the same time!