ioriot and some new fonts

19 files changed, 23 insertions, 7 deletions

diff --git a/content/gemtext/gemfeed/atom.xml b/content/gemtext/gemfeed/atom.xml
index 152cf019..465ee3ac 100644
--- a/content/gemtext/gemfeed/atom.xml
+++ b/content/gemtext/gemfeed/atom.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
-    <updated>2021-05-14T09:34:34+01:00</updated>
+    <updated>2021-05-14T09:41:13+01:00</updated>
     <title>buetow.org feed</title>
     <subtitle>Having fun with computers!</subtitle>
     <link href="gemini://buetow.org/gemfeed/atom.xml" rel="self" />
@@ -184,7 +184,7 @@ jgs\__/'---'\__/
 <p>This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. </p>
 <a class="textlink" href="https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot">https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot</a><br />
 <p>I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work involving I/O.</p>
-<p>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of Systemtap. Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</p>
+<p>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</p>
 <p>Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those.</p>
 <h1>The article</h1>
 <p>With I/O Riot IT administrators can load test and optimize the I/O subsystem of Linux-based operating systems. The tool makes it possible to record I/O patterns and replay them at a later time as often as desired. This means bottlenecks can be reproduced and eradicated. </p>
diff --git a/content/html/contact-information.html b/content/html/contact-information.html
index 658642be..fa83e6fc 100644
--- a/content/html/contact-information.html
+++ b/content/html/contact-information.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2008-06-26-perl-poetry.html b/content/html/gemfeed/2008-06-26-perl-poetry.html
index 160a4936..9c672122 100644
--- a/content/html/gemfeed/2008-06-26-perl-poetry.html
+++ b/content/html/gemfeed/2008-06-26-perl-poetry.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2010-05-09-the-fype-programming-language.html b/content/html/gemfeed/2010-05-09-the-fype-programming-language.html
index 1088bf2a..64736347 100644
--- a/content/html/gemfeed/2010-05-09-the-fype-programming-language.html
+++ b/content/html/gemfeed/2010-05-09-the-fype-programming-language.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2011-05-07-perl-daemon-service-framework.html b/content/html/gemfeed/2011-05-07-perl-daemon-service-framework.html
index 847cab0f..c74433ee 100644
--- a/content/html/gemfeed/2011-05-07-perl-daemon-service-framework.html
+++ b/content/html/gemfeed/2011-05-07-perl-daemon-service-framework.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2016-04-03-offsite-backup-with-zfs.html b/content/html/gemfeed/2016-04-03-offsite-backup-with-zfs.html
index 8eb59bd0..9d27b09c 100644
--- a/content/html/gemfeed/2016-04-03-offsite-backup-with-zfs.html
+++ b/content/html/gemfeed/2016-04-03-offsite-backup-with-zfs.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html b/content/html/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
index 0939c297..af6385bf 100644
--- a/content/html/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
+++ b/content/html/gemfeed/2016-04-16-offsite-backup-with-zfs-part2.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html b/content/html/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html
index eed4561b..c440de37 100644
--- a/content/html/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html
+++ b/content/html/gemfeed/2016-05-22-spinning-up-my-own-authoritative-dns-servers.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2016-11-20-methods-in-c.html b/content/html/gemfeed/2016-11-20-methods-in-c.html
index 544ad28f..9e3df340 100644
--- a/content/html/gemfeed/2016-11-20-methods-in-c.html
+++ b/content/html/gemfeed/2016-11-20-methods-in-c.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.draft.html b/content/html/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.html
index 47075196..81d79703 100644
--- a/content/html/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.draft.html
+++ b/content/html/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
@@ -48,7 +49,7 @@ h2, h3 {
 </style>
 </head>
 <body>
-<p># Realistic load testing with I/O Riot for Linux</p>
+<h1>Realistic load testing with I/O Riot for Linux</h1>
 <pre>
        .---.
       /     \
@@ -64,7 +65,7 @@ jgs\__/'---'\__/
 <p>This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. </p>
 <a class="textlink" href="https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot">https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot</a><br />
 <p>I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work involving I/O.</p>
-<p>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of Systemtap. Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</p>
+<p>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</p>
 <p>Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those.</p>
 <h1>The article</h1>
 <p>With I/O Riot IT administrators can load test and optimize the I/O subsystem of Linux-based operating systems. The tool makes it possible to record I/O patterns and replay them at a later time as often as desired. This means bottlenecks can be reproduced and eradicated. </p>
diff --git a/content/html/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html b/content/html/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html
index 9e1e6e16..d9ad256f 100644
--- a/content/html/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html
+++ b/content/html/gemfeed/2021-04-22-dtail-the-distributed-log-tail-program.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2021-04-24-welcome-to-the-geminispace.html b/content/html/gemfeed/2021-04-24-welcome-to-the-geminispace.html
index 2a30510d..bf48e0c1 100644
--- a/content/html/gemfeed/2021-04-24-welcome-to-the-geminispace.html
+++ b/content/html/gemfeed/2021-04-24-welcome-to-the-geminispace.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/2021-05-15-buetow.org.sh-One-Bash-script-to-rule-it-all.draft.html b/content/html/gemfeed/2021-05-15-buetow.org.sh-One-Bash-script-to-rule-it-all.draft.html
index e1f53ec8..0d644137 100644
--- a/content/html/gemfeed/2021-05-15-buetow.org.sh-One-Bash-script-to-rule-it-all.draft.html
+++ b/content/html/gemfeed/2021-05-15-buetow.org.sh-One-Bash-script-to-rule-it-all.draft.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/gemfeed/atom.xml b/content/html/gemfeed/atom.xml
index 8f66a786..693a3656 100644
--- a/content/html/gemfeed/atom.xml
+++ b/content/html/gemfeed/atom.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="utf-8"?>
 <feed xmlns="http://www.w3.org/2005/Atom">
-    <updated>2021-05-14T09:34:34+01:00</updated>
+    <updated>2021-05-14T09:41:13+01:00</updated>
     <title>buetow.org feed</title>
     <subtitle>Having fun with computers!</subtitle>
     <link href="https://buetow.org/gemfeed/atom.xml" rel="self" />
@@ -184,7 +184,7 @@ jgs\__/'---'\__/
 <p>This text first was published in the german IT-Administrator computer Magazine. 3 years have passed since and I decided to publish it on my blog too. </p>
 <a class="textlink" href="https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot">https://www.admin-magazin.de/Das-Heft/2018/06/Realistische-Lasttests-mit-I-O-Riot</a><br />
 <p>I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work involving I/O.</p>
-<p>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of Systemtap. Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</p>
+<p>I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.</p>
 <p>Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those.</p>
 <h1>The article</h1>
 <p>With I/O Riot IT administrators can load test and optimize the I/O subsystem of Linux-based operating systems. The tool makes it possible to record I/O patterns and replay them at a later time as often as desired. This means bottlenecks can be reproduced and eradicated. </p>
diff --git a/content/html/gemfeed/index.html b/content/html/gemfeed/index.html
index 6a06d90e..55f0fc7e 100644
--- a/content/html/gemfeed/index.html
+++ b/content/html/gemfeed/index.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/index.html b/content/html/index.html
index 6f5b5dfd..6c8bed44 100644
--- a/content/html/index.html
+++ b/content/html/index.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/html/resources.html b/content/html/resources.html
index b021c733..98645b69 100644
--- a/content/html/resources.html
+++ b/content/html/resources.html
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;
diff --git a/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md b/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md
index 5bb5086f..260a0368 100644
--- a/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md
+++ b/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md
@@ -21,7 +21,7 @@ This text first was published in the german IT-Administrator computer Magazine.
 
 I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work involving I/O.
 
-I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of Systemtap. Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.
+I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency.
 
 Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those.
 
diff --git a/header.html.part b/header.html.part
index 91f0d338..8592effa 100644
--- a/header.html.part
+++ b/header.html.part
@@ -37,6 +37,7 @@ pre {
     border: 1px dashed #BB0000;
     border-radius: 8px;
     padding: 5px;
+    font-family: "Lucida Console", "Courier New", monospace;
 }
 h1 {
     text-align: center;