Editing 2021.09.16.19:08

001/build/codex-001.aux

@@ -55,6 +55,7 @@
 \@writefile{toc}{\contentsline {chapter}{\numberline {4}Miscellany}{23}{chapter.4}\protected@file@percent }
 \@writefile{lof}{\addvspace {10\p@ }}
 \@writefile{lot}{\addvspace {10\p@ }}
-\@writefile{toc}{\contentsline {section}{\numberline {4.1}Is This Really a Hack? Or Is It Just a Tip?}{23}{section.4.1}\protected@file@percent }
+\@writefile{toc}{\contentsline {section}{\numberline {4.1}A Scanner Darkly, but with a workflow}{23}{section.4.1}\protected@file@percent }
-\@writefile{toc}{\contentsline {section}{\numberline {4.2}What I Learned About \LaTeX  \tmspace  +\thinmuskip {.1667em} While Creating This Issue}{25}{section.4.2}\protected@file@percent }
+\@writefile{toc}{\contentsline {section}{\numberline {4.2}Is This Really a Hack? Or Is It Just a Tip?}{23}{section.4.2}\protected@file@percent }
-\@writefile{toc}{\contentsline {section}{\numberline {4.3}Coda: Why \LaTeX  ?}{27}{section.4.3}\protected@file@percent }
+\@writefile{toc}{\contentsline {section}{\numberline {4.3}What I Learned About \LaTeX  \tmspace  +\thinmuskip {.1667em} While Creating This Issue}{26}{section.4.3}\protected@file@percent }
+\@writefile{toc}{\contentsline {section}{\numberline {4.4}Coda: Why \LaTeX  ?}{27}{section.4.4}\protected@file@percent }

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.9.5)  10 SEP 2021 18:47
+This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Debian) (preloaded format=pdflatex 2021.9.5)  16 SEP 2021 19:08
 entering extended mode
  restricted \write18 enabled.
  %&-line parsing enabled.
@@ -843,9 +843,9 @@ LaTeX Font Info:    Trying to load font information for OT1+jkptt on input line
 (/usr/share/texlive/texmf-dist/tex/latex/kpfonts/ot1jkptt.fd
 File: ot1jkptt.fd 2007/01/26 Fontinst v1.928 font definitions for OT1/jkptt.
 )
-Overfull \hbox (0.8861pt too wide) in paragraph at lines 77--78
+Overfull \hbox (87.99597pt too wide) in paragraph at lines 77--78
-\OT1/jkp/m/n/10 Me-dia Com-mons. The im-age is []over here[]: [][]\OT1/jkptt/m/
+\OT1/jkp/m/n/10 layah from the Wiki-Me-dia Com-mons. The im-age is []over here[
-n/10 https://commons.wikimedia.o
+]: [][]\OT1/jkptt/m/n/10 https://commons.wikimedia.o
  []
 
 
@@ -865,7 +865,7 @@ Chapter 1.
 [5
 
 ]
-Overfull \hbox (4.79448pt too wide) in paragraph at lines 110--111
+Overfull \hbox (4.79448pt too wide) in paragraph at lines 112--113
 \OT1/jkp/m/n/10 be-cause they had a go-back-through-all-your-steps-to-see-where
 -you-done-
  []
@@ -874,21 +874,21 @@ Overfull \hbox (4.79448pt too wide) in paragraph at lines 110--111
 <images/casio.jpg, id=223, 303.1325pt x 552.0625pt>
 File: images/casio.jpg Graphic file (type jpg)
 <use images/casio.jpg>
-Package pdftex.def Info: images/casio.jpg  used on input line 117.
+Package pdftex.def Info: images/casio.jpg  used on input line 119.
 (pdftex.def)             Requested size: 45.46791pt x 82.8058pt.
  [7 <./images/casio.jpg>]
 
 Package multicol Warning: I moved some lines to the next page.
-(multicol)                Footnotes on page 8 might be wrong on input line 152.
+(multicol)                Footnotes on page 8 might be wrong on input line 154.
 
 
 [8]
-Underfull \hbox (badness 7595) in paragraph at lines 154--155
+Underfull \hbox (badness 7595) in paragraph at lines 156--157
 \OT1/jkp/m/n/10 1921 by Theodore and Mil-ton
  []
 
 
-Overfull \hbox (1.41647pt too wide) in paragraph at lines 165--166
+Overfull \hbox (1.41647pt too wide) in paragraph at lines 167--168
 []\OT1/jkp/m/n/10 Anyway, that Wednes-day af-ter-noon ex-pe-ri-ence was a real 
 game changer
  []
@@ -900,7 +900,7 @@ Chapter 2.
 ] [12] [13] [14] [15] [16] [17]
 Chapter 3.
 
-Overfull \hbox (0.53847pt too wide) in paragraph at lines 293--294
+Overfull \hbox (0.53847pt too wide) in paragraph at lines 297--298
 \OT1/jkp/m/n/10 This di-rec-tory con-tains es-sen-tial com-mand bi-na-ries[][][
 ] that need to be avail-
  []
@@ -910,7 +910,7 @@ Overfull \hbox (0.53847pt too wide) in paragraph at lines 293--294
 ] [19] [20] [21] [22]
 Chapter 4.
 
-Overfull \hbox (1.1366pt too wide) in paragraph at lines 409--410
+Overfull \hbox (1.1366pt too wide) in paragraph at lines 416--417
 []\OT1/jkp/m/n/10 Rather, I'm talk-ing about the older mean-ing of the term ``h
 acker'' which
  []
@@ -920,38 +920,38 @@ acker'' which
 ] [24]
 
 Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
-(hyperref)                removing `\leavevmode@ifvmode' on input line 436.
+(hyperref)                removing `\leavevmode@ifvmode' on input line 443.
 
 
 Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
 (hyperref)                \kern 1.66702pt
-(hyperref)                removed on input line 436.
+(hyperref)                removed on input line 443.
 
 [25]
-Overfull \hbox (8.25641pt too wide) in paragraph at lines 450--451
+Overfull \hbox (8.25641pt too wide) in paragraph at lines 457--458
 \OT1/jkp/m/n/10 vent that, add [][]\OT1/jkptt/m/n/10 \counterwithout{foootnote}
 {chapter} []\OT1/jkp/m/n/10 to the pream-
  []
 
-[26] [27]
+[26] [27] [28]
-Package atveryend Info: Empty hook `BeforeClearDocument' on input line 493.
+Package atveryend Info: Empty hook `BeforeClearDocument' on input line 500.
- [28]
+ [29]
-Package atveryend Info: Empty hook `AfterLastShipout' on input line 493.
+Package atveryend Info: Empty hook `AfterLastShipout' on input line 500.
  (build/codex-001.aux)
-Package atveryend Info: Executing hook `AtVeryEndDocument' on input line 493.
+Package atveryend Info: Executing hook `AtVeryEndDocument' on input line 500.
-Package atveryend Info: Executing hook `AtEndAfterFileList' on input line 493.
+Package atveryend Info: Executing hook `AtEndAfterFileList' on input line 500.
 Package rerunfilecheck Info: File `codex-001.out' has not changed.
 (rerunfilecheck)             Checksum: <no file>.
-Package atveryend Info: Empty hook `AtVeryVeryEnd' on input line 493.
+Package atveryend Info: Empty hook `AtVeryVeryEnd' on input line 500.
  ) 
 Here is how much of TeX's memory you used:
- 8538 strings out of 483140
+ 8540 strings out of 483140
- 120730 string characters out of 5965152
+ 120748 string characters out of 5965152
- 379450 words of memory out of 5000000
+ 379433 words of memory out of 5000000
  23238 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
- 34i,11n,45p,926b,441s stack positions out of 5000i,500n,10000p,200000b,80000s
+ 34i,11n,45p,976b,441s stack positions out of 5000i,500n,10000p,200000b,80000s
 {/usr/share/texlive/texmf-dist/fonts/enc/dvips/kpfonts/kpfonts-expert.enc}{/u
 sr/share/texlive/texmf-dist/fonts/enc/dvips/base/8r.enc}</usr/share/texlive/tex
 mf-dist/fonts/type1/public/kpfonts/jkpbit8a.pfb></usr/share/texlive/texmf-dist/
@@ -960,10 +960,10 @@ e1/public/kpfonts/jkpbne.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/
 kpfonts/jkpmit8a.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/
 jkpmn8a.pfb></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/jkpmne.pf
 b></usr/share/texlive/texmf-dist/fonts/type1/public/kpfonts/jkpttmn8a.pfb>
-Output written on build/codex-001.pdf (28 pages, 154326 bytes).
+Output written on build/codex-001.pdf (29 pages, 155945 bytes).
 PDF statistics:
- 455 PDF objects out of 1000 (max. 8388607)
+ 461 PDF objects out of 1000 (max. 8388607)
- 410 compressed objects within 5 object streams
+ 415 compressed objects within 5 object streams
- 119 named destinations out of 1000 (max. 500000)
+ 121 named destinations out of 1000 (max. 500000)
  283 words of extra memory for PDF output out of 10000 (max. 10000000)
 

001/build/codex-001.out

@@ -29,6 +29,7 @@
 \BOOKMARK [1][-]{section.3.17}{usr}{chapter.3}% 29
 \BOOKMARK [1][-]{section.3.18}{var}{chapter.3}% 30
 \BOOKMARK [0][-]{chapter.4}{Miscellany}{}% 31
-\BOOKMARK [1][-]{section.4.1}{Is This Really a Hack? Or Is It Just a Tip?}{chapter.4}% 32
+\BOOKMARK [1][-]{section.4.1}{A Scanner Darkly, but with a workflow}{chapter.4}% 32
-\BOOKMARK [1][-]{section.4.2}{What I Learned About LaTeX While Creating This Issue}{chapter.4}% 33
+\BOOKMARK [1][-]{section.4.2}{Is This Really a Hack? Or Is It Just a Tip?}{chapter.4}% 33
-\BOOKMARK [1][-]{section.4.3}{Coda: Why LaTeX?}{chapter.4}% 34
+\BOOKMARK [1][-]{section.4.3}{What I Learned About LaTeX While Creating This Issue}{chapter.4}% 34
+\BOOKMARK [1][-]{section.4.4}{Coda: Why LaTeX?}{chapter.4}% 35

001/build/codex-001.toc

@@ -29,6 +29,7 @@
 \contentsline {section}{\numberline {3.17}usr}{22}{section.3.17}%
 \contentsline {section}{\numberline {3.18}var}{22}{section.3.18}%
 \contentsline {chapter}{\numberline {4}Miscellany}{23}{chapter.4}%
-\contentsline {section}{\numberline {4.1}Is This Really a Hack? Or Is It Just a Tip?}{23}{section.4.1}%
+\contentsline {section}{\numberline {4.1}A Scanner Darkly, but with a workflow}{23}{section.4.1}%
-\contentsline {section}{\numberline {4.2}What I Learned About \LaTeX \tmspace +\thinmuskip {.1667em} While Creating This Issue}{25}{section.4.2}%
+\contentsline {section}{\numberline {4.2}Is This Really a Hack? Or Is It Just a Tip?}{23}{section.4.2}%
-\contentsline {section}{\numberline {4.3}Coda: Why \LaTeX ?}{27}{section.4.3}%
+\contentsline {section}{\numberline {4.3}What I Learned About \LaTeX \tmspace +\thinmuskip {.1667em} While Creating This Issue}{26}{section.4.3}%
+\contentsline {section}{\numberline {4.4}Coda: Why \LaTeX ?}{27}{section.4.4}%

001/codex-001.tex

@@ -60,7 +60,7 @@
 
 \author{Kenneth John Odle}
 \title{{\Huge the codex}\\{\footnotesize Life with Linux — A Zine\\Typeset in \LaTeX}}
-\date{5 September 2021\\\begin{small}2021.09.05\end{small}}
+\date{\begin{small}2021.09.16\end{small}}
 
 \begin{document}
 \maketitle
@@ -74,10 +74,12 @@ FYI, this is made in \LaTeX \,using the report document class. It then gets expo
 
 I'm pushing this to my own git server as I write this. You can find it \href{https://git.kjodle.net/kjodle/the-codex}{here}: \texttt{https://git.kjodle.net/kjodle/the-codex}. New issues will be pushed after they are complete.
 
-The image on the front cover is courtesy JericoDelayah from the WikiMedia Commons. The image is  \href{https://commons.wikimedia.org/wiki/File:4_RETAT_04_Linus_Torvalds.jpg}{over here}: \verb|https://commons.wikimedia.o| \verb|rg/wiki/File:4_RETAT_04_Linus_Torvalds.jpg|. You can also find a link to the Creative Commons CC BY-SA 3.0 license there, as well.
+The image of Linus Torvalds on the front cover is courtesy JericoDelayah from the WikiMedia Commons. The image is  \href{https://commons.wikimedia.org/wiki/File:4_RETAT_04_Linus_Torvalds.jpg}{over here}: \verb|https://commons.wikimedia.o| \verb|rg/wiki/File:4_RETAT_04_Linus_Torvalds.jpg|. You can also find a link to the Creative Commons CC BY-SA 3.0 license there, as well.
 
 The image on the back cover is one that I highly agree with. We built it, it's ours, and we shouldn't be charged for using it. I want my tax dollars to serve my needs. I don't want my tax dollars used to make rich white old men richer.
 
+(If you're reading this zine online in pdf form you won't see this cover, because it's not in this repo. You can check the \verb|.gitignore| file. If you \textit{really} want to see it, you'll need to buy a paper copy, which means we kill a tree and I get validation and a few buck, and you get a picture of Linus Torvalds that you can see online for free. Weird, huh?)
+
 You can just skip over all the diversions in you want. It's just how my mind works. (And yes, there will be politics in this. \textit{You have been warned.}) Also, I use a lot of em-dashes and parentheses because that is also how my mind works. It's just one big long stream of consciousness up in here most days.
 
 \tableofcontents
@@ -96,14 +98,14 @@ I mean, \textit{sure} you can get your kid that Casio, which has all the same fe
 
 \textbf{Oh my, a diversion already.}
 \begin{multicols}{2}
-(A little off track here, but this begs two questions: 1) Why is it always a TI calculator that's required, and 2) Are we teaching kids to learn math or to learn how to operate a calculator? The answer to the first question is that Texas Instruments and the Major Textbook Publishers\texttrademark \, have colluded to produce expensive books that need to be replaced every two to three years [thereby costing the school district money] and that require expensive calculators\footnote{A few years ago, I bought a scientific calculator at the \textbf{dollar store} and tested it against my very expensive TI-92. It was just as accurate as the more expensive calculator, and cheaper by two orders of magnitude. Did I mention that this is a racket? I really should do a YouTube video or blog post about this.} [thereby costing you as a parent money]. It's a racket, but that's capitalism for you.
+A little off track here, but this begs two questions: 1) Why is it always a TI calculator that's required, and 2) Are we teaching kids to learn math or to learn how to operate a calculator? The answer to the first question is that Texas Instruments and the Major Textbook Publishers\texttrademark \, have colluded to produce expensive books that need to be replaced every two to three years [thereby costing the school district money] and that require expensive calculators\footnote{A few years ago, I bought a scientific calculator at the \textbf{dollar store} and tested it against my very expensive TI-92. It was just as accurate as the more expensive calculator, and cheaper by two orders of magnitude. Did I mention that this is a racket? I really should do a YouTube video or blog post about this.} [thereby costing you as a parent money]. It's a racket, but that's capitalism for you.
 
-The answer to the second question is that we are teaching kids how to use calculators. Teaching them how to do actual math would require thought on both the parts of the teachers\footnote{To be fair, a lot of teachers would like to teach kids how to do actual math. But they also need to eat and when it comes down to the difference between doing what is right and doing what pays the bills, they will do the latter. It's not their fault, really; it's just that the system does not like anybody who sticks out. Keep your head down and the worksheets graded—that's what the system rewards.} and the parts of the students, not to mention on the parts of parents and especially administrators, who would also be required to grow a spine—and learn how to use it. Again, education in the United States has become a racket, but that's capitalism for you.)
+The answer to the second question is that we are teaching kids how to use calculators. Teaching them how to do actual math would require thought on both the parts of the teachers\footnote{To be fair, a lot of teachers would like to teach kids how to do actual math. But they also need to eat and when it comes down to the difference between doing what is right and doing what pays the bills, they will do the latter. It's not their fault, really; it's just that the system does not like anybody who sticks out. Keep your head down and the worksheets graded—that's what the system rewards.} and the parts of the students, not to mention on the parts of parents and especially of  administrators, who would also be required to grow a spine—and learn how to use it. Again, education in the United States has become a racket, but that's capitalism for you.
 \end{multicols}
 
 \hrulefill
 
-(Well, you can probably tell what my thoughts are on the dominant economic system on planet Earth. There \textit{will} be more of that. If you're okay with that, I'm okay with that, too. If you're not okay with it and you want your money back, it's too late—I've already spent it.\footnote{But that's capitalism for you!})
+(Well, you can probably tell what my thoughts are on the dominant economic system on planet Earth. There \textit{will} be more of that. If you're okay with that, I'm okay with that, too. If you're not okay with it and you want your money back, it's too late—I've already spent it.\footnote{But that's capitalism for you! \textit{Caveat emptor!}})
 
 I have noticed that even little kids are required to bring little kid calculators to school with them in most of the local school districts. As I write this, the school supply buying season is coming to an end, but for the past six weeks every store was filled with school supply lists and yeah, you have to have a calculator to get into the second grade.
 
@@ -117,11 +119,11 @@ The other early calculator I remember was a Casio calculator and it was on a wat
  \includegraphics[scale=0.15]{casio}
 \end{wrapfigure}
 
-Well, I grew up and I didn't buy one of them, even though they are still available. I could just never justify spending the money on what is—let's face it—just a bit of full-frontal nerdity when there were bills to pay. Nope, just could never bring myself to do it.
+Well, I grew up and I didn't buy one of them, even though they are still available. I could never justify spending the money on what is—let's face it—just a bit of full-frontal nerdity when there were bills to pay. Nope, just could never bring myself to do it.
 
 It's just me now, and my expenses are numerous but small, and a couple of years ago my local all-in-one-store had all their watches on sale for 40\% off, including the name brand watches. I checked—it was in stock. At \$25 bucks it was a lot, but on sale it was only \$15. I could do this! So I picked it up and looked at it lovingly, thinking about all the good times we would have together as we went forth and explored the world one simple calculation at a time.
 
-But there was a problem. A rather large problem, actually. The print on those buttons is tiny. And my eyes are bad. I couldn't actually read any of buttons. I use reading glasses when I'm reading or working on the computer, but I don't need them out in the wild. I could wear the watch with me everywhere, but unless I were at my desk, I wouldn't be able to actually use it.
+But there was a problem. A rather large problem, actually. The print on those buttons is tiny. And my eyes are bad. I couldn't actually read any of the buttons. I use reading glasses when I'm reading or working on the computer, but I don't need them out in the wild. I could wear the watch with me everywhere, but unless I were at my desk, I wouldn't be able to actually use it.
 
 Back on the shelf it went. I'm not going to spend money on something that is not actually useful to me.
 
@@ -135,11 +137,11 @@ I don't remember much about it, actually, other than it was small and sleek and
 
 This is where memory gets wonky, because I remember seeing this when I was about ten years old. But according to Wikipedia, the Timex Sinclair\footnotemark was released in 1982, when I would have been 14 years old. So it's entirely possible that my memory is losing track of \textit{when} things happened, or it's possible that this aunt had some other home computer that for whatever reason my brain thinks is a Timex Sinclair. Who knows? I certainly don't, and I'll probably never find out for sure.
 
-\footnotetext{It was called the Timex Sinclair because this was a collaboration between the Time Corporation and the Sinclair Corporation. I imagine Sinclair handled the R\&D and manufacturing and Timex handled the marketing. If so, Timex didn't \textit{technically} make a computer, but they wanted us to think that they did. Good enough for me.}
+\footnotetext{It was called the Timex Sinclair because this was a collaboration between the Timex Corporation and the Sinclair Corporation. I imagine Sinclair handled the R\&D and manufacturing and Timex handled the marketing. If so, Timex didn't \textit{technically} make a computer, but they wanted us to think that they did. Good enough for me.}
 
 \section{The Joy of a Trash-80}
 
-One thing I'm quite sure about is that in seventh grade a select group of smart kids from my class were allowed to go to the local ``skills center''\footnote{This was a centralized school where eleventh and twelfth graders who definitely weren't going on to college could take classes like agriculture and welding. We used to teach these classes in each school under the guise of ``vocational education'' but somehow lost our way.} one day a week (Wednesday afternoons, as I recall) to study computers. This was the first time I'd every laid my fingers on an actual computer keyboard.
+One thing I'm quite sure about is that in seventh grade a select group of smart kids from my class were allowed to go to the local ``skills center''\footnote{This was a centralized school where eleventh and twelfth graders who definitely weren't going on to college could take classes like agriculture and welding. We used to teach these classes in each school under the guise of ``vocational education'' but somehow lost our way.} one day a week (Wednesday afternoons, as I recall) to study computers. This was the first time I'd ever laid my fingers on an actual computer keyboard.
 
 \hrulefill
 
@@ -149,7 +151,7 @@ One thing I'm quite sure about is that in seventh grade a select group of smart
 
 Those of us with fond memories of Radio Shack, and what it used to be, bristle at the memory of how it was terribly mismanaged at the end of its life. But in some weird postmodern way, Radio Shack does live on, but not as you might expect. 
 
-A brief history shall ensue.
+A brief history shall ensue:
 
 Radio Shack was founded in 1921 by Theodore and Milton Deutschmann, two brothers who wanted to cash in on the burgeoning ham radio field. Initially successful, it was nearly bankrupt in 1962, when it was acquired by the Tandy Corporation. If you've ever been in 4H, that name may ring a bell. Tandy is a leather goods corporation, and has been selling supplies for home leathercrafters since 1919. If you did leathercrafting as a 4H kid, chances are the introductory tool kit and all the materials you needed to make that belt or wallet, came from Tandy Leather Company.
 
@@ -210,6 +212,8 @@ There is no ``undo'' on the command line.
 
 I need to get that on a t-shirt.
 
+\medskip
+
 Why? Because the command line is like real life. There is no undo button in real life. GUIs have made us lazy—lazy at thinking, lazy at figuring things out. Just do it, if you don't like it, just Ctrl-Z. Just throw that document away and leave it in the recycle bin. If you decide you want/need it later, you can just drag it on out of there.
 
 With a GUI, that ``undo'' button is always an option.\footnote{Except for the rare occasion when it isn't. Those times are fun.} But in real life, you can't \textit{unmake} a mistake. Sure, you can recover from a mistake, but you are going to have to do some scrambling, my friend, and if you are at least halfway intelligent, you will definitely think twice about trying that again, or at least trying it \textit{that way} again. You don't want to jump through all those hoops again, so you think about your end goal and try to develop a better workflow for next time.
@@ -228,7 +232,7 @@ Unfortunately, it seems that it's impossible to build a device that will do a la
 
 I absolutely \textit{love} this thing for slicing potatoes, and since I spend each autumn and winter making scalloped potatoes or au gratin potatoes, it sees a lot of use during those months when the days are short. It does a fantastic job slicing potatoes into a uniform thickness and does it far more quickly than I can do it with a knife.
 
-It also includes inserts to make waffle slices (if you rotate the potato 90 degrees on each pass, you're supposed to be able to make waffle fries), inserts for dicing onions, and so forth. But here's the thing: as great as it is at slicing potatoes (and also carrots, which have the same general hardness as potatoes), it does a terrible job at slicing anything else. Basically, the thin and the thick slicing inserts work well for potatoes and carrots, and all the other inserts don't work at all for them, and any other vegetable just doesn't get cut or gets crushed because you have to hold onto it so hard.
+It also includes inserts to make waffle slices (if you rotate the potato 90 degrees on each pass, you're supposed to be able to make waffle fries), inserts for dicing onions, and so forth. But here's the thing: as great as it is at slicing potatoes (and also carrots, which have the same general hardness as potatoes), it does a terrible job at slicing anything else. Basically, the thin and the thick slicing inserts work well for potatoes and carrots, and all the other inserts don't work at all for them, and any other vegetable just doesn't get cut or gets crushed because you have to hold onto it so firmly.
 
 I don't know how much my parents spent on this thing, but if it's anything north of \$20, that's a lot of money for something I can already do fairly easily (and actually enjoy doing) with a sharp knife. Don't get me wrong—I love the thing (even though it's a bit of a pain to clean), but if we had spent at least as much time and money engineering the thing as we did marketing it, we might have concluded that it would probably be better to just encourage people to buy decent knives and then teach them how to sharpen them and use them properly.
 
@@ -257,10 +261,10 @@ Sure, there are always those oddball tasks that you have to do once a year or le
  \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. 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.
+ \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!) cheese knife that did an okay job; it also had a two-prong fork on the end to pick up the slice of cheese with. My current one has 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\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.
+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. (Go to your terminal and type in \verb|man knife|.)
 
 \medskip
 
@@ -287,21 +291,19 @@ I've resisted buying a breadmaker for years, because I actually don't want a dev
 \chapter{What Are All Those Files in the Linux Root?}
 
 If you're using a Linux distro with a GUI (Ubuntu, Puppy OS, Mint, etc.) you land right in your Home folder whenever you click on ``Files''. But if you've ever gone all the way into the root of your computer (the Windows equivalent would be \verb|C:\|) you'll see a lot of folders\footnote{Technically, these are \textit{directories}, but let's not be pedantic. In a GUI, the icon usually looks like a folder.} there with mysterious three-letter names. Let's take a look at the them and what they contain.\footnotemark
-\footnotetext{For more information about this, consult the Linux Foundation Referenced specifications, which are found at \href{https://refspecs.linuxfoundation.org/}{https://refspecs.linuxfoundation.org/}. You're probably going to want the pdf version of this, which is at \href{https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf}{https://refspecs.linuxfoundation.org/FHS\_3.0/fhs-3.0.pdf}. It really is amazing how much you can learn just by reading the specs and manuals.}
+\footnotetext{For more information about this, consult the Linux Foundation Referenced specifications, which are found at \href{https://refspecs.linuxfoundation.org/}{https://refspecs.linuxfoundation.org/}. You're probably going to want the pdf version of this, which is at \href{https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf}{https://refspecs.linuxfoundation.org/FHS\_3.0/fhs-3.0.pdf}. It really is amazing how much you can learn just by reading the specs and manuals. Scotty was right.}
 
 \section{bin}
 This directory contains essential command binaries\footnote{Files that contain compiled source or machine code. They are also called ``executables'' because they can be run (i.e., ``executed'') on the computer. Programs, if you will.} that need to be available for all users. Many of these include binaries that bring up the system or repair it. Your basic binaries like \verb|cat|, \verb|ls|, and \verb|mv| live here.
 
 \section{boot}
-Boot loader files. (It's complicated—kernels, and so forth. It is also four letters instead of three.)
+Boot loader files. It's complicated—kernels, and so forth. It is also four letters instead of three. I don't really understand it, but I'll look into it.
 
 \section{dev}
 Device files, such as \verb|/dev/disk0/|, \verb|dev/sda1|, etc. Also the home of the wonderful \verb|/dev/null|.
 
 \section{etc}
-System-wide static configuration files. It is not allowed to contain binaries.
+System-wide static configuration files. It is \textbf{not} allowed to contain binaries. Some examples include:
-
-Some examples include:
 
 \medskip
 
@@ -323,7 +325,7 @@ Some examples include:
 Users' home directories. If you have multiple users, you will see a directory in here for each user, named after their login name. Their personal settings are stored as invisible files in their home directory.
 
 \section{lib}
-This directory contains libraries that are essential for the binaries in \verb|/bin| and \verb|/sbin|. It also contains kernel module, whose filenames are identifiable as \verb|ld*| or \verb|lib*.so.*|. Unlike bin, it only contains system binaries which require root privilege.
+This directory contains libraries that are essential for the binaries in \verb|/bin| and \verb|/sbin|. Unlike bin, it only contains system binaries which require root privilege.
 
 \medskip
 
@@ -331,7 +333,7 @@ This directory contains libraries that are essential for the binaries in \verb|/
 
 \medskip
 
-\noindent \textbf{lib/modules} — This directory stores kernel modules (pieces of code that can be loaded and unloaded into the kernel upon demand, adding functionality to the kernel without needing to reboot the system\footnote{Handy, that.}), with each installed kernel having its own directory. The Linux kernel typically loads kernel modules from the appropriate kernel version directory. 
+\noindent \textbf{lib/modules} — This directory stores kernel modules (pieces of code that can be loaded and unloaded into the kernel upon demand, adding functionality to the kernel without needing to reboot the system\footnote{Handy, that.}), with each installed kernel having its own directory. Their filenames are identifiable as \verb|ld*| or \verb|lib*.so.*|. The Linux kernel typically loads kernel modules from the appropriate kernel version directory. 
 
 To show which kernel modules are currently loaded, run
 
@@ -401,6 +403,11 @@ This directory contains files who content is expected to continually change duri
 
 \chapter{Miscellany}
 
+\section{A Scanner Darkly, but with a workflow}
+I suppose I should have been an archivist.
+
+tips about pdftk. (What were these? from the man pages.)
+
 \section{Is This Really a Hack? Or Is It Just a Tip?}
 The word ``hacker'' has a lot of defitions, and if you just google it, you'll find a lot of scary ones on the websites of companies that want you to be scared of ``hackers'' and spend hundreds of dollars on their security products, some of which may actually protect you against actual threats, and some of which may provide protection against a threat which isn't actually real.
 
@@ -410,15 +417,15 @@ Rather, I'm talking about the older meaning of the term ``hacker'' which is some
 
 Of course, this term originally referred to computer technology, but now I'm finding that people are using it everywhere, even in places where it doesn't belong. (I'm looking at you, the writers and editors of apparently every food magazine and website ever.)
 
-So let's look at some things that have been called ``hacks'' but may or may not be actual hacks.
+So let's look at some things that have been called ``hacks'' but may or may not be actual hacks. These all came from cooking websites that were at the top of a google search for ``cooking hacks.''
 
 \begin{enumerate}
  \itemsep-0.20em
- \item \textbf{How to cut up a mango} — Not a hack. In fact, I'd argue that this is just basic knowledge. Chop up one ripe mango the wrong way and you'll be googling how to do that pretty darn quick.
+ \item \textbf{How to cut up a mango} — Not a hack. In fact, I'd argue that this is just basic knowledge. Chop up one ripe mango the wrong way and you'll be googling the right way to do that pretty darn quick.
- \item \textbf{Using an ice cube tray to make sushi (in lieu of using a bamboo sushi roller)} — While you are using a common device in an uncommon way, I don't think this rises to the level of a hack. There are a lot of ways to put raw fish and rice together.\footnote{Also, be sure to sanitize the hell of that ice cube tray before you use it to make ice again.}
+ \item \textbf{Use an ice cube tray to make sushi (in lieu of using a bamboo sushi roller)} — While you are using a common device in an uncommon way, I don't think this rises to the level of a hack. There are a lot of ways to put raw fish and rice together.\footnote{Also, be sure to sanitize the hell of that ice cube tray before you use it to make ice again.}
- \item \textbf{Making hot chocolate cocoa bombs} — Not a hack. A technique, to be certain, but not a hack.
+ \item \textbf{Make hot chocolate cocoa bombs} — Not a hack. A technique, to be certain, but not a hack.
- \item \textbf{Punching holes in your sausage with a toothpick before cooking to keep them from exploding} — A useful tip (especially in the air fryer), but definitely not a hack.
+ \item \textbf{Punch holes in your sausage with a toothpick before cooking to keep them from exploding} — A useful tip (especially in the air fryer), but definitely not a hack.
- \item \textbf{Use a spiralizer for perfect baked curly fries} — Really? Next we'll have ``Use a hammer to pound nails into wood'' or ``Use a pencil to make marks on paper.'' Using a tool for what it's meant to be used for is not a hack.
+ \item \textbf{Use a spiralizer for perfect baked curly fries} — Really? Next we'll have ``Use a hammer to pound nails into wood'' or ``Use a pencil to make marks on paper.'' Using a tool for what it's meant to be used for is not a hack. The unique thing here is ``baked'' and that has nothing to do with a spiralizer.
  \item \textbf{Peel ginger with a spoon} — This is most definitely not what you're supposed to use a spoon for. But this works great. I'll call this one a hack, but just barely. If I used ginger all the time, I'd probably just call this a technique.
  \item \textbf{Microwave lemons and limes to get more juice out of them} — A tip, not a hack.
  \item \textbf{Freeze cheese to make it easier to grate} — I do this all the time, and it's a great technique. The trick is leave the cheese in the freezer for just the right amount of time. Not a hack.
@@ -428,7 +435,7 @@ So let's look at some things that have been called ``hacks'' but may or may not
  \item \textbf{Flavor your pasta water with a chicken stock cube} — Not a hack. Anyone who grew up eating instant ramen on a regular basis figured this one out by the time they hit double digits.
  \item \textbf{Use a potato masher to break up ground meat} — While technically a potato masher is meant to be used on potatoes, its ultimate purpose is to mash big things into little things.\footnote{It's right there in the name!} This is like using a screwdriver to pry up a lid of paint. It's not a hack because it's so obvious.
  \item \textbf{Collect all your vegetable scraps in a freezer bag and use them to make stock} — Not a hack. Just frugality in action.
- \item \textbf{Buy the biggest cutting board you can find.} — While this is great advice, it's not a hack.
+ \item \textbf{Buy the biggest cutting board you can find} — While this is great advice, it's not a hack.
 \end{enumerate}
 
 So, 15 ``cooking hacks'' and only two of them are an actual hacks, and one of them is pretty questionable. I'm pretty much calling it a hack because I'm trying to be generous. The thing that strikes me is not so much that these aren't actually hacks, but the difference between a ``tip'' and a ``technique.'' Maybe I'm just tired, but it seems like it's a technique if you use it on a regular basis and a tip if you're in a jam and someone tells you about it. But that's an argument for another day in another zine.
@@ -462,13 +469,13 @@ As for why I wanted to learn LaTeX in the first place—well, that's complicated
 
 I knew in the back of my mind that there was this great typesetting thing specifically for math and scientific papers, but it took me a while to find it. (This was back in the days before the internet.) But I could recognize just about any paper typeset with it.
 
-Is LaTeX the ideal thing to create zines with? Not necessarily. It does give the finished product a very polished look, and although I love the handmade look (i.e., ``clip and copy'') of a lot of zines, I don't have the talent (or the patience) required to pull that look off. The important thing for me is to be able to create something that is easy on the eyes. (And I've see a lot of handmade zines that \textit{aren't} easy on the eyes.)
+Is LaTeX the ideal thing to create zines with? Not necessarily. It does give the finished product a very polished look, and although I love the handmade look (i.e., ``clip and copy'') of a lot of zines, I don't have the talent (or the patience) required to pull that look off. The important thing for me is to be able to create something that is easy on the eyes. (And I've seen a lot of handmade zines that \textit{aren't} easy on the eyes.)
 
 I've created zines in the past, and I've previously used Adobe InDesign (back in my Macintosh days) and LibreOffice Writer (more recently). They are WYSIWYG\footnote{What You See Is What You Get} programs and it's fairly easy to get what you want (more or less).
 
 (They can be a pain in other ways, however. InDesign used a lot of resources on the little Mac Mini I was using and crashes, while not frequent, were not unknown. LibreOffice has certain interface quirks that I just find frustrating, such as using sections to have different footers or headers. You can't have everything.)
 
-However, they aren't very amenable to version control, because they don't generate text files, but proprietary files. (I'm not sure about InDesign files, but .odt files are just a collection of \verb|.xml| files and a few others. Change the \verb|.odt| to \verb|.zip| to see them.) While you can track this files in with version control software such as \verb|git|, you can't see the differences between those files by running a simple \verb|git diff|. You have to download the files in question, make sure they have different names so they don't overwrite each other, and check for differences manually.\footnotemark
+However, they aren't very amenable to version control, because they don't generate text files, but proprietary files. (I'm not sure about InDesign files, but .odt files are just a collection of \verb|.xml| files and a few others. Change the \verb|.odt| to \verb|.zip| to see them.) While you can track these files in with version control software such as \verb|git|, you can't see the differences between those files by running a simple \verb|git diff|. You have to download the files in question, make sure they have different names so they don't overwrite each other, and check for differences manually.\footnotemark
 \footnotetext{As a result, to do version control, I used a version number in the file name and simply did a ``save as'' every time I opened the file for editing, incrementing the version number as I did so.} 
 
 With LaTeX however, your \verb|.tex| file really is just a text file, and so if you use something like \verb|git| to track changes, you can run a \verb|git diff| and see changes from one commit to the other pretty easily. This is nice when you are writing, because if something is working, you can just delete it, and if you decide you can use it after all, you can just go back to the repo and get it.