Re: Announcing xorriso-0.3.6

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

Joerg Schilling wrote:
> you need to know how other OS implement things.

I had reason to peek into Linux, FreeBSD and
Solaris. Some other BSDs too.


> Your "bug report" is invalid

It would not do harm to Solaris if it accepts
the same ER signatures as Linux and the BSDs.


> There is no IEEE-1282 standard.

How come you use the PX entries of RRIP-1.12
but not the signature which is prescribed
in there ?

In http://cdrecord.berlios.de/private/RRIP/rrip.ps
(which describes RRIP-1.10) i read:
"
  [2] "BP 3 - Length" shall specify as an 8-bit number the length
  in bytes of the "PX" System Use Field. The number in this fieldi
  shall be 36 
"
whereas in mkisofs/rock.c i read:

#define PX_OLD_SIZE 36  /* RR   POSIX Extensions (mode/nlink/uid/gid)   */
#define PX_SIZE 44      /* RR   POSIX Extensions (mode/nlink/uid/gid/ino) */
[...]
        Rock[ipnt++] = 'P';
        Rock[ipnt++] = 'X';
        if (rrip112) {
                Rock[ipnt++] = PX_SIZE;
        } else {
                Rock[ipnt++] = PX_OLD_SIZE;
        }

RRIP-1.12 does prescribe the "IEEE" ER signatures.
And it prescribes PX size 44. This allows to
express hard links. You want hard links.
So do one step more and accept whole RRIP-1.12.

I do not state that there exists IEEE 1282.
But there exists that string in ISO images.
Obviously long before my team mates began
to produce our first images.
We are not the only ones who believe that
SUSP-1.12 and RRIP-1.12 are valid specs.


> If you did ever compile on UNIX before, you did know that
> you need to add /usr/ccs/bin/ to you PATH.

That was not necessary on SunOS 4.


> I would recommend to make a disk installation.

There is not enough partition for that.
I needed a LiveCD for testing how xorriso does
on a general X/Open system. The osol-*.iso image
is nice to look at. But compiling is not foreseen.
Belenix stalls on boot. Schillix-0.6.7 is not very
recent but at least i could get it to work for me.

I'd rather like to have a shell account on a
well administered remote Solaris system.
For FreeBSD i found such a host.
That helps a lot with polishing the build process.


> In your specific case, I believe that I am able to help you....

I listen to any advise (... and then i do
my own awkward decisions, sorry).

Currently my priority is a complete list
of SUSP-like entry names.
If you know any, then please tell.


> You implement things that do not fit well into existing frameworks. 
> Writing a CD/DVD is e.g. a privileged operation,

Maybe on Solaris. On Linux and FreeBSD it is
perfectly sufficient to have rw-access to the
device file.


> This cannot be done in a library

Our source code is not bound to the library
architecture. Best proof is the xorriso standalone
tarball which i announce on this list. It is
a static compilation of all three library sources
and of the xorriso application code.

But system maintainers on Linux and FreeBSD want
dynamic libraries. My personal taste of linking
is perceived awkward but i am politely tolerated.


Have a nice day :)

Thomas