Language Selection

English French German Italian Portuguese Spanish

The offensive Microsoft anti-Linux netbook offensive

Filed under
Microsoft

The netbook explosion proved that these days the killer app is mobility, portability and frankly just plain being online anywhere.

Linux had the edge; after all, netbooks were cheap. Sure, not so cheap you’d find them in the impulse purchase shelves at supermarkets while waiting in line at the checkouts but certainly cheap enough that you could justify buying one without too much effort and with little buyer’s remorse later on.

Netbooks were cost-effective enough that they put computing power into the hands of students, the elderly and others who might not otherwise obtain a laptop or desktop computer.

To keep the price down manufacturers obviously used hardware components that were far from the bleeding edge and they used software that added nothing to the total cost. Linux was a natural choice; its zero dollar licensing was a natural fit for netbooks.

Microsoft wasn’t so happy with this situation and made a dramatic u-turn.

rest here




Also: When netbooks first came along, they almost all ran Linux. Microsoft, which was stuck with the resource pig known as Windows Vista, simply couldn't compete. So, reluctantly, Microsoft gave Windows XP Home a new lease on life and sold it below cost to OEMs (original equipment manufacturers) to kill the Linux desktop at the root. For this cost, Microsoft was successful, but now Microsoft is about to blow it by replacing XP Home with Windows 7 Starter Edition, which is crippleware by any other name.

Microsoft has been selling crippleware, software that's deliberately had features removed, for some time. This is why Microsoft has been claiming that Windows 7 will run just great on netbooks. Except, now they're not. Now, Microsoft is telling us that instead of full-strength Windows 7, you'll be getting Windows 7 Starter Edition instead.

Will Microsoft blow its netbook lead with Windows 7 crippleware?

More in Tux Machines

Red Hat Announces General Availability of Red Hat Enterprise Linux 5.11

Red Hat, Inc. RHT, +0.07% the world's leading provider of open source solutions, today announced the availability of Red Hat Enterprise Linux 5.11, the final minor release of the mature Red Hat Enterprise Linux 5 Platform. Red Hat Enterprise Linux 5.11 reiterates Red Hat’s commitment to a 10-year product lifecycle for all major Red Hat Enterprise Linux releases and offers a a secure, stable, and reliable platform for critical enterprise applications. Read more

New Code Starts Lining Up For X.Org Server 1.17

X.Org Server 1.17 is planned for release at the start of 2015 and thus puts the closing of the merge window in the middle of October. While some xorg-server 1.17 code has already landed, more is on the way. X.Org Server 1.17 will continue with refining the in-server GLAMOR code that was merged with 1.16 for 2D acceleration in a generic manner over OpenGL. X.Org Server 1.17 is also looking to integrate the universal KMS mode-setting DDX driver. Keith Packard on Monday also shared several other code branches he's looking at as material for the 1.17 release. Read more

More Intel DRM Changes Queued For Linux 3.18, Including Old i830M Fixes

With the drm-next merge window for Linux 3.18 closing, Intel's open-source developers have submitted another round of changes for ultimately landing with the Linux 3.18 kernel. Intel has already sent in multiple pull requests of new DRM graphics driver code to push into drm-next for the Linux 3.18 merge window. Among the changes include various Cherryview improvements for the forthcoming low-power Atom SoC, and code clean-ups and continued Broadwell tweaks. Another Git pull request landed in drm-next over the night. Read more

Speeding up the Debian installer using eatmydata and dpkg-divert

The Debian installer could be a lot quicker. When we install more than 2000 packages in Skolelinux / Debian Edu using tasksel in the installer, unpacking the binary packages take forever. A part of the slow I/O issue was discussed in bug #613428 about too much file system sync-ing done by dpkg, which is the package responsible for unpacking the binary packages. Other parts (like code executed by postinst scripts) might also sync to disk during installation. All this sync-ing to disk do not really make sense to me. If the machine crash half-way through, I start over, I do not try to salvage the half installed system. So the failure sync-ing is supposed to protect against, hardware or system crash, is not really relevant while the installer is running. Read more