[syslinux] The "core32" development branch
Jeffrey Hutzelman
jhutz at cmu.edu
Wed May 20 07:17:30 PDT 2009
--On Tuesday, May 19, 2009 11:19:09 PM +0200 Dag Wieers <dag at wieers.com>
wrote:
> Well, a small look at the list below makes it quite obvious why I think
> NASM <= 2.x might be important.
>
> Works currently on:
>
> RHEL5: nasm-0.98.39-3.2.2 end-of-life on 31/mar/2014
> RHEL4: nasm-0.98.38-3.EL4 end-of-life on 29/feb/2012
> RHEL3: nasm-0.98.35-3.EL3 end-of-life on 31/oct/2010
> RH9: nasm-0.98.35-3 end-of-life now
>
> Fails already on:
>
> RH7: nasm-0.98.22-2 end-of-life now
> RHEL2: nasm-0.98-8.EL21 end-of-life on 31/may/2009
>
> We use syslinux to generate new bootable ISO images on the fly with
> thousands of system's boot parameters hardcoded (not being able to use
> PXE can be hard :-))
>
> Being able to use a new syslinux on normal Enterprise Linux servers is
> certainly a plus. I can only hope that RHEL6 will have a newer nasm by
> default, but RHEL5 will be around for some time before RHEL6 becomes an
> acceptable solution for a lot of companies.
Our computing environment is based largely on Fedora, though we support
systems as old as RH9. However, it's not necessary to be able to build
syslinux on every one of those machines; it should only have to be built
once, or at least only in one place.
F7 comes with nasm-0.98.39, though there may be something newer in updates.
F10 comes with nasm-2.03.01, so I would not be surprised to see something
of that vintage in RHEL6.
-- Jeff
More information about the Syslinux
mailing list