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
Mozilla Launches Paid Thunderbird E-Mail Service Which "Aligns With Our Values"

Mozilla values: Deplatforming of Conservatives, A.I. Generated Content, Mozilla can use your data however it wants, & "Feminist, Decolonial, LGBTQIA Climate Justice using Al".

00:23:05
IBM "White Men" Discrimination Lawsuit Moves Forward, Judge Denies IBM's Motion to Dismiss

Dill v. IBM -- one of multiple cases against IBM for racial discrimination and Woke DEl policies - is moving toward trial.

The IBM / Red Hat Leaks: What we've learned so far:
https://lunduke.locals.com/post/5515346/the-ibm-red-hat-leaks-what-weve-learned-so-far

00:18:28
Open Source DNA Project Dies of Trump Derangement Syndrome

Founder says they are shutting down because, "Trump has focused on criminalizing immigrants and trans people," & the "fascist coup in the U.S."

00:14:33
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
Help The Lunduke Journal fight against the Tech Goliaths

The corrupt Tech Foundations of the world — WikiMedia, The Linux Foundation, Mozilla, and the rest — have received hundreds of Millions of dollars in donations. The Big Tech giants bring in Billions and Billions ever year.

And there is only one Tech News outlet that is pushing back against these woke, dirty organizations… The Lunduke Journal.

One nerdy David. Against an army of well-funded, woke Tech Goliaths.

Without your support, The Lunduke Journal would not exist.

And, without The Lunduke Journal, many Tech News stories simply would never be told.

From now, through Friday, March 28th, we are running The Lunduke Journal pledge drive.

Make a one time donation (with multiple options, including Bitcoin) — and help keep The Lunduke Journal publishing commercial free, Big-Tech-Free news.

Or grab a discounted subscription and get a few fun perks:

  • Access to the exclusive Forum.

  • Access to exclusive shows (such as Q & A’s).

  • Warm Fuzzy Feelings (tm) that you’re supporting truly independent Tech Journalism.

Scroll down to find the option that works bet for you. Give only what you are able. Together we will tell the Tech News stories that no other Tech News outlet has the guts cover — together we will hold these Tech Goliaths accountable.

Make a One Time Donation

Want to toss in a one-time donation to The Lunduke Journal? There’s a few great options!

Via BitCoin:

Send any amount of BTC to the following address:

bc1qyjakve8fywm8pz2v99v57yhjj0vzr2vjze6fcq

  • Email "bryan at lunduke.com" with to let us know it was you! You can choose to keep your donation anonymous if you prefer.

Via Locals:

  1. Go to Lunduke.Locals.com/support.

  2. Click “GIVE ONCE”.

  3. Enter any amount you like.

Looking for a subscription? Scroll down for options!

50% Off Yearly Subscription:

50% off a Yearly subscription to The Lunduke Journal via both Locals and Substack. (This includes full access to the community Forum.)

That’s $2.25 per month. Pocket change.

The Famous Lifetime Subscription:

The "World Famous Lunduke Journal Lifetime Subscription" is exactly what it sounds like. Pay once and get full access to The Lunduke Journal. For life. A great way to support Big-Tech-Free Journalism.

(This includes full access to the community Forum.)

New Lifetime Subscriptions are available, for $200, from now through Friday, March 28th.

The Lifetime Subscription can be obtained via Locals, Substack, or using Bitcoin. All three options work great and are super easy.

How to get a Lifetime Subscription via Locals:

  1. Go to Lunduke.Locals.com/support.

  2. Select "Give Once".

  3. Enter "200" into the amount field.

  4. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

How to get a Lifetime Subscription via Substack:

  1. Go to Lunduke.Substack.com/subscribe.

  2. Select the “Lifetime Subscription” option.

  3. After checking out, Lunduke will toss you an email once your account is set to full lifetime status. (This usually happens within a few hours.)

If you would also like full, Lifetime access to Lunduke.Locals.com (which is included):

  1. Make a free account on Lunduke.Locals.com.

  2. Email “bryan at lunduke.com” with the email address you use on both Substack and Locals (can be different email addresses).

  3. Lunduke will toss you an email once your account is set to full lifetime status on Locals.

How to get a Lifetime Subscription with Bitcoin:

And, finally, you can obtain a Lifetime Subscription via Bitcoin. Save a few bucks with this option, as Bitcoin processing has fewer fees associated with it.

bc1qyjakve8fywm8pz2v99v57yhjj0vzr2vjze6fcq

  • Email "bryan at lunduke.com" with the following information: What time you made the transaction, how much was sent (in Bitcoin), and the email address you use (or plan to use) on Locals.com or Substack.com.

50% Off DRM-Free, MP4 Downloads:

Want to be able to download every show The Lunduke Journal releases (and watch them on whatever device you like)? Yeah. You can do that. For 50% off.

Note: This DRM-Free download option does not include access to the Forum. This option is strictly for downloading the episodes.

The Lunduke Journal would not be possible without your support. Every subscriber, of every type, makes a massive difference in bringing Big-Tech-Free Tech Journalism to the world.

This truly is the last bastion of independent Tech Journalism.

Thank you.

-Lunduke

Read full Article
February 24, 2025
post photo preview
12% of Tech Workers Believe macOS is Based on Linux
Over 70% believe in at least one common Myth of Computer History.

The following data was derived from the 2025 Tech Industry Demographic Survey, which included over 12,000 respondents -- from across companies and organizations throughout the Tech Industry -- surveyed during February of 2025.

 

Ready to have your mind blown?

According to those surveyed:

  • Nearly 12% believe that macOS is based on Linux.
  • Over 70% believe in at least one common Myth of Computer History.
  • The most commonly believed myth (at 52%) is the myth that "the first computer bug was a real bug (a moth)".

 

Those who took the survey were presented with 6 common (but debunked) computer history myths... and were asked to select the myths which they believed to be true and factual historical statements.

Here is the breakdown of how many believed in each myth.

 

 

One rather fascinating piece of data: Those percentages held steady for nearly every demographic group within the survey.

For example:

Roughly 12% of respondents who prefer Linux, believe macOS is based on Linux.  The same was true of Windows users, C / C++ programmers, and those who perfer the Firefox Web Browser... no matter what sub-group was looked at... that number stayed roughly steady (around 12%).

The one outlier appeared when I looked at how many myths a person says they believe in... grouped by generic political leanings (Left, Centrist, or Right Leaning).

 

Notice that the percentage of respondents who "Believe at least one myth" or "Believes 4+ myths" stays roughly consistent (with only mild variances) across all three political groupings.

But, if you look at the "Believes 3+ myths" data, there is an 8% spike among those who identify as "Left Leaning".

While all surveyed were likely to believe at least one myth, "Left Leaning" respondents were slightly more likely to believe up to 3 myths (of the 6 presented).

 

The Myths of Computer History

 

For those curious, here are the 6 myths included in the survey (with links to debunk each of them).  

 

Read full Article
February 18, 2025
Lunduke's Birthday! Woo!

Wooo! Today is Lunduke’s birthday! Want to help celebrate this most excellent of holidays? Here’s some totally radical ideas!

1) Share some links to Lunduke Journal shows.

Bonus points if you share those shows to the type of places where people would get mad about it. 🤣

The “Open Source is Anti-Free Speech” video is a great choice. Just remember to take screenshots… because some sites will censor those links faster than you can blink (be sure to let me know if they do censor).

2) Grab a Subscription

Gotta keep the lights on here at The Lunduke Journal! And, shoot, there’s no better gift than the gift of Big-Tech-Free Journalism. 😎

Plus… for the rest of February there’s some massive discounts (like 50% off).

https://lunduke.locals.com/post/6661699/for-february-50-off-subscriptions-50-off-drm-free-downloads-lifetime-subscriptions-available

So, you know, win-win!

Now, if you’ll excuse me, I’m going to go eat some BBQ. Because… birthday.

-Lunduke

 
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