Re: [Bug-xorriso] building libisofs-1.4.4, libburn-1.4.4, libisoburn-1.4.4 on OpenBSD

[Thomas Schmitt]

Hi,

> OpenBSD-5.9/amd64

A new operating system on the list of fully supported ones. \o/
Thank you for porting the libburnia libraries.

--------------------------------------------------------------------

SASANO Takayoshi wrote:
> is there any good method to test?

make "check" of libisoburn would report general runnability, version number,
and enabling of extra features.

xorriso -devices was already some step beyond this by actually using the
OS adapter for drive detection and SCSI command passthrough. The manufacturer
and model name stem from such transactions.

A much more extensive test suite is described in
  libisoburn-1.4.4/releng/README
When in libisoburn-1.4.4 execute:

  cd ./releng
  ./change_shell_to_use
  ./run_all_auto -x ../xorriso/xorriso

If you have bash installed, then the change_shell_to_use run is not needed.
The shell code itself should be sufficiently portable amoung the bourne-ish
shells.

With some medium in the drive, make drive and media inspection tests

  ./manual_devices -x ../xorriso/xorriso -- --dev /dev/rcd0c

With a re-usable medium (ie.g. DVD+RW or BD-RE) in the drive, make a
write-and-verify test

  ./manual_burn -x ../xorriso/xorriso -- --dev /dev/rcd0c --what /usr/bin

Instead of /usr/bin one may use some other directory tree which bears
a suitable amount of data. 4x DVD speed is 5.5 MB/s, 2x BD is 9 MB/s.
So a few hundred MB would need a few dozen seconds.

If you only have write-once media and are willing to use one up, append
option "--any_media".

----------

If you are interested in producing bootable ISOs, consider GRUB2 program

  grub-mkrescue

which uses xorriso for ISO production with boot sectors for the installed
GRUB2 firmware-related software variants (for BIOS, for EFI, ...).

----------

You could make a backup of your $HOME (if you have a medium where it fits).
Once before the first $HOME backup on re-usable medium:

  xorriso -outdev /dev/rcd0c -blank as_needed 

For the first $HOME backup and as often as you want to update it
(until the medium is full) run:

  xorriso -abort_on FATAL \
          -for_backup -disk_dev_ino on \
          -assert_volid 'HOME_*' FATAL \
          -dev /dev/rcd0c \
          -volid HOME_"$(date '+%Y_%m_%d_%H%M%S')" \
          -not_leaf '*.o' -not_leaf '*.swp' \
          -update_r "$HOME" /"$(basename "$HOME")" \
          -commit -toc -check_md5 FAILURE -- -eject all

This will copy all files which have appeared or changed since the previous
run. A new directory tree will be composed from old still-up-to-date files
and from the newly copied files. Files which vanished on disk since the
last run will not be shown in the new directory tree.
The new session will get appended to the existing data on medium.
On overwritable media, the superblock at block 0 will get updated.
The freshly written session will get checked by the MD5 which was recorded
during the burn process and appended to the session.

Afterwards the youngest update state will be visible on mount(8).
  http://man.openbsd.org/mount_cd9660.8
mentions option "-s" for addressing older sessions (-s seems to be
in conflict with -s of mount(8)).
xorriso command -toc will tell the offset numbers in column "sbsector" of
its output table:

  TOC layout   : Idx ,  sbsector ,       Size , Volume Id
  ISO session  :   1 ,        32 ,    973200s , HOME_Z_2016_06_07_224758
  ISO session  :   2 ,    973248 ,     37499s , HOME_Z_2016_06_08_231748
  ...
  ISO session  :  37 ,   2061568 ,     18563s , HOME_Z_2016_07_19_223103
  Media summary: 37 sessions, 2079550 data blocks, 4062m data,  420m free

(Offset 0 leads to the most recent session as does offset 2061568.)

See also man xorriso example "Incremental backup of a few directory trees".

--------------------------------------------------------------------

> +#if defined(__NetBSD__) || defined(__OpenBSD__)

I see traces of myself suspecting that both are very similar.
But i cannot quite remember what i found out about their relationship,
back then.


> libburn-1.4.4/libburn/os-netbsd.h

Normally a fully supported OS may get its own os-*.h.
I will inspect your patch and then decide what to do.

(The <pthread.h> inclusions make me ponder ...)

When i am done with integrating it, i will ask you to test a development
snapshot of GNU xorriso, too. (Same source, other build software.)

But probably i will have some questions first.


Have a nice day :)

Thomas