Browse Source

Editing 2021.09.02.21:06

tags/Issue-001
Kenneth John Odle 1 year ago
parent
commit
4c04d405b2
  1. 2
      001/build/codex-001.aux
  2. 32
      001/build/codex-001.log
  3. BIN
      001/build/codex-001.pdf
  4. BIN
      001/build/codex-001.synctex.gz
  5. 2
      001/build/codex-001.toc
  6. 25
      001/codex-001.tex

2
001/build/codex-001.aux

@ -29,7 +29,7 @@
\@writefile{toc}{\contentsline {section}{\numberline {2.2}Knowledge is Power}{9}{section.2.2}\protected@file@percent }
\@writefile{toc}{\contentsline {section}{\numberline {2.3}The Unix Philosophy}{10}{section.2.3}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3.1}Where does the Unix Principle actually apply in real life?}{11}{subsection.2.3.1}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3.2}Where else does the Unix Principle \textit {not} apply that it probably should in real life?}{13}{subsection.2.3.2}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3.2}Where else does the Unix Principle \textit {not} apply that it probably should in real life?}{14}{subsection.2.3.2}\protected@file@percent }
\@writefile{toc}{\contentsline {subsection}{\numberline {2.3.3}Where does the Unix Principle not apply in real life and this is actually a good thing?}{14}{subsection.2.3.3}\protected@file@percent }
\@writefile{toc}{\contentsline {chapter}{\numberline {3}What Are All Those Files in the Linux Root?}{15}{chapter.3}\protected@file@percent }
\@writefile{lof}{\addvspace {10\p@ }}

32
001/build/codex-001.log

@ -1,4 +1,4 @@
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2021.7.3) 2 SEP 2021 19:40
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2021.7.3) 2 SEP 2021 21:04
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
@ -877,35 +877,35 @@ Chapter 3.
Chapter 4.
Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
(hyperref) removing `\leavevmode@ifvmode' on input line 263.
(hyperref) removing `\leavevmode@ifvmode' on input line 266.
Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
(hyperref) \kern 1.66702pt
(hyperref) removed on input line 263.
(hyperref) removed on input line 266.
[16
]
Overfull \hbox (8.25641pt too wide) in paragraph at lines 277--278
Overfull \hbox (8.25641pt too wide) in paragraph at lines 280--281
\OT1/jkp/m/n/10 vent that, add [][]\OT1/jkptt/m/n/10 \counterwithout{foootnote}
{chapter} []\OT1/jkp/m/n/10 to the pream-
[]
Package atveryend Info: Empty hook `BeforeClearDocument' on input line 288.
Package atveryend Info: Empty hook `BeforeClearDocument' on input line 291.
[17]
Package atveryend Info: Empty hook `AfterLastShipout' on input line 288.
Package atveryend Info: Empty hook `AfterLastShipout' on input line 291.
(build/codex-001.aux)
Package atveryend Info: Executing hook `AtVeryEndDocument' on input line 288.
Package atveryend Info: Executing hook `AtEndAfterFileList' on input line 288.
Package atveryend Info: Executing hook `AtVeryEndDocument' on input line 291.
Package atveryend Info: Executing hook `AtEndAfterFileList' on input line 291.
Package rerunfilecheck Info: File `codex-001.out' has not changed.
(rerunfilecheck) Checksum: <no file>.
Package atveryend Info: Empty hook `AtVeryVeryEnd' on input line 288.
Package atveryend Info: Empty hook `AtVeryVeryEnd' on input line 291.
)
Here is how much of TeX's memory you used:
8456 strings out of 483140
119868 string characters out of 5965152
375470 words of memory out of 5000000
8458 strings out of 483140
119892 string characters out of 5965152
375476 words of memory out of 5000000
23217 multiletter control sequences out of 15000+600000
590533 words of font info for 154 fonts, out of 8000000 for 9000
36 hyphenation exceptions out of 8191
@ -918,10 +918,10 @@ e1/public/kpfonts/jkpmit8a.pfb></usr/share/texlive/texmf-dist/fonts/type1/publi
c/kpfonts/jkpmn8a.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts
/jkpmne.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/jkpttmn8a
.pfb>
Output written on build/codex-001.pdf (17 pages, 121355 bytes).
Output written on build/codex-001.pdf (17 pages, 122271 bytes).
PDF statistics:
250 PDF objects out of 1000 (max. 8388607)
219 compressed objects within 3 object streams
59 named destinations out of 1000 (max. 500000)
255 PDF objects out of 1000 (max. 8388607)
224 compressed objects within 3 object streams
61 named destinations out of 1000 (max. 500000)
139 words of extra memory for PDF output out of 10000 (max. 10000000)

BIN
001/build/codex-001.pdf

BIN
001/build/codex-001.synctex.gz

2
001/build/codex-001.toc

@ -7,7 +7,7 @@
\contentsline {section}{\numberline {2.2}Knowledge is Power}{9}{section.2.2}%
\contentsline {section}{\numberline {2.3}The Unix Philosophy}{10}{section.2.3}%
\contentsline {subsection}{\numberline {2.3.1}Where does the Unix Principle actually apply in real life?}{11}{subsection.2.3.1}%
\contentsline {subsection}{\numberline {2.3.2}Where else does the Unix Principle \textit {not} apply that it probably should in real life?}{13}{subsection.2.3.2}%
\contentsline {subsection}{\numberline {2.3.2}Where else does the Unix Principle \textit {not} apply that it probably should in real life?}{14}{subsection.2.3.2}%
\contentsline {subsection}{\numberline {2.3.3}Where does the Unix Principle not apply in real life and this is actually a good thing?}{14}{subsection.2.3.3}%
\contentsline {chapter}{\numberline {3}What Are All Those Files in the Linux Root?}{15}{chapter.3}%
\contentsline {chapter}{\numberline {4}Miscellany}{16}{chapter.4}%

25
001/codex-001.tex

@ -31,7 +31,7 @@
\usepackage{fancyhdr}
\pagestyle{fancy}
\fancyhf{}
\fancyhead[LE,RO]{the codex}
\fancyhead[LE,RO]{\textit{the codex}}
\fancyhead[RE,LO]{Issue \#001}
\cfoot{Page \thepage}
\renewcommand{\footrulewidth}{0.5pt}
@ -214,45 +214,48 @@ I don't know how much my parents spent on this thing, but if it's anything north
Most people have too many knives, myself included. (Again, this is due to marketing and FOMO—fear of missing out.) But really, you only have three or four basic tasks that you use a knife for:
\begin{itemize}
\itemsep0em
\itemsep-0.30em
\item Slicing bread
\item Cutting meats
\item Peeling fruits and vegetables
\item Cutting fruits and vegetables
\item Cutting cheese
\item Cutting cheese\footnote{Yes, I know I said "three or four" and then immediately listed five. Bear with me.}
\end{itemize}
Sure, there are always those oddball tasks that you have to do once a year or less, like using a butcher's cleaver to torque open a pumpkin, but lets talk about those tasks you do on a weekly basis. So let's talk about the knives I have that will accomplish those tasks:
\begin{itemize}
\itemsep-0.30em
\item \textbf{Slicing bread} — The afore-mentioned serrated knife with a long, fairly rigid blade.
\item \textbf{Cutting meats} — If I am cutting meat from the bone, I'll use a boning knife, which has a slightly curved blade that narrows at the tip. Kept sharp, it will also do a great job of cutting up meat for stir-fries, or trimming the fat off the edges of pork chops.
\item \textbf{Peeling fruits and vegetables} — I don't use a knife for this, because a T-handle peeler is much more efficient, easier on the wrist, and safer.
\item \textbf{Cutting fruits and vegetables} — Most fruits and vegetables tend to be firm enough that any sharp knife will do. I have a long chef's knife with an 8" blade which is great when I'm chopping a lot of something. (I do wish I had one with a 10" blade, because that would be even more efficient.) I also have a small santoku knife with a thin blade which I prefer when I need to slice something into thin slices, such as cucumbers.
\item \textbf{Cutting cheese} — I have a knife with a 4" blade with holes in it. The idea is that holes prevent the cheese slices from sticking to the cheese. I had an expensive (\$15!) that did all right; it also had a two-prong fork on the end to pick up the slice of cheese with. It did an okay job. I now have one with a shorter, thicker blade that does an excellent job. I paid \$4 for it at Menard's.
\item \textbf{Cutting fruits and vegetables} — Most fruits and vegetables tend to be firm enough that any sharp knife will do. I have a long chef's knife with an 8" blade which is great when I'm chopping a lot of something. (I do wish I had one with a 10" blade, because that would be even more efficient.) I also have a small santoku knife with a thin blade which I prefer when I need to slice something into thin slices, such as cucumbers. It also does a great job of cutting meat into tiny pieces, especially if you put the meat in the freezer for 20-30 minutes first.
\item \textbf{Cutting cheese} — I have a knife with a 4" blade with holes in it. The idea is that holes prevent the cheese slices from sticking to the cheese. I had an expensive (\$15!) that did all right; it also had a two-prong fork on the end to pick up the slice of cheese with. It did an okay job. I now have one with a shorter, thicker blade that does an excellent job. I paid \$4 for it at Menard's. It simply outperformed the more expensive knife.
\end{itemize}
I know that someone out there is itching to point out that tomatoes aren't potatoes and potatoes aren't carrots, \textit{ad infinitum}, and thus the Unix Principle doesn't apply. Well, there are a lot of different pdfs out there, as well, and if I'm skilled with a command line application (such as \verb|pdftk|) it doesn't really matter which pdf I'm dealing with. The job of a knife is to cut. If you keep the knife sharp (which is a skill in and of itself; if you watch someone that's good at it, you'll realize that it's also an art form) and \textit{learn how to use it properly}, you'll be a lot more efficient in the kitchen. Notice the emphasis on learning how to use a tool properly. You can learn a lot just by reading the manual.
I know that someone out there is itching to point out that tomatoes aren't potatoes and potatoes aren't carrots, \textit{ad infinitum}, and thus the Unix Principle doesn't apply. Well, there are a lot of different pdfs out there, as well, and if I'm skilled with a command line application (such as \verb|pdftk|) it doesn't really matter which pdf I'm dealing with. The job of a knife is to cut. If you keep the knife sharp\footnote{Sharpening a knife is a skill in and of itself. If you watch someone that's good at it, you'll realize that it's also an art form. You can get the skill with practice; you can learn the art with long experience. This is something else that you need to learn.} and \textit{learn how to use it properly}, you'll be a lot more efficient in the kitchen. Notice the emphasis on learning how to use a tool properly. You can learn a lot just by reading the manual.
\medskip
\textbf{Breadmakers} — I'm going on a limb here, because a lot of people will be happy to point out that there are sorts of breadmakers will all sorts of settings. Relax. Breadmakers are designed to do one thing: turn flour, water, yeast, and salt into dough, and then turn that dough into bread. All those settings are just options.
\noindent \textbf{Breadmakers} — I'm going on a limb here, because a lot of people will be happy to point out that there are sorts of breadmakers will all sorts of settings. Relax. Breadmakers are designed to do one thing: turn flour, water, yeast, and salt into dough, and then turn that dough into bread. All those settings are just options.
I've resisted buying a breadmaker for years, because I actually don't want a device in my kitchen that only does one thing, and I've always known how to make bread from scratch. But as I get older, I don't always have the time or patience to make homemade bread (it can be a messy process), and a breadmaker is ideal. It does one thing, and it does it really well. (Hint: bread machine yeast is your friend.)
\medskip
\textbf{Air fryers} — Everything I said for breadmakers also applies to air fryers. They have one job: cook food fast and make it crispy. They work really well on certain items (tater tots!) and not so well on others. I have two analog air fryers, and all you really get to choose is time and temperature. I know that fancy digital ones have \textit{programs}, but really, they are just different time and temperature combinations, which means less thinking for you. But I like to think (and I like to experiment) so I am perfectly happy with my little analog air fryers.
\noindent \textbf{Air fryers} — Everything I said for breadmakers also applies to air fryers. They have one job: cook food fast and make it crispy. They work really well on certain items (tater tots!) and not so well on others. I have two analog air fryers, and all you really get to choose is time and temperature. I know that fancy digital ones have \textit{programs}, but really, they are just different time and temperature combinations, which means less thinking for you. But I like to think (and I like to experiment) so I am perfectly happy with my little analog air fryers.
\subsection{Where else does the Unix Principle \textit{not} apply that it probably should in real life?}
\textbf{Cars (i.e., portable entertainment centers)}
\textbf{Microwave ovens}
\medskip
\noindent \textbf{Microwave ovens}
\subsection{Where does the Unix Principle not apply in real life and this is actually a good thing?}
\textbf{Instant Pots/multicookers}
\textbf{Instant Pots (and to a lesser degree, multicookers)}
\chapter{What Are All Those Files in the Linux Root?}
@ -277,7 +280,7 @@ I'm still a relative newbie to LaTeX, so there's always something to learn. Here
\item Footnotes reset back to the number one with each chapter. To prevent that, add \verb|\counterwithout{foootnote}{chapter}| to the preamble.
\end{enumerate}
Like I said, I'm still a newb and I may be completely wrong or off base on some of these things, in which case, I'll make a note of that in a future issue \footnote{Always assuming that there \textit{will} be another issue.}
\noindent Like I said, I'm still a newb and I may be completely wrong or off base on some of these things, in which case, I'll make a note of that in a future issue \footnote{Always assuming that there \textit{will} be another issue.}
If you are interested, there is a link in the Impressum to the git repo for this publication where you can check out the source code.

Loading…
Cancel
Save