Re: Announcing xorriso-0.3.6
"Thomas Schmitt" <email@example.com> wrote:
> Joerg Schilling wrote:
> > My trick is to implement standards in the Solaris kernel
> > to get support for standard compliant features in mkisofs ;-)
> > [...]
> > The best I can do is to implement things in the kernel and to convince
> > people to do more collaboration.
> That is quite a luxury situation.
This is not luxury but hard work. If you like to do the same you would also
need to do hard work....
If you like to convince people, you need to know how different people agree on
proposals and you need to know how other OS implement things.
> Could you please point the person who is
> in charge for High Sierra FS to my bug
> report about missing recognition of RRIP-1.12 ?
> It is two weeks old and got no reply yet.
> I found the user community of Solaris very
> friendly but with the technical openness
> there could be some improvements.
There is enough technical openness, but people check ideas for correctness and
on whether they make sense.
Your "bug report" is invalid as you again refer to a withdrawn standard
proposal. I thought it was already marked as invalid. Solaris implements
the Rock Ridge standard but the the IEEE-1282
proposal was withdrawn. There is no IEEE-1282 standard.
> As we are at it and you are my inofficial
> Solaris distributor:
> Why is Schillix-0.6.7 as Live CD not ready
> for preforming
> ./configure && make
> although all tools are in the ISO image ?
If you did ever compile on UNIX before, you did know that
you need to add /usr/ccs/bin/ to you PATH.
> After booting one needs only to set 5 symbolic
> links to make it a rough but sufficient
> system for software building:
The READMEs explain what you need to do get gcc working.
I would recommend to make a disk installation.
> Is there a way to make the RAM disk larger ?
> (The 70+ MB of perl5 give enough room but i deem
> the method unelegant if there are still 600 MB
> RAM free.)
If you don't like to install, you may create your own CD using the toolkit.
> > I would call it NIH Syndrom :-(
> I often hit the Not Invented Here receptor of
> people with my ideas.
> Rather than quarreling i prefer to implement
> them and let them compete with what was
> already invented decades ago.
In your specific case, I believe that I am able to help you....
You implement things that do not fit well into existing frameworks.
If you did ask before and listen to warnings, you could avoid this.
Writing a CD/DVD is e.g. a privileged operation, a writing library forces the
calling code to be privileged too. Cdrecord carefully encapsules the privileged
part and drops privileges when they are no longer needed. This cannot be done
in a library and as a result, you make the system less secure.
Adding new ideas to old ideas or frameworks that have already been withdrawn is
a bad idea as this will not be accepted in a larger community.
EMail:firstname.lastname@example.org (home) Jörg Schilling D-13353 Berlin
email@example.com (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily