Cuba Launches Own Linux Variation
willclem writes "According to Reuters, it seems that Cuba has launched its own variation of Linux in order to fulfill its government's desire to replace Microsoft operating systems. 'Getting greater control over the informatic process is an important issue,' said Communications Minister Ramiro Valdes, who heads a commission pushing Cuba's migration to free software."
Seeing as you have to go through great hoops, (most of them not legal), to get anything Cuban around here, how is the Cuban government running american products? I suppose they purchased from south american, european or asian retailers, but one has to wonder, how many legit copies of windows are in Cuba? Can Microsoft go in to sue the Cuban government about illegal copies? What jurisdiction would Microsoft have to keep Cuba from enjoying their cracked copies until communism dies?
Is it sad that I am more likely to recognize you and your posts by your sig than your name or UID?
Somehow I have a hard time picturing penguins in Cuba.
I don't.
How can I believe you when you tell me what I don't want to hear?
It is kind of sad.
A Good Troll is better than a Bad Human.
Yes, in stark contrast to the politically flawless United States, having no record of any government involvement with production of open source or proprietary software. Pleeeeeaaaaassssssssseeeee.
Sam ty sig.
I dont see the big deal here. Governments would love to have direct control of operating systems, so that they can place undocumented "features" inside them. Even if they release the source code (which I suppose they have to, theoretically), 99.99% of the users who will be employing their distro will not be able to understand what source code even is, or how to interpret it.
Well, I guess there are still people (the people who are reading this message) who will be able to report any backdoors/home phoning they notice placed into the source, but that will only make a difference provided:
1- Cuba releases the source
2- The distro is popular enough to have people using it
3- People carefully examine the source code
4- Said examiners are able to spot a problem
5- Said problem is heard by the end users of the distro
6- End users of the distro have options as to what operating system they are able to use, if it is mandated by the government, they pretty much have to live with it.
I'd love to see the logo be an image of Fidel dressed-up as a penguin.
I'm pretty sure the guy has a sense of humor. When I was a kid, I was a "shortwave listener" (before I got my ham license) and sent of to Radio Havana (among others) for a "QSL" card, confirming that I had heard their station.
Besides the card, I got other periodic mailings, including a Christmxxxx New Year card one year, bearing the cartoon likeness of Fidel Castro, laid-out on the dining-room table as a pig, complete with an apple in his mouth. I kid you not. I'll bet he had a big laugh.
Wish I still had it - could probably sell it for a bundle on eBay!
(Other "interesting" material I received included a copy of the Little Red Book from Radio Peking, and a subscription to China Pictorial - a beautifully-printed bled-to-edge full color magazine with gorgeous pictures of fields and tractors...)
There market is about to shrink in a BIG way. If they were smart, they would jump on a couple of distros of linux and make sure that they are the standards. Adobe, Intuit, AutoCad all have programs that are in demand. If they port to this, they can quit having to compete against MS on MS's turf. More importantly, they would get a WHOLE NEW market with minimal competition.
I prefer the "u" in honour as it seems to be missing these days.
Chevy had some trouble in Mexico and South America with it's 'Nova,' because the name is a play on no va, or it doesn't go.
Funny that Cuba would pick such a name for their new OS.
Message contains 1 attachment: spam.gif
Gah. Are you retarded or what? The whole fucking point of the article is that the Cuban government wants to be able to look for back doors in the software. They're not relying on the open source community being "more aware and quicker to patch said vulnerabilities", at all. This is simply a case of Cubans saying "why are we running software we can't even inspect?"
How we know is more important than what we know.
Hey, Americans are dumb (and really, the only place where being "socialist" is something you have to worry about really would be the US). Many probably still associate Russia with communism, even though it was socialist when it was Soviet and hasn't been Soviet for ~20ish years now.
I know people who grew up in Eastern Europe. They had home computers, mostly C64s and the like imported at vast expense from the West. Apparently in Russia a few people had cloned machines, mostly from designs from Sinclair in the UK.
On the other hand I met someone who worked in a chip factory in East Germany. Everyone knew what they were doing was very far behind the west. In fact there was a joke that the first 1Mhz processor in the Eastern Bloc would fly in on a cruise missile.
This page reckons that the Soviet Block was 10-12 years behind the West at chip production.
http://www.cpushack.net/soviet-cpus.html
There were also CoCom restrictions on selling technology. You can see how this worked with this example
http://www.canberra.edu.au/~scott/C=Hacking/C-Hacking13/os.html
Bootstrapping was the first major problem. How do you start a new computer and debug its OS if don't have an OS on the computer? From earlier systems I already had a small monitor program - directly burned into an EPROM - able to load binaries through a serial line. Getting the MMU (74ls610) was the second problem, because it was on the CoCom list, and it was not allowed to export to eastern countries. (Although I don't live in an eastern country, this posed some difficulties...)
So if you were an Eastern Block engineer you'd have to get someone to buy this MMU on the black market somehow which cost precious hard currency. Or you could get some local factory to make a clone. Obviously either are harder than buying it from a mailorder shop.
My guess is that the Cubans set up a front company and buy PCs somewhere in the West and then probably pirate the software.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
The point here is not really about socialism or communism, but about countries that are neither free nor open embracing software that is.
(Imagine explaining 'Free as in speech, not free as in beer' in Cuba or China. Or Russia, for that matter, with its open season on investigative journalists.)
People strongly committed to the idea that there is some kind of intrinsic link between FOSS and political freedom might want to chew this over.
One thing I am concerned about is that Linux is a moving target. Will an app developed today work on a distro 10 years from now, without having to rewrite it to match the modern libraries?
The good thing it that nothing will stop distro-makers from packaging several libraries or several generations of them.
In fact most installed Linux around have both QT and GTK2 installed, because these are use by lot of software. As a similar example, during the KDE3-4 transition you're bound to find both QT3 and QT4 installed on lots of machines. Up until recently you had GTK1 and GTK2 installed together because lots of legacy application didn't make the move.
Also if some legacy interface is *that much* popular, newer version will include wrapper code :
- pulse-audio has lot of interface plugins to communicate with applications targeting only ALSA or ESD or ARTSD.
- latest GTK2 version has a GTK1 wrapper for legacy applications
- etc.
So even if Linux is a moving target, its modularity gives you a lot of room for maneuvering.
(Even if I personally think that, once in a while, restarting a project a fresh and including latest input between the original version and now isn't bad. As long as you make your users aware that the new version won't be as good as the old one for the first duration. cf. KDE3 vs KDE4).
The only point where Linux is a moving target is when writting driver code, because you can only have 1 single kernel to target and thus only 1 single API (mostly). For example, you can't (easily) mix 1.x, 2.x and 2.6 driver models.
But that's not what most applications developpers have to worry about.
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]