[talks/lbs] Finished package manager and war on distros slides

1 files changed, 40 insertions, 12 deletions

diff --git a/src/talks/linuxgraphy-by-strabo/index.md b/src/talks/linuxgraphy-by-strabo/index.md
index bcf578f..a414952 100644
--- a/src/talks/linuxgraphy-by-strabo/index.md
+++ b/src/talks/linuxgraphy-by-strabo/index.md
@@ -1234,17 +1234,46 @@ WantedBy=multi-user.target
 
 
 
-&&clide
+&&slide
 
 ## 5.3. Package manager
 
-Running a program is as simple as putting the executable in a nice folder, like `/usr/bin`.
-However this process isn't very convenient if you're only using a shell and more tedious when using a graphical shell.
+&&lineb1
+
+Programs are just executable files, usually placed in a specific folder, like `/usr/bin`.
 
-The solution is to use a package manager, a single command with which you can download, install and update any program from a variety of (web) sources, just by specifying it's name.
-Often a package manager supports installing dependencies and checking for package tampering.
+- MLL comes with ~100 executables (and ~230 after my script)
+- my Debian server has ~1000 installed packages
+- my current desktop Gentoo setup has ~1500 installed packages
+- my old Fedora setups have reached ~3000 packages on multiple occasions
 
-&&/clide
+Updating all of them means replacing all of the binaries, means tracking where each one came from, installing a new one might require installing multiple others and so on.
+
+On modern systems, managing binaries is automated by an application called a package manager.
+
+&&/slide
+
+
+
+&&clide &&font35
+
+Additional benefits of package management automation include:
+
+- checking for package validity (and tampering)
+- utilising multiple server mirrors
+- automatic dependency management and installation
+- version caveats
+- (indirectly) improved stability because of maintainer compatibility checks
+
+&&lineb1
+
+```
+apt install PKG
+apt remove PKG
+apt upgrade
+```
+
+&&/font &&/clide
 
 
 
@@ -1271,20 +1300,19 @@ It's main components are:
 
 # 6. War on distros
 
-A distribution is a complete set of of all applications that we've talked so far.
+A distribution is a complete set of of all applications that you might use.
 
 Overall, there are five distributions from which 90% of all other distros are based upon:
 
 1. [Slackware](http://www.slackware.com/): as the oldest still maintained distro, it served as inspiration for a lot of other distros. It aims to be as simple and as close to UNIX as possible.
-2. [Debian](https://www.debian.org/) (and [Ubuntu](https://ubuntu.com/)): it is the most popular distribution (if we also include Ubuntu, since they're so similar). Ubuntu aims to be modern and fancy, while Debian aims to be as stable as possible, which makes it the most popular in server usage.
+2. [Debian](https://www.debian.org/) (and [Ubuntu](https://ubuntu.com/)): it is the most popular distribution (if we also include Ubuntu). Ubuntu aims to be modern and fancy, while Debian aims to be as stable as possible, which makes it the most popular in server usage.
 4. [Gentoo](https://www.gentoo.org/): the distribution which defined non-binary software distribution
 5. [Arch Linux](https://archlinux.org/): a very popular and modern distribution with the goal of providing the latest and greatest software.
 
 We haven't touched too much, but Linux distributions aren't limited to desktop or server computers.
-Two more uncommon ones are:
 
-1. AOSP: the base of the whole Android operating system
-2. OpenWRT: a router operating system
+1. [AOSP](https://en.wikipedia.org/wiki/Android_%28operating_system%29#AOSP): the base of the whole Android operating system
+2. [OpenWRT](https://en.wikipedia.org/wiki/OpenWrt): a router operating system
 
 &&/font &&/slide
 
@@ -1321,7 +1349,7 @@ Currently there won't be an official recording of the process, you should've bee
 All of these contain, at most, small paraphrased sentences in the slides.
 They served as personal educational and reference tools.
 
-- [wikipedia](https://en.wikipedia.org/) and [stackexchange](https://stackexchange.com/) has been used extensively and linked where appropriate.
+- [wikipedia](https://en.wikipedia.org/) and [stackexchange](https://stackexchange.com/) have been used extensively and linked where appropriate.
 - [CS416 - Operating Systems Design](https://people.cs.rutgers.edu/~pxk/416/index.html) by [Paul Krzyzanowski](https://people.cs.rutgers.edu/~pxk/rutgers/) at [Rutgers State University](https://www.cs.rutgers.edu/)
 - [Origins and History of UNIX, 1969-1995](https://web.archive.org/web/20220713165958/https://homepage.cs.uri.edu/~thenry/resources/unix_art/ch02s01.html) from [The Art of Unix Programming](https://web.archive.org/web/20220611160552/https://homepage.cs.uri.edu/~thenry/resources/unix_art/index.html) by Eric Steven Raymond
 - [Ken Thompson interviewed by Brian Kernighan at VCF East 2019](https://www.youtube.com/watch?v=EY6q5dv_B-o) by [Vintage Computer Federation](https://vcfed.org/)