Re: [Bug-xorriso] (no subject)

[Thomas Schmitt]

Hi,

Rihards Balins wrote:
> when it comes to partitioning in
> ubiquity installer, then, when I want to install alongside somehow
> installer wants to partition sdb(where is my iso image) not sda and
> throws error that swap space can't be created.

This is not caused by the way how xorriso packed up the ISO and
equipped it with entry points for boot firmware.
As soon as the firmware (BIOS or EFI) has started the first programs
of the boot loader (i.e. MBR or \EFI\BOOT\BOOT*.EFI), the job of the
entry points is done. It then depends on bootloader and later on the
started operating system what happens further.


> These are commands I am using.

Looks like a normal "mjg" layout with ISOLINUX for BIOS and GRUB for EFI.

The only argument i can spot which might be of special meaning to
the installer is
  -volid "custom-iso-desktop-amd64" \
But normally an unsuitable volume id causes that the early stages of
the booting operating systems do not find the ISO, rather than mistaking
it for the disk to which software from the ISO shall installed.

Maybe your /dev/sda contains some partitioning which the installer
does not dare to touch. (Obviously the hardware is recognized by the
kernel, or else the ISO would be found on sda and not sdb.)

I guess you will have to ask Ubiquity users or developers what can cause
the behavior you observe. I'd either file a bug report
  https://bugs.launchpad.net/ubuntu/+source/ubiquity
or try to start a discussion at the mailing list
  https://lists.ubuntu.com/mailman/listinfo/Ubuntu-installer

If you do so, then please give me a short note here where to watch the
discussion for any indication that xorriso or your use of its options
is to blame despite my current opinion.


Have a nice day :)

Thomas