LWN: Comments on "The value of middlemen" https://lwn.net/Articles/97469/ This is a special feed containing comments posted to the individual LWN article titled "The value of middlemen". en-us Thu, 18 Sep 2025 02:12:59 +0000 Thu, 18 Sep 2025 02:12:59 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net The value of middlemen ... or less impassioned criticisers https://lwn.net/Articles/105850/ https://lwn.net/Articles/105850/ jamincollins Oh, I have a feeling if you read the entire thread in depth (I did a while back) you'll find that Jorg is just being a stubborn fool. This is just my opinion, but I lost a lot of respect for him over that flame fest.<br> Sat, 09 Oct 2004 06:26:39 +0000 The value of middlemen ... or less impassioned criticisers https://lwn.net/Articles/99746/ https://lwn.net/Articles/99746/ rabnud "Sometimes a middleman is just what is needed to make the whole process work."<br> <p> Well, sometimes collaborative effort is shunnedby a mind that is not accustomed to collaborative efforts. Not for nothing, but what is the real issue here - the method of addressing the device? Or is it the lack of clear 'Anglicised' thinking on the part of Jorg?? How about the amount of time he has evidently spent 'hacking' (in an unfavored sense) the core code (which was evidently SCSI oriented), just to accommodate the 'johnny come lately' ATAPI based devices which are not as familiar to Jorg??<br> <p> In his mind, I believe, the concept exists that the SCSI orientation has been the focus and maybe he is a little uncertain of the ATAPI patches, and hence is possibly a little resentful of the compromises made to accommodate ATAPI.<br> <p> I, for one, could see this discussion as alienating a valuable Linux contributor, all over the matter of him being a] not a native english thinker (and thus using english words in a less than accurate fashion), and b] possibly he is a little concerned that people (who are already critical of his software) are scrutinizing this software, as dozens of development fronts ask him questions regarding compromises that have been made to a core software in order to accomplish the existing software... maybe Jorg is a tad concerned over the people that always jump on others and scream 'I could have done better!'??<br> <p> I've only skimmed the thread, and I suspect the matter is misinterpreted.<br> Sat, 28 Aug 2004 01:19:38 +0000 Notification of modification https://lwn.net/Articles/99583/ https://lwn.net/Articles/99583/ sinnerbofh Same kind of warning in MandrakeLinux 10.0:<br> <p> $ cdrecord --version<br> <p> Cdrecord-Clone 2.01a27-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling<br> Note: This version is an unofficial (modified) version with DVD support<br> Note: and therefore may have bugs that are not present in the original.<br> Note: Please send bug reports or support requests to &lt;warly@mandrakesoft.com&gt;.<br> Note: The author of cdrecord should not be bothered with problems in this version.<br> <p> Salut,<br> Sinner<br> Fri, 27 Aug 2004 12:36:08 +0000 The value of middlemen https://lwn.net/Articles/98704/ https://lwn.net/Articles/98704/ AJWM For simply burning a DVD from an ISO, "growisofs" has, er, grown on me. It will burn from an existing ISO, although the command line argument syntax for that is a bit odd (ie something like "growisofs /dev/dvd=foo.iso").<br> Thu, 19 Aug 2004 19:17:30 +0000 The value of middlemen https://lwn.net/Articles/98520/ https://lwn.net/Articles/98520/ mbp I don't think that implies a "revocation" -- that term means that you are no longer allowed to use or redistribute previously-obtained copies. The GPL wouldn't allow that except in particular circumstances. <br> <p> What he may be doing here is refusing to licence future versions under the GPL. If he owns all the copyrights, then that is his right. Of course someone else can fork a previous version.<br> Thu, 19 Aug 2004 02:45:38 +0000 The value of middlemen https://lwn.net/Articles/98111/ https://lwn.net/Articles/98111/ mbp I actually do mean "fork".<br> <p> When, as is apparently the case here, the upstream developer simply will not take patches that almost everyone else agrees is a good idea, then it's time to fork. There *is* a time and a place for forking.<br> <p> (If it turns out that the author was right, the patches were a bad idea, and nobody uses them... well, that's life. But I don't think that would be the case here.)<br> <p> It would hardly be the first time. Somebody else mentioned XFree86. An even more relevant example is OpenSSH: when the original maintainer went off into a proprietary development, a fork arose and all the distributions adopted it.<br> <p> If somebody forked cdrecord into a free version that could record DVDs I think that would be great too.<br> <p> The choice here is not between zero forks and one fork. It is between one open fork, or alternatively every distribution applying different random patches.<br> <p> <font class="QuotedText">&gt;&gt; Which one, overweening, system would you have us all use?</font><br> <p> The one which allows you to say "cdrecord dev=/dev/cdrw". Is that so unreasonable?<br> Tue, 17 Aug 2004 05:08:26 +0000 The value of middlemen https://lwn.net/Articles/97958/ https://lwn.net/Articles/97958/ stock <br> maybe checkout OSS DVD at <a href="http://crashrecovery.org/oss-dvd.html">http://crashrecovery.org/oss-dvd.html</a> <br> <br> Robert <br> Mon, 16 Aug 2004 00:21:54 +0000 The value of middlemen https://lwn.net/Articles/97754/ https://lwn.net/Articles/97754/ garloff <font class="QuotedText">&gt; So he has added this GPL incompatible clause to 2.0a36: </font><br> <br> 2.01a36, sorry for being unprecise. <br> Fri, 13 Aug 2004 06:52:02 +0000 Notification of modification https://lwn.net/Articles/97753/ https://lwn.net/Articles/97753/ garloff On my SUSE Linux 9.1: <P> <TT> garloff@tpkurt:~ [0]$ cdrecord --version <Br> cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler <Br> cdrecord: Permission denied. WARNING: Cannot set priority using setpriority(). <Br> cdrecord: WARNING: This causes a high risk for buffer underruns. <Br> Cdrecord-Clone-dvd 2.01a27 (i686-suse-linux) Copyright (C) 1995-2004 J&ouml;rg Schilling <Br> Note: This version is an unofficial (modified) version with DVD support <Br> Note: and therefore may have bugs that are not present in the original. <Br> Note: Please send bug reports or support requests to http://www.suse.de/feedback <Br> Note: The author of cdrecord should not be bothered with problems in this version. <Br> </TT> <P> That should be clear enough. And that notice has been put there to avoid conflicts with Mr. Schilling.<Br> But apparently on some old release (on SL82?), there was no such clear warning. He complains about that, despite it's been fixed long since then. I wonder whether that's what really bothers him, though. Fri, 13 Aug 2004 06:46:44 +0000 special "Linux" version https://lwn.net/Articles/97745/ https://lwn.net/Articles/97745/ giraffedata I don't think this is a case in that point. <p> This is a rare case where the relevant characteristic of the systems in question is a matter of the Linux kernel. One of the issues is the way the user identifies the CDROM drive and how the program accesses it. That's pure Linux kernel. <p> Neither that nor the other issue -- DVD writing -- seem to have any connection to GNU software. Fri, 13 Aug 2004 02:44:30 +0000 The value of middlemen https://lwn.net/Articles/97739/ https://lwn.net/Articles/97739/ bignose <font class="QuotedText">&gt; &gt; There are good reasons why Red Hat and Debian (for example) are not</font><br> <font class="QuotedText">&gt; &gt; identical. [...] Which one, overweening, system would you have us all</font><br> <font class="QuotedText">&gt; &gt; use?</font><br> <font class="QuotedText">&gt; &gt; One shared linux friendly fork of cdrecord, not one version of linux.</font><br> <p> A case in point for the confusion caused by saying "Linux" when one means "GNU".<br> <p> Fri, 13 Aug 2004 00:42:19 +0000 Notification of modification https://lwn.net/Articles/97738/ https://lwn.net/Articles/97738/ droberge The version on my Debian system also displays such a notice; I guess I spoke in haste. <br> Fri, 13 Aug 2004 00:34:14 +0000 The value of middlemen https://lwn.net/Articles/97736/ https://lwn.net/Articles/97736/ gerv Yep - according to <a href="ftp://ftp.berlios.de/pub/cdrecord/alpha/">ftp://ftp.berlios.de/pub/cdrecord/alpha/</a> , cdrtools-2.01a36 is the latest version. I compared it against 2.01a35 and noted that this comment had been added.<br> <p> Gerv<br> Thu, 12 Aug 2004 23:43:25 +0000 Notification of modification https://lwn.net/Articles/97730/ https://lwn.net/Articles/97730/ Soruk The DVD patch I got from <A HREF="http://people.mandrakesoft.com/~warly/files/cdrtools/">Florent (Warly) Villard's CDRtools DVD patch</A> also puts up such a message. I have no problem with this - indeed it makes perfect sense. Thu, 12 Aug 2004 22:39:41 +0000 The value of middlemen https://lwn.net/Articles/97728/ https://lwn.net/Articles/97728/ Soruk You refer to "2.01a36" in your blog entry. Is this intentional?<br> Thu, 12 Aug 2004 22:29:21 +0000 Notification of modification https://lwn.net/Articles/97711/ https://lwn.net/Articles/97711/ corbet Don't know about the SUSE version, but Fedora's cdrecord starts by printing a four-line warning that the program has been modified and the original author should not be bothered. Seems like that should suffice. Thu, 12 Aug 2004 20:35:27 +0000 The value of middlemen https://lwn.net/Articles/97710/ https://lwn.net/Articles/97710/ droberge <p>It would appear that the text in the GPL that Mr. Schilling is referring to is: <blockquote> Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. </blockquote> which is the sixth paragraph in the <u>Preamble</u> to the GPL.</p> <p>It would appear that to some extent SUSE is in fact violating this, but it wouldn't actually be a violation of the GPL since the Preamble isn't actually prescriptive. (IANAL) I am not sure how one could completely comply with this without purging the original author's name from the program which is a clear GPL violation.</p> Thu, 12 Aug 2004 20:27:50 +0000 The value of middlemen https://lwn.net/Articles/97702/ https://lwn.net/Articles/97702/ mongre26 Sorry iabervon I was not specifically replying to you, hit the wrong link.<br> Thu, 12 Aug 2004 19:34:33 +0000 The value of middlemen https://lwn.net/Articles/97698/ https://lwn.net/Articles/97698/ mongre26 It is not Suse's fault that cdrecord users contact the author instead of him. <br> <p> I dubious of Mr. Schilling's claim that Suse is in violation of the GPL as the result of the actions of users. Namely contacting Mr. Schilling. Particularly when the GPL itself says there is no warranty. <br> <p> I have to investigate this more in depth, but I am gathering that there is more here than just people contacting Mr. Schilling for support for versions that are patched by Suse. More specifically that the distributors have had to apply patches (like DVD burning) to their cdrecord because the author has refused to do so himself. <br> <p> Given it is mentioned in the article that Mr. Schilling actually sells a commercial Linux DVD burning tool based on cdrecord I see a definite conflict of interest here.<br> <p> GPL and Open Source software is a two way street. Authors produce works, people write patches and submit them back. The system works best when there is two way movement of code. What it looks like from here is that Mr. Schilling has set up a roadblock and only allows those pieces of code to be applied to his version of cdrecord that do not conflict with the functionality of his commerical proprietary cdrecord version. What Mr. Schilling aparently did not realize is that Opensource has a way of routing around roadblocks and this is exactly what has happened with Suse and other distributors. <br> <p> Since Mr. Schilling was not able to or willing to accept key patches from others to add DVD functionality, nor was he willing to add it himself distributors like Suse acted in a way that is not only acceptable, but is exactly how the GPL is intended to work. Suse modified and distributed their own non-warrantied version under the GPL with improved usability and functionality, or at least as far as they are concerned. Relative evaluations of whether Suse cdrecord is better than vanilla cdrecord is not relevant. <br> <p> Mr. Schilling is trying to exert a level of control he does not have under the GPL and as someone said in an old movie I saw once "The more you tighten your grip... the more...will slip through your fingers.".<br> <p> If Mr. Schilling really wants to he can make version 2.0a37 and place it under "All Rights Reserved". His contributions to cdrecord from the communities perspective will cease and the fork will be official. <br> <p> Even without closing future cdrecord versions though Mr. Schilling has still put out notice that while he may say cdrecord is GPL it is only GPL on his terms. I think he needs to realize it does not work like that. The GPL gives rights to users that you do not usually see with most copyrighted works. That inevitably takes some rights away from authors. This is a key intent of GPL to give these rights to distributors and users, to ensure the software remains free. <br> <p> Mr. Schillings addition certainly violates the spirit of the GPL, and if there is code in cdrecord he does not hold copyright on he may be violating the letter as well. <br> <p> In any case I think it is prudent to assume that cdrecord 2.0a36 is not under any license for Mr. Schillings code and may have additional encumbrances. cdrecord 2.0a36 should be avoided. <br> Thu, 12 Aug 2004 19:32:45 +0000 The value of middlemen https://lwn.net/Articles/97686/ https://lwn.net/Articles/97686/ iabervon At the beginning of the file (at least in a35), it says "This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version." As far as I can tell, this grants permission to redistribute it and/or modify it under the GPL, and contradictory comments elsewhere in the file are not actual license terms.<br> <p> I find it odd that his claims about section 2c of the GPL are not, in fact, correct, though; he seems to think that if you distribute a modified version, you must include a notice that it is modified. In fact, you must include (2c) "an appropriate copyright notice and a notice that there is no warranty". If you don't claim copyright on your modifications, there's no way for an end user who doesn't read the (section 2a) "modified files" to tell that they have a modified version.<br> <p> It seems to me that he would actually be perfectly happy if distros were actually really acting completely as middlemen; his issue is that users contact him when they have problems rather than contacting the distributors who could actually be helpful.<br> Thu, 12 Aug 2004 18:55:35 +0000 The value of middlemen https://lwn.net/Articles/97694/ https://lwn.net/Articles/97694/ oak "wonder whether he has the right to revoke the GPL license, though"<br> <p> At least he cannot say it's GPL anymore. GPL as license is copyrighted too, so that people cannot claim as GPL (+ modifications) something which doesn't anymore have the same intent as GPL...<br> <p> Thu, 12 Aug 2004 18:39:22 +0000 The value of middlemen https://lwn.net/Articles/97675/ https://lwn.net/Articles/97675/ gerv <p>BTW, thanks for the tip-off. I've <a href="http://weblogs.mozillazine.org/gerv/archives/006193.html">blogged further</a> about this.</p> <p>Gerv</p> Thu, 12 Aug 2004 17:20:02 +0000 The value of middlemen https://lwn.net/Articles/97658/ https://lwn.net/Articles/97658/ gerv That clause makes the code it refers to non-free; this is an extra restriction which violates section 6 of the GPL. This has several ramifications:<br> <p> 1) When Jorg distributes the current version of cdrecord, he is violating the GPL license *on those parts he does not own the copyright on* - because the copyright holders of those parts have not given permission for their code to be linked with non-free code.<br> <p> This would allow anyone with code in cdrecord to sue him for copyright infringement.<br> <p> 2) Anyone who receives the code receives it under two conflicting license provisions. That means, according to section 7 of the GPL, that they may not re-redistribute the code at all, because they cannot simultaneously satisfy the GPL and the other conditions (allow unlimited freedom to modify, and stop modification of that section.)<br> <p> So any Linux distributor or other party distributing 2.0a36 or above is violating the GPL, and could be sued by copyright infringement by any contributor, including Jorg.<br> <p> Gerv<br> Thu, 12 Aug 2004 16:34:59 +0000 The value of middlemen https://lwn.net/Articles/97655/ https://lwn.net/Articles/97655/ garloff Mr. Schilling seems to disagree about the value of middlemen. He seems to have a special issue with SUSE, maybe because it was Jens being very patient trying to explain to him, why some of his statements do not really convince the community. <P> So he has added this GPL incompatible clause to 2.0a36: <Pre> /* * You are not allowed to modify or remove the following code. * I am sorry that I am forced to do things like this, but defective * versions of cdrecord cause a lot of work load to me and it seems * to be impossible to otherwise convince SuSE to cooperate. * As people contact me and bother me with the related problems, * it is obvious that SuSE is violating subsection 6 in the preamble of * the GPL. * * Note that although the SuSE test is effective only for SuSE, the * intention to have non bastardized versions out is not limited * to SuSE. It is bad to see that in special in the "Linux" business, * companies prefer a model with many proprietary differing programs * instead of cooperating with the program authors. */ </Pre> I wonder whether he has the right to revoke the GPL license, though. <P> Does he own the complete copyrights for cdrecord? Did contributors assign the copyright to him? Or has nobody succeeded to work with him and sent him patches? Thu, 12 Aug 2004 15:52:47 +0000 The value of middlemen https://lwn.net/Articles/97645/ https://lwn.net/Articles/97645/ jre I encountered the same problems as everyone else when I first tried to burn a DVD under Linux. In searching for the right patches, I found that J&ouml;rg Schilling had set up a weird system in which his GPLed CD-writing tools coexisted with a proprietary DVD-burning application, for which non-commercial users could get a time-limited key. The whole thing made my head spin. Then I discovered K3B, and my troubles were over. <br><br> I admire J&ouml;rg Schilling for the superb work he's done in creating the suite of CD-writing tools we all use. I respect his right to license his own work under whatever license he wishes. But, as a practical matter, I wish he would stick with the (correct) decision he made initially, and GPL every tool he releases. Trying to have it both ways just causes a lot of heartache and confusion and -- given the availability of alternative tools -- probably does not benefit him much, either. Thu, 12 Aug 2004 15:24:23 +0000 The value of middlemen https://lwn.net/Articles/97620/ https://lwn.net/Articles/97620/ ewan <i>No it wouldn't. And I don't think you mean 'fork' either - distributors try hard not to actually fork things.</i> <br> Most of the time, but sometimes it's necessary, as it was with the XFree86 - X.org change. <p> <i>There are good reasons why Red Hat and Debian (for example) are not identical. [...] Which one, overweening, system would you have us all use?</i> <br> One shared linux friendly fork <b>of cdrecord</b>, not one version of linux. It would be silly if everybody was independently patching cdrecord to fix the same problems, but I don't think that actually happens too much since they can all lift patches from each other. <br> That said it's possible that the pain of a full-blown fork might be less than the pain of dealing with Jörg.... Thu, 12 Aug 2004 12:14:59 +0000 Minor error https://lwn.net/Articles/97621/ https://lwn.net/Articles/97621/ corbet Yesterday was a long day...fixed now... Thu, 12 Aug 2004 12:07:18 +0000 The value of middlemen https://lwn.net/Articles/97586/ https://lwn.net/Articles/97586/ wookey No it wouldn't. And I don't think you mean 'fork' either - distributors try hard not to actually fork things.<br> <p> There are good reasons why Red Hat and Debian (for example) are not identical. Nevertheless they are highly compatible and you can generally use either if all you want is a 'linux system'. Choice is not a bad thing - it's good, and choice is not incompatible with interoperability.<br> <p> Which one, overweening, system would you have us all use?<br> Thu, 12 Aug 2004 11:15:15 +0000 The value of middlemen https://lwn.net/Articles/97571/ https://lwn.net/Articles/97571/ mbp It might be nice if the Linux distributors made a single Linux fork, rather than making every version a bit different...<br> Thu, 12 Aug 2004 08:01:26 +0000 Minor error https://lwn.net/Articles/97567/ https://lwn.net/Articles/97567/ jwharmanny /dev/cdrom is a symlink to /dev/hdc in most cases.<br> Thu, 12 Aug 2004 07:14:46 +0000 Minor error https://lwn.net/Articles/97563/ https://lwn.net/Articles/97563/ Duncan The following is rather minor, and it's obvious upon second look what was <br> intended, but it DID cause me to stop, go back and reparse the sentence to <br> see why it didn't make sense the first time thru. <br> <br> <font class="QuotedText">&gt; So, if your drive is /dev/hdc (or, better, /dev/cdwriter), </font><br> <font class="QuotedText">&gt; you run cdrecord with dev=/dev/cdrom [...] </font><br> <br> Where'd /dev/cdrom come from? &lt;g&gt; The hypothetical up to that point was <br> discussing /dev/hdc, with a parenthetical comment that /dev/cdwriter would <br> be more appropriate. Nothing at all about /dev/cdrom, until it's pulled <br> out of thin air, at a point where the reader would expect a reference to <br> something earlier. <br> <br> Not that I did well in composition (I didn't), or have any room to <br> criticise as a writer, but just as an initially confused reader.. <br> <br> The article /does/ make a very valid point, however, one that isn't <br> commonly emphasized in the community, and that deserves more attention <br> than it often gets. Distribution developers put a lot of at times very <br> hard work into their product, taking a lot of heat at times in the <br> process, and deserve a lot more credit than they sometimes get. <br> <br> Duncan <br> Thu, 12 Aug 2004 05:37:38 +0000