[syslinux] Syslinux 5.00 released

[Ady]

> On 12/07/2012 01:08 PM, Shao Miller wrote:
> > On 12/7/2012 15:59, H. Peter Anvin wrote:
> >> Actually, I'm thinking of maybe using a
> >> different extension than .c32 for library modules might be a good idea,
> >> to distinguish them from executable modules.
> > 
> > Not that anyone has asked me for suggestions, but here are some :)
> > 
> >   .lxo (sysLinuX Object code)
> >   .slx (SysLinuX something)
> >   .lxb (sysLinuX Binary)
> >   .cbl (ComBoot Library)
> >   .hpa ;)
> > 
> 
> I was kind of thinking .clb (comboot library).
> 
> 	-hpa
> 

I don't see the point in adding yet another file name extension. As 
users, we don't need to associate it to any program. The only 
reference to "shared objects" is between developers, and the amount 
of files is so small (only six at this moment) that every Syslinux 
developer would know which specific files they are talking about. If 
it is about documentation, I would suggest to just list those 6 files 
and move on.

For the purpose of searching those specific files, at this moment it 
is really easy. Just search for ldlinux.c32 and lib*.c32.


For those asking about the new "usage dependencies" in Syslinux 
5.00...

The required files, as of 5.00, are as follows.

For any Syslinux variant, like isolinux.bin for example, add 
"ldlinux.c32" too if the relevant installer doesn't add it 
automatically (or if an installer doesn't exist).

The following is a list gathered from Syslinux 5.00 using the "ldd" 
command under Linux.

(Note: use a monospaced font for clarity.)

advdump.c32:      statically linked
cat.c32:          statically linked
chain.c32:        libutil_com.c32
                  libcom32.c32
cmd.c32:          libcom32.c32
config.c32:       libcom32.c32
cpuid.c32:        statically linked
cpuidtest.c32:    libcom32gpl.c32
disk.c32:         libcom32gpl.c32
dmitest.c32:      libcom32gpl.c32
elf.c32:          libcom32.c32
entrydump.c32:    statically linked
ethersel.c32:     libcom32.c32
fancyhello.c32:   libutil_com.c32
gfxboot.c32:      libcom32.c32
gpxecmd.c32:      libcom32.c32
hdt.c32:          libutil_com.c32
                  libcom32gpl.c32
                  libcom32.c32
                  libmenu.c32
hello.c32:        statically linked
hexdump.c32:      libcom32.c32
host.c32:         libcom32.c32
ifcpu.c32:        libutil_com.c32
                  libcom32gpl.c32
                  libcom32.c32
ifcpu64.c32:      libcom32.c32
ifmemdsk.c32:     libcom32.c32
ifplop.c32:       libcom32.c32
kbdmap.c32:       libcom32.c32
keytest.c32:      libutil_com.c32
kontron_wdt.c32:  libcom32.c32
ldlinux.c32:      statically linked
libcom32.c32:     statically linked
libcom32gpl.c32:  statically linked
liblua.c32:       statically linked
libmenu.c32:      libutil_com.c32
                  libcom32.c32
libutil_com.c32:  statically linked
linux.c32:        libcom32.c32
localboot.c32:    libcom32.c32
ls.c32:           statically linked
lua.c32:          liblua.c32
                  libcom32gpl.c32
                  libcom32.c32
mboot.c32:        libcom32.c32
meminfo.c32:      statically linked
menu.c32:         libutil_com.c32
pcitest.c32:      libcom32.c32
pmload.c32:       libcom32.c32
prdhcp.c32:       libutil_com.c32
                  libcom32.c32
pwd.c32:          statically linked
pxechn.c32:       libutil_com.c32
                  libcom32.c32
reboot.c32:       libcom32.c32
resolv.c32:       statically linked
rosh.c32:         libutil_com.c32
                  libcom32.c32
sanboot.c32:      libcom32.c32
sdi.c32:          libcom32.c32
serialinfo.c32:   statically linked
sysdump.c32:      libcom32.c32
vesainfo.c32:     statically linked
vesamenu.c32:     libutil_com.c32
                  libcom32.c32
vpdtest.c32:      libcom32gpl.c32
whichsys.c32:     libcom32.c32
zzjson.c32:       libcom32gpl.c32

The new PATH directive is used in the cfg files to point to the 
location of the lib*.c32 files, just in case that location is not the 
"Current Working Directory".

HTH,
Ady.