mjo
/
inferno
mirror of https://github.com/mjohanning99/inferno.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add more text, change formatting

master
Marvin Johanning 2020-04-26 12:37:14 +02:00
parent 059a0b67ca
commit 334919e0d6
6 changed files with 29 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
inferno.fdb_latexmk
View File

@ -1,10 +1,10 @@
# Fdb version 3
["makeindex inferno.idx"] 1587809296 "inferno.idx" "inferno.ind" "inferno" 1587840243
"inferno.idx" 1587840173 0 d41d8cd98f00b204e9800998ecf8427e "pdflatex"
["makeindex inferno.idx"] 1587809296 "inferno.idx" "inferno.ind" "inferno" 1587897354
"inferno.idx" 1587897353 0 d41d8cd98f00b204e9800998ecf8427e "pdflatex"
(generated)
"inferno.ind"
"inferno.ilg"
["pdflatex"] 1587840172 "inferno.tex" "inferno.pdf" "inferno" 1587840243
["pdflatex"] 1587897353 "inferno.tex" "inferno.pdf" "inferno" 1587897354
"/usr/share/texmf-dist/fonts/enc/dvips/lm/lm-mathsy.enc" 1572595918 2840 216e6e45ad352e2456e1149f28885bee ""
"/usr/share/texmf-dist/fonts/enc/dvips/lm/lm-rm.enc" 1572595918 2327 9d6df24f9c4f7368395224341a95523a ""
"/usr/share/texmf-dist/fonts/enc/dvips/lm/lm-rmtt.enc" 1572595918 2359 de53213020575850c8f8debc35095765 ""
@ -94,15 +94,15 @@
"/usr/share/texmf-dist/tex/latex/ucs/utf8x.def" 1572592815 8036 21f7ac37aafb6cfeddbb196b8bfd6280 ""
"/usr/share/texmf-dist/tex/latex/wrapfig/wrapfig.sty" 1572592815 26220 3701aebf80ccdef248c0c20dd062fea9 ""
"/usr/share/texmf-dist/web2c/texmf.cnf" 1572595918 33301 a3134070eacafb10b1f371612ce2650d ""
"/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map" 1587147714 4567315 5bff4ef6a80dad29ef009f9621a3294a ""
"/var/lib/texmf/web2c/pdftex/pdflatex.fmt" 1587147691 8044939 89f2e011f7a0c932a29ba4073502f201 ""
"inferno.aux" 1587840173 655 56fd88b45fb792889a315782b4e710b5 "pdflatex"
"inferno.ind" 1587826626 0 d41d8cd98f00b204e9800998ecf8427e "makeindex inferno.idx"
"inferno.tex" 1587840172 21978 663cb4da2f52d612d2ee363527899139 ""
"inferno.toc" 1587840173 351 5ff13bbfe522b846a5c87461d60d0028 "pdflatex"
"/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map" 1587147931 334286 7d54d57af850f32d2e4cd0d3222731c3 ""
"/var/lib/texmf/web2c/pdftex/pdflatex.fmt" 1587147917 8044939 0faf3f72f02e850181fdc04d9dd7f8b0 ""
"inferno.aux" 1587897353 655 56fd88b45fb792889a315782b4e710b5 "pdflatex"
"inferno.ind" 1587809296 0 d41d8cd98f00b204e9800998ecf8427e "makeindex inferno.idx"
"inferno.tex" 1587897351 23428 611cbe7a6a507a56bc57cf0123733226 ""
"inferno.toc" 1587897353 351 5ff13bbfe522b846a5c87461d60d0028 "pdflatex"
(generated)
"inferno.toc"
"inferno.aux"
"inferno.idx"
"inferno.log"
"inferno.pdf"
"inferno.aux"
"inferno.toc"

2
inferno.fls
View File

@ -1,4 +1,4 @@
PWD /home/sophon/Documents/inferno
PWD /home/sophon/Documents/ComputerStuff/Articles/Mine/InfernoOS
INPUT /usr/share/texmf-dist/web2c/texmf.cnf
INPUT /var/lib/texmf/web2c/pdftex/pdflatex.fmt
INPUT inferno.tex

10
inferno.log
View File

@ -1,4 +1,4 @@
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) (preloaded format=pdflatex 2020.4.17) 25 APR 2020 20:42
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch Linux) (preloaded format=pdflatex 2020.4.17) 26 APR 2020 12:35
entering extended mode
restricted \write18 enabled.
file:line:error style messages enabled.
@ -386,15 +386,15 @@ Package microtype Info: Loading generic protrusion settings for font family
] [14] (./inferno.aux) )
Here is how much of TeX's memory you used:
6126 strings out of 492167
89066 string characters out of 6131558
6128 strings out of 492167
89088 string characters out of 6131558
206179 words of memory out of 5000000
10267 multiletter control sequences out of 15000+600000
68691 words of font info for 96 fonts, out of 8000000 for 9000
68778 words of font info for 97 fonts, out of 8000000 for 9000
1141 hyphenation exceptions out of 8191
46i,6n,45p,833b,480s stack positions out of 5000i,500n,10000p,200000b,80000s
{/usr/share/texmf-dist/fonts/enc/dvips/lm/lm-rmtt.enc}{/usr/share/texmf-dist/fonts/enc/dvips/lm/lm-rm.enc}{/usr/share/texmf-dist/fonts/enc/dvips/lm/lm-mathsy.enc}</usr/share/texmf-dist/fonts/type1/public/lm/lmbx12.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmr10.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmr12.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmr17.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmri10.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmri12.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmsy10.pfb></usr/share/texmf-dist/fonts/type1/public/lm/lmtt12.pfb>
Output written on inferno.pdf (20 pages, 201876 bytes).
Output written on inferno.pdf (20 pages, 203267 bytes).
PDF statistics:
104 PDF objects out of 1000 (max. 8388607)
73 compressed objects within 1 object stream

BIN
inferno.pdf
View File

Binary file not shown.

BIN
inferno.synctex.gz
View File

Binary file not shown.

17
inferno.tex
View File

@ -159,9 +159,9 @@ But fret not! While abandoned by Bell Labs long ago — what vile traitors they
It is, however, to be noted that my instructions henceforth will work only on Linux x86; should you wish to be presented with instructions regarding other systems — systems whose name should not be spoken, for they are vicious and vile, forged somewhere far below hell itself; in a place Be\"{e}lzebub himself does not dare to enter — you may cease your reading here, for you may not find the information you desire. The following chapter is akin to a recipe from a cook book; hence follow the instructions with care, or your ``meal'' may turn out wretched, ugly and inedible.
One must first define the \textit{root} of the installation; this may sound somewhat strange, yet in actuality one is simply required to aid Inferno in knowing where on your system it is located — it cannot know on its own and assumes it is located in \texttt{/usr/local/inferno}. Hence, should you not wish Inferno to be installed there, you must alter the \texttt{mkconfig} file; therein you can modify the \texttt{ROOT} variable to point to your Inferno directory.
Yet withal, I would recommend simply using the directory Infenro wishes to be inside of by creating it using \texttt{sudo mkdir /usr/local/inferno} and thereafter copying the contents from the old directory to the new one by typing \texttt{sudo cp -r * /usr/local/inferno}; I have found this to be much more simple. You must then move into this directory by typing \texttt{cd /usr/local/inferno}.
Yet withal, I would recommend simply using the directory Inferno wishes to be inside of by creating it using \texttt{sudo mkdir /usr/local/inferno} and thereafter copying the contents from the old directory to the new one by typing \texttt{sudo cp -r * /usr/local/inferno}; I have found this to be much more simple. You must then move into this directory by typing \texttt{cd /usr/local/inferno}.
But be aware! Apart from the \texttt{ROOT} variable, there exist two others, namely \texttt{SYSHOST} and \texttt{OBJTYPE}; it is imperative to modify these so that they match your system, for otherwise your installation will fail — inded, this is akin to letting a scoundrel wreak havoc on your system. Thus — this is, unless you are using one of the aforementioned systems whose names should never be mentioned, for they cause terror and fear far greater than that caused by the devil himself —, pay heed to the values of these two variables, for they ought to be set to \texttt{Linux} and \texttt{386} respectively. The latter should be modified to equal \texttt{arm} should your Linux installation be ARM-based, such as those running on the Raspberry Pi.
But be aware! Apart from the \texttt{ROOT} variable, there exist two others, namely \texttt{SYSHOST} and \texttt{OBJTYPE}; it is imperative to modify these so that they match your system, for otherwise your installation will fail — indeed, this is akin to letting a scoundrel wreak havoc on your system. Thus — this is, unless you are using one of the aforementioned systems whose names should never be mentioned, for they cause terror and fear far greater than that caused by the devil himself —, pay heed to the values of these two variables, for they ought to be set to \texttt{Linux} and \texttt{386} respectively. The latter should be modified to equal \texttt{arm} should your Linux installation be ARM-based, such as those running on the Raspberry Pi.
Having completed this task, you will thence be able to execute \texttt{makemk.sh}, a shell script that will spawn the \texttt{mk} executable which shall thenceforth be used for building Inferno itself; a infernal tool for certain, yet one that shall prove invaluable.
@ -173,7 +173,7 @@ But fret not! While abandoned by Bell Labs long ago — what vile traitors they
But alas, our machine is dim-witted, for running \texttt{mk} does not yield anything; nay, it appears the command does not exist — which is undoubtebly wrong, for its existance can be ascertained by looking at the aforementioned directory. So what is one to do? The machine needs to be told where to find it — and the binaries that shall be brought into existance soon —, which means that we will need to modify the \texttt{PATH} variable.
The contents of this variable tell our machine where binaries are located and one must thus affix the path to our previously created binary onto the \texttt{PATH} variable, a task swiftly accomplished; but first it is imperative to know what Shell is currently being used. This is achived by typing \texttt{echo \$SHELL} into one's terminal, which, in my case, yields \texttt{/usr/bin/zsh}, for I use Zsh; on your system, a likely candidate will be \texttt{/usr/bin/bash}, since the Bourne Shell, as it is called, is one of the most prominent ones in use today.
The contents of this variable tell our machine where binaries are located and one must thus affix the path to our previously created binary onto the \texttt{PATH} variable, a task swiftly accomplished; but first it is imperative to know what Shell is currently being used. This is achieved by typing \texttt{echo \$SHELL} into one's terminal, which, in my case, yields \texttt{/usr/bin/zsh}, for I use Zsh; on your system, a likely candidate will be \texttt{/usr/bin/bash}, since the Bourne Shell, as it is called, is one of the most prominent ones in use today.
Nevertheless, one needs to add the following line to one's \texttt{~/.bashrc} or \texttt{~/.zshrc} whose purpose it is to inform the machine of our newly built binary's location, so that by typing its name it will be executed: \texttt{export PATH="/usr/local/bin/inferno/Linux/386/bin:\$PATH"}.
@ -185,7 +185,7 @@ But fret not! While abandoned by Bell Labs long ago — what vile traitors they
Yet you may wonder — why, even be bothered —, for what has all this effort lead to? How has this file aided us in our journey towards Inferno? Fret not, for this file is but the beginning — why, it is akin to the apple that those whom God created first, Adam and Eve, had fallen for; the apple that initiated their fall from Eden; and just as they were cast from Eden, we, too, shall be cast from our current operating system and into Inferno. We, too, have sinned — albeit knowingly — to continue our descent into Inferno; \texttt{mk} is our apple, our forbidden fruit, wherewith we shall enter hell.
Having gained access to such a powerful tool, we must go back to our Inferno installation in \texttt{/usr/local/inferno} and, upon having arrived, we must commence with the creation of the system itself.
Having gained access to such a powerful tool, we must return to our Inferno installation in \texttt{/usr/local/inferno} and, upon having arrived, we must commence with the creation of the system itself.
The first command that must be run is \texttt{sudo mk nuke} — just a reminder of what is to come; for if we must nuke something, this surely cannot be a system of good. Running this command will erase files which are not necessary for us; thereupon we may begin the actual installation.
@ -218,7 +218,14 @@ But fret not! While abandoned by Bell Labs long ago — what vile traitors they
Undoubtebly proud of their previous achievements, they decided to implement — a wise decision, might I add — a large number of the commands that are to be found in Unix-based systems in Inferno. Yet you should not let yourself get fooled, for this is not Unix — 'tis merely hell hiding in plain sight; and whilst it is indeed possible to use Inferno from its shell only, it does provide a window mananger; for, as I hope you remember, they longed to create an operating system that was built with a window manager in mind and not have it be, as was the case with Unix, an afterthought, carelessly plastered onto it years later.
Its window manager — simply and rather uncreatively titled \texttt{wm} — can be evoked by typing \texttt{wm/wm}.
Its window manager — simply and rather uncreatively titled \texttt{wm} — can be evoked by typing \texttt{wm/wm}, whereupon one will be greeted by a small window; indeed, its appearance is somewhat dull, consisting of a grey background, and a grey task bar — truly an atrocity to behold. Indeed, it is puzzling, for what is to be done? What is to be clicked? Whence can programs be started and wherefrom is a poor fellow supposed to receive help? Having been tossed down into this abysmal realm of dread, one is reminded of what, in his book Paradise Lost, John Milton writes: —
\begin{quote}
Seest thou yon dreary plain, forlorn and wild, \\
The seat of desolation, void of light, \\
Save what the glimmering of these livid flames \\
Casts pale and dreadful?
\end{quote}
For indeed it seems what have stridden upon a system wholly encompassed by the colour of despair with no task to accomplish but to gaze upon its grey insipidness. You should not fret, though, for this is but a disguise; hiding beneath its ghastly appearance lie programs who are waiting eagerly to be used. To aid you in your journey, you shall henceforth be provided with photographs of the system as I see it, since I believe this will simplify your journey considerably; indeed, those poor souls whom the ability to use Inferno has not been bestowed for they lack a proper system install it onto, are what these photographs will aid most substantially, as they may therefore see the happenings of our doings without needing their own installation.
\end{document}