Slashdot Mirror


Stallman And Bero Interviewed

Juraj Bednar writes: "I have done two interviews: one with Bero from RedHat and one with Richard Stallman, the GNU and FSF founder. I usually write in my native language, but since these interviews were done in English, I asked myself why not to share them" Readers may want to also visit Bero's shared-source.com, and bookmark it as a FUD antidote.

12 of 262 comments (clear)

  1. Re:Bero not quite accurate about GPL and derived w by Ridge2001 · · Score: 2, Interesting
    Those sorts of programs are "derived" in the GPL sense from Microsoft code

    When you say "derived in the GPL sense" you don't know what you're talking about. There is no "derived in the GPL sense". A "derived work" is a legal construct taken from ordinary copyright law. The GPL in no way introduces its own definition of "derived", nor does it modify the existing definition of "derived".

    The owner of a copyrighted work has the sole right to prepare derived works based on the copyrighted work. The license does not need to state this. This right is given by ordinary copyright law, and remains in place unless the license specifically allows others to prepare derived works.

    But Microsoft's code is under a redistributable licence, and the relationship between their code and your code is clearly spelled out in that licence.

    I have the license right in front of me. It's a ghastly hornet's nest of legalese, and it does sort of suggest that you have the rights to your own code, but it says nothing specifically mentioning header files. (Compare to the LGPL, which specifically mentions that including header files from a LGPL'd library does not infect your code.)

    Now am I suggesting that Microsoft has a secret plan to launch a massive lawsuit against all developers who have ever used Visual C++ to create a program that uses one or more header files, claiming ownership of their code, in an attempt to completely take over the world? Of course not. But, otherwise sane and rational people are willing to make the similar claims for Richard Stallman and the GNU project, even though their licenses are clearer and less ambiguous than Microsoft's. In fact, when the GNU project attempts to clarify and assert your rights by removing even the slightest ambiguity in one of their licenses (such as clarifying the role of header files in the LGPL, or making a special modification for the license of Bison), this is twisted, in the finest Orwellian fashion, into proof that Stallman must have been scheming to take over your code all along.

  2. Re:This is a common flaw in thinking. by Hilary+Rosen · · Score: 3, Interesting

    Unfortunately (the brutal truth).. the people who are business minded are FEEDING on people like us.

    You say this like it's a bad thing. Dung beetles feed on what I produce, too (well, not literally, but they could), but you don't hear too many people complaining.

    OSS only works for commodity software. Kernels. Web servers. Mail servers. Toolkits. Stuff that people use to get other forms of business done. The software you're writing is not a commodity, so you can sell it. But you rely on a certain level of infrastructure (Apache, say), so it's in your interests to fix Apache if it's causing you a problem. You could fork Apache, and start bundling Pengo-httpd with your product, but who would want that?

    --
    Yes, the nick is flamebait
  3. Re:Free vs Open by Anonymous Coward · · Score: 2, Interesting

    This is why free/open sourcers are called communists; because they advocate a social model where no one is making money off of software. In their model, no software generates money because no one is going to be willing to pay for something that has been devalued as low as "free". The value of our hard work is brought down so low that we become the janitors of the network world rather than seen as highly skilled people.

    Instead, money is generated by services. Unfortunately, as the value of that software is brought lower, those services will be needed more and more to deal with what will eventually be an acceptance of faulty software. Don't believe it it can happen? There's a whole majority of software users out there, one of which might be your grandmother or cousin, who believe that its OK for the program to crash if you can just restart it or reboot and carry on. Customer service is only glad to help at $100/hr when you call. Somehow I think this is really not what they intend, but there are roads leading off to all sorts of bad places paved with good intentions.

  4. RMS phoned it in by gmhowell · · Score: 3, Interesting

    Hey, unlike many, I like what Stallman says, and frequently how he says it. But it looks like Stallman just copied and pasted some boilerplate. Heck, I bet Jim Allchin could have written those responses to the question on behalf of Stallman:)

    But seriously, I think the interviewer wanted a solid answer in the first question: How does your view help me? We got the standard "someone can make a change". Maybe a better question is: how will this help my grandmother?

    --
    Jesus was all right but his disciples were thick and ordinary. -John Lennon
  5. *Offtopic* Re:Hack this box. by Faux_Pseudo · · Score: 2, Interesting

    I have a GUI installed on faux-wife's computer.
    It is running KDE 2.0 and I think its a very nice GUI. Better infact than windows even if it is a little less "entuative", entuative is like the word reality -- it always belongs in quotes.

    But I alwasy feel limited by the GUI. I can not >, |, x(){} or , a GUI app to get the level of power that I require/want. Command line apps are also easier to hack because you just add anoteher -x option instead of haveing to find room on an already clutterd API.

    You can not cron a GUI app that does anything substantial.

    My sig is not ment to spark a GUI vs Command Line argument. Its ment to appeal to those who thrive on the things that a command line can do that a GUI just is not capable of. By the same token there are those things a GUI can do that the command line can't. It is all a matter of preferance.

    Drag and drop and WYSIWYG is not always the best way to go.

  6. Re:Hack this box. by NonSequor · · Score: 3, Interesting
    Well I still have the Aqua themes that were taken down from themes.org. There are a lot of other Gtk and Sawfish themes that I think look far better than the Windows GUI. Granted, there are some _ugly_ themes, but I don't use them. I usually use one of the Aqua Gtk themes, but I often change to other good ones for variety.

    The splash screens that come with Ximian Gnome are always stunning, but they're not a major component of the GUI so they don't count for that much. The icons that come with Gnome need to be improved but they are still fairly good.

    I can't say anything for KDE since I haven't used it in a while, but I remember it looking pretty good when I did.

    I don't really see how one can say that Gnome and KDE are uglier than Windows and MacOS X when you can get themes that make the widgets look identical to those in Windows and MacOS X (although its a bit harder to find the MacOS X themes).

    --
    My only political goal is to see to it that no political party achieves its goals.
  7. Bero not quite accurate about GPL and derived work by joneshenry · · Score: 4, Interesting

    I'm sorry but I don't believe that Bero is being completely accurate when he claims that the "GPL makes no claims to data generated, processed, or stored by something covered by it." According to the text of the GPL "The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does." IANAL, but in my opinion, for a company to be completely safe about using the output of GPLed software, they must examine every line of the source code. The reason is that it is possible that the program will inject portions of itself into the output. An example is Bison whose license was modified. To quote documentation from an older version of Bison 1.20 "Bison grammars can be used only in programs that are free software. This is in contrast to what happens with the GNU C compiler and the other GNU programming tools. The reason Bison is special is that the output of the Bison utility--the Bison parser file--contains a verbatim copy of a sizable piece of Bison, which is the code for the yyparse function. As a result, the Bison parser file is covered by the same copying conditions that cover Bison itself and the rest of the GNU system: any program containing it has to be distributed under the standard GNU copying conditions." The license was later changed in version 1.24 and beyond: "As of Bison version 1.24, we have changed the distribution terms for yyparse to permit using Bison's output in non-free programs. Formerly, Bison parsers could be used only in programs that were free software."

  8. Re:Means of production by mimbleton · · Score: 2, Interesting

    "The core of communism is who controls the means of production. Did the people in the Soviet Union control the means of production? No, they did not. Thus it was not communism. "

    True, but simply because communism, as a completely utopian idea, cannot exist in reality.
    Human nature alone is a reason enough that communism will never succeed.
    There will always be a stronger individual, somebody with enough balls to hijack the entire enterprise and pretend that everything is done "in the name of the people."
    It happened every time people tried to implement workable version of communism ...

  9. don't forget the other interview! by reaper20 · · Score: 5, Interesting

    I'm glad we finally get an interview with bero, one of the most underrated hackers out there imo, i've always been fascinated with the Bero Linux distribution from a while back and everything he's done with RH so far. I would have asked some other questions, so since we all know he reads slashdot I have a few questions:

    1) You apparantly host dot.kde.org and post regulary, though RH 'sponsors' GNOME. Anyone at redhat have any comments towards you? Hate mail? Unexpected nerf ambushes? Do they sign you up for GNOME mailing lists? Do they make fun of the 'KDE guy in the corner'? (BTW, this is what makes open source so cool, the freedom to choose what you want).

    2) Any of the ideas from bero linux make their way into the main RH distro? I know Mandrake did, but since RH is mostly conservative, I'd like to hear your opinion.

    3) Does it piss you off that every complaint about the gcc in RH is answered on your website and you have to post the URL for the last 2 red hat releases including the betas? (that must suck).

    4) You get paid to work on Linux, that rocks! What do you think needs the most attention?

    5) Any chance that prelinking stuff will make KDE2.2? How about any of the other RH packages?

    Thanks, and thanks for the kde daily builds ... they rock.

  10. Re:Who is to write software, then? by rgmoore · · Score: 3, Interesting
    If software is to be free, then who can we expect to write it. Obviously, I have a need for a paycheck. Since I have this need, I have an employer. In order for my employer to pay me, I have to contribute to their revenue.

    You have made the classic mistake (and it's an honest and reasonable one given the dual meaning of free) of software that is available at no charge with software that's free of restrictions. Mr. Stallman has never suggested that it's wrong to charge money for software (to the contrary, in fact), only that it should not have obnoxious restrictions placed on it. RedHat, Mandrake, et. al (even non-proft Debian) charge money for Free Software and it doesn't make it non-free.

    And, of course, there are ways of funding free software other than trying to sell it. Linus is being paid partly to hack Linux because his employers think that it will help sell their products (microprocessors). Larry Wall is being paid to hack Perl because his employer thinks that it will help them sell their product (reference books). And now a number of big companies like IBM and Sun are paying developers to write Free Software at least in part because they think that it will help them sell their products (mostly expensive hardware).

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

  11. Re:Who is to write software, then? by Chris+Johnson · · Score: 4, Interesting
    Easy: people.

    What gives you the notion that writing software must be constrained to programmers?

    At http://www.airwindows.com/dithering/index.html you will find an elaborate program for high-end digital audio mastering from >16bit word lengths. It includes a number of very killer vertical-market type features like multiband sidechain compression. It does NOT have remotely professional file-reading and writing, because those are more 'real programmer' things, and I'm not a 'real programmer'. However, no 'real programmer' has shown any interest in writing such an app, and the market is so tiny that the few people building stuff for it tend to charge in the kilobucks- and the app I did is GPLed and just to have it costs nothing.

    So it is not a question of 'so if you wanted said mastering software, how would get it if nobody will write it without money?'. Surprise! Nobody wrote it anyway. The 'market' did not lead to any such software existing, even though I needed it desperately.

    And it is not a question of 'yeah, right, like a programmer is going to do hard work like that for free': clue jet coming in on runway six, a programmer didn't do that. I did. It's not done in the way you'd want to sell as shrinkwrapped greedware, but then the market's too small anyhow. The point is, this program _exists_ and grows and evolves based on just one person's ability to mostly sort of program. It's GPLed making it that much easier for the _next_ person who has a personal task to accomplish, to get a head start. And that's how it goes...

    I really have little patience for programmers. Programmers are like the people who put the spyware boobytrap 'dial up and invalidate the registration number if the person's reinstalled the program too many times' code into an mp3 player app that I _bought_ and ended up demanding my money back on. There's a lot that you don't really need a programmer for- you need one for good games, for serious server apps, for the _computery_ stuff, but there's a million other things that can be done more crudely by just regular people with a bit of determination.

    (I'm not _really_ against programmers- not like that- but I grow very sick and tired of the 'software can't be free, how will you survive without paying US?!?' refrain. Maybe you're not as indispensable as you think.)

  12. Re:Public universities, health care etc. by mimbleton · · Score: 2, Interesting

    "This is why we have kde vs. gnome "

    Both of which are trying to CATCH up with MS desktop which supposedly is so stagnated because of lack of competition ....
    Dumbass.