||Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix|
The real economic question of the OS model is how is money made, and who is making the money. Who is being rewarded financially for the enormous development effort? The open source initiative claims that there are at least four different models that allow someone to reap rewards. Oddly, it is not mentioned that it is not necessarily the people who did the development work that gain financially.
The third case, "Widget Frosting", sounds completely practical. The premise that hardware makers produce open source software so that the OS development community will work for free to produce better drivers and interface tools for their hardware products. It sounds great on the surface, especially for the company that produces the hardware: they get free drivers and do not have to pay for expensive developers. The OS community wins by getting presumably stable drivers and tools. What is not mentioned is the reason hardware makers usually don’t do this is because they do not want to reveal trade secrets regarding their hardware design. Production of efficient drivers requires an intimate knowledge of the hardware the driver is for. It is almost always the case that it is in the hardware developers’ best interest to keep their hardware secrets close to home. This also brings up the question of why isn’t hardware "open"? So much for the frosting case.
The final case, "Accessorizing", is similar to the first, but throws in the idea of selling books and complete systems with the open source software, and other accessories as well. It is obvious that selling books qualifies as support, and that it really belongs in the first case. The idea of selling computer systems, T-Shirts, dolls, again begs the question: "Who is making the money?" As with the first case, it is not necessarily the people who have done the development work. Additionally, the question of how much money can be made selling books, t-shirts, mugs, etc, is never answered. O’Reilly Associates is frequently used as an example to be a company who has made money using this case. The reader should notice that O’Reilly Associates are not the people doing the development work. Indeed, it is never asked why all the O’Reilly books are not available for free or at least at manufacturing cost? This also brings up the question of why isn't book production "open"? Perhaps they are waiting to see if they could sell enough O’Reilly T-Shirts to pay their bills. So much for the accessories.
...the discussion of Linux among people you would expect to be its champions, such as programmers and computer-security experts who disdain Microsoft and work to build, maintain and protect sites and systems that use Linux, is more nuances — and less glowing. When I contacted one resolute Microsoft-hater, who works at what is probably the Internet’s busiest Linux-using commercial site, he replied immediately via e-mail that he was willing to detail Linux’s numerous shortcomings, but only anonymously: “I work with all these Linux zealots who have nearly fired me over my pokings at Linux.”
Most of Linux’s failings, according to my expert witness, are about what you would expect from a free operating system that exists in almost as many versions as there are people who use it. (Like Unix, Linux keeps mutating because the source code is available to anyone who wants to tinker with it.) “Linux isn't secure and it isn't stable,” my informant writes, with his usual bracing disdain for grammar and punctuation. “its a moving target that never really gets out of beta. sure people run production sites on Linux. I know a lot of these people. they don't get much sleep and have grown opaque from the lack of sunlight. I have admin'd large Linux shops. they require huge amounts of admin overhead, and if you want shit to really work you are going to spend alot of time manually fixing things. the number of outstanding security holes and lack of stable functionality is monumental.”
... Discussions of Linux’s weaknesses can be found on several Web sites, along with programs used by hackers to attack Linux sites. To outsiders, many of the exchanges between devotees of BSD, Solaris or other Unix variations sound opaque or shrill: (“It will be a cold day at the equator before L. Torvalds sets aside his ego for the sake of someone else’s better ideas.”). But much of the discussion is serious and alarming. Linux, according to these users, has serious security problems and a tendency to break down. The overriding theme in all of these messages and warnings is clear: If Red Hat and other Linux promoters hope to market an operating system that meets the demands of today’s market — to wit, a system that can run around the clock without faltering — their product is a long way from the Holy Grail.
An oft-quoted statement on the Internet is "The programming industry is the largest service industry pretending to be a manufacturing industry." This is more than just a catch-phrase -- it is the truth. The service of producing a piece of software, and the service of marketing it, is where money is spent. A thought experiment you can carry out to verify is this: in New York, a software vendor develops an office program. In Tibet, a software store receives only a single copy of this program. An office in Tibet requires three copies of the software - so they buy the copy that arrived in the software store and make two additional copies for use on their other two machines.
If the stock market is over-valued, there is a correction. If one company is grossly over charging for a product or service, there will be another company that arises to provide that same product or service at a reasonable rate. These principles are what is driving the free software movement: the market is being run by a few incredibly greedy individuals. Microsoft is not the Great Satan, it is merely a symptom of a broken system of intellectual property and morality regarding information. Most importantly, however, it is a company producing an inferior product and charging too much for it.
Linux will win, firstly because it is a clearly superior product to NT, but furthermore because the way in which it exchanges value is more in touch with the realities of the software world than the current system that is in place. Although there has been much hype recently about many commercial vendors porting software to Linux, it is out of fear of the possibility of having an open-source solution appear and completely destroy their market that most companies are doing so. Oracle's Linux announcement would certainly not have gone so smoothly if there were already an open-source equivalent of their software available. Informix's Linux support includes a free download of INFORMIX-SE, presumably in order to discourage development of truly free alternatives.
The reason that Microsoft has not jumped on the bandwagon yet and started developing for Linux is that if Linux succeeds, their development model no longer makes any sense. If quality software can be produced for an operating system which was freely developed, that would mean that quality documents could be created on a word processor that was freely developed - should such a product arise. That would eliminate the need for Microsoft to continue producing - as I believe most readers agree that Microsoft Word is bloated and over featured, and there is no reason to continue developing it, and Microsoft provides little in the way of services that extend beyond the software itself. The same could be said for Excel, or any other piece of software developed by the cost-software world.
The revolution is come - but it is a capitalist revolution, not a communist one.
Cathedrals, Bazaars and the Town Council
These are some of my thoughts on the Bazaar model that I figure are worth sharing. Its also a guide to how to completely screw up a free software project. I've picked a classic example of what I think is best dubbed the "Town Council" effect (although town councillors may think otherwise).
...The first thing to understand is that really good programmers are relatively unusual...
Secondly you need to understand that a lot of the wannabe real programmers are very good at having opinions. Many of them also catch buzzword disease or have some speciality they consider the "one true path". On the Internet talk is cheap.
The third part of any software project is what we shall call "the masses". They range between people who don't program but contribute massively in other areas -- documentation, helping users and artwork to the sort of people that are often used to argue that you should require a license to connect to the Internet.
<discussion of Linux 8086 project deleted>
The problem that started to arise was the arrival of a lot of (mostly well meaning) and dangerously half clued people with opinions -- not code, opinions. They knew enough to know how it should be written but most of them couldn't write "hello world" in C. So they argue for weeks about it and they vote about what compiler to use and whether to write one - a year after the project started using a perfectly adequate compiler. They were busy debating how to generate large model binaries while ignoring the kernel swapper design.
Linux 8086 went on, the real developers have many of the other list members in their kill files so they can communicate via the list and there are simply too many half clued people milling around. It ceased to be a bazaar model and turns into a core team, which to a lot of people is a polite word for a clique. It is an inevitable defensive position in the circumstances.
In the Linux case the user/programmer base grew slowly and it grew from a background group of people who did contribute code and either had a basis in the original Minix hacking community or learned a few things the hard way reboot by reboot. As the project grew people who would have turned into "The committee for the administration of the structural planning of the Linux kernel" instead got dropped in an environment where they were expected to deliver and where failure wasn't seen as a problem. To quote Linus "show me the source".
If someone got stuck they posted questions and there was and is a sufficiently large base that someone normally has both the time and the knowledge to reply. In the Linux8086 case the developers had long since walled themselves off. Given a better ratio of active programmers to potentially useful wannabe programmers would have rapidly turned some of the noise into productivity. The project would have gained more useful programmers and they in turn would have taught others. As with any learning exercise you are better off having only a few trainees.
There is an assumption some people make that you can't turn the "lesser programmers" into real programmers. From personal experience in the Linux project there are plenty of people who given a little help and a bit of confidence boosting will become one with the best. There are many who won't but enough that will. 
The lessons from this project, and others that went the same way (and sometimes died - remember the earlier Linux word processor projects) are fairly clear:
- Release code right from the start. It doesn't matter if its not very useful. The best way to sort a town council is to simply do the job then tell them it has been done. Linux, KDE and GNOME have all taken this attitude and all done well from it. You can argue about the right way to program for a lifetime. Once there is code out there people (whatever their skill) can play with it.
- Appreciate there are people who with a bit of help will contribute very much to a project. If their first patches are buggy don't put them down, explain why there is a problem and suggest solutions or places to look for examples of solutions. Every minute spent answering real questions helping someone work on a project will be paid back ten-fold to the project, and incalculably to society.
- Don't forget non programmers. I find it sad that many people when asked "name the most important five Linux kernel people" rarely name some of the most important folk of all -- the all to forgotten people who maintain web sites, change logs, mailing lists and documentation are as important.
Linus says "Show me the code". That is a narrow view of a real project. When you hear "I'd love to help but I can't program", you hear a documenter. When they say "But English is not my first language" you have a documenter and translator for another language.
- Try and separate useful people from the noise. It is hard to separate people trying to help from a mass of pointless discussion and in the Linux 8086 case I definitely did the wrong thing by giving up on that goal. How to remove just those who talk and do not do anything is a research topic 8).
So next time someone wants to vote on a project, or discuss issues for a month and then implement it - be warned. They may end up with the right solution. The odds are however in your favour for carrying on regardless. Just ask them to send you a patch when it works.
Beware "We should", extend a hand to "How do I"...
 As an example of this claim the original author of the Linux IPv6 code used to sit on irc from Portugal playing with a few basic ideas and asking questions. After we helped him figure some of the kernel internals he wrote probably 75% of the Linux IPv6 stack and was last seen working in the USA for cisco
Pulling on one end of the rope by Jordan Hubbard, The FreeBSD Project
... all is rosy and wonderful and this is basically another feel-good editorial about the magic of free software, right? Wrong, unfortunately...
To illustrate just how serious those problems can get, let's go back about 8 years to a period known as the "GUI wars" - a time of all-out battle between OpenLook, Motif and a host of lesser contenders. For those who were "there", the event probably needs no further description - the very mention of the GUI wars is enough to send cold shivers down the spine of even the most hardened Unix devotee. Not only did these wars cost Unix the desktop, they cost it a significant number of the few remaining ISVs (Independent Software Vendors) that it had....
The GUI wars also only added to an already untenable situation brought on by the SYSV/UCB split (AIX/HP-UX vs. Ultrix/SunOS etc), another ugly chapter which I won't go into here, making the typical ISV's life a real porting hell in return for access to a market which was already dwindling in comparison to the booming Windows market. If it were at all possible for the Unix market to sabotage itself more effectively during that period, I'm not sure how it could have been accomplished...
...Well, first there was the matter of Ego (spelled with a capital E). Everyone wanted to be the one to "own" the standard for how the GUI on this nifty new X Window System thing would look, and the dominant corporate players which eventually emerged also decided that they wanted to either sell their technology or keep it proprietary and distribute it only with their own workstations....
The X Window System itself was popular principally because it was a free and open standard with a non-aggressive copyright (you could productize it if you wished without being compelled to give the source away, helping to get it past the usual corporate legal department blockades without a fuss) and it was highly portable - I remember being highly chuffed that I could now use the same window system on the IBM PC/RT, Sun 3/50 and DEC MicroVAX machines in my office, a real luxury at the time. The people who wanted to create follow-on standards which they alone controlled, on the other hand, were simply not positioning themselves to take advantage of the X user community's rapid growth, nor could they leverage the work of all those potential volunteer programmers while the sources were being kept under lock and key, so to speak.
NIH was also a big factor, nobody liking anyone else's standard and deciding that a perfect standard was far preferable to having any standard (de-facto or not) at all. Of course, no such degree of perfection was ever achieved and the greater good was sacrificed in pursuit of short-term gains which never even really materialized - the opportunity for a effective and open standard was not only thrown away, it was thrown away for nothing. Thus ended the first age of Unix, many (including myself) believing that this was quite possibly The End since its community of developers, while highly capable tacticians, had proved to be abominable strategists and seemed to be winning battles in order to lose wars with depressing frequency.
Wind the clock forward to today, almost a decade later, and we find many of those things happening again and for exactly the same reasons. Don't get me wrong - it is a perfectly natural human desire to form clans and proudly wear the clan colors on Robert the Bruce Day, or whatever, diversity and competition being good things which encourage innovation and inspire people to greater heights of productivity. When you add Rampaging Egos to the mix, however, things get messy very quickly as the various clans decide that they want to be *the* clan, the only ones in line when the awards for best clan colors or most unique sporran are being handed out. Before long, rival clans are firing flaming arrows at one another and launching raids into each other's camps, generally making life difficult all around for a lot of folks who would really rather just get on with the business of living.
So it is somewhat today in the world of free software. Even though any marginally sane person would be appalled at the sight of two organizations like C.A.R.E and the International Red Cross fighting one another for the privilege of feeding starving children in Africa, for some reason the same behavior seems OK if it's just a bunch of people who write free software doing it. I don't mean to equate the process of feeding starving children with that of writing free software, far from it, but they're both "benevolent activities" which one would certainly hope could transcend any rivalries in carrying out their good works.
NIH is also still alive and well, many people choosing to do the same work over (and over) again just because it wasn't someone from *their* clan who wrote it or they have some deep-seated prejudice against anything done by clans who put green before red in their kilts - it's simply ludicrous a lot of the time! More importantly, the larger picture is being lost again, just as the entire Unix world is getting a second chance at life (a privilege which isn't usually afforded to software of this nature - once it dies once, it generally stays dead). The larger picture that people are losing sight of is that we're all truly in this together and, even if we don't explicitly go out of our way to help one another, at the very least we shouldn't be doing our damnedest to kick the crutches out from under one another.
A good example of keeping sight of the larger picture is FreeBSD's attitude towards its Linux emulation. It's not only very important to us that FreeBSD continues to run Linux binaries effectively, it's also what we suggest to those ISVs who are coming back somewhat cautiously to this "new" Unix market and obviously want to maximize their gains while minimizing risk. We tell them to port to Linux and not FreeBSD, even though we'd certainly love to have native binaries for anything and everything, and, by telling them to port to Linux first (or at all), we are giving them the best advice on how to get access to the widest possible segment of the free software market, one which includes but is not limited to us. That is the kind of "what is best for *all* the clans?" thinking I actively try to promote and essentially why I am taking the time out to write this editorial.
After 5 years of intermittent warfare, not just between the Linux/BSD camps but also within the various Linux and *BSD camps themselves (serving only to prove that *any* clan can and will fight another, even when they're all related :-), it's also not going to be one giant hug fest from now on just because people like me stand up and say that everyone really ought to get along - life's not that simple. What we can do, however, is to continue to *strongly* promote any and all ties between the various free software groups and also actively encourage users to familiarize themselves with each and every one of the various types of free software out there, whether they're currently "pledged" to a given cause or not. Not only will this experience help to shatter some of the walls of mistrust and general acrimony between the various clans, but it can also benefit those who are firmly convinced that they wish to stick with a certain one.
(see also Gnome/KDE debate -- Problems with the Qt Free Edition License -- NNB)
Yes, we really do want to use Free Software.
...We are building a large distributed system (about 200 processors over a 20 mile region) using Linux and Interbase only. Recently, a consultant hired by our client popped up with the questions I have heard soooo much about:
- Do you really want to base your system on "freeware?"
- There is no technical support, how will you get questions answered?
- Who are you going to blame?
Fortunately, my (Government) customer has had such a bad time with NT over the past couple of years, the questions were not even forwarded to us for review. The customer was happy to provide the following answers directly to the consultant:
- You bet, the quality of code is too high to ignore. By the way it isn't freeware, it's open source.
- We have given up calling Microsoft for support. Their support people seem to be incapable of answering technical questions that are deeper than simple "how do I boot my computer" questions. As far as we are concerned Microsoft does not support its product. The support we have received for Linux has been the best we have ever experienced from any vendor...
- Since Linux is very reliable, our trial systems were 100% operational from day one, the issue of blame doesn't surface. However, our experience with NT (SP4) gave us some insight into the "who to blame" mentality.
The customer has really begun to despise Microsoft with their lack of support and buggy operating systems. The customer's primary server is operational and has a zero item bug list, except in the operating system (NT). Since our overall strategy is to build the entire "second phase" system from Linux, we have the task of porting the existing server code to Linux, a task that ordinarily would take a low priority since a working server already exists.
The customer has overridden our own prioritization and requested that the Linux port be completed ASAP. Two reasons:
- At least twice a week the NT machine crashes or starts to behave strangely and a reboot is required.
- Remote system administration cannot be performed on the NT box so we have to talk the customer through troubleshooting instead of simply logging into their boxes directly from our site.
Since this customer now has about 30 Linux machines working in remote, hostile environments and those machines NEVER go down, one can understand their desire to get the NT -> Linux upgrade completed soon...
Unbeknownst to the checkout clerk ringing up a pair of slacks, Linux will replace DOS as the operating system at Jay Jacobs stores nationwide next year.
The clothing retailer last week became the latest commercial user to adopt Linux, the poster child of the open-source software movement.
Starting immediately, Jay Jacobs will deploy an application suite on Linux in its 115 stores and at the company's headquarters. Scheduled to be completed by the end of next year, the project will replace a number of antiquated, homegrown DOS systems that use the Paradox database.
The new application suite was developed by Apropos Retail Management Systems Inc., which said it will save around $1,000 per site by using Linux, and will not have to pay an operating system vendor for a site license. Jay Jacobs said it will save in the "hundreds" of dollars per installation.
"Cost savings are not the point," said Amy Wohl, president of Wohl & Associates. "If a company spends half a million dollars on a customized software program, a $10,000 savings on the OS isn't the point." Rather, she said, Linux achieves what the fractious Unix vendors have so far failed to deliver: a single code base that runs across multiple platforms.
Politburo Or Anarchy? by Jordan K. Hubbard
Politburo Or Anarchy?
Despite what some free-software advocates may erroneously claim from time to time, centralized development models like the FreeBSD Project's are hardly obsolete or ineffective in the world of free software. A careful examination of the success of reputedly anarchistic or "bazaar" development models often reveals some fairly significant degrees of centralization that are still very much a part of their development process.
To cite the Linux community as an often misquoted example of semi-organized anarchy in action, the entire Linux kernel is still primarily under the control of one individual (Linus Torvalds) and his immediate circle of kernel developers. Even leaving aside the kernel for a moment, the contents of each mainstream Linux distribution are themselves under the control of some distinct group of developers, from the primarily corporate (like Caldera or Red Hat) to the primarily volunteer-driven (like Debian or Slackware). This isn't necessarily negative, it's merely the price you pay for a certain degree of cohesion and consistency. In any case, you still need to get the "buy in" of someone like Torvalds or an influential developer for one of the aforementioned distributions if you want to see your changes adopted by a mainstream release. If they refuse, you're basically out of luck--you and your users can scream all you like but you still don't get a vote.
In attempting to refute this, some will state that a developer can put any changes on some FTP site or create a competing Linux distribution from scratch, but that's not what most developers do. They prefer to influence their personal distribution of choice, eliminating the need to maintain another set of custom patches with each subsequent release. The freedom to simply throw the changes out on the net with no "buy in" from the developers who make the integration decisions isn't a desirable form of freedom. It's also no more or less than they'd already get with a "politburo-controlled" release like FreeBSD, where anyone is free to put his changes up on an FTP server or otherwise diverge as he sees fit. In truth, both systems are effectively centralized development efforts and deal every day with some of the same upsides and downsides to this approach.
So what are these forces and conditions? First, every wide spread alternative social movement requires a powerful, even obvious, impetus against which to react: in the Reformation it was the Roman Catholic Church. In the early days of the Internet, it was IBM and mainframe hegemony. Today it is Microsoft. Just as the German Reformation enfranchised specific groups previously disaffected (specifically, Luther and the German princes), the Internet empowered individuals and groups previously outside the traditionally well funded technocracy that supported and in turn was nurtured by IBM. Linux has been propelled by the same forces. Currently, a major share of commercial software resources is concentrated around Microsoft products like a large low pressure area. However, such a coalescence of power and influence disenfranchises many for whom high cost and restrictive licenses (lack of freedom really) prevent full and easy access to computing resources. So alternative paths are sought. Like the weather, alternatives may appear randomly and then dissipate. Typically, an additional sustaining force, an opposing low pressure area, is required. For Luther this pressure was provided by the German princes, for the early days of the Internet it was provided by ARPA, and for Linux, it has been provided by the Internet community itself. In the case of Linux, the Internet community desperately needed a competent OS platform. AT&T had shut out many Unix users with restrictive licenses and high fees. UC Berkeley had crippled BSD by removing all vendor proprietary code which adapted it to the underlying hardware: you could study it but not run it! Many saw a potential in Andy Tanenbaum's Minix to counterbalance an increasingly unfree Unix. But Minix was incomplete, did not have critical mass and its source distribution became too restrictive. These conditions inspired the community OS effort, initially derived from Minix, which produced Linux. Linux became readily available and increasingly capable. When it aligned with FSF licensing and could support the powerful GNU tools as well as run on a wide range of inexpensive hardware, a truly useful operating system platform was born. The Internet community finally had a way to run a fully networked Unix cheaply and reliably with no strings attached.
Linux appeared almost randomly on the scene but quickly gathered into a well organized storm because it had a powerful force to react against. It also had a sponsor.
Therefore, the Linux "Bazaar" is not simply a loose collection of vendors and other proponents, motivated only by mutual recognition. The "Bazaar" really operates on a larger stage. When forces of the larger stage organize around a dominant restrictive group, a reactionary force is generated in the remaining community. Over time, this reactive force propels various alternatives. If one or more of these alternatives can find support (the Internet community in the case of Linux), then a new "movement" is born which is sustained and even enriched by the powerful forces of the larger stage. Ironically the more dominant Microsoft becomes, the more powerful the reactive forces become, and the more fuel is fed to movements such as Linux. If an unencumbered BSD had been available earlier running on inexpensive Intel hardware, BSD might have become the seed for this storm. But the same drama would have unfolded: thesis and antithesis on a dialectic stage whose imperative will persist until Microsoft runs out of energy or dissipates its focus. Microsoft has only to look over its shoulder at the cycle of hegemony and superannuation revealed by a once almost omnipotent old technocrat: IBM.
Beyond the Cathedral Beyond The Bazaar by Jonathan Eunice
One of the strengths of an open development model is that it allows (and even encourages) many people to share enhancements and defect fixes to software (collectively called "modifications" hereafter.) Frequently a modification is a result of a user satisfying an individual need and is made known to others by a mailing list or newsgroup. Keeping with the bazaar metaphor, this is equivalent to "advertising your goods." When the bazaar model described by Raymond is working well, (preconditions met, etc), there will be an abundance of advertised modifications. In this paper, I postulate that
The size of the bazaar (number of participants) affects the "health" and success of the bazaar, even if not a pre-condition to successful bazaar startup.
Not simply "size" but "effective working size" has important implications for the continued progress of the product and strength of the bazaar.
Debugging by testing includes factors which give the bazaar a very much smaller "effective working size"
There are alternative debugging methods which might be used to counter a small "effective working size."
There are activities and natural progression which tend to erode the "effective working size" of the bazaar over time.
[October 27, 1998] Open Source and Code Quality by Linas VEPSTAS email@example.com. BTW this is a very good page, with extremely interesting links. But the point of view proclaimed in the article IMHO require some critical assessment ;-)
To recast it in more radical words: the relationship between the software worker and the means of software production is so radically different than any other relationship that we have in out collective economic history, that a fundamental shift in the industry is inevitable. Although management fiat will never go away, the traditional models of the relationship between management and product will no longer apply to the software industry. The traditional models of the distribution of (software) wealth are already strained. The freedoms of choice coupled with the ability to cheaply, almost freely, make copies, will radically alter the software landscape, and require new economic theories to be created.
I strongly disagree. That's not that easy. This point of view reminds of communist religion. I believe if you were right than communism would be successfully build in the USSR. The problem with open source is that it does need corporate support to be successful. And the real trick is that sometimes corporations can afford to give the source for free (if and only if they have another sources of revenue): remember Digital and it's role in Linux development -- what they wanted was not Linux -- they just wanted Alpha to be more popular.
[October 17, 1998] The Free Software Bazaar -- by Axel Boldt <firstname.lastname@example.org> -- a very interesting idea -- site where you can put you own request for new free software and/or existing software modification for a small fee. the site can also be used for Free Software CD and book exchange/donations (for the price of postage)
It works like this: you request that a certain piece of free software or documentation be written or improved and offer something in return, usually an amount of money to be paid directly to the developer (or to some charity or other free software project). If you are a developer yourself, you can also turn it around and offer to write a specified piece of free software and request some money for it.
...three paths to getting up and running with Linux: the hard way, the most popular way and the easy way. First, I set up Debian GNU/Linux on my laptop. The Debian distribution is utterly free and totally non-commercial and eschews all but the most basic new-user hand-holding. Second, I installed the market leader, Red Hat 5.1, on my main workstation. And finally, I obtained a review copy of a VA Research Linux PC, preinstalled with all kinds of user-friendly goodies. It was obvious from the beginning that no sane person would recommend installing Debian GNU/Linux to anyone who hadn't already evinced some serious hacker tendencies. There's a certain sick satisfaction to be derived from attempting to do something the hardest possible way, but it sure isn't a fair test of Linux's usability. Red Hat, however, is acclaimed for its easy installation, and the newest release, 5.1, has been widely heralded as the easiest ever. Yet even so, new users attempting to make the transition from Windows are likely to be taken aback by the convoluted steps necessary to correctly partition their hard drive for use with Linux. And even if they make it past that step, what then? Red Hat CEO Bob Young claims that the bulk of its sales is generated by non-Unix users. I'm skeptical. As the Red Hat installation manual makes clear, familiarity with basic Unix concepts is required to make any effective use of Red Hat Linux. Page 8 of the manual even recommends purchasing a book on Unix. This is good advice -- but it's not what Windows 95 users looking for an alternative to Microsoft will want to hear. But installing any new operating system is often filled with pitfalls. How many average users, whose main interest in a computer is running a word processor and getting their e-mail, are ever going to attempt such an overhaul?
Surely the best test of Linux's usability is to test-drive a brand new computer with the operating system already installed -- preferably with some kind of handy-dandy graphical user interface like KDE set to go? I got to Tetris just fine, but my block-manipulating joy dissipated almost immediately as soon as I began my very next task -- installing WordPerfect for Linux from a Red Hat CD-ROM. It should have been simple. But it wasn't. To access the files on a CD-ROM in a Unix system, one must first "mount" the CD-ROM. KDE offered no obvious way to do this. In the end, I had to retreat to a command prompt and type in an arcane string of commands sure to be utterly unintelligible to a Windows 95 user. I enjoyed solving the problem -- which, to a Unix aficionado, would have been quite trivial. But accessing the CD-ROM should not require typing "mount -t iso9660 /dev/cdrom /mnt." Such problems are far from insuperable; indeed, at the rate at which things change in the Linux world, they could well be solved within months. But at this moment, it's clear to me that Linux is not yet an alternative for the average Windows user. It still has a long way to go.
Whether it will ever get there is impossible to predict. In the meantime, Linux's unfriendliness to users who demand utter point-and-click simplicity should by no means rule it out for everyone. For the computer-literate user -- the person who is not afraid of a challenge and is eager to learn -- coming to grips with Linux can be hugely enjoyable. Linux devotees regularly tout how readily help and support can be obtained on the Net, and I found that these claims are not exaggerated. Every time I posted a question, I received loads of immediate, friendly and exhaustive help.
...I find it fascinating that so many mainstream publications would suggest that Microsoft is threatened by Linux.
The idea itself doesn't surprise me. It's the spin -- or, rather, the conspicuous absence of it. The recent Linux coverage lacks pundimosity. No, you won't find "pundimosity" in the dictionary. It is an invention of my own. It stands for the animosity many pundits exhibit toward technologies outside the mainstream. If you want historical examples of the inflammatory rhetoric that is pundimosity, go to your local library and search trade publication archives using keywords such as OS/2, OpenDoc, and network computing.
Perhaps one reason you can talk about Linux without wearing an asbestos suit is that there is no single leader to vilify. The network computer was vulnerable to pundimosity because its primary evangelist, Larry Ellison, is the kind of public personality people love to hate. As another example, anti-Java pundits were fond of accusing Scott McNealy of wanting to replace Bill Gates as software platform dictator. (As if there's something honorable about sticking with Windows because Gates' competition wants to make money.)
...It is also difficult to undermine the credibility of Linux advocates. They are perceived as the good guys. The ones who charge you for buggy software and keep the source code secret are the nasty black hats. The white hats keep source code open and often donate their time and effort for the good of the cause. As a result, to quote Red Hat Software President Bob Young, "attacking Linux devotees would be like attacking Mother Teresa." Any effort to do so would surely backfire.
"A skilled net-surfer with a fast modem can routinely download volumes of the kind of high-grade information that old-style intelligence services once had to pay for with time, sweat, and money if not blood."  ...
...A National Knowledge Strategy should aim the elimination of various "iron curtains" between nine major sectors and the creation of an "information continuum" that focuses on:
- "CONNECTIVITY:" By providing leading representatives of each of the nine sectors with the necessary technical kit to harness (not impede) progress.
- "CONTENT:" By inciting all parties to maximize the amount of information they put on-line. Intelligence Newsletter interpretation of this clause is the increase of information available to citizens.
- "CULTURE:" By understanding the importance of accelerating the integration of ethnic populations and the economically impoverished. This is in particular reference to immigrants who can be used as interpreters and translators with a unique cultural insight.
- "COIN:" Call to a reduction of government and private annual waste spent on information technology and development. Typically between 10 and 20 billion dollars will be saved yearly. ("COORDINATION" in )
- "C4 SECURITY:" By identifying flaws in existing Command, Control, Communication, and Computer services. (Also referred to as "C4I" in the other papers and interviews)... ... ...
...Al Gore and the National Information Infrastructure (NII) are "all connectivity and no content," concludes Mr. Steele "sadly" [20, 23]. "This Nation [US] does not have a National Knowledge Strategy, and there is no one in Washington with any clue as to how to devise one."
... ... ...
Other intellectuals resist the promises and "hype" of the "Information Age" on ideological grounds. John Zerzan sees in this "information revolution" more alienation and anxiety. "Second Wave" enslavement of labor will be no different from its "Third Wave" counterpart. "The Information Age 'office of tomorrow' will be no better that the sweatshop of yesteryear."  The future is no bright either. The "Universal Dead Zone of Civilization" will be infanticized by more computerization. The problem is internal. An emasculated society that cannot resist "consumerism" and its modus vivendi cannot transmit "experience" (which is the chore of civilization).  Before empowerment, we need to answer a fundamental question: Can the "world-that-enforces-our-inability-to-change" be forced to change? Daniel Brandt wrote some thought provoking arguments along these same lines in his "Decline of American Journalism" piece [2, 28].
One final trend, a "Jeffersonian Vision" , is represented in the persons of John Perry Barlow, Mitch Kapor, Jerry Berman and the "INTERNET-based" Electronic Frontier Foundation (EFF). While recognizing in this technology the "most liberating development in the history of humankind," they fear it could become the surveillance system that monitors future generations. New and fresh readings of George Orwell's "1984" resurfaced on the interplay of technology, privacy and the role of "Big Brother". 
The new Unix alters NT's orbit: The re-emergence of Unix threatens to modify the future direction of NT -- By Nicholas Petreley. NC World, April 1998.
"...The future of Windows NT is threatened less by the superiority of its competition than the inferiority of Windows NT, which results from Microsoft's misplaced priorities. As we demonstrated in the first installment, Microsoft's design decisions are driven more by its attempt to protect its desktop monopoly than by technical excellence. As evidence, Windows NT is less stable than Unix because it is more vulnerable to clashing shared libraries (DLL conflicts). But it is only left vulnerable in this way because Microsoft likes to overwrite existing system DLLs with its applications (thus secretly "upgrading" the operating system in ways no competitor would dare to do) to gain unfair leverage against its competition. "Fixing" the DLL problem is technical simplicity. It simply isn't desirable from Microsoft's perspective. In addition, Windows NT has a dangerous driver model because it is willing to sacrifice stability for speed in an attempt to win benchmarks against competing operating systems. Until now, these compromises have worked because Microsoft's domain has been limited to the desktop. It is only now beginning to infiltrate the departmental server market, and is attempting to challenge higher-end systems. And as Intel-based Unix draws attention to the differences in quality between NT and Unix, the prospect of a wholesale switch to NT is looking less and less appealing."
Archives - Intranet Explorer -- Linux Grows Up -- Red Hat's commercial Linux beats NT at its own game
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to to buy a cup of coffee for authors of this site|
Last modified: March, 12, 2019