Lunduke
News • Science & Tech
The History of the First Computer Shell
BASH? PowerShell? It all traces back to 1963. And the work of an amazing Frenchman, CTTS, and Multics.
October 07, 2022
post photo preview

Powerful, “Command Line” computer interfaces have been around for — what seems like — forever. Interfaces where you can run multiple commands, one after another (in a batch)… where you can have simple “scripts” to tie those commands together.

That sort of “Shell” comes in so many forms… from SH and BASH on UNIX-like (and Linux) systems… to COMMAND.COM and PowerShell on Windows.

The text “Shell” is everywhere. And has been for longer than most can even remember.

But it had to start somewhere. Someone had to make the first “Shell”.

This is that story.

And that story starts… with a man. His name is Louis Pouzin.

The Man

Louis Pouzin was born, in 1931, in a small town in almost the smack-dab-middle of France: Chantenay-Saint-Imbert.

Louis Pouzin. With a sweet mustache. Photo credit: Jérémie Bernard

In the 1960’s Pouzin would move from France — and his job managing programmers at Bull (a French computer company) — to Massachusetts. His new job would put him working on an ambitious computing project at the Massachusetts Institute of Technology…

The Compatible Time-Sharing System

In 1961, the world’s first, general purpose, time sharing operating system was demonstrated at MIT.

That system — the “Compatible Time-Sharing System”… or “CTTS” — was originally developed on an IBM 709. And oh, what a beautiful machine it was.

The IBM 709

The IBM 709 was an absolute beast. Capable of adding 42,000 numbers per second, and multiplying two 36-bit integers together at a (then) blinding speed: 5,000 per second.

All contained in a svelte 2,000 pounds.

And this IBM 709, running CTTS, certainly had a text interface… but it wasn’t exactly a “Shell”. At least not in any way we would recognize together. Certainly, no scripting together of commands.

Over the next two years, CTTS continued to improve and evolve. Getting ported, by 1963, to a modified IBM 7094. Which, like the 709 before it, was a gorgeous machine. With enough physical switches to make any Sci-Fi nerd happy.

The IBM 7094 - “The Blue Machine”. Photo credit: IBM

It is around this time, that Pouzin arrives at MIT, where he is (at least partially) responsible for a little program called “MAIL”.

Wait. What? Pouzin invented E-Mail?

 

Well. Not quite. This was several years before what we now call “E-Mail” was created. This original “MAIL”, on CTTS, was a system for sending mail messages to other users… on the same CTTS system. It lacked a mechanism for forwarding messages to users on other systems.

 

Just the same, this work heavily influenced what would later become “E-Mail”.

But we’re not here to talk about MAIL or the many contributions Pouzin made to computer networking (leading to what we call “The Internet”) — that’s a fascinating topic for another day. Let’s focus on a little program that Pouzin wrote… which would change computing forever.

RUNCOM

You see, in those days, there was no “command interpreter” program. No “shell”. You simply instructed the kernel to run a single program.

Nothing like “COMMAND.COM” on DOS. Or BASH, SH, or other shells on UNIX and Linux systems. Nothing at a all like that existed.

That all changed in 1963, when Pouzin came up with “RUNCOM” — short for “RUN COMmand”.

In Pouzin’s words:

“After having written dozens of commands for CTSS, I reached the stage where I felt that commands should be usable as building blocks for writing more commands, just like subroutine libraries. Hence, I wrote "RUNCOM", a sort of shell driving the execution of command scripts, with argument substitution. The tool became instantly most popular, as it became possible to go home in the evening while leaving behind long runcoms executing overnight. It was quite neat for boring and repetitive tasks such as renaming, moving, updating, compiling, etc. whole directories of files for system and application maintenance and monitoring.”

RUNCOM was, truly, the first “Shell” system.

In fact, Pouzin, was the first person to call such a program a “Shell”.

His RUNCOM program would continue to be a critical component of the CTTS system until it ceased operations in 1973.

RUNCOM section from the CTTS Programmers Guide. Courtesy: Internet Archive

But we still didn’t quite have what we would call a “Shell”. Not yet.

The “Shell” had a name, and some of the features, but it wasn’t a truly interactive experience.

Meanwhile, in England…

During 1964, a computer scientist named Christopher Strachey was working at the University of Cambridge… on, what he called, the “General Purpose Macrogenerator”. Or “GPM”, for short.

Christopher Strachey, sporting a most excellent mustache. Photo courtesy: University of Oxford

This language had a heavy influence on much of 1960s and 1970s computing — including on “m4”.

M4 is a macro language, developed by Brian Kernighan and Dennis Ritchie, that was part of the original version of UNIX… and was later adopted as a part of the POSIX standard.

Strachey’s GPM design document. Published in a 1965 issue of The Computer Journal.

Back in Massachusetts…

During 1964, work on Multics (the “Multiplexed Information and Computing Service”) was getting underway at MIT (as a joint project between MIT, General Electric, and Bell Labs).

While Pouzin wasn’t going to be part of the Multics project… boy howdy… he had some ideas.

In his own words:

“Then in 64 came the Multics design time, in which I was not much involved, because I had made it clear I wanted to return to France in mid 65. However, this idea of using commands somehow like a programming language was still in the back of my mind. Christopher Strachey, a British scientist, had visited MIT about that time, and his macro-generator design appeared to me a very solid base for a command language, in particular the techniques for quoting and passing arguments. Without being invited on the subject, I wrote a paper explaining how the Multics command language could be designed with this objective. And I coined the word "shell" to name it. It must have been at the end of 64 or beginning of 65.”

Pouzin made sure his ideas were documented, by publishing a document entitled: “The SHELL: A global tool for calling and chaining procedures in the system”.

The full document is archived by MIT.
 

According to Pouzin:

“The small gang of Multics wizards found it a sleek idea, but they wanted something more refined in terms of language syntax. As time left to me was short, and I was not an expert in language design, I let the issue for them to debate, and instead I made a program flowchart of the shell. It was used after I left for writing the first Multics shell. Glenda Schroeder (MIT) and a GE man did it.”

From Tom Van Vleck, who worked on Multics for 16 years (starting in 1965):

“The first time I remember the name "shell" for the function of finding and running a command was in a Multics Design Notebook document by Louis Pouzin.

 

These memos con[t]ained the idea of having the command processing shell be an unprivileged user program that parsed a command line, located a program to run, and executed it with arguments.”

So. Who created the first “Shell”?

The concept, and first implementation of a “Shell” (RUNCOM for the CTTS), was made by Louis Pouzin.

But the first truly interactive example of a Shell — the one that was part of Multics, and which would most closely resemble the interactive shells of today — was initially designed by Pouzin… and programmed by Glenda Schroeder and a “Mystery Man from General Electric”.

The impact of RUNCOM and the Multics Shell

The impact of these early Shells cannot be understated.

Because of RUNCOM — and the designs of Pouzin — we have the Multics Shell.

Because of Multics… we have UNIX (originally named UNICS… before someone in marketing decided an “X” looked cooler) and SH.

You can trace every single computer Shell in existence — including BASH, PowerShell, and so many others — back to that first work. Back to the ideas of Louis Pouzin.

In fact, that influence expands far beyond just the design ideas of a scriptable, interactive Shell.

According to Brian Kernighan and Dennis Ritchie:

"There was a facility that would execute a bunch of commands stored in a file; it was called RUNCOM for "run commands", and the file began to be called "a runcom". rc in Unix is a fossil from that usage."

That’s right. Have you seen “rc” on your UNIX or Posix systems — such as .cshrc or /etc/rc? Those are named that way, according the the men behind UNIX itself, because of RUNCOM and Louis Pouzin.

To put it simply, modern computing is the way it is, in large part… thanks to Pouzin. A computer scientist that should be a household name.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
9
What else you may like…
Videos
Podcasts
Posts
Articles
PSX Emu Dev Forbids Arch Linux Packages

DuckStation developer says, "Next step will be removing Linux support entirely, because I'm sick of the headaches and hacks." Specifically naming Wayland as a source of problems.

00:15:52
Groupthink, Tech Journalism, & The Lunduke Journal

Why The Lunduke Journal uses the "10th Man Rule" to counter groupthink in the Tech Industry. (And why you'll definitely disagree with Lunduke sometimes.)

Stick it to Big Tech, 50% off everything at The Lunduke Journal:
https://lunduke.substack.com/p/stick-it-to-big-tech-50-off-everything

00:18:10
The Age of Non-Woke Open Source is Beginning

Non-Woke "Political Protest Forks" like XLibre & Redot are thriving. Non-DEl Linux Distributions like Open Mandriva are as well. But Woke projects? Not doing so well.

The Article:
https://lunduke.substack.com/p/open-source-political-protest-forks

00:21:04
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

There's a new conference in town. And it seems it's already sold out!
#VibeCoding

For all you Commodore fans…

If you've done 6 impossible things this week, why not round it off with a trip onboard "thE grAvY trAIn" TONIGHT at 21:00 BST! (1pm PST/4pm EST)

https://erb.pw/y/tgt20250802

post photo preview
IBM Taking DEI “Under the Radar”
Whistleblowers provide details on how IBM & Red Hat are simply renaming “Diversity” programs, as the company continues discriminatory hiring practices.

Back in April, The Lunduke Journal broke the story of IBM “ditching DEI policies” company wide — including at their subsidiary, Red Hat. This change was announced in the wake of multiple lawsuits against IBM (for their DEI policies) and executive orders against DEI from President Trump.

At the time, activist employees at Red Hat / IBM were not happy (to say the least). Encouraging and planning protests, “raising hell”, and even “killing fascists”.

But, now that a little time has passed, let’s take a look inside at IBM and see how their “ditching DEI” change is actually going.

DEI Staying “Under the Radar”

Thanks to whistleblowers within IBM, we know that employee groups focused on DEI still, in fact, exist. They are simply changing names in order to “stay under the radar” and avoid having “a target on their back”.

 

The “diversity-inclusion” corporate Slack channel, for example, is now named “inclusion-at-ibm”. They simply dropped the word “diversity”.

The DEI Department is Still There

Employees are using that IBM DEI Slack channel to clarify corporate changes to DEI policy. Which, again, thanks to whistleblowers… we have screenshots of.

A few key items:

  • The “DEI Department” has been renamed to “Inclusion” — and now reports to Kitty Chaney Reed (the Chief Leadership, Culture and Inclusion Officer).

  • IBM is no longer part of the Human Rights Campaign — “the HRC no longer align with IBM priorities”.

  • “People can still identify their preferred pronouns in all of IBM systems.”

  • The game-ified “Allyship Badge” system has been removed.

 

As we can see, some DEI policies and programs are gone, while others remain. And IBM is making a point of renaming their DEI Department within HR.

We gain these insights thanks to Ruth Davis — an IBM Executive and who currently identifies as a “DEI Advocate”.

 

These clarifications were published by a current member of the IBM HR team… who was originally hired as a “Diversity and Inclusion Intern”.

 

In short: DEI advocates continue to control IBM HR, and DEI departments continue to exist.

IBM / Red Hat Discriminatory Quotas

Up until recently, both IBM & Red Hat had discriminatory hiring policies — including sex and skin color quotas and even rewards for executives for hiring fewer white men.

We learned, as part of the original leaks supplied to The Lunduke Journal back in April, that “diversity goals are no longer part of the executive incentive program”.

 

Which begs the question, now that a few months have passed, is IBM still discriminating against White Men?

Getting hard numbers on the demographics of new IBM / Red Hat employees is not likely to happen for quite some time — if ever. But here is a picture, posted yesterday, of new Red Hat interns.

That might give us some indication of where things are heading.

 

Well. Huh.

Finding the “White Guys” in this photo of Red Hat interns isn’t quite as challenging as a round of “Where’s Waldo?”… but it’s close.

Now for me, personally, I truly don’t care what the demographic ratios are of employees & interns within a company. Hire the best people for the job, regardless of their sex or ethnicity. Meritocracy is a good thing.

That said, considering the multiple pending lawsuits against IBM and Red Hat — specifically regarding their discriminatory policies towards White Men (and their previously stated goals of hiring less of them) — it is more than a little interesting that their latest crop of Red Hat interns is almost entirely… people who are not White Men.

Results Are Mixed

There are a few good signs in here of IBM dropping DEI related policies — including no longer being involved in the Human Right Campaign and the removal of the (rather repulsive, anti-White) “Allyship Badges”.

Unfortunately, most of the rest of what we’re seeing is less encouraging.

  • “DEI” groups simply being renamed to “Inclusion” in order to stay on the right side of the law.

  • What appears to be continued discriminatory hiring at Red Hat (despite lawsuits and stated policy changes).

  • Executives and HR still heavily controlled by “DEI Advocates”.

  • Corporate systems still using “preferred pronouns”.

While making significant changes to corporate policies can take time — especially across large organizations like IBM — some of these internal reports indicate an unwillingness to drop DEI policies on the part of key IBM leadership.

The Lunduke Journal will continue keeping tabs on both IBM and Red Hat.

Any employees looking to become whistleblowers can find whistleblower resources at Lunduke.com.

Read full Article
post photo preview
LibreOffice Developer’s Hotmail Account Locked After LibreOffice Criticizes Microsoft
“Wow that looks bad,” says Microsoft employee.

Mike Kaginski, a LibreOffice developer (who works for Collabora), has had his Microsoft-hosted email account, which he uses for open source development, locked for “activity that violates our Microsoft Services Agreement”.

 

Kaginski discovered this when attempting to send an email to the LibreOffice development mailing list (hosted by FreeDesktop). It remains unclear if that specific email (which he sent via another address and was rather bland and technical) was the reason for the ban… or if attempting to send the email was simply the first time the ban was noticed by him.

This happened just days after LibreOffice officially accused Microsoft of engaging in a “Lock-in” strategy by creating “artificially complex”, XML-based office documents.

Are the two events related? Hard to say with any certainty.

To make matters worse, Kaginski has had no success in getting Microsoft to lift his locked email account — with the company making him jump through numerous, impossible hoops (such as requiring him to sign in to submit an appeal for his account being locked… but not allowing him to sign in… because his account is locked).

You got that? Sign in to fix the account you can’t sign in with.

Gotta love a good Catch-22.

Good job, Microsoft.

The Lunduke Journal reached out to a contact, within Microsoft, who made it clear that their group was not aware of the LibreOffice Developer’s locked account, but they were aware of the LibreOffice complaint article regarding “artificially complex” XML lock-in. Adding, “wow that looks bad”.

The Lunduke Journal’s Analysis

The odds of locking a LibreOffice developer’s email account being an official Microsoft corporate decision seems highly unlikely.

Microsoft, as a company, makes a lot of bad decisions — but this would just be too stupid for words. A massive PR blunder.

But could a single employee, feeling grumpy, have done it on an impulse? As some sort of revenge for LibreOffice’s “harsh” words about Microsoft? Sure. That seems entirely plausible?

Though, it’s also entirely plausible that some poorly designed AI-driven “naughty activity” detection bot flagged his account. Or, perhaps, the developer was reported by some random Open Source hooligan who likes to cause chaos (there’s a lot of those).

Either way, the fact that Microsoft requires people to log in — on accounts which cannot log in — in order to file an “appeal” is incredibly amusing. And is very, very typical Microsoft.

Read full Article
post photo preview
Open Source “Political Protest Forks” Thriving
Many called XLibre & Redot nothing more than “political protests” that would quickly die and be forgotten. Boy were those naysayers wrong.

Over the last year, we’ve seen a couple of high profile forks, of large Open Source projects, which were inspired — in part — by a desire to move away from the political discrimination and Leftist Extremism within the original projects.

At the time, when each of these forked projects were started, many predicted that they would go nowhere. That they were nothing more than “political protest forks” — and they would die out quickly.

Let’s check in on both of those project to see if that has happened.

XLibre - The Xorg Fork

Since officially launching, at the end of June (last month), the XLibre project has published a handful of official releases (now up to version 25.0.0.5)… with a significant number of changes and fixes.

 

In fact, considering the significant new features (such as XNamespace Extensions), the first release of XLibre is larger (in every way I can think to measure) than any Xorg release in the last decade. With the number of contributors growing.

How about Operating System support? Many predicted that XLibre would be ignored by every Linux distribution on the planet. That it would go nowhere and nobody would use it.

According to the “Are we XLibre yet?” wiki, a number of systems have already (officially) adopted XLibre. Including: Devuan, Artix, GhostBSD, and (my personal favorite) OpenMandriva.

 

This is important to note: All of that support has occurred even though XLibre has only existed for one month. Several systems already officially supporting it is nothing short of “crazy impressive”. Borderline unprecedented.

In addition, a number of systems have 3rd party repositories which allow users to install and use XLibre. Including: Arch, FreeBSD, Gentoo, NixOS, Slackware, and (seriously) macOS.

 

In short: Growing group of developers. Rapidly growing platform support. New releases which put the original project (Xorg) to shame.

Redot - The Godot Game Engine Fork

The Redot project — which forked off of Godot back in October of 2024 — had a stable release (4.3.1) back in June, and just had a new test release (4.4 Alpha 2). Both with both new features and fixes.

 

In fact, Redot has had 13 releases since the project started late last year.

With an absolutely massive number of commits since then.

 

In short: Steady, new releases. New features and bug fixes. Both stable and testing releases.

These Projects are Thriving

It’s hard to look at either of these projects and come to any conclusion other than they are absolutely thriving.

At this point, it’s looking like those who predicted rapid failure for these “Political Forks” were not only wrong… but wildly, obscenely wrong.

There’s a lesson in there.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals