similar to: Workaround for "hybriding" large ISO images?

Hi, > since the Tails ISO grew from ~900MB to ~1.1GB, we see this warning > when running isohybrid on it: > > isohybrid: Warning: more than 1024 cylinders: 1045 That would be the default cylinder size of 64*32*512 = 1 MiB. Try isohybrid options -h 255 -s 63 to get the maximum cylinder size of a bit less than 8 MiB. This will suffice for ISOs up to nearly 8 GiB. > So, my

Hi, at [Tails] we're in the process of shipping hybrid ISO images by default again. We're using `isohybrid -h 255 -s 63' to do that (thanks to the advice we got on this mailing-list a few months ago!). And then, we've discovered that sometimes, isohybrid produces ISO images whose size is not a multiple of 2048 bytes. Who cares? ... may you ask. Well, apparently, VirtualBox does:

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

> Hi, > > at [Tails] we're in the process of shipping hybrid ISO images by > default again. We're using `isohybrid -h 255 -s 63' to do that (thanks > to the advice we got on this mailing-list a few months ago!). > > And then, we've discovered that sometimes, isohybrid produces ISO > images whose size is not a multiple of 2048 bytes. > > Who cares?

>What I reminder from it: > > The first "isohybrid" was in perl. > But that made perl a run-time dependency. > > A compiled version of "isohybrid" removed that > run-time dependency on perl. > > >What I think of it: > > The Perl variant of isohybrid should be removed > from the source tree. One advantage of the Perl one for me

Hi, [ouch, it take me a year? thank you all for this very interesting thread that I'm going to finish reading now.] Pete Batard via Syslinux: > I'll skip the EFI part of tails (that uses grub/EFI) to talk only > about the BIOS/Syslinux part. JFTR Tails uses GRUB only for 32-bit UEFI. We use syslinux for BIOS and 64-bit UEFI. > So, one thing Rufus will need to do is find a

[I was dropped from cc in the initial response but I'd appreciate if you could keep it this time around since I'm not subscribed to this list. Thanks!] Ady wrote: > I do not know the exact complete procedure that the TAILS team is using > to build the original ISO image, and how it is transformed into an > isohybrid image (there are multiple tools for each, sometimes >

Op 2014-06-21 om 21:19 schreef intrigeri: > Hi, > > Ian Bannerman wrote (21 Jun 2014 15:49:51 GMT) : > > One advantage of the Perl one for me is that I can run it on Windows. > > We at Tails rely on isohybrid.pl for installing on OSX: > https://tails.boum.org/doc/first_steps/installation/manual/mac/ > > Of course, this does not mean that the current syslinux team

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules

Hi, > What about '-h 255 -s 63 , ISO size 1085736960' ? -h 255 -s 63 , ISO size 1085736960 : align_factor= 4 , padding= 0 , image size= 132.000000 cylinders ----------------------------------------------------------------- Code of isohybrid_test_mockup.c : ----------------------------------------------------------------- #include <stdlib.h> #include <stdio.h> int

Hi, Ian Bannerman: > I did not know the Perl version did not support the EFI/Mac changes. Comparing the help texts of http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.c and http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.in shows that the latter lacks: -u --uefi Build EFI bootable image -m --mac Add AFP table support

Hi, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO

Hi, it would be interesting to know for what solution TAILS decides and whether any problems arise with it. ------------------------------------------------------- On with the fundamental discussion of MBR cylinders: Ady wrote: > 1_ The resulting ISO9660 file system size shall be a multiple of 2048 > (bytes_per_sector). The known ISO production programs comply to this condition.

Just a small correction: Thomas Schmitt via Syslinux <syslinux at zytor.com> wrote: > > > I expect the average waste to be a bit less than 16 MB. > > Yes, but slightly misleading. For example, the "16MB average" is > > relevant for 255/63. > > We advise two geometries: -h 63 -s 32 and -h 255 -s 63. > isohybrid behavior with the first one will not

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? >

Hi, Ady wrote: > I fear we would get slightly off-topic. Yep. Since the TAILS ISO is supposed to not grow over 2 GiB for now, it seems best to just use -h 128 -s 32 in order to stay near to traditions. ----------------------------------------------------------- Summary: The alignment to cylinder size is a core feature of isohybrid. If -h multiplied by -s is not divisible by 4, then ISO

Hi, first, thanks a lot, Ady and Gene, for your prompt and very useful replies! Ady wrote (11 Jun 2014 20:18:43 GMT) : > Although I haven't tested it lately, the Tuxboot tool should be able > to use the version of Syslinux included in your ISO images so to > transfer it to a (USB) drive. Since it works for other Debian-based > distros, it might answer to your needs.

> Hi, > > Ady wrote: > > I fear we would get slightly off-topic. > > Yep. Since the TAILS ISO is supposed to not grow over 2 GiB > for now, it seems best to just use -h 128 -s 32 in order to > stay near to traditions. > > > ----------------------------------------------------------- > Summary: > > The alignment to cylinder size is a core feature of

Hi, Ady wrote: > Let's not forget that the goal usually is to select CHS values so that > the resulting (optical and/or other) media would boot correctly in as > many systems as possible Agreed. But we now have a report about failure of 255x63 on a popular pseudo-hardware, when the ISO is presented as DVD-ROM. (Probably there is no complaint when it gets presented as hard disk.)

Hi, intrigeri wrote: > We're using `isohybrid -h 255 -s 63' [...] > isohybrid produces ISO > images whose size is not a multiple of 2048 bytes. Seems to be intentional. http://git.kernel.org/cgit/boot/syslinux/syslinux.git/tree/utils/isohybrid.in # Target image size: round up to a multiple of $h*$s*512