Tag Archive for 'gnulinux'

Choice is Good

I read this nonsense recently:
It’s no wonder that the Linux desktop operating system is not attracting hoards of new users from Microsoft Windows and the Mac OS X platforms. Linux has almost too many desktop choices.

Uh… Are people buying fewer cars, eggs, flowers, candy-bars etc. because there are too many choices? Nope. They just spend more time shopping… It’s fun. If you happen not to like shopping, just buy what others buy or what’s prominent on the shelves.

GNU/Linux distros offer a lot of choice. Most of them don’t amount to much but if you pick any of the top ten in DistroWatch’s hit list, you will have a fine experience. Distrowatch exists partly to show users what choices there are and to make comparisons. Most newbies will not be particularly interested in features but will want ease of installation and use. Go for it. Choice is good.

I recommend Debian GNU/Linux because it works for you and me and not M$. It’s a cooperative product of the world with software from many thousands of contributors and a dedicated team of Debian developers who package software to make it easy to manage.

- Robert Pogson

2009 May be the Year of Thin Clients, Too

I have already confirmed that 2009 is the year of GNU/Linux. It looks like its the year of the Thin Client, too. My dataset:

  • five of the top ten most popular whitepapers on desktop+OS on ZDnet are about thin clients
  • virtualization has reached a crescendo with thin clients being one of the major modes. India and Indonesia seem to be hotbeds.
  • while production of thin clients is only 2% of desktops, the long life makes them about 10% of PCs and the production is growing rapidly
  • IDC sees thin clients riding the wave of virtualization
  • thin clients are green
  • netbooks are forking with some OEMs trying to force more feature-bloat and higher prices but many smaller OEMs are cranking out GNU/Linux netbooks at ever lower prices. Thin clients should cost less than netbooks so the $700 thin client is on short time. If thin clients cost less they will sell faster.
- Robert Pogson

Inversion

I woke up this morning and realized I had created an inversion. No, not a condition of the weather likely to result in a storm, or an inverted population of excited atome likely to lase, but an inverted population of students, users of PCs.

You see, in this school there are two labs.

For higher forms of life:

  • five year old PCs with XP sp3, 1 gB, 1.9 gHz CPU
  • boot time 2 minutes

For lower forms of life:

  • ten year old PCs with XP sp3, 384 MB, 330-850 MHz CPU
  • boot time 3 minutes

It is the natural order of things that the lower forms of life are the bottom feeders, living off what filters down from above.

The lab for the lower forms of life was a disaster. Every time I visited it, I would take 20 minutes putting cables back in place because students believed their “mouse was not working” because XP froze or was too busy to pay attention to them. Of course, XP put virus scanning as a higher priority and 2003 would put in random waits just for fun.

The lab upstairs works marginally. Power supply failures are its main problem.

The inversion? Now, the PCs in the lab downstairs run as thin clients and applications run on a newer PC, also 5 years old, but running Debian Lenny GNU/Linux on an AMD64 3000 with 1.8 gHz clock, 2 gB RAM, gigabit/s NICs and RAID on larger hard drives… So, the lab downstairs now

  • boots in 60s with login in 5s (POST takes 15s!)
  • applications load in 2s
  • has 24 machines instead of 22 because I was able to install tiny drive in a few more failed machines. The drives are used for the bootloaders.
  • is several times faster than the lab upstairs

I took a walk around the old lab while writing this. One machine would not boot because of a loose ethernet jack and one had a mouse failure, leaving 22 machines fully functional when they were down to 17 or so on many days in the past. The lab is much more solid as well as being fast. Vista or 7 does not work here. GNU/Linux does. 87 users think so.

On top of the performance, we have iTalc for the teacher to control the lab. Not all the features work, but the teacher can demonstrate and monitor very well. I can give the teacher a button to shut the lab down. Locking the machines already works.

So, there is an inversion. The natural way of things is turned upside down. The lower forms of life have better IT. Thank you, LTSP.org, GNU/Linux and Debian. What will this instability produce? I do not know, but I expect there will be some demand for newer IT to be GNU/Linux because they can see the improvement using GNU/Linux instead of that other OS. The machines in the upstairs lab will never run an upgrade from that other OS. They may run GNU/Linux or be scrapped in favour of modern tiny thin clients. That would be sweet as we run on diesel power. The power savings alone would pay for the changeover.

The cost of the upgrade to the downstairs lab was mostly in downloading software which was incredibly slow on our ISP and struggling to authenticate against AD. What a waste of time. Students would be better off with separate accounts. 2003 still has long pauses… PDC will not answer the call so the BDC responds after a timeout… arghhh! Give me simple LDAP any day.

The new server in the old lab is my old PC which I upgraded when I prepared for the conference in February. I kept my case and power supply but donated the guts which, with a new power supply, went into a failed PC from the newer lab.

- Robert Pogson

Stupidity

Resistance to change is a defensive measure we all have to prevent wasting time learning something new for the sake of change. It can go too far. It has gone too far the way many retain that other OS. You know the kind:

  • never used anything else
  • hires someone every year to re-install/delouse that other OS or pesters an acquaintance to do it for less
  • accepts the idea that computers slow down (HAHAHA!)

These behaviours are irrational acts of the lazy. They are not idiots incapable of deeper thought. They are just using poor judgment and are resistant to change. The Blog of Helios does use the “idiot” term today. I guess enough resistance to change warrants the term but I think “stupid” is more appropriate. There cannot be that many idiots in the gene pool or we would not have gotten this far as a species.

I try not to be stupid but I did use that other OS for far too long:

  • I used a dozen different architectures of hardware, some even without an operating system, just stand-alone programmes
  • I like the old days of automobiles when anyone with wrenches and screwdrivers could fix their own vehicle. I try to fix my own PC and I rarely am stopped
  • my computers do not slow down. I run GNU/Linux. It has no brakes.

I had an example of this last item in operation in my school this week. I converted a lab to use GNU/Linux by adding a 5 year old PC as a terminal server and converted the 20 PCs in the lab to thin clients. It was a struggle because of various hardware and software issues like having to edit the boot loader configuration of that other OS to preserve it (Why? Some resist change…), many hardware problems in the old equipment (Remember 4MB video cards?), but it was worth it:

  • booting of clients in 30s instead or 3 minutes
  • login takes 5s instead of a minute or so
  • the largest application opens its window in 2s

This weekend, I added four more clients. The users of that other OS, who find they have to have the latest processor just to keep the bloatware moving fast enough cannot understand how one old PC can give 24 people good performance simultaneiously but it is easy if you

  • waste no cycles doing M$’s bidding
  • do not waste cycles running malware
  • do not clog network connections with spam
  • avoid features like “roaming profiles” which suck the life out of your network

So, including a switch from that other OS, my old PCs actually speed up! Isn’t that a refreshing change? I converted ten year old clients and a five year old PC into something wonderful. Students are excited about it and the increased performance is an obvious reward for the effort of changing. Most people are not stupid. They just need a little guidance. By asking the old boxes to do less, they get it done sooner. Simple concept. It works.

I believe if you cannot describe in numbers knowledge is of an uncertain kind:

  • the clients use 48 MB of RAM to do the job now instead of 384 MB and swapping madly with XP
  • the clients use only about 20% of their CPU time when busy
  • the clients need only about 2 megabits/s of network bandwidth each so there is no bottleneck at the gigabits/switch/ NIC on the server
  • the server PC has 2 gB RAM and runs at about 50% CPU utilization on AMD64 1.8 gHz

Those used to their machines dragging with fragmented file systems and the like would appreciate a machine giving snappy performance with 2000 context switches per second. There is no bottleneck in this system except RAM is a little tight (swap reached 1.6 gB), but then I am running a LAMP stack on the same machine… Those who object that the students are not all working on 200 MB images with GIMP are being picky. Students read, write and think. This system works for them.

Want to take a tour of the lab? What have I left running?

sh-3.1$ ssh old
Last login: Fri May 8 21:20:34 2009 from beast.ahs.net
pogson@old:~$ su
Password:
old:/home/pogson# nmap -sP 192.168.0.*

Starting Nmap 4.62 ( http://nmap.org ) at 2009-05-10 09:12 CDT
Host old-o07 (192.168.0.7) appears to be up.
MAC Address: 00:0D:88:36:C0:F3 (D-Link)
Host old-o08 (192.168.0.8) appears to be up.
MAC Address: 00:0D:88:36:C3:19 (D-Link)
Host old-o12 (192.168.0.12) appears to be up.
MAC Address: 00:15:E9:B0:FD:12 (D-Link)
Host old-o15 (192.168.0.15) appears to be up.
MAC Address: 00:50:BA:AA:54:79 (D-link)
Host old-o16 (192.168.0.16) appears to be up.
MAC Address: 00:50:BA:86:5E:B5 (D-link)
Host old (192.168.0.254) appears to be up.
Nmap done: 256 IP addresses (6 hosts up) scanned in 1.697 seconds
old:/home/pogson# for f in 7 8 12 15 16;do echo $f;ssh 192.168.0.$f cat /proc/cpuinfo|grep z;done
7
cpu MHz : 451.035
cache size : 64 KB
clflush size : 32
8
cpu MHz : 863.875
cache size : 256 KB
clflush size : 32
12
cpu MHz : 451.034
cache size : 64 KB
clflush size : 32
15
cpu MHz : 451.040
cache size : 64 KB
clflush size : 32
16
cpu MHz : 601.396
cache size : 256 KB
clflush size : 32
old:/home/pogson#

There. The typical CPU is 450 MHz and the caches are 64kB. They make great thin clients and lousy clients for that other OS. Should we chuck them and pollute the planet? Should we burn less fuel by switching to modern hardware? Yes, if we use thin clients and a hot new server, the performance will be a bit better and we will use a lot less power, but this is what we have with which to work. We do the best we can and the students appreciate it.

- Robert Pogson

Change

Change is in the air in 2009.

  • 7 is being touted as a “Linux-killer” by sycophants of that other OS. This means the puppet-masters are fearful of GNU/Linux. They have been fearful since 2000 or so when IBM began to push GNU/Linux. Now their worst nightmares are coming true:
    • netbooks give them nowhere to hide the cost of that other OS

    • Obama won
    • Vista only sells to those who do not know they have a choice
    • economic downturn makes GNU/Linux very conspicuous as a centre of growth
  • Obama won. He used FLOSS in his campaign. He has asked McNealy to report on use of FLOSS in government
  • netbooks are selling like hot-cakes
  • quad-core CPUs are becoming inexpensive but CPUs have been good enough for a long time, probably since 1998 for the desktop, and 1990 for thin clients.
  • layoffs abound, even in IT
  • RAM prices are dirt-cheap
  • hard drive prices are becoming dirt-cheap
  • motherboards are having GNU/Linux in ROM and it is not only for thin clients

What does all this mean? I believe we will see real change in IT in 2009.

  • The quad-core revolution combined with dirt-cheap components will permit M$’s bloat to run for those foolish enough to spend money on high-end systems when low-end will do the job but I predict fewer people will be that foolish in 2009. Not everyone chooses to drive a Cadillac. Other cars have wheels. Most people are finding the wonderfully inexpensive netbooks will do the jobs they need doing: surfing and a bit of word-processing. With more services coming from the web, very few of us need anything more than that. Intel and AMD who have bet the farm on high-end CPUs will be in for a shock in 2009 when netbooks keep growing and notebooks and desktops become large netbooks. Wintel cannot fool all the people all the time. Price/performance competition is emerging to undermine the sand-castle of monopoly.

    I am surprised by AMD. They seem to be ignoring the netbook. This is utter folly. Soon only gamers, HPC, and servers will use AMD’s chips.

  • Ignoring the netbook/assuming it is transient will cost AMD and Intel dearly in 2009. Chinese home-grown processors, VIA and others will make huge gains in unit-share.
  • If 7 is installed on netbooks without malware-scanning they will be owned by the malware. If 7 is installed with malware-scanning/DRM/phoning home, what will happen to the “performance increase” over Vista? GNU/Linux will win the netbook market easily. There is no magic in 7. It cannot do more useless stuff without impacting performance.
  • Emerging markets will continue to gobble up GNU/Linux as they are very sensitive to price and not locked in. Expect much of Europe, South America, Asia and Africa to grow away from the monopoly in 2009. Netbooks will lead the charge. If the big OEMs will not produce enough of them others will. Others are 40% of the production now. ACER and ASUS grew spectacularly in 2008 by pushing netbooks.
  • Chinese production of all things IT will continue to grow. They are not locked in to Wintel and will produce $100 netbooks in 2009 in quantity. That will surely be the end of the Wintel monopoly. If netbooks are hot everywhere at $250-$300, they will be incendiary at $100. There will be few sales of licences by M$ at that price. If M$ tries to sell 7 for $0 on the netbook, who, in their right mind, would pay $300 for it on a bigger machine? Very few. Only those locked in and they are not buying in 2009.
  • The only reasonable use for the quad-core CPUs on most desktops will be as a GNU/Linux terminal server so expect huge increases in this sector. In a few years, thin clients will be as popular as netbooks today. Price/performance advantages are very large against XP. They will be astronomical against Vista/Vista II. The OEMs will have to push hard on server consolidation and terminal servers to sell chips in 2009. That other OS is at an extreme disadvantage in these spaces because of the GUI/malware/updates/registry/re-re-re-boots/lack of shared memory. It is a single-user OS, after all. Compared to GNU/Linux, on the server, Vista/Vista II is like DOS compared to UNIX, a pale imitation.

    Thin client production/sales should make a real move in 2009. Growth and consolidation have made the supply side mature but they have plenty of production head-room. 2009 will use that up. Because of the low material costs, thin client production can be ramped up much faster than desktop/notebook production falls. There will be a large market swing in 2009. For schools, governments, and offices in business and healthcare, expect many new installations/upgrades to use thin clients. Those that stick with Wintel will lose a lot of the cost advantage of thin clients but gain the labour reductions matching the economic downturn. Those who adopt GNU/Linux will have it all. OpenSolaris will have some action too.

  • The Seagate fiasco will see a shift to Western Digital. No one needs the hassle of flashing their hard drives. Coming in an economic downturn, this event could be a severe hit for Seagate. Perhaps they will not recover from it. They lost brand loyalty.
  • In 2009, M$ should start re-organizing. They cannot ignore reality much longer or they will take a big hit in their bottom line. If Vista does not sell in 2009, “software assurance” fizzles, and they dump XP on netbooks at a very low price, where is the growth? The toys will not subsidize the empire. It must eventually produce something of value in the market or be replaced with something that does. 7 is M$’s last chance and the longer it is delayed, the more remote is that chance. If 7 comes out laden with DRM/phoning home/any warts at all then the cash cow is ended. Christmas 2009 will be the deadline. If 7 is not a winner by then it never will be able to hold back the flood. To be a winner, 7 has to appeal to the XP-lovers out there and it will not. To promote 7 they will have to kill XP and that is the end of the story. If they keep XP some way, they will lock themselves into technology from 2001 which was obsolete then. There is no way that will be able to compete with market dominance in the face of Vista II/GNU/Linux etc. They cannot promote both XP and Vista II. The hypocrisy will be palpable. Will they keep XP for netbooks only? Then business will migrate to Mac OS or GNU/Linux. If they allow XP back onto notebooks/desktops then the XP-lovers will never buy the newer products. Will they put an XP-skin on Vista II? Then performance will drop again. This is a no-win situation for M$ They must descend the mountain of monopoly to survive.
  • GNU/Linux will keep on doing what it is doing. Through diversity, it can survive any twists of fate. Through collaboration it will become the largest software development house on the planet. In 2009, everyone on the planet will know there is a choice in OS. Everyone will have that choice and many millions will make that choice. They will have lower-cost software and make the best use of their hardware.

Update:M$ makes cuts. How is that for an accurate prediction? I had not read this article which was published today when I made my prediction. M$ blames netbooks. HAHAHAHA! M$ should blame its short-sighted approach to IT. The chickens are coming home to roost.

- Robert Pogson

XP, Obsolete When It Was Released?

Abstract:
XP was obsolete by ordinary standards of computer science in 2001 when it was released and remains today inferior to other operating systems such as GNU/Linux.


Part I

Introduction


In a meeting of a committee for information technology, the statement was made that Windows XP was obsolete when it was introduced in 2001. This brought comments of “Windows bashing” and “negativity”. Here, the case will be made in support of the assertion. What makes an operating system obsolete can be issues of quality, reliability, features and the availability of something better. GNU/Linux was better than XP in 2001. It did not crash. It had all the features we needed.


Part II
Properties of a Good Operating System, circa 1970


Forty years ago, computer science was thriving. Universities had access to a variety of expensive but barely affordable main-frame, mini and, about 1974, micro computers. The knowledge of what a operating system needed to do and how to develop reliable software were being developed. The first GUIs emerged. UNIX emerged. UNIX was the standard operating system of computer science for several reasons:


  • ATT had developed UNIX for the purposes of their own business but
    had realized that UNIX had market value.
  • They shared the source code with many universities so that a wider range of higher expertise could be employed to improve the operating system. This code became so much superior to most other commercial operating systems that it became the standard for large businesses and universities around the world.
  • Eventually ATT decided to cash in and made the licence for the binary and source code very expensive and restrictive. A legal suit resulted in decisions that BSD (Berkeley Software Distribution) was sufficiently unique and mostly not created by ATT that ATT had not the right to restrict it.
  • From this codebase evolved many operating systems: Mac OS/X, FreeBSD and the networking stack in Windows after it was shown repeatedly to be superior.


One thing that most UNIX operating systems lacked was a decent programming language. C was a crude language, but, because it had been used to write the original UNIX operating system it became widely used to write most important software on the market today. C lacked a mechanism called “garbage collection” which recovered resources left over from terminated processes. When programmes work with dynamic data structures, they request storage from the operating system and when properly executed and designed should return that storage to the operating system. This does not happen well if the process dies suddenly or if there is an error in the programme. Other languages automatically recall all storage issued upon the death of a process, but not C.

This defect is present in most operating systems and requires a greater
effort at debugging and testing to ensure processes do not die unexpectedly and that resources are returned.


A good operating system follows the KISS principal, “Keep it Simple, Stupid!”, because the simpler any code


  • the easier it is to debug,

  • the more efficient it can be in terms of speed of execution and use of resources (utilizing the same algorithm),
  • the easier it is to document so that staff turnover/growth does not unduly increase the rate of errors in modifications and additions to the code, and
  • the fewer undetected/unfixed bugs will be in it.


A good operating system can run for years under a full load, starting
and stopping many processes, without a failure. e.g. Netcraft monitors
as many web servers as it can find on the Internet. The November 2008
report from netcraft summarizes the results of observing 185 million
web sites. Windows 2003, which is far more reliable than XP because
it does not have all the desktop tools and users needs to be rebooted
much more frequently than a UNIX operating system.[reboots, reboots2, bleed]The
feature of GNU/Linux that makes it far superior to XP is that large
distributions of applications, the operating system and its drivers
are all checked out together in the beta stage. XP was a beta project
when it was released and it had many teething pains with the applications
that were ported to it. GNU/Linux when released was tested with all
the applications and driver in its distribution. Currently, Debian
has tens of thousands of sofware packages that are down to a level
of a few hundred known bugs. XP shipped with tens of thousands of
bugs.

The basis of the rapid development and high quality of GNU/Linux software is the use of FLOSS development model. A developer does not need to pay for a licence for a number of different software libraries and does not need to create his own. That leaves him much less work to do because the nuts and bolts already exist. Microsoft has similar libraries available but the software that uses them is only portable to Windows. Further, the application/project is distributed at very
low cost. The libraries distributed by Microsoft make second-class
citizens of developers because Microsoft has one API for itself and
another for potential competitors. GNU/Linux gives everyone equal
opportunity which inspires innovation.


Part III

Properties of Windows XP

The rebuttal that Windows XP is widely used does not counter the argument that XP was obsolete when it was introduced in 2001. XP and other recent Windows operating system all deviate from the known characteristics of a good operating system.


  1. XP is not simple. Microsoft deliberately chose to integrate many interlocking features into every part of the operating system from the user interface to the kernel. They did this to provide features and performance that competitors could not duplicate because they had no access to Microsoft’s source code. This made the use of any other operating system or competitor’s application a jarring experience so that users would perceive that Windows was a superior operating system. The purpose of an operating system is to provide a uniform interface between users, applications and hardware, not to promote one supplier’s software. This complexity introduced many opportunities for bugs and malware to operate on an enormous scale compared to other operating systems and was used by Microsoft to exclude competition from the market.[tying] What Microsoft was doing actually gave users a uniformly poor performance with all third-party applications developed for Windows which became
    very poor when ported to another operating system. When Microsoft
    wanted to put any competitor out of business they had only to use
    their private, preferred API to magically gain superior performance.
    After a decade of this, developers are writing web applications that
    do not require Windows on the client or server because it is easier
    and avoids the API trap.[API]
  2. XP is terribly insecure. Because it was designed as a single-user system, no thought was given to security until malware from the Internet raged through the XP mono-culture.[2007, insecurity, shatter]
  3. Backwards compatibility, intended to make transition to new versions easier and migration to other operating systems harder, and increasing lock-in, actually copied bugs from the 1980s into XP. [backwards]
    This is one of the key reasons why XP was obsolete when released.
    It does many things the same way as DOS.

  4. XP is slow. Microsoft deliberately wastes computer resources so each release needs new hardware.[slow] Tests on the PCs in the
    lab show booting to a log-in screen takes 45s with GNU/Linux or XP
    (largely determined by speed of storage) but after entering credentials,
    XP takes 75s to get a usable desktop while GNU/Linux takes 7s (largely
    determined by the presence or absence of bloat). The difference is
    feature-bloat. This pattern of ever-increasing bloat reached new highs
    with Vista. Employees are actually suing employers for long boot-times.
    Employers are refusing to pay the employees while they wait for a
    usable desktop.[boot]
  5. XP is difficult to administer. Because there are so many features, updates, vulnerabilities, patches, licences, versions, and bugs, a system administrator has much more to do that with a UNIX operating system:maintain accounts, backups, and to install useful stuff.
    e.g. a school division moved from 300 Windows stations to 1400 Solaris
    (a UNIX OS) stations without adding any support staff and the support
    staff had much more time for planning and organizing after the change.
    Sun claims for their Solaris/thin client setups:”Reduce Administration Costs – One administrator may now easily manage thousands of desktops. Stateless thin clients require no management or maintenance ”[hard]
    In Easterville, I was system administrator for a school running GNU/Linux. That task took about five minutes on an average day for 153 seats and 700 accounts. Here, I spend more time than that resetting passwords. At Easterville, I created 700 accounts in five minutes and only had to reset passwords a few times. Here, I have to type the
    administrator’s password dozens of times per day. At Easterville,
    once every few days was enough. I could access everything I needed
    to access from my ordinary user account without typing the root password, in a secure manner, with stored keys. I could log into any computer in the system without leaving my chair. This is what the legacy of being a networked operating system from conception means. Windows
    had no concept of a network and jumped into the game late, breaking
    things. They used a GUI to do things that were best done using a keyboard. Imagine creating 700 accounts clicking a dozen times with a mouse for each one. Imagine having to visit every PC to install software
    on it. With GNU/Linux or other modern operating system, there are
    tools in the system to expedite all those things. The Windows way
    of doing things may work for a single PC at home but it does not work
    for schools.
  6. XP squanders resources. Consider our lab. Using XP, we have 22 gB of RAM in the clients alone and several gigabytes on the servers. Using GNU/Linux, and thin clients, we could cut memory on a client to 256 MB or less and increase memory on the server for a large net decrease (24gB – 4gB = 20gB) in memory with no decrease in performance except full-screen video. For video, one needs much more memory on the client to buffer data from the server. The difference is that Windows was designed as a single-user system and does not share memory between processes. UNIX has been doing that well for decades. The server running with 8gB RAM could run the whole school. [resources]
    Then there is disc storage. We have 22 X 40gB = 880gB of storage almost
    unused on the clients. Yet our servers are short of storage. We have
    22 X 1600MHz = 35 gHz of computing power tied up in our XP clients
    in the lab utilized about 1% when students are browsing, a colossal
    waste. It would take much less power than that to run the server and
    it would be well utilized. One good thing about our implementation
    of XP, because we write files on the server our clients do not have
    fragmented hard drives.
  7. XP is useless without a server because of the weight of system administration. Tools on the server manage accounts/security/storage/printing. Without the server we would have a bunch of home-style personal computers each needing individual care by the system administrator. Typically, a Windows server does about one-third as much work as a UNIX server. We have 7 servers, all idling, partly because we use XP. In Easterville, MB, I built a system for a school with 153 seats and three servers could do the job easily. One would have done if the school were not so long that two network segments/server rooms were needed. We have 75 seats working, sometimes. One UNIX server costing a few thousand dollars could easily run our school these days, thanks to Moore’s Law. Throughput of servers running GNU/Linux is 50% higher than Windows by some measures and lower downtime increases the margin further.
    [put]

  8. Licensing is unnecessarily complex and expensive. Many businesses pay more than they should because it is impossible to know what is the best deal.[SA] The terms of the licence are so complicated that many businesses find it difficult to follow and the cost of being caught out of compliance can be very large.[BSA] Microsoft
    also pressures businesses to buy more and more expensive licences
    than needed.[tactics]
  9. Rather than merely providing an operating system which manages resources between users, applications and the hardware, XP is a tool of Microsoft to exclude competition from the market. They have been able to maintain very high prices and provide substandard performance and still remain dominant because of these practices. Not only is this evidence of a bad operating system, it is illegal as has been demonstrated in courts in the USA and the EU. In particular, Microsoft “embraces, extends, and extinguishes” innovations of competitors, for example network protocols, and tying Microsoft’s products to the operating system in such a way that these products have innate advantages over competitors’ products in distribution and features. As the features often result in instability, poor performance, and avenues for malware, these are indications of a poor operating system. Other operating systems of the time did not exhibit these characteristics. e.g. GNU/Linux was and remains vendor-neutral, being based on open standards. Attempts by the Samba group to interoperate with Windows were stifled until the EU ordered Microsoft to divulge specifications of protocols that had been embraced and extended.[EU] Apple did use these
    same tactics but as they are not and never have been a monopoly, they
    did not harm the market except for their own opportunities in it.
  10. XP has a definite end-of-life date set by Microsoft. It has passed. In 2001, it was known that XP would expire eventually and a forced upgrade of hardware and software would result. GNU/Linux has no such end-of-life date because we could, in theory, obtain the source code and maintain it ourselves. As the school does not have the budget/manpower for this, it was obvious that eventually a GNU/Linux system would need migration as well but the system as installed would have worked indefinitely. XP is tied to Office that changes file formats on each release and this forced users of Windows to migrate eventually as they will no longer be able to open files sent from more recent releases. The operating system I used in Whale Cove in 2000, Caldera GNU/Linux could still have been functioning today except that .odf replaces .sxx as a file format in OpenOffice.org. OpenOffice.org can now produce .sxx and .pdf. It is not a good characteristic of an operating system that one is forced to migrate on the schedule of a corporation. One
    should normally do it at the end-of-life of the hardware to avoid
    re-installing. As hardware for clients can easily last ten years,
    a forced upgrade from XP in 2008 or so is definitely an undesirable
    property. Businesses have confirmed they do not intend to migrate
    form XP to Vista simply because they get no benefit form Vista and
    it is a huge cost. [KACE]

    KEY FINDINGS


    • 60% report that they have no plans to deploy Vista at this time,
      up from 53% in the 2007 survey
    • 92% say Vista Service Pack 1 has not changed their plans for Vista deployment
    • 14% report they have delayed their Vista deployments while they wait to hear more about Windows 7, and an additional 14% say they will skip Vista to wait for Windows 7
    • 83% of participants say they are concerned about the compatibility of required business software with Vista
    • 42% have considered deploying non-Windows operating systems to avoid a Vista migration compared to 44% in the 2007 survey
    • 11% are already in the process of switching operating systems, up from 9% in the 2007 survey, and a further 30% expect to switch within the next year, up from 25% in 2007
    • Mac OS is the most likely operating system to be deployed in place of Vista (29%)

One can see dramatic differences in uptime of servers running Windows and various UNIX-like operating systems at NetCraft.com. The fragility and poor managability of Windows make it a poor choice for servers. Desktop systems demand even more so XP and its kin are not good choices for an OS.

Part IV

GNU/Linux at the Time of the Release of XP.

One could make the argument that XP was the state of the art and so was widely adopted but it was not. I know that time very well because I was introduced to GNU/Linux the year before XP was released and implemented GNU/Linux on my own on a cluster of desktops in my classroom. On five machines we had not one crash in six months of daily use. The machines were left running 24×7 because they were so slow to boot. These were Pentium Pros with 72 MB RAM and 800-1000 MB hard drives. I fondly remember being able to tidy up errant applications from the gui with xkill.[xkill] We used StarOffice 5.2 (a precursor to OpenOffice.org) and Netscape, the browser that Microsoft effectively killed by illegal anti-competitive actions. The next year, XP was
released and people who used it had so much grief. Driver problems,
crashes, and re-re-reboots. Companies actually sold products that
could inform the user when XP was about to crash so they could close
files and reboot.[crashes]

Many installations of GNU/Linux were successful since about 1995.
Several of the classic distros like Debian and RedHat were active
and the software was developed and tested openly with all bugs publicized. This made development rapid and reliable unlike XP which evolved from NT in those days but in a closed shop strongly influenced by sales strategies and plans to kill competition rather than technology. Netcraft tracked the emergence of GNU/Linux on the web. It’s presence grew rapidly and its dominance over Windows remains today. With the advent of XP, there was strong pressure to use Windows servers but that cooled in the face of reality. Microsoft had nothing to offer that GNU/Linux could not at the time. The uptick in 2006 is again nothing but a marketing ploy. Microsoft paid large hosting systems like GoDaddy.com to switch to Windows Server 2003. GoDaddy.com uses Windows 2003 Server to host inactive sites/placeholders.[GoDaddy]




Figure 3: Netcraft Server Counts 1995-2008

Shortly after XP was released there were major migrations to GNU/Linux because XP/2003 was much more costly and less reliable than GNU/Linux. Extremadura, Munich, and Andalucia were in the news. Even when Microsoft cut prices to stay price-competitive with GNU/Linux in Munich, Munich valued the future costs and manageability of the system ahead of short-term costs. One migrates to GNU/Linux once but upgrades Windows licences forever. The per-seat cost advantage of forever is very large.[Andalucia]
GNU/Linux would not have this spectacular growth rate if XP was a
great operating system, technically. XP has improved since 2001 but
this is in response to the phenomenal growth of competitors like MacOS/X
and GNU/Linux.





Part V

Conclusion

I stand by the assertion that XP was obsolete in 2001. The facts supporting this position are many and solid. XP has improved but so have the competition. XP is still not technically as good as GNU/Linux and other UNIX-like operating systems. A rational decision in 2001 could have been made to install a more modern operating system in 2001. By 2004, there was little doubt that if a migration was possible it should have been done. Microsoft’s attempts to spread FUD about GNU/Linux may have held the day but the monopoly is crumbling. Brazil has 20% of PCs sold with GNU/Linux. China, Russia, Spain and many other countries are encouraging migration to GNU/Linux.[Connectado, Brazil] The migrations are late but they cannot be denied. The emergence of the low-cost PC where the price of XP/Vista cannot be hidden and the bloat cannot fit is doubling the rate of adoption of GNU/Linux.[LCPC] A survey of IT is showing that the world is waking up to the reality that Microsoft is not working for them.[KACE]


References

[uptime]

Netcraft’s report on reliability of service
sorted by failed requests in the last day. On 2008-12-6 , 22 of the
top 50 ran Linux, 8 ran Windows, and 6 ran FreeBSD. see http://up-time.netcraft.com/perf/reports/Hosters
[reboots]
The “up-time” graph for the most reliable
hosting outfit, www.nyi.net, shows they reboot every 500 days, like
clock-work, indicating they reboot only for planned maintenance. see
http://up-time.netcraft.com/up/graph?site=www.nyi.net They run FreeBSD.
[reboots2]
The “up-time” graph for the most
reliable hosting outfit running Windows 2003, www.serverintellect.com,
shows they reboot every six weeks, much more often than physical maintenance
would require. see http://uptime.netcraft.com/up/graph?site=www.serverintellect.com
[tying]
“Nevertheless, Microsoft tied the two
together, refusing to sell Windows 95 or Windows 98 without Microsoft’s
browser or to permit OEMs to remove the browser before selling their
PCs loaded with Windows. With Windows 98, Microsoft also unnecessarily
“welded” the browser to the operating system, so
that using another browser would be a “jarring experience,”
further excluding rival browser suppliers. ”see http://www.usdoj.gov/atr/cases/f2600/2613overview.pdf
[insecurity]
CyberInsecurity – “Over the years,
Microsoft has deliberately added more and more features into its operating
system in such a way that no end user could easily remove them. Yet,
in so doing, the world’s PC operating system monopoly has created
unacceptable levels of complexity to its software, in direct contradiction
of the most basic tenets of computer security. ” see http://www.ccianet.org/papers/cyberinsecurity.pdf
[shatter]
”All windows running in the Windows GUI
are peers, which means that at the level of window management they
are all equal in Windows’ view, and that they can send messages to
each other. There’s no authentication behind these messages, so there’s
no way to control who can send messages to whom…Some of these messages
can invoke commands; for example, to expand the size of an Edit Control.
Here’s how someone might invoke a buffer overflow and shatter the
window: First the Edit Control is grown by sending data to it, which
then overflows the buffer for that Control. Remember, the buffer was
sized to the original, smaller version of the Edit Control….A more
scary shatter attack (that has been fixed by Microsoft) uses the WM_TIMER
message. This common message has an optional parameter for a callback
function, so that the window receiving the message should execute
the code pointed to by the message. Any unprivileged process could
send a WM_TIMER message to a privileged interactive process and capture
its privilege level just by having it call back. ” This was the
state of XP in 2003 when XP had been widely distributed already. see
http://www.castlecops.com/a3654-Shattering_Windows_Is_a_Disaster_Lurking.html
[backwards]
“It’s Not a Bug. It’s a Feature”

“What exactly is going wrong with the WMF vulnerability? … Turns
out this is not really a bug, it’s just bad design. Design from another
era…. When Windows Metafiles were designed in late 1980s, a feature
was included that allowed the image files to contain actual code.
This code would be executed via a callback in special situations.
This was not a bug; this was something which was needed at the time.”
see http://www.f-secure.com/weblog/archives/00000761.html

[2007]
”2007: How was it for security?” Six years
after its release, and running on 90% of desktops, XP still has gaping
holes, often in features no one needs. see http://www.zdnet.com.au/news/security/soa/2007-How-was-it-for-security-/0,130061744,339284667,00.htm?feed=pt_malware
[slow]
”Current PC technology is totally sufficient
for most office tasks and consumers desires and any performance bottleneck
is not in today’s PCs but in today’s COM pipes. This in itself might
slow down replacement cycles and life time shortening until we find
true MIPS eating applications – a priority not only Intel should subscribe
to.” -Joachim Kempin, Microsoft’s OEM Chief see http://www.usdoj.gov/atr/cases/exhibits/365.pdf
This shows that “slow” is a design parameter. It is a conspiracy
between the OEMs and Microsoft to mutually promote their businesses
without regard to what the customer needs or wants.
[hard]
One system administrator can manage thousands
of UNIX desktops. see http://tapor.ualberta.ca/Res/Documents/SunRay01.pdf
It costs twice as much to maintain a system of Windows desktops according
to David Richards, the system administrator for Largo, FL. see http://www.freesoftwaremagazine.com/articles/book_review_linux_thin_client_networks_design_and_deployment_by_david_richards_2
[resources]
”If this scenario is deployed on centralized
Microsoft Windows using thin clients, then 2.76 GB is required. This
slight increase is because of the small amount of memory required
on the thin client to handle the video portion of the remote application
((256 MB + 10 MB +1 MB) X 10). However, when a centralized UNIX/Linux
solution is used, only 376 MB of memory is required. This is because
of shared memory. When the server detects that a program is already
running, it doesn’t start another instance of it in memory, and instead
simply adds a user space that stores the data specific to the user
(10 MB + 1 MB) X 10 +256 MB).” Windows uses nine times as much memory,
even using thin clients. Memory costs money and can fail. That is
squandering resources. see http://www.freesoftwaremagazine.com/articles/book_review_linux_thin_client_networks_design_and_deployment_by_david_richards_2
[put]
Throughput of servers running Linux or Windows
was compared. Linux was superior in most categories by large margins
of 50%. see http://www.webperformanceinc.com/library/reports/windows_vs_linux_part2/
[SA]
”Microsoft introduced Software Assurance as
part of Licensing 6 in May 2001. The plan received scathing response
from analysts and customers. Under Microsoft’s Licensing 5, companies
had the option of buying upgrades when they wanted and paying a discounted
price at time of acquisition. Licensing 6 did away with off-the-shelf
upgrades and, through Software Assurance, had companies paying upfront
for software, under two- or three-year commitments. For upgrade rights,
customers pay 29 percent annually for desktop products and 25 percent
for server software. In 2001, Gartner estimated that about 80 percent
of Microsoft customers would see price increases ranging from about
35 percent to 107 percent.” see http://www.microsoft-watch.com/content/operating_systems/software_assurance_storm_warning.html
[BSA]
”I became an open-source guy because we’re
a privately owned company, a family business that’s been around for
30 years, making products and being a good member of society. We’ve
never been sued, never had any problems paying our bills. And one
day I got a call that there were armed marshals at my door talking
about software license compliance…I thought I was OK; I buy computers
with licensed software. But my lawyer told me it could be pretty bad.

—The BSA had a program back then called “Nail Your Boss,”
where they encouraged disgruntled employees to report on their company…and
that’s what happened to us. Anyways, they basically shut us down…We
were out of compliance I figure by about 8 percent (out of 72 desktops).—How
did that happen? We pass our old computers down. The guys in engineering
need a new PC, so they get one and we pass theirs on to somebody doing
clerical work. Well, if you don’t wipe the hard drive on that PC,
that’s a violation. Even if they can tell a piece of software isn’t
being used, it’s still a violation if it’s on that hard drive. What
I really thought is that you ought to treat people the way you want
to be treated. I couldn’t treat a customer the way Microsoft dealt
with me…I went from being a pro-Microsoft guy to instantly being
an anti-Microsoft guy.—Did you want to settle? Never, never. That’s
the difference between the way an employee and an owner thinks. They
attacked my family’s name and came into my community and made us look
bad. There was never an instance of me wanting to give in. I would
have loved to have fought it. But when (the BSA) went to Congress
to get their powers, part of what they got is that I automatically
have to pay their legal fees from day one. That’s why nobody’s ever
challenged them–they can’t afford it. My attorney said it was going
to cost our side a quarter million dollars to fight them, and since
you’re paying their side, too, figure at least half a million. It’s
not worth it. You pay the fine and get on with your business. What
most people do is get terrified and pay their license and continue
to pay their licenses. And they do that no matter what the license
program turns into. ”see http://news.cnet.com/2008-1082_3-5065859.html

[bleed]
”George Kapotto :—We dropped Desktop SA
- Vista and Office came out before the expiry so we are entitled.
We just upgraded to XP and there is no interest in another quick upgrade
so XP for 3-ish years followed by Vista for a couple or 3 more (provided
MS ever gets a version worth using ). With approx. 1000 desktops it
is easily cheaper to just start fresh when/if the need arises. We
kept the server SA primarily because of the CALs – the ROI is a bit
more clear in this area.—And somewhere in there, we will start using
Linux for thin clients.—That about sums up our current stand on
the M$ bleed.—Posted by George Kapotto | July 10, 2007 9:41 AM
” see http://www.microsoft-watch.com/content/business_applications/microsofts_licensing_response.html#comments
[tactics]
””Thank you for your offer to
send your purchase records to me,” she wrote, “however
our Software Asset Management (SAM) program is the only unbiased way
to create an accurate baseline and resolve this matter.”—That
did it. Frantz informed Lawless that he wasn’t going to waste anymore
time with her, and he left the matter with his attorney. The attorney,
suspecting that Lawless’ actions were part of an elaborate sales effort,
basically told her to back off.—Indeed, according to Microsoft’s
Web site, the responsibility of someone with Lawless’ title of “engagement
manager” is to “perform as an integrated member
of the account team, drive business development and closing of new
services engagements in targeted accounts.” So why was someone
in a sales position leaning so hard on AWC about a supposed licensing
compliance concern?—When I phoned Lawless to find out, she referred
me to Microsoft’s PR machine. The responses I got through that channel
stressed that Microsoft’s aim is to help customers navigate the complexities
of software licensing and that one of the roles of engagement managers
is to assist in that effort by informing customers of a potential
licensing risk. I was told to attribute the responses to Lawless.”

see http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=111186

[xkill]
From the man page: “Xkill is a utility
for forcing the X server to close connections to clients. This program
is very dangerous, but is useful for aborting programs that have displayed
undesired windows on a user’s screen. If no resource identifier is
given with -id, xkill will display a special cursor as a prompt for
the user to select a window to be killed. If a pointer button is pressed
over a non-root window, the server will close its connection to the
client that created the window. ”
[crashes]
Even after SP2, XP still crashes frequently.
Notice that many commentators blame third-party drivers and applications
but this still signals a weakness in the design of the OS that it
is so easily crashed. No user application can ruin GNU/Linux that
easily and drivers supplied with the Linux kernel are very solid and
well tested. Microsoft does not protect its registry from third party
applications. see http://weblog.infoworld.com/daily/archives/2006/06/talkback_does_w.html
[GoDaddy]
”Perens: Not the first. It’s part of a
continuing behavior pattern by Microsoft that I think it’s fair to
call “dirty fighting.” GoDaddy was using Apache
(I assume on Linux) because it was a great technical solution. They
didn’t switch to IIS on Windows Server 2003 for any technical reason.
The switch was accompanied by a press release by GoDaddy, containing
Microsoft promotional language. Now, I’ve changed many servers from
one thing to another, but I’ve never made a press release about it.
GoDaddy wouldn’t be doing that unless Microsoft had offered them something
valuable in return. There has been talk in the domain business that
Microsoft has been offering the large domain registries a wad of cash
to switch their parked sites. There is no other reason to do this
than to influence the Netcraft figures.” see http://www.itbusinessedge.com/item/?ci=15108
[Andalucia]
see http://www.linuxforum.dk/2004/program/slides/greg_mancusi/greg_LinuxForum_01.ppt
[EU]
Microsoft uses various levers to
favour the migration towards new versions: providing an easy migration
path by ensuring “backward-compatibility”, which
guarantees, for example, that successive versions of Windows retain
the ability to run key applications developed for earlier versions,
advocating to software developers the use of new features of the Windows
platform, which means that increasingly the most recent applications
will no longer run in fully compatible mode on older versions of Windows
and, eventually, discontinuing support for previous versions of the
operating system.
” … “As regards competitors, the
fringe competition constituted by Linux is a case in point. Linux,
which has been developed under the open source model, can be technically
pre-installed on PCs at virtually no cost by OEMs. Whilst the first
versions of Linux were fairly difficult to use for non-technicians,
the product is widely considered to have matured at the end of the
1990s and now there is no significant difference in terms of ease
of use between Windows and most commercial Linux operating systems.
Microsoft’s financial performance on the market, however, does not
seem to have been affected by the emergence of such a rival. Microsoft
has not substantially altered its pricing policy and business model,
and it has remained very successful.
”…””The Windows
API is so broad, so deep, and so functional that most ISVs would be
crazy not to use it. And it is so deeply embedded in the source code
of many Windows apps that there is a huge switching cost to using
a different operating system instead…. It is this switching cost
that has given customers the patience to stick with Windows through
all our mistakes, our buggy drivers, our high TCO, our lack of a sexy
vision at times, and many other difficulties. [...] Customers constantly
evaluate other desktop platforms, [but] it would be so much work
to move over that they hope we just improve Windows rather than force
them to move. In short, without this exclusive franchise called the
Windows API, we would have been dead a long time ago.”579
“The Windows franchise is fueled by application development
which is focused on our core APIs”580 ”…”Once Microsoft’s
work group server operating system gained acceptance in the market,
however, Microsoft’s incentives changed and holding back access to
information relating to interoperability with the Windows environment
started to make sense. With Windows 2000, Microsoft then engaged in
a strategy of diminishing previous levels of supply of interoperability
information. This disruption of previous levels of supply concerns
elements that pertain to the core tasks that are expected from work
group server operating systems, and in particular to the provision
of group and user administration services. In the following recitals
(recitals (590) to (692)), it will be established that Microsoft’s
refusal puts Microsoft’s competitors at a strong competitive disadvantage
in the work group server operating system market, to an extent where
there is a risk of elimination of competition.712 ”…”Through
tying WMP with Windows, Microsoft uses Windows as a distribution channel
to anti-competitively ensure for itself a significant competition
advantage in the media player market. Competitors, due to Microsoft’s
tying, are a priori at a disadvantage irrespective of whether their
products are potentially more attractive on the merits.
” … The
EU ruling: http://ec.europa.eu/comm/competition/antitrust/cases/decisions/37792/en.pdf
[KACE]
”Windows Vista Adoption and Alternatives:
A Survey of Technology” “”see http://www.kace.com/pdf/index_vista_survey.php
[Connectado]
”Brazil’s new PC Conectado plan will
make Internet-connected Linux PCs affordable to poor households. Buyers
will be able to pay just under $25/month for 24 months for a PC and
Internet service; the Brazilian government expects up to 1,000,000
participants in the program by the end of the year.” see http://www.windsofchange.net/archives/pc_connectado_brings_internet_linux_to_brazils_masses.php
[Brazil]
1.5million GNU/Linux PCs each year sold in
Brazil see http://www.brazzilmag.com/content/view/7963/54/
[LCPC]
Report from spring 2008 on the emergence of
the lowcost PC and its market outlook with GNU/Linux. see http://www.caixamagica.pt/Linux2008/01_lisbon.pdf
[boot]
According to a report this week
in the National Law Journal, hourly employees of AT&T, UnitedHealth
Group, and Cigna have sued their employers for not paying them for
the 15 to 30 minutes it takes to start up and shut down their PCs.

see http://www.crn.com/software/212101166

[API]
”How Microsoft Lost the API War”see http://www.joelonsoftware.com/articles/APIWar.html





This document was translated from LATEX by
HEVEA.

- Robert Pogson

Google Elephant in the Kitchen

The relationship between Google and M$ is very interesting. Google operates in a different universe, one so far, far away from M$ that M$ has not been able to touch it. Google got into business on the web which M$ does not control. With a huge search/ad business, they could be a competitor of M$ but they are not, because M$ started so late. Now, it develops, Google has found a worm-hole back into M$’s universe and is readying an army of developers to flood M$’s universe with Android applications. Android was known to be developed for cell-phones but it has been discovered that Android can be compiled from source to produce a desktop OS.

Wow! A small bit of tweaking allows Android to run on netbooks… Google must be up on SunTzu:


Thus we may know that there are five essentials
for victory:
(1) He will win who knows when to fight and when
not to fight.
(2) He will win who knows how to handle both superior
and inferior forces.
(3) He will win whose army is animated by the same
spirit throughout all its ranks.
(4) He will win who, prepared himself, waits to take
the enemy unprepared.
(5) He will win who has military capacity and is
not interfered with by the sovereign.

Thus, while appearing not to be dangerous or aggressive, Google has set up everything needed to depose M$ on the desktop, a huge army of developers, a platform easily ported to anything, and a revenue-generator. All that remains is the announcement of the battle, or perhaps, the victory.

If we look at netbooks as the battle-ground, and assume the end-user is agnostic (the OS just works), then market share will go as 1/N where M$ counts as one OS in the battle. There are many GNU/Linux choices, all making ground. Android can instantly push into the fray and take a huge portion because there could be a huge financial incentive to the OEMs in a partnership with Google… XP has perhaps 70% of new netbooks today. By next year it could have as little as 20% because it has nothing in particular that the consumer wants in this space. No bloat, please. No phoning home! No DRM! No licence-fee!

Once netbooks are overwhelmed, the notebook and desktop can follow because there is no particular difference that matters to Android/GNU/Linux. This is a one-way worm-hole. Google can attack and M$ has no response. Can they buy Yahoo? Can they build a decent OS for free? No way. Can they pay the whole world to install that other OS? Not for long. The world is too large to buy.

- Robert Pogson

Flexibility

A good article at Linuxinsider.com begins with

“Linux has proven that the open source  open source model works — it addresses two of the biggest challenges for IT professionals: the high cost of infrastructure software and the limitations a closed stack imposes on the enterprise. Open source is particularly appealing for the following reasons:

* Cost savings — Users do not pay a license fee to adopt open source software nor do they pay for updates, eliminating the large upfront cost typically associated with infrastructure development and significantly reducing the total cost of the project.

* Vendor neutrality — Open source software is developed and owned by the community. Users of the project are not locked in to a vendor’s platform and are not forced to buy proprietary modules or adopt prerequisite technology.”

* Access to source code — By definition, open source projects make the source code available. This allows enterprises to inspect the code for safety, edit the code to add unique features, and not be at the mercy of a vendor.

* Innovation — With a large community that includes end users contributing to the project, open source software has proven itself to be a practical vehicle for the latest technological advancements.”

Deborah Moynihan comes close but seems to circle around one of my favourite advantages of FLOSS: flexibility.  While all of her major points are fallout of flexibility, she does not seem to see the crater flexibility creates. One starts any software project by collecting ideas and resources. If one decides to use “proprietary”/non-free software, one has to dig that big hole with a teaspoon rather than with an explosive. This is expensive, locks one in, does not give access to source and stifles innovation. The non-free licences usually place so many restrictions that the project is no longer your own. FLOSS on the other hand moves a mountain for you and all you have to do is the landscaping, adding a few features and concentrating on what you want your software and your computers to do, a much better use of your resources. All the little negatives she does bring out, like the viral nature of FLOSS, pale in comparison to the value of flexibility. One needs lawyers to review non-free licences as well as FLOSS, but FLOSS gives lawyers much less work because the GPL has been designed by lawyers to do the things FLOSS needs doing, including providing flexibility to developers and end-users.

If one can find tons of software with licence lawyers and developers love, many obstacles to software development evaporate. Those who insist on the “proprietary” model for everything are making themselves into dinosaurs very rapidly. Re-inventing the wheel or paying someone to do that is really stupid and expensive.

- Robert Pogson

Reality, What a Concept

My school has a powerful server, idling, and a mess of sissy servers, also idling. Server consolidation is in order. They all run that other OS. They need a server running GNU/Linux to run various web applications. The solution: VirtualBox from Sun Microsystems.

Virtual Box is a hypervisor for virtual machines. One installs VirtualBox, creates and configures as many virtual machines as one needs and installs an operating system in each. I chose GNU/Linux because that is what I am most comfortable using and I have tons of free software for it. On the first one, I installed LAMP (GNU/Linux, Apache, MySQL, and PHP). This lets me add server scripts in PHP to do some very useful things:

  • collaboration/knowledge database with WikiMedia
  • huge number of text files indexed with SWISH-e and searched with swishe.php
  • searchable image gallery with Gallery
  • Moodle course management system

Then, I can create other virtual machines to hold the functions of the lesser servers, mostly print, file-sharing and database.

The only problems I had with this project?

  • the underlying OS was 32bit so I could not install more RAM than 4gB
  • it was tricky to use the NICs on the machine

Even the devotees of that other OS can use this technology and when they want to get off the Wintel treadmill, they can migrate their host OS and their virtual machines one by one making the job much easier. I can OpenSSH into mine to tweak and to manage. I can also control that other OS using Rdesktop (RDP protocol). That works better from a GNU/Linux machine than using the native Remote Desktop from my XP box. The print server no longer crashes weekly if I use GNU/Linux Rdesktop. Interesting, and very real. So, time moves on. If I keep beating my head against that monopolistic wall, it will move.

Lo, and behold, SUN has a new release which deals with both issues.

When my organization is comfortable with GNU/Linux as a guest OS (my boss already uses GNU/Linux at home), they can switch services one at a time to GNU/Linux guests and eventually, only a few databases will remain for compatibility with the mother ship.

So far, VirtualBox has been solid for us. It just works. I did find that the emulated SCSI drive was much faster than the emulated IDE drive which is no surprise if well emulated. The big server is still lightly loaded but now it actually does useful stuff for us besides authentication and DHCP. It could for instance run a basic GNU/Linux terminal server in one of the virtual machines to give a new lease on life to the old thick clients that populate our system.

Virtuality is a wonderful use of the modern multi-core system. I have previously used LTSP which virtualizes the desktop. Now we can enjoy virtualization of the server for similar comprehensive benefits:

  • lower cost of maintenance
  • lower parts count
  • easier administration
  • easier integration of GNU/Linux
  • lower power consumption
  • less congestion in the server room
- Robert Pogson

Excellent Article at Heise on LTSP

see TFA.

TFA is concise, well-written and gives tons of links to further information about LTSP, the Linux Terminal Server Project, which is a great solution for extending the power of a newer PC or server and for centrally managing PCs at home, school or in business.

I first used LTSP in 2003 as implemented in the distro, K12LTSP. The LTSP team, and several distros have turned this combination of x-window-system, DHCP/BootP/TFTP/NFS into a means of booting diskless clients. This saves thousands of dollars in capital costs for even a small installation and lightens the load on the system administrator by a large factor.

- Robert Pogson

If You Like Thin Clients Stay Away From That Other OS

Thin clients are wonderful. They are:

  • small
  • quiet
  • cool
  • inexpensive
  • fast

but M$ wants to take away one of their chief advantages. This is what BILL VEGHTE said in an interview at Credit Suisse Annual Technology Conference 2008:

“we’ve been very successful in making sure that if you want the full Windows experience on there, that that is not — that doesn’t hit our average selling price. It’s delivering that Windows experience just through a different model, but our ability to deliver that, to extract that value instead of sort of a royalty type thing, do it through Client Access Licenses, server side and client.”

I will stick with GNU/Linux, Bill. I want it all. Compared to those big, old boxes, they are beautiful, eh? Let us reclaim the desktop.thin_client1

- Robert Pogson

Excitement About Thin Clients

IDC has issued a press release:”IDC Predicts Current Economic Crisis Still Provides For Pockets Of Opportunities Within The Asia/Pacific (Excluding Japan) Region in 2009

12 Dec 2008

9. Thin Clients Will Ride The Wave Of Cost Cutting And Desktop Virtualization

As the market matures, and better vendor collaboration results in software standards merging, virtualization to cut costs will extend beyond server virtualization in datacenters to virtualizing the desktop. In addition, deploying thin clients and a virtualized desktop environment will also reduce the carbon footprint. IDC is therefore optimistic and predicts that thin-client deployments on the back of desktop virtualization will gain traction in 2009, and further accelerate into 2010, as PC replacement cycles peak across the region. Full year 2009 thin-client shipments are expected to grow within the 12–15% range over 2008, to about 765,000 units.

10. The Economy And Mini-Notebooks Will Challenge The Way Computers Are Used And Sold In Asia/Pacific

IDC expects mini notebooks, a new product category created due to demand for devices that support mobility, to increase from around 5% of total notebooks shipped in the APEJ region in 2008 to more than 10% in 2009. The small cutesy form factor will be the primary selling point, but it will also change the way these devices are being used. With limited processing power and storage, users will be heavily dependent on being connected to the Internet, eventually running applications through the cloud. This demand for connectivity will further change the way mini notebooks are sold – instead of retail stores, partnerships with mobile operators are expected to proliferate with devices sold in service bundles like mobile phones, leveraging operators’ cellular 3G infrastructures. With vendors already looking at ways to overcome the challenges associated with this product category, IDC believes that mini notebooks will change the way traditional notebooks are used and sold.

This reflects the excitement I have been feeling about thin clients in education for several years. They are a great solution for cost-cutting and manageability. Of course, the IDC report is not only about education but the whole market in APEJ. Still, if businesses see the benefit, schools should as well.

The connection with netbooks is that both thin clients and netbooks share common features:

  • low cost
  • low footprint
  • low power
  • low noise

, all bringing value. The lack of horsepower for video is unimportant in many cases and, with the march of Moore’s Law, perhaps this will disappear as an impediment. That leaves the question, Why don’t more systems use thin clients?. I have no answer. Everyone to whom I have shown thin clients loves the improved performance and small footprint. Perhaps not enough people have seen them yet. I intend to change that in a small way at my next conference of teachers. I have a portable lab of thin clients under construction and will show it off with GNU/Linux, standard desktop applications, some particularly useful in education and some web applications like

Perhaps the IT industry is nervous about thin clients. After all, if thin clients cost less and last three times as long, isn’t there less money to be made selling them? Yes, but you should be able to sell many more and the servers to go with them. It is a paradigm shift, not the death of IT.

- Robert Pogson



Archives by Month

My Mission

My observations and opinions about IT are based on 40 years of use in science and technology and lately, in education. I like IT that is fast, cost-effective and reliable. I do not care whether my solution is the same as yours. I like to think for myself.

My first use of GNU/Linux in 2001 was so remarkably better than what I had been using, I feel it is important work to share GNU/Linux with the world. I have been blessed by working in schools where students and school systems have benefited by good, modular software easily installed in most systems.

I have shown GNU/Linux to thousands of students and hundreds of teachers over the years and will continue in some way doing that until I die in spite of the opposition.

Posts

May 2012
S M T W T F S
« Apr    
 12345
6789101112
13141516171819
20212223242526
2728293031