Summary Files Commits Branches @commit @diff @stats
path: root / src / slides
diff options
context:
space:
mode:
Commite1854cef24aae1c0137f38ff7c088dfc9cb42fe4 (patch)
Author
 Syndamia <kamen@syndamia.com>
2025-07-28 17:49:36 +0300
Committer
 Syndamia <kamen@syndamia.com>
2025-07-28 17:49:36 +0300
Filesb6391dd793413e013e66f502538800420154132b /src/slides
syndamia.com-e1854cef24aae1c0137f38ff7c088dfc9cb42fe4.tar
syndamia.com-e1854cef24aae1c0137f38ff7c088dfc9cb42fe4.tar.gz
syndamia.com-e1854cef24aae1c0137f38ff7c088dfc9cb42fe4.zip
Parenta8269cc3de8ed385ebb9b667a709a2991185161d (diff)
fix: Update lists with empty lines in between items
With a new dunbar update, unordered/ordered lists specify a possible empty line between all list items (instead of being simple aliases for bulleted/numbered list).
2 files changed, 10 insertions, 12 deletions
-rw-r--r--src/slides/demo/index.du15
-rw-r--r--src/slides/linuxgraphy-by-strabo/index.du7
diff --git a/src/slides/demo/index.du b/src/slides/demo/index.du
index f9dc241..fe71321 100644
--- a/src/slides/demo/index.du
+++ b/src/slides/demo/index.du
@@ -68,16 +68,13 @@ An easy example is the image of the Great Britain flag (part of [url https://git
## Why?
-:bulleted
--
-.p Programs like Microsoft PowerPoint and LibreOffice Impress have very poor compatibility, between programs, versions, languages and even operating systems.
+:unordered
+- Programs like Microsoft PowerPoint and LibreOffice Impress have very poor compatibility, between programs, versions, languages and even operating systems.
A web-based solution is significantly more consistent and flexible.
--
-.p Ideally, the system would be made well enough that creating a presentation would be significantly faster than with one of those.
+- Ideally, the system would be made well enough that creating a presentation would be significantly faster than with one of those.
--
-.p Making my own system means I can tailor it to my needs and preferences.
+- Making my own system means I can tailor it to my needs and preferences.
Looking around other [url https://gist.github.com/vasilisvg/1611562 HTML-based presentation tools]:
.bulleted
@@ -149,7 +146,7 @@ Maybe this should be changed?
The source Markdown for the predvious slide is:
```dunbar
-'snippet 114 145 ./index.du
+'snippet 111 142 ./index.du
:middle_slide
@@ -185,7 +182,7 @@ The source Markdown for the predvious slide is:
The source Markdown for the predvious slide is:
```dunbar
-'snippet 155 181 ./index.du
+'snippet 152 178 ./index.du
:slide27
diff --git a/src/slides/linuxgraphy-by-strabo/index.du b/src/slides/linuxgraphy-by-strabo/index.du
index a203bbb..1e7dfb1 100644
--- a/src/slides/linuxgraphy-by-strabo/index.du
+++ b/src/slides/linuxgraphy-by-strabo/index.du
@@ -64,6 +64,7 @@
1. Shell
2. UNIX-style file system
2. Kernel
+
[$br2]
3. Linux from the inside
@@ -212,14 +213,14 @@ In the beginning, programming was done mostly by [url https://en.wikipedia.org/w
.p
Ignoring [url https://unix.stackexchange.com/questions/14368/difference-between-posix-single-unix-specification-and-open-group-base-specifi/14415 standards] and [url https://unix.stackexchange.com/questions/87686/what-makes-an-operating-system-unix-like specifications], in my opinion, from the point of a user, a UNIX-like OS has the following components:
-[$br4]
+[$br2]
.ordered
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]=: [url https://en.wikipedia.org/wiki/Unix_filesystem Filesystem] as a single rooted tree, objects (nodes) in the file system are [url https://en.wikipedia.org/wiki/Inode inodes] and an inode can be [url https://en.wikipedia.org/wiki/Unix_file_types (at least)] either a regular file, directory or devices. Permissions per users and group.
3. =[kernel]=: Program that manages all communication and operations between the hardware and software
-[$br4]
+[$br2]
.font18 *[For now we'll generally just look over some of the common stuff and go into detail later, while in Linux.]*
@@ -518,7 +519,7 @@ All process information is stored in a data structure, called a *[process contro
Not to be confused with a [url https://en.wikipedia.org/wiki/Printed_circuit_board printed circuit board]!\n
A PCB's data can be split into three categories:
-.ordered
+.numbered
1. =[Process identification]= - the ID of the process itself, of it's parent process, of it's owner (user), etc.
2. =[Process state]= - as described, the processor state, etc.\n
On a context switch, values in registers are put into the stopped PCB and then are loaded from the running PCB.