My initial goal is a "thingy" which a human at a terminal would not
notice any operational difference from netinst.iso on a CD.
This "thingy" would:
1. *NOT* have any internal assumption of being ISO9660 compliant.
2. intrinsically assume it will be resident on an ext2 device.
3. be recognizable and boot-able by Grub2.
On 09/19/2017 10:14 AM, Thomas Schmitt wrote
<https://lists.debian.org/debian-user/2017/09/msg00772.html>:
> Richard Owlett wrote:
>>>> xorriso -osirrox on ... -extract / /media/richard/netinst1
>
> i wrote:
>>> (This is just one way to copy the directory tree out of the ISO into
>>> a disk tree. xorriso packs them up and packs them out.)
>
>> I assumed that using xorriso on both ends would give me a
>> "byte for byte" copy.
>
> No, that's the job of "dd" or similar copy programs.
>
I had been attempting to follow the pattern of "Debian-Installer: How to
modify an existing CD image - Create copy of the image"
<https://wiki.debian.org/DebianInstaller/Modify/CD#Create_copy_of_the_image>
Using "tar" instead of "bsdtar" gave an error message that "This does
not look like a tar archive". That was the reason for attempting to use
xorriso with the assumption it would give a perfect copy of image used
by the developers/packagers to create netinst.iso .
Re-reading <https://wiki.debian.org/DebianInstaller/Modify/CD> after
reading <
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/MANIFEST>
suggested at least one reason I could not boot the resulting partition -
I needed an appropriate set of initrd/vmlinuz.
