Slashdot Mirror


Wine BSD Fork 'Rewind' Emerges

Moridineas writes: "Since the wine project decided to change from an X11 style license to an LGPL license, a BSD fork has emerged, called Rewind (for 'Re-engineering Windows,' or something like 'Rewind to the old Windows days' in the words of Ove Kaaven) and currently hosted at http://rewind.sourceforge.net (but looking for a new home). The announcement of the fork and some additional information was posted to the wine-license mailing list [winehq.com]. At least one company [transgaming.com] has already stated that they will not be able to work with the LPGL wine (citing among other things, possible DMCA violations) and will be actively helping Rewind (with cash and code it seems)."

55 comments

  1. I find this cool! by mirabilos · · Score: 3, Informative

    If this is going to be a more qualitative version
    of Win32 I find this really cool.
    Ok, Microsoft will be able to integrate parts
    of Rewind into Windows, but, hey, BSD spirit is
    not "Let's make free software better!" but more
    like "Let's make _all_ software better!"
    Probably even some folks at Microsoft will be able
    to contribute to Rewind - hey am I dreaming?
    Anyways, let's see which one will be better than
    the other one, which evolves to the more accepted.

    If only the Rewind developers would care about it
    running on OpenBSD... the last Wine that did is
    from 1999, because it is said to require new
    binutils (which OpenBSD doesn't have on i386
    because it uses a.out-bsd format and not ELF)
    and kernel threads.

    --
    My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
    1. Re:I find this cool! by tps12 · · Score: 2
      which OpenBSD doesn't have on i386 because it uses a.out-bsd format and not ELF

      Is that true?

      --

      Karma: Good (despite my invention of the Karma: sig)
    2. Re:I find this cool! by mirabilos · · Score: 3, Insightful

      Yes, it is true at the moment, but more and more
      architectures are switching to ELF/OLF, and i386
      will be amongst them until 3.3, but probably even
      3.2 - as Art has received the gcc/binutils config
      he had requested, he will probably do it soon.
      You can look for ELF on http://marc.theaimsgroup.com/
      on the OpenBSD mailing lists (I think it was on
      misc@).

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
    3. Re:I find this cool! by tps12 · · Score: 3
      That really surprises me. Doesn't the use of .so dynamic libraries depend on ELF? I thought that was why Linux, NetBSD, FreeBSD, etc. switched in the first place. Or does OpenBSD use some kind of improved a.out on steroids?

      Also, how come OpenBSD has way better "album covers" than any other OS? No offense to Linus Torvalds, but the penguin is pretty dumb. Worse even than the BSD "daemon", and definitely no match for that puffer fish or whatever. Also, the name "Tux" is dumb...it is not clever to point out that penguins look like they are wearing tuxedoes. It would be much better if the mascot were a guy in a tux whose name was "Penguin". Haha. Also, is "Tux" supposed to rhyme with "Linux"? That means it's either pronounced "Tix" or "Toox", both of which sound stupid and make no sense.

      --

      Karma: Good (despite my invention of the Karma: sig)
    4. Re:I find this cool! by Anonymous Coward · · Score: 0

      FreeBSD and NetBSD use elf. Open BSD uses a.out due to security issues with ELF. Elf exports all symbols by default, which is a potential security hazard.

    5. Re:I find this cool! by Guy+Harris · · Score: 2
      Doesn't the use of .so dynamic libraries depend on ELF?

      No. The first UNIX to use that particular flavor of dynamic libraries was SunOS 4.0, which used a.out. (NOTE: I said "that particular flavor of dynamic libraries", not "dynamic libraries".)

      The BSDs that had dynamic libraries originally used a.out as well; one could think of the a.out that SunOS 4.x and the BSDs used as an "improved a.out on steroids".

      The System V Release 4 shared library mechanism was derived from the SunOS 4.x one; some of the things put into ELF (which was the executable image/shareable image/object file/core dump format devised by AT&T for System V Release 4) were done to better support that shared library mechanism. The free UNIXes that use ELF use reimplementations of the SVR4 shared library mechanism.

      Systems using the Linux 1.x kernel didn't use a SunOS 4.x-style shared library mechanism, although it might have been possible to implement it if the 1.x kernel supported calls to memory-map files; perhaps 1.x lacked those calls.

    6. Re:I find this cool! by mirabilos · · Score: 2

      Actually, the special a.out flavour used by OpenBSD
      for everything (on i386 et al.) is called NETBSD_NATIVE.
      You can also find a lot more hints at the NASM
      (Netwide ASseMbler) page at http://nasm.2y.net
      The format is called aoutb (in contrast to aout)
      and fairly modern, there is (in the nasmdoc) a
      tutorial how to write shared libraries, which also
      explains the few (user-visible) differences like
      the traditional underscore.
      By the way, if ELF hadn't been underscore-less,
      we would have gas with .intel_syntax not needing
      those cruelful % signs before the registers.
      That sucks (which does GNU, anyway, but with GNU
      it is like with democracy: choose the smaller bad).

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
    7. Re:I find this cool! by Anonymous Coward · · Score: 0

      OpenBSD is COFF, you clueless wanker.

    8. Re:I find this cool! by mirabilos · · Score: 2

      OpenBSD is a.out-bsd, on i386.
      With regards to the other arches, I do not operate
      them so I don't know it without having to look.

      But the source is free, try it yourself:

      http://www.openbsd.org/cgi-bin/cvsweb/src/sys/ar ch /

      --
      My Karma isn't excellent, damn it! (And /. still does not get UTF-8 right in 2012. Wow.)
  2. *BSD Trolls by norwoodites · · Score: 1

    Why in this article are there *BSD Trolls when this article is about a fork of WINE which still uses Berkeley license instead of LGPL. WINE would in a good thing to have a BSD like license on because corporations can use it for their apps and change it according to their needs and their code and not release that info. Code which is not in GPL is still can be Free Software, http://www.gnu.org/.

    1. Re:*BSD Trolls by MaxQuordlepleen · · Score: 1

      I'm guessing they are scripts dude.

      something like this:

      foreach my $title in (@slashdot_articles)
      {
      if ($title=~m/BSD/)
      {
      insert_bsd_is_dying();
      }
      }
  3. Wine will still be number 1 by Eivind · · Score: 3, Interesting

    This project will always lag behind the Wine-LGPL tree.

    The reason is simple. Anyone can take code under the X11-license and relicense it under the LGPL, while it is not allowed to distribute code under the LGPL under a X11-license.

    The practical upshot of this is that any improvements to the Rewind tree can be instantly copied into the Wine-LGPL tree, while any new functionality or bugfixes in Wine-LGPL has to be clea-room re-implemented to go into the Rewind-tree (unless the contributor licenses his contribution under X11-license like some contributors have said they will.)

    1. Re:Wine will still be number 1 by tps12 · · Score: 3, Interesting

      Well, the nature of the fork is that after a short while the two code bases will probably differ by enough that patches to one will not be immediately relevent to the other. By the same token, the developers of the two projects will probably become fairly disjoint. It'll be interesting to see where they both end up going. If Rewind is going to be the path of choice for commercial interests, then we will probably see more of Wine's top goals (running Office and the more popular games) being accomplished in Rewind. Then Wine will likely develop a new focus (Wine CE? Or tighter integration into Gnome? Lots of ways to go...). It'll be fun to see what slashdot story is posted about these project a year from now. (Even more fun than seeing what slashdot story is posted about them next Wednesday.)

      --

      Karma: Good (despite my invention of the Karma: sig)
    2. Re:Wine will still be number 1 by Anonymous Coward · · Score: 1, Informative

      I tend to doubt that. A lot of developers are jumping ship for the free BSD-based Wine, and it has multiple companies' support behind it, which the LGPL Wine doesn't have. I don't expect them to be around much longer at all.

    3. Re:Wine will still be number 1 by rubinson · · Score: 3, Funny

      It'll be fun to see what slashdot story is posted about these project a year from now. (Even more fun than seeing what slashdot story is posted about them next Wednesday.)

      Given Slashdot's track record, it'll probably be the exact same story!

    4. Re:Wine will still be number 1 by Anonymous Coward · · Score: 0

      "A lot of developers are jumping ship for the free BSD-based Wine and it has multiple companies' support behind it, which the LGPL Wine doesn't have."

      What a load of _FUD_! The majority of developers voted to move to the LGPL license and codeweavers (you know the company behind the crossover plugin and crossover office) started this move to the LGPL!

    5. Re:Wine will still be number 1 by Anonymous Coward · · Score: 0

      "If Rewind is going to be the path of choice for commercial interests... "

      The majority of developers voted to move to the LGPL license and codeweavers (you know the company behind the crossover plugin and crossover office) started this move to the LGPL so I fail to see how Wine will just become a specialized version of ReWind. More like the other way around.

    6. Re:Wine will still be number 1 by Anonymous Coward · · Score: 0
      The reason is simple. Anyone can take code under the X11-license and relicense it under the LGPL, while it is not allowed to distribute code under the LGPL under a X11-license.

      Unless they add an advertising clause, ala the original BSD license :)

    7. Re:Wine will still be number 1 by Anonymous Coward · · Score: 0

      Open Source is good for a lot of things, but online multiplayer games open sourced maybe isnt.

      Cheating can still happen, but it will be MUCH harder. I prefer a closed source version where I know the player at the other end has the same client I have.

  4. This is the wrong approach by Ogerman · · Score: 3, Interesting

    At least one company [transgaming.com] has already stated that they will not be able to work with the LPGL wine (citing among other things, possible DMCA violations) and will be actively helping Rewind (with cash and code it seems)

    First of all, the DMCA is an unconstitutional law and it needs to be fought tooth and nail until it is defeated. Transgaming should not be required to implement copy controls for their emulator to be both useful and legal.

    Second, this is more about Transgaming's business model than anything else. It's incompatible with LGPL because they require the ability to sell "value-added" proprietary versions of Wine. Since they don't own Wine, they are unable to dual-license it--such as making the old free and the new proprietary. Now, if we can trust them to release improvements back to the BSD codebase, this is fine. I, for one, would be more inclined to support them if they stuck with LGPL and just let subscribers control by vote the direction of development (ie. which games to support). Here's another idea: Proprietary game developers themselves! If game companies could pay Transgaming to support their latest and greatest games in Linux, don't you think their sales would rise? It would be sort of like Loki, except ensuring emulator support would be alot easier than porting. Then game companies could put stickers on their games that say "Works with Linux via Wine!" Or they could even include a Wine install kit (unsupported of course).

    1. Re:This is the wrong approach by Anonymous Coward · · Score: 0

      The Transgaming copy-protection stuff is licenced, no? If so, it has nothing to do with the DMCA, but instead whatever deal they worked out.

      Anyway feel free to reverse-engineer the stuff and hire a lawyer.

  5. Transgaming by ulmanms · · Score: 2, Informative

    From their page:

    The LGPL would dictate that we publicly release the source code to our copy-protection support - an action which would violate the tenets of the US Digital Millennium Copyright Act (DMCA)

    Now, I've never used their software, but wouldn't the breaking of the copy protection be the part that the DMCA would have a problem with, not the publishing of how to do so? ElcomSoft wasn't publishing how to crack ebooks, but that didn't help Dmitry.
    I'm sure Transgaming knows more about why they can't use the LGPL than I do, but this part seems inconsistent to me.

    1. Re:Transgaming by Anonymous Coward · · Score: 0

      I'm a fan of the BSD license, but this does sound a little backhanded.

      Restated more clearly, they're concerned about violating the DMCA on their *own* copy-protection technique, also known as "protecting their interests."

      As others have stated, useful Rewind code other than the copy-protection can easily be backported into the LGPL tree. However, it sounds like they could've just put their copy protection into a library for the same effect.

  6. DMCA by rodentia · · Score: 2

    I believe the issue is that TransGaming's copy-protection support, which is a major feature incenting game shops to work with them, could be construed at law to constitute a circumvention technique against the game's copy-protection. Remember that the DMCA is concerned about sustaining copy-protection, not interdicting code. It remains technically illegal for one to explain how deCSS works, let alone write code to do it.

    --
    illegitimii non ingravare
  7. Can someone explain to me... by Squeezer · · Score: 1

    If Transgaming can't help rewind because of possible DMCA violations then why are they contributing code and cash?

    Is it just me, or does that not make sense?

    --
    Does the name Pavlov ring a bell?
    1. Re:Can someone explain to me... by spongman · · Score: 2

      no, that doesn't make sense, but that's not what the article says. read it again.

  8. Transgaming: nothing but empty promises! by Anonymous Coward · · Score: 0

    The truth is transgaming has been promising to release there code to the main Wine branch before this change of license took place and _they_never_did_this! They are now promising developers a similar release, but only if developers agree to let them use there code in there proprietary software.

    Transgaming will _never_ release the substantial portion of there code and all of these promises of cash and code are empty. Transgaming, Lindows, Xandros: these are all companies looking to make a quick buck off of the backs of the community with little to nothing given in return.

    For an example of a good commercial collaboration with Free Software look at CodeWeavers, they are the one's pushing for the LGPL and they have improved the main Wine codebase exponentially!

    1. Re:Transgaming: nothing but empty promises! by TommyBear · · Score: 1

      Oh fuck off. What are you talking about? Transgaming were constantly submitting code to the Wine project... Nothing but empty promises? Man I can run Max Payne out of the box on Linux... and you call that empty?

      Get off your fucking fat arse and contribute first and talk later. Dickhead.

  9. This is BAD!! by Anonymous Coward · · Score: 0

    If they use a BSD-style licence, monopolistic companies like Microsoft can easily take the code and make their own, slightly different versions of the Windows libraries! "Embrace and extend", anyone?!

    Nevermind..

    1. Re:This is BAD!! by Anonymous Coward · · Score: 0

      Or the WINE developers could just take the Rewind code and put it into WINE. Would defeat the purpose of the two projects, but anyway...

    2. Re:This is BAD!! by sydneyfong · · Score: 1

      Wine is an implementation of the windows APIs on X and Unix. Aside from the very very core code, I don't really see how M$ could make anything out of the wine codebase... They already have their implementation of the APIs (and wine is only copying the published APIs, and APIs are usually fully implemented by windows before they are published), and since they have total understanding of the APIs, I doubt they really have the need to use wine code.

      --
      Don't quote me on this.
    3. Re:This is BAD!! by Anonymous Coward · · Score: 0

      No, really?

  10. Translation of their "PRESS RELEASE" by borgheron · · Score: 1

    TRANSLATION:
    They want to benefit from the work of others for free, but they don't want to share the changes they have built on top of the hard work done by the original developers. GJC

    P.S. Please don't mod me down as I am not trolling, just speaking the truth. :)

    --
    Gregory Casamento
    ## Chief Maintainer for GNUstep
    1. Re:Translation of their "PRESS RELEASE" by TommyBear · · Score: 1

      Yes you are trolling and so what? Many companies have contrbuted to the wine project, Corel, Transgaming, Codeweavers, Lindows even.

      Don't jump to conclusions. For fucks sake, Transgaming implemented entire DCOM support for wine.

    2. Re:Translation of their "PRESS RELEASE" by HanzoSan · · Score: 2

      Transgaming needs to make money, why dont you subcribe and help them RELEASE their code if you want it so bad.

      --
      If you use Linux, please help development of Autopac
    3. Re:Translation of their "PRESS RELEASE" by Abnormal+Coward · · Score: 1

      actually, according to the PDF's on there web site, they have only implemented in-process COM objects. Which is enough to code up DirectX 8 (which uses COM).

      DCOM and out-of-process COM would be a LOT hard to implement, you have to cope with passing data to another block of code in a diffrent memory space (Marsheling).

  11. Elegy for *BSD by Anonymous Coward · · Score: 0

    I am a *BSD user
    and I try hard to be brave
    That is a tall order
    *BSD's foot is in the grave.

    I tap at my toy kyboard
    and whistle a cheerful tune
    but keeping happy is so hard,
    *BSD will be dead soon.

    Each day I wake and softly sob
    Nightfall finds me crying
    Not only am Ia zit faced slob
    but *BSD is dying.
  12. No thats not it by HanzoSan · · Score: 2

    Transgaming doesnt sell software, you subscribe to a service which funds development of the software.

    The software is free, however they CANT release the binary version of wine because it uses securerom and other licensed code.

    They cant release the 3d game code because not enough users subscribed to pay for it.

    Nothing is being sold, you subscribe to pay for the development of the code when transgaming can pay for that development the code is released to you

    --
    If you use Linux, please help development of Autopac
  13. Wrong by HanzoSan · · Score: 2



    Transgaming will take Rewind, and add their own code to it then just release a binary.

    Transgaming will only release to Rewind when they get enough subscribers to pay for the release of code

    You see, the Rewind tree is NOT GPL which means it will always have corperate support

    --
    If you use Linux, please help development of Autopac
  14. Why didn't Wine Dual licence to avoid this? by Anonymous Coward · · Score: 0

    Obviously this could be avoided if the Wine guys simply used a dual BSD/LGPL.

    The more alternate licences, the more freedom.

  15. *BSD is dying by Anonymous Coward · · Score: 0
    It is official; Netcraft confirms: *BSD is dying

    One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 prcent of ll servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.

    Let's keep to the facts and look at the numbers.

    OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.

    Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.

    All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.

    Fact: *BSD is dying

  16. DCMA is US only you know by horza · · Score: 2

    Why not just host the software in Europe (and have it's theoretical 'base' there)? We are unencumbered by oppressive regimes such as the USA. Remember PGP and other encryption packages, where you could download secure versions from Europe but could only obtain crippled versions from the USA? This was used as evidence that the law was driving hi-tech business overseas and the US law was changed. Perhaps you could achieve the same with the DCMA?

    Phillip.