Language Selection

English French German Italian Portuguese Spanish

Why Chicago Chose Linux

Filed under
Linux

As the platform architect for the city of Chicago, Amy Niersbach had a decision to make. The city’s IT infrastructure needed some refreshing. Chicago wanted to rid itself of its vintage mainframes, and its aging Sun Solaris servers were costly to maintain.

The Windy City needed a major migration. But to what?

An obvious choice would have been the Windows server, partially because the city’s infrastructure – which includes “a little bit of everything,” Niersbach says – already uses a major Windows element.

But she opted to avoid Windows. “When you think of Windows server, you think of rebooting the server, of always having to apply security patches. You think of viruses,” she tells Datamation. “Not that it’s not great for some things, but Linux and Solaris prove to be a lot less headaches than any other platform.”

With her preference for Linux, she went shopping. "We evaluated Suse Linux. They were a good runner-up, but at the time they didn’t have the Oracle certification.” Since the city relies so heavily on Oracle, this was a deal breaker.

Full Story.

More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more