[talks/lbs] Reworked formatting, following changes to presentation system

1 files changed, 31 insertions, 40 deletions

diff --git a/src/talks/linuxgraphy-by-strabo/index.md b/src/talks/linuxgraphy-by-strabo/index.md
index edb7797..c77d6a6 100644
--- a/src/talks/linuxgraphy-by-strabo/index.md
+++ b/src/talks/linuxgraphy-by-strabo/index.md
@@ -4,14 +4,16 @@
 
 
 
-&&clide
+&&centered &&clide
 
 &&font35
 # Linuxgraphy by Strabo
 &&/font
-<br>
+*Made by [Syndamia](https://syndamia.com)*
 
-&&centered &&frow &&flexer
+&&lineb4 &&ftable
+
+&&lineb1
 
 2000 years ago [Strabo](https://en.wikipedia.org/wiki/Strabo) published [Geography](https://en.wikipedia.org/wiki/Geography), in which he laid out the world as it was known to the Romans and Greeks.
 <br><br>
@@ -19,13 +21,12 @@ Today, I'll lay out Linux as it is known to me.
 
 ![](https://upload.wikimedia.org/wikipedia/commons/thumb/e/ed/Strabo.jpg/199px-Strabo.jpg)
 
-&&flexer &&/frow &&/centered
+&&lineb1
 
-&&/centered &&flexer
+&&/table
 
-&&fright *Made by [Syndamia](https://syndamia.com)* &&/fright
 
-&&/slide
+&&/clide &&/centered
 
 
 
@@ -33,7 +34,7 @@ Today, I'll lay out Linux as it is known to me.
 
 # Contents
 
-&&frow &&font20
+&&ftable &&font20
 
 1. Brief timeline
 2. Structure of UNIX-likes
@@ -79,7 +80,7 @@ Today, I'll lay out Linux as it is known to me.
       2. OpenWRT
 7. Full setup and demonstration with Linux Mint
 
-&&/font &&/frow
+&&/font &&/table
 
 &&/slide
 
@@ -113,13 +114,15 @@ This process is called [batch processing](https://en.wikipedia.org/wiki/Batch_pr
 
 
 
-&&slide &&flexer &&font27
+&&font27 &&slide
 
 #### 1960s
 
 But by far the biggest bottle neck were peripherals, tapes and punch cards were extremely slow.
 [Multiprogramming](https://en.wikipedia.org/wiki/Computer_multitasking#Multiprogramming) was born: while the current job is waiting for a peripheral, doing nothing, another job would be started.
 
+&&lineb2
+
 American Airlines (in collaboration with IBM) created a [travel reservation system](https://en.wikipedia.org/wiki/Sabre_%28travel_reservation_system%29), where travel agents would search, price and book services provided by the airline.
 Such systems increased the requirements of a computer system:
 
@@ -128,9 +131,11 @@ Such systems increased the requirements of a computer system:
 - Storage organization, also following the rise of disks
 - Data communication links (were often phone lines)
 
+&&lineb2
+
 Another important factor is the rise of minicomputers: much smaller and incredibly cheap (compared to the alternatives) computers, which lead to an increase in digital technology usage by businesses.
 
-&&/font &&flexer &&/slide
+&&/slide &&/font
 
 
 
@@ -163,8 +168,7 @@ Some of it's novel ideas include, but are not limited to:
 Multics was very ambitous and had a lot of great ideas and minds behind it, but it ultimately grew too large and failed.
 Programming was done mostly in [Bell Labs](TODO), who pulled pretty quickly from the project.
 
-&&flexer
-&&frow
+&&lineb1 &&ftable
 
 &&font18
 ![](https://upload.wikimedia.org/wikipedia/commons/f/f8/Ken-Thompson-2019.png =250x)  
@@ -173,7 +177,7 @@ Programming was done mostly in [Bell Labs](TODO), who pulled pretty quickly from
 *Ken Thompson and Dennis Ritchie in 1973*
 &&/font
 
-&&fccen &&expand
+&&cont
 
 [Ken Thompson](TODO), one of the programmers that worked on it, still had some desire to work on operating systems.  
 After Bell Labs left Multics, he made a program for maximizing the throughput of a disk on a PDP-7.
@@ -181,10 +185,9 @@ To test it, he wrote some programs over time and eventually realised an operatin
 
 This marked the birth of UNIX, an operating system, based and expanded on many of Multic's ideas (except the "grow too large" one).
 
-&&/expand &&/fccen
+&&/cont
 
-&&/frow
-&&flexer
+&&/table
 &&/slide &&/font
 
 
@@ -195,13 +198,13 @@ This marked the birth of UNIX, an operating system, based and expanded on many o
 
 Ignoring [standards](https://unix.stackexchange.com/questions/14368/difference-between-posix-single-unix-specification-and-open-group-base-specifi/14415) and [specifications](https://unix.stackexchange.com/questions/87686/what-makes-an-operating-system-unix-like), in my opinion, from the point of a user, a UNIX-like OS has the following components:
 
-&&flexer
+&&lineb1
 
 1. **shell**: A programmable replaceable command-line interpreter, with utilities for managing the whole system and support for pipelines and I/O redirection
 2. **UNIX-style file system**: [Filesystem](https://en.wikipedia.org/wiki/Unix_filesystem) as a rooted tree (even for all seperate volumes), objects (nodes) in the file system are [inodes](TODO) and an inode can be [(at least)](https://en.wikipedia.org/wiki/Unix_file_types) either a regular file, directory or devices. Permissions are set per owner, group members and other users.
 3. **kernel**: Program that manages all communication and operations between the hardware and software
 
-&&flexer
+&&lineb3
 
 &&font20 *For now we'll generally just look over some of the common stuff and go into detail later, while in Linux.* &&/font
 
@@ -213,7 +216,7 @@ Ignoring [standards](https://unix.stackexchange.com/questions/14368/difference-b
 
 ## 2.1. shell
 
-&&flexer &&frow
+&&lineb2 &&ftable
 
 &&cont
 Our operating system is divided into layers, [like an onion](https://youtu.be/-FtCTW2rVFM?t=57).  
@@ -224,9 +227,9 @@ shells provide user interfaces, [both](http://en.wikipedia.org/wiki/Shell_%28com
 While on the topic of UNIX, we'll only discuss the former.
 &&/cont
 
-![](./img/unix-layers.png)
+&&centered ![](./img/unix-layers.png) &&/centered
 
-&&/frow &&flexer &&/slide &&/font
+&&/table &&/slide &&/font
 
 
 
@@ -234,8 +237,7 @@ While on the topic of UNIX, we'll only discuss the former.
 
 Command-line shells operate solely with text, preferrably without too fancy formatting (there are very modern ones that can handle images, but these are an exception, rather than the norm).
 
-&&flexer
-&&frow
+&&lineb1 &&ftable
 
 Historically, video displays (at first [CRT](TODO) ones) became widely available in the late 1970s, but before that the "mainstream" way to access a computer was with a teleprinter (commonly known as teletype): effectively a (typewriter) keyboard and a fast text priner, connected to a computer.
 
@@ -243,11 +245,8 @@ Historically, video displays (at first [CRT](TODO) ones) became widely available
 ![](https://upload.wikimedia.org/wikipedia/commons/thumb/d/df/ASR-33_at_CHM.agr.jpg/1280px-ASR-33_at_CHM.agr.jpg =320x)  
 *Teletype Model 33 by [Arnold Reinhold](https://commons.wikimedia.org/wiki/User:ArnoldReinhold)*
 &&/fright &&/font
-&&/frow
-
-&&flexer
 
-&&frow
+&&tarow
 
 &&font18
 ![](https://upload.wikimedia.org/wikipedia/commons/thumb/9/99/DEC_VT100_terminal.jpg/675px-DEC_VT100_terminal.jpg?20131106192408 =320x)  
@@ -257,7 +256,7 @@ Historically, video displays (at first [CRT](TODO) ones) became widely available
 Later, those were replaced by terminals, a "normal" keyboard and a display, connected to a computer.
 **The** most popular and influential one was the [VT100](TODO), with it's most influential feature being neven seen before support of [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code): special text that would modify the cursor position and later being able to, for example, change colors for specific text.
 
-&&/frow &&/slide &&/font
+&&/table &&/slide &&/font
 
 
 
@@ -266,8 +265,6 @@ Later, those were replaced by terminals, a "normal" keyboard and a display, conn
 In UNIX CLI shells, most of the commands are just regular programs.
 These programs could exist in more than one folder: `/bin` and `/usr/bin` for example, so we store every location in a variable called "PATH".
 
-&&flexer
-
 Command-line UNIX shells always have the following features:
 
 - pipelines: being able to redirect the output from one command to another without limit
@@ -300,15 +297,11 @@ Command-line UNIX shells always have the following features:
 
 ## 2.2. UNIX-style file system
 
-&&flexer
-
 - Rooted singular tree of directories. Disk partitions, removeable media, etc. all live in that tree.
 - Each tree object (node) is an [i(ndex)node](TODO), containing type, ownership, access, internal data and any other metadata, but **not** name!
 - Directory inodes (files) contain a table with rows of names and inode numbers, mapping a file name to it's contents. Each row is called a [hard link](https://en.wikipedia.org/wiki/Hard_link). Every directory has a hard link to itself, called ".", and a hard link to it's parent, called "..".
 
-&&flexer
-
-&&fcol ![](./img/unix-dir-tree.png) &&/fcol
+![](./img/unix-dir-tree.png)
 
 &&/slide &&/font
 
@@ -353,16 +346,14 @@ The main attributes that every inode has are as follows:
 
 ## 2.3. Kernel
 
-&&flexer
+&&lineb2
 
 The kernel is completely separated from everything else, it only communicates with hardware and exposes an API to have other programmes communicate with it.
 
-&&flexer
+&&lineb2
 
 Linux is **not** an operating system, it is a kernel!!!
 
-&&flexer
-
 &&/slide &&/font