Slashdot Mirror


Red Hat will give eCos Copyrights to the FSF!

An anonymous reader notes "Businesswire reports in this article that RedHat will assign its copyrights for the eCos embedded OS to the FSF. This is great news, considering that they have stopped developing it in 2002. Hopefully this will mean new life for the project."

197 comments

  1. New life for the project? by SpanishInquisition · · Score: 5, Funny

    You mean like HURD?

    --
    Je t'aime Stéphanie
    1. Re:New life for the project? by Anonymous Coward · · Score: 0

      No, like Linux 3.0

  2. If development stopped in 2002... by Fortunato_NC · · Score: 4, Interesting

    how come it looks like they added CPU architectures and features in 2003?

    --
    Blogging Weight Loss, Distance Education, and more at verlin.com
    1. Re:If development stopped in 2002... by mcspock · · Score: 5, Informative

      Development by redhat stopped in 2002, when they did a round of layoffs. Basically the entire ecos dev group (which all came from the cygnus buyout) got dropped, and the majority of them went to form eCosCentric.

      Redhat has continued to host the eCos project, just like they do for gcc and gdb, and the eCosCentric team has been writing updates as far as i know.

      --
      -- Patience is a virtue, but impatience is an art.
  3. tax writeoff by TedCheshireAcad · · Score: 3, Interesting

    Notice this is a healty tax writeoff at the beginning of the year. Hmmmm....

    1. Re:tax writeoff by greenhide · · Score: 5, Informative

      Probably not, unless they can show lost profit due to this maneuver. I once tried to donate a few websites to some organizations. After I'd developed them, I found out that I can't deduct one dollar of their value. Not one. Basically, the only thing you can easily take a deduction for is hard goods or cash.

      --
      Karma: Chevy Kavalierma.
    2. Re:tax writeoff by Anonymous Coward · · Score: 0

      So they should not have done it and kept it closed? If they did that, would you complain about propriatary software? Seems like a no-win situation.

    3. Re:tax writeoff by TykeClone · · Score: 1

      Which sucks - if your time is worth $x and you give away a couple of hours to a church or the local library, it would be nice to take a writeoff for lost earnings.

      --
      A fine is a tax you pay for doing wrong and a tax is a fine you pay for doing all right.
    4. Re:tax writeoff by XpirateX · · Score: 2, Insightful

      More than a "beginning of the year" coincidence, I would also consider RedHat's (fairly) recent move toward a very specific market (servers). It seems they're trying to possibly focus their efforts more, and along the way have a few "give-aways" that could be nothing but good publicity.

    5. Re:tax writeoff by SkArcher · · Score: 1

      You should have produced the source code for them on a CD and given them over. That would count as actual items, you see.

      --

      An infinite number of monkeys will eventually come up with the complete works of /.
    6. Re:tax writeoff by TrueJim · · Score: 1

      Why would one want a tax writeoff at the -beginning- of the year? The -end- of the year makes more sense. We pay taxes now on -last- year's activities, not this year's.

      --
      I hope that after I die the one word people use to describe me is "resurrected."
    7. Re:tax writeoff by SkArcher · · Score: 1

      oh, and in time honoured fashion, here it is in Slashdot mode

      1) Write Website Code & Burn to CD 2) Value Website at $$$$$ 3) ????? 4) Profit!!!111one

      --

      An infinite number of monkeys will eventually come up with the complete works of /.
    8. Re:tax writeoff by BritGeek · · Score: 1

      As an organization, you could - if you had capitalized the development costs. As an individual, you may very well not be able to.

      --
      "The time is always now" - Victor
    9. Re:tax writeoff by Lumpy · · Score: 2, Informative

      you did not do it right.

      I was albe to write off 4 websites for non-profit groups.

      1 - document hours spend working on it.
      2 - Bill the group a real invoice for services rendered.
      3 - get from them your form showing the donation amount.

      Voila! tax writeoffs. a website is no different than donating IT time. Time spent as labor is time spent as labor, there are no provisions for it must be on specific items.

      My CPA was who showed the correct proceedure to get things documented correctly to make it deductable.

      I reccomend talking to one to find out if there is anything special for your state so the deduction will apply to both federal and state taxes.

      --
      Do not look at laser with remaining good eye.
    10. Re:tax writeoff by DrSkwid · · Score: 1

      calendar year == financial year == year end ?

      Here in the UK the three are usually different.
      Financial years rollover on April 1st.
      A Company's financial year rollover is chosen by the company.
      This is so that there isn't a pile of work needed to be done around Christmas.

      Is the US not the same / similar?

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    11. Re:tax writeoff by Anonymous Coward · · Score: 0

      You better watch out for the auditors. What you did is not legal and if your CPA endorsed it then I recommend swithing quickly. Take a read Here (warning PDF) under what you cannot deduct. It very clearly states your time and services. This is true for individuals and businesses alike. You can only charge for out of pocket expenses.

      And yes I am a CPA but not a tax accountant. My specialty was Audit but I still had to take those damn classes.

    12. Re:tax writeoff by RazzleFrog · · Score: 1

      I forgot to add that by invoicing them and not receiving payment you effectively wrote them off as bad debt which is also not allowed for services. Overall I would be very careful about this year's return. I also apologize for the AC post before. Hit the wrong damn checkbox.

    13. Re:tax writeoff by greenhide · · Score: 1

      Huh.

      Your CPA is better than our CPA, then. We followed all of those steps, and then bubkas. We even got the letters from the organizations listing the amount of the donation.

      Nothing.

      --
      Karma: Chevy Kavalierma.
    14. Re:tax writeoff by RazzleFrog · · Score: 1

      You should be glad. As I pointed out above this is not a legal practice. He may get away with it because the IRS doesn't review things nearly as closely as people think. There are some flags that set them off and a few thousand in charitable contributions is not one. They do, however, do random audits at times.

    15. Re:tax writeoff by Ktulu_03 · · Score: 1

      RedHat's fiscal year begins on Feb 1st, so that's probably why they are doing this now.

    16. Re:tax writeoff by WuphonsReach · · Score: 1

      In the US, it's pretty much up to the company to determine when it's financial year ends. Some do calendar year, others often end their fiscal years on June 30th.

      Choosing a fiscal year
      Info about form 1120

      --
      Wolde you bothe eate your cake, and have your cake?
    17. Re:tax writeoff by Anonymous Coward · · Score: 0

      It would. But you'd have had to pay income tax on the earnings, so in a sense you've already got the writeoff.

    18. Re:tax writeoff by The+Snowman · · Score: 1

      Why would one want a tax writeoff at the -beginning- of the year? The -end- of the year makes more sense. We pay taxes now on -last- year's activities, not this year's.

      You pay taxes all year long. This will count for their CY04 taxes, even in January. Besides, I doubt this move was motivated by financial or tax reasons -- they probably donated it because they have no interest in the project and feel the community's needs are best met by the FSF taking control. This isn't the first time Red Hat did something morally commendable.

      --
      24 beers in a case, 24 hours in a day. Coincidence? I think not!
  4. Stopped developing it in 2002? by Saeed+al-Sahaf · · Score: 4, Informative
    This is great news, considering that they have stopped developing it in 2002. Hopefully this will mean new life for the project."

    The web site indecates new development as recent as September of last year.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:Stopped developing it in 2002? by jifl · · Score: 5, Informative
      >The web site indecates new development as recent as
      >September of last year.

      Um, development has been ongoing, irrespective of Red Hat's loss of interest back at the start of 2002. There just hasn't been any big news since then. See the patch list for example.

      The eCos maintainers (of which I'm one) have been pushing for a solution to the copyright issue for quite some time. It's good for everyone that Red Hat have donated eCos to the FSF.

  5. Wonderful news! by Seth+Finklestein · · Score: 0, Troll

    I used to work for a large consulting company (their name starts with "A" and ends with "con," if that's any clarification) that developed an embedded OS. This OS, "Clarix," was highly advanced and far superior to the piece of commercial dreck they bought for pennies on the dollar. They then jettisoned all the Clarix developers, but the large company retained copyrights on all their "intellectual property."

    I am highly gladdened to see Red Hat doing the right thing: when they no longer have a use for a product, they give the product away so that future hackers can leverage its power. Kudos to you, Red Hat!

    Sincerely,
    Seth Finklestein
    Retired Developer

    --
    I'm not Seth Finkelstein. I still speak the truth.
    1. Re:Wonderful news! by jeffkjo1 · · Score: 0, Offtopic

      Above poster is a lying troll. Check out his previous posts. Please mod down accordingly!!!

    2. Re:Wonderful news! by FortKnox · · Score: 1

      Actually, for once, he's telling the truth. I was on the Clarix project and he pretty much sums it up (albeit a bit tactless, but still true).

      --
      Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    3. Re:Wonderful news! by AKAImBatman · · Score: 1

      Do you have any links describing Clarix? I did a web and usenet search and the only thing that comes up is misspellings of Claris-Works.

    4. Re:Wonderful news! by Seth+Finklestein · · Score: 0, Troll

      Clarix was a "private-label" operating system. A*on only called it "Clarix" internally. Licensees were free to add their own branding and replace the name. The only documents you might find about Clarix are on the A*on intranet; of course, since you can't search that from Google, you can't find any "insider information" about it.

      Sincerely,
      Seth Finklestein
      Former Clarix Expert

      --
      I'm not Seth Finkelstein. I still speak the truth.
    5. Re:Wonderful news! by webtre · · Score: 0

      check your previous posts to see if you didn't post the same thing in the past

      --
      litigious bastards
      suck it sco!
    6. Re:Wonderful news! by OrangeTide · · Score: 4, Informative
      Not really big news. eCos was GPL since March of 2002. The difference is that Redhat is giving the copyright over to FSF to watch over. Prior to March 2002 eCos was under the Red Hat eCos Public License. If you go back even further eCos was first released in October 1998 by Cygnus Solutions. And [as far as I know] was property of Cygnus Solutions until November 1999, which was when Red Hat aquired them.

      If you are interested in developing with eCos the only book I know of is
      Embedded Software Development with eCos

      First chapter of the book...

      1.1 Where It All Started--Cygnus Solutions

      Michael Tiemann, David Henkel-Wallace, and John Gilmore founded Cygnus Solutions in 1989. The idea behind Cygnus Solutions was to provide high-quality support and development for open source software. It was initially unclear whether this business model would work out; however, by the end of the first year it was obvious from the value of the support and development contracts that the business was real. The workload was enormous for the five-person company (the three founders, a salesperson, and a part-time graduate student).

      It was clear that the engineering support model worked; however, the costs to fulfill these contracts were very high. In order to generate income at a lower cost, the engineers had to put their heads together to come up with an idea. The plan was to focus their development efforts on a small set of open-source technology that could be sold. The key to maintaining this development on an order that could be handled by the group was to keep the focus very small. What they came up with was selling the GNU compiler (GCC) and debugger (GDB) as shrink-wrapped software. This was the right team of people to do the job. Michael Tiemann, who contributed numerous GNU compiler ports and also wrote the first native C++ compiler (GNU C++ or G++), took on the task of working on GCC; David Henkel-Wallace worked on the binary utilities (binutils) and the library; and John Gilmore worked on GDB.

      This task grew to monumental proportions. One advantage, or so it seemed, was that John Gilmore decided to become the new GDB maintainer. Making this known to the Internet community immediately flooded him with different versions of GDB. Now came the task of integrating these new version features.

      Eventually, the hard work paid off in what today is called the GNUPro Developers Kit. The kit includes:


      Read the rest of the chapter yourself.
      --
      “Common sense is not so common.” — Voltaire
  6. Get it right! by Anonymous Coward · · Score: 3, Funny

    SCO/FSF/GNU/eCos

    1. Re:Get it right! by Anonymous Coward · · Score: 0

      ITYM
      s/SCO\/FSF/GNU\/eCos/gi

  7. Depends by AKAImBatman · · Score: 5, Insightful

    Hopefully this will mean new life for the project.

    I guess that kind of depends on whether anyone cares or not. Most people who might have used eCos for the commercial support aspect, are using the high powered and rock-solid QNX OS. And those who wanted free embedded OSes for home projects are already using Embedded Linux or *BSD. Even more difficult for eCos is that embedded Linux and *BSD distros are usually custom to the application. Why would anyone want the overhead of a prepackaged solution?

    Perhaps eCos has its uses, but it's a very small niche.

    1. Re:Depends by torpor · · Score: 2, Interesting

      You painted an interesting picture, but left a big gap.

      There are a lot of commercial companies actually using Linux, for whom QNX and eCOS are not worth the investment in light of recent kernel advances.

      I've considered using eCOS in some of my commercial products, but found that Linux does just as good a job in the right hands... not that its the be-all/end-all of embedded operating systems, but it sure is nice to be able to use the same system on an Intel developers box and an [insert-cpu]-type embedded box, for development and deployment...

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    2. Re:Depends by AKAImBatman · · Score: 4, Funny

      You painted an interesting picture, but left a big gap.

      There are a lot of commercial companies actually using Linux, for whom QNX and eCOS are not worth the investment in light of recent kernel advances.


      I'm sorry. I could have sworn that I already stated that the other end of the spectrum is "already using Embedded Linux and *BSD". Oh wait. I did.

      You might save yourself some trouble if you read more carefully. :-)

    3. Re:Depends by ams001 · · Score: 2, Informative

      My guess is you are a staunch QNX user and you know very little outside the QNX marketplace. eCos is the fastest growing RTOS (used in projects) and is being used in far more projects than QNX. Don't believe me, read the latest market surveys (unfortunatley, not public as the reports cost $4000 a shot). As for rock solid commercial support, eCosCentric was founded by the original developers of eCos after being laid off by Red Hat and continues to be developed and supported both by the community and the mainatiners with eCosCentric continuing to provide commercial versions.

    4. Re:Depends by mcspock · · Score: 4, Interesting

      My last company used eCos to build handheld and stereo component MP3 players, so that's my experience with it. In the handheld space it was great; small footprint (i built 40K ram/200K rom mp3+wma players with it), low overhead, minimal MMU requirements. The problem, with that space at least, is that the entire segment has shifted to faster processors with better MMUs, bigger hard drives, and generally larger requirements, which warrants using Linux. Even the eCos team was aware of this, as they started adding support for CPUs with memory protection and implementing more advanced OS features, basically scaling eCos up to...a trimmed down Linux.

      It was very good and extremely competitive at the time though; i think the issue is just that this time has passed.

      --
      -- Patience is a virtue, but impatience is an art.
    5. Re:Depends by AKAImBatman · · Score: 1

      eCos is the fastest growing RTOS (used in projects) and is being used in far more projects than QNX.

      Perhaps. Only time and the market will tell.

    6. Re:Depends by jifl · · Score: 4, Informative

      [Uh oh! Advocacy war storm clouds gather]

      I think you need to read up more on eCos! To call eCos "prepackaged" is about as far from the truth as you can get. The big C in eCos stands for configurable, and it is far more configurable and customizable to your application than any Linux or BSD will ever be, and certainly QNX.

      eCos is for the deeply embedded market, and embedded Linux, even in 2.6 is so much bigger. eCos systems start from just a few KB (~10KB I think I remember), and scale up from there as you use more features - using configuration, just exactly the features you want, and with the semantics you want. You get the choice.

      Add to that that eCos is completely open source, and royalty free with no upfront costs either (although you do have the option of commercial support if you do want it), and you'll understand why eCos is so popular.

      eCos supports many more targets and architectures than QNX too.

    7. Re:Depends by torpor · · Score: 1

      I guess I got tripped up on "embedded linux" versus "linux".

      My point is, with Linux being what it is, there's very little actual difference between an 'embedded linux' and a 'linux' kernel...

      Sorry for being brash. Get what I mean though?

      {Linux rocks. Put it in a box, any box.}

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    8. Re:Depends by AKAImBatman · · Score: 1

      eCos is for the deeply embedded market, and embedded Linux, even in 2.6 is so much bigger.

      But my point is that this is a niche market. Or to be more specific, an ever shrinking niche market. eCos probably fills that area quite well, but there's no way you could make any serious amount of money off of it. Even more difficult is the future development aspect of eCos. Given that the embedded market keeps moving to larger processors and more memory, eCos will either have to scale up to QNX proportions or get lost in the sands of time.

      Consider this for a moment. QNX started in the extremely small embedded market (e.g. dishwashers, car computers, microwaves, etc.) and has built up to its current size and ability due to customer demand. If that's what customers are demanding, is it really too big?

    9. Re:Depends by AKAImBatman · · Score: 1

      Get what I mean though?

      I understand. :-)

      The only real difference when it comes to embedded Linux and *BSD is how much you strip out of the kernel. When you're embedding, you tend to only include the modules, drivers, and utilities that are absolutely essential to the system functioning. Otherwise, the kernels tend to be the same thing.

    10. Re:Depends by Lumpy · · Score: 3, Insightful

      you still are not looking at the big picture...

      eCos on these Super fast processors can now deliver more than the same processor using a larger/slower OS.

      make a pocket video playback unit with eCos that is only slow and choppy with the larger players.

      just because you have more processing power does not mean it's smart to use it up with a larger platform that you won't use the added functionality.

      --
      Do not look at laser with remaining good eye.
    11. Re:Depends by ams001 · · Score: 1
      Consider this for a moment. QNX started in the extremely small embedded market (e.g. dishwashers, car computers, microwaves, etc.) and has built up to its current size and ability due to customer demand. If that's what customers are demanding, is it really too big?

      If eCos is targetting the extremely small embedded market and has a bigger market share than QNX, do you still think QNX made the right choice in going bigger? Fact is, when companies are producing millions of units and they can save $1 by using less memory, they will. I have seen companies spend six figure sums to modify their software to use less memory and cheaper parts so they can shave a few dollars off the cost of the unit. If they produce a couple of million units, that is a couple of million saved.

      So unless the price difference between memory sizes and CPUs becomes insignificant or reverses, there will always be a demand for smaller RTOSes.

      eCos is also royalty and license fee free, so there is another couple of dollars saved per unit right there.

    12. Re:Depends by torpor · · Score: 1

      I've considered a *BSD for one of my embedded projects, but Linux is just too easy to use...

      Its pretty nice actually, to run something like ROCK linux on all systems - development, deployment, testing...

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    13. Re:Depends by mcspock · · Score: 1

      No, i am looking at the big picture. I led a team of engineers building a home jukebox (think rio central, only affordable) using eCos. We had CD ripping, mp3 encoding, wma/ogg/mp3 playback, network streaming via UPnP, etc. We had 16MB of ram on board and 80k lines of code, and what we found out is as you expand your hardware and expand your codebase, you really need features like memory protection, and schedulers with feedback. With eCos memory protection was only available on a select number of processors, and there was no multi-level queue + feedback scheduler.

      Your example might be true if software was stagnant, and all you ever did was one function (play a video). In that case, sure, just get the faster processor and leave the software alone. However, in my post i was pointing out that hardware was expanding, software was following it, and continuing to build larger applications on a limited OS was eventually futile.

      --
      -- Patience is a virtue, but impatience is an art.
    14. Re:Depends by sessyargc · · Score: 1

      indeed its a very small niche but i think eCos would still be a very important (and popular) OS to Japanese companies because it provides an API layer (wrapper) that conforms to TRON. and it has a very small memory footprint.

      --
      - not everything that can be counted counts, and not everything that counts can be counted
  8. Abandonware by Rhubarb+Crumble · · Score: 5, Interesting

    Is this the first time a software developer has expressly relinquished copyright for abandonware? Of course, eCos was never proprietary, so it's not quite the same...

    1. Re:Abandonware by TwistedSquare · · Score: 4, Informative

      I remember reading (can't find mention on the site though) that Al Lowe, creator of the Leisure Suit Larry series, released the copyright on various old games (the ones owned by him rather than the publishers) for abandonware, since otherwise they would have died out... Confirmation would be good though.

  9. hmm... by Suppafly · · Score: 5, Funny

    I wonder what license the FSF will put on the copyrights when they get them?

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

      I wonder what licence Microsoft uses when they buy FSF.


      Any reason they couldn't/wouldn't do this?

    2. Re:hmm... by jifl · · Score: 1

      The same one as there is now.

    3. Re:hmm... by AKnightCowboy · · Score: 1
      I wonder what license the FSF will put on the copyrights when they get them?

      Well, if they're smart they'll put it under a BSD license so that companies can use eCos without worrying about some FSF lawyers coming after their ass like is what is going on with KISS technologies. Knowing the FSF and the rampant free software fanboys that are associated with it like RMS, I'm sure it will be the GPL which is a horrible license for embedded device software.

    4. Re:hmm... by Eric+Smith · · Score: 2, Interesting
      Hopefully they'll retain the modified GPL that it is under currently. Otherwise the developers will likely fork the last modified-GPL version.

      The eCOS license applies the GPL terms only to the actual eCOS license, but not to any user application code linked to eCOS. This is similar to how you can run an application program on a Linux kernel without the application being subject to the GPL. However, with eCOS, normally the application is linked directly to the eCOS kernel, so the modified license takes that into account.

    5. Re:hmm... by Ben+Hutchings · · Score: 1

      What are the differences between this modified GPL and the LGPL, then?

    6. Re:hmm... by Eric+Smith · · Score: 1
      If I link my proprietary code to an LGPL'd kernel and distribute the resulting derived work, I have to make available an unlinked (or partially linked) version of my code, so that the end user can relink it against a different version of the kernel.

      With the eCos modified GPL (which is essentially the same as the RTEMS modified GPL), if I link my proprietary code to the kernel, I am only obligated to provide the kernel sources (including any modifications I've made to the kernel). I don't have to provide unlinked or partially linked object code for my application.

  10. Go Red Hat! by fader · · Score: 4, Interesting

    As much as everyone seems to hate Red Hat for being big and pushing for what they want, I have to say that I truly respect them. They've never been anything but fair, honest, and helpful to the OSS community. Sure, they sometimes make unpopular decisions, but they focus on their business and don't try to meddle in anyone else's. And they've certainly never pulled any stunt worthy of calling them the 'Microsoft of Linux' as gets thrown about from time to time. The worst they've ever done is ask that people redistributing their distro use a different name and artwork. I can't see how anyone could have a problem with that.

    And as this shows, they often go above and beyond the mere requirements of the GPL. They've released a good amount of software under the GPL when they really didn't have to. They pay a lot of developers' salaries, too.

    So I'd like to say thanks, Red Hat. I have nothing but good feelings toward you, and I hope you do better and better financially.

    (Full disclosure: I don't work for Red Hat, don't own any of their stock, etc. I knew one guy who worked for them, but he was a tech support grunt there for a few months and I wasn't even in contact with him then. These opinions are my own.)

    --
    - fader
    1. Re:Go Red Hat! by Anonymous Coward · · Score: 1, Insightful
      Fair and honest - just as FOX is fair and balanced.

      It might be fair and honest on paper to dump their desktop clients in favor of enterprise clients, but I will never forget or forgive them for that decision.

    2. Re:Go Red Hat! by torpor · · Score: 1

      Everyone doesn't hate Red Hat. In fact, quite a few people do respect this company, use its products, pay for its products, and are quite happy with it.

      Its just that those who hate RH are the only ones talking about it. You're only sampling data from one side of the argument, because you rarely get someone going to a lot of trouble to praise something as avidly as they might criticize it...

      Human nature. Get used to it, and try to read it properly.

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    3. Re:Go Red Hat! by hendridm · · Score: 1

      > As much as everyone seems to hate Red Hat for being big and pushing for what they want

      I think the vocal minority here on Slashdot has said negative things about RedHat in the past. I'd dare to say there are a lot of Slashdotters who use RedHat/Fedora on the server/desktop daily. I like their products, and although I think their WS edition is way overpriced, they still make a good distro IMO. They've given a lot to the community and I appreciate their sponsorship of Fedora.

    4. Re:Go Red Hat! by Anonymous Coward · · Score: 0
      Well, I've got only one thing to say to people like you.

      I hate you for supporting an "open source" corporation that dumps its desktop clients.

  11. This is strange. by Krapangor · · Score: 2, Interesting

    I always thought that code based on GPLed code falls under the GPL anyway and must be published.

    --
    Owner of a Mensa membership card.
    1. Re:This is strange. by xianzombie · · Score: 2, Interesting

      True, but even under GPL, doesn't it still kinda belong directly to the original creator, if only by name alone?

      Perhaps this is RH's way of reliqusihing all ties.

      I don't see how it serves much of a specific purpose though.

    2. Re:This is strange. by AndyFewt · · Score: 2, Informative

      Code != Copyright
      They've assigned the copyrights (not code) over to the FSF. The code has always been available from: http://ecos.sourceware.org/getstart.html

    3. Re:This is strange. by The+Lord+of+Chaos · · Score: 4, Informative

      AFAIK eCos was always published under the GPL.

      Assigning copyright to the FSF means that the FSF now owns the eCos codebase and they can do whatever they want with it including publishing it under the GPL.

      Basically the point of this is so that if a developer wants to contribute to the eCos codebase they fill out a copyright assignment to the FSF instead of RedHat from now on.

    4. Re:This is strange. by i_really_dont_care · · Score: 2, Informative

      eCos was once published under the eCos License, which was similar to the LGPL but not GPL-compatible. It is now published under the GPL with the exception of allowing proprietary applications / extensions (this is important in the embedded software market).

    5. Re:This is strange. by mcspock · · Score: 1

      This is incorrect. It was originally published under some license from cygnus, which i dont recall; then when redhat purchased cygnus it was RHPL.

      The last time i checked, they had transitioned to a modified GPL. In fact i dont think the license is GPL compatable, since the modification they made allows companies to opt out of open-sourcing code they link against eCos, basically avoiding the corporation-unfriendly aspect of the GPL.

      --
      -- Patience is a virtue, but impatience is an art.
    6. Re:This is strange. by Frater+219 · · Score: 2, Insightful
      True, but even under GPL, doesn't it still kinda belong directly to the original creator, if only by name alone?
      Red Hat was the copyright holder. They got eCos when they bought (IIRC) Cygnus. Thus, what they are doing here is not simply licensing eCos to FSF; they are transferring the copyright to FSF. FSF now is the copyright holder, not simply a licensee.

      My reading of this is that it means that Red Hat is not interested in spending money defending the eCos copyright, if it should be violated. Only the copyright holder can pursue a claim when a copyright is violated. FSF has a history of doing this for GNU products they hold copyright to -- going back to the '80s when they nicely informed Steve Jobs that he had to follow the GPL for NeXT's gcc derivative.

      (One of the lies people like to tell about the GPL is that "it's unproven because it's never been tested in court". Fact is, it's never had to be tested in court -- violators have always backed down before they had to be sued. NeXT was violating the GPL by distributing an extended gcc -- with Objective-C support -- without source. Once FSF confronted them, they released the source. The descendant of that gcc is still used in Mac OS X.)

    7. Re:This is strange. by bradkittenbrink · · Score: 2, Interesting

      That may be true, but the fact that the FSF now owns the copyrights means that the FSF can take over license enforcement. That's why they really did it.

    8. Re:This is strange. by Mikkeles · · Score: 1
      All anyone needs to know about the eCos licence is here :^)

      The linked page begins:


      As of May 2002, eCos is released under a modified version of the well known GNU General Public License (GPL). The eCos license is officially recognised as a GPL-compatible Free Software License. An exception clause has been added which limits the circumstances in which the license applies to other code when used in conjunction with eCos. The exception clause is as follows:
      As a special exception, if other files instantiate templates or use macros or inline functions from this file, or you compile this file and link it with other works to produce a work based on this file, this file does not by itself cause the resulting work to be covered by the GNU General Public License. However the source code for this file must still be made available in accordance with section (3) of the GNU General Public License.
      This exception does not invalidate any other reasons why a work based on this file might be covered by the GNU General Public License.
      --
      Great minds think alike; fools seldom differ.
    9. Re:This is strange. by jifl · · Score: 1

      By that token, libgcc is GPL incompatible, libstdc++ is GPL incompatible, Guile is GPL incompatible, etc. The whole point of the exceptions for those bits of GNU software, and for eCos, is to make it possible to write application code, without the GPL affecting that code.

      To give some accurate background, the first eCos license was the CEPL - Cygnus eCos Public License. This was a Mozilla Public License derivative. Then Red Hat bought Cygnus and it became the RHEPL - the same license with the names changed, that's all.

      Then not long before the eCos team left Red Hat, it was put under the current GPL+exception license.

      With the Red Hat assignment to the FSF, we can now enforce the license much more easily, change the license if needed down the road (in case it was needed for legal reasons - it requires 100% agreement from all copyright holders), and there were a few contributors who were not prepared to make copyright assignments for their contributions to Red Hat, it being a commercial company, and especially when Red Hat no longer had any real interest in eCos. It also resolves a few hiccups with the copyright assignment process we had.

    10. Re:This is strange. by mcspock · · Score: 1

      Hi Jonathan. I used to work with eCos a bit (danc at fullplaymedia/iobjects), and i seem to remember having this discussion with you in the past.

      I understand the point of the exception, and the reasoning behind it. I more than agree with it too. The reason i made the "gpl imconpatible" comment is that the exception basically undermines one of the main provisions of the GPL regarding redistribution. I dont know if you follow linux stuff at all, but even recently Linus stated that kernel modules built specifically for linux, and even applications including linux specific headers, would have to be GPL'd because they linked in or used portions of the kernel and fell under the GPL's distribution clause.

      Making an exception to this clause basically makes your license not like the GPL. :) That has always been my view. I seem to remember there being some other wordage since eCos links statically instead of dynamically (as with the above libraries) but i'm not sure about this.

      Regardless of the licensing here, i can see how redhat releasing the copyrights would benefit everyone here. Hopefully things continue to go well for you and for eCosCentric

      --
      -- Patience is a virtue, but impatience is an art.
    11. Re:This is strange. by Xtifr · · Score: 1

      I always thought that code based on GPLed code falls under the GPL anyway

      No, any original work you do can be licensed any way you want. If you combine your work with GPL'd code, then the combined result must be GPL if you distribute it, but your individual sections can still be under another license as long as that license is GPL-compatible or you don't distribute.

      Thus, any BSD-licensed bits in the Linux kernel are still BSD-licensed, even though the kernel as a whole is GPL'd.

      and must be published.

      No, you don't have to publish. If you do publish, you have to publish everything (inc. source), but you still retain the option of publishing nothing. If you just want to use the system, you can combine it with any sort of code your heart desires. Microsoft, if they wanted, could make a modified version of Linux that was inextricably linked to IE, and could deploy that system on every desktop in their company. They just couldn't distribute it outside of the company.

      Anyway, this is all irrelevent to the topic of eCos. They're changing the copyright owner not the license! Owners aren't subject to license terms -- owners set license terms!

    12. Re:This is strange. by ceswiedler · · Score: 1

      EULAs have never really been tested in court, and generally when confronted with violating them, people will back down. Until the stakes get high enough, the threat of a lawsuit is usually enough.

      But when the stakes DO get high enough, there is a world of difference between a license which has been found valid by a judge, and one which has not. Because the potential payoff is high enough for SCO, they are willing to go up against the GPL.

      Of course, even a judge's decision doesn't mean someone won't re-argue the same thing a decade later, and possibly even win...

    13. Re:This is strange. by droopycom · · Score: 1

      Amen to that...

      I know at least one person whose first reaction to the news was "We can forgot about using eCos".

      Now anybody can expect the FSF to eventually go to a even more restrictive license.

    14. Re:This is strange. by jifl · · Score: 1

      We've already been discussing with the FSF how to phrase a declaration/guarantee that the eCos license stays as it is in principle (i.e. keeping the exception part). We just haven't agreed the final wording yet.

      So you can tell your friend not to worry :-).

  12. Good news by CelticWhisper · · Score: 2, Insightful

    Indeed, this is great news. And this is one copyright I won't mind respecting :-)

    It's good to see a company with its head screwed on straight, who can acknowledge when its time to move on from old wares and just let them go, instead of clinging to everything it's ever had its hands in, even when it's obviously pointless to do so.

    --
    Help protect civil rights from abuse by the TSA - visit TSA News Blog.
    http://www.tsanewsblog.com
  13. Where has eCos been used? by anactofgod · · Score: 1

    I see on the eCos site a listing of support platforms, but can anyone point me to an actual project/product that used eCos?

    Thanks in advance.

    ---anactofgod---

    --

    ---anactofgod---

    "Equal opportunity swindling - *that* is the true test of a sustainable democracy."
    1. Re:Where has eCos been used? by ams001 · · Score: 5, Informative

      There are loads of commercial products and projects using eCos. See http://www.ecoscentric.com/ecos/examples.shtml

  14. Dreamcast Linux by Erwos · · Score: 5, Informative

    The Linux-Dreamcast port apparently uses eCos to do some of the initial booting. So, while I wouldn't say I've seen it used practically, it was a nifty application of the OS.

    -Erwos

    --
    Plausible conjecture should not be misrepresented as proof positive.
  15. It could possible be by 2names · · Score: 1, Informative

    that the actual development was done prior to 2003 and only implemented in 2003. Just a guess, though, I could be wrong.

    --
    "I'm just here to regulate funkiness."
  16. Mixed Feelings about news like this by dr_canak · · Score: 4, Interesting

    I'm a Redhat shareholder, not a lot of shares, and bought well after they bottomed out. I bought the shares for two reasons.

    The first was because I thought if any company had a shot a taking a piece of Microsoft, it was Redhat. I use MS products everyday, probably always will, but I'm one who believes that MS got where they are with unfair market practices and ended up a little too big for their (and our) own good. By buying Redhat shares, I figured I was backing up my philosophy with my wallet.

    The second reason is purely more pragmatic. Assuming Linux can take a stab at Microsoft, I believe Redhat is the most viable company to do it. In 30+ years, I'd like to think my decision to buy Redhat shares (when it was $12.00 a share) will be similar to people who bought Cisco, Oracle, MS, etc... back in the day. Sure the stock prices have wildly fluctuated, but look at the splits, and you realize just how much money there was to be made. So of course I would like to see that kind of return on this investment.

    Which is why I end up conflicted when I see news like this. On the one hand, giving away a copyright is exactly the kind of collaboration you see with the Linux development model, and why it *may* in the end surpass MS in some, if not all, applications. But as a shareholder, giving away copyrights is hardly a way to grow a business. It took time, money, and effort to secure the copyright. Who knows if this news really effected shareprice, but with the release of this news, Redhat is down almost .50/share. So as a stockholder hoping to make money on my investment, I'm not too thrilled with this kind of news.

    I suppose that's why you need to leave your emotional mind out of the market place, to avoid investing with your heart, and not your head ;-).

    just my .02 (- .50)
    jeff

    1. Re:Mixed Feelings about news like this by Xenopax · · Score: 3, Informative

      I'd like to think my decision to buy Redhat shares (when it was $12.00 a share) Haha, I got in at something like $4/share. Either way though, you have to be happy with their earnings report in December. Also, I don't believe giving away copyright will significantly reduce the share price. Anyone with half a brain who's invested in Redhat knows the company gives away its work and makes it up on the support side. Oh wait, I said half a brain, that rules out 99% of investors.

    2. Re:Mixed Feelings about news like this by Anonymous Coward · · Score: 1, Insightful
      eCos is something they picked up with the Cygnus acquisition, and I'd be very very surprised if they ever made a dime off of it.

      Taking exception with the management for continued funding for the project when they saw it wasn't going to make any money is one thing; but taking exception for throwing away the "value" in the copyright of the commercially unsusccesful project is another.

      Sure, you can use 20/20 hindsight and lambast them for funding it in the first place. And anyone familiar with R&D in a large organization will jump all over you.

      But being peeved because they are donating something of zero value to them just shows you need to relax your sphincter.

    3. Re:Mixed Feelings about news like this by Jerky+McNaughty · · Score: 1

      Note that the market as a whole is down today, as well. I don't think that Redhat's release of these copyrights has much to do with this very short term decline at all. I doubt that eCos was ever much of a revenue stream for them at all.

      It's not as if Redhat is somehow being forced legally to assign copyrights to some major portion of what generates profitability for them. eCos doesn't fit with what Redhat's business model is about any more, so they're giving it away.

      I say, "Good for them!"

    4. Re:Mixed Feelings about news like this by billimad · · Score: 1

      dude that is suuuuch a bill gates saying ;-)

    5. Re:Mixed Feelings about news like this by Godeke · · Score: 2, Insightful

      I can understand your mixed feelings. Personally, I use open source extensively and have released some minor contributions to those projects I use. I think in the long run, it is a slow moving ball of snow at the top of a very large mountain: it doesn't look like much sometimes, but it will continue to roll and gain size and speed.

      That said, the commercial prospects around it will always be running madly on top of a rolling ball of snow (to continue with and strain the analogy). Some might manage to remain on top for a bit, but eventually they will bet rolled over and become part of the main bulk, rolling down the hill.

      In the end, a huge amount of general purpose software will be subsumed by the bulk of our rolling ball, and all will benefit from it. But to build a business (that isn't consulting based) on it seems worse than building on a house on a bed of sand... it's building a house on a rolling snowball (OK, now I just *snapped* the analogy in pieces).

      --
      Sig under construction since 1998.
    6. Re:Mixed Feelings about news like this by jared_hanson · · Score: 1

      I understand your concern, but there are many ways to look at the issue. First, Red Hat spent very little time on eCos. It was aquired when they bought a company, Cygnus I believe.

      Presumably, Cygnus was aquired more for their Linux solutions and experience, and eCos was sort of something that came along. I always saw it more as a hindrance to Red Hat. Red Hat had always been strictly Linux based, and now they had to justify this side project and make it fit with their business strategy. They tried a couple of different things (cell phones, etc) but it all seemed very contrived, especially since that effort could have been put into Linux.

      So, now they are jettisoning this project, which should let them get back to their core strategy. At the same time, they are giving back to the community so the effort was not a total waste.

      --
      -- Fighting mediocrity one bad post at a time.
    7. Re:Mixed Feelings about news like this by ams001 · · Score: 1
      To be fair, I believe Red Hat did the right thing in donating the copyright to the FSF. It is good for the project and hey, Red Hat and the FSF even generate some positive PR out of it.

      I am not surprised that Red Hat and the FSF made this announcement as if it was their idea, since it was their agreement that eventually made this possible, but it was the eCos maintainers and community that wanted this to happen. The maintainers first negotiated with the FSF to accept public assignments of eCos after considering various alternatives, along with several requests to Red Hat to contribute the copyright to a not-for-profit organisation. You can read the start of the negotiations in the eCos maintainers mailing list here

      In reality the eCos project was never discontinued as many incorrect postings suggest. The original developers formed eCosCentric to continue providing commercial support and the community using and supporting eCos continued to grow. The public version was also moved away to a sourceware address as Red Hat which was concentrating on Linux and the Linux Enterprise and moving away from the embedded space. (Red Hat still host the sourceware site which is also home for many other FSF and open source projects -gcc, gdb, gcj, etc - mostly from the Cygnus era.)

      Red Hat effectively gave up control of eCos when it laid off the eCos group as the original developers and maintainers continued to work on eCos in the public version. With only 1 internal maintainer left to support existing customers, the public version of eCos soon surpassed the version held entirely by Red Hat. Rather than fork the code base or split copyright/ownership between Red Hat and the maintainers and to protect eCos against the SCO's of this world, the eCos mainatainers and community decided to push for Red Hat to assign ownership of eCos to the FSF. So the right thing for eCos finally happened IMNSHO :-)

    8. Re:Mixed Feelings about news like this by Beowabbit · · Score: 1

      Well, if Red Hat takes actions that ultimately help level the playing field, even if those actions involve giving stuff away, long-term it might help Red Hat's profitability. MS didn't give away IE out of altruism; they thought it would cut the legs out from under Netscape and ultimately give them another market segment where they could leverage monopoly power, and they were right. If giving away the copyright to ecos helps prevent WinCE from taking over the embedded market, that might enable Red Hat to compete down the road in areas (including outside the embedded market) where they otherwise couldn't. (Of course, this is sort of irrelevant in this case, since ecos was open-source to start with. But my point is that giving stuff away can be a sensible thing to do from a competitive point of view, as well as from a moral point of view.)

    9. Re:Mixed Feelings about news like this by stomv · · Score: 1

      I bought x (x < 1000) when it was $3.60 a share. This wasn't a financial investment. This was a show of support -- financial activism, if you will.

      The way I see it, if folks that believe in open source software start to buy up some stock in companies that support open source software (directly or indirectly), than those companies will get a bit of a boost in share price. Who cares?

      Welp, in the case of Red Hat (at $4 a share), boosting the price by even a few percentage points helps keep it out of penny stock territory, and brings it on the radar of more and more investors. A little momentum, a good press release, and sure enough... the stock is close to $20 a share now. Just like nearly all open source programmers are contribute a drop or two into the open source ocean, a single investor tacks on minisucle fractions of a penny to share price. While in OSS development many eyes make bugs shallow, on Wall Street many investors can collectively drive the price of the stock.

      So, 5% of my portfolio consists of stocks that are entirely political -- solely to support open source companies. I don't seek to profit from them, although they tend to make money anyway if the trades are timed well. If all /.ers with jobs did the same, we could have a collective impact on Wall Street; the impact would significantly benefit the software in which we believe.

    10. Re:Mixed Feelings about news like this by jifl · · Score: 1

      I'm not able to go into details, but be very very surprised in that case :-P.

      The eCos copyright is zero value to Red Hat now, but it was valuable in 2002. A big reason it isn't now is because the eCos maintainers themselves have not assigned their code to Red Hat (even though other contributors have), and so the current source base is a mixture of Red Hat copyright and maintainer copyright code. As a result, Red Hat no longer really derives any benefit from being (part) copyright owners as they cannot unilaterally change the license. They could only change the license on their two year old source base for which they have full copyright.

      The eCos maintainers will of course be assigning all their copyright to the FSF now.

  17. What has really changed? by pavon · · Score: 5, Insightful

    I'm not certain what effect if any this has on the development of the software. To correct several misinformed posts: As the article mentions Red Hat stopped development on the project in 2002. The community continued which is why you see new releases after then. Second, the software was already open source - the licence has not changed. What has changed is that they given copyright over to FSF. The reason for this is that it is easier from a legal standpoint for the copyright of a project to be held by a single entity who can defend the entire project rather than each little peice being copyright of the respective authors. Since Redhat was no longer actively developing eCos, it made since for them to turn over the copyright to someone else. But unless people were resistant to contribute because RedHat still maintained copyright, I don't see how this will give the project new life. What may help more is having the fact that the project has a new maintainer (and the front-page slashdot article won't hurt either ;)

  18. The problem with QNX by Anonymous Coward · · Score: 1, Insightful
    The problem with QNX, of course, is that it is not Free.

    Maybe hacking eCos will give us the first "high powered, rock-solid and truly Free" embedded OS.

  19. In my experience... by AKAImBatman · · Score: 2, Insightful

    ...Red Hat has been a decent company. They usually make their stance clear and try to be honest at all times. That being said, their product distribution methodology could use some work. They have burned customers time and time again by distributing pre-release software that lacked polish. This would tend to result in oddities in their OSes such as USB mouse lockups, GNOME menus that lose their icons when installing user icons, kernel versions that are unsupported by hardware drivers such as NVidia (thank God NVidia found a way to fix that), and installations that randomly self-destruct. While I understand the pressures of the market place, a more stable codebase would inspire much more confidence in their customers.

    1. Re:In my experience... by williamhooper · · Score: 1

      OMFG, where is the "Troll of the year" mod?

      It's Red Hat's fault that their Open Source kernel doesn't work with nVidia's close sourced drivers...

    2. Re:In my experience... by AKAImBatman · · Score: 1

      It is when they use a not-yet-released-for-public-consumption-because-it 's-still-under-development kernel. Would it have killed them to use the stable kernel?

      And it is their responsibility as an OS manufacturer to make sure the hardware works. The fact that they gave no consideration to that was a bit upsetting.

    3. Re:In my experience... by Anonymous Coward · · Score: 0

      I'm sure that $0.00 that you paid for the OS really helped them....

      loser.

    4. Re:In my experience... by AKAImBatman · · Score: 1

      I'm actually speaking as an ISV who's done a lot of work to try to add as much support for RedHat as possible. Obviously I want to deliver the best experience to my customers possible, but that's not really possible when installing icons in the foot menu causes them all to disappear! And you know who that hurts? Both of us. RedHat will catch some blame for being a crappy OS, and I will catch some blame for not providing a good user experience.

    5. Re:In my experience... by doom · · Score: 1
      ...Red Hat has been a decent company. They usually make their stance clear and try to be honest at all times.
      Yes, exactly. It's very cool that Red Hat walks-the-walk, and releases software under the GPL. But...
      They have burned customers time and time again by distributing pre-release software that lacked polish.
      Yeah, right again. Red Hat at least used to seem to feel they needed to include alpha-quality junk in their distribution in order to "stay ahead of the pack" or some such. Foisting things like "linuxconf" on newbies was just incredible. Enlightment (when they were pushing it, at least) wasn't much better.

      Red Hat announcing that Linux isn't ready for the desktop was grimly amusing in a way... it's more like Red Hat isn't ready for it...

    6. Re:In my experience... by williamhooper · · Score: 1

      That was in three public betas before being released?

      Again, how is it Red Hat's fault that nVidia's closed source driver doesn't work with their open source kernel. Additionally, how is it Red Hat's fault that nVidia doesn't support Red Hat's beta releases?

    7. Re:In my experience... by AKAImBatman · · Score: 1

      That was in three public betas before being released?

      The 2.5 kernel? In public beta? I seriously doubt that.

    8. Re:In my experience... by williamhooper · · Score: 1

      WTF are you talking about? Please provide a link to a Red Hat OR Fedora release with a 2.5 kernel.

  20. That's nice. Customers should require this. by Animats · · Score: 4, Interesting
    Big customers should require that when a company drops a software product, it goes open source. This offers the option to keep the product alive if it's needed by the customer. Such terms are occasionally seen in the embedded world, but on a single-customer basis. A standard, well-accepted contract for software escrow and open-sourcing when the product is abandoned would be a useful thing to have.

    Vendors go bankrupt, exit a field of business, or simply discontinue products all the time. Deals like this could help small vendors, providing long-term customer assurance.

    1. Re:That's nice. Customers should require this. by gregarican · · Score: 2, Interesting
      Good point. I know that some software vendors I have purchased from in the past have had clauses where their source code is held in escrow. If the company goes belly up then the customer base receives the source code out of escrow and can take off on their own with either in-house or contracted programming work.

      Most software vendors who have offered this assurance are typically smaller scale. So this idea is out there indeed.

    2. Re:That's nice. Customers should require this. by anactofgod · · Score: 1

      Big customers typically will have as part of their contract with a vendor a clause regarding the maintenance of source code/hardware designs/etc in "escrow", to be made available to the customer if the vendor ceases operation or support of the product.

      Of course, this is no real remedy, since a customer that purchased the vendor's products typically doesn't have the resources to maintain the product on their own.

      Regardless, a customer that decided to purchase a closed-source solution is probably not at-tall interested in having that solution be made open source at some future date. After all, why would one consent to a possible public kimono lifting, if one weren't absolutely sure that one's undergarments were properly cleaned and nicely mended?

      ---anactofgod---

      --

      ---anactofgod---

      "Equal opportunity swindling - *that* is the true test of a sustainable democracy."
    3. Re:That's nice. Customers should require this. by JordanH · · Score: 3, Interesting
      Uhhh... eCos already was Open Source, RedHat just held all the copyrights. Now, the copyrights are assigned to FSF.

      The difference is that users can now be assured that eCos will be released under the GPL only in the future. The copyright owner can always license software out however they want and RedHat did use a GPL-compatible license. It was already Open Source, but it wasn't already Free.

    4. Re:That's nice. Customers should require this. by EricTheGreen · · Score: 2, Interesting

      I absolutely agree that doing this would benefit any company buying software.

      But the net effect of requiring this escrow for general-use software (read: not a custom job for the client) would be to devalue most software company's assets in the event of a liquidation. When liquidating, companies look to realize as much value as possible from whatever assets they possess at the time. This usually takes the form of an IP sale.

      In such a case as you describe, no external company would be motivated to bid for a insolvent company's software assets--why, when they're most likely going to go open immediately upon formal dissolution of the original owner?

      This implied de-valuation removes a significant hedge strategy from the hands of start-ups and would be entered into reluctantly, at best, by all but the largest, most well-established companies. I wouldn't ever expect to see your idea widely adopted.

      A shame, though--it really does benefit the people shelling out those big checks for these systems....

    5. Re:That's nice. Customers should require this. by Anonymous Coward · · Score: 0
      Nice of you to read a parallel post that was already made on this in the same thread.

      Numbnuts.

    6. Re:That's nice. Customers should require this. by Anonymous Coward · · Score: 0
      back in the bad old days, i saw contracts where the source code was held in escrow (I think by an outside interest, like their bank or something) for the benefit of their customers.


      This was before the microsoft eula or fsf.

    7. Re:That's nice. Customers should require this. by Eric+Smith · · Score: 1
      RedHat did use a GPL-compatible license. It was already Open Source, but it wasn't already Free.
      eCOS most certainly was already free, at least as of eCOS 2.x. 1.x was under a different license, but 2.x was released under a modified GPL, which grants all the rights of the GPL and the additional right to distribute executables without having to distribute source code for any application software that is linked to the eCOS kernel.
    8. Re:That's nice. Customers should require this. by Animats · · Score: 1

      Realistically, the IP assets of defunct software companies typically have very low value. Yes, there are IP liquidators, but the number of "back from the dead and profitable" success stories is very, very low.

    9. Re:That's nice. Customers should require this. by EricTheGreen · · Score: 1

      I will have to gather some data points to back this up, but my impression is, successful or not, quite a bit of software IP and money change hands during liquidation, so I stand by my original assertion.

      Given enough time, some of these products end up becoming the software equivalents of the unwanted fruitcakes we receive in December, constantly being bounced from one insolvent company to another.

      You're right they may not blossom post-liquidation. But there's still plenty of people willing to take the chance for (to them) reasonable prices. And post-liquidation-release source escrow would pretty much destroy any value to be gained from such transactions.

    10. Re:That's nice. Customers should require this. by JordanH · · Score: 1
      Well, technically, it was under a very slightly modified GPL, which was "GPL compatible". Being GPL compatible doesn't really make you Free.

      I'm not trying to quibble here, for all intents and purposes it might have been Free.

    11. Re:That's nice. Customers should require this. by Anonymous Coward · · Score: 0

      Actually, companies would buy the software assets specifically to keep them closed. Which might, in some cases, increase the value of said assets.

    12. Re:That's nice. Customers should require this. by phr1 · · Score: 1
      Actually, it was already Free (according to the FSF). GPL software is a subset of Free software. Anything GPL-compatible is also necessarily Free. There are even some GPL-incompatible licenses which are still Free but the FSF advises against using them.

      Full definition: FSF Free Software Definition.

    13. Re:That's nice. Customers should require this. by EricTheGreen · · Score: 1

      Except that every escrow agreement I've ever worked with specifies that should the business entity being contracted with by the buyer should cease doing business, the escrow would be unlocked. Just transferring ownership of the asset would not satisfy the "ongoing concern" language of these agreements. So they'd still open up anyway.

    14. Re:That's nice. Customers should require this. by Eric+Smith · · Score: 1
      If software covered by the GPL is "Free", surely software that is covered by a license that gives the user all of the rights the GPL would, plus some additional rights, would also qualify as "Free". It certainly provides all four freedoms the FSF defines for a Free software license.

      Whether the eCOS modified GPL is "GPL-compatible" is irrelevant to determining whether it is "Free". For instance, the original BSD license is considered by the FSF to be Free but not GPL-Compatible, as are a whole list of others. (The newer modified BSD license is, however, GPL-Compatible.)

    15. Re:That's nice. Customers should require this. by JordanH · · Score: 1

      Agreed. I thought "Free" (as used by RMS) == GPL, but I've been educated. Thanks.

    16. Re:That's nice. Customers should require this. by burns210 · · Score: 1

      no, the customer should demand that they get a copy of the code for personal use, so that they may support the product themselves if the source comapy goes down or discontinues the product. The customer should be able to use the code only for personal use within the company, and should not be able to use that code in any other product.

    17. Re:That's nice. Customers should require this. by Animats · · Score: 1
      The worst case is for customers of "application service providers", one of the bad ideas of the dot-com boom. See this article on how to survive the bankruptcy of your application service provider. That's a situation in which software escrow is almost mandatory. If you've outsourced a key business function to an ASP, and they go under, you need both the correct contractual terms and software escrow to survive.

      For a good laugh (assuming you're not an ASP user) see ASP news. Lots of happy talk about how, even though 2002 was a bad year, 2003 will be really great. There don't seem to have been any updates for a year or so. Many of the 2002 stories involve bankruptcies.

      Any ASP customer without a software escrow agreement in place is taking a big business risk.

  21. Abandonware != transfer copyright by genericacct · · Score: 2, Informative

    This isn't abandonware in the traditional sense, where copyright is "relinquished" into the public domain. Rather, they are transferring the copyright to another organization, for them to retain copyright and re-license as they see fit. Assuming they GPL it, the code would be distributable and enforcable accordingly.

  22. eCos use, "abandonware", etc.... by DavidNWelton · · Score: 1

    First of all, let's say this loud and clear:

    eCos is not abandonware!

    Development has continued throughout the project's life. I think the only thing that was in question was who the code actually belonged to. It's always been GPL'ed.

    As to what it's used for, I don't know about commercially, but I've used it for a couple of fun/learning projects: "Scivoli" - a bootable floppy image that loads jpegs from the floppy and displays the to the screen, and "ZOG", which is the ficl forth interpreter layered on top of eCos. Neither one makes much claim to being all that useful, but Scivoli especially shows off how small the OS and display code is (about 130K without much effort at all to reduce it). It would be difficult to squeeze Linux onto a floppy with a bunch of images like I have done. Both are available from http://dedasys.com/freesoftware.

    eCos is fun for those learning about OS's because it's well written code, modular, and small enough that it's easier to get a handle on than Linux.

  23. Re:QNX IS ON TEH SPOKE!!~1`` by AKAImBatman · · Score: 4, Funny

    Wasn't that nice of moderators to moderate a polite comment out of existence? So, I'll repost it at +2 and if that gets modded to -1, I'll post it again. Here's the original response:

    Here we have an example of the rarest of birds, an informed and insightful post... on slashdot.

    QNX truly is the king of kings.


    To which I replied:

    Check my posting history. I don't always get it right, but I always attempt to present an informed and useful opinion.

    And if you don't care for friendly banter, you can mark me as a foe. I'll get all broken up about it. Really. (rolls eyes)

  24. still being developed? by apachetoolbox · · Score: 1, Interesting

    looks like September 19, 2003 was the last update. What to do you mean by "stopped developing in 2002"?

  25. Re:QNX IS ON TEH SPOKE!!~1`` by Anonymous Coward · · Score: 0, Insightful

    The moderation system actually discourages discussion and rewards one shot posts that leave little or no room for debate. Check out the shit that floats to the top and you'll see the trend.

  26. Re:Don't tell me you didn't expect this by AKAImBatman · · Score: 0, Offtopic

    Don't tell me you expected fair moderation here on Slashdot?

    No, but I'm well aware of what I can do about it. Moderators only have 5 points and can moderate a post only once. Reposting stuff at +2 that was at 0 and +1 respectively, gives the rouge mods a hard target to hit. Even worse, it draws attention to their poor moderation, so meta-mods who view in context will (hopefully) slam these guys.

    Now go out there and troll the hell out of Slashdot!

    Not on my watch. By God, I'll have an intelligent conversation if it kills me.

  27. Of course you can't. by brunes69 · · Score: 3, Informative

    Saying this is like saying that you can deduct your hourly wage for the time you spend volenteering att he soup kitchen after work.

    You can deduct goods, not time or services rendered. Not unless the donation of those services have a direct impact on your companies bottom line (ie, the donation nof thoe services meant lost time where you could have made profit from soemthing else ).

    1. Re:Of course you can't. by neurojab · · Score: 1

      >Not unless the donation of those services have a direct impact on your companies bottom line

      What's really interesting is that Microsoft is allowed to pay reduced taxes due to "donating" software licenses to schools. Giving the licenses away costs them nothing, increases their market share, makes their monopoly even more firmly entrenched, and yet somehow still is a tax deduction.

      It makes the tax paying public look like fools.

  28. Re:I blame the liberal media... by Anonymous Coward · · Score: 0

    Slashdotters are too young and culturally illiterate to bite on your sig troll. Maybe you should try misattributing a quote from Lord of the Rings or something like that, that would probably work. HTH.

  29. eCos wasn't GPLed. by Svartalf · · Score: 1

    It was under a different Open Source license.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:eCos wasn't GPLed. by Anonymous Coward · · Score: 0
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the United States of America

      I am not merely a "flamebaiter" or a "truth purveyor". I Do Not care what you are.

  30. One thing you didn't give consideration to... by Svartalf · · Score: 2, Interesting

    The Open Source license that Red Hat used for eCos isn't the GPL nor is it compatible with the same.

    With the FSF recieving ownership of the Copyrights on the code in question, you can bet your bottom dollar that it will be relicensed under the GPL or LGPL the moment that the ownership changes hands.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:One thing you didn't give consideration to... by Anonymous Coward · · Score: 0
      If I were RedHat, I'd make it damn sure that FSF doesn't change the license.

      Then again, I run a succesful business...

    2. Re:One thing you didn't give consideration to... by jifl · · Score: 1

      Sorry but you're wrong. (scroll down two screens or so)

      This has been the license for coming up to 2 years now.

  31. Does anyone know by 2names · · Score: 1

    how TRON would fit into this discussion?

    --
    "I'm just here to regulate funkiness."
    1. Re:Does anyone know by Paul+Rutland · · Score: 1

      eCos provides a ulTRON compatible API as well as a POSIX layer and a native HAL.

      You can use any of these to develop applications, if you don't want or need them you can cut them out of the kernel.

  32. Re:I succeeded with the engaging in floor bugle by Anonymous Coward · · Score: 0

    I like this post, very much.

    Can someone explain it please?

  33. Red Hat quit developing on it... by Svartalf · · Score: 3, Informative

    The main people working on eCos got laid off in Red Hat's small downsizing in 2002. The work you see is from the community and the company founded by the people that got laid off.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  34. Re:Don't tell me you didn't expect this by AKAImBatman · · Score: 0, Offtopic

    I read at 0. -1 has all the troll bullsh*t that's not very pleasent to read.

  35. Friendly and hostile takeovers by tepples · · Score: 1

    I wonder what licence Microsoft uses when they buy FSF.

    There are two circumstances in which a company can buy out a solvent company: 1. if the bought company agrees to the deal ("friendly takeover"), or 2. if the bought company is publicly held and the buying company has cash to burn ("hostile takeover"). The FSF is a 501(c)(3) charity, and it does not agree to being bought by Microsoft, SCO, Unisys, or any other large publisher of proprietary software. In fact, can charities be publicly held? And even if Microsoft were to take over FSF, it wouldn't be able to revoke the GNU General Public License that covers the copyrights on its already published software.

    1. Re:Friendly and hostile takeovers by Anonymous Coward · · Score: 0

      it wouldn't be able to revoke the GNU General Public License that covers the copyrights on its already published software.

      Sure they would. There's a clause right in the GPL that calls for updates at the whim of the copyright holder.

    2. Re:Friendly and hostile takeovers by Anonymous Coward · · Score: 0

      MS will simply pay Congress and teh President to pass a "GPL is Void and Unenforceable" act.

    3. Re:Friendly and hostile takeovers by Anonymous Coward · · Score: 0

      . The FSF is a 501(c)(3) charity [fsf.org], and it does not agree to being bought by Microsoft, SCO, Unisys, or any other large publisher of proprietary software. In fact, can charities be publicly held?

      According to google, 501 * c * 3 = 450 588 064 374 m / s.

      The IRS sez: "To be organized exclusively for a charitable purpose, the organization must be a corporation, community chest, fund, or foundation. A charitable trust is a fund or foundation and will qualify.[..] In addition, assets of an organization must be permanently dedicated to an exempt purpose. This means that should an organization dissolve, its assets must be distributed for an exempt purpose described in this chapter, or to the federal government or to a state or local government for a public purpose."

      And they go on to say that "The organization must not be organized or operated for the benefit of private interests, such as the creator or the creator's family, shareholders of the organization, other designated individuals, or persons controlled directly or indirectly by such private interests."

      Of course, if a charitable corporation goes commercial, worst that can happen is that it loses its 501(c)(3) exemption.

      It is possible to take over a charitable foundation without their consent; if you trick them into going bankrupt you can snap up their assets for next to nothing.

  36. mp3 players with MMUs? by Anonymous Coward · · Score: 1, Informative

    I can tell you the PortalPlayer chip doesn't have an MMU, and thus the:
    iPod (all of them, including mini)
    Samsung Napster
    Philips HD100
    Rio Karma

    don't have MMUs.

    That's a large portion of the market, and the high-end to boot. Protected memory is generally not considered overly useful in consumer products since all it does is crash you when you do something wrong. The #2 thing you don't want to do on a consumer device is crash/hang.

    Of these, none run Linux either, except for the Karma.

  37. What the hell is this? by Ayanami+Rei · · Score: 1

    What are you talking about and what does it have to do with the "liberal media"?

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  38. Another embedded OS : Inferno by DrSkwid · · Score: 2, Interesting



    A spin off from the plan9 project was Inferno.

    The 4th Edition is now released under a dual licence such that all source code is available under a Free licence (as defined by the FSF). The GPL it isn't but it brings the world of Limbo into the open.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  39. Development has been continuous by tdrury · · Score: 3, Informative

    The slashdot summary is (*shock*) misleading. Officially Redhat stopped support and laid off the eCos developers, but the core developer as well as the at-large developers have been continuously developing eCos after Redhat backed out. In fact, I didn't start developing the AT91/EB40 port of eCos until after Redhat dropped it. Commits to CVS were slow since they had to be funnelled through the former Redhat developers which were fewer and number and looking for new sources of income, but development has been continuous.

  40. Wow, deja vu ... by Anonymous Coward · · Score: 0

    Same question and same answer posted almost verbatim half an hour earlier. Has RTFA expanded to include even the Slashdot comments themselves? The original was only the 2nd post in the story and the first thing I saw when I read this thread.

  41. Re:I blame the liberal media... by Anonymous Coward · · Score: 0

    Liberal media...is it good, or is it whack?

  42. Re: Semper non sequitur. by Psykechan · · Score: 1

    It looks like MS Office has found a way to spread it's
    gibberish by posting as an AC to /.

    I'm surprised I hadn't noticed earlier.

  43. Serious question here about end-of-life support by grioghar · · Score: 4, Interesting

    Let's use Microsoft for an example, since they're so fun to pick on here on Slashdot.

    Let's say MS was to release the source to Windows 98 4 years from now. Obviously no support for the software, MS is hoping everyone has upgraded. So, IMMEDIATELY people begin ripping the code apart, seeing blatant software security issues in the code.

    Who is responsible for the ensuing chaos that results from the hacks and cracks that occur because now everyone knows where the buffer overflows are. Microsoft indemnifies themself, and then the user of the original software is left to hang.

    I can think of one good example. I'm still a big fan of Quake II, and since the code release, there have been some SERIOUS cheats developed.

    Just a thought

    --
    Can you ping me now? Gooood! | Manhappenin.Net - Things to do
    1. Re:Serious question here about end-of-life support by drinkypoo · · Score: 2, Insightful
      If Windows 98 supports ends two years from now, and Windows 98 is open sourced four years from now, anyone still using it has no excuse for not upgrading, especially when numerous commercial and noncommercial alternatives are available. I know not everyone has scads of money to throw at upgrades, which is why they should be buying used hardware (and software - contrary to what the EULA says, first sale allows you to transfer software so long as you transfer all copies, licenses, and documentation) which is at least still supported.

      Alternatively, they can use Linux, BSD, or similar, and get something which is actively supported.

      Ultimately, the user is responsible for being educated. There's no reason Microsoft (or anyone else) should have to support something in perpetuity. The savvy users who would have something to gain from Windows 98 being open sourced have at least as much right to benefit as the clueless ones who would have something to lose have the right to benefit from it remaining closed. HOWEVER, there are two reasons why it still makes more sense to be on the side of the open-sourcers. One, security through obscurity is no security. This is a truism. Two, the code (most of it anyway) belongs to Microsoft. If you don't want to be boned by Microsoft, don't do business with them. Your average computer user's needs (Office, web browsing, media playing, and solitaire-playing) are met more than adequately by Free/free operating systems and applications, which tend to be supported long past their apparent usefulness. However, especially as Windows 98's long sunset shows, Microsoft is very good about supporting operating systems long past the time when they should have been put to their death by any means necessary.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  44. Open source is cheaper, even if you pay by jifl · · Score: 1

    So it's open source - add them :-) Or pay someone else to add them. Unlike proprietary RTOS's, you can't get fleeced for even the smallest changes because Megacorp has the source code and you don't. Even if you want to pay someone else, you can't be charged silly prices like they sometimes do because you can always compare against how much it would cost you to do it yourself.

    Since you've used eCos, you should already have seen how modular it is, and in particular you may have seen that it is designed to allow you to add new schedulers should you want.

    What's more, being open source, it only takes one person or company to add them, or pay for them to be developed, and everyone can benefit and eCos moves forwards.

    1. Re:Open source is cheaper, even if you pay by Rysc · · Score: 2, Insightful

      What's more, being open source, it only takes one person or company to add them, or pay for them to be developed, and everyone can benefit and eCos moves forwards.

      It's probably cheaper to port your apps to Linux than to pay someone to enhance eCos. Plus, Linux has had this stuff for a while; it's tested, it's known to be stable. Any new implimentation might have inefficiencies, which adds more worries.

      I'm talking out of my ass, since I don't know eCos or any RTOS, but I'm guessing that it's a simple matter of economics.

      --
      I want my Cowboyneal
    2. Re:Open source is cheaper, even if you pay by drinkypoo · · Score: 1

      In the embedded space it becomes a question of scale. If you're just making a couple thousand units, it's probably cheaper to port to linux. However if you're going to make a couple hundred thousand units, using a more efficient operating system (which may do less, but you're giving up features you're not using, meaning you're not giving up anything important) will let you use less powerful hardware, which is cheaper. It also tends to use less power, which means either more battery life, or a cheaper battery.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  45. Re:hi by Anonymous Coward · · Score: 0

    You must be new here.

  46. Development never stopped by najay · · Score: 1

    eCos has been actively supported by the ex-eCos development team ( www.ecoscentric.com) and other developers since the day RedHat cut the team loose. It is a very nice embedded RTOS.

  47. Is the FSF the right organization for this? by Anonymous Coward · · Score: 0

    Shouldn't the eCos system be under the
    authority of the EPA?

    Captain Clueless

  48. Re:QNX IS ON TEH SPOKE!!~1`` by Anonymous Coward · · Score: 0

    So, get rid of it. Turn off comment scores in your comments prefs and browse at -1, oldest first nested. I did and Slashdot almost looks entertaining again.

  49. A current product that uses eCos by Anonymous Coward · · Score: 0

    The Rio Karma (extremely cool HD-based MP3/OGG/FLAC jukebox iPod killer) runs eCos, according to its developers- the same guys that created the Empeg/Rio Car players that run Linux. Here's Rio's site.

  50. Re:I blame the liberal media... by Morosoph · · Score: 1
    I blame the liberal media for this issue.
    too obvious.

    I didn't believe your article referenced here (now deleted) when read it, but now I do.
  51. I suspect. by shaitand · · Score: 1

    This is redhat's way of saying sorry about the Fedora thing that pissed alot of people off.

    (translation)
    I suspect this is redhat's way of donating technology they weren't making any money off of and using the Positive PR to make up for Negative PR they recieved last time they dumped liabilities onto the community.

    Either way, works for me, thanks redhat :)

  52. micro-iTRON compatibility! by neutralstone · · Score: 1

    w00! An Free Software platform against which we can create iTRON apps! (see here)

    'course, there's already an open-source (or Public Domain) iTRON OS out there, but all the source comments are in Japanese. :-)

  53. "At your option, any later version" by tepples · · Score: 1

    From the GNU GPL boilerplate text:

    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 of the License, or (at your option) any later version.

    If the FSF were to go evil, redistributors of GNU programs would have every right to fork them under "version 2 of the License". Some authors such as Linus Torvalds have already planned for such an event, removing the "any later version" verbiage from the GPL boilerplate attached to their programs.

  54. License still the same by droopycom · · Score: 1

    So this shouldnt really change anything.

    It would just be interesting to see how the FSF will _interpret_ the license which is basically a GPL with a big hole in it.

    The license is supposed to be designed for embedded application, but now that FSF is in charge it would be more difficult for companies to discuss with FSF rather than to a company like RedHat.

  55. You dont know what you are talking about. by droopycom · · Score: 1

    I dont really have experience with QNX but I have developped with both eCos and uClinux. I can tell you that you can do things a lot more custom with eCos than linux with much less overhead.

    1. Re:You dont know what you are talking about. by AKAImBatman · · Score: 1

      Don't you think it's a little presumptuous to say that I don't know what I'm talking about when you yourself admit to not understanding half the spectrum I'm referring to?

      Besides, I said before that eCos probably has a market. It just isn't a big one (i.e. niche).

  56. Re:I blame the liberal media... by FortKnox · · Score: 1

    Actually, I mentioned in a comment a bit ago I'd have a "I blame the liberal media" day where that's all I commented. I tested to see if people would laugh. Instead I get cursed at. Oh well.

    --
    Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
  57. It makes little difference... by tiger99 · · Score: 1
    The only difference this makes is that the FSF are the people who can take legal action if someone decides to violate the GPL. The copyright holder is the legal owner in that sense. It makes little or no difference as to who may use, contribute or develop it.

    Naturally, I hope development will continue, much of my interest is in smaller things like microcontrollers where this is of use.

  58. Thank you. by 2names · · Score: 1

    See Subject line.

    --
    "I'm just here to regulate funkiness."
  59. Re:I blame the liberal media... by Morosoph · · Score: 1

    It's the fault of our conservative media, I say! ;-)

  60. Re:QNX IS ON TEH SPOKE!!~1`` by NanoGator · · Score: 1

    Hopefully you understand why I now metamod all negative moderations as unfair.

    --
    "Derp de derp."
  61. Negative moderations by cubic6 · · Score: 1

    When you metamod GNAA posts, do you metamod their troll moderation as "unfair" because of principle?

    The reason we have negative mods is so things like Goatse.cx links, GNAA trolls, and random off-topic posts don't interrupt the actual discussion. You may not like the fact that some posts get negative mods, but it's for the greater good. If we didn't have neg mods and metamods, the whole place would be overrun by trolls.

    --
    Karma: Contrapositive
    1. Re:Negative moderations by NanoGator · · Score: 1

      "When you metamod GNAA posts, do you metamod their troll moderation as "unfair" because of principle?"

      No. Nothing with the n-word gets meta modded as unfair, assuming it's modded negatively.

      "You may not like the fact that some posts get negative mods, but it's for the greater good. If we didn't have neg mods and metamods, the whole place would be overrun by trolls."

      No. The trolls use anonymous posting. They're not going to get modded up, so if they stay at 0, all's good. The place will not be overrun by trolls.

      As for the greater good, the greater good is to encourage good posts. Unfortunately, there are too many mods modding badly, and metamoderation as it is today isn't doing its job to keep these guys out. They don't get your joke? -1 Off topic. Argue about the off-topic mod? -1 Off topic. Legitimately criticize Mozilla? -1 Troll. Spout off ignorant stereotypes about IE? +1 Insightful.

      The greater good is for moderation to be done to encourage more intelligent posts. Wanna get rid of the 'overrun by trolls' factor? Disable AC posting.

      --
      "Derp de derp."
    2. Re:Negative moderations by cubic6 · · Score: 1

      Agreed about the abusive mods and disabling AC, but I was under the impression that you were metamodding *all* negative mods. Thanks for clearing that up.

      --
      Karma: Contrapositive
    3. Re:Negative moderations by NanoGator · · Score: 1

      " but I was under the impression that you were metamodding *all* negative mods"

      That is exactly what my sig says and implies, and you were right to think that. Unfortunately, I am limited on sig length, plus it doesn't sound so threatening when I clarify hehe.

      For the record, I actually do read what I'm modding as unfair. But, for the most part, they're nearly all modded as unfair.

      --
      "Derp de derp."