Hi,

> teach me how to ask xorriso to burn distro ISOs.
> This post is a test. We have already been over the material :-)

Just for the records:

Writing a bootable ISO is the use case of xorriso -as cdrecord:
Whether an ISO boots from DVD via any mainboard firmware depends entirely
on the ISO's content. The burn program has no stake in this when putting
the ISO onto DVD.
bionicpup64-8.0-uefi.iso and debian-10.3.0-amd64-DVD-1.iso are supposed to
boot via legacy BIOS and via EFI.

Have a nice day

Thomas

Howdy! Thomas :-)

Looks like your tutoring paid off. It's been my goal to create a bootable disk from an distro iso, and you gave me the tools to do just that, and I thank you for it.

.........................................................................................
1) Assignment of path to variable "iso"
2) Insert file tree.
3) load iso files onto file tree.
.......................................................................................

Here is the code and its sequence of use.

1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso

2) xorriso -as mkisofs -v -J -r -V MY_DISK_LABEL -o my.iso /"$iso"

3) xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"

.........................................................................................

1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
2) xorriso -as mkisofs -v -J -r -V MY_DISK_LABEL -o my.iso /"$iso"

.........................................................................................

1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
3) xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"

.......................................................................................
cheers :-) Wayne

Howdy! Thomas :-0

Looked at my email to late to use your more direct approach :-( your approach would had saved me three days of head scratching, but hey! i love this stuff :-)

A question: When code begins "xorriso -as cdrecord" does this indicate a wrapper placed about cdrecord, and xorriso has taken a sudo position? This probably makes no sense :-(


cheers :-) Wayne

Disk is bootable; Distro workable :-)

Hi,

> 1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
> 2) xorriso -as mkisofs -v -J -r -V MY_DISK_LABEL -o my.iso /"$iso"
> 3) xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"

What is the purpose of step 2 ? It creates a file "my.iso", but then
you burn the original "$iso" to DVD.

"my.iso" would not boot, btw, because it lacks boot records which
direct the firmware to the bootloader programs in the ISO.
Examples of how Debian makes its ISOs can be seen at
https://wiki.debian.org/RepackBootableISO

> A question: When code begins "xorriso -as cdrecord" does this indicate
> a wrapper placed about cdrecord, and xorriso has taken a sudo position?
> This probably makes no sense :-(

No. It does not.

-as "cdrecord" is a xorriso command which interprets its parameters
roughly as cdrecord would do with its options. But then it uses
xorriso's internal capabilities to perform the job.
No source code from cdrecord was taken and no cdrecord program is involved.

The burn capabilities of xorriso are restricted to burning sessions of
a single data track each to CD, DVD, or BD media.
cdrecord can write audio CDs, which usually consist of multiple tracks
and are not readable as data. It can burn DVD and BD, too.

Have a nice day

Thomas

Step 1) Assigns bionicpup path to variable (iso)
Step 2 Burns file tree to disk.

1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
2) xorriso -as mkisofs -v -J -r -V MY_DISK_LABEL -o my.iso /"$iso"

xorriso 1.4.8 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:my.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 40.1g free
Added to ISO image: file '/bionicpup64-8.0-uefi.iso'='/home/ddval/Downloads/bionicpup64-8.0-uefi.iso'
xorriso : UPDATE : 1 files added in 1 seconds
xorriso : UPDATE : 1 files added in 1 seconds
xorriso : UPDATE : 2.66% done
.
.
.
ISO image produced: 181431 sectors
Written to medium : 181431 sectors at LBA 0
Writing to 'stdio:my.iso' completed successfully.
...............................................................................

Step 1) Assigns bionicpup path to variable (iso)
Step 3) Burns iso files to disk

1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
3) xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"

xorriso 1.4.8 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev '/dev/sr0'
Media current: DVD+RW
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free
Beginning to write data track.
xorriso : UPDATE : Formatting. Working since 0 seconds
xorriso : UPDATE : Formatting. Working since 1 seconds
xorriso : UPDATE : Formatting. Working since 2 seconds
xorriso : UPDATE : Formatting. Working since 3 seconds
libburn : NOTE : Write start address is 0 * 2048
xorriso : UPDATE : 1 of 354 MB written (fifo 99%) [buf 100%] 0.9x.
xorriso : UPDATE : 1 of 354 MB written (fifo 97%) [buf 100%] 0.3x.
xorriso : UPDATE : 6 of 354 MB written (fifo 98%) [buf 99%] 4.0x.
.
.
.
xorriso : UPDATE : 353 of 354 MB written (fifo 7%) [buf 99%] 4.0x.
xorriso : UPDATE : Closing track/session. Working since 74 seconds
xorriso : UPDATE : Closing track/session. Working since 75 seconds
xorriso : UPDATE : Closing track/session. Working since 76 seconds
xorriso : UPDATE : Closing track/session. Working since 77 seconds
xorriso : UPDATE : Closing track/session. Working since 78 seconds
Writing to '/dev/sr0' completed successfully.

xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
Drive current: -outdev '/dev/sr0'
Media current: DVD+RW
Media status : is written , is appendable
Media summary: 1 session, 181030 data blocks, 354m data, 4129m free
................................................................................
The disk generated does boot up and works.

Howdy! Thomas :-(

Well! Now it's obvious to me I was not aware of what is suppose to happen when 2)code excuted. Studied Debian Wiki,that's where I copied 2)code from. Honestly, did not know an iso is to be made with 2)code. I was simply attempting to put something together that would burn an iso to disk, and believed 2)code was part of the process. Strangely, [1); 2); 3]codes accomplished what I wanted, so, I believed what I achieved to be correct, and, although the bionicpup iso burned and created a bootable DVD, 2)code is wrong for the process. My bad :-(


cheers :-( Wayne

Hi,

step 2 did nothing except creating an ISO with a single data file in it:
the bootable ISO. To your luck you did not use that file "my.iso" for
the burn run.

Creating bootable ISOs is an expert task. Not only that you have to get
the xorriso run right. Before you can do that you need to compose an
operating system file collection and you have to set up bootloaders which
start the operating system.

Many small operating system producers use the program grub-mkrescue from
the GRUB bootloader project. It coordinates the creation of GRUB
bootloader equipment and the final xorriso run. The user still has to
provide the operating system files and a GRUB configuration which starts
the operating system.

Have a nice day

Thomas

1 members found this post helpful.

Right! took the process step by step to determine exactly what occurred with each code and various combinations. The fault lies in my interpretation of purpose for the Debian 2)code. :-(

1) iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
2) xorriso -as mkisofs -v -J -r -V MY_DISK_LABEL -o my.iso
3) xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"

2) Modified: Removed (/"$iso")from trailing end - no effect - successful execution.
ISO image produced @ home/ddval. 458.8 kB, ISO image produced 27 sectors. 192 sectors at LBA 32 written to medium. disk reported as blank, small sector count suggest isofs on disk. 2) does not require a path.

1) Provides path for 3)
3) Burns iso to disk,
.........................................................................................
1), 2), 3) executed successfully, burned bionicpup iso to disk.
.........................................................................................
1), 3) executed without 2) successfully, burned bionicpup iso to disk. therefore, if disk needs an isofs then 3) provides it.

cheers :-) Wayne

>>step 2 did nothing except creating an ISO with a single data file in it:
>>the bootable ISO. To your luck you did not use that file "my.iso" for
>>the burn run.


Creating bootable ISOs is an expert task. Not only that you have to get
the xorriso run right. Before you can do that you need to compose an
operating system file collection and you have to set up bootloaders which
start the operating system.

Many small operating system producers use the program grub-mkrescue from
the GRUB bootloader project. It coordinates the creation of GRUB
bootloader equipment and the final xorriso run. The user still has to
provide the operating system files and a GRUB configuration which starts
the operating system.

Well I saw the elephant, now it's time to turn toward more fundamental uses and understanding of xorriso. Actually, I believe, a good place to start could be Debian Wiki and xorriso GNU. Briefly perused both and found both loaded with a plethora of material that spiked my academic thirst. I'll have lots of questions :-)

cheers :-) Wayne

Hi,

> 2) xorriso -as mkisofs -v -J -r -V MY_DISK_LABEL -o my.iso
> 2) does not require a path.

It does require some path. Without any, the resulting "my.iso" will only
consist of an empty directory.
(But the procedure of burning a bootable ISO does not need step 2 at all.)

Have a nice day

Thomas