Advanced

Desktop Linux: The Final Hurdles

Posted by tadelste on · 12 comments
lxer.com; By Tom Adelstein
Mail this story
Print this story

Desktop Linux is almost soup. We only have a few items left on the short list. Will we do it? If history is an indicator, the answer is yes.

I remember the major turning point that took Linux from an OS that Microsoft used to call competition during their anti-trust case to a serious commercial operating system. At the time, Linux users numbered two million and Microsoft users numbered 300 million. I used to say Linux makes more news than anything else and I owned a Linux company.



In April 1999, D.H. Brown Associates, Inc. published a report called Linux: How Good Is It? Hardly any archives exist today mentioning that story with the possible exception of this C/Net News article.



The study dinged Linux for lacking features needed to make it a serious consideration as an operating system. The report said that Linux was good for file and print servers, Web servers, some scientific computing, and thin client computers. But, the DH Brown report said Linux lacked support for computers with multiple processors; failover and a "journaling" file system needed to reboot a crashed machine without having to reconstruct the system files.



I attended a briefing on the report by Linux International and learned that the kernel developers started addressing the issues before the report's official release. As we know now, the open source community responded rapidly and the Linux server has taken a commanding share of the server market. The DH Brown report became the Linux server roadmap placing it among elite operating systems.



What About the Desktop?



The Linux Desktop sits at the foothills of success. I have walked in the trenches in numerous market sectors and would like to report what Linux needs to become a serious competitor to Microsoft. Like D.H. Brown, I don't intend to pull any punches. Linux is a very good desktop but it cannot play seriously in the market until Linux companies take customer feedback seriously.



Large and small organizations want a Linux desktop. Many face the expiration of their Microsoft Software Assurance contracts and do not want to renew them. The value proposition of Linux is compelling. The platform requires less administration, fewer support personnel and offers unmatched security.



You cannot fault corporate customers for failing to try the Linux desktop. If you could see the lists of pilots of which I am aware, you might fall out of your chair. If Bill Gates saw this list, he might consider offering a Linux desktop. But, the companies trying Linux do not want to alert Mr. Gates for fear of reprisals –audits by the Business Software Alliance.



Two complaints seem universal: Some Linux Desktops come ready to use out of the box but fail in their due diligence. The others pass due diligence but do not come ready to use out of the box.



Corporate Requirements



In the fall of 2001, I received a call from an IBM reseller working with one of largest investment banks on Wall Street. During the 9/11 tragedy, the company lost its email capability and could not restore its mail on its Microsoft Exchange servers. As a consequence, the company faced stiff penalties from its regulators.



IBM had made my firm a Business Partner for porting a replacement for Microsoft Exchange to Linux on the S/390 mainframe. The product worked and generated IBM's first domestic Linux reference account, Winnebago Industries.



The IBM reseller handed me a list of requirements that included a deeper level of interoperability for shared calendars. Other than that, the customer had tried our server, liked it and only wanted a little more functionality. We made changes to the product and met the requirement. But it didn't end there.



If you follow the sequence of events following our meeting the requirements, they can reveal the nature of meeting widespread corporate needs. Between the IBM reseller and my Linux firm we satisfied the requirements the investment bank: The ability to restore mail during a catastrophic event and their need for robust meeting management. According to our contract and the criteria for success, we should have won the business and started deploying the solution. The customer, however, wanted more. They wanted a transparent solution so their administrators wouldn't know the difference.



We followed change after change in requirements for approximately nine months and the customer refused to pay us anything. They said they were helping us make a better product. Additionally, the customer demanded that we meet the changes or lose the business. Try servicing a zillion dollar investment bank with all your developers while you attempt to live off revenue.



As a member of the board of directors, the COO and director of development, I put my foot down after we met the first requirements. I said, drop the account and service our existing base. I was out voted and eventually left nine months later when the customer finally said that the product wasn't good enough (which was untrue). After I left, the customer came back and drug the party out another six months then decided to outsource its mail services to IBM Global Services.



Here's the lesson: If it doesn't work out of the box, you won't win the business. The product has to meet the corporate need. That also means, know the customer need when you come out with a product.



Linux Corporate Desktop Needs



The Linux desktop firms have done hundreds of corporate pilots for big organizations. At the same time organizations have done hundreds of pilots about which the Linux desktop firms know nothing. Here's one example of a failed pilot. A Fortune 100 company decided they wanted to go with Linux. They assembled a project team and went out and did everything they could to analyze the market and see if the desktop would work.



Ultimately, they found the product they wanted. But the company offering the product could not pass vendor requirements. Now, the desktop effort continues but they want the product to work out of the box and they want a significant supplier.



I won't divulge the company, but I will combine their needs with those of similar organizations and provide a list of functionality. Here's a short list:



  • 1.Windows Network Neighborhood visibility and UNIX/Linux visibility in the same panel.
  • 2.Active Directory password management which includes single sign-on and password expiration policies.
  • 3.Interoperability with Exchange 5.5 and Exchange 2000.
  • 4.Font compatibility with Microsoft Office and Openoffice.org and/or StarOffice.
  • 5.Windows Terminal Server clients using RDP out of the box for home grown applications and special Windows applications.
  • 6.Ability to click on a file in a Windows or Samba share and initiate the associated application.
  • 7.Device management for hardware compatibility.
  • 8. Compatible Windows Media player Codecs.


  • That's the short list, here's the strategic list:



    Small-Office / Home-Office Networking



    One difficulty with Linux out of the box is setting up a small network. Many Linux users want to set up small networks that allow them to share printers, scanners, files, Internet connections and bring up a remote desktop without having to move to a different machine. A current trend includes having the ability to use a laptop or portable computer and move comfortably around an office or home with wireless connectivity. This is a plug and play small network requirement.



    When small business workgroups buy PC's they tend to purchase a few name brand PCs and wire them together perhaps with a number of existing Windows machines; they then plug in a networked printer, possibly a scanner too, and they're done. Absent such simple peer-to-peer facilities, Linux can hope for practically no capture of this important market segment.



    A small-business networking solution would permit Linux boxes to be networked together without a server and in short order make the system relevant to a large number of users. The SO/HO segment does not appear to have been originally specified as a Linux target; however, it's a large, fast-growing and important segment in itself and for its indirect upstream influences on the main target enterprise segments.



    This is a market segment that Microsoft serves effectively and which helped that company as it moved into prominence in the late 1980's and early 1990's. Any system seeking to gain market share needs to address the basic requirements of the Small Office / Home Office demographic.



    Printing



    The Linux printing system works poorly and requires seasoned system administrators to set it up and maintain it. It does not work with all applications. Problems exist when printing from a browser, a wine application or when trying to share a printer.



    Laptop Support

    Broader WiFi card support needs to be introduced to Linux. WiFi card support for the large and important group of laptop users hardly exists. The expedient solution here would to use something like Linuxant's DriverLoader which has the elegance of being a single point solution that's applicable to the great majority of user/device scenarios.



    Device Compatibility



    Linux would benefit from the equivalent of Microsoft Windows Device Manager. This will provide a visual display of all hardware devices in the Linux PC and show the user which devices work and which need a module to be configured.



    We suggest for unsupported devices in device manager that the user be enabled to download a driver by simply pointing and clicking on the respective device as it is listed in the device manager. Alternatively the system could provide a message that a request has been made for the device driver, with instruction on how to follow up that request in the future.



    Uniformity of Different Distributions



    A place exists for distributions that have no interest in the commercial market. I use one of those distributions, Debian to test, learn and enjoy pure Linux. I use commercial Linux distributions for production purposes.



    If the major Linux desktop companies plan to succeed in their endeavors, they will have to learn to work together or die. Sun Microsystems just learned that they will have to delay project Janus.

    Project Janus is Sun's initiative which allows Linux applications to run on Solaris unmodified. The project team discovered that Linux software has differing dependencies built-in depending on which distribution the software is built. Each software program requires separate development work for each version.



    Corporate desktop buyers won't put up with this craziness. They don't want to maintain full time staffs of developers to modify software. If they did, they might as well go back to using IBM Mainframes. Except for the hassle of programming staffs, they're less expensive today that hordes of PCs.



    Hurry Up



    The Window will close in the not too distant future on the Linux desktop – no pun intended. The Linux desktop could fail if companies continue to pilot programs and conclude that it's less trouble to buy Microsoft. Everyone loses in that scenario.



    The Linux Desktop Future



    I won't use Microsoft. But, then people will soon say that I wrote the book on Essential Linux System Administration. For me and lots of others, Linux will continue as our desktop of choice.



    The Linux desktop could grab major market share if the desktop companies do what the server companies did after the D.H. Brown report in 1999. If they don't make Linux a commercial competitor, then we will continue to maintain about six percent market share and a great opportunity will go by.



    We will know, because the next major releases of the Linux desktop should hit at the end of the first quarter of 2005. In the mean time, some Linux desktops should sell between now and then. But who will buy them?

      Nav
    » Read more about: Story Type: LXer Features; Groups: Linspire, Microsoft, Novell, Sun, Ximian

    » Get new stories by e-mail: nightly or as they are published

    « Return to the newswire homepage

      Related stories
    » More like this

    Comments (12)

    Here's the lesson?

    "If it doesn't work out of the box, you won't win the business. The product has to meet the corporate need. That also means, know the customer need when you come out with a product."

    I can't think of any product that a large organisation would use that works out of the box. Everything requires some configuration and tweaking. Working around that problem involves managing your customers' needs.

    I think you raised a couple of valid areas where Linux could improve, but I'm not sure about that terminal services point. Not only is that functionality built-in to the X Window System, but there's also rdesktop, an open source RDP client, if you need connectivity to a Windows-flavoured server. Both of these work fine out of the box with most distributions.

    A lot of your points tend to point (quite accurately) at the fact that Linux isn't Windows (imperfect A/D, Exchange and MS Browsing integration). It's a pity that people are so determined to stay in a rut though. It is possible to have both platforms sharing the same network space and offering similar or the same services. This is mainly due to concessions made on the Linux side.

    You're right though. Having manufacturers starting to provide drivers is a necessity. It'll mean organisations don't have to be selective about the hardware they buy.
    mgeddes:

    Hey, thanks for your post.

    I really love Linux. I liked it the way it was in 1996 when we used it on a DEC multia as a firewall and I liked it when Looking Glass was Caldera's desktop. I liked it when I had to configure X on slackware after I installed the packages I wanted.

    I worked with a lot of distributions and some work with me. If I take functionality from Xandros and put it in JDS and then kick in a couple of utilities here and there - you have a desktop that would fit into a corporate environment or at home like a glove. In fact, you wouldn't need Windows at all. You could just leave the windows server environment in place and put JDS on the network and that's that.

    The people who post long diatribes [about how I don't know what I'm talking about] don't touch the customers with whom I work. They couldn't get in the front door much less consult with the CIO and technical people. And I can go talk to engineers at certain Linux distribution makers and discuss changes and get a lot done. I don't say that out of arrogance - it's just what's so. I also have consulted with and worked for some of the Big 5 PC makers about Linux strategies.

    Here's the point. We are really there. I'm saying that in March, you will see a Linux desktop that's interchangeable with anything Windows can put up. Then, you'll see a couple of product additions in April and May that will complete the desktop.

    It's Linux and it doesn't have any Microsoft stuff that Sun supposedly got. In fact, the Microsoft deal has turned out like a slow boat to China.

    So what I'm saying is very simple - if the distributions don't get with it one will emerge. It wouldn't be Novell or Mandrake. I don't think Red Hat will be ready in time. It will be a bunch of silly BSD guys from the 1980's that do it.

    How do I know? Eyes seen it eh.

    The Final Hurdles ????

    I disagree with you saying "The final hurdles". I use linux at the house (and I like it), but not at the office, and I don't see any near future where I will. I do not see a short list of things that needs to done. I see a long long list. The biggest item on my list is lack of Windows Compatible programs. There is Openoffice.org which work with MS Office, but that's about it. Lets face facts most companies use Windows. If get an e-mail attachment form a client It's going to from a Windows program. Which may be a AutoCAD drawing, MS Project file, or an Access database in which finding a Linux program to open these type files is a nightmare. There also seems to be a lack of companies willing to work on these short comings. I may be wrong but I had heard there are now more linux users than Mac users, but still I can find more Mac programs than Linux programs. Another short coming of Linux is hardware, when buying new hardware for Windows computer you do have to look on the side of box to see if It will work with Windows. It does. Printers are the worsts, not far behind is wireless networking cards. Yet another gripe it is there is no unity in Linux. Kde is getting there. Many people complained when Microsoft strong armed Companies to use there common .lib's and .dll's, but is nice to the same common dialog box on every Windows program. A bigger part of product is it's look and feel. People don't buy hummers because they are good on gas. They look cool and there is hype behind them. Linux needs to look better, and have unity. Every program in linux should have "crl+c" as copy for example. The last thing I really think has been a mistake with Linux is not trying harder to make a personal desktop sooner. Most people I know learn the computer skills at home, and playing on the inter-net at there house before landing the job that lets them play at work. Ok, so lets now that young man or woman who has worked with Windows in there home is now starting a business there not going to jump ship. I do hope I'm wrong about most of the above because I like Linux, I just think it needs more work.
    You're wrong about most of the above. :p No really, some of the points you make I agree with, Linux is a work in progress. I do think some standardization is definitely a good thing, but all things in moderation. Too much standardization stifles creativity IMHO. Forcing a user to only use Gnome rather than giving them the choice between Gnome and KDE for instance is too much standardization for me. In a business world I can see the advantage, but I'm not a business Linux user.
    techieMoe Wrote: In a business world I can see the advantage, but I'm not a business Linux user.

    JasonBrooks: I agree. That is why the 2nd line in my first post was ... I use linux at the house (and I like it), but not at the office,
    I use CrossOver Office with Office Prof (2K, XP)... No problems with Word/Excel/PP/Access. I've used bricscad (beta) for Autocad ([url=http://www.bricscad.com/news/BricsCad goes Linux English.htm]http://www.bricscad.com/news/BricsCad goes Linux English.htm[/url])

    With regards to hardware, do your research before you buy. It's pretty easy to get good printers, wireless, etc for Linux.

    We have 25 users using Linux as their primary desktop at our office.
    I have not tried CrossOver Office, but I tried bricscad. It's not very good. I have alot of problems with zooming on drawing with a good bit of detail. It would work better if they did a port to Linux instead of using Wine. Still though these are all programs that are made for Windows. Does Execl VBA Macro work in CrossOver Office? Regards of you statement about the hardware you said a alot when saying "do your research before you buy". That's my point. With Windows there is not researching, Companies like Novell, RedHat, and others need to pressuring hardware manufactures to for Linux compatibly. I would like know how many Windows computer your company has and how offen you use them.
    Ugghhh... Red Hat, Novell, etc. do not "pressure" hardware manufacturers. If people would change their buying habits and communicate to the vendors, then they'll change. For example, if we could train the Microsoft shops to buy with an eye towards Linux compatibility, then things might change... regardless of whether they run Linux or not.

    In all fairness, there has been a dramatic increase in the number of vendors including a Tux logo on their products to indicate Linux compatibility. I think this trend will continue. Also, now that you can order from the major players (Dell, HP, IBM and even Sun) hardware that will work with Linux, this too will help bring more players to the space.

    Briscad is considering the possibility of doing a native port: "In a first phase the software will run in the WINE environment, enabling a quick availability on a fast growing market."
    Oh... and I haven't had any problems with Excel macros.. but YMMV. I don't create too many spreadsheets, but have received many with macros and they have worked fine.
    "With Windows there is not researching," - that's really sad. So many Windows drivers and applications clash amongst themselves and with each other, even under XP where "DLL Hell has been cured". XP SP2 broke a lot of applications, and a lot of drivers. Unlike Linux, you can't just patch around the problem on the spot and get everyone your site going again, you have to wait weeks/months/forever for some unhappy Korean wage slave to get around to fixing it instead. If they still support the device at all. And then Microsoft break it again with the next patch-set. Or you can revert XP2 - maybe - and get splattered when the next virus beats the signature update to your mail server. The way to get better Linux applications is to start using it at the office. Put BricsCAD/IntelliCAD on a PC which isn't your main desktop and tell BricsCAD how it went. Then ask them how far away a native version is. Do this with each new release. The squeaky wheel gets the grease.

    Regarding to printers.

    I really don't think you've tried to use CUPS yet?

    1) Install 2) Point browser at http://localhost:631/ 3) Configure

    max 5 minutes.

    Now it's even shared to other cups installations that dont have a localprinter, without doing anything..

    I've had quite a lot more trouble making printers work under Windows.
    jesper:

    I use CUPS as my own printing system. It's really nice. Windows 2000 even supports Internet Printing Protocol.

    It's not workable in a Microsoft network if the architects don't put it up. In that case samba needs to be automated to browse and configure itself without having to log out, etc. and use the Win 32 printers.

    If the infrastructure is Linux, then cups is fine. You just won't find medium to large size companies running a Linux infrastructure. The Chicago Mercantile is migrating to one. That doesn't solve the problem of "Desktop" Linux acceptance.

    Great try!

    Post a comment

    A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

    Your message:
    |||||
    10
    Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

    Sign up and post (it is free)  or  Log in and post