Slashdot Mirror
The Steady Decline of Unix
stinkymountain writes "Unix, the core server operating system in enterprise networks for decades, now finds itself in a slow, inexorable decline, according to Network World. Jean Bozman, research vice president at IDC Enterprise Server Group, attributes the decline to platform migration issues; competition from Linux and Microsoft; more efficient hardware with more powerful processor cores; and the abundance of Unix-specific apps that can now also run on competitor's servers."
Combine that with the fact that Solaris is now in the hands of Oracle, who are squeezing out everybody who doesn't have a support contract and pissing off people who used to use it ... or that HPUX is still in the hands of HP (where technology goes to die) ... and what's even left?
AIX is still around, but I have no idea of how widespread. Beyond that, I'm hard pressed to think of another commercial version of UNIX I've encountered. (That doesn't mean they don't exist, but they were never in any shops I was in.)
That pretty much leaves Linux as the primary UNIX-like-thing for most people.
Lost at C:>. Found at C.
Oracle is the reason that my employer is switching from Solaris to Linux. We were one of Sun's biggest customers, too.
Errol Rasit, research director at Gartner, concurs that the primary cause of Unix weakness over the past decade is migration from the RISC platform to x86-processor based alternatives, which can run many Unix workloads, usually at attractive price/performance ratios.
x86 has been implemented on a RISC based core ever since the PentiumPro. RISC won. It didn't wither away. That transition made possible a performance boost allowing Intel to compete against the home-grown processors of the traditional Unix vendors who lacked the cash to invest in fab advancements needed to match pace.
Such are the fools pandering their vaunted "analysis" to the media these days.
I am becoming gerund, destroyer of verbs.
My experience was on AT&T Unix System V. I used to jokingly refer to it as REAL UNIX with a hint of faux snobbery and a straight face.
While working on a Linux system, I was using some command line utility (doesn't matter) and the command kept wrapping. Ran it - errors. Retyped - errors. Retyped - finally worked.
Anyway, a skilled Linux user was watching me, typing away and then running my command - the syntax worked like it was a AT&T System V UNIX, BTW.
Said Linux dude said, try this - and he proceed to do the same thing with the same program but with like one or two flags and then the args.
It worked.
There have been quite a few time savers (I won't call them improvements) built into Linux.
I can't blame them - some of the most common things that we did in Sys V were overly verbose.
Anyway, wanted to share that - gotta go; there's a Matlock marathon and it's Pizza and Banana pudding night! Betsy has got the hots for me and she so young - 68! I'm gonna have a GOOD time tonight!
No kidding. I had to go back and read the headline twice after reading the blurb and the article before it made sense.
Well, no DUH that Unix is loosing ground to Linux. I honestly cannot remember the last time I saw a data center with true UNIX machines (oh wait, yeah I can, it was 14 years ago, unless you want to include OSX as a UNIX, in which case that was five years ago). This has been happening for like 15 years.
When I saw the headline, I was thinking "*nix is loosing ground to Windows?" (which also wouldn't have been a huge surprise).
No news here.
In the Engineering CAD world, Unix has nearly run its course. All companies have dropped Unix support for the newest versions and only some maintain Linux/OSX versions for newer unix-like machines. Most are Windows only. Automotive companies, which are notoriously slow in technology adoption have mostly abandoned UNIX
Ford will retire their UNIX workstations (HPUX) for suppliers and customers in February 2014. These are largely HPUX 11.11i.
Unigraphics NX stopped UNIX support (HPUX, AIX, etc) as of NX 6 but opened support for Linux and OSX as of 8.
Dassault systems CATIA supported HPUX, AIX (6.1+) and Solaris on V5 - but as of V6 in 2011 they have ended UNIX support and are Windows only.
Pro Engineer quit most UNIX except Solaris until Pro Engineer / Creo 4.0 - at present they are Windows only.
Ok, I'll bite.
I'm a Windows admin, but I just went to a training course to learn about a high-end enterprise product that runs on top of Linux. I've dabbled with Linux-based stuff before (proxies, VMware, ESX, etc...), so it's not exactly new territory, but I figured it's 2013, it'll be interesting to get a glimpse into the current state of the "Linux Enterprise" world.
My experience was this:
-- You still need to patch, or install 140+ dependencies to install one application. Same difference.
-- You still need to reboot. A lot. More than I thought. I suspect that it is possible to avoid most of them though by judiciously restarting services, but the effort is much higher and the outage level is practically the same, so what's the benefit, really?
-- Things that really ought to be automatic, aren't. I spent a good 50% of the lab doing really fiddly things like cut & pasting iptables rules to open firewall ports. The installer really should have just done that for me.
-- Binding services together and just generally getting things to start up and talk required an awful lot of error prone manual labour. The lab guide was liberally sprinkled with warnings and "do not forget this or else" sections. Lots of "go to this unrelated seeming file, and flip this setting... because.. just do it or nothing will work."
-- I love the disclaimer in the training guide: "Linux configuration scripts do not tolerate typos, are case sensitive, and are not possible to validate before running the associated service." Fun stuff. I can't wait to diagnose random single-character problems in 10 kilobyte files when the only error is that one of a dozen services barfed when started.
-- Wow, the 70s called and wanted their limitations back: spaces in file names? You're risking random failures! Case-insensitive user names? Nope. Unicode text? Hah! IPv6? In theory, not in practice. GUI config wizards? Nope. Text-based config wizards? Not many of those either. Want to make a configuration change to a service without having to stop & start it? You're dreaming! An editor more user friendly than vi? Eat some cement and harden up princess!
-- I love the undecipherable command-line wizardry. I'm not an idiot, but how-the-fuck would I know what "-e" does on some random command? There is just no way without trawling through man pages using a command-line reader with no mouse support and keyboard shortcuts I don't know. Compare this to a sample PowerShell pipeline "Get-Process -Name 'n*' | sort -Descending PagedMemorySize". You'd have a hard time finding an IT engineer that can't figure out what that does.
I keep hearing about the supposed efficiency advantage of Linux, but I just don't see it. Given a Hypervisor, PowerShell, and Group Policy, Windows administration a piece of cake in comparison.