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
XLibre Trolls Leftists, Renames FirstScreenPtr() to MasterScreen()

The open source fork of Xorg has renamed the function for returning the primary screen to "Master", which is sure to drive the "Inclusive Naming" people insane.

More from The Lunduke Journal:
https://lunduke.com/

00:08:23
Leaked Email: IBM Assimilating Red Hat Like The Borg

Thanks to leaked emails, provided to The Lunduke Journal, we know that IBM is dismantling and absorbing significant portions of Red Hat. As predicted.

More from The Lunduke Journal:
https://lunduke.com/

00:07:22
September 11, 2025
The Phrack, North Korea, & Proton Mail Story

A hacker for the 1980's zine, Phrack, gained access to a North Korean cyber espionage system... then got banned by Proton Mail. Yeah. It's crazy.

More from The Lunduke Journal:
https://lunduke.com/

00:10:52
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

I'm becoming an [doom] emacs fanboy I think...

Anyone else using it? I had it installed for a few months, but never really got into it until yesterday, giving it a real go and already I can see I'm really liking it.

post photo preview

Is Locals being really stupid lately for everyone? I keep clearing my notifications and every little while after, it goes back to saying I have 216 unread notifications!

September 10, 2025

RIP Charlie Kirk :(

Keep The Lunduke Journal Free!

So far, in 2025, The Lunduke Journal has published 246 shows — being the only Tech News outlet covering the vast majority of those stories.

All without even the slightest influence from Big Tech. No sponsorships, no ad reads, not a penny taken from any company.

And every single story — every article, podcast, & video — is free to share far and wide.

In order for The Lunduke Journal to continue doing this unique work — to keep the lights on well into the future — we need your help.

If you haven’t yet become a subscriber to The Lunduke Journal, doing so today makes a big impact. Pick one of the options below. Big or small. Monthly, Yearly, or Lifetime subscriptions — or even simply one-time donations — all make a huge difference.

Support The Lunduke Journal

Monthly or Yearly Subscriptions:
Locals, Substack, X, YouTube, or Patreon

Lifetime Subscriptions:
Pay Once, For Life (Locals & Substack)

One-Time Donations:
Locals or Bitcoin

You Make The Lunduke Journal Possible

Seriously. This is all possible because of you.

We are able to make all of this free to share with the world because of you.

Might I make a suggestion?

The Lifetime Subscription (which counts towards both Substack and Locals) is a marvelous, one time, way to show support. And it comes with all of the perks (access to the Locals community as well as the official Lunduke Journal forum, & DRM-free eBooks).

You can snag a Lifetime Subscription via Locals, Substack, or with Bitcoin. Lots of options.

But, heck, any type of subscription (via any platform) is appreciated! Choose whichever works best for you!

Then be sure to go to Lunduke.com and choose the platforms which are the most convenient for you to use — The Lunduke Journal publishes all over!

And, once again, thank you for making The Lunduke Journal possible.

-Lunduke

Read full Article
September 08, 2025
post photo preview
Lunduke Journal hit 9 million views in August
And still not taking a single penny from Big Tech.

Thanks to all of you, August was a truly spectacular month for The Lunduke Journal.

After everything was tallied up — audio podcast downloads, video views, and article views — all of you viewed (or listened to) my work over 9 million times last month.

I’m not sure if that’s a record or not — I’ll need to go over some of the past stats to be sure — but it definitely makes me smile.

It means that the real Tech News — the stories that most Tech Journalists refuse to tell — is getting out there. In a big way. No matter how much Big Tech wants some of these stories to go away.

Stats for August

Here’s some Lunduke Journal stats (because stats are fun):

  • 238 shows, so far, in 2025 (Jan 1st → Sep 8th, nearly one show per day).

  • Over 9 million views (or listens) during the last month (August) alone.

  • 131,817 free subscribers (not including audio podcast feeds).

  • 4,488 new free subscribers on the primary platforms.

  • $0.00 (zero) taken from any corporation (no sponsorships, no ad campaigns… not a penny).

9 Million “views”. In one month. Hot diggity!

You better believe I’ll be keeping a close eye on the stats this month to see if we get close to 10 Million. Because 10 Million is a nice, big round number.

And big, round numbers are fun.

No Sales in September

One other thing I wanted to mention: I’m hoping to do away with sales and discounts on Lunduke Journal subscriptions. Which means no sales during this month (September).

My hope is that, with the rapidly growing size of The Lunduke Journal’s audience, enough new subscriptions and donations will continue to roll in to keep this publication afloat… without sales. Because, let’s be honest, sales are kind of annoying, right?

The Lunduke Journal is unique in taking zero money from any company (while giving away nearly everything for free). Most Tech News outlets struggle to keep the lights on even with running paid ads (and paid articles) nearly non-stop.

Being funded 100% by all of you is something no other Tech News outlet even attempts.

And if we can do that while making all articles & shows free for the world… without needing to run any sales or promotions? How amazing would that be? It would send a profound message.

With that in mind, if you appreciate The Lunduke Journal, consider grabbing a subscription. Big or small (and via any platform), every subscription and donation goes directly to making this work possible.

Once again, a huge thank you for every subscription and donation.

Truly, The Lunduke Journal would not be possible without all of you.

Now, if you’ll excuse me, I have another show to record… which is probably going to make another Tech company very grumpy.

I love my job.

-Lunduke

Read full Article
September 01, 2025
post photo preview
Fired Microsoft Employee Encouraged Corporate Sabotage
Leaked screenshots from a Microsoft whistleblower reveals efforts, by a "Worker Intifada" organizer, to disrupt Microsoft business and send spam propaganda email to thousands.

This last week, members of the Microsoft “Worker Intifada” claimed that some of their members were fired by Microsoft in an attempt to silence the speech of pro-Palestinian employees.

Thanks to an internal Microsoft whistleblower, we have gained additional insight into the real reasons at least one of the “Intifada” organizers was fired.

Including mass emailing thousands of Microsoft employees with anti-Microsoft messages, and building internal, corporate websites dedicated to disrupting company business. Over the course of months.

And, of course, we’ve got screenshots.

The Microsoft “Intifada”

The Microsoft’s “Worker Intifada” held a press conference, on August 28th, at the office of CAIR — a response to a Microsoft’s Media briefing held 2 days earlier.

The topic of both press events being the “Intifada” actions of the previous week — including vandalism, breaking and entering, and public demonstrations against Jewish people (with chants of “Go away, Jews!”).

A key topic being the firing of 4 Microsoft employees related to the “Intifada”.

One of those fired employees is Nisreen Jaradat, seen here speaking at the press conference at CAIR on August 28th:

 

Thanks to leaked Microsoft material, we can get a glimpse into the anti-Microsoft activity of Nisreen Jaradat… going back several months.

Anti-Microsoft Microsoft Employee

Nisreen created an internal website — on the Microsoft corporate Intranet — entitled “PledgeForPalestine”.

 

On that website, Nisreen encourages employees to take a pledge declaring that employees will “not support genocide”, specifically demanding that Microsoft no longer interact with Israel in any way.

It should be noted that, as of just a few days ago, this website was up within Microsoft.

Nisreen’s website also includes a list of ways where employees could sabotage internal corporate work.

 

Nisreen encouraged employees to:

  1. Refuse to work on support tickets that involve Israel (and sabotage any tickets worked on by others).

  2. Refuse to work with other employees on tasks which may involve Israel — or any Israeli Microsoft employees or customers.

In July, Nisreen sent internal Microsoft Teams messages to thousands of employees encouraging them to sign that anti-Israel and anti-Microsoft pledge.

 

But this wasn’t the first time Nisreen spammed Microsoft employees with pro-Palestinian propaganda.

Back in May of this year, Nisreen sent an email to over 8,000 Microsoft employees entitled “You can’t get rid of us.”

 

Within that email, she declared that her employers have “shown their true face, brutalizing, detaining, firing, pepper spraying, threatening and insulting workers and former workers protesting.”

Surprise, She Got Fired

Protesting your bosses and accusing them of “genocide” while encouraging thousands of other employees, in spam emails, to sabotage corporate work?

Now, think what you will about Microsoft… but I can’t imagine any company not firing someone who takes those actions internally.

In fact, I would suggest that it is wild that Microsoft put up with the actions of this “Intifada” organizer for so many months.


If you would like to be a Tech whistleblower — or would like to support the work of The Lunduke Journal — head to Lunduke.com. All of the information is 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