search for: syslinux_

...t very well-thought reasoning. In the particular case of "padsize" vs. "maxsize" (options / parameters of the Perl script), there used to be a separate use of them. Although there _seems_ to be no use for having both of them simultaneously at this time _for a normal build of Syslinux_, we cannot discard / disregard the possibility that some script in some distro might want to take advantage of each of them independently, especially for some debugging situation (e.g. some buggy / old BIOS). Another potential (hypothetical) use-case might be some "bootable USB tool"...

...> In the particular case of "padsize" vs. "maxsize" (options / parameters > > of the Perl script), there used to be a separate use of them. Although > > there _seems_ to be no use for having both of them simultaneously at > > this time _for a normal build of Syslinux_, we cannot discard / > > disregard the possibility that some script in some distro might want to > > take advantage of each of them independently, especially for some > > debugging situation (e.g. some buggy / old BIOS). > > > > Another potential (hypothetical) use-cas...

...of "padsize" vs. "maxsize" (options / parameters > >> > of the Perl script), there used to be a separate use of them. Although > >> > there _seems_ to be no use for having both of them simultaneously at > >> > this time _for a normal build of Syslinux_, we cannot discard / > >> > disregard the possibility that some script in some distro might want to > >> > take advantage of each of them independently, especially for some > >> > debugging situation (e.g. some buggy / old BIOS). > >> > > >>...

...particular case of "padsize" vs. "maxsize" (options / parameters >> > of the Perl script), there used to be a separate use of them. Although >> > there _seems_ to be no use for having both of them simultaneously at >> > this time _for a normal build of Syslinux_, we cannot discard / >> > disregard the possibility that some script in some distro might want to >> > take advantage of each of them independently, especially for some >> > debugging situation (e.g. some buggy / old BIOS). >> > >> > Another potential (h...

...>> >> > parameters >> >> > of the Perl script), there used to be a separate use of them. >> >> > Although >> >> > there _seems_ to be no use for having both of them simultaneously at >> >> > this time _for a normal build of Syslinux_, we cannot discard / >> >> > disregard the possibility that some script in some distro might want >> >> > to >> >> > take advantage of each of them independently, especially for some >> >> > debugging situation (e.g. some buggy / old BIOS)...

...ith it. > > In the particular case of "padsize" vs. "maxsize" (options / parameters > of the Perl script), there used to be a separate use of them. Although > there _seems_ to be no use for having both of them simultaneously at > this time _for a normal build of Syslinux_, we cannot discard / > disregard the possibility that some script in some distro might want to > take advantage of each of them independently, especially for some > debugging situation (e.g. some buggy / old BIOS). > > Another potential (hypothetical) use-case might be some "boo...

- Remove padsize argument as it is never used. - Add an usage printed when $file is not set or --help, -h is the first argument. - Add basic tests for this script. --- mbr/checksize.pl | 27 ++++++++++++++++++--------- mbr/checksize_test.sh | 22 ++++++++++++++++++++++ 2 files changed, 40 insertions(+), 9 deletions(-) create mode 100644 mbr/checksize_test.sh diff --git a/mbr/checksize.pl