hulselmansgert at gmail.com
Tue Nov 13 00:53:15 PST 2012
2012/11/13 H. Peter Anvin <hpa at zytor.com>:
> On 11/01/2012 03:17 PM, Matt Fleming wrote:
>> On Thu, 2012-11-01 at 19:35 +0100, Bernd Blaauw wrote:
>>> Your mentioning of hugely increased disk sizes for each binary isn't
>>> that positive either in deciding to switch or not, as I sometimes add
>>> syslinux to bootdisks.
>> All the .c32 files together in the 5.00-pre9 release amount to 150M. In
>> 4.06 they're 105M. We're not talking about a huge increase here, since
>> you're unlikely to include *all* the .c32 modules.
>>> If files are getting quite a larger disk-size anyway it might be easier
>>> for non-CD to stick to using some version of GRUB.
>> We're not talking megabytes here. No file is over 736KB and that's
>> libcom32.c32, the biggest file in the release. New features are
>> obviously going to result in bigger object files.
> Although right now the .c32 files are not compressed, whereas ldlinux.sys is
> and was. I am thinking we should compress the .c32 files.
> H. Peter Anvin, Intel Open Source Technology Center
> I work for Intel. I don't speak on their behalf.
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> Please do not send private replies to mailing list traffic.
What about stripping the com32 modules?
libutil_com.c32: 742702 bytes
libutil_com.c32: 184200 bytes
After gzipping (742702):
libutil_com.c32: 295270 bytes
Or is the debug information needed by Syslinux?
More information about the Syslinux