Unix Turns 40 254
wandazulu writes "Forty years ago this summer, Ken Thompson sat down and wrote a small operating system that would eventually be called Unix. An article at ComputerWorld describes the history, present, and future of what could arguably be called the most important operating system of them all. 'Thompson and a colleague, Dennis Ritchie, had been feeling adrift since Bell Labs had withdrawn earlier in the year from a troubled project to develop a time-sharing system called Multics (Multiplexed Information and Computing Service). They had no desire to stick with any of the batch operating systems that predominated at the time, nor did they want to reinvent Multics, which they saw as grotesque and unwieldy. After batting around some ideas for a new system, Thompson wrote the first version of Unix, which the pair would continue to develop over the next several years with the help of colleagues Doug McIlroy, Joe Ossanna and Rudd Canaday.'"
Worth thinking about (Score:5, Interesting)
Not a bad retrospective, and interesting in that it illustrates some of the reasons for Unix's success: availability of source, and the ability for the user to create and replace tools easily. One wonders how those lessons might be applied not necessarily to operating systems or even computing, but to other industries and technical endeavours.
This makes Unix 15 years older than Tetris (Score:5, Interesting)
Unix just turned 40, and Tetris just turned 25 [slashdot.org]. What do they have in common other than closely spaced birthdays? They were both first developed on PDP-11 hardware (Unix on a PDP-11, Tetris on a Russian clone). And they've both been cloned, early and often.
U.S. copyright explicitly doesn't apply to methods of operation. Title 17, United States Code, section 102(b) [bitlaw.com]. This makes it legal to "clone" a computer program by observing its method of operation. But SCO has tried to use copyright to shut down Unix clones, and The Tetris Company has tried to use copyright to shut down Tetris clones. SCO already lost its case (there is no copyrightable piece of Unix in Linux), but the other case (Tetris v. BioSocia) is still pending.
And despite Tetris inventor Alexey Pajitnov's expressed disdain for free software [slashdot.org], two servers operated by Tetris (zone.tetris.com and www.tetrisfriends.com) are run using GNU/Linux.
Re:Worth thinking about (Score:2, Interesting)
Re:And to celebrate, it issued the command: (Score:5, Interesting)
Bah. Your command would fail. You need to escape the splat just like the semicolon:
find my_lawn -name kids\* -exec rm -f {} \;
However -exec is slow. Try:
find my_lawn -name kids\* | xargs rm -rvf
Verbose for your kid-removing satisfaction.
Oh, and happy birthday, UNIX! Without you my career would have undoubtedly been less interesting.
40 and still relevant (Score:5, Interesting)
When I started doing Unix Admin professionally Unix was just turning 30, Linux was poised to take over the Desktop, Mac OS X was just a glimmer of hope, and Sun was the king of commercial Unix.
When I started using Minix, Unix was only 20, but RMS was kvetching about source code (and Hurd was Coming Soon), BSD had just won it's freedom, and Steve Jobs was doing cool things over at NeXT. Unix was just leaving it's First "Golden Age"...
Now, at 40, Mac OS X is the most used Unix system, Sun was just bought cheap, most other commercial Unix systems are defunct... But with Android, Pre, and iPhone all putting *nix systems in the palms of millions, Macs selling more than ever, and many companies offering Linux pre-installed in the box, Unix is as relevant as ever.
Re:Worth thinking about (Score:5, Interesting)
Exactly. Unix has survived for as long as it has because it was built from, encouraged and profited from a culture of free innovation. Indeed, moreso that its actual code, I would argue that it is this culture that constitutes exactly what is meant by Unix.
Unix is not just an OS. It is a culture. Indeed, there is really no one "Unix" operating system. Or at least, no one widely used one called "Unix". Linux, BSD, OSX, BeOS, all can be called *nix systems. But what unifies them is not their internal mechanisms or algorithms or standards. What links them is the culture of the people who use them, and who build them. The idea of freely sharing tools, building on the work of others, understanding the whole of the machine, making magic happen with code; that is what Unix really is. You just don't see this kind of thinking in groups using other operating systems.
It's no surprise that the GPL and open source in general were born from the minds of Unix hackers. In many ways, the GPL only formalises the culture of academic openness, innovation and free sharing of ideas that existed throughout the Unix timeline. It's true that Unix was regarded by Big Corps as a money making excercise, but that's not how hackers saw it. They saw Unix and the programs that ran on it as part of their culture, and more importantly, heritage.
Unix has become more than source code or a framework. Is a significant part of our society. The norms and customs of Unix hackers have become their own tradition and even law in places. Unix and the hacker culture are a way our society has found to cope with the recent addition of computers, a way that has served well as the they and the internet become more and more pervasive. Like the old traditions and customs that founded our legal and civil systems, the Unix culture has formed the foundation of how we deal with the integration of computers into our lives.
The culture, traditions and ethics of Unix will probably outlast the lines of source that make up the programs, or the architectures they ran on. I expect Unix and hacker culture, or their descendants, will still be around in another 40 or 400 years, forming the philosophical foundation of a digital age.
Re:Unix is over the hill (Score:5, Interesting)
Re:40 and still relevant (Score:3, Interesting)
"Now, at 40, Mac OS X is the most used Unix system".
I do not think that phrase means what you think it means.
Re:Worth thinking about (Score:4, Interesting)
I think that The Open Group [opengroup.org] would disagree with your overly broad definition of Unix
Then he needs to put a * in the right place; they can still whine about it [opengroup.org], but they can't pretend the notion to which "Un*x" or "Unix-like" refers doesn't exist.
Windows has more and more Unix features (Score:5, Interesting)
let there be pipes (Score:4, Interesting)
I've encountered bits and pieces of Unix hagiography for the last 15 years, and in all that time, I've internalized that "Multics sucks" (somewhere alongside the virgin birth), yet I can't bring to mind a single reason *why* Multics sucked. Were the Romans really so stupid as they are made out to be?
From Fernando J. Corbató's 1991 Turing lecture [mit.edu] concerning one of Muttlix's early teething problems:
The decision to use a compiler to implement the system software was a good one, but what we did not appreciate was that new language PL/I presented us with two big difficulties: First, the language had constructs in it which were intrinsically complicated, and it required a learning period on the part of system programmers to learn to avoid them; second, no one knew how to do a good job of implementing the compiler.
So, perhaps, not the best suited language for systems programming?
From Wikipedia:
The goal of PL/I was to develop a single language usable for both business and scientific purposes.
Doesn't that vision give your average PHB a throbbing chum? If simplicity is hard, let's scale up the mediocre talent and do sameness instead.
PL/I was designed by a committee drawn from IBM programmers and users drawn from across the United States, working over several months.
No sociology experiment from the 1960s was complete without confederates in white shirts. The free-love hippies managed to sneak into the language promiscuous data type conversions.
Dijkstra summed it up in 1975 with his monograph
How do we tell truths that might hurt? [virginia.edu]
PL/I --"the fatal disease"-- belongs more to the problem set than to the solution set.
God, I love this guy. He's the patron saint of annoying the hell out of people by always being right, and putting a fine point on it. Same monograph includes another famous zinger:
APL is a mistake, carried through to perfection. It is the language of the future for the programming techniques of the past.
From Myths about Multics [multicians.org]
We wrote 3000 pages of the Multics System Programmer's Manual first, while waiting for the PL/I compiler.
That should strike a painful nerve in anyone who tried to adopt the C++ STL in 1994.
Ouch. Shipwrecked on the beach of half a programming language, fondling your monads.
Not half surprising that Thompson ended up carving his own canoe with a pen knife to escape.
Re:And to celebrate, it issued the command: (Score:2, Interesting)
Re:Windows has more and more Unix features (Score:1, Interesting)
Re:Unix is over the hill (Score:5, Interesting)
Does Unix philosophy actually mesh with Unix reality? A reason I ask is because in unix everything is supposedly a file, but there were enough exceptions, such as in networking, that in the seperate Plan9 OS, they sought to really make everything a file. And that by the original makers of unix.
Re:What came before? (Score:3, Interesting)
So could an old salt fill us young-un's in? What was it like before Unix?
Here's a typical computer job from before UNIX... IBM JCL. The following is roughly the equivalent of "lpr -Pxerox
You can thank monopolies (Score:3, Interesting)
Like it or not, most of the key innovations in computers came from monopolies: Xerox, IBM, AT&T. When you have more money than you know how to spend, you can afford letting people play. Why not Microsoft? Although it has had some innovation, MS was never a monopoly in the same league as the other three. Also, there was a lot more low-hanging fruit in the computer world of the 60's and 70's than there was later.
Re:Windows has more and more Unix features (Score:3, Interesting)
Well, considering that Windows NT's development largely predates UTF-8, I think that they could be given a pass on that one. (As I understand it, Windows NT was the first Windows to really deeply embed Unicode, and the reason they went with UTF-16 was because that was the best that was available.) UTF-8 came on the scene in early 1993, and Windows NT came out just a few months later.
Or am I misremembering?