Displaying 4 results from an estimated 4 matches for "idenfify".
2016 Mar 08
5
Module Versioning
...omised version would likely
break too.) I'm not sure if the config file is more portable between
syslinux versions than modules but I guess it would be so for this keeping
fewer versions could be enough.
I was also thinking about storing hashes of files that you have modules
for and try to idenfify the version by comparing the hashes instead of
trying to extract a version number from the binary, but this may be
problematic as well because building with different compilers will result
in different hashes and you don't know what was used by those created the
iso.
I don't see a way...
2016 Mar 08
0
Module Versioning
...gt; break too.) I'm not sure if the config file is more portable between
> syslinux versions than modules but I guess it would be so for this keeping
> fewer versions could be enough.
>
> I was also thinking about storing hashes of files that you have modules
> for and try to idenfify the version by comparing the hashes instead of
> trying to extract a version number from the binary, but this may be
> problematic as well because building with different compilers will result
> in different hashes and you don't know what was used by those created the
> iso.
>...
2016 Mar 08
0
Module Versioning... and other things
...not quite. My
experience so far has been that replacing 'ldlinux.sys' by the closest
official Syslinux version always works and I haven't seen a single case,
so far, where it didn't.
> I was also thinking about storing hashes of files that you have modules
> for and try to idenfify the version by comparing the hashes instead of
> trying to extract a version number from the binary, but this may be
> problematic as well because building with different compilers will
> result in different hashes and you don't know what was used by those
> created the iso.
I thou...
2016 Mar 07
2
Module Versioning
On Mon, 7 Mar 2016, Pete Batard via Syslinux wrote:
> On 2016.03.07 17:55, Ferenc W?gner wrote:
>> Why not install instead an arbitrary version of Syslinux and replace all
>> .c32 files with the modules of the installed version?
>
> I mentioned that in my previous mail. But I reckon it was easy to miss
> as that mail was rather long:
>
>
> "One solution to