Re: post-install-fix.sh (pr05)

[Andreas Schockenhoff <asc@gmx.li>]

Hi, 
On Thursday 06 October 2005 12:22, Jonas Smedegaard wrote:
> > The other suggestion stems from Andreas Schockenhoff, and goes like
> > this:
> >
> > "Alas, pxe-enabled etherboots can not be detected from old ones by
> > means of the pxe-string. But you can help yourself by means of the
> > etherboot version number. Of course it is better, to move entirely
> > to pxe:
> >
> >  filename      "/var/lib/tftpboot/pxelinux.0"; # Menu Test
> >  if substring (option vendor-class-identifier, 0, 13) =
> > "Etherboot-5.2" {
> >    filename      "/tftpboot/lts/vmlinuz-2.4.19";
> >  }
> >  if substring (option vendor-class-identifier, 0, 13) =
> > "Etherboot-5.0" {
> >    filename      "/tftpboot/lts/vmlinuz-2.4.19";
> >  }
> >  # etc. "
> >
> > Now, again the question: can anybody with access to SVN edit these
> > lines in dhcpd.conf?
>
> Do you need an exception for Etherboot 5.2 and 5.0 that you do not
> for, say, 5.1 or 5.3?
>
> If not then don't look for 13 characters but only 9 and match them
> against "Etherboot".
The problem is that PXE enabled Etherboot does not say that he can 
PXE. :-( But the newer releases from Etherboot send the string 
"Etherboot-5.4". This String do not match also all newer releases.

So I make a exception for the last 2 production versions from Etherboot. 
Of course all older or development versions need the same fix, but I 
think that nobody should use them anymore. :-)

bye Andreas