Slashdot Mirror
Countries Ponder: GNU/Linux vs. Microsoft
koody writes: "IDG has an overview of how many countries are getting drawn into the debate over the relative merits of using open source software rather than Microsoft Corp.'s Windows applications. Seems like many countries would be slowly moving towards the open source community, while a few still pledge allegiance to Microsoft."
I really don't care what government decides to waste its money on (after all, if it wasn't software, it would be gold toilet seats).
But I do care when government sponsored research into software is used by companies to make money. Last I checked, I didn't give Sun/MS/et all my tax dollars to make them richer. I want that research GPL'ed so that I know its available, that I, as a tax payer who paid for the R&D gets the benifits, and that it can be made even better by the world (and thus can help my government/business/etc).
52 Weeks, 52 Religions with John Hummel
You forgot "indivisible." Windows isn't modular, remember? :)
Government administrators should note that it is their duty to insure that all government work be done on completely open systems. The citizens and taxpayers of a democracy must have full access to all documents, even 40 or a hundred years from now. There is NO room in a democracy for proprietary, hidden ways of doing things.
What we need is not a better monoculture, but a polyculture (is that a word?) In a polyculture, one company (MS) can't create a format that's impossible for anyone else to implement properly and expect it to be widely used, because users will EXPECT interoperability. They'd be shooting themselves in the foot. By the same token, in a polyculture you have many different products that foster true innovation. I mean ... as much as office sucks, some parts of it have been truly innovative (some parts of Outlook, Excel.)
Hell, in a monoculture half the time software isn't compatible with its previous version (think Office 95 vs. office 97.)
I wouldn't want any government to mandate *one* operating system. Instead, I think that governments should mandate operating system diversity. That's the way to get true, robust reliability and ultimately save money.
"He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
It cited compatibility problems, namely among users trying to receive Microsoft World documents. Microsoft World Documents?? Has Microsoft taken over the World format already? Otto Schily, the German Federal Minister of the Interior, announced last Monday a deal with IBM to promote, for the pubic sector, hardware and software products that support Linux. The pubic sector?? I thought that was my private business! Oh wait, an "L" accidentally got moved. Calming down now.
"As my first act as Software Architect, I will create a grand army to counter the increasing threat of the Open Source seperatists"
War ensues..."Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
> Do they it 'cos they see the benefits of open source or are they just anti-USian ?
> Like the "evil NSA key windows backdoor" rubbish.
> I doubt they would ditch Windows if it was produced by a company of their own.
And what if it would be that way?
As an european country I would find it hard to rely internal security soly on an american company. What if there is a bug, country XYZ can't do anything about it until some guy in the USA fixes it. Now what if the software would be used for something important? And what if we just would have diplomatic problems because of a embargo of product X? (maybe about cars, fuel, meat, who know what...)
It should be the same reason why we europeans or any other country can't use the GPS for anything important. (like i.e. steering the trains with it)
Here the situation is quite obvious. GPS can be turned of with a switch in the USA. Yes GPS is useable as comfortable add-on but non USA countries can never rely on it. Thats why the EU is planning to do it's own positing system, not because it's better than GPS, but we will be able to rely on it.
Same goes for software, a non USA country can not safely use unexchangeable parts like microsoft products for anything important. It's always important to have at least two possible sources for a product, if not more. And windows fills this requirement not.
Okay for the non-geeks, why does OpenSource software fill this need? You still don't have more than one source, _but_ you get all the construction plans with the software, plus the right to actually use them. As a country in time of need you are able to fix possible problems yourself.
--
Karma 50, and all I got was this lousy T-Shirt.
>can't use the GPS for anything important. (like
>i.e. steering the trains with it)
You wacky Euros. Here in the US, the TRACKS tell our trains where they can and can't go.
-l
Whoa! Bill should pay attention to what his marketdriods say. To wit:
Austria:
One of Microsoft's flagship government customers, the Federal Ministry of the Interior in Austria, is the first government body in Europe to become a member of Microsoft's Shared Source Initiative. As part of the program, the Austrian government is allowed access to the Windows XP source code. Program benefits, according to Microsoft, include better understanding of the technical underpinnings of the operating system, better protection against security vulnerabilities and a resource for writing custom applications.
*blink* Wha...? *blink*
Microsoft admits - in full view of the world - that having access to the source improves the security and useability of an Operating System. Didn't some two bit think tank outfit just say that having access to the source was bad?
That's a keeper if there ever was one - Microsoft just made the case for Free Software in spite of itself.
Soko
"Depression is merely anger without enthusiasm." - Anonymous
Nor should tax dollars be spent on Bic pens, or Bostitch staplers, or Lockheed jets, or any other product built by an evil moneygrubbing company!
Please...
Like it or not, years ago M$ was the logical choice for software. And, like it or not, M$ has advanced, through a common user interface, the state of desktop computing.
Now...that situation may be changing, with the advent of new open source tools and applications that actually work and can be used by the average office worker. BUT, an entity the size of (name your fave countries government) cannot change overnight.
Give it time.
That's not a fair generalization. The government can easily switch to another brand of pen, stapler, or jet without worrying interoperatibility with a existing supplies of paper or the existing air traffic control system. There aren't alot of security issues for a government office using a monoculture of Bic and Bostitch. The government is free to disassemble any pens, staplers, or jets they buy to search it for spying devices, attempt to repair problems, hire a third party to hire problems, or customize the products for their use. There isn't alot of risk of a license audit coming from Bic, Bostitch, or Lockheed.
It is a standard that defines the expectation of people receiving software products from a company.
There is a ton of variety in the world of GNU/Linux with a multitude of different vendors competing for the attention of Linux users. It is, in fact, the monoculture that Microsoft causes its products to exist in (by making interopability as difficult as possible) that is at the root of the discontent we are seeing around the world that is shifting the momentum away from Microsoft.
In fact, open source is the opposite of what you argue. By following standards, open source guarantees its users they will continue to have choices.
Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
from the article:
"Thailand:
A government-subsidized technology development group, known as the National Electronics and Computer Technology Centre, or Nactec, announced in April that it has developed its own package of open source software for use o n government desktop computers and servers. Linux-SIS (School Internet Server) for servers and Linux TLE (Thai Linux Extension) for desktops are based on the version of the Linux operating system from Red Hat Inc, a Raleigh, North Carolina, software company. Nactec has made the software freely available to government groups and small businesses. The project , government officials said, aims to narrow the gap between pirated software and legal software use, and promote local business development."
I submitted a story on this a while back, so I will elaborate here. The agency is actually NECTEC (not Nactec), and they have developed a Thai language distro. Thai is problematic because of it's eight bit characters, and vowels that can appear in front, behind, above, or below the consonant. Modifying the many English 7 bit centric apps in RH to work with Thai was no small feat. They also have a web page devoted to training ex-windows users. At this point, it is incomplete.
This is an attempt to curb the estimated 93% piracy rate in the country. It is causing all kinds of problems with the WTO. This distro has been featured front page in four major computer magazines in the last three months. The general review by all the magazines was that it is good, but shouldn't replace Windows. In a primary example of the poor quality of the reviews, the reviewers were unable to mount their windows partition or change the encoding on a web page in konqueror. I am using this distro right now, but have used the apt-get utility which comes pre-installed to dist-upgrade to RH7.3, and everything still works.
Tangentially, Sun has released an all Thai version of open office, called Pladao ("Star Fish") for free, and it is being widely accepted by the mainstream media because it runs on Windows. Solaris and Linux versions are also available. I use this program regularly along with OO 1.0.0 (why the extra 0?) on my machine. It is being written of and reviewed as open source, even though no source is available, so I am confused. I suspect people are confusing OS with "free to use."
Thailand is committed to OS, and has computer standard for OS retail machines and advocacy programs in place. The government wants to stop sending so much of its meager supply of cash to the west.
Put identity in the browser.
This is a myth, and has been debunked so many times that further repetition can only be the result of intentional ignorance. I don't see how this Microsoftian FUD helps the open source cause.
Here is one of the better posts on the issue by screen name "adamba":
I worked at Microsoft for ten years, most of it on the core Windows NT/2000 (hereafter referred to as NT) networking code. [...]
I know a lot about the TCP/IP stack that is running on NT. Here is a short history of it (some of this may also be told in the book How the Web Was Won, but I haven't read it):
The original plan for NT was that a few members of the core NT team (which numbered about 15 developers) would write all the networking code. However, in 1990 a small team was started up in the LAN Manager group at Microsoft to do some of that NT networking work. Eventually that team moved over to be a part of NT (this coincided with the IBM-OS/2 "divorce", if anyone is interested).
Microsoft's networking software at the time ran over a network protocol called Netbeui, but it was decided that TCP/IP was gaining in importance, and should be included in NT. In addition, the user-mode API associated with Netbeui, which was called Netbios, was too Netbeui-specific and couldn't be adapted to allow user-mode access to TCP/IP. As a result, the decision was made:
1) To put a TCP/IP stack in NT
2) To adapt the sockets user-mode API for NT
#1 was solved by licensing code from a company called Spider Systems. However, Spider's TCP/IP stack was written to run within an environment called STREAMS, which was a wrapper that specified how the various parts of the stack would communicate with each other (TCP/IP is really several pieces of code -- two of which are TCP and IP -- layered on top of each other. Most network protocols are like that, which is why they are referred to as "stacks"). As a result, STREAMS also had to be ported to NT.
#2 involved the creation of the winsock API, which persists today.
It was recognized that using Spider's stack was a temporary measure, because nobody really wanted a stack that depended on STREAMS and its associated overhead. So, a short time after this, work was begun on a new version of TCP/IP, written entirely by Microsoft.
Along with Spider's stack came versions of various TCP/IP-related utility programs, such as ftp, rcp and rsh. Those were ported from BSD sockets to winsock (not a huge change) and bundled with NT.
Now, some of Spider's code (possibly all of it) was based on the TCP/IP stack in the BSD flavors of Unix. These are open source, but distributed under the BSD license, not the GPL that Linux is released under. Whereas the GPL states that any software derived from GPL'ed software must also be released under the GPL, the BSD license basically says, "here's the source, you can do whatever you want, just give credit to the original author."
Eventually the new, from scratch TCP/IP stack was done and shipped with NT 3.5 (the second version, despite the number) in late 1994. The same stack was also included with Windows 95.
However, it looks like some of those Unix utilities were never rewritten. If you look at the executables, you can still see the copyright notice from the regents of the University of California (BSD is short for Berkeley Software Distrubution, Berkeley being a branch of the University of California, for some reason referred to as "Berkeley" on the East Coast and "California" on the West Coast...and "Berkeley" is one of those words that starts to look real funny if you stare at it too long - but I digress).
Keep in mind there is no reason to rewrite that code. If your ftp client works fine (no comments from the peanut gallery!) then why change it? Microsoft has other fish to fry. And the software was licensed perfectly legally, since the inclusion of the copyright notice satisfied the BSD license.
I won't even swear on a stack of bibles that the "new" TCP/IP now shipping in NT/2000/XP and Windows 95/98/Me is completely free of the old code from Spider. Since I don't work there I don't have access to the source code. Certainly some parts of TCP (the checksum calculation comes to mind) are the same everywhere and once someone has written an optimized version, why rewrite it? And once again, this would be perfectly legitimate for Microsoft to do under the license.
But it is certainly misleading of the Wall Street Journal to say that BSD code is used "deep inside" the NT networking code, unless they mean the STREAMS wrapper itself, which I believe is still there in case someone wants to write a transport using it (I think there is an OSI TP4 STREAMS transport lurking somewhere out there, if anyone cares - but I just checked, nobody does). But the TCP/IP in NT certainly doesn't use STREAMS.
And implying that the TCP/IP stack uses BSD code is also false. As I said above there may be small vestiges of it in there, although I doubt it. Anyway the FreeBSD programmers who reported all this to the Wall Street Journal can't see the NT TCP/IP source either, so they can't have been referring to that.