search for: partition_offset

...starting absolute offset of the resulting partition should > better be a multiple of 4KiB. This one is new to me. What can possibly happen if it is not fulfilled ? Well, isohybrid MBR partition 1 has to begin at LBA 0 in order to make it mountable, unless the ISO was produced by xorriso with -partition_offset to create a suitable second superblock and file tree. The advisable -partition_offset is 16 * 2 KiB. So the 4 KiB condition is more or less always fulfilled for the first partition of an ISO, after isohybrid is done with it. But it is not fulfilled with partitions which emerge because options --gp...

On Sun, Feb 2, 2014 at 6:27 AM, Mattias Schlenker <ms at mattiasschlenker.de>wrote: [...] > Build a recent xorriso - this can be run from the build directory without > installing (thanks, Thomas!): > > ./configure --enable-static > > Thank you for pointing this out, I tried desperately to statically compile `mkisofs' yesterday, to no avail. To hear that xorriso is

> I proposed -h 252 -s 63 because it yields the largest > possible cylinder size which is divisible by 4 (i.e. > the byte count is divisible by 512*4 = 2048). > -h 240 -s 63 would fulfill this constraint, too. > Size limits are 252*63*1024*512 = 8,323,596,288 > resp. 240*63*1024*512 = 7,927,234,560 bytes. > > > The workaround cannot be temporal, because the

...g partition should > > better be a multiple of 4KiB. > > This one is new to me. > What can possibly happen if it is not fulfilled ? > > Well, isohybrid MBR partition 1 has to begin at LBA 0 > in order to make it mountable, unless the ISO was > produced by xorriso with -partition_offset to create > a suitable second superblock and file tree. > The advisable -partition_offset is 16 * 2 KiB. > > So the 4 KiB condition is more or less always fulfilled > for the first partition of an ISO, after isohybrid is > done with it. > But it is not fulfilled with partition...

...so that when written to a USB, one can "claim the extra space" as another partition. As they are using in the current debian-live. So i came up with this: xorrisofs \ -o output.iso \ -no-emul-boot \ -boot-info-table \ -boot-load-size 4 \ -c isolinux/boot.cat \ -b isolinux/isolinux.bin \ -partition_offset 16 \ -partition_cyl_align auto \ ISO_root This works great, but i first have to run `isohybrid output.iso' which seems to reverse or ruin the special .iso partition. I am guessing it is just a matter of grokking xorrisos options. I didn't expect to get the maintainer of `xorriso' so t...

Hi, (My apologies to Geert Stappers for the inappropriate branch which i grafted on his thread today. It still grows. But i do my share to dry it out by replying to a message in the correct thread. :)) Dean Graff wrote: > But I really want to push xorriso to its limits. Be invited. > -partition_offset 16 \ This makes the partition table look more normal. But it should not be a hard precondition for later adding more partitions by help of some partition editor program. > [without it] # Creates an error for parted. does not work. This is a peculiarity of parted, i'd say. The partition st...

...s and/or finely structured access permissions. Mention that virtual machines can test the .iso file as virtual CD-ROM, and that it can be burnt onto CD/DVD/BD so that BIOS boots it from such media. > # Xorrisos special .iso allows other partitions to be made: I would prefer a statement that -partition_offset 16 creates a partition table which parted is willing to edit. Indeed, the emerging .iso is quite special: http://libburnia-project.org/wiki/PartitionOffset But the refusal of parted with less special images is probably not to expect from all other partition editors. Have a nice day :) Thomas

...[i,m,v]* ISO_root/isolinux cat > ISO_root/isolinux/isolinux.cfg <<EOF UI menu.c32 LABEL isolinuxtests EOF xorrisofs -R -J \ -o output.iso \ -no-emul-boot \ -boot-info-table \ -boot-load-size 4 \ -c isolinux/boot.cat \ -b isolinux/isolinux.bin \ -partition_offset 16 \ -isohybrid-mbr ISO_root/isolinux/isohdpfx.bin \ ISO_root # Put the .iso to a drive dd if=output.iso of=/dev/sdX # Xorrisos special .iso allows other partitions to be made: parted /dev/sdX mkpart primary "$(du output.iso)" 100% -m -s # Test the USB kvm /dev/sdX Thank you...

Hi, > # Most linux distros dont have `mkisofs' Or they have genisoimage under the name "mkisofs". (e.g. Debian, Archlinux) > mkisofs \ > -o output.iso \ > -no-emul-boot \ > -boot-info-table \ > -boot-load-size 4 \ > -c isolinux/boot.cat \ > -b isolinux/isolinux.bin \ > ISO_root I would add option -R or -r for Rock Ridge names and file

Has anyone experimented with installing XCP from a USB thumb drive? Is it possible? How was the installation media installed to the USB thumb drive (e.g., dd)? Eric Pretorious Truckee, CA _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

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.)