Re: PATCH: cdrecord: avoiding scsi device numbering for ide devices

[Robert M. Stockmann]

On Tue, 10 Aug 2004, Joerg Schilling wrote 

> As the people who did create the bastardized version of cdrecord
> you are using did not make clear where the official defaults file
> for cdrecord is located, they did violate the license of cdrecord.
>  
> It really does mot make fun to see useless forks for software including
> only modifications that do not give you a single advantage over the original.
>  
> The license used with cdrecord allows people to make modifications and to 
> rediustribute the versions. 
>  
> Not a single modification from one of the Linux distribution I did see so far
> did introduce any advantage over the original.
>  
> I would love to see cooperations (and there is cooperation with people from 
> many places), but the big Linux distributors all fail to cooperate :-(
>  
> Look into the mkisofs source, I even needed to include a comment in hope to
> prevent people from SuSE to convert legal and correct C code into a broken
> piece of code just because they modify things they don't understand :-(
>  
> Jörg

Hello Jörg,

i must agree here that getting cdrecord/cdrtools-2.0x going on the latest
SuSE 9.x editions has been extremely tiresome. Can it not be the case that
this has something todo with SuSE's inheritance to the UnitedLinux project?

I would like to suggest and kindly propose to maybe start cooperating
with Warly from MandrakeSoft. I think he has done a fine job sofar
in the latest Mandrake editions, 9.2 and 10.0 , making your cdrtools-2.0x
software run like it should. Warly is even by you mentioned as the only
one not violating your GPL licensed cdrtools package.

His efforts to get DVD burning rolling can be found at : 

http://people.mandrakesoft.com/~warly/files/cdrtools/
 
thanks,
best regards,

Robert
-- 
Robert M. Stockmann - RHCE
Network Engineer - UNIX/Linux Specialist
crashrecovery.org  stock@xxxxxxxxxxx

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/