Slashdot Mirror


Why are Free-Desktop Developers Wedded to Linux?

An anonymous reader wonders: "We have been hearing promising predictions like 'This year will be the year of Linux on the desktop' for the last decade. However, the Linux of today seems to be as far away as ever from realizing the expectations of mass adoption we once had for it, without significant growth in home usage since the late 90s. Clearly, if Linux is unable to reproduce a third of Firefox's end user uptake over a much longer time-frame, there are deficiencies with the direction the GNU/Linux/X/Gnome/KDE system has taken. Of course, almost all free software and desktop efforts and development remain unquestioningly oriented around Linux. Other free-desktop operating system projects which take different and innovative approaches like ReactOS, AROS, Mona and Syllable remain comparatively starved of developers and interest. An often cited reason for using a non-Microsoft OS is to avoid a monoculture, but free-desktop efforts have created a total monoculture around developing and promoting Linux, despite a decade of failure in supplanting Microsoft's proprietorial OSes with it. Why are free-desktop developers neglecting to consider an alternative to the penguin?"

528 comments

  1. BSD by MythMoth · · Score: 4, Insightful

    So, what's BSD then, chopped liver?

    --
    --- These are not words: wierd, genious, rediculous
    1. Re:BSD by dosius · · Score: 1

      For a lot of these devs... Yes.

      Every once in a while I try my code on NetBSD and it usually works, thank ghed, because I try to code for all systems, and not just Linux.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    2. Re:BSD by Cius · · Score: 5, Insightful

      Cliff clearly suffers from a myopic conception of FOSS systems. He also demonstrates the danger in representing an entire ecosystem of software with a single moniker. Free and open source software is not 'Linux', but Linux is free and open source software. The distinction is important. Linux is just one piece of a grand and heterogeneous domain of software. On top of that, anyone can contribute to it, take it and do what they like with it. I don't think it quite qualifies as a 'monoculture' the way that Windows does. I also find the Gnome/KDE reference amusing considering that they use completely different toolkits and libraries.

    3. Re:BSD by Anonymous Coward · · Score: 0, Funny

      Chopped liver? No.

      Dying? Yes.

    4. Re:BSD by Anonymous Coward · · Score: 0

      Then what's Gnome running on top of BSD or Mac OS? It doesn't exactly run great, so I'll say that both Gnome and KDE are probably developed almost exclusively on Linux (and the same is true for many other OSS apps).

    5. Re:BSD by Anonymous Coward · · Score: 1, Informative

      Huh? Gnome runs fine of FreeBSD for me.

    6. Re:BSD by dhasenan · · Score: 1, Insightful

      BSD came to the scene about three years later than Linux. That was enough of a head start.

      But the reason GNOME developers don't target most of these other operating systems is because the latter, by and large, offer a full package, including their own GUI. The question should be, where are the innovative interfaces for Linux? Qtopia? Enlightenment for Embedded?

    7. Re:BSD by PFAK · · Score: 2, Informative

      Wrong!

      BSD is a Unix derivative distributed by the University of California, Berkeley, starting in the 1970s.

      --

      Free means no restrictions, ironic the FSF's GPL forces restrictions, isn't it? What's your definition of free?
    8. Re:BSD by compass46 · · Score: 1

      "BSD came to the scene about three years later than Linux. That was enough of a head start."

      Huh?

    9. Re:BSD by novus+ordo · · Score: 2, Insightful

      I'm glad someone mentioned BSD because with BSD a company can just take *your* hard work and say screw you. At least with Linux you have the GPL that legally forces people to be mutualistic. So now the answer to why the free-desktop developers are wedded to Linux: we got screwed before that's why. Come join us when you feel the sting.

      --
      "You're everywhere. You're omnivorous."
    10. Re:BSD by Anonymous Coward · · Score: 0

      It was around about 20 years before, but the USL/BSDI lawsuit kept the open source variants from getting widespread acceptance until '94.

    11. Re:BSD by toadlife · · Score: 1

      Please name an example of a company who has taken one of the BSDs and "screwed the community".

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    12. Re:BSD by Orange+Crush · · Score: 2, Informative
      BSD is a Unix derivative distributed by the University of California, Berkeley, starting in the 1970s.

      But it couldn't come to the party until 1994 when its legal issues were finally cleared up. Linux had already gained enough momentum by then.

    13. Re:BSD by XO · · Score: 1

      Are you implying that due to the fact that the BSD operating system is licensed with the standard BSD license, that you can only write software that is BSD licensed?

      I can't believe that you think that's true, so I can't possibly fathom that you have any point whatsoever in this.

      No one built a desktop for BSD before, because BSD already had a desktop. It sucks ass, but it's there. People built a Linux desktop because there wasn't one to begin with.
          (and they all suck ass too)

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    14. Re:BSD by sofar · · Score: 1

      -- "People built a Linux desktop because there wasn't one to begin with." --

      also completely false, Linux of course ran the desktop alternatives that were available for BSD just as well, because of the very same reason you pointed out.

      I have no idea when Linux had it's first GUI desktop, but I would think that BSD had one *way* before Linux did, as Xfree86 started in 1992 (and releases as early as 1990) as a coherent project. I don't think Linux even supported X at that time yet.

      And thus, BSD had a GUI Desktop before Linux.

    15. Re:BSD by Anonymous Coward · · Score: 0

      APPLE, Microsoft just to name a few....

    16. Re:BSD by novus+ordo · · Score: 1
      Are you implying that due to the fact that the BSD operating system is licensed with the standard BSD license, that you can only write software that is BSD licensed?


      It's more like you can write software that is BSD licensed but you can just take that software as a base without either paying the authors or contributing code back. Actually you can close it off and not let the actual original author modify and use it. See the article I linked in the original post.

      Also I think you're confusing "desktop" as used in the article(?); he clearly uses desktop as a working OS not a windowing system. This goes back to the point I said: the reason people are "wedded to Linux" is *precisely* because of the license issues.
      --
      "You're everywhere. You're omnivorous."
    17. Re:BSD by mrchaotica · · Score: 2, Informative

      He said "came to the scene," not "existed." Sure, BSD has been around since the '70s, but who'd ever heard of it before Linux stole its thunder?

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    18. Re:BSD by Chris+Burke · · Score: 3, Insightful

      Free means no restrictions, ironic the FSF's GPL forces restrictions, isn't it? What's your definition of free?

      "Free to do anything except deny freedom to others" - i.e. maximal freedom for everyone, not just for you.

      In your definition of free, are you restricted from owning slaves? The Bill of Rights puts restrictions on Congress, so we'd be more free without it?

      P.S. I have nothing against the BSD license, but it's purpose is different. Arguments about it being "more free" miss the mark entirely and look at freedom only from a completely selfish perspective.

      --

      The enemies of Democracy are
    19. Re:BSD by Anonymous Coward · · Score: 0

      The Bill of Rights puts restrictions on Congress

      No, it doesn't! The Bill of Rights enumerates some of the more important rights reserved to the people. However, the Constitution strictly defines what Congress can do, not what they can't do; everything not specifically allowed them is supposed to be excluded from their power.

      Of course, they've been ignoring that inconvenience since the early 1800's, but hey, you gotta try.

    20. Re:BSD by toadlife · · Score: 1

      Apple has contributed back the BSD community, and I've never seen BSD developers express dissatisfaction with what Apple has done. Are you a FreeBSD developer? As for Microsoft, they use a few utilities (ftp/telnet/etc) that seem to be ported over from BSD, and for a very short time, used an IP stack that was derived from BSD code. They also wrote their own implementation of Kerberos from scratch (which had nothing to do with BSD, or using other's code).

      Maybe they are to you, but those examples are not particularly compelling to me.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    21. Re:BSD by toadlife · · Score: 1

      "It's more like you can write software that is BSD licensed but you can just take that software as a base without either paying the authors or contributing code back" Yes. That's the whole point of the license.
      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    22. Re:BSD by Anonymous Coward · · Score: 0

      Why is this a troll? It's actually quite insightful.

    23. Re:BSD by infaustus · · Score: 2, Funny

      It is official; Netcraft now 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 percent of all servers. Coming close 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. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying. 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 cockeyed miracle could save *BSD from its fate at this point in time. For all practical purposes, *BSD is dead. Fact: *BSD is dying

      --
      Frosty piss posts are worthless, GNAA posts are worthless and hurtful, but they are the least of this site's neuroses.
    24. Re:BSD by Chris+Burke · · Score: 1

      No, it doesn't! The Bill of Rights enumerates some of the more important rights reserved to the people. However, the Constitution strictly defines what Congress can do, not what they can't do; everything not specifically allowed them is supposed to be excluded from their power.

      Right that being the logic by which some argued that a Bill of Rights defeated the whole purpose as it should, ideally, be redundant. Nevertheless, read any of the Bill of Rights and they say "Congress shall make no law..." and that was the basis of the argument.

      Of course, they've been ignoring that inconvenience since the early 1800's, but hey, you gotta try.

      Well yeah, which is why I'm glad they put in the Bill of Rights after all. Otherwise we'd see Congress claiming that the Commerce Clause grants them the power to regulate the speech in books sold across state lines.

      --

      The enemies of Democracy are
    25. Re:BSD by misleb · · Score: 1

      BSD just isn't significantly different than Linux from a desktop user's perspective, thats all. I mean, KDE is KDE and GNOME is GNOME whether they are running on top of Linux or BSD.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    26. Re:BSD by Bob-taro · · Score: 1
      So, what's BSD then, chopped liver?
      As a matter of fact, yes. BSD basically is another flavor of linux. Specifically, it's chopped-liver-flavored unix.

      --
      Prov 9:8 Do not rebuke mockers or they will hate you; rebuke the wise and they will love you.
    27. Re:BSD by arivanov · · Score: 1

      Yep. Usually it is.

      The insane maze of dependencies brought by a monster like openoffice along with KDE or god forbid Gnome is quite hard to resolve using portage (no offence, Gentoo fans, just personal opinion). In fact certain bits of it always remain dangling.

      There was a period I have managed fairly large lot of workstations in NIS/NFS/Autofs network environment with under 20 man minutes per workstation a month using Debian. If the same lot was a portage based system this would have been nearly impossible. I had 4 BSD with considerably less complex software loads at the same time and keeping them up to date and ticking along nicely took about 4-8 man hours a month.

      If you want it "just to work", debs and to a lesser extent rpms along with their relevant frontends are clearly superior to what BSD shipped up to 5.x (I have not played with 6.x as a workstation, as a server I did not notice any difference in terms of packaging).

      In fact it is quite funny how tables turned over the years. In 1996 BSD (Free, Net and -OS) was clearly beating Slackware and Debian as a workstation. In those days my workstation was a NetBSD running on an ancient MIPS R3000 and I was way happier with it than with Slackware. 10 years later it is the exact opposite.

      Frankly, Debian BSD may have some merit (in fact, with the current state of the Linux kernel I might as well assemble one of the spare machines I got in the loft and start putting some work in it).

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    28. Re:BSD by Anonymous Coward · · Score: 0
      What's your definition of free?
      Not requiring an AT&T Unix license to run for example.
    29. Re:BSD by Overly+Critical+Guy · · Score: 1
      At least with Linux you have the GPL that legally forces people to be mutualistic.

      But according to Slashdot, copyright is evil and obsolete, and people who violate it are heroes who shouldn't be prosecuted. How do you reconcile that with your statement about the GPL?
      --
      "Sufferin' succotash."
    30. Re:BSD by _Sharp'r_ · · Score: 2, Insightful
      but who'd ever heard of it before Linux stole its thunder?


      Anyone who actually worked with the Internet or other large networks/servers in the 80s and early 90s?

      When I started my first ISP back in the days of analog dial-up, pretty much everything everyone used was a flavor of BSD. FreeBSD for most of the low budget crowd and BSDi or a similar commercial offering for the rich folks. There were some people using early versions of Windows NT for some server stuff, but Linux was not really part of the internet/server scene at the time.

      There were still some people using older main-frame style stuff, but the x86 market was BSD, with Sun/IBM/Compaq/HP/etc... mostly doing their own things at least partially based on BSD code bases.

      Even today, the most popular non-MS desktop OS has a large BSD influence in it's userland. Even MS has stolen a lot of BSD stuff over the years, so it's pretty much everywhere.
      --
      The party of stupid and the party of evil get together and do something both stupid and evil, then call it bipartisan.
    31. Re:BSD by muuh-gnu · · Score: 1

      > Yes. That's the whole point of the license.

      And also the main reason not a single desktop is distributed under this licence, and the systems using this licence never took off like the other one not using this licence.

    32. Re:BSD by _Sharp'r_ · · Score: 2

      Based on your comments, I'm going to assume that you somehow missed the advent of cvsup-without-gui and portupgrade?

      "Keeping up" in FreeBSD for me consists of running the following script (could be cron'd easily):

      > cat update_ports.ksh
      #!/usr/local/bin/ksh
      cd /usr/local/etc/cvsup/sup/
      cvsup -g -L 2 ports-supfile
      cd /usr/ports
      portsdb -uU
      cd /usr/local/etc/cvsup/
      portversion -v
      portversion -c >port_updates.sh
      echo "Run /usr/local/etc/cvsup/port_updates.sh to update all ports."

      portversion is part of portupgrade. "-c" creates a script for you to run that consists of the portupgrade command with all of your older-than-current-version ports listed in the command line.

      It could be easily much more automated, but I like to take 5 minutes and glance through the list of what packages are due to be updated so that if I have concerns over a major one (like MySQL or postfix) I can look at the release notes before running the auto-upgrade through portupgrade.

      Maintaining multiple servers is much faster, as presumably you'd have already seen the important release notes for the first server, so each additional server can consist of typing a single command to update everything.

      --
      The party of stupid and the party of evil get together and do something both stupid and evil, then call it bipartisan.
    33. Re:BSD by muuh-gnu · · Score: 2

      > But according to Slashdot, copyright is evil and obsolete, and people who violate it are heroes who shouldn't be prosecuted. How
      > do you reconcile that with your statement about the GPL?

      The GPL crweates an ecosystem where copyright is obsolete, so supporting the GPL does more "damage" to the copyright fascism, than simply ignoring some others unfree copyright.

      Supporting the GPL is a clear stance against "traditional", restrictive copyright.

    34. Re:BSD by toadlife · · Score: 1

      "And also the main reason...the systems using this licence never took off like the other one not using this licence." I'm not sure why you are trying to point this out to me. Just as the GP poster seems to have missed the point of the BSD license, you seemed to have missed the point of my post.

      As for your assertion, there were many different reasons why GNU/Linux took off in favor of BSD based OSs in the early 90's and from all accounts I've read, the license wasn't "the main reason" at all.

      Some of the reasons for linux's early success...

      * BSD was on shaky legal ground at the time because of the AT&T lawsuit, which scared many people away from it at the time.
      * The original goal of Linux was to make a free UNIX that would run on cheap desktop hardware.
      * Though it could make a good UNIX workstation, BSD was not specifically targeted towards the desktop, and (purposely?) lacked hardware support for many low-end devices. This created a barrier to entry.
      * BSD developers were not very good in the advocacy department.

      Did the license have something to do with it? Maybe. I do know that the first time I tried Linux in 1997, the license meant nothing to me. As far as I was concerned it was just "freeware". I also tried FreeBSD for the first time that same year, and to be honest I though it was just another version of Linux. This was a result of the huge amount of hype around linux on the net at the time. It's quite possible that GPL fanaticism was the force behind the linux advocacy phenomenon on the net. Like I said, I don't know because I didn't care about licenses at the time. I just wanted to experiment with my computer.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    35. Re:BSD by toadlife · · Score: 1

      It contains more FUD than insight.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    36. Re:BSD by nurb432 · · Score: 1

      Right, my words exactally.

      Plus *BSD and linux share TENS OF THOUSANDS of applications... These other alternatives dont have anywhere near that.

      Funny how far we come, where linux and bsd are considered standards and we talk about alternatives to THEM.

      --
      ---- Booth was a patriot ----
    37. Re:BSD by HomelessInLaJolla · · Score: 1

      Because the GPL is copyleft. There's plenty of material on GNU.org and FSF.org which explains the basic differences. I'll summarize: Copyrights are ways to restrict the users from doing things, copylefts are rules to follow such that you can do whatever you want.

      --
      the NPG electrode was replaced with carbon blac
    38. Re:BSD by synthespian · · Score: 1

      You neglect the real world cases, where *your* hard FPLed work ends up in a dual-licensed product, where you work for free while other people sell proprietary licenses.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    39. Re:BSD by synthespian · · Score: 1

      s/FPLed/GPLed

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    40. Re:BSD by j-pimp · · Score: 2, Interesting

      I'm glad someone mentioned BSD because with BSD a company can just take *your* hard work and say screw you. At least with Linux you have the GPL that legally forces people to be mutualistic. So now the answer to why the free-desktop developers are wedded to Linux: we got screwed before that's why. Come join us when you feel the sting.

      Maybe its not about being screwed. You obviously feel you or others have been "screwed" by people using you BSD licensed code in ways that the license clearly intended. Maybe sometimes people want to grant others the freedom to create closed source derivatives. Sometimes I want that people to have that freedom with my code. Sometimes I don't.

      For me, it depends on the project. For example, I have written a frontend to Access and SQLite files. On a side not I released a new version today. See the link in my signature. It is GPLed. I wrote this originally to teach myself C#. I then began to use it to deal with access databases and someone pays me to deal with such things. It is a tool that makes my job easier. I give it away in the hopes that it will benefit others. This costs me nothing and if I can get other to try it, I can better improve it with there feedback. Perhaps I will get a patch from someone with improvements.

      Now I have other things I would not mind under a closed source license. Most of these things are incomplete programs. For example, I have written some project and file templates for SharpDevelop, an Open Source IDE for .NET. I would very much like to know that people have used those templates in closed source code. I'd like to see my templates used to make classes that were Open Source as well, but its nice to be useful in general. I have other snippets that I will soon release on SourceForge under a BSD license. They demonstrate patterns and are personally researched and developed best practices. I hope to avoid others the trouble I have gone through.

      The BSD license was specifically developed to allow code to be used in a closed source application. Anyone that contributes to a BSD project should know this.

      --
      --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
    41. Re:BSD by mpfife · · Score: 1
      Folks, it's time to get it through your heads. Guess what the most amazing interfaces (and I'm not an apple or MS fanboy) are developed on today?

      UNIX - I'm talking about the Apple OS X and iPod interfaces.

      Interfaces are NOT primarily about the underlying open/closed sourceness - it's about really amazing *designers* (not primarily the bit-banger) who sit down and build beautiful things - works of moving art really. If you want to cry about interfaces, it isn't because of the software, hardware or if it's open-source or not. It's because you don't have insanely good design engineers and spend lots of blood-sweat and money to get it done. Look where Apple's taken Unix in just 2 years and open-source without direction STILL can't do.

    42. Re:BSD by dfunked · · Score: 1

      GPL sounds like free as in communism.

      In soviet russia, license violate you!

    43. Re:BSD by Anonymous Coward · · Score: 0

      sorry man,

      but the BSD licence is like leaving you car with the keys and the signed title in it with an ad in the paper stating as much and then wondering why you car is gone in the morning with no legal rights to do anything about it.

      personally, I think that the GPL is a better way, you share it but you don't loose it. imagine having to purchase and agree to an EULA on software you developed. I don't think so! you guys can all walk around thinking Steve Jobs is some sort of benevolent saint, but, he is a buisnessman first and foremost and to be honest if Microsoft took BSD and slapped a shiny gui on top and called it "Windows Evolution" everybody here would be outraged. freaking hippocrates, every last Mac apoplgist out there!

      sorry, went off track there....

    44. Re:BSD by toadlife · · Score: 1

      BadAnalogyGuy, is that you?

      Don't karma whore now!

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    45. Re:BSD by faolan_devyn_aodfin · · Score: 1

      Well soon you will not have to choose. I hear that the Debian folks are working on getting a Debian/kFreeBSD out the door. All the Debian packages running underneath a stable BSD core. I'm not a BSD user but I have to say having a choice will be a good thing and I hop this hits big and gets enough sway from developers that it will be able to work out of the box like Linux.

      --
      Pagan? Geek? Check out #paganism on Freenode IRC
    46. Re:BSD by Anonymous Coward · · Score: 0

      actually it is perfect, that is exactly what BSD developers are doing.

      bigcorp: hey, lets take (BSD or parts of BSD) improve on it, rename it, call it our own and sell it! plus we will get praise from the press and the "community" about how wonderful our new (OS or feature) is that we fully developed and own outright. yeah, great idea BSD devs!

    47. Re:BSD by Baloo+Ursidae · · Score: 1

      I thought BSD quit doing the job operating those systems, changed his name to Kenny and started going to school in Park County, Colorado.

      --
      Help us build a better map!
    48. Re:BSD by Breakfast+Pants · · Score: 1

      No way! As the poster says linux fails because of "a decade of failure in supplanting Microsoft's proprietorial OSes with it". BSD succeeded on that count. So did ReactOS, AROS, Mona and Syllable. I agree with the poster--why stick with a loser when we have had 5 successes?

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    49. Re:BSD by arivanov · · Score: 1
      multiple servers - servers are easy. On average, the number of distinct function specific packages on a server is no more than a 30 and BSD makes a perfect server.

      I am are talking about workstations in the GP, not servers. So does the article (which asks the question "why do free desktop developers stick with linux"). On average, a developer workstation requires 300+ distinct packages if it is also used as a main office machine.

      Maintaining something this size using ports is unfeasible. By the time you have turned around someone has checked in a port somewhere which breaks dependencies to bits. Debian (and hence Ubuntu) are one of the very few environments which maintain a mess of this size in a consistent manner. RedHat does not have some of the common developer environment choices so you often end up having to package locally or distribute in /usr/local. So it is a bit more effort. BSD, Gentoo - no. Just resolving dependencies on a security update to one of the packages via portage may take a day or so every time it happens if the sysadmin is also a qualified developer.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    50. Re:BSD by Eivind+Eklund · · Score: 1
      The GPL is removing the freedom to use the full market system to move risk around. This is a very significant freedom that gets removed.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
    51. Re:BSD by emilper · · Score: 1

      well, I can tell you from first hand experience, there was nothing free in Communism.

      Want to imagine rather accurately what Communism meant ? Picture yourself Microsoft bought McDonalds, WallMart, GM, and Pepsico, expropriated your neighbourhood in exchange for shares in the company and asks you rent for your own house, then forbid everything else. You have to work for Microsoft, and you have to buy from Microsoft. In theory you are a shareholder, but do not have enough shares to have a vote. You don't get the dividends directly, and they are spent without you being asked on what they should be spent on.

      GPL is not Communism, but libertarianism, and, IMHO, RMS is no Commie ... only a sentimental Libertarian.

    52. Re:BSD by drsmithy · · Score: 1

      I'm glad someone mentioned BSD because with BSD a company can just take *your* hard work and say screw you.

      No, they can't. Clearly, you understand neither the spirit and intent, nor actual implications, of the BSDL.

      The code you release under the BSDL is, and always will be, available under the BSDL. Someone else can only "take your hard work and screw you" if they add some "hard work" of their own.

      Contrast to the GPL, which requires you give away your "hard work", even if the GPLed code you're using is but a miniscule fraction of your project.

      It boils down to this: The BSDL exists to keep *your code* "free". The GPL exists to impose "freedom" on *other people's* code.

      So now the answer to why the free-desktop developers are wedded to Linux: we got screwed before that's why.

      Free-desktop developers are "wedded" to Linux because it's the Windows of the unix world.

    53. Re:BSD by drsmithy · · Score: 1

      Folks, it's time to get it through your heads. Guess what the most amazing interfaces (and I'm not an apple or MS fanboy) are developed on today? UNIX - I'm talking about the Apple OS X and iPod interfaces.

      Except it's not the UNIXness that makes OS X interesting, nor enables or encourages its "innovation".

      "OS X" could just have easily (and even likely) have been sitting on top of BeOS or Windows NT, and would *still* have been the platform it is today.

    54. Re:BSD by nickos · · Score: 1
      in fact, with the current state of the Linux kernel
      Why do you say that? What's wrong with the current state of the Linux kernel?
    55. Re:BSD by XO · · Score: 1

      I think the AT&T lawsuit predates Linux by many years.
      The original goal of Linux was to make something cool for Comp Sci class.
      I think the BSD people understand that Unix is entirely too complex for the average joe.
      BSD devs are, however, often cocks.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    56. Re:BSD by novus+ordo · · Score: 2, Insightful

      Yes it does impose freedom. Before I launch into this, realize that we have a different definition of freedom as pertaining to software. Where you are concerned with the code itself, being able to do with it as one pleases, I'm more concerned about people that use it. I don't want people using it that just want to take it and give nothing in return. That's essentially what I meant by them "screwing you." I respect the spirit of the BSDL but it's a little naive.

      If somebody can't be bothered to release a few patches as a thanks for letting them have a running start then I don't want them using my code. It's a way to share with the people who appreciate the gesture and hopefully they can give back, but it's more for the Tivos of the world who will just take it for granted. People are not forced to use my code. But if they want to use it, they have to respect the terms I offered. Freedom is "imposed" all around us. Open your eyes.

      --
      "You're everywhere. You're omnivorous."
    57. Re:BSD by markhb · · Score: 1

      [blockquote]Free-desktop developers are "wedded" to Linux because it's the Windows of the unix world.[/blockquote]

      I was wondering when I read the initial question, though: perhaps a better way to phrase it would have been, "Why are free-desktop developers wedded to Unix-like operating systems?"

      --
      Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
    58. Re:BSD by _Sharp'r_ · · Score: 1

      Just checked one of my FreeBSD servers and it has 88 ports currently installed. In three years of using a desktop with the full x-windows and development everything set of ports (just repurposed the machine a couple of months ago to make room for a Christmas home hardware upgrade, so I can't get an exact port count) I can recall one portupgrade failing due to a new port release. Happily, in that situation portupgrade just doesn't change anything and the next day had a new revision of the specific port that was fixed.

      Perhaps you missed that FreeBSD's portupgrade package manages dependencies both directions, to the point of being able to automatically upgrade all ports that the port you want to upgrade depends on as well as upgrading all ports that depend on the port you are upgrading, if desired? And automatically not changing anything if a dependency happens to fail to install for some reason? And automatically using binary packages or compiling from source as appropriate or necessary?

      I've been in dependency hell in various Linux distributions before over the years. Typically because someone at some point HAD to have some package that wasn't part of the "approved" set for that distribution, but was available for a mostly compatible distribution. It sucks. I don't ever want to spend hours hunting through rpm listing sites to find the "right" versions to make it all work ever again. I've never had to do that w/FreeBSD, so I'm happy. Maybe Debian/Ubuntu also has that solved, but that doesn't take anything away from the consistency of FreeBSD and the ports collection.

      --
      The party of stupid and the party of evil get together and do something both stupid and evil, then call it bipartisan.
    59. Re:BSD by Anonymous Coward · · Score: 0

      Who is this "Cliff" person?

    60. Re:BSD by Anonymous Coward · · Score: 0

      GPL is a will-imposing license. It attempts to mind-rape just like companies mind-rape employees and steal their freedom. USA laws help companies do this raping by giving them the power to claim employees' intellectual property as their's via the "work for hire" arrangement. Raping people of their intellectual property is a crime against all of humanity.

  2. NY Times says by Mantorp · · Score: 3, Funny
    1. Re:NY Times says by TheRaven64 · · Score: 3, Insightful
      --
      I am TheRaven on Soylent News
    2. Re:NY Times says by Anonymous Coward · · Score: 0

      We can thank Al Gore for that...and that other movie, "Happy Feet". Maybe if Linux changes its name to happy feet and has a robotic penguin dancing around it might catch on in the mainstream.

  3. Not really by VincenzoRomano · · Score: 4, Insightful

    It is very unlikely that developers follow Linux only.
    They support some well documented and mature standards like Gnu Libc, X window and POSIX, among others.
    Infact, for example, most of the desktop software can be compiled and run under almost all OS that comply to those standards.
    Sometimes even under Microsoft's OSs.

    --
    Maybe Computers will never be as intelligent as Humans.
    For sure they won't ever become so stupid. [VR-1988]
    1. Re:Not really by kotj.mf · · Score: 5, Insightful

      ++

      As far as I'm aware, neither the GNOME nor the KDE devs explicitly promote Linux as the sole underlying OS. The whole point of having an X-based desktop environment is to make it portable to different systems.

      The question might as well be "Why do the GNU people spend all their time developing the Linux userland tools?" The answer is they don't - Linux distributors use the GNU/GNOME/KDE stuff, not the other way around.

      Duh.

      The reason you find the Linux kernel in most free desktop systems should be pretty obvious - it's currently better at handling the random hardware that desktop users throw at it than anything else out there.

      --
      hang brain.
    2. Re:Not really by drinkypoo · · Score: 2, Interesting
      As far as I'm aware, neither the GNOME nor the KDE devs explicitly promote Linux as the sole underlying OS. The whole point of having an X-based desktop environment is to make it portable to different systems.

      Not an X-based desktop, a GTK (or Qt)-based desktop. You don't need X. There are GTK+ and Qt for windows.

      The question might as well be "Why do the GNU people spend all their time developing the Linux userland tools?" The answer is they don't - Linux distributors use the GNU/GNOME/KDE stuff, not the other way around.

      On the other hand, it does seem that a majority of GNU developers do their work on Linux. And why not? It is arguably the "best" Unix out there. Yes, other Unices have features that Linux doesn't, but I don't think any of them have as many of them as Linux has that they don't. The BSDs are very close (some closer than others) but Linux is the "kitchen sink" kernel - of course you can modularize it or just not build things into it, so don't see that as a drawback. Besides, blowing a couple more megabytes of memory to have more functionality doesn't bother many of us any more.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Not really by RAMMS+EIN · · Score: 2, Insightful

      ``On the other hand, it does seem that a majority of GNU developers do their work on Linux. And why not? It is arguably the "best" Unix out there. Yes, other Unices have features that Linux doesn't, but I don't think any of them have as many of them as Linux has that they don't. The BSDs are very close (some closer than others) but Linux is the "kitchen sink" kernel''

      What about Solaris? What about OS X? Can anybody share why they do or do not prefer one of these over GNU/Linux?

      --
      Please correct me if I got my facts wrong.
    4. Re:Not really by Nicolas+MONNET · · Score: 3

      Linux is arguably better than Solaris for the desktop, esp. as far as device support is concerned. In fact, Linux supports more devices than Windows out of the box.

    5. Re:Not really by Lussarn · · Score: 2, Interesting

      For one reason or another most OS X users aren't terribly interested in Free Desktops. As for Solaris, Sun uses a non GPL compatible license (last I checked anyways). The GPL still is the free software license to be compatible with. Suns license seems to be on purpose non GPL compatible, as it is a similiar copy-left license. I think it scares off users and developers.

      But as it is GNOME (Sun makes considerable work on GNOME) and KDE works just as good at least on Solaris so I don't know what this article is all about.

    6. Re:Not really by RAMMS+EIN · · Score: 4, Interesting

      I can tell you myself why I don't use OS X (even though I do use an iBook). Mostly because it's slow and because it's a hassle.

      It's slow mostly because it takes a noticeable time to start processes, and this bothers me, as it's something I do a lot. Also, the GUI takes up so much memory that there is less of it left to get work done with. Once this gets up to the point where it starts swapping a lot, obviously productivity is out of the window.

      It's a hassle, because, although a lot of open source software technically works on it, not all of it is readily available. At least at the time I still used it (the situation may have improved since), there were fink, darwinports, and pkgsrc, each supporting some packages but not everything I wanted (pkgsrc worked best for me, but didn't provide binaries for OS X). Having to use different package managers and having to compile things from source are terrible time wasters. The software that Apple ships is either different from what I'm used to from other *nix systems, or it's the same software, but often an older version, which caused further problems.

      Also keeping the software up to date is a nightmare when some of it is integrated with Apple's updater (which keeps pushing "updates" for software I don't have or want), some of it is integrated with some open-source package manager (fink and friends), some of it comes with custom updaters, and some of it doesn't have any update mechanism at all.

      The final straw was that Tiger broke the ext2 driver, meaning the end of sharing files between OS X and Linux. Yes, Linux supports HFS+, but the interaction between the Linux HFS+ driver and Apple's fsck has given me...bad results in the past, so I'm not going there again.

      Of course, none of this means that OS X doesn't look gorgeous and isn't a great OS if you just want to use the great software that Apple ships with it, and maybe a handful of third-party apps. However, for a command-line junkie like me, GNU/Linux beats OS X hands down.

      --
      Please correct me if I got my facts wrong.
    7. Re:Not really by arodland · · Score: 1

      1) KDE doesn't run (well) on OSX yet.
      2) OSX is funky and breaks lots of Unix conventions for no good reason (yes, even compared to Linux)
      3) IPC is sloooow.

    8. Re:Not really by orasio · · Score: 1

      I did like Solaris, but I like Ubuntu more.
      Now that Solaris is free, or trying to be free, it's worth investing time in, but again, there is not that much of a reason to do that.
      About OSX, it's not a free operating system, it would have to do lots of interest stuff in order to get some interest from me, in the form of trying it at a friends house.

    9. Re:Not really by kotj.mf · · Score: 3, Funny
      What about Solaris? What about OS X? Can anybody share why they do or do not prefer one of these over GNU/Linux?
      Yes, it really is a mystery why a GNU developer, sitting in their office at the Free Software Foundation lair, just down the hall from Richard M. Stallman, would eschew working on Solaris or OSX in favor of an open source OS. I'll get back to you when I figure it out, right here in this Slasdot article about Free operating systems.
      --
      hang brain.
    10. Re:Not really by RAMMS+EIN · · Score: 2, Interesting

      Actually, a quite some GNU software is shipped with OS X, and a lot more can be installed on it. I don't know if Solaris, as shipped, contains a lot of GNU software, but every Solaris install I've worked with had a lot of GNU software on it, and people seemed to prefer the GNU utilities over the Solaris ones. In order for all this to work, some people must be working on the GNU utilities from proprietary *nix systems. I could even imagine that, before Linux, Solaris was the major development platform for GNU, but I could be wrong there.

      --
      Please correct me if I got my facts wrong.
    11. Re:Not really by kotj.mf · · Score: 1
      Not an X-based desktop, a GTK (or Qt)-based desktop. You don't need X. There are GTK+ and Qt for windows.
      I know about ports of various F/OSS apps that use GTK/Qt libraries, but I thought for the full blown environment, you need to run X (via Cygwin or whatever.) If I'm wrong, that would be awesome - because I'm stuck with a Windows box at work for the time being.

      On the other hand, it does seem that a majority of GNU developers do their work on Linux.
      No argument there, based on my competely non-scientific and relatively uninformed opinion. If you've got thousands of individual developers working on thousands of individual projects in a "movement" that works more like an ecosystem than a corporation, I don't see how the AC who posed the original question really has much room to bitch if those individuals mostly end up settling on a de-facto "standard" that works best for everybody involved. Natural selection, baby.
      --
      hang brain.
    12. Re:Not really by tepples · · Score: 3, Insightful

      In fact, Linux supports more devices than Windows out of the box.

      But does Linux support more devices marketed to home users that are still being sold? Drivers for server devices and obsolete devices are good for increasing bullet point counts but not for having the best live-CD experience on real home PCs.

    13. Re:Not really by drinkypoo · · Score: 1
      I know about ports of various F/OSS apps that use GTK/Qt libraries, but I thought for the full blown environment, you need to run X (via Cygwin or whatever.) If I'm wrong, that would be awesome - because I'm stuck with a Windows box at work for the time being.

      I don't know how GNOME is doing but part of the Qt4 project is to provide a complete KDE environment for Windows.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    14. Re:Not really by TheRaven64 · · Score: 2, Interesting

      If you like Solaris and Ubuntu, then maybe you should try Nexenta; it's a Debian/Ubuntu-based system running atop OpenSolaris. You get a system that looks and feels a lot like Ubuntu, but has an OpenSolaris kernel, complete with ZFS, DTrace, Zones, etc.

      --
      I am TheRaven on Soylent News
    15. Re:Not really by MoxFulder · · Score: 3, Interesting
      I could even imagine that, before Linux, Solaris was the major development platform for GNU, but I could be wrong there.


      Yeah, that's probably about right. I imagine most of the GNU development was done under Solaris, NextStep, and AIX... in that order. The first time I got my grubby little 11-year-old hands on a Unix shell account, in 1993, it was on a NeXT box. Most of the utilities on that box were GNU utilities... GCC, binutils, tar, gzip, etc. I remember learning to unpack tarballs and running ./configure to build a GNU Bison package that I downloaded.

      Once I heard about Linux around 1996-ish, there was no going back. Here was a Unix-type operating system I could install on my own Cyrix 486SX PC, awesome :-)

      I haven't seen anything come along that's more versatile and all-around better than Linux. Sure, I think OpenBSD is great for ultra-secure servers, and they've been doing fabulous things with wireless driver support recently. Some Linux distros (cough, Mandrake, cough) have gotten way too far out on the bleeding-edge features curve and had stability and configuration problems.

      But overall Linux has become everything I'd hoped it would be and more: free, good hardware support, well-documented, high performance, good community support, and UBIQUITOUS (my wireless router runs Linux, and I'm sorely tempted to put Linux on my girlfriend's iPod).
    16. Re:Not really by RKThoadan · · Score: 0, Redundant

      Well, I just did a clean install of Windows XP at home and it didn't recognize my ASUS motherboards ethernet and sound (it's about 2.5 years old now). Every Linux distro I've installed on that machine didn't have a problem with those.

    17. Re:Not really by XO · · Score: 1

      Considering that I can't get any distribution to boot and start X without mucking with it, on standard Nvidia hardware of recent age (Vanta to 6000 series), I'd say we're in pretty sad shape there.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    18. Re:Not really by XO · · Score: 1

      AIX was a major pain in the ass, back then. If you didn't have the GNU tools you couldn't compile a -damn- thing on AIX.

      BSD, Sun, and NeXT .. HP/UX and AIX were way behind in GNU stuff, but it eventually did make it over.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    19. Re:Not really by Duncan3 · · Score: 1

      I haven't written OS-tied software since the mid-90's.

      Python for scripting, PHP for the web, and ANSI C for anything serious (yes C is 100% cross-platform). Usually wrapped in a a nice WYSIWYG'd GUI from MSVS or Xcode that adds a whopping 1% to devel time.

      Most serious open source projects are that way to. I really don't know too many people that care at all about the OS, as long as it's not a pain in the ass. So obviously most run OS X, some Windows, and a handful of Linux.

      x86 won the CPU wars, and DONT_CARE won the OS war. But both wars are over.

      We're 2 years into the GPU and other computation engine (Cell etc) wars now, and Apple just started the real mobile computing wars, so try and keep up.

      --
      - Adam L. Beberg - The Cosm Project - http://www.mithral.com/
    20. Re:Not really by crossmr · · Score: 3, Insightful

      you can nitpick all day. There will always be exceptions. I've had machines which worked better under windows without doing anything extra, and ones that worked better under linux without doing anything. It ALL depends on the hardware in the machine, which in the PC world varies greatly.

    21. Re:Not really by JoshJ · · Score: 1

      Solaris wasn't Free Software until recently. OS X is absolutely not Free, and probably never will be, considering Apple's ties to DRM-loving "content providers."

    22. Re:Not really by computational+super · · Score: 1

      Gnu Libc, X window and POSIX

      Speaking of which, Linux seems to work just fine for me (much better than Windows), so I haven't started beating the bushes for an alternative - however, I can't stand X-Windows. The main problem I have with MS-Windows is that it (the OS kernel) is joined at the hip with that horrible desktop with its horrible overbloated API. Although Linux isn't joined at the hip with the horrible XWindows with its horrible overbloated API, but I'm not aware of any alternatives. There are lots of desktops that run on *top of* XWindows, but the only potential replacement I've ever seen is SVGA Lib, which, like the orphan OSes in the OP, doesn't get much developer attention.

      --
      Proud neuron in the Slashdot hivemind since 2002.
    23. Re:Not really by jimicus · · Score: 1

      But does Linux support more devices marketed to home users that are still being sold?

      THANK YOU. I've been saying this for ages - "supports more devices" doesn't count for much when "more devices" is MFM hard disks, ISA network cards and other assorted stuff which simply hasn't been seen in the wild by most people for years.

    24. Re:Not really by Narishma · · Score: 1

      There is no such thing as a "Qt4 project" and only kdelibs and some applications will be ported to Windows and OSX, not the whole KDE environment.

      --
      Mada mada dane.
    25. Re:Not really by bigpat · · Score: 3, Informative

      Drivers for server devices and obsolete devices are good for increasing bullet point counts but not for having the best live-CD experience on real home PCs. Yes, the WindowsXP live CD is so much more impressive than Ubuntu Live CD! Oh wait.

      Seriously though, imagine you had to buy a Dell without Windows and just had to figure out which drivers you needed for the hardware. You will spend hours with no assurance of success, trust me. You can be damned sure that Dell makes sure that the disk they distribute with their machines comes with all the drivers for the hardware they sell you and they will only sell hardware that they know will work with Windows.

      Try one of these or these and it will be a desktop Linux that just works out of the box with the hardware that is attached to your computer, which is what matters.

      Putting the bar at the point where the OS must support the same hardware that Windows XP supports is a bar too high for any OS. Just as there is no way Microsoft would allow itself to be compared by maintaining some arbitrary parity with the hardware devices that Linux supports. I imagine there are in fact some specialized peripherals that only have Linux drivers and not Windows, but you are right that isn't the point. That way of framing the question will always puts your efforts at chasing someone else's lead.

      What Linux needs more of is more places, like the links above, to get fully integrated products that have you favorite distribution working with a full set of compatible hardware to meet your needs. And finally, all that Integration work can't make the product cost more than a few bucks more than a comparable Dell otherwise people are going to try and do it themselves like they have been, with mixed results.

    26. Re:Not really by mrchaotica · · Score: 1
      What about Solaris? What about OS X? Can anybody share why they do or do not prefer one of these over GNU/Linux?

      That's obvious: they both are, or recently were, proprietary!

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    27. Re:Not really by lys1123 · · Score: 1

      There a potential replacement called Y, though I don't see that exactly taking off at the moment.

    28. Re:Not really by penguinboy · · Score: 3, Informative

      Seriously though, imagine you had to buy a Dell without Windows and just had to figure out which drivers you needed for the hardware. You will spend hours with no assurance of success, trust me.

      Hardly. Simply go to http://support.dell.com, enter the machine's service tag, select the desired OS, and get exactly the drivers you need. Sometimes there might be two different drives for a device category (e.g. two possible NICS), but hardly anything requiring hours of work. Dell is by far the best in this category - other vendors certainly do make it much harder to find all of the drivers needed for a given system.
    29. Re:Not really by BrainInAJar · · Score: 1

      Solaris ships with a pretty huge chunk of GNU software in the /usr/sfw consolidation for those who want such a thing.

    30. Re:Not really by macshit · · Score: 2, Insightful

      "supports more devices" doesn't count for much when "more devices" is MFM hard disks, ISA network cards and other assorted stuff which simply hasn't been seen in the wild by most people for years.

      Perhaps not, but it's not very relevant actually. Linux supports a vast number of devices however you look at it, old or new. Support for extremely new hardware is always going to be an issue for non-microsoft software as long as the the device manufacturers ignore or even actively try to prevent support for it, but Linux simply has more mind-share, more developers, and more companies working with it than other free OSes, and as a result has overall better support for new hardware. In general the coverage is quite good.

      --
      We live, as we dream -- alone....
    31. Re:Not really by tepples · · Score: 1

      Try one of these [computers with preinstalled Linux] and it will be a desktop Linux that just works out of the box with the hardware that is attached to your computer, which is what matters.

      But will it work with my Microtek 4850 flatbed scanner that came with a Windows and Mac driver CD but is still "unsupported" in SANE despite my e-mails to Microtek?

    32. Re:Not really by bigpat · · Score: 1

      Sorry I meant to add in, imagine... "like it is for Linux". Sometimes my typing is slower than my brain.

    33. Re:Not really by GeorgeMcBay · · Score: 2, Interesting


      Yeah, that's probably about right. I imagine most of the GNU development was done under Solaris, NextStep, and AIX... in that order.


      Actually, a lot of the machines at the AI Lab/FSF back in that era were DECStations running Ultrix. There was at least one AIX box (hal.gnu.ai.mit.edu, IIRC) and handful of HP/UX boxes, some BSD4.3 and a smattering of SGI boxes running IRIX. Most of the Sun boxes were still running SunOS 4.x and not Solaris. There was one NeXT cube that I remember.

    34. Re:Not really by Hatta · · Score: 1

      Not an X-based desktop, a GTK (or Qt)-based desktop. You don't need X. There are GTK+ and Qt for windows.

      I can run KDE on windows? Without an X server? How?

      --
      Give me Classic Slashdot or give me death!
    35. Re:Not really by drinkypoo · · Score: 1

      Not yet, but it was announced (or at least according to slashdot, it was announced, heh) that the next version will supposedly include KDE for windows. It's NOT there yet, AFAIK. As far as I know the only way to get KDE on windows is to use an X server and cygwin. Of course, cygwin's X server is free, has a relatively small memory footprint, and I've found it to be quite good. YMMV. You can also run GNOME this way. I don't know why you'd be upset you have to use X - it integrates pretty well, even with clipboard support.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    36. Re:Not really by drinkypoo · · Score: 1
      But does Linux support more devices marketed to home users that are still being sold?

      Who cares? When you buy a device to use with windows, you look for the windows logo and you know there's compatibility. Why you (and everyone else) can manage to expect to be able to treat any differently is beyond me.

      Drivers for server devices and obsolete devices are good for increasing bullet point counts but not for having the best live-CD experience on real home PCs.

      I assume you meant something other than live-CD, because windows doesn't offer a Live CD. You can make one, but that is not at all the same thing.

      Perhaps you meant "out of the box" experience. In which case you may be right. However, if the user is willing to purchase hardware based on linux compatibility as they do when they purchase hardware for windows, then there should be no problem at all.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    37. Re:Not really by bigpat · · Score: 1

      But will it work with my Microtek 4850 flatbed scanner that came with a Windows and Mac driver CD but is still "unsupported" in SANE despite my e-mails to Microtek? You youngsters don't seem to remember the days when driver support for MacOS was few and far between. The point is that Apple stepped in and either provided themselves or worked with third party companies to provide competitively priced alternative peripherals that were guaranteed to work. The test for MacOS wasn't 'does every peripheral work with MacOS?', it was rather 'is there an option for a peripheral that we know will work with MacOS?'.

      When I switched from Mac to Windows, I had to leave many of my peripherals behind. Why should it be any different with Linux? Sure that means that there are a lot of people with very expensive hardware that won't be able to just switch and expect seamless integration with their existing peripherals, but if we look at Linux rather as a future purchasing decision rather than just something to throw on old hardware, then it is more important to just have a collection of devices that will just work well out of the box, rather than to try and make every possible combination work just like Windows.

      Right now there lacks a good certification program for third party Linux drivers that a vendor could just put some logo on the box, which could make a compelling selling point. I submit that if there was such a program then there would be little reason for most peripheral makers not to do it, but more importantly the many thousands of us that really hate Microsoft Windows would no longer have a good excuse not to drop it like a bad habit. I look for Linux compatibility, not because it is currently running my primary desktop, it isn't, but I look for compatibility so that some day I might be able to make the switch and never look back.

    38. Re:Not really by Brandybuck · · Score: 1

      GNU libc is not a standard. It's used in Linux and that's it. (Hurd doesn't count for too many reasons to go into). GNU libc is *not* used in any other Free Software operating systems, except as part of a Linux compatibility layer. BSD systems have their own libc, Solaris has it's own libc, etc.

      --
      Don't blame me, I didn't vote for either of them!
    39. Re:Not really by Mr.+Shiny+And+New · · Score: 2, Interesting

      Actually, when I buy a device, I just expect it to work with Windows. I don't think I'm alone in this; any device I buy off-the-shelf for home use I just expect 100% compatibility with whatever the latest version of Windows is. The only time it would even cross my mind that a device might not work with the drivers in the box is if the device is quite old and a new version of Windows was released, or if the device is specifically marketed as a Mac device, with Mac colours and the Apple logo on it. But otherwise, it had better damn well work on Windows or I'm likely to ask for a refund.

      All this assumption, and I KNOW of different OSes and hardware compatibility, etc. But, like it or not, Windows is a de facto standard, so a device can be honestly claimed to not work if it doesn't work with Windows.

      All this aside, when I buy a device I also do my homework to see if it will work in Linux, and that can be a difficult and annoying process. Try buying a scanner sometime when you are looking for specific features that are only found on certain models of scanners. You have to browse the web looking up names of scanners, and their feature sets, until you find the scanners that will meet the functionality requirements. Then you have to cross-ref this with the Sane list of supported devices, which uses European model names for scanners and has some scanners listed as supported with reduced functionality. Then you gamble on a scanner's supported functionality matching your needs, and you also gamble on the scanner's functionality actually working as advertised by Sane. (Not to bash the Sane guys, they do good work but scanning is may latest hardware issue). Repeat this process for all hardware you wish to use, and consider that you can't upgrade some drivers in your Linux system without upgrading the kernel, which can be a problem.... ugh. Frankly the whole situation is annoying.

    40. Re:Not really by wall0159 · · Score: 1

      I have to agree with you. I have an iBook with Tiger, and I love it. But it's the little things - package management in Linux is so much better. There aren't problems cutting/pasting in Linux (Aqua/X11 in OSX is still a little odd sometimes).

      Having said that - I'm running recent Gnome on an X2 AMD64 with 2gb RAM, and it doesn't feel fast! My 800 Mhz G4 feels just as quick, in general.

      But horses for courses - open source programs, packaged for Aqua (eg, Adium, VNC, LyX) are, in general, fantastic.

      OSX is certainly a wonderful OS, but I feel like some of the more powerful aspects of the OS are obfuscated. I'm quite comfortable mucking around in /etc in Linux, but I wouldn't do it in OSX!!! ;-)

    41. Re:Not really by jimicus · · Score: 1

      Support for extremely new hardware is always going to be an issue for non-microsoft software as long as the the device manufacturers ignore or even actively try to prevent support for it, but Linux simply has more mind-share, more developers, and more companies working with it than other free OSes, and as a result has overall better support for new hardware. In general the coverage is quite good.

      TBH, I don't see too much of an issue with core hardware - graphics cards, network cards etc. Support may be a little shakey for very new hardware, but it's not new for long. Though wireless can be a bit of a pain.

      Where I do see an issue is with specialised software (think accounting, payroll - "write your own or pay someone to" doesn't tend to sit very well with an FD who knows damn well he's going to have to retain someone for maintenance and support anyway, and he'd much rather go with a known evil than face something totally unknown) and peripheral devices - scanners, printers, graphics tablets, that sort of stuff. A particular model of scanner is frequently much less common than a particular model of graphics card - and if it's less common, there are fewer people prepared to work on a Free driver and there's less incentive for the manufacturer to sponsor one. Printers are becoming less of an issue these days, and no sane business is buying the cheap nasty £50 jobbies which cost less than their own toner cartridge and are tied to Windows, but the same can't be said for a lot of other stuff.

    42. Re:Not really by tepples · · Score: 1

      When you buy a device to use with windows, you look for the windows logo and you know there's compatibility. Why you (and everyone else) can manage to expect to be able to treat any differently is beyond me.

      We are already being treated differently. Why don't I see any boxes with a cute little penguin in the corner?

      Perhaps you meant "out of the box" experience.

      I deliberately avoided the term "out of the box experience" because Microsoft uses that to refer to something very different.

    43. Re:Not really by darth_linux · · Score: 0

      i agree. i believe cross-platform software (as evidenced by growing web-based software) to be very important in the future of computing. This will push developers to learn to code in a non-proprietary way. /* flame Long live Qt!! end flame */

      --
      Power to the Penguin!
    44. Re:Not really by Hooya · · Score: 1

      yeah, http://support.dell.com/ worked out great when, as i had the dell install CDs in hand, i proceeded to reinstall windows only to discover the NIC wasn't supported out of the box.

      honestly, there are times when linux doesn't support things out of the box (wireless cards, nvidia cards etc..). but there are times windows doesn't support things out of the box either. can we stop this pissing contest already?

    45. Re:Not really by pecosdave · · Score: 1

      Of course the ones that work better in Windows do so because those systems are full of cheap hardware that offload ROM code to the driver.

      --
      The preceding post was not a Slashvertisement.
    46. Re:Not really by Bishop · · Score: 1

      MacOS X is almost but not quite Unix. To a user the differences are minor and likely don't matter. To a programmer some of the differences are quite big and problematic. As a simple example the filesystem layout is completely different.

    47. Re:Not really by pasamio · · Score: 1

      I had no issues, I just used the vesa driver on my 6600 until I grabbed the proprietary binaries and installed them. You don't get 100% of features but its a start on things and gets you a graphical desktop.

      --
      I always wondered where this setting was...
    48. Re:Not really by juhaz · · Score: 1

      But does Linux support more devices marketed to home users that are still being sold?

      Out of the box? Almost certainly. Last windows version being sold to home users at the moment is six years old, it doesn't support anything more recent than 2001.

      Preinstalled or counting manufacturer drivers is a different story, of course.

    49. Re:Not really by Vanders · · Score: 1

      Glibc officially supports GNU HURD and Linux. However it is also used by GNU/kFreeBSD and Syllable, both of which is Free operating systems.

    50. Re:Not really by Anonymous Coward · · Score: 0

      Considering that I can't get any distribution to boot and start X without mucking with it, on standard Nvidia hardware of recent age (Vanta to 6000 series), I'd say we're in pretty sad shape there.

      Are you saying that Linux support for nVidia cards is worse than Solaris support for nVidia cards?

    51. Re:Not really by tepples · · Score: 1

      The assumption is that people can whip out a Wii, PSP, laptop, or other device with web access and use it to browse the Internet in order to repair a primary machine. However, this assumption fails for inexperienced users and users who see no point in owning more than one computer, but those people are most likely to use the operating system that came on their own machine, be it Windows, Mac OS, or Linux.

    52. Re:Not really by XO · · Score: 1

      Guy right above you says "use the VESA drivers" .. that's great, but the distributions default to using the NV drivers, which results in an instant black screen and system lockup. So, I had to fark with the distributions before I could get that running. Then, to get the Official NV drivers (which run better than their Windows counterparts! although they don't seem to have the overclock option) up and running, I had to install the kernel headers, then the kernel source, then compile and load a custom kernel. And because I did that, I couldn't use another binary-only driver that I needed to use for other hardware.

      On your post, I can't comment ,as I am not aware of how bad Solaris support is for anything. What I am aware of, is that NVidia hardware seems to work beautifully, but requires a ton of work to get it going.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    53. Re:Not really by Brandybuck · · Score: 1

      I knew about HURD and some other misc operating systems, but I didn't want to spoil my post with a dozen paragraphs of fine print legal disclaimer.

      In terms of stable, usable, release quality operating systems with a version of at least 1.0, only Linux uses GNU libc. HURD, GNU/kFreeBSD, etc, don't count. Sorry, I don't know about Syllable.

      POSIX is the standard, not GNU libc. People who write userland software requiring GNU libc (that isn't system specific) need to be slapped.

      --
      Don't blame me, I didn't vote for either of them!
    54. Re:Not really by Anonymous Coward · · Score: 0

      Don't worry, I was just taking the oppurtunity to plug Syllable!

      You might be surprised at just how much slapping needs to be done. I've been saying for a while that where it used to be "All the world is a VAX" it has now become "All the world is Linux". It isn't just the abuse of Linux APIs but things like abusing Glib, or codebases with huge dependency trees, or build schemes that require non-standard tools. Using Perl for essential tasks is one of my bug-bears: Perl isn't in POSIX. Use it for optional stuff by all means, but don't make me build and install eleventy-billion Perl modules and their dependencies just to get your code to compile!

    55. Re:Not really by MoxFulder · · Score: 1

      Interesting! Was most of the GNU development actually done at the MIT labs? I was under the impression that even in that early era, a lot of the GNU development was done by hackers around the country and the world, communicating by mailing lists and IRC. Not so?

  4. Why? by YrWrstNtmr · · Score: 1

    Because there are basically 3 alternatives: Windows, Apple, Linux. Only one of these is Free/Free.

    1. Re:Why? by Enderandrew · · Score: 1

      Except there are more alternatives. Your three alternatives are the largest out there, but not the only three.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    2. Re:Why? by Anonymous Coward · · Score: 0

      Of those alternatives, which have support for more hardware than Linux? Which support Java, Flash (despise it, but have to have it), VMWare etc?

      Personally I'd love a viable Free alternative to the Linux kernel. Especially one with a stable ABI so it wouldn't be neccesary to recompile drivers all the time. If only there was a Debian/OpenSolaris. Hopefully Debian/FreeBSD can get more support as well.

    3. Re:Why? by MoHaG · · Score: 1

      Of those alternatives, which have support for more hardware than Linux? Which support Java, Flash (despise it, but have to have it), VMWare etc?

      Personally I'd love a viable Free alternative to the Linux kernel. Especially one with a stable ABI so it wouldn't be neccesary to recompile drivers all the time. If only there was a Debian/OpenSolaris. Hopefully Debian/FreeBSD can get more support as well.

      When it is finished ReactOS should have the same hardware and software support as Windows.

      Except maybe for hardware support, Solaris is not far behind Linux (and probably ahead with Java support)

    4. Re:Why? by ericrost · · Score: 2, Insightful

      In my experience, its because any project that wants to tap any sort of decent user base on a free OS realizes that Linux is the free OS out there that's got support. Although as pointed out before, the point of X and sub's is to be OS/Platform independent. Eric

    5. Re:Why? by LighterShadeOfBlack · · Score: 1, Interesting

      No. That's exactly the point of the article/question. There are far more than 3 alternatives, it is simply that the only Free alternative that ever gets any real attention is Linux, both from mainstream media and from open source developers.

      One of the main problems with Linux is the vast number of distributions, all subtly - and often pointlessly - different. While I can understand the reason for why this happens and why it represents what a lot of people like about Linux, you also have to understand that it is one of the reasons that prospective Windows converts don't like it. So many choices, which one should they pick? Which is better between KDE, Gnome, XFCE, etc.? They don't know, and beyond a few fanboys for each nobody else does either because in all honesty none are truly better than the other. And while that's just wonderful for the guy who knows which is best for him, it's just another choice that the clueless average guy has to make blindly and another reason for him to go scampering back to that othe OS where there's no choices, just familiarity and stuff that works (more or less).

      Unfortunately I think that if another non-Linux OS were to become popular developer-wise it might turn out the same way. More developers, more conflicting opinions, more forks. I think ultimately the succesful free OS might be one that's put together by a small core of developers who are able to make one solid desktop operating system. No "light version", no "enterprise version", no separate distributions, just one clearly branded and defined OS with all the requisite compatability and virtualisation to make other OS'es programs run on it.

      Going slightly offtopic here but I think another issue with Linux is that it's not doing enough to bridge the gap for Windows users to jump ship. It's coming from the other side of the idealogical void from Windows and it seems too self-involved with it's "I'm Free and proud" baggage to really make something that's practical for Windows users to move onto. I'm not talking about applications here, I mean little things. The filesystem of course is one thing that instantly sets the two apart, /usr, /tmp, /etc, - these mean absolutely nothing to the guy that's been looking at c:\windows, c:\program files, c:\documents and settings, since school. I realise that those folder names have changed somewhat in different versions of Windows but they're always recognizable and while no doubt some of you are saying "so what, it's not important", you're wrong, it does matter. Yes it's a tiny thing. Yes it doesn't matter in the big picture sense. But yes, it is important. The little things like this are what makes an OS feel like home to a user and if the FOSS crowd really truly want to take people away from Windows they're going to have to wake up and realise that. /someOS , /programs, /settings anyone?

      This isn't an anti-Linux rant. It's more of a Stop Thinking Outside The Box rant. Outside the box stuff scares people. Get back in the box and think how normal people think dammit.

      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    6. Re:Why? by dosius · · Score: 1

      The thing is that for a *x user, /bin, /usr/bin, /lib, /usr/lib, /etc, /usr/local are just expected to be there. This has been true since long before I was even born (1980), and isn't a Linux thing per se (why do you think it's the same damn way for all the mainline BSDs, Solaris, and all the key players in Unixland except for maybe OSX?).

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    7. Re:Why? by PopeRatzo · · Score: 2, Insightful

      Great point. I'm sort of surprised we haven't seen a stronger emergence of free OS/Application packages for particular user groups. As a producer of various media (video, music), I had high hopes for BeOS. I'm sure people who only use email and surf the web (maybe write a document now and then), would love to see a package that is geared toward those uses without all the extra stuff a basic distro of Linux has in it.

      Let's see a Balkanization of the Open Source OS community!

      --
      You are welcome on my lawn.
    8. Re:Why? by Count+Fenring · · Score: 2, Interesting

      Mayhaps they are thinking "Outside the box" because the box is a shape that is displeasing, and also is ON FIRE.



      The windows way of handling filesystems and drives is more familiar to more people, true... but it's also kind of brain damaged (Example: No distinction between Hard Drives and Partitions in the naming schema). Also, people are either A)Technically illiterate, in which case they navigate the computer by set, static procedures, thus making ANY change of directory harder, but also meaning that keeping some similarities doesn't actually help. B)Technically competant, in which case, they can learn a new directory structure pretty quickly.



      And, again. ON FIRE. A Windows box (XP Corporate) that is not running signifigant antivirus and antispyware can be locked up and owned in less than 10 seconds, remote execution through webpage. I SAW IT HAPPEN. Before I updated it, user miskeyed a search site, got a hostile webpage, and BOOM. Had to reformat.

    9. Re:Why? by JohnFluxx · · Score: 1

      You know we did this for ubuntu in the last release. We added a .hidden file which basically hid /usr etc from the user (those folder simply didn't show up in konqueror).

      Nobody liked it and it was pointless. Anyone who browsed to / (since there's no direct links to it in kubuntu) probably knows enough not to get scared by usr,etc etc
      We removed it in the next release.

    10. Re:Why? by zippthorne · · Score: 1

      OTOH, a good question to ask is why does the standard *nix file system have such terse naming? I mean, most modern shells do some kind of name completion so speed of typing isn't an issue anymore.

      Why put binaries in /bin? why not put them in /binaries

      What is ../sbin for?
      And what the hell is the difference between /usr/local/bin and /usr/share/local/bin (or is that /usr/local/share/bin or something else?)*

      *I don't remember if these are even the exact directories, only that really similar naming in that area has bugged me to the point that I can't remember.

      The point is that maybe it should be obvious where to put and find stuff because the names are intuitive. Perhaps the standard directories shouldn't even have names at all, but rather some kind of magic number, from which the names are chosen based on your choice of language.

      --
      Can you be Even More Awesome?!
    11. Re:Why? by metamatic · · Score: 1

      It's the same way on OS X too, actually.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    12. Re:Why? by NorbrookC · · Score: 1

      The filesystem of course is one thing that instantly sets the two apart, /usr, /tmp, /etc, - these mean absolutely nothing to the guy that's been looking at c:\windows, c:\program files, c:\documents and settings, since school.

      There is a Linux distro which takes that on. http://www.gobolinux.org/index.php is an alternative that makes the Linux system look a little more "familiar" to a Windows user. On another front, I'm a bit disappointed that no one seems to be touting Linspire/Freespire as a distribution. It's one of the few that's really been targeting the consumer market.

      Which is why I also think you have a point about the ideological baggage. A lot of initiatives (like the Linux Standard Base project) get bogged down or caught in the crossfire of the various faction wars. Ideological purity isn't going to move people over to Linux, it's going to be whether they can set it up with a minimum of fuss and have it work, and have the applications they want available for it. We can whine all we want about Microsoft's desktop dominance and how they strong-arm OEM's into installing it. Yes, that's true. It also means that if we want the average user to switch, we have to make it easy for them to install Linux on their own, and have it "just work." Otherwise, they're not going to bother.

    13. Re:Why? by Anne+Thwacks · · Score: 1
      I think FreeBSD is what you want. dont know about Debian/BSD but BSD is Unix as in "what Linux is (not) a clone of".

      Yes its true, Linux is Free, but not as Free as BSD! (Not a lot of people know that). Read the BSD license: Its not the GPL - The BSD licence allows you to use it to make babies or kill money or is that kill babies and make money? Anyway "the hippies did it" - only two things to came from Berkeley (UCB) are LSD and BSD (Maybe Timothy Leary said that).

      --
      Sent from my ASR33 using ASCII
    14. Re:Why? by LighterShadeOfBlack · · Score: 1

      The trouble is that Ubuntu is again Linux. And just like Windows users, Linux users have their own expectations of their environment aswell. I'd imagine that the people who didn't like it weren't the guys just converting (if nothing else they wouldn't have known the change had been made to complain about) they were the ones who'd grown to expect those directories to be visible. I believe it'll take a new (or previously unpopular) OS to really make a proper go of this and not be held back with half-measures to try and please everyone as Linux typically is.

      Bear in mind that none of my ranting here is suggesting we replace Linux or that Linux is bad, just that I don't believe it's the most effective route for a viable short-term competitor to desktop MS Windows.

      What I believe fits the bill is an OS that can basically mimic Windows down to everything but the trademarks and patents. Something that a Windows user can install and use and, barring aforementioned trademarks, not notice that they weren't using Windows anymore. It shouldn't have the multiple window managers of Linux, it needn't have better security than Windows*, it just needs to be Free, it just needs to abstract/emulate/virtualise Windows for software compatability, and simply be WindowsButForTheName. This OS will no doubt be seen as an affront to the FOSS Gods by Linux users. That doesn't matter. It's not for them. It's for Windows users. Remember that free software is all about choice; this OS doesn't have to be the greatest OS ever - in fact thats basically impossible given the "Be Like Windows" mantra, it is quite simply a choice. The first step towards breaking the Windows monopoly and for many users the first step perhaps towards Linux or another Free OS. The first step thing is important I think. The desktop Linux idea is nice but I think it tries to do too much too fast for many Windows users. Instead of thinking of Windows->PerfectFossOS as a great divide I'm proposing that the most effective way to get people across is a set of stepping stone OSes where people can cross gradually. Perhaps some never make it all the way across. Doesn't matter, so long as it's their choice.

      *: Yeah I know. Don't lynch me. I'm not saying it should be insecure by design, but to correctly mimic Windows sacrifices in security will probably be inevitable. Given that it's intention is to subvert Windows the fact that's it's not more secure isn't a problem to the World as a whole.

      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    15. Re:Why? by orasio · · Score: 1

      The admin wouldn't want you to change the names of directories.

      I use Ubuntu, and I know that you don't even need to know that stuff.

      The only directory you need to know about is your home directory. There lays your config, and your data. "Desktop" is your gnome desktop "folder", and your configuration is hidden in .* files. Administration is handled either by system tools in the case of home users, or by administrators.

      The particular case of the guy who wants to admin his own computer, but knows some things about windows, but doesn't want to take the time to learn the standards doesn't matter that much in the big picture.

      You don't need to know what the difference is between /usr/local/bin and /usr/share/bin, because if there is anything useful there, it has been setup by an administrator who knows their stuff.

    16. Re:Why? by Anonymous Coward · · Score: 0

      There are a few places in Linux to put programs yes. It's not exactly the same for all unices but pretty much.
      I only take bin as examples but the same goes for lib and others. /bin - User programs you need if you can't mount /usr (Bare filesystem files like ls, rm, mkdir) /sbin - Admin programs you need if you can't mouse /usr (mkfs, tune2fs)

      The two above should look pretty similar on any Linux box /usr/bin - Non essential (for system startup) user programs (firefox, mplayer) /usr/sbin - Admin non essential (most daemons) /usr/local/bin - Your own installed from source (Not part of package manager) packages goes here. You should never touch bare /usr with your own stuff /usr/local is they way to go.

      ~/bin - Some of us have this too. It's programs for only one user /opt - Self contained non distro packages (vmware, oracle, bought games) (Some games install into /usr/local/games), I would argue this is the wrong place, but at least it's not in distro space.

      As you can (I hope) see, all these places has advantages over the others, mostly in regard to system stability (you don't want to fuck up your distros files when compiling from source). This is somewhat daunting to grasp but nowadays it's so seldom you need to compile yourself so mostly you don't see this at all. When compiling something I mostly use --prefix=/home/username. You should always use --prefix as standard is /usr and thats always the wrong place to put your non distro programs.

    17. Re:Why? by caspper69 · · Score: 1

      You don't need to know what the difference is between /usr/local/bin and /usr/share/bin, because if there is anything useful there, it has been setup by an administrator who knows their stuff.

      You just hit the nail right on the head. Because we all know people buying a $350 computer from Dell or Best Buy have an administrator set up their computer for them...

      This is the reason Linux in its current incarnation will NEVER succeed on the desktop for the average user. The Linux kernel wrapped in another paradigm (non-*NIX) may succeed, but the way distros are put together today is not what customers want, so they speak with their wallet (and pay for something instead of taking the free/free product).

    18. Re:Why? by rolfwind · · Score: 1
      So many choices, which one should they pick?


      Present them with the two (or 3?) most popular distros and let them choose on look and feel - according to distrowatch.com those two would be Ubuntu and OpenSuse right now.

      Instead of asking that there be fewer distros, just realize that non-geeky newbs are not going to choose Gentoo or Damn Small Linux anyway and take it out of the mix until they are more comfortable.

      Anyway, I think the number of distros is a non-starter. Go into any cell phone store and you'll find at least 20 different models doing different niches and no one complains (aside how crappy they all are.)
    19. Re:Why? by cHiphead · · Score: 1

      This is a 10 year old argument and you sir, obviously have not used Ubuntu. As of the LTS release, Ubuntu is hands down the easiest OS I have ever touched for installation and average every day usage.

      Gaming isn't too bad of an issue now with automatix installing the GL video drivers (if you have nvidia), I was able to play Half-Life 2 and its numerous mods with no problem and minimal configuration for wine. Did you never have to run memmaker and edit autoexec.bat and config.sys files trying to squeeze that tiny little bit of extra memory out for a game in DOS? Did you never have to change pagefile settings in windows to improve system performance to get a game to run better?

      The ONLY thing holding linux back from a desktop point of view at this point is a lack of a standardized LDAP backend for businesses thats as retardedly easy to work with as Active Directory (from an admin standpoint). _Thats it_

      Cheers.

      --

      This is my sig. There are many like it, but this one is mine.
    20. Re:Why? by x3nos · · Score: 1

      Sounds like ReactOS to me.

      --
      /* somewhat functional - fix later */
    21. Re:Why? by MoxFulder · · Score: 1
      Except maybe for hardware support, Solaris is not far behind Linux (and probably ahead with Java support)

      That's a BIG "except"!!! Hardware support is basically the only thing that has ever held me back from using an alternative OS. It used to be video and CD burners under Linux, now those work flawlessly. Then it was printers, now my cheapo WinPrinter works flawlessly under Linux. Then it was USB keyboards and mice and joysticks, now those "just work" too. The only area where Linux really lags in hardware support these days is wireless card support.

      Basically, Linux does everything I want it to, and more. My router can run it, my cell phone can run it, my MP3 player can run it. The only thing Linux doesn't quite do right for me is wireless networking... and switching to Solaris won't help with that.

      Other than out of curiosity, why would anyone switch from Linux to OpenSolaris?
    22. Re:Why? by Xabraxas · · Score: 1

      I think FreeBSD is what you want. dont know about Debian/BSD but BSD is Unix as in "what Linux is (not) a clone of".

      Linux is more like Unix than BSD. BSD is more like..well..BSD. The two separated quite some time ago and Linux is much more like Unix of old than BSD.

      --
      Time makes more converts than reason
    23. Re:Why? by MoxFulder · · Score: 1

      I'm not sure if you're being serious or not... but I don't see division for its own sake being a terribly useful thing to try.

      There *are* domain-specific distros out there... education-centric Linux distros, LiveCD distros, system administration/rescue distros, distros aimed at old computers, distros aimed at scientific or musical applications, etc. If you want to make a stripped-down email-and-web-surfing Linux distro, why not roll your own Ubuntu-based kiosk distro like this guy did? http://idea.zanestate.edu/archives/2005/05/kiosk-i sh-ubuntu/ If it's really useful, distribute it to others.

      The free software community has a long tradition of building on successful software, and only creating something brand new when it's really become clear that a different direction is necessary. For example, the recent replacement of the venerable Init daemon with Upstart in Ubuntu (http://en.wikipedia.org/wiki/Upstart).

    24. Re:Why? by MoxFulder · · Score: 1
      Unfortunately I think that if another non-Linux OS were to become popular developer-wise it might turn out the same way. More developers, more conflicting opinions, more forks. I think ultimately the succesful free OS might be one that's put together by a small core of developers who are able to make one solid desktop operating system. No "light version", no "enterprise version", no separate distributions, just one clearly branded and defined OS with all the requisite compatability and virtualisation to make other OS'es programs run on it.


      I think you may be onto something. I believe this is basically the process used in developing Ubuntu, and I think largely responsible for its success: a lot of the development is done by a core of developers paid by Mark Shuttleworth. They've really focused on a solid desktop distro and it shows. They've got enough of a centralized structure and incentives (salaries!) to avoid the forking and bickering of some other distros.
    25. Re:Why? by Anonymous Coward · · Score: 0

      But you have to consider the opportunity cost of setting up, learning, and maintaining Linux. If the user has to spend much more time migrating to Linux than they would installing a comparatively plug-and-play system, and that time represents lost opportunities to do other things such as make money or do a hobby, then a proprietary OS makes economic sense (economic in the academic sense of the word). And yes, I will say that for many experienced users, Linux is a comparatively plug-and-play system. However, these people made the switch a long time ago and those who haven't don't have the savvy to make it look easy. Personally, I spend so much time looking for certain apps or proxies and testing them out, that I sometimes wonder if it would be more time efficient to just purchase all of my software. I am not disparaging open source in all its variants prima facie; I support it for philosophical reasons and as a learning tool and hobby. But in its current implementation, the open source universe is simply too user-unfriendly and requires too much training and special knowledge (and I think many here would be surprised to learn how many things that are "obvious" to them are not to the average PC user). I say this as a former average PC user. It makes sense that Linux has been successful in the server market, since the system administrators can do the upkeep for many people. It is a paradox that Windows, whose development is tightly controlled, has basically fended off the Linux challenge in the most diffuse computer market, the PC, while Linux, whose development is open, has been successful in a more centralized computer market, servers. I guess commercially successful software requires limiting the "user space" for day-to-day activities, either on the part of developers - leaving the user fewer options - or users - leaving the user more responsibility. And my experience with most people is that they will happily trade away responsibility for a more limited horizon.

    26. Re:Why? by massysett · · Score: 1

      basically mimic Windows down to everything but the trademarks and patents.

      ?? Give the people a choice between Windows and Windows, and they'll pick Windows every time.

      If something is a perfect knock-off of Windows except for some IP issues, why use it? Why not just use Windows? Because the non-Windows would be cheaper? You've already said that its security would be no better.

    27. Re:Why? by Kalzus · · Score: 1

      Just to point out: we would have to care about Windows users not liking it regardless of the reasons why.

      Some of us care, some of us don't. To say that the people who are trying to evangelize Linux to non-Linux users are characteristic of, say, me, would be mis-characterizing me.

      --
      "The Devil does not know a lot because He's the Devil, He knows a lot because he's old." -- unknown
    28. Re:Why? by LighterShadeOfBlack · · Score: 1

      Because the non-Windows would be cheaper? Yes. Not simply that though. Although I said it wouldn't have to be more secure than Windows I meant this in terms of policies, remember the code itself is still more capable of being secure (time for the "more eyes, more fixes" theory to be put to the test) and of course there are other benefits of free software that could be expected such as no Genuine Advantage, no more being at Microsoft's mercy to be required to install what they want you to in order to be able to install security fixes. Things like Vista's more draconian "anti-piracy measures" too. Basically, Windows without the cost and without the Evil Empire thing.
      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    29. Re:Why? by dosius · · Score: 1

      So is it safe to say "every mainstream *x" (which is, pretty much, FreeBSD, NetBSD, OpenBSD, OSX, Solaris, AIX, HP-UX, Unixware, Red Hat/Centos/Fedora, SuSE, Mandriva, Debian and Ubuntu) all uses the same basic directory structure as I delineated?

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    30. Re:Why? by LighterShadeOfBlack · · Score: 1

      True. Some people don't care about Windows users liking it. But then you also can't complain when games aren't readily available for non-Windows systems or that hardware manufacturers don't always make open source/Linux drivers. And sure you can argue all you want that companies should be doing those things regardless, but the cold hard truth of the matter is that those things are only likely to happen when Linux or another Free OS hits the mainstream and it becomes clearly financially beneficial for companies to do those things. And hitting the mainstream means enticing Windows users.

      Of course maybe you don't care about games and maybe you've never been affected by hardware compatability issues, but I'd say that you'd be in the minority in that case.

      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    31. Re:Why? by orasio · · Score: 1
      I quote myself:

      if there is anything useful there, it has been setup by an administrator who knows their stuff. If you buy the stuff in Dell, then there is nothing in /usr/local/bin.
      If there is something, it's because the admin put it there.
      No admin, no /usr/local/bin .

      Next!
    32. Re:Why? by LighterShadeOfBlack · · Score: 1

      The problem is they need someone there to present them with those options. If they don't know a guy who can do that for them then they're a bit stuck. Go into some popular PC shop and ask about Linux and chances are you'll be met by blank stares and guided towards the nearest Packard Bell or similar running Vista. OK, so there's websites like distrowatch.com that help but they all seem to assume some degree of knowledge. I'm looking at distrowatch.com right now and I don't see any clear button that says "Which OS is for me?" and leads them through a couple of simple questions and then provides them with an obvious answer or a big honking sign that says "download this if you want to replace Windows and don't really know what you're doing". Sure it's ridiculous and patronising to anyone who's ever used Linux before but you've got to consider that a the Windows user might not even be clear on what a distribution or "distro" is.

      I don't think the cellphone comparison works. Firstly because although the handsets might be different there are only a couple of OS'es on each and that's rarely even considered by the buyer. The non-technical phone user probably doesn't care about the OS running because as cellphones they're generally simplified to the point of being pretty intuitive in terms of arrow keys controlling basic menus etc., the nmon-technical user is more concerned with the fashionable phone, the one with the best camera (ie. the one with the higher Megapixel number) or the most memory. These terms are understandable (bigger number == better) and workable, unfortunately it doesn't work that way for OS distributions.

      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    33. Re:Why? by XO · · Score: 1

      For some reason, /sbin is for binaries that do not use shared libraries (you'd think sbin might be for 'binaries with Shared libraries', but its not) .

      I know that, but there's no good reason for anyone else to ever need to know that. It should just farking work.

      I'm all for your idea, have even folders have magic numbers that identify them .. that would be really awesome for an improved installer that someone needs to write.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    34. Re:Why? by XO · · Score: 1

      What's an "LDAP"? I see people talk about it all the time, but I've never met anyone who's used one.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    35. Re:Why? by XO · · Score: 1

      NTFS can be mounted similarly to a Unix filesystem.

      It would be a lot easier for people who don't have a clue, and don't need one, about file systems and partitions and drives, if all hard drives were simply attached as one volume .. (LVM ? which NTFS also supports, if I'm not mistaken .. I know Linux does, but only because IBM dumped in the OS/2 port of it)

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    36. Re:Why? by XO · · Score: 1

      You'd think if a wireless router ran Linux, that it'd support some wireless network adapters. But, you'd probably be wrong. :(

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    37. Re:Why? by MoxFulder · · Score: 1

      Well, Linux *does* support some wireless adapters very well, and those are indeed the ones used in most of the Linux-based routers. For example, my Netgear WGR614 router contains an Atheros mini-pci wireless card, well-supported by the MadWifi drivers.

      By the way, I just found this Comparison of open-source wireless drivers on wikipedia. Very handy!

    38. Re:Why? by Kesh · · Score: 1
      There *are* domain-specific distros out there...

      ... which are Linux distros. The question is, why aren't people rolling more variant OSes, rather than repackaging Linux?

    39. Re:Why? by MoxFulder · · Score: 1

      Because Linux is so flexible and modular :-)

      In its original form, Linux is basically a server OS like Unix. They've tweaked the scheduler to make it more responsive as Desktop OS. With some modifications, Linux can be a real-time OS. It has been modified to run on 16-bit processors without MMUs, so it can be an embedded OS for tiny systems. It compiles on x86, x86_64, sparc, ppc, alpha, IBM mainframes of every kind, itanium, arm, mips, and even the OpenRISC open-source-design embedded processor.

      But there *are* lots of alternative FLOSS systems in use, I think! One alternative that no one ever mentions, for some reason, is eCos. It's a modular RTOS for embedded systems. A lot of routers use it actually, I had an 802.11b router that was based on eCos. If you need real-time, and don't want the overhead of a "full" operating system, eCos seems like a great choice! (I haven't developed with it myself.)

    40. Re:Why? by jaypaulw · · Score: 1

      "significant" like the free avg antivirus and the free windows defender?

    41. Re:Why? by cHiphead · · Score: 1

      If you have ever logged into a Windows computer joined to a domain, you have used a form of LDAP directory services.

      http://en.wikipedia.org/wiki/Lightweight_Directory _Access_Protocol

      http://en.wikipedia.org/wiki/Active_directory

      Cheers.

      --

      This is my sig. There are many like it, but this one is mine.
    42. Re:Why? by tepples · · Score: 1

      What I believe fits the bill is an OS that can basically mimic Windows down to everything but the trademarks and patents. Something that a Windows user can install and use and, barring aforementioned trademarks, not notice that they weren't using Windows anymore.

      They'll notice the lack of trademarks all right: "Where's the blue E? How do I get to the Intarweb?" They'll also notice the lack of patents: "How do I play MP3s on this?" and trade secrets: "How do I play the WMAs I bought from the online music store on this?"

      it just needs to abstract/emulate/virtualise Windows for software compatability, and simply be WindowsButForTheName.

      Except by the time we're done copying the menu structure of Windows Control Panel and IE and Windows Media Player and Office and everything to the jot and tittle, Microsoft will have introduced a new OS version and everybody will be used to that. How many people trained on Windows Vista will be able to find their way around the control panel of Windows 98?

      Practically, ReactOS is the closest thing to what you ask for.

    43. Re:Why? by metamatic · · Score: 1

      There may be slight variations; /opt and /srv vs /var, /usr/spool/mail vs /var/mail, and so on. But the basic /usr /dev /etc /var /usr/local is universal to every Unix (not TM). Mac OS X just doesn't show the Unix stuff in the Finder, so as not to panic the easily spooked.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    44. Re:Why? by LighterShadeOfBlack · · Score: 1

      They'll notice the lack of trademarks all right: "Where's the blue E? How do I get to the Intarweb?" They'll also notice the lack of patents: "How do I play MP3s on this?" and trade secrets: "How do I play the WMAs I bought from the online music store on this?" I think Firefox and Opera have shown that the "blue E" doesn't have the strangehold on internet access that MS would have you believe, even for the unwashed masses. As long as it's got a decent browser like Firefox or Opera going for it and it's clearly labelled "Internet" then I don't see that as an issue. MP3s could pose a problem however there are plenty of open source projects that support them, if they can do it why not this? As for WMA, well I see that as far less of a problem, however presumably the reason someone would be using WMA's is if they're using a portable device which plays them, in which case the software/codecs installed by the device would provide the playability? With the market-dominance of WMA-incompatible iPods I don't see this as a huge issue anyway.

      Except by the time we're done copying the menu structure of Windows Control Panel and IE and Windows Media Player and Office and everything to the jot and tittle, Microsoft will have introduced a new OS version and everybody will be used to that. How many people trained on Windows Vista will be able to find their way around the control panel of Windows 98? Well IE, Media Player, and Office don't necessarily come into play here. Remember I'm talking about the OS as a whole mimicking Windows, not necessarily each and every application being cloned for it. That software could be installed and run thanks to Windows compatability if necessary. As far as taking too long to develop, it took 5 years between XP and Vista, and with what's come out of MS about future OSes smelling a lot like vapourware at this point I can see another 5 years before the next. I think that's ample time to release what I'm proposing, providing developers recognize the opportunity this OS provides for FOSS as a whole and step up to meet the challenge. Remember it'd still be under an open source licence so it's not like all open source code ever written is out the window. As far as the Windows 98 comment, why would Windows 98 be the Windows to mimic? Vista or XP seem the obvious choice.

      ReactOS may be the closest thing, I admit I haven't tried it yet. Definitely something I intend to look into.
      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    45. Re:Why? by Anonymous Coward · · Score: 0
      As of the LTS release, Ubuntu is hands down the easiest OS I have ever touched for installation and average every day usage.
      Yes, it's pretty good.

      That said, I do find it a bit disappointing that the tilt wheel on my mouse won't work with it. (It worked for a few weeks, then one day X wouldn't launch unless it was disabled.)

      And I'm not very happy with the way that gnome-terminal started crashing when I set up my second monitor. (A little googling revealed that disabling the composite extension in xorg.conf would fix that, but nobody seemed to have any explanation why.)

      And there's this weird thing where if I leave my computer alone for too long my primary display stops working properly. It goes blank except for the mouse pointer, though I can still interact with stuff behind the blankness. Restarting X fixes the problem temporarily. This only started happening today, so I haven't got round to investigating yet.

      And there was this kind of worrying thing that happened yesterday where X crashed altogether and I couldn't switch to another virtual terminal to sort things out because all input was being ignored. I do hope it's not going to make a habit of that...
    46. Re:Why? by synthespian · · Score: 1

      Do "man hier" in a Debian system, and see if it ressembles the truth, even remotely.
      Now do it in a BSD system. See?

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    47. Re:Why? by 1lus10n · · Score: 1

      Depends on what your doing. In a desktop environment ... I wouldnt. On a server I would use solaris in many places, except the lightweight "disposable" boxes like web servers. The real boxes like the DB's and application boxes get the OS that is better suited for dealing with high load, high availability. Which is solaris.

      Linux hasnt been actively developed for the server since early 2.4

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    48. Re:Why? by 1lus10n · · Score: 1

      No, you sir just missed half of his comment. A *home* user is going to use the gui apps to administer such things. Tell me that the average windows user has any fracking clue what the registry is, or what that little section of crap in the lower right hand corner is or how to edit it. Go ahead and try. Then go talk to non-technical people shopping at the local radio shack, best buy, target, wal mart, circuit city or whatever and ask them to explain it to you. Your IQ will drop a few points.

      Users dont know anything, as long as the software "works" then they dont care.

      Users dont pay for anything in their eyes, windows is included on that computer they just bought. Most people dont care enough to bother switching to another os, free or not. Switch it so linux is installed by default and they would have to buy windows and install it and you'll see the exact same thing holds true 10% do something "different" and 90% just roll with it.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    49. Re:Why? by 1lus10n · · Score: 1

      no. Its for "System Binaries" or "System Administration Binaries".
      If you doubt me, go into /sbin and do an ldd on something (ldd $foo) and look at the libraries printed, they are very much shared.

      I would buy into this whole "the user must know everythings location and purpose" crap .... if they already knew it about ... whatever they are running now. OSX, Windows or $other. Users dont know squat. The 10% of people who know something still dont know much.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    50. Re:Why? by XO · · Score: 1

      alright, call me wrong. :P

        All the non-shared Binaries tend to go into that directory, at least ones that are needed to get the system up and running, in case /lib is horked.
          Which is a good idea. I'd never really examined it, even though I've been using it for as long as it's been around.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    51. Re:Why? by PopeRatzo · · Score: 1

      "If you want to make a stripped-down email-and-web-surfing Linux distro, why not roll your own Ubuntu-based kiosk distro like this guy did?"

      THAT's your answer to someone looking for more task-specific operating systems? "Go make your own OS?" Excuse me, but the reason I'm looking for a more specific tool is because I don't really have time to make my own OS. I'm more interested in doing things than playing with an OS.

      --
      You are welcome on my lawn.
    52. Re:Why? by zippthorne · · Score: 1

      Yes, that's plenty easy if you're just going to stay with whatever's in the repositories. But suppose you want a more obscure program? There might not be a package available for your distro. Or maybe you want a feature that's on the latest build of a program that's in the repository but hasn't been updated for a while.

      In that case, the only thing to do is compile from source and/or install the binaries from, more than likely, a tar file. This is not easy for a casual user, especially with the different schemes used by the various distros. I think LSB was supposed to ameliorate this somewhat, but I haven't seen any real progress from the home-user point of view.

      On a windows box, obscure programs are installed the same way as every other program: click the .exe file in explorer. It'll either install or it can just be run from anywhere anyway.

      --
      Can you be Even More Awesome?!
  5. Because it's about freedom! by jimstapleton · · Score: 3, Insightful

    To choose exactly the same thing as they do.

    I know this will get troll/flamebait, this community does not like criticism, even though taking it into account could cause improvements.

    Seriously though, the thoughts are this:

    (1) They are enamored by the GPL license. I'll grant for certain uses and purposes, it's an excellent license, even if I don't agree with it.
    (2) Momentum - Linux is the first OSS OS to gain popularity, and it hit it off big for such things. What this means is that it has more support and developers, which provides a more feature-filled system which brings the people and culture more of what they want.
    (3) Flexibility - I'm not sure the whole background of it, partially it's the GPL, partially it's the management, but the Linux system is highly flexible in terms of development, allowing people to develop their projects how they want to. Especially at the kernel level. It may not be a coders dream environment, but it's pretty close.
    (4) UNIX Like. I know ReactOS isn't Unix like, I don't know about the others. I know BSD, which you didn't mention, but lacks 1-3 is also a Unix OS. Regardless, the Unix methidologies are very comfortable to developers because (a) they are relatively regular in setup. (b) They tend to be highly modular, making things easier to work with and build - lots of re-use of things you made or thigns others made. B can exist in other OSes as well, but it isn't as pervasive as in the UNIX environments.

    Note, there's probably a lot more to it than this, but this is what I've gathered from what I have seen and read on the various topics. and discussions.

    --
    34486853790
    Connection too slow for X forwarding? Try "ssh -CX user@host"
    1. Re:Because it's about freedom! by Je-Tze · · Score: 0

      Funny, but for the most part those aren't really criticisms.
      You've enumerated several good, solid reasons why Linux is ahead.

      --
      jz (Je-Tze)
    2. Re:Because it's about freedom! by jimstapleton · · Score: 1

      it's a criticsm if it's suggesting you are too stuck to them.

      2 and 3 are particularly the criticisms...

      2 - It's the same reason Windows is so big right now in areas where it shouldn't be
      3 - It's great for the coders, but for the people who want to use it, but don't want to code, or for the people who may be good at writing code, but lousy at reading others, it's a major deficit.

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    3. Re:Because it's about freedom! by gsslay · · Score: 1
      (1) They are enamored by the GPL license.


      Are they ever! I've lost track of the number of Linux software packages I've downloaded that have a "read me" that goes into exhaustive and loving detail about the GPL, and absolutely nothing about the installation or use of the package.

    4. Re:Because it's about freedom! by drinkypoo · · Score: 1

      Look, positive moderation! What's going on? I was modded appropriately yesterday myself. Strange things are afoot at the Circle K.

      Anyway let's talk about your comment. You are absolutely correct on all levels. As you say 3 and 4 apply to BSD as well but it's the 1 and 2 that really put on the heat. I haven't been a big fan of the GPL over time but I'm coming around too. I have to admit that it really is a sort of LICENSE OF THE PEOPLE, maybe a little overbearing in some situations, but then it's about freedom and frankly you either care about freedom or you don't. The BSD is a wonderful license if you want to effectively place something in the public domain but can't bring yourself to accept that you might not get any credit for it... but IMO it's just a half-assed half-step towards making it PD.

      The most important aspect is momentum, and what it provides. See, because linux has the momentum, it's the non-closed OS most likely to have drivers provided by the manufacturer. Because it has the momentum, and the other developers are usually writing things for linux first, if you want to play with the latest and greatest, you need to be using Linux, or be willing to do some porting which ranges from trivial to, well, non-trivial :)

      Linux is also generally easiest to install and use. I know there's some BSDs that are making it much easier these days but nothing really compares to Ubuntu. This helps with the installed base, meaning that if you develop some linux software there's already a broad and ready audience.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Because it's about freedom! by jimstapleton · · Score: 1

      3 doesn't apply to BSD, which is probably the biggest reason why it didn't get the lift-off that Linux got, even though it had a much earlier start (as an OS), and slightly earlier start (as a OSS OS), and arguably was better than Linux for quite a while in all other respects.

      The BSD people are quite strict about the code, comment and doc quality of what goes into the kernel in comparison to those who work on Linux.

      Freedom is the ability to make a choide. The GPL is *not* about freedom. It's about Openness. It makes several huge restrictions on what a person can do with GPLed software in order to keep it visible to all.

      I've found, provided you have supported, FreeBSD has been just as easy to install as Linux (though not as pretty) as of version 6. As for administration, it's a bit more work to get off the ground, but with the documentation quality, I've found it easier to get running than Linux if you want to make any modifications over the base install beyond adding users. I used RH/Fedora for four years, Tried FreeBSD 5.4, wen't back to Fedora because the installer was pretty flakey. I then was talked into FreeBSD 6.0, and within two weeks never wanted to see Linux again. I was talked into Ubuntu, tried it for a month, and after issues with it's installer breaking things, went back to FreeBSD. I gave Gentoo a try, it had the feel of FreeBSD, but portage wasn't as reliable as ports in my experience, so I moved back to FreeBSD again.

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    6. Re:Because it's about freedom! by Bogtha · · Score: 1

      They are enamored by the GPL license.

      I don't think that's remotely true.

      GNOME is LGPL, not GPL. In fact, they consider it an advantage to not use the GPL.

      KDE libraries are LGPL, KDE applications are GPL.

      XFCE uses a mixture of the GPL, LGPL and BSD licenses.

      Enlightenment uses the BSD license.

      GNUStep uses the LGPL.

      As you can see, none of the major free operating environments use the GPL exclusively, in fact half of them don't use it at all. Hell, GNOME is part of the GNU project, the FSF recommends the GPL instead of the LGPL, and GNOME ignores them and use the LGPL anyway.

      --
      Bogtha Bogtha Bogtha
    7. Re:Because it's about freedom! by orasio · · Score: 2, Insightful

      Freedom is the ability to make a choide. The GPL is *not* about freedom. It's about Openness. It makes several huge restrictions on what a person can do with GPLed software in order to keep it visible to all. Wrong.
      The GPL is not about Openness. LEt's not start a disinformation battle here.
      The BSD license and the GPL are about freedom but they choose different people to give it to.

      FreeBSD gives the most freedom to the first tier of users. The guys who get the software fromt he author have the freedom to do pretty much anything they want with it, even restricting the freedom of people they distribute the software to, or creating proprietary derivatives.

      The GPL takes some of that freedom away fromt he first tier, in order to assure that everybody who gets the software, no matter how deep in the distribution chain, gets the same freedom. So, when they distribute it, they are prevented from restricting further users, and from creating proprietary derivatives.
      In exchange, the freedom to use, study, share, improve, and modify improvements of the software, is assured for every user of the GPL software.

      The BSD license grants freedom for the first tier of users, and that's it.
      The GPL takes some freedom from them as distributors, but ensures the freedom of all users.

    8. Re:Because it's about freedom! by marcosdumay · · Score: 1

      "3 - It's great for the coders, but for the people who want to use it, but don't want to code, or for the people who may be good at writing code, but lousy at reading others, it's a major deficit."

      It is a deficit until you consider that the software that those non-coders will be using where written by coders, that like the flexibility.

    9. Re:Because it's about freedom! by timeOday · · Score: 1

      And that is why Linux beat BSD. The GPL prevented fragmentation.

    10. Re:Because it's about freedom! by jimstapleton · · Score: 1

      except in many cases the non-coders don't have the patience to deal with the lackluster documentation and go to other sources for their applications.

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    11. Re:Because it's about freedom! by chromatic · · Score: 1
      The GPL takes some of that freedom away fromt he first tier....

      No, copyright takes away freedom. The GPL gives some of it back.

    12. Re:Because it's about freedom! by Ashtead · · Score: 1

      The LGPL license allows you to use the code and also distribute it along with your own proprietary software, similar to the BSD license.

      But unlike the BSD license, the LGPL still gives the same freedoms to the next tier of users as the regular GPL, in that the source of the LGPL'd parts has to be passed on to these, and if any modifications have been done to the code that is LGPL licensed, these will also have to be passed on. The proprietary software can still have trade secrets kept inside it (thus, no source) and be legally distributed along with the LGPL'd (but not GPL'd) libraries.

      Like the regular GPL, the LGPL does not allow the code to be "locked away".

      What we see happen is that some libraries are LGPL and freely useable for everyone (proprietary or otherwise) and others are dual-licensed, (MySQL and Qt come to mind) where the free ("beer" and "speech") version is GPL-licensed, requiring compliant users also to license their products as GPL, and for those users who can't or won't do so, there is an option of licensing the libraries from their copyright holders for proprietary software use, for a charge, and with closed-source-style restrictions.

      --
      SIGBUS @ NO-07.308
    13. Re:Because it's about freedom! by Dastardly · · Score: 1

      No, copyright takes away freedom. The GPL gives some of it back. Oh be, nit picky. So, translate to GPL gives less freedom to first tier compared to the BSD license in exchange for making sure those below the first tier have the same freedoms as the first tier.
    14. Re:Because it's about freedom! by falconwolf · · Score: 1

      No, copyright takes away freedom. The GPL gives some of it back.

      Yes, copyright grants freedom. If I copyright something, I have the right, freedom, to prevent others from making money off of my efforts without paying me anything.

      Falcon
    15. Re:Because it's about freedom! by chromatic · · Score: 1
      Yes, copyright grants freedom.

      I live in the US. Our Constitution specifically mentions copyright as a specifically granted limited-time monopoly with legal enforcement. Our guiding philosophy also acknowledges the presence of certain (and unexhaustively enumerated) natural rights. I take this to mean that copyright is not a natural right.

      Your political jurisdiction and views may differ.

    16. Re:Because it's about freedom! by synthespian · · Score: 1

      Yeah, the GPL grants you the freedom to work for free for first-tier users, who then take your work and dual-license it, or sell per-seat licenses.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    17. Re:Because it's about freedom! by orasio · · Score: 1

      You are right, I stand corrected, and the first child of your post clarifies it ok.

      Aside from that, to argue with another sibling, copyright is not a right. It's only a restriction on free speech (which is actually a right), with some purpose.

      I don't think authors have a right to profit from their works, per se. They have the advantage of a monopoly, in the first round of distribution, that could even be enough, for the next wave of media, where everybody has access to the channels of distribution.
      Copyright made sense when the author needed to show his work to a distributor to sell it, in order to protect him from being ripped off.
      Now that it is increasingly easier to distribute works (not promote, but distribute) , and the channels are more easily accessible, authors can sell their works themselves, and there would be no distributors to protect them from.

      In the future, works could be produced a la Elephant Dream, raising the money based on your reputation, and then producing the work, free for everyone.
      It does work, and it could be powerful, and even make copyright useless.

      Aside from that, trademark laws, I can understand, because they protect the reputation of a company, but copyright has no actual foundation.

    18. Re:Because it's about freedom! by synthespian · · Score: 1

      All KDE libraries are licensed under the LGPL, but all KDE applications are licensed under the GPL.

      It's no wonder that Linux has not made it into the corporate desktop. If small and large ISVs cannot develop products around applications, like you can in Windows using OLE, COM and .NET, then you will never reach the ammount of integration you need in some business/corporate setting, particularly in what regards eletronic document management. I mean, you can take software for Windows, third-party, and within minutes fashion you custom built GUI for e-documents. Linux/Unix is so far behind the curve.

      Of course, you can go buy a QT license. Wait - It's cheaper if you develop for Microsoft. Plus, you get a larger return.

      The GPL has hurt FOSS software more than it helped.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    19. Re:Because it's about freedom! by orasio · · Score: 1

      The GPL doesn't do that. When you work for free on GPLed works, and release under GPL terms, you work for free for everybody, without dual licenses or per-seat charges.

      Giving your copyright to the original author has that potential, like if you contribute to MySQL and give them the potential. Of if you contribute to the FSF, and they somehow turn into an evil corporation overnight. When granting copyrights, you are always giving up all your claims on its "ownership".

      But that would be a copyright flaw, at most, the GPL has absolutely nothing to do with that.

      It's a shame that copyright is such a difficult issue.
      There is not such a thing as a FAQ about it, where people can actually learn.

      The GPL is very simple, but its consequences are difficult to grasp, because of the underlying complexity of copyrights.

    20. Re:Because it's about freedom! by Anonymous Coward · · Score: 0

      I have the right, freedom, to prevent others...

      Stopping other people from doing something that doesn't directly harm you is not a freedom but a privilege.

  6. Sour grapes by tfbastard · · Score: 1

    The entire summary sounds like a severe case of sour grapes.

    As to why Linux is popular as a target platform, how about existing adaption, source code compatibility (well, almost) with a range of other UNIX- and UNIX-like operating systems, hardware compatibility etc.

  7. The operating system is irrelevent... by Wdomburg · · Score: 3, Insightful

    All the interesting stuff in supplanting Windows in the desktop is in, well, the desktop. The underlying operating system is irrelevent so long as it works, and Linux is going to continue doing that far better than upstart efforts.

    1. Re:The operating system is irrelevent... by timeOday · · Score: 1
      The underlying operating system is irrelevent so long as it works
      But it doesn't, and it can't. The unsolvable issue for *every* open-source OS is device support and software support. "Works" for a user means they can buy a device and/or software and it will work (without hassle). Hardware developers have mostly spurned open source because they don't want their source open. Windows programs will never run well under Linux (with the release of Vista, Wine is losing more ground than it ever took). Even shockwave and quite a few video codecs don't work.

      Linux hasn't failed to take over the world because it needs a microkernel or a different IP stack or whatever, so changing that stuff will never matter much. Mainly it's just because Microsoft is too entrenched.

    2. Re:The operating system is irrelevent... by mackyrae · · Score: 1

      I think what the GP meant is that after all the years of hacking together drivers, Linux has better hardware support than other minority OS's, but what the user sees is all userland GNU stuff. The underlying kernel could change, but they'd still use FF and OOo and bash. There's a TON of stuff that needs drivers in Linux, but you know what? Those hardware companies could ship binary drivers on the same cd as the Windows drivers they give with the hardware if they don't want to give open source ones. nVidia and ATi have binary drivers available because their OSS ones lack 3D acceleration. If I buy something and it has binary drivers on a cd, that's still better than the Linux drivers not existing at all. Someone can get around to reverse engineering it later.

      --
      look! it's a bird, it's a plane, it's....a girl? yes, a girl browsing Slashdot on Linux
    3. Re:The operating system is irrelevent... by Wdomburg · · Score: 1

      But it doesn't, and it can't.

      Exactly. Linux does it better but still doesn't do it well. At this point in time it has a far better chance of improving significantly than a new project would be.

      Windows programs will never run well under Linux (with the release of Vista, Wine is losing more ground than it ever took).

      I don't think this is necessarily a death knell as a viable desktop platform. The same can be said about MacOS X, afterall. Services are finally becoming viable alternatives to applications - see gmail instead of outlook, flikr instead of local photo management, the popularity of flash games.

      The era of "I need Windows because I need " certainly isn't over by a long shot, but it's not as strong an argument as it once was. (When that's true, I expect virtualization to be a much more common solution than emulation.)

      Even shockwave and quite a few video codecs don't work.

      After hardware (specifically 3d drivers for video cards and wireless chipsets) that strikes me as the biggest barrier. Thankfully it's not nearly as dire as it could be. Most online video is trending to FLV, which works fine (though it will be nice when FP9 finally comes out of beta since it allows richer controls and the significantly better On6 codec). Next biggie for video would be VC-1/WMV9, which is now fully supported. For audio it's all about mp3. That's a huge blow. On the other hand Fluendo paid for a patent license to allow free distribution of their plugin.

  8. Is this a serious question? by heinousjay · · Score: 0, Flamebait

    When has anyone ever known a zealot to change their mind? I can't believe this is even being asked.

    --
    Slashdot - where whining about luck is the new way to make the world you want.
    1. Re:Is this a serious question? by Skewray · · Score: 2, Funny

      My god your right! I am wiping my linux os's immediately and installing Minix! I have seen the light!

  9. Go Xfce! by sofar · · Score: 2, Informative

    See also Xfce (www.xfce.org), which has several key developers who work using BSD and Solaris instead of linux.

  10. Too many flavours by Anonymous Coward · · Score: 0

    The main reason why Firefox gained so much popularity compared to Linux is it's so easy to install and use. Linux has so many flavours that people don't know which one to pick and shy away from it.

    I'm still looking for a Linux that's easy to install and use without having to "rebuild kernels, install hundreds of packages, etc". I tried Ubuntu and that never worked...

    I'm sure I'm not the only one wanting to give Linux a try but it's so compilicated.

  11. False analogy by Noksagt · · Score: 4, Insightful
    Clearly, if Linux is unable to reproduce a third of Firefox's end user uptake over a much longer time-frame, there are deficiencies with the direction the GNU/Linux/X/Gnome/KDE system has taken.
    This is a false analogy.

    Linux is an OS. Firefox is a desktop application. An OS differs from an application in many ways, including ease of installation and the impact to the rest of the desktop.

    Perhaps this suggests "alternative OSs" should make it even easier to make use of virtualization on "popular OSs" (LiveCDs are popular & this would be the next logical step).

    Of course the way to find the adoption of any software is difficult & the ways people look at browser usage compared to OS usage often differ.

    Firefox can run on many OSs, including Linux. Unless another browser becomes very dominant on Linux or Firefox becomes unpopular in other OSs, it isn't a good point of comparison.

    The fact that a browser was the basis for comparison is telling--server-side apps are becoming more important & many of these do run on Linux.
    1. Re:False analogy by Chris+Burke · · Score: 2, Insightful

      Linux is an OS. Firefox is a desktop application. An OS differs from an application in many ways, including ease of installation and the impact to the rest of the desktop.

      No kidding, I thought this was a ludicrous comparison when I read it too. Firefox achieved popular success because it runs on Windows. Can Linux do that? Uh, no, barring geeky stuff like vmware which itself doesn't have the same uptake as a web browser.

      Plus when he talks about the Linux desktops being wedded to Linux even though Linux has failed to achieve Firefox-like success, he misses the whole friggen point of these desktops: to make Linux and other *nix more ammenable to being the "average user's" desktop! He's basically saying, give up on that, and try to be popular on Windows, assuming that's even possible.

      The fact that a browser was the basis for comparison is telling--server-side apps are becoming more important & many of these do run on Linux.

      Indeed, good point.

      --

      The enemies of Democracy are
    2. Re:False analogy by Odin_Tiger · · Score: 1

      Or just make installation easier. One of my newer PC's has this SATA / RAID onboard contoller, but there are BIOS options that make it 'fake' stock-standard IDE. Using this setting, I can install my ancient copy of Win98SE. I've tried (and failed) several times to get various Linux distros / BSD's to even acknowledge that I have hard drives. Similar issues with picking your mouse type, picking your monitor, etc. Even doing 'the right thing' by getting a list of all the hardware you have before you install Linux (or BSD) is useless more than half the time, because unless your hardware is 3+ years old, it is unlikely to be listed...you have to pick a compatible driver. If you haven't spent a few hours a week for the last several years browsing NewEgg, I expect it's rather difficult to know what piece of hardware is going to be most similar to the one you have. That's just the tip of the iceberg on the difficulty of installing Linux, let alone setting everything up (CUPS...gah!) once you have it installed.
      Don't get me wrong, I like Linux and BSD (slightly leaning towards BSD), but I make a living doing hardware / software maintenance on PC's, setting up and managing networks and servers, helping users, etc., and I HATE installing *nix. How hard must it be for non-geeks? My mom can install Windows XP on a computer all by herself (Step 1: Insert OS CD, keep clicking next / yes / ok. Pick your time zone. Continue clicking next / yes / ok. Be sure to remove the CD when it tells you to. Step 2: Insert MoBo CD. Keep clicking next / yes / ok. Remove CD. Step 3: Insert Video Card CD. Keep clicking next / yes / ok. Remove CD. DONE!) I don't expect *nix to be THAT easy, but it would be nice to be confident that without having a secondary PC available, a given Linux can be installed on a 1 year old or less PC in less than 10 utterances of WTF, SOAB, or MFPOS.

      --
      Unpleasantries.
    3. Re:False analogy by mobby_6kl · · Score: 1

      >Linux is an OS.

      No it's not. Linux is a kernel.

    4. Re:False analogy by ahodgson · · Score: 1

      I don't expect *nix to be THAT easy, but it would be nice to be confident that without having a secondary PC available, a given Linux can be installed on a 1 year old or less PC in less than 10 utterances of WTF, SOAB, or MFPOS.

      It can't, because the hardware manufacturers don't provide Linux drivers, or in most cases any help at all to the people who do.

      So it takes time to reverse-engineer whatever it is they do, and make Linux work.

      The hardware works with Windows because the hardware guys have to provide working drivers for Windows to sell any of their stuff.

      Personally, I find it miraculous that Linux has as many drivers as it does. And I carefully buy motherboards with supported chipsets.

    5. Re:False analogy by Odin_Tiger · · Score: 1

      Not so, I consider that a lame cop-out. If I can get it working through a series of steps, there is no reason an installation process can't do it for me. On most recent installations, I can -eventually- get it working without even having to download extra drivers etc. In other words, it's all right there on the installation discs, but for some stupid reason, the installer insists that you hold it's hand all the way through and then pukes all over the place if you pick something wrong or refuses to proceed if you don't know the correct selection (many installers have nothing in the way of default just-to-get-by-for-now selections.) Also, the reason I use the Win98 example is that it manages to somehow get me through installation and in at least a passably functional graphical state even on brand-spanking-new hardware that it no way in hell has drivers for, and in a few cases probably not even remotely similar drivers? I guess what pisses me off most about *nix installs is that in too many cases there is little / nothing in the way of legacy, one size fits all, it'll-work-but-it'll-be-ugly drivers, which means that if you don't have a second PC handy, you'll have to re-format, re-install Windows, fire up Google, and spend 3 hours searching for 1) somebody who actually had the same problem as you who 2) miraculously got a helpful reply, and then start the *nix installation all over again from scratch and hope to hell you don't hit another wall and have to go through it all over again. I've rarely had trouble installing *nix because the driver wasn't included in the install .iso's and never had a problem where the driver didn't exist at all. The problem isn't a lack of drivers, it's a lack of sane installers.

      --
      Unpleasantries.
    6. Re:False analogy by Anonymous Coward · · Score: 0

      Windows 98 can work because it's still basically DOS. As long as the hardware provides an ancient BIOS emulation layer for apps running in DOS mode, 98 can limp along.

      OS's running in protected mode cannot do that. They have to have real drivers for the hardware running underneath them (except for IDE controllers and 2D video, which have protected-mode standards they can comply with).

  12. Some do by Enderandrew · · Score: 5, Insightful

    Some do consider alternatives, and that is why programs like ReactOS exist. Most of the smaller alternatives aren't really designed to be desktop replacements for the world, but rather small niche desktops. Of all the alternatives, Linux is the best candidate to supplant Windows on someone's PC.

    Firefox used aggressive marketing in quick blitz. It had a great name. And Firefox had rapid growth because of that.

    Linux is associated with geeks and carries plenty of negative baggage with the average person. When Mozilla became Firefox, it was able to be reborn in a marketing perspective, and may someday win the fight that Mozilla never could.

    If Linux gets a similiar marketing facelift, you could see similiar adoption rates that Firefox had. It is a much bigger adjustment for people, but in the wake of Vista, more people may be looking for alternatives. However, the majority of the Linux community is quite content to cater to themselves rather than try to cater to the outside market. For mass consumption you would really need:

    1 major primary distro for home users.
    1 major desktop
    Easy conversion wizard to help people convert Microsoft documents, desktops and settings.
    1 major form of package management, and thusly one major package repository

    Remember the GetFirefox.com campaign? Remember all the CDs thrown around?

    Imagine a LiveCD distribution campaign that did the same thing, but also helped you convert/migrate? Give it a snappy name, and a cute mascot and there you go!

    --
    http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    1. Re:Some do by ericrost · · Score: 2, Insightful

      Only problem with that is the VAST difference in philosophy between distro's. I run Gentoo because its scalable, portable, and has the best package manager out there. However as any new Gentoo user will tell you, it's a bitch to get going the first time. It made me learn though. I had a technical background in computers and networking in the Windows environment and bloatware holds you by the hand so much that when you're faced with an OS that can do anything you want it to, you cry out for help. Once I got through the pain, I'm now running my system the way I want it to be run. The average user can't do this. The average user wants to click Yes and have everything run. There are a few distros out there for this, but they have their problems as well (security, portability, package management). There (at present) isn't a magic bullet out there in the Linux world for an end user's home PC. You have to be techinical to run a Linux system properly, and most people want an appliance, not a computer.

    2. Re:Some do by Enderandrew · · Score: 1

      Not trying to start a flame-war here, but I loathe Gnome. I point most "typical-users" to SUSE, but with the Novell fiasco, I'd point them to Kubuntu likely.

      Both show great promise to that end. If the community weren't so completely fractured, we could develop a magic bullet.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    3. Re:Some do by ericrost · · Score: 1

      I completely agree that those are the distros that work best for end users, but take a look at the installs, huge bloated OS's that aren't stable and don't have good package management. With the built in bloat they just don't run as fast as the hardware could/should. The flexibility and optimizations for my hardware are what led me to Gentoo. Although it may not have been the most user friendly (In my view Gentoo's biggest "drawback") I was able to get it going with the documentation (80 page install guide) available and there's a HOWTO for everything you want to do to get it running and then tweak it. And that fact that almost everything is compiled from source optimized for my architecture and not including support for hardware/features I don't need makes up (to me) for the fact that its a bit of a shooting match getting things correctly configured. But anyway, there's a good reason there are different distros, and that's because there are different user bases. But like we've said already, there isn't a magic bullet. I would hate to get a call from someone who doesn't know what they're doing trying to set up Gentoo, but I don't know that I'd recommend Ubuntu or openSUSE because of the lack of effective package management when they're trying to get a new application running.

    4. Re:Some do by MagicM · · Score: 1

      Isn't this exactly what Ubuntu is doing (minus the easy conversion wizard)? They "throw around" CDs, and even try to send you more CDs than you need so you'll hand them to your friends.

      So all they need is a snappy mascot. I nominate him.

    5. Re:Some do by Enderandrew · · Score: 1

      I'm a big advocate of Gentoo as well, though lately I've been frustrated with the lack of updates in Portage for certain packages. They sorely need more package maintainers.

      But Gentoo is not the magic bullet to spark the Linux revolution for the typical user.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    6. Re:Some do by Enderandrew · · Score: 1

      They are making installing Linux fairly easy, though I think Suse has the best installer, and YAST is great for new users.

      I don't think Ubuntu is a sexy name, the mascot isn't sexy, and I don't care for the color scheme. It seems to be the fastest growing Linux distro on the planet, but I don't think it is a marketing home run either.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    7. Re:Some do by AeroIllini · · Score: 2, Insightful
      Nice to see a fellow Gentooer admitting that not everyone should run Gentoo. I run Gentoo on everything I own, but it's a power user's OS, not Joe Average's.

      The average user wants to click Yes and have everything run. There are a few distros out there for this, but they have their problems as well (security, portability, package management).
      Well, sure. But Windows suffers from all these problems and more. For every "I couldn't get my digital camera working in Ubuntu" anecdote out there, there is a similar "I couldn't get this scanner working in Windows" anecdote. Technical issues are not the problem. Technically, Linux is ready for the desktop.

      The big barrier here is user perception, and market fragmentation. Would Firefox have been as successful if people were told to switch, and then told that they could choose from Firefox, Mozilla, or Seamonkey, and that each one is very similar but different in some visible ways, and that users of each one are fiercely loyal and will tell you to bugger off if you asked in the wrong forum for help? Of course not. The same situation applies to Linux. We (the Linux evangelists) push Linux on people, but then we are ambiguous about what Linux actually is. Is it Ubuntu? Is it Debian? Is it BSD? Is it Gentoo? And even within distros, there is ambiguity about KDE vs. Gnome, etc.

      Joe Average is not ready for a change in paradigm, just a change in OS. What we need to do as a community is to standardize on a single "evangelist" distribution, that comes with fewer choices than most distros. Then we need to start a marketing campaign, like the GetFirefox campaign, that encourages people to use a LiveCD. Give this distribution the "click Yes to install" functionality that people expect. Once we've gained marketshare, THEN we can start introducing Joe Average to the paradigm of choice within the OS itself.

      Remember that when trying to unseat a major market player, your product can't simply be "as good as." It must be better. So much better that people have incentive to switch.
      --
      For security, the MD5 hash of this message and sig is 09f911029d74e35bd84156c5635688c0.
    8. Re:Some do by ericrost · · Score: 1

      I agree with enderandrew and you on this. I waited to make the Linux jump to see MacroShaft make the mistakes it made with XP then Vista. XP I was able to do what I wanted to do with, so I didn't jump because of the perceived inconvenience of re-learning. In the end I chose the hardest distro to jump into because I weighed the advantages of each and figured I could handle it. After four days of hair pulling, I had a fully configured, working system, that had exactly the software running on it that I wanted. Now there is no M$haft software in my household except for my X360 (damn games). But I acknowledge wholeheartedly that I'm not the average user. If I had the trouble I did with getting it going, I can't imagine someone who wants to turn their comp on and be greeted with a fuzzy warm feeling doing it. Those users will only be accessible when we have OEM support. OEM's will only come on board with a workable business model and a critical mass of users and developers. I definitely think Linux is headed this way. End of ramble.

    9. Re:Some do by orasio · · Score: 2, Interesting

      KDE and Gnome cater to different users.
      Former expert windows users sometimes prefer KDE, because it resembles mswindows better.
      Gnome is, in my opinion, better for completely new users.
      The magic bullet is that, Kubuntu for switchers, and Ubuntu for everybody else.

    10. Re:Some do by XO · · Score: 1

      Imagine a LiveCD distribution campaign that did the same thing, but also helped you convert/migrate?

      We tried this in the days of OS/2 .. unfortunatly, we didn't have the snappy name thing. Do you think that might've helped?

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    11. Re:Some do by Anonymous Coward · · Score: 0

      As much as some of the free software zealots want to crush the idea, what is needed is Linux OS with proprietary parts. I have managed to finally replace Windows as my desktop OS because of Freespire - Linspire would work also for those who don't mind paying. I keep Windows XP on for duel booting to run a few games and use virtualization to run a couple of Windows programs that I need to run until I can transition them to Linux. I tried many different distributions over the past eight years or so, and not until Freespire did I find one that I could use as a desktop OS, simply because I enjoy having access to some proprietary file formats, particularly those found on web pages in the form of embedded video. What you mention in your post as needed for mass consumption is available in Freespire/Linspire.

    12. Re:Some do by JoshJ · · Score: 1

      If you look at google trends, one would almost think that ubuntu is taking market share from all the other linux systems too.
      http://www.google.com/trends?q=ubuntu%2C+debian%2C +fedora%2C+gentoo%2C+mandriva&ctab=0&geo=all&date= all
      Furthermore, this is a particularly interesting stat:
      http://www.google.com/trends?q=ubuntu+linux%2C+mic rosoft+windows&ctab=0&geo=all&date=all
      Searching for "windows" gets false hits, so using 2 words for each makes sure there's no bias in just searching for ubuntu vs "microsoft windows".

      Note the cities and regions that score top hits- none of them are in the USA.

    13. Re:Some do by gad_zuki! · · Score: 1

      >For every "I couldn't get my digital camera working in Ubuntu" anecdote out there, there is a similar "I couldn't get this scanner working in Windows" anecdote. Technical issues are not the problem.

      There's a big difference between "i lost my install disc" and "I have no idea how this command line crap works." Technically, those are two different problems. Linux's reliance on the command line to get mostly everything done is just a turn off to joe and jane windows users. On top of it they have no real motivation to switch. The PC works well enough, the OS came with it, they spent years learning how to point a mouse and a reboot, etc.

      FF's popularity has a lot to do with people seeing their browser as a problem. Too much spyware, no pop-up blocking, etc. Ist not branding, its not marketing, etc. There's no scratch to itch for linux right now, if ever. If it only remains a niche OS then what the hell is wrong with that? This demand to make it the new windows is baffling.

      Not to mention just the idea of joe and jane going to a forum to get flamed is laughable. They wont even stop by. They dont go to forums. They have a CD with autorun which runs a brain-dead wizard. If that fails they have the manufacturers website. If that fails they have a toll-free number to call. Compare that to the typical response on a linux newsgroup, especially about drivers and packages. These people can barely use a TV remote!

      Linux is for a certain demographic. Period. Thinking elsewhere leads to more laughable "this is the year of the linux desktop" articles. The OSS evangelists should really focus on getting more OSS stuff on windows instead of this horrible misguided badvista campaign going on with my donated money.

    14. Re:Some do by Enderandrew · · Score: 1

      Possibly. OS/2 Warp was a little bloated, but I actually liked it. I ran a BBS off it back in the day.

      --
      http://blindscribblings.com - Tasty pop-culture in conceptual fashion.
    15. Re:Some do by Door+in+Cart · · Score: 1
      Joe Average is not ready for a change in paradigm, just a change in OS.
      Joe Average doesn't know or care what OS stands for. The only real barrier to the mass-adoption of Linux or any other OS is the fact that Windows comes pre-installed on every computer for sale at every store in every mall (with rare exception).
    16. Re:Some do by AeroIllini · · Score: 1
      Joe Average doesn't know or care what OS stands for. The only real barrier to the mass-adoption of Linux or any other OS is the fact that Windows comes pre-installed on every computer for sale at every store in every mall (with rare exception).
      You're absolutely right.

      Just like Joe Average has no idea what a "web browser" is or even that he has a choice, because MSIE comes preinstalled on every computer for sale at every store in every mall (with rare exception).

      But remember that people were grumbling about how much surfing the internet sucked, what with all the Flash ads, popups, annoying JavaScripts, and so forth. Along came the Firefox advertising team, and they said, "we know it sucks. There's a better way." Education caused people to install Firefox in droves, because it really was that much better than the preinstalled competition. MS played catch up with IE7, but Firefox has mindshare now, and that's priceless.

      People complain about MS Windows and MS Office all the time, even when they don't recognize the difference between Windows and Office or even realize they have a choice. Education, advertising, and being unequivically better than the preinstalled competition is the only way Linux will take off as a desktop OS.
      --
      For security, the MD5 hash of this message and sig is 09f911029d74e35bd84156c5635688c0.
    17. Re:Some do by XO · · Score: 1

      Well, you could certainly say that the average Windows and Linux distributions are painfully bloated as well. I used a stripped OS/2 v3.0 to play games at the time that were -way- out of spec for my 486sx, while running other programs simultaneously .. I remember specifically playing Descent (which was supposed to run on at least a 486DX/33, I had an sx/16 .. it hardly ran at ALL in DOS, but ran playably in OS/2, while running Telemate in another DOS window and TAG in another DOS window. :D ) while downloading something in one window, and running my BBS in another. :D

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    18. Re:Some do by Anonymous Coward · · Score: 0

      I admit i'ts been a couple of years now since I tried Linux (Mandrake at the time) - but what quickly became apparant to me was that for non-Unix users the learning curve was just too steep. It's taken me years to figure out how to get my Windows systems the way I want them but at this point I know all of the dos commands, registry edits, etc to do that. I write code in several different languages but unfortunately none of them is Unix. So if the need for Unix makes it difficult for experienced users to get the system to work the way they want it and the hardware support issues make it difficult for the inexperienced users to get it to work, who is the target audience? Old Unix coders?

      Firefox is better than the default from just about every perspective (security, ease of use, ease of installation, performance) the only question for Firefox is really why WOULDN'T everyone switch. For Linux I've decided it's not worth the effort to learn how to get it up and running only to find out down the road that the new video card I want won't work on it or some key new application I want to use won't run on it. Which is too bad because I'm no fan of MS

  13. Why Linux will never be a major desktop OS by itwerx · · Score: 4, Funny

    Here's the Flamebait/Insightful reason why Linux will never be a desktop OS: 99% of the development is driven by developers. Developers are geeks. Developers have their friends and the rest of the OSS community test their stuff. If they ran it by their grandmothers once in awhile maybe we'd make some headway...

    1. Re:Why Linux will never be a major desktop OS by kotj.mf · · Score: 1
      Here's the Flamebait/Insightful reason why Linux will never be a desktop OS:
      Wrong flamebait. We're supposed to be explaining why Linux has so much of the desktop market. Get with the program!
      --
      hang brain.
    2. Re:Why Linux will never be a major desktop OS by Dr.+Manhattan · · Score: 1
      If they ran it by their grandmothers once in awhile maybe we'd make some headway...

      I've had my parents on Ubuntu for over a year now. It was easy. I first got them to move to Firefox and Thunderbird. Then, when they were getting a new computer, I set up Ubuntu and spent a little time (maybe a hour total, spread over a week) getting them used to it.

      Their main comment? "Linux has much better screensavers."

      Linux isn't a great desktop for hardcore gamers, or people with really specialized hardware needs (like, say, higher-end telescopes or something). For the majority of people, it's already as good as Windows. And now when I visit my parents, I don't have to spend half the time troubleshooting their machine.

      --
      PHEM - party like it's 1997-2003!
    3. Re:Why Linux will never be a major desktop OS by a.d.trick · · Score: 1
      For the majority of people, it's already as good as Windows.

      Except for application support. This is the only real problem my parents have with Linux. They are linguists and they rely on several Windows-only tools to do their work. This is an issue for a good number of other people to.

    4. Re:Why Linux will never be a major desktop OS by Dr.+Manhattan · · Score: 1
      Except for application support. This is the only real problem my parents have with Linux.

      There are niche apps that aren't on Linux, you're right. But those are just that - niche apps, like the telescope drivers I mentioned.

      Maybe it's true that almost everyone falls into some niche or another, but I haven't really seen that. Almost everything most people do with computers are web, email, music, and games. And Linux the first three well, and isn't so bad on the latter. My kids love the games on Linux - when my oldest son was five I found out he'd figured out how to reboot the computer to Linux so he could play Tuxracer.

      Windows XP crapped out on us (again) a few months ago, and I was tired of fixing it. I got my wife to move over, the kids were no problem. She misses Word a little, but is mostly used to OpenOffice. The only sticking point is her greeting card program, which isn't quite right under Wine. I may have to QEMU that one. But that's it.

      --
      PHEM - party like it's 1997-2003!
    5. Re:Why Linux will never be a major desktop OS by Anonymous Coward · · Score: 0
      I've had my parents on Ubuntu for over a year now. It was easy. I first got them to move to Firefox and Thunderbird.

      Interesting. What do you do about things like, Mastercook, Sunset Western Garden Interactive Computer Guide and Problem solver, Home Planning Software, Exercise and Diet Nutrition Software, Quicken and Monopoly?

      I tried to get my updated linux to install some old Loki disks I bought in the late 90s along with my WordPerfect 8.0 disks, and they won't install on the newer version. I need to go back to "old" versions of Linux from around 1999 to get them to work. Seems to me, that is a good reason why most people are not changing to Linux and why most independent software developers are sticking with developing on windows.

    6. Re:Why Linux will never be a major desktop OS by Anonymous Coward · · Score: 0

      That's just the thing. Her greeting card program isn't quite right under Wine, so you have to QEMU it. So first you set up Wine, tested the program, saw it didn't work, then knew of a different way of solving the problem. That's great when you're familiar with Linux, and know how to do all of that. However, a lot of people don't have family or friends who are familiar or comfortable enough with Linux to be able to solve these problems when they pop up, and to configure the right apps in the right way to make them work. And that's part of the problem. There are too many applications on Linux that are not trivial to get and set up (I do not expect my grandmother to be able to do this, but my younger sister definitely should). If the program and all its dependencies can be found on some distribution-related repository (which has a GUI accessible front-end, and can be browsed by application type), and be installed automagically, great. But in my experience, even with a user friendly distribution such as Ubuntu, things sometimes go wrong, and are not always simple enough for the common user to fix.

      As for most people not needing niche apps- I disagree. For the people who only need web, email, and music (without iTunes, though, of course), as well as built-in games, sure. In this case, though, I would argue that the choice of OS doesn't really matter, as long as it is sufficiently developed to hold its own ground. Any modern OS deserving of that title should be able to run a browser (web, email), have a basic music app, and possibly provide some built in games (Windows only comes with a few card games, and even that is enough). But how about "niche" apps such as Photoshop (probably the most-used high end graphics application) or Flash (the editor, not the browser plugin)? I know many non-techy people who love to mess around with their own Flash sites, or with graphics in Photoshop. Sure, you could use GIMP, but (a) I have personally never liked its interface (granted, that is my opinion), and found it more complicated than Photoshop's (and thus assume that others would too- being a compsci grad student, I probably have a higher than average tolerance to lack of ease-of-use), and (b) no school that I am aware of will offer a digital editing class using GIMP. There are many other applications such as these, which have a large enough user base to be considered non-niche.

      In short, Linux just isn't ready to seriously compete with Windows and OS-X for the common user, mostly because of lack of application support (the fact that there are open-source alternatives to many apps does not mean that the open-source versions are better, and does not make up for having been trained on the original app), a confusing array of different versions and distributions ("You want to install this new version of Y? Oh, that needs kernel version 2.6.15 and above. And there are no rpms for Ubuntu currently."), and frankly a user interface which even at its simplest still caters to the knowledgeable user.

    7. Re:Why Linux will never be a major desktop OS by Dr.+Manhattan · · Score: 1
      However, a lot of people don't have family or friends who are familiar or comfortable enough with Linux to be able to solve these problems

      They do if they are changing to Linux. If they are "ordinary users" they'll use what they can get support for from their friends. It's not like Windows can be operated without regular maintenance by a fairly technical admin. And one reasonably savvy Linux user can support a lot of Linux users. As I said, I have a lot more time to visit when I head over to my parents house now.

      But how about "niche" apps such as Photoshop

      Um, Adobe specifically made sure Photoshop would run well under WINE. I'll grant Flash authoring, but most people don't need to write it (especially not the parents of most Slashdot readers), just run it, and there are current workarounds and good future prospects for that.

      In short, Linux just isn't ready to seriously compete with Windows and OS-X for the common user, mostly because of lack of application support...

      Well, you start out talking about greeting card programs and wrap up with Photoshop and Flash editing. I think your definition of the "common user" is a bit... odd.

      --
      PHEM - party like it's 1997-2003!
    8. Re:Why Linux will never be a major desktop OS by Dr.+Manhattan · · Score: 1
      Interesting. What do you do about things like, Mastercook, Sunset Western Garden Interactive Computer Guide and Problem solver, Home Planning Software, Exercise and Diet Nutrition Software, Quicken and Monopoly?

      I'd presume various combinations of WINE and QEMU would work. Once they're set up, they'll run pretty much forever with no real maintenance needs, and backup is much simpler, too. QEMU's how I got my wife's greeting card program running, though she made it through the holidays without it.

      I tried to get my updated linux to install some old Loki disks I bought in the late 90s along with my WordPerfect 8.0 disks, and they won't install on the newer version.

      A separate issue. I dunno about WP8, never used it. But I've got three Loki games running just fine on my Ubuntu system - Myth II, Heretic II, and Descent 3. You might try running the scripts and such as "bash [install].run" instead of "sh [install].run", or maybe you could Google a bit, just like you would with an old Windows game. I couldn't get Aliens versus Predator to run stably on my Windows XP system. Some sound issue, but it would hang or play the same sounds over and over. The AvP Linux port, on the other hand, runs a treat.

      I've had decent luck with stock Wine for some games. Valve's Steam runs under Wine; HL2 not so much, but HL and its mods seem fine. American McGee's Alice runs utterly flawlessly. But - as I said - games can be an issue. Feel free to put points in your column or whatever on that score.

      --
      PHEM - party like it's 1997-2003!
    9. Re:Why Linux will never be a major desktop OS by ChunderDownunder · · Score: 1

      My grandmothers are both deceased, you insensitive clod!

    10. Re:Why Linux will never be a major desktop OS by Anonymous Coward · · Score: 0

      So first you set up Wine, tested the program, saw it didn't work, then knew of a different way of solving the problem.

      And MS Windows doesn't have this problem? I'm fairly sure XP won't run a bunch of older apps without some screwing around. I'll bet Vista won't, too.

    11. Re:Why Linux will never be a major desktop OS by Anonymous Coward · · Score: 0

      Unless you're talking DOS apps, or old windows 3.1, 95 etc apps, XP runs everything you throw at it. And if not- it's more a matter of right clicking it and choosing a compatibility mode than installing something like WINE. Besides, I wasn't talking ancient apps, but current ones. Backward compatibility is a whole other problem, that most OSs have to deal with in some way.

    12. Re:Why Linux will never be a major desktop OS by Anonymous Coward · · Score: 0

      They do if they are changing to Linux Currently, sure. Few people would get Linux unless they have someone who recommended it and knows how to set it up. That's where Linux is currently, and that is part of why this thread came to be. But when you're saying that you want Linux to be a "major desktop OS", you are talking about giving it to people who won't have that kind of support. Windows and OS-X are both at that point. Linux just isn't.

      It's not like Windows can be operated without regular maintenance by a fairly technical admin I don't think that's true. My grandmother has been running Windows very successfully for a few years now. Only in a handful of rare cases where she needed to install a new printer, or when something stopped working did she need any assistance. And even then my sister, who is far from a techie, was able to provide that help. I could not imagine her being able to provide the same support if my grandmother was running a Linux box.

      Adobe specifically made sure Photoshop would run well under WINE. Again, WINE. This is something that has to be set up to work with Photoshop, and something I would have to do rather than my sister.

      Well, you start out talking about greeting card programs and wrap up with Photoshop and Flash editing. I think your definition of the "common user" is a bit... odd. My point is exactly that. The "common user" should not have to be restricted to only one very specific set of needs. Users need that basic set of programs, such as internet, etc- but at some point, they will probably also have something that will not work on Linux, be it Flash, a greeting card program, or something else entirely. My father has recently starting using an interior design program to design renovations to the house. Maybe I could have gotten it to work under Linux as well, after tweaking WINE for a bit. But part of the point is that this is a hassle, and not a small one at that.
  14. Toy OSes... by kosmosik · · Score: 1, Flamebait

    That is because these projects are not finished and stable operating systems. Linux is quite mainstream now the others you mention are just toys with no real future really. Maybe that is why people tend to prefer running Linux than not running some Toy OS which does not work.

    1. Re:Toy OSes... by Eli+Gottlieb · · Score: 0

      Popularity and development hours are the only difference between a toy and a mainstream operating system.

  15. what about cygwin, fink? by davek · · Score: 1

    I know that the question concerns other operating systems, but I've had the same questions concerning the portability-layer projects like cygwin (windows) and fink (osx). I tried in vain for a few months to get stock garnome to compile and run on cygwin. As for fink, KDE seems to run, albeit in a crippled state.

    IMHO, if the desktop layer of OSS becomes too coupled with the kernel, then we've shot ourselves right in the foot. However, if OSS can continue to develop a somewhat uniform desktop system across multiple platforms...... now that's a developers dream :)

    -dave

    --
    6th Street Radio @ddombrowsky
  16. The're not wedded to Linux.. but are to Unix by HighOrbit · · Score: 3, Insightful

    I disagree "free-desktop efforts have created a total monoculture around developing and promoting Linux" because KDE, Blackbox, XFCE, etc, etc.. all compile on pretty much any implementation of Unix, of which Linux is just a clone. Solaris now runs Gnome (branded as Java Desktop System) as the prefered desktop.

    Unix is probably popular with developers because it is "open" and standardized in the specifications and widely know and taught in computer science departments.

    So the "failure" to catch on is wider than Linux. Solaris/SunOS alone has been deployed in probably every large corporation in America and Western Europe since the '80s, but has never broken out of the specialist server/workstation market and into the general desktop market. And during all that time, SunOS/Solaris has gone from OpenLook, to CDE, to Gnome. The various X-Windows desktops really didn't get off the ground in a meaningful way until the mid-1990's with CDE (which was announced in 1993, I first saw it myself in 1996 on HP-UX), by which time Win3.1 and Win95 were already entrenched. Also, compare Win95 and FVWM circa 1995, and you'll see why Windows was the only desktop game in town at the time.

    Windows owes it sucess to the ubiquity of MS-DOS in the 1980s-early 1990s. MS-DOS owed its ubiquity to the "street-credit" granted to it by IBM's endorsement. Had IBM implemented their PC with Xenix or some flavor of Unix capable of running on an 8088, then we would all have unix desktops.

  17. Re:I not anymore a Linux User by PingSpike · · Score: 1

    While I can understand your situation, Windows may meet your needs best...the crux of your example was photoshop, one application used for specific types of work. It hardly makes the case that only Windows can get the job done for computing...especially since its also available on the Mac.

  18. If they could just cooperate more by paltemalte · · Score: 1

    I know this is slightly off-topic for this question, but I still think that all the people and developers who keep talking about the 'ability to choose' is so great - is the big reason why Linux on the desktop never gets anywhere.
    If all the bright minds of KDE, gnome, QT, the people behind xfree etc would come together, and work out one single system that they all afterwards work on together, I think Linux could stand a chance again. They should focus on what apple has done and how the MacOSX desktop works and try and copy and/or improve on that.

    I as a simple user frankly don't care about having 2 or 3 or 15 mediocre different choices of desktop systems.
    Give me just one good choice instead and I will be happy.

    --
    Sam has one liberty, which he sacrifices for one security. Can you tell me what Sam has now?
    1. Re:If they could just cooperate more by Yvan256 · · Score: 1
      They should focus on what apple has done and how the MacOSX desktop works and try and copy and/or improve on that.
      Indeed. I've switched from Windows to Mac about two years ago, and now every time someone shows me their Linux box, I have the impression to see something from 5-10 years ago.

      If Microsoft is trying to copy OS X, and the Linux community is trying to copy Windows, they'll never be ahead and stay in 3rd place. I'm talking desktop users, not servers.

      Why copy the copier when you could copy the original? OS X is your target, if only for the inspiration on how to interact with and present information to its users. Make it easy to use, allow programs to talk to each other (OS X drag'n drop or copy/paste style, not "Windows-that-allows-worms-to-spread" style). I don't care if it's "hard to code", if you want more users then you need to fill the needs and wants of those users.

      And yes, I know some people will reply with the usual "those fancy users just have to code their own stuff" and "we don't want to fill the needs of dumb users". Don't bother, I'm not talking to you, I'm talking to those who want to spread Linux adoption.
    2. Re:If they could just cooperate more by jonasj · · Score: 2, Insightful

      How about this: Don't think of "Linux on the desktop" as one single competitor to Windows and OS X. Instead, think of GNOME, KDE, XFCE, etc. all as competitors on the same level as Windows and OS X. If you look at it that way, suggesting that KDE and GNOME merge to develop a single desktop makes as much sense as suggesting that KDE and Mac OS X merge.

      The goal of the GNOME project, for example, isn't to spread Linux desktops -- it is to spread GNOME desktops.

      --
      You know, Microsoft's street address also says a lot about their mentality.
    3. Re:If they could just cooperate more by blankaBrew · · Score: 1

      You're describing the GNUStep project. Sadly, it doesn't get the attention that it should.

    4. Re:If they could just cooperate more by Anne+Thwacks · · Score: 1
      And let all drivers get behind the Ford Focus?

      As a Merc driver, I resent that. Why should we all have to use the same desktop? I use FreeBSD, not Linux or Windows, and I use kde, but many of the apps I use depend on bits of gnome.

      What is really needed is for people to start realising that 100 years ago, you could have any car so long as it was a black model T Ford. Now we can all choose our desktop, people want the model T Ford back? Have you ever tried driving a model T Ford? In today's traffic? Yeah - its like driving Windows - almost anbyone can do it badly, but noone can do it well. As yourself, when was the last time James Bond drove a model T?

      What Linux needs (Of a BSD for that matter) is for James Bond to show how OSes kill villains and get girls. Or mabe a famous Rapper to be caught using Redhat to kill other famous rappers? (Everyone knows Al Quaieda use SuSe to kill US soldiers!;-)

      --
      Sent from my ASR33 using ASCII
    5. Re:If they could just cooperate more by paltemalte · · Score: 1

      The reason I think KDE, Gnome, XFCE and what have you should join forces, is so that they could get one single good system out the door quick enough to compete with Windows and Mac. Basically, I think instead of having 4 or 5 groups all invent the same wheels, they should team up and build different wheels each that then can work together.

      If ANY linux desktop system could compete with Mac OSX (or even windows) today this joining of forces obviously wouldn't be needed. But face it, the linux desktops are to MacOSX what a trailerpark home is to a beverly hills mansion. At least from a regular users point of view. I think if all of them pooled their talents together they could change that.

      --
      Sam has one liberty, which he sacrifices for one security. Can you tell me what Sam has now?
    6. Re:If they could just cooperate more by Fulg · · Score: 1
      I know this is slightly off-topic for this question, but I still think that all the people and developers who keep talking about the 'ability to choose' is so great - is the big reason why Linux on the desktop never gets anywhere.
      My thoughts exactly. Too much choice is just as bad as not enough...

      If all the bright minds of KDE, gnome, QT, the people behind xfree etc would come together, and work out one single system that they all afterwards work on together, I think Linux could stand a chance again.
      In an ideal world, that'd work fine. However part of the problem is that no one can agree on the One True Way to do X or Y. There's always someone, somewhere who thinks "this is crap, I can do better" and starts his own version. While there is certainly value in being able to do that, the downside is that it also splits the developer pool for a particular feature. That is why on Linux there is a multitude of programming IDEs, yet none of them comes close to Visual Studio on Windows. If all of those devs worked together on ONE IDE, we'd have that by now.

      Same thing with KDE and Gnome, same thing with the multitude of X composition managers, etc.
      --
      gcc: no input sig
    7. Re:If they could just cooperate more by jonasj · · Score: 1

      If any linux desktop could compete with even windows? You and I must live in two different universes. I have installed Ubuntu for (IIRC) six people who used to be regular Windows users (one of them my mom). One of them I have never spoken to since, but the other five had pretty much the same experience: Their computers went from often being a frustrating nightmare to use, into being a pleasant experience. These are people who use their computers for regular stuff like web, email, IM, writing documents, downloading music with soulseek, playing World of Warcraft, etc.

      GNOME, particularly in Ubuntu's configuration, simply makes it much more intuitive to use a computer for someone who isn't a power user. Compared to any version of Windows, at least -- my OS X experience is too limited for me to say.

      But regarding the idea of the different desktop projects merging... you know, they have different goals and different ideas, and they are not all in it to compete with Windows or Mac OS, but to make the system the way they want to use it. Actually it's almost like suggesting that three rock bands should just come together and make one album instead of making three separate ones, 'cause together they must really be able to make a great album, right?

      --
      You know, Microsoft's street address also says a lot about their mentality.
    8. Re:If they could just cooperate more by SiChemist · · Score: 1

      This might come as a shock to you, but some of us LIKE the way that Linux desktops work now and don't particularly want to copy your precious OS X. I was exclusively Windows until about 4 years ago. I switched to Linux and haven't looked back. I have an OS X desktop at work, and it's nice, but I am much more comfortable with my KDE desktop. KIO slaves are one of the most useful innovations in desktop design and they make my work so much simpler.

    9. Re:If they could just cooperate more by Yvan256 · · Score: 1

      What I mean is, the Linux community should try to do the best of all worlds. If something works fine on one OS (File Explorer on Windows), take it. If something else works fine on another OS (Exposé on OS X), take it too.

      The goal here is not to copy Windows nor OS X, however when I look at most Linux desktops I have the feeling of looking at Windows 98 with another skin applied.

      The fact that there's so many desktops to choose from, and that apps may require/work better under a particular desktop doesn't help the "Linux cause" one bit.

  19. Userbase critical mass by Coryoth · · Score: 4, Insightful

    I think the simple answer is critical mass: you need a sufficient number of developers developing not just the platform itself, but applications to run on it. Without a sufficient base of applications you're going to inevitably be perceived as a minority player and fail to attract many users, and hence many extra developers. Past a certain threshold you can be roughly self sustaining - Linux is across it, and so is MacOS X, but I don't think the projects you mention are even close. There is simply too much software built up on the GNU and X11 toolchain (and increasingly on GNOME and KDE) that people would have to leave behind to move to a new open source OS - it just isn't that tempting when the alternatives look so application poor.

    To succeed you really need some base to start with (as Apple had when they moved to MacOS X, although even they lean on X11 and apps built on the GNU toolchain to some extent), or you need to support the toolchains of the applications (see OpenSolaris and BSD, which lean on X11, GNOME, KDE, etc.). Depending on what it is you wish to get rid off things can go from easy to very hard. Just ditching the Linux kernel is feasible - see the BSD and OpenSolaris options, among others. If you want to get rid of X11 as well... well that's trickier, but if you have a graphics system that will run GTK+ and or QT you might get by because you'll still have the rich supply of GTK+ apps, and can probably get KDE ported. If you want to ditch everything up to GNOME and KDE... well that means rewriting all your applications from scratch, and really that's a huge and incredibly daunting task. It's not just the big applications like web browsers and email clients, its all the different little niche applications that make the environment so rich. Its that that keeps many people on Windows - the one little application that few other people have any interest in, but happens to be vital to them; because everyone has a slightly different vital niche program it adds up to a lot of applications to reproduce before you can truly draw a large user base.

    Linux has crossed the first threshold: it has enough users and application developers working on it that its self sustaining. It has yet to cross the next threshold where it provides a rich enough ecosystem of applications to entice the myriad of home users. It is, however, slowly crawling toward that goal.

    1. Re:Userbase critical mass by demachina · · Score: 1


      The key point is that success as a desktop OS REQUIRES a monoculture. You need basically one standard and it needs to maintain compatibility over time so that A) you develop a rich application base, B) users have excellent compatibility and interoperability with their peers and C) once you get an app you like and which works, it keeps working without needing to upgrade it every few months/years.

      Its already a huge problem for Linux that there are two desktop GUI standards. It completely fractures the application base, hampers interoperability and dilutes developer resources. You frequently end up with two medicore apps, one KDE and one GNOME. Competition is good and all but the competition should be focused more in application space than on OS and GUI framework space.

      Developing a bunch more fringe OS's is exactly the wrong thing to do if you want to displace Windows on the desktop. All that does is dilute developer resources even more and lead to even fewer and lower quality applications due to that dilution. The best thing that could happen to the Linux desktop at the moment, though it is impossible due to the religious wars that would ensue, would be to settle on one desktop GUI standard and consolidate down to a very small number of Linux distributions. One desktop distribution would be best, unless others serve some very specific need.

      The bottomline is you want developers focused on high quality, innovative and interesting applications, not constantly reinventing the OS and GUI wheel. Desktop users care about applications, not really operating systems or GUI frameworks.

      Linux and OSX have enough adoption that it would be possible for them to gain critical mass and to penetrate the desktop market further. It would take a freaking miracle for some other fringe OS to penetrate it on the PC. The only way it would happen is for an OS to take over through the consumer device space first, where some huge company decides on the OS, and have people start using a settop box or media server as their PC too. The problem in the consumer device space is the application set is usually EXTREMELY limited and not under user control.

      --
      @de_machina
  20. Yes, they do follow linux only. by Generic+Player · · Score: 1

    Try using a BSD or solaris and see just how standards compliant most open source software is. There's tons of linuxism and gnuisms in not just the software, but also their configure and build setups. And glibc is not a standard. If you mean one of the C standards like C99, then no, lots of people write gnu/C.

  21. Linux doesn't only exist to overthrow MS by Elentari · · Score: 2, Insightful
    From the tone of the summary, it seems that a failure to challenge the Windows monopoly - and to do so succesfully - is grounds to abandon a project you enjoy contributing to.

    I use Linux because I prefer it, not because I want to spite a business. Same reason, I think, that many developers work on Linux. They like the system; they don't (all) feel the need for penguiny desktop domination.

  22. poster clearly isn't a developer by blackcoot · · Score: 1

    why am i not interested in developing for platforms other than linux? a short list:

    - linux is what i use on a daily basis for work. if i'm going to write software on my own time, it's going to be for a platform that i use
    - i know enough linux apis that i can be useful (e.g: posix, qt, opengl, etc.) whereas with most of the alternative OSes that you've listed, i'd have to start from scratch learning pre-alpha APIs. no thanks.
    - i have the right tools under linux to get the job done, while the OSes you've mentioned are still playing catch-up to get pretty basic things in place
    - i have a plethora of documentation and easily accessible expertise readily available to help me with linux development

    if those other OSes gain linux-like momentum in the next two to five years, i'll reconsider. until then, no thanks.

    1. Re:poster clearly isn't a developer by Anonymous Coward · · Score: 0

      These seem to be exactly the same reasons people don't move away from Windows

  23. 2 answers by mnmn · · Score: 4, Insightful

    You have posted two questions, why are all free software developers headed towards Linux and why Linux has not supplanted Windows as a Desktop OS..

    Answers:
    1) Most free software developers I know gravitate towards standards, not an OS. Their programs will run well on a GNU BSD system and cygwin. That's their goal. Every developer whose motivation for development is philanthropy or ego will aim to maximize compatibility rather than being exclusive to Linux.

    2) Linux cannot take over the desktop for a few simple reasons. First and foremost is the lack of standards. Theres gnome AND kde. And there are several popular distros to develop and test for to make sure installation is smooth and seamless like in Windows. Windows is a single distro and extremely predictable in that regard. Developing and deploying a desktop app for it is much easier.

    Secondly there is a lack of opensourced drivers and directx doesnt exist. DirectX makes things much easier than opengl plus other api.

    Once a real and effective standard is settled upon in Linux (api, distro, installation and package maintenance mechanism) I suspect Linux would be much more popular on the layman's desktop.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    1. Re:2 answers by BecomingLumberg · · Score: 1

      "Theres gnome AND kde. "

      I think you make a good point here. Moreover, i really wish app developers would try to make apps that have kde and gnome flavors, at least. I prefer Gnome, but i love Amarok. I know that i still can install amarok, but it gets a little squirrelly using it in gnome. It would be nice if there was a direct port to the different desktop (not a knock off like listen or exaile, although they are nice).

      --
      If a nation expects to be ignorant and free, in a state of civilization, it expects what never was and never will be.-TJ
    2. Re:2 answers by DaveV1.0 · · Score: 1
      Once a real and effective standard is settled upon in Linux (api, distro, installation and package maintenance mechanism) I suspect Linux would be much more popular on the layman's desktop.


      I don't see that happening any time soon. Too much ideology wrapped up in those things.
      --
      There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
    3. Re:2 answers by jonasj · · Score: 1
      Linux cannot take over the desktop for a few simple reasons. First and foremost is the lack of standards. Theres gnome AND kde. And there are several popular distros to develop and test for to make sure installation is smooth and seamless like in Windows. Windows is a single distro and extremely predictable in that regard. Developing and deploying a desktop app for it is much easier.

      I'm gonna sort of repeat what I just wrote in reply to paltemalte earlier in this thread: What if instead of thinking of "Linux" as one thing that wants to take over the Desktop, you think of GNOME and KDE as two projects each wanting to take over the desktop, that is, consider GNOME, KDE, OS X, Windows to be on the same level.

      And similarly, maybe try to think of the different distros as different operating systems in their own right? Instead of thinking "Windows, OS X, Linux (with many different distros)", think "Windows, OS X, Fedora, Debian, Ubuntu, etc".

      It's all about different levels of abstraction, really. Parodying your argument, one could even argue that UNIX-like systems could never take over the desktop because "first and foremost is the lack of standards. Theres linux AND os x". You see my point?
      --
      You know, Microsoft's street address also says a lot about their mentality.
    4. Re:2 answers by cyclop · · Score: 1

      I never understood this "I like app X but it's for desktop A and I run desktop B so it's bad". Not in the last 2 years, at least. I run a Gentoo desktop with XFCE (based on GTK), I run GTK based browser and mail client (firefox+thunderbird), but most other apps I use are KDE apps (Konqueror, amaroK, K3b, Kate) etc. - they all play nice with each other. At work I have a Kubuntu KDE desktop where I use GTK apps (firefox,thunderbird,synaptic,inkscape,gimp) inside the KDE desktop. Seriously, where is the problem?

      --
      -- Patent no.123456: A way to personalize /. comments with a sig attached to the end.
    5. Re:2 answers by BecomingLumberg · · Score: 2, Interesting

      Many of the direct interfaces do not work as well. In KDE, you can do some intuitive things - like dragging an .mp3 from the desktop into the playlist. From GNOME to Amarok, I found there was some difficulty. Admittedly, it has been more than a year since I used Amarok in Gnome. I've been using listen, which would be my second choice...

      I know this is not a very detailed answer, and certainly this is not the only thing that i saw that wasn't quite right. Its the best example I can think of this far down the road.

      --
      If a nation expects to be ignorant and free, in a state of civilization, it expects what never was and never will be.-TJ
    6. Re:2 answers by XO · · Score: 1

      There needs to be an absolute standard interface, such as Windows provides, for doing things like file dragging and dropping, and other things that we can -expect- to be able to do. The API isn't there, and there are two different desktops that provide it, and then there are hundreds of other WMs that provide different things. Since that stuff is not part of X, it needs to be part of something else, and then the functionality needs to be built on top of IT.

      GTK doesn't provide it, I don't even know what the hell GTK provides except a really farking awful File dialog box (although I've noticed in the most recent versions if you type into it, it works, instead of having to know the unexplained shortcut to get to it.. but still, that's not at all obvious). The drag/drop/object/etc is provided by GNOME or KDE .. and it sucks.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    7. Re:2 answers by finarfinjge · · Score: 1

      GNU BSD ???? Would that be the Gnu's Not Unix Berkely Software Distribution of Unix? Because BSD IS Unix.http://www.freebsd.org/

      Cheers

      JE

    8. Re:2 answers by Anonymous Coward · · Score: 0

      I respectfully disagree. Since X is the lowest common denominator along the stack, support for things like drag&drop, global hotkeys, etc. NEEDS to be implemented in X. The real problem is that X developers are in denial about what it actually represents as part of the GUI toolchain (i.e. much more than it actually implements, because of what it DOES implement like selections, interactions, keymapping, etc).

    9. Re:2 answers by ChunderDownunder · · Score: 1
      Have a gander at freedesktop.org.

      This community does provide 'standards' for interoperability, including drag and drop. Various UI operations mightn't work as seemlessly as on Windows or Mac but the intent is there.

    10. Re:2 answers by XO · · Score: 1

      I'm perfectly fine with X being just input and output. Normally, I'm one advocating DECREASING the amount of layers between point A and point B, but in this case, I think there needs to be another layer, and it needs to NOT have 11 different choices for it. There should be -one- layer, and everyone should work together to perfect it.

      You know, like the kernel. Like X itself.

      It's possible that someone could come up with other things. But things like Drag-n-Drop, and I don't know what else, I'd probably need to look through a listing of all the services that Gnome and KDE and Windows provide, should be universal across all WMs and Desktops.

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  24. A world of projects, but only few winners by JanStedehouder · · Score: 2, Insightful
    Linux was developed around a very open and collaborative concept and it succeeded in drawing the attention of tons of developers and a growing number of end-users. NeXT was an innovative concept, supported by the some of the brightest minds around. But it did not succeed. Some it found it's way in other desktops. BeOS was a great concept. It is one of the fastest desktops ever with a very high performance. Yet, it did not succeed in the market place (MonaOS looks like BeOS). Amiga? Same thing.

    We can't blame Linux for being more succesfull in attracting the workforce. The question should be: "Why are the projects you mention unable to attract the same kind of attention?" Maybe there is no answer, maybe some of their good parts will one day merge into what is now considered the main stream (like the BeOS developer that is now hired by Microsoft).

  25. What is the non-web-only market share? by _iris · · Score: 1

    For the past year or two I've half-jokingly told people that I think that Linux has as much as 35% marketshare when you discount people who use nothing but a web browser (since in this case the OS doesn't really matter, so the user doesn't have to make a choice). I'm curious what the real number is. Does anyone here know how to find out?

    1. Re:What is the non-web-only market share? by Anonymous+Brave+Guy · · Score: 1

      Does anyone here know how to find out?

      No, but given the number of business users who rely on MS Office and a few other key applications, and the number of home users who play games, I'm afraid your 35% is wildly optimistic. I'd guess it's nearer 1/10 of that, if you're lucky, and most of that is server-side rather than user desktop.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    2. Re:What is the non-web-only market share? by Anonymous Coward · · Score: 0

      You're out of date.

      Most people *aren't* just browsing (and doing email) now. They're using multimedia applications. And in fact *that* is a problem for Linux:

      http://catb.org/~esr/writings/world-domination/wor ld-domination-201.html#id288174

    3. Re:What is the non-web-only market share? by _iris · · Score: 1

      Actually that is a problem for OSS and Free Software, not Linux.

  26. (Raises Hand) AROS Dev by cyclomedia · · Score: 2, Informative

    Though i've lived an internet connectionless home life for well over a year now, so havent actually had anything to show for it for a while. The goals of AROS, aside from promoting a warm fuzzy feeling amongst amiga stalwarts, are a small, efficient, multitasking, modular OS. and by small we mean less megabytes than you can count on one hand. and by multitasking we mean being able to process more than one thing at once, which lets face it, windows sucks at 20+ years after AmigaOS 1 came out.

    --
    If you don't risk failure you don't risk success.
  27. Open Source desktops not limited to Linux by arevos · · Score: 1

    Of course, almost all free software and desktop efforts and development remain unquestioningly oriented around Linux.

    No, no they aren't. No critical functionality in KDE or GNOME relies on the Linux kernel, and both desktops will run happily in the various BSDs. So maybe a more accurate question for Ask Slashdot would be, "Why are Free-Desktop developers wedded to the X Window System?"

    I'm not particularly knowledgeable about the merits of X, but there are a number of advantages to using it that I can think of off the top of my head:

    1. It's based on an open standard.
    2. The most often used open source implementation of it, X.Org, supports a large number of graphics cards.
    3. X.Org 7.1 and up support hardware acceleration via AIGLX, allowing for window distortions, particle effects, alpha blending, etc.
    4. It's already used by a lot of other projects and is in active development.
    5. It's network transparent.

    An often cited reason for using a non-Microsoft OS is to avoid a monoculture, but free-desktop efforts have created a total monoculture around developing and promoting Linux, despite a decade of failure in supplanting Microsoft's proprietorial OSes with it.

    I'll mentally sustitute "Linux" with "X" here. What exactly makes the equivalent GUI layer on Windows significantly better than X.org? I can't think of anything; so it would seem that we cannot blame X.org for Linux failing to achieve a large market share.

    Indeed, it's debatable whether the desktop is to blame at all. I'd have thought it was more to do with lack of compatibility with Windows applications, and that again would seem to be a problem that's largely independant of the kernel or the desktop. You can run Wine or Mono applications on KDE, GNOME, Linux or BSD; the problems with Wine or Mono aren't anything to do with the systems on which they run.

  28. Re:I not anymore a Linux User by jimstapleton · · Score: 1

    And what license would you suggest? A more open but less free license, like the GPL?

    Freedom means being able to make choices and decisions. Suggesting that using GPL, which is more restrictive of the choices avialable, over the BSD/MIT/LGPL/etc. licenses is not a push for freedom, it's a push for openness, there is a difference.

    Stand on your platform all you like, but don't call it a name that would fool others into thinking it's anything other than what it is.

    --
    34486853790
    Connection too slow for X forwarding? Try "ssh -CX user@host"
  29. a simple theory by Yaddoshi · · Score: 2, Interesting

    LINUX has readily available development tools that do not cost the software developer anything beyond hardware and an internet connection to access, therefore they can maintain the lowest possible overhead while developing their free desktop applications, and because LINUX can be run on older computer systems, the cost of hardware can be kept significantly low as well.

    When you are creating something that is going to be offered to the general public as "free", the only significant investment you wish to commit is time. Oddly enough, time is the only resource we as human beings will always run out of, plus we do not know how much time is allotted to any of us, and therefore its value cannot be calculated (even though lawyers sure seem know how to put a price-tag on it).

  30. Re:I not anymore a Linux User by PinkPanther · · Score: 1
    A Unix admin who needs office and photoshop? What the hell kind of work are you onto?

    Sorry, but I smell troll. Your post just doesn't make sense.

    I have been able to do my work on either GNU/Linux or XP for quite some time now (except for some CE app development projects). I just cannot buy the concept that a "unix admin" feels that "Windows" fixes usability problems.

    --
    It's a simple matter of complex programming.
  31. Bollocks by RAMMS+EIN · · Score: 1

    Excuse me for saying so, but the submission is a load of bollocks.

    ``However, the Linux of today seems to be as far away as ever from realizing the expectations of mass adoption we once had for it, without significant growth in home usage since the late 90s.''

    Where do you get your numbers? People all around me have switched to GNU/Linux, and some more are currently making the switch. Ubuntu, in particular, has worked wonders. If the fora are any indication, a lot of people have started using Linux thanks to Ubuntu.

    ``Clearly, if Linux is unable to reproduce a third of Firefox's end user uptake over a much longer time-frame, there are deficiencies with the direction the GNU/Linux/X/Gnome/KDE system has taken.''

    That's not so clear to me. Switching web browsers is a much smaller step than switching operating systems. That seems a simple and plausible explanation of why Firefox could be more popular than Linux.

    ``Of course, almost all free software and desktop efforts and development remain unquestioningly oriented around Linux.''

    Most, perhaps, but there's a lot going on around FreeBSD, Solaris, NetBSD, OpenBSD, Windows, and ReactOS, too, as well as around some smaller operating systems.

    ``Other free-desktop operating system projects which take different and innovative approaches like ReactOS, AROS, Mona and Syllable remain comparatively starved of developers and interest.''

    That is true, and it's probably a combination of factors. Particularly, the fact that GNU/Linux is a known quantity; it implements APIs that have been around for decades, whereas innovative APIs have yet to prove themselves. Secondly, the fact that many of these OSes don't stack up in terms of usability means that many people don't get past the stage of taking a look and going back to whatever they were using. Thirdly, "Linux" is very well known by now, thanks to hype generated by both advocates and the press.

    ``An often cited reason for using a non-Microsoft OS is to avoid a monoculture, but free-desktop efforts have created a total monoculture around developing and promoting Linux,''

    Now, that's really outrageous. First of all, GNU/Linux implements many standard APIs which are also implemented by other operating systems, meaning that monoculture, if it exists at all, is more of a choice made by users than something forced by developers. Secondly, some of the operating systems implementing said APIs are also Free, notwithstanding your suggestion that all free-desktop efforts are about Linux. Thirdly, people do actually use other Free OSes besides GNU/Linux. Fourthly, as long as Windows has the lion's share of the market, any increase in market share by another OS, including GNU/Linux, is likely to reduce monoculture.

    ``despite a decade of failure in supplanting Microsoft's proprietorial OSes with it.'' ...in some market segments, and among certain groups of users. Linux has made major inroads in segments other than the desktop, and even on the desktop, it's slowly but surely replacing Windows. I don't recall that I was walking into rooms or offices and seeing devices running Linux a lot a decade ago, but nowadays, it happens all the time.

    ``Why are free-desktop developers neglecting to consider an alternative to the penguin?''

    To the extent that they are, I would imagine it is because Linux works so well. This causes people to use it, and some of these users contribute to it.

    --
    Please correct me if I got my facts wrong.
  32. Firefox and Linux ... not really comparable by swanriversean · · Score: 5, Insightful

    This is a bit of a red herring. Firefox gained market share for a number of reasons, some that may be applicable to Linux as well. But the single biggest reason for Firefox's market share is that you could install it on Windows.

    I'm still looking for a Linux that's easy to install and use without having to "rebuild kernels, install hundreds of packages, etc". I tried Ubuntu and that never worked..."

    Have you ever tried installing Windows from scratch? That is like two days effort (by the time you get all your drivers and programs installed, and everything set up as you like). I don't think Linux is worse than Windows, just different. And for certain setups, its better (consider all the good programs that are already available by most distros default install).

    So, the main reason Firefox gained so much popularity compared to Linux, was that you could use it on whatever OS you were already using. Possibly this includes it being "so easy to install and use", but that is a misleading statement because you are implying a Linux distro isn't. Firefox installs like any other application on any supported OS, and is as usable as most mature programs. Linux distros are likely the easiest operating systems to install, but that doesn't really matter, because most people will never install an OS. Linux is quite usable, as long as you don't expect it to be the same as Windows or OSX and are willing to get used to it.

    --
    Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind. - Dr. Seus
    1. Re:Firefox and Linux ... not really comparable by DahGhostfacedFiddlah · · Score: 1, Troll

      Sorry, this simply isn't true. To get Windows to a point where I can use it, it's generally a four-hour process, and then gradual tweaking of things over the next few weeks.

      Linux is about a four-hour process too, for just the basic installation. But getting it to a point where I can use it is far more involved. I've had to edit XF86Config files to get my desktop how I want it, locate and install special codecs for mplayer, edit httpd.conf for my web server. For a novice, each of these things is about half a day of researching the problems and playing around with different configuration options. Even now that I've done them, I still have to refresh my memory on the dozens of different configuration file formats if I ever have to dive into them again.

      Windows *is* easier to use. Learn one interface (Next->Typical Install->Next->Next->Finish->Start Menu->All Programs->Click the program name), and you've learned 90% of what is involved in installing and configuring new software. For someone who's never used a computer before, maybe that is a half-day process as well. But Linux has different install interfaces every way you turn, and special cases out the yin-yang (not Linux' fault most of the time due to proprietary formats or patent issues, but that doesn't make the cases any less special)

      Maybe it's changed in the two years since my last install, but I doubt it.

      Bottom line - For a lot of things Linux is, more stable, more powerful, offers more fine control, and is simply a better OS for developers and sysadmins.

      But ease of use? Forget about it.

    2. Re:Firefox and Linux ... not really comparable by Chemicalscum · · Score: 1
      Maybe it's changed in the two years since my last install, but I doubt it.

      It has - install Ubuntu run Automatix2 to install the goodies you want - done fully featured working system. Tweak it if you like at a few extra apps though add/remove or synaptic no problem.

    3. Re:Firefox and Linux ... not really comparable by JoshJ · · Score: 1

      Windows *is* easier to use. Learn one interface (Next->Typical Install->Next->Next->Finish->Start Menu->All Programs->Click the program name), and you've learned 90% of what is involved in installing and configuring new software. For someone who's never used a computer before, maybe that is a half-day process as well. A lot has changed in the past two years. All I do to install a program is either load up a command line, go apt-cache search whatever, sudo apt-get install whatever or load up the add/remove programs dialog, search in that, and check whatever boxes I want and hit "apply". I assume most of the other top-notch distros have add/remove program dialogs (adept, synaptic, whatever).

    4. Re:Firefox and Linux ... not really comparable by swanriversean · · Score: 1

      Linux has come a long way in the last two years ... but still, if you're happy with Windows, why bother making the switch? And that is the point: you can't say that Firefox is primarily successful (market share) because it installs easily and Linux does not ... Firefox is primarily successful because it installs on Windows.

      Linux installs easier than windows, no doubt. You compare the best case scenario for Windows (by the way, what programs do you get installed in 4 hours ... and are all the updates installed ... how many reboots ... ) to the worst for Linux. (Who cares, right, just another guy's one-of experience, but I've installed Ubuntu, with everything you'd like in a couple hours ... and long before then, like the default installation's 20 minutes, I've had a usable system for many tasks.) But again, how many people are going to install their OS anyway?

      Lastly, ease of use? Yes, I know Linux + Gnome is a good user environment. My step father, my mother, my father, my sister, my wife have all used it, and still use it. Despite their imperfections, the DE's available today are usable, even, 'easy to use' (misunderstood concept that it is). And as too your:

      Next->Typical Install->Next->Next->Finish->Start Menu->All Programs->Click the program name what is so hard about (since you already seem to know the app you want)

      apt-get install app-name; app-name
      or the equivalent GUI sequence?

      Oh, it is a commercial application? If it is available on Linux, then you may get your installation wizard dream paradigm! Oh, so that's it, is it? Linux doesn't have some commercial application you want to use ... Oh, so the main reason why Linux hasn't been adopted isn't because it is too hard to install (for an OS), or too hard to use (anymore), but because millions of computers are shipped every month with Windows pre-installed, a platform which few third-party developers don't support, and works pretty much the same as any computer you've touched since 1995 ... and to use Linux I have to install another platform?

      While this may be true (although, Windows is pretty good for developers too, and decently stable, now):

      Bottom line - For a lot of things Linux is, more stable, more powerful, offers more fine control, and is simply a better OS for developers and sysadmins. it does not prove that Linux is unsuited for regular users, and my experience is that Linux + Gnome is suitable for regular users, except when some Windows-only application is the deal-breaker.
      --
      Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind. - Dr. Seus
    5. Re:Firefox and Linux ... not really comparable by Shaiken · · Score: 1

      Bullshit.
      You're comparing a simple windows install, with nothing beyond the most basic applications to a fully features Linux install, with a webserver and mulimedia capability.

      If you want to play divx on windows you need the codec. If you want a webserver on windows you need to install it. That's normal, but when you need to the the same goddamn thing on Linux it's suddenly a huge problem?

      Let me counter your silly example with a slightly less silly one:
      Whenever I upgrade/reinstall my laptop (openSuse 10.x) I need about 4 hours. Half an hour to backup my home directory, two hours to wait while the installer runs and an hour to set up the system again.
      Setting it up again is basically restoring my home directory and installing a few missing packets.

      The same thing on windows takes me twice as long and even so I never manage to reproduce all settings the way they used to be, because windows software insists on using that abomination of a registry. In windows I have to go hunt all over the net to find all of my software again, in Linux I can just use the package manager.
      I don't need to reconfigure the mail client, my bookmarks are all there, ...

    6. Re:Firefox and Linux ... not really comparable by VGPowerlord · · Score: 1

      I have, and it was relatively easy. Of course, that's probably because I had a slipstreamed Windows CD (which isn't owned "out of the box"), and everything else on hand that I needed to install on CDs (programs) and a USB flash drive (drivers, downloadable programs, important documents).

      On the flip side, what happens in Linux if the driver for my wireless card isn't in the distribution?

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    7. Re:Firefox and Linux ... not really comparable by neimon · · Score: 1

      "Have you ever tried installing Windows from scratch? That is like two days effort (by the time you get all your drivers and programs installed, and everything set up as you like)."

      Maybe for someone who doesn't know what he's doing. More like three to four hours tops if you have the proper preparation. Less than that for the OEM restore disk with the drivers and apps on it.

      Compare that with the bullshit you have to go through to make Firefox appear on your Gnome taskbar. Hah!

    8. Re:Firefox and Linux ... not really comparable by swanriversean · · Score: 1

      When I said Windows from scratch ... I meant all the applications you need to have a productive system.

      that is more than 4 hours.

      --
      Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind. - Dr. Seus
    9. Re:Firefox and Linux ... not really comparable by DahGhostfacedFiddlah · · Score: 1

      My Windows came with a webserver that is easily configured using a GUI. I can install the DivX codec using the exact same install sequence as anything else - NextNextNextFinish. Installing Visual Studio - same thing. Installation is a breeze. Configuration - as long as you don't need fine-grained control - is as easy as a few point-and-clicks.

      Is installing a codec as easy in Linux? What media player/writer are you using? What's the configuration format? Can you just drop the codec in the filesystem and forget about it? Sure, it's usually pretty easy to find out, but in Windows: NextNextNextFinish.

      Setting up a new virtual directory on your web server? Windows: Right-click your server, New Virtual Directory, Next, enter server path, Next, enter filesystem path, Finish. Every step logically follows the last to complete a simple task. Apache? Edit httpd.conf. If you've worked on it recently, or have a template to go on, you might not even have to look to the man pages. In Windows you could be asked to do it again next week and not have to pull in a single reference manual. In Linux, you're looking for an existing configuration file to copy, or going back to the man pages.

      Or maybe I can put this another way. I'm a geek. I ran Linux exclusively for three years. I've been programming since I was twelve. I've written clients and servers and simply enjoy tinkering.

      For installation and configuration, I find Windows programs have a smoother learning curve and make new things easier than Linux programs do (once again - two years ago - things may have changed). You may disagree, but you'd be in the minority - and when it comes to ease-of-use, majority opinion tends to rule.

    10. Re:Firefox and Linux ... not really comparable by Shaiken · · Score: 1

      You did forgot the step before Next,Next,Finish. Where did you find the installer? Did you virus scan it+ Can you trust it? My codecs came from Yast. They installed in exactly the same way as all (well, most to be honest) my other software. Because it's part of Yast I know I can trust it (no viruses, no spyware). I can control my HTTP sever using Yast as well, which means Next, Next, fill out server name, next, finish is all I need to do to add a virtual server.

    11. Re:Firefox and Linux ... not really comparable by DraconPern · · Score: 1

      I did an install of Ubuntu and Vista on the same laptop. Vista installed much faster. Then I wanted 3d acceleration. It was automatic in Vista. It took me 2 hours to get the ati driver installed on Ubuntu. I got xgl working for a while, then it broke my X11. XGL sucked so much anyways that I just reformated the whole thing and installed Vista.

    12. Re:Firefox and Linux ... not really comparable by Anonymous Coward · · Score: 0

      I've got a /. account, but since I lurk so much and don't post often, I can't for the life of me recall what the Nick was. Nor do I care to put myself through the effort of rediscovering it right now.

      Next time, you might want to define what *you*, specifically, mean by a fully productive system.

      I just had to rebuild my Windows XP desktop machine at home thanks to a faulty motherboard.. and since the chipset was just enough different between the two motherboards that the drives wouldn't boot anymore, I decided on a clean install of Windows XP.

      Total installation time, from full format to "complete" --- defined in this case as all drivers installed, all patches installed, full Office suite setup (I put both Office XP and OpenOffice on the machine), Firefox, Opera, Macromedia Studio, PuTTY, Trillian, VMware Player, and EverQuest... 3 hours. (Granted, the "install" of EQ was the original game CD for the registry entries, followed by a network copy of the folder from the XP laptop, but that's really the only shortcut I took.)

      Repeated... a home-brew box for which the only driver I installed from CD was for the onboard NIC... and I downloaded and installed all the other drivers and patches from the web... fully productive (for me) in three (3) hours.

      Now, my Fedora laptop took a little under three hours to fully build... again, including all patches, Firefox, OpenOffice, and VMware Player. Most of the time was spent watching the packages install from CD, then waiting for Package Updater. But getting EQ to run took another hour or so of fiddling with WINE; Trillian's not available, so I have to put up with GAIM, which is a poor substitute.

    13. Re:Firefox and Linux ... not really comparable by DahGhostfacedFiddlah · · Score: 1

      I found the installer using Google. Just like I would in Linux. Sure, maybe the software is available from apt-get, but generally I'd have to hit Google just to find out that the MP3 player for Linux is XMMS, so no extra time spent there.

      As for security - look, I'm talking about ease of use. Security is an afterthought - if that - by most home Windows users. You may not like it. I certainly don't. But it doesn't enter into the ease-of-use question. Installation from a website is the easiest thing ever. Click Download, NNNF.

      The problem is, the Linux world is inhabited by some pretty smart people who are willing to put in the effort to use Linux. If Linux is ever going to take the home desktop, the community has to ask itself "What if I had the IQ of a retarded monkey and the attention span of a gnat?".

    14. Re:Firefox and Linux ... not really comparable by Jynx77 · · Score: 1
      Have you ever tried installing Windows from scratch? That is like two days effort (by the time you get all your drivers and programs installed, and everything set up as you like).
      I just installed Windows Vista on my son's PC (needed bigger/faster hard drive) "from scratch." Didn't have to install/upgrade a single driver and this is a "home-built" PC. It was literally less than two hours including the time require to install a couple of games. Totally painless.
      --
      It's turtles all the way down!
    15. Re:Firefox and Linux ... not really comparable by swanriversean · · Score: 1

      try that again just before service pack 1 ...
      oh, try to install office too, around the same time

      --
      Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind. - Dr. Seus
    16. Re:Firefox and Linux ... not really comparable by Anonymous Coward · · Score: 0

      I did install office. 0 problems.

  33. Mu by swillden · · Score: 5, Insightful

    The premise of the question is that Linux' lack of desktop market penetration indicates some failing with Linux. I think that premise is flawed. I think Linux has achieved more desktop market share than could reasonably be expected in the time elapsed, and that all of those who have predicted more widespread use were simply fooling themselves.

    See, every bit of desktop market share that Linux achieves must be taken away from the Microsoft desktop monopoly (plus maybe a bit from Apple, but that's a tiny corner of the market and one that is very hard to crack). That means that Linux has to deal with the fact that pretty much all of the desktop software in the world, and all of the PC hardware in the world, is built for and around Microsoft Windows.

    Look, for example, at the reasons why people here on /. commonly say that they don't want to (or can't) switch to Linux:

    1. Hardware support. Some bit or piece of their system doesn't work properly under Linux. While these problems are rarer than they were in the past, they'll never go away completely until Linux is big enough that hardware vendors do what's necessary to make sure their hardware is supported on Linux.
    2. Software support. Whether it's games, photo or video editing tools, Microsoft Office, or whatever, the other major complaint about Linux is that it doesn't have whatever app the user wants. The Linux community's response has been to try to build Free versions of everything the user might want. That's great in many cases, but in many others what the user wants is *exactly* the particular app they like on Windows, rather than something similar.

    Looking beyond the slashdot crowd to the more general PC user base, Linux has another, even bigger obstacle: Most people don't install their own operating system, ever. They buy a PC with an OS already on it, and that's what they use. What OS comes on every PC on the shelf? The latest version of Microsoft Windows, of course.

    Given that these are the real problems holding back widespread desktop adoption of Linux, what is some other OS, that supports less hardware and has less software available, and even less mindshare among PC vendors going to do to fix the problem?

    Not a damned thing, obviously.

    Desktop Linux will make its breakout, if it does, in exactly the same way that Desktop DOS and Windows achieved theirs -- via the business desktop. In the more-controlled corporate environment, where hardware is less varied, the IT support staff is better educated (i.e., there is an IT support staff), application sets are more limited (e.g. no games), and there is a stronger focus on cost containment and security, Linux is beginning to make some inroads, and will continue to make more. Linux is getting serious attention as a preferred desktop platform by governments, both for reasons of openness and for reasons of cost management.

    When a significant percentage of the world's desktop PC users use Linux at work, then you'll start to see significant home market penetration as well. And that business desktop penetration is happening, but it's going to be a long, slow process because it's a fight against a very deeply entrenched and very powerful monopoly.

    I think Linux is doing an excellent job of getting there. The Free desktop environments and application suites are in excellent shape, and are continuing to improve rapidly. I think KDE and GNOME are both much *more* usable than MS Windows, each in their own way, and I can cite numerous Free applications that rival or even exceed the best of their commercial competition. Linux is *ready* for the desktop, and has been for quite some time. But being ready isn't enough to displace Windows. There have to be other advantages, to counter the massive juggernaut of Windows inertia. And there *are* other advantages, but even so, it will take time. Lots of time.

    People don't focus much on the other a

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    1. Re:Mu by symbolic · · Score: 1

      ooking beyond the slashdot crowd to the more general PC user base, Linux has another, even bigger obstacle: Most people don't install their own operating system, ever.

      No install? With Windows? Are you serious? I'm willing to bet that this is the most common operation recommended by most sources that offer Windows support:

      1. Make sure the computer is plugged in.
      2. If it's already running, try rebooting.
      3. If 2. doesn't work, re-install Windows.

    2. Re:Mu by XO · · Score: 1

      Looks like you're still stuck in 1990, along with the Linux desktop :(

      --
      "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
    3. Re:Mu by pwhysall · · Score: 1

      Most people don't reinstall Windows in the literal sense; they simply follow the procedure for re-imaging their machine back to the factory state with the not-real-install CDs they got with the box.

      --
      Peter
    4. Re:Mu by bcrowell · · Score: 1
      I agree with most of your points, but I think you're oversimplifying in some ways.
      1. Part of the problem with getting linux to be more widely used is that it's difficult or impossible to get a PC with Linux preinstalled. Heck, it's very difficult to get a PC (especially a laptop) without Windows installed. Installing an OS, any OS, is way too hard for most people. And there's a tendency for consumers not to want to buy something (a copy of Windows that came preinstalled) and then throw it away and use something else.
      2. I know at least two novice Linux users who basically gave up on Linux, and from listening to them talk, it sounds like a lot of the wasted effort was installing applications. To someone who is used to Linux, runs Ubuntu, and knows how to use apt-get or synaptic, it seems like, "WTF? Why is this even an issue?" The problem is that these people aren't used to Linux, and aren't running Ubuntu or any other Linux derivative.
      3. A lot of people have a ton of documents in Office formats, and if they were to import them into OOo, they'll lose at least some of the formatting and functionality. That may seem to a Linux geek like it's not a big deal, but in reality, it's just not on the average person's agenda to spend weeks or months fixing everything that broke in their documents. (It took me about 5 years of off-and-on work to finish converting all my books from PageMaker to TeX.)
      4. It's still a huge hassle, on every Linux distro, to get a bunch of little stuff working: peripherals, flash drives, audio and video codecs, browser plugins, wifi, ... Often if you haven't planned ahead by buying Linux-compatible hardware, you simply won't be able to switch to Linux. I think this is the area where the OP's assumptions had the most validity. There definitely is a lot of stuff like this that's harder to do on Linux than it needs to be, and the problems could be solved. OTOH, many of the problems are due to lack of cooperation from hardware manufacturers.
      5. Most people don't have the knowledge of OSS and pro-OSS sentiments of the slashdot crowd. I was just talking to my mom's new boyfriend about OSS over the holidays, and by the time I left, we were at the stage of, "Huh? Why would anyone make software and give it away for free. Don't they need to make money?" This could be both good and bad for small, alternative OSes. It could be good since public knowledge of Linux is so scanty that people's minds are basically blank slates. It could be bad because, realistically, if people haven't heard of Linux, they're even less likely to have heard of Syllable.
    5. Re:Mu by swillden · · Score: 1

      I agree with most of your points, but I think you're oversimplifying in some ways.

      Am I missing something? It looks to me that you just pointed out some specific cases that support my argument. I didn't mention the issue of familiarity (your example was how software is installed), but I think that's a lesser issue. If the other ones were solved, that one would be manageable.

      Your last point is an interesting one, though, in that "Why do they do that?" is a hard question to answer. It's not hard to answer because the reason is obscure or unfathomable, though, it's hard to answer because there isn't a single answer.

      My answer to that question is something like: "There are different people working on it, and they have different reasons. Some do it because they can make money selling support services to business that use Linux. Some do it because they like programming and think its more fun than what their boss pays them to do. Some do it to build up their resumes. Some do it because they think it makes the world a better place, like working for the Peace Corps, or donating their time to a charity. And some do it because the commercial software doesn't do what they want, so they make their own that does. There are probably 100,000 people working on it, and there are about as many reasons as there are people."

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    6. Re:Mu by kripkenstein · · Score: 1

      There is one problem with your argument here. Yes, the Windows monopoly is the biggest thing standing in the way of Linux desktop adoption, and yes, software and hardware support are the crucial issues. But Linux alternatives may do better than Linux is getting around these things. For example, ReactOS intends to be binary-compatible with Windows, both for device drivers and for applications. If they achieve that goal, it would make them a far better candidate to replace Windows than Linux, for the vast majority of users.

      Linux isn't taking that approach because of FOSS principles, which I agree with personally, but that doesn't stop me from admitting that other approaches may work better in some ways.

    7. Re:Mu by bcrowell · · Score: 1

      Am I missing something? It looks to me that you just pointed out some specific cases that support my argument.
      My point #4 works at least partly against your argument, because I'm claiming that in some cases, Linux actually does make certain things harder than they need to be, and an alternative OS could try to make those things easier. My point #2 is likewise against your argument, because I was pointing out that many flavors of Linux make software installation harder than it has to be, and an alternative OS could try to do better. My point #3 wasn't about the unavailability of software, it was about the fact that no software ever can or ever will be 100% compatible with Office formats. My point #5 was about awareness, which you hadn't addressed.

      I didn't mention the issue of familiarity (your example was how software is installed), but I think that's a lesser issue.
      I don't think it's just a familiarity issue. Fundamentally one of the problems with the bazaar method of OSS development, as it applies to Linux and Linux apps, is that the method is incapable of picking winners and losers. Even though apt works great, there are still all these distros out there that make it more difficult to install software, and those distros are never going away or changing to a better method.

      Your last point is an interesting one, though, in that "Why do they do that?" is a hard question to answer.
      My point wasn't that he asked that particular question, it was that he was so unfamiliar with the whole concept of OSS that that was the basic level we had gotten to by the time I left. This complete lack of knowledge and interest works against Linux, but could work either for or against alternative OSes if they want to outcompete Linux.

    8. Re:Mu by swillden · · Score: 1

      My point #4 works at least partly against your argument, because I'm claiming that in some cases, Linux actually does make certain things harder than they need to be, and an alternative OS could try to make those things easier.

      I disagree that Linux makes it harder than it needs to be, or that an alternative OS can do better. The issues you mention arise from two sources: (1) lack of support from hardware vendors and (2) patents. Any alternative Free OS will be in the same boat as Linux with respect to hardware support, but probably worse (unless it can use all of the Windows drivers, which creates its own set of issues). And any gratis OS will have issues with the patents on audio and video codecs, just like Linux does. Of course, there are non-gratis Linux distros that provide legal, licensed copies of the relevant codecs. That issue is orthogonal to the question of which OS you want to use.

      My point #2 is likewise against your argument, because I was pointing out that many flavors of Linux make software installation harder than it has to be, and an alternative OS could try to do better.

      I'd like to see what would be easier than Linux! Linux is certainly easier than Windows. Perhaps the Mac drag-n-drop approach? Actually, though, that's not an OS kernel issue, it's entirely a userspace issue. If there's a better way to do it, it makes more sense to implement that on Linux rather than abandon all of the Linux hardware and software support.

      Fundamentally one of the problems with the bazaar method of OSS development, as it applies to Linux and Linux apps, is that the method is incapable of picking winners and losers. Even though apt works great, there are still all these distros out there that make it more difficult to install software, and those distros are never going away or changing to a better method.

      Actually, the approach to software installation and management is pretty homogeneous in Linux now. Sure, LFS, Slackware and a few other small distros do it differently, but everything else is either deb/apt, rpm/yum or ebuild/emerge -- and all three of those effectively work the same way from a user perspective. In fact, you can even use the same GUI tools for all of them (so I've heard; I pretty much stick with Debian).

      From the user's perspective, software installation on Linux is both easy and consistent -- you run the add/remove programs app, pick the software you want, and click install.

      My point wasn't that he asked that particular question, it was that he was so unfamiliar with the whole concept of OSS that that was the basic level we had gotten to by the time I left. This complete lack of knowledge and interest works against Linux, but could work either for or against alternative OSes if they want to outcompete Linux.

      It seems to me that all Free OSes would raise exactly the same questions. I don't see a distinction here.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:Mu by bcrowell · · Score: 1

      >>My point #2 is likewise against your argument, because I was pointing out that many flavors of Linux make software installation harder than it has to be, and an alternative OS could try to do better.

      > I'd like to see what would be easier than Linux!
      I didn't say easier than Linux, I said easier than some flavors of Linux.

      >Linux is certainly easier than Windows.
      I was just reporting that two people found their distros more difficult than Windows, so evidently, for them, software installation on Windows was easier than on their distros of Linux.

      > Perhaps the Mac drag-n-drop approach? Actually, though, that's not an OS kernel issue, it's entirely a userspace issue. If there's a better way to do it, it makes more sense to implement that on Linux rather than abandon all of the Linux hardware and software support.
      As I said in my previous post, I think some distros have implemented something better. The problem is that there are still all the other distros' systems running around.

      >Actually, the approach to software installation and management is pretty homogeneous in Linux now. Sure, LFS, Slackware and a few other small distros do it differently, but everything else is either deb/apt, rpm/yum or ebuild/emerge -- and all three of those effectively work the same way from a user perspective.
      Huh? It sounds like you're saying all fruit is the same, except that of course blueberries and watermelons are different, but apples and pears are similar from the user's perspective.

    10. Re:Mu by swillden · · Score: 1

      I was just reporting that two people found their distros more difficult than Windows, so evidently, for them, software installation on Windows was easier than on their distros of Linux.

      But the example you gave was an issue of familiarity, not ease of use.

      Huh? It sounds like you're saying all fruit is the same, except that of course blueberries and watermelons are different, but apples and pears are similar from the user's perspective.

      Apples and pears are identical from a user's perspective, and only experts eat blueberries or watermelons, so they don't really affect new user adoption. Does that clear it up?

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  34. You should check harder. by Generic+Player · · Score: 1

    First of all, they come with very little GNU stuff, pretty much just the compiler/toolchain. And that is maintained as a patched version for the OS in question. Of course, I didn't say anything about GNU software, I said most open source software. Download some random software from sourceforge, half of it won't compile on anything but linux, and even then often only i386 or i386 and amd64. And the stuff that does compile is often subtly broken because of linuxisms or gnuisms in it. Hell, I've seen plenty of stuff that won't even work on all popular linux distros. Assuming broken glibc behaviour, or stupid GNU extensions is very common in open source software since most people writing it have never tried unix before, so they assume the entire world is just like their distro or choice.

    1. Re:You should check harder. by lahvak · · Score: 1

      First, GNU is not Linux. I agree that there is awfully lot of software that relies on gnu. But that does not tie the software to Linux. Most of application that I use on daily bases works just as well on any version of BSD, and even Windows. I agree that there are programs out there that compile only on red hat and nothing else, but I would not say that majority of free software is like that. AFAIK Solaris ships with Gnome desktop.

      Yes, there are incompatibilities in Unix world. First there is the old east-west (System V and BSD) division, then GNU and nonGNU, then linux and unix.

      One of the main ideas of free software is that you can take any damn thing that only compile on some obscure version of Red Hat, edit the damn code, write a good makefile or configure script, and make it run on whatever common or exotic system you use. If there is an application you care about that does not compile with your cc, fix it and submit the patches.

      --
      AccountKiller
    2. Re:You should check harder. by Zoolander · · Score: 1

      GNU is not Linux
      GNL?

      --
      Meep.
    3. Re:You should check harder. by MoxFulder · · Score: 1

      This may be true, and it's certainly something to be remedied. However, I must say that this is usually just because the developers only have access to Linux boxes. As open-source software becomes more popular, things like GNOME, KDE, Gaim, HAL, cdrecord get modified to be more standards-compliant and work on more flavors of Unix.

      As always, this the great thing about open source... if it doesn't compile on your box, you can tweak it until it does, then submit the patch and help everyone else out. I did this a few months ago when I wanted the Ogg Theora video codec to use MMX optimizations on x86_64... patched the code, and now everyone with a 64-bit box can use optimized video encoding. Yay!

    4. Re:You should check harder. by Generic+Player · · Score: 1

      "First, GNU is not Linux. I agree that there is awfully lot of software that relies on gnu. But that does not tie the software to Linux."

      That's why I mentioned both linuxisms and gnuisms. There's both. The bizzare linux /proc is not gnu anything, its part of linux. Software that expects that is relying on a linuxism.

      "AFAIK Solaris ships with Gnome desktop."

      Yes, and they had to spend a lot of time and effort correcting the code so it would work properly because Gnome is developed by linux users, for linux users, on linux. It is linux software. The fact that 3rd parties are required to port Gnome to unix OSs means its not unix software, its linux software.

      "One of the main ideas of free software is that you can take any damn thing that only compile on some obscure version of Red Hat, edit the damn code, write a good makefile or configure script, and make it run on whatever common or exotic system you use. If there is an application you care about that does not compile with your cc, fix it and submit the patches."

      This doesn't change the fact that many people do in fact write linux software instead of unix software. I could spend my entire life fixing people's unportable code, and having them ignore the patches, or worse yet accept them, then in 2 months have re-broken it all. That's not the point though. The point is the thread was started by a linux user making the false assertion that open source software is portable and not linux-centric because he's never used anything but linux. This is incorrect, tons of open source software is linux software, and much of what does work elsewhere works elsewhere because of other people, the software is still linux centric and forcing other people to constantly patch it to work.

    5. Re:You should check harder. by Mr.+Hankey · · Score: 1

      This doesn't change the fact that many people do in fact write linux software instead of unix software.

      That's a result of the fact that there are in fact many more Linux users than users of the other *NIX systems. (OS X excepted of course, as it's less often used as an *NIX for various reasons.) It's like complaining that there's more Windows software than OS X, or Solaris software vs. AIX, and complaining alone won't get you anywhere.

      In the case of Linux software however, you're a lot closer to a "port" (really portability patches) than a Winxx/OS X port. The X11 backend is the same, most of the C library is the same, and the differences typically aren't that difficult to work around. Differences exist in other forms of *NIX as well, remember that your favorite OS isn't the only one out there. The effort to perfect a software package for another *NIX/X11 platform is typically quite minimal when compared to systems with wildly different APIs, and that was really the point.

      --
      GPL: Free as in will
    6. Re:You should check harder. by EsbenMoseHansen · · Score: 1

      And it's not even just GNU... BSD have their own quirks, like strlcpy, which are so badly thought off that the glibc maintainers (and Linus for that matter) refuses to adopt it into glibc.

      However, porting is fairly trivial between unixes. I should know, I've ported stuff to the unix compability layer in Z/OS, which is frankly terrifying implementation of the POSIX and related standards. Tracking down subtle bugs are, of course, not so easy, though valgrind and gdb are a tremendous help.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    7. Re:You should check harder. by Generic+Player · · Score: 1

      "It's like complaining that there's more Windows software than OS X, or Solaris software vs. AIX, and complaining alone won't get you anywhere."

      No its not, its like saying "yes, McDonald's does sell hamburgers" to someone who says "I don't think McDonald's really concentrates on selling hamburgers". I didn't complain, I pointed out that the "insightful" post that started this thread is in fact completely incorrect. I know linux sofware is written because there's so many linux users. That in fact proves my point, people are writing linux software.

    8. Re:You should check harder. by BrainInAJar · · Score: 1

      "I must say that this is usually just because the developers only have access to Linux boxes"

      Solaris is free, all the BSD's are free... no excuse other than laziness

    9. Re:You should check harder. by Mr.+Hankey · · Score: 1

      That does indeed back up your observation, but it doesn't invalidate the original poster's point. Linux software is very similar, and often identical, to what you are calling UNIX software. "Porting" is generally trivial when compared to ports between other, less similar systems.

      Many UNIX systems are different in small ways, so there will typically be a few changes needed to make any given software package run on different systems. I've built software on Linux systems from kernel 1.2 to 2.6, SunOS 4.x, Solaris, IRIX, Tru64, SCO, FreeBSD, and a number of other UNIX variants. They each have their differences, but the basic concepts of X11 and the basic C libraries are very similar.

      --
      GPL: Free as in will
    10. Re:You should check harder. by Generic+Player · · Score: 1

      There is no invalidating his point, he is simply wrong. What he said is incorrect.

      "It is very unlikely that developers follow Linux only."

      Yes, that is exactly what most of them do. They use linux, and develop on and for linux.

      "They support some well documented and mature standards like Gnu Libc, X window and POSIX, among others."

      Glibc is not a standard, and the fact that people do program for it is "following linux only".

      "Infact, for example, most of the desktop software can be compiled and run under almost all OS that comply to those standards."

      In fact, most of it cannot. It has to be altered to work on all the other OSs. Because it is written for linux.

      See, he is wrong, and clearly you know that since you've pointed out reasons why people write linux code. How easy or hard it is to fix that code is both irrelivant, and varies tremendously depending on the code.

    11. Re:You should check harder. by MoxFulder · · Score: 1

      I disagree. There's no laziness involved. Even if there's no monetary cost to testing on other OSes, developers have only a finite amount of time. If they choose to devote it to making their software work on one operating only, that's their business. Since we're talking about open source software here, I will again suggest that anyone who needs to get software working on a variant platform try hacking on it him/her self... it's easier than you think :-)

      Especially when they're not getting paid to write the software (as is the case in many FLOSS projects), there's no reason anyone is ENTITLED to have that software work on any other OS.

      That being said, many open source projects DO make cross-platform compatibility a goal. For example the GNU tools, the Upstart daemon to replace SysV init (even though it was written by the Ubuntu folks!), GNOME, KDE, etc.

    12. Re:You should check harder. by Mr.+Hankey · · Score: 1

      Not really. Not everything is dependent on one platform or another. By your logic, if people wrote software for Solaris then they were writing code not for UNIX but for Solaris only; In order to compile for SunOS 4.x, HPUX, AIX, IRIX, Tru64, Free/Net/OpenBSD, and other UNIX systems there would need to be changes made because each system is a bit different.

      He's not wrong in stating that most code can be compiled on all systems, because it can with little effort. Some projects may not be as widely ported as others, and might need changes to work on your favorite OS/Kernel, but I've built software for many systems that weren't necessarily the original coder's targets and it's not that difficult. You're simply trying to pin Linux and GNU systems down as the only odd ones out there, whereas most systems have a variety of small differences.

      The most differences for that matter are probably between the BSDs and SysV based systems. Take a look at the output of autoconf's "configure" on multiple UNIX flavors and you'll see what I mean; even SysV systems can have different numbers of arguments for various library functions.

      --
      GPL: Free as in will
    13. Re:You should check harder. by Generic+Player · · Score: 1

      "Not really"

      Yes really. People develop for linux. He said people don't develop for linux. But that's exactly what they do. Its very simple.

      "By your logic, if people wrote software for Solaris then they were writing code not for UNIX but for Solaris only; In order to compile for SunOS 4.x, HPUX, AIX, IRIX, Tru64, Free/Net/OpenBSD, and other UNIX systems there would need to be changes made because each system is a bit different."

      Right, they would be devloping for solaris. But people don't do that. People who develop primarily on Solaris or a BSD of their choice are almost always nice enough to test their software on other free OSs and make sure it works. I can understand people not making sure their stuff works on AIX or HP-UX or whatever, but solaris and BSDs and linux and darwin are all free. There's really no reason not to make your software work on them besides laziness.

      "but I've built software for many systems that weren't necessarily the original coder's targets and it's not that difficult."

      That depends on the software. Trivial software tends to be trivial to port. Go get wine working on openbsd and tell me how easy that is.

      "You're simply trying to pin Linux and GNU systems down as the only odd ones out there, whereas most systems have a variety of small differences."

      No, it has nothing to do with linux being the odd one out, its just popular. And I am not pinning anything, I am simply correcting a completely wrong statement. It would be just as dumb to develop software for netbsd/arm only and not bother testing it out on other platforms. But that's not what people do.

      "The most differences for that matter are probably between the BSDs and SysV based systems. Take a look at the output of autoconf's "configure" on multiple UNIX flavors and you'll see what I mean; even SysV systems can have different numbers of arguments for various library functions."

      No need, I actually write unix software in C. I know there's alot of differences. And I test out my code on a wide variety of hardware and software platforms before making releases so that I don't let BSDisms creep into my software. I am not sure why you keep trying to convince me of things I am already aware of, what does any of this have to do with the original post? Yes, people do develop directly on and for linux, with no regard to other OSs. That is exactly what happens in many cases. Hence the original post claiming people develop for posix plus nonexistant "standards" is wrong. The part about people coding for glibc is correct however, he just seems to mistakenly think glibc is a standard.

    14. Re:You should check harder. by Mr.+Hankey · · Score: 1

      Right, they would be devloping for solaris. But people don't do that. People who develop primarily on Solaris or a BSD of their choice are almost always nice enough to test their software on other free OSs and make sure it works.

      Most definitely not. The vast majority of code out there gets developed for one OS (particularly Win32 and embedded operating systems, but it happens enough in the *NIX world too) and runs there. It gets ported only if the need arises. I've seen a lot of software development where I work now and in previous jobs, and have contributed to open source projects myself (typically offering Linux development services to a project.) That's just how it goes in most cases. When Open Source/Free software supports more than one platform, it's typically because there are multiple developers with different requirements. Most open source applications are developed to scratch an itch, if someone else has their own itch they're welcome to scratch it. Often you'll see projects asking for assistance in testing/developing for other platforms. More people will complain rather than doing anything, but that's human nature.

      Go get wine working on openbsd and tell me how easy that is.

      Not to be rude, but really, why would most people care? It works on several other platforms, including FreeBSD which is common enough that I have an installation of it myself on my laptop and in VmWare. I even have a copy of Syllable, but not OpenBSD. If there are enough people who want WINE on OpenBSD then it'll get there, but it doesn't sound like there are. Remember that WINE is a large project, and needs a bit of support from those who use fringe platforms to ensure that it works there. Of course, most software packages are not a Win32 API implementation and ABI loader, and thus tend to be much smaller with fewer piles of code to check. An ABI loader in particular can be very system specific since it deals with loading CPU opcodes into an executive layer. Why don't you help them with the port, since you have expertise with so many UNIX systems and seem to want it to work? It's not going to happen without people who care.

      It would be just as dumb to develop software for netbsd/arm only and not bother testing it out on other platforms. But that's not what people do.

      I work with plenty of people developing for embedded systems, and I see a lot of software that is never ported to anything other than the target system. It's the real world, dumb as it may be. The software you write may be different, and that's great, but people work within their desire/resources and not everyone can/will test on every platform imaginable. Does your code run on Tru64 and IRIX? On all CPUs supported by Linux, or platforms without a flat addressing space? Do you do develop for the VMS or NT POSIX layer?

      No need, I actually write unix software in C. I know there's alot of differences. And I test out my code on a wide variety of hardware and software platforms before making releases so that I don't let BSDisms creep into my software.

      That's great, but as you already know you're in the minority if you feel the need to test on multiple platforms. Developers will write to their target platform, be it Linux, BSD, Solaris, AIX or whatever. There's nothing special about this, and it takes an interested contributor to fix it in the open source/Free software world. In the closed source world it takes money more than anything else. If your definition of UNIX software must include every variant, then there are few to no true UNIX developers left. Luckily, most large software projects have multiple developers and people who manage and keep alive code for various platforms.

      As previously mentioned, WINE works on FreeBSD and PC-BSD. It works on Solaris, Windows, and is packaged for six Linux distributions. Why doesn't it work on OpenBSD as well, considering they actually package binaries for the aforementioned platforms? In all likelihood, it's because noone cares enough to do anything about

      --
      GPL: Free as in will
    15. Re:You should check harder. by Generic+Player · · Score: 1

      "Most definitely not. The vast majority of code out there gets developed for one OS (particularly Win32 and embedded operating systems, but it happens enough in the *NIX world too) and runs there"

      We're talking about open source projects remember? Seriously, every project I know developed primarily on a non-linux unix is tested and fixed for linux at least, and usually BSD and solaris as well. This doesn't occur very often going the other way.

      "Not to be rude, but really, why would most people care?"

      Not to be rude, but are you incapable of grasping simple concepts? I DO NOT CARE. You said its trivial to port software, I pointed out an example of how non-trivial it can be. Why do you persist in pretending I give a shit about porting any given piece of software? I have made it very clear several times now that I am simply correcting the false assertion that people don't develop for linux. They do.

      "GLIBC is part of the GNU system and uses GNU conventions. That's about as close to a standard as one can get in the current fragmented UNIX environment"

      No, there is the C standard actually.

      "In all likelihood, it's because noone cares enough to do anything about it. Do you?"

      No, I do not. Try to read what you are replying to.

    16. Re:You should check harder. by Mr.+Hankey · · Score: 1

      We're talking about open source projects remember? Seriously, every project I know developed primarily on a non-linux unix is tested and fixed for linux at least, and usually BSD and solaris as well. This doesn't occur very often going the other way.

      For Free and Open Source software, sure it does. Successful projects which interest developers who prefer other platforms are developed for those platforms. That's how Open Source and Free software works. If it doesn't happen, the project was likely not all that successful or interesting for the developers who prefer those target systems. If there aren't very many people who prefer those systems, as seems to be the case with OpenBSD, then it may never be tested. It might work, might not.

      You said its trivial to port software, I pointed out an example of how non-trivial it can be.

      It works on FreeBSD, which is a BSD and not Linux. Tell me then, why is it so difficult to get it running on OpenBSD? Is WINE FreeBSD software as well? It's not because WINE is impossible to port; probably not even as difficult as you think. It's because most OpenBSD developers don't care enough to put forth the effort. Even Mac OS X/Darwin has a project to get WINE running. Unless someone's interested in paying a developer to manage the difference, or OpenBSD becomes enough like a supported platform (like FreeBSD) that it starts working, then the lack of interest will prevent it from being supported. This is not a failing of all other platforms, nor of the software.

      Why do you persist in pretending I give a shit about porting any given piece of software? I have made it very clear several times now that I am simply correcting the false assertion that people don't develop for linux. They do.

      I'm not pretending; I'm telling you you're complaining about fringe platforms being ignored that do not in themselves define UNIX. There are in fact ports available for systems that more people care about and use. Many people develop applications on Linux, and if this is all one would base a "Linux application" on then you would be correct. Unless it's using actual kernel functions to utilize a specific resource however, you're using the GNU C library and the functions that come with it. That's the GNU platform, not Linux. Yes, it differs from BSD in some ways. If you're saying that there are a lot of GNU applications that never get ported to your favorite platform, then that in all likelihood means no developers on your favorite platform were interested in assisting with the application's development. If it sees a lot of use and is worth the effort to port, it'll probably will work on FreeBSD at least. A reasonable number of people actively use it. This is not a failing of the GNU platform, nor an issue particular to Linux.

      No, there is the C standard actually.

      There was the K&R compiler and there have been several variants of ANSI C, but C itself is a rather minimal standard. C compilers have extended the standard simply because C by itself doesn't do that much. C was intended to be small, easy to optimize, and easily extensible. Some extended elements went in several directions on different platforms. The UNIX APIs that we use today are by no means all part of a standard C API, and these differences are typically where you'll find incompatibilities. Most programmers I know go with the current ANSI C standard as supported by their compiler and OS libraries.

      No, I do not. Try to read what you are replying to.

      You're complaining that a lot of software is written on Linux and somehow never gets ported to other platforms. Yes, there's a lot of software written on Linux. There are a lot of Linux users out there, and many tend to be developers. No, that doesn't mean it's all automagically Linux-only software. It just means that not enough people care to try it or modify it (when necessary) for the less-used platforms. It's the same catch-22 that Linux users complain about with Windows software really. Most developers

      --
      GPL: Free as in will
    17. Re:You should check harder. by kv9 · · Score: 1

      Go get wine working on openbsd and tell me how easy that is.

      cd /usr/ports/emulators/wine; make install clean. shit, that was hard!

    18. Re:You should check harder. by Generic+Player · · Score: 1

      "For Free and Open Source software, sure it does."

      Name some examples then. There's tons of open source code that is targetted directly at linux. There is very little targetted at any other unix. I know several people who develop exclusively on solaris or their BSD of choice, and all of them have linux and either solaris or a BSD (whichever they aren't using obviously) installed in a VM of some sort for testing. I don't know of anyone who develops primarily on linux and does the same. They all just assume real unixes are scary and hard to use and so rely on other people to fix their code for them.

      "It works on FreeBSD, which is a BSD and not Linux. Tell me then, why is it so difficult to get it running on OpenBSD?"

      Because FreeBSD people took the time to fix it for FreeBSD. And they keep taking that time over and over and over again since the wine developers keep writing more linux only code.

      "Is WINE FreeBSD software as well?"

      No, its linux software that dedicated FreeBSD fans have ported.

      "probably not even as difficult as you think."

      Probably exactly as difficult as I think, I tried. Now you go try instead of pretending its so easy. You are insulting all the people who spent the time getting it working on FreeBSD with your ignorance.

      "I'm not pretending; I'm telling you you're complaining about fringe platforms being ignored that do not in themselves define UNIX"

      Yes, you are pretending. I have made it very clear over and over and over again what I am saying, and you are ignoring that, pretending I am saying something else, and arguing against that. You don't need me for that, go argue with your made up pretend me on your own. You can grab an old sock and make a me puppet to argue with if you can't respond to what I say instead of what you want me to say. Just make sure you give the me sock puppet a nice moustache.

      "If you're saying that there are a lot of GNU applications that never get ported to your favorite platform"

      I didn't say they never get ported, I said THEY NEED PORTING. Much of it is ported, some is not. Either way its totally irrelivant, the point is that it needed ported to begin with because the authors wrote it for linux + gcc + glibc. What the hell kind of mental block is crippling your ability to grasp this simple concept?

      "Most programmers I know go with the current ANSI C standard as supported by their compiler and OS libraries."

      No, they ignore the C standard and go with gcc + glibc.

      "You're complaining that a lot of software is written on Linux and somehow never gets ported to other platforms."

      This is the last time I will say this, obviously you are choosing not to listen because you like strawman arguments. I am making this as clear as I possibly can, please read this instead of making up more bullshit and pretending I said it:

      PEOPLE WRITE SOFTWARE FOR LINUX.

      Are we clear? That is what I am saying. That is all I am saying. I am not complaining about anything except your refusal to stick to what I am saying instead of what you want me to be saying. The original poster claimed that people do not write software for linux, but again, and as you are clearly aware of since you've admitted it over and over:

      PEOPLE WRITE SOFTWARE FOR LINUX.

      It is a correction of the incorrect post. Nothing more. Stop reading anything else into it, everything else is in your imagination. Its unfortunate that in trying to demonstrate to you that PEOPLE WRITE SOFTWARE FOR LINUX, you focus in on all sorts of details in the examples and ignore the point, that PEOPLE WRITE SOFTWARE FOR LINUX.

    19. Re:You should check harder. by Mr.+Hankey · · Score: 1

      Name some examples then.

      Well, we're supposedly discussing the desktop. I'll pick a few from mine. How about KDE? A large number of KDE apps originated on Linux. XMMS definitely originated on Linux, and it works on OpenBSD. The mplayer program works on OpenBSD as well. It took a few minutes to come up with and verify that list. The list grows much larger when you include FreeBSD, since more people seem to use it.

      Probably exactly as difficult as I think, I tried. Now you go try instead of pretending its so easy. You are insulting all the people who spent the time getting it working on FreeBSD with your ignorance.

      Scarcely, FreeBSD has everything that WINE needs to run. When OpenBSD supports everything that WINE currently needs, it won't be as difficult so much as potentially time consuming given the size of the code. A cursory look into the issue shows that kernel level thread support is currently holding back the OpenBSD port, which isn't a WINE issue as much as an issue for OpenBSD threads. Older versions which did not require this support did run on OpenBSD. Once OpenBSD thread support is considered a stable target, and a WINE developer ports the thread code, OpenBSD should get a port again. WINE can be run on other BSD systems until then.

      No, its linux software that dedicated FreeBSD fans have ported.

      It's software that now has a FreeBSD port. Your insistence in calling it Linux software is where we disagree and will continue to do so. Unless it accesses a kernel specific resource, there's nothing Linux particular about it. There may be GNUisms, or code that leans toward SysV, but that's a different issue.

      PEOPLE WRITE SOFTWARE UNDER LINUX.

      Fixed it for you, and now we're crystal clear.

      --
      GPL: Free as in will
    20. Re:You should check harder. by Generic+Player · · Score: 1

      "Well, we're supposedly discussing the desktop. I'll pick a few from mine. How about KDE? A large number of KDE apps originated on Linux. XMMS definitely originated on Linux, and it works on OpenBSD. The mplayer program works on OpenBSD as well. It took a few minutes to come up with and verify that list. The list grows much larger when you include FreeBSD, since more people seem to use it."

      Huh, why are you listing software developed on and for linux? I asked for examples of people writing code for solaris or BSD that linux users have to fix to get working, since you claim that happens too.

      "Scarcely, FreeBSD has everything that WINE needs to run."

      So do openbsd and netbsd. It was alot of work to get wine running on freebsd, dismissing the work those people did won't make it dissapear.

      "When OpenBSD supports everything that WINE currently needs, it won't be as difficult so much as potentially time consuming given the size of the code"

      It already does support everything wine needs. Its still as difficult to port right now as it was yesterday.

      "A cursory look into the issue shows that kernel level thread support is currently holding back the OpenBSD port, which isn't a WINE issue as much as an issue for OpenBSD threads."

      A cursory look into the website you mean. OpenBSD has kernel threads. Rather than reading an incorrect note someone who didn't try porting wrote, try compiling the code. You will see it has nothing to do with kernel threads at all. Hell, I've had wine developers tell me that OpenBSD is fully supported and the latest wine works on it fine. They don't seem to pay much attention to what works and why.

      "WINE can be run on other BSD systems until then."

      No, just freebsd and the freebsd compatible systems (PC BSD and such). It doesn't run on netbsd either.

      "It's software that now has a FreeBSD port."

      Has a freebsd port because of freebsd users. It was and is developed on and for linux, and requires 3rd parties to fix it. If the developer of the software made sure it ran on freebsd, then it wouldn't be linux software. But if the developer just develops it on and for linux, and then 3rd parties have to fix it for other OSs, then its clearly targetting linux, like I said, and contrary to the original posters blately incorrect statement.

      "Your insistence in calling it Linux software is where we disagree and will continue to do so. Unless it accesses a kernel specific resource, there's nothing Linux particular about it. There may be GNUisms, or code that leans toward SysV, but that's a different issue."

      Linux isn't just a kernel, its also an OS. Wether you like the fact that linux is a name for 2 things or not won't change that. Even all the indignation that RMS can muster has not and will not change this. Using glibc functionality is targetting linux (the OSs), as that is what linux (the OSs) includes with linux (the kernel).

    21. Re:You should check harder. by Mr.+Hankey · · Score: 1

      I do see that I misread your question re: BSD/Solaris apps that will not run under Linux. As for software that was written for BSDs or Solaris that has trouble running on Linux, that's the whole point I suppose. While there may be less of these packages, there tend to be enough volunteers who will work with the software's developers to ensure that it does work under Linux. Developers have more users to gain by supporting the Linux platform, assuming that's their goal. Compiling them is not always a picnic even under Linux, if you've ever built OpenInventor from scratch you'd see what I mean. Sometimes a bit of modification is required. Still, it's almost always possible. The GNU environment actually helps a lot in this regard, and the kernel interfaces tend to be kind to programs from other platforms. Kernel modules are a different story, but that's not end-user application software.

      In the end, most software I build runs on the UNIX, FreeBSD and Linux/GNU UNIX-like systems we support. For that reason, I'll call it UNIX software. There's the occasional hiccup with IRIX and Tru64, regardless of where the code came from, but I have both compiled trivial and non-trivial software on all of them when needed. I'm happy to say that I don't need to support the OpenBSD platform in our environment, nor NetBSD for that matter, and won't support its inclusion in the future given the trouble you seem to be having.

      --
      GPL: Free as in will
    22. Re:You should check harder. by Generic+Player · · Score: 1

      "As for software that was written for BSDs or Solaris that has trouble running on Linux, that's the whole point I suppose. While there may be less of these packages, there tend to be enough volunteers who will work with the software's developers to ensure that it does work under Linux"

      Its not volunteers though, its the developers. I develop on openbsd since its a much better platform for C development than other unixes. I fix it for linux, solaris and hp-ux (and test on freebsd and netbsd, but only occasionally have to fix a freebsd problem, it usually is fine). I know people who develop on Solaris, and they test on linux and freebsd too. They don't just release their code as-is and wait for users to submit patches to get it working on linux and BSDs, they take the time to do it themselves. This is the difference, developers are writing for linux, and making other people fix it. This doesn't happen the other direction (ignoring of course OS included utils, I don't expect Sun to make sure their userland software runs on linux and BSD).

      "In the end, most software I build runs on the UNIX, FreeBSD and Linux/GNU UNIX-like systems we support."

      Because someone ported it. It was developed for linux, then 3rd parties fixed it for other OSs. This isn't a difficult concept. Most of the software I build runs on most unixes too, including netbsd and openbsd, and dragonflybsd. But I am also more careful and look through config.log's and see the little oopses and fix those, instead of blindly ignoring them because "it compiled so its ok". As someone who has submitted the patches that make software "just work" on various OSs, I find it insulting that you assume everything has just always worked and nobody has been involved in making that the case.

      "For that reason, I'll call it UNIX software"

      You can call it whatever you want, but that doesn't change the fact that it is, contrary to the original posts assertion, targetted at linux.

      "I'm happy to say that I don't need to support the OpenBSD platform in our environment, nor NetBSD for that matter, and won't support its inclusion in the future given the trouble you seem to be having."

      The only trouble I am having it getting you to grasp the simple concept of "yes, developers do target linux specifically". I am not sure how that is either openbsd's nor netbsd's fault, but I do hope you will try to avoid them. I know its a little schadenfreude, but I do take pleasure in knowing dumbasses go out of their way to make their lives worse to spite other people. I always get a laugh at the linux users who whine about how BSD X is not exactly like linux, "so I'm going to go back to linux and not using BSD, take that!". Like it somehow hurts me that you are avoiding better operating systems. Ow, my pancreas!

    23. Re:You should check harder. by Mr.+Hankey · · Score: 1

      Yes, thank you again for all the ammunition I'll ever need to avoid those two particular flavors. Linux, FreeBSD and Solaris should suffice for any purposes we'll have.

      --
      GPL: Free as in will
  35. This is retarded by inaneframe · · Score: 1

    How in the hell can any of you talk in definites in an industry shown to be indefinite? How can you give one or two examples/reasons, weak ones at that, and then hyperbolize them into some "universal principle" of the software industry and somehow indicative of the future? You give weak comparisons and draw weaker analogies. I can count but two or three other main replies to this article that make any sense. You should all be hung, drawn, and quartered. Fucking retards, sorry but this shit is stupid!

    Firefox is a browser. Stop. Linux is a popular kernel for free software distributions. Stop. How do you begin to compare the two?

    Over half of the world hold to the Christian faith, very few people are Atheist. Does that mean that there is some inherent flaw within Atheism?

    Most of the world eats meat. Does that mean that Vegetarians need to rethink their approach?

    You call Linux developers and free software proponents zealots, look at yourselves! The free software movement is not here to replace your hated OS, it is not here to be the next big thing, or the newest golden child and it most definitely is NOT just GNU/Linux. It was never meant to be the golden child and any one who expected that is clearly dillusional. It is not here for the immediate future, they are not looking at some commercial strategy, they don't need to reinvest in their packaging and they are not interested in competing with a dying operating system.

    If you are so convinced that GNU/Linux/BSD/Free Software are not going anywhere and will never go anywhere than stick with your bloody mass of a bullet ridden dying operating system. Free Software is not qualified to compete on those grounds, the same that Microsoft is on. If the market wants to run Free Software, it needs to change the way that it operates or move on. Free Software will not go anywhere, it will still be here no matter what.

    Sorry if GNU/Linux is not meeting your expected quotas Mr. CEO's. Let us all strive to do a better job of marketing less this board of the chair of Free Software cancel Linux!

    --
    "Creationists make it sound as though a 'theory' is something you dreamt up after being drunk all night." -Asimov
    1. Re:This is retarded by toganet · · Score: 1

      Thank you for pointing this out. This is a symptom of one of the worst (in my opinion) aspects of American culture -- the idea that, as if the Highlander were running things, There Can Be Only One!

      Choice and Freedom are supposed to be at the root of not just the Free Software Movement, but the American Way Of Life. In reality, the US is a conformist culture at its heart, and is run by people who seek to force their choices onto others because they cannot imagine a case where someone who chooses differently does not, ipso facto, choose wrongly.

      Just as multiculturalism is seen as a threat, heterogeneity in desktop platforms is taken a symptom on non-conformism.

      Now that I think of it, the Linux v. Microsoft v. Apple battle for the desktop may work as a microcosm for the US as a whole. In much the same way as celebrities get to break all the puritanical rules laid down by mainstream culture while wallowing in the spotlight, Apple can 'Think Different' and be the media darling. Meanwhile, Linux is derided as difficult to use and fit only for "geeks". Heck, it might even be illegal -- it's definitely un-American! Probably Communist!

    2. Re:This is retarded by inaneframe · · Score: 1

      I, personally, have no doubt that the future of operating systems and most productivity software will be within Free Software. But there is something that subconsciously eludes most of the people here and in most places and it is this: Free SoftwareLinux and LinuxFree Software. Yes Linux is a Free Software kernel and yes it is the term commonly used for the GNU/Linux operating systems but it is NOT Free Software, only OF Free Software. In the future you will have many more options as to what you would like to run on your computers and most of those options will be Free Software and will likely be very compatible with most other Free Software OS options. Some day the GNU/Linux OS as we know it will no longer exist, there will be another kernel that will fuel the community for the next 30 years and that is par for course for Free Software. No matter what happens it will still be Free Software. . . Almost anything resembling Unix may disappear from what they currently call GNU/Linux and you will not be able to call it GNU OR Linux but one thing will remain the same. It is still Free Software. For the time being the current most popular Free Software operating system is GNU/Linux and that is the state of things. And it is popular! Don't believe me? The three largest software companies are: Microsoft Oracle Novell And they are all distributing Linux this year. If you ignore the Free Software bit, which I try not to, there are two main systems around now--NT and POSIX (and if you are inside of NT with SFU than you are also POSIX compatible, sorta)

      --
      "Creationists make it sound as though a 'theory' is something you dreamt up after being drunk all night." -Asimov
  36. pre-installed... by Anonymous Coward · · Score: 0

    Yeah right, people go to the store and shop for an OS - they don't even know what an OS is. Might as well ask, "Which is better, Beige or Translucent computers.". If somebody wants linux to be cool then Gnome & KDE need to special order a bunch of pc cases with nice power supplies.

  37. patie de foi gras by Anonymous Coward · · Score: 0

    BSD developers are force feeding geese?

  38. Haiku by 11223 · · Score: 3, Informative

    Don't forget Haiku, the free BeOS reimplementation. What's been done so far is impressive for the number of developers working on it; if a few more developers joined the progress, I (personally, IMHO) think R1 could happen this year.

    1. Re:Haiku by donstenk72 · · Score: 1

      I loved BeOS at the time (1998-99?) and I haven't seen anything that snappy since.... Wonder if one wanted cutting edge today, what system would you want: SuSE or Ubuntu Linux? Very pleasant, hardly innovative - where can you try out that new suse start menu in VMWare? Vista? Never seen it, if it is anything like WMP11 or IE7 I don't like it. OSX? From the few times that I have used friends Mac's and edited video's etc I must say it's very simple and intuitive, but hardly innovative. What about Leopard - is it worth putting forward a MacBook purchase? Thanks, Don.

  39. Reactos is being ignored? I don't think so. by kimvette · · Score: 2, Informative
    Other free-desktop operating system projects which take different and innovative approaches like ReactOS(snip) remain comparatively starved of developers and interest.


    It seems to me, in theory at least, that every Free/Open Source Software project developed for/ported to Windows is in effect developed for or ported to ReactOS - at least once ReactOS actually works.

    Maybe the reason it is not well supported and tested is that the driver installation process is an absolute beast. Ever try to get an All in Wonder card set up in ReactOS? I got partway through and quit out of sheer boredom.

    Why?

    Here is the process:
      - Install a clean Windows installation (Win2K for this situation)
      - Dump the registry
      - Capture a file listing of the entire system. Don't forget to include meta data such as file size, date, and version
      - Install the All in Wonder drivers/software
      - Dump the registry
      - Capture a file listing of the entire system. Don't forget to include meta data such as file size, date, and version
      - Diff the registry dumps, create a patch file (a properly-formatted .reg file)
      - diff the file listing, figure out which files $vendor changed, note location
      - Import the registry into ReactOS
      - manually copy the files over
      - watch it croak. Use depends or another dependency checker to figure out what else needs to be copied from Windows to ReactOS to make it work (and if you do not own a Windows license, at this point copyright law becomes an issue, especially if you want to offer a "free" and *cough*"100% compatible"*cough* Windows alternative to customers)

    Why does ReactOS enjoy more support, including developer, tester, and user? Gee, I don't know. That's a tough question.
    --
    The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
  40. It's called "momentum" by betelgeuse68 · · Score: 1

    A simple principle that holds up when the bull (real one) is charging at you as well as metaphorically.

    The road is littered with technology panaceas spanning the gamut from programming languages that are the "greatest" and "will make developers far more productive" to operating systems that never went anywhere, e.g., BeOS.

    Call me jaded, who cares about the others you mentioned. LINUX still sucks on the desktop for average users, largely because the software ecosystem that surrounds Windows is so massive and is quite hard to ignore. Just let me listen to music and play games (and no, I don't mean "checkers"). I want to install and run iTunes without thinking about downloading emulation software. I want to play cutting edge games.

    I like LINUX on the back end but that is about it (as far as its proximity to my desktop). My strategy has been to leverage open source technologies on Windows, Cygwin, PERL, etc., etc. Besides I can always fire up the X window server and view graphical applications on Windows. Kudos to MIT for such prescience two decades ago, i.e., "the network s the computer."

    -M

  41. Monopoly Lock On the Desktop by codepunk · · Score: 2, Interesting

    In order to dominate the desktop the monopoly currently strangling the market needs to be removed. The linux desktop does not dominate only because of the noose on the OEMs and it is also the reason BEOS got no where.

    I am no Mac fan but I actually think that apple currently has the ability to shake the market to it's core. They now have a intel version of the operating system, increase the driver support and put it on the shelves and I think it could really create a explosive impact on the home desktop industry.

    --


    Got Code?
    1. Re:Monopoly Lock On the Desktop by Anonymous Coward · · Score: 0

      Won't ever happen for very simple reasons. OSX does not run on commodity hardware. No Apple OS ever will, because Apple makes their money as a hardware company. Running on commodity hardware is what gave Windows its dominance since the OEM could buy whatever hardware they want at whatever price point they want and slap an OS on it.

      Apple will never hold a considerable share of the market for those simple reasons, and in dropping "Computer" from the name of their company they've shown that they really truly don't give a shit about that fact.

    2. Re:Monopoly Lock On the Desktop by sowth · · Score: 1

      We don't need a dominating player in the market, we need a market where no one dominates. If there is no leader, then nature dictates that all the players have to use standards or they will be limited to niche markets. Standards for everything, so programs will run on all the different systems without adapting the code. This is why things like OpenGL, libc, ELF, Ansi C and such are so important.

  42. X11 sucks, that's why! by Temkin · · Score: 1, Insightful



    X11 was great back in 1990. But we've stuck with it for too long. The various widget sets built on top of it (motif/gtk/etc...) are just lipstick on the pig.

    Look at OS X... Throw out X11. Implement a nice clean OO GUI desktop, and add a rootless X11 compatability layer back in for the legacy apps.

    1. Re:X11 sucks, that's why! by arevos · · Score: 1

      Could you give some specific examples with what is wrong with X11, or is this merely an opinion piece?

    2. Re:X11 sucks, that's why! by Anonymous Coward · · Score: 0

      OS X is cool and all but it would be much cooler if I could export the display and also have multiple terminals on the same host.

      I'm a UNIX admin. I ran Linux on my desktop for the better part of 6-7 years. I gave it up and bought a Mac in 2003. You'll have to pry my Powerbook from my cold, dead hands before I let you saddle me with the pile of steaming bullsh!t that is the Linux desktop.

    3. Re:X11 sucks, that's why! by WhiteWolf666 · · Score: 1

      Aroo???

      X11 does things that other GUIs can only dream of. While X11 development languished for quite some time, the freedesktop movement is dragging it kicking and screaming into the future.

      What, pray tell, is it that you don't like about X?

      That its fast, lightweight, extensible, network transparent, and desktop agnostic?

      That it can be compiled to work on anything from an iPaq to a home desktop to a server to a mainframe?

      That it is a venerable, tried and true solution from gaming platforms to 25+ multi-monitor displays?

      What's wrong with X?

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    4. Re:X11 sucks, that's why! by Anonymous Coward · · Score: 0

      look at beryl/compiz and drool

    5. Re:X11 sucks, that's why! by mechsoph · · Score: 1
      What's wrong with X?

      As someone who used X11 on Linux and Solaris every day, my biggest complaint is it's sensitivity to latency. Apps are essentially unusable across a WAN while Citrix on the MS side and even VNC perform significantly better for that case.

      Supposedly NoMachine's NX fixes that problem. It would be nice to get something like that rolled into the standard.

    6. Re:X11 sucks, that's why! by Kazoo+the+Clown · · Score: 1

      If you don't know what's wrong with X, then you're part of the problem.

      Flying windows around the screen very fast or in 3D, isn't what anyone but windowing software developers care about. What needs to be exceedingly fast is how it performs from the application and then user's point of view and how easy it is to program that application. And how easy is it to tie things like scanners and realtime vidcap devices into it. If the answer isn't "lots BETTER than OS X or DirectX," then it's short of the mark.

      It'll take more than a few government agencies getting behind ODF and Linux, especially when they choose to do so for cost or freedom reasons, and not because they think that Gnome or KDE is "better." In mundane office situations it can be marginally "good enough," but that's not enough to start a worldwide mass exodus.

    7. Re:X11 sucks, that's why! by istewart · · Score: 1

      OS X was great back in 1990, too, when it was called NeXTSTEP and used a Display PostScript backend. Just because an established technology is old doesn't mean it's worthless.

    8. Re:X11 sucks, that's why! by Anonymous Coward · · Score: 0

      If you don't know what's wrong with X, then you're part of the problem.

      Or he's just never come across (or has no problem with) the issues you've described, which makes you the problem.

    9. Re:X11 sucks, that's why! by pato101 · · Score: 1
      Completely disagree.

      I don't see any problem with gtk/Qt. There are cross-widget themes like qtcurve -which provides gtk and Qt native themes- that allow you to unify the look in case that is what you miss from other systems. Nevertheless IMHO having same colors through toolkits is fair enough. Motif sure it is outdated, but there are still some efforts to make it better (antialiased fonts are almost there), and some apps like NEdit deserve be used despite of the old look of Motif- again using same colors than your gtk/Qt makes it look quite good.

      Having several toolkits has the benefit of being able to have different desktops oriented to different needs. Again NEdit will run on any old machine, meanwhile gedit or kate might be slow there. Anyone remembers tkdesk?. Also, people may experiment with new and old concepts, as GNUstep project does.

      On the other hand, I use to work with more than one computer. I love to do "ssh -CX other_computer" and launch the apps I need from there: I don't want another full desktop, just the app(s) I need. In this sense, IMHO the flexibility and performance of X11 over LAN is the best solution. And it is available for *every* app, not just the legacy ones. Even OpenGL apps (thanks to GLX extension) use the display hardware when used remotely

      Finally, the look and feel of X11 is being largely improved with Compiz/Beryl. Your pig is a very fast and beautiful one, nowadays.

    10. Re:X11 sucks, that's why! by Anonymous Coward · · Score: 0

      Hello id***

      if X11 performance is slow because you have an old CPU, select configuration -> login screen -> configure X server -> add the option -wm to the command line. This enables backing store "when mapped". After that your computer will consume much more memory (similar to what the memory hog known as "Mac OSX" consumes) but it will perform MUCH faster. To enable 3d simply click on configuration -> enable 3d effects.

      Everything else you wrote is pure nonsense. What does a scanner have to do with the X11 graphic sub system.

      > lots BETTER than OS X or DirectX

      Maybe not for OSX or Windows trolls like you. But for most Linux users it is.

      > Gnome or KDE is "better."

      WTF does gnome or kde have to do with X11?

    11. Re:X11 sucks, that's why! by WhiteWolf666 · · Score: 1

      NX fixes the problem 100%. You should try it.

      NX vastly outperforms VNC, and IMHO, is better than Citrix.

      Grab the FreeNX packages, and give it a whirl. It's really easy to install, and the client supports NX, MS Remote Desktop, and VNC.

      NX improves the responsiveness of all three.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    12. Re:X11 sucks, that's why! by WhiteWolf666 · · Score: 1

      Your Slashdot handle seems to reflect the quality of your posts.

      Please go do some research on the performance of X. It's very, very fast; faster than everything else out there except for some proprietary X servers.

      Furthermore, its modular nature makes it far more extensible than OS X's Aqua, or even Vista's WGF (renamed DX10).

      X is substantially better than OS X or Direct X. It's faster, it's lighter, it's more extensible, and it's more portable. It's got a far greater number of features, and when you encompass the full "ecosystem" of X software (including stuff like Compiz) it out "blings" OS X/Direct X. There's a reason that pro video editing works great on X system.

      And what the hell do scanners have to do with a windowing system? That's the realm of raster graphics, not something to be handled in the windowing system.

      Show me a network transparent windowing system with 1/4 of the performance of X, and I'll show you a liar.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  43. Re:False Problems by mpapet · · Score: 1

    The problems the stated will get non-win32 operating systems nowhere.

    No one *wants* to change simply to substitute one OS for another. No one! They switch when there is a problem with their computer that they get so sick and tired of dealing with, they go to another platform.

        My Dad (an aol user no less) switched when I told him I won't fix his Windows box any more. Switched to Linux, got AOHell working and never looked back. He wanted a new PC, so he got a mac mini. Why? Because I won't support windows.

    In his case he was compelled to switch, as nearly every user that actually switches. There are many many people that talk, but few actually do. Copy-cat applications will never drive adoption. Apple is a visible example where the applications are driving adoption.

    Today's lesson: It takes a compelling application, not one that already exists in the Windows world to make people switch. The variety of apps is the fertilizer out of which a killer app will come that will make people switch.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  44. Its simple. by dilvish_the_damned · · Score: 1

    Linux sucks less. Mostly.
    Besides, did you have a better plan? And why is it better? Anyhow most mature OSS projects strive for some measure portability, so this question smells pretty rhetorical.

    --
    I think you underestimate just how much I just dont care.
  45. Argh by magicrobotmonkey · · Score: 1

    I wish i could delete this question from my brain

  46. NO its not by criscooil · · Score: 1

    It is not a "false analogy". Its not even any kind of analogy. It is a non sequitur. This is not pedantic. It is completely different.

    --

    My life is an open book ... up to a point.

  47. Re:ReactOS is an abortion of an OS by Anonymous Coward · · Score: 0

    ReactOS is one of the more interesting projects around. Like FreeDOS, ReactOS fills an important niche in the free software family tree. A free NT/2000/XP clone would be extremely useful for many individuals and organizations. Plus, there is a lot of knowledge to be gained by the mere act of trying to do this. Certainly there has been cross fertilization between the ReactOS project and WINE.

    I'm a Linux user, and am happy with Linux for my purposes. But I will be giving ReactOS a try after its next release. It won't replace Linux for me, but complement it.

  48. Gentoo speed highly dependent on setup by Anonymous Coward · · Score: 0

    Unless you have put the portage folders and /usr/tmp on a different filesystem from /home and/or / then your gentoo will over time become much slower than pretty much any other system.

    Gentoo has to be the worst-case usage for causing a filesystem to get fragmented and to scatter data all about, with its hundreds of thousands of tiny portage files that get updated/modified/deleted regularly along with lots of large files (source tarballs) mixed in with compile cycles that make lots of temporary that get mixed in with that. Sometimes say when a compile fails the compiled files get left in /usr/tmp/portage for a long time, then finally get deleted leaving 'holes'.

    Since I made /usr/tmp, /usr/portage, /var/db and /var/tmp links to a separate reiserfs (not reiser4) partition gentoo has been much faster.

  49. KDE runs just fine on Darwin/MacOS-X by Archeopteryx · · Score: 1

    And I imagine on almost anything that implements the right libraries and hooks. I think it is up to the advocates of a particular OS to port in the desktop, not the desktop developers.

    --
    Dog is my co-pilot.
  50. is this fucking Digg.com? by redhat_redneck · · Score: 0

    blatant flamebait. I thought that was the point of having editorial control ... to control trolls- right, cmdrtaco or are we just going to be lord to the flies and shit. If you'd used any of those platforms you'd know why their development starved and anyway why don't you develop on them, dipshit.... having windows and linux is not a monoculture you, asshat... I just quit smoking sorry, I'm not previewing it, and you can go shove your karma up some developer ass who ignores systems that have no users and no apps and no fucking reason to live .. so there ....

  51. BSD is Dead. by chopper749 · · Score: 0

    If you had read /. yesterday, you would have known that.

  52. Open source is very alive on windoze by Anonymous Coward · · Score: 0

    This toll doesn't know what the hell he is talking about. One just need to look at AVRFreaks to know that open source is often better supported on winblows to the dismay of many of us Linux users. If I want good development on Linux, be with the ARM or AVR I must often do it on my own as the bulk of the fancy support is on windoze and not on Linux.
    The irony is that the code is linux (and or Unix) code to start with.

  53. Costs Is Too High by rawg · · Score: 0, Troll

    This is simple. It would cost too much to develop free software on the MS platform. Just think of all the time you will spend working around stability issues and support problems. Then you have to figure out all the undocumented API's and hidden functionality. On top of that, Windows doesn't have half the support, libraries, and code that Linux/FreeBSD has. You have to even _pay_ for the stinking OS to program free software on it.

    Why would you want to program free software on something that is not free to develop on?

    --
    The above is not worth reading.
  54. device drivers. by Russ+Nelson · · Score: 1

    A desktop is all about the device. Linux will always have better device drivers htan any other open source os.

    --
    Don't piss off The Angry Economist
  55. My personal reason... by DoofusOfDeath · · Score: 1
    Why are Free-Desktop Developers Wedded to Linux?
    Because it hurts more you twit!
  56. your installation instructions by Anonymous Coward · · Score: 0

    ./configure
    make
    su
    (enter root password)
    make install
    exit

    Have fun with your new software!

  57. Linux is an OS/ Firefox a Browser... Duh! by Bryansix · · Score: 1

    Obviously it is harder to get people to switch to a completely different OS which means they have to change all of the software they are using compared to switching just to a more secure and just as easy to use web browser. The article summary is flamebait!

  58. Re:I not anymore a Linux User by Anonymous Coward · · Score: 0
    A Unix admin who needs office and photoshop? What the hell kind of work are you onto?

    Sorry, but I smell troll. Your post just doesn't make sense.
    Some of us have hobbies that have nothing to do with what we do for a living. Maybe after you move out of your mother's basement, you'll find out there's more to life than what you can type in at a command prompt.
  59. OLPC uses Redhat by timezra · · Score: 2, Insightful

    This post will probably be less relevant in 7 months when the OLPC project ships its first units. In a few more years, when this project is in full bloom, then the majority of desktop users in the world (maybe not the US) may very well be running the Linux kernel on their desktops.

  60. Clearly, if Linux is unable to reproduce a third . by T-Ranger · · Score: 2, Insightful

    Thats not clear, at all.

    A web browser and a OS Desktop are very different things, and require very different reasons to switch. Perhaps most importantly, whereas many users have noticed that IE began to suck (with viruses, popups, et al), Windows just is; for non-Windows users, its always sucked. For Windows users it just has been; and 95-98-XP, it has gotten better. The Firefox marketing campaign has been "Take back the web", not "Get a brand new web that you don't know about".

    The effort to implement a switch to FF, from IE is 5 minutes. And to become just as proficient as a user, from a couple of hours to a couple of days. For Windows to some other Desktop, days and months. The "undo" time for FF is 0, IE is still installed. Undo Linux may be 0, or as much as a few days too.

    To repeat myself: browsers and Desktops are very different things; users annoyance with them is different, the effort to switch is different. Comparing the relative "success" of OSS versions of these different things is blatantly wrong, and a disservice to hackers on both teams.

  61. General Motors Anaology by Anonymous Coward · · Score: 0

    Think of Linux, which is a kernel not really an overall OS per se, as General Motors. You have your choice of Chevrolet, Buick, Pontiac, Saturn, Saab, Cadillac, etc. But underneath it all is General Motors. Linux is just an inner core that developers can build whatever they want around it.

  62. Innovative? by salimma · · Score: 1
    Other free-desktop operating system projects which take different and innovative approaches like ReactOS...


    In what way is a clone of the Windows kernel innovative?
    --
    Michel
    Fedora Project Contribut
  63. Because.... by Kjella · · Score: 1

    ...it's one of three underlying kernels (win32, linux, osx/darwin) that have something like a market share?

    Besides, I'm very excited to see what happens with KDE4 is released for Windows, bringing the whole free desktop to the biggest market there is - Windows. If that works out well (KDE + games + whatever else win-only apps you need, I don't see how it couldn't) then that might be the gateway. People that find they don't need Windows can "pull the carpet" moving from KDE/Windows to KDE/Linux, and even if they stay on Windows their fileformats are compatible with Linux. I certainly look forward to that.

    --
    Live today, because you never know what tomorrow brings
  64. Looks like a false analogy to ME by Anonymous Coward · · Score: 0

    Analogy: Linux is like Firefox
    Observation: Linux is much less popular than Firefox
    Conclusion: Linux is doomed.

  65. It's the applications, stupid by amyhughes · · Score: 1

    The trouble with linux isn't linux, it's the lack of big-name applications. The FOSS solution has been to create free alternatives, and that's fine if your market is yourself, but normal people don't want programmerware.

    I recently wrote about why GIMP and other great applications aren't useful to normal people. The short of it is that when you google for a way to accomplish a graphic design or photo editing task you find tutorials that work with Photoshop and don't work with GIMP. If you want a book you'll find only Photoshop books at Borders. No matter how good GIMP is it's inaccessible to normal people.

    [She says, sitting down to learn Illustrator with a Borders-purchased book.]

    1. Re:It's the applications, stupid by Anonymous Coward · · Score: 0

      The corollary to this is that the F/LOSS community on Linux has made Linux toxic to vendors trying to make a living off of software. Fundamentally, the overwhelming majority in the F/LOSS community are just a bunch of cheap tightwads that insist on getting everything free (as in beer - not liberty). The viral nature of the GNU licence is merely a symptom of this predilection.

      Back in the day, vendors had the same problem with OS/2, and the only major customers for OS/2 apps were institutions that insisted on buying only from IBM. Typical OS/2 fanboys had the same tight-fisted nature back then that typical Linux fanboys do now. End result - OS/2 is dead.

      Normal vendors won't look at Linux (for the desktop) without hedging their bets with some sort of cross-platform toolkit.
      And if a program is available in cross-platform, vendors discover that the only customers that are actually willing to pay will be the Windows flavored ones. It makes less and less sense to develop for customers that won't pay.

      The things that normal vendors do that institutional vendors and fanboy developers don't include
      1) listening to end user's complaints and responding with reasonable solutions
      2) making the software simple to use and understand by cleaning up the interface and documenting the crap out of it
      3) adding a bit of glitz to the application to make it appealing enough to not want to run away from
      4) making it easy to install and configure

      This all costs serious money and a fair amount of non-developer skillset work that has to be paid.

      Unless normal application vendors can find a way of making money from Linux desktop development,
      the Linux desktop will never fly.

    2. Re:It's the applications, stupid by btolle · · Score: 1

      "This all costs serious money and a fair amount of non-developer skillset work that has to be paid. Unless normal application vendors can find a way of making money from Linux desktop development, the Linux desktop will never fly." The lack of apps is a real problem for us "normies". I am in the process of switching to a dual boot WinXP/Linspire system because I have some apps that simply won't run in Linspire or any other Linux flavor. There are Microsoft apps that are great and cheap, one example is MS Streets & Trips. For ~$30 I get a map of the entire US that is very accurate with the driving distances, has all the highways and most of the city streets on it. What programmer is going to write a Linux program equal to that for free? And I have too much invested in some apps where Linux has absolutely no alternative to consider switching. For instance, I have 5 states worth of Maptech Terrain Navigator that cost me close to $500 and allows me to plug my GPS into my laptop and use the USGS 1:24,000 maps to navigate. Since we love offroading there is no substitute for the above when wandering 4WD drive trails in Utah and Colorado. One other thing that has kept me away from Linux for years is the "geek attitude" that seems to be prevalent. If you ask a question on a forum the first thing you get is some "geekspeak" about how to run something from the command line. I am not afraid of the command line, I have been using computers since the days of the C/PM86 operating system which predates MS-DOS by a few years so I am not afraid on the command line but when I can't even understand what to put on the command line it doesn't help me. I think Linux has an opportunity to make some real headway once people start looking at the price of Vista and Office 2007 along with all the DRM stuff MS has stuck into it. That was precisely what made me decide it was time to make the switch. XP is bad enough with it's activation scheme, I have no intention of going down the Vista road. Like it or not, Linspire has made it a lot easier for us "normies" to look at Linux. When I can click on an icon in CNR and the programs installs automatically and works I am happy. When you start using "rpm", "packages", and such you will see me roll my eyes. I am enough of a "half geek" that I can live with a dual boot system, but say "dual boot" to the ordinary PC user and they will think you are talking about a pair of shoes. Bill Tolle

  66. I'll ask just the opposite. by Enahs · · Score: 2, Interesting

    Why, when you have an OS that has support for a lot of hardware, modern niceties such as hotplugging hardware, building blocks such as X11 and standards-compliant building blocks such as CUPS, why must that be ditched in favor of a from-scratch effort such as ReactOS? Or why should it be a necessity to target a server-targeted OS such as FreeBSD?

    --
    Stating on Slashdot that I like cheese since 1997.
    1. Re:I'll ask just the opposite. by sowth · · Score: 1

      Linux is a server targeted OS. It is based on the ideas Unix/Posix and X11 which are most certainly server/client based. Though I don't see project trying to copy MSWin as a good thing...

      What needs to be done is an original project made for the desktop from the ground up. I can't say if there are any which fit the bill or not...

  67. what a nonsense by Anonymous Coward · · Score: 0

    I strongly disagree with the person who posted these nonsense statements. For the past year Linux has been enjoying tremendous popularity and now even larger corporations are switching to Linux to escape horrors of Windows XP and the outrageous licensing fees of desktop slowdown of Vista. A bit more collaboration and joining of forces would help but overall Linux is currently the best basis for free desktop development and is definitely heading in the right direction.

  68. XServer on Windows by flight_master · · Score: 1

    I was flipping through a software catalogue a while back, and I know I saw a few XServer for Windows apps, so, doesn't that also mean you could run KDE/Gnome on Windows? I do know there is a F/OSS window manager for Windows, I used to use it, but can't remember the name now.

    --
    "Free software" is a matter of liberty, not price.
  69. Why should we care about "supplanting" windows? by ghettoimp · · Score: 1

    I don't know why anyone cares about this.

    I've been using a Linux desktop for about eight years and it's generally been quite nice. I have a windows machine, and I know how to use it pretty well, but I only turn it on when I want to play a game. Maybe I'm just set in my ways, but I don't think I'd enjoy using the Windows machine for much else, since I wouldn't care for not having virtual desktops and a useful shell.

    But it doesn't really affect me if other people want to use Windows for their own reasons. I can still use Linux when I want to. Lots of people are constantly improving it, and I get to enjoy their efforts. I suppose if my bank stopped supporting Linux or something, that might be irritating, but it seems that the trend has been for more people to support Firefox since it's gaining traction on Windows, so it probably won't happen.

  70. "It will be the last OS" by npsimons · · Score: 1

    I probably shouldn't be encouraging such trollish behavior by responding to this flamebait article, but here goes:


    Free-desktop developers are "wedded" (well, they aren't really) to GNU/Linux because it will be the last OS. They've seen the light, they know better than the users, and they know what's coming. It's all well and good to develop alternative free operating systems, and I would encourage anyone who wants to to do it, but the fact is that if you create something really neat, it will make it into GNU/Linux sooner or later.


  71. Unix methodology vs Linux methodology by Half-pint+HAL · · Score: 1

    the Unix methidologies are very comfortable to developers because (a) they are relatively regular in setup. (b) They tend to be highly modular, making things easier to work with and build - lots of re-use of things you made or thigns others made.

    Sometimes it seems to me that the Unix and Linux methodologies have forked somewhat. Modularity in old-school Unix took an almost completely bottom-approach with small self-contained basic apps that could be tied together at the user interface level or from within scripts or even programs themselves. Linux devs seem to focus on modularity at a source code level, to the exclusion of user interface level. Sure, you can still use switches, pipes and redirection on most modern programs, but generally only to do the most high-level tasks, not the low level primitives. Some people are trying to correct this, but (eg) the Gimp came years before the Gimp Command-Line Tools -- and that's not Unix methodology, it's practically top-down.

    Real modularity, based on Unix pipes, could completely decouple the GUI from the code. This would be a Very Good Thing.

    Right now, the biggest obstacle to any sort of Unix/Linux on the desktop is the inconsistency in GUIs. Scream KDE or Gnome if you want, but these don't enforce any consistency on apps. In fact, by being compatible with non-KDE/Gnome apps, they invite inconsistency in. Yes! - it means there's a lot of apps available, but! - it scares non-geeks.

    If we had our UIs decoupled from our apps, it would take very little time to gather all sorts of old code and put together a consistent GUI from X widget libraries.

    Everything would look the same, people wouldn't be scared. And the code may just be more maintainable.

    HAL.

    --
    Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    1. Re:Unix methodology vs Linux methodology by marcosdumay · · Score: 1

      The UI is not some simple glue anymore. We have very complex UIs nowadays that couldn't port that easily from DE to DE.

    2. Re:Unix methodology vs Linux methodology by arevos · · Score: 1

      Real modularity, based on Unix pipes, could completely decouple the GUI from the code. This would be a Very Good Thing.

      Based on Unix pipes? Seriously?

      Right now, the biggest obstacle to any sort of Unix/Linux on the desktop is the inconsistency in GUIs.... If we had our UIs decoupled from our apps, it would take very little time to gather all sorts of old code and put together a consistent GUI from X widget libraries.

      Decoupling the UI and application layer would not automatically result in compatibility between UIs. You'd first have to get everyone to agree on a common interface (which in itself is a whole can of worms, and made even more difficult due to different layout engines, different widgets etc.). But a common interface can be achieved whether you're using pipes or binary libraries, the only difference between the two being that pipes would be considerably less efficient, with little appreciable advantages.

  72. You're asking the wrong question by dannys42 · · Score: 1

    If you're concerned about the adoption of alternative Desktop's, whether it's Linux-based (or more accurately has a large Linux population) is irrelavent. In fact, it seems relatively simple for GNOME apps to run on Windows. I imagine someone's got (or is working on) porting the entire GNOME environment for Windows as well.

    The question really is why do OSS Desktops currently suck? Why does GNOME insist on taking away features or cloning the bad features of Windows that Windows doesn't even use anymore. I haven't used KDE in a while, but I felt KDE lacked a bit of coherency in the apps.

    In addition, why are all the desktop OS's playing catchup, and still using outdated models of "icons" as bitmap images? Why couldn't an "icon" be composed of 3D rendered animation with sound effects, and an understanding of user/desktop/system events? eg. an icon that "schwings" whenever the app is loaded (whether it was loaded via the icon or some other way). That's just an example of course. But the closest desktop I know of to do anything like that is OS X.

    1. Re:You're asking the wrong question by doom · · Score: 1
      Why couldn't an "icon" be composed of 3D rendered animation with sound effects,

      Because they realize that I might shoot them.

      (Have you ever heard of television? Why don't you go away and watch it for awhile...)

  73. Talk about your flamebait... by kjkeefe · · Score: 1

    The only problem with Linux in the home is that it doesn't run the programs that users are already used to running. It seems like most geeks forget that the average joe user does NOT use a computer for its OS, they use it for the word processor/game/media player/porn organizer that they already know and love. Want linux to be a raging success in the home? Make it run windows apps. Same thing with OSX...

    Personally, I run Linux everywhere. And, every time I see a windows app that I want to buy, I make it a point to email the company and say, "Boy, I sure was ready to buy your software until I realized it wouldn't run on Linux. When is the Linux version due out?"

    PS, This is part of why virtualization is going to be so important in the future (even though it isn't a final solution).

    --
    1, 2, 3, 4, 5... That's the combination on my luggage!
  74. Gnome and KDE are very linux centric. by Generic+Player · · Score: 1

    KDE and Gnome require a great deal of effort to be ported to other OSs besides linux. They are written for linux, and then people who use other OSs have to port it themselves if they want it to run anywhere else. On a reasonably current openbsd system:

    $ find /usr/ports/x11/kde/ -name patch-* | wc -l
              115
    $ find /usr/ports/x11/gnome -name patch-* | wc -l
                92

    Do you really think software that requires ~100 files to be patched if you aren't running on linux isn't linux centric?

    1. Re:Gnome and KDE are very linux centric. by WhiteWolf666 · · Score: 1

      I'm not sure that is relevant.

      Both Gnome and KDE are huge. AFAIK, OpenSuSE uses quite a few MORE patches for both KDE and Gnome than ~100.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    2. Re:Gnome and KDE are very linux centric. by toganet · · Score: 1

      I wonder what the outcome would be for the same command on a Linux box? Just because it is patched for OpenBSD does not mean it isn't also patched for Linux.

    3. Re:Gnome and KDE are very linux centric. by Generic+Player · · Score: 1

      Being large projects has nothing to do with it. Suse's patches are for making it fit their desktop setup. OpenBSD doesn't have anything like that, its just gnome or KDE as is. These patches are just to function correctly, not to add icons and setup default apps and such. If you need alot of patches to work on non-linux systems, then you have linux software. Pretty straight forward. Please stop trying to spread misinformation, we've got plenty enough unportable software without you trying to convince everyone that it is in fact portable and they can keep writing linuxware and it will work everywhere.

    4. Re:Gnome and KDE are very linux centric. by Anonymous Coward · · Score: 0

      gnome is not even linux centric. It breaks many things for no good reason (like discardings HOME environment variable for some other obscure data)

    5. Re:Gnome and KDE are very linux centric. by Brandybuck · · Score: 1

      KDE and Gnome require a great deal of effort to be ported to other OSs besides linux.

      Nonsense! Get out from behind that rock and see the real world!

      Building KDE under FreeBSD is as simple as "configure; make; make install". Really it is. I've done it countless times. Go look at the KDE ports and see how very very little they patch KDE. Yes, there are a few KDE apps that have "linuxisms" (kfloppy), but they are the rare exception.

      I'm not a GNOME user, and every time I've built it has been a painful experience. But that's not because it's meant for Linux, it's because it has a nasty twisted dependency tree. There's a large script to build GNOME under FreeBSD, but that's no different from the large scripts used to build it for Linux distros.

      Go look at those patches you talk about. They are either standard bug/exploit fixes, changes to hardcoded file paths and names, or they're changes to default values. All of these are changes that most Linux distros are going to make as well. Patches that deal with genuine linuxisms are few and far between.

      --
      Don't blame me, I didn't vote for either of them!
    6. Re:Gnome and KDE are very linux centric. by Generic+Player · · Score: 1

      "Nonsense! Get out from behind that rock and see the real world!"

      I'm sure the people who spend hours making it so you can run KDE on freebsd really appreciate your gratitude. I am not trying to trash KDE, I don't even use it. I am just saying that yes, it is in fact developed by linux users, for linux users, on linux machines. Then BSD people fix it. KDE people are nice enough to take the patches, but they still developed linux software, and BSD people fixed it. This nonsense claim that people are developing cross platform code that works out of the box everywhere is crazy.

      "Go look at those patches you talk about. They are either standard bug/exploit fixes, changes to hardcoded file paths and names, or they're changes to default values."

      I did look, plenty of them are fixing linuxisms. Even little things like ifdefs being in the wrong places so that the code doesn't compile if LINUX_ONLY_FEATURE_X is not defined.

    7. Re:Gnome and KDE are very linux centric. by Brandybuck · · Score: 1

      I'm sure the people who spend hours making it so you can run KDE on freebsd really appreciate your gratitude.

      I happen to be one of those people! There are problems getting KDE into ports, but they have little to do with linuxisms, and an awful lot to do with the fact that it's a big ass piece of software.

      I'm not saying there aren't any linuxims in KDE, because there are. But a lot of stuff is simply because FreeBSD stuff needs to be done on FreeBSD. You can't expect someone developing on Solaris to write the FreeBSD backend for HAL, for example.

      One of the current problems, for antoher example, is making the Qt4 port. I've been building Qt4 on my FreeBSD system with "configure; make; make install" every week for the past year. Porting it to FreeBSD is NOT the problem. Making it live gracefully with Qt3 is. That's why there isn't a Qt4 port yet.

      --
      Don't blame me, I didn't vote for either of them!
    8. Re:Gnome and KDE are very linux centric. by Generic+Player · · Score: 1

      "I'm not saying there aren't any linuxims in KDE, because there are."

      Right, that's the point. It is written for linux, and then users of other systems have to fix it for their systems. So its not a case of linux distros using KDE and Gnome as kotj.mf thinks. Quite the opposite, it is a case of Gnome and KDE developers using linux.

    9. Re:Gnome and KDE are very linux centric. by Brandybuck · · Score: 1

      You said, "KDE and Gnome require a great deal of effort to be ported to other OSs besides linux."

      Your implication is you do NOT need a great deal of effort to port it to a particular Linux distro. Yet the effort Debian or Slackware spend packaging KDE is just as great as the effort spent by FreeBSD.

      --
      Don't blame me, I didn't vote for either of them!
    10. Re:Gnome and KDE are very linux centric. by Generic+Player · · Score: 1

      "Your implication is you do NOT need a great deal of effort to port it to a particular Linux distro. Yet the effort Debian or Slackware spend packaging KDE is just as great as the effort spent by FreeBSD."

      Because you don't. They choose to patch it to make it behave the way they want for their distro. That's fine, but its not required. It does require patches for it to function correctly on BSDs. Yes, KDE is very good at releasing test candidates and taking patches from the BSD people so that by the time the release comes out it works out of the box, I am not saying KDE sucks or KDE developers suck. I am just saying KDE developers do in fact target linux, and other people fix it for other OSs.

  75. A mistaken belief... by Anonymous Coward · · Score: 0

    that Linux would make a good desktop. Other than the MS moral issues, the greatest reason that Linux is making in roads on MS is that it's a fine _server_. With the integral GUI, MS has more overhead than Linux. (I understand that may be changing though.) With that overhead, Linux is faster and with less code in play at one time, more reliable.

    On the other side of the issue, Linux will not be a good desktop (my opinion). It's more complex than a desktop needs to be. You don't need to serve out Apache on a desktop. You do need a good GUI.

    I haven't seen a alternative OS that truly stands out yet. Of course, in order for one to do so, developers have to give up the mistaken belief that Linux would make a good desktop and the client OS would have to tie into Linux (and most likely MS) well. Until that happens, you aren't going to see a desktop that is really popular other than Windows (again... my opinion).

  76. Can anybody share why they do or do not prefer.. by weierstrass · · Score: 1

    Ever heard of a concept called 'free as in freedom'?

    --
    my password really is 'stinkypants'
  77. I have a better question... by the+saltydog · · Score: 1

    Why doesn't Dan "Lyin'" Lyons just ask the question on his OWN damned anti-Linux bash-fest troll blog, instead of wasting his time posting here?

    (Not that it really IS a statement from old Danny boy, but it sounds exactly like him, complete with false analogies and strawmen galore... I guess for guys like him, and Rob "Rent-a-rant" Enderle, when you've been suckling at the withered teat of Microsoft for most of your life, it's difficult to learn any other way to survive.)

  78. windows shells by XO · · Score: 1

    ...on the other hand, I think some aspiring coders out there should build a nice desktop for Windows that isn't as bad as the existing one.

    I installed Linux a few days ago, hoping to see some improvement in the general desktop stuff since I last used it about two years ago.. unfortunatly, the whole time I was in X, it felt like I was stuck in 1990, with Gnome. I didn't make it to KDE because Debian pissed me off too much.

    Then I went and installed Windows, and was equally pissed off that it's installation process felt like I was stuck in 1991.

    --
    "Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
  79. It's unpleasant to get too "weird" by Sloppy · · Score: 1

    As an ex-Amigan, the main reason I switched to Linux was that I wanted a platform that was getting maintenance. But the second reason was that I was tired of .. well .. "being a weirdo" -- being so far from the mainstream that I was always alone. Linux, because of its Unix ties, is orthodox, mainstream, whatever you want to call it. It's mainstream enough that there's a whole lot of popular interest in it, and it's getting lots of development. It's off the beaten path enough, that the development isn't stupid and destructive (e.g. Microsoft's "Genuine Advantage" or Apple's efforts to keep their new OS from running on whiteboxes) and instead oriented toward giving people what they want. It's not a product, it's technology (even if a bit bland and outdated).

    Those other (arguably higher-tech) OSes are so small and isolated, that development happens very, very slowly. They have the potential to have non-stupid development (and maybe they really do) but the smallness of the teams and isolation put them at risk of becoming cults. Despite fanaticism that is sometimes seen (and exaggerated) among Linux users, one thing that has struck me about most Linux developers (and really, Linus himself even if I think he's wrong about some things) is sanity. There's no cultiness to it. Linux has a long-term stability that I really feel like I can count on. I don't feel that confidence with the fringe projects (whether deserved or not).

    As for monoculture, I have two takes on it. Linux is a monoculture in terms of ideas, and creativity is somewhat retarded. A lot of things never really get thought about. But in terms of security, there's enough variety in distributions, configuration options, etc, that I think there is considerable resistance to the kinds of risks that systems like MS Windows face. If I were at a large company and every computer were running the same version and installation of Fedora, I might feel a little uneasy. The culture as a whole, though, isn't like that.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  80. It's the community, stupid by LunchSpecial · · Score: 1

    The reason that we don't see wider Linux adoption is because calling the it all "Linux" is a faulty assumption.

    There isn't one Linux operating system, there are many. And they are all different.
    Different leaders, different philosophies, different bug tracking systems...
    If the distros weren't the only problem you have multiple window managers, multiple desktop managers, multiple ways of doing package management, etc etc...

    It's called the Paradox of Choice, and it's been covered on this site many times...
    http://science.slashdot.org/article.pl?sid=04/03/2 9/1214225

    Until there is a clear winner, we won't see a good jump in Linux market share.

    Until the "Linux Community" actually starts working in the same direction this is simply going to stay a collection of stuff that doesn't always work together.

    The original poster is right in a way, we have failed. Until there is a significant amount of people working towards a stable "Linux Desktop", a product we can all get behind, we can't mount an organized campaign.

    But this is contrary to the whole "Linux Community" philosophy which basically says "If I don't like it your way, or I don't understand it your way I'm going to rewrite/engineer/fork the code. Then I'm going to make a distro and support my users... Sure it may confuse the users, but my machine is going to work. We're going to get into bitter flame wars, we're going to have all this redundant code. We're going to keep fighting each other while the big boys get the market."

  81. Re:False Problems by amorsen · · Score: 1

    Today's lesson: It takes a compelling application, not one that already exists in the Windows world to make people switch. The variety of apps is the fertilizer out of which a killer app will come that will make people switch.

    Why won't this app be ported to Windows a month later? Killer apps don't exist anymore.

    --
    Finally! A year of moderation! Ready for 2019?
  82. "Neglecting to consider" by wootest · · Score: 1

    "Why are free-desktop developers neglecting to consider an alternative to the penguin?"

    Why does "they all run Linux" imply neglect, that "none of them ever considered the alternatives"? It seems to me that considering the alternatives is just the thing that brought the majority of the Linux users (and the Mac OS X users and the Solaris users and the *BSD users too, for that matter) to the platform where they are today.

    Ironically, since this is a Linux-centric column, I think Steve Jobs summed this kind of thinking up best: "Some of our competitors say we're not offering people choice. We're offering them choice, they just don't like the choice our customers are making."

  83. PC-BSD by easyEmu · · Score: 1

    Is only the greatest OS ever made!!! Easier to install and add applications than Windows or Linux; there are tons of free software packages that have there own GUI installer for download on their site. If I want something not there, then I simply have to compile from source like in Linux. More people should get behind PC-BSD, and I think they are. What doomed BSD early on is that it was extremely hard to install. PC-BSD remedies this, I installed it on my computer in about four mouse clicks, everything on my system auto-detected and worked without any input from me.

    1. Re:PC-BSD by synthespian · · Score: 1

      The thing is that you can't compete with a Linux distro that has millionaire that you ship you 100 Ubuntu CDs for free.
      PC-BSD is probably the most user-friendly open source Unix out there.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  84. It's not about the OS, it's about computer sales by Anonymous Coward · · Score: 0

    The reason that Linux cannot match firefox is that most people buy a computer with an OS installed on it. True they also have Internet Explorer, but it is relatively trivial for them (or a relative) to install Firefox without changing anything else in the way they use their computer (and it doesn't take much time). Changing the OS takes a major commitment. If they were offered different OSes at the salepoint (with corresponding cost), things would be different. My aunt got her new computer with Linux pre-installed (by me), and she's just as happy as when she had Windows on her old computer. I'm happier because calls to fix her computer have gone from one every couple of weeks to... I haven't had one in the 2 years she's been on Linux. She's happier because it just works. People who only need a computer to play around on the web, send-receive e-mails, view their pictures from cameras, and burn said pictures or music on CDs don't need anything more. Grad students who have to produce all kinds of graphs and data analysis probably can't ask for anything better. But it rarely comes pre-installed. You have to go out of your way to get it. Most people don't like to go out of their way. Firefox is not quite the same. One click and bang. Not much out of the way. And even then most people won't use it because it's too much. It's at the consumer goods providers level that Linux, BSDs, ReactOS etc, etc, can reach people. Or at the school level by showing learning minds what's out there.

  85. Anyone tried GNU/Hurd? by gbalaji · · Score: 0

    Couldn't agree more with the article. GNU/Linux users should also try GNU/Hurd just for the heck of it. That would atleast help us understand 'Linux' alone is not FOSS.

    For me the most important aspect of using free and open source software is the amount of CS knowledge we get without even realizing it! More options at the kernel, desktop and distro levels mean that you invariably learn more trying to choose from them! Imagine the millions of Computer Science graduates coming from countries like India who have never used a non-Windows OS let alone installing or contributing to FOSS. Several theory courses in OS may not equal one GNU/Linux installation!

    Ofcourse non-technical people should not have to worry about these things. Hence popular GNU/Linux distros like Ubuntu/Fedora/SUSE which even non-techies can install are welcome.

    Balaji.

  86. poppycock... by advocate_one · · Score: 1
    However, the Linux of today seems to be as far away as ever from realizing the expectations of mass adoption we once had for it, without significant growth in home usage since the late 90s.

    I know Linux is taking off. Tesco has finally admitted a Linux magazine into their limited range of computer magazines in my city... this means that the sales of the magazines are good enough to warrant the shelf space... which means there are sufficient Linux users out there to generate demand...

    of course they are basically uncountable because the vast majority of them will have bought their machine with windows on it in the first place. This means that they were all counted as windows sales...

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  87. It's *nix by PenGun · · Score: 1

    It's a useful unix. The most developed one these days and a beautiful OS. It is an absolute joy for someone who "likes" computers.

      It is a twisty maze for users and people who just want it to "just work". Tough.

      It's a killer HTPC, my present jones, and I can't even imagine what I would have to go through to get my present functionality in windose or osex.

  88. hardware support by falconwolf · · Score: 1

    The reason you find the Linux kernel in most free desktop systems should be pretty obvious - it's currently better at handling the random hardware that desktop users throw at it than anything else out there.

    That's sort of a catch22 isn' it? I mean more people use Linux because it works with more hardware, yet it works with more hardware because more people develop drivers and otherwise work to get hardware working on Linux. To get more people to use these other OSes more people need to develop for them yet many won't until they see them being used more.

    Falcon
    1. Re:hardware support by muuh-gnu · · Score: 1

      So the few using the other OSes neet to develop something a system so outstanding and superior to the other, to impress all those driver hackers to port their drivers over. Obviously the BSDs do not impress the relevant device driver writers more than Linux, and Linux does not impress some other driver writers more than Windows. They seem both to be not impressive enough in the eyes of the people who have control over the actual hardware they want to run on. A simple "Build it too, and they will come" wont cut it, it has to be a "Build it so much better that they dont have an excuse any more, not to come."

  89. Because of Linux (teh kernel) by miffo.swe · · Score: 1

    I think drivers is what pulls developers towards linux. That and the abundance of developing tools. Also, how fun is it to make your own os nowadays and then populate it with Firefox, OpenOffice, Gimp and whatnot and realize that your new shiny OS is looking more and more lika a heavily altered linux distribution? It would be fun to see more projects with new ideas and conventions for the desktop and the file system. By starting off with Linux such projects can concentrate on the fun part right away, That said, there are room for more OS as long as they follow standards in protocols and file formats.

    --
    HTTP/1.1 400
  90. Flawed Assumption by seeks2know · · Score: 1
    "Why are free-desktop developers neglecting to consider an alternative to the penguin?"

    The basic premise of the author is flawed. This is akin to asking, "When did you stop beating your wife?" The author presumes that free desktop authors develop for Linux only; and that assumption is flat out wrong.

    Consider these points:

    1. Firefox is developed to run on MS-Windows, Mac OS-X and Linux.
    2. OpenOffice.org offers downloads for MS-Windows, Mac OS-X, Linux, Solaris, and FreeBSD
    3. KDE 4.0 will provide porting libraries to support MS-Windows and Mac OS-X

    Heck, I can execute many free desktop applications on my Windows PC via Cygwin.

    And the reason that Linux has failed (and will continue to fail) to obtain widespread adoption has much more to do with Microsoft's monopoly and their continued antitrust activities than Linux desktop functionality.

    Label this article as flame bait. Let's move on...

  91. It's the applications, silly! by spaceyhackerlady · · Score: 1

    I've played with a number of research/hobby OSs, and, for the most part, they work as advertised. They often have interesting ideas. Sometimes it's just plain fun to mess around.

    The catch always seems to be applications. If the OS doesn't actually do anything, there is little point in using it. And while many apps can be ported, if you're not using, for example, the native GUI and API of Syllable, what's the point of running Syllable at all?

    I suspect this is a critical-mass-meets-chicken-and-the-egg problem. Nobody will write apps if people aren't using the system. Nobody will use the system if there aren't apps.

    ...laura

  92. KDE or Gnome on Windows? by knisa · · Score: 1

    There's probably a very good, technical reason for this, but I'm going to ask anyway. Why can't KDE and/or Gnome be ported over to Windows? You could then have your free desktop on your already paid for (or pirated) windows installation. You could still run your Windows apps until free alternatives are developed or learned, and then switch to Linux (if you want) when it isn't as painful.

    I have a handful of things keeping me from running Linux full time on the desktop, but I wouldn't mind being able to use Gnome instead of Explorer (natively, not via cygwin or whatever).

    --
    This space for rent.
  93. what about other OSes? by falconwolf · · Score: 1

    What about Solaris? What about OS X? Can anybody share why they do or do not prefer one of these over GNU/Linux?

    I can only talk about myself when saying what OS I prefer, others may agree or disagree. As for Solaris, I've never used it and I don't have any prctical knowledge about it. On using MacOS, not just OSX but the MacOS family, I've first used it sometime around 1985 or so and for about 10 years I used it more than anyother OS though I did use AmigaOS, DOS, and Windows some. But the past 10 years I've used Windows almost exclusively. I have used Linux some but that was some year ago, however as I recently got a new PC with Linux preinstalled I'll be using it more. Also because I'd like a laptop, and I don't to have to deal with any Activation, WGA, or any other BS MS wants users to do to use Windows I plan on getting a Macbook for a laptop. Though I haven't decided to yet, I may setup the Macbook as a dualboot between OSX and Linux.

    As for what OSes I prefer, of those I used I liked Amiga the best, then either Macs or Linux.

    Falcon
  94. Wow, talk about full of shit. by Generic+Player · · Score: 1

    First of all, strlcpy/cat are very well thought out. If you have a problem with them, say what it is. Second, they are not in glibc because Ulrich Drepper is a moron with a severe case of NIH syndrome. Third, it IS in the linux kernel, Linus accepted it just fine. He had to put it in the kernel so he could use it because Ulrich Drepper is too dense to let it into glibc. And fourth, nobody writes software that relies on strlcpy without also including a configure check and strlcpy, making it portable. Duh?

    Clearly you haven't done the porting you claim you have, or you would realize valgrind is linux only, and thus does not help you porting to other systems. Valgrind isn't going to do jack for you on z/os.

    1. Re:Wow, talk about full of shit. by ctzan · · Score: 1

      Third, it IS in the linux kernel, Linus accepted it just fine. He had to put it in the kernel so he could use it because Ulrich Drepper is too dense to let it into glibc.


      I don't get this. Is linux (the kernel) linking against glibc ?
      Even if strl{cat,cpy} were in glibc, this would not make any
      difference for kernel programming.

      Of course, having the strl* functions available as builtins
      in gcc (like most other string functions) would be more
      interesting, but I don't thing Ulrich Drepper has any say in
      this.
  95. BS by Godji · · Score: 1

    Clearly, if Linux is unable to reproduce a third of Firefox's end user uptake over a much longer time-frame, there are deficiencies with the direction the GNU/Linux/X/Gnome/KDE system has taken.

    Nonsense. Firefox is a drop-in replacement for IE: 1. Remove IE (yeah right :P), 2. Install Firefox, 3. Work as before. Linux is a completely different world. "So it doesn't have C: and D:... can it use my hard disk then?"... The direction taken by GNU/Linux/X/Gnome/KDE is wonderful.

    Besides, Linux is not a monoculture. The kernel, sure. But the entire system has distributions. My Gentoo is a lot different than the millions of Ubuntu desktops there are.

    It seems to me that someone needs to read this: http://linux.oneandoneis2.org/LNW.htm

  96. proprietorial? by Anonymous Coward · · Score: 0

    I don't mean to be an ass, but I've never heard of a 'proprietorial' OS. Proprietary OS? Yes. Proprietorial rights? Yes. 'Proprietorial OS'? No. Shouldn't editors, I dunno, edit things?

  97. Once more with feeling by bitspotter · · Score: 1

    Once again, the point of free and open source software is NOT USER BASE.

    It's freedom.

    That's why call it "Free Software" and not "Popular Software".

    If user's don't pick up GNU or Linux, it is not because something is "wrong" with it. It just means that, well, freedom isn't popular. Too bad. Is this so hard to believe? Have you looked at what the White House has been doing lately?

    Most people who come to and develop GNU/Linux do so because they want the freedom, not the popularity. There's a lot of work being done to make freedom function fully for non-geeks as well as the experienced. That's the direction.

    So if you want take steps to change "the" direction of GNU/Linux to make it more popular, knock yourself out. You are free to do that. Unlike other platforms, we let you. Just don't expect to monopolize the whole "direction", or tell us our preferred priorities are "wrong" because they don't match an old-school commercial worldview that puts market domination on top of the stack, over user freedom.

  98. Grandmas don't want that one extra package! by blue.earthling · · Score: 1

    GNU/Linux is open source and is under GPL. From a Hacker/Developer perspective it can't get better than that. What would be the purpose of forking for the sake of forking?

    One reason, why there are multiple forks even inside the GNU world, could be the fact that promoting decentralization is an imperative principle of hackers.

    Main Linux distributions come with couple of THOUSAND packages. Do your grandmas really need that one extra package?

  99. Missing Drivers and Applications by dusty123 · · Score: 2, Insightful

    The reason for the lack of Linux on desktop systems is not a bad desktop environment. KDE does well, Gnome too.

    To my mind the problem is threefold:

    1) Installing desktop hardware (especially notebooks) can still be a nightmare, even for advanced Linux users: Webcams, modesm, scanners, soundcards, new motherboard chipsets, bluetooth, graphic cards, input devices (keyboard/mouse/joystick) - they all come in various fashions and nearly none of them have native Linux driver support. This is different with server hardware, where drivers most often exist for Linux - moreover people who install servers are seldom Linux newbies.

    2) Missing applications: No MS-Office, no CorelDraw, no Adobe Writer, no xyz, no... - the list is sooo long. And people often _have_ to use these applications.

    3) Various content can not / not easily be viewed from Linux. This can be blamed on missing applications as denoted above but also on DRM, such as encrypted DVD's and the like. And for sure, new multimedia content will emerge that can not be viewed on Linux due to DRM restrictions.

    The above three points apply to all other operating systems, such as ReactOS, BSD - regardless if these operating systems have "better" concepts or not. If there are no drivers, no applications and no content, no one will use it and it's pretty useless to port KDE/Gnome...

  100. the USA Constitution Commerce clause by falconwolf · · Score: 1

    Well yeah, which is why I'm glad they put in the Bill of Rights after all. Otherwise we'd see Congress claiming that the Commerce Clause grants them the power to regulate the speech in books sold across state lines.

    Substitute medical marijuana for everything after "the speech" and you have exactly what the USSC Justices are allowing the federal government to do. In a California case on medical marijuana that went up to the USSC the Justices ruled that the federal government could prevent California from using marijuana medically. They said if the states wanted to allow it to be used legally then federal laws had to be changed.

    Falcon
    1. Re:the USA Constitution Commerce clause by Chris+Burke · · Score: 1

      That's my point. Congress basically treats the Commerce Clause like it gives them the power to do anything they want, so it's a damn good thing that at least some of the things Congress can't abuse it for are explicitly spelled out in the Bill of Rights.

      How they decided the Clause to allow them to restrict solely in-state activity like CA's medical mj, and more importantly got SCOTUS to go along, I'll never figure out though. I'll just chalk it up to the usual cynical causes.

      --

      The enemies of Democracy are
    2. Re:the USA Constitution Commerce clause by falconwolf · · Score: 1

      How they decided the Clause to allow them to restrict solely in-state activity like CA's medical mj, and more importantly got SCOTUS to go along, I'll never figure out though. I'll just chalk it up to the usual cynical causes.

      I don't know how the Justices figured out how CA's medical marijuana had anything to do with interstate commerce either myself, but a majority of them did. If I recall right 3 of the 9 members said the Commerce clause had nothing to do with medical marijuana, unfortunately the other 6 didn't agree. Instead they waved their arms up in the air and a link materialized in their brains, maybe they also said "abracadabra"?

      Falcon
    3. Re:the USA Constitution Commerce clause by An+Onerous+Coward · · Score: 1

      Remember, kids: it's only judicial activism when the rulings support left-wing positions.

      --

      You want the truthiness? You can't handle the truthiness!

  101. A New Low by Anonymous Coward · · Score: 0

    I've seen dumb stories posted to Slashdot before, but this one takes the booby prize for utter, heathen ignorance. Linux is simply the most famous and widespread of the FOSS distros. Rest assured, anybody who uses Linux is well aware of BSD, Open Solaris, and Minix, and more likely than not follows the progress of ReactOS, GNU/HURD, and other pocket niches such as Plan 9 from Bell Labs.

    The only people married here is Microsoft married to the idea that they can defeat their main competitor on the PC by hiring asstroturfers to post FUD on how 'Linux is failing'. Yes, Boo-Hoo, I'm so discouraged, I guess I'll go turn myself in to Redmond for my mandatory borging now.

    Fucking idiot.

  102. Re:Can anybody share why they do or do not prefer. by laffer1 · · Score: 1

    The difference between GPL and BSD licenses:
    1. GPL = code freedom
    2. BSD = coders freedom

    I care about people more than source code. Everyone is entitled to their opinion.

    As for the article, it makes a good point. I've had constant problems getting GNU types to accept patches for my BSD. I get lovely replies like "BSD is dead", "why not use linux?", "I only care about linux.", etc. This is a real problem. I know considering I'm working on BSD desktop environment. Linux adopters had to fight hard for drivers, applications and other things that many new linux users take for granted. Now the BSD community is fighting that fight and losing because people point at Linux. I'd argue that part of the problem is the corporate involvement in linux, but there are advantages to it as well. Plus FreeBSD seems to be getting handouts from companies as well. I'm not so lucky.

  103. philanthropy AND ego by l4m3z0r · · Score: 1

    except the developer whose motivation is philanthropy AND ego, this guy is interested in licensing his code so that in can only be used on his terms.

    s/the developer/stallman/

  104. Such language people have :) by EsbenMoseHansen · · Score: 1

    Hey, I don't really have a problem with it, and I resent your language. Learn to talk nice, even if disagree, please. My personal opinion, if you care, is that they are poorly designed functions, but so are just about all the str* function (at least, for inclusion in the stdlib), and 2 more won't really hurt. As I said, it is the glibc team (and yes, Ulrich among them) and Linus that spearheaded rejection of that patch. (I found this out via searching the group with google; I'm sure you can do the same since you seem to care so much)

    As I recall, the reasons (not my reasons, though I find them reasonably sounds) were:

    • they are unneccessary (as you should always keep track of how long your string is and realloc as neccesary strcpy or memcpy will do as well. Randomly truncating of stings are not really any better than overflowing. (I disagree about this).
    • They invite the use of fixed buffers of strings, which are unfortunate design in any case where the string length cannot be known beforehand, such as a file name and input
    • They bloat glibc, if even just by a tiny amount, making every program in linux (near enough) just that much slowly launch. (and yes, glibc is already way too bloated, everyone agrees in this. That does not adding more stuff any better).
    • As you yourself say, writing the function out and including them around a configure check is pretty much mandatory anyway.

    Personally, if I ever wanted to do any development in C that involved more than a few string would be to pick up a better library, that handled the reallocs automatically. If none exists (which I sincerely doubt), I would write it. I prefer C++ for my own writings, or ruby or perl or something, depending on the job at hand.

    As for Ulrich Drepper, from my few (electronic) impressions, seems a nice if passionate guy. I'm sure he does the best he can, and I for one appreciate all the efforts he does. He is quite stubborn, which I think is pretty much mandatory in the job he has.

    Yes, valgrind helped in Z/Os, not that you can run it there, as I well know, but the bugs that appears in one system tends to be hidden on other systems as well... but for various, the bugs aren't triggered. The most common is branching on uninitialized data, which tend to be completely predicable for a given system. I squashed a great many bugs that way, which helped in the porting. Gdb doesn't run on Z/Os either, at least not in the installation I had. And yes, I've worked on Z/Os, the OS that tended to handle everything a little different. E.g, if you fork()'ed, you had to be sure only to close any sockets in one of the branches, as the FIN... sequence was sent on the first close. Great, eh? Or how about fork() not forking every file handle, automatically closing those it did not want to fork. No, the standards does not, as far as I could determine, prevent an OS from doing this. Add to that the pletora of compiler bugs in IBM's C++ compiler.... I was glad to get out of that.

    My point was, most application are easy enough to port, inserting the configure or cmake or whatever checks as neccessary. At least, that is my experience. Of course, if the libraries it uses doesn't work... it can become a big issue. Luckily, I have escaped from that part during my porting works. Porting to windows is a bit harder, but if the GUI toolkit is available on windows (most are), it is not *that* hard, depending on the application of course.

    --
    Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    1. Re:Such language people have :) by Generic+Player · · Score: 1

      "Hey, I don't really have a problem with it, and I resent your language. Learn to talk nice, even if disagree, please"

      Learn not to make nonsense claims with nothing to back them up.

      "As I said, it is the glibc team (and yes, Ulrich among them) and Linus that spearheaded rejection of that patch. (I found this out via searching the group with google; I'm sure you can do the same since you seem to care so much)"

      No, it was just Ulrich, and I know this because I found so much humour in this particular post: http://sources.redhat.com/ml/libc-alpha/2000-08/ms g00061.html so I have no need to google it.

      As I said, Linus does use it, its in the linux kernel because Drepper was too big of a douche to accept it in glibc, grep for yourself.

      "they are unneccessary (as you should always keep track of how long your string is and realloc as neccesary strcpy or memcpy will do as well. Randomly truncating of stings are not really any better than overflowing. (I disagree about this)."

      Obviously this is silly, of course you keep track of how long it is, that's why you pass it a length argument. strcpy and memcpy will not due, as they will gladly overflow that fixed length buffer. strncpy will not due because it fails to NULL terminate strings all the time and is slow. And strlcpy doesn't randomly truncate strings, it truncates strings that are too long, and then tells you it truncated them in case that matters (which it sometimes does).

      "They invite the use of fixed buffers of strings, which are unfortunate design in any case where the string length cannot be known beforehand, such as a file name and input"

      Yes, lets just keep strlening everything new we get and reallocing our buffer to fit that new size. All machines have infinite RAM, and realloc takes no time, so why bother keeping strings to a reasonable length.

      "They bloat glibc, if even just by a tiny amount, making every program in linux (near enough) just that much slowly launch. (and yes, glibc is already way too bloated, everyone agrees in this. That does not adding more stuff any better). "

      This is the funny one, as if a 25 line function is going to bloat glibc up, when its got thousands and thousands of lines of bloat already. It won't make anything launch any slower at all, what a pathetic excuse.

      "As you yourself say, writing the function out and including them around a configure check is pretty much mandatory anyway."

      Pretty much mandatory because Ulrich Drepper is a tard and thinks:
      *((char *) mempcpy (dst, src, n)) = '\0';
      is nicer than:
      strlcpy(dst, src, n);
      If it were in glibc, then standardization attempts would succeed because of it being in all the most used unixes (BSDs, OSX, solaris and linux) and then it would end up everywhere and wouldn't need configure checks.

      "Yes, valgrind helped in Z/Os, not that you can run it there, as I well know, but the bugs that appears in one system tends to be hidden on other systems as well... but for various, the bugs aren't triggered."

      Existing bugs are not part of a linuxism though. Valgrind helps be a very slow version of just developing on openbsd to start with, yes. But those bugs are there on linux too, they just don't trigger reliably. I wasn't saying software is buggy (which is obviously the case) I was saying that its written for linux.

    2. Re:Such language people have :) by EsbenMoseHansen · · Score: 1

      I have made no nonsense claims, and even if I had, you have no reason to be rude.

      For Linus's stand on the issue, please read a post he made on this issue. In fact, skip the rest of this post and just read that thread, Linus is a much better teacher than I ever will be.

      Still reading? ok, you don't need to tell me basics about C or it's standard library.. I know the language quite well. And I happen to agree that including strlcpy and friends with glibc is no great harm, as long as a fat warning is included in it's manpage (as well as all the other str* and even mem* should have) about it's shortcomings. However, you blithely ignore the fact that truncating strings based on length likely covers a bug more effectively than the security problem the buffer overflow is. Yes, you might avoid the easy security problem (buffer overflow) but you might introduce a worse one. Consider the example. I can follow Ulrich

      #ifdef BSD_HACK
      // Woops! Something like
      // DELETE FROM TABLE_THAT_USER_IS_NOT_ALLOWED_TO_ACCESS_USER_VIEW
      // might become
      // DELETE FROM TABLE_THAT_USER_IS_NOT_ALLOWED_TO_ACCESS
      char input[51];
      strlcpy(input, getValidatedSqlFromUser(), sizeof input);
      #else
      #ifdef ULRICH
      // Safe, if cumbersome.
      const char* sqlFromUser = getValidatedSqlFromUser();
      char* input = (char*) MALLOC(strlen(sqlFromUser)+1);
      if (!input) { abort();}
      strcpy(input, getValidatedSqlFromUser(), sizeof input);
      #else
      char input[51];
      // Woops. Could SEGFAULT (if compiler with stack smashing protection), or overflow bufffer if not (security breach)
      strcpy(input, getValidatedSqlFromUser());
      #endif
      #endif
      executesql(input);

      Now, given that stack smash protection is pretty much default these days, I'd say the BSD version is the worse security risk, or at least, the one that is hardest to detect. Of course, the design of that program is insane (restricting access in application rather than in the db, e.g.), but I think it illustrates the problem with the strlcpy and friend function pretty clearly.

      As for the linuxism... I have had little problem working around them. If you have had trouble with doing that, perhaps I can point out that the source code to each and every non-standard function is available, as well as documentation? Yes, they happen, because like it or not, most people prefer a good function over a portable one, and nothing you or I can do will change this. Nor would I, if I could really. Improving the libraries tend to start at the grassroot level.

      Finally, I must declare I am tired of your baseless insults, and will only respond to polite posts from this point on. I can accept shit from great programmers that have illustrated their worthiness, but not from someone who obviously still have a lot to learn.

      P.S: Ulrich Drepper's code is incorrect (even if ugly) unlike the code you wrote, at least in the general case. So I think it is taken out of context, as I don't see Drepper making that sort of mistake. The only case strlcpy is valid is if you really want to copy & truncate a string. So if strlcpy was renamed to strcptr(dst,src,n), I think it might be accepted. Though it is a relatively rare usecase, and might be better placed in another library. And once we embarm upon that route, we might as well replace the weak stdlib string library with a safer and better dedicated string library. Like C++ have done with the std::string.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    3. Re:Such language people have :) by Generic+Player · · Score: 1

      "I have made no nonsense claims, and even if I had, you have no reason to be rude."

      What are you talking about? I am not being rude, do you have a persecution complex or something?

      "For Linus's stand on the issue, please read a post he made on this issue. In fact, skip the rest of this post and just read that thread, Linus is a much better teacher than I ever will be."

      Uh, just because he points out that using strlcpy where its not needed is dumb doesn't mean he thinks strlcpy is bad. HE HAS IT IN THE KERNEL. How much more clear can this get?

      "However, you blithely ignore the fact that truncating strings based on length likely covers a bug more effectively than the security problem the buffer overflow is."

      No, I don't. Instead of telling me what I am doing, how about you read what I wrote. To quote me, in the post you are replying to:

      "And strlcpy doesn't randomly truncate strings, it truncates strings that are too long, and then tells you it truncated them in case that matters (which it sometimes does)."

      This is very simple, and people who pretend this is an issue are either repeating nonsense because they don't know C, or they are making up the nonsense because they have an agenda (Drepper). See below where I point out how your code is nonsense.

      "I'd say the BSD version is the worse security risk, or at least, the one that is hardest to detect"

      A single if statement is actually quite simple.

      "Yes, they happen, because like it or not, most people prefer a good function over a portable one, and nothing you or I can do will change this"

      Why do you think I care? I am simply pointing out the fact that the poster starting this thread is wrong, software is in fact targeted for linux. I know why, and I don't need help fixing it. I am just pointing out the fact to the "insightful" but completely wrong poster.

      "Finally, I must declare I am tired of your baseless insults, and will only respond to polite posts from this point on. I can accept shit from great programmers that have illustrated their worthiness, but not from someone who obviously still have a lot to learn."

      I didn't insult you in the last post, baseless or otherwise. And given the code you just posted, you have no ability to judge how much I or anyone else needs to learn.

      "P.S: Ulrich Drepper's code is incorrect (even if ugly) unlike the code you wrote, at least in the general case. So I think it is taken out of context, as I don't see Drepper making that sort of mistake."

      I posted the link for you, its taken directly from his post. And its not incorrect, just ugly and a gnuism.

      "The only case strlcpy is valid is if you really want to copy & truncate a string."

      Uh huh.

      So if strlcpy was renamed to strcptr(dst,src,n), I think it might be accepted.

      Why? strncpy truncates too, that's what its modelled after, hence the name.

      "Though it is a relatively rare usecase, and might be better placed in another library."

      No, its a ordinary use case, not rare. Its a replacement for strncpy because strncpy is stupid and doesn't guarantee to NULL terminate, is slow, and is so frequently misused leading to exploitable holes. Anywhere that has strncpy should have strlcpy, there is absolutely no reason to have strn but not strl.

      As for your code, where to begin. First of all, in your example case you would know the max length of table names, and so you would use that instead of 51 as your buffer size. Second, in a case where truncation matters, you test for it, duh?

      if (strlcpy(input, getValidatedSqlFromUser(), sizeof input) > 51) do_whatever_you_want_to_handle_truncation();

      Third, your ifdef ULRICH strcpy won't compile, strcpy doesn't take a length. You want strncpy. And you just end up with a slower version of strdup, which is what you should have used in your nonsense made up example that has nothing to do with strlcpy at all. Notice how all the examples strlcpy haters come up with are ridiculous and nonsensical?

    4. Re:Such language people have :) by synthespian · · Score: 1

      Yes, listen to the words of your gurus...

      I guess we must just forget the fact the Theo De Raadt (one of the guys who created strlcpy), of OpenBSD, has produced a vastly better security track record in the OS he develops, than that of Linus' OS, right?

      Linux security was pretty much a joke, years ago. They all laughed at it, at the OpenBSD side of the fence.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    5. Re:Such language people have :) by EsbenMoseHansen · · Score: 1

      A few points, the rest of your post speaks for itself.

      As for Linus's opinion, anyone can read it in the linked post. He is against the inclusion in glibc and states that very clearly in that thread, for the reasons I have outlined.

      First of all, in your example case you would know the max length of table names, and so you would use that instead of 51 as your buffer size. Second, in a case where truncation matters, you test for it, duh?

      Until the next someone uses some sort of valid filler (like a spaces, or something else) to achieve that chopoff. Boom, security breach. Yeah, I should've checked the return value, but what then would I have done? Raised an error? Reallocated? The code would end up being even uglier. And we all know that requiring developers to check return codes all the time instead of just doing the right thing is a bound to lead to bugs. Which is why C++'s new no longer returns a null pointer if the allocation fails.

      The real problem is the usage of a fixed buffers in the first place. str*cpy all encourages using fixed buffers, which is why these people oppose them. We can't get rid of strncpy (without violated the C standard), but we can avoid adding more of these functions, which only gives you a false sense of security. You could read that thread I linked, (not just the random post I linked to yesterday)... it is quite informative.Here it is openSSH's code that is being picked apart.

      And I most certainly don't want strncpy. Yeah, I made a typo, forgetting to remove the length while I copied and pasted, so shoot me. I'd get a compile error and remove the extra parameter. The purpose of strncpy and friends is to manipulate records in a database in a certain format; using them for string handling in any other case is insane. You know that, I know that, any C programmer worth his salt knows that, why do you keep bringing strncpy up?

      I didn't use strdup since it isn't available on all platforms, and because I wanted to illustrate the general concept (keep track of the length, (re)alloc as necessary. If I was doing this for real, I'd use/write a library, where the stringtype would be something like

      struct easy_string {
      // length of string
      size_t length;
      union {
      char buffer[40];
      char* buf_ptr;
      };
      };

      Which could be used with library functions to behave correctly in all circumstances. I am sure such an obvious idea is already implemented in some library, though.

      PS: Not being rude? What do you call, and I quote,

      Wow, talk about full of shit. ? But I commend you latest effort, which is in a nice and sober tone. Thank you for that, I really appreciate it.
      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    6. Re:Such language people have :) by Anonymous Coward · · Score: 0

      Your problem in that example isn't strlcpy(), it is that you are not capable of writing correct C. If you're not going to check the return value of functions like strlcpy() then of course you will introduce subtle bugs and security holes.

    7. Re:Such language people have :) by Generic+Player · · Score: 1

      "As for Linus's opinion, anyone can read it in the linked post. He is against the inclusion in glibc and states that very clearly in that thread, for the reasons I have outlined."

      Anyone can grep -r strlcpy in the kernel source tree too. Actions speak louder than flamewars, especially considering Linus' tendancy to flame people because they are smarter than him, then quietly do what they said in the background because he knows they are right.

      "Until the next someone uses some sort of valid filler (like a spaces, or something else) to achieve that chopoff. Boom, security breach."

      Boom, wtf are you talking about? If the max table length is 255 lets say, and someone puts a 255 char table name in plus a bunch of spaces which we truncate, how is that any different from them just putting in the 255 char table name to begin with? This has nothing to do with anything, why do you think its a security breach?

      "Yeah, I should've checked the return value, but what then would I have done? Raised an error?"

      Gee, what do you think you should do when you get a table name longer than the max length of a table name? Sounds like an error to me.

      "And we all know that requiring developers to check return codes all the time instead of just doing the right thing is a bound to lead to bugs."

      We all don't know that. If you don't like C then don't use it. But refusing to include useful C functions because you don't like that they behave consistantly with the rest of C is moronic at best.

      "The real problem is the usage of a fixed buffers in the first place. str*cpy all encourages using fixed buffers, which is why these people oppose them."

      And fixed buffers make perfect sense, because a tons of things have a fixed max size, like table names. Your example is a perfect example of why strlcpy IS GOOD. You would need to recreate strlcpy's behaviour to make your example correct and secure.

      "You could read that thread I linked, (not just the random post I linked to yesterday)... it is quite informative.Here it is openSSH's code that is being picked apart."

      Yes, it is quite informative. It shows both how ignorant Linus is, and how he likes to flame people for being better programmers than him, while in the background copying the same thing he is flaming them for. That's not openssh's code being picked apart, its a typo'd version of a few lines being bitched about by idiots who haven't actually looked at the code. Considering the security track records of linux and openbsd, Linus has no place to be telling openbsd developers about secure coding. I will trust history over a bizzare fetish where you have convinced yourself that Linus knows anything about secure programming.

      "The purpose of strncpy and friends is to manipulate records in a database in a certain format; using them for string handling in any other case is insane. You know that, I know that, any C programmer worth his salt knows that, why do you keep bringing strncpy up?"

      BECAUSE strlcpy IS A REPLACEMENT FOR strncpy! Are you retarded? I bring it up because its 100% relevant, it is in fact the whole fucking point. strlcpy is a correct, secure and effecient replacement for strncpy, so obviously it is to be used instead of strncpy. In situations where you are dealing with fixed size buffers. And despite ignorant, memory exhaustion error filled code that tries to show otherwise, this is very often the case. I was right to insult you in the first post, I apologize for not being more of a dick in the second post. You are a fucking idiot.

      "I didn't use strdup since it isn't available on all platforms, and because I wanted to illustrate the general concept (keep track of the length, (re)alloc as necessary."

      And so you gave an example where it makes no sense at all to realloc, and where it would slow down the code and create security holes if you did? TABLE NAMES HAVE A MAX LENGTH. THEY ARE FIXED SIZE. Why do you think using a function that operatings of fixed length strings whe

    8. Re:Such language people have :) by EsbenMoseHansen · · Score: 1

      I see I will get nowhere with this. My example string contained abitrary SQL, not a single table name, and anyway, the table names were of an unknown max length (I see I should have used the classed path length, since that one is well known to be of unknowable length.). Also, the spaces were supposed to go in front, I didn't think I needed to spell that out.

      strncpy is not meant for general string manipulation, but for putting strings into a record format which is rarely used these days... at least I have not seen it for more than 10 years.

      But as you seem to think that anyone not agreeing with you must be an idiot, I am only writing this in case a novice programmer stumbles upon our, eh, conversation and makes that very common mistake about strlcpy. To recap: In the general case, strlcpy is wrong and non-standard, where another function could achieve at least one of those 2. That's 2 good reasons to avoid it.

      That it is also a BSD'ism is the fact that got lost somewhere in this thread.

      plonk.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    9. Re:Such language people have :) by Generic+Player · · Score: 1

      "Also, the spaces were supposed to go in front, I didn't think I needed to spell that out."

      And that still does not lead to a security hole. You can't even make up an example where you shouldn't use strlcpy? You're entire argument is that because strlcpy is not meant to be used for everything it should not be used at all. memcpy is not meant to be used for everything either, yet there it is. Just because you can use a function wrong, does not mean it adds no value since you can also use it right.

      "strncpy is not meant for general string manipulation"

      Yes it is, it was meant as a bounded strcpy. It does this task very poorly, hence strlcpy replacing it. Why do you think its named strncpy? It has nothing to do with your bizzare record format nonsense, its strcpy with a length.

      And you can see strncpy in use all over the place, grep the source tree of most open source C programs and you will see strncpy being used.

      "But as you seem to think that anyone not agreeing with you must be an idiot,"

      No, I made it quite clear that failing to understand someone else's opinion, presenting it as your own in an incorrect and obviously stupid example, while pretending to be an authority on secure C programming makes you an idiot. Ulrich Drepper thinks strlcpy is bad too, but he at least knows C and is capable of making up examples where you shouldn't use strlcpy. Hence he's not an idiot, just a liar for pretending that's why he won't include it when its really his NIH complex where he wants to push his non-standard mempcpy function over someone else's non-standard strlcpy function. Obviously he has no problem with the concept of such a function, or including non-standard functions or else mempcpy wouldn't be in glibc. He just wants people to use his non-standard extension over the one that looks nicer and is already widely adopted.

      "To recap: In the general case, strlcpy is wrong and non-standard, where another function could achieve at least one of those 2. That's 2 good reasons to avoid it."

      To recap: strncpy fails to guarentee NULL termination and doesn't let you check truncation. strlcpy solves these problems and is faster than strncpy. Use strlcpy instead of strncpy, its 51 lines long including the license, you can use it in any project. Nobody with any background in secure C programming denies the usefulness of strlcpy/cat. The only people who argue against strlcpy/cat are people with an agenda of pushing their strncpy alternatives, or people like you who just regurgitate those people's rhetoric without understanding it. Even systems without strlcpy like plan 9 include some function to replace strncpy securely, showing that wether or not you want the particular implimentation that is strlcpy, there is a need and desire to have a secure strncpy replacement.

      "That it is also a BSD'ism is the fact that got lost somewhere in this thread."

      First of all, its not a BSDism. All the BSDs are smart enough to include it in their libc, yes. But so do Solaris and Windows services for unix. Just because a couple programmers from one of the BSDs made the functions initially, doesn't make it a BSDism. It would be a BSDism if it only was found in BSDs.

      Second, the fact that people who use it include it in their code got lost on you. Its not relying on a BSDism if you include the function in your code, use your head. That's like saying that using daemon() is a relying on a BSDism, when in fact most unix systems have daemon(), and you can can include it for those that don't. Or that using sockets is relying on a BSDism. A ton of current unix implimentations came from a BSD initially, its only a problem if you blindly assume every system is the same.

      I never said people shouldn't use non-standard extentions like gnuisms, just that they should not RELY on them. So if you include the functions in question, you are all good. Pretty simple huh?

  105. its not that hard to understand by cinnamon+colbert · · Score: 1

    people adopted firefox cause it gave them real benefits that THEY actually cared about and cause it was not that hard (me personally, i cared bout tabs, security, book mark all tabs to folder, cntrl+ increases font)

    why would I adopt linux when the barrier is high and there are no benfits. I personally don't care bout security and multi thread and all that crap; that linux has a cool desktop with a nice gui is like the ford dealer saying the car comes with 4 wheels, and adopting linux is a pain - gotta go out and get a new printer , gotta go out and get a new wireless card, gotta do this, gotta do that, for what ?
    tell me why I - not you but me- wants linux

    tell me some real vendors who sell predone machines (I went to dell/hp sites the other day, if preloaded consumer machines are there, they are hard to find)

    the rant that drivers are the barrier is nonsense

    the barrier is that linux does not do something new that people care about. people don't care about security and file systems and all that crap. maybe people are stupid, or dumb, or whatever, but you are learning something about life when you learn that all the technical crap in the world does not matter if people don't care about it.

    one thing and one thing only will drive linux adoption to the desktop: do something that people care about
    the corallary is that you have to patent it, to restrict MS and sun, otherwise they will just steal it, and even if they do it badly people wont care

    I am sure any /.s out there who have tried to sell products will tell yo0u that displacing an existing product wiht a variant is very very very...very hard.

    call me troll, but I speak the truth: do something that people care about and they will come.

  106. hello there by crodrigu1 · · Score: 0

    This issue is because several problems: 1) Like driving in Boston, if you do not know how to use the tool you do not belong here, so get out 2) My SDK is better than your SDK. 3) Because is not for profit, is for glory. I cannot be a follower (see #2) 4) Games, every time that I mentioned Linux to friends said NO GAMES (yes there is some games, but no like Windows) 5) Installers: Something so basic for a GUI do not exists for Linux (yes they are about 2000 of them, nothing works, if you do not believe me, see the Reviews for the Nvidia Driver installer) Problem with Linux GUI is that is fragmented into multiple camps, everyone has wonderful ideas and implementations, but they never are complete.

  107. Focus, Pinky, Focus! by FloridaSage · · Score: 1

    The userbase for GNU/Linux is the largest in all the Open Source OSes. Developers are shooting for the biggest audience. *BSD is certainly second in userbase numbers. Both appear in multiple variations to suit the needs of niche users. But, they are not monolithic in the many thousands of viable applications. The applications tend to be fast and light in the code, because they share support applications (ex: spellchecker is shared by 26 Office and editor, browser, programs). Open Source is code done right, from the first line through the full release it is inspected, detected, and bad parts rejected, by millions of developers, coders, users. Hey, it works for me, and for all of the Eastbrook Elementary kids, who prefer http://pclinuxos.com/ that you could run, so you would see how good FREEdom can be!

  108. Trick for future reference by frogstar_robot · · Score: 1

    Once you DO get the Linux system the way you like it:

    # tar cvfz etc_correctly_configured.tar.gz /etc
    If you running a Debian derivative add this too:

    dpkg --get-selections > installed_packages.txt

    You should use checkinstall to install any non repo software built from source and keep either the debs or source trees. All this can be tucked out of the way. Finally, keep a backup of your home directory on an external hard drive or burned to DVDs.

    I can replicate my perfectly working setups in about four hours and most of that is waiting for apt-get to pull in and install the stuff. You don't want to drop the etc tarball on a new system. It is strictly a reference to save you from googling up how say mplayer works. I've certainly made judicious use of old config files though. What you can do with the installed_packages.txt file though is simply magical:

    cp old_etc/apt/sources.list /etc/apt/sources.list
    dpkg --set-selections (less than symbol - f'ing lameness filter) installed_packages.txt
    apt-get dselect-upgrade

    Those three commands will install everything that was on the old system minus anything that didn't come from the repos; that is 95% of the work of replicating a system right there. But you kept all of that stuff or know where to find it?

    If you aren't using a Debian derivative, I assume equivalent tricks can be played with yum.

  109. Framebuffer consoles! by The_Dougster · · Score: 1

    The Linux console in framebuffer mode is pretty cool. A lot of Gentoo users typically have it loaded so as to use the spiffy bootsplash system, and the graphics consoles are wonderful.

    If you are into text console stuff, there is Twin - Textmode window environment which is surprisingly neat. It can run bash boxes in a ncurses based environment. Gentoo had it in portage and it compiled easily for me. A bit rough around the edges, but cool.

    Also, I just have to plug Turbo Vision for POSIX which is that classic Borland library used for the great DOS apps of yore. I've been tinkering with it on Gentoo amd64 and even submitted a patch for the terminal class upstream. (Yes, I managed to compile it with debugging symbols, and trace down a segfault using gdb). I'd love to see Turbo Vision get a little luvin' so that it can run Bash boxes like Twin can, for no real reason other that its just such a darned nifty (and fast) environment.

    And back to the framebuffer graphics consoles themselves. I believe you can write SDL apps that use the framebuffer. There was a FBUI project going, but I think it's dead.

    --
    Clickety Click ...
  110. hardware support in Linux by falconwolf · · Score: 1

    The only area where Linux really lags in hardware support these days is wireless card support.

    Another area where Linux lags in hardware support is with double or dual layer DVDs. For the past few months I've been looking for one for my Linux box but I haven't found one I can just walk into a store and pickup. Sure I may be able to order one but I want a physical brick and mortor store I can return it to if I have a problem with it. I'd also like it if my distro supports it, but as it is most of the drives my distro supports are single layered and discontinued.

    Falcon
  111. Free software needs solidarity by slapys · · Score: 1

    While I somewhat disagree with your opinion that "Linux is ready for the desktop" (having your package management system break is NOT very user-friendly), I definitely agree with you when you say that Linux is "doing an excellent job" in entering the business desktop scene.

    I have a lot of respect for ReactOS and the other free OSes out there, and I don't want to marginalize work that has gone into those systems, but I believe that improving Linux is the right direction. If an average PC user sees several operating systems with mediocre application and hardware support, she is not likely to want to try them out, because Windows offers a better experience than those operating systems. She will be more attracted to a single, powerful OS with lots of support that is easy to install. This is why Ubuntu is gaining popularity. Once I installed it, I fell in love and will probably never go back. Never again do I have to spend time on figuring out how to support my hardware. Everything works. I appreciate this the most because time is valuable to me - I am a college student at a fast-paced university, and I can't afford to spend lots of time on the inner details of my OS. I just want to use my computer.

    1. Re:Free software needs solidarity by swillden · · Score: 1

      having your package management system break is NOT very user-friendly

      Is there some package management system that breaks? Maybe I'm spoiled by Debian, but that's not a problem I'm familiar with. I'd also point out that Windows' "package management system" breaks on occasion, too, so that's not a good criterion for determining desktop "readiness". There's been more than one Windows app that I couldn't install or uninstall because of some weirdness.

      I have a lot of respect for ReactOS and the other free OSes out there, and I don't want to marginalize work that has gone into those systems, but I believe that improving Linux is the right direction. If an average PC user sees several operating systems with mediocre application and hardware support, she is not likely to want to try them out, because Windows offers a better experience than those operating systems

      Agreed, but I think those are all second-order issues. Most people will use what's well-supported by hardware and software vendors -- especially PC system vendors. Relatively few people are willing to try out anything that's different, no matter how much better it is. OS X is much better than Windows... yet Apple's market share is small, and would be even without the small premium you pay for Apple hardware.

      No, the issues that will propel Linux don't have much to do with it being better in terms of user interface or features. Those must be good enough, of course, and "good enough" is a moving target. But by themselves those aren't enough to push people to switch. Firefox is vastly better than IE6, switching is easy, and *still* only about 10% of users bothered. The issues that encourage Linux adoption are largely things that desktop users don't care about. They are things that corporate and government IT staffs care about, though, which is why Linux is making progress in those environments.

      So while I agree with your conclusion, that solidarity is important, I disagree with your rationale. Solidarity is important because it allows Linux to obtain hardware and software vendor mindshare. It's much more compelling when 1000 potential customers ask for Linux compatibility than when 400 ask for Linux, 200 ask for ReactOS, 150 ask for AROS, etc., etc. Even if, honestly, the same vendor action (releasing good docs) will enable support for all of the Free OSes.

      Not only doesn't combining our forces behind one platform in order to push it forward as fast as possible not matter, I don't think it would happen. It's the same as the notion that the existence of both GNOME and KDE divides the Free desktop development resources. Free Software doesn't work that way. It's not the case that if a GNOME or ReactOS developer didn't have GNOME or ReactOS to work on that they'd work on KDE or Linux.

      Volunteer developers work on a project because there's something about that project that attracts them. If there's a "competing" project, it's typically different enough that the same developers aren't attracted to it -- otherwise the projects would likely be combined. For example, I contribute a bit to KDE, because I like C++, I like Qt and I like the architecture and the philosophy. If KDE didn't exist, I probably wouldn't contribute to GNOME because I don't like C and I don't like Gtk.

      So, I applaud all of the developers who work on non-Linux Free OSes. I only ask that they claim to be Linux users when talking to the non-Free world :-)

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  112. What's holding Linux back? by falconwolf · · Score: 1

    The ONLY thing holding linux back from a desktop point of view at this point is a lack of a standardized LDAP backend for businesses thats as retardedly easy to work with as Active Directory (from an admin standpoint). _Thats it_

    Not at all. What is holding Linux back from most people's desktops is that most users can't just walk into a store and buy a PC with Linux preinstalled. Most PCs have Windows preinstalled and Macs have OSX preinstalled, for most people to use Linux they have to install Linux themself, yet most people hardly ever install an OS, and I dare say that most of the tyme they do they do because the PC companies tech support said to reinstall the OS when they've had a problem and called tech support.

    Falcon
    1. Re:What's holding Linux back? by cHiphead · · Score: 1

      Sure, thats a reasonable explanation, but until its adoptable in a business sense, home users don't matter. Business is where the defacto standards result from.

      Reinstalling Ubuntu is WAY easier than Windows... Boot with install disk (which is now a LiveCD), click 'Install on Hard Drive' icon on the desktop, browse the internet/check mail/write a document while its installing, reboot, use.

      --

      This is my sig. There are many like it, but this one is mine.
  113. Re:Can anybody share why they do or do not prefer. by doom · · Score: 1
    laffer1 wrote:
    The difference between GPL and BSD licenses: 1. GPL = code freedom 2. BSD = coders freedom

    I care about people more than source code. Everyone is entitled to their opinion.

    Oh, knock it off. The trouble with the BSD is that it's prone toward proprietary forks, which splits the community and bleeds off energy from the projects. Take a look at the Unix wars of the 80s. For that matter, take a look at Mac OS X.

  114. Linspire by falconwolf · · Score: 0

    On another front, I'm a bit disappointed that no one seems to be touting Linspire/Freespire as a distribution. It's one of the few that's really been targeting the consumer market.

    I got a new PC with Linspire preinstalled a few months ago, and I've made mention of it a number of tymes. Once booted up it acts pretty much like Windows, so like you say, it's targetted at the consumer market. Get more OEMs to preinstall Linux and more stores to carry them is what it will take for linux to have a bigger market share.

    Falcon
  115. hw at mit by Anonymous Coward · · Score: 0

    none of the HP chipmunks were there running SCHEME?

    They were in the software labs for the undergrads during that era.

  116. BSD License by falconwolf · · Score: 1

    The BSD is a wonderful license if you want to effectively place something in the public domain but can't bring yourself to accept that you might not get any credit for it... but IMO it's just a half-assed half-step towards making it PD.

    The BSD License isn't all just about putting software into the PD, public domain. I'm not a developer myself, however as a photographer I'd like to work on graphics, photo editing, software comparable to Photoshop and if I were to put the effort required in developing such an app I'd want to be able to make money off of selling it without having someone else take the source code and selling it as well without paying me anything. More like what I'd like to do is to keep the code closed until I have made enough money to make it worthwhile then release or copyleft the code. Though I'm not sure I think the BSD license allows this whereas the GPL most definitely does not.

    Falcon
    1. Re:BSD License by drinkypoo · · Score: 1
      More like what I'd like to do is to keep the code closed until I have made enough money to make it worthwhile then release or copyleft the code. Though I'm not sure I think the BSD license allows this whereas the GPL most definitely does not.

      Using no source license (i.e. the source is protected by copyright) allows you to do this! Then when you want to release the code, you pick any license you want.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:BSD License by synthespian · · Score: 1

      BSD code is not public domain. Credit must be given in BSD code. In public domain, it's not necessary.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    3. Re:BSD License by falconwolf · · Score: 1

      Using no source license (i.e. the source is protected by copyright) allows you to do this! Then when you want to release the code, you pick any license you want.

      However if I use some code with a BSD license, from my understanding of the license, I need do is give credit to the authors of the code I use along with any conditions they've put on it. On the other hand if I use any GPL code then I have to include all the code if I distribute the program. For instance if I started with GIMP but made improvements, like adding 16 or 24 bit colour support which it doesn't have yet, then I'd have to release all the code imcluding the modifications I made.

      Falcon
    4. Re:BSD License by drinkypoo · · Score: 1
      However if I use some code with a BSD license, from my understanding of the license, I need do is give credit to the authors of the code I use along with any conditions they've put on it. On the other hand if I use any GPL code then I have to include all the code if I distribute the program. For instance if I started with GIMP but made improvements, like adding 16 or 24 bit colour support which it doesn't have yet, then I'd have to release all the code imcluding the modifications I made.

      Your understanding is correct. My point is that you don't need a source license until you distribute the source in some way. Now, you could use the BSD license, but the only difference between that and putting it in the public domain is that the code is still protected by copyright. But if you release it under BSD then people can use it as they wish anyway and all they have to do is put your copyright notice in the code and keep that code under the BSD license. They don't have to distribute the code to anyone. This is no different from the public domain license except your name will stay on a piece of code which will never see the light of day again.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  117. And that is why Linux beat BSD. The GPL prevented by falconwolf · · Score: 1

    fragmentation.

    If the GPL prevented fragmentation then what are all of the different distros? Isn't having all of them causing fragmentation?

    Falcon
  118. You should check it out again by Paradox · · Score: 1
    It's slow mostly because it takes a noticeable time to start processes, and this bothers me, as it's something I do a lot. Also, the GUI takes up so much memory that there is less of it left to get work done with. Once this gets up to the point where it starts swapping a lot, obviously productivity is out of the window.


    You say 'iBook'. Which I assumes means you've got a much older laptop there. I completely agree, the G3 iBooks were real dogs. But you shouldn't extend that to the modern system. When I pull up something lightweight like a command line utility or an X11 app (running over Apple's X11 layer) the response is about as fast as any of my linux boxes.

    Otherwise, about the only thing my linux install does faster is boot.

    It's a hassle, because, although a lot of open source software technically works on it, not all of it is readily available. At least at the time I still used it (the situation may have improved since), there were fink, darwinports, and pkgsrc, each supporting some packages but not everything I wanted (pkgsrc worked best for me, but didn't provide binaries for OS X). Having to use different package managers and having to compile things from source are terrible time wasters. The software that Apple ships is either different from what I'm used to from other *nix systems, or it's the same software, but often an older version, which caused further problems.


    This is better than it used to be, but certainly Fink and DarwinPorts leave a lot to be desired. But as time has gone on, the free and open source mac software world has grown significantly. Most of the irreplacable linux-oriented apps are in a package manager, and there are great FOSS alternatives for many common mac tasks.

    There are also some closed products that are so good that they beg for that fact to be excused. For example, the now extremely popular TextMate editor is something so incredibly good that if it and emacs had a fight, I'm not sure who'd win. And certainly TextMate is easier to get started with, Emacs has a very stiff learning curve and lacks the awesome video podcast showing tips and tricks.

    Also keeping the software up to date is a nightmare when some of it is integrated with Apple's updater (which keeps pushing "updates" for software I don't have or want), some of it is integrated with some open-source package manager (fink and friends), some of it comes with custom updaters, and some of it doesn't have any update mechanism at all.


    You know, thinking about this, I realized that a lot of my linux stuff has to be outside the package structure too. If you're developing, you often get nightlies and betas well before any kind of package can be submitted and piped through. Personally I call this a wash. Most Linux distros update core components, provide a marginally complete but not terribly up-to-date package directory, and that's what OS X does.

    The final straw was that Tiger broke the ext2 driver, meaning the end of sharing files between OS X and Linux. Yes, Linux supports HFS+, but the interaction between the Linux HFS+ driver and Apple's fsck has given me...bad results in the past, so I'm not going there again.


    Your information is outdated.

    Of course, none of this means that OS X doesn't look gorgeous and isn't a great OS if you just want to use the great software that Apple ships with it, and maybe a handful of third-party apps. However, for a command-line junkie like me, GNU/Linux beats OS X hands down.


    I find myself far more productive in OS X than in Linux, and I have used both for years and understand them both quite well. I think the real reason is that OS X has Quicksilver, whereas there is no good competition for that in the linux space.
    --
    Slashdot. It's Not For Common Sense
    1. Re:You should check it out again by RAMMS+EIN · · Score: 1

      ``You say 'iBook'. Which I assumes means you've got a much older laptop there. I completely agree, the G3 iBooks were real dogs.''

      But I have a G4, 1.33 GHz. Got it just after Apple announced the Macbook and stopped boasting about battery life.

      ``Otherwise, about the only thing my linux install does faster is boot.''

      Funny. Fast boot times are the only thing I miss from OS X. Although I'm running Dapper (Kubuntu), which is notoriously slow in booting.

      ``For example, the now extremely popular TextMate editor is something so incredibly good that if it and emacs had a fight, I'm not sure who'd win.''

      Perhaps TextMate should be included as a text editor in the Emacs operating system? ;-)

      ``Most Linux distros update core components, provide a marginally complete but not terribly up-to-date package directory''

      Debian sid and Gentoo tend to be very up to date.

      ``Your information is outdated. [link to ext2 driver]''

      Thanks. I didn't mean it's still broken (I expected it to be fixed at some point), I just meant that's what finally got me off OS X. Before that, I actually used OS X regularly, to test my software on it.

      By the way, I just booted OS X, and something is terribly wrong. The clock is set to sometime in 1904, the keyboard is misbehaving, sometimes typing normally, sometimes not eliciting any response, sometimes putting the computer to sleep. And, of course, my icons have gone missing, but that's almost routine. Anyway, I'm sure this is not a normal Mac experience...but I seriously wonder what caused it, considering that the same machine was working fine under Linux just now...

      --
      Please correct me if I got my facts wrong.
    2. Re:You should check it out again by Paradox · · Score: 1
      Debian sid and Gentoo tend to be very up to date.


      Either the packages are up-to-date enough on DarwinPorts, or they are just too slow for my development cycle. It's interesting to note that the stuff I've got installed outside of management on my OS X box is pretty much the same stuff I have on my linux box.

      Maybe I have a bad taste in my mouth from Debian's package system going insane and being unable to install most packages because I installed one misconfigured package and it destroyed my version database. :\
      --
      Slashdot. It's Not For Common Sense
    3. Re:You should check it out again by Bender0x7D1 · · Score: 1

      But I have a G4, 1.33 GHz. Got it just after Apple announced the Macbook and stopped boasting about battery life.

      There is no comparison between a G4 and a MacBook, let alone a MacBook Pro. The new systems are much, much faster. Remember, the G4s were dated even before the switch to Intel was announced, let alone completed.

      --
      Reading code is like reading the dictionary - you have to read half of it before you can go back and understand it.
  119. idiot by Anonymous Coward · · Score: 0

    Idiot... No, really...

  120. The little penguin by towsonu2003 · · Score: 1

    I don't think the problem is with the penguin. It's the environment this penguin is trying to survive in...

  121. Linux won't become popular on the desktop by mushadv · · Score: 1

    Not the whole of it, anyway. A loosely connected collection of operating systems won't suddenly get popular, because that's just not promotable. It's a hell of a lot more feasible to get people to switch when you say "Get Ubuntu!" rather than "Get Linux! One of three hundred different flavors!" It's one distro that will rise up and take the desktop (well...hopefully).

  122. judicial activism by falconwolf · · Score: 1

    Remember, kids: it's only judicial activism when the rulings support left-wing positions.

    That's about the size of it, for right-wing positions. On the left, if a judge doesn't support their position s/he is an activist judge. And the same on the right. I say get back to the orignial meaning of the USA Constitution!!! Liberty and SMALL government.

    Falcon
    1. Re:judicial activism by HomelessInLaJolla · · Score: 1

      My favorite source for a well-written research paper on the issue, articlev.com, is currently unavailable. I imagine a political lobbyist group managed to get the site taken down through some legal crap.

      As far as the right of Congress to regulate interstate commerce: My genuine belief is that, at the time the Constitution was written, "commerce" had a very succinct legal definition that didn't mean "anything under the sun". The definition of "commerce" was probably linked to official incorporation with the government or legal papers involved in the licensing of a stamp such as was available for tea and tobacco and other materials of trade.

      --
      the NPG electrode was replaced with carbon blac
    2. Re:judicial activism by faolan_devyn_aodfin · · Score: 1

      Well I don't think we are going to get back our small government. History shows that governments tend to become more bloated with time as they accumulate more laws. Sometimes they can be won back by revolts and civil war but that isn't pretty and if the wrong side wins you could get end up with a megalomaniac with a big militia on your hands... like say Napoleon Bonaparte after the French Revolution. That would be bad.

      --
      Pagan? Geek? Check out #paganism on Freenode IRC
  123. Linux isn't the issue by Anonymous Coward · · Score: 0

    WINE is. People aren't going to move to Linux *or any other* platform for much the same reason that Microsoft is tied to supporting decades-old software -- because people want all their stuff to work without having to become programmers themselves to get it working.

    Trying to move consumers to another platform would simply erase all of the progress made by Linux -- you would have to start over and eventually end up at the same bottleneck. Pick your battles. It does no good to fight over the scraps of FOSS operating systems when MS still has a monopoly.

    Game support especially is terrible for Linux, which is why WINE is so important. While games may seem trivial to some, the average consumer is going to balk whenever they hear the word "except". As in, this OS supports everything you would use a computer for, except...

    Why would the average person use a different OS if it meant having less functionality? You have to keep in mind that concepts like open source are lost to people who don't work with source code. The key to beating Windows is to be compatible with it.

    (See also: Macintosh)

  124. Comparing Linux/Firefox marketshare is idiotic by walterbyrd · · Score: 1

    Using firefox has no effect on what other apps I can run, or what hardware I can run. I don't have to change anything to put firefox on my windows box. Using linux means I have to change everything.

    To compare linux/firefox marketshare, and conclude that the FSF must be doing something wrong is idiotic.

    It's all about drivers and apps. Windows has them, Linux doesn't.

  125. how can Linux take over? by falconwolf · · Score: 1

    Linux hasn't failed to take over the world because it needs a microkernel or a different IP stack or whatever

    I don't think so, Linux hasn't taken over because it is the rare PC that has Linux preinstalled. The vast majority of people don't buy a PC then install an OS. When they get home with a new PC all they want to do is set it up, plug it in, and have it work. When PCs with Linux preinstalled can be found anywhere and are easy to setup then they will gain market share.

    Falcon
  126. MP3, WMA, AAC, and first mover advantage by tepples · · Score: 1

    MP3s could pose a problem however there are plenty of open source projects that support them, if they can do it why not this?

    A lot of these open-source projects are developed outside the United States. We want to be able to distribute this Windows clone in territories where courts have recognized patents on methods of communication defined by data processing algorithms (e.g. LZW, MP3).

    As for WMA, well I see that as far less of a problem, however presumably the reason someone would be using WMA's is if they're using a portable device which plays them, in which case the software/codecs installed by the device would provide the playability?

    WMA player software on Windows relies on the codecs provided as part of the Windows Media Player software, which require a validly licensed copy of Windows to be present.

    With the market-dominance of WMA-incompatible iPods I don't see this as a huge issue anyway.

    AAC is just as much patented, and FairPlay is just as much a trade secret, as WMA technologies.

    Well IE, Media Player, and Office don't necessarily come into play here. [...] That software could be installed and run thanks to Windows compatability if necessary.

    Per copyright law, you'll have to have a validly licensed copy of Windows present in order to run these programs, so why not just use Windows and avoid the bother of maintaining a dual boot?

    As far as the Windows 98 comment, why would Windows 98 be the Windows to mimic? Vista or XP seem the obvious choice.

    I was imagining the following use case: Windows 98 is released. Free software developers take years to clone all of its user interface, relying on the uncopyrightability of user interfaces under United States copyright case law (Lotus v. Borland). Before they finish, Windows XP is released. Or: Windows XP is released. Free software developers take years to clone all of its user interface. Before they finish, Windows Vista is released.

    1. Re:MP3, WMA, AAC, and first mover advantage by LighterShadeOfBlack · · Score: 1

      A lot of these open-source projects are developed outside the United States. We want to be able to distribute this Windows clone in territories where courts have recognized patents on methods of communication defined by data processing algorithms (e.g. LZW, MP3). Possibly, however the bottom line is that this is no more of an issue for my hypothetical Windows-a-like then it is for desktop Linux. The difference perhaps being that there's a fair chance that if the Windows user is using anything but WMP they can still run their favourite media player on the OS as-is.

      WMA player software on Windows relies on the codecs provided as part of the Windows Media Player software, which require a validly licensed copy of Windows to be present. Do programs like Winamp use WMP for this? I admit I've never dealt with WMA much because, well, quite frankly it's a bullshit format. Obviously some people use it, maybe there's an issue for them in some cases where their chosen player requires WMP codecs, again though this is no more of an issue then it would be for people trying to switch to Linux.

      AAC is just as much patented, and FairPlay is just as much a trade secret, as WMA technologies. Yes but if they're using an iPod they're almost definitely using iTunes aswell, which of course handles AAC, MP3, and I believe possibly WMA aswell.

      Per copyright law, you'll have to have a validly licensed copy of Windows present in order to run these programs, so why not just use Windows and avoid the bother of maintaining a dual boot? I don't think there's anything in copyright law that demands you to own Microsoft Windows in order to run Microsoft Office? Granted I don't think I've ever installed MS Office, however if it tries to make such a requirement that's an anti-trust suit waiting to be made (at least here in Europe). As for WMP and IE, well I believe it's possible for these to be installed and run separately of Windows although I doubt it simple enough for the target audience. However remember that this is all part of a what-if scenario where the user finds whatever equivalent comes with the OS unacceptable. And again this then begs the issue of what would Linux do any better in this unique situation?

      I was imagining the following use case: Windows 98 is released. Free software developers take years to clone all of its user interface, relying on the uncopyrightability of user interfaces under United States copyright case law (Lotus v. Borland). Before they finish, Windows XP is released. Or: Windows XP is released. Free software developers take years to clone all of its user interface. Before they finish, Windows Vista is released. Fair enough, but as I said I don't think they'd be that far behind if a concerted effort is made. Maybe one version behind from the initial build, but then most people don't rush out to buy a new version of Windows anyway so I don't consider that a major roadblock.

      I'll apologise in advance for typos and grammatical errors on this one. It's 2am here.
      --
      Spelling mistakes, grammatical errors, and stupid comments are intentional.
    2. Re:MP3, WMA, AAC, and first mover advantage by tepples · · Score: 1

      the bottom line is that this is no more of an issue for my hypothetical Windows-a-like then it is for desktop Linux.

      True, but it is still an issue. Look at what happened when Red Hat and later Fedora left out all MP3 software after getting the letter from FhG.

      Do programs like Winamp use WMP for [WMA playback]?

      Yes, Winamp uses a codec provided by Microsoft, which I believe comes with a license tied to the use of the codec on Microsoft Windows brand operating systems.

      again though this is no more of an issue then it would be for people trying to switch to Linux.

      Yet still an issue.

      if they're using an iPod they're almost definitely using iTunes aswell, which of course handles AAC, MP3, and I believe possibly WMA aswell.

      But how well would iTunes software run under a workalike operating system? It fails in Wine.

      I don't think there's anything in copyright law that demands you to own Microsoft Windows in order to run Microsoft Office?

      Maybe not copyright law but contract law. The "supplemental EULA" for at least Internet Explorer and Windows Media Player require a valid Windows EULA; see IE Supplemental EULA. The EULA for Office 2003 doesn't appear to have such a restriction, but doesn't it depend on product activation, which has its own EULA and emulator-detection capability?

      And again this then begs the issue of what would Linux do any better in this unique situation?

      I didn't say it could. People demand familiarity, and Windows provides familiarity.

  127. copyrights by falconwolf · · Score: 1

    I live in the US. Our Constitution specifically mentions copyright as a specifically granted limited-time monopoly with legal enforcement. Our guiding philosophy also acknowledges the presence of certain (and unexhaustively enumerated) natural rights. I take this to mean that copyright is not a natural right.

    Your political jurisdiction and views may differ.

    I live in the USA too, and you're right. Copyrights aren't a natural right. It is a right, along with patents, granted by the Constitution to encourage progress in the arts and sciences. However congress has gone way past the point of encouraging progress by making the duration of copyrights last longer than the creater lives. If you want to encourage progress then you want creaters to continue creating, and one of the best ways is financial so you want copyrights to last a short period to encourage more creativity. Once a person creates a blockbuster, admittedly not many people do, they don't have much reason to create more.

    Falcon
  128. Re:Can anybody share why they do or do not prefer. by laffer1 · · Score: 1

    Apple has contributed code back to the FreeBSD project. There are a few portions of darwin that were released under BSD license, etc. I'll agree there are many interesting bits under more restrictive licenses. Besides, OS X is just a continuation of NEXTSTEP anyway. Your 80s comment covered it already.

    I don't know if I agree with your comment about bleeding either. Many BSD developers work on several projects. For instance, Oliver Fromme (sp?) recently proposed a patch for FreeBSD's init to allow chroot for use with Live CDs, etc. He also has worked with DragonFly.

    There are also people who tried to join a project, but were pushed aside or treated unkindly. Most BSD forks start with conflict or a disagreement with direction. Isn't that one of the benefits of open source? You can explore different directions?

  129. ease of installing Linux by falconwolf · · Score: 1

    My mom can install Windows XP on a computer all by herself (Step 1: Insert OS CD, keep clicking next / yes / ok. Pick your time zone. Continue clicking next / yes / ok. Be sure to remove the CD when it tells you to. Step 2: Insert MoBo CD. Keep clicking next / yes / ok. Remove CD. Step 3: Insert Video Card CD. Keep clicking next / yes / ok. Remove CD. DONE!) I don't expect *nix to be THAT easy, but it would be nice to be confident that without having a secondary PC available, a given Linux can be installed on a 1 year old or less PC in less than 10 utterances of WTF, SOAB, or MFPOS.

    I haven't tried to in several years but from I've heard some Linux distros are as easy to install as Windows. I may find out soon, I got a new PC and I've been thinking of setting it as a multiboot PC, currently it runs Linspire Linux but I'd like to try Ubuntu and maybe Kubuntu as well as gentoo and one or two more distros.

    Falcon
  130. Free Software Stack by Anonymous Coward · · Score: 0

    OS - Linux - OpenSolaris
    JSP - Tomcat
    DB - Postgres - Similar to Oracle, so if an upgrade is necessary you do have the Oracle Option.
    Email Server - Sendmail - QMail - Postfix
    IDE: Netbeans
    Testing in a virtual environment: VMWare Workstation - Parallels
    - Apple uses Postfix

  131. Re:Can anybody share why they do or do not prefer. by synthespian · · Score: 1

    Oh, knock it off. The problem with the GPL is that it's prone to proprietary dual-licensing schemes.
    To contribute to a large GPLed project, it's required that you agree to legal documents whereupon you promise to give away your copyright to the project.
    They then can dual-license it, or sell per-seat licenses, get rich, while you sit in a corner and suck your thumb, living in your mother's basement, coding for free.
    At least with the BSD license, the code is yours, wherever and whenever you want it, be it in a community situation or a corporate setting. Hence, "freedom for coders." Your motivation to contribute to a code base should not be a "moral imperative", but a technical decision. I'll leave morality to religious zealots or for fans of personality cults that choose their leader's definition of "freedom."
    Some coders just happen to think it's to their advantage they can use code that can be made into a proprietary fork. Besides, what is the point of having patches, in Linux, for a lot of shit you don't even have, and will never have? About one or two years ago, major commercial Linux distros were complaining that the kernel was too big.

    Fact: the majority of open source project out there with "massive" adoption _do_ _not_ license under GPL or GPL-like terms. They are more like the BSD license. Even Google and Intel release BSDed code. Get real. The FSF religion is in the minority.

    In fact, small ISVs probably do not want to develop for Linux, due to "GPL virus fear." I know some like that. Besides, Linux is a PITA, anyways. Too bad there's a lot of hype behind this thing now, instead of BSDs.

    Linux is backed up by corporations that work on the same hardware. Consider that Apple, for instance, uses BSD code, because they have exclusive hardware and are not on the same competition niche as vanilla-hardware manufacturers. So, case in point, there is no "highl moral ground" explanation as to why IBM supports the GPL. They just commoditize their complements, as Joel Spolsky wrote.

    --
    Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  132. which Linux distro should be recommended? by falconwolf · · Score: 1

    I would hate to get a call from someone who doesn't know what they're doing trying to set up Gentoo, but I don't know that I'd recommend Ubuntu or openSUSE because of the lack of effective package management when they're trying to get a new application running.

    Have you checked out Linspire Linux? I don't know how well installation of it goes, my new PC came with it preinstalled, but Linspire maintains a warehouse of software that only requires a click to download and install. As long as you've got a broadband collection it's easier to install software in Linspire than in Windows.

    Falcon
  133. Well, there are a few but essential reasons... by rtssmkn · · Score: 1

    to this:

    less stress, semi-freedom of choice, higher availability, less crashes, higher productivity, increased to the max usability, what more *your suggestions*?

    but first of all: it is non M.

  134. Re:And that is why Linux beat BSD. The GPL prevent by the+phantom · · Score: 1

    .* <-- the joke
    .o
    \|/
    .| <-- you
    / \
    Lameness filter! Probably because it is lame!
  135. Re:Can anybody share why they do or do not prefer. by doom · · Score: 1
    The problem with the GPL is that it's prone to proprietary dual-licensing schemes.

    A point perhaps -- and this may be a bug in the GPL -- but it's somewhat muted in the case of distributed ownership of copyright, as is the case of the Linux kernel. The copyright owners can't play games with you, because it's nearly impossible to even find all of them.

    To contribute to a large GPLed project, it's required that you agree to legal documents whereupon you promise to give away your copyright to the project.

    The FSF does things that way, it is true, but (1) I'm not worried about FSF corruption scenarios any time soon and (2) unlike nearly every other group out there, the FSF actually employs lawyers, so I'm inclined to cut them some slack if they tell me they need this for legal reasons.

    If the Linux guys are demanding this now, that's a new one on me.

    They then can dual-license it, or sell per-seat licenses, get rich, while you sit in a corner and suck your thumb, living in your mother's basement, coding for free.

    And how is this case any different from the BSD case? In the GPL case, if you don't like what the copyright holder is doing you can fork it and maintain a GPL version...

    At least with the BSD license, the code is yours, wherever and whenever you want it, be it in a community situation or a corporate setting. Hence, "freedom for coders."

    I disagree. What this really does do is encourage people to indulge in dreams of avarice, forking off the BSD version, adding some bells and whistles, and selling their proprietary version for a gazillion dollars. This is (a) largely a pipe dream, these days (b) likely to be a screw-the-coder scenario. The original authors don't often get a cut of the pie... unless they start pushing their own proprietary versions...

    Your motivation to contribute to a code base should not be a "moral imperative", but a technical decision.

    My motivation should be whatever I want it to be.

    I'll leave morality to religious zealots or for fans of personality cults that choose their leader's definition of "freedom."

    Note to self: don't take anyone seriously who uses the word "zealot". They can't see past the end of their nose.

  136. Windows distros by falconwolf · · Score: 1

    And there are several popular distros to develop and test for to make sure installation is smooth and seamless like in Windows. Windows is a single distro and extremely predictable in that regard.

    There hasn't been one Windows distro for years, and now with Vista there are even more. I lost track, but isn't there 4 or 5 versions of Vista?

    Once a real and effective standard is settled upon in Linux (api, distro, installation and package maintenance mechanism) I suspect Linux would be much more popular on the layman's desktop.

    And a lot less popular on geeks', power users', and developers' desktop. Once this happens less people will work on or develop for linux. Linux lets it's users setup their PCs the way they want, if it no longer does then they will use something else that will.

    Falcon
    1. Re:Windows distros by steelcobra · · Score: 1

      The difference is that the different retail boxes are all interchangable, with the difference being the feature sets, not what will run on it. You can take XP Home and run nearly anything (aside from domain-dependant software)you could on XP Pro. Without recompiling the binary for your particular version and hoping for the best.

  137. Answers to all your questions by WK1 · · Score: 0
    We have been hearing promising predictions like 'This year will be the year of Linux on the desktop' for the last decade.

    Yes, but the media says lots of stuff like that. We have also been hearing that the world is going to end this year, or in a few years, for thousands of years. People say stuff. Unless there is a radical change, we will continue hearing all of this stuff for a long time. Just try to ignore it.

    Clearly, if Linux is unable to reproduce a third of Firefox's end user uptake over a much longer time-frame, there are deficiencies with the direction the GNU/Linux/X/Gnome/KDE system has taken.

    Don't say "clearly" when referring to a speculation. You have a theory that answers a question. I have a different theory. I think the reason that Linux is not so popular is because Linux is not installed by default. Firefox, also, is not installed by default, but Firefox is much easier to install. There are bugs and problems with GNU / Linux / X / Gnome / KDE / etc, but there are bugs and problems with most software, even Windows. I think the general public would be happier with Linux if it suddenly and magically replaced Windows on all OEM computers. But that's probably not going to happen soon, so we can only speculate.

    Other free-desktop operating system projects which take different and innovative approaches like ReactOS, AROS, Mona and Syllable remain comparatively starved of developers and interest.

    I never heard of those. Perhaps I'm not as geeky as others. I've been using Linux for the past year, and am happy with it. Part of the reason I chose Linux rather than looking at a bunch of free solutions is that I had heard of Linux, and knew that the user and developer bases were strong and solid. So, maybe people ignore those OSes because other people ignore those OSes? Kind of like saying AROS is to Linux as Linux is to Windows?

    An often cited reason for using a non-Microsoft OS is to avoid a monoculture, but free-desktop efforts have created a total monoculture around developing and promoting Linux...

    Yeah. There are pros and cons to monocultures. On the the con side, it leads to less choice for users, and inappropriate solutions for developers. It leads to webmasters and developers only writing for one platform, which can be especially a nuisance if that platform is buggy.

    On the plus side, a monoculture, or in this case, a limited culture, consolidates users and developers. Developers can concentrate on just a few OSes, rather than hundreds. Do you know of any AROS user groups? It's easier to find help on the internet for something that more people use.

  138. You mean you have to ask this question? by edunbar93 · · Score: 1

    I mean really, you practically answered it yourself.

    As big as it is, Linux is too small a community and userbase to ever usurp Windows on the desktop. So you ask why even *smaller* projects can't do it either?

    The fact of the matter is that any desktop OS is in the unenviable catch-22 of "noone uses our OS because there's not enough software, and there's not enough developers making software because noone uses it."

    --
    "No problem. I have the capacity to do infinite work so long as you don't mind that my quality approaches zero."-Dilbert
  139. I'll say. by Grendel+Drago · · Score: 1

    I've run into some odd problems running Linux software under Cygwin. Nothing insurmountable; the developers just hadn't tried it under that platform. In general, the fixes were pretty straightforward, standards-compliance sorts of things.

    It supposedly also runs as part of Sun's Java Desktop System, under Cygwin (which is kind of Linuxy, I suppose), and under a large variety of Unix-like systems. Supposedly. If people were actually using it, there would be portability bug reports, right?

    --
    Laws do not persuade just because they threaten. --Seneca
  140. Because consumers do what consumers do ....... by HW_Hack · · Score: 1

    Using the old Betamax example - when consumers (even businesses) are faced with a decision where added cost or complexity or having to wait - competes with a technology that is "good enough" or "works well enough to get the job done" and that technology is readily available ....... the answer is a no-brainer (literally). If its good enough and works most of the time its a done deal - hence MS on the desktop.

    The consumer (i.e. a non-geek) will make the simple decision every time.

    I know longer think about Linux torpedoing MS - I use Linux because its superior for both my home computing and for servers at work. I also use Macs, and when I have to I use Xpeeee.

    Now if Linux was as mature as it is now when Win95 came out .... you might have a horse race

    --
    Its not the years, its the mileage .....
  141. So you really can't tell the difference. by Grendel+Drago · · Score: 1

    So... you can't tell the difference between criticizing current copyright terms, decrying the rise of grotesquely grabby DRM software and bitching about incredibly harsh penalties for minor copyright infringements, and the pirate-worshipping strawman you've set up there? Man, it must suck to be you.

    --
    Laws do not persuade just because they threaten. --Seneca
  142. Firefox and GNU/Linux switch... by silkenphoenixx · · Score: 1

    It should be noted that it is far easier for the average home / work user to use Firefox instead of IE than it is for said user to switch completely to a Free Software operating system such as GNU/Linux or BSD.

  143. Re:I not anymore a Linux User by denisbergeron · · Score: 1

    This article speak about Linux, the fact that I use Windows or Mac is irrelevant, but indeed I am thinking about switching to the Mac, but the Photoshop license are not transferable.

    --
    Ceci n'est pas une Signature !
  144. Re:I not anymore a Linux User by denisbergeron · · Score: 1

    I not unix admin anymore, I don't say I need office, I use OpenOffice to write tps report and stack them under my red stapler.
    Photoshop, because I love taking picture of my vacantion (http://denis.b.bergeron.googlepages.com/) and that why I need photoshop. I prefert gimp, because I know it better, but it doesn't support raw files and 32 bits images.

    --
    Ceci n'est pas une Signature !
  145. Re:I not anymore a Linux User by denisbergeron · · Score: 1

    The parent are not a flamebait, hum some a$$h*le receive mod point !

    --
    Ceci n'est pas une Signature !
  146. Re:I not anymore a Linux User by denisbergeron · · Score: 1

    Hum flamebait and Redundant, this site is loaded woth a$$h*le with mod point who don't know what is a flamebait!
    For the Redundant point, hum I was the 18th post, when I post an no one speak about this probleme what did Redundant mean !

    --
    Ceci n'est pas une Signature !
  147. Re:Can anybody share why they do or do not prefer. by kv9 · · Score: 1

    did Netcraft confirm this?

  148. Why do you beat your mother? by WindShadow · · Score: 1
    Like the legendary why do you beat your mother? question, there is an assumption in the question. In this case the assumption that any other O/S has a realistic chance of pushing Windows off the desktop in significant numbers. In truth, if the widely known Mac interface hasn't done it in a decade longer than Linux has existed, it's not going to be a revolution, but an evolution.

    Why people like an O/S is somewhat like a discussion of the technical merits of blonds vs. redheads. I like the better user interface of Linux, with realistic choices for both GUI and a command line interface where that makes sense. People develop free software for attaboys, not money, and frankly how many will you get if you write for one of the O/S variants even geeks don't recognize?

    People write desktop for Linux because it's the only viable open source alternative to Windows at the moment, and as a fringe benefit the Mac folks can use most applications as well.

  149. Be serious. by Generic+Player · · Score: 1

    Wine as it exists today smart ass, not a version from 1999 that can't run any windows software at all.

    1. Re:Be serious. by kv9 · · Score: 1

      you should have been more specific

    2. Re:Be serious. by Generic+Player · · Score: 1

      Yes, I shouldn't be assuming anyone on slashdot has common sense, my bad.

    3. Re:Be serious. by kv9 · · Score: 1

      you're new here, aren't you?

  150. Yes, I am counting drivers on the bundled CD by tepples · · Score: 1

    Preinstalled or counting manufacturer drivers is a different story, of course.

    Yes, I am counting manufacturer drivers. Many (but not all) people using Linux or *BSD would be willing to install proprietary drivers from the CD bundled with the device, if such drivers weren't entirely ENOENT. Why can't I find a single NIC or scanner with a drawing of a penguin in the corner of the box?

  151. Super by CopaceticOpus · · Score: 1

    Hey, this is a great idea... since all the open source desktop developers have yet to make one truly compelling desktop environment, let's just splinter the group and get them working on several unrelated projects. That ought to speed things up.

    Linux has critical mass and is the most mature open source OS. Let's get it to the point where it's on 50% of new PC's, then maybe we can start toying with other ideas.

  152. My thoughts by nyghtraven · · Score: 1

    Personally I think Linux has a good chance of taking on Windows even more so than Mac, but a few things have to get doen first. 1. These developers need to realize that most people do not care to do any compiling or anything else special to install a package and go. There needs to be something that will do this for the person so that only an executable is used. 2. One unified desktop, or at least one that runs programs for any of the major ones and is completly transparent to the user. 3. Absolutly no CLI. GUI apps need to be made that are nice looking and feature filled, and do not require a user to run a CLI to do anything they normally do. 4. Honestly, a better bootup screen would help as well. And faster.. much faster. Linux takes a long time to start up compared to windows or QNX. But it needs a more professional look to it at the boot screen as well. 5. Good advertising. Linux doesnt really have any advertising. MS advertises, even on TV. Their name is know. Linux companies need todo the same or there isnt a chance in hell of Linux going far because few will know much about it. Those that do know have it in their head it is hard and a geek OS. That image needs to change.

  153. Why? by eric_ykchan · · Score: 1

    I don't know anybody using open-source OS other than Linux? Why should you bother to ask people to work other open-source OS that almost nobody uses?