feat: tidy up Unix History

4 files changed, 118 insertions, 88 deletions

diff --git a/content/unix-history/01_multics.md b/content/unix-history/01_multics.md
index d4feb5f..0cdf7b5 100644
--- a/content/unix-history/01_multics.md
+++ b/content/unix-history/01_multics.md
@@ -4,15 +4,17 @@ author = ["Michał Sapka"]
 date = 2024-03-09T21:03:00+01:00
 categories = ["unix-history"]
 draft = false
-weight = 1002
-primary_menu = "unix-history"
+weight = 2002
+image_dir = "unix-history"
+image_max_width = 700
 abstract = "Unix history starts with Multics"
 shortname = "Part I: Multics"
 link = "part-ii-multics"
 aliases = ["/bsd/history/01_multics/"]
+primary_menu = "unix-history"
 [menu]
   [menu.unix-history]
-    weight = 1002
+    weight = 2002
     identifier = "history-of-unix-part-i-multics"
     name = "1. Multics"
 +++
@@ -29,9 +31,9 @@ Sellers earned a lot from the devices.
 But, naturally, companies making all those investments wanted a nice return.
 This led to the creation of _time-sharing_.
 
-{{< img-c "ibm-360.jpg" "https://www.nbcnews.com/tech/gadgets/5-reasons-love-mad-mens-new-star-ibm-360-n101716" >}}
+{{< image class="centered" alt="Photo of old computer room full of tape drives. The primary color is red." source="https://www.nbcnews.com/tech/gadgets/5-reasons-love-mad-mens-new-star-ibm-360-n101716" file="ibm-360.jpg" >}}
 IBM 360 in an official photoshoot.
-{{< /img-c >}}
+{{< /image >}}
 
 This concept seems natural now: multiple processes were able to share computer resources, so multiple applications could run at the same time.
 Applications could even run for different users.
@@ -46,9 +48,9 @@ What is multiplexing you ask?
 Simply said, it's a way to combine different signals into a shared medium.
 It was used extensively for land-line telephony, where all signals were transferred over shared wires.
 
-{{< img-c "edsac.jpg" "https://www.datacenterdynamics.com/en/analysis/rebuilding-edsac-the-first-real-computer/" >}}
+{{< image class="centered" alt="Black and white photo of a group of man standing next to a mechanical computer" source="https://www.datacenterdynamics.com/en/analysis/rebuilding-edsac-the-first-real-computer/" file="edsac.jpg" >}}
 EDSAC, the "first computer".
-{{< /img-c >}}
+{{< /image >}}
 
 
 ## Multics {#multics}
@@ -61,13 +63,13 @@ It was however also huge, both in terms of memory usage (the resident kernel cou
 _Multics_ was experimental and therefore ambitious, complex - designed by trial and error.
 It was delivered late, early on had performance problems, and in 1969 _Bell Labs_ withrew from the project[^fn:5].
 
-{{< img-c "multics-login.png" "https://en.wikipedia.org/wiki/Multics#/media/File:Multics-Login.png" >}}
+{{< image class="centered" alt="Screenshot of SSH connection with big Multics written in ASCII" source="https://en.wikipedia.org/wiki/Multics#/media/File:Multics-Login.png" file="multics-login.png" >}}
 Multics login screen.
-{{< /img-c >}}
+{{< /image >}}
 
-{{< img-c "thompson-ritchie.jpg" "https://computerhistory.org/blog/discovering-dennis-ritchies-lost-dissertation/" >}}
+{{< image class="centered" alt="Photo of two white, bearded men. They are both wearing thick glasses. The person on the left is wearing gray-blue polo shirt. The person on the right is wearing a red tshift with big X and Bell Labs Sensitive text in center" source="https://computerhistory.org/blog/discovering-dennis-ritchies-lost-dissertation/" file="thompson-ritchie.jpg" >}}
 Ken Thompson and Denis Ritchie.
-{{< /img-c >}}
+{{< /image >}}
 
 Ken Thompson, Dennis Ritchie, Douglas McIlroy, and Joe Ossanna, frustrated with their experiences with _Multics_ Operating System are starting to work on their own alternative.
 Their work will become one of the most beloved computer products of all time - _UNIX_.
diff --git a/content/unix-history/02_unix.md b/content/unix-history/02_unix.md
index 8cf268a..ca3b29b 100644
--- a/content/unix-history/02_unix.md
+++ b/content/unix-history/02_unix.md
@@ -5,11 +5,13 @@ date = 2024-03-16T21:00:00+01:00
 categories = ["unix-history"]
 draft = false
 weight = 2003
-primary_menu = "unix-history"
+image_dir = "unix-history"
+image_max_width = 700
 abstract = "How Unix came to be?"
 shortname = "Part II: Unix"
 link = "part-ii-unix"
 aliases = ["/bsd/history/02_unix/"]
+primary_menu = "unix-history"
 [menu]
   [menu.unix-history]
     weight = 2003
@@ -55,9 +57,9 @@ And since those costed an arm and a leg, end users were paying for time they use
 A single game of _Space Travel_ could cost Ken USD 50-75[^fn:3].
 Luckily, he was able to find a discarded PDP-7 from another department[^fn:2].
 
-{{< img-c "space-travel.png" "https://www.uvlist.net/game-164857-Space+Travel" >}}
+{{< image class="centered" alt="Two red books containing Volume 1 and 2 of Programmers Manuals for CB Unix" source="https://www.uvlist.net/game-164857-Space+Travel" file="space-travel.png" >}}
 Space Travel
-{{< /img-c >}}
+{{< /image >}}
 
 What the PDP-7 was, was a refrigerator size 18bit monstrosity[^fn:2].
 It was at the time a 5-year-old and obsolete[^fn:4] leftover from an ended research into audio-psychology.
@@ -77,13 +79,13 @@ The biggest benefit however was the popularity of this machine - over the next d
 You can buy a working one from _eBay_ today.
 It won't be easy nor cheap, but definitely possible.
 
-{{< img-c "pdp-7.jpeg" "https://en.wikipedia.org/wiki/PDP-7#/media/File:Pdp7-oslo-2005.jpeg" >}}
+{{< image class="centered" alt="Two red books containing Volume 1 and 2 of Programmers Manuals for CB Unix" source="https://en.wikipedia.org/wiki/PDP-7#/media/File:Pdp7-oslo-2005.jpeg" file="pdp-7.jpeg" >}}
 PDP-7
-{{< /img-c >}}
+{{< /image >}}
 
-{{< img-c "thompson-ritchie-pdp11.jpg" "https://www.bell-labs.com/institute/blog/invention-unix/" >}}
+{{< image class="centered" alt="Two red books containing Volume 1 and 2 of Programmers Manuals for CB Unix" source="https://www.bell-labs.com/institute/blog/invention-unix/" file="thompson-ritchie-pdp11.jpg" >}}
 Ken Thompson and Denis Ritchie working on the legendary PDP-11.
-{{< /img-c >}}
+{{< /image >}}
 
 
 ## Unix 1 {#unix-1}
@@ -121,9 +123,9 @@ This made it the first portable _UNIX_, as it could be recompiled to any compare
 The system was presented by Ken and Denis during the _4th Symposium on Operating System Principles_ the same year,
 and a year later Ken and Dennis publish the first paper on _UNIX_ - "The UNIX Time-Sharing System" in the _Communications_ journal of ACM.
 
-{{< img-c "unix-tech-journal.jpg" "https://leancrew.com/all-this/2011/10/dennis-ritchie-unix-and-clarity/" >}}
+{{< image class="centered" alt="Photo of front and back cover of an orange book with The Unix System written in the center; Above it a text states AT&amp;T Bell Laboratories Technical Jurnal" source="https://leancrew.com/all-this/2011/10/dennis-ritchie-unix-and-clarity/" file="unix-tech-journal.jpg" >}}
 Bell System Technical Journal cover.
-{{< /img-c >}}
+{{< /image >}}
 
 The word was out and _UNIX_ became known outside of _Bell Labs_.
 
diff --git a/content/unix-history/03_unix_wars.md b/content/unix-history/03_unix_wars.md
index d792364..51ad920 100644
--- a/content/unix-history/03_unix_wars.md
+++ b/content/unix-history/03_unix_wars.md
@@ -17,12 +17,12 @@ primary_menu = "unix-history"
     name = "3. Forks and Wars"
 +++
 
-This resulted in a very peticular situation.
-Different organizations got into possesion of a _great_ operating system with which they were able to do whatever they pleased.
+This resulted in a very particualar situation.
+Different organizations came into possesion of a _great_ operating system with which they were able to do whatever they pleased.
 The original creators, AT&amp;T were unable to sell the software.
-Of course, they wanted to monetize on this opportunitty.
+Of course, they wanted to monetize this opportunity.
 
-This chapter of history is convolutted, so hopefully I won't make any significant errors here.
+This chapter of history is convoluted, so hopefully I won't make any significant errors here.
 Most of this history would be lost to time, if it it wasn't for dedication of dedicated fans.
 Remember, I try to link sources so please go take a visit to _their_ sites and talks.
 But please, go and see Warner Hosh's [talk](https://www.youtube.com/watch?v=XuzeagzQwRs) on the early history of UNIX.
@@ -31,7 +31,7 @@ It's a gold mine and guiding light allowing me to write the following chapter.
 
 ## Other Bell Unixes {#other-bell-unixes}
 
-But the first forks (separately developed versions of _Unix_) came from Bell[^fn:1].
+The first forks (separately developed versions of _Unix_) came from Bell[^fn:1].
 
 <https://youtu.be/XuzeagzQwRs?si=VJjyR1A_ofZAoguI&t=1610>
 
@@ -41,18 +41,18 @@ The first known fork of _Unix_ was intended to automate switching of connections
 This version of /Unix_ is the earliest known usage of the OS family outside of Bell Labs.
 It was released in 1971 as a fork of 1st or 2nd edition of _Unix_ and was the first known _Unix_ to support inter-process communication and file locking.
 Those advancements were not back ported to mainline _Unix_ until _System V_[^fn:2],[^fn:1].
-Soon, after it evolved into Columbus Linux (_CB-Unix_), as the _SCCS Unix_ was developed by Bell Division 59473 in Columbus, Ohio.
+Soon, after it evolved into Columbus Unix (_CB-Unix_), as the _SCCS Unix_ was developed by Bell Division 59473 in Columbus, Ohio.
 
 {{< image class="centered" alt="Two red books containing Volume 1 and 2 of Programmers Manuals for CB Unix" source="https://en.wikipedia.org/wiki/CB_UNIX#/media/File:CB_Unix_Manuals.jpg" file="cb-unix-manuals.jpg" >}}
 Programmers Manuals for CB Unix
 {{< /image >}}
 
 In a completely different part of Bell Labs, another project was starting to use _Unix_.
-_Mert_ (Multi-Environment Real-Time) was a fork for use in embedded minicomputers, like PDP-11s[^fn:3].
-Yes, virtualization is not a new idea - it dates back to the 60s where it was developed by IBM.
-And so in 1973 _Unix V4_ was ported to run as a supervisor.
-It was the first time _Unix_ was run in a virtualized environment[^fn:1],[^fn:3].
-Thus system evolved into _Unix/RT_ and then _DMERT_
+_Mert_ (Multi-Environment Real-Time[^fn:3]) was a fork for use in embedded minicomputers, like PDP-11s[^fn:4].
+And so in 1973 _Unix V4_ was ported to run as a supervisor on DEC PDP-11 computers, models -11/45 and -11/70&nbsp;[^fn:5].
+It was the first time _Unix_ was run in a virtualized environment[^fn:1],[^fn:4].
+To achieve this, authors used a new (at the time) idea that we now call microkernel.
+This system evolved later into _Unix/RT_ and then _DMERT_
 
 Yet another version was _PWB/Unix_ which was designed to be used to create software for batch processing.
 This was how processing was done back then - you created your program, submitted it to a mainframe, but with the use of _Unix_ no longer one needed to provide a deck of cards to a operator.
@@ -60,18 +60,18 @@ As a result, _PWB_ provided an early version of Source Control System.
 To make work easier, this was the first version to include a _shell_ - _pwb shell_.
 Other tools we know and love today that originate in _PWB_ are awk, sed, grep, or make[^fn:1].
 Ergo, this was one of the OSes made for work, not for research.
-This OS was released in 1977 but Evan Ivie and Rudd Canaday started working on it in 1973[^fn:4].
+This OS was released in 1977 but Evan Ivie and Rudd Canaday started working on it in 1973[^fn:6].
 
-In the same year, 1973, Bell funds a small group to support the use of _Unix_ across the lab - the _UNIX Support Group_ or _USG_ for short[^fn:5].
+In the same year, 1973, Bell funds a small group to support the use of _Unix_ across the lab - the _UNIX Support Group_ or _USG_ for short[^fn:7].
 Their version of _Unix_ was called _Unix/TS_ and was based on _UNIX v4_.
 It was later merged with _PWB_ and _32V_ to become _Unix/TS 3.0_ known also as _System III_.
 After another merge, this time with CB-Unix and it became _Unix/TS 4.0_, which however was never released.
-The next version after that, _Unix-TS 5.0_, became the _System V_.[^fn:1],[^fn:5].
+The next version after that, _Unix-TS 5.0_, became the _System V_.[^fn:1],[^fn:7].
 
 We're not done yet.
-_UNIX_ has seen it's share of history and we're still in the 70s.
+_UNIX_ has seen its share of history and we're still in the 70s.
 1975 saw the release of MUNUX, most likely as a fork of _UNIX V5_[^fn:1].
-It was a modification of mono-processing system, UNIX, to multiprocessing utilizing two PDP 11/50[^fn:6].
+It was a modification of mono-processing system, UNIX, to multiprocessing utilizing two PDP 11/50[^fn:8].
 Yes, multi processor processing was researched in the 70s.
 
 _UNIX V6_ saw the addition of BBN TCP/IP Stack in 1977.
@@ -84,7 +84,7 @@ We will get back to that, but it is what sounds like: AT&amp;T is earning money
 ## AUSAN and the birth of BSD {#ausan-and-the-birth-of-bsd}
 
 _AUSAM_, the _Australian Unix Share Accounting Method_ was the first community maintained fork of Unix based on the Sixth Edition[^fn:1].
-The work conducted at Universities of Sydney and New South Wales focused on allowing the system to run with huge number of users[^fn:7].
+The work conducted at Universities of Sydney and New South Wales focused on allowing the system to run with huge number of users[^fn:9].
 The changes returned to _Unix V7_, but _AUSAM_ was never upgraded to a full 7th ed[^fn:1]
 
 <https://youtu.be/XuzeagzQwRs?si=ZXhDIsNgliZpfml3>
@@ -93,21 +93,21 @@ In 1975, Ken Thompson took a sabbatical and took a teaching job at Berkeley Univ
 The OS received quite the attention of students and faculty, resulting in the first version of _BSD Unix_ - _1BSD_.
 The lineage of BSD is extensive (not to mention their descendants are what I use) and will be a subject of the next part of our story.
 For now, remember that _BSD_ exists.
-The name will be all over the place, but proper history of _BSD_ lineage deserves deeper look.
+The name will be all over the place, but proper history of _BSD_ lineage deserves a deeper look.
 
-_Unixes_ we got to know here were research projects.
-People tried to understand what can be done with Computer using _Unix_ as the base.
+The _Unixes_ we've talked about here were research projects.
+People tried to understand what can be done with a Computer using _Unix_ as the base.
 But no one was stopping other people from earning money.
 So they did.
 
 The first wave of commercial Unixes were mostly ports allowing to run _Unix_ on wide range of hardware.
-Remember, this was way before X86 desecrated the scene and computers there were vastly different computer architectures on the market.
-It was not small feat, and this is the hobby of a lot of folks in IT.
+Remember, this was way before X86 destroyed the scene and computers, there were vastly different computer architectures on the market.
+It was no small feat, and this is the hobby of a lot of folks in IT.
 _Doom_ is supposed to be ported to _everything that can compute_.
 The good old IBM PC got _386/IX_ (aka _PC/386_) in 1977.
 Amigas got their _Amiga Unix_ in 1990 developed by _Commodore-Amiga, Inc./_.
-HP's internal line of mainframes were given _HP-Unix_ in 1984.
-Most of those don't have any value now, but it's important thread in out story.
+HP's internal line of mainframes were given _HP-UX_ (sometimes called _HP-SUX_) in 1984.
+Most of those don't have any value now, but it's important thread in our story.
 
 
 ## Solaris {#solaris}
@@ -122,12 +122,12 @@ Mind you, it's still developed (in 2023), but people simply don't want to do any
 
 ## Xenix {#xenix}
 
-Some _Unixes_ are remember for very different version.
-Xenix, released in 1970 was a fork for IBM/PC (among st others) released and developed by Microsoft.
+Some _Unixes_ are remembered for very different version.
+Xenix, released in 1970 was a fork for IBM/PC (amongst others) released and developed by Microsoft.
 Yes, a timeline exists where Windows never became the standard, and instead a MS branded Unix rules the land.
-The firt version is said to be very close to _System 7_, but with time more and more changes were applied.
+The first version is said to be very close to _System 7_, but with time more and more changes were applied.
 It was quite the buzz in the buzz, even Intel sold a complete computers with Xenix preinstalled under the name System 86.
-Measured by number of machines on which it was installed, _Xenix_ was the most common _Unix_ variant by the mid-to-late 1980s[^fn:8]
+Measured by number of machines on which it was installed, _Xenix_ was the most common _Unix_ variant by the mid-to-late 1980s[^fn:10]
 Nothing of this mattered in the death march of Windows, and the last version was released in 1991.
 
 {{< image class="centered" alt="Cover of Unix World from 1985 showing Bill Gates with &quot;Bill Gates on the future of Xenix&quot; feature" source="https://computeradsfromthepast.substack.com/p/microsofts-xenix" file="unix-world-xenix.jpg" >}}
@@ -139,14 +139,14 @@ What an issue that was!
 
 None of the systems developed outside of AT&amp;T could use the name _Unix_, as the it was a trademark.
 The management of AT&amp;T was paying attention and starting to get hungry.
-However, by 1980s, the most popular variant of non-commercial _Unix_ was _BSD[^fn:9]_.
+However, by 1980s, the most popular variant of non-commercial _Unix_ was _BSD[^fn:11]_.
 
 The _Unix_ landscape was like nothing else.
 Despite companies sharing up to 90% of code, all the _Unixes_ were incompatible.
 Hardware and software vendors were unable to support all of them.
 The was no _Single Unix_, which made it the adoption much slower and painful.
 In 1981 Ma Bell (Mother Bell, a common colloquial name for Bell companies) helped a bit by combining all of Bell's _Unixes_ into a single one - _Unix System 3_.
-It's binaries were sub-licensed for 100USD.
+Its binaries were sub-licensed for 100USD.
 Nothing big enough to trigger legal actions, but _Bell Unix_ became a commercial product.
 
 This could not go like this forever.
@@ -157,7 +157,7 @@ This removed the decree from 1956 and AT&amp;T was able to commercialize _Unix_.
 AT&amp;T swiftly introduced the (aforementioned) _Unix System V_ (note the lack of _System IV_).
 You could now buy an AT&amp;T _Unix_ for the low price of $43,000, though it allowed for commercial usage of the source code.
 Of course, add-ons (like networking) were sold separately.
-This product received it's own division within AT&amp;T - _AT&amp;T Information Systems_, later _Unix System Laboratories_ or _USL_[^fn:10].
+This product received its own division within AT&amp;T - _AT&amp;T Information Systems_, later _Unix System Laboratories_ or _USL_[^fn:12].
 
 AT&amp;T intended _System V_ to be the standard way to experience _Unix_, but others disagreed.
 The situation on the battlefield was complex, with different players putting their figures all over the place.
@@ -166,7 +166,7 @@ AT&amp;T had all the money and name to crush anyone but did not support networki
 BSD had a TCP/IP based networking and was popular among st universities.
 
 Vendor were choosing sides - IBM and HP went with _System V_ while others, like Sun choose _BSD_.
-On 27th of March, 1984 AT&amp;T officially enters computer market with their own line of computers from desktops PCs to "super-microcomputers" powered by _Unix_[^fn:10].
+On 27th of March, 1984 AT&amp;T officially enters computer market with their own line of computers from desktops PCs to "super-microcomputers" powered by _Unix_[^fn:12].
 
 {{< image class="centered" alt="An print ad for AT&amp;T Unix PC showing the computer and listing features" source="https://www.thejumpingfrog.com/product/sku/1526351" file="att-unix-pc.jpg" >}}
 Introducing the AT&amp;T Unix PC.
@@ -186,7 +186,7 @@ The system came with license agreement allowing only for usage in academic insti
 
 By 1980s features of BSD were adopted back in _System V_.
 This, and the license made users and vendors flock towards AT&amp;T, since they had to get a license anyway.
-Even curriculum was changed, since distributed source code of Unix (be it during lectures or in text books) were under AT&amp;T control[^fn:10].
+Even curriculum was changed, since distributed source code of Unix (be it during lectures or in text books) were under AT&amp;T control[^fn:12].
 This made _Lions Commentary on UNIX_ the most photocopied book in academic history.
 Owning Nth generation, barely readable copy gave significant bragging rights[^fn:1].
 
@@ -201,40 +201,47 @@ In 1984 the _Open Group for Unix Systems_ was formed by the likes of Bull, ICL,
 The group was commonly known as _BISON_, from first names of their name.
 Later, the name was changed to _X/Open_.
 
-The group decided to base their standard on _System V_ because they "decided to run the risk of exploitation by AT&amp;T rather than by IBM”[^fn:11].
-The first version of the specification, X/Open Portability Guide Issue 1 was published in 1985 and “covered basic operating system interfaces”[^fn:12].
+The group decided to base their standard on _System V_ because they "decided to run the risk of exploitation by AT&amp;T rather than by IBM”[^fn:13].
+The first version of the specification, X/Open Portability Guide Issue 1 was published in 1985 and “covered basic operating system interfaces”[^fn:14].
 
 The situation was, however, dire.
 In 1985 _MS-DOS_ had 5x the number of applications compared to _Unix_.
 This lead to the year 1986, and AT&amp;T took a $1.2 billion loss, with half of that in computer industry.
 
 In 1987 AT&amp;T and Sun enter an agreement.
-Sun, by that time, was the largest _Unix_ vendor with _Solaris_ based on _BSD 4.2_ and their own line of RISC-based microprocessors - SPARC.
-The official note stated that they are joining forces to "pursue co-development of a standard Unix operating system based on AT&amp;T’s System V, Berkeley’s BSD 4.2, and the graphical capabilities of Sun’s Sun-OS"[^fn:12].
+Sun, by that time, was the largest _Unix_ vendor with _SunOS_ based on _BSD 4.2_ and their own line of RISC-based microprocessors - SPARC.
+The official note stated that they are joining forces to "pursue co-development of a standard Unix operating system based on AT&amp;T’s System V, Berkeley’s BSD 4.2, and the graphical capabilities of Sun’s SunOS"[^fn:14].
 
 The computer world was not happy with those giants creating their own front.
 The fear was that it could lead to a total domination of the market by AT&amp;T OS running on Sun hardware.
-DEC engineer Armando Stettner, said: "When Sun and AT&amp;T announced the alliance, we at Digital were concerned that AT&amp;T was no longer the benign, benevolent progenitor of UNIX…Sun was everyone’s most aggressive competitor.
-We saw Sun’s systems were direct replacements for the VAX.
-Just think: the alliance combined our most aggressive and innovative competitor with the sole source of the system software — the balance shifted."[^fn:12],&nbsp;[^fn:13]
+DEC engineer Armando Stettner, said:
+
+> "When Sun and AT&amp;T announced the alliance, we at Digital were concerned that AT&amp;T was no longer the benign, benevolent progenitor of UNIX…Sun was everyone’s most aggressive competitor.
+> We saw Sun’s systems were direct replacements for the VAX.
+> Just think: the alliance combined our most aggressive and innovative competitor with the sole source of the system software — the balance shifted."[^fn:14],&nbsp;[^fn:15]
 
 This lead to the creation of third combined group - in 1988 representatives from Apollo, DEC, Gould Electronics, Hewlett-Packard, Honeywell-Bull, InfoCorp, MIPS, NCR, Silicon Graphics, UniSoft, and Unisys met in DEC's office in Palo Alto.
 Initially the group called themselves _Hamilton Group_ (from Hamilton Avenue, where DEC offices were located).
-Their goal was to get AT&amp;T on board, but it failed.[^fn:12]
-As a reaction, they invited IBM who happily joined and  in May of 1988 they official announced their existence under the name of _Open Software Foundation (OSF)_.[^fn:10]
-They decided not to base their standard on AT&amp;T: "Unlike X/Open, OSF planned to produce an operating system that it would license to its members, rather than function only as an advisory body."[^fn:12]
+Their goal was to get AT&amp;T on board, but it failed.[^fn:14]
+As a reaction, they invited IBM who happily joined and  in May of 1988 they official announced their existence under the name of _Open Software Foundation (OSF)_.[^fn:12]
+They decided not to base their standard on AT&amp;T:
+
+> "Unlike X/Open, OSF planned to produce an operating system that it would license to its members, rather than function only as an advisory body."[^fn:14]
 
-This had the historical effect of putting rivals, DEC and IBM on the same side.
+This had the historic effect of putting rivals, DEC and IBM on the same side.
 DEC co-founder, Ken Olsen never before shared a stage with any IBM executive before.
-Even Ken Thomson while traveling in Australia commented on this to Dennis Ritchie: "Just think, IBM and DEC in one room. We did it!"[^fn:10].
+Even Ken Thomson while traveling in Australia commented on this to Dennis Ritchie:
+
+> "Just think, IBM and DEC in one room. We did it!"[^fn:12].
+
 Sun's CEO, Scott McNealy was not as pleased, as he called the OSF the "Oppose Sun Forever".
-The heat lead to AT&amp;T and Sun creating _Unix International_, whose goal was to advice AT&amp;T on _System V_ and promote its development.
-The voting rights were based on, of course, financial contributions[^fn:12].
+The heat lead to AT&amp;T and Sun creating _Unix International_, whose goal was to advise AT&amp;T on _System V_ and promote its development.
+The voting rights were based on, of course, financial contributions[^fn:14].
 
-OSF faced internal problems due to consisting parties often competing on mainframe market.
+OSF faced internal problems due to consisting parties often competing on the mainframe market.
 This left OSI and UI as the dominant powers in the straggle, and in total they ended with over two hundred members.
 Both also developed and released their own Unixes.
-In November of 1989 AT&amp;T releases a commercial version of _System V Release 5_, and in 1990 the OSF released _OSF/1_ based on IBM's AIX and Carnegie Mellon’s MACH operating systems[^fn:12]
+In November of 1989 AT&amp;T releases a commercial version of _System V Release 5_, and in 1990 the OSF released _OSF/1_ based on IBM's AIX and Carnegie Mellon’s MACH operating systems[^fn:14]
 
 
 ## Enemy mine {#enemy-mine}
@@ -251,34 +258,38 @@ Firstly, in 1988 the IEEE 1003 was released, _Portable Operating System Interfac
 
 The second was known as _Common Open Software Environment_, the _COSE_.
 It was one more attempt to create an open, unified, standardized _Unix_.
-This time, however, it was not an fight between _Unix_ vendors.
+This time, however, it was not a fight between _Unix_ vendors.
 This was the first time they had to unite against a common enemy.
-Initially the group consisted of The Santa Cruz Operations, Unix System Laboratories, Univel, Sun, HP, and IBM
+Initially the group consisted of The Santa Cruz Operation, Unix System Laboratories, Univel, Sun, HP, and IBM
 They tasked themselves not with creating of a single unified OS, but rather with survey and document what already was there.
-The result of their work is _Spec 1170_, now known as _Single Unix Specification_.[^fn:12],&nbsp;[^fn:14]
+The result of their work is _Spec 1170_, now known as _Single Unix Specification_.[^fn:14],&nbsp;[^fn:16]
 
 This lead to the last attempt.
 In 1996 OSF and X/Open merged and became _The Open Group_ which exists till today.
-It was however too late for _Unix_ to regain it's dominance.
-The value was lost, the _Unix_ wars saw the raise of Microsoft and a new player - GNU/Linux.
+It was however too late for _Unix_ to regain its dominance.
+The value was lost, the _Unix_ wars saw the rise of Microsoft and a new player - GNU/Linux.
 
 {{< image class="centered" alt="Screenshot of an Unix system running Common Desktop Environment" source="http://sourceforge.net/p/cdesktopenv/wiki/LinuxBuild/" file="cde.png" >}}
 One of the great achievements of The Open Group was Common Desktop Environment
 {{< /image >}}
 
 The trademark of _Unix_ resides now with _The Open Group_ which is responsible for certification of products.
+It's quite expensive, so now we have two types of OSes in our lineage: Unix (with certification, like MacOS) and Unix-Like (following all requirements, but not certified - like GNU/Liunux).
+_The Open Group_ develops a very large volume of specifications under the name of _POSIX_ (_The Portable Operating System Interface_).
 
 [^fn:1]: [The hidden early history of unix the forgotten history of early unix](https://www.youtube.com/watch?v=xuzeagzqwrs)
-[^fn:2]: <https://en.wikipedia.org/wiki/CB_UNIX>
-[^fn:3]: <https://en.wikipedia.org/wiki/Multi-Environment_Real-Time>
-[^fn:4]: <https://en.wikipedia.org/wiki/PWB/UNIX>
-[^fn:5]: <https://gunkies.org/wiki/UNIX_Support_Group>
-[^fn:6]: <https://core.ac.uk/download/pdf/36714194.pdf>
-[^fn:7]: <https://www.tuhs.org/cgi-bin/utree.pl?file=AUSAM>
-[^fn:8]: <https://en.wikipedia.org/wiki/Xenix>
-[^fn:9]: <https://en.wikipedia.org/wiki/Unix_wars>
-[^fn:10]: [A Chronicle of the Unix Wars](https://www.youtube.com/watch?v=Ffh3DRFzRL0) by Asianometry on Youtube
-[^fn:11]: [UNIX STANDARDS IN THE 1990s](https://websites.umich.edu/~afuah/cases/case12.html) on University of Michigan
-[^fn:12]: [Unix Wars](https://klarasystems.com/articles/unix-wars-the-battle-for-standards/) on Klara Systems
-[^fn:13]: [The Daemon, the GNU and the Penguin](http://www.groklaw.net/article.php?story=20050601125916588) by by Peter H. Salus
-[^fn:14]: <https://en.wikipedia.org/wiki/Common_Open_Software_Environment>
+[^fn:2]: [CB Unix](https://en.wikipedia.org/wiki/CB_UNIX) on Wikipedia
+[^fn:3]: Yes, virtualization is not a new idea as it dates back to the 60s when IBM designed the System/360 to emulate other devices, like the 1401.
+[^fn:4]: [MERT](https://en.wikipedia.org/wiki/Multi-Environment_Real-Time) on Wikipedia
+[^fn:5]: [MERT](https://gunkies.org/wiki/MERT_operating_system) on Gnukies
+[^fn:6]: [PWB/UNIX](https://en.wikipedia.org/wiki/PWB/UNIX) on Wikipedia
+[^fn:7]: [Unix Support Group](https://gunkies.org/wiki/UNIX_Support_Group) on Gnukies
+[^fn:8]: [MUNIX, A MULTIPROCESSING VERSION OF UNIX](https://core.ac.uk/download/pdf/36714194.pdf) by John Alfred Hawley, Naval Postgrade School, June 1975
+[^fn:9]: [AUSAM](https://www.tuhs.org/cgi-bin/utree.pl?file=AUSAM) on The Unix Heritage Society
+[^fn:10]: [Xenix](https://en.wikipedia.org/wiki/Xenix) on Wikipedia
+[^fn:11]: [Unix Wars](https://en.wikipedia.org/wiki/Unix_wars) on Wikipedia
+[^fn:12]: [A Chronicle of the Unix Wars](https://www.youtube.com/watch?v=Ffh3DRFzRL0) by Asianometry on Youtube
+[^fn:13]: [UNIX STANDARDS IN THE 1990s](https://websites.umich.edu/~afuah/cases/case12.html) on University of Michigan
+[^fn:14]: [Unix Wars](https://klarasystems.com/articles/unix-wars-the-battle-for-standards/) on Klara Systems
+[^fn:15]: [The Daemon, the GNU and the Penguin](http://www.groklaw.net/article.php?story=20050601125916588) by by Peter H. Salus
+[^fn:16]: [COSE](https://en.wikipedia.org/wiki/Common_Open_Software_Environment) on Wikipedia
diff --git a/content/unix-history/_index.md b/content/unix-history/_index.md
index ee15bae..50d2e32 100644
--- a/content/unix-history/_index.md
+++ b/content/unix-history/_index.md
@@ -1,7 +1,7 @@
 +++
 title = "Unix history"
 author = ["Michał Sapka"]
-date = 2024-03-09T21:03:00+01:00
+date = 2024-05-30T21:03:00+02:00
 categories = ["unix-history"]
 draft = false
 weight = 2001
@@ -23,3 +23,18 @@ This site is a fanpage, and a love letter to computer history. To the brilliant
 {{< menu "unix-history" >}}
 Dune
 {{< /menu >}}
+
+
+## Acknowledgements {#acknowledgements}
+
+-   [Jeff](http://wovenmemories.net/), for proofreading Part III
+-   [Tomáš](https://www.analognowhere.com/), for providing dedicated artwork
+
+
+## Changes {#changes}
+
+-   _2024-05-.._: First release of Part 3
+-   _2024-05-30_: Extract into self-contained website
+-   _2024-04-08_: Extract Unix History to dedicated section
+-   _2024-03-16_: First relase of Part 2
+-   _2024-03-09_: First relase of Part 1