askiiart/engl-2311-blog
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add Vanilla OS post, other minor fixes (fix sitemap script)

Browse source
This commit is contained in:
askiiart 2024-09-19 10:57:15 -05:00
parent 0eb45fcec5
commit 6e1ef23aab
Signed by untrusted user who does not match committer: askiiart
GPG key ID: EA85979611654C30
12 changed files with 326 additions and 37 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
assets/vanilla-os/1.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 206 KiB

BIN
assets/vanilla-os/2.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 211 KiB

15
blog/blendos.html
View file

@ -104,8 +104,7 @@
(as used by Fedora atomic); instead, it just completely rebuilds (as used by Fedora atomic); instead, it just completely rebuilds
the system every single time. Because of this, it takes a long the system every single time. Because of this, it takes a long
time to run the updater/rebuilder, even to just install one more time to run the updater/rebuilder, even to just install one more
package.<a href="#fn3" class="footnote-ref" id="fnref3" package.</p>
role="doc-noteref"><sup>3</sup></a></p>
<p>Besides that, my only complaints are:</p> <p>Besides that, my only complaints are:</p>
<ol type="1"> <ol type="1">
<li>The <code>akshara</code>'s (the update/rebuild tool) major <li>The <code>akshara</code>'s (the update/rebuild tool) major
@ -184,23 +183,13 @@
actually inherits from the <code>gnome</code> track.<a actually inherits from the <code>gnome</code> track.<a
href="#fnref2" class="footnote-back" href="#fnref2" class="footnote-back"
role="doc-backlink">↩︎</a></p></li> role="doc-backlink">↩︎</a></p></li>
<li id="fn3"><p>In the meantime while I've been writing this, a
community member has implemented <a
href="https://aur.archlinux.org">AUR</a> package caching, which
can definitely cut down on the build time by a lot, depending on
how many packages you're using from the AUR. However, this
hasn't been added to the upstream version of Akshara yet, though
through no fault of the blendOS team; as far as I know, the dev
who implemented it just hasn't sent it over to be added yet.<a
href="#fnref3" class="footnote-back"
role="doc-backlink">↩︎</a></p></li>
</ol> </ol>
</aside> </aside>
<iframe src="https://john.citrons.xyz/embed?ref=askiiart.net" style="margin-left:auto;display:block;margin-right:auto;max-width:732px;width:100%;height:94px;border:none;"></iframe> <iframe src="https://john.citrons.xyz/embed?ref=askiiart.net" style="margin-left:auto;display:block;margin-right:auto;max-width:732px;width:100%;height:94px;border:none;"></iframe>
<script src="/prism.js"></script> <script src="/prism.js"></script>
</body> </body>
<footer> <footer>
<p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a></p> <p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a>&ensp;|&ensp;<a href="/glossary.html">Glossary</a></p>
<small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small> <small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small>
</footer> </footer>
</html> </html>

121
blog/vanilla-os.html Normal file
View file

@ -0,0 +1,121 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta content="width=device-width, initial-scale=1" charset="utf-8" />
<link rel="icon" href="/assets/askiiart.gif" type="image/icon">
<title>OCI Images as a "Filesystem": Vanilla OS</title>
<link href="/style.css" type="text/css" rel="stylesheet" />
<link href="/prism.css" type="text/css" rel="stylesheet" />
</head>
<body class="line-numbers">
<h1 id="oci-images-as-a-filesystem-vanilla-os">OCI Images as a
"Filesystem": Vanilla OS</h1>
<p>In looking for a layered solution to blendOS's issues, I
found that the lead maintainer and creator of blendOS was
looking into using OCI images, and has even forked a repo from
Vanilla OS. So I'm trying out Vanilla OS's usage of OCI images
(which are inherently layered) to see about implementing a
similar system in blendOS.</p>
<h2 id="installation">Installation</h2>
<p>Installation is pretty simple, you're again dropped into a
simple GNOME session with a GTK installer:</p>
<img src="/assets/vanilla-os/1.png"
title="A basic GNOME session with a white GTK-based installer; it&#39;s showing the date and time/time zone selector." alt="A basic GNOME session with a white GTK-based installer; it&#39;s showing the date and time/time zone selector." />
<p>The process was very similar to blendOS's, though it also
detects virtual machines and offers an option to install tools
(e.g. clipboard sharing, video drivers) to help with that.</p>
<p>Another notable bit is that it requires more space than
blendOS, with a minimum disk size of 50 GB, but given its A/B
slot architecture (which I'll get to later), this makes
sense.</p>
<h2 id="first-boot">First boot</h2>
<p>On first boot, there's a very similar setup tool, surely
based off the installer. It makes you put in your language,
timezone, etc. again, which I was a bit annoyed by, but it's no
big deal. Then it has you create your login, select what you
want installed (from basic programs like a calendar, office
suite, etc.), then restarts and does all that.</p>
<img src="/assets/vanilla-os/2.png"
title="A similar wizard to the installer; it has the Vanilla OS logo and says &quot;Welcome&quot;, &quot;Make your choices, this wizard will take care of everything&quot;" alt="A similar wizard to the installer; it has the Vanilla OS logo and says &quot;Welcome&quot;, &quot;Make your choices, this wizard will take care of everything&quot;" />
<p>Then you just get a little slideshow detailing automatic
updates, its Apx package manager, and other basics, nothing
interesting, and nothing I care about.</p>
<h2 id="usage-and-configuration">Usage and configuration</h2>
<p>I tried checking the docs (<em>Vanilla OS Docs</em>), which
by themselves were difficult to find. They're a bit hidden in
"Help" despite being <em>absolutely essential</em> to using this
distro[^1]. But what I found easily was screenshots of
Overwatch. (<em>Vanilla OS</em>)</p>
<p>Regardless, once I found the docs, I tried to figure out how
it worked, and I was still very confused. After looking over it
again, I decided to check Apx's docs, its package manager, and
found how to install packages, of course. (<em>Vanilla OS
Docs</em>) I tried to install GParted; after it not running at
first due to Vanilla OS not being configured correctly and not
showing a password prompt for it, causing GParted to exit, I ran
it in the terminal with <code>sudo</code>, just to get a
permission denied error. That's because all packages are
installed in containers, there is no system package manager...
kinda.</p>
<h3 id="abroot">ABRoot</h3>
<p>ABRoot is the magic behind Vanilla OS's OCI image backend. As
far as I can tell (again, I don't believe there are no relevant
for docs for this) it essentially generates a tarball of the
relevant data for the new iteration, then symlinks to either
that or the current iteration on boot, depending on what the
user selects. It provides essentially no advantages over
blendOS's approach, and is, in my opinion, massively
overcomplicated. (<em>GitHub: Vanilla-os/abroot</em>)</p>
<p>It also acts as a package manager of sorts - it's the only
way to install packages system-wide on Vanilla OS, and it does
this by running <code>apt</code> when the new image is built,
similar to Akshara.</p>
<p>ABRoot's config file is at
<code>/etc/abroot/abroot.json</code>, but it doesn't support
declarative system-wide packages. Instead, run the
following:</p>
<div class="sourceCode" id="cb1"><pre
class="language-bash"><code class="language-bash"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="ex">abroot</span> pkg add <span class="va">$PACKAGE_NAME</span></span></code></pre></div>
<p>(<em>Install additional drivers and libraries in Vanilla
OS</em>)</p>
<h2 id="conclusion">Conclusion</h2>
<p>Vanilla OS wasn't very helpful as to OCI-based layers, but I
don't think it was a complete waste of time. Vanilla OS gave me
some ideas, and I like its backend's ideas; it will most likely
serve as inspiration for when I add layers to blendOS. Plus, my
idea would have an advantage: compression.</p>
<p>But I'll get into it later, once it's a bit more fleshed out;
plus, that's not the point of this post anyways.</p>
<p>P.S. I can't get it across while keeping this post decent
quality and on-topic, but I need to emphasize how confusing the
docs were for Vanilla OS. It feels like they try to appeal to
users with basic tech literacy while not explaining how it
actually works or what anything does. They write how-to guides,
not documentation.</p>
<h2 id="footnotes">Footnotes</h2>
<p>[^1] Below the big download button, there's a link to the
installation guide, but this provides nothing helpful, it just
guides you through the already extremely simple
installation.</p>
<h2 id="sources">Sources</h2>
<p>“Install Additional Drivers and Libraries in Vanilla OS.”
<em>Vanilla OS Docs</em>, Vanilla OS, <a
href="https://docs.vanillaos.org/handbook/en/install-additional-drivers">docs.vanillaos.org/handbook/en/install-additional-drivers</a>.
Accessed 19 Sept. 2024.<br />
“Vanilla OS Docs.” <em>Vanilla OS</em>, Vanilla OS, <a
href="https://docs.vanillaos.org/collections/docs">docs.vanillaos.org/collections/docs</a>.
Accessed 19 Sept. 2024.<br />
<em>Vanilla OS</em>, <a
href="https://vanillaos.org">vanillaos.org</a>. Accessed 19
Sept. 2024.<br />
Vanilla-OS. “GitHub: Vanilla-Os/Abroot.” <em>GitHub</em>, <a
href="github.com/Vanilla-OS/ABRoot">github.com/Vanilla-OS/ABRoot</a>.
Accessed 19 Sept. 2024.</p>
<iframe src="https://john.citrons.xyz/embed?ref=askiiart.net" style="margin-left:auto;display:block;margin-right:auto;max-width:732px;width:100%;height:94px;border:none;"></iframe>
<script src="/prism.js"></script>
</body>
<footer>
<p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a>&ensp;|&ensp;<a href="/glossary.html">Glossary</a></p>
<small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small>
</footer>
</html>

60
blog/vanilla-os.md Normal file
View file

@ -0,0 +1,60 @@
# OCI Images as a "Filesystem": Vanilla OS
In looking for a layered solution to blendOS's issues, I found that the lead maintainer and creator of blendOS was looking into using OCI images, and has even forked a repo from Vanilla OS. So I'm trying out Vanilla OS's usage of OCI images (which are inherently layered) to see about implementing a similar system in blendOS.
## Installation
Installation is pretty simple, you're again dropped into a simple GNOME session with a GTK installer:
![A basic GNOME session with a white GTK-based installer; it's showing the date and time/time zone selector.](/assets/vanilla-os/1.png)
The process was very similar to blendOS's, though it also detects virtual machines and offers an option to install tools (e.g. clipboard sharing, video drivers) to help with that.
Another notable bit is that it requires more space than blendOS, with a minimum disk size of 50 GB, but given its A/B slot architecture (which I'll get to later), this makes sense.
## First boot
On first boot, there's a very similar setup tool, surely based off the installer. It makes you put in your language, timezone, etc. again, which I was a bit annoyed by, but it's no big deal. Then it has you create your login, select what you want installed (from basic programs like a calendar, office suite, etc.), then restarts and does all that.
![A similar wizard to the installer; it has the Vanilla OS logo and says "Welcome", "Make your choices, this wizard will take care of everything"](/assets/vanilla-os/2.png)
Then you just get a little slideshow detailing automatic updates, its Apx package manager, and other basics, nothing interesting, and nothing I care about.
## Usage and configuration
I tried checking the docs (*Vanilla OS Docs*), which by themselves were difficult to find. They're a bit hidden in "Help" despite being *absolutely essential* to using this distro[^1]. But what I found easily was screenshots of Overwatch. (*Vanilla OS*)
Regardless, once I found the docs, I tried to figure out how it worked, and I was still very confused. After looking over it again, I decided to check Apx's docs, its package manager, and found how to install packages, of course. (*Vanilla OS Docs*) I tried to install GParted; after it not running at first due to Vanilla OS not being configured correctly and not showing a password prompt for it, causing GParted to exit, I ran it in the terminal with `sudo`, just to get a permission denied error. That's because all packages are installed in containers, there is no system package manager... kinda.
### ABRoot
ABRoot is the magic behind Vanilla OS's OCI image backend. As far as I can tell (again, I don't believe there are no relevant for docs for this) it essentially generates a tarball of the relevant data for the new iteration, then symlinks to either that or the current iteration on boot, depending on what the user selects. It provides essentially no advantages over blendOS's approach, and is, in my opinion, massively overcomplicated. (*GitHub: Vanilla-os/abroot*)
It also acts as a package manager of sorts - it's the only way to install packages system-wide on Vanilla OS, and it does this by running `apt` when the new image is built, similar to Akshara.
ABRoot's config file is at `/etc/abroot/abroot.json`, but it doesn't support declarative system-wide packages. Instead, run the following:
```bash
abroot pkg add $PACKAGE_NAME
```
(*Install additional drivers and libraries in Vanilla OS*)
## Conclusion
Vanilla OS wasn't very helpful as to OCI-based layers, but I don't think it was a complete waste of time. Vanilla OS gave me some ideas, and I like its backend's ideas; it will most likely serve as inspiration for when I add layers to blendOS. Plus, my idea would have an advantage: compression.
But I'll get into it later, once it's a bit more fleshed out; plus, that's not the point of this post anyways.
P.S. I can't get it across while keeping this post decent quality and on-topic, but I need to emphasize how confusing the docs were for Vanilla OS. It feels like they try to appeal to users with basic tech literacy while not explaining how it actually works or what anything does. They write how-to guides, not documentation.
## Footnotes
[^1] Below the big download button, there's a link to the installation guide, but this provides nothing helpful, it just guides you through the already extremely simple installation.
## Sources
“Install Additional Drivers and Libraries in Vanilla OS.” *Vanilla OS Docs*, Vanilla OS, [docs.vanillaos.org/handbook/en/install-additional-drivers](https://docs.vanillaos.org/handbook/en/install-additional-drivers). Accessed 19 Sept. 2024.\
“Vanilla OS Docs.” *Vanilla OS*, Vanilla OS, [docs.vanillaos.org/collections/docs](https://docs.vanillaos.org/collections/docs). Accessed 19 Sept. 2024.\
*Vanilla OS*, [vanillaos.org](https://vanillaos.org). Accessed 19 Sept. 2024.\
Vanilla-OS. “GitHub: Vanilla-Os/Abroot.” *GitHub*, [github.com/Vanilla-OS/ABRoot](github.com/Vanilla-OS/ABRoot). Accessed 19 Sept. 2024.

10
feed.xml
View file

@ -5,7 +5,15 @@
<title>eng.askiiart.net</title> <title>eng.askiiart.net</title>
<description>This is the feed for engl.askiiart.net, I guess</description> <description>This is the feed for engl.askiiart.net, I guess</description>
<link>https://askiiart.net</link> <link>https://askiiart.net</link>
<lastBuildDate>Mon, 02 Sep 2024 04:10:52 +0000</lastBuildDate> <lastBuildDate>Thu, 19 Sep 2024 15:42:25 +0000</lastBuildDate>
<item>
<title>Glossary</title>
<link>https://engl.askiiart.net/glossary.html</link>
</item>
<item>
<title>OCI Images as a "Filesystem": Vanilla OS</title>
<link>https://engl.askiiart.net/blog/vanilla-os.html</link>
</item>
<item> <item>
<title>Checking out blendOS</title> <title>Checking out blendOS</title>
<link>https://engl.askiiart.net/blog/blendos.html</link> <link>https://engl.askiiart.net/blog/blendos.html</link>

28
generate-sitemap.sh
View file

@ -1,30 +1,20 @@
#!/usr/bin/env bash #!/usr/bin/env bash
### Stolen from TCCD-CompSci-and-Coding-Club/website on Codeberg (also written by me) # Based on this: https://www.lostsaloon.com/technology/how-to-create-an-xml-sitemap-using-wget-and-shell-script/
# Taken from here and modified: https://www.lostsaloon.com/technology/how-to-create-an-xml-sitemap-using-wget-and-shell-script/
# (https://web.archive.org/web/20231202193251/https://www.lostsaloon.com/technology/how-to-create-an-xml-sitemap-using-wget-and-shell-script/) (https://archive.ph/qtdMP) # (https://web.archive.org/web/20231202193251/https://www.lostsaloon.com/technology/how-to-create-an-xml-sitemap-using-wget-and-shell-script/) (https://archive.ph/qtdMP)
sitedomain=https://engl.askiiart.net/ sitedomain=https://engl.askiiart.net
dir=$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" &>/dev/null && pwd) dir=$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" &>/dev/null && pwd)
wget --spider --recursive --level=inf --output-file=$dir/linklist.txt $sitedomain
# greps for the relevant lines, gets the URLs, gets only the lines for $sitedomain, and sorts them
# wget's output changed, so this line had to be updated
# also, not sure why it ends up working, since there's a leading space in the lines after `awk` runs, but it works soooo i'mnot gonna mess with it
grep "Adding URL:" $dir/linklist.txt | awk -F 'Adding URL:' '{print $2}' | grep "$sitedomain" | sort -u >$dir/sortedurls.txt
header='<?xml version="1.0" encoding="UTF-8"?><urlset header='<?xml version="1.0" encoding="UTF-8"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9
http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">' http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">'
echo $header >sitemap.xml echo $header >sitemap.xml
while read p; do
case "$p" in find . -name "*.md" | while read -r item; do
*/ | *.html | *.htm) item="${item:2}"
echo '<url><loc>'$p'</loc></url>' >>sitemap.xml item="${item%.*}"
;; echo '<url><loc>'${sitedomain}/${item}.html'</loc></url>' >>sitemap.xml
*) ;; done
esac
done <$dir/sortedurls.txt
echo "</urlset>" >> sitemap.xml echo "</urlset>" >> sitemap.xml
rm $dir/linklist.txt
rm $dir/sortedurls.txt

92
glossary.html Normal file
View file

@ -0,0 +1,92 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta content="width=device-width, initial-scale=1" charset="utf-8" />
<link rel="icon" href="/assets/askiiart.gif" type="image/icon">
<title>Glossary</title>
<link href="/style.css" type="text/css" rel="stylesheet" />
<link href="/prism.css" type="text/css" rel="stylesheet" />
</head>
<body class="line-numbers">
<h1 id="glossary">Glossary</h1>
<ul>
<li>Linux: An open-source family of operating systems
<ul>
<li>Linux distro (distribution): One of the operating systems in
the Linux family (i.e. using the Linux kernel)</li>
</ul></li>
<li>OCI: Open Container Initiative; a project for open-source
standardization of containers</li>
<li>Containers: An isolated environment to run programs, great
for avoiding conflicting dependencies and for ease-of-use</li>
<li>Container image: The base filesystem of a container
<ul>
<li>OCI image: The OCI's standard for container images, used by
essentially all Linux container platforms</li>
</ul></li>
<li>AUR: Arch User Repository, a repository for Arch Linux
packages which are maintained by users. AUR only hosts
computer-readable instructions and related files (via
<code>PKGBUILD</code> files) for creating the packages, not the
packages or programs themselves</li>
<li>Filesystem: The system which keeps track of how data is
written to disk, like NTFS, FAT32, or ext4. Some filesystems,
like ZFS or btrfs, have extra features like redundancy or
compression.<img src="image.png" title="alt text" alt="alt text" /></li>
<li>Git: The most common version control system by far - keeps
track of different versions of files, can be used to resolve
conflicting changes, etc.
<ul>
<li>Forking: Copying a Git repository and adding your own stuff
to it. Can be simply to contribute the changes back to the
upstream project later, or to use something as a base for your
own project.</li>
</ul></li>
<li>Repository: Usually refers to either a Git repository (i.e.
a Git project), or a server hosting packages to be installed by
a package manager.</li>
<li>GUI toolkit: A set of programs used for making graphical
interfaces
<ul>
<li>Qt: A GUI toolkit with an appearance similar to normal
Windows interfaces; pronounced "cute"</li>
<li>GTK: A more (literally) rounded GUI toolkit, hated by some
for its programs usually having highly excessive whitespace and
poor design (though there are some exceptions)</li>
</ul></li>
<li>Window manager: The program which keeps track of and
determines where each program's window(s) go.</li>
<li>Desktop Environment: A window manager, programs, and
configurations, all wrapped up into a bundle, providing a
comprehensive desktop.
<ul>
<li>GNOME: A popular GTK-based extensible desktop
environment.</li>
</ul></li>
<li>Virtual machine: A virtual computer.</li>
<li>Partition: A part of a disk. For example, modern computers
have a small boot partition and a big partition holding all the
actual data.</li>
<li>GParted: GNOME's partition manager - and my favorite
partition manager.</li>
<li><code>sudo</code>: Super user do; runs a command as
<code>root</code>, Linux's admin account.</li>
<li>Tarball: An archive of data, preserving its file and
directory structure. Not compressed, though its tools come with
options to compress it after generation.</li>
<li><code>apt</code>: The package manager for Debian-based Linux
distros.</li>
<li>blendOS: "Arch Linux, made declarative, immutable and
atomic."
<ul>
<li>Akshara: blendOS's system rebuilder</li>
</ul></li>
</ul>
<iframe src="https://john.citrons.xyz/embed?ref=askiiart.net" style="margin-left:auto;display:block;margin-right:auto;max-width:732px;width:100%;height:94px;border:none;"></iframe>
<script src="/prism.js"></script>
</body>
<footer>
<p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a>&ensp;|&ensp;<a href="/glossary.html">Glossary</a></p>
<small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small>
</footer>
</html>

27
glossary.md Normal file
View file

@ -0,0 +1,27 @@
# Glossary
- Linux: An open-source family of operating systems
- Linux distro (distribution): One of the operating systems in the Linux family (i.e. using the Linux kernel)
- OCI: Open Container Initiative; a project for open-source standardization of containers
- Containers: An isolated environment to run programs, great for avoiding conflicting dependencies and for ease-of-use
- Container image: The base filesystem of a container
- OCI image: The OCI's standard for container images, used by essentially all Linux container platforms
- AUR: Arch User Repository, a repository for Arch Linux packages which are maintained by users. AUR only hosts computer-readable instructions and related files (via `PKGBUILD` files) for creating the packages, not the packages or programs themselves
- Filesystem: The system which keeps track of how data is written to disk, like NTFS, FAT32, or ext4. Some filesystems, like ZFS or btrfs, have extra features like redundancy or compression.![alt text](image.png)
- Git: The most common version control system by far - keeps track of different versions of files, can be used to resolve conflicting changes, etc.
- Forking: Copying a Git repository and adding your own stuff to it. Can be simply to contribute the changes back to the upstream project later, or to use something as a base for your own project.
- Repository: Usually refers to either a Git repository (i.e. a Git project), or a server hosting packages to be installed by a package manager.
- GUI toolkit: A set of programs used for making graphical interfaces
- Qt: A GUI toolkit with an appearance similar to normal Windows interfaces; pronounced "cute"
- GTK: A more (literally) rounded GUI toolkit, hated by some for its programs usually having highly excessive whitespace and poor design (though there are some exceptions)
- Window manager: The program which keeps track of and determines where each program's window(s) go.
- Desktop Environment: A window manager, programs, and configurations, all wrapped up into a bundle, providing a comprehensive desktop.
- GNOME: A popular GTK-based extensible desktop environment.
- Virtual machine: A virtual computer.
- Partition: A part of a disk. For example, modern computers have a small boot partition and a big partition holding all the actual data.
- GParted: GNOME's partition manager - and my favorite partition manager.
- `sudo`: Super user do; runs a command as `root`, Linux's admin account.
- Tarball: An archive of data, preserving its file and directory structure. Not compressed, though its tools come with options to compress it after generation.
- `apt`: The package manager for Debian-based Linux distros.
- blendOS: "Arch Linux, made declarative, immutable and atomic."
- Akshara: blendOS's system rebuilder

2
index.html
View file

@ -19,7 +19,7 @@
<script src="/prism.js"></script> <script src="/prism.js"></script>
</body> </body>
<footer> <footer>
<p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a></p> <p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a>&ensp;|&ensp;<a href="/glossary.html">Glossary</a></p>
<small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small> <small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small>
</footer> </footer>
</html> </html>

3
sitemap.xml
View file

@ -1,3 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"> <?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
<url><loc>https://engl.askiiart.net/index.html</loc></url>
<url><loc>https://engl.askiiart.net/glossary.html</loc></url>
<url><loc>https://engl.askiiart.net/blog/vanilla-os.html</loc></url>
<url><loc>https://engl.askiiart.net/blog/blendos.html</loc></url> <url><loc>https://engl.askiiart.net/blog/blendos.html</loc></url>
</urlset> </urlset>

3
template.html
View file

@ -2,7 +2,6 @@
<html lang="en"> <html lang="en">
<head> <head>
<meta content="width=device-width, initial-scale=1" charset="utf-8" /> <meta content="width=device-width, initial-scale=1" charset="utf-8" />
<link rel="icon" href="/assets/askiiart.gif" type="image/icon">
<title>$title$</title> <title>$title$</title>
<link href="/style.css" type="text/css" rel="stylesheet" /> <link href="/style.css" type="text/css" rel="stylesheet" />
<link href="/prism.css" type="text/css" rel="stylesheet" /> <link href="/prism.css" type="text/css" rel="stylesheet" />
@ -13,7 +12,7 @@
<script src="/prism.js"></script> <script src="/prism.js"></script>
</body> </body>
<footer> <footer>
<p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a></p> <p><a href="https://git.askiiart.net/askiiart/engl-2311-blog">Source code</a>&ensp;|&ensp;<a href="/feed.xml">RSS</a>&ensp;|&ensp;<a href="/glossary.html">Glossary</a></p>
<small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small> <small>Image captions are the same as the alt text; assuming you're sighted, you can most likely ignore them.</small>
</footer> </footer>
</html> </html>